This may be a stupid question but, if the voltage can be underclocked for the cpu, how about lowering the voltage output for the screen?
Related
Been wondering this for a few days. Does setCPU raise CPU voltage when it overclocks ?
Because if it doesn't, then battery life shouldn't be affected.
I'm not sure about SetCPU itself, but in order to overclock, the voltage must be raised anyway - for example on my milestone ( using milestone-overclock ) when i set the maximum to 1.2Ghz, i have to change it to 80vsel. ... so battery life will be affected when you load a custom ROM or load the kernel module to overclock.
so when you load the overclocked setting in setCPU, it uses the vsel specifed from there, right? which would result in more voltage
Does anyone else think the CPU running at 480Mhz-800Mhz screen on is a bit too high? It's more than capable running at a 122Mhz minimum - heck, even 19Mhz, although it doesn't spend much time at 19Mhz. Also, if perflock is enabled, it locks itself to 245Mhz only when screen off - still seems a bit too high for me, considering there's lower selectable frequencies.
Anyone who's temprooted their device: Are you using SetCPU to change the CPU frequencies/disabling perflock? I have my Chacha running at 800Mhz max / 122Mhz min perfectly fine (running my battery down for a while to see if the battery life benefits) - although occasionally, it still locks itself to 122Mhz even after turning the screen on for about a minute, which I believe is a kernel issue
For reference, the frequency options are: 19Mhz, 122Mhz, 128Mhz, 245Mhz, 480Mhz and 800Mhz.
128Mhz doesn't actually work, and if it's selected, it uses 245Mhz instead even though SetCPU says "128 min"
Unfortunately I can't help you, but I'm totally interested on the subject!
As far as I know and tested on other android devices, setting the CPU freq too low will cause some unwanted behavior like being unable to power up the screen. Happened on a Galaxy S, where I've set the freq to 19Mhz (or something similar) and I've locked the screen. Pressing the power button did nothing so I had to re-flash the rom.
really need low cpu frequency?
low frequency is certainly not good. For chachar, I just hope 600 frequency could be done the hardware itself(not by setcpu). I hate the power consumption is too big, and the machine is easy to get hot.
Alex C. said:
As far as I know and tested on other android devices, setting the CPU freq too low will cause some unwanted behavior like being unable to power up the screen. Happened on a Galaxy S, where I've set the freq to 19Mhz (or something similar) and I've locked the screen. Pressing the power button did nothing so I had to re-flash the rom.
Click to expand...
Click to collapse
True, setting the frequency too low is bad for some devices, but in my personal experience with my Chacha, I can actually run mine at 19Mhz min/800Mhz max and have little to no problems, since it doesn't spend much time at 19Mhz anyways. (I use no SetCPU profiles, as I feel they have little to no benefit on battery life.)
All of this is just a thought though, since HTC set the minimum to 480Mhz with the screen on which seems way too high to me :/
Also, locking the CPU to a single low frequency was actually a bad thing on one of my old devices, a Desire Z, which usually caused wake problems, etc.
semanty said:
low frequency is certainly not good. For chachar, I just hope 600 frequency could be done the hardware itself(not by setcpu). I hate the power consumption is too big, and the machine is easy to get hot.
Click to expand...
Click to collapse
600Mhz is possible indeed - the MSM7227 processor that the Chacha uses is actually rated at 600Mhz, but HTC factory overclocked it to 800Mhz. It would require a custom kernel to have 600Mhz added back in
anyone thought of a way to undervolt???? i mean use less voltage for each frequency..am trying to search for kernels to flash but cudnt find any
Hi,
I'm running NSCollab 1.0.50 with franco.kernel from Nov. 13 on a I9020a.
I'm playing around with undervolting the cpu and trying to find the minimum stable voltages. My procedure is to start the voltage as low as the voltage for the frequency step before it and then increase the voltage in 25mV steps until everything is stable. I am using SetCPU to adjust the voltages.
So far this has worked for every frequency step except for the 100MHz step. I can't seem to find the lowest voltage for 100MHz. For example, the 200MHz step will be unstable at 750mV but is stable at 775mV. The 100MHz step is never unstable no matter how low I set the voltage. I can even set it to 0mV (which I know is ridiculous) and it wont freeze.
Does anyone know why the phone doesn't become unstable at ridiculously low voltages for the 100MHz step? I see that the slider to adjust voltages in SetCPU only goes down to 600mV but I can manually type in lower voltage values. Is there some kind of hard-set voltage minimum for the cpu that even SetCPU can't bypass when setting the voltage? Is the phone violating the laws of physics?
Thanks in advance
What's your min frequency in setcpu?
Oh yeah, I should have posted that.
100MHz min
1000MHz max
lazy scaling
i heard that ...
force phone running in low mV MAY damage the CPU and other parts of it and destablize it...
=================================
i have seen some applications that would ignore your input value when it is not logical ...
for example like NS tools , one of them , i don't remember which exactly , perhaps it's live OC, for live OC, if you set value lower then 100 , it would automatically set back to 100 ... i think this may be same as your min frequency case...
nathanson666 said:
Hi,
I'm running NSCollab 1.0.50 with franco.kernel from Nov. 13 on a I9020a.
I'm playing around with undervolting the cpu and trying to find the minimum stable voltages. My procedure is to start the voltage as low as the voltage for the frequency step before it and then increase the voltage in 25mV steps until everything is stable. I am using SetCPU to adjust the voltages.
So far this has worked for every frequency step except for the 100MHz step. I can't seem to find the lowest voltage for 100MHz. For example, the 200MHz step will be unstable at 750mV but is stable at 775mV. The 100MHz step is never unstable no matter how low I set the voltage. I can even set it to 0mV (which I know is ridiculous) and it wont freeze.
Does anyone know why the phone doesn't become unstable at ridiculously low voltages for the 100MHz step? I see that the slider to adjust voltages in SetCPU only goes down to 600mV but I can manually type in lower voltage values. Is there some kind of hard-set voltage minimum for the cpu that even SetCPU can't bypass when setting the voltage? Is the phone violating the laws of physics?
Thanks in advance
Click to expand...
Click to collapse
The method you are using is wrong. I did the same thing a few days ago, and changing the values like that won't work.
What I found out is that to easily find stable values, in SetCPU put your max as 200MHz and your min at 100MHz. Use ondemand. Keep 200MHz at stock volts and 100MHz try an undervolt.
Apply everything then slide the minimum frequency slider around a bit. I guarantee you 600mv will freeze. Do the same for each value, if testing 200MHz, use 400MHz as your max and 200MHz as your min, stock volts for 400MHz. Slide the minimum frequency left and right.
Sounds weird, but it works. Do this until you find a voltage for each frequency. Then put your frequency max and frequency min at the same value (IE 200MHz) and launch a game or a demanding app and play for a lil while, even if performance suck. Hope it doesn't freeze on you, but if it does, bump the voltage a bit.
If you want good starting values, here's the values I have found that work for me and are 100% stable. No force close over the last few days since I started using those:
100MHz 875mv (75mv under stock)
200MHz 875mv (75mv under stock)
400MHz 900mv (150mv under stock)
800MHz 1125mv (75mv under stock)
1000MHz 1225mv (25mv under stock)
I'm pretty new to Android. I got my N5 2 months ago and rooted it as soon as I took it out of the box to get rid of the navigation bar. Didnt install any ROM or kernal.
What I did today was try to overclock it. I wanted to test the performance upgrade with Geekbench 3.
I got 2500. Tried to overclock with this app called: No-frills CPU control. And suddenly I get no higher than 2000...... Tried everything. I'm stuck at a multi core score of 2000 in geekbench while it should be 2500>.
WTF DO I DO? My device is noticeably slower, it's like a GS4 D: I'd rather not install any kernals/Roms
I set the minimum CPU frequency to 300Mhz and max to 2.266Ghz
Hi,
Thermal throttling..., overclocking produces more heat than the stock CPU freq so more thermal throttling. To prevent any damage, the CPU freq decreases according to the CPU temperature...
Let cool down your phone.
Hammer_Of_The_Gods said:
Hi,
Thermal throttling..., overclocking produces more heat than the stock CPU freq so more thermal throttling. To prevent any damage, the CPU freq decreases according to the CPU temperature...
Let cool down your phone.
Click to expand...
Click to collapse
Sure, I'll turn it off for a while.
Just to make sure: the standard CPU frequencies are 300Mhz MIN and 2.266Ghz MAX, right?
Fandrold said:
Sure, I'll turn it off for a while.
Just to make sure: the standard CPU frequencies are 300Mhz MIN and 2.266Ghz MAX, right?
Click to expand...
Click to collapse
Yes, that's right 300 Mhz-2,26 Ghz.
Not necessary to turn your phone OFF , when it boots it's a process that causes "heat" at the beginning then you will need to let it cool down again. EDIT: oups, you mean the thermal throttling OFF maybe?
Don't touch it for a while, airplane mode can help. If you are in a "hot" country/weather, air cooling, fridge...
We speak about this here: http://forum.xda-developers.com/goo...5-user-benchmark-thread-added-t2506965/page42.
Hammer_Of_The_Gods said:
Hi,
Thermal throttling..., overclocking produces more heat than the stock CPU freq so more thermal throttling. To prevent any damage, the CPU freq decreases according to the CPU temperature...
Let cool down your phone.
Click to expand...
Click to collapse
I've let it cool down and I got my old performance back . Never knew the solution would be so simple. Thanks.
Does anyone know what are default cpu voltage values for our cpu?