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
Related
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=lgv500
Is where you can get it (start your downloading now...)
the strange thing is they appear to have two uploads for kitkat...
Sent from my LG-V500 using XDA Premium HD app
Yay! What does it mean for the simple user? Better roms?
Sent from my iPhone using Tapatalk
All I really want is gamma correction and maybe overclocking and U/V.
This means that anyone interested in building a replacement kernel for the LG stock 4.4.2 release has a blueprint to start from. I know of two kernels that have been released for 4.2.2 stock, this release means that we may see updates of these projects to 4.4.2.
I may try and restart my own efforts in this area as well depending upon time and what kind of problems I find in the 4.4.2 US release.
M
muiriddin said:
This means that anyone interested in building a replacement kernel for the LG stock 4.4.2 release has a blueprint to start from. I know of two kernels that have been released for 4.2.2 stock, this release means that we may see updates of these projects to 4.4.2.
I may try and restart my own efforts in this area as well depending upon time and what kind of problems I find in the 4.4.2 US release.
M
Click to expand...
Click to collapse
The first and most obvious is the gamma set at 2.05 roughly. If you set it to 2.2 - 2.3, that would already be a big plus.
The source uploaded by LG didn't include the kernel source so I contacted their open source division and they've now uploaded a proper kernel source. I'm travelling for work now, but will take a look at it when I get back home next week and get something compiled.
G Pad(V500)_Android_KitKat_LGV500_v20b_Kernel
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
Sent from my LG-V500 using Tapatalk
id10terror said:
The source uploaded by LG didn't include the kernel source so I contacted their open source division and they've now uploaded a proper kernel source. I'm travelling for work now, but will take a look at it when I get back home next week and get something compiled.
G Pad(V500)_Android_KitKat_LGV500_v20b_Kernel
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Good to hear that someone else contacted them as well. I have been impressed with their open source group responding as quickly as they did. They definitely respond better than several other companies when facing these requests!
:good::good: I would pay anybody to incorporate or activate the OTG+Charging in this Kernel. :good::good: :fingers-crossed:
id10terror said:
The source uploaded by LG didn't include the kernel source so I contacted their open source division and they've now uploaded a proper kernel source. I'm travelling for work now, but will take a look at it when I get back home next week and get something compiled.
G Pad(V500)_Android_KitKat_LGV500_v20b_Kernel
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
When if get the chance can you compare the 18a kernel to the 20b one? I like the settings the 18a kernel, the lower brightness levels are setup in a way that makes it great for night time. I have the 18a kernel running on the 20b build but after the screen is locked it and turned back on it changes to levels of the 20b kernel, but retains the gamma level. I could attach a flashable zip with the 18a kernel if you need it.
LBJM said:
When if get the chance can you compare the 18a kernel to the 20b one? I like the settings the 18a kernel, the lower brightness levels are setup in a way that makes it great for night time. I have the 18a kernel running on the 20b build but after the screen is locked it and turned back on it changes to levels of the 20b kernel, but retains the gamma level. I could attach a flashable zip with the 18a kernel if you need it.
Click to expand...
Click to collapse
Hi, I am quite a newbie. Just wondering what is the use of the kernels? Can we just flash it on custom roms like the kitkats ones done by _infected. AOKP or the Cynogenmod for the GPAD? The AOKP and the Cynogen are smooth but few features like Autorotate doesn't work and there is no gamma correction i think
I compiled a kernel using the source provided by LG, but for some reason, it doesn't boot.
I keep getting this error:
Code:
Secure booting error
Cause: boot certification verify
I noticed that the resulting "boot.emmc.win" is a lot smaller than the original boot.emmc.win (~10 MB compared to 24MB)
Another interesting thing is that if I uncompress the original 24 MB boot.emmc.win using the command "unmkbootimg -i boot.emmc.win", I get two files: kernel (7.5 MB) and ramdisk.cpio.gz (2.6 MB). If I rebuild the boot.emmc.win using these exact two files, I get an 11MB boot.emmc.win, but this one DOES boot.
It probably has something to do with the locked bootloader and the loki exploit.
Can anyone help me get to the bottom of this? I really want to solve the gamma issue.
Well, as I suspected, it was because of the locked bootloader, but using the loki_tool, I was able to bypass the bootloader check.
So I now have a working, self-compiled 4.4.2 kernel (using the eabi-4.7) , based on LG's kernel source.
Unfortunatelly, gamma is still the same (about 2 - 2.1). Need to figure out how to modify it.
If someone can and wants to help, I'd greatly appreciate it.
Can you look at the 18 Rom kernel and see what has changed?
Sent from my SM-N900W8 using Tapatalk
ruxandy said:
Well, as I suspected, it was because of the locked bootloader, but using the loki_tool, I was able to bypass the bootloader check.
So I now have a working, self-compiled 4.4.2 kernel (using the eabi-4.7) , based on LG's kernel source.
Unfortunatelly, gamma is still the same (about 2 - 2.1). Need to figure out how to modify it.
If someone can and wants to help, I'd greatly appreciate it.
Click to expand...
Click to collapse
Canadoc said:
Can you look at the 18 Rom kernel and see what has changed?
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
Panel is very close to correct gamma when using default linear qlut, instead of MSM_MIPI_LGIT_VIDEO_WUXGA_PT_PANEL qlut.
I would definitely take a look at the 50018A kernel if someone can provide the source. I wasn't able to find it.
gin_silver said:
Hi, I am quite a newbie. Just wondering what is the use of the kernels? Can we just flash it on custom roms like the kitkats ones done by _infected. AOKP or the Cynogenmod for the GPAD? The AOKP and the Cynogen are smooth but few features like Autorotate doesn't work and there is no gamma correction i think
Click to expand...
Click to collapse
The kernel is what drives the Rom. Without the kernel sources improvements to a device are hard to make. It's AOSP ( Android Open Source Project) not AOKP.
LBJM said:
The kernel is what drives the Rom. Without the kernel sources improvements to a device are hard to make. It's AOSP ( Android Open Source Project) not AOKP.
Click to expand...
Click to collapse
Thanks. Hopefully we will have some great modified kernels for the kitkat version
Btw i was referring to AOKP (K for Kang) in this thread http://forum.xda-developers.com/showthread.php?t=2710996
gin_silver said:
Thanks. Hopefully we will have some great modified kernels for the kitkat version
Btw i was referring to AOKP (K for Kang) in this thread http://forum.xda-developers.com/showthread.php?t=2710996
Click to expand...
Click to collapse
Good to know.
20d source released
I do not know if anyone will find this of use, but they have now posted the 20d kernel source (and some other stuff).
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
ruxandy said:
Well, as I suspected, it was because of the locked bootloader, but using the loki_tool, I was able to bypass the bootloader check.
So I now have a working, self-compiled 4.4.2 kernel (using the eabi-4.7) , based on LG's kernel source.
Unfortunatelly, gamma is still the same (about 2 - 2.1). Need to figure out how to modify it.
If someone can and wants to help, I'd greatly appreciate it.
Click to expand...
Click to collapse
Hello ruxandy,
Can you explain in few words how did you manage to push the kernel to your v500?
Here is my story:
I downloaded the V500 Lollipop kernel because I wanted to compile .ko loadable modules and drivers to support RTL2832U DVB USB dongle. I successfully compiled those modules, rooted the tabled and tried to insmod them. But it failed because the modules did not find some kernel APIs.
Then I decided to build the kernel with built-in those drivers and I did it successfully, the problem now is what to do with zImage. I read there are two roads the one building own KDZ file seems very complicated and not sure if really possible. The other seems to be to extract the boot.emmc.win file using TWRP. So I downgraded the V500 bootloader from LT to KK and installed TWRT using this http://forum.xda-developers.com/lg-g-pad-83/help/v500-how-to-install-twrp-stock-lp-t3165846 but after reboot got the secure boot error you did.
So again - how to use self built zImage and is this possible for KitKat only, since installing TWRP with Lollipop does not seem possible so far?
Hi everybody
I have made a flashable kernel zip from latest nightly update for 11s
Has all latest patch from cm.
I test with 38R
If you are coming from custom kernel s make sure that system files is untouch
Flash from recovery
geowolf1000 said:
Hi everybody
I have made a flashable kernel zip from latest nightly update for 11s
Has all latest patch from cm.
I test with 38R
If you are coming from custom kernel s make sure that system files is untouch
Flash from recovery
Click to expand...
Click to collapse
Didnt this the nightly with the new Touch update? I read that this causes sensor problems. I think there is another version to be released with the 28th nightly (tonight)
Just update to 28
geowolf1000 said:
Just update to 28
Click to expand...
Click to collapse
I am on rooted Stock 38R ROM. My wifi setting broke after installed this kernel, but the kernel did have much more improvement over stock 38R kernel.
Is there anyway to install the kernel without breaking wifi? Thanks!
bingbinghaha said:
I am on rooted Stock 38R ROM. My wifi setting broke after installed this kernel, but the kernel did have much more improvement over stock 38R kernel.
Is there anyway to install the kernel without breaking wifi? Thanks!
Click to expand...
Click to collapse
Let me guess, you were coming back to this kernel from Franco?
Also, to OP, are you going to keep maintaining this thread? Maybe having a regular (like weekly) updates or so?
zaphodbeeb said:
Didnt this the nightly with the new Touch update? I read that this causes sensor problems. I think there is another version to be released with the 28th nightly (tonight)
Click to expand...
Click to collapse
I can flash it or someone has a kernel update to the last nightly?
inscythe said:
Also, to OP, are you going to keep maintaining this thread? Maybe having a regular (like weekly) updates or so?
Click to expand...
Click to collapse
I will try
I am doing this for my self but i want to share with xda friends
Thread update to 31
Amazing improvement to touchscreen
how did u compile this kernel ??
was there any update officially from oneplus for the kernel of the stock 38r firmware?
reyscott1968 said:
how did u compile this kernel ??
was there any update officially from oneplus for the kernel of the stock 38r firmware?
Click to expand...
Click to collapse
After R38 can use nightly built
They impement kernel source
Its original from cm download page
Working like a charm
Thats why post here and not to developers threads
I dont compile nothing
I buy this phone because i do not have time to make my own and update from best
My wifi broke with this as well. Running completely stock 38R.
Can you share Source code please?
CrunchSA said:
My wifi broke with this as well. Running completely stock 38R.
Click to expand...
Click to collapse
Have you backup?
Just restore only system from revovery
Yeah, did that. Just reporting here that it was broken as an FYI.
https://github.com/CyanogenMod/android_kernel_oneplus_msm8974
Would this flash over Franco fine? Thanks in advance.
geowolf1000 said:
After R38 can use nightly built
They impement kernel source
Its original from cm download page
Working like a charm
Thats why post here and not to developers threads
I dont compile nothing
I buy this phone because i do not have time to make my own and update from best
Click to expand...
Click to collapse
Hmmm... I'm not that sure, but I guess there are some differences in the kernel between the standard CM11 and CM11S. Not too sure whether it is a good idea to flash kernel from nightly into 11S... How's your experience so far btw?
inscythe said:
Hmmm... I'm not that sure, but I guess there are some differences in the kernel between the standard CM11 and CM11S. Not too sure whether it is a good idea to flash kernel from nightly into 11S... How's your experience so far btw?
Click to expand...
Click to collapse
Why not ?
The device boot fine and all hardware are working fine
If was not compatibility the device could even boot
Which hardware are different to nightly????
geowolf1000 said:
Why not ?
The device boot fine and all hardware are working fine
If was not compatibility the device could even boot
Which hardware are different to nightly????
Click to expand...
Click to collapse
If you see other custom kernel pages, usually they would have different versions for CM11 and CM11S... So I would assume that there are inherent differences between them. But if it is working fine for you, then great! Maybe I'll try it myself too
runderekrun said:
Would this flash over Franco fine? Thanks in advance.
Click to expand...
Click to collapse
Reflash (dirty) your ROM first to restore WiFi firmware
Is there any kernel for Android 6.0.1 on Nexus 7 2012?
Yes, every 6.x ROM provides a kernel, too, or what are you looking for? If you are looking for sources, you might want to have a look at my Github.
AndDiSa said:
Yes, every 6.x ROM provides a kernel, too, or what are you looking for? If you are looking for sources, you might want to have a look at my Github.
Click to expand...
Click to collapse
I am looking for kernel that enables overclocking. I searched forum but there are only kernels for Lollipop, not Marshmallow.
Probably you would like to have a look on Daniel_hk's kernel for Omni ROM. If I got it right, he implemented some overclocking into it, but I did not test it.
AndDiSa said:
Probably you would like to have a look on Daniel_hk's kernel for Omni ROM. If I got it right, he implemented some overclocking into it, but I did not test it.
Click to expand...
Click to collapse
So just flash OmniROM for 6.0.1? And the kernel is included? Or is there a separate file for kernel that must be flashed?
His Omni-build should include the OC-kernel directly.
Looking for a kernel on Nexus 7 2012 (3G) to fix baseband_XMM_power wakelock
@williamlaw: my kernel has the patch included. Most likely I'll upload a fastboot flashable zip today or tomorrow onto my Android 6 AOSP on Grouper thread.
AndDiSa said:
@williamlaw: my kernel has the patch included. Most likely I'll upload a fastboot flashable zip today or tomorrow onto my Android 6 AOSP on Grouper thread.
Click to expand...
Click to collapse
Thanks for your work but i am using 3G version.
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.
I'm looking at the Neptune pine to see what I can do with it.
so far I have obtained the kernel config
Configkernel3.4
This Thread is for sharing information and Q/A
My goal is to have a custom android rom compiled and then to try port different O/S's to it.
Nice! What's the status of your efforts?
How to the testing .....
JustSueMe said:
I'm looking at the Neptune pine to see what I can do with it.
so far I have obtained the kernel config
Configkernel3.4
This Thread is for sharing information and Q/A
My goal is to have a custom android rom compiled and then to try port different O/S's to it.
Click to expand...
Click to collapse
What about using the kernel source from cyanogenmod, like the dev did who released beta cyanogenmod?
F0L said:
What about using the kernel source from cyanogenmod, like the dev did who released beta cyanogenmod?
Click to expand...
Click to collapse
Ok, should have read it better. Are you able to just compile a kernel for testing. Once you have a working one, that would be a good base for updating rom.
JustSueMe said:
I'm looking at the Neptune pine to see what I can do with it.
so far I have obtained the kernel config
Configkernel3.4
This Thread is for sharing information and Q/A
My goal is to have a custom android rom compiled and then to try port different O/S's to it.
Click to expand...
Click to collapse
Any update on this?
Guess this is not going to happen. Just wish I still had the time I used to. I would have had a go my self, as the vanilla kernel is what kills this cool bit of kit.
I managed to get it to a usable state with google play installed, by installing SkyNET. Which tweaks the system on the fly when needed. Helps keep as much memory as possible.
Would the kernel source of the Nokia X help? as it uses the exact same hardware.
I have it downloaded, so if it will help, I can link.
I have given up on anyone doing anything with pine. So I tweaked stock rom as much as I could, got it running very nicely even with my 130GB storage (link2sd). I also modified the ramdisk image to support init.d on boot. Im also using kickarse kernel script.
F0L said:
I have given up on anyone doing anything with pine. So I tweaked stock rom as much as I could, got it running very nicely even with my 130GB storage (link2sd). I also modified the ramdisk image to support init.d on boot. Im also using kickarse kernel script.
Click to expand...
Click to collapse
Can you post how you did it? Thanks
@fol I would also be interested in it.
killervette said:
Can you post how you did it? Thanks
Click to expand...
Click to collapse
I used rom kichen to mess with ramdisk (it was very risky as messing with boot image can brick pine). I manually added init.d support. Then repacked it. Luckly it worked fine. I even flashed it to my sons.
I extracted stock system.zip and tweaked it the way I wanted (debloated added apps I owned), then flashed that. As I added init.d, I could use scripts on boot to alter running of pine.
Im currently using Project skynet vr4, which runs very nice.
@fol What is skynet? Do you have a link?