-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
[Verizon] [ROM][4.0.4] AOKP ICS B40/M6/Mods (7/8)
- Thread starter jbdan
- Start date
-
- Tags
- galaxy nexus
ryancmatchett
Android Expert
So i did another test today. On M2, Lean 1.6.6. Turned the wifi off at mid day, only 3g on all day. Here are a couple of screenshots:
Gotta be honest, not liking this result at all. However, if you look, my mobile signal which has been 3g all day is better than my 4g has been, but to have less than 12hrs on the phone...and its below the 20% mark....this is a REALLY light use day. No games no browser not much of anything. Really disappointed. Gonna go back to wifi and 4g tomorrow as I actually got way better life....in fact as I am writing this on the phandroid app I have just watched my battery go down to 9%....jeez
Gotta be honest, not liking this result at all. However, if you look, my mobile signal which has been 3g all day is better than my 4g has been, but to have less than 12hrs on the phone...and its below the 20% mark....this is a REALLY light use day. No games no browser not much of anything. Really disappointed. Gonna go back to wifi and 4g tomorrow as I actually got way better life....in fact as I am writing this on the phandroid app I have just watched my battery go down to 9%....jeez
BabyBlues
Trouble Just Finds Me!
So i did another test today. On M2, Lean 1.6.6. Turned the wifi off at mid day, only 3g on all day. Here are a couple of screenshots:
Gotta be honest, not liking this result at all. However, if you look, my mobile signal which has been 3g all day is better than my 4g has been, but to have less than 12hrs on the phone...and its below the 20% mark....this is a REALLY light use day. No games no browser not much of anything. Really disappointed. Gonna go back to wifi and 4g tomorrow as I actually got way better life....in fact as I am writing this on the phandroid app I have just watched my battery go down to 9%....jeez
Phandroid is a known battery hog.
andoird213
Android Expert
TheRoosevelt
Android Expert
That's just a safeguard so that, if the settings turn out to be unstable on your phone and cause a restart, when you reboot you'll have your previous settings, not the unstable ones
I'm about to go from 1.2.0 to 1.6.6 exp 230, I'll report back
I flashed from M2 to 19 yesterday and I have to say, it was well worth the flash. The amount of features and the smoothness on this ROM is amazing.
andoird213
Android Expert
I'm trying this out all. I'm gonna be out ALL day tomorrow so it'll be a good day one test. Keep y'all updated.
andoird213
Android Expert
I know this doesn't mean much but if its any indication, I was just browsing through pics for 10 min straight screen on time I lost 3% battery (imo's 1.2.1). I lost 15% in 5 on 1.6.6.
jbdan
Extreme Android User
How much screen on time did you have at the time of that screen shot? Next time include that I'm curious. I've never tested 3G as 4G is up and running everywhere I go in Atlanta so far. So spark my memory for me...you're using 1.6.6 stable, InteractiveX gov with no voltage tweaks, and no over/under clocking right?
What Teddy said
gl! I've been on 1.6.6exp4 hotplug gov no undervolt & stock MHz for 12 hrs and it is just about matching battery life of that 1.2.1 setup, maybe slightly better. This is my first time trying the hotplug governer (edit: for an extended time), & as far as responsiveness it seems a little more snappy overall than InteractiveX.
I really like 1.6.6exp4 so far. The hotplug gov, for me, is very stable at stock MHz's and mV's
jbdan
Extreme Android User
I'll be interested in your results after using it for some time. It is funny how one kernel can rock for one person and bonk for the other
It's all about trial and error and what works best on our phone. Every phone is different which is so wild!
jbdan
Extreme Android User
I also forgot to add, those voltages I posted are quite conservative by some standards. I've seen some people using crazy low voltages and are still stable. That's why you should never "set on boot" till you know you are safe
TheRoosevelt
Android Expert
I tried using hotplug for a couple days, but I was getting some lockscreen lag, both in imo's kernel and franco. I don't have any such issues with interactiveX
jbdan
Extreme Android User
on 1.6.6exp4? I tried it on previous kernels but didn't use it past a couple minutes...reason being is exactly what you said. I have had none of it on hotplug 1.6.6exp4 350MHz min today.
I've also been experimenting with auto-brightness and lockscreen lag. Been very interesting and telling so far. Try to reproduce that same lockscreen lag, but first set your brightness to a static level and see if you get it then.
ryancmatchett
Android Expert
Correct with no tweaks. Next time I will get the screen time.
Btw thanks for all the responses jbdan...seems this test was not to my liking!!!
jbdan
Extreme Android User
So screen on time was roughly 44 minutes. You're right those results aren't that good, but I must say your AndroidOS times look mint. Really good! You also have some really nice plateaus in your graph so it looks like it is sleeping nicely. You also have some big dips you hit it hard on those. Your cell signal is much better than mine I barely have a hint of green if I'm around the house all day.
What I like to gauge is screen on time. It shows your screen is on, and that means you're on the device using it in some way, most often. If you can pull close to 3 hours of screen on time in a lets say a 12-15 hour charge cycle you're doing really good imo.
There are soooooooo many other variables it's so hard to discern and easy to get caught up in this battery life thing. I should know
To test these kernels and battery life consistently you really have to have the same usage from charge to charge : same wifi usage, same amount of voice calls, screen on time, run same apps, sms the same, email the same, be in the same location as the day before aka cell signal etc...near impossible to do right!
elmerjr128
Android Enthusiast
Here's an update to my test from Wednesday night (in which I forgot to turn on Auto-sync):
Unplugged from charger at 10:05pm Thursday night, screenshots taken at 6:21am Friday morning.
Not sure exactly what that big span of Awake time is, but it doesn't seem to have hurt my battery too much.
This was using imo's 1.6.6 exp 230 (min 230, max 920) with InteractiveX governor. I tried the hotplug for a few hours, and BetterBatteryStats showed an enormous drain coming from vbus_tuna_otg. Switched back to InteractiveX and it looks like my battery thanked me for it.
I'd like to try out 1.2.1 since so many others seem to have had great results.
In any case, I'm pleased with my battery life!
Unplugged from charger at 10:05pm Thursday night, screenshots taken at 6:21am Friday morning.
Not sure exactly what that big span of Awake time is, but it doesn't seem to have hurt my battery too much.
This was using imo's 1.6.6 exp 230 (min 230, max 920) with InteractiveX governor. I tried the hotplug for a few hours, and BetterBatteryStats showed an enormous drain coming from vbus_tuna_otg. Switched back to InteractiveX and it looks like my battery thanked me for it.
I'd like to try out 1.2.1 since so many others seem to have had great results.
In any case, I'm pleased with my battery life!
elmerjr128
Android Enthusiast
My phone is running great (no FCs, freezes, reboots, etc.) on 1.6.6 experimental 230 with 230min and 920max, InteractiveX governor. I'm thinking I will "set on boot" in another day or so just to be safe.
Those stats are looking good, BB!
Those stats are looking good, BB!
elmerjr128
Android Enthusiast
Question - Are you guys setting the UV/governor in the ROM Control > Performance settings AND SetCPU? Just ROM? Just SetCPU?
BabyBlues
Trouble Just Finds Me!
Just setCPU for me
jbdan
Extreme Android User
Exactly how the battery should drain imo under non-usage. Great results looks like you've found your kernel and settings (until your addictions force you to the next flash right
)Great charge there BB's if that was your first run with the settings I'll bet it even gets a little better with your next charge cycle. You could always bump down the mV's by 25mV on each frequency if you wanted to live dangerously
jbdan
Extreme Android User
Just setCPU for me too!
BabyBlues
Trouble Just Finds Me!
Great charge there BB's if that was your first run with the settings I'll bet it even gets a little better with your next charge cycle. You could always bump down the mV's by 25mV on each frequency if you wanted to live dangerously
Hmmmm. Maybe I'll see how it goes on one more full charge then try living dangerously. Noob question for ya - what exactly am I changing?
jbdan
Extreme Android User
Hmmmm. Maybe I'll see how it goes on one more full charge then try living dangerously. Noob question for ya - what exactly am I changing?
Under VOL TAG column in setCPU is where you can control the voltage your CPU is getting at the respected MHz's/frequency. You always have a "current" and a "saved".
If you do decide to ever play with this more, the default voltages for imoseyon 1.2.1 are:
1200MHz = 1300mV
920MHz = 1250mV
700MHz = 1150mV
350MHz = 950mV
In case you ever want to reset your saved values to the kernel default.
To give you a base to see how these kernels are already UV'd otb, the stock kernel (what comes built in to AOKP 19) from ICS voltages are:
1200MHz = 1380mV
920MHz = 1317mV
700MHz = 1203mV
350MHz = 1025mV
I know some people say that they don't UV and it's not worth it. I say bullocks
jbdan
Extreme Android User
So if you used those settings I posted earlier BB's (the ones Patriot was trying), then you'd drop the 1200MHz down to 1225mV, the 920MHz down to 1175mV and so on. Test before setting on boot and so on.
You can also try the Interactive governor at some point, and really lower the mV's as it has much more leeway with undervolting than IAX does.
Just something else to pass the time and be obsessive about
You can also try the Interactive governor at some point, and really lower the mV's as it has much more leeway with undervolting than IAX does.
Just something else to pass the time and be obsessive about