As the title says, anyone know how to make aosp-based kernel compatible with cyanogenmod?
What I'm searching for is a set of particular commits that will make the kernel compatible with CM11.
Any help will be appreciated, thanks!
BTW how to search for commit message in github?
I need to search for commit that will give faux123 voltage control.
You can just take a CM11 kernel for mako for example and look at the first few commits.
As far as I know you can't search by commit message.
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
Found my answer my self
https://github.com/bedalus/nexus4/blob/225bb02af8fa5cb75f294e5e826d5910be347119/cm.patch
Related
Hello. Does anybody know good guide how to compile Cyanogenmod for our devices ? i want to try make own custom rom, and i want cyanogenmod 7/10, but have no idea from where to start
http://xda-university.com/as-a-developer/introduction-how-an-android-rom-is-built
http://forum.xda-developers.com/showthread.php?t=1801690
Cheers and good luck
mission733 said:
Hello. Does anybody know good guide how to compile Cyanogenmod for our devices ? i want to try make own custom rom, and i want cyanogenmod 7/10, but have no idea from where to start
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1903413 For the GT540
If you run into any issue while building read the last few pages of the thread
Hi guys,
I've been compiling CM 10.2 with loadable module support for some time already. The only change I had to make was to modify appropriate configuration parameter in cyanogen_mako_defconfig file (change to CONFIG_MODULES=y). Since CM11, kernel compiled with this change gives me bootloops. If I revert the change back, compiled kernel functions properly.
Any idea what would be (additionally) needed to build CM 11 kernel with loadable modules support?
Thanks!
yopet said:
Hi guys,
I've been compiling CM 10.2 with loadable module support for some time already. The only change I had to make was to modify appropriate configuration parameter in cyanogen_mako_defconfig file (change to CONFIG_MODULES=y). Since CM11, kernel compiled with this change gives me bootloops. If I revert the change back, compiled kernel functions properly.
Any idea what would be (additionally) needed to build CM 11 kernel with loadable modules support?
Thanks!
Click to expand...
Click to collapse
Did you resolve this? I hit on the same problem. Once the modules are enabled it enters into boot-loop.
Unfortunately, no.
Had to give up cause I didn't have the time to try anymore.
I took the easier route and currently I'm on kernel from crDroid simple.
Sent from my Nexus 4 using xda app-developers app
yopet said:
Unfortunately, no.
Had to give up cause I didn't have the time to try anymore.
I took the easier route and currently I'm on kernel from crDroid simple.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I went the same way. Extracted the kernel from crDroid rom and flashed it.
But anyway interesting why cm team broke this option in the kernel. Will they fix it in future?...
woland_ca said:
Thanks. I went the same way. Extracted the kernel from crDroid rom and flashed it.
But anyway interesting why cm team broke this option in the kernel. Will they fix it in future?...
Click to expand...
Click to collapse
I really don't know. Since CM team decided for their rom not to have module support anymore, seems that talking about that topic is kind of a taboo.
Anyway, since module support is not something CM is interested in at all, I doubt anything will change. At least not intentionally.
Having in mind that there are many kernels based on CM which have module support enabled, it is not impossible. It just requires some more understanding and work how to do it. I asked this on many different forums and got 0 answers.
Kernel change
woland_ca said:
Thanks. I went the same way. Extracted the kernel from crDroid rom and flashed it.
But anyway interesting why cm team broke this option in the kernel. Will they fix it in future?...
Click to expand...
Click to collapse
Hey
can you explain how you changed the kernel?
thank you
yosef_a said:
Hey
can you explain how you changed the kernel?
thank you
Click to expand...
Click to collapse
Pull the boot.img out of the rom
Sent from my Nexus 5 using XDA Free mobile app
The kernel has been open sourced, by CM, as any OEM should do when device hits retail. That means a great step for us, ROM developers. We may discuss findings for reference on future development here.
Link to source code: https://github.com/CyanogenMod/android_kernel_oneplus_msm8974
By the way, it's not only useful for the OnePlus One, seems that it's interesting for Find 7 as they borrow some code from it, worthy to read.
Oh Gr8 news ! Hope we could get custom kernel on OPO soon
Sent from my One using XDA Premium 4 mobile app
I am hoping we get one soon also.
Sent from my One using Tapatalk
SferaDev said:
The kernel has been open sourced, by CM, as any OEM should do when device hits retail. That means a great step for us, ROM developers. We may discuss findings for reference on future development here.
Link to source code: https://github.com/CyanogenMod/android_kernel_oneplus_msm8974
By the way, it's not only useful for the OnePlus One, seems that it's interesting for Find 7 as they borrow some code from it, worthy to read.
Click to expand...
Click to collapse
Mind putting together the flashable zip of the stock kernel so that users who go custom kernel flashing (Franco for now) can fall back to the stock kernel?
A flashable .zip would be great
@SferaDev Thanks for this, I will be using this to build a kernel for our devices
Gamma control is out:
0f98e789af8c12ce3687cbe4515b429aa1e031a3 video: mdss: Add predefined gamma selection
I'm a bit confused.
So far, I know of two kernel sources: This one and AOSP-compatible sources released by OnePlus directly (OnePlusTech on github, can't post links at my postcount).
However, there are already custom kernels that claim to only work with CM11S, and others that claim to only work with CM11. I assume the latter are based on this source. So what's the current (official) branch for CM11S?
DrDaxxy said:
I'm a bit confused.
So far, I know of two kernel sources: This one and AOSP-compatible sources released by OnePlus directly (OnePlusTech on github, can't post links at my postcount).
However, there are already custom kernels that claim to only work with CM11S, and others that claim to only work with CM11. I assume the latter are based on this source. So what's the current (official) branch for CM11S?
Click to expand...
Click to collapse
OnePlus AOSP is really new and I personally recommend CMs one. Their original intention was to keep as CM as possible...
SferaDev said:
OnePlus AOSP is really new and I personally recommend CMs one. Their original intention was to keep as CM as possible...
Click to expand...
Click to collapse
So kernels that don't work with the stock ROM are just based on a newer revision of the kernel in CM's repo, and older revisions in there would boot CM11S just fine?
DrDaxxy said:
So kernels that don't work with the stock ROM are just based on a newer revision of the kernel in CM's repo, and older revisions in there would boot CM11S just fine?
Click to expand...
Click to collapse
I haven't faced ANY kernel that doesn't work...
A flashable zip will be great! Can any expert help on this?
Hello!
I am new here and I tried searching but couldn't find an answer.
Is there any Kernel available that allows for undevolting and can be used with stock 4.4.4 the .167 build?
Any help or guidance will be appreciated.
Cheers
Hi,
You should use the Q&A, Help and Troubleshooting section for questions.
Cheers
I was planning to do one this week (without any guaranty). It will have undervolting but probably not many other features. Maybe a couple of governors. If you want I can pm it to you when I've done it.
pec0ra said:
I was planning to do one this week (without any guaranty). It will have undervolting but probably not many other features. Maybe a couple of governors. If you want I can pm it to you when I've done it.
Click to expand...
Click to collapse
Hmm i was working on a kernel for my self and i had added voltage control but i cant get past the compiling error
Could you help me perhaps?
Im no dev so i know extremly basic things.
Envious_Data said:
Hmm i was working on a kernel for my self and i had added voltage control but i cant get past the compiling error
Could you help me perhaps?
Im no dev so i know extremly basic things.
Click to expand...
Click to collapse
Of course !
In I'm at a wine degustation at the moment but send me a message and I'll answer tomorrow morning.
Envious_Data said:
Hmm i was working on a kernel for my self and i had added voltage control but i cant get past the compiling error
Could you help me perhaps?
Im no dev so i know extremly basic things.
Click to expand...
Click to collapse
Seems like you blocked private messages... so sorry for the off topic but here is my answer :
Are you using linaro greater than 4.8 ?
If so I think adding a Wno-sizeof-pointer-memaccess to your compile flags should do it. Yo be sure, look at my github in the abricot repository (abricot branch) and one of the first commits is for compatibility with linaro >= 4.8. Look at the changes in the Makefile.
By the way, maybe I'm just blocked by tapatalk in this case tell me and I'll find a way to send you pms
pec0ra said:
Seems like you blocked private messages... so sorry for the off topic but here is my answer :
Are you using linaro greater than 4.8 ?
If so I think adding a Wno-sizeof-pointer-memaccess to your compile flags should do it. Yo be sure, look at my github in the abricot repository (abricot branch) and one of the first commits is for compatibility with linaro >= 4.8. Look at the changes in the Makefile.
By the way, maybe I'm just blocked by tapatalk in this case tell me and I'll find a way to send you pms
Click to expand...
Click to collapse
Odd i could have sworn i disabled that...
Anywhoo i am trying to compile with 4.8
I have added the makefile fix both for GCC 4.6 and 4.7 but i was having a very odd error where it said the toolchain didnt exist even with the correct directory
I cant remember if im trying to compile with 4.8 or 4.8.2 linaro, in quite sure its just 4.8 arm-eabi-linux(something like that)
Ill disable(or try) the messaging thing and ill get back to you on this tomorow
Abricot kernel
I got a 4.4.4 kernel working with some extra governors, recovery (I think reboot to recovery doesn't work yet but you can access it with volume down button) and undervolting.
I'll send you a link via PM and maybe I'll also make a thread for it in the following weeks. In the mean time you can check it's sources at my github
Hello everyone.
http://download.jgcaap.xyz/files/bullhead/cm-13.0/
Would like to request if possible if someone could test this build
This build is based on CM device tree kernel and blobs, which shouldn't cause any issues on flashing.
As a test, please remember i'm not responsible to any damage which might occurr.
The worst thing might happen is not booting.
This rom is like flashing a CM nightly.
I'm interested on expanding my work between diferent devices. So please let me know how it goes.
Please list the bugs.
F2FS is compatible with this device?
source https://github.com/CyanogenMod/android_kernel_lge_bullhead
Thank you
jgcaap said:
Hello everyone.
http://download.jgcaap.xyz/files/bullhead/cm-13.0/
Would like to request if possible if someone could test this build
This build is based on CM device tree kernel and blobs, which shouldn't cause any issues on flashing.
As a test, please remember i'm not responsible to any damage which might occurr.
The worst thing might happen is not booting.
This rom is like flashing a CM nightly.
I'm interested on expanding my work between diferent devices. So please let me know how it goes.
Please list the bugs.
F2FS is compatible with this device?
Thank you
Click to expand...
Click to collapse
Please add a direct link to kernel source used as required by XDA and GPLv2...thanks. And thanks for your contribution.
KennyG123 said:
Please add a direct link to kernel source used as required by XDA and GPLv2...thanks. And thanks for your contribution.
Click to expand...
Click to collapse
It's stock from CM. I'll open a new post under development thread if everything goes well on tests and add all source links there. Is it ok? thanks
jgcaap said:
It's stock from CM. I'll open a new post under development thread if everything goes well on tests and add all source links there. Is it ok? thanks
Click to expand...
Click to collapse
The only thing considered stock is direct from the manufacturer, LG or Google. CM is not a stock OS, therefore if you are distributing the binary (boot.img) in your link then you must post a link to the kernel source compiled to make it. Otherwise you need to remove the boot.img and let people get their own kernel.
Thanks
KennyG123 said:
The only thing considered stock is direct from the manufacturer, LG or Google. CM is not a stock OS, therefore if you are distributing the binary (boot.img) in your link then you must post a link to the kernel source compiled to make it. Otherwise you need to remove the boot.img and let people get their own kernel.
Thanks
Click to expand...
Click to collapse
done Thanks for clarifying.
Hello @jgcaap
i will test and report back
thanks for supporting 5x and 6p (i have both)
edit: i'm using F2FS and un-encrypted. I've had to change the kernel to jolla's, to make it boot. It does not boot on stock kernel.
everything else seems to be working fine.