[Verizon] [KERNEL][4.0.4] Franco M4 & Nightlies (6/5)

[jbdan]

Kernel developer Francisco Franco

Kernel link

M4 changelog:

Spoiler

* Added 192Mhz slot
* Reverted all previous OMAP4 patches forked from Texas Instruments to fix most of the bugs coming from them
* Interactive governor patches from android-omap-3.0
* Screen_off_max_freq re-enabled and available here: /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq
* Lowmemorykiller driver updated to 3.4 version
* Fix for random mac id address for some users - from Imoseyon
* Special compiler flags to get some extra bits of performance
* Wi-Fi voltage back to stock to prevent signal issues
* Fix a crash present on stock kernel on i2c remove - patch from TI
* Remove generic_hotplug and Hotplug governor. The device shuts down cpu1 as it see fits so to prevent instabilities what so ever this function is now gone
* Fix to boosted sound when a notification was received - from Ezekeel
* Some OMAP4 patches from android-omap-3.0 for stability purposes
* Kernel 99% cleaned up from warnings that were present on stock kernel for stability purposes
* VDD_MIN voltage back to stock to prevent data loss or any other instability
* Add OMAP GAMMA interface - values range from 1.0 to 2.0 and are to be echoed to this file: /sys/devices/platform/omapdss/manager0/gamma
* Some MUSB patches from mainline kernel to improve battery life calling the correct pm_runtime functions on USB functions
* GPU clock is now 384Mhz by default because it can use the same amount of voltage and the same OPP as the 307Mhz giving us extra performance without taking a battery hit
* Other bunch of smaller patches and fixes that can be seen on my bitbucket repository

 

[jbdan]

Bumped up to #7.1 now. The fastest kernels I've had the pleasure of using. If you flash this please report if you experience any "initial screen wake up slide unlock lag". Link in OP

 

[jbdan]

After using Lou's kernel for 2 days (it's nice and stable solid battery life) I jumped ship to this yesterday. I'm UV'ing and noticed a 2% drop last night (in my testing condition of WIFI while sleeping) over 7 hours. Equaled that of imo's 1.1.0 UV'd and lovely idle battery life! And the gravy on top is this kernel is so fast.

