I don't know if this is tandard on all kernels but on my kernel for example the steps are like that:
1000mhz=1175mv
1100mhz=1225mv
1200mhz=1275mv
Now at THIS point it starts getting weird. Suddenly the voltage increases by 25mv each
1300mhz=1300mv
1400mhz=1325mv
then it's 50 again
1500mhz=1375mv
then 25 again
1600mhz=1400mv
I know a bit about overclocking and overvolting CPUs. And I know that the higher you go the bigger the steps to increase voltage have to be (assuming you always choose the lowest voltage possible on which everything is stable). That's just due to physics. And now the opposite is the case... Why is the step from 1,5ghz to 1,6ghz only 25mv but from 1000 to 1100mhz it's 50mv? This doesn't make much sense.
Seriously no wonder that my phone is instable on 1600mhz. I guess the voltage just isn't high enought so the transistors aren't able to do their job properly within that short amount of time they're given at 1,6ghz.
Are the voltage steps like that on every kernel?
Frozenthunder said:
I don't know if this is tandard on all kernels but on my kernel for example the steps are like that:
1000mhz=1175mv
1100mhz=1225mv
1200mhz=1275mv
Now at THIS point it starts getting weird. Suddenly the voltage increases by 25mv each
1300mhz=1300mv
1400mhz=1325mv
then it's 50 again
1500mhz=1375mv
then 25 again
1600mhz=1400mv
I know a bit about overclocking and overvolting CPUs. And I know that the higher you go the bigger the steps to increase voltage have to be (assuming you always choose the lowest voltage possible on which everything is stable). That's just due to physics. And now the opposite is the case... Why is the step from 1,5ghz to 1,6ghz only 25mv but from 1000 to 1100mhz it's 50mv? This doesn't make much sense.
Seriously no wonder that my phone is instable on 1600mhz. I guess the voltage just isn't high enought so the transistors aren't able to do their job properly within that short amount of time they're given at 1,6ghz.
Are the voltage steps like that on every kernel?
Click to expand...
Click to collapse
I'm on Siyah 2.6.14 Voltage Control setting as follow:
I/O = bfq & Governor = ondemand
1600Mhz - 1500mv
1400Mhz - 1300mv
1200Mhz - 1200mv
1000Mhz - 1100mv
800Mhz - 1000mv
500Mhz - 950mv
200Mhz - 900mv
100Mhz - 900mv
I've applied these setting as default at bootup with no problem.
OC to 1600Mhz + set to Performance gives me 6800-6990 benchmark score in Antutu.
Which kernel are you on?
Siyah 3.2
I see you are using 1,5V on 1,6ghz. Maybe that's why you running stable?
When I set max clock to 1,6ghz and 1,4V at that clock then I get random app crashes/freezes... Once I tried shutting down my phone and it made some very loud and creepy noise... Some very loud beeping. It was definitely not the shutdown sound of the rom.
On my stock rom I just get random reboot.
Can you also permanently work on 1,[email protected],5V (setting min clock to 1,6ghz) without freezes/crashes?
Also funny that at 1400mhz you are on 1,3v while standard on siyah 3.2 is [email protected],4ghz
While 1600mhz is lower voltage again.. This is messed up
Frozenthunder said:
Siyah 3.2
I see you are using 1,5V on 1,6ghz. Maybe that's why you running stable?
When I set max clock to 1,6ghz and 1,4V at that clock then I get random app crashes/freezes... Once I tried shutting down my phone and it made some very loud and creepy noise... Some very loud beeping. It was definitely not the shutdown sound of the rom.
On my stock rom I just get random reboot.
Can you also permanently work on 1,[email protected],5V (setting min clock to 1,6ghz) without freezes/crashes?
Also funny that at 1400mhz you are on 1,3v while standard on siyah 3.2 is [email protected],4ghz
While 1600mhz is lower voltage again.. This is messed up
Click to expand...
Click to collapse
I face lots of apps crashed/Forced closed before someone refer me to here:
http://forum.xda-developers.com/showthread.php?t=1466017
Take a look....
i neva do oc , but had tried ov an phone simply was not stable as out of the box.as my sig says iam good wiv 520 apps right now wiv decent batt life and good speed,only thing u got to kno wat ur phone can handle..
Related
Yesterday I thought I would test my battery life if I left my clock speed at 806 MHz, It lasted over 24 hours with no real speed decrease... I am requesting that a developer makes a kernel that is underclocked to 806 MHz and undervolted as much as possible so we can see how much battery life we can pull out of this thing.
take intersectRavens 800mv (or 925) kernel and underclock via setcpu?
lower than 800mv won't be possible, even 800mv is too low for me, it uses more battery cause data connections is very unstable. 925 gives better battery life for me.
IR kernel supports conservative governor too.. works great for me.
yeah just use set cpu to underclock the device. all these kernels already have the lowest voltages for each cpu frequency. but once again, the lower the voltage, the lower your signal strength, and if you signal strength gets too low, your phone will boost voltage to the radio to try to increase it and it will end up using more power. this is why many prefer the 925mv kernels as opposed to the 800mv ones.
this is my understanding, please correct me if i am wrong.
nellyspageli said:
yeah just use set cpu to underclock the device. all these kernels already have the lowest voltages for each cpu frequency. but once again, the lower the voltage, the lower your signal strength, and if you signal strength gets too low, your phone will boost voltage to the radio to try to increase it and it will end up using more power. this is why many prefer the 925mv kernels as opposed to the 800mv ones.
this is my understanding, please correct me if i am wrong.
Click to expand...
Click to collapse
I wasn't sure, that's why I said lowest possible. So I think I'll just do that, but from what you said I'm now wondering if we can OV the radio's voltage from the kernel to fix the 3g/speed problems...
will it work on froyo? i have CM6alpha1
link to the kernal to use and setCPU settings please (including profiles) much appreciated!
1st : My understands
So I'm completely new on the undevolting science and don't know if I understood everything correctly... For me, undevolting the cpu means : reduce power consumption for the same speed, so we can minimize the battery drain and have the same performance at high frequencies. Am I right?
I also understood that if we UV too much, the phone will be buggy/freeze. Is there any other risk I should be aware?
2nd : My statements
I start to UV my phone tonight and now I'm quite surprised to see how low I can go : I'm running at 1200MHz / 600mV (instead of the stock 1275mV) and the phone is solid stable (I don't know if I can go slower though, I was a bit scared and decided to post this message before continuing). So how do I check setcpu applied the settings correctly? To check system stability I use setcpu's stress test for about 2mins (the short test between two settings), then about 10mins (the big test for the final seting) and finally my feelings using my phone as a daily usage. Am I doing it right?
What are the common values at the UV exercise?
3rd : Some wtf in my head
If our phones can handle a so low value (compared to the stock one), why is it so high by default? I understand that, for stability and because every device is different, sammsung could not use the lowest value, but even some 100mV could improve the battery life of the phone, and since not everybody is tweaking his phone as us, it would have made an even greater phone OTB...
PS : my configuration
Phone/Pda/CSC : XXKG5
Kernel : ninphetamine 2.0.5
Yes, lower voltage is better but not all chips will take it. With undevolting the main risk is random instability or reboots, if you get a reboot just scale your uv back by 25mv and see what happens.
As far as why the voltages are what they are, for a chip as young as the one in the sgs2 there is a lot of variance in the chip, not all will be as "good" as others, so samsung bin (select) them to hit the clock they do at the voltage they do at a certain yield (aka not to many chips unable to hit the needed specs).
Maybe in the future the stock voltage will be lower, but for the time being we can tweak and see if we got a gold sample (better than standard) chip.
Also as far as your uv settings, you are not at 600 or something mv, the kernel has a hard lower limit of 800mv, even if it slows something below that in setcpu, the minimum the kernel will give the cpu is 800mv.
Sent from my GT-I9100 using XDA Premium App
Thank you very much for your quick reply ! And sory for being late too ^^
I indeed re-read more carefully Ninpo's thread and saw his kernel can UV from 800mV to 1500mV. Btw I think because 600mV was under the limit, stock setting was applied.
So after a day of testing, I can say my phone handle 200MHz / 825mV, 500MHz / 850mV, 800MHZ / 950mV, 1GHz / 1075mV and 1,2GHz / 1150mV with no problem at all And now, my battery will last forever
skuizy said:
Thank you very much for your quick reply ! And sory for being late too ^^
I indeed re-read more carefully Ninpo's thread and saw his kernel can UV from 800mV to 1500mV. Btw I think because 600mV was under the limit, stock setting was applied.
So after a day of testing, I can say my phone handle 200MHz / 825mV, 500MHz / 850mV, 800MHZ / 950mV, 1GHz / 1075mV and 1,2GHz / 1150mV with no problem at all And now, my battery will last forever
Click to expand...
Click to collapse
To make it last forever you want to set it to 0mV
Just don't set 200mhz to low or your phone may suffer from the sleep of death where it won't wake up.
Sent from my GT-I9100 using XDA Premium App
veyka said:
To make it last forever you want to set it to 0mV
Click to expand...
Click to collapse
Haha, if I could do it !!!
Thanks for the advice, if it doesn't wake up, I'll put the 200MHz voltage a bit higher
As I understand solution for "998 MHz with screen on" bug is found: http://forum.xda-developers.com/showthread.php?t=1225411&page=17#post16944722
We need to replace only one governor.
I don't want to play with different ROMs and kernels and I'm looking for simplest solution.
Is it possible to compile it as a module ("ondemand_mod" for ex.) and add it to stock ROM?
Or any other (simple) way?
Wrong section ...
Sent from my X10i using Tapatalk
Why wrong Section, this is Development to get the CPU Governor working correctly
Wolfbreak said:
Why wrong Section, this is Development to get the CPU Governor working correctly
Click to expand...
Click to collapse
Exactly, this is the right section for such request.
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
My_Immortal said:
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
Click to expand...
Click to collapse
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
As I see it's possible to compile and use governor as module.
Could someone compile it? And assemble as xRecovery package?
Or point me where to read about compiling for arm, where to get tools and so on...
Karlson2k said:
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
Click to expand...
Click to collapse
The thing is, on 245 MHz, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Xperia X10i via Tapatalk
My_Immortal said:
The thing is, on 245 MHz with high load, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Click to expand...
Click to collapse
There is no need to work on 245MHz as proper governor rise frequency automatically when it's necessary.
And really no stress for CPU to work an low frequency at full load. Moreover - CPU will consume more power at 500Mhz with 45% load than at 250Mhz with 95% load.
Sometime I use phone for navigation - long time with screen on and very low load. In this scenario battery drains very fast.
And last one - I like to have everything working properly. In case that I'll really need high frequency all the time I'll use other governor. I just want to have a choice.
I need a simple solotion for this too..I use z kernel and I found that Thego2s kernel fixed this problem..I was going to flash that kernel but think that has a bug and stoucks on logo ..can some one sayas a simple way?
Yes, I think a lot of people would prefer to use just small and simple fixes rather than replacing the whole kernel with a lot of nice but (personally) unnecessary features.
I am waiting for developers to release a fix for this problam
My CPU's temp is ~ 49 degree when do nothing, but when i do something it will come to > 53 degree .
I flashed all Custom rom to find one can help my cpu temp is low but .. it still high.
This is hardware problem ?
I'm getting mid-30s when idle. I suggest trying another kernel.
lamx710 said:
My CPU's temp is ~ 49 degree when do nothing, but when i do something it will come to > 53 degree .
I flashed all Custom rom to find one can help my cpu temp is low but .. it still high.
This is hardware problem ?
Click to expand...
Click to collapse
Which ROM and which kernel are you using?
Also, undervolting will reduce temperatures substantially.
Im using CM9 beta-0.4.5.1-cm-9.0.0-RC0-olympus-UNOFFICIAL-signed.zip
Kernel 2.6.32.59-MB860-CM9-gf77ecf8
Jokersax
This kernel may doesnt support Voltages. Open SetCPU i not see Voltages tab.
Can u suggest me some other kernel ?
Try faux123's kernel, and then do some undervolting.
I changed to faux but when change some voltage setting then my phone hang and reboot many times. temp still so high ( i only set -50mhz). Any sugest ?
Try -25 and use profiles for screen off. Don't forget that there's a 100mV delta limit for each step. Are you overclocking your phone?
My current settings with faux123's kernel:
Screen off profile: 216 min - 456 max
Voltages:
1000 MHz - 950 mV
912 MHz - 900 mV
750 MHz - 800 mV
608 MHz - 700 mV
456 MHz - 600 mV
312 MHz - 500 mV
216 MHz - 400 mV
A note about undervolting: not every cpu is the same. You might be able to get an even lower undervolt, or you might not even be able to undervolt at all. Just make sure you uncheck "Set on Boot" until you get a 100% stable undervolt.
Edit: While you're at it, take a look at the "Time in State" info. What frequency does your phone spend most of its time at? If it spends a lot of time on higher frequencies, there's your culprit for high temps.
lamx710 said:
I changed to faux but when change some voltage setting then my phone hang and reboot many times. temp still so high ( i only set -50mhz). Any sugest ?
Click to expand...
Click to collapse
Which Faux kernel did you flash? You should be using the 1.0GHz kernel. If you are using that and have mild UV then you should have no heat (or battery life) issues. Also, you need to check for any apps which are causing your CPU to be continually under load when it should be at idle. This could also account for higher than normal heat.
Your phone should be able to handle -50 Hz at all frequencies, as that is a very low UV.
quetzalcoatl2435 said:
Try -25 and use profiles for screen off. Don't forget that there's a 100mV delta limit for each step. Are you overclocking your phone?
My current settings with faux123's kernel:
Screen off profile: 216 min - 456 max
Voltages:
1000 MHz - 950 mV
912 MHz - 900 mV
750 MHz - 800 mV
608 MHz - 700 mV
456 MHz - 600 mV
312 MHz - 500 mV
216 MHz - 400 mV
A note about undervolting: not every cpu is the same. You might be able to get an even lower undervolt, or you might not even be able to undervolt at all. Just make sure you uncheck "Set on Boot" until you get a 100% stable undervolt.
Edit: While you're at it, take a look at the "Time in State" info. What frequency does your phone spend most of its time at? If it spends a lot of time on higher frequencies, there's your culprit for high temps.
Click to expand...
Click to collapse
Ok i will try and will report soon . Tks
CaelanT said:
Which Faux kernel did you flash? You should be using the 1.0GHz kernel. If you are using that and have mild UV then you should have no heat (or battery life) issues. Also, you need to check for any apps which are causing your CPU to be continually under load when it should be at idle. This could also account for higher than normal heat.
Your phone should be able to handle -50 Hz at all frequencies, as that is a very low UV.
Click to expand...
Click to collapse
I flash Faux 1.0 GHz kernel (my old post) like u said. I will try all you suggest then report soon tks guys
I tried all you suggest but still automatic off (or idle cause i press power button my phone dont start ... it like my phone is hanging ) then I must off my battery to power on my phone.
The average temp around 44 degrees or higher ..
What ROM are you using, and did this problem occur on stock?
I'm using CM9 ICS
Sometime with stock rom, this problem appear. I think it from my phone's hardware. When CPU temp > 50 degree it happen.
Today,
after talk over skype,
view some webpage,
it's seem abit hot (about 45 degree).
After all, i lock screen then put to my trouser. When come to other place I open it, press power and nothing come to screen like its still running so i must off my battery to turn on again.
Flashed many rom from stock to custom but never see one can make me feel happy ). If it from hardware so poor me
Sounds like a hardware issue. Do you happen to use any type of case on your phone?
rieslav canopy
I dont use any case on my phone (sorry my bad english, "case" in your question mean protect item ? ).
I just found, when my phone is hot, it will shutdown.
Today when my battery < 15%. My phone suddenly running smoothly @@. I dont know why.
trying to find a way to help my phone run ok
When I first switched to CM9 a month ago or so, I noticed that the undervolt was SO limited compared to CM7 (well, stock kernels don't support undervolting, but the result is the same with different kernels).
Under CM7 I could undervolt at -250mV (100mhz frequency step) and at -75mV for every step between 200 and 1000mhz.
Now I can undervolt at -25mV between 200mhz and 1000mhz and no undervolt is possible at 100mhz. Anything lower than -25mV will cause instant or delayed freezes and reboots.
If the hardware is still the same, I wonder if there's an explaination for such behaviour.
ICS/JB architectures put way more stress on CPU/GPU/RAM then FROYO/GB thus causing less OC/UV.
flapane said:
Under CM7 I could undervolt at -250mV (100mhz frequency step) and at -75mV for every step between 200 and 1000mhz.
Now I can undervolt at -25mV between 200mhz and 1000mhz and no undervolt is possible at 100mhz. Anything lower than -25mV will cause instant or delayed freezes and reboots.
Click to expand...
Click to collapse
That's interesting.
After a couple of months, I can say that those voltages keep the CPU rock solid under CM10 and Semaphore kernel:
-25mv @ 800 and 1000mhz
-75mv @ 100, 200mhz and 400mhz
It's worse than CM7, but it's better than CM9.
Somehow, JB architecture has been improved.