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.
INSTALLATIONStep 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
...
Related
WARNING
Overclocking/undervolting could cause crashes with loss of data, or even damage hardware including the CPU or GPU.
Voodoo support included since 1.5, remove all non-Voodoo lagfixes before installing.
This works for me, but you are ultimately responsible for what happens to your device and your data - have backups, preferably on an external SD that you remove for initial testing.
These are unsigned and will not flash via stock recovery. Use ROM Manager to flash, with ROM Manager you also don't need to rename them as it can select any zip file from internal storage.
Features:
Voodoo lagfix support - should work correctly flashed over other Voodoo beta4 kernels, remove non-Voodoo lagfixes before installing.
BLN support to allow use of touch-button lights to indicate pending notifications when screen is off. The lights will light for all statusbar notifications, unless disabled in the app producing the notification (not all apps will have an option to do this, I don't think any stock Samsung apps do).
Stock voltages/clocks at boot, runtime configuration of clocks and voltages via sysfs, nilfs2 and ext2/3/4 filesystem support, two-stage user init - early scripts for mounting filesystems, late ones for running services. Default I/O scheduler is BFQ, BFQ/CFQ/anticipatory all perform roughly the same in benchmarks with multiple threads competing for I/O. Typical wakeup between instant and about one second, built with the binutils 2.19.1 / gcc 4.3.4 toolchain.
User clock/voltage configuration can be read from/written to /sys/devices/system/cpu/cpu0/cpufreq/freq_volt_table. Copy this file to get the defaults, edit your copy and write back over the original to update, or save your new file in /sdcard/sd/config, /sdcard/config, or /system/etc/config to have it applied on boot. The first column is CPU clock, the second GPU clock, the third CPU voltage, the fourth internal voltage. Changing values besides CPU clock/voltage is not recommended. You must keep 100MHz as the lowest speed. Clocks are in KHz, voltages in mV. Modify at your own risk, I find that my phone runs 1.2GHz @ 1.3V just fine, but yours may vary.
Be aware that your phone might appear to run fine with overclock/undervolt at first but crash later due to some error in calculation or data transfer - i recommend a good number of runs on something like Quadrant, and at least five minutes or so of SetCPU stress test for each frequency you add or change.
User inits must be placed in /system/etc/init.d, and properly named - names starting with "E" will run before /data and /dbdata are mounted, names starting with "S" will run right before startup is completed and normal Android services start. Inits are sorted by name, so you can follow the initial E or S with a number to change the order in which they will run. Scripts need not be executable, and will be run with the shell provided in initramfs for Voodoo support (busybox ash). If either /data or /dbdata is not a mount point after E scripts are completed, /user_early_init.sh will attempt to mount an rfs filesystem there from the usual location. If you want to mount a filesystem that is some other type, you will need to do so in a user script. If you want to format /data with another filesystem, you must edit the partition table to change the partition number - I have disabled the code in /sbin/init that rewrites the partition table, but if it finds something on standard /data partition that does not look like a valid RFS filesystem, it will reformat it.
If you want to build yourself, see the toolchains thread for known-working tools. Run
Code:
make ARCH=arm i897_defconfig
make ARCH=arm menuconfig [COLOR="blue"]optional[/COLOR]
make CROSS_COMPILE=/path/to/toolchain/arm-none-eabi- zImage [COLOR="blue"]change if using a different toolchain[/COLOR]
tar c -C arch/arm/boot/zImage >captivate_zimage.tar
Flash captivate_zimage.tar as PDA in Odin - see other threads for how to use Odin and where to get it. Use menuconfig to select a different initramfs source if you wish, by default an included one at usr/initrd_files will be used.
Starting with v1.4, create a .build_config file to change any variables and run build_kernel.sh to build tar flashable with Odin or update.zip. As of v1.5.2 you can also use .build_config to inject commands and files into update.zip builds.
CREDITS
raspdeep - the original OC code
curio - Voodoo lagfix original concept and script
neldar - BLN support
atinm - BLN port for Captivate
BusyBox, buildroot, crosstool-ng, nilfs2 - see respective projects for original contributors and source
v1.7ClockworkMod Recovery
flashable binary: mediafire mirror | github mirror
github source
BETA ClockworkMod Recovery replaces stock recovery
BETA support for backup/restore with Voodoo enabled
v1.6BLN Support
flashable binary: View attachment i897-unhelpful-v1.6.zip | mediafire mirror | github mirror
github source
BLN support - use the touch-button lights to alert of pending notification when screen is off.
Disable check for SGH-I897 device, since this can fail on Captivate hardware if an alternate ROM is flashed.
v1.5.3Bugfix release
flashable binary: View attachment i897-unhelpful-v1.5.3.zip | mediafire mirror | github mirror
github source
Revert from the config based on kepler_rev02_defconfig, suggested by the 9/6 code drop, to aries_rev02_defconfig. The config change appears to have been responsible for the power drain problems seen in v1.5.1 and v1.5.2.
v1.5.2Bugfixes and Voodoo lagfix support
flashable binary: View attachment i897-unhelpful-v1.5.2.zip | View attachment i897-unhelpful-v1.5.2.tar.7z | mediafire mirror | github mirror
github source
Odin-flashable tar file (inside 7z to allow upload to XDA), please use only to recover from bad flash of v1.5.1, the update.zip contains scripts that are important if you're running SRE.
Voodoo lagfix support
Restore correct stock voltage (1.275V) for 1GHz
Update sources and config from Captivate 9/6 source drop
Update modules from JH7 OTA
LZMA initramfs compression to reduce compressed kernel size / allow larger initramfs
Enhanced update.zip support allows developers to easily inject their own commands and files into update.zip on build, and allows run_programs scripts to produce screen output and can flash kernel/modem partitions directly.
v1.4.1BUGFIX for SRE users
flashable binary: View attachment i897-unhelpful-v1.4.1.zip | View attachment i897-unhelpful-v1.4.1.tar.7z | mediafire mirror | github mirror
github source
Bug with SRE + 1.4 causing storage to become unavailable should be fixed by this kernel, fix works on my phone but some have reported problem spontaneously ifxing itself.
v1.4Load OC/UV config from file, system early init (for developers).
downloads removed due to bugs
github source
Built with gcc-4.4.3
build_kernel.sh reads variables from .build_config, or from config file specified by $BUILD_CONFIG, so you can keep the script file clean.
Early system init - E* scripts in /sbin/init.d run before user early init, for developers to include startup scripts.
System init loading of OC/UV table - searches for config/freq_volt_table on external SD, then internal SD, then in /system/etc.
ADB checks uses the first shell found from the list bash, ash, /system/xbin/sh, /system/bin/sh, sh.
Correctly set cpufreq policy on table change - should fix resets of maximum clock to 1GHz after new tables are loaded.
v1.3.1OC/UV configuration
flashable binary: View attachment i897-unhelpful-v1.3.1.zip | mediafire mirror | github mirror
github source
Stock clocks/voltages at boot, user can add new clocks and change voltages at runtime - see above for details.
Modify stock init to avoid rewriting partition table at boot - change the partition table for internal SD, resize partitions or remake /data with a different partition number so it can be safely formatted with another filesystem.
v1.2Bugfix / update.zip / dev features
flashable binary: View attachment 389189 | mediafire mirror | github mirror
github source
Fix scaling bug, performance level was set past end of table on sleep
Scaling enhancement, selectable clock source for GPU
GPU clocked at 222MHz for all speeds except 100MHz, where it matches CPU clock
Basic build_kernel.sh script, edit to change configuration - builds unsigned update.zip with default kernel config by default
Add interactive CPU governor - enabled in build but conservative is still configured as the default
v1.1Bugfix release
flashable binary: mediafire mirror | github mirror
github source
Rework of user init, resolves lost-settings-on-boot issue for me.
v1.0Initial release for Captivate I897
flashable binary: mediafire mirror | github mirror
github source
nilfs2, ext2/3/4 filesystems
separate early and late user init
600MHz and 1.2GHz speeds, use SetCPU to enable 1.2GHz
fast scaling from low speed, skipping from 100MHz to 800MHzOther Downloads
User Init Scripts
mediafire, github - enable 1.2GHz overclock on startup
mediafire, github - start Mobile AP background service
Does this include the ability to clock at 1000 mhz?
Sent from my Nexus One using XDA App
You're my hero.
*edit*
_Opiate_ said:
Does this include the ability to clock at 1000 mhz?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yea it is, I have it set at 1200 in setcpu and I saw it hit 1000mhz a few times just watching it.
Yes, the scaling steps are 100MHz, 200MHz, 400MHz, 600MHz, 800MHz, 1GHz, and 1.2GHz. 1.2GHz is disabled at startup until the user enables it, so that the kernel can be used without overclocking.
Sent from my SAMSUNG-SGH-I897 using XDA App
So will this undo the MobileAP that was just put out. I know we had to flash a custom kernel to enable that. Will this undo it?
Clienterror said:
You're my hero.
*edit*
Yea it is, I have it set at 1200 in setcpu and I saw it hit 1000mhz a few times just watching it.
Click to expand...
Click to collapse
Never mind I just flashed it. No On demand?
Unhelpful said:
Yes, the scaling steps are 100MHz, 200MHz, 400MHz, 600MHz, 800MHz, 1GHz, and 1.2GHz. 1.2GHz is disabled at startup until the user enables it, so that the kernel can be used without overclocking.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Thats great. Hell just running it at 1000mhz is a slight improvement in Quadrant. Before when I was running the stock kernel I never saw it clock above 800mhz.
Also no wake up lag at all!!!!!!!!! Great fraking job man!!!!!
jhernand1102 said:
So will this undo the MobileAP that was just put out. I know we had to flash a custom kernal to enable that. Will this undo it?
Click to expand...
Click to collapse
This does not run wlp2pservice in the init.rc, but a user script can easily be written to do that - I already have one on my phone, I'm going to add a section for init scripts in the OP when I get the chance.
Can you toss up a donation link plz :-D
Unhelpful said:
This does not run wlp2pservice in the init.rc, but a user script can easily be written to do that - I already have one on my phone, I'm going to add a section for init scripts in the OP when I get the chance.
Click to expand...
Click to collapse
Thanks for the info...looking forward to trying this out once there is a script so MobileAP still works...
jhernand1102 said:
Thanks for the info...looking forward to trying this out once there is a script so MobileAP still works...
Click to expand...
Click to collapse
Yeah that's one reason I still use my Nexus One mainly. The ability to tether is built right in to Froyo. But I can wait for tethering till we have a kernel that will do both. I prefer to play with this kernel now. Lol
Sent from my Nexus One using XDA App
_Opiate_ said:
Yeah that's one reason I still use my Nexus One mainly. The ability to tether is built right in to Froyo. But I can wait for tethering till we have a kernel that will do both. I prefer to play with this kernel now. Lol
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yeah hopeful it can be put in the same kernel then we can have the best of both worlds...
I just found something strange. When I reboot and enter set cpu the phone say I have to chose my device again so I have to choose autodetect again.
Sent from my SAMSUNG-SGH-I897 using XDA App
do we just flash this with odin ? in the op there are many intrsuctions on putting stuff here and there i got lost
_Opiate_ said:
I just found something strange. When I reboot and enter set cpu the phone say I have to chose my device again so I have to choose autodetect again.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Every time I reboot it's all in Russian again like the first boot with JM5 lol.
Crizthakidd said:
do we just flash this with odin ? in the op there are many intrsuctions on putting stuff here and there i got lost
Click to expand...
Click to collapse
Yep, just use 7zip and extract the .tar then flash with odin3 as PDA.
Wow, unhelpful you are the MAN. Put up a donate link, I'll send a few beers your way.
Works!!
Unhelpful, you're probably one of the MOST helpful people on this forum. haha
minor bug, usb debugging doesn't seem to stay on between reboots.
and i can't seem to send emails using the gmail client anymore
IStern said:
minor bug, usb debugging doesn't seem to stay on between reboots.
and i can't seem to send emails using the gmail client anymore
Click to expand...
Click to collapse
ditto on the usb debugging, wont stay on between reboots
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
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
I have the following init.d script, named 05mpoffpsb200. It disables mpdecision but it fails to set the value of powersave_bias. I have to manually change it on every boot to make it work. Anybody know to make the script set the powersave_bias value?
Code:
#!/system/bin/sh
su
stop mpdecision
echo "200" > /sys/devices/system/cpu/cpufreq/intellidemand/powersave_bias
Hi,
I don't use this kernel, but are you sure it's the right path (ok it seems good)?
Try with this:
#!/system/bin/sh
echo "200" > /sys/devices/system/cpu/cpufreq/intellidemand/powersave_bias
Click to expand...
Click to collapse
Other than that, others init.d sripts work?
Sometimes you can change some settings in live but it didn't work with init.d scripts (I think it depends how it's defined when the kernel is compiled or something like that ).
You can try with an app with a setting like "on boot completed" -> SetCPU (the app sets the value on boot without init.d scripts, works well in general).
Or ask in the kernel thread?
Yeah the same script successfully stops mpdecision service like I said, but fails on the powersave_bias setting.
I even tried a script with the lone powersave_bias setting but it does not work.
Is the governor getting changed to intellidemand after boot up ?
maybe it's not setting because a different governor is in use while booting.
if thats the case add a line for each core to change it's governor to intellidemand befor the powersave_bias setting
does the powersave bias command work as expected if you run it in terminal after booting?
If so, try adding a sleep command before the powersave bias line; could be some conflict during bootup that interferes with the powersave bias setting.
viking37 said:
Hi,
I don't use this kernel, but are you sure it's the right path (ok it seems good)?
Try with this:
Other than that, others init.d sripts work?
Sometimes you can change some settings in live but it didn't work with init.d scripts (I think it depends how it's defined when the kernel is compiled or something like that ).
You can try with an app with a setting like "on boot completed" -> SetCPU (the app sets the value on boot without init.d scripts, works well in general).
Or ask in the kernel thread?
Click to expand...
Click to collapse
I didn't read your addition to your comment, but I will that out.
meangreenie said:
Is the governor getting changed to intellidemand after boot up ?
maybe it's not setting because a different governor is in use while booting.
if thats the case add a line for each core to change it's governor to intellidemand befor the powersave_bias setting
Click to expand...
Click to collapse
I do have the governor selected and "applied on boot" using the performance settings (in main settings). Possibility of the device using a different governor before setting it to intellidemand seems quite plausible.
halluci293 said:
does the powersave bias command work as expected if you run it in terminal after booting?
If so, try adding a sleep command before the powersave bias line; could be some conflict during bootup that interferes with the powersave bias setting.
Click to expand...
Click to collapse
Yes, the script does work as intended on manual execution which supports the possibility mentioned by meangreenie.
I will look into it and post back my results.
Thank you for the input everyone.
4/20/2017 [] 7.1.1 UPDATE [] One Plus 3 (msm 8996) [] CPU, VM, RAM, IO "Tune"
ORIGINAL THREAD HERE: https://forum.xda-developers.com/axon-7/development/2-15-2017-axon-7-msm-8996-cpu-vm-ram-t3557392
This mod was originally created for the Axon 7, but due to several requests, I've modified a version for the One Plus 3, please see below, and post questions or comments in the original thread above. Please state you are a One Plus 3 user if you have feedback in that thread, to consolidate user feedback and speed up response time.
Custom tuning for a device is always a necessity. "Canned" settings will get you by, but they are certainly never optimized for a specific device. In fact, Linux typically takes a general approach to find harmonic balance in default settings that will, for the most part, work in an acceptable manner for just about any device. There are a lot of resources available on this device, so we should utilize it in a manner appropriate to squeeze out as much battery life and performance as possible without sacrificing much of those outputs, don't you think? This is going to fix that for you.
Here is what is required of you before you begin:
1. Must be rooted
2. Must have the One Plus 3 OR a device running the Snapdragon 820, as this modification is not so much device specific, but hardware specific. The important aspect being the snapdragon 820 and the RAM disk size.
3. Must have write protection disabled. If the One Plus 3 requires write protection to be disabled, see the code and instruction below:
Using adb shell:
Code:
adb reboot disemmcwp
Using Linux terminal (from your phone, for example):
Code:
reboot disemmcwp
Let's begin.
Getting right to it, here's what I've done:
- modified parameters of the interactive governor, and quite extensively at that (search some of my threads if you want a little bit of a breakdown of the general approach I take)
- reconfigured input_boost parameters
- reconfigured vm parameters (again, the device has a lot of RAM resource, this will utilize it and give you a far better user experience. Basically, I've adjusted dirty_ratio, dirty_background_ratio, swappiness, and other parameters of the virtual machine.)
- disabled zRAM for 6 GB variants (RAM compression, again, not needed on this device really, this mod will save you CPU cycles and power) this will not apply to 4 GB devices, you will still have zRAM enabled.
- remapped minfree parameters for LMK (low memory killer) again only for 6 GB variants
- Tuned CFQ scheduler for flash storage devices
- Tuned "core_ctl" module (needs kernel support, I recommend freeza's latest version of BeastMode. For those wondering, yes, you can still use this mod with the stock kernel. It won't break anything.) again this will only apply to devices that support core_ctl at the kernel.
In a nutshell, that's what we're looking at here. I can guarantee you this will have a significantly positive impact on your device. Turbo time, homies.
How to install????
Easy. First, the file we are replacing is found in /system/etc... it is the "init.qcom.post_boot.sh" file - this file is basically shell scripts, which are applied at boot via this particular shell file.
All you have to do is download the file to your device, open up a file explorer (must have root capability), navigate to the /system/etc folder with said file explorer, mount your /system as RW (read write), delete your stock "init.qcom.post_boot.sh" file, and replace it with mine.
After you've successfully done this, change the new file's permissions to rw-r--r-- (0644), and then reboot!
Or, if you are brave, you can do it manually via a terminal app and get your fingers wet... if you choose to do that, see below:
Make sure the file is located on the root of your internal sdcard in /sdcard, open your terminal app (again, must have root) and type the following commands, hitting enter after each one (be careful to pay attention to the spacing).
Code:
su
Code:
cd /
Code:
mount -o remount,rw /system
Code:
cd /system/etc
Code:
rm init.qcom.post_boot.sh
Code:
cd /sdcard
Code:
mv init.qcom.post_boot.sh /system/etc
Code:
chmod 0644 /system/etc/init.qcom.post_boot.sh
I don't want credit, don't need you to give or offer donations, this is purely for the community in the spirit of Linux ideology. All I ask is for you to hit the thanks button :good:
That's pretty much it, guys. Enjoy!
DOWNLOAD
I'm willing to give it a go...
File attached ?
Downloaded
warBeard_actual said:
ORIGINAL THREAD HERE: https://forum.xda-developers.com/axon-7/development/2-15-2017-axon-7-msm-8996-cpu-vm-ram-t3557392
Hello, everyone. I would like to provide this modification for this device, as it uses the same SoC as the Axon 7, V10, HTC 10... and a few other devices.
If anybody is interested, please provide me with the STOCK init.qcom.post_boot.sh file, which is found in /system/etc and I will post the modified file and instructions on how to install it.
:good:
Click to expand...
Click to collapse
Ok see immediately improvement! Thanks !
Going to test it a couple of days!
danny b. said:
Ok see immediately improvement! Thanks !
Going to test it a couple of days!
Click to expand...
Click to collapse
I haven't posted the one for your device yet, but I am uploading now.
op updated****
Axon7
warBeard_actual said:
I haven't posted the one for your device yet, but I am uploading now.
op updated****
Click to expand...
Click to collapse
This op3 is my daily phone
The axon 7 is my girlfriend phone also mine?but tested it on the 7 sorry for the confusion. Great work going to test it tomorrow on op3
Read through your entire other thread, you have been updating pretty tirelessly. I installed it on Open Beta 14, ran cat /proc to ensure swappiness was good and it shows 1 just like the config file so the tweaks are up and running on my device. I'm running the beta with the stock kernel so I'll do some testing and see how it does with general performance over the next few days.
I don't know who asked to you share this with us, but we definitely appreciate it :good:
will test it for a couple of days and report...
Heads Up...
the adb command doesn't work for me on OB13, it reboots the phone and doesn't disable Write protection, i went around that by deleting and replacing the file from TWRP...
Thank you I could see some battery improvements.i copied that file through twrp ..Using 4g and got 2.40 hours sot still 50 percent battery remaining.phone doesn't slow down or heat up it's a must try
If i change the kernel like blue spark then its worth it ?
And orignel file is about 122 k and youe file is only 22k.
Facebooook said:
If i change the kernel like blue spark then its worth it ?
And orignel file is about 122 k and youe file is only 22k.
Click to expand...
Click to collapse
He addresses this in the original thread and it is the same size difference on the axon 7. He removed the generic options and put in modified and tuned optimizations for our specific hardware build instead of every MSM device. It definitely provides a more responsive system overall, but I haven't had it running long enough to see the battery impact on the device.
How to check if it works?
Will it work on custom ROMs (AICP etc?)
Day 2 hotter than normal. In keep on testing
Edit: back to normal
Problem was new app
Plz ignore. Problem solved
Will definitely try this thanx a bunch???
Sn0wFl4keZ said:
How to check if it works?
Will it work on custom ROMs (AICP etc?)
Click to expand...
Click to collapse
Definitely no for custom ROMs. Using AICP with latest ElementalX, the file mentioned by OP is not even present in our /system/etc.
Anyway, pretty sure that kernel devs have already tweaked most of the parameters changed by this sh script, so I don't see any need for it for anyone except stock ROM and stock kernel users.
P.S. Still, a lot of work was done by OP, it definitely deserves a big Thank you.
Nezorflame said:
Definitely no for custom ROMs. Using AICP with latest ElementalX, the file mentioned by OP is not even present in our /system/etc.
Anyway, pretty sure that kernel devs have already tweaked most of the parameters changed by this sh script, so I don't see any need for it for anyone except stock ROM and stock kernel users.
P.S. Still, a lot of work was done by OP, it definitely deserves a big Thank you.
Click to expand...
Click to collapse
Thanks for the nod. And while I can't speak to the changes implemented by kernel compilers on this forum, I would be willing to give you guys a comparison of the custom ROMs/combos you're running on your op3.
It might shed some light on whether or not you'd benefit from using it if you're using a CM type set up.
Here's what you do... Go into /sys/devices/system/cpu/cpu0/cpufreq/interactive ...
There will be a bunch of files in there for above_hispeed_freq, hispeed_load... A bunch of others. Open them up with a file explorer, snap a screen shot, post it here so I can see the values of your CM-based ROMs.
Is there I way to confirm that it is working properly because I think it is but it feels like a placebo effect. Thanks for the mod :good:
Thanks
warBeard_actual said:
Thanks for the nod. And while I can't speak to the changes implemented by kernel compilers on this forum, I would be willing to give you guys a comparison of the custom ROMs/combos you're running on your op3.
It might shed some light on whether or not you'd benefit from using it if you're using a CM type set up.
Here's what you do... Go into /sys/devices/system/cpu/cpu0/cpufreq/interactive ...
There will be a bunch of files in there for above_hispeed_freq, hispeed_load... A bunch of others. Open them up with a file explorer, snap a screen shot, post it here so I can see the values of your CM-based ROMs.
Click to expand...
Click to collapse
Here are the contents of the .../interactive folder (everything except boostpulse - got 'Permision denied' on that).
That's for the AICP (based on LOS).
Hello.. Thanks for your mod.
I'm using freedomOS OB13 with francos kernel with his app. Already did all the steps in this thread.
Now, I Just wanted to know if it's just for stock phones or will it improve for everyone?
And how to check if everything is as it should?
Thanks in advance!
---------- Post added at 10:27 AM ---------- Previous post was at 10:22 AM ----------
theduke7 said:
will test it for a couple of days and report...
Heads Up...
the adb command doesn't work for me on OB13, it reboots the phone and doesn't disable Write protection, i went around that by deleting and replacing the file from TWRP...
Click to expand...
Click to collapse
Hey.. How did you check if the write protection is still disabled?
I'm on OB13 as well and my phone just restarted after the command and I thought that's it!