* 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
__________________ All the Thanks!, go to Him <))><
Last edited by jbdan; June 4th, 2012 at 10:54 PM.
The Following 11 Users Say Thank You to jbdan For This Useful Post:
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
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:
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 O.o
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.
__________________
You should follow me on Twitter.
If you're looking for good cloud storage, you should check out Minus! 10GB free (compared to 2GB with Dropbox) and they have Windows, Mac, Linux, Android, and iOS applications
The Following User Says Thank You to TheRoosevelt For This Useful Post:
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 O.o
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?
The Following User Says Thank You to jbdan For This Useful Post:
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.
The Following User Says Thank You to TheRoosevelt For This Useful Post:
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!
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.
The Following User Says Thank You to PhilosoRaptor For This Useful Post:
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 =)
The Following 2 Users Say Thank You to jbdan For This Useful Post:
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.
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:
Is this better them what you get with lean kernal?
It is an interesting thing. On imoseyons 1.6.6 exp4 it is about equal battery life to franco13.1 while on 4G only.
On WIFI, franco 13.1 owned everything I've tried to this date. I've never in the last month been able to get close to 3hrs "screen on" time whether on 4G or WIFI. I got 4 in the WIFI test above.
The battery drain while "screen on" is considerably more efficient on franco 13.1. Sleep/idle states between the 2 kernels is comparable.
The Following User Says Thank You to jbdan For This Useful Post:
Gonna flash this now. Got some prep work to do first with Jakes script. Do you use setcpu on this?
Yes I use setCPU to set the min frequency to 350MHz and set on boot so it sticks. 13.1 comes stock with min freq set to 700MHz. That is the ONLY thing I adjust.
To make sure you don't get any abnormal results, be sure you flash fauxs reset kernel first to set ramdisk back to stock. Also reset all your setCPU data (any voltage tweaks you've made and any set on boot tweaks you have made). In other words start from scratch so you don't get anything "left over" from your previous settings. Then flash 13.1
I like to clear data in setCPU then uninstall it, the re-install once new kernel is flashed, but that's just me. I don't believe it should be required.
The Following User Says Thank You to jbdan For This Useful Post:
Looking pretty good so far. I signed out of gtalk and things improved dramatically.
Yeah I'll be curious what you think after some time with it keep me updated. I think the kernel is excellent and have really hammered it today. I'm almost at 3 days on it, it's one of the best overall kernels I've used on the GN.
Planning my next test kernel to be GLaDOS this week. It really looks interesting and I've heard good stuff about the new Wheatley governor.
I've never signed out of gtalk with any kernel. Could it really get better if I try that? Are you saying that is part of the AndroidOS keep awake dealio? I'll try it
Last edited by jbdan; January 23rd, 2012 at 09:52 PM.
Device(s): S3, Galaxy Nexus(wifi), TB(backup), DI(wife), Eris (love that thing)
Carrier: Not Provided
Thanks: 336
Thanked 484 Times in 358 Posts
Adrynalyne was talking about it today on irc. He believes gtalk and google+ are issues with wake lock, but not the only issues. He doesn't believe it's kernel related either. Someone with a new nexus tried it and his battery drain stopped, so I did it as well. A little too early to tell for sure but it does look like the rapid loss has subsided. I'd be curious to know if it helps you at all.
I'll keep you posted on the kernel too. I am liking it a lot so far, no issues whatsoever and pretty snappy.
The Following User Says Thank You to bjanow For This Useful Post:
Device(s): S3, Galaxy Nexus(wifi), TB(backup), DI(wife), Eris (love that thing)
Carrier: Not Provided
Thanks: 336
Thanked 484 Times in 358 Posts
Weird thing happened with this kernel last night. Everything during the day was running swimmingly and then I plugged it in at night. I started listening to some music and the phone started getting warm. Figured ah no big deal, checked temp in was around 92. Screen off still listening.. getting warmer.. 95, then 98 then 102 and finally 105. Turned off the music.. same thing. Flashed back to Imo and it immediately cooled down.
Is this an issue with this kernel or was this an aberration. As it now stands I'm on stock kernel since flashing aokp 20 this morning but I'm a little gun shy about going back now. Any idea as to what happened?
Weird thing happened with this kernel last night. Everything during the day was running swimmingly and then I plugged it in at night. I started listening to some music and the phone started getting warm. Figured ah no big deal, checked temp in was around 92. Screen off still listening.. getting warmer.. 95, then 98 then 102 and finally 105. Turned off the music.. same thing. Flashed back to Imo and it immediately cooled down.
Is this an issue with this kernel or was this an aberration. As it now stands I'm on stock kernel since flashing aokp 20 this morning but I'm a little gun shy about going back now. Any idea as to what happened?
No clue. I stream music via Google music all the time with it and never had it get warm. Matter of fact nav'd with it yesterday along with streaming music and it ran cooler than past kernels (that is when I really feel the heat). Not a nagging issue I haven't seen anyone with that same complaint. Each kernel though as you well know is different on each phone so....
Last edited by jbdan; January 24th, 2012 at 09:53 AM.
Now that I think about it bj, did you go into setCPU, manually move the slider for min freq to 700MHz then back to 350MHz and then check "set on boot"? I noticed since the kernel comes default min freq at 700MHz you have to do this in setCPU to get it to stick for future boots and just for future use. Maybe that is what happened?
You could easily check this....in setCPU go to INFO tab then go to "Time In State" to check it out
I too have had issues with my phone getting warm to hot when using this kernel. In fact, on the latest version, it sent my phone into bootloops.
This is the second time I've tried this kernel and did all the normal stuff like wipe cache and dalivik cache etc.
That said, I will not use his kernel anymore and am sticking with Imo's where I have no issues. I saw another guy on Rootzwiki the other day saying the same thing happened to him with this kernel, weird. But all phones and chips are not identical.
The Following User Says Thank You to Trooper For This Useful Post:
I too have had issues with my phone getting warm to hot when using this kernel. In fact, on the latest version, it sent my phone into bootloops.
This is the second time I've tried this kernel and did all the normal stuff like wipe cache and dalivik cache etc.
That said, I will not use his kernel anymore and am sticking with Imo's where I have no issues. I saw another guy on Rootzwiki the other day saying the same thing happened to him with this kernel, weird. But all phones and chips are not identical.
Totally understand. I've seen people say they get bootloops on kernel xxx it all just depends on your experience, your setup, and/or your flashing methods
Device(s): S3, Galaxy Nexus(wifi), TB(backup), DI(wife), Eris (love that thing)
Carrier: Not Provided
Thanks: 336
Thanked 484 Times in 358 Posts
Yeah I had done that. Perhaps it was the charger? But no, as soon as I flashed back to Imo the phone cooled down. I'll have to reflash it now that I upgraded to 20. The kernel reset puts it back to stock, right? (just in case) Oh well, flashing now. And the thing is it was fine all day. I'm going to stream some music now too just to see. bbiab
The Following User Says Thank You to bjanow For This Useful Post:
Yeah I had done that. Perhaps it was the charger? But no, as soon as I flashed back to Imo the phone cooled down. I'll have to reflash it now that I upgraded to 20. The kernel reset puts it back to stock, right? (just in case) Oh well, flashing now. And the thing is it was fine all day. I'm going to stream some music now too just to see. bbiab
Are you using a different charger? Perhaps.
Yeah the reset kernel puts back to stock.
gl! report back!
The Following User Says Thank You to jbdan For This Useful Post:
Device(s): S3, Galaxy Nexus(wifi), TB(backup), DI(wife), Eris (love that thing)
Carrier: Not Provided
Thanks: 336
Thanked 484 Times in 358 Posts
Well happy to report none of those issues any longer, for now at least. Heavy use, music, at 92deg, just music at 86. Fully charged now going to test out the battery now that I have all that google stuff disabled. Only difference is that I'm on a USB charge now and not the wall charger. I'll bring that down and try that out later, but I don't suspect that should make a difference since it's the same one I've been using since I bought the phone.
Oh heck, I'll get it now and do the same test.
Edit: It looks fine. Holding at 88 deg. Glad it was a false alarm. Thanks jbdan.
Last edited by bjanow; January 24th, 2012 at 12:06 PM.
The Following User Says Thank You to bjanow For This Useful Post:
Totally understand. I've seen people say they get bootloops on kernel xxx it all just depends on your experience, your setup, and/or your flashing methods
But Im not a noob. Lol.
The Following User Says Thank You to Trooper For This Useful Post:
Device(s): S3, Galaxy Nexus(wifi), TB(backup), DI(wife), Eris (love that thing)
Carrier: Not Provided
Thanks: 336
Thanked 484 Times in 358 Posts
I saw that on the kernel updater this morning and flashed immediately. It's looking pretty sweet right about now. I went with the 700/1200 defaults, conserv gov. But I cheat and OC to 1350 when plugged in only. Noticeable difference when browsing forums but prob not worth it on batt.
The Following User Says Thank You to bjanow For This Useful Post:
I saw that on the kernel updater this morning and flashed immediately. It's looking pretty sweet right about now. I went with the 700/1200 defaults, conserv gov. But I cheat and OC to 1350 when plugged in only. Noticeable difference when browsing forums but prob not worth it on batt.
So, I'm curious here and am testing some things out, what are all your settings (his app, hotplugging, frequencies, gov, etc..) atm on 14.2? Thanks
Interesting. Something is up, not in a bad way, but for the version to go from 14, 14.1, 14.2, now 14.3 in 3 days....
13.1 has the best 'screen on' battery drain I've ever seen from any kernel and the 'screen off' drain is also excellent.
I only got to test 14.1 for 24+ hrs and while it is definitely snappier than 13.1 and the 'screen off drain' equal to 13.1, the 'screen on' drain is not as efficient.
Have you tried 14.3 yet? The base is updated to 3.0.18 wonder what new features it includes
1Likes
[KERNEL][4.0.4] Franco M4 & Nightlies (6/5)
