Database Users

Overclocking N1

You can overclock n1 only to 1.190ghz, while desire hd 1.9ghz and the htc desire Z (G2) 2.0ghz. Does N1 has to old cpu?
-------------------------------------
Sent via the XDA Tapatalk App with my Sexy Nexy

Yes. 1st Gen snapdragon
Sent from my Nexus One using XDA App

if you want to OC you N1 go and OC you Desktop is the best choice

Why would you wanna over clock your phone? I have my N1 clocked @ 691 and works really fast with the MIUI rom and battery performance is better than stock. I'm not a fan of custom rom & rooting but I been pretty pleased so far. overclocking the nexus one will drain your battery like crazy plus the 1st Gen of snapdragons weren't as good with graphics as the A4chips and humming birds.

i have mine underclocked too and it works fine. try going a step further and underclocking it to like 422 when it's sleeping/standby. it'll help your battery

josemedina1983 said:
Why would you wanna over clock your phone? I have my N1 clocked @ 691 and works really fast with the MIUI rom and battery performance is better than stock. I'm not a fan of custom rom & rooting but I been pretty pleased so far. overclocking the nexus one will drain your battery like crazy plus the 1st Gen of snapdragons weren't as good with graphics as the A4chips and humming birds.
Click to expand...
Click to collapse
The connection between clockspeed and power consumption is not as strong as you think. But without a doubt it has an influence. Much more important is the voltage. If you "undervolt" the Nexus One CPU you can even get better battery live with higher clockspeed.
And if you use a tool to change the clockspeed depending on the situation (display on/off, battery % left, workload) and undervolt the cpu you can safe A LOT of juice.
With Wildmonks kernel, MIUI and SetCPU I get a much better lifetime than ever before even though my Nexus runs at 1152MHz.

Actually, the frequency makes a BIG difference in power consumption. Think of it this way - each clock causes changes propagating in transistors, which are the actual power draw. More clocks = more changes = more power drawn. As easy as that.
So, having 10% higher frequency and 10% lower voltage compensates each other.
Nexus has examples that overclock to 1.5GHz when overvolted, like Desire Z and Desire HD (both of those have to be overvolted to go up stable from 1.2GHz). Most of Nexus Ones fail when overclocking and don't reach higher than 1.2GHz, but it might be not because of the CPU, but because of other devices on system board.

Generally, it is only when you change the voltage (which is required to stabilize the higher frequency) that you see noticeable differences in battery life.
Jack_R1 said:
Actually, the frequency makes a BIG difference in power consumption. Think of it this way - each clock causes changes propagating in transistors, which are the actual power draw. More clocks = more changes = more power drawn. As easy as that.
So, having 10% higher frequency and 10% lower voltage compensates each other.
Nexus has examples that overclock to 1.5GHz when overvolted, like Desire Z and Desire HD (both of those have to be overvolted to go up stable from 1.2GHz). Most of Nexus Ones fail when overclocking and don't reach higher than 1.2GHz, but it might be not because of the CPU, but because of other devices on system board.
Click to expand...
Click to collapse

willverduzco said:
Generally, it is only when you change the voltage (which is required to stabilize the higher frequency) that you see noticeable differences in battery life.
Click to expand...
Click to collapse
Ok, some additions required.
Leakage is also dependent on power, and the dependency graph isn't linear - and starts breaking upwards at some point, usually being a tad above the max designed voltage.
Going down in voltage makes leakage change approximately linear, and doesn't affect nearly as much as going up.
Overclocking will draw power just as I noted above - exactly with the same percentage difference - only when the clock is reaching the overclocked area, which happens only when you're playing games or doing CPU-intensive tasks.
Undervolting will affect leakage, which happens 100% of the time.
So yes, when running in dynamically scaled environment, undervolting has more effect than overclocking. On desktop PC, running the same clock frequency constantly, the effect is the same.

Very True. And I wasn't saying that overclocking, while at the same voltage, didn't draw ANY more power... I just am trying to say that (for example in this graph) overclocking only has a small effect on power draw until you actually change the voltage. In that same example, going from 3.4 to 3.8 GHz only adds about 6% current draw while at the same vCore, while going up a similar amount in clock speed.
I'd even wager to say that if you're slightly under-volted and as heavily overclocked as you can go at that given voltage, you'll save some trivial amount of power versus stock because of the fact that voltage affects power draw significantly more than clock speed. I would also wager that if you are at an overclocked speed and are at stock voltage, the amount of current and power draw will be almost indistinguishable to the end user, since things like display will almost always use much more power if the display is on for any appreciable amount of time.
Jack_R1 said:
Ok, some additions required.
Leakage is also dependent on power, and the dependency graph isn't linear - and starts breaking upwards at some point, usually being a tad above the max designed voltage.
Going down in voltage makes leakage change approximately linear, and doesn't affect nearly as much as going up.
Overclocking will draw power just as I noted above - exactly with the same percentage difference - only when the clock is reaching the overclocked area, which happens only when you're playing games or doing CPU-intensive tasks.
Undervolting will affect leakage, which happens 100% of the time.
So yes, when running in dynamically scaled environment, undervolting has more effect than overclocking. On desktop PC, running the same clock frequency constantly, the effect is the same.
Click to expand...
Click to collapse

