Database Info

[REF][SCRIPTS] Android Optimization Tips + i9000 specifics (UPDATED 1/10/12)

Attention!
If you're looking for scripts, here it is:
[CWM][SCRIPTS][TWEAKS] Thunderbolt!
Script Reviews are here:
Script Reviews
Introduction
I've been meaning to share this with the whole Android community. It seems unfair that only the i9000 folks have access to the vast research that I've done so far. Hence I'm sharing this in the general Android thread in hopes that it'll benefit everyone in the long run
A lot of people often asked about how Android really works and the optimizations can be made to their Android to make it perform better in terms of:
- battery life
- raw performance
- GUI smoothness
With Android based on Linux, and with the experience I have with Linux/Unix (I deal with Unix/Linux on a daily basis for my work) I managed to find some tweaks that we can do to optimize our phones.
I also hope that people will experiment with the tweaks posted here and feedback to me if there are certain ways that I'm doing incorrectly or there are better ways than what I've posted here.
Script tweaks
There are a lot of scripts in XDA that specifically uses the optimizations (Linux or Android based) that I will explain below to actually increase performance/battery life. However, you need to know what those scripts do before using it.
I've done some reviews of the script here:
Script Reviews by Pikachu01
There are good scripts that are properly tested and made sure that it works. It's a script by Zacharias maladroit, the kernel dev who makes the platypus kernel for CM7 and snail kernel for i9000. I modded it to be compatible with i9000 and it'll probably do more than some of the scripts I reviewed
From there, I've also taken the liberty of modifying it some more based on my knowledge and research I've done. It's called ThunderBolt!:
LINK
Now onwards to what actually goes on beneath the hood.
Android Governors
Some custom kernels provide customized governors for you to choose. These are currently known:
- Ondemand (CPU scales to the highest frequency immediately after a certain CPU threshold)
- Conservative (CPU scales to the highest or 1 scale lower than that after a certain threshold gradually and scales down if CPU is below a certain threshold
- OndemandX (Has sleep codes that scales down the CPU when device is asleep. Threshold is set to scale slower)
OndemandX
OndemandX has a suspend frequency that it maintains when the phone is sleeping. It does have a known issue of waking up too slowly when a call comes in.
Conservative
Conservative is used when you would like the CPU to scale to the maximum through each frequency slowly before reaching the maximum. It saves more battery at the expense of smoothness. There are a few tunables that can be configured in Conservative governor, namely the freq_step and both the up and down thresholds.
freq_step is a tunable that determines how much frequency (a percentage of the maximum frequency of your device) to increase at each sampling rate. e.g. you have 5 as freq_step and your maximum frequency is 1GHz. At each sampling rate, it'll increase by 50MHz. If your current frequency is 100MHz, it'll increase to 150MHz at the next sampling. What if your device doesn't support 150MHz? This is done by splitting time between 100MHz and 200MHz (assuming your next frequency is 200MHz) so that in average, your phone is performing at 150MHz.
The up_threshold is how much threshold to wait for before increasing the base frequency to the next freq_step. I.e. if it is 80, the CPU will wait until it is 80% loaded before increasing the frequency. The down threshold is the opposite of up_threshold, which is the threshold to wait until the CPU downscales the frequency to the next frequency step.
Ondemand
Ondemand is a governor that basically a simpler version of conservative. One difference is that it scales to the maximum frequency after load has exceeded a threshold. This is usually 80. After that, it looks at the load again when it's at the max frequency. If it's below 80 (example), it'll scale down one frequency step. The frequency step mentioned here is the available frequency step. I.e. if your device has frequencies of 100,200,400,800 to 1GHz then it'll scale down from 1GHZ to 800, 400 then 200 and 100.
One optimization I have for Ondemand for i9000 TalonDev is that I tuned it to be 80 rather than 65. I have not felt any slowdowns from using this setting and it saves a tiny bit more battery. You can experiment on this value however you want, but bear in mind that I'm not responsible for any slowdowns or damage that is caused by it. Read up a bit more on thresholds to know more (Google it).
I/O scheduler tweaks
Another tweak that can be done is the I/O scheduler tweak. Some kernels come with a few standard I/O schedulers while others have extra schedulers that you can choose from. I'll explain the few that I know and if you have more information on the schedulers, you can post it here for everyone to discuss/share
CFQ - Completely fair. Most will come with this, but this is not optimized for android. Some kernels do optimize it and use it.
Noop - Simple and least overhead of all I/O schedulers. Produces the best outcome for some cases and some do swear by it. It's downside is that it is easily bogged down by high I/O transactions.
Deadline - Optimized for mobile-like devices like Android. Also, some do swear by this. If its writes_starve sysfs is tweaked to be fair, it's the same as SIO.
SIO - It's a fair deadline scheduler. It's the best scheduler. Nuff said.
VR - A newer I/O scheduler that places penalty on reverse seeks. Not for flash drives, though the R penalty can be tweaked to be a multiplier of 1. Even if this is done, it has a high overhead.. Read more here: http://www.gelato.unsw.edu.au/IA64wiki/IOScheduling/VRscheduler
BFQ - Too high of an overhead, it is optimized for spindle disks.
You can pick and choose from Voltage Control or other UV/OC apps and apply it immediately to feel the difference.
Here's my assessment of all the schedulers that I know:
SIO> NOOP> Deadline > VR > BFQ > CFQ
NOOP is a simple I/O scheduler without overhead that tries to do each I/O transaction as it comes (FIFO). When a group of transactions is detected, it will try to merge it together to make batches of transactions (makes the whole transaction faster). NOOP doesn't have starvation detection, hence if an I/O transaction takes a painfully long amount of time, it will still continue to do it rather than switch the CPU into doing something else e.g. GUI interrupts (i.e. scrolling lists, flicking screens). All other schedulers also have the "merge" feature. NOOP is the only one that makes the "merge" feature its only feature.
CFQ is a complex I/O scheduler that tries to determine the address space of the transaction and applies a cost algorithm in that if the address is close together, it will group them up and perform them. It also tries to make the transaction incremental (i.e. reading/writing through address incrementally so that the disk spindle needs to wind down the least in conventional platter hard disks) The problem is, our flash devices have very little delta between reading a far reaching address space (than the one currently being written/read) or a closer one as it doesn't rely on spindle/rotations. Hence, having this costing algorithm adds overhead and slows down the overall transaction. CFQ has a lot of algorithms to make sure each process gets a fair slice of time on I/O transcations. Too much overhead.
Deadline has a starvation detector and is simple enough that it doesn't have all the overhead of doing rotational/costing disks algorithm. However, reads are done 2x more likely than writes as it has a algorithm based on weights in that reads must be done first if both a read and a write is detected. It has a 2:1 ratio of read to write weights coded into the scheduler (that can be tweaked - writes_starved, will include it in the next version of system_tweak). Hence it's not a fair scheduler.
SIO is Simple I/O that tries to implement a NOOP type scheduler that has starvation detection. Hence, long I/O transactions will be preempted and given CPU time only after other faster transactions are completed, guaranteeing smoothness. Also, it doesn't have overhead of calculating costs. Also, it has a fair number of writes to read, guaranteeing that all transactions are equal.
BFQ has a lot of algorithms to make sure each process gets a fair slice of bandwidth (Budget Fair Queueing). Too much overhead.
V(R) tries to make sure that each transaction has a weight associated with it, being R. And if the seek is reversed, the R will be multiplied by a penalty making it less likely to be processed. Not for flash drives as reverse seek in a flash drive is just as fast as a forward seek.
In benchmarking tests, the tests normally consists of testing the time it takes for a contiguous I/O transfer from 1 point to another. NOOP excels at that because it won't let itself get interrupted to perform another I/O task. This would mean that in real life testing, NOOP will let a long arduous task to finish while at the expense of UI functionality (you will get UI lags)
SIO on the other hand will perform badly at benchmarking as it gets pre-empted when the contiguous tasks takes more than 0.5secs (for synchronous tasks as benchmarking tools perform a synchronous I/O task from one point to another) to another more important task like UI interrupt (when you're scrolling) or Kernel interrupt (when your kernel needs to perform garbage collecting or swap memory etc)
The 0.5 secs can be tuned in the SIO tuneables though, but I would think 0.5 secs for synchronous tasks and 5 secs for async tasks is pretty good to maintain a balance between long/short tasks enabling a smoother experience in Android.
LowMemoryKiller
The LowMemoryKiller is a constant debate between more free RAM and more multitasking capabilities as free RAM (more than 60MB free) is actually wasted RAM. The fact is SGS only has a puny amount of RAM left after a few big chunks are allocated to the Graphics, Modem, Sound and Video (and some others that I do not know a lot about). With that knowledge, Samsung decided to give the SGS SL a bigger amount of RAM when they released it ( about ~650MB of RAM read that from somewhere, can't remember).
The LowMemoryKiller is actually a feature in the Android OS for better memory management.
You can read about it more here:
http://forum.xda-developers.com/showpost.php?p=5442369&postcount=1
This is an important feature due to the perennial problem of having low free memory causing lagginess and slowness in launching apps. When you have free memory lingering around the number of 40MB or less, the Android OS just lags like hell.
What this would mean is, you would want to tweak the LMK to not have the situation of it having less than 40MB (or even close to that).
The modern Linux machine in the Android ecosystem relies on a mechanism called Low Memory Killer (LMK) to consistently free up RAM. This is due to Android's internal mechanism of caching apps (and never fully exiting them) when you press the back button. This is to enable faster app switching and provide a seamless experience for apps usage model. Android also, by itself will also constantly look for often used apps to cache them for faster app opening. This will happen even before your system fully boots.
Now, when you mention LMK, the most obvious thoughts that come up are minfrees and Out Of Memory (OOM) groupings. Yes, those two are integral parts when it comes to LMK. The issue here is that no one actually mentioned that there are two LMK systems in Android, that being:
- Linux LMK
- Android Dalvik VM LMK
Both are separate entities that kills/removes app/dalvik cache from RAM when RAM reaches a certain level.
What confuses most people (including me) is that the OOM groupings of both mechanisms have the same names being (Android 2.3 based):
LMK App Categories
FOREGROUND_APP: Your apps in the foreground, being used currently, interfacing with the user.
VISIBLE_APP: Visible app that is still viewable by the user, but not interacting with the user, example could be apps that reside in the status bar, and giving live information i.e. Os monitor graphs.
PERCEPTIBLE_APP: App that the user can still perceive i.e. Music app that is playing music.
HEAVY_WEIGHT_APP: RAM heavy apps that are not being interacted with, but will be a pain to load if its information is cleared in the memory.
SECONDARY_SERVER: App that acts as a secondary server. Not sure what this really means, but client-server thingy but secondary? Could be something that syncs with an app, but is not syncing currently?
BACKUP_APP: App that is currently making a backup (like Titanium backup?)
HOME_APP: Your launcher.
HIDDEN_APP: An exited app that still significant residual memory in the RAM. Exited only some time ago, or is constantly used by the user.
EMPTY_APP: An exited app that only has small remnants of residual memory in RAM. App that is exited quite some time ago.
Take note that this is my understanding of the OOM groupings. If there are mistakes, please correct me
Tuning LMK
Both the LMK and Dalvik VM has this groupings and they can be tunable by using prop and lowmemorykiller/parameters/adj respectively.
One errata about this is that the Dalvik LMK has one extra tunable which is CONTENT_PROVIDER, which affects widgets that are not currently refreshing or displaying information. The ADJ (which I will explain later) is not available to be tuned though. And it is clearly missing from the Linux LMK.
The ADJ is the so-called priority of the app categories, with 0 being the highest (should not be killed) and 15 being the lowest (should be the first to be killed). I haven't seen values other than 0-15 but I have a feeling that the numbers are arbitrary, and can be extended up to 65535, but who would want to do that since they're only 9 app categories
LMK are specified by pages, with memory = 4 * pages.
e.g.
4096 pages represents 16MB RAM (16 *1.024)
From the Linux LMK source code, the parameters can be adjusted as such:
Code:
* For example, write "0,8" to /sys/module/lowmemorykiller/parameters/adj and
* "1024,4096" to /sys/module/lowmemorykiller/parameters/minfree to kill processes
* with a oom_adj value of 8 or higher when the free memory drops below 4096 pages
* and kill processes with a oom_adj value of 0 or higher when the free memory
* drops below 1024 pages.
Take note that the oom_adj so far takes only 6 values (although I am confident that it can take more than that). Haven't experimented enough to validate that, but I shouldn't need to as assigning different oom_adj should be a given for all the app categories. This is to make the LMK intelligent enough to determine which app to kill first rather than grouping different app categories into one priority, in which a lot of popular LMK settings that devs provide do that.
And for the Dalvik LMK, my understanding is that it will remove all dalvik caches of <INSERT_APP_CATEGORY_ADJ> or higher if free RAM/pages reaches the level specified.
Hence, two things are learned here:
- Linux LMK will kill an app category of that particular RAM level or higher if free RAM drops below a certain level e.g.
Hidden_APP has a minfree of 16384 pages. If pages fall below this level, Empty_App will be killed first, free pages is recalculated, then if RAM is still below that, Hidden_Apps will be killed next.
- Dalvik LMK will clear all dalvik caches in RAM of all the App category if free RAM reaches the level e.g.
SECONDARY_SERVER_MEM is 8192 pages. When RAM reaches 8192 pages, all SECONDARY_SERVER caches are cleared.
Best Practices
Now, how do we tweak both so that it is efficient in doing its job, i.e. LMK.
From my experiments I can safely say that:
- Below 60MB free RAM you will feel lag 5-10% of the time.
- Below 52MB free RAM you will feel lag 5-15% of the time.
- Below 46MB free RAM you will feel lag 15-20% of the time.
- Below 42MB free RAM you will feel lag 20-50% of the time.
- Below 36MB free RAM you will feel lag 100% of the time.
The experience of lag increases exponentially from 60 down to 36MB. Hence, the LMK should be tweaked against that.
Also, it is considered best practices to group oom_adj settings of Linux LMK with the Dalvik LMK as when free RAM drops to that level, both the Linux LMK and Dalvik LMK will work together to free up at both sides.
The 6 oom_adj that can be tuned for Linux minfree also need to be tuned correctly, failing this would make the LMK too aggressive/under aggressive in mid levels (even if your EMPTY_APP is aggressive, if your oom_adj is selected incorrectly, you'll get to a point where memory leak occurs).
Talon LMK - This is obsolete, TalonDev is using ThunderBolt! LMK from 0.5.x
Take for example, the Talon default LMK setting where:
LMK_ADJ is 0,1,2,3,7,15.
It's EMPTY_APP is 15
It's HIDDEN_APP is 5
It's HEAVYWEIGHT, SECONDARY and BACKUP is 3
Last three values of MINFREE is 4096, 9216, 12288.
Where's the issue here? If you noticed it congrats.
If you didn't, here's the issue:
The minfree 12288 is tied to EMPTY_APP which has a OOM_ADJ of 15.
The minfree 9216 is tied to nothing but has a OOM_ADJ of 7
The minfree 4096 is tied to HEAVYWEIGHT,SECONDARY and BACKUP with the OOM_ADJ of 3.
The LMK_ADJ is important as it represents the checkpoints where the Linux kernel will check for minfrees and kill them. Here's a situation:
Memory is below 12288 pages, OOM is triggered and Linux looks for EMPTY_APP to kill and kills all of them. Job done. Memory is back to >12288 pages.
After a few days, memory is below 12288 pages again, OOM kills all EMPTY_APP, but free memory is still lower than that. It sees if the next checkpoint is fulfilled, which is 9216 pages, and yes memory is still below 9216 pages. It looks for an OOM_ADJ of 7 and above to kill, but fails to find any as 7 and above OOM_ADJ only consists of EMPTY_APP.
Here comes the quandary. The next checkpoint is 4096. We're not ever going to reach that as you'll need memory to fall below 16MB, and at that time it'll be super sluggish to even support GUI. Hence BAM, memory leak or lag or something.
Supercharger LMK 512HP - Multitasking
Let me just paste this to avoid a lot of retyping
Code:
FOREGROUND_APP_ADJ=0
VISIBLE_APP_ADJ=4
PERCEPTIBLE_APP_ADJ=2
HEAVY_WEIGHT_APP_ADJ=5
SECONDARY_SERVER_ADJ=6
BACKUP_APP_ADJ=7
HOME_APP_ADJ=1
HIDDEN_APP_MIN_ADJ=8
EMPTY_APP_ADJ=15
FOREGROUND_APP_MEM=1536
VISIBLE_APP_MEM=3072
PERCEPTIBLE_APP_MEM=1024
HEAVY_WEIGHT_APP_MEM=10240
SECONDARY_SERVER_MEM=10240
BACKUP_APP_MEM=15360
HOME_APP_MEM=1024
HIDDEN_APP_MEM=15360
EMPTY_APP_MEM=25600
LMK_ADJ="0,4,6,8,14,15"
LMK_MINFREE="1536,3072,10240,15360,20480,25600"
A few things here:
It's EMPTY_APP and HIDDEN_APP is too large, 80 and 100MB respectively, but the 80MB is a false flag hence it doesn't really matter if you tweak that and you can get a very minor degree of multitasking because of this false flag. I'll get to that in a moment.
It's PERCEPTIBLE_APP has higher OOM_ADJ than VISIBLE_APP (odd selection, but RAM rarely goes below 40MB before it starts lagging like hell) People would reboot their phones when it gets to that, but it rarely gets to that for this configuration as LMK is pretty aggressive here.
Now, it's LMK_ADJ is "0,4,6,8,14,15"
15 is EMPTY_APP,
14 is nothing
8 is HIDDEN_APP - it looks like it'll only kill HIDDEN_APPs when it reaches 60MB, with HIDDEN_APPs being the heavy hitter of apps as most apps will end up in this category. Hence why multitasking is still doable (to an extent) but an aggressive LMK means taking a call or switching to a browser will kill your game (losing saves). Inconvenient, but it works for some people who haven't played a long game without saving and never took a call in between. Imagine the horror LOL!
Juwe's RAM Script
Code:
if [ -e /sys/module/lowmemorykiller/parameters/adj ]; then
echo "0,1,2,4,6,15" > /sys/module/lowmemorykiller/parameters/adj
fi
if [ -e /sys/module/lowmemorykiller/parameters/minfree ]; then
echo "2560,4096,5632,10240,11776,14848" > /sys/module/lowmemorykiller/parameters/minfree
fi
No OOM_ADJ are given, hence the stock ones are in effect here.
From init.rc, this is the stock 2.3.5 OOM_ADJ.
FOREGROUND 0
VISIBLE, PERCEPTIBLE 1
HEAVY_WEIGHT, SECONDARY_SERVER, BACKUP 2
HOME 4
HIDDEN_APP 7
EMPTY_APP 15
This one also suffers from the false flag of the 2nd last minfree not being used. It will start killing HIDDEN_APP at 40MB, which is usable (you'll only get lags 15-20% of the time, and most probably after long usage). Other than that, it's pretty stable.
Misc
There are a few known scripts that tweaks the LMK as well as the app priority (yes, the priority of the process categories can be changed too by using setprop.)
Supercharger is one of them:
http://forum.xda-developers.com/showthread.php?t=991276
Take note that Talon doesn't permit Supercharger to be used (it will override it when booting through boot scripts) as Talon itself uses its own LMK settings that are optimized for ZRAM/Swap.
Kickasskernel script is also included in Supercharger. The script will clash with Zach's script in ThunderBolt! too as both of them tries to set different values for the same settings.
Note that Zach's script doesn't tweak LMK settings as i9000 Talon doesn't permit it. With that, if you're using Zach's scripts, you would need to find other ways of tweaking the LMK. Using Auto Memory Manager is good. You can download Supercharger, look at the presets and apply it using Auto Memory Manager. The preset is the only thing important here
LMK App Category Priorities
Using setprop, there is a way to set the priorities of the category. Since, app categories are different, I can only offer one recommendation: The HOME_APP_ADJ.
This prop setting sets how high of a priority your launcher is. A 1 or 2 is sufficient to make sure your launcher doesn't get killed. However, do you really want it to be on 1 or 2. Based on the previous article (LMK/OOM), you would know that OOM priorities are comparatively based on one another. Setting it 1 or 2 in stock 2.3.5 values would basically override PERCEPTIBLE/VISIBLE app priorities. Do you want your launcher to be killed only after your keyboard/music player to be killed? You decide
Journaling/Barriers
This has been a touchy subject here in XDA for most people who debate about it. Most recently, the SAS/Acid tweaks included a way to disable journaling on these partitions:
/system (System is read only, it's safe to remove journaling. However, you will not see speed increase by removing it as you're not writing onto /system 99.99% of the time unless you're using Titanium backup to remove system apps or copying init.d scripts to it)
/cache (Cache can be rebuilt on the fly. Data corruption on it is not game breaking)
/data (All of your data on your phone is here. Removing journaling can risk data corruption. Read more below)
On whether we need journaling or not, I will pose this situation:
Journaling is required to maintain data consistency in events that could lead to data corruption. Data could get corrupted in a number of situations:
- Misbehaving app that constantly writes without syncing/committing data to the disk
- Power loss due to forced reboots or bootloops when data is partially written/committed into disk
Android will normally buffer its writes before committing to the disk. This way, data stays in the RAM before data would only get written into the disk after a period of time. Take note that we as Android enthusiasts seek ways to better our phone to get the most out of it through experimental and sometimes wacky ways. Take OC/UV for example. When we OCed or UVed too much, sometimes our phone will get deadsleep or constant reboots. This leads to corruption if journaling is not turned on. However, we can get corruption too even with journaling but the risk is smaller.
Mount options too, play a role in whether journaling can be safe/unsafe. Most lagfixes will place a "barrier=1" in the /data to make sure that journals are actually committed before an out-of-order write is done. With that, the risk is greatly reduced at the cost of performance. You could experiment by removing barriers and see if it works for you. No guarantees on data if you remove barriers! More info on ext4/barriers:
http://lwn.net/Articles/283161/
http://kernelnewbies.org/Ext4#head-25c0a1275a571f7332fa196d4437c38e79f39f63
If you do disable journaling, make sure to manually run an fsck on your disk. Make sure the fsck binaries are in your binary paths (echo $PATH to show your binary paths). Don't ask how to do this if you're unable to do fsck. It is your own risk that you are disabling journaling/barriers.
One experiencing I would like to relate is this:
I've personally disabled ext4 journaling on my device. After experiencing a sudden power loss (forced reboot), my apps started FCing left and right and device became unstable that it sometimes rebooted when the device is sleeping. In other words, it's a lost case. Reflashing was the only way to restore my phone. This happened 1 day after disabling my journals.
Also note that ext2 is basically an ext4 without journaling. However, ext4 is updated all the time while ext2 source is not updated for quite some time (2 or 3 years?). Most optimizations are already in ext4 while ext2 even without journaling is slower than ext4 without journaling. A comparison of performance:
No journal:
ext4 > ext2
With Journal:
ext2 (can't do journaling in ext2) > ext4 > ext3
Update: Attached is a JournalingOn.zip for i9000 only that you can flash to rejournal your partitions (Only for i9000 devices!). Also attached is Acid Tweaksv6 - Removed Useless Stuff that will disable journaling only for /system and /cache, if anyone is interested. You will need to rejournal first before unjournaling. To be sure that /system and /cache has no journaling and your mounts are applied correctly, type "mount" without the quotes.
You'll be able to see that /data will have:
Code:
barrier=1, data=ordered
/system and /cache will have:
Code:
barrier=0, data=writeback
To be really sure, you can check by using tune2fs included in both the JournalingOn.zip and Acid Tweaksv6 - Removed Useless Stuff.zip.
Copy the tune2fs to /tmp and set rwxr-xr-x as its permissions using Root Explorer/File Expert
Code:
/tmp/tune2fs -l /dev/block/mmcblk0p2 | grep features
You can substitute the /dev/block/mmcblk0p2 (which is /data) to /dev/block/stl10 (/dbdata) /dev/block/stl9 (/system) /dev/block/stl11 (/cache) to check each partition.
Continued in Post #2 - Lack of space
Still posting ...

Undervolting/Overclocking
This is also another touchy subject, but more towards people complaining about phones that get forced reboots or bootloops. OCing is done to get better performance on your android. WARNING: Ocing will cause more wear and tear on your CPU and will reduce your CPU lifetime. How much it will reduce it? No one knows. It depends on how sturdy your CPU is, and that cannot be measured by any means. It could be reducing months out of year e.g. 6months out of 3 years? No one actually knows.
UVing on the other hand reduces battery drain especially when you UV your 100MHz as 90% of the time in normal usage, your CPU will idle at 100MHz. How much can it save? No one actually did a benchmark on it. Save to say, UVing does not harm your CPU, it will actually extend the life of it by reducing wear and tear Oh, bootloops do corrupt data if you're without journaling
Always remember to clear your UV/OC settings before flashing another kernel!
Take note that the ability to OC/UV depend on your phone. Some SGS can UV better or OC better and some might not.
On how to UV:
1. You can UV more on the lower frequencies than the higher frequencies.
2. Do a UV for
100MHz with (950-150=800) - Take note that 950 is the base value for the voltage. Some kernels might have changed this value to 925 or 900. This is why clearing your OC/UV settings is important as the OC/UV settings will only load the voltage difference, which in this case -150. If the base voltage is 900 and you do a -150 for it, you'll end up with 750 which might cause bootloops.
3. Limit the max frequency to 100MHz. WARNING: Doing this will significantly slow down your system to a crawl, but it is still running. This is done only to test the stability of your system. You can skip this if you want, but you would need to find a way to stress test your CPU at the 100MHz value (and other values as well by limiting the max frequency). Failing in testing this will result in deadsleeping (as your phone is in 100MHz when you sleep and if you undervolt too much, you deadsleep)
3. Test with RockPlayer (or MX Video Player) and play an RMVB file using software decoding for 10mins. If your settings is unstable, Android will freeze up and reboot. (this is just an example, but I find that this way stresses the CPU to the max. I fail to find another way of stressing it as even playing NFS is stable on some voltages but fails when I play rockplayer. Hence rockplayer is the best way so far)
4. After doing this, remove the limit and move on with the next few frequencies.
The rest of the voltages, just rinse and repeat.
200MHz with (950-100 = 850)
400MHz with (1050-75 = 975)
800MHz with (1200-25= 1175)
1000MHz with (no change)
You can experiment with lesser values than these if you get freezes/bootloops as this is by no means a one size fits all value. Some might think this UV is overly aggressive or some might think that this UV value is too underwhelming.
Mine if you're interested:
Code:
100MHz = -200 (950 base)
200MHz = -150 (950 base)
400MHz = -125 (1050 base)
800MHz = -75 (1200 base)
1000MHz = -50 (1275 base)
As for OCing, you would do the same to test the stability. Just that you will be enabling a higher clock for your L0 frequency (L0 is the highest frequency). Some kernels might add more frequency states i.e. from the 5 states above to 6. You can try using Tegrak OC app too. It all depends on your own experimentation.
Memory Leaks
If you found out that your Android is laggy after sometime and a reboot will make it faster, then you're experiencing memory leaks. "free" is a command to show your currently free memory. It will not necessarily be the same value as your phone's free memory (as it takes into account swaps and buffers)
1. Go to terminal emulator (or download the script at Post #3)
Code:
su <ENTER>
free <ENTER>
This will show your buffers and free memory.
My example:
Code:
total used free shared buffers
Mem: 348548 340280 8268 0 1320
Swap: 163836 47292 116544
Total: 512384 387572 124812
Then do this:
Code:
sync <ENTER>
echo 3 > /proc/sys/vm/drop_caches <ENTER>
Type:
Code:
free<ENTER>
And you'll realize that the buffers will reduce and free memory will increase, like this example:
Code:
total used free shared buffers
Mem: 348548 305212 43336 0 88
Swap: 163836 46804 117032
Total: 512384 352016 160368
That means it's done.
Click to expand...
Click to collapse
If this solves the laggginess problem, it's due to vfs_cache_pressure being too low and dirty_ratio being too high. However, in most cases, you don't have to do this as Linux will manage to clear the RAM in a timely manner as long as there are no apps that constantly hold on to the memory (not releasing it). Hence, only do this when necessary (lagginess and such).
With that, I've updated the system_tweak yet again, with this knowledge by making the VM settings more aggressive, which will trigger the memory leak faster. I made this so, as there's a workaround to clear the caches when it gets full.
Having a low vfs_cache_pressure and a high dirty_ratio will save battery and make your device perform faster at the cost of higher RAM usage.
You can actually automate it by using Script Manager by making a script, pasting the instructions and making a widget out of it. To learn more, read the android market description or the in-help guide in the app.
Some commonly asked questions about drop_caches that were answered by me from flolep:
http://forum.xda-developers.com/showpost.php?p=17727859&postcount=3428
http://forum.xda-developers.com/showpost.php?p=17731938&postcount=3446
http://forum.xda-developers.com/showpost.php?p=17736421&postcount=3450
Checking for Battery Drain/ Saving battery
Starting from Gingerbread, you can't really look for Partial wakelocks anymore to determine what is draining your battery at night. BetterBatteryStats is a way to check for that. It also can provide the process that drains your battery most of the time.
A high partial wakelock usually says that something is waking up your phone at night. With that, checking partial wakelock, you can see if these are the culprit:
-Network Location
-Location Manager Service
If so, disable Lattitude or any location check-in app that you're using. It's checking you in every few minutes that drains the battery.
Disabling Wifi/3G/HSDPA saves battery too. I find that Wifi/Edge drains the least amount of battery when idling. To switch to EDGE as opposed to HSDPA/3G.
Go to:
Code:
Settings > Wireless > Mobile Networks > Network Mode > GSM Only
Disabling "Use Wireless Networks" in location and security would save a little bit of battery too I guess. It's in:
Code:
Settings > Locations and Security > Use wireless networks
CSC
CSC is a folder that defines your APN settings and country/region specific configurations aside from Language/Time that is configured in build.prop(also for Samsung Apps).
Having to manually set your APN is annoying right?
Your product code being KOR by default is another annoying thing to deal with. How do I resolve this?
1. Get your CSC from your own country here: http://forum.xda-developers.com/showthread.php?t=948790
2. Extract from the zip file /system/csc/<folder> (where <folder> is your Country's CSC)
3. Use Root Explorer/File Expert to copy it to the phone's /system/csc/.
4. Use nitrality to change your product code. WARNING: This will wipe all your data.
Odexed vs Deodexed
I've been using Deodexed ROMs since I first flash my custom ROMs. One gripe I have is that I seem to have lost the stock smoothness/speed that I experience when I'm using a stock ROM. I found out that deodexing actually extracts the customization files back to the APK (using APK manager) and Odexed files are actually done to optimize the speed of those files itself.
The only reason ROM chefs are using deodexed files is that it is easier to theme. There is no need to decompile the odex files and make the changes as all the theme files are in the APK themselves.
Only other reason that I know of is the overscroll glow. Odexed files can't support it. However, that is a small price to pay for speed/smoothness that I am willing to sacrifice.
Busybox
Busybox is required to perform all of your superuser activities in your android phone. There are some problems associated with this when ROM developers decide to use a certain version of Busybox that are incompatible with the binaries that we use in our phones. When you found out that after changing your kernel/ROM:
- You still have superuser and Titanium Backup still works but,
- Root Explorer/File Expert can't copy files correctly to the /system after mounting rw
- Voltage Control/ Pimp My CPU/ Control Freak/ SetCPU cannot create the Svolt_scheduler file in /etc/init.d
You have a clashing busybox version issue. This can be remedied by:
- Installing the busybox installer from the market
- Installing busybox 1.17.x into /xbin
- Removing all other busybox binaries from your binary path. (This is optional if you found out that after installing busybox, everything works. Try it first before removing) To know your binary path, do an
Code:
echo $PATH
Nandroid Backup
Nandroid Backup is done in recovery (VolumeUp + Home + Power). In recovery, choose Backup And Restore. What it does is it backs up your:
- Boot
- System
- Data
- Cache
When you restore, you should preferably use Advanced restore and restore the /system and /data. All others can be built from scratch (except /boot). If you're converting from CM7 to Samsung Roms, it's best to start from scratch either ways. Restoring nandroid from any is considered dangerous and not supported by most cases. Best is to use Titanium Backup to backup as it can be restored both ways (only restore app though, restore data sometimes can lead to FCs)
Voodoo Color
Voodoo Color is also a point of contention among users. Some like it and some hate it with a passion. If your kernel does support it, here's a way to tweak it:
1. Tweak the color profiles. Can't see a difference, hence I would just pick Voodoo most of the time.
2. Tweak the gamma first to a comfortable value. I.e. drag the 3 sliders together to a comfortable gamma level. After that, try looking in the gradient (the gray slab below the slider) and try to find for neutral gray values. Adjust each slider until you find a neutral gray (i.e. left and right until you see that slab is truly gray)
3. Tweak the RGB multiplier until you have a comfortable level (3 sliders together). Then tweak it the same by referring to the gradient until you're comfortable.
4. Switch off your display for a while and look at your surroundings to reset your eyes. Then turn on your screen again and see if its too green/yellow/blue etc. Adjust the gamma/RGB multiplier until you're satisfied.
This might take a few rounds of testing, but in the end you'll be truly satisfied with it
i9000 Specific
i9000 Kernels - In Depth
You will need to have a stock odexed (why odexed? read a few passages below)ROM with root. You can easily do this by flashing stock XXJVS 2.3.5 and then flashing a custom kernel through Odin like:
- Dark Core - Uses Voodoo initramfs
- CF-root - Uses CF-root initramfs
- Semaphore - Uses CF-root initramfs
- Midnight - Uses Speedmod initramfs
- Galaxian - Uses CF-root initramfs
- Voodoo - Uses Voodoo initramfs
You can flash the custom kernel through Odin by placing the tar file into the PDA section and pressing Start. At this point, do not convert your partitions to ext4 (lagfix) unless you're using a Voodoo based initramfs as Voodoo based initramfs will convert your partitions to ext4 automatically at first boot.
After flashing a custom kernel through Odin, you will gain root. From there, you can choose to use any other custom kernels that use CWM to install or stick with the custom kernel that you've flashed through Odin like:
- TalonDev - Uses Voodoo initramfs
- TalonSH - Uses Voodoo initramfs
There are other kernels as well, but since I did not stress test them, I will not include them here. This thread lists the full repertoire of custom kernels that you can choose from:
http://forum.xda-developers.com/showthread.php?t=1196704
On which custom kernel to pick, you're advised to look at the individual threads original post as well as the last 5 pages of the thread to know about its stability and features. I pick TalonDev myself as it has compache as well as the latest upstream (kernel updates from the Linux OS as well as the official Android Open Source Project/AOSP and optimizations) patches.
At this point, you should decide if you would want to convert to ext4 (lagfix) or not. Your phone by default will reside in an RFS system. The RFS at this point in time is pretty stable and its performance can easily match ext4. Too bad Quadrant scores are bad for RFS, but who cares about Quadrant anyways. I myself choose to use ext4 as the TalonDev kernel has a lot of ext4 upstream patches that optimizes the usage of ext4 on Android.
If you're using Voodoo initramfs, you'll be converted to ext4 automatically.
If you're using CF-root initramfs, you will require the CF-root ext4 app to convert that can be found here:
http://forum.xda-developers.com/showpost.php?p=12651371&postcount=7
Note that on some kernels that use CF-root initramfs, the ext4 app will warn you that you're not on CF-root type kernels. Ignore this warning. You'll be able to convert to ext4 anyways unless you're on Galaxian. Certain Galaxian versions (since the kernels are not versioned, I can't tell which versions are not working) will bar you from converting to ext4 using the ext4 app. If that is the case, just flash CF-root, convert to ext4 and then flash back to Galaxian.
Also not that CF-root based initramfs kernels will remove your bootsounds on first boot. Don't be alarmed by this.
In terms of which lagfix is better (Voodoo vs CF-root lagfix), I can't tell at this point in time. Both are equally good. Since TalonDev uses the Voodoo initramfs, I am inclined to use the same when I am using the same kernel. That should be a good yardstick to follow.
BIGMEM/ Non-BIGMEM:
Some kernel developers released BIGMEM versions of their kernel:
-TalonDev BIGMEM
-TalonSH BIGMEM
-Semaphore bm version
The only difference a bigmem kernel can bring is more memory at the expense of 720p video recording. Playing a 720p video is still possible. Recording it is not on a bigmem kernel. Bigmem kernels normally have 13MB more than their non-bigmem counterparts. How this 13MB could affect you? It depends on the apps you use and how aggressive your LowMemoryKiller is.
XXJVT System apps
System apps can be frozen/removed to make your system faster/less battery draining.
In order to remove/freeze system apps, you would need Titanium Backup (Pro) or System Tuner.
The choice whether we want to remove or freeze the system apps should now be decided. Titanium Backup Pro and System Tuner uses a built in Android mechanism to freeze your system apps - PM disable. PM disable will actually disable the app from the system itself. It will not drain the battery or even launch itself. It is a safer way so to speak. Removing will physically delete the APK app from the system freeing up disk space. If you decide to remove, make sure to have a backup before proceeding. Even if you have a backup, restoring from Titanium Backup may sometime fail. Hence, do this only if you're sure you want to remove that certain app. Freezing an app will make it easier to defrost without any consequences.
Here are the apps that I disabled:
Code:
AngryGPS > Used to manually configure GPS. Not needed if GPS works OK.
BluetoothTest
Buddies Now
lcdtest
screencapture > Screen capture app
Daily Briefing
Days
EncryptApp
Factory Test
Gallery -> I use QuickPic as a replacement. It's faster than Gallery.
Google Partner Setup
Google Search > Google search widget
Home screen tips
HTML Viewer
Market Feedback Agent
Market Updater > I froze this to avoid being updated to Market 3.0. It currently sucks now
Mobile tracker > Mobile tracker, only if you use it, then keep it
Mobile tracker settings > Mobile tracker, only if you use it, then keep it
Perso
PhoneSetupWizard > Required if you're first booting/installing the ROM, not needed afterwards
PopupuiReceiver
Press Reader
Print via Bluetooth
RoseEuKor
Samsung Account
Samsung Keypad -> I use Swype beta instead
Self Test Mode
Service mode
SimDetachNotifier > Will notify you if you detached your sim card. Seems pointless
SNS > Only necessary to sync your contacts if you're using Social hub to do so or syncing calendar from Facebook
SNSAccount > Same as above
Social Hub
Software Update
Synchronise
TwLauncher -> Using Go Launcher Ex instead
wipeoutreceiver > Wipe if phone is stolen. Not needed if you don't use the Samsung service
WlanTest
wssyncmlnps
There are others that you can remove as well. I'm hoping to gather feedback on the other APKs that can be removed and what will be affected by its removal. Please post if you have more information
Disabling Lagfix
Most ROMs would advice you to disable lagfix before flashing a new ROM. Although this is not necessary in most cases (as all Gingerbread kernels support ext4 from the get-go) moving from one kernel to another might need it (to optimize the initramfs it is used on). Hence if you're swapping from one kernel (that has a different initramfs) to another. It is adviseable to undo the lagfix.
CF's lagfix can be undone by using the ext4 app.
Voodoo lagfix can be undone by using the Voodoo Control App.
Speedmod lagfix can be undone by using it's recovery.
Odexed ROM
You might say, hey if I'm using stock, I'll be missing extended power menu, battery percentage and all other theme mods that are not in the stock ROM. Fear not, you can get all these back including Gtalk2, CRT screen off etc here:
$omator's stock+
Gtalk2
There are odexed themes too, in which the developers would decompile the odex files into APKs, make the changes then compile the APKs into odex files again. It is more tedious than deodexed themes but odexing generally makes the phone smoother
You can find the themes here:
http://forum.xda-developers.com/forumdisplay.php?f=666
WIFI Issue on JVR/JVS/JVT
You might be facing some wifi connectivity issues on JVR/JVS/JVT ROMs i.e. it disconnects every few seconds.
This is due to some changes in the ROM that doesn't permit a "Forever" lease time from your modem. Change your lease time to an hour (or two) or if you don't have that option, remove your address reservation option from your modem (Yes, it's a modem only tweak, nothing you can do on your phone)
Memory Freak
Memory Freak is an app in TalonDev that tweaks the ZRAM/Swap and LMK settings. There's a golden rule to the ZRAM/Swap that is:
Swapping to and from the ZRAM will be slower if the amount of ZRAM is more than 50% of the total usable memory, . Hence, I set mine to 160MB (from the 340 total usable RAM). Swappiness in most Linux machines is 60. This means, the system will be inclined to swap in/out more than just using the RAM. I set mine to 50 as a personal preference so that there would be 50% chance that the system will use swap or RAM.
HiddenApp is the amount of free memory to be when LMK starts looking for hiddenapps to kill. I set mine to 52 for my multitasking preference. Experiment with it to see how much multitasking vs smoothness you're looking for. My preference will change in time. Check my signature for the most updated ones.
WIP:
This is obviously a work in progress article that will undergo changes as the Android scene improves. I will spend time to make edits and additions to the post whenever I see fit. Sometimes I will post changelogs at the end of the thread, sometimes I won't if I only make minor edits. Just be sure to check back often to see any new tips offered
Credits:
I claim no credit on these findings except for the ones that I've researched on my own. However, all of it is not of original work since I form my own opinions after reading a lot. I also don't claim that the settings I posted are the most optimal there is. It might not even work well for most of you guys. The key here is tweaking it to your own perfection as there is no setting that will cater to everyone's needs. Hence the real people who deserve credits are:
* All the devs' kernel/apps that I posted here
* XDA forum
* Google
Attention!
If you're looking for scripts, here it is:
[CWM][SCRIPTS][TWEAKS] Thunderbolt!
Script Reviews are here:
Script Reviews
GUIDE UPDATES
UPDATE 1/10/12
* Edited some sections with some new knowledge that I have. A few places, can't name them all Check them out and see if you can spot them.
UPDATE 10/19/11
* Moved around some guides and grouped them together
* Updated some guides to make them more Android centric (as opposed to i9000 centric)
UPDATE 10/18/2011 - Added an indepth article about LMK/OOM. CTRL-F for LMK.
UPDATE 10/12/2011
* Added some comments on the apps removed/frozen so that you can make an informed choice of why the apps can be removed/frozen.
* Added my analysis of most schedulers that I know of and why they are good/bad.
* Moved the scripts to ThunderBolt!: LINK
* Added a guide on the wifi issue for JVR/JVS/JVT
UPDATE 10/1/2011 - Moved the script reviews to this post LINK
UPDATE 9/23/2011:
* Removed the JournalingOn.zip and Acid Tweaksv6 - Removed Useless Stuff.zip because people might use it for devices other than the i9000. This is because in other devices such as SGS4G, the /dev/block/stl10 is /data while in i9000 it's /dbdata. The JournalingOn.zip will not enable journaling on /dbdata without some editing. Hence, I removed it as I don't have a time to put up a warning or notice, and didn't have time to edit the script inside the zip file.
* Readded an edited JournalingOn.zip and readded the Acid Tweaksv6 - Removed Useless Stuff.zip (did not change) to the first post. Only for i9000 devices!!
* Added another way to check if you're journaled or unjournaled. Check the guide below.
* Added some more explanation on common scripts I found.
* Moved the guides around due to lack of space. I added some minor changes to most of the guides. See if you can detect them

Reserved - 10 char

Reserved - 10 char again ...

Changed the name to get more attention. Surprised that no one gave a comment about it
Appreciate any comments or criticisms or correction of what I've written here.
Thanks!

Excellent Read!
Thank you very much!

carnagecjb said:
Excellent Read!
Thank you very much!
Click to expand...
Click to collapse
Glad you enjoyed it

this is actually really helpful. half the time I really didnt know what I was messing around with thanks.

Dataslycer said:
this is actually really helpful. half the time I really didnt know what I was messing around with thanks.
Click to expand...
Click to collapse
Cool Glad that you liked it.
Hope this gets more attention as I would want it to be beneficial to people who uses tweaks and to know how to use them

Nice read Mate. I used to wonder about I/O schedulers and which one to use etc. I like to add build.prop scripts and int.d scripts. This thread just helped me to understand more about it.
Thanks!

read every word, thank you very much. I'll be talking to my kernel dev about BIGRAM... on miui our 720p recording doesn't work right anyways. Thanks again for the great info.
Sent from my MIUI SCH-i500

ShyamSasi said:
Nice read Mate. I used to wonder about I/O schedulers and which one to use etc. I like to add build.prop scripts and int.d scripts. This thread just helped me to understand more about it.
Thanks!
Click to expand...
Click to collapse
Thank you for reading. Hope the knowledge comes in handy when you tweak your phone
sageDieu said:
read every word, thank you very much. I'll be talking to my kernel dev about BIGRAM... on miui our 720p recording doesn't work right anyways. Thanks again for the great info.
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
Wow, great! Hope you enjoy reading it as much as I enjoyed writing it

having trouble with your thunderbolt tweak. I downloaded the file for I9000 placed it on my phone (SD card) mounted my system and data in recovery mode then proceeded to install the thunderbolt zip file. Using script manager i found the bolt_scripts file and ticked the run at boot button. Then i hit the run button and got 14 permission denied messages asking are you root. Do i have to run this as root. Might be a dumb question but im very new to trying this. Thanks

kevnac said:
having trouble with your thunderbolt tweak. I downloaded the file for I9000 placed it on my phone (SD card) mounted my system and data in recovery mode then proceeded to install the thunderbolt zip file. Using script manager i found the bolt_scripts file and ticked the run at boot button. Then i hit the run button and got 14 permission denied messages asking are you root. Do i have to run this as root. Might be a dumb question but im very new to trying this. Thanks
Click to expand...
Click to collapse
Yes, you need to run everything as root . Scripts in init.d would already be running as root. You just need to make sure Script Manager is running as root for the remount script

Excellent thread, very well written, had a quick skim read, but I'm going to take some time tonight to absorb it all ;-).
Thank you!

zeekiz said:
Excellent thread, very well written, had a quick skim read, but I'm going to take some time tonight to absorb it all ;-).
Thank you!
Click to expand...
Click to collapse
Cool Thank you for reading such a long article
Let me know if you have any questions or if you think I made a mistake

superb thread !

testomat said:
superb thread !
Click to expand...
Click to collapse
Thank you for reading

testomat said:
superb thread !
Click to expand...
Click to collapse
+1
10 chars

rom-g said:
+1
10 chars
Click to expand...
Click to collapse
Thank you for the support

[GUIDE] Advanced Interactive Governor Script - Battery Life

Remember to have the screen turned ON while you apply the script!!!
Hi guys!
Today i want to share with you a script i specifically tailored for our 4C, to decrease high battery drain just by tuning parameters of the interactive governor.
As many of you know, on the Nexus 5X forum there is a huge post about different profiles created to achieve the same purpose, and almost all of them works with our device (personally tested)
[GUIDE] Advanced Interactive Governor Tweaks; Buttery smooth and insane battery life!
I raccomed to read it!
One of them in particular was extremely good battery wise but i felt some lagginess here and there (talkin about HawkTail 1.2)
So i decided to make a script myself and share it with you, the idea behind it is to force the CPU to scale better with loads and making the Big cores in use more frequently by tuning some of the kernel parameters.
Plus we will have the GPU idling @ 180MhZ instead of 300MhZ (like in the Nexus 5x) and a switch to noop scheduler.
Performance wise and taking in example the latest stable ROM from Xiaomi.eu (8.0.5) we will have a decrease of about 5k point in Antutu (I'll attach two screenshots, the 71K was the result without tweaking, plus just by switching back to CFQ scheduler you'll get 2K points back but NOOP is more battery friendly)
So here you go, this is my script TAO.
Using it is pretty simple and you have a couple of options: [ROOT IS NEEDED]
Since it's a script, if your rom have INIT.D folder support, you can just move the file under /etc/Init.d and reboot the device. The script will make a log file under /sdcard/TAO.log that you can check if anything went wrong.
The second option, if your rom doesn't have Init.d folder support, just use Kernel Auditor and a text editor.
Open the downloaded file in a text editor, select all and copy the text.
Then open Kernel Auditor, and in the menu look for init.d, enable the "Emulate Init.d" and then click the "+" symbol. It will ask to add a name (let's set it to TAO for coherence), then OK. It will open a new window where we have to paste all the text previously copied, save it by pressing the icon on the top right. Now we can just reboot the device or click the newly created item and select execute.
Third option is to run it manually from terminal.
Plus, i'll add my Thermal-engine-8992.conf that you guys can use to change the thermal throttling values. Download it and replace it in /system/etc/ , set it with permission 644 and reboot.
This modded thermal will move up the limits, long story short, your device will continue to perform even if it gets hot.
Enjoy! & report back for feedback
Remember to have the screen turned ON while you apply the script!!!
P.S.
Files are zipped, extract them!!!
UPDATE
Minor update - use_sched_load set to 0 for both cores
Correction made for the log file
UPDATE 0.7
Since @solis_f is having some problem with the big cores, and this could be a common problem to many others too i've decided to add something in the script that will force the big core online so you should not have any more problem executing the script. Let me know
UPDATE 0.8 - Experimental
Updated Target_loads for both Little and Big cores.
Little core min freq. to 384 MhZ.
Input boost @ 787 MhZ instead of 600 MhZ.
hispeed_load disabled for both cores.
Updated values for UpMigrate.
Enabled core_ctl for big cluster:
With this update, you'll have your big cores Offline most of the time, but they will comes online when needed.
Yours perfd (/data/system/perfd/default_values) with this version have to look like this:
Code:
ihf;787200
iahd;38000
ighl;200
itl;39 460800:5 600000:62 672000:10 787200:81 864000:90 960000:99
gpu_default_pwrlvl;5
sst;33
smil;20
sminr;3
sitl;65
sum;66
sdm;54
cbmf;1525
cbhdr;90
cbhip;16
ihf0;787200
iahd0;38000
itl0;39 460800:5 600000:62 672000:10 787200:81 864000:90 960000:99
imst0;0
ighl0;200
imf0;0
itr0;30000
its0;-1
iiib0;1
intb0;0
ibd0;0
ihf4;1248000
iahd4;38000
itl4;53 768000:64 864000:72 960000:79 1248000:99
imst4;0
ighl4;200
imf4;20000
itr4;30000
its4;-1
iiib4;1
intb4;0
ibd4;0
P.P.S.
Over two hundred downloads, but not even half of you gives me feedback...
UPDATE 0.9
Sorry for the delay, many things to do IRL.
This version is what i'm using now, should be smoother then v0.8, hope you like it.

nice one, will try this

Did you try to run Antutu several times in a row, so we can see is the result of 66k almost constant. Since as we all know, results can degrade towards 44k because of overheating..

predragiPredrag said:
Did you try to run Antutu several times in a row, so we can see is the result of 66k almost constant. Since as we all know, results can degrade towards 44k because of overheating..
Click to expand...
Click to collapse
I did not, but degradation of score is dictated by the thermal config. That's why i modded that too, and pushed the standard limits...
Let me show you with an example:
Code:
[SS-SKIN-XO-THERM-PERF]
algo_type ss
sampling 250
sensor xo_therm_buf
device cluster1
set_point 43000
set_point_clr 37000
time_constant 0
device_max_limit 800000
This is taken from the original file, and it covers the big cluster... when it reach 43° celsius, the thermal throttling will limit the max frequency of the cluster to 800MhZ
Code:
[SS-SKIN-XO-THERM-PERF]
algo_type monitor
sampling 5000
sensor quiet_therm
thresholds 46000 48000 50000
thresholds_clr 44000 46000 48000
actions cluster1 cluster1 cluster1
action_info 1632000 1248000 960000
This is the same part but modified by me, i've added more step... as you can see thermal throttling for big cluster will work once the big cluster reach 46° and it will cut the max frequency to 1632MhZ, then at 48° 1248MhZ and at 50° at 960MhZ
The hot-plug, that put the cores offline, on the original file for the big cluster is marked at 42° for core 4 and 45° for core 5.
On my config file both cores will be hot-plugged once they reach 52°.
TL;DR if you use my thermal-engine conf file, you will get more consistent score on several runs.

Nice to hear that will try this when I have more time to play with my phone and report back.
Great work and thanks for sharing this

GoldGanja said:
Hi guys!
Today i want to share with you a script i specifically tailored for our 4C, to decrease high battery drain just by tuning parameters of the interactive governor.
As many of you know, on the Nexus 5X forum there is a huge post about different profiles created to achieve the same purpose, and almost all of them works with our device (personally tested)
[GUIDE] Advanced Interactive Governor Tweaks; Buttery smooth and insane battery life!
I raccomed to read it!
(...)
Enjoy! & report back for feedback
P.S.
Files are zipped, extract them!!!
Click to expand...
Click to collapse
Hi,
I can not apply root because of he problem between pokemon go and root, (I am playing pokemon go with my 8 years old son a father-son activity and he loves it)
I am using a dev miui rom and i did tune my thermal-engine and remove the input boost using the TWRP file manager to apply the files.
This rom does not have init.d folder could i call your script from init.qcom.post_boot.sh? if so, do you know how to?
best regards,
John

You should look for some sort of systemless root, and magisk to masquerade root and be able to play Po Go on a rooted phone. I don't think you can chain load the script within post_boot.sh and by the way to modify it you should have super user permissions. Anyway keep up the father and son activity, is way more important!
Sent from my Mi-4c using Tapatalk

GoldGanja said:
You should look for some sort of systemless root, and magisk to masquerade root and be able to play Po Go on a rooted phone. I don't think you can chain load the script within post_boot.sh and by the way to modify it you should have super user permissions. Anyway keep up the father and son activity, is way more important!
Sent from my Mi-4c using Tapatalk
Click to expand...
Click to collapse
thanx, my son does not talk about anything else...
About the chain load the TS rom does that with ts_power.sh file.
Code:
# ts power scripts permissions
chown -h system /system/etc/ts_power.sh
chown -h system /data/ts_power.sh
Code:
# Call ts_power.sh, if found
if [ -f /data/ts_power.sh ]; then
logi "Call /data/ts_power.sh set_profile $profile"
sh /data/ts_power.sh set_profile $profile
elif [ -f /system/etc/ts_power.sh ]; then
logi "Call /system/etc/ts_power.sh set_profile $profile"
sh /system/etc/ts_power.sh set_profile $profile
fi
I will try to see if it works using your script.
About systemless root, i don't want to be in the middle of the cat and mouse thing. Today google update and tomorrow there is another hide root.
I did replace the thermal engine using the twrp file manager. It works.

Nice share bro. Thermal engine + init.d script is good battery backup for mi4c.

Hello,
could you make patched files available and the place where they should be placed ?
I don't want to root my phone but I want to give your optimisation a try. It is possible with TWRP to replace the files in the file manager. More work but it can be done without root. Therefore however I will need the allready patched files....
A little more "complicated" even... might it not be possible using TWRP to flash these files ? I have no idea how that would work exactly but I can imagine it would be possible to create a flashable zip that replaces these files... It currently goes beyound my abbilities though unfortunatly but maybe someone can help with that.

Thanks for your share @GoldGanja , looks interesting.
But i think the thermal-engine.conf would cause more overheating as it is already (for me reduce overheating is the most important), but i like the way to reduce the clockspeed step by step. Maybe i will try it with lower values.
The modified governer looks great. I think this will help with heating too. But on this there aren´t laggings ?

Thank you! i hope this fix my battery drain and the heat, i'll report if i see changes

@nachtwacht
Even if i make a zip file to use with twrp, this will only be useful for the thermal-engine conf file...because the other one is a script i've created and so there is no other file to replace. As stated ROOT is needed, i'm sorry.
@Danny94
thermal-engine.conf per se will not increase or decrease over-heating, of course one could make a conf file to be more restrictive on the temps and brutally decrease the performance but i don't see the need of this because i don't have any over-heat problem within my device with the script i've made. A major cause of over-heating is the input-boost frequency that by default is set to 1248MhZ, while if you run my script it will be 600 MhZ. Farther i have no lags at all...give it a try and report back. More feedback I have about it, the better I can adjust some parameters.
@HYBRIDEMON
Thanks!

@GoldGanja
Yeah i will try tomorrow if i get some free time.
Wich Rom do you use ? I have at almost all roms overheating problems. After 10 min+ of 3d gaming i have ~55°c + (On my old phone Thl 5k i could play the same game hours, don´t get over 45 °c and no lagging or something - and yeah its not the best phone).
With your thermal config the device throttles later. So it will heat higher, until it shut down big core etc. As hotter it becomes as more difficult its to cooldown. Sure if you won´t reach 52°c would be perfect one. But maybe i will replace the values with lower, else it looks very good.

I can't find tao.log at sdcard.
Script is applied or not?
I copied to etc/init.d and set 755 permissions.
Edit:
Finally I applied manually and I have 2 errors with big cluster settings.
Enviado desde mi Mi-4c mediante Tapatalk

@dany94
I'm using last stable from xiaomi.eu (8.0.5). Anyway, if you get to know how the gears of the thermal engine works, do what is best for your usage. Feel free to change the numbers on my file if needed
siba01 said:
I can't find tao.log at sdcard.
Script is applied or not?
I copied to etc/init.d and set 755 permissions.
Edit:
Finally I applied manually and I have 2 errors with big cluster settings.
Enviado desde mi Mi-4c mediante Tapatalk
Click to expand...
Click to collapse
I think you are using a CM TS rom, right? well, for that you have to do two things.
First, set the battery mode to QUICK, because on BALANCE there is the hotplug of the BIG cores. Then re-run my script.
If that's not the case, maybe the device was just a bit hot, and the hotplug kicked in by the thermal-engine...let it cool down first or use my thermal-engine conf.
Second, rename my file to userinit.sh and place it under /data/local if you want the settings to be applied at each boot.

GoldGanja said:
Even if i make a zip file to use with twrp, this will only be useful for the thermal-engine conf file...because the other one is a script i've created and so there is no other file to replace. As stated ROOT is needed, i'm sorry.
Click to expand...
Click to collapse
Maybe I was not clear or, more likely I do not completely understand which is a fact for sure
Let me clear up the first part, then hopefully in the end I will also better understand
Your script chances several files if I understand correctly ? scaling_min_freq for example is the first one you change in the script ?
Could we not update all the files that you change using TWRP ?
My guess is, (that's just me trying to understand better.....) that I think that using TWRP it is possible to change these files without root, but in reality it is not because the phone is not rooted ? Maybe because only the complete system can be changed and not single files ? (without root)
I do know that in the end, for me it is possible to root my phone, apply the settings, and then unroot it again.... which hopefully have my phone working like it never was rooted... it's just a risk I would like to avoid if in any way possible, therefore I am investigating and trying to get it all clear for me, sorry for that

GoldGanja said:
@dany94
I'm using last stable from xiaomi.eu (8.0.5). Anyway, if you get to know how the gears of the thermal engine works, do what is best for your usage. Feel free to change the numbers on my file if needed
I think you are using a CM TS rom, right? well, for that you have to do two things.
First, set the battery mode to QUICK, because on BALANCE there is the hotplug of the BIG cores. Then re-run my script.
If that's not the case, maybe the device was just a bit hot, and the hotplug kicked in by the thermal-engine...let it cool down first or use my thermal-engine conf.
Second, rename my file to userinit.sh and place it under /data/local if you want the settings to be applied at each boot.
Click to expand...
Click to collapse
I'm using Resurrecction Remix.
Thanks for your answer.
Enviado desde mi Mi-4c mediante Tapatalk

I was pretty sure you will do such a good job for Mi4c! Well done!
Edit: btw big cluster values are not getting applied

solis_f said:
I was pretty sure you will do such a good job for Mi4c! Well done!
Edit: btw big cluster values are not getting applied
Click to expand...
Click to collapse
What ROM are you using?
Sent from my Mi-4c using Tapatalk

[KERNEL][GUIDE] Alcatel Ideal (4060A) Insecure Boot Image with Init.d Support

ALCATEL IDEAL 4060A
STOCK KERNEL WITH INIT.D. & INSECURE BOOT SUPPORT​
SPECIFICATIONS:
Model: Alcatel Ideal 4060A
Android Version: 5.1.1 Lollipop
Kernel Version: 3.10.49-g3d12fcb
GCC Version: 4.8
Build Date: Tuesday, July 26, 2016
Revisions Date: Saturday, August 5, 2017
Board Platform: Qualcomm Snapdragon 210 (MSM8909)
FEATURES:
CPU Governors: Interactive, OnDemand, Performance, Userspace, Powersave
Frequencies: 200MHz, 400MHz, 533MHz, 800MHz, 998MHz, 1094MHz
Minimum & Maximum Core Control
VDD Restriction & Temperature Throttle Control
GPU Frequencies: 200MHz, 307MHz, 409MHz
GPU Governors: bw_hwmon, bw_vbif, cpufreq, gpubw_mon, msm-adreno-tz,
 performance, powersave, simple_ondemand, spdm_bw_hyp, userspace
I/O Schedulers: cfq, deadline,row, noop
Adaptive Low Memory Killer: 5 Presets & Tunables
Z-RAM Support
Virtual Memory Tunables: Dirty Ratio, Dirty Background Ratio, Dirty Expire Centisecs, Dirty Writeback Centisecs, Overcommit Ratio, Swappiness, VFS Cache Pressure, Laptop Mode
SELinux Permissive/Enforcing Toggling
Entropy Read/Write Ahead Support
TCP Congestion Algorithms: cubic, reno
Hostname Editing
ADB Over WiFi Support
Android Logging Support
Init.d Script Support & Emulator
REQUIREMENTS:
In order to use init.d script support, and in order to be able to tune this kernel and use its features, you need to be running a ROM with root privileges. Also, while not absolutely required, it is recommended that you have TWRP custom recovery installed. This kernel can be installed by on-device flashing apps such as Rashr, Flashfire, etc. However, for this thread, I will be instructing on TWRP installation only. In order to utilize init.d support, you also need to install a recent version of BusyBox.
DISCLAIMER: You flash this kernel at your own risk. As always, rooting or flashing the partitions of your device comes with the inherent risk of rendering your device inoperable.
You hereby assume responsibility for your own device, and absolve me of any liability for any damage caused to your phone by flashing this kernel. Follow the simple instructions carefully and you should experience no adverse results.
NOTES: This is a stock kernel which has been modified to provide init.d and insecure boot support. The advantages of insecure boot support include having root access through adb shell -- it enables adbd to run as root. Init.d support gives you enormous flexibility in the ability to run scripts and mods to be run at boot -- everything from battery tweaks to performance mods. Aside from init.d, the Kernel Adiutor-Mod application, included in the download link below, allows you to tune several parameters of the kernel, change CPU/GPU governors, adjust I/O schedulers, set CPU/GPU frequency minimums & maximums, apply an adaptive low memory killer preset, etc. With some modding, you will notice a remarkable increase in responsiveness, stability and overall performance of the Android OS, as well as a tremendous increase in battery life. . Trial and error is key. Do some research on the best kernel mods and set your own preferences. You are the captain of your own ship...
THANKS & MENTIONS:
Thanks to @Grarak for developing the original Kernel Adiutor application. Thanks also to "Yoinx" for modifying the original application and thus creating Kernel Adiutor-Mod.
KERNEL SOURCE CODE: https://github.com/zombah/android_kernel_alcatel_msm8909
INSTRUCTIONS:
1. Assuming you have root, BusyBox & TWRP custom recovery installed on your device, boot into TWRP and flash the zip installer in the below download link;
2. Wipe the dalvik cache and reboot system;
3. Upon reboot, install the Kernel Adiutor-Mod application from the below download link.
Open the app, grant superuser access when prompted, and tap on the menu icon near the upper left of the screen;
4. Done.....use the options in the menu to tweak the kernel's settings, change CPU governors,
set CPU/GPU frequencies, toggle SELinux mode, etc., etc.
DOWNLOAD LINKS:
Kernel Installer: https://drive.google.com/file/d/0B1Sfod4HWfk2NjUzWGVldThtQ0U/view?usp=sharing
Kernel Adiutor-Mod APK: https://drive.google.com/file/d/0B1Sfod4HWfk2OC1ORURoN3hTeUE/view?usp=sharing

Been trying out KA mod for about a week, not using the cus kernal tho. Just happened to run into it after a search since when I tried Garak's official back awile it didn't seem to have any effect. Not sure but it may have been due to not (unrestricting) it in apps, or not enabling init.d emulation in it? In any case, using it to set SElinux permissive and trying to squeeze a little more battery life out. After not really knowing what I'm doing, I ended up staying with interactive and just making a few guesses from what I could find out in searches. I think battery life is a (little) better?
Interactive:
CPU minimum freq 400 MHz
tunables:
go_hispeed_load 95
target_loads 1 533000:85
800000:90
998400:90
1094400:80
If there are other/additional things to try, please let me know!

scohut said:
Been trying out KA mod for about a week, not using the cus kernal tho. Just happened to run into it after a search since when I tried Garak's official back awile it didn't seem to have any effect. Not sure but it may have been due to not (unrestricting) it in apps, or not enabling init.d emulation in it? In any case, using it to set SElinux permissive and trying to squeeze a little more battery life out. After not really knowing what I'm doing, I ended up staying with interactive and just making a few guesses from what I could find out in searches. I think battery life is a (little) better?
Interactive:
CPU minimum freq 400 MHz
tunables:
go_hispeed_load 95
target_loads 1 533000:85
800000:90
998400:90
1094400:80
If there are other/additional things to try, please let me know!
Click to expand...
Click to collapse
Set your Adaptive Low Memory Killer to Very Aggressive. This will restrict background apps from flooding your free RAM and save on battery life.
Are you not able to use init.d with this kernel?

MotoJunkie01 said:
Are you not able to use init.d with this kernel?
Click to expand...
Click to collapse
I have init.d emulated ticked on. Settings work, even on reboot. I'll try the memory settings.

scohut said:
I have init.d emulated ticked on. Settings work, even on reboot. I'll try the memory settings.
Click to expand...
Click to collapse
Good to hear

MotoJunkie01 said:
Set your Adaptive Low Memory Killer to Very Aggressive. This will restrict background apps from flooding your free RAM and save on battery life.
Click to expand...
Click to collapse
This DOES seem to be helping also..

scohut said:
This DOES seem to be helping also..
Click to expand...
Click to collapse
It does me too. With a free RAM widget running, I notice about 325Mb+ free RAM most times with 24 user apps installed.

With only a 1750 MAh battery we need all the help we can get

scohut said:
With only a 1750 MAh battery we need all the help we can get
Click to expand...
Click to collapse
Amen there

Snapdragon 820 Power Consumption In Watts

I found a hidden XML called power_profile.xml in the root directory. I found about about its existence after reading this page from Google that explained a requirement for device manufacturers to include information in the OS about the power consumption of every component in the phone. (Source: https://source.android.com/devices/tech/power/values).
After extracting a hidden APK in the root directory, I found this XML file detailing the power consumption of nearly every component in the LG V20, in addition to the power consumption of each CPU core at every possible frequency. (https://drive.google.com/file/d/0B64FbyJyGsUFNUdLbHZvZUJ2QWc/view?usp=sharing). Most of the file is indecipherable, but the important parts are written in English.
I used the data to create this spreadsheet to find the most power efficient frequency to run my rooted phone at. (https://docs.google.com/spreadsheets/d/1by5DiFxtnFS4nbUp7717mgM2TbFQT76lWDsbYGzrphQ/edit?usp=sharing). I set my CPU to 2.1GHz for the big cores and 1.5GHz for the small cores because the highest frequencies seem to use an excessive amount of power.
Comment if you have any questions or suggestions.

bobbyqba2011 said:
I found a hidden XML called power_profile.xml in the root directory. I found about about its existence after reading this page from Google that explained a requirement for device manufacturers to include information in the OS about the power consumption of every component in the phone. (Source: https://source.android.com/devices/tech/power/values).
After extracting a hidden APK in the root directory, I found this XML file detailing the power consumption of nearly every component in the LG V20, in addition to the power consumption of each CPU core at every possible frequency. (https://drive.google.com/file/d/0B64FbyJyGsUFNUdLbHZvZUJ2QWc/view?usp=sharing). Most of the file is indecipherable, but the important parts are written in English.
I used the data to create this spreadsheet to find the most power efficient frequency to run my rooted phone at. (https://docs.google.com/spreadsheet...717mgM2TbFQT76lWDsbYGzrphQ/edit?usp=sharing). I set my CPU to 2.1GHz for the big cores and 1.5GHz for the small cores because the highest frequencies seem to use an excessive amount of power.
Comment if you have any questions or suggestions.
Click to expand...
Click to collapse
which variant of the V20 do you have? how did you go about setting the big and small cores and does changing them require a reboot? do you notice any performance differences from your seeing and the default?

dimm0k said:
which variant of the V20 do you have? how did you go about setting the big and small cores and does changing them require a reboot? do you notice any performance differences from your seeing and the default?
Click to expand...
Click to collapse
I have an H918 from T-Mobile running Nougat 7.0 10d. You have to root your phone to change the cpu frequency. After that, it's really easy and there are no reboots required. I use an app called Kernel Adiutor, but there are others. I haven't tested this specific configuration yet, but there's usually a linear correlation between frequency and Geekbench scores. So the performance is worse at 2.1/1.5GHz, but it's not really noticeable.

There are more factors responsible for battery comsumption than just your cpu, screen is the biggest battery eater. Then services, gpu, etc
Adjust your cpu speeds from 2500 to 2100 wont give much battery boost tbh only by marginal results
Not worth the performance decline if you ask me
Try using different gouvernors / other i/o schedulers like ZEN

[Tweaks][su.d][build.prop] Thermal Throttling solution and more

Hi Snapdragon S7 users!
As we know we have a locked bootloader, and rooting includes heavy thermal throttling and strange frequency managment done by the system automatically (try to change max/min freq and you will se how it resists). Also to suffer a slower system (apps take longer to open/multitask), And a higher battery consumption (kernel organises processes strangely and big cpu is always under moderate-high load)
i have been searching all over xda (and many other forums) to get to the solution. And this is how far i could get:
Warning
Use this at your own risk!
su.d scripts will break safety net​
Thanks to:
@xFirefly93 and his [MOD] Pixel (XL) Unified Kernel(s) Tuning Script (v1.3)
@Zola III
@TheDevelopper
@Craz Basics
Xperia XZ forum
OnePlus 3/3T forums
Pixel XL forum
su.d/init.d
Thermal throttling solution
Block max/min auto frequency: Samsung Custom Frequency Manager, i call it "The Slippery" (gekkehenkie11 explanation here) is "samsungs personal assistant" when it comes to cpu frequency, changing it according to samsung preferences. We don't have sourcecode of it, so we cant modify it. But we can override it so it doesn't modify our settings (we do it with permissions this way) so then you can choose the range of frequencies you prefer with any cpu manager like kernel adiutor (kernel's thermal throttling will still continue working) re-activated in v8 (see changelog for more info)
"Disable" throttling (push it further) = snappier device specially during heavy tasks (tested very heavily and couldnt pass 82C (180F) battery never reached 42C (108F)) you may have different temps due to Sillicon lottery or heavy gaming modified in v8 (see changelog for more info)
We have 3 options to manage temperature: Core Control (turns off cores), VDD Restriction (increases voltage when cpu is really cold) explanation HERE and HERE and Throttling (decreases cpu max freq)
How to check
A log file with the name "90Thermal_solution.log" will be created at /data
Click to expand...
Click to collapse
CPU Solution
If you take a look you will realise big cpu utilization percent is always high, and that leads to higher frequencies used and sustained for more time = higher battery consumption and cpu temps
I've tried to mitigate that by changing interactive cpu governor tunables and after setting tunables i got to a point where big cpu doesn't ramp up so often when nothing is being done (there is always something going on in background but that cpu usage and frequencies when doing "nothing" can't be justified in my opinion (i blame eng kernel for this)
Change gpu governor to cpufreq (i didnt notice any increment in battery consumption whereas the smoothness has increased for good) and set freqs to 214-624mhz (133 caused scrolling lags sometimes. You can change it if you want -> kernel adiutor)
Useful sites:
Advanced Interactive Governor Tweaks by SoniCron - Angler thread
[Guide] Advanced Interactive Governor Tweaks
GoogleSource documentation about governors
Interactive – why is this the best governor? [INFO]
[*] [URL="https://source.android.com/devices/tech/perf/boot-times"]Optimizing Boot Times | Andorid Open Source Project[/URL]
How to check
A log file with the name "91Cpu_solution.log" will be created at /data
Click to expand...
Click to collapse
DAC Solution
Enable class AB config for hph (good explanation of what it does HERE), In simply words:
Prioritize quality over battery consumption (especially when not at max volume)
High performance only works with headphones (or anything you connect using 3,5mm jack)
How to check
A log file with the name "92Dac_solution.log" will be created at /data
Click to expand...
Click to collapse
More Solutions
First of all, the links:
How GPU governor impacts user experience
GPU causing jitter in essential phone
GPU causing jitter in essential phone 2
Sysctl documentation
Extra free kbytes explanation
Extra free kbytes explanation 2
Difference between vm.dirty_ratio and vm.dirty_background_ratio
VM tunning
More VM explanations
Entropy explanation by zeppelinrox
Overcommit ratio is a myth
How overcommit works
good scheduler explanation by kgs1992
cfq, noop, deadline comparison
Improving the Real-Time Properties
What this does:
Adjust some VM things
We will allow dirty data to stay on ram for a while (i cant belive why this was "off" originally -> eng kernel (maybe))
We will ajdust min and extra freekbytes to stock user-kernel value
Adjust lmk values
Increase read ahead and disable io stats (technically this should free some cpu) + change scheduler to deadline
Disable some logs (less 'disk' use) and other useless things
Modify entropy rngd tunables and link random to urandom
How to check
A log file with the name "94More_Solutions.log" will be created at /data
Click to expand...
Click to collapse
Installation
All has been tested in S7 Edge 935V with CRG2 Stock_Oreo_Hybrid by Jrkruse Rooted with Root For S7/S7Edge Oreo And Nougat by Jrkrusewith interactive governor option without issues (no bootloop)
0 ) You must be rooted
1 ) Make sure you have lastest busybox installed Google Play link
2 ) Download the Files (attached)
3 ) Extract .zip or .rar (they have the same files)
4 ) Copy tweak files (.sh ones) you want to apply to
Code:
/system/su.d
or
Code:
/system/etc/init.d
or use any init.d emulator (i dont guarantee it wil work) [MOD][APK+SCRIPT+ZIP] Enable Init.d for Any Phones w/o Need of Custom Kernels!!!
5 ) Set 777 permission (rwx-rwx-rwx)
6 ) Reboot
Click to expand...
Click to collapse
Click to expand...
Click to collapse
build.prop
Dalvik solution
I'll keep this simple
Most important pages:
Configuring ART
Optimize android rutime
GoogleSource: Configuring ART
Eng builds different things
More eng builds different things, and stock values
Google Pixel default values
[MODULE][SYSTEM/LESS] ART Optimization v2.0 [DISCONTINUED]
Conclusions:
Our eng kernel has different values for certain dalvik things which ruins the "smooth android experience" (eng kernels are not meant for normal use). Hopefully most of them can be changed (fixed) into normal/stock values
The whole dalvik cache creation is really complex (and i barely know chunks of it), but to summarise It uses profiles which are a versus of "space utilization vs performance" more speed = less space available and vice versa (there are exceptions of course)
After testing with an exynos s7 besides my snapdragon i saw that exynos dalvik-cache folder was like 1gb big in stock conditions (and the phone was basically factory resetted), whereas snapdragon's folder was 300mb or so (with more than 100 aps installed). After applying the tweaks to exynos variant, dalvik folder went to like 1,2gb. After restoring ~100 apps on exynos dalvik is 1,8gb
Applying this tweaks could lead to (after dalvik-cache gets completely rebuilt):
Apps opening faster (they have more "parts" optimized)
Less cpu cycles used (apps have more "parts" optimized, so no need to waste cpu on doing that every cold launch)
Less battery consumption (above reasons)
Less internal space available (Dalvik cache will get bigger)
Longer first boot (A LOT LONGER) only first after deleting dalvik. Then it will be almost like before applying patch until dalvik gets completely rebuilt.
Some battery consumption increase until dalvik gets completely rebuilt (it's built while phone is booting, idle or charging)
After applying this tweak and deleting dalvik cache next boot will take A LOT LONGER. It's not a bootloop, i can ensure you, just wait. (like 20min)
How to install
Since values were not applying using setprop, i think it's better to add the values inside the build.prop (if someone has a better idea please tell me)
Make build.prop backup
Add values to build.prop
Leave one blank line at the end, like this:
battery.capcacity=3600
improve.performance=true
Last.buildprop.line=1
'empty space'
Click to expand...
Click to collapse
Delete dalvik-cache
Delete what is inside /data/dalvik-cache/
or
wipe dalvik-cache through Flashfire
Reboot (and go make a sandwich as it will take some time)
Click to expand...
Click to collapse
Dalvik takes time to rebuild, so wait some time (a couple of hours of device idle, charging if possible). I suggest you to do this at night some time before going to sleep: follow installation steps, check dalvik folder size and go to sleep (you can take screenshots to keep trace). at the next day check again if it has gain some size, reboot the phone, and use it normally. That night check again dalvik size. As soon as you see it stopped growing you can "document" your feelings with the configuration
Values
pm.dexopt.boot=verify
pm.dexopt.first-boot=quicken
pm.dexopt.bg-dexopt=speed
dalvik.vm.image-dex2oat-filter=speed
dalvik.vm.dex2oat-filter=speed
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.dex2oat-flags=--compiler-filter=speed
dalvik.vm.dex2oat-flags=--compiler-backend=optimizing
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Extra build.prop tweaks
Here are some more build.prop values i found and im using right now. You can add them under dalvik solution ones if you like
boot.fps=30
shutdown.fps=30
ro.secure=1
ro.debuggable=0
persist.sys.scrollingcache=4
sys.config.samp_spcm_enable=false
sys.config.samp_enable=false
ro.config.fha_enable=true
ro.sys.fw.use_trim_settings=false
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Extra
Rendering Solution
We know gpu is better than cpu at graphic rendering
In the old times a file named egl.cfg existed at lib/gles | lib/egl. That file contained the name of the libraries which would be used to render the screen (Phone and external). Some users modified the file in order to force gpu rendering always. This basically made phones smoother (info HERE)
Many people claimed that using gpu rendering only would increase battery consumption, whereas others said the opposite
We dont have egl.cfg, so i investigated and it results that since oreo the EGL loader doesn't need a config file to "know" which libraries to load, it detects the libraries and loads them automatically. So deleting (or renaming) libGLES_android.so makes the EGL loader unable to detect software rendering libraries and stick with only hardware ones, thus disabling cpu rendering List of commits
As far as i've tested, disabling cpu rendering made the device perform smoother (easily noticeable, specially just after a reboot). I didn't notice any big difference with battery (it may be lasting a little longer though)
How to
Rename (or delete) "libGLES_android.so" to "libGLES_android.bak" and set 444 permissions. . The file is at /system/lib/egl and /system/lib64/egl
Reboot
Click to expand...
Click to collapse
Apps Solution
Unlike the rest of solutions, this is not a script. Here i will tell you two group of apps i disabled, and made a LOT of difference in terms of snappiness
Short tuto:
1 ) in titanium backup search for 'qualcomm' with system/defrosted filter
2 ) freeze all
3 ) do the same but searching 'knox'
4 ) delete frozen apps data
5 ) reboot
Long tuto:
1 ) Download Titanium backup
2 ) open and go to 'backup/restore' tab
3 ) 'click to edit filters' and select type 'system', temperature 'defrosted'. the rest in 'all'
4 ) apply filter
5 ) click the magnifying glass and type 'qualcomm'
6 ) tap the paper with a tick
7 ) go to 'freeze/defrost' and tap 'run' in the first option "freeze all user & system...."
8 ) select all and tap the tick
9 ) repeat from step 5 but instead of qualcomm type 'knox'
10 ) go to 'backup/restore' tab
11 ) 'click to edit filters' and select type 'system', temperature 'frozen'. the rest in 'all'
12 ) tap the paper with a tick
13 ) go to 'manipulate data' and tap 'run' in the second option "wipe data for user & system apps"
14 ) select all and tap the tick
15 ) reboot
I will leave you also attached some screenshots of the apps i have frozen, so you can be sure they don't cause bootloops in case you wonder that. If you froze/disable something and suddenly something stops working (for example: bluetooth doesnt turn on) just defrost/enable it again and you should be fine
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Solution Installer
This is just 2 .bat installer, which will install
EngSolution.bat
Thermal Throtlling Solution
Cpu Solution
Dac Solution
More Solutions
Rendering Solution
A modified sysconfig to allow google play services and playstore be optimized by doze
AppSolution.bat
Will delete lots of apps i consider bloat
This is done using a pc
1 ) Unzip/decompress
2 ) Run .bat you want
3 ) Device will reboot once completed
Click to expand...
Click to collapse
If you want to Uninstall
1 ) Delete the files you copied and reboot
2 ) If you used dalvik solution, restore build.prop backup and wipe dalvik cache (delete the files inside /data/dalvik-cache/) --> Next boot will take more time after this (only the next one after deleting)
3 ) If you used Rendering solution, restore stock name and set permission to 777
4 ) If you used Apps solution, defrost all the apps you froze
Click to expand...
Click to collapse
Changelog
V2
V3
V4
V5
V6
V7
V8
V9
Click to expand...
Click to collapse

