Introduction
Hello everyone, this is a thread to introduce both users and kernel developers to the concept of linux-stable as well as give developers some tips and a tree to either merge into their own, use as a base, or just as a reference. Feel free to ask questions and enjoy!
What is it?
linux-stable is, as the name implies, the stable branch of the Linux kernel, the base of Android. The phone could not run without the Linux kernel (at least not without reworking a lot of stuff). The Android kernels are based on the longterm stable trees:
Longterm
There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees.
Click to expand...
Click to collapse
Source: https://www.kernel.org/category/releases.html
All Linux development happens on the master branch, which is governed by Linus Torvalds. When issues are discovered there, the fixes are applied then backported to these various stable trees for consumption. It is not uncommon for a fix to need to go back a few years.
There is a LOT more information available in the notes repo in the android-linux-stable organization if you care to learn more in-depth: https://github.com/android-linux-stable/notes
What does this mean for me?
If you are a developer, this means you should be merging these changes into your own tree. These are vetted, stable fixes to real world problems and they are being handed out for free. It does not take long to get up to date (as you can just merge this tree directly into your own or do it yourself using the tree as a reference) and once you are up to date, there is usually a release once every two weeks, give or take. I provide a rebuttal to a lot of various complaints here. If you still feel like there is a good reason not to do this, please let me know, I'll be happy to try and debate on it!
If you are a user, it means that you should be looking for and using kernels that have these fixes, as it shows the developers care for your security and stability. The current version for this device is 3.18.100 and the current version upstream is 3.18.124 so all you need to do is go into Settings > About phone and look at the kernel version to know if you are up to date.
How do I use?
If you are a developer, the reference tree is located in the android-linux-stable organization: https://github.com/android-linux-stable/marlin
This can either be merged into your existing kernel tree if you have one or be used as a fresh base. You do not need my permission to use it nor do you need to give me credit (although it would be appreciated).
If you are a user, use a kernel that has the changes added in!
Getting notified about updates
There are a few ways to get notified of linux-stable updates:
The linux-kernel-announce mailing list: http://vger.kernel.org/vger-lists.html#linux-kernel-announce
The android-linux-stable Telegram channel: https://t.me/alsupdates
Subscribe to this thread
Follow me on Google+ or Twitter
Getting help
If you have any issues with getting these changes into your tree or want to ask a question, there are a few different ways to do it:
Post in this thread
Join the linux-stable support chat on Telegram: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
File an issue either in the android-linux-stable notes repo or the android-linux-stable repo for this device
When requesting help, please give some solid details as to what you are struggling with, as I am happy to provide assistant and clarity but not to do something for you (unless I screwed up).
3.18.88 has been merged in.
3.18.89 has been merged in.
3.18.90 has been merged in.
Thanks bro
3.18.91 has been merged in (conflict notes).
Thank you to the developer .I have a question
Witch kernel have wireguard for pixel XL?
pixel52 said:
Thank you to the developer .I have a question
Witch kernel have wireguard for pixel XL?
Click to expand...
Click to collapse
Not something appropriate for this thread, but if you look at the OP of 2 of the XL kernels they mention wiregard support
3.18.92 has been merged in.
Nevermindthelabel said:
Not something appropriate for this thread, but if you look at the OP of 2 of the XL kernels they mention wiregard support
Click to expand...
Click to collapse
Search op for custom kernels a few do and sorry i posted to wrong quote sorry bro
3.18.93 has been merged in.
3.18.94 has been merged in (conflict notes).
3.18.95 has been merged in.
The OP has been updated, including some more information for users as well as some more ways of getting help and notified of updates! Enjoy
3.18.96 has been merged in.
For some reason I have to set selinux to permissive to work is that normal I can't get it to compile any other way
joeeboogz said:
For some reason I have to set selinux to permissive to work is that normal I can't get it to compile any other way
Click to expand...
Click to collapse
I'm not sure I understand, what do you mean set to permissive to get it to compile? You're compiling on the computer.
nathanchance said:
I'm not sure I understand, what do you mean set to permissive to get it to compile? You're compiling on the computer.
Click to expand...
Click to collapse
Yes I compile kernel with a ROM but it throws sepolicy error then I set to permissive it compiles.
joeeboogz said:
Yes I compile kernel with a ROM but it throws sepolicy error then I set to permissive it compiles.
Click to expand...
Click to collapse
Well does it build without using this kernel and without permissive?
Sent from my Google Pixel 2 XL using XDA Labs
nathanchance said:
Well does it build without using this kernel and without permissive?
Click to expand...
Click to collapse
I figured it out thanks
Related
** Disclaimer **
If you flash this and your device breaks, I'm not taking responsibility. You flash anything and everything AT YOUR OWN RISK.
This is intended (at time of writing) to remain stock AOSP source with upstream Linux 3.10.x merged in. I will be keeping a living copy of the Nexus 6 kernel source up-to-date with AOSP sources, as well as TESTED and VERIFIED upstream Linux subversion up to the most recent (3.10.63 at time of writing). This is mainly to save other developers time spent merging upstream Linux (while ultimately not very influential on Android, some benefits still remain that make it worthwhile to maintain this)
Branches to reference:
android-5.1 (AOSP + Upstream Linux Kernel)
Update: omnirom/android-5.1 AOSP lollipop-mr1 kernel including necessary bcmdhd and selinux changes for WFC (this is NOT an m-preview merge into lollipop-mr1)
AOSP Nexus 6 Kernel Source
Linux Kernel 3.10.x Source
Currently tested with:
Stock (5.0.1 at time of writing)
OmniROM
CyanogenMod
CleanROM 1.3.5
As you test on different ROMs, please let me know so I can keep this list updated.
Also, this is a Nexus, as long as people don't start adding weird things, this will work fine on just about any ROM.
Reserve 2
I think you posted this in the wrong section, anyhow, thank you for your contribution I will for sure be taking a look at your work.
RIPng said:
I think you posted this in the wrong section, anyhow, thank you for your contribution I will for sure be taking a look at your work.
Click to expand...
Click to collapse
No, correct section. I plan on providing a "customized" version soon, which will provide some minor optimizations and changes. Currently working on another kernel for another device right now, so that will come once I complete my other project (next few days )
jakew02 said:
** This will mainly be for reference for developers, but can also be flashed for use with any ROM as well **
This is intended (at time of writing) to remain stock AOSP source with upstream Linux 3.10.x merged in. I will be keeping a living copy of the Nexus 6 kernel source up-to-date with AOSP sources, as well as TESTED and VERIFIED upstream Linux subversion up to the most recent (3.10.63 at time of writing). This is mainly to save other developers time spent merging upstream Linux (while ultimately not very influential on Android, some benefits still remain that make it worthwhile to maintain this)
Reference the android-5.0. I will only push to that branch after personally compiling and testing the kernel.
Source: https://github.com/jakew02/android_kernel_moto_shamu
AOSP Nexus 6
Linux Kernel 3.10.x
(Will make post pretty later)
Click to expand...
Click to collapse
Hey Jake...have you tried compiling this kernel on mac yet? I am having tons of issues with headers. Not sure if something is missing with Xcode. I am pretty sure I remember you having a mac.
rlasalle15 said:
Hey Jake...have you tried compiling this kernel on mac yet? I am having tons of issues with headers. Not sure if something is missing with Xcode. I am pretty sure I remember you having a mac.
Click to expand...
Click to collapse
I used to, but not anymore. Most certainly an OS X issue. You would need to give me the errors to look at since I have no issues compiling on Arch.
jakew02 said:
I used to, but not anymore. Most certainly an OS X issue. You would need to give me the errors to look at since I have no issues compiling on Arch.
Click to expand...
Click to collapse
Going to try again.....building inline. give me a few.
---------- Post added 29th December 2014 at 12:41 AM ---------- Previous post was 28th December 2014 at 11:55 PM ----------
jakew02 said:
I used to, but not anymore. Most certainly an OS X issue. You would need to give me the errors to look at since I have no issues compiling on Arch.
Click to expand...
Click to collapse
sent you a pm.
here is the issue for anyone else that may have a clue on what a fix could be:
In file included from /Volumes/android/eos/kernel/moto/shamu/scripts/sortextable.c:31:
/Volumes/android/eos/kernel/moto/shamu/tools/include/tools/be_byteshift.h:4:10: fatal error: 'linux/types.h'
file not found
#include <linux/types.h>
^
1 error generated.
It seems like mac os x doesn't have types.h headers that linux does. Hammerhead compiles just fine, but shamu....she no wanna compile inline.
Download link for the boot image added to OP. Tested ROMs are in post #2.
jakew02 said:
** This will mainly be for reference for developers, but can also be flashed for use with any ROM as well **
This is intended (at time of writing) to remain stock AOSP source with upstream Linux 3.10.x merged in. I will be keeping a living copy of the Nexus 6 kernel source up-to-date with AOSP sources, as well as TESTED and VERIFIED upstream Linux subversion up to the most recent (3.10.63 at time of writing). This is mainly to save other developers time spent merging upstream Linux (while ultimately not very influential on Android, some benefits still remain that make it worthwhile to maintain this)
Reference the android-5.0. I will only push to that branch after personally compiling and testing the kernel.
I will not be providing a recovery zip for installation. Use fastboot of Flashify.
Eventually going to add a custom version with CPU frequency and voltage control, and maybe some other stuff.
Download: shamu-3.10.63-20141230
Source: https://github.com/jakew02/android_kernel_moto_shamu
AOSP Nexus 6
Linux Kernel 3.10.x
(Will make post pretty later)
Click to expand...
Click to collapse
Sweet, thanks for this Jake - I like merging much better than manually patching
CPA Poke said:
Sweet, thanks for this Jake - I like merging much better than manually patching
Click to expand...
Click to collapse
The way I have setup the commit history should allow for most developers to just rebase onto my kernel source. I'm willing to bet there will be minimal merge conflicts in doing that (depending on what has been changed, of course)
jakew02 said:
The way I have setup the commit history should allow for most developers to just rebase onto my kernel source. I'm willing to bet there will be minimal merge conflicts in doing that (depending on what has been changed, of course)
Click to expand...
Click to collapse
Already started I was talking about future maintenance, ie for those who have already updated to the most recent sources.
Updated to 3.10.64
rlasalle15 said:
Going to try again.....building inline. give me a few.
---------- Post added 29th December 2014 at 12:41 AM ---------- Previous post was 28th December 2014 at 11:55 PM ----------
sent you a pm.
here is the issue for anyone else that may have a clue on what a fix could be:
In file included from /Volumes/android/eos/kernel/moto/shamu/scripts/sortextable.c:31:
/Volumes/android/eos/kernel/moto/shamu/tools/include/tools/be_byteshift.h:4:10: fatal error: 'linux/types.h'
file not found
#include <linux/types.h>
^
1 error generated.
It seems like mac os x doesn't have types.h headers that linux does. Hammerhead compiles just fine, but shamu....she no wanna compile inline.
Click to expand...
Click to collapse
This is related to your toolchain and the 'include' files, or your NDK sysroot if you are using NDK/toolchain. What toolchain are you using to compile?
ryanbg said:
This is related to your toolchain and the 'include' files, or your NDK sysroot if you are using NDK/toolchain. What toolchain are you using to compile?
Click to expand...
Click to collapse
He is building in OS X, probably not a toolchain issue. I would assume it's a compiler issue that needs to be fixed with some strange workaround specifically for OS X, since he said hammerhead kernel builds fine.
jakew02 said:
He is building in OS X, probably not a toolchain issue. I would assume it's a compiler issue that needs to be fixed with some strange workaround specifically for OS X, since he said hammerhead kernel builds fine.
Click to expand...
Click to collapse
Depends on if he is using the prebuilt darwin toolchain, there's some missing data types/ops in the header types.h. I've noticed it's been like that since Android 19 platform.
@ryanbg possible. @rlasalle15 I had issues with Mac previously (about a year and a half ago) but have since purchased a new laptop and use Linux exclusively so I'm not much help here.
Updated 3.10.64 image available via OP.
I'm happy using by his kernel. Thanks! I've tried several different kernels, and this seems to keep the phone running fast, reliable, and adequate battery life.
updated to 3.10.65, boot.img included in OP and github reflects.
Apologize for my ignorance...but is this encrypted?
Hello,
This is a stock SeLinux permissive kernel and init.d activated for Samsung Galaxy Note Edge (N915F) for Lollipop 5.0.1.
There are inputs that is working also on N915FY.
The kernel was compiled from Samsung source LL_CIS kernel using Google toolcahin v4.8.
If you want to test it, please flash in cwm the attached file and report back. Please make a backup of your actual kernel (boot.img) befor flashing this one.
Special thanks to @Micky387 who advised me to update the source kernel (MH driverI), @Wuby986 for his support and guidance and @daxgirl for his advices.
My kernel source for N915F (N915FOXE1BOC6) is here.
Happy flashing.
PS. Kernel updated. Same functionality but some different info in "About".
Well you got further than I did .. Kept getting some driver file referenced so it would not complied.. Thanks for effort I hope you work it out soon.. Unfortunately I don't have time at the moment ..
starbucks2010 said:
Hello,
Since few days I struggle to build a SeLinux permissive kernel for Samsung Galaxy Note Edge with Lollipop 5.0.1 but without success. Or with partial success.
I followed several guides from xda and other sites but it seems that everyone has his different way of doing it.
What I have done so far:
- I installed Ubuntu 14.04 with all updates and apt-get xxx
- I installed the Google toolchain arm-eabi-4.8
- I Installed Samsung kernel source for N915F_CIS from here
- I changed the path to the toolchain in Makefile and build_kernel.sh
- I run from kernel source folder: ./build_kernel.sh
- After 10-15 min of compilation I get a zImage file in //output/arch/arm/boot of ~ 9.8 Mb
- Using Android Image Kitchen v2.2 I integrated the zImage into a boot.img to be flashed with cwm
I flashed this new boot.img but the phone is rebooting every minute and in about I have "unknown"as baseband.
Anyone have an idea how to fix this?
Thank you in advance.
Click to expand...
Click to collapse
hi man. How are you ?
So many thing are change in lollipop . the modem and firmware modem dont call same as KK ROM.
So be sure you are this commit https://github.com/CyanogenMod/andr...mmit/784aa9a84b77090fa591bff77045341c3e3c6293
and add MHI module into tblte_defconfig
https://github.com/CyanogenMod/andr...mmit/1dd44659ee26c2d8b313c1346192e2bfa2ac7bb9
dont delete 18 and 19 line if you build for TW rom .
Try and report
micky387 said:
hi man. How are you ?
So many thing are change in lollipop . the modem and firmware modem dont call same as KK ROM.
So be sure you are this commit https://github.com/CyanogenMod/andr...mmit/784aa9a84b77090fa591bff77045341c3e3c6293
and add MHI module into tblte_defconfig
https://github.com/CyanogenMod/andr...mmit/1dd44659ee26c2d8b313c1346192e2bfa2ac7bb9
dont delete 18 and 19 line if you build for TW rom .
Try and report
Click to expand...
Click to collapse
Bonjour Mickey,
Thank you for your advice. I'll try it and let you know how it goes. Do you know if I have to flash also the modules together with the new kernel or only the boot.img alone ?
Merci.
starbucks2010 said:
Bonjour Mickey,
Thank you for your advice. I'll try it and let you know how it goes. Do you know if I have to flash also the modules together with the new kernel or only the boot.img alone ?
Merci.
Click to expand...
Click to collapse
No need to flash module. The MHI module will be in the kernel so you have boot.img with all inside.
starbucks2010 said:
Hello,
Since few days I struggle to build a SeLinux permissive kernel for Samsung Galaxy Note Edge with Lollipop 5.0.1 but without success. Or with partial success.
I followed several guides from xda and other sites but it seems that everyone has his different way of doing it.
What I have done so far:
- I installed Ubuntu 14.04 with all updates and apt-get xxx
- I installed the Google toolchain arm-eabi-4.8
- I Installed Samsung kernel source for N915F_CIS from here
- I changed the path to the toolchain in Makefile and build_kernel.sh
- I run from kernel source folder: ./build_kernel.sh
- After 10-15 min of compilation I get a zImage file in //output/arch/arm/boot of ~ 9.8 Mb
- Using Android Image Kitchen v2.2 I integrated the zImage into a boot.img to be flashed with cwm
I flashed this new boot.img but the phone is rebooting every minute and in about I have "unknown"as baseband.
Anyone have an idea how to fix this?
Thank you in advance.
Click to expand...
Click to collapse
Wait one more day..
Or maybe earlier
Finally done.
Make backup of your actual kernel, flash the attached zip from post 1in cwm and please report back.I didn't check the init.d support but it should work.
Good, I'll try.
Dev.
Just a small request please.
If you could please make sure a link to YOUR kernel sources in OP.
Any Linux kernel publicly released must have source to compile the exact binary (zImage) as repacked into your distributed boot.img. This must be current at time of every released version.
This is not just a XDA rule, but a legal GPL requirement, applying to all, even if modification is only minor. This is open-source
I would suggest the use of a github repo that helps keep track of your changes (commits), promotes open transparency, sharing and colaboration
If you have any questions on how to go about this, i would be happy to help via pm (but currently away with work), but would suggest to contact our friendly forum Mod.
Best of luck with your project. :thumbup:
Cheers.
UITA
Any chance that you would be willing to make this kernel compatible with the Sprint variety? Man.... I need my viper4android bro. Please. Lol
UpInTheAir said:
Dev.
Just a small request please.
If you could please make sure a link to YOUR kernel sources in OP.
Any Linux kernel publicly released must have source to compile the exact binary (zImage) as repacked into your distributed boot.img. This must be current at time of every released version.
This is not just a XDA rule, but a legal GPL requirement, applying to all, even if modification is only minor. This is open-source
I would suggest the use of a github repo that helps keep track of your changes (commits), promotes open transparency, sharing and colaboration
If you have any questions on how to go about this, i would be happy to help via pm (but currently away with work), but would suggest to contact our friendly forum Mod.
Best of luck with your project. :thumbup:
Cheers.
UITA
Click to expand...
Click to collapse
Thank you for your advices.The link to Samsung kernel source was already there . Anyway, I added it one more time just to be sure that is more visible.
For the github repo, I have to create an account and then I'll upload the files.
Best regards.
Well done mate ..... Yea
---------- Post added at 08:32 AM ---------- Previous post was at 07:36 AM ----------
Boot and works fine , nice one
Can this be used on N915FY as well?
I don't have any reports from N915FY users. You can try and tell us
Don't forget to make a backup first.
starbucks2010 said:
Thank you for your advices.The link to Samsung kernel source was already there . Anyway, I added it one more time just to be sure that is more visible.
For the github repo, I have to create an account and then I'll upload the files.
Best regards.
Click to expand...
Click to collapse
Hey, no problem.
Just to clarify....
If you've made any (even minor) change to "Samsung" source, then you have to upload "your" complete source and link "your" source, not "Samsung" So if you've made the kernel permissive or even use a different toolchain or path, technically you have modified from original and is now "your" source If you use a custom defconfig, don't forget it too
github is well worth the pain I Google for answers all the time (how to do this and that), but still screw things up (sometimes majorly) now and then.
dubart said:
Can this be used on N915FY as well?
Click to expand...
Click to collapse
Using this kernel with a N915FY. Great job btw I can finally use viper audio which I've missed so much. Major props dude!
I'm gonna flash this on sprint variant either that or throw this device out my window
dinaps86 said:
I'm gonna flash this on sprint variant either that or throw this device out my window
Click to expand...
Click to collapse
Lol it booted just no data. Yaaayyy!!!
I see that there are other people who are interested in Selinux permissive kernels.
So, if you want, I can add selinux permissive to any samsung kernel as long as you provide me 2 files: your original kernel (boot.img) from the ROM you want to flash and the Kernel.tar.gz - source kernel from Samsung site. In order to get Kernel.tar.gz file you'll need to download the kernel source file (~ 1Gb) from Samsung site, open the archive and upload ONLY the Kernel.tar.gz (~ 100-150 Mb) and the readme file from the archive to some sharing site. Then, I'll try to compile that kernel for you.
There are also downsides. I cannot stay up to date will all new commits done to the kernel source so I'll compile your kernels only with info that I have at that date. If you fork the github and find kernel source updates, I can add them.
PS. I only set up a working PC with Ubuntu and Google toolchain v4.8. If you find any information that this setup is not suitable for compiling your kernel, then there is no point of providing me the above files.
Best regards.
OP updated with some Antutu screen shots.
After compiling roms for some time now i decided to dabbled in the arts of kernel building and modding.
Ok now i am back and i present you Winxkernel for nougat 7.1.1 stock rom. This time i will be able to continue work and update
this kernel when new sources and patches come out for our device. I have made a new website and I have also created a Google+ community page for this kernel and anything else i decide to work on. please share around. even if you dont like my work, maybe someone else might. i know that i will never be able to create a kernel like the greatest devs eg, yank, nathan, frap and franco, but i will certainly hope to learn from them about anything they have to give and possibly lend a hand.
Here is the download link
XDA:DevDB Information
WinXkernel, Kernel for the Huawei Nexus 6P
Contributors
winxuser
Source Code: https://github.com/winxdroid/kernel_angler
Kernel Special Features:
Version Information
Status: Alpha
Created 2016-08-10
Last Updated 2016-12-30
02/01/17
Update zram, zmalloc and add zpool
updated adreno gpu drivers
added ardreno idler
http://winxdroid.byethost8.com/Nexus-6p.html
30/12/16:
updated linaro to 6.2
added BFQ
couple interactive patches
exfat support
fsync on/off support
latest patches from 3.10 common branch
updated ICE driver
16/12/16:
upstream to latest f2fs updates for 3.10
add saftey net bootloader check (doesnt work with december security patch )
franco sound control
live display driver
removed maple
fixed kcal ( you can now change settings )
01/12/16
add msmhotplug
KCAL driver
fiops scheduler
maple scheduler
f2fs data and cache support
30/11/16
Rebased source to clean angler with 3.10.104
A few camera updates from CAF
16/08/16:
Cleaned up source
Added KCAL support
Added F2FS support
updated linaro toolchains
10/08/16:
Used android-msm-angler-3.10-marshmallow-dr1.6-1 as base
Updated to 3.10.102
Used lastest Linaro GCC 6.1 update
i will add the new security patches in for the next build
Thanks bro
Brokerzhang said:
Thanks bro
Click to expand...
Click to collapse
no worries, this kernel will also be in a rom im going to work on
Thanks.
Will it work on DP5?
leots1234 said:
Thanks.
Will it work on DP5?
Click to expand...
Click to collapse
Don't think so. But you could always try,, make sure you backup your boot partition first.
leots1234 said:
Thanks.
Will it work on DP5?
Click to expand...
Click to collapse
A kernel for M will not work on N due to defconfig changes (camera and some sensors will most likely not work).
Added to Nexus 6P index thread:
[INDEX] Huawei Nexus 6P
Good job mate. Can't wait to try your rom+kernel combo.:silly:
Will have an update in a couple days, not going to be home and I don't have a remote connection to my computer so I can't do it while I'm not home lol.. I have redone the sources so it shows all commits of changes up to 3.10.102, I will add the vulnerabilities patches for the next version and add f2fs support and kcal driver support
Sent from my Nexus 6P using XDA-Developers mobile app
winxuser said:
Will have an update in a couple days, not going to be home and I don't have a remote connection to my computer so I can't do it while I'm not home lol.. I have redone the sources so it shows all commits of changes up to 3.10.102, I will add the vulnerabilities patches for the next version and add f2fs support and kcal driver support
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
kernel updated guys, if there is anything you want in this kernel let me know and ill try and add it
someone who has my kernel installed, or can quickly install it can you scan for vulnerabilities please, I know I patched one, just need to know the others. I'm not home and won't be for a fair few hours, and I'm currently running N and not M
Sent from my Nexus 6P using XDA-Developers mobile app
Hey winxuser, I see that you have moved on from the i9305. Have fun with the 6p, and N!
P.S. Why were you inactive for so long?
limjh16 said:
Hey winxuser, I see that you have moved on from the i9305. Have fun with the 6p, and N!
P.S. Why were you inactive for so long?
Click to expand...
Click to collapse
Yeah I moved away from the i9305 when my phone stopped working and I got my 6p.. and there wasn't much more I could do, I'm not that great of a developer to have been able to completely fix the radio issue. I know the radio issue is kinda fixed but I think that's a big dirty hack to use cm12.1 as a radio backup for radio to work... I have been active since but no one really needed me anymore over there..
Sent from my Nexus 6P using XDA-Developers mobile app
hey guys im back, after some time of just trying out other things which has made me frustrated hahaha.
so i am back with a new kernel for N dev preview 7.1.1 only, im currently on dev preview 2 and its working well. i have also finally after a long time created a new website for my development, and i have also created a google+ community which is here https://plus.google.com/communities/101442640267768818970
Very nice website. Trying out the nougat build right now.
Can someone please tell me how can I change to f2fs on dp2 ?!
NOTilyass said:
Can someone please tell me how can I change to f2fs on dp2 ?!
Click to expand...
Click to collapse
The New kernel doesn't support f2fs just yet, will add it in to the next version
NOTilyass said:
Can someone please tell me how can I change to f2fs on dp2 ?!
Click to expand...
Click to collapse
F2fs make a difference on the 6P? Only tried it on the OnePlus One.
The good stuff: https://github.com/jcadduono/android_kernel_lge_msm8996/commits/android-7.0
Fork it!
Update: CAF branch has some problems at the moment, use this one instead for now.
So this is currently the v10d release. It's compatible with V20 Nougat v10d and G5 v20a.
Place toolchain (pick one up from here) in ~/build/toolchain & tar xf.
git clone https://[email protected]/yourname/android_kernel_lge_msm8996.git
If you want to change any config options:
./menuconfig.sh (optional target, ex. twrp or lge)
Ready?
./build.sh h850/h830/h918/us996/any model you want
Models are applied onto the target base defconfig, so your V20 kernels will build for all V20 variants and for all variants of the G5 as well.
Create your own by copying arch/arm64/configs/lge_defconfig to arch/arm64/configs/your-awesome_defconfig!
Grab:
build/arch/arm64/boot/Image.lz4-dtb [or] build/arch/arm64/boot/Image.gz-dtb
build/lib/modules
Place in:
https://github.com/jcadduono/lazyflasher/tree/kernel-flasher
make
You got yourself a magical all-powerful custom kernel installer, complete with your own custom kernel!
Notice that there's a few branches:
opensource is where I merge LG changes, when it's updated, android-7.0 is rebased on it
android-7.0 is a starting off point closest to absolute stock, base off here
android-7.0-security adds security and bug fixes from CAF on top of android-7.0 branch
twrp-7.0 is for Team Win Recovery Project (yes, it's ready, come with an unlocked device and I'll give it to you)
nethunter-7.0 is for the Kali NetHunter project (if you dare, some fun there)
Another issue was their weird build system, I dropped that. Replaced tuxera's exFAT prebuilt downloader with Samsung's GPL'd exFAT drivers instead. Unsure how well it works replacing it like that, we'll have to see.
I also added Qualcomm's Core Control which they just released the sources to somewhat recently. I believe it's already included on the G5 and probably V20 as a kernel module. Their released version doesn't have module support yet but it's fairly easy to add I guess with the leaked proprietary module version out there to pick pieces from.
Have fun!
Great Man !
thanks for this..
I've been following the root process since the beginning and I'm amazed at the relatively short amount of time it took. Huge kudos to @jcadduono! I will purchase this phone. Now, since the kernel needed to have it's encryption support modifed, are the patches added to a branch on your Github fork? I would like to compile a custom kernel, along with patching it with SultanXDA's SafetyNet boot bypass. Which branch will be appropiate to fork to flash on the TWRP/Rooted V20?
Thanks much @jcadduono! I'm going to start poking around in here and see if I can find anything particularly interesting.
zabracks said:
Thanks much @jcadduono! I'm going to start poking around in here and see if I can find anything particularly interesting.
Click to expand...
Click to collapse
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
jcadduono said:
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
Click to expand...
Click to collapse
I've got an H918, if you need somebody to test a kernel.
jcadduono said:
Hey guys so I did get a kernel booting but not yet one built from CAF sources so it'll take a bit of work to figure out why.
There seems to be a couple occurrences of null pointer dereferences in early boot stage in both stock release and this CAF. Currently investigating (or trying to anyway, it's hard to find people that can flash my test builds and report back with logs - I do not own this phone)
Click to expand...
Click to collapse
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
albinoman887 said:
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
Click to expand...
Click to collapse
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
jcadduono said:
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
Click to expand...
Click to collapse
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
jcadduono said:
I can compile it and flash it. There seems to be an issue with the sources LG has provided regarding display drivers. It seems any attempts at a stock kernel build results in a messed up screen once you hit the lock screen. I assume this has something to do with 2D graphics firmware and kernel framebuffer driver badly interacting. These sources are for v10b firmware, while the device appears to ship with v10d. I don't know if LG made any changes since then that could have caused this issue.
FYI the sources up right now are not my CAF merge, I had to move it to (same url but with -caf on the end) - I still have some issues to work out with the CAF merged sources (they aren't booting for whatever reason - not even TWRP).
It could take me a while to work on this as I still don't and likely never will own this device due to my lack of trust when it comes to LG.
Click to expand...
Click to collapse
which branch/repo is the one that boots but messed up display?
albinoman887 said:
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
Click to expand...
Click to collapse
Would absolutely LOVE to see CM on our phones! Not that it'll make things move faster, but I'll throw 100 bucks your way if it's done before Christmas
lightninbug said:
Would absolutely LOVE to see CM on our phones! Not that it'll make things move faster, but I'll throw 100 bucks your way if it's done before Christmas
Click to expand...
Click to collapse
I want Nethunter too
I'll be around to test any of the stuff, usually at night.
The v20 kernel is available on the lg open-source site, at least the h990 one is.
Sent from my LG-H990 using Tapatalk
---------- Post added at 03:36 PM ---------- Previous post was at 03:25 PM ----------
Artcrime said:
The v20 kernel is available on the lg open-source site, at least the h990 one is.
Sent from my LG-H990 using Tapatalk
Click to expand...
Click to collapse
There is v10d version for 918. opensource.lge.com forgive me if this is old news. a|c
albinoman887 said:
sounds like the kgsl drivers. If you want we can work together on this. I want to get CM going too i just need some help. Im and experienced dev but havent jumped in the LG pool before. id look at the google pixel kernel source and grab the kgsl/adreno crap and update that.
i'll clone the source and check it out since i'm finally getting the stock rom downloaded (thanks for the wget tip)
Click to expand...
Click to collapse
slayerh4x said:
I want Nethunter too
I'll be around to test any of the stuff, usually at night.
Click to expand...
Click to collapse
albinoman887 said:
two things. Did you figure out how to compile boot.img or are you flashing the zimage? also hit me up on hangouts I've been wanting to dive into this device just looking for someone else to colaberate with.
EDIT: sent email in PM
Click to expand...
Click to collapse
Sent from my LG-H990 using Tapatalk
I updated all the branches earlier today...should work fine now, so apparently was a source code issue that needed v10d update, not sure though no one's volunteered for testing (I don't do requests/testing over the forum, only on IRC)
Is a kernel the main thing stopping us from a CM rom?
what toolchain should we be using? got a link to a compiled one? i'm getting build errors I know are related to the toolchain but i've been out of the game for awhile. last i knew we needed gcc-4.9?
jcadduono said:
I updated all the branches earlier today...should work fine now, so apparently was a source code issue that needed v10d update, not sure though no one's volunteered for testing (I don't do requests/testing over the forum, only on IRC)
Click to expand...
Click to collapse
I'm there.
albinoman887 said:
what toolchain should we be using? got a link to a compiled one? i'm getting build errors I know are related to the toolchain but i've been out of the game for awhile. last i knew we needed gcc-4.9?
Click to expand...
Click to collapse
gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu.tar.xz .Be sure to change the PATH in menuconfig.sh
@jcadduono , thank you. You are truly an inspiration
Wondering if anyone can help me learn how to do this right...
So I was able to compile the kernel, but I didn't get an Image.gz (which im sure is fine). I did get an Image.lz4, Image.lz4-dtb, and Image (no extension). I figure only the .lz4* files are needed. I added all 3 to the lazyflasher, and ran make. The resulting zip flashed, but sent me straight to Bootloader. I then tried to fix by flashing the stock kernel, but this still did not boot. ReFlashed my ROM and it's booting now.
I used this toolchain gcc-linaro-5.3.1-2016.05-x86_64_aarch64-linux-gnu
Any guidance? My guess is it's flashing at the wrong point?
Here is the ZIP. DO NOT FLASH. This is only for someone who knows what they are looking at to tell me what is wrong with it. No modifications were done. Source was forked from OP, and compiled with default menuconfig, then build.sh h918
TitanX Kernel​Hi XDA, here is the TitanX standalone kernel, this is my build and version. Joe's is in all of his roms that he compiles.
This kernel is compiled with Clang 7.0 from Dragon TC and GCC 7 linaro
Feature List (to save space): https://docs.google.com/document/d/1tA9uth8Y8yQMliwocKRy2Qx2lJmvk7RiimoCLiASNVs/edit?usp=sharing
Changelog (to save space): https://docs.google.com/document/d/1UvNirSLUZQ2vfP_m8DGf7wp6VCKDDHhU2klDBOOczNw/edit?usp=sharing
Update Schedule
Stable builds will be released every week if possible
I will be making a test build, but it's on a different website linked here
All new kernels posted on kernel.org will be merged in and pushed 24 hours afterwards
Download link
https://drive.google.com/open?id=1-vY5nZoIp-doytF7Yi5nFij2PZLktve4
Sources
https://github.com/TitanOsRom/los_marlin_titanx
Mods, Do not clean this thread, I like any discussion in forums. Feel free to suggest features as needed
Thanks for your work but does this kernel support Android P DP3? Really want to give it a try.
Queentus said:
Thanks for your work but does this kernel support Android P DP3? Really want to give it a try.
Click to expand...
Click to collapse
I believe that it should work, but the official commits are not in the kernel. I have tried it on DP3 and it worked well, give it a go!
do it work on the sailfish too?
Sh0X31 said:
do it work on the sailfish too?
Click to expand...
Click to collapse
Yes it does
The testing branch has been updated and merged with P. Stable version of this will be released on Tuesday. Feel free to check it out on the link in the OP.
Great kernel so far, the GPU OC seems to do wonders (unless it's some other tweaks/mods).
Found one bug, I can't change vibration strength (this is using EX Kernel Manager).
I don't believe vibration control is added, but I will work on it. Also there is a poll to see which kernel base we should use, I am using lineage right now
Delete
Mods, please close this thread as this branch is no longer in development, it is replaced by KingKernel