Database Users

[Q] Will this work for our WF?

Found this thread on the HTC Hero section for it's open GL will this work for our wildfire?
http://forum.xda-developers.com/showthread.php?t=899801

Yea I flashed it, noticed an improvement in playing angry birds...i think.
Sent from my HTC Wildfire using XDA App

Will it work on cm7 nightlies kevin?
Sent from my HTC Wildfire using XDA App

Yeah
Sent from my HTC Wildfire using XDA App

Yes it works with just about every ROM, but, in my view, I can't see any benefit. (I dont play Angry Birds, and, the rest of the games and LWP's don't show any benefit).

How do you do this?
Just flash it like a rom?

Well, that's what I initially did. Flash the ZIP in Post #49 in that thread. But, on reading that complete thread, I guess you have to edit the build.prop file in /system (Using Root Explorer / ADB Push Pull).
However, this is where I cant get it to work. WHenever I add the 2 lines in Root Explorer and Save Changes, the phone reboots. If I use ADB, even after pushing, when I check the same file using build.prop, no changes are visible, (The opengles.version automatically reverts back to 65536 and the line which enabled hardware acceleration of the UI is gone) and, ASI only shows OpenGL 1.0 due to this
Well, I have no idea what I am doing wrong, will try it out again and see..

I'm a newb with this.
Could someone possibly make a bit more explained guide?

Very basic guide:
* Get Root Explorer or any other file manager that can show the root folders
* Open Root Explorer, change permissions on top to R/W (Be very careful after that. Dont delete anything!)
* Locate the file build.prop under /system
* Long Press the file, Select Edit with Text Editor
* Updated: (ADB Commands Copy - Pasted from another post by kevin2516. Thanks mate )
*Make sure ADB is installed on your system and it is working. There are many guides available to install ADB, so I wont be going into that.
*Start Command Prompt (cmd), Browse to your "Tools" folder into your SDK
*Use the ADB Pull Command adb pull /system/build.prop
*This will now be saved to your tools folder. Edit is using Wordpad / Notepad++ (Not Notepad) as follows:
*Locate a line which starts with dalvik. (The first one, there are 3 of them)
Add the following 2 lines before that:
debug.sf.hw=1
ro.opengles.version=65537
* Save it.
* Push it back to System using the ADB Push Command: adb push build.prop /system/build.prop
* Reboot ADB using the adb reboot command
* Then, grab the Flashable Zip in that thread from Post #48
* Flash it as normal
Done.
Check whether it is implemented or not by going to Android System Info > System Tab > OpenGL. Here, there are 2 OpenGL versions. The first line should say 1.1, and the second should say OpenGL 1.0 ES.

With S-On you cannot change the systemfile directly I think. Thats the reason why your system not keep the change. I have write by myself a little install zip and flash it with nandroid and it works. the zip only works with wildpuzzlerom v0.8 and you can find in the thread for wpr0.8.

bgx said:
With S-On you cannot change the systemfile directly I think. Thats the reason why your system not keep the change. I have write by myself a little install zip and flash it with nandroid and it works. the zip only works with wildpuzzlerom v0.8 and you can find in the thread for wpr0.8.
Click to expand...
Click to collapse
Well, I took your flashable ZIP, removed the build.prop it contained, and replaced it with the build.prop of CM7 Nightly 2. Then, I tried flashing it, still no change.
Now, I have no idea whether I am 'allowed' to change flashable ZIP's like that or not, but, from what it is looking like, I am still unable to get this working on CM7NB2. I'll probably try making a flashable ZIP from scratch later as I get time.

bgx said:
I have write by myself a little install zip and flash it with nandroid and it works. the zip only works with wildpuzzlerom v0.8 and you can find in the thread for wpr0.8.
Click to expand...
Click to collapse
If it's simple enough, it would be nice if you could tell how to do a flashable zip (or yourself make a one suitable for CM6/7 ). I just want to test these libraries on CM7, any help is appreciated
Don't expect nothing special, I'm not a dev!

3xeno said:
Very basic guide:
* Get Root Explorer or any other file manager that can show the root folders
* Open Root Explorer, change permissions on top to R/W (Be very careful after that. Dont delete anything!)
* Locate the file build.prop under /system
* Long Press the file, Select Edit with Text Editor
* Then, locate a line which starts with dalvik. (The first one, there are 3 of them)
* Add the following 2 lines before that:
debug.sf.hw=1
ro.opengles.version=65537
* Save and Exit
* Then, grab the Flashable Zip in that thread from Post #48
* Flash it as normal
Done.
Check whether it is implemented or not by going to Android System Info > System Tab > OpenGL. Here, there are 2 OpenGL versions. The first line should say 1.1, and the second should say OpenGL 1.0 ES.
Click to expand...
Click to collapse
But it's not working for CM7?
Where can i find FLashable zip? I don't understand where is post #48
Even if i find, i have read, that it's not working? Or working?

You can find the OpenGLES 1.1 Flashable ZIP in Post #48 of this thread:
http://forum.xda-developers.com/showthread.php?t=899801
I have updated my post since Root Explorer method doesnt work (No S-OFF).

