This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
I'd be a little careful with pushing undervolts too much. For one, it can and will lead to instability if you get very aggressive (of course, you can bump things back up). But from what I've read over on xda from some of the devs, undervolting too much can lead to issues where the phone may still seem stable but will internally mess some things up and not go into deep sleep correctly or quickly, thus resulting in more battery drain in the long run. Here is what I have managed so far:
Btw, you should also check whether your voltages are actually being applied. Some of the kernels seem to allow undervolting in SetCPU but are actually undervolted by a fixed amount by the kernel developers, and SetCPU changes have no effect on the actual voltages on the processor. An easy way to test it is to drop the 1.2 or 1.35 GHz to something really low like 1000mV and seeing if you have to do a battery pull to reboot your phone (make sure SetCPU isn't set to apply voltages at Boot). I'm using the Jame Bond kernel over on XDA and it definitely allows undervolting as I've had my phone freeze up when I push below 775mV @320MHz
Yeah the voltages are definitely being applied set them all to 600mv and it froze up. But I'm well aware of the risks I'm just wondering what people are going down to, my battery life has increased by like 2x. Lol
Ah, good to know. I just wanted to put it out there so someone didn't try to use your voltages right off the bat and then come back here to rage at you for breaking his/her phone Looks like you have a great chip in your phone if you are stable at 700mV @320MHz. 775 is the lowest I could go, and I'm staying at 800mV just to ensure being rock stable. Still, battery life has been awesome. With Wifi on, I still get a little less than 1% per hour drainage overnight. And that is without any juice defender tricks...and all google apps pushing updates/email to my phone.
370mhz is stable at 600mv lol... I put 370 as the min and Max frequency then did a stress test for around 30 seconds with no errors or freeze ups.. I got lucky with this phone, my old Droid couldn't be undervolted at all
so i have been flashing and doing this stuff for awhile but never really got into undervolting.. I am running axiom 2.4 with his apex kernal (the one that comes with the rom) I have used setcpu in the past (mainly to overclock OG Droid, DINC2)
I don't mind undervolting if it will help battery life some while not cutting on performance too much..
can someone either explain or give me a link that would help me better understand undervolting?
http://www.droidforums.net/forum/rescue-squad-guides/47871-overclocking-101-a.html <-- that thread is a general overclocking guide, but hits voltages too. Of course it was designed for the OG Droid, but same basic ideas remain. I haven't actually read it in a while to remember how much details he goes into about voltages. There is much more detailed information out there though, if that doesn't cut it for you.
My Gnex is running RootzBoat and I'm using the same kernel as you (Fab's). However, my SetCPU screen does not show the VOLTAGE tab between the PROFILE and ADVANCE tabs. What am I missing?
Edit: NVM, I installed the AOSP rom codename android and I now have the Voltage tab.
I see that you are on Verizon when I looked at your radio version on screenshot. Can you share what kind of battery life are you getting with setup rom and UV settings? In terms of screen time keep awake time and % of CPU used by android os.