Develop Bugs

[Q] OC'd G2 starting to slow down?

I've had my g2 for a couple months now and I feel like I'm starting to see it slow down. I have it temprooted (w Visionary) and overclocked to 1.4 ghz. I used to never experience any lag at all. Lately, I've been noticing slower speeds with opening apps, navigating, etc. I have a setcpu profile set to turn the speed down to .245 ghz when the screen is off. While I expect to see some lag on turning the screen on, lately it has become extra laggy. Earlier today, I received a call and the screen didnt come up until several seconds after it began ringing. I can't take this slowness anymore.
Has anyone else experienced anything like this? Anyone know how I can fix it? I rarely turn my phone off, its been running for probably about a week and a half straight. Does that wear on the phone, could that be slowing it down?
Thanks

{
"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: Screen off profiles are a waste if you ask me, I have no profiles enabled and I text HEAVILY through the day, it's been 17 hours and I'm currently at 23%. In fact, I'm still heavily texting

Some people say its good to restart at least once a day ..i usually do
[G2/HTC Vision]

Is your phone getting stuck at low clock speeds after you wake up the screen. That happened to me and reflashing the kernel cleared that up.
Sent from my HTC Vision using XDA App

cmccollough said:
I've had my g2 for a couple months now and I feel like I'm starting to see it slow down. I have it temprooted (w Visionary) and overclocked to 1.4 ghz. I used to never experience any lag at all. Lately, I've been noticing slower speeds with opening apps, navigating, etc. I have a setcpu profile set to turn the speed down to .245 ghz when the screen is off. While I expect to see some lag on turning the screen on, lately it has become extra laggy. Earlier today, I received a call and the screen didnt come up until several seconds after it began ringing. I can't take this slowness anymore.
Has anyone else experienced anything like this? Anyone know how I can fix it? I rarely turn my phone off, its been running for probably about a week and a half straight. Does that wear on the phone, could that be slowing it down?
Thanks
Click to expand...
Click to collapse
I know overclocking your device seems cool and all but come on. 1.4 ghz? do you really need it that high? When I first got my g2 and I stumbled upon the 1.8 GHZ kernel I though "DAMN! I'm flashing that right now!!" but I soon realized that the stock 800 MHZ was more than enough for me after my battery life took a ****. I'm not sure how you use your phone, maybe you game a lot, maybe you need the extra 600 mhz. But remember one thing. It takes power to make power. your phone was never meant to be ran past 800 mhz. which is why it came from the manufacturer clocked in at that speed. the hardware within the phone was never meant to work that hard and the manufacturer has already deciphered the perfect combination for your phone to life its life to its full extent. I dont know how much you know about overclocking but when you overclock, you're upping the voltage to gain higher frequencies out of the cpu. this results in more heat output from the hardware. we usually compensate this by upgrading the cooling system but you cant really do that on a phone can you? sure, you can set profiles and what not but whenever you turn that screen back on, your right back at 1.4 ghz. My point is, increasing the clock speeds result in more heat. failure to dissipate that heat effectively will result in damaged components. I currently have my phone set on 245/245 screen off and 245/800 fully charged. and when the battery gets to 60% or lower, its 245/768. and believe me, i experience NO lag whatsoever. the most graphically intense game i have right now is need for speed shift. and it runs fine even on 245/768. of course i dont get insanely high linpack/quadrant scores with these clocks but even so, its not reflected when i use my phone.
All im saying is think about it, think about how you use your phone, and if its really necessary to have such high cpu speeds. Because I'm sure you already know that increasing that cpu speed also decreases its lifespan. It's your decision dude. (sorry about the essay lol)

Ive been runnin' my G2 at 1.51ghz since the day we had temp-root and ive never had any issues. Also setpCPU profiles are a waste of time and im pretty sure youre actually losing more battery life since its always underclocking and overclocking it when youve got specific profiles set for it. I run 1.51ghz on the interactive governor and i can get a good 10+ hours out of the phone with moderate usage - thats with NO profiles set.
You may think the extra mhz isnt needed but trust me it makes a big difference. Then again everyone has their own preference and beliefs.
Nissan350 said:
I know overclocking your device seems cool and all but come on. 1.4 ghz? do you really need it that high? When I first got my g2 and I stumbled upon the 1.8 GHZ kernel I though "DAMN! I'm flashing that right now!!" but I soon realized that the stock 800 MHZ was more than enough for me after my battery life took a ****. I'm not sure how you use your phone, maybe you game a lot, maybe you need the extra 600 mhz. But remember one thing. It takes power to make power. your phone was never meant to be ran past 800 mhz. which is why it came from the manufacturer clocked in at that speed. the hardware within the phone was never meant to work that hard and the manufacturer has already deciphered the perfect combination for your phone to life its life to its full extent. I dont know how much you know about overclocking but when you overclock, you're upping the voltage to gain higher frequencies out of the cpu. this results in more heat output from the hardware. we usually compensate this by upgrading the cooling system but you cant really do that on a phone can you? sure, you can set profiles and what not but whenever you turn that screen back on, your right back at 1.4 ghz. My point is, increasing the clock speeds result in more heat. failure to dissipate that heat effectively will result in damaged components. I currently have my phone set on 245/245 screen off and 245/800 fully charged. and when the battery gets to 60% or lower, its 245/768. and believe me, i experience NO lag whatsoever. the most graphically intense game i have right now is need for speed shift. and it runs fine even on 245/768. of course i dont get insanely high linpack/quadrant scores with these clocks but even so, its not reflected when i use my phone.
All im saying is think about it, think about how you use your phone, and if its really necessary to have such high cpu speeds. Because I'm sure you already know that increasing that cpu speed also decreases its lifespan. It's your decision dude. (sorry about the essay lol)
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App

TL24 said:
Ive been runnin' my G2 at 1.51ghz since the day we had temp-root and ive never had any issues. Also setpCPU profiles are a waste of time and im pretty sure youre actually losing more battery life since its always underclocking and overclocking it when youve got specific profiles set for it. I run 1.51ghz on the interactive governor and i can get a good 10+ hours out of the phone with moderate usage - thats with NO profiles set.
You may think the extra mhz isnt needed but trust me it makes a big difference. Then again everyone has their own preference and beliefs.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I totally see where you're coming from with the whole battery life thing with setcpu. But then again it all depends on how we use our phones. My phone is off the charger from 5:00 A.M. to 10:00 P.M. Monday through Friday and I end the day off with about 15% left with moderate/normal usage. Tried doing this without profiles and it was impossible. So there are some of us that simply cannot afford to overclock our devices for two reasons. Number 1 being that we need the extra juice to get us through our day being able to be contacted through our phones. Number 2 being that we simply do not want to cut the life of our phones by 1/3 and there's not a doubt in my mind that you know that OCing anything cuts its lifespan. But then again, there are those who simply do not care about any of that and I say **** if you don't care then why not? My main question to you though, is where? Where does it make a big difference to OC your device to 1.5 GHZ? I'm not in any way saying that you shouldn't because like you said, everyone has their own beliefs. But I want to know where it makes such a big difference? Is it the 1 second you shave off when installing apps? Or is it the 2 seconds you shave off of the boot time? In my eyes, its simply not worth it to put the cpu under so much stress and giving the device a premature death when you only shave off 1 or 2 seconds. If you hit 60+ on linpack, that's great, but I really don't think its going to reflect so much in normal functions of the device such as opening your app drawer, launching an app, or sending a text. If you game a lot, on the other hand, I can totally see why you would want to OC.
Not saying you're wrong dude, it's just something to think about.

Battery problems solved/improved!!! (Two findings to drastically improve drain)

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

Frequency of cpu

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

[GUIDE] Learn to Overclock and Undervolt your phone

This is an article that I've founded on a website and I want to share with you. Everything has been already posted and there is no new info for advanced users, but I think this will be very useful to many of you. Anyways, here it is
Click to expand...
Click to collapse
Your phone was taught to underachieve
You are not getting the maximum power and battery life out of your phone. At factory settings your Motorola Defy is underclocked and overvolted, which means that it runs slower than it should and drinks too much battery juice (even so it performs well and has a good battery life compared to other Android phones). Some people believe that the Defy was deliberately crippled for commercial reasons: Motorola didn't want to jeopardise sales of more expensive models by making the Defy too attractive. Nobody knows if this rumor is true or false. Either way, there is a tradeoff between performance and battery life, and Motorola erred on the side of caution. A phone that crashes because it runs too fast at too low a voltage causes a lot of expensive work for customer service. A phone that drains the battery a bit faster while running a bit slower won't send its users back to the stores to demand a fix, as long as it performs within the advertised specifications.
And the specs are too conservative. Your phone can run longer and faster.
To understand why, let's dig into the numbers.
{
"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"
}
Speed, voltage, and battery trade-offs
Motorola set the three CPU speed/voltage combinations for the Defy at:
1) 300 MHz at VSel1 = 33;
2) 600 MHz at VSel2 = 48;
3) 800 MHz at VSel3 = 58;
at a threshold of 86%.
The threshold determines when the processor steps up to a higher speed. By default, it switches to high speed if it runs at 86% capacity, and slows to a lower gear when the usage drops.
Higher speed (more MHz) requires a higher voltage, which is why the VSel (Voltage Select) goes up. VSel is related to voltage according to:
V = 0.0125*VSel + 0.6.
So at the lowest default VSel (33), your phone runs at 1.0125 V. At the highest default VSel (58) it runs at 1.325 V.
The power consumed by the processor increases in a linear fashion with the clock speed (twice the speed is twice the power), but quadratically with the voltage: twice the volts means four times more power.
The display and the radios eat up most of your battery. Turning down the brightness and switching off GPS, Wi-Fi and mobile data when not in use improves battery life more than undervolting your processor.
However, you can squeeze a few more hours out of a battery charge if you undervolt your CPU, and overclocking may make some apps run a little smoother. Just don't expect miracles, and be prepared for errors and crashes when you push the wrong buttons.
Room for improvement
The main battery saver is a low VSel1 (the lowest voltage at the lowest speed), because your phone runs at this speed most of the time. Underclocking VSel1 is not a good idea, because below the default 300 MHz it takes noticably longer before your phone responds to an incoming call in standby mode. Reducing VSel1 too much makes your phone hang or reboot when it's idle, but you can reduce VSel1 within reason to increase standby time. If you cut VSel1 from 33 to 20 the processor uses 40% less power most of the time, which can make the difference between your phone lasting a full day or blacking out before you get a chance to plug it in. (There are more ways to stretch your battery without dumbing down your smartphone.)
Lowering the intermediate voltage at medium speed (600 MHz by default) saves a bit of juice when you're playing with your phone a lot, because VSel2 is the typical setting when you're using your phone. If you use your phone as an mp3 player on a long trip you may notice the difference.
Your phone rarely runs at top speed. It spikes at VSel3 occassionally, but even with QueueTube streaming, Wi-Fi Ruler scanning, GPS Status looking for satellites, and Dolphin HD loading pages in the background my processor spent most of the time at 600 MHz instead of the default maximum (800 MHz) or my custom 1 GHz.
Overclocking may make a difference if you're playing resource-hungry games or watch badly encoded videos. Just don't overdo it, because the voltage required to run at more than 1 GHz makes your phone produce more heat, reduces battery life, and may even shorten the life of your hardware. Try to keep the maximum VSel below or at the default maximum, and don't let the temperature increase beyond 35°C for too long unless you live in a very hot place. High temperatures won't kill your phone at once, but they will kill your processor and battery slowly. Batteries may be cheap, but a dead processor will turn out very expensive. Especially when the manufacturer finds out you've messed with the settings and voids your warranty.
So what settings should you use?
Workout schedule for your phone
There is no one-size-fits-all answer. Processor performance varies, even if they're from the same batch. Your optimum settings depend on your phone, whether it runs Eclair or Froyo, how you use it, where you use it. A phone in a hot jeans pocket doesn't dissipate heat as fast as a phone in a cool handbag, and shooting video is more demanding than listening to podcasts. You'll have to find the best settings for your phone by trial and error.
Start by lowering VSel1 in small steps and check if your phone runs stable for a while under real world conditions. The stability test that's built in SetVsel is a rough indication, but also test stability by running a couple of streaming video apps over 3G together with other power-hungry apps, because seemless switching between speeds is not the same as an artificial stress test at constant voltage. If your phone starts rebooting by itself, increase the VSel by a safe margin.
There's no point trying to push the numbers to the max, because the power used by your CPU is just a small part of the big picture. Tweak the next VSel after you have the first one tuned. Don't change all at once, because then you don't know which one is wrong if your phone becomes unstable. Tweak your VSels one at a time.
Remember: undervolting won't damage your phone. Pushing the voltage too high may fry your CPU and kill your battery. I wouldn't push my Defy beyond 1000 MHz unless I can make it run at a very low voltage.
Judging from reported values at which Motorola Defy (most of them on Eclair, some on Froyo) phones ran without issues (see below for details), the safe ranges seem to be:
- 300 MHz, VSel1 24-33
(some people report stable systems as low as VSel1 14);
- 600 MHz, VSel2 31-48;
(some people report stable systems as low as VSel2 27);
- 800 MHz, VSel3 41-58.
(some people report stable systems as low as VSel3 39);
- 1000 MHz, VSel3 45-74.
(above VSel3 58 your phone may get really warm).
I started with 300/24, 600/34, 1000/52. When that ran OK for a couple of days I knocked the voltage down in bits and pieces. I now keep my phone running at 300/16, 600/28, 1000/52, with the threshold at the original 86%. My phone runs smoothly, passes the stability test (check the bottom of the SetVsel screen) with flying colors, and the battery lasts noticably longer than with the default settings.
Of course that doesn't necessarily mean these settings will work for you, because every CPU is different. The only way to find out is by trial and error. Push your VSels down in small steps, one at a time, until your phone fails the stability test or starts rebooting by itself. Then go back to the last "safe" setting and continue with the next VSel.
If you like to take risks and don't mind your phone getting hot:
- 1100 MHz, VSel3 55-66;
- 1200 MHz, VSel3 60-75.
More options
SetVsel has two options to let your phone go on a diet when your battery runs low. The first option is to limit your phone to VSel2 when the battery level drops below a set percentage (e.g.30%), the other method is setting the threshold to 99% when the battery runs low. New versions of SetVsel may come with new tricks to squeeze some extra time out of dry batteries.
SetVsel can show your processor status in the notification bar if you check the speed icon box. Don't panic if the reported speed is different from what you entered into the program. SetVsel polls the processor speed more often than the notification refreshes, so the numbers indicate average speeds.
The "apply at boot" option is best left alone. If your phone runs well you won't reboot it very often anyway, and if it crashes a lot you'll probably need to try different voltages and reduce the maximum speed.
Go get it
• SetVsel (Android Market)
• SetVsel (xda forum)
SetVsel was designed for the Motorola Defy, but it also works on the Droid X and the Milestone. It may work on other phones, but your best bet is to search the market for "overclock" or "undervolt" and pick an app tailored for your device. Read the comments in the market to check if it works on your phone model. Checking out forums like xda before you start messing with the voltage is a good idea too.
Note: all overclock/undervolt apps require that your phone is rooted.
The safe ranges were estimated by searching Google for "Motorola Defy undervolt" and taking the speed-VSel combinations reported as being stable or unstable. The full list of values used:
reported as stable:
300/15 ? ?, 300/15 500/34 600/38, 300/14 550/26 800/38, 300/16 550/27 800/39, 300/16 600/28 800/39, 300/18 600/33 800/43, 300/20 600/32 800/50, 300/26 600/32 800/44, 300/26 600/33 800/39, 300/24 600/34 900/44, 300/28 600/38 900/46, 300/28 600/38 900/48, 300/18 600/30 1000/52, 300/18 600/38 1000/52 86%, 300/20 600/28 1000/54, 300/20 600/30 1000/48, 300/20 600/30 1000/52 80%, 300/20 600/34 1000/52, 300/22 600/32 1000/52, 300/22 600/32 1000/52, 300/24 600/34 1000/52, 300/24 600/36 1000/56 80%, 300/26 600/32 1000/56, 300/26 600/34 1000/54, 300/30 600/48 1000/58, 300/30 600/48 1000/58, 300/33 600/48 1000/52 92%, 300/33 600/48 1000/58, 300/16 600/27 1100/58, 300/19 600/29 1100/54, 300/26 600/34 1100/58 60%, 300/28 600/44 1100/58, 300/28 600/44 1100/62, 300/30 600/40 1100/58, 300/30 600/44 1100/60, 300/15 600/25 1200/60, 300/20 600/32 1200/63, 300/24 600/34 1200/62 80%, 300/30 666/46 1000/58, 300/17 700/35 1100/57, 300/28 700/52 1100/62, 300/30 700/46 1100/58, 300/16 700/33 1200/60 90%, 300/16 700/34 1200/63, 300/30 700/48 1200/68 86%, 300/30 700/48 1200/68 92%, 300/28 800/46 1200/60, 300/28 800/46 1200/60 76%, 300/25 900/56 1100/66, ? 900/40 ?, ? ? 900/46, ? ? 1000/45, ? ? 1000/50, ? ? 1000/56, ? ? 1000/56, ? ? 1000/56, ? ? 1000/58, ? ? 1000/60, ? ? 1000/74, ? ? 1100/55, ? ? 1100/56, ? ? 1100/58 70%, ? ? 1100/58, ? ? 1100/59, ? ? 1100/64, ? ? 1200/64, ? ? 1200/65, ? ? 1200/66, ? ? 1200/68, 300/33 600/48 800/58 1200/68
reported as unstable:
300/13 ? ?, 300/20 ? ?, 300/20 600/30 800/40, ? ? 900/46, ? ? 1000/56, ? ? 1000/60, ? ? 1100/53, ? ? 1100/54, 300/26 600/40 1100/58, ? ? 1200/60, ? ? 1200/66, ? ? 1350/76​