3xeno said:
You can find the OpenGLES 1.1 Flashable ZIP in Post #48 of this thread:
http://forum.xda-developers.com/showthread.php?t=899801
I have updated my post since Root Explorer method doesnt work (No S-OFF).
Click to expand...
Click to collapse
You wrote : last edit: I didn't notice any difference, much like the test ran above. I'm going to revert until more knowledgeable people look at this.
if it is like you saying, then i dont have point to that **** too.
i think devs who makes this rom should instal in rom everything what can increase perfomance. so im waiting for the rom with all those things instaled.
will it happen someday?:/

vilks said:
You wrote : last edit: I didn't notice any difference, much like the test ran above. I'm going to revert until more knowledgeable people look at this.
if it is like you saying, then i dont have point to that **** too.
i think devs who makes this rom should instal in rom everything what can increase perfomance. so im waiting for the rom with all those things instaled.
will it happen someday?:/
Click to expand...
Click to collapse
Which is exactly what I said in the CM7 thread. No one here has till date, found verifiable gains, with using OpenGL on the Wildfire. Everyone reports the same thing, that there is no or absolutely negligible (Which I think is just a mind thing) change in gaming / intensive applications performance.
If you are looking for ROM's wit inbuilt OpenGLES Support, WildPuzzle has a flashable ZIP, and DS and DK Roms provides it inbuilt in its latest version. For the others, the manual method has to be followed.

Overclocking Daemon with or without RAM optimizations

This is a tweak of this thread to work with the nexus. I claim no credit what so ever. All the work was done by Smokin1337, Rmk40, Juwe11, Sybregunne, and -viperboy-, I just tweaked it a bit to work with the nexus.
I am using this at the moment with the latest MIUI.us rom (1.8.26) and it is working for me. I am unsure about other roms but I imagine that it will work with CM because it supports init.d.
Install this from recovery and make sure to make a backup before because I guarantee nothing. Make sure to remove any overclocking apps otherwise the daemon wont work. A lowmemorykiller app such as autokiller will change the values set by the RAM script therefore you might want to remove that too.
More info on the overclock daemon here. http://forum.xda-developers.com/showpost.php?p=14529333&postcount=5
More info on the RAM optimization. http://forum.xda-developers.com/showpost.php?p=14446249&postcount=1
A nice graphical tool that allows users to change Virtuous_OC frequencies and governors. http://forum.xda-developers.com/showpost.php?p=16726715&postcount=2
edit:
updated zips because i messed up the update-script on the original ones.

flashed zip and installed apk but cant get the gui to work the apply button doesnt allow it to apply, 1.8.26 miui

which gui version are you using? I used 2.11 and it works for me.

2.11 hangs on the loading screen for me...i get further with 1.21 but not by much

probably hanging because the install didnt work. Using adb shell, terminal emulator, or root explorer verify that the virtuous_oc folder got installed to /system/etc and has the 6 adjustable files inside of it. I will do a clean wipe on my phone and give it a try again with the files from the OP.

OK so I messed up on the update-script, I am still new to this. The OP will have the updated zips.
to tell if its working go to adb shell or a terminal emulator and type
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
it should change when you wake and sleep the phone
edit:
lol just thought about this. Will be kinda hard to check to see if it is working from a terminal emulator.

Working now thanks
Sent from my Nexus One using XDA App

[GUIDE] Make VooDoo Settings Stick on Boot

