v5.2 is up
I finally had a chance tonight to create one zip to rule them all. No more maintaining four different versions. The new zip contains a script that runs when you flash it the first time to determine what needs to be enabled and makes the necessary changes regardless of which ROM you're on.
More details on the mods
What to expect - hopefully faster, more stable, and longer lasting DX/D2.
How to check if the mods are in effect: 1) Launch Terminal Emulator, 2) Type "sh /data/imoseyon/checkimosey.sh", without the quotes and hit enter.
(Keep in mind that this is a work in progress and your mileage WILL vary.)
- tweaked minfree to be less aggressive for foreground app and background services
- does a nightly check to see if it's enabled at boot and fixes it if the boot startup is clobbered by another app.
- new script - run "sh /data/imoseyon/checkimosey.sh" anytime to see if all the tweaks are in effect.
- v5.11: fixed a bug where if you didn't already have busybox installed my tweaks probably didn't stick at boot (for 3.4.2 users).
- v5.1: updated to work on 3.4.2. (only 3.4.2 users need to flash)
- v5.0: universal version for all ROMs. Created two separate zips for governor types. (upgrade from 4.3 is only necessary if you want to go back to ondemand governor).
Here are the differences between the two governors (taken from the Cyanogen docs):
The CPUfreq governor "interactive" is designed for low latency,What's my verdict? It's hard to say. Interactive governor does feel a bit snappier but theoretically it should consume a bit more battery. And I had a random reboot for the first time in months, after enabling interactive governor.... I'll post my opinion after using it for a week or so.
interactive workloads. This governor sets the CPU speed depending on
usage, similar to "ondemand" and "conservative" governors. However
there is no polling, or 'sample_rate' required to scale the CPU up.
Sampling CPU load every X ms can lead to under powering the CPU
for X ms, leading to dropped framerate, stuttering UI etc..
Scaling the CPU up is done when coming out of idle, and like "ondemand"
scaling up will always go to MAX, then step down based off of cpu load.