Overclocked
[email protected]
[email protected]
[email protected]
[email protected]

My values are:
[email protected]
[email protected]
[email protected]
[email protected]
I Have Slim Defy wJellyBean4.3 and Works Like a Charm.

[email protected]
[email protected]
[email protected]
[email protected]
Have had these settings working nice and stable for a long time on CM7 then CM10. Now on Mokee 43.1 and seems good so far.
Also using Aero Control to overclock the GPU to 266Mhz, this has made quite a big difference. My Antutu score went from approx 4500 to 5000 and everything seems just a bit smoother. Only problem is I can't get Aero Control to retain the settings on boot.

MB526[Defy+]:
[email protected]
[email protected]
[email protected]
[email protected]

themaker69 said:
MB526[Defy+]:
[email protected]
[email protected]
[email protected]
[email protected]
Click to expand...
Click to collapse
Mine are:
[email protected]
[email protected]
[email protected]
[email protected]
everything's just fine with it.

Title is misleading
hoderer said:
Mine are:
[email protected]
[email protected]
[email protected]
[email protected]
everything's just fine with it.
Click to expand...
Click to collapse
I found this thread from a huge noob guide, it's disappointing to see it only refers to one type of phone i've never even heard of. I searched for overclocking Samsung Galaxy Mega and nobody seems to know anything yet. If anyone has tested settings for this phone, pls advise. I'm on a L600 Sprint tinkering around with a bunch of stuff, and overclocking is certainly on my to do list.

