Did a search but no dice...
Basically I am struggling to see the benefits, or differences for that matter, between having the official kernel source from HTC vs custom ones the clever devs have produced.
Am I right in thinking that kernel source for ICS has been released for our One S, but not the kernel source for JB yet?
In which case, how come there are custom kernels available for both ICS based ROMs, such as Beastmode Bricked Kernel, and JB based ROMs such as ElementalX kernel? They are both working and functioning, with similar enough features.
Is it just that all the custom ICS Kernels are built up on more stable source code and so have less errors and bugs etc? Whereas the JB Kernels are being built from scratch so it takes longer to overcome errors, and features have to slowly be added in one by one?
I am struggling to see the reason why everyone is so desperate for HTC to release the JB Kernel source code for the One S when the devs have already got us working custom kernels???
Yes, the kernel source for ICS has been released, but not for JB yet.
I dont keep much track of kernels for JB, but most of them are for AOSP roms. The ones for Sense roms can change some things, but most of the settings needs to be applied during installation of the kernel.
Custom kernels offers a lot of custimization. What kind of custimization? Well, changing the CPU Speed and voltage is one of them - which can be used to either increase performance, or increase battery life. They also (in most cases) come with much better governours, which increases both speed and performance (simply put - a governour is what decides when a certain cpu speed is supposed to be used).
And then theres other things, for example sweep2wake, USB OTG with a normal usb cable etc etc.
From my POV, the CPU settings is what appeals to me the most. And back when I used stock ICS it was the USB OTG feature that appealed the most.
If you dont care about any of these things, then theres not much point in a custom kernel.
To summorize in one line: Custom kernels offers a lot more features than a stock kernel.
I understand all the option custom kernels offer, but my real question was; why is there so much need for the official JB source code when there already are JB custom kernels?
And as I said, most of them are for AOSP roms. The ones for Sense roms can change some things, but most of the settings needs to be applied during installation of the kernel.
To clarify: with the source, we can change all the settings within the OS, without the need to reinstall the kernel to change the CPU speed for example.
ahhh I'm following you now I think. So with the official source code there is less need for Aroma installers etc? as all those settings can be edited 'on the go' rather than declared for good at the installation, and remain unchangeable until a new kernel is fastbooted?
Exactly. With a (real) custom kernel, you can for example overclock the CPU when you want to play a game, and when you're done playing, you can change it back. Without the need of a reboot/reinstall.
Also custom kernels for JB Sense ROMs unlock writing to the system folder.
Sent from my HTC One S Special Edition using xda app-developers app
mainly, you cannot produce a custom kernel without the source code. Elemental is actually the stock kernel using initd scripts. You cannot add sweep 2 wake, etc..
HTC_One_S | Xparent_ICS_Blue_Tapatalk_2 1.06_Hboot_Downgrade | unofficial_4.2.1_AOKP_Feb7 | Komodo_Kernel
Related
So I recently rooted my Galaxy Nexus and other than using WidgetLocker I haven't done anything to my phone to take advantage of my root and SU privileges.
This is my first phone that I have done this too so this is all a major learning curve which brings me to my question(s):
(1) Can the phones memory be over locked?
[If yes....] What are the factory Memory Times and what is a safe level to overclock them to - and How?
(2) What is the factory setting for the processor and what is a safe and efficient overclocked setting?
Is the Highest (but again safe and efficient) level a noticeable change?
(3) Overclocking the GPU can reach a maximum setting of 512Mhz (correct?)
What is the default setting for the GPU and is overclocking the GPU to the highest (but "safest" & efficient) level noticeable and worth the trouble?
(4) How do I overclock my phone?
I know that (probably) a kernel replacement is going to be the answer to this question but I was wondering if maybe there is a script I could run in recovery console or terminal, whatever...instead of replacing the entire kernel.
If the kernel is the only way, does this effect future ICS system updates?
What is the best (most stable, most features, best for overclocking) kernel for ICS/GalaxyNexus? - I dont know poop about kernels.
(4a) with the kernel loaded, what apps do I need to snatch from the market to actually overclock my Galaxy Nexus? Try to recommend free ones please =P
(5) Since I am replacing the Kernel, should I dive in 100% and flash a ROM too?
Yes?: what is the best (very very stable, fast, efficient, tweakable) ROM out there for GNexus?
do roms do anything to assist in the overclocking process?
The only reason I would consider a ROM too is because I want Wifi/USB Tethering, Facebook contact syncing, and a few other things.. but only if there are overclocking tools too!
Does flashing a ROM eliminate myself from ICS updates(pretty sure the answer is yes)??
(6) I am currently on a stock kernel and "rom" (if u couldn't tell...) but I am rooted and using Launcher Pro (free version) and I am happy with it but out of the other launchers which is the best (fastest, easy to use, customisable)?
If I flash a custom ROM will a custom launcher be necessary or do they cone with tweaked launchers?
I had other questions but I can't think of it right now, I'll update the OP and thread if I think of anymore. Thank you so much community members for taking time to answer these questions!!!
Sent from my Galaxy Nexus using XDA App
ksaul said:
(1) Can the phones memory be over locked?
[If yes....] What are the factory Memory Times and what is a safe level to overclock them to - and How?
Click to expand...
Click to collapse
No, it can't.
(2) What is the factory setting for the processor and what is a safe and efficient overclocked setting?
Is the Highest (but again safe and efficient) level a noticeable change?
Click to expand...
Click to collapse
1200 MHz is stock, 1350-1400 MHz is the highest you can get at the moment, as stability is an issue.
(3) Overclocking the GPU can reach a maximum setting of 512Mhz (correct?)
What is the default setting for the GPU and is overclocking the GPU to the highest (but "safest" & efficient) level noticeable and worth the trouble?
Click to expand...
Click to collapse
307MHz is stock (underclocked), 387MHz I believe is it's nominal speed, and is billed as 'overclocked' here on XDA.
(4) How do I overclock my phone?
I know that (probably) a kernel replacement is going to be the answer to this question but I was wondering if maybe there is a script I could run in recovery console or terminal, whatever...instead of replacing the entire kernel.
If the kernel is the only way, does this effect future ICS system updates?
What is the best (most stable, most features, best for overclocking) kernel for ICS/GalaxyNexus? - I dont know poop about kernels.
Click to expand...
Click to collapse
You need to flash a kernel using CWM Recovery. The kernel will be rewritten every time you flash a new ROM with that ROMs kernel, if you like a specific kernel you can reflash after installing a ROM, I use Franco Kernel which is by far the most popular. Once you flash a custom ROM you won't bother with ICS system updates, custom are bleeding edge with custom tweaks and months and months earlier than OTA releases.
(4a) with the kernel loaded, what apps do I need to snatch from the market to actually overclock my Galaxy Nexus? Try to recommend free ones please =P
Click to expand...
Click to collapse
SetCPU is by far the best, don't be a cheapskate shell out the $2 for it. AOKP ROM has one built in, but I still use SetCPU.
(5) Since I am replacing the Kernel, should I dive in 100% and flash a ROM too?
Yes?: what is the best (very very stable, fast, efficient, tweakable) ROM out there for GNexus?
do roms do anything to assist in the overclocking process?
The only reason I would consider a ROM too is because I want Wifi/USB Tethering, Facebook contact syncing, and a few other things.. but only if there are overclocking tools too!
Does flashing a ROM eliminate myself from ICS updates(pretty sure the answer is yes)??
Click to expand...
Click to collapse
Flashing a custom ROM will stop you being able to recieve OTA's, yes. But like I said earlier, they are ****. Custom ROMs are far, far better, so just keep up to date with your ROMs releases and you will always have a ROM with more features that stock OTAs. Most ROMS come with overclocked kernels, most have optimized kernels also, AOKP even has a built in overclocking program in the settings menu, which might appeal to you.
(6) I am currently on a stock kernel and "rom" (if u couldn't tell...) but I am rooted and using Launcher Pro (free version) and I am happy with it but out of the other launchers which is the best (fastest, easy to use, customisable)?
If I flash a custom ROM will a custom launcher be necessary or do they cone with tweaked launchers?
Click to expand...
Click to collapse
I don't know about other ROMs but AOKP comes with a custom launcher called Nova Launcher, it's essentially the stock launcher with tweaks.
wow thank you so much for your reply... i stumbled upon AOKP on droidforums before reading your reply and am actually about to flash it now - thank you for this very detailed response!!
No problem my man, there is actually a good few stable 1500MHz kernels out now and the GPU can be overclocked to 512MHz if you really want to kill your battery.
First off, here is the github
https://github.com/pio-masaki/at100-kernel.git
Everything I do for this kernel is done there.
Now that's out of the way, here are some highlights:
Beginning of OC code (yes, an OC ICS kernel)
Added a slew of governors for your choosing
Added a couple i/o schedulers
Slight CFLAG tweaking
This is a work in progress!
If you have issues feel free to report, but this is my first ever kernel project, and it may take some time for me to address them!
Dos and Dont's in this thread:
No flaming, please. If someone asks a question thats been asked before, simply remind them and if you would, link the post or thread containing the answer. Replies like "Use search" don't help at all. Saying "Next time, use the search, the information is here" is of course what I would like to see. XDA will be better for this.
No ETAs! I can not, and will not, make any promises on when I can fix, build, or otherwise even think about this kernel, or any rom, period. Asking for ETAs, even politely, will either go unanswered, or reminded of this note.
Issue reporting: I always welcome issue reports, of course, however keep in mind, the point made above is also covering this, I may not have time to address an issue immediatly, though I will try to post back and acknowledge that I have seen the issue, or to ask further questions. Please include as much information as possible, settings for speed, governor, IO, profiles in use for screen off (which I advise against), cpu control app in use, etc. Dmesg would be nice as well, use pastebin, we don't want to see an 8K line post of a log
Changelog:
Experimental V0.1 10-02-12
First "release" for testing. This is internal build 8, and from this point on, will be labeled and numbered as releases, IE if this does ok, next will be Alpha 1, or experimental V0.2, etc.
Added OC code
Experimental V0.2 10-05.12
Second release for testing. Does now include the CODE for voltage control, but is not enabled yet. I didn't enable it to help prevent issues with instabilities from UV being confused with kernel issues. GPU OC is active, 320/400 MHz 2D/3D. Does not play well with ICS, CM10 use only.
Experimental V0.3 10-06-12
Rewrote alot of the upper end speed/voltage/timing code from 1.508 to 1.472, VT, haptic feedback fix? Proved unstable to the point of being unusable. Pulled.
Stable V0.4 10-06-12 "Caspar"
Reverted to V0.1 OC code after the disaster of V0.3. Left out voltage control code, implemented GPU OC as previous in V0.2, VT is enabled, possible haptic fix (not likely). Governors and IO schedulers should remain as before, min/max settings should remain as before. 1.5 is likely still broken.
Experimental V0.5e "Melchoir" 10-18-12 ICS only
All new CPU Speed tables, overall max is lowered from 1.5 which froze to 1.478, and more speeds in between. Those who used the Shiva Kernel will be familiar with the speed range. GPU OC is bumped up 20mhz in 2D/3D. SmartassV2 code added. The kernel has branched since V0.4 and is now a JB and an ICS specific design, one doesn't work for the other anymore, sorry to say. "Melchoir" is the ICS branch kernel, "Balthesaur" is the JB branch kernel which is included in the CM10/Kuroikaze builds.
"Melchoir" V2.4 ICS
Experimental support of CIFS and slight config changes to maybe improve kernel performance. Branch from "Caspar" and includes speeds, governors, IO schedulers and any previous bugs. 1.5Ghz is likely still broken.
"Balthesaur" V2.75 Linaro JB NON OC
Experimental fixes for ExFat corruption issues.
No CPU or GPU OC
Built with Linaro 4.7 toolchain with some optimizing tags turned on
Retains Governors and IO Schedulers from the OC version
Instructions
Download the zip from the link given below
Boot into CWM
Wipe cache
Wipe dalvik cache
Install from zip
Install the kernel zip
Reboot
First boot will take longer as the caches are being rebuilt
Let kernel settle for 10 minutes
Reboot
Let kernel settle for 5 minutes
Begin normal usage and setting up
System Tuner has been reported to work with great success.
Downloads
Experimental OC 1 | Mirror
*note* 1.5Ghz is unstable, please limit to 1.4Ghz for testing.
Experimental V0.2
*note* 1.5Ghz is unstable, please limit to 1.4Ghz for testing. Only for CM10.
Experimental V0.3
*note* completely unstable, pulled.
Stable V0.4 "Caspar" ICS
*note* 1.5Ghz is unstable, please limit to 1.4Ghz for testing.
Experimental V0.5e "Melchoir" ICS
*note* does not boot. See change log for information. ICS only kernel. Please have V0.4 zip handy in case this kernel goes ballistic or doesn't boot, etc.
Experimental V2.4 "Melchoir" ICS
*note* likely retains the 1.5GHz lockup issue.
Balthesaur V2.75 Linaro No OC JB ONLY
Non OC kernel by request. Built with Linaro and current 2.75 source. For use with Jellybean ROMs only. Retains IO Schedulers and Governors, just no CPU or GPU overclock at all. Possibly includes fixes for exfat corruption (planned for U6, but may as well)
Revert kernel
Favum ICS kernel | Mirror
Use this in CWM, same as before, to restore the boot.img and modules for Favum ICS, it may work for other Official based ICS, may not, untested.
Notes and Updates
Mirrors added, V0.1 initial release
V0.2: GPU OC 320/400 MHz 2D/3D. Does not play well with ICS, use only with CM10.
Kernel naming and what they mean:
As the kernel development for Jellybean gained momentum, changes to the kernel source and drivers made the kernel no longer compatible with BOTH ICS and JB, so a new branch needed to be built, one for each android version.
Caspar = The trunk kernel, the first base which all other kernels are built from, contains the original OC settings, governors and schedulers, but not much else, pretty stock.
Melchoir = The First branch, this is for ICS only, and is slightly more updated then the JB kernel, but not by far, is pretty stale development wise while I work on the JB kernel.
Balthesaur = The second branch, this is for JB only, and is the more updated and recent and heavily developed kernel by far.
Each kernel release is still compatible with ANY ROM, however it MUST be of the proper android version, Meclchoir should be flashed only to ICS and Balthesaur should only be flashed to JB. Caspar, should you choose to use it, is ICS only as well.
Do not flash these to other android versions, including Honey Comb, they may boot but they will certainly not function correctly.
FAQ
Q: How does this work with any ROM?
A: Installs by taking apart the current boot image, replacing the kernel binary, repacking then reflashing the boot image, and copies the matching modules into your system/lib folder. It keeps the existing ramdisk, which is why it works in between both ICS and JB.
Q: Where did you get your source changes from?
A: Source changes are coming from ezTerry and Godmachine, with guidance from Godmachine. Changes by ezTerry may come from other places, however I can not verify that, and its from his github.
Q: Is this included in any ROM?
A: Yes, this kernel is included with my CM10 builds, including Kuroikaze-Thrive
Thanks go out to:
First off, godmachine / linux society! We've had our spats (rather, I've had mine) however his guidance made this possible.
ezTerry: for giving us the first modded Acer Iconia kernels, also basing some of this work on his work on ezT20 kernel.
Da-pharoah for as always encouraging my work and to try new things.
tybar over at thriveforums.org (he may also be here?) for his work on CM10 and supplying the initial source this began with.
The rest of the guys pitching in over there!
Very excited to see a kernel! Could you possibly post a stock kernel as well that can be flashed back to if needed as this gets refined? Just trying to cover all contingencies.
Sent from my AT100 using Tapatalk 2
wigginst said:
Very excited to see a kernel! Could you possibly post a stock kernel as well that can be flashed back to if needed as this gets refined? Just trying to cover all contingencies.
Sent from my AT100 using Tapatalk 2
Click to expand...
Click to collapse
That depends on the ROM being used so no, I hadn't planned on it. I probably could but its per ROM which is quite a few lol
Sent from my Galaxy Nexus using Tapatalk 2
Ok. Was just thinking of a backup in case. Flashed it to favum and letting it settle right now.
Sent from my PG86100 using Tapatalk 2
On jbreezy darkside ROM v2 he modified the ram disk a bit would that interfere with installing this kernel?
Edit: nevermind you said it keeps the existing ram disk
Could you make a revert for his darkside ROM? Sorry for being a pain
Sent from my AT100 using xda app-developers app
stevie13.xo said:
On jbreezy darkside ROM v2 he modified the ram disk a bit would that interfere with installing this kernel?
Edit: nevermind you said it keeps the existing ram disk
Sent from my AT100 using xda app-developers app
Click to expand...
Click to collapse
Yeah unless something is different with the kernel binary as well, which I doubt, it shouldnt cause a problem.
As far as I know its the first kernel from source for ics so I don't think any issues will come up.
Edit: I'll try to get a revert zip up for dark side as well, the favum won't work, different ramdisk I think.
Sent from my Galaxy Nexus using Tapatalk 2
Are u saying I can use this kernel on my phone or some specific phone only?
ramoneC said:
Are u saying I can use this kernel on my phone or some specific phone only?
Click to expand...
Click to collapse
For the device this forum is for? In other words its for the Toshiba thrive 10" tablet. Flashing this on anything else can lead to no boots or even bricks. Its for any ROM, not device.
Sent from my Galaxy Nexus using Tapatalk 2
I nearly was going to brick my phone /: maybe not cos your updater-script might have been aborted but the main thing was I could not download it because of some sqlite error
God damn goo.im I've been waiting for an oc ics kernel for a minute.. A long minute
me checking the site every minute isn't helping probably either
Can I flash a kernel for similar phone which has similar buttons and screen resolution and sensors but different board base and hope it works?
ramoneC said:
Can I flash a kernel for similar phone which has similar buttons and screen resolution and sensors but different board base and hope it works?
Click to expand...
Click to collapse
Generally speaking, no. What device are you talking about?
Sent from my Galaxy Nexus using Tapatalk 2
old galaxy s5830 < wont matter if it bricked
ramoneC said:
old galaxy s5830 < wont matter if it bricked
Click to expand...
Click to collapse
This kernel won't flash let alone boot on that lol
Sent from my Galaxy Nexus using Tapatalk 2
I have decided to buy googles phone henceforth so I wont have to worry about updating
stevie13.xo said:
God damn goo.im I've been waiting for an oc ics kernel for a minute.. A long minute
me checking the site every minute isn't helping probably either
Click to expand...
Click to collapse
Mirrors are up.
Maybe I missed something, but I've noticed a huge lack of JB kernels for the infuse, which is pretty odd. are they out there and I'm just blind, or are they way more integrated with the roms now?
Most JB roms, if not all of them, use scott's kernel source. That's practically all there is at this level..
mr.jaguar said:
Maybe I missed something, but I've noticed a huge lack of JB kernels for the infuse, which is pretty odd. are they out there and I'm just blind, or are they way more integrated with the roms now?
Click to expand...
Click to collapse
and if you want to get technical we dont have any jb kernel, or ics kernels because every kernel for the infuse (unless it was from back before we got the official GB) are Gingerbread kernel modified to allow compatibility for ICS and JB, so technicially we wont have any jb kernel, but as far as a variety of jb compatible kernels i would believe the reason why we only have one of those is because most of our kernel devs are not doing much with the infuse now, unless it is posted elsewhere and not on xda, but in all actuality why do we need a variety of kernels, the one we have is working excellent and includes OC, and several other performance enhancing features such as ZRAM
deathblade said:
and if you want to get technical we dont have any jb kernel, or ics kernels because every kernel for the infuse (unless it was from back before we got the official GB) are Gingerbread kernel modified to allow compatibility for ICS and JB, so technicially we wont have any jb kernel, but as far as a variety of jb compatible kernels i would believe the reason why we only have one of those is because most of our kernel devs are not doing much with the infuse now, unless it is posted elsewhere and not on xda, but in all actuality why do we need a variety of kernels, the one we have is working excellent and includes OC, and several other performance enhancing features such as ZRAM
Click to expand...
Click to collapse
Exactly this...our current kernel is phenomenal....and we lack kernel devs...that stuffs confusing...at least to me.
Sent from my HTC PH39100 using Tapatalk 2
Hello community,
I am a rookie in the subject of kernels/roms and I would love to have some precious help from any1 that knows even the smallest of information. I recently installed CM kernel and CM nightly 0422. The thing is, I read in many forums (in here as well) that there is a kernel that can boost battery life to its max, Franco Kernel. But I also read that it is somehow incompatible with CM 10+ and causes bootloop if you install it with CM already in phone. What I can't understand is why can't I just simply replace CM kernel (like stock kernel was replaced by CM kernel) by Franco Kernel? What is the fact that I am missing?
ALL (and I mean ALL) help will be highly appreaciated, thanks for your time
T.
f33d_me_plz said:
Hello community,
I am a rookie in the subject of kernels/roms and I would love to have some precious help from any1 that knows even the smallest of information. I recently installed CM kernel and CM nightly 0422. The thing is, I read in many forums (in here as well) that there is a kernel that can boost battery life to its max, Franco Kernel. But I also read that it is somehow incompatible with CM 10+ and causes bootloop if you install it with CM already in phone. What I can't understand is why can't I just simply replace CM kernel (like stock kernel was replaced by CM kernel) by Franco Kernel? What is the fact that I am missing?
ALL (and I mean ALL) help will be highly appreaciated, thanks for your time
T.
Click to expand...
Click to collapse
first off.. there is no magic pill to give your phone for battery life. battery life mostly depends on your personal usage, your personal setup, your apps used, and most importantly the quality of your phone/data connection. everything else is minor for battery life, including kernels.
cm uses CAF as its base now, they went away from aosp(like most kernels here). so everything that is aosp based is not compatible with cm anymore. franco kernel is aosp based(most kernels are). there are a few kernels that are CAF based built just for cm and cm based roms.
simms22 said:
first off.. there is no magic pill to give your phone for battery life. battery life mostly depends on your personal usage, your personal setup, your apps used, and most importantly the quality of your phone/data connection. everything else is minor for battery life, including kernels.
cm uses CAF as its base now, they went away from aosp(like most kernels here). so everything that is aosp based is not compatible with cm anymore. franco kernel is aosp based(most kernels are). there are a few kernels that are CAF based built just for cm and cm based roms.
Click to expand...
Click to collapse
Thanks for your time and your answer
First of all, I know for myself that there is no magic pill about battery life, I just read in too many threads that FK added a good portion of battery life (with same use of phone like when it had CM) ! Moreover it allows you to overclock (my) Nexus5 beyond 2.2GHz, something that CM doesn't allow you too (I know that overclocking kills battery, I just want to test something). What I don't understand is how can FK mess up with CM when both are different kernels and by installing FK over CM means that FK replaces CM. There is no CM in the end, only FK. Or not...? What have I understood wrong?
Thanks again
f33d_me_plz said:
Thanks for your time and your answer
First of all, I know for myself that there is no magic pill about battery life, I just read in too many threads that FK added a good portion of battery life (with same use of phone like when it had CM) ! Moreover it allows you to overclock (my) Nexus5 beyond 2.2GHz, something that CM doesn't allow you too (I know that overclocking kills battery, I just want to test something). What I don't understand is how can FK mess up with CM when both are different kernels and by installing FK over CM means that FK replaces CM. There is no CM in the end, only FK. Or not...? What have I understood wrong?
Thanks again
Click to expand...
Click to collapse
yes, franco would replace cm kernel if all worked right. but what you are doing is replacing cm kernel with franco kernel, but cm rom stays on your phone. franco kernel is incompatible with cm rom. since franco is aosp and cm is caf, your phone would never boot up all the way.
simms22 said:
yes, franco would replace cm kernel if all worked right. but what you are doing is replacing cm kernel with franco kernel, but cm rom stays on your phone. franco kernel is incompatible with cm rom. since franco is aosp and cm is caf, your phone would never boot up all the way.
Click to expand...
Click to collapse
So, if I am getting your point right, since one is aosp and the other is caf THAT is the reason why CM doesn't uninstall and will exist together with franco? Is there a way to permanently delete CM in order to install franco? Maybe to go back to stock kernel then install FK?
f33d_me_plz said:
So, if I am getting your point right, since one is aosp and the other is caf THAT is the reason why CM doesn't uninstall and will exist together with franco? Is there a way to permanently delete CM in order to install franco? Maybe to go back to stock kernel then install FK?
Click to expand...
Click to collapse
its not about the kernel, its about the rom. they are different things. when you flash a kernel(any), it replaces the kernel thats on your phone(kernels come with roms, cm kernel with cm rom). cm rom includes cm kernel, both are built from caf source. franco kernel is aosp, it is not compatible with cm rom. it has nothing to do with cm kernel, it replaces cm kernel when flashed. but you will never boot up your phone because it isnt compatible with cm rom.
simms22 said:
its not about the kernel, its about the rom. they are different things. when you flash a kernel(any), it replaces the kernel thats on your phone(kernels come with roms, cm kernel with cm rom). cm rom includes cm kernel, both are built from caf source. franco kernel is aosp, it is not compatible with cm rom. it has nothing to do with cm kernel, it replaces cm kernel when flashed. but you will never boot up your phone because it isnt compatible with cm rom.
Click to expand...
Click to collapse
ok, finally I got it, thanks to you Last question... is there a way to get FK now or am I just locked to caf due to CM "for life"? which way (if there is any at all) in your opinion is the best way to go from CM to FK? maybe go back to stock rom/kernel then flash FK? Will this work?
f33d_me_plz said:
ok, finally I got it, thanks to you Last question... is there a way to get FK now or am I just locked to caf due to CM "for life"? which way (if there is any at all) in your opinion is the best way to go from CM to FK? maybe go back to stock rom/kernel then flash FK? Will this work?
Click to expand...
Click to collapse
no, they arent compatible at all. you can not use franco kernel with any cm based roms. you can change roms and use franco kernel with it, any aosp rom or even the stock rom. but cm isnt compatible at all with franko kernel.
simms22 said:
no, they arent compatible at all. you can not use franco kernel with any cm based roms. you can change roms and use franco kernel with it, any aosp rom or even the stock rom. but cm isnt compatible at all with franko kernel.
Click to expand...
Click to collapse
Thanks man !!
f33d_me_plz said:
Thanks man !!
Click to expand...
Click to collapse
If your looking for a good CAF kernel to run with a PAC or CM based ROM. I'd recommend the ElementalX CAF kernel. It's very stable, rich features, great performance and great battery life. Make sure to read the OP for directions and if you decide to try it out download the ElementalX R38 version with the aromma installer (not the express version) As with running any new kernel run it for a few days minimum to allow for it by on settle in.
There is another option for you to explore too - http://forum.xda-developers.com/google-nexus-5/development/cm11-users-heres-how-aospnon-caf-t2626961
This allows you to run a script that will basically De-CAF your rom and allow you to run a AOSP kernel on CM11ROMs.. Be sure to read the OP. It works with many CM11 and CM based ROMs, but not on all the newest versions. Definitely worth checking out.
xdrc45 said:
If your looking for a good CAF kernel to run with a PAC or CM based ROM. I'd recommend the ElementalX CAF kernel. It's very stable, rich features, great performance and great battery life. Make sure to read the OP for directions and if you decide to try it out download the ElementalX R38 version with the aromma installer (not the express version) As with running any new kernel run it for a few days minimum to allow for it by on settle in.
There is another option for you to explore too - http://forum.xda-developers.com/google-nexus-5/development/cm11-users-heres-how-aospnon-caf-t2626961
This allows you to run a script that will basically De-CAF your rom and allow you to run a AOSP kernel on CM11ROMs.. Be sure to read the OP. It works with many CM11 and CM based ROMs, but not on all the newest versions. Definitely worth checking out.
Click to expand...
Click to collapse
Thanks for your interest and time! I will sure check both your ROM and the De-CAF script soon and post my opinion/experience ! For newbies like me that are reading this post, here is a quite enbrightening thread about CAF and qualcomm processors (although it's Reddit, it's quite explanatory).
Peace!
T.
f33d_me_plz said:
Thanks for your interest and time! I will sure check both your ROM and the De-CAF script soon and post my opinion/experience ! For newbies like me that are reading this post, here is a quite enbrightening thread about CAF and qualcomm processors (although it's Reddit, it's quite explanatory).
Peace!
T.
Click to expand...
Click to collapse
Sorry, I forgot to paste the link cheers ! http://www.reddit.com/r/Android/comments/1rt9md/eli5_what_is_caf_why_is_cm_going_caf_affects_the/
when i was using lollipop i always went with ak kernel but since ak kernel stopped supporting oneplus one when marshmallow roms began to come i became a bit confused as to which kernel i should use.
so i did a bit of searching with kernels that existed. and the kernels i found that i could use was
1. Sultan
2. Tyr Kernel
3. Andy Kernel
4. Radioactive Kernel
so i was wondering what kernel is the best alternative to ak kernel and if so does that kernel have any problems which makes so i should avoid it?
p.s im open to discussions and even having an idea of what i should do will probly help more then it hurts
calionte said:
when i was using lollipop i always went with ak kernel but since ak kernel stopped supporting oneplus one when marshmallow roms began to come i became a bit confused as to which kernel i should use.
so i did a bit of searching with kernels that existed. and the kernels i found that i could use was
1. Sultan
2. Tyr Kernel
3. Andy Kernel
4. Radioactive Kernel
so i was wondering what kernel is the best alternative to ak kernel and if so does that kernel have any problems which makes so i should avoid it?
p.s im open to discussions and even having an idea of what i should do will probly help more then it hurts
Click to expand...
Click to collapse
It's pretty simple actually CAF kernels usually stated in the title of the kernel thread work on CAF ROMs e.g. Sultan, and any ROM that states CAF in its title works with these kernels.
CM kernel such as Lightning, Boeffla and Andy all state specifically CM12/13 in the thread title and those work with stock CM and ROMs derived from CM source and kernel trees.
Finally Omni based kernels only one works properly (Donkey Kernel) also states Omni in the thread title.
The common denominator is that they all clearly state in the thread title what they are for so there's nothing to discuss on which ones to be used for which ROM. In regards to quality that's a bit trickier as we all like different things in a kernel and personally I'm a big fan of Boeffla when I'm on CM13 cause it works great and the app is very intuitive. I've also tried Andy kernel and its got a good mix of features. I'm on Omni 5.1.1 nightlies so I'm on the stock kernel but when I move back to Marshmallow I can update on kernels
Sent from my A0001 using Tapatalk
Renosh said:
It's pretty simple actually CAF kernels usually stated in the title of the kernel thread work on CAF ROMs e.g. Sultan, and any ROM that states CAF in its title works with these kernels.
CM kernel such as Lightning, Boeffla and Andy all state specifically CM12/13 in the thread title and those work with stock CM and ROMs derived from CM source and kernel trees.
Finally Omni based kernels only one works properly (Donkey Kernel) also states Omni in the thread title.
The common denominator is that they all clearly state in the thread title what they are for so there's nothing to discuss on which ones to be used for which ROM. In regards to quality that's a bit trickier as we all like different things in a kernel and personally I'm a big fan of Boeffla when I'm on CM13 cause it works great and the app is very intuitive. I've also tried Andy kernel and its got a good mix of features. I'm on Omni 5.1.1 nightlies so I'm on the stock kernel but when I move back to Marshmallow I can update on kernels
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
which kernels works with which rom i already knew but i still respect the answer i got. well the main concern i had was about the quality of the roms and which roms is good for what.
It depends on what you want. For example some devs here around merge a bunch of patches to improve sth. Sometimes i dont know what they are doing. I also started with that but soon i have learned less is more. Than there are kernels with gazillion oft features to choose. Thousond hotplugs and governors etc. Than there are small and simple kernels without such experimental features close to stock. I for example dont want to tune 5 days to improve me results i like it simple. So you have 3 or more different types to choose.
1. experimental maybe unstable kernels with lots of patches
2. kernels with lots of features
3. small and simple and more stable kernel close to stock
There is no best or better kernel. Choose the one you like best.
Its your choice.
You also missed the CAF lightning Kernel built off of AK's caf kernel. It's the best kernel for CAF right now IMO. It's basically all of AK kernel's great features just updated to support CAF marshmallow and bug fixes/ latest commits. Works with synapse and all of the original AK CAF kernel profiles.