• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[Verizon] [KERNEL][4.0.4] LeanKernel 3.10.0 (7/2)

Yeh, I downloaded the stable last night and went to bed.
I know it should settle in a day or so but.........

Running it as delivered the battery was @67% and 9.5 hours later it was @58%.

WiFi on, one Gmail account syncing browser, calendar, contacts, & mail.
Four email accounts syncing, 2 every 30 minutes and 2 every hour, 3 email notifications came in over night.
I live in a 3G area but LTE is always toggled on.

SSo all that at just under 1 % per hr is not bad for a 1st run with no gov tweaks. Eh?
 
The real test, in my opinion, is the "screen on" battery drain.

I agree, all of that for under 1% an hour is damn good, but how is it treating you when your screen is on?
 
elmerjr128 said:
The real test, in my opinion, is the "screen on" battery drain.

I agree, all of that for under 1% an hour is damn good, but how is it treating you when your screen is on?
Click to expand...


Just put in a 2100mAh battery @100% and setting my time out for 10 minutes.
We will see.
 
elmerjr128 said:
The real test, in my opinion, is the "screen on" battery drain.

I agree, all of that for under 1% an hour is damn good, but how is it treating you when your screen is on?
Click to expand...

You will never see a difference in screen on battery drain from one kernel to the next. The screen is by far the biggest power drain on the phone and kernels do not change how much current is drawn to power the screen. Now, there may be a difference in screen on time if you run different governors regarding how it ramps up to max frequency, what the max frequency is, and what the voltage is at that frequency, but that has nothing to do with the screen.

Ideally, the best way to test kernel battery life would be to keep the cpu at a relatively high frequency and keep it from going to sleep with the screen off and compare results. Maybe set the min frequency to 700 and play stored music on a continuous loop to keep the processor awake at the lowest volume setting so the speaker won't affect your current draw. All that with screen off of course. That will give you an idea of the difference from kernel to kernel with the screen not having any affect. 20-30 minutes of screen on time difference and variances in ambient lighting conditions will make a huge difference in results when comparing from one kernel to the next.
 
svt_gEEk said:
You will never see a difference in screen on battery drain from one kernel to the next. The screen is by far the biggest power drain on the phone and kernels do not change how much current is drawn to power the screen. Now, there may be a difference in screen on time if you run different governors regarding how it ramps up to max frequency, what the max frequency is, and what the voltage is at that frequency, but that has nothing to do with the screen.

Ideally, the best way to test kernel battery life would be to keep the cpu at a relatively high frequency and keep it from going to sleep with the screen off and compare results. Maybe set the min frequency to 700 and play stored music on a continuous loop to keep the processor awake at the lowest volume setting so the speaker won't affect your current draw. All that with screen off of course. That will give you an idea of the difference from kernel to kernel with the screen not having any affect. 20-30 minutes of screen on time difference and variances in ambient lighting conditions will make a huge difference in results when comparing from one kernel to the next.
Click to expand...

Actually for me, and others, screen-on drain does vary from kernel to kernel. And quite considerably.
 
svt_gEEk said:
You will never see a difference in screen on battery drain from one kernel to the next. The screen is by far the biggest power drain on the phone and kernels do not change how much current is drawn to power the screen. Now, there may be a difference in screen on time if you run different governors regarding how it ramps up to max frequency, what the max frequency is, and what the voltage is at that frequency, but that has nothing to do with the screen.

Ideally, the best way to test kernel battery life would be to keep the cpu at a relatively high frequency and keep it from going to sleep with the screen off and compare results. Maybe set the min frequency to 700 and play stored music on a continuous loop to keep the processor awake at the lowest volume setting so the speaker won't affect your current draw. All that with screen off of course. That will give you an idea of the difference from kernel to kernel with the screen not having any affect. 20-30 minutes of screen on time difference and variances in ambient lighting conditions will make a huge difference in results when comparing from one kernel to the next.
Click to expand...


I beg to differ. As jbdan stated, I, and many others, have seen considerable gains in "screen on" time from one kernel to the next.
 
Or, if you just do the same thing as you do with all the other kernels or builds and compare, then do the math.
 
I'm not saying you won't notice a difference in screen on time from one kernel to the next. Just it shouldn't be because of the current draw from the screen.
 
