A lo of galaxy Nexus users use the freq 729/1*00. Why?
Inviato dal mio Galaxy Nexus con Tapatalk 2
? not sure what you mean
some kernels have the ability to change frequency, but most have a range of 320-1320. using the lower frequency saves battery
StormIceX said:
A lo of galaxy Nexus users use the freq 729/1*00. Why?
Inviato dal mio Galaxy Nexus con Tapatalk 2
Click to expand...
Click to collapse
I don't know why they would clock it that high for minimum freq unless they like low battery life or is using a 4000mAh battery.
I use 192/1024 with the 'conservative' governor.
The CPU is one of the most power efficients components on smartphones and most frequency/voltage tweaks don't go beyond the placebo zone. Your priority for a reasonable and enjoyable use should be performance, since undervolting/underclocking doesn't really do much as far as battery goes.
Just take a look at an application like CPUSpy and see how much time your phone spends at the highest frequencies.
For most governors, state time at max frequency is well under <10% of the total time and the difference of voltages is around 300 mv (from ~900 to ~1200 mv at max frequency) so, in my opinion, battery savings obtained by using a lower max frequency are minimal, if existant. On the other hand, it does have a performance hit. Therefore, I use 1350 mhz as max frequency; I would use a higher one but I find it to heat up the phone quite a bit while using it.
Now, there are things that actually influence battery. The screen is by far the biggest battery hog. By using autobrightness (and tweak it to lower levels through CM9) I find that you can get a really good balance between power savings and readability.
Another significant battery hog is a persistent data connection (in my case HSPDA/3G). If you take the time to set the phone to 2G during idle periods you also get a nice battery saving. Wi-Fi isn't really a variable to me because I find it to have a really low idle drain.
You can also try to turn on Airplane Mode when you go to sleep (only if you don't charge it during sleep, that is), because it has a very low idle drain and it's perfect to keep juice for the next day.
Hope some of my tips follow through!
It is known that using a higher min freq saves battery because it takes less time for the cpu to complete the tasks it has been asigned to do.
Others think that they dont get signal drops if they dont use 350 step, when it probably happens because of insuficient voltage.
Sent from my Transformer Prime TF201
bk201doesntexist said:
It is known that using a higher min freq saves battery because it takes less time for the cpu to complete the tasks it has been asigned to do.
Others think that they dont get signal drops if they dont use 350 step, when it probably happens because of insuficient voltage.
Sent from my Transformer Prime TF201
Click to expand...
Click to collapse
I agree. I get 5-7h screen on time and i have 729mhz min freq. 2000 mah battery.
jnr21 said:
I agree. I get 5-7h screen on time and i have 729mhz min freq. 2000 mah battery.
Click to expand...
Click to collapse
{
"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"
}
I get 4:30 hours with 350/1200 and wheatley governor platino with fpse, riptide gp and Temple run about 1:30h, 3g on, Facebook and tapatalk. No undervolt. If i set 749/1200 i can have more screen on time?
Inviato dal mio Galaxy Nexus con Tapatalk 2
StormIceX said:
View attachment 1100575
I get 4:30 hours with 350/1200 and wheatley governor platino with fpse, riptide gp and Temple run about 1:30h, 3g on, Facebook and tapatalk. No undervolt. If i set 749/1200 i can have more screen on time?
Inviato dal mio Galaxy Nexus con Tapatalk 2
Click to expand...
Click to collapse
Dunno, every phone is different.
If you used a higher minimum frequency you would enhance the race to idle process (deep sleep). Unfortunately I don't think anyone knows where the cutoff is, since it's a balance between frequency, voltage and task load which is hard to objectively measure and therefore calculate the optimal frequency.
In my experience, 700 mhz is just fine for minimum frequency as well, without any noticeable impact in battery (for the better or the worse). It has one downside though, which are low power continuous tasks such as listening to music in which you'll keep your phone awake at 700 mhz when you could do the same task at a lower frequency. On the other hand, a minimum frequency of 700 mhz does make the phone smoother when waking up, etc...
My personal belief is that you should pick the frequencies according to the governor you're using. In conservative, a minimum of 700 mhz is a good idea. In interactive, specially in some custom kernels where it scales more agressively (CMPlus, Leankernel, for instance), you can keep a minimum of 350 mhz without any impact on performance. In wheatley (Ezekeel), I really don't know since it potentiates the use of C4 states which I don't completely understand, but Ezekeel is so smart that you might as well just trust his defaults blindly
About signal drops, as bk201doesntexist mentioned, it's probably fixable by increasing the voltage at the minimum frequency (disabling smart reflex). I used to have that issue with smartreflex on, but it was fixed in the last update. YMMV.
I run my min at 192 and my phone never lags never slow and still deep sleeps within like 10 seconds of screen off. Honestly its whatever you like I believe. I see no difference is smoothness or performance with it at 192 or 700.
Sent from my Galaxy Nexus using Tapatalk 2
Gahh Its Lee said:
I run my min at 192 and my phone never lags never slow and still deep sleeps within like 10 seconds of screen off. Honestly its whatever you like I believe. I see no difference is smoothness or performance with it at 192 or 700.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You don't see it because it's unlikely that when the screen is on your phone ever falls back to 192 mhz, since the minimal task would exceed the load threshold for that step (depends on the governor ofc). Probably the only diference you'd eventually notice would be a slow wake up or some jitterness in the first one or two seconds.
On the other hand, with a 700 min you can notice in an app like CPUSpy that the phone rarely spikes to the maximum frequency because 700 mhz can handle most loads effectively.
I personally don't believe in battery optimizations just by undervolting/underclocking, it's just too minimal of a effect for an already very efficient component...But it's a fun discussion nonetheless
---edit
CMPlus @ Interactive Governor
Use Profile: mostly idle, lots of background music listening, ~2 hours of music in the bg, ~1h of screen on time
You can see that the maximum frequency is hardly a variable here since it only occupies a mere 7 minutes in over 70 hours. The true "muscle" is the 700 mhz slot, that buffers most of the load instead of jumping to the highest frequency (which it still does, but for a very short amount of time)
better performance,better battery life and no data drops
Sent from my Galaxy Nexus using xda premium
dreamhunterr said:
You don't see it because it's unlikely that when the screen is on your phone ever falls back to 192 mhz, since the minimal task would exceed the load threshold for that step (depends on the governor ofc). Probably the only diference you'd eventually notice would be a slow wake up or some jitterness in the first one or two seconds.
On the other hand, with a 700 min you can notice in an app like CPUSpy that the phone rarely spikes to the maximum frequency because 700 mhz can handle most loads effectively.
I personally don't believe in battery optimizations just by undervolting/underclocking, it's just too minimal of a effect for an already very efficient component...But it's a fun discussion nonetheless
---edit
CMPlus @ Interactive Governor
Use Profile: mostly idle, lots of background music listening, ~2 hours of music in the bg, ~1h of screen on time
You can see that the maximum frequency is hardly a variable here since it only occupies a mere 7 minutes in over 70 hours. The true "muscle" is the 700 mhz slot, that buffers most of the load instead of jumping to the highest frequency (which it still does, but for a very short amount of time)
Click to expand...
Click to collapse
Actually my 192 was in use over twice as often as Max or anything else but I'm gonna try 700 since I was at 1350 for 25% of my time awake.
Sent from my Galaxy Nexus using Tapatalk 2
dreamhunterr said:
You don't see it because it's unlikely that when the screen is on your phone ever falls back to 192 mhz, since the minimal task would exceed the load threshold for that step (depends on the governor ofc). Probably the only diference you'd eventually notice would be a slow wake up or some jitterness in the first one or two seconds.
On the other hand, with a 700 min you can notice in an app like CPUSpy that the phone rarely spikes to the maximum frequency because 700 mhz can handle most loads effectively.
I personally don't believe in battery optimizations just by undervolting/underclocking, it's just too minimal of a effect for an already very efficient component...But it's a fun discussion nonetheless
---edit
CMPlus @ Interactive Governor
Use Profile: mostly idle, lots of background music listening, ~2 hours of music in the bg, ~1h of screen on time
You can see that the maximum frequency is hardly a variable here since it only occupies a mere 7 minutes in over 70 hours. The true "muscle" is the 700 mhz slot, that buffers most of the load instead of jumping to the highest frequency (which it still does, but for a very short amount of time)
Click to expand...
Click to collapse
I think the bigger question is.. how did you only touch your phone for an hour out of 70?
Sent from my Galaxy Nexus using xda premium
joshnichols189 said:
I think the bigger question is.. how did you only touch your phone for an hour out of 70?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Well, a total of 1 hour of screen on and 2 hours of music in the background and some phone calls lol.
It's simple, I'm studying at home and I do most of my web stuff on an iPad 3 which I've recently bought. In retrospective, if I had known I was going to buy an iPad 3 I wouldn't have invested this much on a high end Android phone
dreamhunterr said:
Well, a total of 1 hour of screen on and 2 hours of music in the background and some phone calls lol.
It's simple, I'm studying at home and I do most of my web stuff on an iPad 3 which I've recently bought. In retrospective, if I had known I was going to buy an iPad 3 I wouldn't have invested this much on a high end Android phone
Click to expand...
Click to collapse
Your nexus just called me..
she's sad you've replaced her haha
Related
I know unrooted desire z devices always work at 800mhz. My device is set to 245mhz min and 1400mhz max (interactive or smartass governor). It sometimes causes my device to wake up a bit late. I wonder how long time my battery goes if I set my device at min 800 mhz and max 1200 or 1400 mhz... Did anyone try this clock speeds?
Deadly Sto(R)m said:
I know unrooted desire z devices always work at 800mhz. My device is set to 245mhz min and 1400mhz max (interactive or smartass governor). It sometimes causes my device to wake up a bit late. I wonder how long time my battery goes if I set my device at min 800 mhz and max 1200 or 1400 mhz... Did anyone try this clock speeds?
Click to expand...
Click to collapse
That's way too low of a min speed, just bump it up to the next (I think it's 386) and you should see noticable improvement.
I'd also suggest the ondemand gov; since it only ramps up to the top speed when needed, then drops it back down again, you should get a bit better battery life.
Sent from my HTC Vision using XDA App
OriginalGabriel said:
That's way too low of a min speed, just bump it up to the next (I think it's 386) and you should see noticable improvement.
I'd also suggest the ondemand gov; since it only ramps up to the top speed when needed, then drops it back down again, you should get a bit better battery life.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
i read ondemand and conservative governors are od, so using interactive or smartass are better then using others. I will try min 368 mhz but am not sure if it works...
What are you trying to accomplish by messing with the clock speed? Leave it alone at default. Performance difference is NEGLIGIBLE (bottleneck is elsewhere), and all you'll accomplish is eating the battery and burning it up with excessive heat caused by excessive clock.
dhkr234 said:
What are you trying to accomplish by messing with the clock speed? Leave it alone at default. Performance difference is NEGLIGIBLE (bottleneck is elsewhere), and all you'll accomplish is eating the battery and burning it up with excessive heat caused by excessive clock.
Click to expand...
Click to collapse
First of all, I would like to thank you for your comments.
People don't do anything to access root if they don't want to mess device. I am one of them and want to have a device which both has performance and visuality. You offered me to not to change clock speeds. But we know HTC Desire Z is scheduled to work at 800mhz everytime (default). My opinion is just to set minimum clock speed to 800 mhz or something like this. If my device was burn by this clock speed, it was already dead.
Today i tried this clock speed (min 614, max 1382) and during the day it didn't heat up. Moreover, 8 hours passed, i played NFS for about 1,5 hour, made some call and 30 percent of battery left. It seems this clockspeeds doesn't cause battery drain or i couldn't feel it...
EDIT: 13 hours passes, 16 percent battery left (I made minimum 30 minutes of call)
How safe is it to overclock my Galaxy S II to 1.78 max and 1.78 min?
If not, what combination of max and min would be most safe but still give a noticeably boost in speed.
In theory overclocking isn't that good as is adding additional strain to the CPU than it was designed to.this will cause wear and tear faster possibly shortening the life of your phone. I would set your min much lower and place it on demand. There's no need for your CPU to be running at max all the time, set it on demand do it only runs at a faster speed when it's needed to...
PS this has been covered in other threads a search would have given you an answer oppose to starting another thread.
Sent from my SGH-T989 using XDA App
Voltage kills components, not overclocking.
You can google this and research it if you would like.
I keep mine min 810 max 1782 ondemand with setcpu.
810 is more than enough(still faster than Iphone4) to hold its own without lag when you actually start to bog it down.
I think the max itll go is 1.83ghz. in reality nothing over 1.65ish really adds anything.
Sent from my SGH-T989 using XDA App
locked mine at 1.51ghz which is plenty of fast, no throttling and no lag
Setting the min up that high will kill your battery in hours. You can over clock it by setting the max up to whatever you like. Set the min lower. Then set your governor. Overclocking will wear down your cpu faster and make it run hotter. Overvolting will do the same. I would only overclock when I need it. Normally mine is set at 1.5 for max and .3-.5 for min.
As many of you know, battery life on the One X has been lets say, poor.
I decided to narrow down the problems and try to figure out whats causing it.
I figured i'd download voltage control (SetCPU works also) and underclock the CPU, low and behold......I may have figured out why the battery was dropping so much during screen on standby.
ONDEMAND GOVERNOR!!! It was causing crazy CPU instability. The CPU was constantly changing from 340mhz to 1500mhz (or your max speed) every single second, alternating constantly.
I've changed it to Interactive and it's been much more stable now. When not doing anything, the CPU will stay at 340mhz and no longer constantly ramps up to maxx CPU speed and back down alternating.
Try this out and see if it helps you guys. I'm going to continue experimenting with the other governors, but Interactive should be the best blend between battery and performance.
Also download CPU spy to see what steps of the Speeds have been active the most.
Edit: Changing the frequencies does not do anything sadly. Will need to wait for VoltageControl and SetCPU to be updated.
BUT changing the governor does work and makes a big difference.
Going to Interactive, my battery no longer drains at around 1% for every 1-2 minutes of screen on time leaving the screen on and idle. It drains much more normally.
Tonight I will do the HTC test where you check how much battery drains for 1 hour of screen on time at max brightness. You may feel free to try it out using the dialer *#*#3424#*#* and running battery test.
I will do this tonight and upload my results/screenshots
Update:
Here are the two main tips that I have found out now to help a lot with battery and low CPU usage that is stable
1) Use Interactive Governor, it is less aggressive at ramping up to max frequency and much more efficient. Also more stable and not erratic like OnDemand Governor
2) USE APEX LAUNCHER or something besides Sense Launcher.
I have downloaded Tegrastats to show me CPU usage and have compared between Sense Launcher and Apex. Sense is very resource hungry, and CPU usage is very high. It is almost constantly has both cores turned on and usage fluctuates between 15-70% alternating on the two cores when screen is on but idle. The frequency also stays around 400mhz on idle.
Apex launcher on the other hand, uses 1 core when idle, and usage stays around 10%. It also hovers around 102-204mhz when screen is on but idle. When swiping as fast as possible to ramp up speeds, I haven't seen it go above 640mhz and usage between the two cores is around 30-50% EVEN with both cores vs. alternating 15-70% on both cores with Sense Launcher
Thanks mate
Strange, from what I remember any CPU-tool didn't have any impact on my governor and cpu behavior. Maybe this has changed with the update. So I will have another go
(Just put it on its 7th charge, gotta wait a while..)
pewpewbangbang said:
As many of you know, battery life on the One X has been lets say, poor.
I decided to narrow down the problems and try to figure out whats causing it.
I figured i'd download voltage control (SetCPU works also) and underclock the CPU, low and behold......I may have figured out why the battery was dropping so much during screen on standby.
ONDEMAND GOVERNOR!!! It was causing crazy CPU instability. The CPU was constantly changing from 340mhz to 1500mhz (or your max speed) every single second, alternating constantly.
I've changed it to Interactive and it's been much more stable now. When not doing anything, the CPU will stay at 340mhz and no longer constantly ramps up to maxx CPU speed and back down alternating.
Try this out and see if it helps you guys. I'm going to continue experimenting with the other governors, but Interactive should be the best blend between battery and performance.
Also download CPU spy to see what steps of the Speeds have been active the most.
Click to expand...
Click to collapse
What have you set your min frequency to? I take it 340?
Sent from my HTC One X using xda premium
pewpewbangbang said:
As many of you know, battery life on the One X has been lets say, poor.
I decided to narrow down the problems and try to figure out whats causing it.
I figured i'd download voltage control (SetCPU works also) and underclock the CPU, low and behold......I may have figured out why the battery was dropping so much during screen on standby.
ONDEMAND GOVERNOR!!! It was causing crazy CPU instability. The CPU was constantly changing from 340mhz to 1500mhz (or your max speed) every single second, alternating constantly.
I've changed it to Interactive and it's been much more stable now. When not doing anything, the CPU will stay at 340mhz and no longer constantly ramps up to maxx CPU speed and back down alternating.
Try this out and see if it helps you guys. I'm going to continue experimenting with the other governors, but Interactive should be the best blend between battery and performance.
Also download CPU spy to see what steps of the Speeds have been active the most.
Click to expand...
Click to collapse
I`m not seeing this at all.My phone has been on standy for a few hours..wifi on/auto sync on..ondemand governor.Battery loss about 4% in 3 hours. CPUspy reports no high frequency spikes..highest shown is 475MHz.
I believe in ARHD mike has already set to Interactive Governer.
Set CPU doesn't work it will still go over the max set. I have contacted the maker and he is looking into it hard without kernel sources. Screen shot
{
"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"
}
Sent from my HTC One X using xda premium
ttav said:
I`m not seeing this at all.My phone has been on standy for a few hours..wifi on/auto sync on..ondemand governor.Battery loss about 4% in 3 hours. CPUspy reports no high frequency spikes..highest shown is 475MHz.
Click to expand...
Click to collapse
You have got the best one.
Sent from my HTC One X using Tapatalk 2
I wouldn't lose battery with screen off. But with the screen on and not doing anything. Just watching the speeds in voltage control I watched it constantly alternate with 340 and 1500.
My min is the lowest I can set, around idk 50? I don't remember. But it doesn't go that low unless screen off standby. Probably for companion core.
This is just to let people know that ondemand governor acts funky and interactive is probably the best to use.
Sent from my HTC One X using XDA
treebill said:
Set CPU doesn't work it will still go over the max set. I have contacted the maker and he is looking into it hard without kernel sources. Screen shot
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Sadly true. Don't know how these other people can claim that it's working.
Fruktsallad said:
Sadly true. Don't know how these other people can claim that it's working.
Click to expand...
Click to collapse
Use voltage control, it's free from the play store.
You can tell the difference between OnDemand and Interactive or w/e governor you choose. OnDemand not touching the screen, you can watch in VoltageControl it alternates constantly between your max CPU and 340mhz (This is about the lowest it goes while screen is on). Then apply Interactive and it will stay at 340mhz and not jump up to the max speed anymore.
pewpewbangbang said:
Use voltage control, it's free from the play store.
Click to expand...
Click to collapse
OK, I'll check it out!
EDIT: Not working at all. Sorry. You can check that it goes over your set values using CPU Spy.
Fruktsallad said:
OK, I'll check it out!
Click to expand...
Click to collapse
Yup, I just checked again and watched OnDemand be very unstable as the Governor itself is somewhat like that.
OnDemand ramps up to the high frequences so that everything is smooth, the only problem is that it's doing it way too easily. Leaving screen on and not touching it, something causes it to constantly jump back and forth between low and max frequencies.
Setting to Interactive or even Conservative makes it much more "stable"
Conservative is really good at staying on low frequences (takes longer to ramp up speeds) but as a result feels very laggy so Interactive is what I recommend as the best blend. (In general, Interactive governor is becoming the standard for most phones. I remember it being very popular on the i9100 and Galaxy Nexus)
So yea, just try out Interactive and see how it works for you. I am no longer draining battery at like 1% for ever 1-2 minutes of screen on time leaving it
Fruktsallad said:
OK, I'll check it out!
EDIT: Not working at all. Sorry. You can check that it goes over your set values using CPU Spy.
Click to expand...
Click to collapse
Yea I just realized messing with the frequencies isn't working
I will edit my OP
But setting to Interactive Governor DOES make changes
pewpewbangbang said:
I wouldn't lose battery with screen off. But with the screen on and not doing anything. Just watching the speeds in voltage control I watched it constantly alternate with 340 and 1500.
My min is the lowest I can set, around idk 50? I don't remember. But it doesn't go that low unless screen off standby. Probably for companion core.
This is just to let people know that ondemand governor acts funky and interactive is probably the best to use.
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
OK i assumed standby = screen off.Switched to interactive on System Tuner Pro....i see less spikes at 475 MHz.
I don`t have time but maybe someone could test for lag between the onedemand and interactive governors. I know for sure that the Tegra 3 works better using ondemand on my prime.
Anyway interesting things gould come from this.
---------- Post added at 07:55 PM ---------- Previous post was at 07:52 PM ----------
We really need the kernel source released so the devs can get to work.
ttav said:
OK i assumed standby = screen off.Switched to interactive on System Tuner Pro....i see less spikes at 475 MHz.
I don`t have time but maybe someone could test for lag between the onedemand and interactive governors. I know for sure that the Tegra 3 works better using ondemand on my prime.
Anyway interesting things gould come from this.
Click to expand...
Click to collapse
Interactive is very similar to OnDemand, but it is not as "aggressive" in it's frequency changes.
It is a very popular Governor on other phones and Kernels. So far, I've experienced no lag as it still hits those high frequencies, but less often and only when it needs to.
My main issue was leaving screen on and in standby with OnDemand and watching it constantly jump from low to max frequency which is definitely not correct.
Using interactive, battery drain has been much better and to the norm.
Can't wait for kernels to come out and optimize battery and performance.
pewpewbangbang said:
Interactive is very similar to OnDemand, but it is not as "aggressive" in it's frequency changes.
It is a very popular Governor on other phones and Kernels. So far, I've experienced no lag as it still hits those high frequencies, but less often and only when it needs to.
My main issue was leaving screen on and in standby with OnDemand and watching it constantly jump from low to max frequency which is definitely not correct.
Using interactive, battery drain has been much better and to the norm.
Can't wait for kernels to come out and optimize battery and performance.
Click to expand...
Click to collapse
I suggest everyone head over to HTCdev.com and post a comment asking for the One X kernel source code release.
I was going to make a new thread until I saw this.
I was able to override the Tegra 3 system using a few tricks which allowed me to change the frequency to my own, plus only allowing 2 cores to come on.
I'm at work but ill post a video soon, you only need setCPU and patience to get it to work.
I monitored this by TegraSTATS in the market for free
MrPhilo said:
I was going to make a new thread until I saw this.
I was able to override the Tegra 3 system using a few tricks which allowed me to change the frequency to my own, plus only allowing 2 cores to come on.
I'm at work but ill post a video soon, you only need setCPU and patience to get it to work.
I monitored this by TegraSTATS in the market for free
Click to expand...
Click to collapse
Great!, would be awesome if you can post it up here later
pewpewbangbang said:
Great!, would be awesome if you can post it up here later
Click to expand...
Click to collapse
Here's a small evidence for now, my CPU is set from 102mhz to 1000mhz. The bottom monitor is Tegrastats, as you can see only 2 cores are running max at 100% at 1Ghz on the CPU benchmark.
MrPhilo said:
Here's a small evidence for now, my CPU is set from 102mhz to 1000mhz. The bottom monitor is Tegrastats, as you can see only 2 cores are running max at 100% at 1Ghz on the CPU benchmark.
Click to expand...
Click to collapse
Yea similar to hotplug governor except is it always 2 cores for your mod?
Hotplug governor enabled however many cores were needed and disabled when not in use.
Either way, awesome work.
Sent from my HTC One X using XDA
hi,
I am running stock jellybean with franco kernel. just wondering what is the optimal CPU setup that doesnt sacrifice too much performance while increasing battery life. Im not too concerned about games as I rarely play them. I ussualy use the phone for music, calls, text, email, and webbrowsing.
I am using the Franco updater app. I have 1228 max, 230 min
and screen off max is 384.
I also noticed in cpu spy that my highest two frequencies 1036, 1228 are combined less than 10%.
with all that information, what do you suggest?
hshaikh said:
hi,
I am running stock jellybean with franco kernel. just wondering what is the optimal CPU setup that doesnt sacrifice too much performance while increasing battery life. Im not too concerned about games as I rarely play them. I ussualy use the phone for music, calls, text, email, and webbrowsing.
I am using the Franco updater app. I have 1228 max, 230 min
and screen off max is 384.
I also noticed in cpu spy that my highest two frequencies 1036, 1228 are combined less than 10%.
with all that information, what do you suggest?
Click to expand...
Click to collapse
I suggest to decrease your max CPU until you feel it affects performance too much. You can also try switching to a governor less aggressive than interactive (try ondemand).
Don't expect magic though. I've played with decreasing max CPU clock, max CPU screen off, governor settings etc with three different kernels. Gathered stats for at least one week each time. Never noticed a difference large enough to actually matter to me. For maximizing battery life, you can gain more by hunting apps that cause a lot of (partial) wakelocks and alarms, and use low screen brightness.
hshaikh said:
and screen off max is 384.
with all that information, what do you suggest?
Click to expand...
Click to collapse
don't limit screen off cpu speed to 384. it will take longer to perform operations under wakelock, thus killing of more battery than it actually saves.
it would be nice if listening to music, since it's not an intensive task and it requires constant cpu usage. still, you'll most likely have stuff syncing in the background so i don't think you're doing any good by limiting it to 384 on screen off.
power isnt going to be conserved with lower clock speed. lower clock speed means it takes longer to finish the task. to conserve power, your phone has to do less. for example, lower brightness, no sound, less/no syncing.
Darunion said:
power isnt going to be conserved with lower clock speed. lower clock speed means it takes longer to finish the task. to conserve power, your phone has to do less. for example, lower brightness, no sound, less/no syncing.
Click to expand...
Click to collapse
Well, there is an optimum somewhere. Higher CPU speed means tasks are executed more quickly, but higher clock speeds also draw more current from the battery. I agree that tweaking this has little effect on battery life though.
Petrovski80 said:
Well, there is an optimum somewhere. Higher CPU speed means tasks are executed more quickly, but higher clock speeds also draw more current from the battery. I agree that tweaking this has little effect on battery life though.
Click to expand...
Click to collapse
you are correct. there is a magic middle ground because power consumption doesnt scale in a linear way. but finding that spot would take massive testing and even getting to the center, would still probably only gain about 10-15mins average use on a battery charge :/
bk201doesntexist said:
don't limit screen off cpu speed to 384. it will take longer to perform operations under wakelock, thus killing of more battery than it actually saves.
it would be nice if listening to music, since it's not an intensive task and it requires constant cpu usage. still, you'll most likely have stuff syncing in the background so i don't think you're doing any good by limiting it to 384 on screen off.
Click to expand...
Click to collapse
what speed show i set to max when screen is off.
did you read anything that Darunion and Petrovski80 wrote? I keep mine at it's max, i don't care, i don't live in the woods with no electricity.
thanks for your inputs. i have experimented and I found out that changing the cpu speeds has minimal effect of battery life. the clock speed is not killing the battery the screen is. no matter what cpu settings i use i get 3-4 hours screen on time.
if i dont use the phone alot that day (like 1 hour screen on time) the battery will still be 40% after a day.
hshaikh said:
thanks for your inputs. i have experimented and I found out that changing the cpu speeds has minimal effect of battery life. the clock speed is not killing the battery the screen is. no matter what cpu settings i use i get 3-4 hours screen on time.
if i dont use the phone alot that day (like 1 hour screen on time) the battery will still be 40% after a day.
Click to expand...
Click to collapse
Exactly. I get similar performance.
Sent from my Galaxy Nexus using Tapatalk 2
Hi
so what are your undervolting results of your S4 Mini?
A quick test allowed me to go -200mv. (crashed at -225mv). Now I am running StabilityTest at -150mv @ 1728 MHz (performance governor), while charging and wrapped into a winter pullover
30 minutes have passed and still running. I guess I will go up to 2 hours before lowering to -175.
I wonder if you have big undervolt differences between lower and higher frequencies?
neustadt said:
Hi
so what are your undervolting results of your S4 Mini?
A quick test allowed me to go -200mv. (crashed at -225mv). Now I am running StabilityTest at -150mv @ 1728 MHz (performance governor), while charging and wrapped into a winter pullover
30 minutes have passed and still running. I guess I will go up to 2 hours before lowering to -175.
I wonder if you have big undervolt differences between lower and higher frequencies?
Click to expand...
Click to collapse
Did you set difference voltages for every frequenzy or did you use the two buttons at the top and lower every voltage the same? My device crashes if i go -200. My max freq. is 1566 and my min. freq. is 162. As governor I use smartmax and I/O scheduler is fiops I also underclocked my Gpu to 192 Mhz.
Not yet. I want to find a working global value and then tweak at 162MHz and 700MHz.
Did you limit your max frequency at 1566?
Flatric said:
I also underclocked my Gpu to 192 Mhz.
Click to expand...
Click to collapse
What app did you use for that?
neustadt said:
What app did you use for that?
Click to expand...
Click to collapse
Yes I limtited it at 1566, I used also Kernel tweaker to underclock my Gpu
Flatric said:
Yes I limtited it at 1566, I used also Kernel tweaker to underclock my Gpu
Click to expand...
Click to collapse
Oh, ok. So you limited your max gpu clock. Maybe I will try this out as well. But I would need to find out how far I can go down. Usually I dont play any games so I probably dont need the highest clocks on my gpu. But I do watch the occasional HD video.
In the end it might not help save batterylife, if my GPU doesnt clock that high anyways.
I would rather like to adjust the different speedsteps of the gpu just like on the cpu. ExTweaks looked processing, but doesnt seem to work with f4ktion kernel.
neustadt said:
Oh, ok. So you limited your max gpu clock. Maybe I will try this out as well. But I would need to find out how far I can go down. Usually I dont play any games so I probably dont need the highest clocks on my gpu. But I do watch the occasional HD video.
In the end it might not help save batterylife, if my GPU doesnt clock that high anyways.
I would rather like to adjust the different speedsteps of the gpu just like on the cpu. ExTweaks looked processing, but doesnt seem to work with f4ktion kernel.
Click to expand...
Click to collapse
Please tell me your result if you finished
neustadt said:
Hi
so what are your undervolting results of your S4 Mini?
A quick test allowed me to go -200mv. (crashed at -225mv). Now I am running StabilityTest at -150mv @ 1728 MHz (performance governor), while charging and wrapped into a winter pullover
30 minutes have passed and still running. I guess I will go up to 2 hours before lowering to -175.
I wonder if you have big undervolt differences between lower and higher frequencies?
Click to expand...
Click to collapse
I don't understand what you are trying to prove with wrapping your device in a winter pullover while undervolting.
When I have to apply tests at my job for simulating mobile applications, we undervolt (the solenoid of a valve) -30% and do test at very low temperature of -25'C. Then we overvolt with 30% and run '100% duty cycle' test at high temperature of +70'C. At low temperature there is a chance of not reacting anymore, at high temperature it is the latter: the coil could be toast since it can't radiate all the generated heat away.
With the undervolt test, you should put your phone in the fridge or freezer to really seeing it's behaviour at extreme circumstances. In my opinion you are now easing the pain on your phone during undervolting, by heating it from 2 sides, by charging and heat insulating it.
jake3317 said:
I don't understand what you are trying to prove with wrapping your device in a winter pullover while undervolting.
When I have to apply tests at my job for simulating mobile applications, we undervolt (the solenoid of a valve) -30% and do test at very low temperature of -25'C. Then we overvolt with 30% and run '100% duty cycle' test at high temperature of +70'C. At low temperature there is a chance of not reacting anymore, at high temperature it is the latter: the coil could be toast since it can't radiate all the generated heat away.
With the undervolt test, you should put your phone in the fridge or freezer to really seeing it's behaviour at extreme circumstances. In my opinion you are now easing the pain on your phone during undervolting, by heating it from 2 sides, by charging and heat insulating it.
Click to expand...
Click to collapse
Thanks for the info. I tried to apply what I knew about desktop CPUs and overclocking/undervolting to smarphones. Since people cant put their desktop machines into a freezer this was new to me.
I think I found my final settings now and attached them as a screenshots. Its really convinient to apply different voltages to different frequencies. If I look at my last 48 hours of regular usage (it was the weekend and I went biking with gps and stuff) I have still 55% deep sleep state and 30% 162MHz. So this state is clearly the most important for battery saving.
I found that google maps navigation is a good real life test for undervolting. It crashed my device once, where i didnt have any issues going through a scaled stability test. this is a nice feature of the StabilityTest app, where the the test goes periodically through all selected frequencies. Maybe the crash was also related to jake3317 comment, as I was outside at 10° C / 50° F. Anyways I gave the cpu a little more juice on the higher frequencies and I hadn't had a crash since then.
{
"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"
}
I've been trying to undervolt my phone using SetCpu but nothing seems to work and my phone has recently started to have huge battery drain issues.
May I know the app you guys use to set voltages for your phone? And also to test for the stability of your phone after the voltage changes?
You can use Kernel Tweaker for adjustments and StabilityTest for testing.
Whosat said:
I've been trying to undervolt my phone using SetCpu but nothing seems to work and my phone has recently started to have huge battery drain issues.
May I know the app you guys use to set voltages for your phone? And also to test for the stability of your phone after the voltage changes?
Click to expand...
Click to collapse
I use the App "Kernel Tweaker" https://play.google.com/store/apps/details?id=com.dsht.kerneltweaker
Ah, finally a decent app that doesn't crash out of nowhere. I've spent the last night trying to undervolt using Kernel Tweaker and tested using the stability test.
Unstable at -200mV, rebooting after almost 2 hours. Gonna try -150mV now
Update: -150mV was stable up to 41mins where I had to stop the test as I had to leave for work. Will continue testing tonight
Update 2: -175mV & -150mV unstable, crashing and rebooting randomly. Running -125mV now
Whosat said:
Ah, finally a decent app that doesn't crash out of nowhere. I've spent the last night trying to undervolt using Kernel Tweaker and tested using the stability test.
Unstable at -200mV, rebooting after almost 2 hours. Gonna try -150mV now
Update: -150mV was stable up to 41mins where I had to stop the test as I had to leave for work. Will continue testing tonight
Update 2: -175mV & -150mV unstable, crashing and rebooting randomly. Running -125mV now
Click to expand...
Click to collapse
If you found a stable base voltage you can do two more things: 1st. lower your minimum cpu clock to 162MHz. 2nd lower the voltage of this frequency alone a little more. for me it can take 50mv less then my base voltage. and its my most used clock besides deep sleep.
Will keep that in mind. I'm still randomly rebooting at -125mV.. Bringing it up to -100mV. Hopefully it'll be stable at this voltage!
Whosat said:
Will keep that in mind. I'm still randomly rebooting at -125mV.. Bringing it up to -100mV. Hopefully it'll be stable at this voltage!
Click to expand...
Click to collapse
Thanks please keep us updated on results. Will use it as a base.
Sent from my GT-I8190 using xda app-developers app
It may be worthy to note that every device has different undervolting potentials so you should experiment on your own too!
But I'll keep posted here
Have yet to run a full stability test but I've had a pretty stable day of using the phone at -100mV.
Will probably test while plugged in tonight when I find a reliable power source
So I've got a steady 5 hour stability test going at -100mV, with the exception of 1728 set at -115mV and 162 set at -125mV.
I've now decreased an additional 10mV across the board to see how it goes for the next 5 hours.
I'm also now using the Trickster MOD kernel app instead of the open source kernel tweaker app as I found that the open source version sometimes does not set my settings at boot (Min/Max frequencies to be exact). And the trickster mod app has the bonus of being able to control fauxsound
Whosat said:
So I've got a steady 5 hour stability test going at -100mV, with the exception of 1728 set at -115mV and 162 set at -125mV.
I've now decreased an additional 10mV across the board to see how it goes for the next 5 hours.
I'm also now using the Trickster MOD kernel app instead of the open source kernel tweaker app as I found that the open source version sometimes does not set my settings at boot (Min/Max frequencies to be exact). And the trickster mod app has the bonus of being able to control fauxsound
Click to expand...
Click to collapse
Awesome im interested to see your final results in undervolting im looking to get some more battery power