Has anyone tried this and noticed any improvement? What about heat issues?

Archangel said:
Has anyone tried this and noticed any improvement? What about heat issues?
Click to expand...
Click to collapse
I have! I have noticed my device is much more snappy and I do notice an improvement in audio. I have a s7 edge and it is running cool.

I ran it for a day or so and it seemed to make mine run hotter,,,I will try it again and see
C64assembly said:
I have! I have noticed my device is much more snappy and I do notice an improvement in audio. I have a s7 edge and it is running cool.
Click to expand...
Click to collapse

Archangel said:
I ran it for a day or so and it seemed to make mine run hotter,,,I will try it again and see
Click to expand...
Click to collapse
It will run hotter. Anyways i couldn't make cpu surpass 82C/180F, and i think it's really worth the benefit. I think samsung's eng kernel throttling wasn't totally polished, because some degrees ahead device stops getting hotter (unless during a heavy task), apps opening/switching becomes noticeably faster and scrolling lag decreases
I need to do some more research about how thermal throttling kicks in (eng kernel is weird) because i have plans and new ideas for an update but im not having my phone in hands until next week. Im thinking of wether release all at once or make it in 2 or 3 simpler updates

Reorganized post, added dalvik tweaks, redone all the scripts.
I suggest anyone who is using this uninstall and install new versions

