Flashed Codenameandroid and flashed lean kernel but not impressed with battery life

[bsmith0731]

Suggestions? Just want something that gives me better battery life? can that be found on this rom and kernel? do i need to change more settings?

Just not having much luck.

thinking about going a new route, but dont know where to start?

 

[Creed]

I don't recall, does Codename have a power saving setting? AOKP has one and it basically turns of data and syncing when the screen is off but still checks for emails and other stuff you sync every 30 minutes (or any user defined time). It basically saves you battery without affecting your usage at all.

Also, if you are using leankernal use interactiveX as your governor as it uses hotplug which essentially turns off one of your cores when the screen is off, also saving a ton battery with only minimal lag when turning on your phone.

In my opinion the best battery life comes from franco kernal - here is a quick comparison. http://attachments.xda-developers.com/attachment.php?attachmentid=844333&d=1325825469
Combined with the likes of AOKP, RootzBoat, or Revolution ROM great battery is very close. If features aren't your thing than bugless beast can also be a great battery saver thanks to the lean code it uses.

My 2¢.

 

[bsmith0731]

Also, if you are using leankernal use interactiveX as your governor as it uses hotplug which essentially turns off one of your cores when the screen is off, also saving a ton battery with only minimal lag when turning on your phone.

Thanks for your help.

I dont see anything listed for power options.

Not sure how to use a governor??

Sent from my GalaxyNexus using DroidForums

 

[Creed]

Download No Frills and set the setting called 'governor' to InteractiveX.

 

[bsmith0731]

Download No Frills and set the setting called 'governor' to InteractiveX.
http://qrcode.kaywa.com/img.php?s=8...details?id=it.sineo.android.noFrillsCPU&hl=en

Do I change the maximum or minimum apply at boot??

What about the I/o scheduler deadline??

Sent from my GalaxyNexus using DroidForums

 

[Creed]

Don't change either of those settings, go to the pull down menu called "Governor Performance" and select InteractiveX or Hotplug. If neither of those are available conservative is your best bet for battery life.

 

[bsmith0731]

Don't change either of those settings, go to the pull down menu called "Governor Performance" and select InteractiveX or Hotplug. If neither of those are available conservative is your best bet for battery life.

OK I will try that. Thanks Creed

Sent from my GalaxyNexus using DroidForums

 

[Creed]

Not a problem, good luck! Remember, do not select the set on boot setting until you know it won't cause crashes. I recommend a week or so of regular use before setting on boot as one bad mishap here could put you in boot loop. Fixable but not worth the trouble.

 

[BayouFlyFisher]

[FONT=&quot]As noted in a lot threads on a lot of forums, there are some phones that have a problem with the Android OS and the "Keep Awake" time. There seems to be an issue with some phones not truly going to sleep when the power button is used to turn off the screen as opposed to letting the screen turn off automatically when the screen times out. This results in a very high time in the Settings/Battery/Android OS/Keep Awake menu.

In stock form and with every rom that I have installed, my "Keep Awake" time was always about 50-60% of my total battery time. If the phone had been off charger for 8 hours, I'd have 4-6 hours of Andorid OS "Keep Awake" time. This was true even if the phone had been in my pocket unused and seems to be exacerbated by my habit of turning the screen off manually with the power button every single time. I used to never let the screen timeout.

There seems to be two "fixes" according to Franco (of kernel fame). One concerns the camera. Seems the camera is started and then turned off during startup. But in so doing, it leaves a sensor active and this prevents the phone from actually going to sleep. So he recommends starting and using the back button to go back to the home screen. The other is DRM Protected Content. He recommends this be disabled or frozen. A third, that I don't believe I recall seeing him recommend but that I have seen on his thread at XDA (down for blackout right now) is to disable Maps.

I have done all three of those and my Keep Awake time has gone from 40-50% of my total battery time down to a few percentage points. I mean if I don't use my phone it will now show less than a minute of Keep Awake time per hour.

Good luck
[/FONT]

 

[syndicate0017]

Thanks for the tips Bayou. While I don't think disabling maps is a feasible solution for some, I'm going to give it a shot. If I need maps, I'll just defrost it.

Sent from my Galaxy Nexus using Tapatalk

 

[BayouFlyFisher]

Thanks for the tips Bayou. While I don't think disabling maps is a feasible solution for some, I'm going to give it a shot. If I need maps, I'll just defrost it.

Sent from my Galaxy Nexus using Tapatalk

Agree about the maps issue - that one's not for everyone.

 

[syndicate0017]