FIRST: Supercurio makes a really awesome app, so I highly recommend purchasing the pro version to support further development for two reasons. First, it's the right thing to do and second, I haven't figured out how to make all of the VooDoo sound settings work yet, and I'm a busy college student in my senior year attempting to convince someone to pay me, so I don't have much time on my hands (thus my erratic shower schedule).
That being said, I have attached a script that I run on boot. That being said, I'm running AOSP's oiCSv43 ROM with Eugene's Speedy 2 kernel. So long as your kernel supports the following options (which will be listed below), you shouldn't have a problem with this script. I've also verified that it works just peachy with GLaDOS 2.5 for ICS-- another very good ICS kernel [I head 2.6 is quite nice]. (This should also work for GB roms if anyone cares to test for me)
You must have
root
superuser
busybox, or an alternate way to mount /system as writable (there are 2 other methods AFAIK)
ROM that supports init.d scripts OR scripter or some other app like it (in this case, you can just add the script to scripter and set it to run on boot)
If you don't (know if you) have init.d support, check out this post by damnmisur about scripting with ROM Toolbox
This script changes the following:
cpu governor -> interactive
max freq->1000mhz
min freq->150mhz
touchwake enabled with 10 second delay
back light dimmer settings are commented out, so it uses whatever is default for you kernel
bln enabled with blink disabled
blx commented out (reverts to kernel default which is likely 96%)
voodoo_color/red_multiplier->2724764160
voodoo_color/green_multiplier->3059586880
voodoo_color/blue_multiplier->2944130880
voodoo_color/red_v1_offset->-26
voodoo_color/green_v1_offset->-30
voodoo_color/blue_v1_offset->-33
voodoo sound anti-jitter, hi-fi play, hi-fi record, dac direct, voodoo sound control enabled
headphone_amplifier_level->+3db
voodoo sound mono downmix disabled
USE AT YOUR OWN RISK! I AM NOT LIABLE IF ANYTHING GOES WRONG!!!
NANDROID NANDROID NANDROID.
ALWAYS MAKE A BACKUP
NANDROID
The script is in the zip. To install:
Unzip archive into same directory as adb (or wherever you want if you know what you're doing)
open a terminal
Code:
adb remount
adb shell
su
busybox mount -o remount,rw /system
exit
adb push 99whirlpool-Speedy_2 /system/etc/init.d/99whirlpool-Speedy_2
adb shell
chmod 755 /system/etc/init.d/99whirlpool-Speedy_2 && reboot
The file has no extension! If you want to edit it, open it in a text editor. If you don't know what you're doing, don't play with it. To disable boolean values, change the 1 (1 means true i.e. on) to a 0 (which means false, i.e. off).
frequency values are in hertz
you can find out what scaling governors and frequencies your kernel supports by typing
Code:
adb shell
su
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
Feel free to edit anything you'd like!
DO NOT FLASH THE .ZIP FILE! Extract and follow the directions above

thanks....

Nice but some of your changes are the exact opposite of what I use. So I'll just change voodoo settings because I'll be a lot less to change with every boot than if I was to use this.
I do of course use easy settings. Color multipliyer: all the way right.
Gama: all the way left.
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.

Thank you.

Don't voodoo settings stick by default? It seems my voodoo settings stick just fine without using any script?

Si_NZ said:
Don't voodoo settings stick by default? It seems my voodoo settings stick just fine without using any script?
Click to expand...
Click to collapse
They do with the PRO version, not the free one. I've also never had a problem with them NOT sticking on Pete Alfonso's GPA19, or any GB ROM for that matter, but many ICS users, including myself, have not been able to get our settings to stick recently.
This also means that I don't have to use NSTools or VooDoo Control.
Translation:
no apps changing settings on boot->
fewer individual SU requests (count the number of toast notifications, or check the request list in the superuser app for NSTools and VooDoo control on boot)->
faster boot sequence, and less lag on boot.
Not everyone may have this problem, but I and others do.

I'm visiting for a lesson, had read this before on aosp's or Eugene's kernel threads, but didn't get it so, wanted to ask and thank you for this help.
I'm trying to make voodoo stick, I downloaded your zip, opened and changed a couple of things in Wordpad, it asked to save and rezip, said yes. I used different multipliers and want bln to blink, so changed those numbers and the blink 0 to 1 (or vice versa, followed your directions).
So to do this, do I just flash zip in recovery? Any wipe or just flash away??
Like you said, I will backup, but really don't want to make a mess and thought I would double check first.

nmoreman said:
I'm visiting for a lesson, had read this before on aosp's or Eugene's kernel threads, but didn't get it so, wanted to ask and thank you for this help.
I'm trying to make voodoo stick, I downloaded your zip, opened and changed a couple of things in Wordpad, it asked to save and rezip, said yes. I used different multipliers and want bln to blink, so changed those numbers and the blink 0 to 1 (or vice versa, followed your directions).
So to do this, do I just flash zip in recovery? Any wipe or just flash away??
Like you said, I will backup, but really don't want to make a mess and thought I would double check first.
Click to expand...
Click to collapse
Don't flash the zip. It's just there so that I could upload the attachment properly.
The script is in the zip. To install:
Unzip archive into same directory as adb (or wherever you want if you know what you're doing)
open a terminal
Code:
adb remount
adb shell
su
busybox mount -o remount,rw /system
exit
adb push 99whirlpool-Speedy_2 /system/etc/init.d/99whirlpool-Speedy_2
adb shell
chmod 755 /system/etc/init.d/99whirlpool-Speedy_2 && reboot
I'll add a readme to the zip to make it more obvious.

Shark_On_Land said:
Nice but some of your changes are the exact opposite of what I use. So I'll just change voodoo settings because I'll be a lot less to change with every boot than if I was to use this.
I do of course use easy settings. Color multipliyer: all the way right.
Gama: all the way left.
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.
Click to expand...
Click to collapse
If your just worried about voodoo settings you could do the following :
http://forum.xda-developers.com/showthread.php?t=1366780 or just use the script from this method. Of course you have to edit numbers to your preference.
Sent from my Skanky Nexus S in the Matr1x using XDA App

damnmisur said:
If your just worried about voodoo settings you could do the following :
http://forum.xda-developers.com/showthread.php?t=1366780 or just use the script from this method. Of course you have to edit numbers to your preference.
Sent from my Skanky Nexus S in the Matr1x using XDA App
Click to expand...
Click to collapse
Thanks, I'm going to add this post to the OP as an alternative for those without init.d support

[CWM][Flashable]Init.d Support and Tweaks for Aurora ICS

The aurora_4.1+-init.d-addon zip is compatible with Aurora v4.1+.
The OOM-Priority-Charger-v1.4-Aurora-4.1a zip is compatible ONLY with Aurora v4.1a.
You can visit android.mimic.ca to upload and automatically patch your newer services.jar in an updated Aurora version.
Hello everyone,
I have created an update package that enables init.d support and also has some premade scripts to tweak various settings by the user e.g.
- Synaptics Touchscreen Sensitivity
- Apply FPS Novatek Fix to raise FPS to 53fps
- Set CPU Frequency and Governor
- Disable Atmel Haptic Feedback
- Turn VSync OFF
- Raise SDCard Read Ahead Value
All the above settings are at their defaults meaning that you must change the Settings in the Scripts and reboot to apply them, otherwise all values are the defaults in Aurora after flashing the Package.
It also includes and by default enables Androcharger (V6 SuperCharger tweaked by blk_jack for Desire Z, it is the same as V6's option 5), KickAssKernelizer by zeppelinrox and Loopy Smoothness tweak.
For a full "Supercharge" you must also tweak services.jar via android.mimic.ca (See the V6 Supercharger link for info). I have attached the CWM flashable zip for Aurora 4.1a (OOM-Priority-Charger-v1.4-Aurora-4.1a.zip).
Disclaimer
I am not responsible for any damage to your Device.
Notes:
This will make your boot slower as all these scripts have to be executed at startup. Especially the Loopy Smoothness Tweak will add at least 3 seconds at boot.
To apply Changes you have to Reboot
Changelog:
v1: Initial Release
v2: Resolve Bootloops for Atmel Users
Links:
V6 SuperCharger by zeppelinrox
AndroCharger by blk_jack
Thanks to dzo for his excellent ROM and the U8800 xda community for many of the tweaks.
And of course thanks to zeppelinrox, blk_jack, the EVO 4G developers.

Tweaking Values of Scripts
To tweak the Scripts you must use a File Explorer to navigate to /systemd/etc/init.d/ and open the files with your Favourite Text Editor.
There are instructions in each script.
In detail:
- 11synaptics_sens
Tweak Synaptics Touchsreen sensitivity, values 1 to 8, default=4 to accomodate your fingers and remove "jittering"
Simply replace 4 with your desired value.
- 12fpsfix
This enables the FPS fix that raises the panel's Frame Rate to ~53 from ~46.
This may not work for all phones but it is customizable, to enable it just uncomment (remove the starting #) from the echo line.
- 13cpu
Set your Desired Min/Max CPU Frequency and Governor. You may use copy and paste and finding values by opening:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
For Example to use SmartassV2 replace "echo ondemand > /sys/...." with "echo smartassV2 > /sys/...." in line 9.
If you use SmartassV2 There are extra tweaks for Performance and a highly suggested tweak for Sleep Ideal Frequency.
- 14atmel_haptic_disable
Disable Atmel Haptic Feedback (i.e. Vibration on Touch) by uncommenting the echo line. If you want to enable replace 0 with 1.
(I believe the default is ON here, some atmel user input is appreciated)
- 69vsync_off
This file disables VSync. This will increase FPS, performance and benchmark scores but it will introduce Tearing (try e.g. SpeedX with and without VSync to see jarred lines) and it will probably drain battery faster.
Simply uncomment (remove starting #) from line 8 (echo '0' > /sys/kernel/debug/msm_fb/0/vsync_enable)
- 71sdcard_read_ahead
This file raises the read ahead value for your SDCard meaning faster throughput.
----------
The files 96AndroCharger,97loopy_smoothness_tweak,98KickAssKernel should not be edited.
If you wish to use V6 SuperCharger please remove 96AndroCharger first.

Thank you man this is really usefull, gona try ASAP
BTW "For a full "Supercharge" you must also tweak settings.jar via android.mimic.ca", maybe you wanted to say "services.jar" ?

What is inside the flashable ZIP
The ZIP contains a modified boot.img(its initrd image and specifically init.rc not the Kernel), init.d scripts and an executable file: /system/bin/sysinit that in turn executes all init.d scripts.
The source can be modified to support init.d by applying the attached patch to init.rc in platform/system/core repository of CAF. The init.rc is located in rootdir directory.
The patch is a simple two line patch to run sysinit. I will test, and it will of course be preferable to embed sysinit contents directly in init.rc.
Otherwise the initrd.img in the final bootimage can be unpacked,modified and repacked.
I also modified the update script to set permissions on the init.d directory to 755 and owned by root:shell.
Finally, init.qcom.post_boot.sh has been modded so as not to overwrite CPU settings and exec again 13cpu. I may try to modify it so as to source 13cpu instead.

kaza said:
Thank you man this is really usefull, gona try ASAP
BTW "For a full "Supercharge" you must also tweak settings.jar via android.mimic.ca", maybe you wanted to say "services.jar" ?
Click to expand...
Click to collapse
Yes, thank you kaza.
Please let me know if this works fine for you and if you notice any RAM management improvements.

zephyr1988 said:
Yes, thank you kaza.
Please let me know if this works fine for you and if you notice any RAM management improvements.
Click to expand...
Click to collapse
First impressions after first reboot "wow, this thing is really smoother ^^"
Secound impressions after turn on "12fpsfix" "OMG I have a new mobile phone xD"
Boot its slower, but not that much.
Right after boot i have 173 MB free ram, dont really know how much i had before, what i know is that launcher is not redrawing thats really cool
Until now i can only say this, amazing improvement for Aurora, thank you zephyr1988, I will keep in touch with further testing
EDIT: Aps are opening and closing faster too

Thank you so much for this zephyr.
like kaza said, this impoves smoothess a lot.
And being able to use sd-ext again is really good
Thanks again for this!

Yes, improves everything a lot!
Sent from my U8800

kaza said:
First impressions after first reboot "wow, this thing is really smoother ^^"
Secound impressions after turn on "12fpsfix" "OMG I have a new mobile phone xD"
Boot its slower, but not that much.
Right after boot i have 173 MB free ram, dont really know how much i had before, what i know is that launcher is not redrawing thats really cool
Until now i can only say this, amazing improvement for Aurora, thank you zephyr1988, I will keep in touch with further testing
EDIT: Aps are opening and closing faster too
Click to expand...
Click to collapse
Thanks for testing kaza I'm glad it is useful for you
Thank zeppelinrox for his supercharger and the EVO 4G devs for these two things.
I was simply lucky to find them
@Loureiro,fjsferreira
Glad it works for you guys and thanks for testing

A quick question...
"If you use SmartassV2 There are extra tweaks for Performance and a highly suggested tweak for Sleep Ideal Frequency."
If I change to SmartassV2 with No-frills CPU Control will I benefit from that extra tweaks or only if I change it in 13cpu?
EDIT: Nevermind I saw that its needed to uncoment some lines

kaza said:
A quick question...
"If you use SmartassV2 There are extra tweaks for Performance and a highly suggested tweak for Sleep Ideal Frequency."
If I change to SmartassV2 with No-frills CPU Control will I benefit from that extra tweaks or only if I change it in 13cpu?
Click to expand...
Click to collapse
No Frills will overwrite 13cpu's settings in all cases but if you use smartassv2 in 13cpu and enable the tweaks they should stick, I believe.
In two words, use smartassV2 in both No Frills and 13cpu.
Try enabling the sleep ideal freq tweak and then open with a file manager the file:
/sys/devices/system/cpu/cpufreq/smartass/sleep_ideal_freq
(or in a terminal:
cat /sys/devices/system/cpu/cpufreq/smartass/sleep_ideal_freq)
and see if the value is 368640. If it is it works.

Don't know why, but I installed Aurora 4.0, installed all my apps and then rebooted into Recovery to flash the two Zip files attached to the first post and the phone now is bootlooping :\

trocLas said:
Don't know why, but I installed Aurora 4.0, installed all my apps and then rebooted into Recovery to flash the two Zip files attached to the first post and the phone now is bootlooping :\
Click to expand...
Click to collapse
Are you sure this is because of this mod?
Have you installed other mods too?
Before trying a fresh install, try deleting the three files 96Androcharger, 98KickAsskernel and 97loopy_smoothness_tweak via Pink Screen and PC. Then it is exactly the same as normal aurora and your problem is elsewhere.
Then you should try doing a fresh install of Aurora 4.0, then flash this zip and see if you get bootloops before installing other mods or apps.

wow, I know this will sound strange but at least for me it really happens, i had some slow downloads with Aurora just like most of the guys were reporting, I am using 12fpsfix, 13cpu with 368 min, 1.4 max, smartassV2 with teawks and 71sdcard_read_ahead, and now my downloads are really faster, downloading Asphalt 6 cache now was really fast, maybe its because my read and write speeds of sdcard were increased, dont know, but this is the best tweak so far for Aurora in my opinion lol

kaza said:
wow, I know this will sound strange but at least for me it really happens, i had some slow downloads with Aurora just like most of the guys were reporting, I am using 12fpsfix, 13cpu with 368 min, 1.4 max, smartassV2 with teawks and 71sdcard_read_ahead, and now my downloads are really faster, downloading Asphalt 6 cache now was really fast, maybe its because my read and write speeds of sdcard were increased, dont know, but this is the best tweak so far for Aurora in my opinion lol
Click to expand...
Click to collapse
Yes, I have noticed this too, and also Internet browsing is a little speedier for me.
KickAssKernelizer and SuperCharger(i.e. the modified Androcharger script) apply kernel and tcp stack optimizations

zephyr1988 said:
Are you sure this is because of this mod?
Have you installed other mods too?
Before trying a fresh install, try deleting the three files 96Androcharger, 98KickAsskernel and 97loopy_smoothness_tweak via Pink Screen and PC. Then it is exactly the same as normal aurora and your problem is elsewhere.
Then you should try doing a fresh install of Aurora 4.0, then flash this zip and see if you get bootloops before installing other mods or apps.
Click to expand...
Click to collapse
I tried it with ICS 4.0.4 Toucwiz 5 theme and resulted a bootloop. I will re-install ICS4.0.4 and then your scripts to see if they are working.

zephyr1988 said:
Are you sure this is because of this mod?
Have you installed other mods too?
Before trying a fresh install, try deleting the three files 96Androcharger, 98KickAsskernel and 97loopy_smoothness_tweak via Pink Screen and PC. Then it is exactly the same as normal aurora and your problem is elsewhere.
Then you should try doing a fresh install of Aurora 4.0, then flash this zip and see if you get bootloops before installing other mods or apps.
Click to expand...
Click to collapse
I haven't installed any other mods. I'm going to do a fresh install and then install the two zip files and report what happened!
------------ EDIT ------------
Made a fresh install of Aurora 4.0 and flashed the two zip files from the first post, rebooted the phone, and it entered in bootloop again. Would you upload the files to another host (maybe the files I downloaded are corrupted?).
Don't know why this happens :|

trocLas said:
I haven't installed any other mods. I'm going to do a fresh install and then install the two zip files and report what happened!
Click to expand...
Click to collapse
Did a fresh install but same result(bootloop). Does it make any diffrence which file you install from CWM first?

right after flashing those files, go to Advanced->Report Error. Then mounts and storage -> mount USB storage. You will find inside clockworkmod dir a .log file with debug lines. If something went wrong (mounting or unmounting partitions), it's all there.
Btw which CWM are you using? 5.0.2.7 or 5.5.0.4?

trocLas said:
Don't know why, but I installed Aurora 4.0, installed all my apps and then rebooted into Recovery to flash the two Zip files attached to the first post and the phone now is bootlooping :\
Click to expand...
Click to collapse
same here
Sent from my U8800 using XDA

Llama Sweet Kernel Tweaks

Feature list​
- sets hostname to LG-G4 something that was missing at first from lineage/aosp 7.1.1 (maybe i will remove that)
- Better mount point flags
- Internal storage:
nomerges
nr_requests
lower safe read_ahead_kb
cfq scheduler
cfq scheduler tweaks
remove add_random (if its enabled in the kernel by default)
rq_affinity
- external storage:
nomerges
nr_requests
lower safe read_ahead_kb
cfq scheduler
cfq scheduler tweaks
remove add_random (if its enabled in the kernel by default)
rq_affinity
- Net and virtual memory:
tcp_congestion_control
disable_ipv6
dirty_writeback_centisecs
dirty_expire_centisecs
dirty_background_ratio
dirty_ratio
drop_caches
kernel.panic
min_free_kbytes
overcommit_ratio
panic_on_oom
swappiness 0 #llama doesn't have zram feature, it's useless on Lg G4
vfs_cache_pressure
- CPU customisations ~depends on your choice of script~
balanced ~doesn't make any cpu changes~
less ~for less battery drain, cpu rests more~
more-less ~for a lot less battery drain, but with a big lag (will soon try fix stability and smoothness)~
performance ~for full cpu power, but rest when the screen is off~
- Kernel customisations
msm_thermal ~off on battery save / on and set a safe temp. for performance~
lowmemorykiller
read_wakeup_threshold
write_wakeup_threshold
hotplug customisation
- Only the safe internet customisations
tcp_timestamps
tcp_tw_reuse
tcp_sack
tcp_tw_recycle
tcp_window_scaling
tcp_keepalive_probes
tcp_keepalive_intvl
tcp_fin_timeout
For stock based roms follow the guide in post #2
How to "install" it ? Simple
1.unzip
2.place it in /system/etc/init.d
Code:
adb root
adb remount
adb push <your tweak> system/etc/init.d/
3.change its permissions to 755
4.lastly change owner:group to root:shell
Code:
adb shell
su
mount -o remount rw /system
chmod 755 /system/etc/init.d/<your tweak>
chown root:shell /system/etc/init.d/<your tweak>
If you don't have a pc, type in a terminal inside your g4
Code:
su
mount -o rw remount /system
chmod 755 /system/etc/init.d/<your tweak>
chown root:shell /system/etc/init.d/<your tweak>
Those of you that use the new systemless root method of chainfire you can put the script in /system/su.d or in /su/su.d with permissions 700 (same permissions at folder and script) and set owner:group to root:root
Those of you that use the new magisk root method you can put the script in /magisk/.core/service.d/ with the same permissions and ownership as in init.d
Those coming using search bar and don't have this phone and this kernel, don't try it, unless you know what to edit to "fit" your own kernel.
These tweaks aren't just for faster easy setting up our phone, they are more useful for those that don't want to have root access ON, for various personal reasons. They can apply those settings on boot and setup their phone without the need of root and an app asking for root.
Easy removal: delete the script and reboot. And never use more than one of these scripts inside init.d
Careful, some stock based roms have preinstalled some scripts inside init.d by default.
Those must be removed after flashing Llama Sweet Kernel. They are not compatible and they cause instability !
BIG Thanks to this genius
@genesixxbf3
for his kernel to our lg g4.
XDA:DevDB Information
[Tweaks][MM/N][H815][H811]Kernel Tweaks[CM/STOCK/AOSP], Tool/Utility for the LG G4
Contributors
kessaras, genesixxbf3
Version Information
Status: Stable
Created 2016-12-09
Last Updated 2017-04-25

Reserved
This is a guide for ALL stock based roms and all kernels.
My script will only add tweaks that apply to all kernels.
For those that are rooted with SuperSu, they must first fully remove it.
Nub guide to change SuperSu for Magisk root:​
Step 1.
SuperSu must be removed.
Go into supersu -> settings -> fully remove root access.
###Or download and flash in recovery mode the UnSu script from osm0sis thread.###
Step 2.
Use hardware key combination to boot to TWRP.
###If you used the UnSu script, no need to reboot to recovery, skip step 2 and go to next one.###
Step 3.
Flash latest magisk flashable zip for users that are not rooted yet.
It sais: "If you're not rooted, or something went wrong and you need a clean start"
Download that .zip file and flash it.
Now you are rooted again. Reboot to your rom.
Step 4.
Download Magisk Manager from play store. In that app you can even enable systemless root to hide root from the apps, or do many things that you like.
Questions further go to magisk thread not here. And don't forget to re-enable usb debugging. After you removed root, that was toggled, ###Unless you used the UnSu script again. That means that before reboot you were already rooted.###
Now it's time to install your script.
Download the compressed tweak from this post , uncompress it and follow the next guide.
The steps are the same with the lineage based roms and it works for ALL lineage based roms too
If you use a root file manager then you can skip the guide and just cut - paste the script in /magisk/.core/service.d/
set permissions to 755, ownership to root:shell and reboot.
INSTALLATION​Step 1.
place it in /magisk/.core/service.d/
Code:
adb push /<path to the script>/90balanced /sdcard/
adb shell
su
mv /sdcard/90balanced /magisk/.core/service.d/
Step 2.change its permissions to 755 if it's not already set to 755 by default
Code:
chmod 755 /magisk/.core/service.d/90balanced
If you don't have a pc, type the same commands in g4 terminal but of course without the adb command. Script is supposed to be in path /sdcard/
not in /sdcard/download/ or whatever path. Otherwise edit the command "mv ..." to match the script path.
That's it. Reboot to apply your tweaks.
~I will add Llama Sweet kernel tweaks for stock based ROMS when Genesixxbf3 fixes the bluetooth issue.
Until then all use this one that applies to all kernels including Llama.
Special thanks to:
@topjohnwu for developing Magisk
and to
@osm0sis for his UnSU script

My scripts are not meant for use with kernel adiutor.
Changelog
31/01/2017
- fixed stability for "90less"
- changed to "westwood" tcp congestion control
01/02/2017
- changed to Fiops scheduler only for the 90less and 90more-less
- fixed stability for 90more-less
12/02/2017
- when screen is on, 3 cores always online not 1.
- fixed stability for 90less , 90more-less
- 90balance, interactive governor stable and at the same time conserving some battery
- big cores governor is same with small cores
15/02/2017 and 20/02/2017
- changed back to cfq scheduler
- added cfq scheduler tweaks
- fixed path to disable ipv6
09/03/2017
- fixed a bug for those that big cores were found disabled on boot
Although this is something caused from dirty flashing and can only be fixed with a clean flash
18/03/2017
- Added better mount point flags for Lineage/Aosp based roms, for f2fs, for those that prefer using f2fs partitions format
- i changed the way the mount points get set, now you don't need busybox if you don't want to.
- bigger timer rate for interactive governor for the balanced tweak, balanced can conserve battery now too.
25/04/2017
- Less-more is not lagging anymore but of course it still loads slow since cpu runs at a lower frequency
- interactive governor in balanced script saves more battery than before
- All scripts now give a small cpu frequency amount on input to reduce lag
- At less and less-more the hotplug sets the cores online at a lower frequency. Before, with those scripts you could rarely see the other cores online

kessaras said:
You can request any setting for kernel and cpu you want. I can add them for you.
Screenshots of battery with 90less.
~Haven't done anything special. Brightness is at normal with "auto" ON, gapps stock, usage: Normal, chat, xda, phone Calls/Messages, GPS ON.
Many factors determine the battery drain, such as 3rd party apps, ads from apps, services and more, don't blame my settings. Those settings are absolute and tested and i only do this to help everyone.
Click to expand...
Click to collapse
Thanks for you work, I am using H818p without BL unlock. Currently, I can modify /etc/init/qcom.post_boot.sh from this thread (http://forum.xda-developers.com/tmo...-msm-8992-cpu-io-ram-interactive-gov-t3351478).
The question is, can I port some tweaks from this thread to the stock kernel using qcom.post_boot ? I am not familiar with the seqence of boot, any idea ?
Thanks,

jskasia said:
Thanks for you work, I am using H818p without BL unlock. Currently, I can modify /etc/init/qcom.post_boot.sh from this thread (http://forum.xda-developers.com/tmo...sm-8992-cpu-io-ram-interactive-gov-t3351478).
The question is, can I port some tweaks from this thread to the stock kernel using qcom.post_boot ? I am not familiar with the seqence of boot, any idea ?
Thanks,
Click to expand...
Click to collapse
Scripts are only for Llama kernel. So,
it depends if the stock kernel has same file "trees". Worst case scenario is to not be able to boot. If you can enter recovery you can fix it by doing :
Code:
rm /system/etc/init.d/<name of the script>
Or use the recovery file manager to delete it,
reboot and you are fine.
Don't use 90less as it is or for sure you won't boot. Less is using alucard governor which doesn't exist in stock. Open script and edit those lines, change alucard to interactive.
"kernel tweaks" delete them. the stock kernel doesn't have same hotplugs and heat protection.
EDIT:
a part of the scripts does work for stock without llama kernel. it's not dangerous because the stock lg rom doesn't have init.d support on boot and the script only can be applied inside kernel adiutor by enabling init.d emulator.
you can use it then. you will just not get the 100% out of it.
in the 90less you wont get the alucard governor and the hotplug to let the cpu rest.
the only alternative available is to make you one that edits the interactive governor to work almost the same as alucard and conserve a bit more battery than the stock interactive does.

@matgesiarz
follow the op

kessaras said:
Scripts are only for Llama kernel. So,
it depends if the stock kernel has same file "trees". Worst case scenario is to not be able to boot. If you can enter recovery you can fix it by doing :
Code:
rm /system/etc/init.d/<name of the script>
Or use the recovery file manager to delete it,
reboot and you are fine.
Don't use 90less as it is or for sure you won't boot. Less is using alucard governor which doesn't exist in stock. Open script and edit those lines, change alucard to interactive.
"kernel tweaks" delete them. the stock kernel doesn't have same hotplugs and heat protection.
Click to expand...
Click to collapse
Okay, I successfully put the tweaks (balance) on to init.qcom.post_boot.sh. My phone boot without any problem. After few days we will see the result.
Thanks

we just need to push scripts or I need also to clean the init.d folder first from other scripts? I am on ChyperOS 3.1.4

If I understand right, if I put this tweak I don't need to setup any kernel modification in apps like EX Kernel manager, isn't?

Vipery said:
we just need to push scripts or I need also to clean the init.d folder first from other scripts? I am on ChyperOS 3.1.4
Click to expand...
Click to collapse
no you don't clean the init.d folder. if you do that you will lose important script that needs the rom to boot. you only use one of those scripts in init.d, if you put 2 of those in, delete the one.
Oletros said:
If I understand right, if I put this tweak I don't need to setup any kernel modification in apps like EX Kernel manager, isn't?
Click to expand...
Click to collapse
exactly and if you need any change and you don't know how to edit the script, you can ask me to add it for you

kessaras said:
no you don't clean the init.d folder. if you do that you will lose important script that needs the rom to boot. you only use one of those scripts in init.d, if you put 2 of those in, delete the one.
Click to expand...
Click to collapse
Thank you. Another thing, I need to set owner and group to shell or just group? The other scripts are set root/shell and not shell/shell.

Vipery said:
Thank you. Another thing, I need to set owner and group to shell or just group? The other scripts are set root/shell and not shell/shell.
Click to expand...
Click to collapse
only what the op sais. only group owner. its already set from me, but you have to at least check if its set, if not, set it. group owner shell

Thanks for the tweaks!
Sorry for this perhaps silly question, but which is supposed to be more battery friendly between balanced and less?

joaste said:
Thanks for the tweaks!
Sorry for this perhaps silly question, but which is supposed to be more battery friendly between balanced and less?
Click to expand...
Click to collapse
less refers to less battery consuption and its only by a little cause we don't want to have lags. Of course we can do it even more battery friendly but we will have a very slow phone.

kessaras said:
less refers to less battery consuption and its only by a little cause we don't want to have lags. Of course we can do it even more battery friendly but we will have a very slow phone.
Click to expand...
Click to collapse
Thanks for the clarification!

kessaras said:
exactly and if you need any change and you don't know how to edit the script, you can ask me to add it for you
Click to expand...
Click to collapse
Thanks

Ok,I applied your 90less tweaks and here's what I've got after reboot:
The big cores governor-interactive,max.freq.-1248
The little cores governor-alucard,max.freq.-1440
MSM Hotplug-OFF
MSM MPDecision Hotplug-ON
Is that ok or...?

welder73 said:
Ok,I applied your 90less tweaks and here's what I've got after reboot:
The big cores governor-interactive,max.freq.-1248
The little cores governor-alucard,max.freq.-1440
MSM Hotplug-OFF
MSM MPDecision Hotplug-ON
Is that ok or...?
Click to expand...
Click to collapse
nothing applied on boot.
in less,
max for the big is set to 1536
and hotplug is off to not get load for nothing since the temp wont go higher than 60 even under the hot summer sun.

kessaras said:
nothing applied on boot.
in less,
max for the big is set to 1536
and hotplug is off to not get load for nothing since the temp wont go higher than 60 even under the hot summer sun.
Click to expand...
Click to collapse
So I should change the max for the little cores to 1536 and everything else is ok?

Vipery said:
Thank you. Another thing, I need to set owner and group to shell or just group? The other scripts are set root/shell and not shell/shell.
Click to expand...
Click to collapse
...