I do not know if you're aware but Im pretty sure installing these and rebooting breaks safetynet! I had signed out of snapchat a day after installing these and tried to sign back in and i got the dialog you get if you are rooted and snap detects safetynet is broken, I then went an uninstalled the files from the su.d, rebooted and i was able to log in again, might want to add to OP !

gwilly3301 said:
I do not know if you're aware but Im pretty sure installing these and rebooting breaks safetynet! I had signed out of snapchat a day after installing these and tried to sign back in and i got the dialog you get if you are rooted and snap detects safetynet is broken, I then went an uninstalled the files from the su.d, rebooted and i was able to log in again, might want to add to OP !
Click to expand...
Click to collapse
oh, thank you. Since don't use snapchat, and none app has given me problems, i didn't realise it. added to op :good:
Are build.prop lines working for you without breaking safety net?

Maxissc said:
oh, thank you. Since don't use snapchat, and none app has given me problems, i didn't realise it. added to op :good:
Are build.prop lines working for you without breaking safety net?
Click to expand...
Click to collapse
Build.prop lines should be fine, they won't break safetynet. As that's what apps like L-Speed modify are lines in the build.prop and it doesn't cause any problems

Maxissc said:
Hi S7 users!
As we know we have a locked bootloader, and rooting includes heavy thermal throttling and strange frequency managment done by the system automatically (try to change max/min freq and you will se how it resists). Also to suffer a slower system (apps take longer to open/multitask), And a higher battery consumption (kernel organises processes strangely and big cpu is always under moderate-high load)
i have been searching all over xda (and many other forums) to get to the solution. And this is how far i could get:
Warning
Use this at your own risk!
su.d scripts will break safety net​
Thermal throttling solution
CPU Solution Not finished, only touchboost tweaks for now
DAC's high performance mode
Installation
Dalvik solution
If you want to Uninstall
Click to expand...
Click to collapse
Have you had anymore development on these? Running these along with my flashing stock BL tweak has been very helpful

