Wich undervolting values do you prefer with the latest nightly from Franco?
The efficient and stablest
Sent from my Galaxy Nexus using xda premium
I am on franco kernel r180. I actually am using default mV. And have seen great results this far.
Just as well, using 25% brightness and only used Wi-Fi (4G buries my battery. Using a stock GN (Verizon) battery). Here's some photos.
Edit: I accidentally reversed the order of the screen shots from the way I wanted. Anyway, its been a great kernel. Kudos to franco. He's very smart. I wish I could do something this awesome.
One last thing, I've kept Max CPU at 1036MHz. It keeps the phone cool as the other side of the pillow. When I'm only using xda premium app, some light web browsing and Pandora running, 1036MHz is perfectly fine. I hope you find this useful.
Sent from my Galaxy Nexus using xda premium
Running AOKP B38 + Franco M3, and seeing great results with these voltages. If I lower it -25 mv across the board, the phone gets hot easily. And -50 mv across the board, and it'll randomly reboot when turning on Wi-Fi or while playing music, multitasking, etc.
Also, usually have it running at 728 MHz, unless I actually need to get stuff done and I up it to 1036 MHz. I've never had to set it at 1228 MHz.
Sent from my Galaxy Nexus using Tapatalk 2
The upper value doesn't really matter at all since the CPU is hardly ever sitting there.
Sent from my Galaxy Nexus using xda premium
I just wanted to post an update on how I am doing with Franco kernel r180. Just to be clear, this is not a continuation of my results from yesterday. Today's results are after a full charge.
CPU settings remain the same in terms of min and max, 384/1036 respectively, mainly on Wi-Fi (was on 3G for a good 20 minutes when I walked to the local CVS) and 25% brightness (again, shifted that to 100% when I went to CVS, but brought that back down to 25% when I got home).
I am close to 2.5 hours of screen time with 50% battery used. I have kept the screen on for a long time for testing reasons. Also, a 23 minute phone call was done on speaker phone with screen on as well. Phone stays very cool with these CPU settings.
If you have any questions, please feel free to ask.
Edit: as for under volting, I'm at (all in mV units of course) 1400, 1300, 1250, 1225, 1125, 950 ,900 for (all in MHz units of course) 1536, 1344, 1228, 1036, 729, 384,192 respectively. Again, my CPU boundaries are stated above so I'm never at settings such as 1534, 1334, etc.
Sent from my Galaxy Nexus using xda premium
I got these results using AOKP build 36 and Franco Kernel 166. 3G on when screen is on with occaisonal LTE (no WiFi usage). CPU clocked between 196MHz and 1036MHz with 384MHz for when the screen is off. Auto screen brightness. The last 3 images are my voltage settings. The saved voltages are the ones that were used.
I had a slightly longer screen on time and battery life. In my experience the voltage didn't affect heat output, but clocking the CPU at 1036MHz instead of 1228MHz did.
Related
Im new to android, what is the best setting for setcpu for balancing performance and battery life. Thanks in advance
Sent from my SPH-D700 using XDA App
What Rom/kernel are you on? Voltage Control might be the better option.
The Root said:
What Rom/kernel are you on? Voltage Control might be the better option.
Click to expand...
Click to collapse
On leaky gingerbread eeo3, don't know what kernel but kernel version is 2.6.35.7, firmware is 2.3.3...
The lower the maximum speed you can tolerate will give you the max battery life. A lot of people keep 800 Mhz as max for that reason.
If you want a good mix between battery and performance, I recommend keeping your maximum clock at 1000Mhz (default) and lowering your minimum clock to 100Mhz (default should be 200Mhz) if your phone will allow it.
Blankrubber said:
If you want a good mix between battery and performance, I recommend keeping your maximum clock at 1000Mhz (default) and lowering your minimum clock to 100Mhz (default should be 200Mhz) if your phone will allow it.
Click to expand...
Click to collapse
Yeah, just make sure you have journaling on if you are going to try 100 Mhz. A lot of phones get the sleep of death from that. Mine is one of those. Then you will have to pull the battery and adjust your settings to 200 Mhz minimum on SetCPU.
Or....You could not use 100mhz at all!
It uses the same voltage as 200mhz. And by increasing the amount frequencies scaled makes the phone slower.
800mhz max, 200mhz min. 800mhz is volted -75 over 1ghz. Which should increase battery life.
Awsome stuff guys. Thanks for all the great info and to all that reply... Thanks again
Sent From My Epic 4G
darkierawr said:
Or....You could not use 100mhz at all!
It uses the same voltage as 200mhz. And by increasing the amount frequencies scaled makes the phone slower.
800mhz max, 200mhz min. 800mhz is volted -75 over 1ghz. Which should increase battery life.
Click to expand...
Click to collapse
I'd quote him but I'm on my phone. Rodderik has stated that all the frequencies use the same internal voltage except for 100mhz, which uses a slightly less internal voltage. What we're adjusting and seeing read in voltage control is the arm voltage, or the processor voltage at each frequencies. I'm not sure the exact difference, but there is a slight drop in voltage at 100mhz compared to the other frequencies? A battery saving difference? Who knows
Sent from my SPH-D700 using XDA App
Just insalled new syndicate frozen rom. Set cpu not compatible? Installed set cpu and every time screen goes to sleep, I can't get it to wake up unless I pull out battery. Anybody else having this problem on this rom?
Sent from my SPH-D700 using XDA Premium App
otee670 said:
Just insalled new syndicate frozen rom. Set cpu not compatible? Installed set cpu and every time screen goes to sleep, I can't get it to wake up unless I pull out battery. Anybody else having this problem on this rom?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Everyone try conservative now, not on demand...
Edit::: The problem is with Voltage control 4b4, I'm going to test more before I report and start a thread, but feel free to...
Help support autism awareness,it only takes 2 seconds to help make a difference...
http://picketfenceblogs.com/vote/3616
Just changed setting to coservative and so far it seems to be working. settings is max-1300000 min-200 conservative (charging) max-1300000 min-1300000 conservative (screen off) max-400 min-400 consevative... on screen off, I tried max-200 min-200 phone stays in sleep. This what worked for me...
Sent from my SPH-D700 using XDA Premium App
Thanks to ecooce
Sent from my SPH-D700 using XDA Premium App
As far as power saving goes, we all know dark wallpapers, small data usage and brightness can drastically reduce power consumption. CPU is also a large part of power usage especially the GN's dual core. I haven't messed with SetCPU since my nexus one. What might be some of the SetCPU profiles you might be using? And some of the other power saving techniques?
So far I just have a flat black wallpaper, auto-brightness, and a setCPU profile of the lowest MHz when screen off, although I can't tell if the profile is making a difference.
I have screen off at 350/700 because 700mhz only costs me an extra 100mv with my undervolts. And battery <20% @ 350/700 Also but my battery life is so good i havent made it to <20% yet.
Sent from my Galaxy Nexus using xda premium
How do i change the amount of volts used in SetCPU?, sorry i have no experience with voltages haha
mikeacela said:
How do i change the amount of volts used in SetCPU?, sorry i have no experience with voltages haha
Click to expand...
Click to collapse
You need a kernel such as this
I'm currently using the UV only kernel as I dont find an overclock is necessary on the Gnex.
Basically, the stock kernels on this phone (like every other phone) don't support voltage control out of the box
@rbiter said:
I have screen off at 350/700 because 700mhz only costs me an extra 100mv with my undervolts. And battery <20% @ 350/700 Also but my battery life is so good i havent made it to <20% yet.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have the same screen off profile, with conservative governor. On the stock 4.0.1 kernel. No problems with this at all. Probably saves quite a bit of battery.
Antzor said:
You need a kernel such as this
I'm currently using the UV only kernel as I dont find an overclock is necessary on the Gnex.
Basically, the stock kernels on this phone (like every other phone) don't support voltage control out of the box
Click to expand...
Click to collapse
Is this kernel compatible with CDMA bands?
mikeacela said:
Is this kernel compatible with CDMA bands?
Click to expand...
Click to collapse
Nope
Sent from my Galaxy Nexus using XDA App
Running ARHD 2.1.2 on LTE VZW GNex
CPU Profiles:
350/350 when Battery <20% Priority 97
700/350 when Battery <50% Priority 99
920/350 when Battery <80% Priority 98
350/350 when Screen Off Priority 100
Not sure how effective they are, only second day using the profiles.
What temperatures are considered normal for the CPU?
I'm running Franco kernel and liquid smooth 1.3 with default settings on both.
Heavy use in ambient 20 degrees my CPU sits around 50. Low use I sit close to ambient.
Sent from my Galaxy Nexus using XDA
It's normal.
I'm wondering if anyone's undervolted and to what values.
I'm also wondering waht the deafult values are and if they change per kernel.
Is there a way to disable SetCPUs undervolting settings?
Has anyone improved battery life with profiles? On the Eris this was the only way to get usable battery life.
Or not. I gave up undervolting after I actually compared battery life at stock values vs undervolted (on my old phone, sgs4g) and discovered it does nothing for battery life.
Edit: undervolting "might" marginally increase standby battery life, but considering how good this phone already does... it certainly won't increase actual screen on usage.
Sent from my Galaxy Nexus using xda premium
Depends how low you under volt. Got more battery life, maybe about an hour, after finding optimal battery life on my gfs Gnex.
If you don't under volt correctly, of course it won't improve battery life.
From my sexy white, Nocturnaled HTC One X
If you're not overly comfortable with undervolting, then using one of the many kernels with Smart Reflex will do a mild undervolt for you. If you are comfortable, then the only way to find numbers good for your phone is to try and test. I tweaked mine down to the point that I was occasionally getting hot boots when the screen was off and media was playing. Tweaking the numbers back up added the needed stability. Even little things like kernel or ROM revisions can change what voltage is or isn't stable. Another example is that when I updated my Jellybro CM10 version the other night, along with updating leankernel from 4.1.0exp3 to 4.2.0, I had to increase a few of my voltages to avoid hot boots.
Just for example numbers, here are mine:
Code:
1350MHz -- 1200mV
1200MHz -- 1150mV
920MHz -- 1050mV
700MHz -- 950mV
350MHz -- 825mV
These numbers will vary from device to device and even between ROM/kernel combinations, so don't use them as hard fact.
Thanks. On a phone like this it might not make a huge difference but on the Eris (Where stock battery life could sometimes be 6 hours if you actually used your phone) an undervolted kernel with setcpu could turn those 6 ours into 48.
Thanks Cilraaz, I'll try those voltages out and benchmark a bit to see if they're stable for my system.
Two things I can say for sure:
1. you will have very limit battery gain by undervolting with Gnex, no matter how low you try.
2. undervolting will bring some stable issue if you get too low, like lose signal and reboot.
I am using Kernel Franco GPU 384 Stock rom on my 4.1.1 and did undervolting
Current configuration:
384Mhz
950mv
------------
729Mhz
1050mv
-----------
1036mhz
1125mv
----------
1228mhz
1275mv
-------------
I did not change the frequencies of overclocking, because I'm not using them.
I felt an improvement in battery consumption unless the unit is heating up.
Just curious - what kind of profiles are you using? I have a "Screen off" that's 350min and 700max. I figure that's fast enough f someone calls me.
I've read many times undervolting isn't worth it.
Hungry Man said:
Just curious - what kind of profiles are you using? I have a "Screen off" that's 350min and 700max. I figure that's fast enough f someone calls me.
Click to expand...
Click to collapse
I'm using the following with SetCPU: default (1350MHz-350MHz), charging, CPU temp > 64, and battery < 35%.
If you're using a kernel and governor that support hotplug, then you likely don't want to use a screen off profile. The combination of the two can tend to cause sleep-of-death or hot boots.
I Am Marino said:
I've read many times undervolting isn't worth it.
Click to expand...
Click to collapse
Most people don't want to spend the time to do it right.
I'm actually not used to the new kernels. I haven't messed with my eris in about a year and back them there was "smartass, on demand, performance," and some other one that clocked down instead of up
Can you explain th escreen off profile causing issues? I don't even know what hotplug is lol I've been out of Android for a long time.
Hungry Man said:
Can you explain th escreen off profile causing issues? I don't even know what hotplug is lol I've been out of Android for a long time.
Click to expand...
Click to collapse
Hotplug disables one of the CPU cores when the screen is off. Some governors, like hotplugx, will also attempt to disable a CPU core during periods of low CPU usage. For some reason, this combined with a screen off profile can cause some problems. I assume it's because of the "screen-off-max-freq" that Imoseyon mentions in the quote below.
Personally, I prefer the interactivex governor with leankernel by Imoseyon. From his kernel thread:
With interactiveX V2 (for gnexus), things are a bit different, since gnexus has built-in support for screen-off-max-freq for all its governors. I took the new interactive code in gnexus, added early_suspend support (screen off/on trigger), and then added logic to the code so the governor uses the phone's built-in hotplugging capability to turn off cpu1 when screen is off (and then turn it back on when screen comes back on). Cpu1 goes offline entirely - no idle, no sleep.
Click to expand...
Click to collapse
I think undervolting helps - my phone is running 728 - 1228 using the interactive governor, with voltages of 600 mV, 700 mV, and 800 mV (728 MHz, 1036 MHz, 1228 MHz respectively) and I haven't had any issues so far. I know there are some reports that say undervolting doesn't help much, but those are when people undervolt by like 50 mV, whereas here I'm going like 400 mV under lol. (Yes, smart reflex is off).
Thanks Cilraaz. Good to know.
So turning the screen-off profile could improve things? Honestly, my system does fine at 350mhz with screen off. Turning a core entirely off would probably help though.
If I use hotplugx governor that would disable one core when the screens off, right?
Hungry Man said:
If I use hotplugx governor that would disable one core when the screens off, right?
Click to expand...
Click to collapse
Hotplugx will disable a core when the screen is off or when there is low system load. Depending on your kernel/governor choice, other governors may do it also. On leankernel, for instance, interactivex will disable a core when the screen is off, but not on low system load.
Ok, thank you.
I haven't done any comparisons of before/ after since I undervolted/ underclocked first thing. But I was browsing for hours while listening to music while talking to a friend with GTalk. talked for about 1.5 hours with someone, Left it on overnight (10 hours), woke up, used it to talk (voice to text) to someone via GTalk, and it's 3:25PM right now and I still have a fair amount of battery life left.
I'd heard mixed things about the battery on this so I'm happy.
My voltages:
1650: 1300
1520: 1250
1350: 1175:
1200: 1125
920: 1000
700: 925
350: 900
I stress tested each one without a crash.
Is there a way to monitor how much power each frequency uses during screen on and screen off? I have my phone underclocked and caped at 96-192 mhz when the screen is off and 96 - 1512 mhz screen on. I'd like to see if using the 96 mhz is actually worth it power wise. I'm trying to find the best screen off profile without the wake super lag I experience with capping the screen off at 96 mhz. I'm using kt747 kernel and the Ktoonservative governor.
Sent from my SPH-L710 using xda app-developers app
https://play.google.com/store/apps/...251bGwsMSwxLDEsImNvbS5idmFsb3Nlay5jcHVzcHkiXQ..
There's Better Battery Stats, it'll give you the CPU usage (frequencies) along with kernel and other usage.