Re: [ROM][AOSP][9/7][JB] Bugless Beast VZW Galaxy Nexus
My battery life is atrocious since going to 9/7 with their kernel. 16% drain in less than an hr with full signal (4g) previous version I used from July was much better.
If this doesn't improve and I go back to Franco I am flashing the Pink Unicorn.
It can take a few days to see real battery life after flashing. Just flashing backing up and flashing the new version will suck your battery down. That process is CPU intensive, the screen is always on and you don't have the bits in the OS helping to improve battery life because it's not loaded. Once the flash is complete it can take a few charge cycles for things to settle down. The type of drain you are seeing doesn't surprise me. Give it a day and see if you see an improvement.
how long have you been on BB? my first day was a quick one in terms of battery life, and it has gotten a bit better, but I'm still interested in trying a different kernel. With that said, can anyone point me to some sort of general kernel FAQ or something? I get the basics of it all, but am lost when trying to decide/decipher the cpu/gpu speeds and whatnot.
Sent from my Galaxy Nexus using Android Central Forums
This is a pretty good explanation
How to Get Better Battery Life and Performance on Your Android Phone with a New Kernel
What you are talking about with the CPU and GPU speeds is basically governors and over/underclocking.
GPU: is the graphics processing unit. Dedicated CPU to push pixels, basically. In the case of the GNex, there seem to be two speeds, 384MHz, default, and 512MHz. I'm sure there are other speed options out there but those are the most popular that I've seen.
Like any type of overclocking, your specific phone MAY not be able to handle 512 well. You also aren't going to see higher battery drain on 512MHz vs 384MHz, for obvious reasons. I'm not one to dwell on battery life. I don't believe that i should sacrifice a phone's features or speed just to get an hour or so more battery life in a day. But, I don't run 512Mhz because it does seem to kill the battery pretty fast and aside from gaming, which I don't do the phone, there doesn't seem to be any real benefit to me so I just stick with 384MHz.
CPU: With the CPU and kernels it gets more complicated. Most custom kernels will support some over/under clocking but the max and min varies for a number of reasons. There are also cpu "steps". This is the speeds that the CPU increments up and down at, like the steps on stairs and includes the various voltages that each of those steps operates at. Generally speaking, I don't screw with those. I don't even overclock. The way I look at it, someone smarter than me set that all up and thinks it's right, and I don't know enough to disagree, so I just leave it at the defaults.
Governors: How the kernel spins up and down. Meaning, when and what happens to make it go up the "steps" and then back down. This is pretty complicated. There are about a doz different governors out there and most are based on other ones and there are new ones that pop up every few months, some stick around, others fizzle out. I don't focus too much on the names because honestly, their implementation between kernels can be different anyway.
Generally speaking, considering what I've said above, I like Franco's 384MHz, running on his balanced profile which runs at 1228MHz on the CPU and uses the Interactive governor.
Now, with all that said, I don't use a custom kernel for all the stuff above, really. I use it because a good kernel dev merges in drivers and changes from a ton of different sources (like the new WiFi drives in r251) and implements kernel features that aren't in stock (Color and sound hacks are two of my favorites in Franco's).
Hope that helps a bit! Mostly I just felt like babbling for a bit
Facebook
Twitter
Instagram