My voltages, and I feel like a safe moderate UV (although it is phone dependent so do not "set on boot" until you're stable after tinkering for a day), are:

1200MHz = 1175mV
920MHz = 1050mV
700MHz = 975mV
350MHz = 850mV

Stock voltages in case:

1200MHZ = 1380mV
920MHz = 1317mV
700MHz = 1203mV
350MHz = 1025mV

 

[TheRoosevelt]

I'm going to try this. Last night over around 7 hours my battery dropped from 100 to 75% with data off. That was UVed and with imo's kernel. I looked at battery stats and Android OS was consuming 86%, whatever that means

I'll report back with this kernel. In his xda thread, franco said the battery drain may be something to do with the camera sensor being kept on after boot.

 

[jbdan]

I'm going to try this. Last night over around 7 hours my battery dropped from 100 to 75% with data off. That was UVed and with imo's kernel. I looked at battery stats and Android OS was consuming 86%, whatever that means

I'll report back with this kernel. In his xda thread, franco said the battery drain may be something to do with the camera sensor being kept on after boot.

Yeah the google+ and camera issue keeping phone awake was definitely something that worked for me early on in .3 roms. However, it does seem with these latest iteration .3 roms the wake issue, on my end at least, has been somewhat remedied. idk what I've done differently besides flashing the latest version of a .3 ROM

My battery, during the 1st 3 days with the GN (unrooted and locked) had that same "lose ~20% overnight while doing nothing".

Try leaving data on (wifi if you're at home) overnight. Wipe your batt stats (charge with power off till 100% then boot into recovery and go to advanced> wipe battery stats then reboot and unplug). Give it a good 48 hours for the kernel to settle and see accurate results.

Are your awake times at night blue/high?

 

[TheRoosevelt]

Yeah the google+ and camera issue keeping phone awake was definitely something that worked for me early on in .3 roms. However, it does seem with these latest iteration .3 roms the wake issue, on my end at least, has been somewhat remedied. idk what I've done differently besides flashing the latest version of a .3 ROM

My battery, during the 1st 3 days with the GN (unrooted and locked) had that same "lose ~20% overnight while doing nothing".

Try leaving data on (wifi if you're at home) overnight. Wipe your batt stats (charge with power off till 100% then boot into recovery and go to advanced> wipe battery stats then reboot and unplug). Give it a good 48 hours for the kernel to settle and see accurate results.

Are your awake times at night blue/high?

Unfortunately, I didn't take a screenshot, and I rebooted to flash the kernel, so I lost the graph from last night

I'll do what you said about wiping the battery stats, and report back.

As for the kernel itself, it's impossibly fast. I don't know how it got even faster than it already was. Your UV settings have worked fine for me since yesterday. No lock screen lag either.

 

[jbdan]

Unfortunately, I didn't take a screenshot, and I rebooted to flash the kernel, so I lost the graph from last night

I'll do what you said about wiping the battery stats, and report back.

As for the kernel itself, it's impossibly fast. I don't know how it got even faster than it already was. Your UV settings have worked fine for me since yesterday. No lock screen lag either.

Thanks for reporting I'm not getting the screen unlock lag I've seen in previous builds either. Looking good so far. And yes it is super snappy!

 

[jbdan]

#8 nightly now up for grabs updated OP click link for changelog!

 

[jbdan]

#9 available OP updated

 

[TheRoosevelt]

9.2 is up

I'm gonna switch back to this. My battery life hasn't been as good after flashing Lean 1.3.0.

 

[jbdan]

Thx will update OP. I'm sticking to 1.2.0. When I find gold I hold on to it.
Let me know how 9.2 does

 

[jbdan]

Updated to #10

 

[jbdan]

Updated to #12

 

[dabomb224]

Updated to #12

Any recommendations for a pure stock 4.0.3 ROM that plays nice with this kernel?

 

[WormDoes]

Any recommendations for a pure stock 4.0.3 ROM that plays nice with this kernel?

I'd check out Bugless Beast by Peter Alfonso or Redemption ROM by OhHeyIt'sLou. They're both stock 4.0.3 based with minimal customization's

 

[jbdan]

Upped to #13

 

[Crashumbc]

What do you have to wipe when flashing a kernel ?

Just the davlik? or do you have to do a full wipe/re-load like with most ROMS?

 

[PhilosoRaptor]

What do you have to wipe when flashing a kernel ?

Just the davlik? or do you have to do a full wipe/re-load like with most ROMS?

Just wipe the Davlik cache. You shouldn't ever have to do a full wipe to change the kernel. But it's still wise to do a full backup before flashing or at least have the .zip of the previous (known good) kernal available to revert back to in case the new one doesn't boot for whatever reason.

 

[jbdan]

What do you have to wipe when flashing a kernel ?

Just the davlik? or do you have to do a full wipe/re-load like with most ROMS?

I like to wipe just dalvik for any new kernel flash. Some don't wipe anything at all and have no issues. So my advice is to wipe dalvik, flash kernel, enjoy =)

 

[jbdan]

I haven't given this kernel a chance since #10 a couple weeks ago. Previous versions have had a nagging issue (for me).....screen turn on time/wake up lag. In other words from the time you pushed the power button till when the screen came on was delayed, and then, when you go to immediately swipe to unlock and it has been delayed as well.

Well the unlock delay has been 100% fixed (for me) and the screen on delay minimized so much that it doesn't bother me anymore.

I've been running imo's kernels so long now I was ready to try something new. Franco 13.1 comes out-of-the-box undervolted pretty aggressively, minimum CPU frequency set to 700MHz (I set mine to 350MHz), and the default governor is the conservative governor. He's modified the threshold settings (ADV ANC in setCPU) and it's really impressive in my first 22 hours with it. I like to test for 48hrs so testing will continue, but this is what I saw on my first charge using my phone like I normally would sans voice calls:

AOKP #19 franco kernel #13.1
1850mAh standard battery
WIFI on 18.5 hrs 4G on 3.7 hrs
Screen on auto-brightness
15 min of voice calls (not normal I usually talk much more)
2 email accounts push notify
Weather updating every hour
Sync'ing browser, google+, contacts, calender, music
3 widgets on 3 screens (android weather, calender, music)
Cell signal at home is -105dbm to -115dbm. While on 4G it was around -90dbm
The only change I made in setCPU was lower min freq to 350MHz

That "Time w/o a Signal" was while I slept, the darker yellow in the graph. Sometimes I get this sometimes I don't.

If you want to try this kernel and are coming from any of imo's I suggest flashing faux's reset kernel (the one compatible with your build either 4.0.3 or 4.0.2) then rebooting to homescreen. Once there reboot into recovery and flash 13.1. Wipe dalvik before each kernel flash.

 

[Trooper]

Hey man,

Where can I find this reset kernel you speak of?

Thanks!

 

[JustNexus]

Hey man,

Where can I find this reset kernel you speak of?

Thanks!

This. Man you get so much better battery life on wifi then lte. Do you get better battery on this than leankernal?

 

[jbdan]

Hey man,

Where can I find this reset kernel you speak of?

Thanks!

You can get it here it works very well!

 

[jbdan]

This. Man you get so much better battery life on wifi then lte. Do you get better battery on this than leankernal?

Definitely better on wifi than LTE. I'll do LTE test this week

 

[jbdan]

And here is LTE only results after 1st charge with 13.1. Considerably less than the above wifi test, but still almost 3 hours screen on time. Everything else from the first test remains just about the same so pretty consistent with the WIFI test.

I forgot to take this screen shot and had plugged it in at 6% so that's why it's at 7% in this ss: