Nice work mate. Great to finally see a thread with your base settings. These really helped when I started out with UV/OC. So here's a BIG thanks!!!
Anyone bringing negativity in to this thread should seriously get their head examined, considering geko is probably one of the most helpful guys on these forums. I've seen him answer questions from n00bs (some seriously dumb questions too) over and over, without ever being rude or losing his patience. That ain't easy.
Criskelo ROM | Siyah Kernel | Custom OC/UV | Audio Tweaked
Most of my testing so far has indicated that enabling 100 MHz could actually reduce your battery life a bit, because the CPU spends more time active and less time in deeper idle states like AFTR or LPA.
Because there is little to no voltage difference between 100 and 200, and leakage current dominates at this frequency, it's better to hit AFTR or LPA idle than to clock down.
In short - disable 100 MHz and you get free "Wheatley".
I agree your assessment on the 100Mhz not saving much or any at all. I started disabling it 3 weeks ago.
AT&T Samsung Galaxy Note II(i317)
Previous devices: Samsung Galaxy S II & III Retired devices: AT&T Samsung Galaxy Note / Moto Atrix and SGS Captivate / HTC Leo(HD2) / AT&T Tilt 2/ HTC Fuze / HTC Advantage / I-Mate JasJam / JasJar / Pocket PC / XDA SAMSUNG CAPTIVATE AND T-MOBILE HD2 FOR SALE, PM ME IF YOUR ARE INTERESTED.
Most of my testing so far has indicated that enabling 100 MHz could actually reduce your battery life a bit, because the CPU spends more time active and less time in deeper idle states like AFTR or LPA.
Because there is little to no voltage difference between 100 and 200, and leakage current dominates at this frequency, it's better to hit AFTR or LPA idle than to clock down.
In short - disable 100 MHz and you get free "Wheatley".
Yes, i have the same opinion.
Second graph in this thread by Ezekeel, shows the difference between lower and higher frequency steps' battery consumption with and without LPA/deep idle. As it occurs, higher frequency supports race-to-idle better there
Again, "100 mhz bad compared to 200 mhz" depends on we're using lpa or not. (sched_mc=2 or 3).
Anyhow, since only first core can hit lpa, screen-off profiles with: different governor, hard limiting frequency, switching to single core mode, etc actually does a little harm than good by delaying for race-to-idle.
Yes, i have the same opinion.
Second graph in this thread by Ezekeel, shows the difference between lower and higher frequency steps' battery consumption with and without LPA/deep idle. As it occurs, higher frequency supports race-to-idle better there
Again, "100 mhz bad compared to 200 mhz" depends on we're using lpa or not. (sched_mc=2 or 3).
Anyhow, since only first core can hit lpa, screen-off profiles with: different governor, hard limiting frequency, switching to single core mode, etc actually does a little harm than good by delaying for race-to-idle.
I lil noob question..so above posts only shows that 100mhz will consume more battery? Hmmm..right now im running 100-1000mhz..is it better to use 200-1000mhz instead?
I lil noob question..so above posts only shows that 100mhz will consume more battery? Hmmm..right now im running 100-1000mhz..is it better to use 200-1000mhz instead?
Sent from my GT-I9100 using xda premium
I'd have to agree with Entropy and droidphile mate, in my experience having it set 100Mhz doesn't really provide any noticeable battery life gains. I just haven't taken a look at any info proving this point before.
It's definitely making sense though, since the CPU doesn't have to go to 200Mhz as the next frequency when it scales up. It can go straight to 500Mhz (of course dependant on the governor you're using).
I guess its that illusion, having a lower number = better results.
Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Enterprise.
I'd have to agree with Entropy and droidphile mate, in my experience having it set 100Mhz doesn't really provide any noticeable battery life gains. I just haven't taken a look at any info proving this point before.
It's definitely making sense though, since the CPU doesn't have to go to 200Mhz as the next frequency when it scales up. It can go straight to 500Mhz (of course dependant on the governor you're using).
I guess its that illusion, having a lower number = better results.
Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Enterprise.
So should i go along with 200mhz as the lowest step and 1000mhz as the highest mate?
There are still quite a few of folks who run Gingerbread on their … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?