Develop Bugs

[Q] Compile kernel

I thought of developing a kernel so that i can use it with my CM11 that im going to port shortly. I thought I'll compile the stock kernel from source itself. I use android pre-built tool chain (arm-eabi-4.6)
I get a lot of compiler errors on stock kernel without any modifications itself...
Do i need to change my tool chain?
Sent from my One V using XDA Free mobile app

I never tried to build the stock kernel, but I think they did it with the android 4.0 toolchain.
To run CM, you need a CM-Kernel. You have to port things from the stock or a custom kernel (like Hellboy by maxwen) to the cm11 kernel.
Try to use rastomanchiks kernel sources (https://github.com/rastomanchik/android_kernel_htc_primou). This kernel is mostly working, stable and has a good battery life now.
I'd also like to build cm11, but my download speed is to slow to download the sources.

Exactly. Even my download speed is slow. And i have a cap also. After 8GB, my download speed drastically decreases. It takes ages to sync the sources...
Sent from my One V using XDA Free mobile app

How different is Cm kernel from stock? I mean what changes should i make?
Sent from my One V using XDA Free mobile app

Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.

Help
jonas2790 said:
Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.
Click to expand...
Click to collapse
Yeah. How do I port?
What happened to your CM12 project?

hehaichi said:
Yeah. How do I port?
What happened to your CM12 project?
Click to expand...
Click to collapse
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.

jonas2790 said:
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.
Click to expand...
Click to collapse
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!

hehaichi said:
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!
Click to expand...
Click to collapse
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.

jonas2790 said:
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.
Click to expand...
Click to collapse
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?

hehaichi said:
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?
Click to expand...
Click to collapse
Yes you can use a prebuilt kernel, but it will only work if the kernel supports you cm version.
You apply patches to a kernel by changing files or directories in the kernel. For example you can use another fs module (maybe with more functions) by copy and pasting the folder for the module from another kernel. The problem is, the new module may require some functions your kernel does not have so it won't compile.

Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V

hehaichi said:
Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V
Click to expand...
Click to collapse
1. It would be much, much, much work.
2. I think there are some device-specific drivers that only work with 3.0

I'm ready to do that work only if i knew how to...
Sent from my One V

hehaichi said:
I'm ready to do that work only if i knew how to...
Sent from my One V
Click to expand...
Click to collapse
Try to get into it yourself or talk with people who know about kernel developement, I'm also new to android developement.

[DISCUSSIONS][TESTING][ROM][UNOFFICIAL] CyanogenMod 13 ALPHA Build

This is a test build I take no responsibility for what this may or may not do to your device.
Click to expand...
Click to collapse
NEED TESTERS
currently i don't have the device to test i will be getting my device in the next week .
Click to expand...
Click to collapse
1. Install CWM Recovery
2. Do Full Wipe If coming from another ROM
3. Flash ROM
4. Flash Google Apps (my recommendation is to install minipal gapps due to /system partition size limits)
5. Reboot
Click to expand...
Click to collapse
]Not Booting
Click to expand...
Click to collapse
Code:
[B]Source[/B]
Here are the device tree :
Device Tree (from cm13 Nexus 9) : https://github.com/vickdu31/android_device_xiaomi_mocha
Kernel Tree (from Xiaomi KK) : https://github.com/vickdu31/android_kernel_xiaomi_mocha
Vendor Tree (old Xiaomi KK) : https://github.com/vickdu31/android_vendor_xiaomi_mocha
Thank you
@faust93 for cwm
XDA:DevDB Information
CM-13, ROM for the Xiaomi Mi Pad
Contributors
Rohit99, tank0412, vickdu31
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-12-10
Last Updated 2016-12-13

Reserved

Edit 1:initial build didn't boot for me, no adb can't get log

Ok im gonna try it.
If you want, i can leave logcat for you

OoSTARTERoO said:
Ok im gonna try it.
If you want, i can leave logcat for you
Click to expand...
Click to collapse
Can get logcat? Try please.

