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

Root [KERNEL] Franco Kernel Discussion (r68)

I'm not really sure. My first instinct would be no because I know faux kernel isn't compatible with cm11. I'm actually caught in a limbo state because I want to run cm11 for voice+, but my kernel of choice doesn't work with it. First world problems :rolleyes:
 
Why aren't any custom kernels compatible with CM anymore? I mean CM has a great kernel stock but what gives?
 
p-bOt said:
Why aren't any custom kernels compatible with CM anymore? I mean CM has a great kernel stock but what gives?
Click to expand...

I've wanted to know the official reason as well, but searches come up empty and asking just results in flaming on xda.
 
Kinda sucks. Franco kernel "plus" works with CM11 on the nexus 4 but Idk if the developer is going to support the N5 or not. Hope so
 
p-bOt said:
Why aren't any custom kernels compatible with CM anymore? I mean CM has a great kernel stock but what gives?
Click to expand...

They no longer use a purely AOSP base for the ROM.

They now use a CAF (Qualcomm's open source) base and kernels based on AOSP won't work. The timing of this change depends on the device, but occurred within the last year

CAF is less optimized than the AOSP code built specifically for our device.

p-bOt said:
Kinda sucks. Franco kernel "plus" works with CM11 on the nexus 4 but Idk if the developer is going to support the N5 or not. Hope so
Click to expand...

Its cm inc's decision that makes other kernels not compatible

Some devs don't want to maintain multiple kernels just because one (rather large) dev group went off and did their own thing. On a nexus device it doesn't really make sense to switch to a less optimized base. On non-nexus devices it isnt AS big of a deal, but when we already have optimized AOSP available its a step backwards if you ask me.
 
p-bOt said:
So...(at the risk of offending someone) Cyanogenmod is a "step backwards" in your opinion?
Click to expand...

Not at all :). The rom itself is a very popular ROM with some great additions to stock AOSP. I ran it quite a bit on my S3.

IMO (this is all my opinion) moving to a CAF base on a nexus device when we already have fully available source was a bad decision. It fragmented the nexus ROMs/kernels into CAF or AOSP, with seemingly no good reason for doing so.

Its not as big of deal on non nexus devices because they don't have AOSP support, so every "aosp" ROM is based on cyanogenmods caf base. Therefore no fragmentation.

I've never seen CMs reasoning for this decision.
 
I see. Well I happen to like it but I dot know much of the facts haha. I don't have as much as time as I did back in the GNex days haha. Thank you for your knowledge though.
 
Gave their newest nightly a try but my superuser permissions were all screwy. Back to cataclysm for me. Hope the dev pushes out 4.2.2 soon
 
I only use CM for Voice+, do you know of another rom that would be compatible with Franco or Faux besides CM that uses their Voice+ code?
 
p-bOt said:
What is voice+?
Click to expand...

Voice+ is an app with some framework modifications that allow one to send/receive Google Voice texts using the Google Voice number itself in any messaging app you want. If you've never used the Google Voice app for texting, let me just tell you it's atrocious as far as organization goes. Using a standard messaging app fixes this.
 
jhawkkw said:
I only use CM for Voice+, do you know of another rom that would be compatible with Franco or Faux besides CM that uses their Voice+ code?
Click to expand...

Is voice+ closed source? They've got IP to protect now that they went incorporated.


I've only seen it on cm
 
franciscofranco said:
Pushed r21:

* Added KEXEC MultiRom patch
* Severe improvements to interactive to make it more intelligent during high CPU load for long periods of time
* Merged a series of patches from upstream to improve the kernel threads management per each cpu
* Improved the hotplug driver algorithm
* Merged two patches from showp to decrease the minimum brightness values

Have fun!
Click to expand...

happy flashing:D
 
Could you explain in better detail what the KEXEC patch is? I read up on it in XDA but didn't quite understand lol.
 
How do you get the speaker boost settings to remain after phone is shut off OR do they need to be reset each time phone is charged.. The fast USB charge seems to stick...
 
4ubest said:
How do you get the speaker boost settings to remain after phone is shut off OR do they need to be reset each time phone is charged.. The fast USB charge seems to stick...
Click to expand...

If you long press the setting, a box comes up with a description and a "set on boot" check box. I think checking that box will do it.
 
You must log in or register to reply here.
Back
Top Bottom