Hi. Today I installed the cyanogenmod 10.2 snapshot on my phone and then i installed the latest version of franco kernel r193 JSS. Instead of the normal CM boot animation there was a weird blue screen with glitchy squares. After the device booted all the colors weren't normal (for example the blue turned yellow). Previously I had cm 10.1.3 stable version with franco m3. Is franco incompatible with the latest CM snapshot? Am I doing something wrong?
tzaranu said:
Hi. Today I installed the cyanogenmod 10.2 snapshot on my phone and then i installed the latest version of franco kernel r193 JSS. Instead of the normal CM boot animation there was a weird blue screen with glitchy squares. After the device booted all the colors weren't normal (for example the blue turned yellow). Previously I had cm 10.1.3 stable version with franco m3. Is franco incompatible with the latest CM snapshot? Am I doing something wrong?
Click to expand...
Click to collapse
Much reading in the Q&A thread if you search for "Franco" or the Franco thread if you search for "CM".
tl;dr a CAF kernel commit in the nightlies borked non-CM kernels. There are "fixes" available.
CMNein said:
Much reading in the Q&A thread if you search for "Franco" or the Franco thread if you search for "CM".
tl;dr a CAF kernel commit in the nightlies borked non-CM kernels. There are "fixes" available.
Click to expand...
Click to collapse
Found the fix, thanks.
Related
Hi guys,
Just have a quick question- wondering if anyone is running into the same problem. I just installed Cyanogen 7 rc1, and it is force closing between the load screen and the welcome screen (for the first time).
I'm not sure if this is the correct place to post this, but any help would be great.
Thanks
Based off what I've read in the development threads, the RC does't seem to be too much of an RC. I'd restore and wait.
you have to flash RC1 over a nightly build.
Nowak4G said:
you have to flash RC1 over a nightly build.
Click to expand...
Click to collapse
Yep! Its was a known issue with the first build of RC1. Something was botched. I recommend you either flash RC1 over nightly build #38, or you just flash nightly build #39 (which already includes fixes that were left out of RC1).
Cheers!
I wanna run these two together but when I install Franco it messes up the screen color....
Plz help
robbieast said:
I wanna run these two together but when I install Franco it messes up the screen color....
Plz help
Click to expand...
Click to collapse
youre mistaken, its not franco kernel that messes up your screen color, its your cm10.2 nightly.
cm xhanged its sourse from aosp to qualcomm, so running any asop kernel in cm will give you that effect. only cm based custom kernels will be fine. theres a temporary flashable fix for this floating around, if it still works that is.
robbieast said:
I wanna run these two together but when I install Franco it messes up the screen color....
Plz help
Click to expand...
Click to collapse
Yes lately cm is causing some color problems.
Here is the colorfix zip file flash this in recovery and also use a JSS kernel AFAIK cm needs a JSS kernel'
COLORFIX zip : DOWNLOAD
Press thanks if I helped you.
how about CM11.. is there any colorfix available yet?
i flashed CM10 colorfix for the 4.4.X based CM11 variant but seems it'll restart the session after the boot animation
Are they still going the CAF route? Or is that ending since it mainly had to do with freezes (if I recall) in 4.3?
It's going to affect my decision to go back to 10.1. I really want to have touch2wake on my kernel and these fixes to make faux and franco kernels function are starting to cause issues on 10.2.
AFAIK, these developers will not be supporting CAF =/
Elegant996 said:
Are they still going the CAF route? Or is that ending since it mainly had to do with freezes (if I recall) in 4.3?
It's going to affect my decision to go back to 10.1. I really want to have touch2wake on my kernel and these fixes to make faux and franco kernels function are starting to cause issues on 10.2.
AFAIK, these developers will not be supporting CAF =/
Click to expand...
Click to collapse
freezes on 4.3 was due to bug in aosp jss code, witch have been fixed in 4.3.1. so update to lastest cm.
and in 4.4 they will continue.
Yeah, I'm running the stable release of 10.2 with ziddley's franco kernel and it's causing issues here and there now. I was hoping they were going to revert back to AOSP. I guess I'll revert back to 10.1 to maintain my desired functionality for now.
Elegant996 said:
Yeah, I'm running the stable release of 10.2 with ziddley's franco kernel and it's causing issues here and there now. I was hoping they were going to revert back to AOSP. I guess I'll revert back to 10.1 to maintain my desired functionality for now.
Click to expand...
Click to collapse
ahh u using custom kernel, not cm one.no issue while i was on cm 10.2 with my modified build of franco.kernel
opssemnik said:
ahh u using custom kernel, not cm one.no issue while i was on cm 10.2 with my modified build of franco.kernel
Click to expand...
Click to collapse
Yeah, unless there's some way to get touch2wake working on 10.2; I heard you have gamma settings now with the caf kernel included so I figure I can maintain my color scheme.
Elegant996 said:
Yeah, unless there's some way to get touch2wake working on 10.2; I heard you have gamma settings now with the caf kernel included so I figure I can maintain my color scheme.
Click to expand...
Click to collapse
try with other kernels.
On CM11 and Cm10.2 try these: 1) Modified franco and faux to work on Cm : http://forum.xda-developers.com/showthread.php?t=2487246
2) AK has CM exclusive kernel : http://forum.xda-developers.com/showthread.php?t=2473454
opssemnik said:
ahh u using custom kernel, not cm one.no issue while i was on cm 10.2 with my modified build of franco.kernel
Click to expand...
Click to collapse
You can always follow a tutorial to build your own cm from source code and enable module support. In that way you won't be using custom kernels, everything will be cm 100%.
I am using touchcontrol in that way, and I'm quite happy with the results.
Sent from my Nexus 4 using xda app-developers app
CM11 is great with hells-core. Touch control works, and battery/performance is amazing.
korockinout13 said:
CM11 is great with hells-core. Touch control works, and battery/performance is amazing.
Click to expand...
Click to collapse
I have been trying to find a link for 15 minutes!
Could you provide me with a link?
Thanks!
myweca said:
I have been trying to find a link for 15 minutes!
Could you provide me with a link?
Thanks!
Click to expand...
Click to collapse
Right in the general section: http://forum.xda-developers.com/showthread.php?t=2495373
Didn't see this here, let's go!
Stock CM11s, rooted, running Franco kernel.
PA with stock PA kernel
it has the best touch responsiveness with my glass screen protector on
CM11s +root +franco.kernel
Sent from my awsome OnePlus One using Tapatalk
Waka waka waka waka waka waka. Uuuhm, i mean't Pac-Rom with Franco kernel.
Had some strange issues with PA such as not being able to search a network even after full-wipe.
Mahdi + Franco
Pacman + ak as primary, MIUI as secondary and Flyme OS as second secondary, will add more...
dansou901 said:
Pacman + ak as primary, MIUI as secondary and Flyme OS as second secondary, will add more...
Click to expand...
Click to collapse
Where did you find the Flyme port ?
Link please
Also Mahdi+ Franco(optimised) primary and Mahdi + AK , PA+Franco, DroidKang as secondary.
It's here somewhere: http://forum.xda-developers.com/oneplus-one/general/fly-ui-oneplus-t2865796
Kind of useless without a poll.
Using CM11 nightlies.
Hello!
I use Droidkang 6.1 with Stock Kernel
Stock CM11s - Stock Kernel - Bootloader Unlocked - Unrooted
CM11S with ak on dalvik
Currently on IUNI (really nice ROM but a bit hungry when idle) but about to flash FLYUI for a few days.
What benefits does Franco kernel provide over stock? Doesn't seem to be much info on it. Thanks.
AndroidInsanity said:
What benefits does Franco kernel provide over stock? Doesn't seem to be much info on it. Thanks.
Click to expand...
Click to collapse
We won't discuss this here, or else the thread will be closed by mod. This is only for sharing ones configuration :good:
dansou901 said:
It's here somewhere: http://forum.xda-developers.com/oneplus-one/general/fly-ui-oneplus-t2865796
Click to expand...
Click to collapse
It's not Flyme OS, just a Mod skin CM11 rom.
PA 4.6 Beta 1 + FK r15 with CM11S as a secondary
Liquid Smooth 3.2 with optimized franco Kernel.
really smooth, 7am - 7pm: 100%--> 89%: less usage but this power consumtion is just awesome..
Lugke said:
Liquid Smooth 3.2 with optimized franco Kernel.
really smooth, 7am - 7pm: 100%--> 89%: less usage but this power consumtion is just awesome..
Click to expand...
Click to collapse
Yup me too...liquid smooth and franco
I was using PA Betas with Franco but not happy at all with how some apps interact with android wear so I am going back to CM11s with Franco tonight.
Hi,
I want to see if i can get Franco Kernel on my Nexus 4 running CyanogenMod 12.1. I tried using auto flash on the Franco Kernel app on the app store and it gave me a warning stating it might not work... Any suggestions whether it works or not? I don't want to ruin my phone
I tried this yesterday and my Nexus 4 was stuck in a bootloop after until I reflashed CM 12.1.
In short; no, don't do it.
There is two different types of Rom's and kernels. There is those that are based on AOSP and those who are based on CAF.
You can't mix different types of Rom's and kernels. So to you can't use a AOSP kernel on a CAF Rom and vice verca.
CM is a CAF based Rom and Franco kernel is an AOSP based kernel. So you can't use those together.