Disclaimer; This does not damage your phone at all or fry/mess up your cpu. On the contrary, it helps it by not running at full capacity all the time resulting in less stress and increased battery.
This method works universally for any Android phone you're using. But you'll need ROOT for Set CPU.
IMPORTANT: The newer versions of SetCPU might prevent your phone from entering deep sleep. Download version 2.24 from the following link which is the one with no problems and completely works 100%.
http://forum.xda-developers.com/showthread.php?t=505419
The Ace sucks in battery life. We all know that. And on 3G? Don't even mention it. But here's a fix, ever tried Under clocking instead of Over clocking?
Someone brought it up on a thread a couple of days ago and I have to spread the word, that works wonders. Got my Ace running on 245 min and 806 max and a different Screen Off profile. And now from the morning till 6PM in the afternoon, its just 61% AND recorded a 7 minute video/took pictures.
Battery was the only issue I had with my Ace. But now that its fixed, I love it
When screen is on:
MAX 806
MIN 245
Ondemand governor (This governor bumps up to max when needed but spends most time on the min freq. Best battery saver.)
When screen is off:
MAX 320
MIN 122
This way, you have a beast quick phone when you're using it, and the best battery saver when you're not!
This is what CPU spy should look like when you're done:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTE: Turn off Autosync from the settings. It's only used to sync your gmail and contacts and such. You can manually sync when you add a new contact and since I don't use gmail, I refresh manually whenever I do. 3G is the worst battery killer so this will help a lot.
SetCPU: http://forum.xda-developers.com/showthread.php?t=505419
Specific instructions for those that can't get it to work!:
On SetCPU:
Click Add profile
Where it says Profile, select it and tap "Screen Off"
Set the frequencies you want in use while screen is off (If you want just one frecuency, put both sliders on the same number)
Set priority (in case you have other profiles, otherwise don't bother)
Select governor (Won't really matter since cpu is gonna be running at 1 frecuency)
Tap save
Go back to Profiles tab at the top, then tap Enable at the top left to make the profiles work.
For a list of most governors detailed; check out this thread! http://forum.xda-developers.com/showthread.php?t=1242323
To check if its all working, install CPU spy from the market:
https://play.google.com/store/apps/...251bGwsMSwxLDEsImNvbS5idmFsb3Nlay5jcHVzcHkiXQ..
Battery Calibration
1. Turn your phone off
2. Leave charging over night
3. Turn it on
4. Leave it charging for half an hour
5. Download this app https://play.google.com/store/apps/details?id=com.nema.batterycalibration&feature=search_result
6. Open it and press calibrate battery
7. Discharge your phone down to 0% during the day
8. Charge back up to 100% NON-STOP.
This is to make sure you're using your battery at 100%. Only do this after you flash a new rom.
The worst battery killer is 3G itself. No matter how much you try to optimize battery and underclock, if you have 3G on, you're gonna have a bad time. MAKE SURE Autosync is disabled.
Thanks to QNBT for the AutoSync off and new profile settings hint!
gotta try this one. hope this works!
Hey dude I may try that tip, but I wanted to know about the governor that you are using, is that one a battery saver?, and what about chainfire 3d? you said that you dont use heavy apps and as far as I know that one is for heavy gaming isnt it?
ps. I recommend you install Vturbo 8.5 by gadgetcheck since I didnt see it on your signature, it really works
tyraelasd said:
Hey dude I may try that tip, but I wanted to know about the governor that you are using, is that one a battery saver?, and what about chainfire 3d? you said that you dont use heavy apps and as far as I know that one is for heavy gaming isnt it?
ps. I recommend you install Vturbo 8.5 by gadgetcheck since I didnt see it on your signature, it really works
Click to expand...
Click to collapse
Yeah, I'm not using heavy apps now but I do like some gaming now and then. When I do game, I crank up the processor back to normal but I rarely do. And I use Smartass governor, not really sure if its a battery saver but its working great.
And yeah, I think I had turbo 8.5. But for now, my ace runs perfectly fine so I don't really need other scripts or optimizers
CPU governors control exactly how the CPU scales between your “max” and “min” set frequencies. Most kernels have “ondemand” and “performance.” The availability
ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
interactive – Available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
smartass – Included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
Thanks for the tip, works for me
Im trying smartass governor but I noticed that the battery got really hot for some unknown reason :/, and I I got back to ondemand it becomes normal. Any idea?
I would rather use SetCPu becouse a need automatic changes since I play a lot ;P
I have no idea. My phone's working fine. I keep switching between interactive and smartass. Can't really tell which one works better xD
Sent from my GT-S5830 using XDA App
Ooohhh I see. Thanks for the governor definitions. Keeping Smartass then
Sent from my GT-S5830 using XDA App
i had battery issues (only lasts for a day), after applying this, another day was introduced for my SGA. LOL clicked the thanks button! cheers!
tomy2590 said:
i had battery issues (only lasts for a day), after applying this, another day was introduced for my SGA. LOL clicked the thanks button! cheers!
Click to expand...
Click to collapse
Haha good to know it doesn't only work for me. I clocked it down lower to 320 since I'm barely using it now. Love my ace
SuperAce609 said:
Haha good to know it doesn't only work for me. I clocked it down lower to 320 since I'm barely using it now. Love my ace
Click to expand...
Click to collapse
Hahaa... I know why...
Because you using What ROM? What Tweaks/script? like me too.. Hehehe..
Thank for sharing that setting... I'm really love my SGA now..
arip30 said:
Hahaa... I know why...
Because you using What ROM? What Tweaks/script? like me too.. Hehehe..
Thank for sharing that setting... I'm really love my SGA now..
Click to expand...
Click to collapse
This rom actually has a pretty bad battery life. But makes up for it with speed and stability. I'm only using the LagFree V2 script and thinking about adding TurboBoost but I'm not sure if they can work together.
SuperAce609 said:
This rom actually has a pretty bad battery life. But makes up for it with speed and stability. I'm only using the LagFree V2 script and thinking about adding TurboBoost but I'm not sure if they can work together.
Click to expand...
Click to collapse
I already using both.. I'thing its can work together.. But i'm not to sure cause am only using lest then 1 week..
For me, i want to using a smoth n fast.. i don't care about the battery live cause i can charge or use my secondary/spare battery..
________________________________
Please push thank button for me.. TQ..
arip30 said:
I already using both.. I'thing its can work together.. But i'm not to sure cause am only using lest then 1 week..
For me, i want to using a smoth n fast.. i don't care about the battery live cause i can charge or use my secondary/spare battery..
________________________________
Please push thank button for me.. TQ..
Click to expand...
Click to collapse
Well, just in case you miss your spare battery at home or something, check out the edit I just made on the thread.
Will make your spare battery look like wasted money xD
Using CPUtuner now. Free and works perfectly. I dont think i need smartass governor, since it offers separate screenoff profile, where i can set everything i want, including services on/off.
knall said:
Using CPUtuner now. Free and works perfectly. I dont think i need smartass governor, since it offers separate screenoff profile, where i can set everything i want, including services on/off.
Click to expand...
Click to collapse
Lol, okay. SetCPU is also free (on XDA). But whatever works for you is fine. My fix is just running CPU at minimum as soon as the screen is off and switch profiles when the screen is on. That way you'll always have battery to use when you want to and not use up battery when you're not using the phone.
rjyama said:
CPU governors control exactly how the CPU scales between your “max” and “min” set frequencies. Most kernels have “ondemand” and “performance.” The availability
ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
interactive – Available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
smartass – Included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
Thanks for the tip, works for me
Click to expand...
Click to collapse
Thanks for the explanation, man...it was very useful
My setting
Profile: screen off
Min 122
Max 122
Governor: powersave
Profile: battery
101%
Min 122
Max 806
Governor: conservative
pyronia said:
My setting
Profile: screen off
Min 122
Max 122
Governor: powersave
Profile: battery
101%
Min 122
Max 806
Governor: conservative
Click to expand...
Click to collapse
I REALLY don't recommend leaving it at 122 minimum. I tried it today and had a lot of lag attacks. Though the battery saving is incredible, but at the cost of a lot of performance. Like taking a call, it'll lag like hell. Had a lot of missed calls today just because of that issue.
But if it works for you, then have fun!
SuperAce609 said:
I REALLY don't recommend leaving it at 122 minimum. I tried it today and had a lot of lag attacks. Though the battery saving is incredible, but at the cost of a lot of performance. Like taking a call, it'll lag like hell. Had a lot of missed calls today just because of that issue.
But if it works for you, then have fun!
Click to expand...
Click to collapse
Yeah, I noticed that a few weeks back, couldn't even answer so much it was laggy. You can set in phone call 245mhz and priority higher than screen off and it resolves that issue.
I use cyanogenmod performance for setting the clock with 245mhz min now, I don't have any wakelocks so the processor is always off (deep sleep) when the screen is off, at the same time I don't have the wake lag issue since its not running at 122mhz when it wakes.
Related
Is there a negative effect of setting the clock speed lower while screen off? Aside from running really labor intensive tasks?
It just seems like a great way to save battery to me. Right?
The only negative is getting the phone to wake up fast enough when you get an inbound call.
The CFS kernel (which is widely used now) seems to be less able to come out of a deep sleep rapidly than the older "zanfur" OC kernel did.
IIRC, on the older "zanfur" OC kernel, you could set the minimum scaling frequency to 19 Mhz - but with with the CFS kernel, you may need to use a minimum value of 122 Mhz or 245 Mhz.
Set the max scaling speed to 480 or 528 when sleeping. (The max frequency is only rarely used when the phone is sleeping - but you want the phone to pop out of it's low speed state quickly when you power up the screen, or experience an inbound call).
Thanks, Yeah I usually set the max to 480 while sleeping and 480 as min while awake. Battery seems good there.
Originally I was using SetCPU but I have switched to CPUBoost. Most all the kernels in the past few roms I have used are made by conap and he is also the creator of CPUBoost, so I figured they would integrate really well.
Also if I enter anything above the 800 range the phone will have random reboots throughout a few different roms I've tried.
As a note, if I remember correctly, if you have a kernel/ROM that supports the smartass governor, you should be able to use it and not need to have a profile set to underclock while the screen is off, or really need to underclock at all, as I believe it determines for you how much CPU is needed and sets the clock speed accordingly, simply abiding by your max and min speeds you set. Since less CPU is needed when the screen is off, it will automatically adjust accordingly. However, this is just something I've read around the forums, so don't take my word for it
Pokelover980 said:
As a note, if I remember correctly, if you have a kernel/ROM that supports the smartass governor, you should be able to use it and not need to have a profile set to underclock while the screen is off, or really need to underclock at all, as I believe it determines for you how much CPU is needed and sets the clock speed accordingly, simply abiding by your max and min speeds you set. Since less CPU is needed when the screen is off, it will automatically adjust accordingly. However, this is just something I've read around the forums, so don't take my word for it
Click to expand...
Click to collapse
Thanks for the info, I didn't know that. I will assume that's more or less accurate unless Conap or bftb0 chime in.
Pokelover980 said:
As a note, if I remember correctly, if you have a kernel/ROM that supports the smartass governor, you should be able to use it and not need to have a profile set to underclock while the screen is off, or really need to underclock at all, as I believe it determines for you how much CPU is needed and sets the clock speed accordingly, simply abiding by your max and min speeds you set. Since less CPU is needed when the screen is off, it will automatically adjust accordingly. However, this is just something I've read around the forums, so don't take my word for it
Click to expand...
Click to collapse
roirraW "edor" ehT said:
Thanks for the info, I didn't know that. I will assume that's more or less accurate unless Conap or bftb0 chime in.
Click to expand...
Click to collapse
Well, I suppose it could be said that the whole point of any rate governor is to reduce overall power consumption without markedly affecting the user's perception of "responsiveness" or "speed" - however they go about defining those metrics.
OTOH, because there are - what - five different scaling governors available, it is apparent that people have found their own reasons to create new scaling governors; presumably that arose from a dissatisfaction with the behavior of the available scaling governor - or, that different users have differing application workloads, and so they prefer one governor over another.
As Pokelover980 suggests, you could just hand a given rate governor a fixed set of limits (min/max), and be done with it.** For folks that have the time and desire to experiment, I would suggest that: pick a governor and a min/max clock rate and run that way for 2-3 days - no profiles at all. Then pick a different governor with the same min/max clock rate and run that way for another 2-3 days, and see how it goes - maybe not in battery life, because that's hard to measure in a repeatable way, but at least to see if any problems occur coming out of sleep.
Is the "smartass" governor better than all the rest of them? I don't really know. I used it for a little while, but found something I didn't like about it. (But don't take that as conclusive about anything; I doubt that I was doing disciplined testing when that happened). I tend to use either "interactive" or "ondemand", and don't have a strong preference for one over the other.
There probably is some value in keeping things simple. I think that I mentioned before that at one point (back when the CFS kernels were still in a state of flux) I was convinced that using setCPU was exacerbating problems with lock-ups I observed (once every couple of days). Again, though - that was really only my suspicion; I can't really prove it.
bftb0
** I suppose that folks that insist on extreme levels of overclocking ought to use either an overtemp profile or some other means to monitor temperature so that they don't cook their phone.
I Installed SetCPU on the wifes Eris. The smartass governor on CM7 will max out the cpu (to your preset max) if needed. I dont think the smartest thing to do is max out the cpu at 15% batt life. I have 5 different profiles set. One for screen off, charging, < 50%, < 30%, <10%. I use interactive governor vs smartass. Her phone is pretty responsive and I dont hear about issues with it not waking up. Battery life has also increased quite a bit.
As I understand solution for "998 MHz with screen on" bug is found: http://forum.xda-developers.com/showthread.php?t=1225411&page=17#post16944722
We need to replace only one governor.
I don't want to play with different ROMs and kernels and I'm looking for simplest solution.
Is it possible to compile it as a module ("ondemand_mod" for ex.) and add it to stock ROM?
Or any other (simple) way?
Wrong section ...
Sent from my X10i using Tapatalk
Why wrong Section, this is Development to get the CPU Governor working correctly
Wolfbreak said:
Why wrong Section, this is Development to get the CPU Governor working correctly
Click to expand...
Click to collapse
Exactly, this is the right section for such request.
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
My_Immortal said:
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
Click to expand...
Click to collapse
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
As I see it's possible to compile and use governor as module.
Could someone compile it? And assemble as xRecovery package?
Or point me where to read about compiling for arm, where to get tools and so on...
Karlson2k said:
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
Click to expand...
Click to collapse
The thing is, on 245 MHz, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Xperia X10i via Tapatalk
My_Immortal said:
The thing is, on 245 MHz with high load, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Click to expand...
Click to collapse
There is no need to work on 245MHz as proper governor rise frequency automatically when it's necessary.
And really no stress for CPU to work an low frequency at full load. Moreover - CPU will consume more power at 500Mhz with 45% load than at 250Mhz with 95% load.
Sometime I use phone for navigation - long time with screen on and very low load. In this scenario battery drains very fast.
And last one - I like to have everything working properly. In case that I'll really need high frequency all the time I'll use other governor. I just want to have a choice.
I need a simple solotion for this too..I use z kernel and I found that Thego2s kernel fixed this problem..I was going to flash that kernel but think that has a bug and stoucks on logo ..can some one sayas a simple way?
Yes, I think a lot of people would prefer to use just small and simple fixes rather than replacing the whole kernel with a lot of nice but (personally) unnecessary features.
I am waiting for developers to release a fix for this problam
Hey,
I'm just curious how overclocking to 1.51ghz effects battery life (over 1.18ghz).
I'm currently running LeeDroid with Anryl 10.07 (great for battery life), but i'm wondering if I want the extra horsepower how will this affects battery life with just normal day to day activity. e.g. web browsing, email, facebook, twitter, messaging and sometimes a small bit of gaming (nothing too intensive).
The speed increase of a 1.51ghz OC is quite noticeable and all apps just seem so much more responsive. With your experiences how much has your battery life been affected over the stock speed with general use?
Thanks.
Louis
lhayati said:
Hey,
I'm just curious how overclocking to 1.51ghz effects battery life (over 1.18ghz).
I'm currently running LeeDroid with Anryl 10.07 (great for battery life), but i'm wondering if I want the extra horsepower how will this affects battery life with just normal day to day activity. e.g. web browsing, email, facebook, twitter, messaging and sometimes a small bit of gaming (nothing too intensive).
The speed increase of a 1.51ghz OC is quite noticeable and all apps just seem so much more responsive. With your experiences how much has your battery life been affected over the stock speed with general use?
Thanks.
Louis
Click to expand...
Click to collapse
It really depends what governor your using. If you use On Demand, and set the low to around 400-500, you shouldn't have that much of a problem. I can't really give you an accurate answer as it defers for everyone. It also depends on the Kernel, ROM, apps your using...
Check this page out for reference on the Governors. I found it to help me out a lot and I hope it will do the same for you.
http://forum.xda-developers.com/showthread.php?t=843406
It destroys my battery life, so I only have it going 1.51 GHz when connecting to wall charger.
Sent via carrier pigeon
I also have it on 1.51Ghz, but I'm sure when I travel to China that for battery saving its better to put it on 1.2Ghz.
Mine drained a lot. From 7 to 3 pm my battery had about 20% left its 2:44 now. And I'm at 71 percent.
Sent from my PG86100 using Tapatalk
it really depends on how aggressive your settings are for the selected governors. a lot of people make the mistake of feeling like the presets for ondemand need to be super aggressive in order to squeeze performance out of the device and run smooth. this is simply not true.
applying up_threshold values lower than 90 (and 90 is arguably pretty aggressive to most people who understand how this works) is unnecessary in most instances. i have seen presets as low as 60, even 50... that is simply overkill and causes your processors to ramp up really high when they don't need to be.... basically wasting power and spinning at max frequency for a simple task that can be executed at a much lower frequency.
and as somebody else here mentioned, it depends on the governor you are using. the all have different functions and performance benefits/flaws.
i have recently found that using interactive governors on both cores with a go_maxspeed_load value from 80 to 85 is very efficient and snappy. the goal with your processors and scaling governor presets should be to make them more efficient, not necessarily faster because efficiency is what saves energy AND time when executing a task.
i don't use anything but IntelliAnthraX and interactive. smartass is pretty good too. it is similar to interactive but with a screen off profile.
and to add to the whole power consumption of these devices....
your display chews 10 times more power than your processors do at any given speed.... adjust your display dynamics because that is what truly saves you power.
---------- Post added at 03:23 PM ---------- Previous post was at 03:22 PM ----------
maybe not ten times more.... but quite a bit more...
to drive the point in about efficiency.... here is a screen shot of my last charge. heavy use.. both cores spinning all the time and clocked at 1.51 gHz...
http://db.tt/bEgjzTMh
infEcted
cobraboy85 said:
to drive the point in about efficiency.... here is a screen shot of my last charge. heavy use.. both cores spinning all the time and clocked at 1.51 gHz...
http://db.tt/bEgjzTMh
infEcted
Click to expand...
Click to collapse
Thats some pretty decent life for 1.51ghz, before on LeeDroids kernel I couldn't get that with 1.18ghz :/
system efficiency man... the laws of physics apply to anything that requires energy to operate.
that was on Chad's rls08 beta 5, interactive governors, default settings for interactive.
infEcted
cobraboy85 said:
system efficiency man... the laws of physics apply to anything that requires energy to operate.
that was on Chad's rls08 beta 5, interactive governors, default settings for interactive.
infEcted
Click to expand...
Click to collapse
Would you recommend the interactive governor over on-demand for power efficiency?
Because on-demand only ever clocks at the MIN or MAX never inbetween
absolutely. for these devices, ondemand is quickly becoming useless for me. interactive is so much more efficient because it is a much simpler way of analyzing and dealing with CPU load. none of this sampling rate, ignore nice load, or powersave bias is used. it is simple - cpu load reaches a given percentage of maximum (much like the way up threshold works) and based on that number the cpu ramps up. and if it is above that predefined load then it ramps from highest frequency to lowest. rather than always lowest to highest. on top of that, there is a time interval defined which tells the cpu to hang at the highest frequency when that load value is reached or exceeded. the result is a more efficient way of allocating cpu frequency usage. your processor doesn't waste energy spinning up all the way when it doesn't need to and does not analyze cpu load to know when to scale back down.
responsiveness improves because of this as well and larger tasks are actually executed more efficiently and quicker because of the scaling down dynamic.
people feel that ondemand needs to be the one to use and that you need all these aggressive settings to squeeze performance out of the device. the truth is, side by side interactive is hitting the same benchmarks on my device as before and is managing cpu load a hell of a lot better... the result is the screen shot you just saw.... with android OS, cell standby, and display, accumulating over 80 percent of the usage in a 15 hour window. and display being 63 percent of that.... that screen shot is ungodly battery life for this device. much of it has to do with system efficiency while I am interacting with the device.
infEcted
---------- Post added at 10:25 AM ---------- Previous post was at 10:16 AM ----------
if i can add to that as well....
i wish i would have taken a screen shot of my cpu frequency times (via the app CPU spy) .... you would be surprised at how much overall time is spent in each frequency and how little time your device spends at the highest frequencies compared to ondemand. i will do it this next battery cycle to give you and idea. ondemand is a complex and inefficient way of handling cpu load for these devices. you want performance, you want to save power, use interactive governors. your higher frequencies should only be used when absolutely needed... like loading web pages, playing games that are taxing on overall processing load, etc,.... not sending a text message to your mom or flinging through your contacts to make a phone call.
Wow man thank you so much for the into. Thanks given!
And I agree about On-Demand just scrolling through a menu doesn't need MAX clock speed :/
What are your opinions on undervolting? I'm using Anryl's awesome kernel (great for powersaving)
undervolting is good when it isn't too agressive. my opinion of it is simply that i don't really see the need. the effects are pretty minimal when you compare it to the overall voltage, your display output, any other functions of the device that eat power. reboots are too easily a problem caused by agressive undervolting or even by just undervolting the lowest frequency (totally unnecessary to undervolt the 192000mHz rang imo... it eats absolute minimal power as it sits and saves you nothing).
as far as voltages go, i use chad's kernels exclusively and he gets his voltage specs straight from Qualcom... that is good enough for me. i have used ROMs that have UV scripts that are applied post boot and whenever i use them with chad's kernels i am almost guaranteed a lockup or reboot by the end of the day. when i remove those scripts, reboots, lockups all of the issues mysteriously disappear. the issue is evident.
don't dismiss undervolting, though. as i said, if done properly and not too aggressive it can be a positive dynamic of your goal to minimize power consumption... is it noticeably worth it? eh, debatable in my opinion.
Yeah, I haven't really seen the effects of undervolting myself (Thanks given again). I did a -50mv undervolt and all that really happened were reboots every few hours :/
I'm using Anryls Kernel because of it's really good battery life. But you can tell it is a bit slower that others. Would you recommend Chad's Anthrax over Anryl? Whats the battery drain in comparison. (I have looked at the kernel comparison thread, but it not that detailed and lacks info on certain kernels).
lhayati said:
Yeah, I haven't really seen the effects of undervolting myself (Thanks given again). I did a -50mv undervolt and all that really happened were reboots every few hours :/
I'm using Anryls Kernel because of it's really good battery life. But you can tell it is a bit slower that others. Would you recommend Chad's Anthrax over Anryl? Whats the battery drain in comparison. (I have looked at the kernel comparison thread, but it not that detailed and lacks info on certain kernels).
Click to expand...
Click to collapse
there are few people that give in depth detailed lists of what exactly they have been doing with their work. it is hard to compare when you don't have the ingredients that went into making it. chad is good about keeping us updated on exactly what he is doing. many times I have talked to him personally about his work and what he is cooking up as he is cooking it up. my personal experience has been that for the last few months I have yet to see something even come close to what he is doing with this device. all opinion of course, but being somebody who talks to him on a daily basis and has used his work as extensively and rigorously as I have, I would say if there is a GSM version available (check his dl site) use it. his are miles ahead of even HTC. I mean for hells sake he had the camera working on the device before the source code for the camera drivers was released. guy is unreal.
to answer your question, battery drain is likely normal. I know he recently made some changes to the battery drivers but I believe that was due to a lockup issue a small number of people were having (myself included) not anything to do with actual usage or drain.
there is a laundry list of tweaks and additions to his kernels. I couldn't tell you all of them if I tried. just too many. with anthrax kernels there is way more into them than just undervolting, overclocking, and removing perflock. bt drivers, touch drivers, battery drivers, camera drivers, sound drivers.... nothing is untouched. and he uses qualcom source not busted ass HTC source code. overclocked GPU? check. beats audio drivers? check. a kernel that is universal between multiple versions of android? ****, why not. his own built from scratch scaling governor? well damn since I'm not doing anything why not right? if you can find a GSM version of a recent anthrax kernel, don't even think twice about it.
anyways,
infEcted
and to answer your question yes there are GSM versions of anthrax. I just checked. the latest update was approximately a week ago.
infEcted
Wow it sounds great and thanks given again
I was sure that is was discontinued as a whole, but it seems to just be removed from XDA. I'm unsure which version is right for me as there are 4 versions?
I am on a LeeDroid's Sense 3.0 rom. I think it's the RLS04 because I have seen it mentioned before, but I don't want to risk it and flash the wrong kernel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
RLS04 is the one you want... you shouldn't have any issues with it.
Ok I just flashed it and it seems to run really smooth. But in all benchmarks the CPU score is incredibly low. I think it's something weird with the interactive governor on this kernel.
I see there are SmartAssV2 and IntelliAnthraX should I use one of these? What one is best?
*EDIT*
Even with Performance on I'm getting an unusually low Productivity score in SmartBench of 600 and in Quadrant Advanced about 1700 even in AnTuTu it's lower than Anryl. (am I doing something wrong?)
what did you use to set the cpu settings
infEcted
has anyone else tried using setcpu with ics roms? does it actually do anything?? I'm trying now, and i set my lowest frequency to 192 and like max at 894...thing is I don't notice the phone being any slower... is it actually doing anything? it says it is.. system panel shows it maxing out at 894..but I'm still dropping battery like crazy lol clearly it doesn't help enough if it even works.
Sent from my ADR6425LVW using XDA App
Known bug with ics roms, will not work at all until source is released and we get someone to to build a kernel without HTC perflock built in
Sent from my aokpcb_tenderloin using xda premium
don't use any apps that control the CPU. that goes for frequency,governors,etc. it messes with perflock which causes the CPU to run at only the min/max frequency and no proper scaling. stick with this advice until custom ics kernels come
It works for me. Tell me I'm stupid if you want but my battery doesn't drain as fast with it. If I set CPU to 500mhz it runs slower so it does something. It does bounce around due to perflock. But it helps me
Sent from my ADR6425LVW using Tapatalk 2
Evocm7 said:
It works for me. Tell me I'm stupid if you want but my battery doesn't drain as fast with it. If I set CPU to 500mhz it runs slower so it does something. It does bounce around due to perflock. But it helps me
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ehhh far to many times I'd have the phone go 1.5Ghz full blast non stop even with the screen off. Be at work and wonder why my leg was on fire.
Sent from my ADR6425LVW using XDA
It works great for me, and was just updated recently and fixed all the little minor problems and occasional crashes that I used to have.
None of the stock kernels should ever be govern with a CPU app. I have no idea why people say it only applies to ICS. In fact this applies to BOTH GB and ICS kernels. GB and ICS kernels have the same battery life on stock roms.
If the kernel does not allow you to disable perflock, it won't scale right, stock kernels cannot have it disabled. I say again, BOTH ICS and GB because people like to give out FALSE INFORMATION.
Sent from my ADR6425LVW using XDA
nosympathy said:
Ehhh far to many times I'd have the phone go 1.5Ghz full blast non stop even with the screen off. Be at work and wonder why my leg was on fire.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
That has happened to me once. But not since last update. It does bounce around sometimes but never goes above the max I specify so I'm happy with it. Keeps temps down under heavy use as well even though temps aren't much of an issue with latest leak
Sent from my ADR6425LVW using Tapatalk 2
Works fine after the latest update on conservative governor, scales throughout the range given. Cleanrom 4.4 stock kernel.
richii0207 said:
I say again, BOTH ICS and GB because people like to give out FALSE INFORMATION.
Click to expand...
Click to collapse
exactly...
lol so people are saying it works, and people are saying it doesn't.
doesn't really answer my question lol
Sent from my ADR6425LVW using XDA App
Quadrant only shows my CPUas being single core . I'm on CleanRom Standard Edition 4.5. Wasn't sure if that had been addressed in a thread yet or not . So I wasn't sure where to address this, but this seemed like a good place . I took a screenshot of it .
Sent from my ADR6425LVW using xda premium
jayochs said:
lol so people are saying it works, and people are saying it doesn't.
doesn't really answer my question lol
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
If it works its doing something, it works. It works on cleanrom ics pro 4.4 on conservative governor since the last update before that it wasn't working right for me it would jump to Max all the time now it scales right.
Kane5581 said:
If it works its doing something, it works. It works on cleanrom ics pro 4.4 on conservative governor since the last update before that it wasn't working right for me it would jump to Max all the time now it scales right.
Click to expand...
Click to collapse
i'm running cleanrom 4.5 right now. when i set to conservative, it jumps all over, but it still maxes ouat at 1512 often.
i just stopped touching it because i didn't feel like breaking anything lol but again, some people are saying due to perflock it won't work, while others say they have experience of it working. so confusing.
Perflock being the pain it is, I'm staying away from it right now.
When I had it installed, my battery life was complete fail.
Sent from my ADR6425LVW using Tapatalk 2
jayochs said:
lol so people are saying it works, and people are saying it doesn't.
doesn't really answer my question lol
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
All you can do is try it. Worst case scenario your battery drains too fast. Then uninstall it. Why it helps some and not others, I don't know. It helped me get 16 hrs of battery life with 4hr screen time with 4g on stock battery (ics) yesterday. No way in hell I could get that without setcpu
Sent from my ADR6425LVW using Tapatalk 2
Well at the risk of posting terrible "FALSE INFORMATION!", I'll let you know my experience with setCPU so far and you can make your own decisions from there.
First, here's my current config:
Android 4.0.1, SebastianFM's 1.20 OC Kernel, CFQ IO scheduler, interactive or on-demand governor depending on situation (cpu profiles enabled).
Profiles enabled, listed lowest to highest priority:
bat <=100% -- min=384, max=1566, interactive, CFQ
bat < 90% -- min=384, max=1350, interactive, CFQ
bat < 75% -- min=192, max=1188, interactive, CFQ
bat < 50% -- min=192, max=1026, interactive, CFQ
temp > 105*F -- min=192, max864, interactive, CFQ
bat < 34% -- min=192, max=864, conservative, CFQ
bat < 25% -- min=192, max=648, conservative, CFQ
SCREEN OFF -- min=192, max=540, interactive, CFQ
temp > 120*F -- min=192, max=540, conservative, CFQ
bat < 15% -- min=192, max=540, conservative, CFQ
So, I realize Perflock is enabled, so frequencies do tend to jump around. However, when you set and enable profiles, setCPU does seem to control the frequencies still, even though you can watch the min/max frequencies move around.
I use the setCPU widget on my homescreen too. So lets assume for example my battery is between 90-100% charge, in which case my min=384 and my max=1566. With profiles enabled, I can watch my minimum frequency occasionally go as high as my max, or 1566. Generally, this happens when my phone is actually using the 1566 frequency at the present moment, which is indicated by the current frequency display on the widget. However, if my current CPU speed happens to be anywhere in between the range i selected, lets just say its at 864mhz currently. In this situation, my current frequency will show 864mhz, but my min frequency might also show 864mhz and my max might show 1188mhz, at that particular time.
OK so now my battery has depleted to 49%, and so my profile kicks in and sets the minimum frequency at 192 and the maximum frequency at 1026. In this case, I'll NEVER see a current CPU speed over 1026mhz. I might see both the minimum and maximum at 1026mhz for a period of time, or I may see the current frequency say 648mhz while the minimum is at 192mhz and the maximum reports 648mhz also.
The point is, YES, I can watch perflock doing its thing and changing my min/max frequencies around constantly. However, by simple observation I can confirm it does actually scale within my specified parameters.
There was a bug with setCPU up to about a month ago where it would occasionally crash and your CPU would just go to its normal default (384-1512mhz, deadline scheduler, on-demand governor), however the recent updates have fixed the crashes! SetCPU now continually runs without crashing, and when you use profiles, it DOES seem to scale exactly how you tell it to.
a.mcdear said:
Well at the risk of posting terrible "FALSE INFORMATION!", I'll let you know my experience with setCPU so far and you can make your own decisions from there.
First, here's my current config:
Android 4.0.1, SebastianFM's 1.20 OC Kernel, CFQ IO scheduler, interactive or on-demand governor depending on situation (cpu profiles enabled).
Profiles enabled, listed lowest to highest priority:
bat <=100% -- min=384, max=1566, interactive, CFQ
bat < 90% -- min=384, max=1350, interactive, CFQ
bat < 75% -- min=192, max=1188, interactive, CFQ
bat < 50% -- min=192, max=1026, interactive, CFQ
temp > 105*F -- min=192, max864, interactive, CFQ
bat < 34% -- min=192, max=864, conservative, CFQ
bat < 25% -- min=192, max=648, conservative, CFQ
SCREEN OFF -- min=192, max=540, interactive, CFQ
temp > 120*F -- min=192, max=540, conservative, CFQ
bat < 15% -- min=192, max=540, conservative, CFQ
So, I realize Perflock is enabled, so frequencies do tend to jump around. However, when you set and enable profiles, setCPU does seem to control the frequencies still, even though you can watch the min/max frequencies move around.
I use the setCPU widget on my homescreen too. So lets assume for example my battery is between 90-100% charge, in which case my min=384 and my max=1566. With profiles enabled, I can watch my minimum frequency occasionally go as high as my max, or 1566. Generally, this happens when my phone is actually using the 1566 frequency at the present moment, which is indicated by the current frequency display on the widget. However, if my current CPU speed happens to be anywhere in between the range i selected, lets just say its at 864mhz currently. In this situation, my current frequency will show 864mhz, but my min frequency might also show 864mhz and my max might show 1188mhz, at that particular time.
OK so now my battery has depleted to 49%, and so my profile kicks in and sets the minimum frequency at 192 and the maximum frequency at 1026. In this case, I'll NEVER see a current CPU speed over 1026mhz. I might see both the minimum and maximum at 1026mhz for a period of time, or I may see the current frequency say 648mhz while the minimum is at 192mhz and the maximum reports 648mhz also.
The point is, YES, I can watch perflock doing its thing and changing my min/max frequencies around constantly. However, by simple observation I can confirm it does actually scale within my specified parameters.
There was a bug with setCPU up to about a month ago where it would occasionally crash and your CPU would just go to its normal default (384-1512mhz, deadline scheduler, on-demand governor), however the recent updates have fixed the crashes! SetCPU now continually runs without crashing, and when you use profiles, it DOES seem to scale exactly how you tell it to.
Click to expand...
Click to collapse
awesome analysis. ...so what's your battery life like?
I've gottent it to work a couple of times, other times it seems to do nothing at all, and i have also had it almost burn a hole in my pocket due to heat. I would say dont try to OC for now and wait until we have something more stable as they have previously stated. To be honest its a hit or miss type of mod for now.
jayochs said:
awesome analysis. ...so what's your battery life like?
Click to expand...
Click to collapse
My battery life is pretty good. I'm very surprised by how little i actually notice the difference in responsiveness and performance as my CPU throttles lower as my battery drains throughout the day.. However, I will admit that the only reason I have it scaling so low like that was to match the same battery life that I was getting on totally de-sensed GB builds...
So far, I've read and tested some CPU governors to find the best in battery life that doesn't sacrifice performance too much (powersave is out of the list), namely:
Smoothass
SmartassV2
Virtuous
Intellidemand2
From all these, I found that Intellidemand2 is the best (lag when playing games appear quite rarely, only when complex calculation happens). However, I'd like to hear from you (esp. those who already tested ALL available governers) which one, in your opinion, that fulfills above requirement and is suitable for XMP (device does matter, doesn't it)?
P.S.: If the I/O scheduler also affects, please mention it along
It all depends... No battery governor can spare you 2 days of battery..... But you may try InteractiveX in combination with smartassv2... Best to use InteractiveX when the phone is idle and smartassv2 for gaming and music.....
Smartassv2 combined with sio. Anyway u doesn't need to use such cpu app that sets "profiles" e.g. changing governor while screen turned off etc, smartassv2 is smart enough, it got its own algorithm to limit max cpu when phone is sleeping.
icarious said:
It all depends... No battery governor can spare you 2 days of battery..... But you may try InteractiveX in combination with smartassv2... Best to use InteractiveX when the phone is idle and smartassv2 for gaming and music.....
Click to expand...
Click to collapse
Haha, I don't expect 2 days, not even 1 day. My normal daily use is mostly social networking (3 apps, all with background updates), email (2 accounts, 1 with push, 1 with 15 minutes period notification), chatting, sms and gaming. Sometimes music also. It seldom passes 10 hours which is why I'm looking one with best battery life (it can reach 13 hours if I don't play game).
an0nym0us_ said:
Smartassv2 combined with sio. Anyway u doesn't need to use such cpu app that sets "profiles" e.g. changing governor while screen turned off etc, smartassv2 is smart enough, it got its own algorithm to limit max cpu when phone is sleeping.
Click to expand...
Click to collapse
Will try that, seems like I haven't tried the combination with sio. Thanks.