If you use a custom kernel like Aero Kernel, what is your best undervolting settings?
I have been using this for a week and my phone is very stable
300 mhz - 990 mV
384 mhz - 990 mV
600 mhz - 1000 mV
787 mhz - 1000 mV
998 mhz - 1025 mV
1094 mhz - 1025 mV
1190 mhz - 1050 mV
Any suggestions to undervolt it even better?
Related
For those of you who undervolt your Sensation... would you be so kind to post here your voltage settings by frequencies
Left column is CPU frequency in Hz and right column are Voltages that seem to be working for me (this is a combination of Bricked and Faust Kernel frequencies/voltages)
192000: 700.000 mV
310500: 800.000 mV
384000: 812.500 mV
432000: 812.500 mV
486000: 812.500 mV
540000: 812.500 mV
576000: 812.500 mV
594000: 825.000 mV
648000: 825.000 mV
702000: 837.500 mV
756000: 837.500 mV
768000: 837.500 mV
810000: 850.000 mV
864000: 862.500 mV
918000: 875.000 mV
960000: 900.000 mV
972000: 900.000 mV
1026000: 925.000 mV
1080000: 950.000 mV
1134000: 962.500 mV
1188000: 987.500 mV
1242000: 1000.000 mV
1296000: 1025.000 mV
1340000: 1037.500 mV
1350000: 1037.500 mV
1404000: 1062.500 mV
1440000: 1087.500 mV
1458000: 1087.500 mV
1512000: 1100.000 mV
1530000: 1100.000 mV
1566000: 1125.000 mV
1620000: 1187.500 mV
1670000: 1212.500 mV
1720000: 1225.000 mV
1780000: 1250.000 mV
1830000: 1287.500 mV
1890000: - Unstable
Undervolting all frequencies at the same time by a certain step via script doesn't seem like a good approach to me.
My approach was to find out lowest possible voltages by setting a certain frequency fixed (for example max = min = 1566000. Then lowering the voltages from stock (recommended) untill I reached the minimum possible voltage while testing it with benchmarks and regular phone usage.
This way I've obtained a minimum frequency list - but this is definitely not a voltage list that can be used while phone is switching through frequencies (because of voltage drop - you would definitely experience instability). Because of this, I've tried to find voltages that would work for me by setting a certain frequency range - and then increasing the voltage untill everything was working fine.
I use System Tuner that can be found on the Market.
Battery saving tips:
- set Wallpaper as your Lock Screen Style (Weather eats a lot of battery juice)
- Use a dark screen background (it's battery friendly, and If you use total black instead of fancy images, you can notice increase in speed when you scroll through screens)
gvego said:
For those of you who undervolt your Sensation... would you be so kind to post here your voltage settings by frequencies (left column is CPU frequency in Hz, right column is Faux kernel default frequency (I think... i get it when I push 'Reset All' in System Tuner under voltage tweaks)...
Voltages that seem to be working for me are written in the parenthesis.
Undervolting all frequencies at the same time by a certain step via script doesn't seem like a good approach to me.
192000: 812.500 mV
310500: 812.500 mV
384000: 812.500 mV
432000: 812.500 mV
486000: 837.500 mV
540000: 850.000 mV
594000: 862.500 mV
648000: 875.000 mV
702000: 900.000 mV
756000: 925.000 mV
810000: 937.500 mV
864000: 962.500 mV
918000: 962.500 mV
972000: 962.500 mV
1026000: 975.000 mV
1080000: 987.500 mV
1134000: 1000.000 mV
1188000: 1012.500 mV
1242000: 1025.000 mV
1296000: 1050.000 mV
1350000: 1075.000 mV (1037.5 mV)
1404000: 1100.000 mV
1458000: 1112.500 mV
1512000: 1125.000 mV (1087.5 mV)
1566000: 1150.000 mV (1125.0 mV)
1620000: 1250.000 mV (1187.5 mV)
1670000: 1275.000 mV (1212.5 mV)
1720000: 1300.000 mV (1225.0 mV)
1780000: 1350.000 mV (1237.5 mV)
Click to expand...
Click to collapse
i might add this to my script
ifti_a said:
i might add this to my script
Click to expand...
Click to collapse
That would be nice... but first we have to gather more data here
well i underclocked all mine by -25 except the first one 192mhz
Deleted (changed)
Even lower
Is there a way to undervolt beneath 812.5 mV on Bricked kernel?
gvego said:
Is there a way to undervolt beneath 812.5 mV?
Click to expand...
Click to collapse
dont think so
the phone might not wake up if it doesnt get enough power
leave it at 812.5,
not a big cut to 800.0 plus the phone only goes to 192Mhz when idle and screen off....
Well - it seems that the two lowest frequencies are working fine with 800mV (faux kernel)... I'll edit my first post here as I "fine tune" the frequencies...
Gaming seems to be the hardest stability test.
i dont know how though i managed to undervolt my sensation by 100mv across the board with bricked kernel.
I thought it must not have been working cause it was such a high undervolt. though as soon as i go 125mv then it crashes so it must be working. Antutu Benchmark runs too so i assume its stable.
i am using Incredicontrol.
I'm new to this how do I got about undervolting my sensation.
Sent from my HTC Sensation 4G using xda app-developers app
as long as your kernel supports just install and app that lets you adjust it. fauxclock (if using faux kernel) or incredicontrol or system tuner to name a few.
i'm trying this now...will report the result (battery life and stability soon after a few cycles)
thanks for sharing, dude!
Mesaman2012 said:
I'm new to this how do I got about undervolting my sensation.
Click to expand...
Click to collapse
i don't know about any scripting etc, but i'm using SystemTuner (you can get the free or pro in play store) just find the "voltage" settings somewhere down near CPU uc/oc settings... :good:
i am using 782 and its working nice with 192 mhz
i've tried these settings and applied it to my sensation using system tuner..
I'm using HyperNonSense 2.8 and the processor is underclocked from the default faux's setting to 1,18MHz.
the interface using is stable, but I've experienced some freezing while scrolling or long touch on several apps. it froze while scrolling in Browser (ICS Browser and Opera), MMS.
the freezing problem lifted up after I add 12,5mV to each clock of the processor and until now no problem...
now I'm watching the battery life...
*just my two cents*
i am on
700 @ 192Mhz
725 @ 310Mhz
725 @ 384
750 @ 432
750 @ 486
775 @ 540
775 @ 594
800 @ 648
800 @ 702
825 @ 756
875 @ 918
900 @ 1026
925 @ 1134
950 @ 1188
1000 @ 1296
1025 @ 1350
1050 @ 1404
1050 @ 1458
1100 @ 1566
Hopefully someone can either confirm my beliefs or clear up any confusion I may be suffering from lol.
If these are my UV settings (just the lower end of the freqs range):
192 MHz > 800 mV
310 MHz > 800 mV
384 MHz > 800 mV
432 MHz > 800 mV
486 MHz > 825 mV
540 MHz > 837.5 mV
Is there any difference in power usage between having my minimum wake frequency set to 432 MHz as opposed to 192 MHz? I am currently under the impression that since both frequencies are set to 800 mV, the end power usage will be the same.
Current Daemon Controller settings are:
Wake Min > 432 MHz
Wake Max > 1026 MHz
Ondemand
Sleep Min > 192 MHz
Sleep Max > 384 MHz
SmartassV2
And using Bricked 1.6 AOSP kernel.
And thanks, of course!
Sent from my Sensation using XDA App
-bump-
44 views and no one knows?
Sent from my Sensation using XDA App
Hi XDA,
I recently installed Apex ROM and have tried a couple kernels (Matr1x and Trinity) but it seems that whenever I receive an incoming call AND the screen is off my device reboots.
I am able to receive calls normally when my screen is on. I'm also able to make outgoing calls without any problems.
I suspect that it has something to do with either my minimum frequency or my voltages (i.e. my phone isn't coming out of deep sleep properly), but after raising either/both of them the problem persists.
Has anyone come across this before, or have any suggestions on how to fix this? Would flashing a different radio help (although I've used my current radio on a different ROM without any issues)?
I apologize if this has been asked before. I did a brief search but did not find anything similar to this exact problem.
Some more info:
-ROM: Apex v1.1.3
-Kernel: Trinity (T132-NS-CV-56HZ-ANY-201212623)
-When a call is incoming:
1) The screen remains off, while the capacitive touch keys light up. There is no ringing either.
2) After a few seconds, the phone reboots and the splash animation appears.
What clock speeds are you running at (Min and max)? Are you using deep idle? etc.
063_XOBX said:
What clock speeds are you running at (Min and max)? Are you using deep idle? etc.
Click to expand...
Click to collapse
I do not have deep idle enabled.
Frequency:
400/1000 MHz, ondemand
(15000 sampling rate, 98% up threshold, 1 sampling down factor, 0 powersave bias)
Voltages:
Max Arm Volt - 1500 mV (1250 mV INT)
1320 mhz - 1425 mV (1150 mV INT)
1000 mhz - 1425 mV (1150 mV INT)
800 mhz -1200 mV (1150 mV INT)
400 mhz - 1100 mV (1150 mV INT)
200 mhz - 1000 mV (1150 mV INT)
100 mhz - 1000 mV (1050 mV INT)
developersdevelopers said:
I do not have deep idle enabled.
Frequency:
400/1000 MHz, ondemand
(15000 sampling rate, 98% up threshold, 1 sampling down factor, 0 powersave bias)
Voltages:
Max Arm Volt - 1500 mV (1250 mV INT)
1320 mhz - 1425 mV (1150 mV INT)
1000 mhz - 1425 mV (1150 mV INT)
800 mhz -1200 mV (1150 mV INT)
400 mhz - 1100 mV (1150 mV INT)
200 mhz - 1000 mV (1150 mV INT)
100 mhz - 1000 mV (1050 mV INT)
Click to expand...
Click to collapse
Your ARM voltages are all wrong. This can cause crashes, if they're too high.
Stock from 100 to 1000.
950
950
1050
1200
1250
polobunny said:
Your ARM voltages are all wrong. This can cause crashes, if they're too high.
Stock from 100 to 1000.
950
950
1050
1200
1250
Click to expand...
Click to collapse
Thanks for responding.
The default voltages for Trinity are slightly higher than default because of the bus OC I believe. It was only after I realized I had this problem that I raised the voltages for 100 MHz to 400 MHz a bit.
Anyways, I tried your above voltages but the problem remains.
I'm going to try flashing a couple more kernels (AirKernel, SimpleKernel) and finally my ROM again to see if that helps.
developersdevelopers said:
Thanks for responding.
The default voltages for Trinity are slightly higher than default because of the bus OC I believe. It was only after I realized I had this problem that I raised the voltages for 100 MHz to 400 MHz a bit.
Anyways, I tried your above voltages but the problem remains.
I'm going to try flashing a couple more kernels (AirKernel, SimpleKernel) and finally my ROM again to see if that helps.
Click to expand...
Click to collapse
Which kernel are you using presently? It is quite possible if it's a Trinity kernel that your phone simply doesn't support any type of overclock whatsoever. I'd recommend something a bit more "stock-ish" like the CM9 kernel, thalamus or simple kernel. Air kernel is very good too, very solid on my phone and not overclocked in any way by default. Has the stock voltages too.
Ok so apparently it's an issue specific to the Apex v1.1.3 ROM (which I would have realized if I read that thread more thoroughly, doh).
I'm on Euroskank CM9 now and everything seems to be working just fine.
Oh damn, those kind of things happen I guess. Good to know you got skankwich on this ;D
I have recently installed PimpMyROM for my tablet and have found this nice voltage setting feature.
Anyone have any good voltage values for longer lasting battery life without any cases of random reboots?
Best guaranteed to work is really not dialed into your specific tab and user habits.
Setcpu is an excellent app that can help you out with testing. It has a stress test future to make it easy to see if your Undervolt settings are stable.
Google Play claimed it isn't compatible for my tab so I grabbed it off Xda. It works fine. I gotta donate still... (and so should you if you get it here)
Btw: Setcpu has Undervolt settings built in too. You may want to freeze PMR while testing to be sure their settings are not conflicting.
Sent from my SGH-I997 using Xparent Red Tapatalk 2
But as for a starting place...
I have both my daughter's p6210 running smooth with these settings:
1200 MHz 1175 mV
1000 MHz 1050 mV
800 MHz 950 mV
500 MHz 925 mV
200 MHz 900 mV
The most intensive thing they do is play Survival Craft (for hours). Tabs were getting excessively hot before I Undervolted them. No crashes in days...
They're both on CM10.1
Sent from my SGH-I997 using Xparent Red Tapatalk 2
My voltages:
1400 MHz 1325mV
1200 MHz 1225mV
1000MHz 1175mV
800MHz 1150mV
500MHz 1050mV
200MHz 975mV
Its not much battery saver but rom is stable
My battery is getting old and along with that its life length. So I decided to undervolt and found it stressful but fun (lol weird huh?).
I'm currently stress testing it using SetCPU's stress test, so far it has not crashed.
My undervolt settings:
100 MHz - 950
200 MHz - 950
300 MHz - 975 *
400 MHz - 1000
500 MHz - 1025 *
600 MHz - 1050 *
700 MHz - 1075 *
800 MHz - 1100
900 MHz - 1125 *
1000 MHz - 1150
1100 MHz - 1175 *
1200 MHz - 1200
* - I'm just assuming SetCPU sets this automatically since it skips some clock speeds.
However I set the voltages increment by 25, so far the stress test has not shown any crashes.
What are your settings?
I run about -75 I think across the board using AndroidTuner, no stress test, but seems stable.