[KERNEL][N5] FrancoKernel - r115 - 2nd November - Stock & Oreo

[lmulli]

Pushed r112 with more security patches!

It says Oreo, I downloaded it from your 8 folder, but it doesn't appear to work alas. Just dumps me back at the bootloader each time. Easily remedied though with a backup though.

 

[Hiyaslalabs]

I will install on my dark ROM but dirty flash. Is procedure to clean cache & dalvik, install ROM, install Magisk then the FK? Thanks! I don't want to have bootloop at this point

 

[tom0769]

Just realized how gigantic this thread really is. This device was absurdely popular and I'm so glad to have been through this journey with you all!

Yeah, look in the mirror and you'll see who's to blame:laugh:

 

[Kusie]

Hello,
FYI: latest two releases of this kernel break EDS encryption app. It force closes immediately after opening. Going back to prior version.
K.

 

[osm0sis]

Hello,
FYI: latest two releases of this kernel break EDS encryption app. It force closes immediately after opening. Going back to prior version.
K.

It's probably due to a security fix, so you should probably instead report it to the app developer with some logs so they can try and work around it.

 

[nleitao]

Obrigado Francisco plo excelente trabalho.

 

[franciscofranco]

It says Oreo, I downloaded it from your 8 folder, but it doesn't appear to work alas. Just dumps me back at the bootloader each time. Easily remedied though with a backup though.

It should work unless the rom your using made changes that need some kind of Kernel support? Dunno really. What I tested worked fine.

I will install on my dark ROM but dirty flash. Is procedure to clean cache & dalvik, install ROM, install Magisk then the FK? Thanks! I don't want to have bootloop at this point

You don't need to wipe caches.

 

[Hiyaslalabs]

Yes I do need to wipe dalvik & cache because I will dirty flash ROM first. Then install Magisk & kernel or whichever comes first? Thanks Dev. I miss using your superb kernel.

 

[L.F.B.]

Just realized how gigantic this thread really is. This device was absurdely popular and I'm so glad to have been through this journey with you all!

This is a really sucesfull project. It will always be!

Its all your fault Master Franco.

You havee created a legion of crazy fans.?

The franco.kernel church folowers...?

 

[aleksb1712]

Lost network on dark rom with the kernel franco r112

 

[franciscofranco]

Yes I do need to wipe dalvik & cache because I will dirty flash ROM first. Then install Magisk & kernel or whichever comes first? Thanks Dev. I miss using your superb kernel.

Wiping those caches is useless for what you're doing.

Lost network on dark rom with the kernel franco r112

FK doesn't touch the network, and with 2353458943754305938 users not once being such thing reported you're probably just using some weird ass rom, either outdated or some crazy ass ****!

 

[dawidececk]

Thanks!

Thanks for this kernel! After broken LG G3 this is my "new" phone. This kernel is one of things why I choose N5.
300-1547MHz
Interactive
-75mV globally
CPU input boost off
2y old battery
RR 5.8.4

 

[Ysfzone]

Thanks for this kernel! After broken LG G3 this is my "new" phone. This kernel is one of things why I choose N5.
300-1547MHz
Interactive
-75mV globally
CPU input boost off
2y old battery
RR 5.8.4

How i can set 75mV globally ?

How i can turn CPU input boost off ?

 

[Arstoien]

How i can set 75mV globally ?

How i can turn CPU input boost off ?

You won't see magical results / improvement just by doing that. You should be able to use Franco's app to UV and change input boost

 

[Paschfire]

How i can set 75mV globally ?

How i can turn CPU input boost off ?

I wouldn't suggest applying the same -75mv UV values until you are sure your Nexus 5 CPU can handle it, this can be done by gradually increase the undervolt value by -5mv over a 12-24hr period until the set value can be determined as stable. -25mv should be an ok starting point but obviously there are no guarantees.

NOTE!! Making sure the UV set-on-boot toggle is disabled within FKMU until the set UV values can be deemed stable, if not you could be setting yourself up for a continuous loop of bootloops everytime the UV values are reapplied after every reboot.

Not all CPUs are created equally as the SoC silicon is rated on a scale of 1~5(slow-nominal-fast-faster-fastest), this 'bin rating' determines the grade quality and performance of the chipset and will also determine what the stock voltage table values will be set to.

For example a CPU with a binning level of 2 will have different base voltage table values compared to a CPU with a binning level of 5.
Even then, when comparing two CPUs with the same binning level as they may have the same stock voltage table values may not be able to handle the same undervolt value changes and doing so could causing erratic performance, bootloops or other issues.

You can determine the CPU bin level by using the following terminal command.

su
dmesg | grep PVS


Undervolting will return very little if anything in regards to battery savings, at most it will only slightly decrease the temperature output of the chipset and this may not even be detectable.
Imho.. It maybe better to just leave the stock voltage values intacted, as undervolting can have a greater possibility of erection performance comparing to what will be minimal in any performance gains.

 

[fun12892]

Is this normal? I set the max frequency to 2265 MHz but it always reverts to 1497 MHz. I couldn't find someone who has the same problem on Nougat on this thread. Or is it a feature?

 

[franciscofranco]

Is this normal? I set the max frequency to 2265 MHz but it always reverts to 1497 MHz. I couldn't find someone who has the same problem on Nougat on this thread. Or is it a feature?

Thermal throttle?

 

[fun12892]

Thermal throttle?

Right. I just checked. Thank you very much.

 

[franciscofranco]

Right. I just checked. Thank you very much.

:highfive:

 

[Paschfire]

Is this normal? I set the max frequency to 2265 MHz but it always reverts to 1497 MHz. I couldn't find someone who has the same problem on Nougat on this thread. Or is it a feature?

Let the device cool down in standby for 5~10mins and recheck, most likely thermal throttle.