Undervolting - good idea or not?

I'm wondering if anyone's undervolted and to what values.
I'm also wondering waht the deafult values are and if they change per kernel.
Is there a way to disable SetCPUs undervolting settings?
Has anyone improved battery life with profiles? On the Eris this was the only way to get usable battery life.

Or not. I gave up undervolting after I actually compared battery life at stock values vs undervolted (on my old phone, sgs4g) and discovered it does nothing for battery life.
Edit: undervolting "might" marginally increase standby battery life, but considering how good this phone already does... it certainly won't increase actual screen on usage.
Sent from my Galaxy Nexus using xda premium

Depends how low you under volt. Got more battery life, maybe about an hour, after finding optimal battery life on my gfs Gnex.
If you don't under volt correctly, of course it won't improve battery life.
From my sexy white, Nocturnaled HTC One X

If you're not overly comfortable with undervolting, then using one of the many kernels with Smart Reflex will do a mild undervolt for you. If you are comfortable, then the only way to find numbers good for your phone is to try and test. I tweaked mine down to the point that I was occasionally getting hot boots when the screen was off and media was playing. Tweaking the numbers back up added the needed stability. Even little things like kernel or ROM revisions can change what voltage is or isn't stable. Another example is that when I updated my Jellybro CM10 version the other night, along with updating leankernel from 4.1.0exp3 to 4.2.0, I had to increase a few of my voltages to avoid hot boots.
Just for example numbers, here are mine:
Code:
1350MHz -- 1200mV
1200MHz -- 1150mV
920MHz -- 1050mV
700MHz -- 950mV
350MHz -- 825mV
These numbers will vary from device to device and even between ROM/kernel combinations, so don't use them as hard fact.