gwilly3301 said:
Have you had anymore development on these? Running these along with my flashing stock BL tweak has been very helpful
Click to expand...
Click to collapse
Yes, im currently testing 2 configs to decide which is better. Then i'll finish with cpu governor tunables and update op

Maxissc said:
Yes, im currently testing 2 configs to decide which is better. Then i'll finish with cpu governor tunables and update op
Click to expand...
Click to collapse
Awesome, thanks for the update! Don't mean to nag

UPDATE V2​
Reworked Thermal solution
Added cpu tunables tweaks (at Cpu Solution)
Deleted some build.prop lines (also there aren't test values any more)

Maxissc said:
UPDATE V2​
Reworked Thermal solution
Added cpu tunables tweaks (at Cpu Solution)
Deleted some build.prop lines (also there aren't test values any more)
Click to expand...
Click to collapse
Awesome, trying now! Will let you know how it runs!
---------- Post added at 11:39 PM ---------- Previous post was at 11:15 PM ----------
Maxissc said:
Hi S7 users!
As we know we have a locked bootloader, and rooting includes heavy thermal throttling and strange frequency managment done by the system automatically (try to change max/min freq and you will se how it resists). Also to suffer a slower system (apps take longer to open/multitask), And a higher battery consumption (kernel organises processes strangely and big cpu is always under moderate-high load)
i have been searching all over xda (and many other forums) to get to the solution. And this is how far i could get:
Warning
Use this at your own risk!
su.d scripts will break safety net​
Thermal throttling solution
CPU Solution
DAC's high performance mode
Installation
Dalvik solution
If you want to Uninstall
Click to expand...
Click to collapse
Does Dalvik Solution.txt go into /su.d as well?

gwilly3301 said:
Awesome, trying now! Will let you know how it runs!
---------- Post added at 11:39 PM ---------- Previous post was at 11:15 PM ----------
Does Dalvik Solution.txt go into /su.d as well?
Click to expand...
Click to collapse
no, i'ts just a txt you can use to copy build.prop tweaks more easily.
about the .sh tell me if you have the logs at /data because i wasn't having them (neither the scripts running) until i deleted and pressed enter at every line of the files (i dont understand why that fixed the issue)

UPDATE V3​
Reupdated V2 with scripts working correctly now

Maxissc said:
no, i'ts just a txt you can use to copy build.prop tweaks more easily.
about the .sh tell me if you have the logs at /data because i wasn't having them (neither the scripts running) until i deleted and pressed enter at every line of the files (i dont understand why that fixed the issue)
Click to expand...
Click to collapse
No, no logs. Does that mean scripts aren't running then?

gwilly3301 said:
No, no logs. Does that mean scripts aren't running then?
Click to expand...
Click to collapse
yes. please try with v3 i just uploaded. im sure they are working fine now

Maxissc said:
UPDATE V3​
Reupdated V2 with scripts working correctly now
Click to expand...
Click to collapse
Should I re-download? Also with the, .txt file, I need to copy what's in there to my build.prop or do the scripts already do that?
---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------
Maxissc said:
yes. please try with v3 i just uploaded. im sure they are working fine now
Click to expand...
Click to collapse
Do I need to clear dalvik again?

gwilly3301 said:
Should I re-download? Also with the, .txt file, I need to copy what's in there to my build.prop or do the scripts already do that?
---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------
Do I need to clear dalvik again?
Click to expand...
Click to collapse
redownload, delete previous files (from v2) at su.d, and copy new ones and give them 777 permission (all rwx). add .txt lines at the end of build.prop (remember to leave a blank line at the end), delete dalvik cache and reboot. it will take a while to boot after deleting dalvik (5-10min or so)