[Q] SetCPU and S3 - Galaxy S III Q&A, Help & Troubleshooting

Hi everyone,
This is the first time owning a Samsung device, so the pegasusq governor is a new thing to me, I read about what it actually is on a thread but I wanted to ask to fellow S3 owners what are they using for great battery life - performance ratio?
I'm running Omega 6.0, slipstreamed loads of crap that is not needed (from the "safe to remove" thread) with Apex Launcher. I'm only using 2 homescreens, dark wallpaper, etc, the typical works to try and improve battery life.
Now the thing is, with SetCPU I'm running the default pegasusq governor ranging from 200mhz -1400mhz. Is the pegasusq governor the right choice here? Isn't it basically a variant of the OnDemand governor but Samsung proprietary for quadcore CPUs? I also recall reading a mention of S3's freezing or not waking up when it's set from the lowest underclocking point (200mhz), is that right? I've been using this for a few hours and no problems yet, but just wanted to know what are everyone elses experiences and what's the best configuration that has worked individually for you!
Cheers! Hope I complied with the rules, I did do a search but didn't find anything of this nature apart from a few separate questions!

---

I use the same governor, 100Mhz - 1704Mhz. No issues. Works great.

---

Siyah kernel is using pegasusq so i think it is the best governer there is. if you're on stock kernel or lowest underclocking is 200mhz but in custom kernels you can use 100mhz.
I have set my SetCPU to 100mhz - 1200mhz and undervolting all 18-steps to -50mv. I seldom reboot my phone but not encounter any freeze on boot

---

You should try tweaks for improving the battery life and peformance. Like supercharger, zipalling , random build.prop tweaks.... Etc xD but yeah use the samsungs "for quad core"

---

Thank you for the prompt replies everyone!
I remember with my Desire the whole development community was pretty much "set in stone" if you will, so it was really easy to choose a kernel etc.
Is there a kernel that you recommend? Is anyone using a "Screen Off" profile without any problems? If so what's the range you have it set at? That's what I was mostly scared as I remember on my Desire the lockscreen or taking calls would lag quite a bit but obviously this is a different beast altogether!
I'm also using AutoKiller Memory with Extreme Settings and some tweaks applied as well.

---

I use Siyah clocked 100-1704 screen on. 100-300 screen off. No issues.

---

Sptz said:
Is there a kernel that you recommend? Is anyone using a "Screen Off" profile without any problems? If so what's the range you have it set at? That's what I was mostly scared as I remember on my Desire the lockscreen or taking calls would lag quite a bit but obviously this is a different beast altogether!
Click to expand...
Click to collapse
I set mine to 100-600 not having any issues, when reiveng notification/phone calls doesn't lag at all. Just don't use "power saving" option.
Sptz said:
I'm also using AutoKiller Memory with Extreme Settings and some tweaks applied as well.
Click to expand...
Click to collapse
3rd party apps don't to any good to battery life it only consumes more(for me) cause it's always running in your background which consumes memory and also battery life.
stock task manager is pretty good, been use it always. Closing all apps and clearing memory

---

bordikun said:
I set mine to 100-600 not having any issues, when reiveng notification/phone calls doesn't lag at all. Just don't use "power saving" option.
3rd party apps don't to any good to battery life it only consumes more(for me) cause it's always running in your background which consumes memory and also battery life.
stock task manager is pretty good, been use it always. Closing all apps and clearing memory
Click to expand...
Click to collapse
Nah, Autokiller isnt a task manager.
Basically, Android automatically kills empty processes (etc) at specified RAM levels. It does this anyway. But on High end RAM packed devices, these values are too low to be of any use as the phone will seldom hit that low a level of free RAM.
Autokiller simply adjusts these values to be more useful for high end devices.
Actually, you don't need autokiller to do this. You can do it in an init.d script although I've not tested this on the SGS3 as I haven't seen a need.
Here is an example I wrote for my Desire AOSP ROM:
Code:
#!/system/bin/sh
echo "8192,16384,19200,23040,25600,30720" > /sys/module/lowmemorykiller/parameters/minfree
Default SGS3 is:
Code:
8192, 10240, 12288, 14336, 16387, 25600
These are for:
Foreground App, Visible App, Secondary Server, Hidden App, Content Provider, Empty App