Database Info

400Mhz at -200mV on top of -50mV?

So I'm not sure if this 4th G2x I received is a total beast or SetCPU is just f'ing with me, but I'm cruising at -200mV on top of the already undervolted Faux CM7 kernel.
The phone has absolutely no problems and it just keeps going.
Here's my setup:
1000Mhz Max 950 mV Current 925 mV (-25 mV)
800Mhz Max 850 mV Current 750 mV (-100 mV)
500Mhz Max 800 mV Current 650 mV (-150 mV)
400Mhz Max 770 mV Current 570 mV (-200 mV)
PS: Real men type it out
Edit: Poll added!

GideonX said:
So I'm not sure if this 4th G2x I received is a total beast or SetCPU is just f'ing with me, but I'm cruising at -200mV on top of the already undervolted Faux CM7 kernel.
The phone has absolutely no problems and it just keeps going.
Here's my setup:
1000Mhz Max 950 mV Current 925 mV (-25 mV)
800Mhz Max 850 mV Current 750 mV (-100 mV)
500Mhz Max 800 mV Current 650 mV (-150 mV)
400Mhz Max 770 mV Current 570 mV (-200 mV)
PS: Real men type it out
Click to expand...
Click to collapse
i really wonder sometimes if its really UVing with values so high x_X 216 running at 350mV x_X
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I read in another thread by one of the developers (Faux?) that 770 mV is the lowest allowed voltage due to hardware restrictions and that any settings below that do nothing.

GideonX said:
So I'm not sure if this 4th G2x I received is a total beast or SetCPU is just f'ing with me, but I'm cruising at -200mV on top of the already undervolted Faux CM7 kernel.
The phone has absolutely no problems and it just keeps going.
Here's my setup:
1000Mhz Max 950 mV Current 925 mV (-25 mV)
800Mhz Max 850 mV Current 750 mV (-100 mV)
500Mhz Max 800 mV Current 650 mV (-150 mV)
400Mhz Max 770 mV Current 570 mV (-200 mV)
PS: Real men type it out
Click to expand...
Click to collapse
sincest said:
i really wonder sometimes if its really UVing with values so high x_X 216 running at 350mV x_X
Click to expand...
Click to collapse
You guys have amazing chips
The reason for 770mv @ 389/400 MHz is the limitation of ~100mv per "frequency jump" according to Tegra2 documentation. With the FakeShmoo implementation of overclock, we have a total of 8 slots (frequencies) to play with. If I start the lowest frequency let say at 500mv, then the max voltage at the eighth slot can only be ~1200mv. With 1200mv we can OC to 1.2~1.3 GHz, beyond that then it becomes unstable. So in order to get more juice @ higher clocks, we have to start a higher voltage at the low to get more juice at the high end. Of course, naturally, the next question would be why not start with 1000mv to begin with then you can get 1700mv at eighth slot? If we started with more juice at the low end, it would kill the battery 2x or 3x faster. So the current voltage table you see from my kernels is a compromise between battery life and OC Hope this clears it up a bit.

faux123 said:
You guys have amazing chips
The reason for 770mv @ 389/400 MHz is the limitation of ~100mv per "frequency jump" according to Tegra2 documentation. With the FakeShmoo implementation of overclock, we have a total of 8 slots (frequencies) to play with. If I start the lowest frequency let say at 500mv, then the max voltage at the eighth slot can only be ~1200mv. With 1200mv we can OC to 1.2~1.3 GHz, beyond that then it becomes unstable. So in order to get more juice @ higher clocks, we have to start a higher voltage at the low to get more juice at the high end. Of course, naturally, the next question would be why not start with 1000mv to begin with then you can get 1700mv at eighth slot? If we started with more juice at the low end, it would kill the battery 2x or 3x faster. So the current voltage table you see from my kernels is a compromise between battery life and OC Hope this clears it up a bit.
Click to expand...
Click to collapse
So there really isn't a hardware limit in place on how low this chip can go?
Sent from my HTC Vision (G2x in disguise)

I'm really starting to wonder if setcpu is busting our chops or not I'm
-100mV on all frequencies starting at 594mhz down to 216mhz on morfics jrcu 6/21 kernel, that can't be right can it is there a way to find out for sure???