Thanks. On a phone like this it might not make a huge difference but on the Eris (Where stock battery life could sometimes be 6 hours if you actually used your phone) an undervolted kernel with setcpu could turn those 6 ours into 48.
Thanks Cilraaz, I'll try those voltages out and benchmark a bit to see if they're stable for my system.

Two things I can say for sure:
1. you will have very limit battery gain by undervolting with Gnex, no matter how low you try.
2. undervolting will bring some stable issue if you get too low, like lose signal and reboot.

I am using Kernel Franco GPU 384 Stock rom on my 4.1.1 and did undervolting
Current configuration:
384Mhz
950mv
------------
729Mhz
1050mv
-----------
1036mhz
1125mv
----------
1228mhz
1275mv
-------------
I did not change the frequencies of overclocking, because I'm not using them.
I felt an improvement in battery consumption unless the unit is heating up.

Just curious - what kind of profiles are you using? I have a "Screen off" that's 350min and 700max. I figure that's fast enough f someone calls me.

I've read many times undervolting isn't worth it.

Hungry Man said:
Just curious - what kind of profiles are you using? I have a "Screen off" that's 350min and 700max. I figure that's fast enough f someone calls me.
Click to expand...
Click to collapse
I'm using the following with SetCPU: default (1350MHz-350MHz), charging, CPU temp > 64, and battery < 35%.
If you're using a kernel and governor that support hotplug, then you likely don't want to use a screen off profile. The combination of the two can tend to cause sleep-of-death or hot boots.
I Am Marino said:
I've read many times undervolting isn't worth it.
Click to expand...
Click to collapse
Most people don't want to spend the time to do it right.

