Related
So im using a CM7 nighlies right now and i just got SetCPU and i was wondering what profiles should i set up and how should i set them up cause all i care about right now is making battery life a better.
As for me, I only have two profiles set up. One for screen off set at 245mhz min/max on powersave/conservative @ 90 priority and one for battery temp greater >45 degree C set at 614 mhz max 245mhz min @ 95 priority, on conservative. I've been using this setup on Fresh 3.5 with Netarchy's 4.3.1 stable kernel and my phone has been off the charger for 22 hours with about 20% remaining battery and thats with moderate usage and with WiFi on entire time. You can have unlimited profiles set up based on remaining battery, battery temp, etc and set up the profiles with higher priorities with higher priority number designation. Even though Net's kernel allows me to underclock all the way to 128 mhz, my phone does not like to me underclocked that low.
I'll try that out see how it works
It's time to Overclock our Phone...
DISCLAIMER: OVERCLOCK IS DANGEROUS FOR OUR PHONES
How to:
1. Now download r151 from Here
2. Put the files of r151 in the root of SD, run HARET.
3. Download SetCPU from Here and install It.
4. Now open SetCPU, And choice "Autodetect Speeds Reccomanded".
5. Allow Root.
6. Press Windows button and choice "Perflock Disabler" and "Attemp to Disable Perflock" and Check "Set on Boot".
7. Now, close the windows and OC our Phone.
My phone under USB and AC run at 825 MHz without Crash, i had tryed to run it at 864 MHz but System Crash everytime. Without USB and AC my phone run at 787 MHz. I Post 2 Images 1. = Normal Clock 2. = 825 MHz Clock.
To Made Benchmark i Use BenchmarkPi.
1. Screen Normal Clock
2. Screen 825MHz
For Other Question:
1. SetCPU
2. -r0bin-'s Post
I did it, it works perferctly !
Upscaled to 825 and min 128
Downscaled to 245 while charging and screen off
Thanks !
doublej4473 said:
I did it, it works perferctly !
Upscaled to 825 and min 128
Downscaled to 245 while charging and screen off
Thanks !
Click to expand...
Click to collapse
My Profiles:
1. Screen Off Min: 19 MHz Max: 245 MHz
2. In Call: Min: 128 MHz Max: 600 MHz
3. Charging AC: Min: 19 MHz Max: 825 MHz
4. Charging USb: Min: 19 MHz Max: 825 MHz
5. Main Profile: Min: 19 MHz Max: 787 MHz
...
Tell me please, does it helps to save the battery in last releace (r163)? I`m asking becouse i try to use Master CPU, and it seems to me that it don`t helps to save energy... But I don`t use profiles, only ondemand settings from 120-600 mHz.
Thanks!
@HTCxxxx
what is the percentage priority by profile?
puxus said:
Tell me please, does it helps to save the battery in last releace (r163)? I`m asking becouse i try to use Master CPU, and it seems to me that it don`t helps to save energy... But I don`t use profiles, only ondemand settings from 120-600 mHz.
Thanks!
Click to expand...
Click to collapse
To PowerSave try 19-480 MHz if Don't need Performance or 19-600 MHz Im Sorry But i Don't Know Master Cpu
doublej4473 said:
@HTCxxxx
what is the percentage priority by profile?
Click to expand...
Click to collapse
In Call is 100
And Screen Off 100 too.
19 Mhz does not work for me. Phone gets unusable slow and dont come back :/
Beside that, underclocking do not have a big influence on the battery consumtion.
Undervolting would be more interesting.
codiak said:
19 Mhz does not work for me. Phone gets unusable slow and dont come back :/
Beside that, underclocking do not have a big influence on the battery consumtion.
Undervolting would be more interesting.
Click to expand...
Click to collapse
Why Unusable??? Yhea, Undervolting can be an Interesting Thing, but i Think if the Volting is too low phone Freeze, and if is too high cpu can have an High temperature if you're stressing cpu and phone can freeze too. But i've noted, when i use a low "screen off" profile battery consumaption is high? why? is a problem of kernel? or is nomal?
codiak said:
19 Mhz does not work for me. Phone gets unusable slow and dont come back :/
Beside that, underclocking do not have a big influence on the battery consumtion.
Undervolting would be more interesting.
Click to expand...
Click to collapse
you are right,i also experienced that 19 Mhz makes phone lazy
i'm also agree about 2nd part..i read the same
HTCxxxx said:
Why Unusable??? Yhea, Undervolting can be an Interesting Thing, but i Think if the Volting is too low phone Freeze, and if is too high cpu can have an High temperature if you're stressing cpu and phone can freeze too. But i've noted, when i use a low "screen off" profile battery consumaption is high? why? is a problem of kernel? or is nomal?
Click to expand...
Click to collapse
you don't need to undervolt it too low,you just need to find the right voltage
try last kernel from r0bin and you will not have high battery consumption anymore
Low Mhz does not lead automaticly to low consumtion.
If you phone has something todo (update something for example) it will get the job done faster with high Mhz and is going fastert to sleep after that.
With low Mhz it takes longer and so can have higher consumtion.
On my HD2 I dont use profiles (like screen off) and it has a very low consumtion on standby/sleep.
If you set a minimum speed when screen is off a11 is not able to go to suspend, maybe
just a quick feedback on power consumption:
it never been so good with r167+drain fix without SetCPU
when I set profiles with low frequency (19 or 128Mhz) it keeps on consuming battery up to 100mA. when i switch SetCPU profiles off, i go to 9mA in suspend mode.
true story
there must be a way to setup SetCPU in a way it doesnt affect too much battery drain in suspend mode, but for the time being i just deactivated it.
tzacapaca said:
you are right,i also experienced that 19 Mhz makes phone lazy
i'm also agree about 2nd part..i read the same
you don't need to undervolt it too low,you just need to find the right voltage
try last kernel from r0bin and you will not have high battery consumption anymore
Click to expand...
Click to collapse
yes i see some improvement, and im happy for it...
(I THINK)
Hi All,
I've understood why CPU doesn't run @ 19MHz or @ 128 MHz...
Go to /sys/acpucloclock and look acpuclk_tbl...In It there are write all frequencies CPU can Run:
245760,400000,480000,600000,768000,787200,806400,825600,844800,864000....
but no Under 245 MHz so if You use a Profile for Screen off From 19MHz to 254MHz, cpu Run everytime @ 245MHz...so there is an high consummation of energy
bye
HTCxxxx said:
(I THINK)
Hi All,
I've understood why CPU doesn't run @ 19MHz or @ 128 MHz...
Go to /sys/acpucloclock and look acpuclk_tbl...In It there are write all frequencies CPU can Run:
245760,400000,480000,600000,768000,787200,806400,825600,844800,864000....
but no Under 245 MHz so if You use a Profile for Screen off From 19MHz to 254MHz, cpu Run everytime @ 245MHz...so there is an high consummation of energy
bye
Click to expand...
Click to collapse
hi
as codiak said earlier lowering CPU(underclocking) doesn't have so much impact on battery life..he also explained you why..if you want i will explain you too
explanation:run CPU at low voltage,open an app or downloading an email,etc= CPU will take time to get to the level app needs,display will stay longer while it CPU will get done the job= worse battery life
Undervolting will have impact on battery life
explanation:run same CPU clock at lower Voltage= CPU will use less power=better battery life
hope it's clear enough for you now,and if anyone else thinks i'm wrong feel free to prove me i'm wrong
P.S. Anyway i asked devs and they will lower CPU to run @ less than 245 Mhz.
Enjoy
tzacapaca said:
hi
as codiak said earlier lowering CPU(underclocking) doesn't have so much impact on battery life..he also explained you why..if you want i will explain you too
explanation:run CPU at low voltage,open an app or downloading an email,etc= CPU will take time to get to the level app needs,display will stay longer while it CPU will get done the job= worse battery life
Undervolting will have impact on battery life
explanation:run same CPU clock at lower Voltage= CPU will use less power=better battery life
hope it's clear enough for you now,and if anyone else thinks i'm wrong feel free to prove me i'm wrong
Click to expand...
Click to collapse
Ok thank you very much!!!
I tried to search but was unsuccessful to find the information that I wanted.
Can someone tell me what are the recommended safe undervolt settings for the transformer?
I'm running prime 1.9 with clemsyn-blades 1.6a.
Thx
Sent from my Transformer TF101 using Tapatalk
steve.garon said:
I tried to search but was unsuccessful to find the information that I wanted.
Can someone tell me what are the recommended safe undervolt settings for the transformer?
I'm running prime 1.9 with clemsyn-blades 1.6a.
Thx
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
I don't know what the stock settings are but I can tell you the process I followed when I OCed my tablet. Install the custom kernel and rom you want. Then install an app to modify frequency and voltages. I use setCPU but pimpmycpu works also.
1. Find the highest clock you can attain with the provided overvolt from the kernel. To do this just start at the highest frequency and see if the tablet reboots or locks during a stress test. Some people play games to stress. I use the built in stress tester in SetCPU. Make sure to apply the higher frequency for testing but not to apply settings on reboot or you could get stuck in a reboot loop (or so I am assuming the kernel might reset to 1 GHz when a hard lock occurs).
2. Once you have the maximum Frequency (for me it was 1.644 MHz) then start lowering the voltage for that frequency only until you loose stability. I can undervolt 1.644 by -75 mV. If I go upto -100 then I get random reboots. I go in -25 mV increments but you could narrow it down even more by going with -10 or even -5 intervals.
3. Take the offset you got (in my case -75 mV)on the highest frequency and apply it to every frequency above 1 GHz and see if this is stable. If not then slowely increase voltage until you gain stability again.
4. (Optional) Then start undervolting stock frequencies from 216 MHz to 1 GHz. Every tablet is different but (I have heard) this could cause sleep issues. I undervolted all frequencies from above 216 to 1000 GHz by -25 Mv without any issues. I may bring it down slowely by increments of-5 or -10 until I run into some issues.
5. (Optional) Undervolt 216 MHz as low as possible to save standby battery power. I undervolted my 216 MHz to 725 mV (even though SetCPu goes lower the kernel is locked at this). Which helps keep my battery levels up when the tablet screen is off and not in use.
Hints: To test that a voltage is okay at a certain frequency then make sure to set your max to the frequency level you want to test. If you set the max at 1544 and undervolt 1 GHz you will never know if it is okay because when you stress it it will blow right past 1 GHz upto 1544 and the voltage for that will take over.
If you have any questions please let me know.
Bjd223 said:
I don't know what the stock settings are but I can tell you the process I followed when I OCed my tablet. Install the custom kernel and rom you want. Then install an app to modify frequency and voltages. I use setCPU but pimpmycpu works also.
1. Find the highest clock you can attain with the provided overvolt from the kernel. To do this just start at the highest frequency and see if the tablet reboots or locks during a stress test. Some people play games to stress. I use the built in stress tester in SetCPU. Make sure to apply the higher frequency for testing but not to apply settings on reboot or you could get stuck in a reboot loop (or so I am assuming the kernel might reset to 1 GHz when a hard lock occurs).
2. Once you have the maximum Frequency (for me it was 1.644 MHz) then start lowering the voltage for that frequency only until you loose stability. I can undervolt 1.644 by -75 mV. If I go upto -100 then I get random reboots. I go in -25 mV increments but you could narrow it down even more by going with -10 or even -5 intervals.
3. Take the offset you got (in my case -75 mV)on the highest frequency and apply it to every frequency above 1 GHz and see if this is stable. If not then slowely increase voltage until you gain stability again.
4. (Optional) Then start undervolting stock frequencies from 216 MHz to 1 GHz. Every tablet is different but (I have heard) this could cause sleep issues. I undervolted all frequencies from above 216 to 1000 GHz by -25 Mv without any issues. I may bring it down slowely by increments of-5 or -10 until I run into some issues.
5. (Optional) Undervolt 216 MHz as low as possible to save standby battery power. I undervolted my 216 MHz to 725 mV (even though SetCPu goes lower the kernel is locked at this). Which helps keep my battery levels up when the tablet screen is off and not in use.
Hints: To test that a voltage is okay at a certain frequency then make sure to set your max to the frequency level you want to test. If you set the max at 1544 and undervolt 1 GHz you will never know if it is okay because when you stress it it will blow right past 1 GHz upto 1544 and the voltage for that will take over.
If you have any questions please let me know.
Click to expand...
Click to collapse
Cool. I'll give this a try.
Sent from my Nexus S using Tapatalk
I get a stable undervolt at -50 on all cpu steps which is pretty good. This should save loads of battery.
Sent from my Nexus S using Tapatalk
steve.garon said:
I get a stable undervolt at -50 on all cpu steps which is pretty good. This should save loads of battery.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I started at the top and went down every stepping from 1624 to 1000 and found out the lowest stable frequency and then added 10 to be safe to each one. I am currently at
1624 (-70)
1592 (-80)
1544 (-180)
1472 (-80)
1424 (-160)
1336 (-185)
1232 (-185)
1000 (- 110) which is 990 mV
I then set every stepping under 1 GHz frequency that was above 990 mV to 990 mV as if it can run at 1 GHz at that voltage then any speed under that will run fine at that voltage also. I have some more stability testing to do but I think I got it pretty much nailed down for my device. I may go through all the sub 1 GHz frequencies but it does take some time to run a stress test under each stepping.
Also I have never had any sleep issues but that is something to look out for. I also wonder how temperature affects stability as I have never gotten it above 40c. The pad might benefit from a 1 or 2mm thermal pad squeezed between the CPU and the back bezel (if it will fit).
Does anyone know that tjunction max for a Tegra2? I have a profile set up in SetCPU that sets the CPU frequency at 1 GHz if the CPU gets above 42 because I saw something similar in the Clemsyn rom but don't really know when the CPU will start to throttle itself at or shut off.
I am trying to find stock voltages for different devices because it seems like some mfgs are undervolting to save battery on some tablets.
Bjd223 said:
I started at the top and went down every stepping from 1624 to 1000 and found out the lowest stable frequency and then added 10 to be safe to each one. I am currently at
1624 (-70)
1592 (-80)
1544 (-180)
1472 (-80)
1424 (-160)
1336 (-185)
1232 (-185)
1000 (- 110) which is 990 mV
I then set every stepping under 1 GHz frequency that was above 990 mV to 990 mV as if it can run at 1 GHz at that voltage then any speed under that will run fine at that voltage also. I have some more stability testing to do but I think I got it pretty much nailed down for my device. I may go through all the sub 1 GHz frequencies but it does take some time to run a stress test under each stepping.
Also I have never had any sleep issues but that is something to look out for. I also wonder how temperature affects stability as I have never gotten it above 40c. The pad might benefit from a 1 or 2mm thermal pad squeezed between the CPU and the back bezel (if it will fit).
Does anyone know that tjunction max for a Tegra2? I have a profile set up in SetCPU that sets the CPU frequency at 1 GHz if the CPU gets above 42 because I saw something similar in the Clemsyn rom but don't really know when the CPU will start to throttle itself at or shut off.
I am trying to find stock voltages for different devices because it seems like some mfgs are undervolting to save battery on some tablets.
Click to expand...
Click to collapse
-180 in some frequencies!! Thats just insane. I've got to try this.
FYI, you don't have to lower voltage for all upper 1ghz frequencies. If your running at 1544 for exemple. The cpu will never touch the frequencies between 1000 and 1544. After the 1000 its a direct step to whatever frequency your overclocking too. You can monitor this in setcpu.
I cannot undervolt as precise as you can. For some reason setcpu only let me do 25mv increment...
Sent from my Nexus S using Tapatalk
I have undervolted by -175 on all frequencies, obviously 216Mhz is locked but all seems pretty stable after some testing. No sleep death either so I'm going to carry on testing.
steve.garon said:
-180 in some frequencies!! Thats just insane. I've got to try this.
FYI, you don't have to lower voltage for all upper 1ghz frequencies. If your running at 1544 for exemple. The cpu will never touch the frequencies between 1000 and 1544. After the 1000 its a direct step to whatever frequency your overclocking too. You can monitor this in setcpu.
I cannot undervolt as precise as you can. For some reason setcpu only let me do 25mv increment...
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
In SetCPU do not use the slider use the keyboard and type in the exact number you want.
I wanted to figure out every stepping in case I wanted to switch to a lower frequency but yeah most poeple don't have to do this.
The lowest stable I have gotten is -190 but feel like adding 10 padding will ensure stability.
I will probably do the sub 1 GHz frequencies today or tomorrow.
Bjd223 said:
In SetCPU do not use the slider use the keyboard and type in the exact number you want.
I wanted to figure out every stepping in case I wanted to switch to a lower frequency but yeah most poeple don't have to do this.
The lowest stable I have gotten is -190 but feel like adding 10 padding will ensure stability.
I will probably do the sub 1 GHz frequencies today or tomorrow.
Click to expand...
Click to collapse
I didnt even noticed I could use the keyboard...
I finally settled to -25 @216, -50 under 612 and -100 over 612. And everything is stable
Sent from my Nexus S using Tapatalk
I have tested each voltage. I am under the impression that 725 mV is the kernel minimum in the Clemsyn kernel so once I hit that I just set every frequency under that too 725. I will eventually go through and stress test every frequency @ 725 to make sure everything is a-okay but I am sure it is.
Here is my list incase anyone wants a place to start.
1680 MHz (-000) I can not overclock to this freuqency.
1624 MHz (-070) 1380 mV
1592 MHz (-080) 1345 mV
1544 MHz (-180) 1220 mV
1472 MHz (-080) 1220 mV
1424 MHz (-160) 1115 mV
1336 MHz (-185) 1065 mV
1232 MHz (-185) 990 mV
1000 MHz (-215) 885 mV
0912 MHz (-215) 835 mV
0816 MHz (-235) 790 mV
0760 MHz (-215) 760 mV
0608 MHz (-225) 725 mV
0456 MHz (-100) 725 mV
0312 MHz (-075) 725 mV
0216 MHz (-025) 725 mV
Clemsyn said the minimum mV in his kernel but I can't seem to find the thread, but I think it was 725. If I find out it is something lower I will go through the lower ones until I hit the minimum.
Also please note that everything above 1 GHz has +10 mV padding added to it above the lowest stable I could find. Everything below 1 GHz only has a +5 mV padding on it. So for example I actually hit a -240 w/o any issues @ 816 MHz.
I tested in +/-5 mV increments but if you wanted you could narrow it down even further.
EDIT: Also after some testing it looks like it does use frequencies between 1 GHz and your max. I have it set to 1644 and it does hit 1232 MHz occasionally.
Bjd223 said:
I don't know what the stock settings are but I can tell you the process I followed when I OCed my tablet. Install the custom kernel and rom you want. Then install an app to modify frequency and voltages. I use setCPU but pimpmycpu works also.
1. Find the highest clock you can attain with the provided overvolt from the kernel. To do this just start at the highest frequency and see if the tablet reboots or locks during a stress test. Some people play games to stress. I use the built in stress tester in SetCPU. Make sure to apply the higher frequency for testing but not to apply settings on reboot or you could get stuck in a reboot loop (or so I am assuming the kernel might reset to 1 GHz when a hard lock occurs).
2. Once you have the maximum Frequency (for me it was 1.644 MHz) then start lowering the voltage for that frequency only until you loose stability. I can undervolt 1.644 by -75 mV. If I go upto -100 then I get random reboots. I go in -25 mV increments but you could narrow it down even more by going with -10 or even -5 intervals.
3. Take the offset you got (in my case -75 mV)on the highest frequency and apply it to every frequency above 1 GHz and see if this is stable. If not then slowely increase voltage until you gain stability again.
4. (Optional) Then start undervolting stock frequencies from 216 MHz to 1 GHz. Every tablet is different but (I have heard) this could cause sleep issues. I undervolted all frequencies from above 216 to 1000 GHz by -25 Mv without any issues. I may bring it down slowely by increments of-5 or -10 until I run into some issues.
5. (Optional) Undervolt 216 MHz as low as possible to save standby battery power. I undervolted my 216 MHz to 725 mV (even though SetCPu goes lower the kernel is locked at this). Which helps keep my battery levels up when the tablet screen is off and not in use.
Hints: To test that a voltage is okay at a certain frequency then make sure to set your max to the frequency level you want to test. If you set the max at 1544 and undervolt 1 GHz you will never know if it is okay because when you stress it it will blow right past 1 GHz upto 1544 and the voltage for that will take over.
If you have any questions please let me know.
Click to expand...
Click to collapse
Thanks for this mate. I followed your guide exactly and I'm using clems 16? Kernel completely stable at all frequencies including the undervolting!
Based on my testing you need ~ a +15 to +25 mV over stable CPU voltage to get stable 3D GPU.
I found that I could run hours of "Stress CPU" without any issues at a voltage but during stressful 3D games that are using CPU + GPU cores, at that same frequency, the machine would FC the app, reboot or lock. I have also noticed that the closer you are to the stable voltage different things will happen.
Far off - machine will usually reboot
Closer - machine will usually hard lock
Even closer - Apps will FC, widgets will act strange (like invert colors, black blocks for backgrounds, etc.)
So what I do now is I test with Dungeon Defenders at the main menu. Its seems that if you can last 1 hr at the Dungeon Defenders menu you are GTG. If you actually play the game then 1 stage is what I use to test.
Bjd223 said:
I don't know what the stock settings are but I can tell you the process I followed when I OCed my tablet. Install the custom kernel and rom you want. Then install an app to modify frequency and voltages. I use setCPU but pimpmycpu works also.
1. Find the highest clock you can attain with the provided overvolt from the kernel. To do this just start at the highest frequency and see if the tablet reboots or locks during a stress test. Some people play games to stress. I use the built in stress tester in SetCPU. Make sure to apply the higher frequency for testing but not to apply settings on reboot or you could get stuck in a reboot loop (or so I am assuming the kernel might reset to 1 GHz when a hard lock occurs).
2. Once you have the maximum Frequency (for me it was 1.644 MHz) then start lowering the voltage for that frequency only until you loose stability. I can undervolt 1.644 by -75 mV. If I go upto -100 then I get random reboots. I go in -25 mV increments but you could narrow it down even more by going with -10 or even -5 intervals.
3. Take the offset you got (in my case -75 mV)on the highest frequency and apply it to every frequency above 1 GHz and see if this is stable. If not then slowely increase voltage until you gain stability again.
4. (Optional) Then start undervolting stock frequencies from 216 MHz to 1 GHz. Every tablet is different but (I have heard) this could cause sleep issues. I undervolted all frequencies from above 216 to 1000 GHz by -25 Mv without any issues. I may bring it down slowely by increments of-5 or -10 until I run into some issues.
5. (Optional) Undervolt 216 MHz as low as possible to save standby battery power. I undervolted my 216 MHz to 725 mV (even though SetCPu goes lower the kernel is locked at this). Which helps keep my battery levels up when the tablet screen is off and not in use.
Hints: To test that a voltage is okay at a certain frequency then make sure to set your max to the frequency level you want to test. If you set the max at 1544 and undervolt 1 GHz you will never know if it is okay because when you stress it it will blow right past 1 GHz upto 1544 and the voltage for that will take over.
If you have any questions please let me know.
Click to expand...
Click to collapse
I always wanted to learn more about the mV and CPU speed stuff. I always install rom, install kernel of the one I heard the better is and that's it. Never had touched the voltage measure in any of my android device. Yeah i know, so noob.
Thanks for this how to info, I think I will play around a bit later. Right now I'm struggling with my self on wish of the 3 roms available install and stay.
Had to remove undervolt this weekend since my camera wouldnt start anymore. I'll have to redo all the tests I was doing but test for camera too. The tablet would just freeze as soon as I opened the camera app
Sent from my Nexus S using Tapatalk
steve.garon said:
Had to remove undervolt this weekend since my camera wouldnt start anymore. I'll have to redo all the tests I was doing but test for camera too. The tablet would just freeze as soon as I opened the camera app
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
My camera does not work either. I just figured it was Clemsyns kernel not the OC. I don't know anything about cameras but maybe they use a lot of voltage so the voltage to the CPU dips.
I never used the camera personally, but I will test it some and see what additional mV you need over stable to get the camera working.
Also I noticed the more you undervolt (it seems to me) the harder it is to undock with an app open. usually instead of reloading they FC or lock the device so i just make sure to hit the home key before I undock then alt tab right back into the app.
Bjd223 said:
My camera does not work either. I just figured it was Clemsyns kernel not the OC. I don't know anything about cameras but maybe they use a lot of voltage so the voltage to the CPU dips.
I never used the camera personally, but I will test it some and see what additional mV you need over stable to get the camera working.
Also I noticed the more you undervolt (it seems to me) the harder it is to undock with an app open. usually instead of reloading they FC or lock the device so i just make sure to hit the home key before I undock then alt tab right back into the app.
Click to expand...
Click to collapse
My camera did not work at 912 MHz at stock voltage on 17b but now on 18 I can do my normal undervolt settings and the camera works fine.
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)
Hi,
1) I have installed Kyorarom 0.5.2 OC kernel and here are my SetCPU profiles.
Main - Min: 300 Mhz, Max: 800Mhz
On Call - Min: 83, Max: 400, Priority: 100
Time - 11 PM to 6 AM - Min: 83, Max: 200, Priority: 99
Screen Off: Min: 83, Max: 400, Priority: 98.
My problem is, if I use my phone after 11PM, the time profile gets activated.
But when screen is on, I want to use the main profile. How can I do that?
2) Which governor has less stress on CPU? Conservative or Lagfree?
3) When in the main profile, my phone constantly runs at my max setting, (ie) 800 Mhz. It never runs lower than that. Why does it happen?
maverickgenius said:
Hi,
1) I have installed Kyorarom 0.5.2 OC kernel and here are my SetCPU profiles.
Main - Min: 300 Mhz, Max: 800Mhz
On Call - Min: 83, Max: 400, Priority: 100
Time - 11 PM to 6 AM - Min: 83, Max: 200, Priority: 99
Screen Off: Min: 83, Max: 400, Priority: 98.
My problem is, if I use my phone after 11PM, the time profile gets activated.
But when screen is on, I want to use the main profile. How can I do that?
2) Which governor has less stress on CPU? Conservative or Lagfree?
3) When in the main profile, my phone constantly runs at my max setting, (ie) 800 Mhz. It never runs lower than that. Why does it happen?
Click to expand...
Click to collapse
HI,
1) I dont think that's even possible man... would be nice though
2) conservative
3) how do you know that its for constant? and that's normal if you've chosen 'performance' gov'ner.
PersianSphinx said:
HI,
1) I dont think that's even possible man... would be nice though
2) conservative
3) how do you know that its for constant? and that's normal if you've chosen 'performance' gov'ner.
Click to expand...
Click to collapse
1) Okay. I thought that the main profile is something like a "screen on" profile, which would override all others.
3) I checked using CPU Spy. My phone is always at the highest frequency. I am using conservative.
try a different governor / kernel
maverickgenius said:
1) Okay. I thought that the main profile is something like a "screen on" profile, which would override all others.
3) I checked using CPU Spy. My phone is always at the highest frequency. I am using conservative.
Click to expand...
Click to collapse
I'm not sure about the constant 800. even if it is, as long as battery works well, everything is OK
PersianSphinx said:
I'm not sure about the constant 800. even if it is, as long as battery works well, everything is OK
Click to expand...
Click to collapse
Well, even if the battery works fine, running the processor constantly at 800 MHz will decrease its life.
Does your phone too behave the same way as mine?
maverickgenius said:
Well, even if the battery works fine, running the processor constantly at 800 MHz will decrease its life.
Does your phone too behave the same way as mine?
Click to expand...
Click to collapse
lol, how long are you planning to keep this phone? decreasing the life from 10 years to 8 wont bother me at all (I dont actually know the life)
PersianSphinx said:
lol, how long are you planning to keep this phone? decreasing the life from 10 years to 8 wont bother me at all (I dont actually know the life)
Click to expand...
Click to collapse
Agree with you on that point. But you still didn't answer my question
1) Not possible.
2) Conservative.
3) Problem with conservative governor in Kyoyakernel maybe.
Advice : - Always use On Demand.
Find Kryllios ROM instructioin, he have sugeested good settings to get maximum battery life...........
Max 300 - MHz and Min 1200 Mhz...what is this!
Hi, I have a Samsung Galaxy S II I9100G and rooted it with Kernel superatoms v3.0 XXLA1 and installed SetCPU 2.3.0.2 in it.
Now, when I set the max and min slider to 1200 MHz (with Governer hotplug) and goes back to the home screen, after that, when I again open SetCPU, the max slider gets to 300 MHz and the min to 1200 MHz (with Governer powersave).
What is this, man!!! How can the processor run with maximum speed of 300 MHz and the minimum of 1200 MHz ....
Plzz...I need help