for frequency 500mhz or 400mhz I can as low as I want ... 10mVs.. even 0mV. so i dont tihnk its accurate

c19932 said:
for frequency 500mhz or 400mhz I can as low as I want ... 10mVs.. even 0mV. so i dont tihnk its accurate
Click to expand...
Click to collapse
do you have any more than 100mV between frequencies?

Black6spdZ said:
do you have any more than 100mV between frequencies?
Click to expand...
Click to collapse
yes I do. should I not exceed 100mV between each frequency level then? would you happen to know the exact biggest voltage difference allowed between each level?
on another note, if I just leave them at 10mV, will that mean the processor will automatically take the voltage down to the lowest possible, or will it just do nothing but run at stock voltage?

c19932 said:
for frequency 500mhz or 400mhz I can as low as I want ... 10mVs.. even 0mV. so i dont tihnk its accurate
Click to expand...
Click to collapse
Yes, it seems possible to make settings that are not logically possible.
It would be nice if either SetCPU (which I am currently using) or Pimp My CPU would display in either real time or histogram what voltages are actually being used in the same way as they show frequency. Although I suspect this may be impossible due to hardware or this would be already implemented.

Added a poll up top.
I made it so you can vote either above or below -50mV. I'm basing this off the OC/UV kernel from Faux123.
I also skipped everything between 1.0 to 1.5Ghz. I'm going to assume at that speed, UV'ing will be very low.

double post

i actually use 1216max and uv it minus 150 all together so fauxs -50 plus i uv it -100, and my phone still flys and battery life is niceeee, oh and for the min i use 389, -200 on top of fauxs -50 so -250 all together

I am OC/UV up to 1200MHz -75mV on all frequencies below the undervolting built into Trinity JRCU kernel. This is stable and further UV gives me trouble. Your assumption about UV at higher frequencies is appears to be incorrect.
The poll actually confuses me, undervolting > -50 could mean I am not undervolting at all since 0 is greater than -50.

Interesting, I can UV more on the lower Mhz than higher. For example, at 1.0Ghz -50mV is already pushing it. Anything higher and I'll notice FC and random closes on certain apps.
First time polling, I guess there's no edit feature to change up the wording. Sigh.

SetCPU doesn't error check so everyone reporting -150mV and greater probably is incorrect. Remember there is only 800mV allowable from the highest frequency and only 100mV allowable between frequencies. So.. take my phone for instance.. I started at the highest 1.5Ghz frequency and tested -25mV at a time until phone rebooted and then went back up 25mV. This just happens to be 1300mV stable for me. This means the lowest 389Mhz can have at the lowest 500mV "1300mV - 800mV". I set everything -50mV across the board and then focused on 503Mhz since no matter what 389Mhz can only be -100mV lower. I was able to get -75Mv "725mV" stable. Then I was able to run 389Mhz stable at -150mV or 620mV. In actuality it is running 625mV since that is 100mV less than the frequency above it... setting it any lower in SetCPU would STILL only be 625mV regardless.
Also, this poll will be useless for everything but the 1500Mhz frequency as we wouldn't know if the user started with the SV or UV kernel. We need multiple polls with the final voltage eg 1100Mhz @ 1000mV,975mV,950mV
Test with a charger plugged in, I've had reboots with a battery at <50% because it cannot supply the high current draw of 100% cpu usage.

My specific settings are as follows as -?? means nothing because different kernels have a different starting point.
1075 mV @ 1200 MHz
975 mV @ 1100 MHz
875 mV @ 1000 MHz
775 mV @ 594 MHz
675 mV @ 432 MHz
575 mV @ 216 MHz
This is solidly stable having run it for several days without any bad behavior although any further reduction of voltage at 1200 MHz causes significant problems.
Phone: G2X
ROM: CyanogenMod 7.1 RC1
Kernel: Trinity 15 jrcu 06212011
Other relevant: SetCPU

I've gotten even better results with the SV kernel. After testing each speed for stability at lower and lower voltages here are my results:
1408Mhz @ 1175mV
1216Mhz @ 1075mV
1100Mhz @ 975mV
1015Mhz @ 900mV
816Mhz @ 800mV
655Mhz @ 725mV
503Mhz @ 650mV
389Mhz @ 595mV
lose 100Mhz from the UV/OC kernel but I get better UV settings with the SV kernel