I'm actually not used to the new kernels. I haven't messed with my eris in about a year and back them there was "smartass, on demand, performance," and some other one that clocked down instead of up
Can you explain th escreen off profile causing issues? I don't even know what hotplug is lol I've been out of Android for a long time.

Hungry Man said:
Can you explain th escreen off profile causing issues? I don't even know what hotplug is lol I've been out of Android for a long time.
Click to expand...
Click to collapse
Hotplug disables one of the CPU cores when the screen is off. Some governors, like hotplugx, will also attempt to disable a CPU core during periods of low CPU usage. For some reason, this combined with a screen off profile can cause some problems. I assume it's because of the "screen-off-max-freq" that Imoseyon mentions in the quote below.
Personally, I prefer the interactivex governor with leankernel by Imoseyon. From his kernel thread:
With interactiveX V2 (for gnexus), things are a bit different, since gnexus has built-in support for screen-off-max-freq for all its governors. I took the new interactive code in gnexus, added early_suspend support (screen off/on trigger), and then added logic to the code so the governor uses the phone's built-in hotplugging capability to turn off cpu1 when screen is off (and then turn it back on when screen comes back on). Cpu1 goes offline entirely - no idle, no sleep.
Click to expand...
Click to collapse

I think undervolting helps - my phone is running 728 - 1228 using the interactive governor, with voltages of 600 mV, 700 mV, and 800 mV (728 MHz, 1036 MHz, 1228 MHz respectively) and I haven't had any issues so far. I know there are some reports that say undervolting doesn't help much, but those are when people undervolt by like 50 mV, whereas here I'm going like 400 mV under lol. (Yes, smart reflex is off).

Thanks Cilraaz. Good to know.
So turning the screen-off profile could improve things? Honestly, my system does fine at 350mhz with screen off. Turning a core entirely off would probably help though.
If I use hotplugx governor that would disable one core when the screens off, right?

Hungry Man said:
If I use hotplugx governor that would disable one core when the screens off, right?
Click to expand...
Click to collapse
Hotplugx will disable a core when the screen is off or when there is low system load. Depending on your kernel/governor choice, other governors may do it also. On leankernel, for instance, interactivex will disable a core when the screen is off, but not on low system load.

Ok, thank you.
I haven't done any comparisons of before/ after since I undervolted/ underclocked first thing. But I was browsing for hours while listening to music while talking to a friend with GTalk. talked for about 1.5 hours with someone, Left it on overnight (10 hours), woke up, used it to talk (voice to text) to someone via GTalk, and it's 3:25PM right now and I still have a fair amount of battery life left.
I'd heard mixed things about the battery on this so I'm happy.
My voltages:
1650: 1300
1520: 1250
1350: 1175:
1200: 1125
920: 1000
700: 925
350: 900
I stress tested each one without a crash.