Ofc, it doesn't boot. And don't create threads without testing.

Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
unfortunately....I couldn't get logcat too...

Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
we can't get logcat. It doesn't boot, i mean there are problems with kernel or init scripts or both. Kernel needs patches.

Nihhaar said:
Ofc, it doesn't boot.
Click to expand...
Click to collapse
As I thought

Prebuilt kernel from cm11
Sudeep Duhoon said:
As I thought
Click to expand...
Click to collapse
hey can i use prebuilt kernel from cm11 source @Nihhaar

Rohit99 said:
hey can i use prebuilt kernel from cm11 source @Nihhaar
Click to expand...
Click to collapse
Always try to build kernel with source. I think you can't, but you can try.

Please edit the link in OP, its me who miswrote it... : /android_device_xioami_mocha --> /android_device_xiaomi_mocha

You need to fix up SELinux and the init scripts. Taking a shield tablet device tree, renaming things to mocha and changing the fstab isn't enough. As far as I can tell the shieldtablet device tree also has dependency on a shield common tree. There's also no value in creating a new thread each time you push new commits
Our kernel from Xiaomi is also pretty useless without commit history. The device tree is also from shield tablet, not Nexus 9.
We also have a tree for building TWRP with OmniROM that you can compile TWRP 3.0.2.0 with.

What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?

highwaystar_ru said:
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
Click to expand...
Click to collapse
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10

Harrynowl said:
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Click to expand...
Click to collapse
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.

highwaystar_ru said:
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
Click to expand...
Click to collapse
Untested, been doing device bring up. That kernel won't work yet anyway it's missing atmel, synaptic and battery firmware. (Plus the code that goes with it)
Some devs have one that gets to recovery but only 1 CPU core can come online and the CPU gets a bit hot. Unfortunately their commit history is hard to follow so I've not had a proper look at it yet

My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.

drakonizer said:
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
Click to expand...
Click to collapse
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.

Harrynowl said:
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Click to expand...
Click to collapse
Oh! I didn't realize we were talking about the same person/team. I'd love to start developing for this device. In fact, I'm working on KEXEC-hardboot and Multirom right now, but I'd like to follow what you guys are doing and contribute as much as I can. Is there an IRC channel/IM app you guys use for communication? If so, I'd appreciate it if you could PM the info.

Making a CAF based rom.

Alright so I've built and modified both LOS and RR a bit and it went pretty well. Tutorials o'plenty when it comes to building those roms.
However I now want to try and build a rom from scratch and I'd like to base it on CAF.
I've *I think* correctly synced up with the latest msm8996 tag, but I may have ****ed that up as well.
My problem is is that I literally can not find any resource for building with CAF sources, and I can't even find my local_manifests/roomservice, so I have no idea where to start.
If any of you have any resources or want to share a bit of your knowledge it would be greatly appreciated.
Thanks.

Anyone?