Black6spdZ said:
I've gotten even better results with the SV kernel. After testing each speed for stability at lower and lower voltages here are my results:
1408Mhz @ 1175mV
1216Mhz @ 1075mV
1100Mhz @ 975mV
1015Mhz @ 900mV
816Mhz @ 800mV
655Mhz @ 725mV
503Mhz @ 650mV
389Mhz @ 595mV
lose 100Mhz from the UV/OC kernel but I get better UV settings with the SV kernel
Click to expand...
Click to collapse
too bad the lowest my phone can go for 1015mhz and 816mhz are 940 and 840mv respectively

Black6spdZ said:
I've gotten even better results with the SV kernel. After testing each speed for stability at lower and lower voltages here are my results:
1408Mhz @ 1175mV
1216Mhz @ 1075mV
1100Mhz @ 975mV
1015Mhz @ 900mV
816Mhz @ 800mV
655Mhz @ 725mV
503Mhz @ 650mV
389Mhz @ 595mV
lose 100Mhz from the UV/OC kernel but I get better UV settings with the SV kernel
Click to expand...
Click to collapse
We seem to be hitting about the same spot, almost exactly, I can OC to 1400 or 1500 but choose not to push my phone to that extent. I live in a very hot area and don't want to tempt fate.

Undervolting your Sensation

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

SetCPU settings

Hey guys, I wanted to make this thread now that we have root! Currently I have the following profiles, lets see how they work over the next few days
Main: 1458 max, 384 min
Battery < 50% - 1242 max, 810 min
Screen off - 810 max, 486 min
Both on demand.
What about you guys?

CollegeProfesor said:
Hey guys, I wanted to make this thread now that we have root! Currently I have the following profiles, lets see how they work over the next few days
Main: 1458 max, 384 min (is 384 too low? It was the default setting)
Battery < 50% - 1242 max, 810 min
Screen off - 810 max, 486 min
Both on demand.
What about you guys?
Click to expand...
Click to collapse
I'm running a little lower. ~1110 max, 384 min
Screen off - ~500, 384 min.
Both on powersave. Getting weird results however.

What type of results?

powersave doesnt work,. use on demand,
left it on power save at 1300, the cpu was running at 1500, changed it to ondemand , looks like its working

[Q] Phone Reboots Instantly on Incoming Call

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

UV limit reached: wakelocks + SOD + Instant Drop in Indicated Battery Level

