I'm looking for any AOSP kernels not based on CM. It turns out the current 3.4 kernels for CM mess up my phone badly causing random reboots. I do not yet know how to build a kernel, hence I'm searching for the possibility of any that is not CM based.
Nope, they are all forked from CM's common one unfortunately
And it wouldn't just require building a kernel...you would need to port another AOSP kernel which is no easy task
Then I guess it's back to TW for good until the problem I'm having with CM 3.4 kernel is fixed, if ever. It was a nice ride with CM right from my GNex to this SGSIII d2spr. Now I can understand why AOKP do not have an AOSP ROM for the Sprint variant of the S3... It just doesn't work...
FAIL for CM... Bye to CM...
in what way does your phone "mess up"? i have the same device and i have not had a problem with Kernels at all
Related
Is this only a big deal for TW users or will the benefits help out with AOSP roms as well? I personally prefer AOSP roms (MIUI and CM9) so I'm really hoping that this recently released code will help those roms become more stable. Can someone briefly explain the significance of the source code being released and what it means for TW and AOSP roms? Thanks
You'll see some kernel tweaks/improvements and possibly better battery life. And we have the kernel source, not "source". "Source" would imply to me that we could build the whole ROM which we can't. Just FYI.
So I have got a question that maybe many others have yet to voice or address (maybe it's just me, and I am delusional). In any event, I am not new to rooting and flashing ROMS. I am also familiar--at least conceptually--with what the kernel is and what it does. For the purposes of this post however, I should mention that I have not ever flashed a custom kernel and am unsure as to why one would or why there is more than one floating around. I have been vacillating back on forth between stock and custom kernels....it seems like in order to flash this ROM you need this Kernel, or that ROM flash that Kernel. I want to learn and to know. I would really appreciate feedback on this.
157
Kernel's are installed or "flashed" in the same manner as a custom ROM, either through CWM or Odin. Kernel's just add an extra level of customization, most people use custom Kernel's for overclocking although they also have many other uses.
Kernals can also highly affect battery life and the speed of roms. The kernal has to match the kind of rom. Samsung kernals go with samsung/touchwiz based roms. Aosp kernals go with aosp based roms like cyanogenmod and aokp. There are a few jellybean kernals and those will work for the current jellybean aosp based roms. Samsung will eventually release their own jellybean update and when that happens expect to see jellybean samsung kernals made for roms based on samsung jellybean.
Hi I am new to rom and kernel flashing, and I am interested in flashing the ElementalX 1.1 kernel on AOKP. I love AOKP, and I am way interested in the swipe-to-wake and double-tap-to-wake features of ElementalX 1.1.
What kinds of things do I need to know about compatibility between kernels and Roms? Can you typically use any kernel with any rom?
Loving the Nexus experience and looking forward to learning more!
They often can but not always.
Android versions need to match.
Usually you can flash any kernel on any ROMs but if its a CM based ROM and you flash a custom kernel then slimport features sometimes don't work or some times you flash a custom kernel then the boot animation gets cut and turns black it doesn't really matter I have done lots of flashing and I would say that every kernel can be a flashed with any ROM without problems I am currently on CM kang and using kernel elemental x and everything runs smooth..hope this help click thankksss
Don't just slap any kernel to your device you might seriously brick it.....learned this lesson when I had an Atrix4G.....
sk8trix said:
Don't just slap any kernel to your device you might seriously brick it.....learned this lesson when I had an Atrix4G.....
Click to expand...
Click to collapse
Nexus devices are different then the Atrix4G. You can not seriously brick it by flashing an incompatible kernel. Even having no kernel will not prevent you from accessing the bootloader and recovery.
In my experience, it seems that pure AOSP builds have always been more stable and less buggy than cm or other aosp based roms. But I've also learned that it's a challenge to build purely from source. My question is, how likely is it for the g3 to get an AOSP ROM build from the main source?
So I've tried all the ROMs, I've tried Stock (When I first got the phone) I then tried CM12.1, then FlexOS, then back to CM, then BlissPop, then back to CM, then Cloudy's ROM, then Back to c-... you get the idea.
I looked in to trying to compile my own kernel, because frankly there isn't an updated d855 CM12.1 kernel to be seen anywhere that has features to make CM the least bit smooth and I decided that with my coursework becoming a bigger part of my life that I would simply have no time to put in the work (Or the knowledge).
So what I'm asking is simple, can someone please compile a custom kernel for cm12.1? I love this ROM, the lack of customization features is a feature in itself for me considering I love AOSP, CM is perfect for my usage but I just need a custom kernel so that it can be complimented and optimized for the G3, thanks.