[Sprint Samsung Galaxy S III] mw86:
Re: [Team Kernelizers] {how to} Ktoonsnative governor and I/O tweaks

Hold off waiting on update from Idcrisis. Yeah i suspected, kernel no frandom it installs easy and runs good right away. With frandom in play it took more steps to get set up and working as to get the scripts involved working i had to reboot and fix permissions more than once.

---------- Post added at 04:51 PM ---------- Previous post was at 04:48 PM ----------

Like Castle Bravo is saying here plus in rescan media root you are supposed to hit disable and exit and reboot on first run then if your phone is idle and you still habe media scanner rampant you enter media scanner root and hit disable media scanner it stops immediately. I got a few links could help with media issues.

---------- Post added at 04:55 PM ---------- Previous post was at 04:51 PM ----------

Note to our users

If samsung device manager is uninstalled to stop wake lock rename both sdm.Exe files unless its removed and this is touchwiz only, no need to modify them.

Qosmgr and gsiffdaemon are necessary to rename as i have had them run rampant and random times on any touchwiz rom ive tried this far.

Mpdecision i have left as is since ktoonsez suggestion and had no issues at all with it on. So if on touch wiz some of the above is necessary if on aosp above 4.1.1 no need to change anything.

---------- Post added at 05:08 PM ---------- Previous post was at 04:55 PM ----------

Lag i have a few suggestions.

You didn't show up threshold so i suggest lowering your up threshold and up threshold hotplug a little, it will be more responsive.

Raise you sample rate to 25k to see if it helps jittery behavior more.

Your row tunings, try using noop until you solved battery drain all over. Then go back to row and start adjusting so you know if row tuning s are causing stuttering and added battery drain. After that you should be able to get row to be less battery consuming.

Thank you for your kind words :)

Media apps may help reign in media issue.

Free:

Duplicate song deleter

https://play.google.com/store/apps/details?id=com.promethyl.duplicate.song.deleter

Force media scan

https://play.google.com/store/apps/details?id=com.promethyl.force.media.scanner

(you can always run media scanner plugged in till it finishes and then go about using phone, since media scanner is a database tool when all media is datatbased media scanner stops running and scanning. I believe the bigger drain from media scanner is the sd card usage that occurs)

Media dumper Audio (list all media audio files, helps locate possible rogue media unknown to user)

https://play.google.com/store/apps/details?id=com.promethylhosting.mediadumper

If these are determined to be useful i could add them to the second post!?

---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------

Posted this in Ktweaker discussion thread that Iilitz started, after reading a post of Lilitz.

Using your suggested sample rate and having good results. I had been extremely low on sample rate and started to experiment a lot and found though a low sample rate can drop back to idle faster its less accurate when load rises very quickly and causes cpu mhz to reach near max more than necessary because the time spent calculating was too long and keeps raising mhz instead of waiting a little before deciding to rise again. So the 70k seems better ive been all over low to high. Im using 75k and it seems to be awesome. Thank you for the suggestion. I use my thresholds a bit higher than you but am using similar tunabkes in Ktoonservative. Cheers thanks. I think this may stabalize undervolt better, as i drop a lot of mv its wasn't stable as i would prefer, having much better luck on 75k as i think the biggest benefit is slower cpu speed switching so voltage is applied and doesn't flip up and down too fast causing instability. My upper frequencies i can match to yours similarly but like Baconator my phone similarly doesnt stand for low mv on low mhz. 700mV ranges seem to always be untouchable for mine.

For a long time i used 2106mhz, now looking at the stock volt table i notice a nice volt range for the given mhz. 1026mhz i am using now as a max and overall it hasn't slowed me down as much as one may think.

I get more drain when battery and cpu temps rise, much lower max seems to help keep from going well over 100F often.