Develop Bugs

Feelings about undervolting.

How does everyone feel? I've always assumed that it forces better battery life but I've noticed a lot of people do. I've done it till now just because I figured it has to help since every kernel I've used on any phone is under volted. Do you think it helps? Any kind of proof is welcome but so are opinions.
Sent from my Galaxy Nexus using XDA App

I'm on board with a modest under volt, but when you drop the voltages to the point that the phone is no longer 100% stable any minuscule battery savings would be undone by the forced reboot.

GN's cpu uses a power management technology called smartreflex which dynamically changes voltages used by different frequencies. The values that are set with setcpu and similiar apps are only the maximum voltages that smartreflex is allowed to use. The actual voltages may be well below the nominal ones.
Personally I never noticed any significant improvements. It's hard to tell how much but it is definitely not worth going really low. Right now I am using leankernel which is undervolted slightly by default.

codesplice said:
I'm on board with a modest under volt, but when you drop the voltages to the point that the phone is no longer 100% stable any minuscule battery savings would be undone by the forced reboot.
Click to expand...
Click to collapse
This.
Apps may stop working randomly or the phone may have random reboots if you mess with the wrong speed.
Honestly speaking, just go to setting...
1. then data and limit background data of certain unimportant apps
2. developer options > background process limit. Set it to like at most 3.
These ways are much safer and will boost your battery life.

Thanks. Right now I have a decently aggressive but stable UV but I'm gonna up them another 50mv just to be safe and do that. Thanks for the suggestion I didn't know I could do that. I'd hit thanks if I wasn't on a phone...
MilkPudding said:
This.
Apps may stop working randomly or the phone may have random reboots if you mess with the wrong speed.
Honestly speaking, just go to setting...
1. then data and limit background data of certain unimportant apps
2. developer options > background process limit. Set it to like at most 3.
These ways are much safer and will boost your battery life.
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using XDA App

[Q] Overclock

Well i have a phone, and in that forum members says that Overclock the cpu shorts the motherboard life, is that true? and for those who are using Overclock, do u really feel something diferent with the performance of the tablet? or do u see something wrong with Overclock? like random reeboots or makes the tablet hot? Im thinking in OC or not my tab, so i wanna see the experience from other members, thx in advance. :good:

Deshabilitado said:
Well i have a phone, and in that forum members says that Overclock the cpu shorts the motherboard life, is that true? and for those who are using Overclock, do u really feel something diferent with the performance of the tablet? or do u see something wrong with Overclock? like random reeboots or makes the tablet hot? Im thinking in OC or not my tab, so i wanna see the experience from other members, thx in advance. :good:
Click to expand...
Click to collapse
I cover this in the guide I wrote in general (which has been pushed down quite a ways) but anyways here goes another version.
Overclocking varies from device to device, even of the same model. Variances in tolerance is on a per chip basis, as long as they pass within a certain range they are sent out for production in devices. Overclocking in general is within means of the chip's abilities, if it isn't, you'll know it. Generally speaking, 1.4 GHz is perfectly fine on our devices. 1.5 GHz is also usually ok, but is the upper end of what the Tegra2 can usually tolerate. Few an go past 1.58 GHz, my old G2x's tegra2 could hit 1.7 GHz,but that's well beyond "normal" range.
Overclocking a device is the same as overclocking a PC, you need to be careful with it. Don't just ramp it to 65% overclock and expect it to run fine. Every chip is different. Do it in steps, and test each step before moving on. Test it in normal usage, test it in heavy usage, gaming, etc.
An overclocked device will certainly run hotter then normal, it's running faster, drawing more power, and that creates a hotter running core, no way around it. Keeping in mind there is no airflow in these things, that makes the biggest enemy to CPUs even more dangerous.Does it run so hot that it can shorten component life? Sure it can. Will you still have the device when it happens? I doubt it. Likely, we'll be on Tegra5 before it even begins to show signs of stress.
One of the nice things, though, is our CPUs range so much in speed according to load that just because your Max is 1.5 GHz, it doesn't always run there. Most times, it won't even be in the overclocked speeds. Does it run faster? Sure does. Benchmarks will raise nicely, and games that maybe got choppy before will smooth out, movies that couldn't play well will be fluid, the heavens will align, mankind will discover world peace and I'll win the lottery.
All that being said, I don't usually overclock, in fact I tend to underclock a little to 800MHz. Its usually sufficient to do normal tablet stuff, and I adjust the speed according to what I require. If my movie is lagging, I'll bump it up until it smooths out. Same for a game if it needs it.
In the end, its all personal choice, really. Just because you CAN overclock, doesn't mean you NEED to. IMO a well tuned governor will give as good a result as overclocking in normal usage, and a good I/O Scheduler will also help alot, without adding anymore heat or stress to your device.
TL;DNR:
Overclocking is fun. It causes more heat. It likely won't explode within the time you own it. Or your children. Your battery will suck.

