When I look at the stock voltage table, every processor speed bellow 378 has the same voltage. Doesn't this mean that underclocking won't save battery, or am I missing something?
Sent from my GT-I9505G using xda app-developers app
macravin said:
When I look at the stock voltage table, every processor speed bellow 378 has the same voltage. Doesn't this mean that underclocking won't save battery, or am I missing something?
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
As far as I know this is where undervolting comes in. At least that's the path I take anyway.
macravin said:
When I look at the stock voltage table, every processor speed bellow 378 has the same voltage. Doesn't this mean that underclocking won't save battery, or am I missing something?
Click to expand...
Click to collapse
Electrical engineer here to explain.
The power used by a digital device running at a given clock speed is as follows:
P = C * V^2 * F
Where P is the power consumed, C is the capacitance, V is the voltage, and F is the clock frequency.
The capacitance of the CPU is fixed, there's nothing we can do about that.
If you lower either V or F, you'll save power. Because the voltage is squared, undervolting has more of an effect than underclocking, but both are still useful.
If you lower the frequency by 10%, you'll save 10% power.
If you can lower the voltage by 10% though, you'll save 19% power.
Personally, I lowered all of my voltages about 10%, and I don't actually let my phone underclock below 378 MHz, because it just takes it too long to respond to the power button and clock back up to a usable speed if I let it go down below that.
Related
Hello..anyone can teach me how to overclock xperia x10
Bootloader is not unlocked. It's impossible at the moment.
Sent from my X10i using XDA App
satAxOnic said:
Hello..anyone can teach me how to overclock xperia x10
Click to expand...
Click to collapse
First, you crack the bootloader.
When you've done that, I'm guessing you allready figured out how to OC the CPU
Sent from my FreeX10i beta2.
satAxOnic said:
Hello..anyone can teach me how to overclock xperia x10
Click to expand...
Click to collapse
For now just use the overclock widget. set top two settings as high as you want up to 998 click on off screen frequency. set between 246 and next number you choose. set at boot save. define settings at what mhz you like and experiment. do not run on screen and off screen freq at max. i have had my battery sweating and even plugged in all day and not gained a single % of charge. until boot loader is cracked.... this is all you can do.
xperiax10a
2.2b2
Bummmod
gapps1901
quadrant 1800
linpack 40.XX
Although it's impossible today because of bootloader, note it's always dangerous and not great to overclock embedded cpus.
You can't overclock a lot, as you have a battery (X10 works about 5-10 hours with full speed - 998MHz), and the CPU only has passive elements to cool. Overclock can damage your CPU and your motherboard, stress all elements and low your battery life (battery charge and cycle of charge). (Even there's a self shutdown when too hot)
You can get an idea of overclock on Nexus forum, as we have the same CPU (Snapdragon 8250) - I saw overclock up to 1300 MHz, but it's really not looking safe to me
Thanx everyone..
Perceval from Hyrule said:
Although it's impossible today because of bootloader, note it's always dangerous and not great to overclock embedded cpus.
You can't overclock a lot, as you have a battery (X10 works about 5-10 hours with full speed - 998MHz), and the CPU only has passive elements to cool. Overclock can damage your CPU and your motherboard, stress all elements and low your battery life (battery charge and cycle of charge). (Even there's a self shutdown when too hot)
You can get an idea of overclock on Nexus forum, as we have the same CPU (Snapdragon 8250) - I saw overclock up to 1300 MHz, but it's really not looking safe to me
Click to expand...
Click to collapse
Depends also on the voltage (as long as your voltage isn't increasing as you overclock, it isn't really that harmful as long as you watch the heat), and what you have your underclock speed set to with screen off (as this can in some sense reverse some of the possible "damage")...
I had my htc hero overclocked to 710 with the screen on, and underclocked 176 with the screen off and it ran a lot better.
I digress, I see no purpose in doing so when you already have a 1ghz processor that is super fast. I only really see a point in overclocking if the possible benefit is greater than the possible harm, and in this circumstance, I really don't think you would see that much benefit.
fiscidtox said:
Depends also on the voltage (as long as your voltage isn't increasing as you overclock, it isn't really that harmful as long as you watch the heat), and what you have your underclock speed set to with screen off (as this can in some sense reverse some of the possible "damage")...
I had my htc hero overclocked to 710 with the screen on, and underclocked 176 with the screen off and it ran a lot better.
I digress, I see no purpose in doing so when you already have a 1ghz processor that is super fast. I only really see a point in overclocking if the possible benefit is greater than the possible harm, and in this circumstance, I really don't think you would see that much benefit.
Click to expand...
Click to collapse
I have seen considearable difference when maxed out. however the dangers are high of overheat. ive done it once and onetime only. kept on and off screen at 998 and hat it plugged in all day with out a single gain of battery. it was like on life support and was hot enough the phone was sweating even when sitting next to a fan blowing on it constantly.:-( since then i have made adjustments to run between 700 and 998mhz on screen and min 246 and 400mhz when screen off.
if looking for better performance without the overclock and good drain of battery, download and install sysctl from market and follow settings below.
min free kb: 900000
dirty ratio:500000
dirty background:200000
vfs cache pressure:10
Oom allocating: checked
On SetCPU there is Set on boot- to be checked or not?
Sent from my X10i using Tapatalk
it should be checked
OC can damage yo device. Id say its better to hv a lil slower device than a dead device
Sent from my X10x using XDA App
live4speed said:
OC can damage yo device. Id say its better to hv a lil slower device than a dead device
Sent from my X10x using XDA App
Click to expand...
Click to collapse
Not in all instances. Depends on the quality of the chip. Lot of chips are capable of handling higher speeds and temps but are set lower quality assurance.
For instance, I've got a NookColor that has base CPU set at 800MHz and is now overclockable to 1.2GHz
We'll have to do stress tests on some to see what they're capable of.
andrewddickey said:
Not in all instances. Depends on the quality of the chip. Lot of chips are capable of handling higher speeds and temps but are set lower quality assurance.
For instance, I've got a NookColor that has base CPU set at 800MHz and is now overclockable to 1.2GHz
We'll have to do stress tests on some to see what they're capable of.
Click to expand...
Click to collapse
Agreed.
My Motorola Defy has a Omap3630 that comes at 800MHz,stock but can be easily overclocked to 1.3GHz without a sweat.
Just depends on the chip's capacity of "Stress".
Respect
What App is everyone using to set their cpu governor along with voltage control? Tegrak? SetCPU?
Also, if you can run 100 mhz on your rom.. Is it even worth using?
Sent from my SCH-I500 using XDA App
Crap wrong section. Move please.
Sent from my SCH-I500 using XDA App
What kernel are you using? If on an OTB kernel, you can use voltage Control. Actually the newest version of voltage control can change governor for any kernel i think, though you can't change voltage settings.
elarson006 said:
What kernel are you using? If on an OTB kernel, you can use voltage Control. Actually the newest version of voltage control can change governor for any kernel i think, though you can't change voltage settings.
Click to expand...
Click to collapse
Otb
Sent from my SCH-I500 using XDA App
Looks like you can change voltages as well on this new version, thanks . Any ideas about the 100 mhz step?
Sent from my SCH-I500 using XDA App
Increasing the voltage for the most part increases the amount of power the CPU consumes (and amount of heat generated!). Higher clock speeds require more power, and therefore a higher voltage. As clock speeds decrease, it's safer to decrease the voltages.
The idea of the having all this control is to allow the user to customize how their phone operates. You can overclock it and go for performance all the way, or keep the clock speeds low so you can decrease voltage and save battery. If you want, you can create a mix between them by decreasing the voltage different amounts on each of the clock speed steps.
Voltage control does the clock voltage and governor for me. I can use 100mhz with CM7 but I wouldn't be too worried about not having it.
Keithn said:
Voltage control does the clock voltage and governor for me. I can use 100mhz with CM7 but I wouldn't be too worried about not having it.
Click to expand...
Click to collapse
Well the thing is i read that it's essentially worthless, as it draws the same voltage as the 200 mhz step... Hence why it's disabled by default
Sent from my SCH-I500 using XDA App
Putting the CPU all the way down to 100 MHz can cause some problems anyway, particularly if you use your phone to play music. A lot of software isn't designed to operate on clock speeds that low. I only go down to 200 MHz.
kallell said:
Well the thing is i read that it's essentially worthless, as it draws the same voltage as the 200 mhz step... Hence why it's disabled by default
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Although you wouldn't notice the difference because it's so little, you will save more battery if you use 100mhz. Because it's on 100mhz you will be able to put it a lot lower than 200mhz. Many people including me is putting -150 with 100mhz.
deaffob said:
Although you wouldn't notice the difference because it's so little, you will save more battery if you use 100mhz. Because it's on 100mhz you will be able to put it a lot lower than 200mhz. Many people including me is putting -150 with 100mhz.
Click to expand...
Click to collapse
Problem for most undervolting that low at 100mhz would be running any music app while the screen is off then upon waking up your phone it would freeze up.
I find that setting setCPU to 450 mhz (900 mhz because of the dual core) the phone works perfectly for my day to day use.
Would underclocking to 450 mhz from 1000 mhz save a lot of battery, or the process of underclocking would take battery to make it equivalent to leaving regular clock.
Not really sure. I've had it set so it goes to 400mhz when the screens off since I had it. I'm sure it helps a little but i doubt it's going to make you get as extra day of battery or anything
Sent from my MB860 using Tapatalk
primeboss said:
I find that setting setCPU to 450 mhz (900 mhz because of the dual core) the phone works perfectly for my day to day use.
Would underclocking to 450 mhz from 1000 mhz save a lot of battery, or the process of underclocking would take battery to make it equivalent to leaving regular clock.
Click to expand...
Click to collapse
I have to intervene here. When you set it to 450 its not 900 because of the dual core. the cores dont add up speeds.
The Atrix doesnt have a 2ghz processor because its 1ghz but two cores.
But to answer your question - yes you would save battery, but the phone would be very slow because you would be at 450 (not 900 or 1ghz)
i have mine set at 600mhz and its fine through the day though i dont do it for battery but to keep it nice and cool(that 1ghz makes it 60C+ easy) but i guess it helps
You have to consider that a lower clock speed means that the CPU must process things for a longer period of time. Sure at a lower speed it will process using less power but the longer period of time it needs to process may mean that the total power consumption is still the same or even higher since the CPU still consumes power simply by being turned on.
palmboy5 said:
You have to consider that a lower clock speed means that the CPU must process things for a longer period of time. Sure at a lower speed it will process using less power but the longer period of time it needs to process may mean that the total power consumption is still the same or even higher since the CPU still consumes power simply by being turned on.
Click to expand...
Click to collapse
+ 1. I'm starting to believe that even the screen-off profile (I have it set on the lowest) has a negative effect on the battery if you use your phone a lot and keep turning the screen back on all the time! Am turning it off now to try..
Sent from my Motorola Olympus using XDA Premium App.
What are the best settings to have you phone's CPU speed set at? I'm looking for both good performance and good battery. Also I am using the default overclocker, what is the best one? Thank you guys for your time.
Sent from my LG-VM670 using XDA Premium App
I use SMARTASS as my CPU speed governor and I set my CPU to 480-748 MHz, seems pretty stable for me.
Sent from my LG-VM670 using xda premium
thaunknownartist said:
What are the best settings to have you phone's CPU speed set at? I'm looking for both good performance and good battery. Also I am using the default overclocker, what is the best one? Thank you guys for your time.
Sent from my LG-VM670 using XDA Premium App
Click to expand...
Click to collapse
Overclocking values differ from phone to phone. Test it out with different values and use the one which is stable for you.
This was just discussed in the IHO technical-discussion thread, as a matter of fact.
My phone is stable for most stuff at 806 MHz, but sometimes the camera will cause a freeze/reboot. So I run at a 786 MHz max. Your phone will be different; this has to do with minute physical differences between individual chips.
The thing to keep in mind when overclocking is that the processor in our phone (unlike those of many other phones) does not make use of dynamic voltage scaling. There are only two voltage levels: a lower one if the phone is running at or below (or is it just below? correct me if I'm wrong, guys) 480 MHz, and a higher one if the phone is running above. So below 480 MHz, the system will give the processor a certain amount of voltage (period), and above, the processor will get a certain higher amount of voltage (period).
Because of that, the tests that have been done indicate that 806 MHz is the sweet spot for battery efficiency when the phone is in use--and the closer you get to 806, the better. Thus, I've had the following settings for quite some time:
786 MHz min
786 MHz max
Performance governor
which has treated me pretty well. On a day of light to moderate use, I'd end up with 65-75% battery left (occasionally more like 80%), depending on cell signal where I am et al. And it gives me probably the best performance I'm gonna get out of this phone.
However, I very recently decided to change the minimum to below that 480 MHz threshold and see what a lower voltage when idling would do for my battery life. My current settings are:
320 MHz min (may change to 480)
786 MHz max
Smart*** governor
There is actually a noticeable performance decrease when I first wake the phone up, so I may switch governors as well. In any case, I've had those settings for only one full day now, but for that one day the battery life was noticeably better. I'll post an update when I've had a few more days to test.
As always, it's difficult to quantify battery life in a reliable/rigorous manner (much less a universally applicable one), so YMMV.
My phone is overclocked. but i always lower Maximum Mhz of it to 1113Mhz or lower by useing SetCpu. so i need to know even if i lower the processor speed will my battery drain because my phone is overclocked.
Overclocking will drain battery more, undervolting less
It will unless you also undervolt....undervolting and overclocking on the same time sends the phone in another dimension and without losing to much juice.
Sent from my GT-I9300 using xda app-developers app