I'm going to create altenative for CM10.1 kernel.
SImply I would add WM1811 improvements, make minor OC and UV, add ROW iosched and compile with good toolchain.
However I can't just cherry-pick commits, because this isn't possible, so I to do many things on my self.
I have some questions for expericied devs.
How to target android_kernel_samsung_smdk4210 for i9300?
Where I should put propietary binaries?
Which voltage table (struct) I should modify?
Can I simply merge some commits from perseus, siyah with one click?
Will BFS and UKMS give boost to android (They did on PC)?
Can I just run patch -p1 row.patch to add row?
I'm not very familiar with linux and C++, I prefer windows and C# in most cases.
there's a link to the developers' section in the section list
Can moderator move thread to devs forum?
I think it's prohibited to duplicate threads
you hit the yellow triangle and ask
Hello friends
last days i'd successfully compiled kernel for GT-N7100 and its work great
added cpu governor
1-but how can compile new gpu driver and use it in kernel?
2-how can identify hardwares to use different driver like wlan?
3-some kernel have extra features like changing gpu freq.how?
Thank you
juan503 said:
Hello friends
last days i'd successfully compiled kernel for GT-N7100 and its work great
added cpu governor
1-but how can compile new gpu driver and use it in kernel?
2-how can identify hardwares to use different driver like wlan?
3-some kernel have extra features like changing gpu freq.how?
Thank you
Click to expand...
Click to collapse
Hi @juan503.
Congrats on your working kernel!
Since we here at XDA Assist merely point you in the right direction, we do not provide tech support; I cannot answer all your questions.
There is however quite a few threads on how to add features to a kernel, and what you don't find in them you can ask there.
Check these out:
Adding features to your kernel - XDA University
[GUIDE] How to compile kernel EASIEST WAY + add features + useful tools
Good luck on your development!
Can someone tell me how to add SmartassV2 to kernel.
I dont know much but i think you have to add it to your kernel source before compiling. Not sure though
Hit thanks if helped
You will have to find the source for the specific governor type, then you will have to add it to your kernel source, then compile it. I'm not a kernel dev but this is probably the approach to it. There are plenty of tutorials that should help you.
This is a build of Ziyan and friend's 3.4 kernel(against their will), optimized for release. Absolutely no debugging features allowed.
Ipv6 and complex adb functions broken.
Graphical Stuttering fixed.
Ubertc4.9.4 (Until I setup 6.0)
Latest F2FS sources. This F2FS is newer than everyone elses. Kanged from KHAON.
Brought up from 3.4.67 to 3.4.110.
Selinux disabled.
Optimized to all hell. Ofast probably regressed performance below that of O2 but Ofast makes people smile so whatever. It's smooth is all I have to say.
Works with any rom.
Mod Edit
Rolling release kernel, no versions. To report bugs tell me the hash, date, or build # of the kernel you have issues with.
Want a feature? Tell me to include it. I'm too lazy to do it? Fork my source and build it then post a link to your sources and I'll include it in the OP if it's good. This project is driven by and for the community.
Sources: Mod Edit
Brought to you by Ziyan, htcdreamon, sheffzor, khaon, eliminater74, coderzs, and me lgrootnoob. Linus Torvalds is a dong, yo.
Thread closed.
Please respect the code originator's polite request in future.
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 either 3.18.66 (OxygenOS) or 3.18.71 (LineageOS and most likely all other custom ROMs) 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/op3
There are three branches: one for OxygenOS stable, one for OxygenOS 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).
hmm this helps a lot bro. Thanks for opening this thread. So, here comes my first question - how can we make a kernal compatible with most of the Oreo roms which we have at present like nos, Z, Pixel, Aosip or omni or others as they all use different.
mady51 said:
hmm this helps a lot bro. Thanks for opening this thread. So, here comes my first question - how can we make a kernal compatible with most of the Oreo roms which we have at present like nos, Z, Pixel, Aosip or omni or others as they all use different.
Click to expand...
Click to collapse
Well that's not exactly a topic for this thread but it depends on what makes them different. Some things can co-exist, others can't. I know that's a generic response but I don't really have anything more descriptive I can give.
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
v3.18.96
https://github.com/nvertigo/android_kernel_oneplus_msm8996/tree/linux-stable/merge-15.1
This is current lineageos/lineage-15.1 merged with https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tag/?h=v3.18.96.
3.18.96 has been merged in.
nathanchance said:
3.18.96 has been merged in.
Click to expand...
Click to collapse
Sir! it's a flashable kernel for 1+3T?
acultr said:
Sir! it's a flashable kernel for 1+3T?
Click to expand...
Click to collapse
Umm.. no. Might wanna read a bit more before asking. It's just the kernel sources.
acultr said:
Sir! it's a flashable kernel for 1+3T?
Click to expand...
Click to collapse
No, it's for peoples who want build upstreamed kernel, like sources to build.
3.18.97 has been merged in.
3.18.98 has been merged in.
My apologies to the custom ROM users for breaking MTP and adb many thanks to @martinusbe and @nvertigo67 for reporting the issue to me and helping me fix it! The change has been pushed, please pull to update!
https://github.com/android-linux-stable/op3/commit/180f737979e7f81b7e650fbff11dcc437d358142
nathanchance said:
My apologies to the custom ROM users for breaking MTP and adb many thanks to @martinusbe and @nvertigo67 for reporting the issue to me and helping me fix it! The change has been pushed, please pull to update!
https://github.com/android-linux-stable/op3/commit/180f737979e7f81b7e650fbff11dcc437d358142
Click to expand...
Click to collapse
No reason to apologies. Thanx to you and @martinusbe for fixing this. Without you I would still search in ffs commits...
nathanchance said:
My apologies to the custom ROM users for breaking MTP and adb many thanks to @martinusbe and @nvertigo67 for reporting the issue to me and helping me fix it! The change has been pushed, please pull to update!
https://github.com/android-linux-stable/op3/commit/180f737979e7f81b7e650fbff11dcc437d358142
Click to expand...
Click to collapse
Yay its fixed. I'm sure people against upstreaming will use this as an argument to say upstreaming is bad. I'm not a dev so I really have no idea what's right. In my book, higher version = good lol xD
knpk13 said:
Yay its fixed. I'm sure people against upstreaming will use this as an argument to say upstreaming is bad. I'm not a dev so I really have no idea what's right. In my book, higher version = good lol xD
Click to expand...
Click to collapse
Well it wasn't stable that broke this, it was a CAF merge I still should have dug deeper into the conflict, I definitely rushed it. I don't do that with the stable merges.
3.18.99 has been merged in.
3.18.100 has been merged in.