Jack_R1 said:
Actually, the frequency makes a BIG difference in power consumption. Think of it this way - each clock causes changes propagating in transistors, which are the actual power draw. More clocks = more changes = more power drawn. As easy as that.
So, having 10% higher frequency and 10% lower voltage compensates each other
Click to expand...
Click to collapse
I wouldn't call 10% more peak power consumption big if you take in account that the cpu is only running at the max clock speed a very small amount of time. 90% of the time the device is sleeping anyway and even if it's not you barely need the max clock speed. But if you do you will recognize the difference.
On the other side the reduced voltaged can safe you power all the time.
willverduzco said:
I'd even wager to say that if you're slightly under-volted and as heavily overclocked as you can go at that given voltage, you'll save some trivial amount of power versus stock because of the fact that voltage affects power draw significantly more than clock speed. I would also wager that if you are at an overclocked speed and are at stock voltage, the amount of current and power draw will be almost indistinguishable to the end user, since things like display will almost always use much more power if the display is on for any appreciable amount of time.
Click to expand...
Click to collapse
That's exactly what I experienced.

Pommes_Schranke said:
I wouldn't call 10% more peak power consumption big if you take in account that the cpu is only running at the max clock speed a very small amount of time. 90% of the time the device is sleeping anyway and even if it's not you barely need the max clock speed. But if you do you will recognize the difference.
On the other side the reduced voltaged can safe you power all the time.
Click to expand...
Click to collapse
Yes, you're right, and that's why I corrected myself in my second post. I totally forgot about the frequency scaling.

Off topic, but this is why I love XDA. Rational debate over a subject by intelligent people, where there usually isn't flaming. Thanks added to the two of your posts.

Underclock

Any idea how to underclock I've heard it increases battery life?
Sent from my Desire HD using XDA App

Root > setcpu
Sent from my HTC Desire S using xda premium

If you are using a custom ROM then the ondemand governance will take care of the underclocking when not in use and increase the clock frequency when your usage demands it. That provides reasonable battery saving while not compromising on performance.
Fixing the frequency to a lower limit might increase the battery life but has serious performance issues. Might be handy in critical battery saving situations though.
SetCPU, CPU Master etc.. Such apps can let you modify the upper and lower clocking limits.

Cheers for the replies,where do I get the oc,as for set CPU..you mean one of killersloths kernel scripts?
Sent from my Desire HD using XDA App

Most of the kernels that you can find in the development section have OC scripts already in them.
SetCPU is an app and can be found in the market : https://market.android.com/details?...wsMSwxLDEsImNvbS5taHVhbmcub3ZlcmNsb2NraW5nIl0.

keep in mind that undervolt = giving less power to CPU = can cause damage overtime or reduce battery life.
I mean all these undervolt things don't increase battery time by a huge difference than stock and risking your CPU for just 15 minutes of battery life isn't worth it in my opinion...

[Q] Interactive vs. Ondemand

I have been experimenting with some various governors and have found that interactive and ondemand work best on the nexus 7. My question is which one will have better battery life on the nexus 7? Which one will have the least stuttering? Just curious. Everyone seems to state that interactive will be the better governor, but I tend to notice interactive heats up more in chrome. Anyone else notice this?
Any helps would be appreciated
-Fishwithadeagle

When running low on battery I found conservative with runnable works the best for me. Undervolting by 50-100mV and running custom kernel plus ROM can also contribute. I always turn my WiFi and GPS off when not being used. I would not know of such imperceivable details between Interactive and Ondemand as battery, stutter or heat. Mine reaches 70 degress celsius under overclocked heavy benchmarking load.

For battery life, stick with interactive or conservative.
For less lag and stuttering, use ondemand or performance.
Sent from my Nexus 4 using Tapatalk 2

Wow, you couldn't be more wrong. You have it completely opposite. For better battery life, and not to have your frequency set to the highest value, almost at all times, go with ondemand. If you want less lag, and stuttering, but worse battery life, interactive.
Test it yourself with setcpu, and CPU spy, and you'll see exactly what I'm talking about.

(Q) Can undervolting too much cause more heat?

As the title says, can undervolting too much cause more heat than just a little undervolting? I'm at - 175mv on every frequency and my phone usually gets quite warm even with normal use, music, etc. Maybe about 45°c...thanks! (I don't over clock, or play games)
Sent from my Carbon powered AKFAUX fueled monster NEXUS 4