thanks pio for the answer, thats what i needed to read, cuz usually when u talk about OC its like "yeah dude, OC its "tha greeeeeat doi it dude" or something like "dont do it!!! u will decrease your tablet life" and yes, i know that devices are way to diferent even if they are the same model, and also im agree with u, governors and I/O works better than OC but we dont have many for our device, i miss the smartass v2 governor,or the brazzilianwax too, but well, hope someone can port it for us someday.

How much is safe for overclocking?

I'm running Blackout v3.0, and it's running pretty smooth at first. But now my phone is stuffed with bunch of apps, making it running slower and slower. I want to keep those apps so I'm willing to overclock but I afraid of damaging my phone. So I would like to ask what's the safe overclocking frequency? I want the optimum frequency, fast enough and safe/stable.

ImjuzCY said:
I'm running Blackout v3.0, and it's running pretty smooth at first. But now my phone is stuffed with bunch of apps, making it running slower and slower. I want to keep those apps so I'm willing to overclock but I afraid of damaging my phone. So I would like to ask what's the safe overclocking frequency? I want the optimum frequency, fast enough and safe/stable.
Click to expand...
Click to collapse
Any overclocking can be unsafe as it can shorten the lifespan of your memory and CPU. But with that said I run mine at 1200 with no issues. Most people don't go higher than 1600 but anything 1400 or lower is not going to burn it up too quick IMO. Everyones hardware will react differently though.
Sent from my Inspire 4G using xda app-developers app

They usually say phone will get damaged, but I think its a myth. You can go up to 1600. After that it will get unstable.
Sent from my Inspire 4G

ImjuzCY said:
I'm running Blackout v3.0, and it's running pretty smooth at first. But now my phone is stuffed with bunch of apps, making it running slower and slower. I want to keep those apps so I'm willing to overclock but I afraid of damaging my phone. So I would like to ask what's the safe overclocking frequency? I want the optimum frequency, fast enough and safe/stable.
Click to expand...
Click to collapse
I run IceColdSandwich and have found 1459MHz to be the best combo of performance and stability on my phone. Every phone handles OCing a little differently, some can reportedly take over 1600 without a flinch and others will lock regularly with even a slight OC. Just experiment with the "set at boot" option turned off until you find something that works reliably on your phone.

Is it true you guys aren't seeing ill effects on your battery by overclocking like that?
Sent from my HTC Desire HD using Tapatalk 2

asif9t9 said:
Is it true you guys aren't seeing ill effects on your battery by overclocking like that?
Sent from my HTC Desire HD using Tapatalk 2
Click to expand...
Click to collapse
I think OC can affect battery drain only if you use an application which utilizes a full cpu load. But, if you're using this app in normal mode, economy will not be great also. So, when you using your phone for calling or general usage you will not see any problems with battery discharge.
I'm using DHD with Blackout v3.0 and I set 1200Mhz for maximum cpu value. I have no problems, phone is stable. Some time ago I used Leedroid ROM and set also 1200Mhz, but phone was rebooted by itself very often. More than twice a day.
You should try to use OC, as someone said above, without "set on boot" option. I think there is no danger for hardware up to 1600Mhz.

