I can't figure out how I can combine cm10.2 m1 snapshot for Google nexus 4 with Franco kernel. I tried to update it with the Franco kernel paid version because I bought it. when it flashes r193 the screen goes all glitchy with weird colors as if everything was inverted. I tried the colorfix they posted somewhere for it. but then I got stuck in a bootloop on the Google logo. restored it back to cm10.2 m1 snapshot.
is there any way to let cm10.2 m1 snapshot work with any Franco kernel so that I can use my wonderfull color profile? I don't want to use the built in one. and I love Franco 's kernels
hope to hear from you guys soon
Depends on whether CM is based on the JSS or JWR release.
Franco has 2 versions available, so try the other one and see if it works any better.
Related
All suggestions welcome
most of the ones found in DEV area seems to be specific to the original Samsung ROM
there's:
Semaphore for JVT
TalonDEV 0.5.1-RC1 for Samsung GBs
Glitch V12 beta 3 (is for CM7 and MUIU but it doesn't look appealing to me)
MIDNIGHT-0.7.6 (i like this the most but is not for CM7)
GALAXIAN for JVT
I want a CM7 + UV Kernel to save battery
I use platypus, the best IMO.
There is also fugumod.
Glitch. Superosr would be my first choice but he chooses not to release kernel separately.
Hello.I am using MIUI 1.10.21 (2.3.7) at 1.2Ghz with UV
i'm testing the glitch v12 beta 3 kernel since yesterday...(the LL Version) and it seems stable
I have used the platypus r17-18 for 2 weeks and no problem with stability
both have similar features
There are 3 that you can use all of them I believe are UV compatible..
fugumod
neo\platypus
glitch
I think the stock CM7.1 kernel also does UV.
Stock with Franco:
Will it work? Will it give the same benefits as CM 10.1?
Will OTA work? If I sideload OTA will I have to reflash kernel?
CM 10.1:
If I flash new ROM/update ROM, will kernel stay?
Thanks,
Yes the kernel will work. The kernel and rom in CM10.1 is obviously different to stock and francos so im not sure how they compare - try both yourself ?
Im not sure about OTA. I would just flash a AOSP stock ROM every time there is an update just in case if you want to stay on stock.
If you flash a new ROM no the kernel will not stay you have to flash the kernel again as CM10.1 (like most ROMs) comes with its own kernel that will overwrite your current one.
I've been wanting to ask this about faux's kernel since I'm having the (very common) msm_hsic_host wakelock issue. Since we're on the subject: does anyone have a suggestion for the most stable, closest to stock, AOSP ROM?
Hi all,
I'm testing the CM10.2 nighties on my Razr M from two weeks. Everything seems stable but I want to try it with the SmartassV2 governor that the CM kernel is missing. I started searching for alternative kernels (like Aaaagh's one) and I noticed that the actual CM10.2 kernel is v.3.0.96: wasn't Android 4.3 supposed to have the 3.4.62 version instead? If so, why Cyanogemod is stuck with th old 3.0.96 version? I've searched for answers but I've find none...
Is it possible that every CM10.2 build has the old kernel, or is this happening only with the Razr M build?
Maybe I'm just missing somenthing...
j27h said:
Hi all,
I'm testing the CM10.2 nighties on my Razr M from two weeks. Everything seems stable but I want to try it with the SmartassV2 governor that the CM kernel is missing. I started searching for alternative kernels (like Aaaagh's one) and I noticed that the actual CM10.2 kernel is v.3.0.96: wasn't Android 4.3 supposed to have the 3.4.62 version instead? If so, why Cyanogemod is stuck with th old 3.0.96 version? I've searched for answers but I've find none...
Is it possible that every CM10.2 build has the old kernel, or is this happening only with the Razr M build?
Maybe I'm just missing somenthing...
Click to expand...
Click to collapse
3.4 kernel for MSM8960 isn't quite available yet.
Hopefully Moto will update to 3.4 if we ever receive official 4.2 (or 4.3)
You can contribute and follow the progress (dev wise) at http://forum.xda-developers.com/showthread.php?t=2243410 and http://www.droidrzr.com/index.php/t...lopment-0610-android-booting-firmware-issues/
Ok, everything isclear now! Thanks for the quick response!
Basically we've two options:
1) use the 3.0 kernel with backported 3.4 funcions (the one integrated in the CM builds)
2) use a 3.4 kernel (like Aaaargh's or others) non totally adapted to our device
And all this because we're still stuck with Android 4.1.2 thanks to Motorola/Google/Verizon...
At this point, I think te safest thing is to keep using the 3.0 kernel... Apart for the new governors/schedulers, why soul I prefer a 3.4 kernel (maybe this is a silly question too...)? Are they usable/stable even if they're not exactly matching our device?
Hello everyone, I know that the latest AOSP branch of 4.3 is r-3.1 (JLS36G). My question is, is there a current kernel, faux or Franco, available that has color calibration and is compatible with JLS36G? I'm currently using CM10.2 and would love to have the same color calibration as PA or Franco.
Threads in this forum are very well labeled, have you done the research and looked at all kernel threads in both sections
I really want to use Stock MIUI, but I want a custom kernel, so I can control temperature and other stuff. And now that Xiaomi released kernel sources I'd thought I'd find a kernel easily here. So if anyone has a kernel with thermal for Stock MIUI on kitkat, please share it