45C is normal for this device, when its in the 60+ range then it's time for concern. Undervolting is in millivolts not volts so the change in temperature and battery is not very significant.

However back in the Nexus S days some genius dev measured that undervolting too much forced the cpu to redo some calculations, which made it use more power than the uv would save. Whether that's what's happening to you I wouldn't know, but it could be.
In the process the dev also found out that undervolting didn't save any noticeable amount of battery. Of course, whether the same goes for our cpu isn't known for sure, but I would guess the same concept applies.
Sent from my Nexus 4 using Tapatalk 4 Beta

One of the main reasons to UV is to prevent overheating/reduce overall temperature increase. So in other words, no. Just don't UV too much (-125 mV MAX)!
Sent by carrier pigeon

your cpu temp is completely normal, a bulls-eye type of normal too. and yes, undervolting too much can cause the phone to work harder, which in turn can cause more heat.

[Q] Questions about undervolting Nexus 4.

Hello!
I heard about the term "UnderVolting" and I heard it would give me better battery life.
I want to do it but I have few questions before.
1. Is undervolting affects the CPU , GPU or Battery?
2. Can It damage the device?
3. Can it decrease the device performance?
Thanks!

Wassupdog said:
Hello!
I heard about the term "UnderVolting" and I heard it would give me better battery life.
I want to do it but I have few questions before.
1. Is undervolting affects the CPU , GPU or Battery?
2. Can It damage the device?
3. Can it decrease the device performance?
Thanks!
Click to expand...
Click to collapse
1. It effects the cpu. When you undervolt you are reducing the amount of power that is supplied to the cpu depending on what speed the cpu is running at.
2. It is unlikely to damage the device physically but if you undervolt too far the cpu can start failing actions resulting in corruption, but the most common symptom is that it will reboot itself if you go too low.
3. Undervolting can reduce performance but going down -100 mv across the board is usually stable for most.
Sent from my Nexus 4 using xda app-developers app

Alex240188 said:
1. It effects the cpu. When you undervolt you are reducing the amount of power that is supplied to the cpu depending on what speed the cpu is running at.
2. It is unlikely to damage the device physically but if you undervolt too far the cpu can start failing actions resulting in corruption, but the most common symptom is that it will reboot itself if you go too low.
3. Undervolting can reduce performance but going down -100 mv across the board is usually stable for most.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks!
Is it recommended to undervolt?
I just want a better battery and around the same performance as it now.

You are confusing undervolt with underclock. UC is a proven way to increase battery, but it directly makes the CPU run slower. UV will make the CPU/GPU/RAM receive less milivolts, and it will only increase battery, and not decrease performance. The thing with UV is that if the CPU at any given time does not get enough power, it can't perform a given task, and your phone will reboot.
Sent from my LG-P760 using xda app-developers app

In a nutshell UV will not destroy your phone and is it recommended? If you are in xda then you know the risks or at least should read up on the risks. I would say 90% of the custom kernels are undervolted out the box and yes its a great help. I have been UV, UC and sometimes even OC for years now with no negative effects. Give it a shot and if you are worried start slow like -25.
Try mathkids kernel(JSS roms only) which is undervolted -100 and if you read the thread its never been an issue for anyone. I have heard that UV may cause some issues with Maps locking fast

Dr.Molestratus said:
You are confusing undervolt with underclock. UC is a proven way to increase battery, but it directly makes the CPU run slower. UV will make the CPU/GPU/RAM receive less milivolts, and it will only increase battery, and not decrease performance. The thing with UV is that if the CPU at any given time does not get enough power, it can't perform a given task, and your phone will reboot.
Sent from my LG-P760 using xda app-developers app
Click to expand...
Click to collapse
I'm not Confusing undervolt with underclock.
Undervolting can and does reduce performance if you go too far. (Not far enough to cause reboots)
Underclocking is not a proven way to increase battery, in fact it's quite controversial.
It's called race to idle.
Pretty much all processors have great power savings at idle speeds.
By lowering the clock speed common tasks and background processes take longer to perform. Thus keeping the cpu at a higher clock rate (using more mv) for longer and overall using more battery than what it would have done at a higher speed.
From my own tests -150 mv undervolt resulted in slower and sometimes even laggy performance. -100 is great
Underclocking to 1ghz shortened my average daily battery life by nearly 2 hrs compared to running at stock 1.5
Say what you like about stats but these are the results I found from actual usage
Sent from my Nexus 4 using xda app-developers app

UV will reduce how hot your phone gets.. and if your phone gets too hot thermal throttling will reduce the cpu speed.. and thus if u UV it will reduce thermal throttling and will increase performance..

Thanks to everyone !