(I intended to post this in "general:, not q&a)
SUMMARY: I have been slowly decreasing my voltage. Wednesday, three weird things happened on my phone that never happened before (wakelocks, unintended reboot, instant drop in battery indication).
CONCLUSION: I attribute all three things (wakelocks, reboot, instant drop in battery indication) to reaching an unstable voltage.
DESIRED OUTCOMES (Why am I posting this):
1 - I think I understand what happened, but maybe you guys can point out if I'm mistaken.
2 - Maybe someone else will be interested in seeing voltage limits for my phone (-75mV appears to work, -100mV appears to be too low for me... I guess other Infuses may act differently)
3 - It seems to me that maybe excess UV should be considered when investigating causes of wakelocks (there are many other causes of course). This conclusion is based only on this one experience as reported below. I have heard obviously unintended reboot can be associated with too much UV'ing, but I never heard wakelocks could be associated with UVing. Open to comments.
DETAILS:
I’m using stock GB, rooted, Zen’s Infusion A/1600 kernel, with governor conservative 100-1200millivolts.
I have been decreasing my voltage settings by 25 millivolts every other day over the last week.
Wednesday, I got to 100 millivolts below max on all points (except 1600Mhz, which was 50 millivolts down)
Specifically, my levels on Wednesday were:
100 Mhz: 950mv max – 100mv = 850 millivolts
200 Mhz: 950mv max – 100mv= 850 millivolts
400 Mhz: 1050mv max – 100mv = 950 millivolts
800 Mhz: 1200mv max – 100mv = 1100 millivolts
1200 Mhz: 1275mv max – 100mv = 1175 millivolts
1600 Mhz: 1400mv max – 50mv = 1350 millivolts
Before Wednesday, I had performed stability test (using “stability test” program for about 30 minutes... it sweeps the frequencies I think) at 1600Mhz Fmax while 50 millivolts down and another stability test at 1200 Fmax while 75 millivolts down, both for around 20 minutes, no problems there and no other problems with my phone in the last week since I upgraded to GB. When I decreased to 100 millivolts down I only did a 30-second “stress test” from within setcpu at 1200Mhz. No problems there.
All day Wednesday I was running the conservative governor, with Fmin=100 and Fmax = 1200, cfq io scheduler, UV settings as above (all 100 down except 1600Mhz). I have one setcpu profile that puts the phone to 1600Mhz Fmax when I manually launch "Memento Database" program, but I did not launch that program at all on Wednesday, so I never got above 1200Mhz on Wednesday.
My battery profile for the day Wednesday is shown in attached graphic.
The label “phone awake with screen off” points to a time period approx 2-4pm when my phone was awake with the screen off. I have never seen this happen on my phone before, and I look at this screen pretty regularly.
I used the phone heavily during my hour-long ride home from work from 5pm to 6pm (no problems). I was surfing the internet, reading the news about the Hurricane in New Orleans (not tweaking my phone). Phone worked absolutely perfectly throughout this hour long heavy usage.
First thing on getting home, I connected to wifi and surfed for about 5 minutes. At about 6:10pm, while surfing with my battery level happened to be 47% (as I deduced later), suddenly appeared the black screen with Samsung logo ... phone booted up to normal home screen. I think that’s what you guys call the “screen of death”?
I assume the phone reboot may be my first indication that I’ve reached my limit for UV’ing?
But here’s what concerned me more than the SOD:
Immediately after rebooting, my battery now showed 8% !
How does it go from 47% to 8% that fast? I have several screens from “battery monitor widget” and from the Android battery screen, and they all confirm the battery dropped from 47% to 8% over this very short time period (less than 5 minutes). I also have audible low-battery warnings on my phone (generated by Tasker, a lass with a pretty British lady voice) at levels of 40%, then 30%, then 20%, then 10%. I didn’t get any of those audible warnings prior to this spurious reboot – seems to confirm either this was a real drop in battery, or else my battery signal feeding all my applications (battery monitor widget, Tasker, GB battery profile) somehow went bezerk.
I have a hard time imagining this could be a real drop in battery ....where would the energy go? The phone did not get hot.
Is it possible somehow the phone’s battery calibration got confused?
Attached is a screenshot of battery drop.
The rapid drop from 70% to 50% was when I was using the phone heavily for an hour... I consider that normal.
The vertical drop from 47% to 8% is what is completely unexplainable to me. Although I have seen in the forum reports of battery gage reading unreliably in certain circumstances.
By the way, I put my UV setting back to -75 Wed night, and phone working fine ever since. No wakelocks or other anomolies.
Questions:
1 – Is this what is known as “screen of death”
2 – Has anyone seen that type of rapid battery level decrease?
3 – What do you think caused it.... calibration problem or actual loss of battery? If calibration problem, it’s kind of weird that the voltage increased smoothly during recharge afterwards?
4 – Do you think the phone-awake-with-screen off occurences earlier in the day are related to my UV'ing? I didn't see them before and I haven't seen them since went back to -75mV, suggesting they are caused by UV'ing. But also note the phone worked fine during my hour long drive home after the wakelocks and before the SOD
5 – Do you agree I have probably reached stability limit and should stick with 75 millivolts down instead of 100 (I have been back on 75 again for awhile...no problems)
Attached below is my battery voltage over the course of the day, annotated with the items discussed above.

If you undervolted, your going to run into problems man. Simple as that. If you do anything to your phone not stock these things can and will happen.
Just take is as a fluke and move on. Everyone's phone uv's differently.
Imo what happened is the processor was making lots of errors and corrupted some part about your batteries actual percentage and was a lot lower than was presented to you.
Phone awake while screen on is a wakelock and quite common. Usually an app holds the phone turned on.
Edit: if uv of 75 fixes the problem. Then that definitely us what you should do. Note, benchmarks don't give stability reports. You would need run them for hours before you get accurate assessment.
Sent from my SGH-I997 using xda premium

1 – SOD is when the screen is black and phone won't unlock. Sometimes the volume buttons work. A long press of the power button will usually reboot the phone.
2 – The rapid power drains I've seen have typically been due to the rild process running amok and maxing the cpu. Typically the phone gets hot when this happens. In a SOD situation, you can typically still connect to the phone via ADB. If you can do this, run "adb shell" and then the following command: "top -m 5 -n 1" (spacing emphasized as all spaces are required).
3 – Dunno, but I'm with Elliot: the thing you changed was UV. Back that out and see if the problem goes way.
4 – Awake when screen off is usually related to an app that sets a wakelock and syncs in the background. Use Better Battery Stats to troubleshoot this. If it was UV causing this, I'm not sure why that would be - see #3
5 – FWIW, I never UV below -75... and truth be told I haven't seen a significant savings in battery life with UV, but that's likely because my phone is asleep most of the time...

Thanks for your response Elliot.
I think you interpretted it roughly the same as me except you lean more towards other possible causes of wakelocks unrelated to UV. That is certainly possible and I will keep a close eye on tha (moreso as a reuslt of your comments)
I am moving on with my phone at –75mv and don’t plan any drastic changes as a result of this unless I see more problems, but I also want to treat this as a learning experience. I spent awhile collecting the data and drawing my own conclusions, but wanted to bounce it off the others here for my own long-term learning.
Thanks again.

Thanks Zen, good info as always.

if you UV, i had better luck with higher UV on the top end:
ex: -125 or 150 @ 1600
-100 or 125 @ 1200
-75 or 100 @ etc
Basically, you are limiting power consumption and increasing battery life.
Once you hit the lower limit, your phone will let you know.
If you care to try, and you will have a slower phone:
set cpu max to 800 and then uv -75, -50, -25 stepping down. you will see the difference. it will make calls or mms fine. But you will notice slowdown with web/games/etc

every cpu is different. i've had 2 infuses because my screen broke, i replaced it and the replacement was defective, found another phone for about the price of a replacement screen.
one get's me about -100mv the other was completely stable at -225(maybe more) with stock clocks and -200 overclocked.
one thing that can cause instability is a big voltage differential from low to high especially with on demand governor, it's not only a matter of necessary volts to drive the chip per clock, the rapid fluctuations can cause issues. if you want performance you might want to uv from the top down leaving the lower freqs stock and seeing how much uv it will tolerate at 1600 before you mess with lower clocks, you might get more uv on the upper clocks that way which will reduce heat. if you want battery life then try less or no overclock still going from the top down.
for people that can't reach 1600, or think they can't try to set 1400 and 1600 at the same voltage so the voltage table has a plateau at the top. setting 1200 and 1400 high might smooth the transition to 1600, also try the voltages across the board, there may be a narrow range where the heat and required voltage balance out. i did this with my captivate and got it from 1200 to 1300mhz but 1300 would only work in a narrow 50mv range and 1200 needed to be enabled as well as set to the same voltage. the chip in that phone didn't like overclock at all compared to most infuses but sometimes thats how it goes.

still have wakelocks
if you UV, i had better luck with higher UV on the top end:
Click to expand...
Click to collapse
one thing that can cause instability is a big voltage differential from low to high especially with on demand governor, it's not only a matter of necessary volts to drive the chip per clock, the rapid fluctuations can cause issues.
Click to expand...
Click to collapse
Interesting. Both comments end up suggesting the same strategy to my way of thinking (more UV'ing at top frequencies will create a flatter voltage curve across the range of frequencies). I'll give it some thought when I get back to polishing my uv strategy. Maybe instead of putting all back to -75 I should do something like:
100 Mhz: 950mv max – 75mv = 875 millivolts
200 Mhz: 950mv max – 50= 900 millivolts
400 Mhz: 1050mv max – 75mv = 975 millivolts
800 Mhz: 1200mv max – 100 mv = 1100 millivolts
1200 Mhz: 1275mv max – 75mv = 1200 millivolts
1600 Mhz: 1400mv max – 100mv = 1300 millivolts
...and stick with conservative governor to avoid the big jumps. That way I'd never jump more than 100millivolts (except between 400 and 800 which jumps by 125... but was apparently already a 150mv jump in the stock?). But I'd want to do some testing on the at 1600 to see how it likes the 100mv down, first. Sound reasonable?
========
New subject
An "update" on my phone:
My battery display still shows today that there is quite a lot of time with cpu on and screen off (wakelock) even though now my phone is not undervolted at all today (I removed undervolting to do some testing and haven't put back the uv'ing yet).
I'm heading over to the market to download Better Battery Stats per Zen's suggestion.
Thanks

electricpete1 said:
Interesting. Both comments end up suggesting the same strategy to my way of thinking (more UV'ing at top frequencies will create a flatter voltage curve across the range of frequencies). I'll give it some thought when I get back to polishing my uv strategy. Maybe instead of putting all back to -75 I should do something like:
100 Mhz: 950mv max – 75mv = 875 millivolts
200 Mhz: 950mv max – 50= 900 millivolts
400 Mhz: 1050mv max – 75mv = 975 millivolts
800 Mhz: 1200mv max – 100 mv = 1100 millivolts
1200 Mhz: 1275mv max – 75mv = 1200 millivolts
1600 Mhz: 1400mv max – 100mv = 1300 millivolts
...and stick with conservative governor to avoid the big jumps. That way I'd never jump more than 100millivolts (except between 400 and 800 which jumps by 125... but was apparently already a 150mv jump in the stock?). But I'd want to do some testing on the at 1600 to see how it likes the 100mv down, first. Sound reasonable?
========
New subject
An "update" on my phone:
My battery display still shows today that there is quite a lot of time with cpu on and screen off (wakelock) even though now my phone is not undervolted at all today (I removed undervolting to do some testing and haven't put back the uv'ing yet).
I'm heading over to the market to download Better Battery Stats per Zen's suggestion.
Thanks
Click to expand...
Click to collapse
in my experience that will probably work well. but if the phone is at it's limits with the 1600mhz clock then you might have a specific voltage that it prefers so it's possible it doesn't work into what i was describing. try it, i can't say uv is safe but i haven't broken a phone yet by driving the voltage too low. it just tends to crash and will be fine on the next boot after you clear the settings in my experience so far.

Thanks. I went ahead and made the above changes in voltage. Then I manually rebooted (to allow voltage changes to take effect), went into setcpu to set my max frequency to 1600.
Successful stress test from within setcpu ~ 50 seconds.
Then went to the application named "Stability Test", selected "scaling" (which is supposed to vary the frequency) and has been successfully running the test for 14 minutes (11 successful cpu runs and 75 successful RAM runs). It has been on 1600Mhz the whole time according to the Stability Test display. The battery temperature increased from 37 to 42 pretty quickly then slowed, looks to be stable at 43C now.
Elliot warned above that it takes stability tests hours to find problems and Stability Test documentation mentions something about 5 hours on one frequency to find a problem. But if it's only running at one frequency as it appears from the display (stuck on 1600), I think even after running it for 5 hours I might not be confident that it will ferret out all the problems that might arise while switching frequencies (and I'm not sure I want to leave it running for 5 hours if it's stuck on 1600). I'm not sure exactly what is the purpose of "scaling" mode is, if it doesn't change frequency.
At any rate, I''m going to terminate the test and give it the real-life test now.
I will leave my governor at 100-1600 conservative governor for a few days to help shake out any glitches hiding inside there.
Will let you know if anything goes wonky.
Later on when I'm confident in results, I plan on setting up profiles for 100-400, 100-800, 100-1200, 100-1600 depending on the situation, but will stick with conservative in all cases.
Thanks again.

I wanted to provide an update of testing I have done with UV on my phone. Nothing conclusive for me yet, just a lot of data.
I’ll discuss 5 different UV settings labeled below as 0, A, B, C, D (going from most UV to least UV).
About notation - I think it is helpful to list UV settings in the full format I use (rather than just how many volts down) for two reasons:
1 – The reference voltages vary depending on kernel. So it could be misleading to report what the reduction in voltage is without reporting the reference. At 1200Mhz, Zen’s Infusion A/B uses 1275millivolts while Entropy’s DD uses 1300millivolts (voltages match at other frequencies). I’m not sure what the voltages are in stock kernel.
2 – Listing the final voltages allows you to see how much jump in voltage there is from one frequency to the next (large jump could possibly increase instability)... this aspect is not as obvious if we just list how many volts below the reference.
Setting set 0
100 Mhz: 950mv max – 100mv = 850 millivolts
200 Mhz: 950mv max – 100mv= 850 millivolts
400 Mhz: 1050mv max – 100mv = 950 millivolts
800 Mhz: 1200mv max – 100mv = 1100 millivolts
1200 Mhz: 1275mv max – 100mv = 1175 millivolts
1600 Mhz: 1400mv max – 50mv = 1350 millivolts
Duration: Tested less than one day.
Results: Reported in original thread: caused unwanted reboot while surfing. After that the battery indicator jumped.
Setting set A.
100 Mhz: 950mv max – 75mv = 875 millivolts
200 Mhz: 950mv max – 50= 900 millivolts
400 Mhz: 1050mv max – 75mv = 975 millivolts
800 Mhz: 1200mv max – 100 mv = 1100 millivolts
1200 Mhz: 1275mv max – 75mv = 1200 millivolts
1600 Mhz: 1400mv max – 100mv = 1300 millivolts
Duration: Tested 3 days heavy use
Results:
* “Rainbow Screen After Trap Game” – I tried the game “Trap” which was recommended in a thread somewhere as being a good test to find stability problems using UV. Sure enough upon exiting the game once, my screen turned to rainbow colors. I rebooted to restore screen to normal (same UV). I played the game for 15 minutes exiting a few more times, no more problems.
* “Widgets Lost” - Once after reboot I lost all my widgets (Tasker, Color Notes, Elixir). They did not come back even when I went to stock voltages and rebooted. Had to manually restore each of my widgets.
* “Discolor Upon Screen On” - Once in awhile when turning on screen, some colors are initially wrong (mostly I notice the white labels of my icons are yellow or pink). It goes away very quickly - either after I touch the screen or after scroll around a little. After that everything is normal.
* “Flash Upon Screen On” - Once in awhile when turning on the screen, I see a white flash for a fraction of a second (sort of like with an old TV tube when you turn it on or off). After that everything is normal.
These last two symptoms (“Discolor Upon Screen On” and “Flash Upon Screen On”) occurred probably once per day over the course of the three days relatively heavy usage.
Setting set B
100 Mhz: 950mv max – 25mv = 925 millivolts
200 Mhz: 950mv max – 25= 925 millivolts
400 Mhz: 1050mv max – 25mv = 1025 millivolts
800 Mhz: 1200mv max – 75 mv = 1125 millivolts
1200 Mhz: 1275mv max – 50mv = 1225 millivolts
1600 Mhz: 1400mv max – 75mv = 1325 millivolts
Duration tested: 3 days heavy use
Results:
* “Discolor Upon Screen On” – Same as above. 2 or 3 times over three days heavy use
* “Flash Upon Screen On” – Same as above. Once over three days.
setting set C
100 Mhz: 950mv max – 15mv = 935 millivolts
200 Mhz: 950mv max – 15= 935 millivolts
400 Mhz: 1050mv max – 15mv = 1035 millivolts
800 Mhz: 1200mv max – 50 mv = 1150 millivolts
1200 Mhz: 1275mv max – 25mv = 1250 millivolts
1600 Mhz: 1400mv max – 50mv = 1350 millivolts
Duration Tested: 3 days heavy use
Results:
* “Discolor Upon Screen On” – Same as above. 2 or 3 times
(Did not have the Flash upon screen on)
setting set D = 0 undervolt – use Zen’s default settings.
Duration: about 2 weeks experience with GB in this configuration
“Discolor Upon Screen On” – Never saw it
* “Flash upon screen on” – Never saw it, but did see a similar flash just once in my phone application when I removed phone from ear to look at keypad.
** EDITED TO ADD - Today after posting this, I noticed the flash upon screen on" while using no UV, 100-1200Mhz. Maybe I just wasn't looking for it before.
Other Testing Using Specific Applications:
I did a lot of testing with these programs on settings A, B, C and saw no anomalies. For settings A, B, and C, did the following:
SetCPU “Stress Test” for approximately one minute
“Stability Test” Applicaiton– “Scaling Stability Test” subtest for approx 20 minutes (battery gets up to about 115F).
“Stability Test” Applicaiton – “CPU+GPU Stability Test” subtest for approx 10 minutes (actually did this only in B, C, didn't try it in A)
I played the game "Trap" (that caused the problem in setting A) for 15-20 minutes in B, C, exiting and reentering a few times. Didn't see any problems.
Interestingly, when I run Quadrant it sometimes flakes out (returns to Quadrant start screen without any result) and somtimes run to conclusion. But this happens even on stock voltages, and I think I remember it's a problem with Quadrant that others have seen, so I’m inclined to think it is not an indicaion of instability I should worry about.
Analysis:
It looks like B is the most UV I can apply without significant problems appearing during 3-day test. But I still had some minor anomalies I notice occasionally when turning screen on (brief flash and brief discoloration),.but they occur to certain extent even at less UV (C) and at zero UV (D)
All of the above real-life testing in A, B, C was done with max frequency of 1200 (because I wanted to rule out 1600 as a problem).
I used 1600 only during the specific stability test appliations.. that ran fine and also in the D configuration that ran fine. So the problems (if they are problems) come from UV, not from using 1600Mhz.
Questions:
Do you think discoloration upon turning on the screen or flash upon turning on is cause for concern? The symptom itself is not an inconvenience but I’m wondering if it’s warning me about something else going on...(***)
I don’t really have a feel for what change in battery life occurs with these different settings. Seems very difficult to quantify. Any thoughts?
By the way, I'm using ULCB3 stock rooted GB. Using Zen's Infusion-A kernel. cpu control using setcpu: Mostly 100-1200Mhz cpu frequency, conservative cpu governor with the Up/Down threshholds tweaked to 95/45, noop io scheduler.
I installed this configuration about a month ago using qkster's Heimdall one-click.Never had any problems other than those mentioned above which may or may not be problems.
*** I have to confess, I wiped Davlick cache and wiped the other cache at that time, but never did the "factory data wipe" because I had data on my phone that wasn't backed up. I'm not sure if those particular instructions required factory data wipe or not but I remember it was mentioned as good practice. It occurs to me maybe these subtle brief strange symptoms upon turning on the screen are remnants from incomplete wipe?

I went back to stock and still had the occasional occurence of discolored screen upon waking from deep sleep.
It seems harmless, goes away if cycle the screen.
So I re-established UV. I have had my phone at the following settings since 9/17/12. No problems for me other than that occasional discoloration or flashing upon waking for sleep and one other problem where the phone would occasionally ring and I could see the call but not hear the caller (they could hear me). I eventually traced that to tweaking my governor settings... will post that in another thread.
100 Mhz: 950mv max – 50mv = 900 millivolts
200 Mhz: 950mv max – 25= 925 millivolts
400 Mhz: 1050mv max – 50mv = 1000 millivolts
800 Mhz: 1200mv max – 75 mv = 1125 millivolts
1200 Mhz: 1275mv max – 50mv = 1225 millivolts
1600 Mhz: 1400mv max – 75mv = 1325 millivolts

electricpete1 said:
I went back to stock and still had the occasional occurence of discolored screen upon waking from deep sleep.
It seems harmless, goes away if cycle the screen.
So I re-established UV. I have had my phone at the following settings since 9/17/12. No problems for me:
100 Mhz: 950mv max – 50mv = 900 millivolts
200 Mhz: 950mv max – 25= 925 millivolts
400 Mhz: 1050mv max – 50mv = 1000 millivolts
800 Mhz: 1200mv max – 75 mv = 1125 millivolts
1200 Mhz: 1275mv max – 50mv = 1225 millivolts
1600 Mhz: 1400mv max – 75mv = 1325 millivolts
Click to expand...
Click to collapse
1. discolored screen: zen told me about these. I've not seen it..no known harm effects though.
2. I've pushed the 1600 to -125mV; 1200 to -100mV without issues.