Hey, check out AOSP-CAF(https://github.com/AOSP-CAF). This is all you'll ever need and it's updated regularly. The dev has already added all the necessary stuff(HALS) and also has CM's build system so all you need to do is fork some device tree , sync it's dependencies and you should be good to go.

INT3NSE07 said:
Hey, check out AOSP-CAF(https://github.com/AOSP-CAF). This is all you'll ever need and it's updated regularly. The dev has already added all the necessary stuff(HALS) and also has CM's build system so all you need to do is fork some device tree , sync it's dependencies and you should be good to go.
Click to expand...
Click to collapse
Thanks! I've synced up with it and also synced with the OnePlusOSS device tree. The builds are failing however because the pull_library.sh script they give doesn't work anymore. Is there another device tree you would recommend? And how could I go about finding the dependencies?
Thanks for your help

GPL Source Request

Hi all,
I've created an issue on Motorola's kernel-msm repo that is a request for them to release the kernel sources for the G 5 Plus (Potter).
The post is here - https://github.com/MotorolaMobilityLLC/kernel-msm/issues/104
Please feel free to reply with similar requests so as to get Motorola moving on a proper GPL source release.
-Rob

bob2600 said:
Hi all,
I've created an issue on Motorola's kernel-msm repo that is a request for them to release the kernel sources for the G 5 Plus (Potter).
The post is here - https://github.com/MotorolaMobilityLLC/kernel-msm/issues/104
Please feel free to reply with similar requests so as to get Motorola moving on a proper GPL source release.
-Rob
Click to expand...
Click to collapse
https://github.com/MotorolaMobilityLLC/kernel-msm/blob/MMI-NPN25.137-15/arch/arm/configs/ext_config/mot8953-potter.config
:good:

The sources are already out....

Oh really? My bad... Can I just pull from that kernel-msm repo mentioned in the original post? Or is there a different repo just for Potter?

It looks like the source release for NPN25.137-15 is tagged here:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/MMI-NPN25.137-15/
It's a bit older than the version shipped with my phone but it could work. I'm going to see if I can compile it later.

bob2600 said:
It looks like the source release for NPN25.137-15 is tagged here:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/MMI-NPN25.137-15/
It's a bit older than the version shipped with my phone but it could work. I'm going to see if I can compile it later.
Click to expand...
Click to collapse
All the best. :good:

rayzen6 said:
All the best. :good:
Click to expand...
Click to collapse
Why'd you edit your post? I took a look at Alberto's repo and it looks like it would be compatible with our phones.
Seemed like a decent course of action to take. Did you try it yourself? Did it work? Don't just provide no reason, let's get hacking...

bob2600 said:
Why'd you edit your post? I took a look at Alberto's repo and it looks like it would be compatible with our phones.
Seemed like a decent course of action to take. Did you try it yourself? Did it work? Don't just provide no reason, let's get hacking...
Click to expand...
Click to collapse
Man yes let me mention the guy who successfully ​able to build with Alberto's sources. He is @i.snehal.kiran.
He has done this to compile but unfortunately for some reason he doesn't able to get the device to test. His msg is below
basically i have taken addison device tree ...just change the kernel path and defconfig name in boradconfig.mk ..makes it build boot.img
the source provided by motorola on github is full of errors..so use alberto's kernel for addison till you get official kernel from moto
https://github.com/Alberto97/android_kernel_motorola_msm8953
I edited the post bcz I thought u want to work with custom kernel for stock rom. And I thought this might not be useful.

bob2600 said:
Why'd you edit your post? I took a look at Alberto's repo and it looks like it would be compatible with our phones.
Seemed like a decent course of action to take. Did you try it yourself? Did it work? Don't just provide no reason, let's get hacking...
Click to expand...
Click to collapse
So what happened next? Did you tried something?
Edit:- btw one of the guy has replied positively on issue. :Good: I think we'll have a separate source soon.

rayzen6 said:
So what happened next? Did you tried something?
Edit:- btw one of the guy has replied positively on issue. :Good: I think we'll have a separate source soon.
Click to expand...
Click to collapse
I got as far as getting the LineageOS sources pulled for 14.1, had to do it twice since it was too big for my home directory so I had to create a new volume and run repo sync again. Took forever, but at least I have the OS sources downloaded. Now we're at the point of getting that kernel and setting up a device configuration for our device. Once we get that, then I can see if we can build and flash.

bob2600 said:
I got as far as getting the LineageOS sources pulled for 14.1, had to do it twice since it was too big for my home directory so I had to create a new volume and run repo sync again. Took forever, but at least I have the OS sources downloaded. Now we're at the point of getting that kernel and setting up a device configuration for our device. Once we get that, then I can see if we can build and flash.
Click to expand...
Click to collapse
Cool. Good work man. I'm in for testing.

Kernel sources are up
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPN25.137-33

[REFERENCE] [OOS/CUSTOM] OnePlus 5 kernel source with linux-stable (4.4.162)

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 4.4.78 on OOS and 4.4.100 on Lineage while the current version upstream is 4.4.162 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/op5
There are three branches, one for OxygenOS 8.0 stable, one for OyxgenOS 8.1 beta, and one for Lineage 15.1.
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).

From what I understand, you're creating a space where you're updating the stock Kernel to the latest Linux tags and creating a clean base that others can develop upon for a consistently updated kernel?
Seems to me like the epitome of a community project and in keeping with the heart behind open source.
Great work Nathan!!!
Sent from my OnePlus 5 using XDA Labs

rav101 said:
From what I understand, you're creating a space where you're updating the stock Kernel to the latest Linux tags and creating a clean base that others can develop upon for a consistently updated kernel?
Seems to me like the epitome of a community project and in keeping with the heart behind open source.
Great work Nathan!!!
Sent from my OnePlus 5 using XDA Labs
Click to expand...
Click to collapse
Exactly correct I have seen others grab my kernel and base their work upon (which I have zero issues with) but I know most do it because I've merged linux-stable as one of my first things. Figured I would make their lives easier (plus doing the conflict resolution summaries helped me validate my own work). I am mulling over posting these to the mailing lists so other mainline Linux developers with these devices can easily test new builds and get the latest fixes without needing to do the work themselves (even if they are fully capable).

nathanchance said:
Exactly correct I have seen others grab my kernel and base their work upon (which I have zero issues with) but I know most do it because I've merged linux-stable as one of my first things. Figured I would make their lives easier (plus doing the conflict resolution summaries helped me validate my own work). I am mulling over posting these to the mailing lists so other mainline Linux developers with these devices can easily test new builds and get the latest fixes without needing to do the work themselves (even if they are fully capable).
Click to expand...
Click to collapse
If you're doing the work anyway and it's just a simple push to mailing list then might as well. Others can choose whether to use it or not but at least it's there. :good:
Sent from my OnePlus 5 using XDA Labs

where to download the link?

Gayrat1999 said:
where to download the link?
Click to expand...
Click to collapse
This isn't a kernel you flash, this is something for developers to use in their own work. For example, my kernel Flash already has all of this, which you can flash.

Nice. How about GCC error fixes and wifi stack driver in this base?

neobuddy89 said:
Nice. How about GCC error fixes and wifi stack driver in this base?
Click to expand...
Click to collapse
I toyed with the idea of doing two branches (one for building, one for usability) but decided against it as 1. I want this source to be as plain as possible and 2. It doesn't fully fit with the idea of this project. This purely to help developers get up and running with linux-stable, not a fully fledged custom kernel. I will consider adding the GCC fixes to the usability README though, that could be useful.

You are a true asset to this community!

4.4.103 has been merged in, with conflict notes updated accordingly.

Oh boy oh boy it might be time for a rebase for me

4.4.104 has been merged in, with conflict notes updated accordingly.

I truly apologize to anyone who was tracking the tree because I just force pushed. I decided to update the location and branch name and wanted everything to be consistent. It is now up to date with 4.4.105.
I have updated the OP with the notes and tree location. The new notes are on the staging branch right now, they will be merged into master once everything is finalized.

I'm sorry being out off topic, but can i use this https://github.com/android-linux-stable/msm-3.18 kernel source as base for my soc (msm8937) sir?

zainifame said:
I'm sorry being out off topic, but can i use this https://github.com/android-linux-stable/msm-3.18 kernel source as base for my soc (msm8937) sir?
Click to expand...
Click to collapse
Most likely yes. For the future, this thread is geared towards the generic CAF trees (msm-3.18 and msm-4.4). Feel free to ask me anything over there.

4.4.106 has been merged in (conflict notes).

4.4.107 has been merged in.

4.4.108 has been merged in.

4.4.109 has been merged in (conflict notes).

4.4.110 has been merged in (conflict notes).