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
Related
If you are using one of the Over-Clocked Undervolted Kernels please uninstall set-cpu and observe your battery life for 3 days and compare it to what you got when you used set-cpu. Then report as to if it is better, worse, or the same.
Just compare to what how long your battery lasts with your normal usage. Please do not give replies like "I only used 30% in two days with normal use."
Just reply with either better, worse, or same. Because usage is relative and that is not the purpose of this.
I think that set-cpu is interfering with the built in govenor and its ability to scale the freq of the phone. I think that it is staying on what-ever freq you set in set-cpu and scaling properly and thus reducing the battery life, and making the undervolting useless.
IF YOU BELIEVE YOU HAVE BETTER BATTERY LIFE WITHOUT SETCPU, THEN GET LOGS WHILE IT IS RUNNING AND SEND THEM TO THE DEV.
I have also noticed lag on the home screen with setcpu, I started using Overclock Widget to detect the values and to diff freq screen off 245-576 and put the phone on sleep while charging so will stay cool. Battery life has been great so far! I'm using 2.6.33.4 [email protected] #1 about to upgrade to his newest 2.6.34...I think SetCpu has flaws!
Will let you know my results.
this thread may be of some help. im currently trying pershoots 5.12vfp release without setcpu at all.
i do, however, remember getting 37 hours with moderate use with setcpu and profiles set, but i cant remember which kernal it was exactly. i think it may have been IRs 4.29 release..
Just uninstalled SetCPU and I'm running Pershoot's newest 2.6.33.4 925 Kernel. I will report back my findings in a couple of days...
Been curious about this for a while, but does the Nexus automatically throttle CPU speed by itself when SetCPU is not installed?
paulk_ said:
Been curious about this for a while, but does the Nexus automatically throttle CPU speed by itself when SetCPU is not installed?
Click to expand...
Click to collapse
Nope, incredible and onwards only.
Did this Quite a bit ago... ran with and without for over a week and i have better battery life without setcpu
When you don't have setcpu, you're not running at 1113ghz..
persiansown said:
When you don't have setcpu, you're not running at 1113ghz..
Click to expand...
Click to collapse
Perhaps...However, Linpack is proportional (I think) to the device's performance. My little experiment was testing different frequency kernels and measuring that against Linpacl
998: 7.4
1.13: 8.2
1.19: 8.9
So it would appear that performance increases with each kernel which wouldn't be the case if SetCPU was required.
I have some reasons to believe that SetCPU would interfere with the actual design of the Nexus One. I mean after all, i'm sure it was programmed to manage itself. So why have another app that does the same thing, twice? Just a thought, but for one thing, my phone is definitely cooler when charging compared to having SetCPU with profiles.
dogiedogie said:
Nope, incredible and onwards only.
Click to expand...
Click to collapse
You mean that the Incredible features CPU throttling?
jlevy73 said:
Perhaps...However, Linpack is proportional (I think) to the device's performance. My little experiment was testing different frequency kernels and measuring that against Linpacl
998: 7.4
1.13: 8.2
1.19: 8.9
So it would appear that performance increases with each kernel which wouldn't be the case if SetCPU was required.
Click to expand...
Click to collapse
There are dozens of potential optimizations that can be done to improve performance without touching the cpu speed. Different kernels, especially if they're from different people, will have different flags set in the build and so will perform differently even at the same clock speed.
Casao said:
There are dozens of potential optimizations that can be done to improve performance without touching the cpu speed. Different kernels, especially if they're from different people, will have different flags set in the build and so will perform differently even at the same clock speed.
Click to expand...
Click to collapse
I completely agree however all the kernels I use are from the same person and the optimizations at the different clocks speeds are identical. Therefore the spread in my linpack scores indicate that setcpu is not required. At least, that's my theory
this and other threads have made me question why we need setcpu anyways. I have it running and its great but can't we just integrate what setcpu is doing from the get go instead of having an external app running a separate process?'seems a little inefficient to me. The reason I say this is that I noticed most people are using the same settings for set cpu.
anyways, I dunno how relevant all this is since froyo's just around the corner and that may alleviate some problems but bring more problems
Yeah, start bashing my app, knowing I was the one who came up with the ideas behind the 1113MHz/uv hack in the first place (in fact, I came up with the 21MB hack as well, so prominently displayed in the OP's kernel thread title). Thanks, nexus one community.
I can explain that setcpu does not run any code in the background if your profiles are disabled, I can explain how cpufreq works, I can explain what lengths I went to to optimize the profiles, and I can explain that the profiles are very passive (except sometimes on the Droid, but there's an option for tweaking that) but I probably won't bother. Grab 1.5.3a and use it, or don't use it. I don't care either way.
I think that set-cpu is interfering with the built in govenor and its ability to scale the freq of the phone. I think that it is staying on what-ever freq you set in set-cpu and scaling properly and thus reducing the battery life, and making the undervolting useless.
Click to expand...
Click to collapse
You obviously do not know how cpufreq works. Setcpu does not touch the values after it sets a profile. Profiles actually run code only when it receives broadcast intents. It sets the max and min bounds and the governor if necessary within a fraction of a second. The service is completely idle otherwise. It can't "interfere with the built in governor." Okay, then. What is your big theory? What exactly is setcpu doing wrong?
SetCPU is advantageous because it allows you to tweak speeds on the fly and based on certain conditions. You can have solely kernel based overclocking and undervolting, sure, and that is perfectly fine. SetCPU is a convenient tool for controlling that without having to compile and flash a new kernel. If you do not like profiles, do not use them. They were only introduced in 1.3.0 But don't uninstall SetCPU because it does nothing with profiles disabled.
dogiedogie said:
Nope, incredible and onwards only.
Click to expand...
Click to collapse
HTC implements a rather awkward driver in nearly all of their Sense UI devices (and I think the Magic 32A) that throttles based on certain conditions. I am not entirely sure how it works, as I have not looked into the specifics, but it seems to max out the CPU under some conditions.
chowlala said:
I have some reasons to believe that SetCPU would interfere with the actual design of the Nexus One. I mean after all, i'm sure it was programmed to manage itself. So why have another app that does the same thing, twice? Just a thought, but for one thing, my phone is definitely cooler when charging compared to having SetCPU with profiles.
Click to expand...
Click to collapse
I am 100% sure this is placebo effect. Setcpu can't make your phone run hotter just because it's there. If you had a charging profile set for 1113/1113, sure, but that is not setcpu itself. Linux does not control the CPU scaling any further than what ondemand does - there is nothing preventing the CPU from going up to your max during sleep (or rather, when the screen is off), for example, or when your battery is low.
Oh, and using the active widget is a bad idea if you care about battery life. I tried to optimize it as much as possible, but realize that it's updating a lot more things than other apps are (the frequency, the bounds, and two temperature readings) at a relatively fast interval. The home screen does pause a bit while it is updating. That is a fact of life. Longer intervals are essentially useless because the update interval for cpufreq itself is on the order of thousands of microseconds. The current appwidget refreshes if the screen is on, regardless of whether it's visible or not (there is currently no way to tell if it is visible). A live wallpaper would be a much better idea than a constantly updating appwidget, and I'll look into that.
Let me explain this bit better. Cpufreq will scale your CPU between the max and min values automatically. Once the CPU load hits the "up threshold," it takes your CPU frequency from the min to the max, then gradually eases it down. SetCPU lets you easily change the max and min values on the fly. If you want, it can also prevent the system from scaling the CPU up that high during times you don't want it to (with profiles, of course). It does not and cannot interfere with the actual governor.
Well there you have it, straight from the source
TL;DR - setCPU doesn't run code in background unless you use profiles, it doesn't make your phone hotter unless you use a 1113/1113 profile, & if you value battery life don't use setCPU Active widget.
SetCPU
coolbho3000 said:
...
Click to expand...
Click to collapse
Props dude. Keep up the good work.
To be honest I'm a user, donator and supporter of SetCPU. I've never had cause to complain.
Not bashing your app dude, in fact I have the paid version. I am only wondering why people are noticing better battery life without it than with it. Want to see if it really is setcpu or something else. To do that something has to be isolated.
And I believe that if the freq are set in the kernel then the phone will scale up an down on its own.
coolbho3000 said:
Yeah, start bashing my app, knowing I was the one who came up with the ideas behind the 1113MHz/uv hack in the first place (in fact, I came up with the 21MB hack as well, so prominently displayed in the OP's kernel thread title). Thanks, nexus one community.
I can explain that setcpu does not run any code in the background if your profiles are disabled, I can explain how cpufreq works, I can explain what lengths I went to to optimize the profiles, and I can explain that the profiles are very passive (except sometimes on the Droid, but there's an option for tweaking that) but I probably won't bother. Grab 1.5.3a and use it, or don't use it. I don't care either way.
You obviously do not know how cpufreq works. Setcpu does not touch the values after it sets a profile. Profiles actually run code only when it receives broadcast intents. It sets the max and min bounds and the governor if necessary within a fraction of a second. The service is completely idle otherwise. It can't "interfere with the built in governor." Okay, then. What is your big theory? What exactly is setcpu doing wrong?
SetCPU is advantageous because it allows you to tweak speeds on the fly and based on certain conditions. You can have solely kernel based overclocking and undervolting, sure, and that is perfectly fine. SetCPU is a convenient tool for controlling that without having to compile and flash a new kernel. If you do not like profiles, do not use them. They were only introduced in 1.3.0 But don't uninstall SetCPU because it does nothing with profiles disabled.
HTC implements a rather awkward driver in nearly all of their Sense UI devices (and I think the Magic 32A) that throttles based on certain conditions. I am not entirely sure how it works, as I have not looked into the specifics, but it seems to max out the CPU under some conditions.
I am 100% sure this is placebo effect. Setcpu can't make your phone run hotter just because it's there. If you had a charging profile set for 1113/1113, sure, but that is not setcpu itself. Linux does not control the CPU scaling any further than what ondemand does - there is nothing preventing the CPU from going up to your max during sleep (or rather, when the screen is off), for example, or when your battery is low.
Oh, and using the active widget is a bad idea if you care about battery life. I tried to optimize it as much as possible, but realize that it's updating a lot more things than other apps are (the frequency, the bounds, and two temperature readings) at a relatively fast interval. The home screen does pause a bit while it is updating. That is a fact of life. Longer intervals are essentially useless because the update interval for cpufreq itself is on the order of thousands of microseconds. The current appwidget refreshes if the screen is on, regardless of whether it's visible or not (there is currently no way to tell if it is visible). A live wallpaper would be a much better idea than a constantly updating appwidget, and I'll look into that.
Let me explain this bit better. Cpufreq will scale your CPU between the max and min values automatically. Once the CPU load hits the "up threshold," it takes your CPU frequency from the min to the max, then gradually eases it down. SetCPU lets you easily change the max and min values on the fly. If you want, it can also prevent the system from scaling the CPU up that high during times you don't want it to (with profiles, of course). It does not and cannot interfere with the actual governor.
Click to expand...
Click to collapse
I too am a fan of setcpu, and over the last week I did get curious due to this this thread. I found my battery ran down quite significantly faster without setcpu, maybe because I didn't have my sleep profile of lowest freq min/max, or my battery profile of max 756, or my low battery profiles scaling down my cpu max. Either way, stop bashing the app, it's awesome, and if you had concerns, take them to the dev rather than start a witch hunt in the forums trying to make a posse.
People that report better battery, may not have had setcpu set up correctly in the first place. A friend of mine at work installed it, ran for a day and uninstalled it, citing it didn't do anything and infact drained his battery. He had the widget running, and had upped the minimum cpu freq to 500 and something, max to the 1.13ghx. He didn't run profiles. But as such, he wasn't letting his phone scale down to the lowest freq when it wanted to, and had the widget drain. I got him to set t up as I have mine, and he was blown away with the change.
"My car wont go over 20km/h"
"Are you putting your foot on the accelerator?"
"Whats an accelerator?"
Things have to be used correctly to get the best out of them, and unless someone saying it's far worse than without actually comes in and puts up their values they have it set to, we have no idea why they are having the fault. My experience (I have worked tech call centres for years) is that 99/100 issues people experience are due to not using things as they are set out to be, or just have no idea how to do what they are trying to do. My work mates thing was that he thought all apps would go faster if he increased the minimum freq, so therefore use less battery because the processes are completed faster. In a way it's logical, but the result is that even when nothings running the cpu wont fall below that value, so the battery drained much faster than he expected.
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
leedavis said:
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
Click to expand...
Click to collapse
Interesting point you raise actually.
I've just installed Setcpu and used the on demand governor. I left the values as default (200mhz for minimum and 1.2 ghz for maximum) - with no overclock.
I've immediately noticed swiping through the screens is a bit smoother and the biggest improvement is the gallery. All my photos appear much smoother. Before the gallery app was a bit lagy.
I haven't set any profiles yet such as screen off.
Every Android phone I've owned scaled the cpu, I think they all do. I've found that with setCPU my battery gets drained much faster en no real benefit in smoothness.
jzuijlek said:
Every Android phone I've owned scaled the cpu, I think they all do. I've found that with setCPU my battery gets drained much faster en no real benefit in smoothness.
Click to expand...
Click to collapse
Have you tried this yet though on the Galaxy S2?
There is definitely less lag than before - as stated, specifically in the gallery app. Just generally swiping feels more responsive as well. Battery is still pretty awesome, especially when using Lightening Rom 1.1 and the Android battery calibration app.
Hmm. I'll try SetCPU on the SGS2 and post back the findings (Performance+Battery).
I don't know how can it get any more smoother, I mean its already SO smooth!
there are many points to use setcpu on gs2:
-for some reason I dunno, gs2 can't manage it's 1.2ghz without gettin too warm. downclock and get rid of the burn effect.
-gs2 sports a good management of gpu (it does most of the work and setcpu doesnt down\overclock that). downclockin doesnt affect UI or video o browsing experience at all. can even downclock at 500 max speed without any sides.
-the only side u ll see it's benchmark (quadrant downgrading to 2000) but I hope u won't pay attention to such an unseful thing. benchmark doenst mean nothing, daily usage it's the only point to look at.
my settings: conservative, 200min 800max.
battery draining doesnt belong to setcpu this time, look to other settings.
alexleon said:
there are many points to use setcpu on gs2:
-for some reason I dunno, gs2 can't manage it's 1.2ghz without gettin too warm. downclock and get rid of the burn effect.
-gs2 sports a good management of gpu (it does most of the work and setcpu doesnt down\overclock that). downclockin doesnt affect UI or video o browsing experience at all. can even downclock at 500 max speed without any sides.
-the only side u ll see it's benchmark (quadrant downgrading to 2000) but I hope u won't pay attention to such an unseful thing. benchmark doenst mean nothing, daily usage it's the only point to look at.
my settings: conservative, 200min 800max.
battery draining doesnt belong to setcpu this time, look to other settings.
Click to expand...
Click to collapse
IT IS TRUE. I agree with every single line you wrote, it is just my expericence.
I have too setcpu conservative and undercloked 800 Mhz.
There no slow down or lag at all... But I am wondering if it gives a real boost to battery life. I am not sure of this.
I'll keep you guys posted... But I think that an undevolted Kernel it is really a need as for the solution of the damn dual core ginger bug that is sucking 20% of my battery every day
Well,from my experience with my Desire and Desire HD(won't even bother with the Hero,I had no real knowledge then),governors can make a huge difference.I for one like smartass or interactive governors(mostly the same).I wouldn't suggest conservative,interactive does the job much better.Tasks get done in less time and the CPU throttles down more quickly.Other than that,you can underclock or overclock all you like,it never made any big difference in battery life for me(Unless Sammy's CPUs are different in that aspect-Snapdragons are really "overclock-friendly").That's personal preference after all!
Anyway,the best solution IMO would be a vdd_levels interface.For those who don't know what it is,it is a mod made by -snq(Meet him at the Desire forums-That guy's a true LEGEND!He can patch/modify anything!),which practically allows you to change the voltage levels of the CPU on the fly rather than having to stick with the values hardcoded into the kernel.Using this and a simple script in GScript to change values that won't survive reboot or in init.d to be applied on boot,you can find the optimal voltages for your CPU(Don't forget,every CPU is unique and different),thus reducing heat and maximizing battery life.
If a dev brings that to the SGS2 it will be a big step in the right direction as far as I'm concerned.
I use SetCPU without issue, but only to run profiles (i limit the device to 500mhz when the screen is off). The rest of the time it scales itself up to 1.4GHz without fuss and using stock voltage. Battery life is fine, best ive had for an android device.
Wow, I've taken SetCPU off but left JuiceDefender on and my battery life is fantastic. At 70% after slightly heavier than normal use (used for listening to music for a couple of hours this morning) and been off charge for 8.5 hours.
SetCPU seems counterproductive on SGS2
leedavis said:
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
Click to expand...
Click to collapse
I did set ondemand which is a little more reactive and slightly smoother.
Though System Tuner is less cpu-consuming and much more useful on the SGS2. No need for all those complicated settings from setCPU. Only changing governor and changing frequencies on standby are useful.
leedavis said:
Wow, I've taken SetCPU off but left JuiceDefender on and my battery life is fantastic. At 70% after slightly heavier than normal use (used for listening to music for a couple of hours this morning) and been off charge for 8.5 hours.
SetCPU seems counterproductive on SGS2
Click to expand...
Click to collapse
Juice Defender uses as much battery as it saves this is fact, i have SepCPU set to 200 Min - 800 Max - On demand and have Juice Defender Ultimate and i thought it was great but it was recommended to me that i could save more battery by not using this, initially i was skeptical but tried it and i was astonished at the results, my battery life improved by 9 hours (i carried out a test with JD and without)
Anyone who says SetCPU uses up loads of battery is talking nonsense,it actually saves battery if configured correctly.
I am using Check Rom with set CPU I have it 1.2ghz max and 200. Using conservative governer. I been off charge for 15hrs, however I am using light usage I am on 72% screen on has been 5h 25m at time of writing. Not yet calibrated the battery.
jonny68 said:
Juice Defender uses as much battery as it saves this is fact, i have SepCPU set to 200 Min - 800 Max - On demand and have Juice Defender Ultimate and i thought it was great but it was recommended to me that i could save more battery by not using this, initially i was skeptical but tried it and i was astonished at the results, my battery life improved by 9 hours (i carried out a test with JD and without)
Anyone who says SetCPU uses up loads of battery is talking nonsense,it actually saves battery if configured correctly.
Click to expand...
Click to collapse
What are the settings are you using for the setcpu program in your S2?? Did you remove the Juice defender application?
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.
Ok, I had a prime that rebooted, swapped it and now have one with BT/wifi issues.
I always thought the reboots were like a bad PC overclock, aka happend to some but not others.
Well now I see by looking at CPU spy, ASUS has not only 1600mhz and 1500mhz marked unused but 1400mhz is now unused as well.
Also they added 370mhz and 204mhz and 102mhz.
So because *some* locked up we all have lower top end performance and more power drain by having 475 vs 102 be the lowest clock.
Dunno about you but this was not the fix I was hoping for.
{
"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"
}
Wait what? ASUS lowered the processing speed of Performance mode back to 1.3Ghz!?
Yep! In performance mode I can get 1300, balance seems to cap out at 1200 max even with glowball going.
So we "fixed" the crashing by Under-clocking? I'm not sure the 90% will be happy.
You would have thought they would have at least let us have 1400 in performance mode.
Does anyone have a app that will show all 5 tegra 3 cores in real time?
Guys by the end of the month they'll release the bootloader unlock tool and then you will ne able to build your own kernels and use whatever clock you want.
I think its more important that the device is stable for the normal user that doesnt know about clocks and voltage. CPUs are different, some can handle extreme values while others chicken out at the slightest overclock. The standard settings have to work on all devices so yeah...
Funny thing: at the same time users report a smoother experience because of the new gpu driver from nvidia I dont see the need to OC the fastest tablet out there anyway. But thats just me.
I can almost buy the 'lets slow everyone down to stop the crashing issue'. But why increase the minimum from 102 to 475? It just uses the battery quicker.
I would like to have the advertised clock speed without voiding my ability to RMA if something breaks. At the VERY least they could add it to the performance setting.
Also while you are looking at the 1.4 lockout, they also locked out 3 low mhz options, and that will have a huge effect on battery life.
This feels more like a hack than a fix.
It would be cool just to have a over clocked kernel just to say that it can be even faster but not really need to utilize it hahaha
I'm not complaining right now my Prime is very stable at the moment & i have been throwing alot at it. But we shall see.
Ok, so from what I can see, rather than have some cores on and other off, and 1 core only when the other 4 are not used etc. It now as all 4 cores on, at 1200 or 475!!!!
All 4 cores on all the time is no doubt going to give us a LOT less battery time!
Sounds like there are some issues with the Tegra3 and ICS in how they handle the "magic" of turning on and off the cores.
From what I have found to test with my prime just cycles between 475X4 and 1200X4 in balanced mode. Anyone else show something different?
Power saving mode seems to be 600mhz X 4 or 475X4
performance is 1300 X 4 and 475X4
fenturi said:
Power saving mode seems to be 600mhz X 4 or 475X4
performance is 1300 X 4 and 475X4
Click to expand...
Click to collapse
For what its worth, I am seeing exactly the same as you fenturi
For me having if I don't see a performance issue by being 100MHz below the spec for now, I'll take it.
It's like my computer.. I have an i-7600k and GTX 580.. I play lot of stuff on max and a good deal of things I do don't peg the GPU or CPU to the max so other than just having the overheard, it's nothing to fret over for me.
For those that just care about benching and raw numbers, yeah it's an issue.
It's more so on a mobile device.. I just want a solid smooth experience with good battery life. We'll have to see how much battery life this adjustment does shave off, but if I can still get a full days usage out of it without having to run to a charger, I'm satisfied. Something like it now runs 9.5 hours instead of 10 hours would be fine by me.
Hopefully, they can mature the drivers and such to eek more performance without having to get the CPU to max out. I'd rather have that then to just have it run at 1400MHz. I'll take optimization over using raw power any day.
I'm a little loss here with the original poster?
You say you would just like the advertised speed, but 1.3 is the advertised speed of the Prime. With Honeycomb, that was all you got. It wasn't until ICS was released that we saw the 1.5 and 1.6 settings, no?
Anyhow, I think what Asus is doing here, is helping those people with tablets with mediocre cores that either cannot handle the lower frequencies while in deep sleep (sleep of death syndrome), and those who have reboots for no other apparent reason, other than there chips cannot handle a bit more juice. So to save face, they lowered back the max clock to the advertised speed, which was 1.3 on Tegra3, and up'ed the deep sleep speed to help alleviate any sleep of death syndrome's.
Like someone posted above, by the end of the month we should hopefully have the bootloader unlocked, the kernal source is already available, so custom kernals should follow, allowing those of us with chips that can go lower and higher those frequencies again.
Remember, this is nVidia, which has been known to release chips on the edge for the past several years! Asus does not make the Tegra3, they just oem it. Ultimately nVidia writes the core drivers, and Asus can modify them if need be, or add there "skin" to them. They have been doing this for years with graphic drivers.
Just like the framebuffer bug that is still in the new release firmware. This is a nVidia issue. Its there graphic driver, and they need to keep tweaking it until they get it right.
jyan_osu said:
For those that just care about benching and raw numbers, yeah it's an issue.
We'll have to see how much battery life this adjustment does shave off, but if I can still get a full days usage out of it without having to run to a charger, I'm satisfied. Something like it now runs 9.5 hours instead of 10 hours would be fine by me.
Click to expand...
Click to collapse
Um... OK, so, if you take the minimum power it can use... Multiply it by 4... And operate four times across all the cores...
This will not be a mere thirty minutes' difference. They apparently did this on 11.1 as well. Can anyone comment on 11? I had already noticed worse battery life but just hadn't thought about it. This is not ok! My device is draining so much faster while doing nothing...
Forget the upper end, OC'ing isn't even needed at this point. Everyone should be livid about the UC'ing, they're murdering our battery just to have it on standby!
1.4Hgz only cuts on when absolutely needed. It doesn't just cut on for hell of it just because you put it in Performance mode. It still stays lower clocked till you do something to need a higher clock. Plus the 1.4Ghz will only be on 1 core. Any other time you will get all cores at 1.3Ghz. Which better or more powerful than just [email protected] 1.4Ghz. People are to quick to jump to conclusions. They get CPU spy for the first time and see something then quick to jumpbto conclusions with nothing tobreally back it up. If you just messing around on home screen, of course the 1.4ghz speed isn't going to cut on. PLAY shadowgun or something n watch that speed easily cut on. Plus when 1.4ghz does cut on, its only briefly. Then other cores take over. Unless the game is taxing it enough to need it on longer.
This is nothing to be pressed about at all. People not understanding how these cores really work or how and when they cut on. Hasn't even been 24hrs. Since update n people already jumping to conclusions. If you so concerned about speed then use ATP tweaks to enable 1.6ghz overclock. Still works just fine n all speeds enabled.
---------- Post added at 09:38 AM ---------- Previous post was at 09:36 AM ----------
1BadHEMI said:
I'm a little loss here with the original poster?
You say you would just like the advertised speed, but 1.3 is the advertised speed of the Prime. With Honeycomb, that was all you got. It wasn't until ICS was released that we saw the 1.5 and 1.6 settings, no?
Anyhow, I think what Asus is doing here, is helping those people with tablets with mediocre cores that either cannot handle the lower frequencies while in deep sleep (sleep of death syndrome), and those who have reboots for no other apparent reason, other than there chips cannot handle a bit more juice. So to save face, they lowered back the max clock to the advertised speed, which was 1.3 on Tegra3, and up'ed the deep sleep speed to help alleviate any sleep of death syndrome's.
Like someone posted above, by the end of the month we should hopefully have the bootloader unlocked, the kernal source is already available, so custom kernals should follow, allowing those of us with chips that can go lower and higher those frequencies again.
Remember, this is nVidia, which has been known to release chips on the edge for the past several years! Asus does not make the Tegra3, they just oem it. Ultimately nVidia writes the core drivers, and Asus can modify them if need be, or add there "skin" to them. They have been doing this for years with graphic drivers.
Just like the framebuffer bug that is still in the new release firmware. This is a nVidia issue. Its there graphic driver, and they need to keep tweaking it until they get it right.
Click to expand...
Click to collapse
Yeah. Advertised speed is 1.3ghz on multiple cores n 1.4ghz on one, in performance mode.
Well said!
To be honest, I'm more concerned about the increase of idle speed and how it will affect battery life.
Just like they removed GPS from the product specs, they're going to have to ammend the "up to 18 hours battery life" part now too...
demandarin said:
1.4Hgz only cuts on when absolutely needed. It doesn't just cut on for hell of it just because you put it in Performance mode. It still stays lower clocked till you do something to need a higher clock. Plus the 1.4Ghz will only be on 1 core. Any other time you will get all cores at 1.3Ghz. Which better or more powerful than just [email protected] 1.4Ghz. People are to quick to jump to conclusions. They get CPU spy for the first time and see something then quick to jumpbto conclusions with nothing tobreally back it up. If you just messing around on home screen, of course the 1.4ghz speed isn't going to cut on. PLAY shadowgun or something n watch that speed easily cut on. Plus when 1.4ghz does cut on, its only briefly. Then other cores take over. Unless the game is taxing it enough to need it on longer.
This is nothing to be pressed about at all. People not understanding how these cores really work or how and when they cut on. Hasn't even been 24hrs. Since update n people already jumping to conclusions. If you so concerned about speed then use ATP tweaks to enable 1.6ghz overclock. Still works just fine n all speeds enabled.
Click to expand...
Click to collapse
Just cut it on
Even if it has absolutely zero impact on usability and battery life, i would still like a technical explanation from Gary as to why the frequency stepping was changed.
Keep in mind, a code change in the stepping could cause CPU spy to report incorrectly.
Probably because the devices worst about crashing would do so both at the lower and higher frequencies, so they just cut 'em both off.
Sent from my HTC Vision using xda premium
What do you mean "cut it on"?
demandarin said:
Just cut it on
Click to expand...
Click to collapse
seeknom said:
Well said!
To be honest, I'm more concerned about the increase of idle speed and how it will affect battery life.
Just like they removed GPS from the product specs, they're going to have to ammend the "up to 18 hours battery life" part now too...
Click to expand...
Click to collapse
It makes sense that there is a possibility they increased the idle speed to address sleep of death or screens not cutting immediately on. Or actually lowering the top speed to reduce random rebooted for reasons they can't figure out. I can see reading the idle speed. Lowering top speed seems unlikely. Even still people that are rooted who are that concerned with speeds can easily just use ATP tweaks or ViperControl to increase speeds. If someone concerned about increased idle speed or the lowest speed, then just use System tuner. Then set the lowest speed to what it was before. Be warned though, your device just might not wake up..lmfao. you can also experiment with the different modes n ATP tweaks, vipercontrol, or in system tuner. Just pay attention to what you doing and do stuff in increments.
---------- Post added at 09:56 AM ---------- Previous post was at 09:51 AM ----------
seeknom said:
What do you mean "cut it on"?
Click to expand...
Click to collapse
I just activated ATP tweaks turbo2 mode, which is 1.6Ghz overclock, to show other speeds enabled. That if someone really wants higher speed they can use this and then use system tuner to back off the Max speed to 1.4Ghz. This will override anything Asus might have possibly done. If they did reduce the speed there's probably a really good reason why. People can't have cake and eat it also. Rebooted n wake up issues resolved and highest speeds possible. So someone can simply manually enable higher speeds if its not activating long enough for you.
---------- Post added at 10:01 AM ---------- Previous post was at 09:56 AM ----------
tdrussell said:
Even if it has absolutely zero impact on usability and battery life, i would still like a technical explanation from Gary as to why the frequency stepping was changed.
Keep in mind, a code change in the stepping could cause CPU spy to report incorrectly.
Click to expand...
Click to collapse
True.....we will have to see. I'm not worried as methods I described can easily override Asus change. Plus I run on overclock most of the time anyways now. People have to tax the system more for a longer period of time to really know. Play some hardcore games and then check CPU spy. People swiping homescreens n think higher speeds will activate. It will only do so when needed.
(Scroll down to The Money Shot if you just wanna know the settings to use and skip all my preamble, but be aware that you may sacrifice results if you don't understand everything fully! You've been warned!!)
The Introduction
I'm about to tell you how to get buttery smooth, lag free performance with insanely good battery life, using an old school governor featured in practically every kernel... This tweak is applicable to every phone with any ROM or kernel--stock or custom--that provides the Interactive Governor. :good:
Yeah, yeah... everyone promises good battery with great performance, but who actually delivers? Maybe it isn't as smooth as you want, or maybe it requires something your kernel or ROM don't support. Or maybe the battery life promises just aren't what you expected. There's always some awful compromise. Not here!
This isn't a guide to get 36 hour battery life... provided you never use your phone. That's deep sleep optimization, which is lovely and all, but what good is the phone if you can never use it?! I'm talking about 7-14 hour screen on, actual hands-on usage times! Without compromising anything, you can get 7-8 hour screen on usage with regular, no-compromise usage habits: daytime visible screen brightness, both radios on, sync on, network location on, all the regular usage features, the whole kit and kaboodle... all smooth as a baby's butt and snappy as a Slim Jim! (Up to 14+ hours if you can stand minimum brightness and WiFi-only! And this is with stock voltages and full frequency range--you'll likely get even more if you choose to optimize those as well!)
However, it should be noted that this does not apply to gaming, heavy camera use, etc. Anything that is an automatic battery killer in and of itself. There's nothing that can be done about anything that forces the phone to utilize its maximum resources all the time. But you should know that by now. Further, this guide is about optimizing the CPU as much as possible. It does not cover things like eliminating wakelocks so your phone sleeps well, removing unnecessary and battery draining stock apps, keeping your screen brightness down*, and all that stuff that's been covered in other posts ad infinitum. Those optimizations are up to you.
*At least on the EvoLTE, you shouldn't be turning your screen brightness above about 60%. It should be more than viewable in sunlight at that brightness, and keep in mind that the brightness power requirements increase exponentially, so a 100% bright LCD screen will use about 3.5-4.5x more power than a 60% bright screen. I don't see that fact brought up often, so I thought I'd mention it here.
The Background
I got my first Android phone (Galaxy S4) about 8 months ago, and after dropping it in the toilet a couple months ago, I had to get something cheap. Enter the EvoLTE.
Performance on the EvoLTE was not what I was used to, and that disappointed me. (I should rephrase. Performance while getting similar battery life was disappointing. What good is a fast phone if you can't use it cuz it's dead?) While I had immediately caved and ROOTed and installed a new ROM (CM 10.2), I soon pined for a new kernel with promises of overclocking, under-volting, new fangled governors, etc.
So, I S-OFFed and installed Haunted Kernel. Played with overclocking, used the suggested governor (smartmax), under-volted, all that jazz. One problem: constant reboots. My focus shifted from performance and battery to just getting it to run reliably.
To my dismay, I learned that my phone has no tolerance for overclocking, so I lost that speed boost. Further, it has no tolerance for under-volting, so I lost that power savings. And then I discovered the recommended governor (which gave pretty good battery life and so-so performance) was too buggy to be reliable, so I lost that balance.
I was never fully satisfied with the performance of that governor. It promised a lot. People raved about it. It was certainly very power-friendly and lag free, but it stuttered. Notice how everyone promises lag free, but rarely do they talk about smoothness as things slow down. You know what I mean... quick scroll through a webpage or list, and as it slows down it hops and jerks. I hate, hate, HATE that! But hey, you can't have all three--smoothness, snappiness, and stutter-free... right?
Wrong! (But I'm getting to that!)
Shifting back to stock CPU settings (clock speed and voltages) I turned my focus to the governors. Surely, I thought, one of these other fancy governors will satisfy my needs. But after weeks of tweaking and testing, I had to make a compromise in one way or another. None of them delivered the results I wanted, no matter how I tweaked them. They were better than the standard governors in many ways, but still didn't meet my expectations. I sat there, so disappointed. All these cool features to boost performance, save battery, all that... out of my reach. I was back to square one. Stock speeds, stock voltages, basic governors...
Basic governors...
...basic governors...
...basic governors..?!
Well that's something I hadn't looked into much, I thought.
I mean, why bother? Either they keep your CPU at a low clock speed, or a high one, or slowly scale between the two, or jump quickly between the two. Pretty basic stuff. The new fangled governors were designed to more efficiently finesse these brute choices to improve performance and battery life, so what would basic governors have to offer?
Nothing, I thought. Until I looked at the kernel source and realized that the Interactive Governor had some advanced features I'd never seen anyone use in their recommended settings. On any forum. Ever.
That's not to say it's some well-kept secret or that I'm the first person in the world to post about such things. But it's certainly not widely known or promoted well. Most people just jump onto some new fangled governor with default settings to provide some features that, in all honesty, we can find in a governor featured in practically all kernels, and actually may out-perform the new fangled governor in both performance and battery life!
After a bit of tweaking and experimenting, I developed some settings that provide absolutely incredible battery life, buttery smooth performance, and a lag free experience. And you don't need a fancy governor, or a custom kernel, custom clock rates, or even an EvoLTE. This will work on any ROOTed phone with the Interactive governor!
Enough long winded preamble! Let's get down to...
The Nitty Gritty
Before I lay out all the settings so you can blindly enter them into your governor control, I should to explain some of the principals I employed to get the results I did. The primary thing to understand before I do is: little might you know, the settings in the Interactive governor can be tweaked on a clock range basis. That is to say, you can finely control how the governor responds at a variety of clock rates, thus better dictating how it should operate under various loads. This is integral to the configuration, because it means the difference between jumping from the slowest speed to the highest speed under load and sustaining lower clock speeds for tasks that don't really require higher clock speeds.
By default, the Interactive governor will jump from lowest speed to a "nominal" speed under load, and then scale up from that speed as load is sustained. That is lovely, but still too twitchy to provide serious efficiency and power savings. It spends most of its time at 2 or 3 clock speeds and barely hits other clock speeds that are ideal for other tasks or usage patterns.
Instead, what we want to do is configure it to handle different types of loads in different ways. A load suited for scrolling through a webpage is not the same as a load suited for decompressing streaming video is not the same as a load suited for snappy loading of an app is not the same as a load suited for high performance gaming. Every kind of load has different tolerances at which their minimal speed is indistinguishable from their maximal speed.
To understand what's best under a variety of tasks, we have to identify two types of load profiles: nominal clock rates and efficient clock rates.
Nominal Clock Rates
Nominal clock rates are the minimum CPU clock rates that perform a given task smoothly and without stuttering or lag. To find the nominal clock rate for a given task, turn on both cores using the Performance governor and turn them both down incrementally until you find the minimum clock rate that works best for what you're trying to do, without introducing hiccups, and multiply that clock speed by your number of cores.
For example, on my EvoLTE, scrolling (not loading, simply scrolling) through a large webpage smoothly will occur when the both CPUs clock rates are no less than 432Mhz. (This is on mine without background tasks taking any CPU. Yours may be different depending on services running, the browser you use, your ROM, kernel, etc.) Because the EvoLTE has 2 cores, we multiply 432Mhz * 2 = 864Mhz. Thus, the nominal clock rate for scrolling a webpage on my EvoLTE is 864Mhz.
Now, here's the rub. If you turn off one of the cores and turn the other core to 864Mhz, you will not find that it is smooth anymore. I will not write a dissertation regarding why this is the case. Suffice it to say, despite what is often incorrectly conveyed, multi-core usage is more efficient in multi-dimensional processing loads--such as rendering graphics, playing sound, or decoding video--than a single core's performance because the time spent at a given clock rate is non-linearly less than if it were processed on a single core at a higher frequency. We want a balance of battery life and performance, and that requires using both cores. The other core will kick on when necessary to "fill in the gaps" under such a load, so our measurement stands. For our purposes, the nominal frequency for a given task is the sum of the frequencies of all cores always on at a given clock rate.
Efficient Clock Rates
Efficient clock rates are CPU clock rates that are unique in that they are the most optimal frequency given the range of voltage requirements. If you map out the frequency jump and the voltage requirement jump between each of the available clock rates, you will find that occasionally the voltage requirement will jump significantly without the frequency jumping proportionally to the previous differentials. For example, using stock voltages, the EvoLTE's msm8960 chipset clock/voltage ratios jump significantly higher from 702Mhz to 810Mhz than the ratios from 594Mhz to 702Mhz.
Using stock voltages, the EvoLTE's efficient clock rates are:
384Mhz
702Mhz
1026Mhz
1512Mhz
These are the clock rates that are at the top tier of each of their voltage ranges, before each anomalous ratio jump. These are the most voltage efficient clock rates using stock EvoLTE voltages. If you are using a custom kernel or have changed your voltages (or a totally different phone altogether), your efficient clock rates may be different. Calculate them as applicable to your setup! List the clock rate differences between each frequency step and the differences for each frequency's voltages. You will see an anomalous voltage jump every several frequency steps. The frequency before this jump is the next efficient clock rate. Write it down and keep going through the frequency steps until you have exhausted them.
Clock Rate Biases
Using the information provided above, figure out both your nominal clock rates for the tasks you perform most often and your efficient clock rates depending on your kernel/custom voltage settings. For me, since I am using stock voltages, I use the efficient clock rates listed above. For the tasks I generally perform on my phone, my nominal clock rates are as follows:
Idle - 189Mhz
Page Scrolling - 864Mhz
Video - 1134Mhz
App Loading - 1350Mhz
High Load Processing - 1512Mhz
(Note that my nominal idle speed is less than stock. This is why you must calculate the values that are optimal for your phone for best battery and performance! Each phone is different because of the ROM, kernel, background tasks, etc!)
Once you've listed all of your nominal clock rates, try to consolidate them if you have more than 3. (This is not entirely necessary as you'll see later, but it simplifies things significantly until you're more comfortable dictating more than a few clock rates for your needed task loads.) If you have any tasks that rest in the far upper portion of the frequency spectrum, discard them! We are by no means underclocking anything, but we are trying to keep the CPU clock rate as low as possible for as long as possible. However, the fastest frequencies will be available for sustained load processing, as you will see later. In my case, in addition to discarding the "high load processing", I'll sacrifice a (very) little app loading speed and consolidate video and app loading:
Idle - 189Mhz
Page Scrolling - 864Mhz
Video/App Loading - 1134Mhz
With this done, you will want to start the fine tuning phase! Correlate the efficient clock rates with their closest nominal clock rates, similar to below:
Idle - 189Mhz efficient / 189Mhz nominal
Page Scrolling - 710Mhz efficient / 864Mhz nominal
Video/App Loading - 1026Mhz efficient / 1134Mhz nominal
Keep these handy, as they're going to be necessary for...
The Set Up
Now that we know what are the most efficient clock rates we want to focus on and what the most optimal are for what we want to do, we will start low and scale up as necessary. It's always better to begin with underperforming and tweak the settings upward until we're satisfied with the performance of our target tasks.
In its default state, the Interactive governor has a hair trigger that will raise and lower the clock rates, which means it spends too much time at unnecessary clock speeds, wasting power, and scales down too quickly, leading to stuttering performance. We will take advantage of a seldom used feature of the Interactive governor. Specifically, that with which it determines when it is okay to scale up to each higher clock rate, on a frequency by frequency basis.
We have two primary goals: respond as quickly as possible to each load request for a lag free experience and exceed the desired clock rate for a given task as little as possible. To do this, we will instruct the Interactive governor to trigger certain clock rates in different ways depending on our expected load.
I won't explain all of the settings of the Interactive governor--there are plenty of summaries all around. (Go search now if you don't know what any of the settings for Interactive governor do. I'll wait here.) However, I will explain an incredibly powerful feature of the Interactive governor that is rarely included in those summaries: multiple frequency adjustments.
The above_highspeed_delay setting, for example, defines how long the governor should wait before escalating the clock rate beyond what's set in highspeed_freq. However, you can define multiple different delays that the governor should use for any specified frequency.
For example, we want the above_highspeed_delay as low as possible to get the CPU out of the idle state as quickly as possible when a significant load is applied. However, we don't want it to jump immediately to the fastest clock rate once it's gotten out of idle, as that may be overkill for the current task. Our target trigger (which you will later adjust to suit your system and usage profile), will begin at 20000μs. That means 20,000μs (or 20ms) after our idle max load has been reached, we want to assume idle has been broken and we want to perform an actual task. (We want this value as low as possible without false positives, because it is one of a few factors that determine how snappy and lag free the CPU's response is.)
But at this point we're not ready to take on a full processing load. We may just be briefly scrolling a webpage and don't need the full power of the CPU now that we've allowed it to break out of idle. So we need it to reach a particular frequency and then hold it there again until we're sure the load is justified before we allow it to push the frequency even higher. To do that, rather than just setting
above_highspeed_delay - 20000
we will instead use the format "frequency:delay" to set
above_highspeed_delay - 20000 702000:60000
"Waaaait... What does that do?!"
This tells the Interactive governor to hold out 20ms after our target load when it's at our highspeed_freq (which we're actually using as our idle frequency--not a burst frequency as originally intended), but then it tells the governor to hold for 60ms after it's reached 702Mhz. (If you don't know what I'm talking about when I say "highspeed_freq" then you didn't go search for the basic Interactive governor settings and read about it! Go do that before you read any further, because I will not explain the basics of this governor!)
So now that we know how to specify different settings for different frequency ranges, let's finish it all up with...
The Money Shot
If you've made it this far, you're ready to put these strategies into play! If you have not read the previous sections, DO NOT COMPLAIN IF THE DEFAULT SETTINGS DON'T PROVIDE WHAT YOU'RE LOOKING FOR!! These settings are templates only and these need to be adjusted for each case based on your system and usage patterns! IF YOU ARE NOT GETTING THE PERFORMANCE OR BATTERY LIFE PROMISED, ***READ THE SECTIONS ABOVE!!!***
With that out of the way... let's rock!
If you are using an EvoLTE, use the following Interactive governor settings and then tweak with the instructions below:
(If you are using a phone other than an EvoLTE, you must read the above sections and replace the frequencies with your own efficient clock rates!)
above_highspeed_delay - 20000 702000:60000 1026000:150000
boost - 0
boostpulse_duration - 80000
go_highspeed_load - 99
hispeed_freq - 384000
io_is_busy - 0
min_sample_time - 40000
target_loads - 98 384000:40 702000:80 1026000:95
timer_rate - 30000
timer_slack - 80000
These defaults work fine for me, but I have otherwise optimized my system fully, so they are at the minimal adequate values. If you have background tasks that consume any somewhat significant amount of CPU on a constant basis, you will most likely see awful, stuttery performance and poor battery life! So you must adjust them to suit your system before you see results!!! Anything more than about 15-20% idle CPU use at any given time will negatively affect the results you see without further tweaking!
Optimize Idle Frequency
Now that you've got the base configuration, we need to tweak it so that the CPU stays at your efficient idle frequency (384Mhz in this case) without spontaneously jumping when your phone is actually idle. To do this, open a CPU monitor that displays the current core frequencies (I like CoolTool, but you can use what you like as long as it doesn't significantly impact the CPU use--you're best off using a passive monitor and checking the results after 30-60 seconds of no activity), watch the frequencies and see how often they go above your efficient idle frequency when you're not doing anything at all, and adjust the following:
timer_rate - If your idle frequency is not being exceeded much, adjust this downward in increments of 5000 until it is, then increase it by 5000. If your idle frequency is being exceeded often, adjust this upward in increments of 5000 until your CPU primarily stays at or below your desired idle frequency.
above_highspeed_delay - Only if your timer_rate has matched or exceeded 50000 and still won't stay at or below your desired idle frequency most of the time, set timer_rate to 50000 and adjust the "20000" portion of the value upwards in increments of 5000 until the idle frequency has stabilized.
The lower these two values are, the more snappy/lag free your system will be. So try to get them as low as possible without the idle frequency being exceeded too much, as this inversely affects the snappiness and efficiency of your phone when you're not doing anything. Lower = snappier but uses more CPU when you're not doing anything (such as reading a webpage); higher = less snappy but stays in a power saving state more often reducing CPU use when you're not interacting with the device. These are the most critical in determining your idle power savings, so keep that in mind if you want the most battery life!
Enhance Task Responsiveness
Now use the efficiency and nominal clock rate correlations you made for your master clock rate list in the section above and adjust your frequencies to suit your usage patterns. For example, I had web page scrolling as my 710Mhz/864Mhz rates, so I will open a web page and scroll and see how everything feels. If it feels sluggish, I will increase all the references to "710000" in both above_highspeed_delay and target_loads upwards to the next available clock rate until that task is smooth. What you are looking for is constant poor/sluggish performance when the task you're testing for is using its highest CPU use. If the task becomes sluggish/stuttery as it winds down (such as a scrolling webpage slowing to a stop), we will address that next, so do not take that behavior into consideration as you adjust these values! If the task is smooth until (or after) it slows down, then you have reached your optimal clock rate and can move on.
If you need to exceed your nominal clock rate for a particular task, first measure it again just to be sure you had it correct. If you did indeed have it correct, leave it at your nominal clock rate and adjust the value after the colon next to the task frequency you're tuning downward in increments of 5. For example, if my setting of "864000:80" is still not sufficient, I will adjust it first to "864000:75", then "864000:70", and so on until the task is smooth. However, it almost certainly won't come to this, but if you reach ":50" and the task still isn't performing how you want, set it back to ":80" and increase the clock step once more, then decrease the ":80" until it is smooth.
Do the same for each other frequency in your master clock rate list until you are satisfied. If you have chosen to use more than 2 primary clock rates, add them and use ":##" values between the two surrounding frequency values.
Fix Stuttering
Now that you have adjusted your frequencies for optimal high CPU use in each given task, you may notice some stuttering as the task winds down. (Such as a scrolling webpage slowing to a stop.) If this bothers you, you can tweak this at the expense of some (minor) battery life by adjusting min_sample_time up in increments of 5000 until you are satisfied.
If you have exceeded a value of 100000 for the min_sample_time setting and still are not satisfied, change it back to 40000 and increase (and re-optimize) your idle frequency by one step. This will impact battery life more, but less than if you were to keep increasing the value of min_sample_time.
Adjust High Load Clock Rates
You're almost done! Now you can leave everything as is and be satisfied with your amazing, buttery smooth, snappy experience, or you can optionally tweak things further to either increase the responsiveness of high load tasks (such as loading image previews in Gallery) or increase battery life somewhat.
Adjust the final delay value in above_highspeed_delay to suit your needs. The default ("150000") means that the CPU load at the highest set frequency (default "1026000") will have to be sustained for 150ms before it allows the load to go above that frequency. Increasing this value will prevent the CPU from reaching higher frequencies (which may be unnecessary) as often, saving battery life. This will come at the expense of burst-type high CPU load tasks. Reducing it will allow the CPU to reach higher frequencies more often, at the expense of battery life. However, adjusting this is probably unnecessary, as it will most likely not yield any perceptible difference in performance. It is recommended to leave this value at its default.
The Conclusion
I have achieved unprecedented performance, smoothness, snappiness, and battery life with the default settings I outlined above. However, your mileage may vary, as every phone, ROM, kernel, installed applications, etc are different. This is a very sensitive governor profile and must be tweaked to just meet the requirements of your system and your usage patterns!
If it is not optimally tuned, performance and battery life will suffer! If you're not seeing buttery smooth, snappy performance, you have not correctly tuned it for your system!! However, if you do have superb performance (and you tweaked the values conservatively and not in large steps), then you will also get the aforementioned battery life.
I will be happy to answer any questions, or provide any guidance I can. However:
You must otherwise optimize your phone first! This will not "fix" a poorly optimized system and will, in fact, reduce performance and battery life without further optimization and proper tweaking.
I will not answer questions about "what is a governor?" There are plenty of resources available already, so search for them.
I will not answer questions about "how can I tweak [some other] governor?" This is about the Interactive governor only.
I will not respond to "nuh uh! show proof!" posts. The fact that I spent 12 hours writing this up should be proof enough that I am satisfied with the results. You can take it or leave it; makes no difference to me. The default settings should work with any fully optimized EvoLTE, so just try them on your own. If you're not absolutely satisfied (and trust me, either it'll work out-of-the-box with flying colors and you'll know it works for your system, or it'll be an awful experience which means you must tweak it), then you haven't adequately adjusted the settings to suit your system.
Lemme know what you think, and good luck!
Really nice write up! Easy to read and understand. One question, how exactly are you changing the above high-speed delay. I input exactly but when I save and go back it's bank only to 20000
Sent from my EVO LTE using XDA Premium 4 mobile app
Great article!
jmkarnai01 said:
Really nice write up! Easy to read and understand. One question, how exactly are you changing the above high-speed delay. I input exactly but when I save and go back it's bank only to 20000
Sent from my EVO LTE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was wondering the same thing.
jmkarnai01 said:
Really nice write up! Easy to read and understand. One question, how exactly are you changing the above high-speed delay. I input exactly but when I save and go back it's bank only to 20000
Sent from my EVO LTE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I use the the fku updater app the paid version and all my settings stick on my g3 and my m8
Nice write up. Just the sort of info I've been looking for
Well done sir
Great information here!
Finally someone makes complete guide on this governor
hello..i am not an advanced user like you guys..great work !..i try my best to understand,i read threw every word,even though i dont have your device.i am useing a htc m8 on sprint..i flashed the kernal after reading all about it..i do want amazeing battery life,i work all the time,constantly networking and listening to music,useing data all the time really,i understand these things will kill battery no matter what..i also know you said if we have abother device other than the evo the device you laid out exact settings for,we would have to tweak on our own..and without you haveing the device i have im sure be hard to give some advice..couple questions?- 1.)if i just use default settings,and change nothing will it benifit me at all,or did i just flash the kernal for nothing,since im not advanced enough to really tweak kernal on my own..2)is there anyway possible to get exact instrutions for my device like you gave for the evo...just wanted to add how lucky users of that device are for you to of givein these details,you seem to of really mastered that device..thanks for hard work either way..if i cant get nothing out of this,its ok i can allways just wipe device and restore back up without the kernal installed...
Very nice, well-written guide. Thanks a lot!
@soniCron: How do I turn on and of cores one by one? I have quad core.
Hi soniCron, I just wanted to let you know that I followed your guide and tweaked my OnePlus One. Great results so far, and stellar battery life. I'm very happy with it, thanks
Phazonclash said:
Hi soniCron, I just wanted to let you know that I followed your guide and tweaked my OnePlus One. Great results so far, and stellar battery life. I'm very happy with it, thanks
Click to expand...
Click to collapse
Can you share your changes/parameter settings?
Maybe via pm if not using the thread?
solar666 said:
Can you share your changes/parameter settings?
Maybe via pm if not using the thread?
Click to expand...
Click to collapse
above_hispeed_delay 20000 652800:20000 1190400:40000 1497600:60000 2265600:80000
boost 0
bootpulse duration 80000
go_hispeed_load 99
hispeed_freq 652800
io_is_busy 0
mac_freq_hysteresis 10000
min_sample_time 60000
target_loads 98 652800:40 1190400:70 1497600:80 2265600:90
timer_rate 30000
timer_slack 40000
How the lemon does this guide only have 2 pages?
Great guide, thanks a lot, going to try it with my oneplus one now
thewind730 said:
I use the the fku updater app the paid version and all my settings stick on my g3 and my m8
Click to expand...
Click to collapse
Can you share please your M8 settings and tell if it really had an impact on performance and battery life. Thanks.
Also I cannot save the edited parameters files under /sys/devices/system/cpu/cpufreq/interactive although I have full root. Any suggestions? I have an HTC One M8 with ViperOneM8 4.3, rooted and S-Off.
Sent from my HTC One_M8 using Tapatalk
tghandour said:
Can you share please your M8 settings and tell if it really had an impact on performance and battery life. Thanks.
Also I cannot save the edited parameters files under /sys/devices/system/cpu/cpufreq/interactive although I have full root. Any suggestions? I have an HTC One M8 with ViperOneM8 4.3, rooted and S-Off.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Sent from my HTC One_M8 using Tapatalk
I'm testing this guide on my LG G2 and it seems to work pretty well.
Good job :good:
Awesome! I just tweaked mine now to the lowest frequencies that is lag free and will check tomorrow if battery life of my htc one m9 has improved somehow.
Also you might want to add this link to kernel cpu governor documentation. Which pretty much explains the other variables.
tghandour said:
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Can u share ur m8 settings to try out please...... Thanks
HTC m8 on arhd 43 using dark blue Tapatalk from jokerpoker1