[KERNEL][GPL][N4] franco.Kernel - r217

[franciscofranco]

I was actually pretty stupid and should've coded a small check to see if the user was on stock colors or not. I'll do that for sure, was on my to-do list yesterday, but I came home and dropped "dead" in my bed

 

[kabauterman]

I was actually pretty stupid and should've coded a small check to see if the user was on stock colors or not. I'll do that for sure, was on my to-do list yesterday, but I came home and dropped "dead" in my bed

this would be just great! :victory:

thanks a lot man, that how It should be.

franco.kernel ftw!

 

[mjehan]

First of all thank you Franco for your work. Your kernel has really improved my stand-by and screen-on time.

Regarding further developement I had some questions/suggestion:
1) How about setting the maximum CPU speed to 584 Mhz while screen is off to reduce the affect of the wakelocks?
2) Underclocking the CPU & GPU (like Apple does) so that the speed is 80% of the rated speed -> for lesser drain when the device is in use
3) Changing CPU governor to Ondemand and I/O Scheduler to Sio
4) Allow Under-volting (like all other kernels) to allow lower speeds -> the consensus is the N4 can handle up to 150mV undervolting
5) Instead of disabling Power HAL and mpdecision, tunining them so that the CPU switching and speed control is much smarter

Please do consider these points

Tip: I have got rid of some CPU peaks by turning off USB debugging, forcing GPU rendering and turn off reporting & logcat in Franco's app

 

[DesolateEgo]

First of all thank you Franco for your work. Your kernel has really improved my stand-by and screen-on time.

Regarding further developement I had some questions/suggestion:
1) How about setting the maximum CPU speed to 584 Mhz while screen is off to reduce the affect of the wakelocks?
2) Underclocking the CPU & GPU (like Apple does) so that the speed is 80% of the rated speed -> for lesser drain when the device is in use
3) Changing CPU governor to Ondemand and I/O Scheduler to Sio
4) Allow Under-volting (like all other kernels) to allow lower speeds -> the consensus is the N4 can handle up to 150mV undervolting
5) Instead of disabling Power HAL and mpdecision, tunining them so that the CPU switching and speed control is much smarter

Please do consider these points

Tip: I have got rid of some CPU peaks by turning off USB debugging, forcing GPU rendering and turn off reporting & logcat in Franco's app

Try searching first!

 

[SupWiz17]

No its not just trinity. A quick work around is to flash the stock reset .zip in fauxs thread then flash a kernel of your choice. This is assuming your on the stock ROM.

Sent from my Nexus 4 using xda premium

Ok I will look for that file. On custom Roms I usually just find it easier to reflash the custom ROM

Sent from my Nexus 7 using Tapatalk 2

 

[CaspaTheGhost]

Settings?!

Sent from my Nexus 4 using xda app-developers app

All stock as Franco intended and I'm running CM10 Jellybro nightly. Everything on as it should be on a smartphone, but WiFi at home and office would have contributed to the great times.

Wondering what it will be like after some more charging cycles!

Sent from my Nexus 4

 

[trailblazerz11]

Kind of new to Nexus so wanted to know if the kernel img includes and replaces recovery?
i.e. if I fastboot flash the kernel will my recovery change from stock? or im guessing it is separate? ( recovery only changes if I fastboot flash a recover img)

came from i9000, recovery included in initramfs. wanted to make sure

 

[albundy2010]

Flashing a kernel with fastboot has no effect at all on recovery.

 

[Dr Zoidberg]

Kind of new to Nexus so wanted to know if the kernel img includes and replaces recovery?
i.e. if I fastboot flash the kernel will my recovery change from stock? or im guessing it is separate? ( recovery only changes if I fastboot flash a recover img)

came from i9000, recovery included in initramfs. wanted to make sure

I have been a long time user of cwm, but I'm now using TWRP and very happy with the results. Install goo.im from the Play store and choose "install custom recovery script". Subsequent installations of ROMs or kernels won't affect the installation of TWRP.

Sent from my Nexus 4 using xda premium

 

[albundy2010]

First of all thank you Franco for your work. Your kernel has really improved my stand-by and screen-on time.