asif9t9 said:
Is it true you guys aren't seeing ill effects on your battery by overclocking like that?
Click to expand...
Click to collapse
Not under normal use. There's a school of thought that says even though the increased speed requires more power, it can also finish tasks and go back to sleep faster, so it ends up being a wash. I've overclocked all three smartphones I've owned to date and haven't experienced any significant difference in battery life.

ai6908 said:
They usually say phone will get damaged, but I think its a myth. You can go up to 1600. After that it will get unstable.
Sent from my Inspire 4G
Click to expand...
Click to collapse
They say that as a precautionary measure just as they say flashing a custom ROM can be dangerous. For people who don't know what they're doing. But precaution aside, just like you said you can go up to 1600 MHz safely on this phone. I know every phone behaves differently but on average no one has issues upto that frequency. But above that frequency the phone might be unstable. The CPU will be drawing much more power at high frequencies and will heat up more. The CPU heating up too much and too frequently reduces the life of the CPU. So it's not a myth.
Sent from my Desire HD using xda premium

2ghz.... the phone is old now. Make it bleed.
Sent from my Desire HD

Don't try to Cross above 1600.

Does undervolting really save battery life?

Hey guys i saw this video on youtube (http://youtu.be/5nrOWZUsEEc) that explains that undervolting wont make your phone save battery life more than 2% even with EXUV. I need explanations for this as i don't really understand.
Via the Internet

TiTAN-O-One said:
Hey guys i saw this video on youtube (http://youtu.be/5nrOWZUsEEc) that explains that undervolting wont make your phone save battery life more than 2% even with EXUV. I need explanations for this as i don't really understand.
Via the Internet
Click to expand...
Click to collapse
What part of "you won't save more than 2%" you didn't understand?

ilusi0n_ said:
What part of "you won't save more than 2%" you didn't understand?
Click to expand...
Click to collapse
Well, i don't really understand WHY it doesn't save more than 2% of the battery life. Afaik, EXUV does reduce heat and improve battery life by miles. But that's what I thought. In reality which is this, im not rly sure why that even with EXUV, it still cant save more than 2% of the battery life.
Sent from my S800 China Phone

TiTAN-O-One said:
Hey guys i saw this video on youtube (http://youtu.be/5nrOWZUsEEc) that explains that undervolting wont make your phone save battery life more than 2% even with EXUV. I need explanations for this as i don't really understand.
Via the Internet
Click to expand...
Click to collapse
I'm not technically expert with things like this but I have read an article/ blog before that undervolting may damage a phone since it was designed to work with that specific voltage. So, I actually didn't do that even UC or OC. Just saying.....

Undervolting doesn't save battery as your CPU will still try and draw the manufacturer set levels.
If it doesn't get those levels it must step down its own level which essentially means that the activity that needs processing needs more time, and consequently, more battery.
Even if you manually adjust the clock speed of your CPU down to match your new voltages, the same applies.
UC/UV is quite simply the worst voodoo that persists across these forums.
/stripped down explanation
(I didn't even watch the video)

r25txe said:
Undervolting doesn't save battery as your CPU will still try and draw the manufacturer set levels.
If it doesn't get those levels it must step down its own level which essentially means that the activity that needs processing needs more time, and consequently, more battery.
Even if you manually adjust the clock speed of your CPU down to match your new voltages, the same applies.
UC/UV is quite simply the worst voodoo that persists across these forums.
/stripped down explanation
(I didn't even watch the video)
Click to expand...
Click to collapse
we can control the hardware through software so we can control the voltages and frequencies through kernel
devs can put new frequency levels as manufacturers did (like this :https://github.com/Christopher83/samsung-kernel-msm7x30/commit/899d5a296a43a6d32c2468bba8121c3a1915dd68)
if its not true and if this method doesnt work, Why all kernel devs on XDA trying the same thing??
https://github.com/faux123/android_kernel_oppo_n1/commit/eaa6639979e1144f28c14e6de48994d41e5d20d8
https://github.com/franciscofranco/hammerhead/commit/104890313a73dae0e7d7a13975801cc568d231ad
in summary EXUV and UV are absolutly battery-friendly
and do not forget undervoltage cant damage the hardware but overvoltage(ı mean OC) can damage the hardware

sir mordred said:
we can control the hardware through software so we can control the voltages and frequencies through kernel
devs can put new frequency levels as manufacturers did (like this :https://github.com/Christopher83/sa...mmit/899d5a296a43a6d32c2468bba8121c3a1915dd68)
if its not true and if this method doesnt work, Why all kernel devs on XDA trying the same thing??
https://github.com/faux123/android_kernel_oppo_n1/commit/eaa6639979e1144f28c14e6de48994d41e5d20d8
https://github.com/franciscofranco/hammerhead/commit/104890313a73dae0e7d7a13975801cc568d231ad
in summary EXUV and UV are absolutly battery-friendly
and do not forget undervoltage cant damage the hardware but overvoltage(ı mean OC) can damage the hardware
Click to expand...
Click to collapse
I've based my reply above on this post.
It is a much longer version of what I summarised earlier.
And, sorry, even UC/UV can damage your hardware in rare situations.
It does baffle me why people spend so much time tweaking things as you mention when the net returns are negligible, and often cancelled out.

So to sum all this up. We just have to leave the CPU & voltage tables alone since it damages hardware?
Via the Internet

It's not that you have to, but that chip designer recommends it.

r25txe said:
I've based my reply above on this post.
It is a much longer version of what I summarised earlier.
And, sorry, even UC/UV can damage your hardware in rare situations.
It does baffle me why people spend so much time tweaking things as you mention when the net returns are negligible, and often cancelled out.
Click to expand...
Click to collapse
That was also the POST that I'm referring to that I've read :good:

Question Unlock cpu power limit for better gaming experience

As title says.
I am cooling my phone with custom cooler and chipset drain like 1500-1600 mAh for like seconds and throttle instantly 1200 mAh/hour before cpu temperature doesn't even goes up like 40°C than drains between 900 mAh to 1200 mAh. I cooled chipset like 30°C for testing and nothing changed. That lead me that this isn't cpu temperature thing. But i don't exactly understand the point.
I can't sustain cpu frequency 2.84 ghz no matter how much i cool it.
I believe gaming phones that using same chipset drain more than that because of their sustainable performance drastically more than our phone even if ı cool my phone better than theirs.
In franco kernel manager there are some settings for cpu behavior but none of them helped.
I wonder is there any possibility that unlock that power drain limit -even if there is in first place- that kernel level. I want to squeeze our chipset's full potential

just curious, why do you need that performance?

i am using emulator thats why.

[Bounty) TPD App Throttling Disablement
I'll Personally donate $50 to anyone that comes up with a easy solution to disable the app throttling. I'm well aware that some Developers can exclude the TPD commit, but it seems like devs aren't too keen on doing that. I also realize that...
forum.xda-developers.com

Orwennes said:
[Bounty) TPD App Throttling Disablement
I'll Personally donate $50 to anyone that comes up with a easy solution to disable the app throttling. I'm well aware that some Developers can exclude the TPD commit, but it seems like devs aren't too keen on doing that. I also realize that...
forum.xda-developers.com
Click to expand...
Click to collapse
This isn't related with my question.

noobzayt said:
This isn't related with my question.
Click to expand...
Click to collapse
Isn't it?

samwhiteUK said:
Isn't it?
Click to expand...
Click to collapse
Isn't that obvious that i am not talking about app specific throttling but power limit throttle like laptop cpus.

noobzayt said:
Isn't that obvious that i am not talking about app specific throttling but power limit throttle like laptop cpus.
Click to expand...
Click to collapse
How do you know which the phone is doing?

samwhiteUK said:
How do you know which the phone is doing?
Click to expand...
Click to collapse
Because chipset constantly behaves like i mentioned regardless which app is running. So i know this thing isn't related with app spesific.

noobzayt said:
i am using emulator thats why.
Click to expand...
Click to collapse
maybe yours phone overheating? [Bounty) TPD App Throttling Disablement works for me perfect, even on hard encoding tasks, just keeping my phone cool