45f7ec4e-3376-8ec6.jpg
45f7ec4e-3386-9f6e.jpg

Not a very high screen on time, but it wasn't intentional, just was busy doing other things.
 
v2.0.0 doesn't seem ready for prime time, IMO. Dev didn't test it at all with LV on any freq slot and there's people reporting issues of weak haptic feedback (mostly fixed with reboot), no sound and random reboots. I myself couldn't get any sound to work, even after changing all voltages back to stock and changing the governor.
 
PhilosoRaptor said:
v2.0.0 doesn't seem ready for prime time, IMO. Dev didn't test it at all with LV on any freq slot and there's people reporting issues of weak haptic feedback (mostly fixed with reboot), no sound and random reboots. I myself couldn't get any sound to work, even after changing all voltages back to stock and changing the governor.
Click to expand...

Thx for the feedback. I give new kernel releases a day out in the masses to see exactly the kinds of things you stated.
 
jbdan said:
Thx for the feedback. I give new kernel releases a day out in the masses to see exactly the kinds of things you stated.
Click to expand...

No prob. Some people are reporting things working fine after a reboot, but I rebooted 3 times after upping the voltages to stock and couldn't get sound to work. I have had 0 issues with all previous versions of Leankernel (started using them at around v1.4.0 I believe). You shouldn't have to reboot to fix issues after installing a kernel. That would lead me to believe that the issue could re-surface at any time under normal usage.

Just posting my experience as that's what forums are for, eh? ;)
 
PhilosoRaptor said:
No prob. Some people are reporting things working fine after a reboot, but I rebooted 3 times after upping the voltages to stock and couldn't get sound to work. I have had 0 issues with all previous versions of Leankernel (started using them at around v1.4.0 I believe). You shouldn't have to reboot to fix issues after installing a kernel. That would lead me to believe that the issue could re-surface at any time under normal usage.

Just posting my experience as that's what forums are for, eh? ;)
Click to expand...

Much appreciated!
 
Mercy! I loaded 2.0.0 last night, it seemed very responsive and smooth. I did have to re-boot to get the haptic feedback back to normal and again just for good measure.

On interactivex, 1200/350, 2100mAh battery.
I put it down at 1:30 AM @ 41%.
Picked it up @ 7:28am @ 40% !!!
1% in 6hrs?
 
gapi said:
Mercy! I loaded 2.0.0 last night, it seemed very responsive and smooth. I did have to re-boot to get the haptic feedback back to normal and again just for good measure.

On interactivex, 1200/350, 2100mAh battery.
I put it down at 1:30 AM @ 41%.
Picked it up @ 7:28am @ 40% !!!
1% in 6hrs?
Click to expand...

Wow, that's impressive. Let us know if that kind of battery life continues for you, and what kind of battery drain you get with the screen on.
 
It's been updated to 2.0.1 to fix some of the previously mentioned issues. Running fine on stock 4.0.4 ROM and radios. Will give it a few days to settle.

I had flashed 2.0.0 and the only issue I had with it was when my alarm went off this morning the dismiss/snooze pop up was missing so I couldn't stop the alarm. Had to pull the battery. The wife was less than pleased. LOL.
 
Mr. Orange 645 said:
It's been updated to 2.0.1 to fix some of the previously mentioned issues. Running fine on stock 4.0.4 ROM and radios. Will give it a few days to settle.

I had flashed 2.0.0 and the only issue I had with it was when my alarm went off this morning the dismiss/snooze pop up was missing so I couldn't stop the alarm. Had to pull the battery. The wife was less than pleased. LOL.
Click to expand...

Hahaha that sounds disastrous.

Let us know how 2.0.1 works out for you. I may just have to give it a shot. Lean 1.6.6 exp3 worked great for me.
 
Went to 2.0.1 last night and ran it kind of hard today. I played a pool game at least 30 minutes but it does not show in the list. Plenty od navigation. A GPS dashboard running. Five minute screen time outs, phone calls........... 2100 mAh battery.

I'll also note this kernel in 2.0.0 was is crazy good when sleeping. I'll try this one tonight.


battery_21712.png
 
You must log in or register to reply here.
Back
Top Bottom