Regarding further developement I had some questions/suggestion:
1) How about setting the maximum CPU speed to 584 Mhz while screen is off to reduce the affect of the wakelocks?
2) Underclocking the CPU & GPU (like Apple does) so that the speed is 80% of the rated speed -> for lesser drain when the device is in use
3) Changing CPU governor to Ondemand and I/O Scheduler to Sio
4) Allow Under-volting (like all other kernels) to allow lower speeds -> the consensus is the N4 can handle up to 150mV undervolting
5) Instead of disabling Power HAL and mpdecision, tunining them so that the CPU switching and speed control is much smarter

Please do consider these points

Tip: I have got rid of some CPU peaks by turning off USB debugging, forcing GPU rendering and turn off reporting & logcat in Franco's app

1. A wake lock will not bump up the frequency high in the first place. Just goes from deep sleep to the lowest clock almost all the time. And if it is a wake lock that actually needs computing power you want it to clock up and complete the task faster anyway.

2. You can under clock yourself.

3. Change to on demand yourself. I/0 add it yourself

4. Franco has already mentioned many times where he a stands on UV. Lowering voltage doesn't have a thing to do with speeds either. And not all kernels allow users to tamper with the voltage either.

5. You can't tune something that is closed source propriety .

Franco knows what he is doing.

 

[thunderinacircle]

Great!

I've been a long time custom kernel user, using Franco, Trinity, GladOS, LeanKernel etc on my Galaxy Nexus over the past year or so. Custom kernels on the GNex, especially pre jelly bean, really seemed to help in both performance and battery life. Despite this knowledge and experience, I was hesitant to move to a custom kernel on my Nexus 4 since the phone was so unbelievably smooth out of the box. Ultimately I succumbed to the urge to tinker once again in an effort to improve my battery life.

Boy am I glad I did! The battery life I'm getting on R15 is great. I've seen a few posts alluding to occasional stutters on this kernel that were not present on the stock kernel, but I sure have not noticed that myself. I feel this provides all the performance of the stock kernel with the added benefit of almost doubling my on-screen time and also dramatically reducing my standby battery performance. (no wakelocks either, not that those are kernel related anyway)

Anyway, today's battery stats: All stock settings, 10.5 hours on battery, 2 hours screen on time, about 45 minutes of screen off music streaming and still at 60% battery. This is almost all on cellular too, only about 1 hr on WIFI.

Thanks Franco! Keep up the good work.

 

[drose6102]

For everyone having Franco kernel updater app showing toast notifications every time you turn the screen on.

Open SuperSU and click on Franco kernel app

Click enabled or global default to the right of notifications and you can disable toast notifications.

You won't see them anymore from Franco kernel updater.... Ever


Sent from my Nexus 4 using Tapatalk 2

 

[AnthonyAldrete]

Does this kernel play nice with stock Roms ?

Sent from my Nexus 4 using xda premium

 

[trailblazerz11]

Was gonna try and stay stock everything for awhile but I couldn't stand that the min frequency was 1000 even when idle.
Very happy I flashed Franco now, no change in performance butter smooth and better battery

Sent from my Nexus 4 using Tapatalk 2

 

[a5ehren]

Does this kernel play nice with stock Roms ?

Sent from my Nexus 4 using xda premium

Yes.

 

[Locksmith81]

I agree with the first 2 sentences, but I think the rest is disrespectful I just wish users read a bit, nothing more!

Maybe a search function built into the kernel

Sent from my Nexus 4 using xda premium

 

[bilago]

Hey, so I was directed to try this thread here for my issue... I cannot get wifi tethering to work at all, it starts but says AP failed and the SSID is not broadcasting. Is this a kernel issue?

 

[ssauger]

Hey, so I was directed to try this thread here for my issue... I cannot get wifi tethering to work at all, it starts but says AP failed and the SSID is not broadcasting. Is this a kernel issue?

You posted in CM thread, right? I am also on CM with this kernel and i got no error when i enable wifiAP.

 

[bilago]

You posted in CM thread, right? I am also on CM with this kernel and i got no error when i enable wifiAP.

Yes, I posted in the CM thread. I'm using the latest CM nightly and the latest Franco Kernel... are you using the default wifi tethering settings or did you change them?

 

[franciscofranco]

r16:
* More interactive patches from Google
* Deep kernel config cleaning, removing lots of useless qualcomm options
* Make the kernel thermal driver a little bit more aggressive
* Hotplug driver behaviour - less hotplug calls, using 2 cores when user is interacting with the screen (less hotplug calls = better battery life because calling that function is very taxative for the device); online the second core when user turns on the screen to maximize user experience