Wow...freezing maps has made a HUGE difference in keep awake time. I haven't even been using my phone and Android OS has dropped 8%. I had already frozen DRM content, but it didn't make the difference this step has made.

 

[MrKleen]

You shouldn't have to do anything special to get good battery life out of your phone with Codename (or any of the roms for that matter)... Maybe reinstall after doing a thorough wipe and see if helps.

Have you tried the Franco kernel? Not that it's meant for battery saving or anything, but my phone runs nice and smooth with it.

 

[orion2001]

I'm still on the stock 4.0.2 ROM because it has been working flawlessly and I've managed to get great battery life with my phone, comparable to the best results on XDA from others on VZW. I've also noticed that in general, battery life seems to take a bit of a hit with a lot of ROMs due to some of the extra performance stuff, or newness of the ROMs.

Here are the things I've done that have helped me with battery life:

1) Undervolt Processor using SetCPU and custom Kernel: Rooted and installed the Jame Bond Kernel 1.35GHz. It does a mild OC on the GPU and enables 1.35GHz and also allows undervolting via SetCPU. I keep my phone at max of 1.2GHz as I really don't need the extra speed. Dropped the voltage for each clock speed systematically till I found the stable volts at 350MHz, and higher. If you go too low, your phone will reboot when stressed and then you can go back and push up the mV a little bit. Also make sure you don't set the voltages to be applied on Boot as that can result in bootloops if you go too low with your settings.

Keep in mind, that I chose this kernel specifically because it doesn't do any other fancy tweaks/fixes. It just enables undervolting and overclocking. This is good for a baseline. I will eventually try one of the fancier kernels like Franco's, but it would be good to first test with something close to stock. The only reason I used this kernel over stock is because there is a lot of power savings to be had by undervolting the processor.

2) Turn off softkey sounds : Using Better Battery Stats, I noticed that Audio_out or something named like that, was causing a huge amount of partial wakelocks (i.e., preventing the phone from going into deepsleep). After googling the issue, I came across a thread on xda where someone else had the same issue and was able to fix it by turning off softkey sounds when they are pressed. This worked for me.

3) Monitor Apps and Processes : Using Better Battery Stats, CPU Spy and Battery Stats Widget, I kept a close eye on any run away processes in my first week, as I tested the battery every night. CPU spy should ideally report 80-90% Deep Sleep if you are not using your phone. Look at the Battery settings screen in ICS to make sure your phone wasn't awake intermittently while you left it off the charger overnight. If it was, try to figure out what processes are waking your phone up and consuming power.

4) Stay with stock (apps and ROMs) if you can (for now): I think it is good to stay with stock and establish a baseline for your battery life and phone performance. This is really useful when you switch to other ROMs and Kernels and you'll be able to tell if they are working better or worse for you. For example, I noticed that with one of the updates for NOVA Launcher, my batterylife got a lot worse, but none of my monitoring apps were pointing towards it being the culprit. I uninstalled it and went back to the stock launcher, and everything went back to the way it should be. Not trying to blame NovaLauncher (I think it is great), but just that it makes sense to take things slow, and build a baseline with your base setup before you go mucking with other apps and ROMs.

5) Always stay on Wifi if you can: Staying connected to Wifi provides better standby power consumption numbers v/s being on 3G or 4G (worst).

I prefer not having to use things like JuiceDefender, etc, to turn off Data as it seems to negate the point of a smartphone. I've found that my GN has excellent standby battery life and I can easily go 30+ hours with normal use without the need to charge. At home, I'm usually always on my home Wifi, and my battery drain is around 1-1.3% per hour. It can go lower if I set it to airplane mode overnight.

This is with Stock 4.0.2, and the Jame Bond kernel, and an undervolted CPU.

PS - I prefer not to use custom power profiles in SetCPU. I've noticed that ICS does a great job with the interactive governor at handling things. Some of the devs on xda have mentioned that the custom profiles can cause more harm than good as they can interfere in the phone being able to go into deep sleep. I haven't tested this, but I certainly haven't seen anything untoward from not using custom power profiles.

PPS - Once things are working well, Android System, and Screen will be your biggest power hogs. The former is an ongoing issue with ICS (though it really doesn't drain a whole lot considering the 1% drain per hour in standby that I am observing...it might just be related to a different way of reporting power consumption in ICS). Screen does eat up power, and at best, I can get 4 hours of screen time with my stock battery.

 

[bsmith0731]

Thanks for your help everyone. I haven't given this set up much time to try out. So ill try it out and comment back.

Sent from my GalaxyNexus using DroidForums