Hey Guys,
Ok so here is my situation.
I have a really old HTC Kernel that is lacking way behind in commits. Due to this, this is why LineageOS 14.1 is failing to build. Of course I could use a ugly hack and apply the commits manually of the Android Source that requires them but this is quite a ugly hack.
This is how the kernel looks like right now.
CAF Kernel from Dec, 2014 + Code removed ( like comments) by HTC + HTC Open Source Software
I want to go back to "CAF Kernel from Dec, 2014", Apply all of the Latest Commits and then apply the "HTC Open Source Software" on top of the Kernel.
What is the best way to do this, If I merge the Kernel, I have a ton of Conflicts and that isn't really efficient, pretty much the whole kernel is a conflict with extra new files added.
I think the best thing to do is to port the device to the normal android_kernel_cyanogen_msm8916 (because it is a Snapdragon 410 Phone) but I don't know how to do this and don't think it will work because it is missing HTC Features in the Kernel.
The latest source from the last device maintainer is here:
https://github.com/PatrikKT/android_kernel_htc_a31ul/commits/cm-12.1
https://github.com/HTC-MSM8916/android_kernel_htc_msm8916/commits/cm-13.0
I am the next Device Maintainer, hopefully.....
What is XenonHD?
XenonHD is a custom firmware aka ROM for various Android devices. It is based on LineageOS 15.0 with additional features, performance and battery life improvements.
The idea behind XenonHD is to give users a ROM that is "blazing fast, rock stable and buttery smooth".
MAIN FEATURES :
XenonHD Changelog
NovaLauncher, Adaway, Kernel Adiutor, SuperSU
Root, adb, dev options, advanced reboot & installing apks enabled by default
Pixel UI, Pixel Navbar + Animation, Wallpaper
Material sounds & icons
Day/Night theme
Network indicator & battery bar in status bar
Live Volume Steps
DT2S on lockscreen
Custom Quick Settings Tiles
Removed unnecessary things
Under the hood improvements and optimizations
...and more on the way!
BUG :
Volte
HOW TO FLASH
Install latest TWRP recovery on your device.
Make a backup of your current ROM.
Wipe system, data, cache and dalvik.
Flash ROM.zip and Googleapps.zip.
Reboot system and setup!
Download :https://drive.google.com/file/d/0B72tZGCxrlDicjJHWG0wV3VLdWM/view?usp=sharing
CREDITS
Team Horizon and Xenon HD Team for the rom source
@[email protected]
XDA:DevDB Information
[Unoffical] Xenon-Hd Android 8 Build, ROM for the Xiaomi Redmi Note 4
Contributors
ZH_Alone
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: Lineage
Version Information
Status: Beta
Current Beta Version: V 1.0
Beta Release Date: 2017-10-07
Created 2017-10-07
Last Updated 2017-10-07
Thanks for your work. Definitely going to test it now. Just one thing : you forgot to add a space after the ":" so the link is not clickable
Remove it please. We didn't allow to release oreo builds and mido will be officially supported anyway
dadi11 said:
Remove it please. We didn't allow to release oreo builds and mido will be officially supported anyway
Click to expand...
Click to collapse
thanks for sharing but please remove it. if anyone is to build oreo based xenon hd, it' s @dadi11 not you or anyone else. He is the official maintainer and developer and no one builds it better than he does. So, keep it for yourself and delete your post please.
Wait so bug is only Volte??
How about goodix fp???
jack_hunter97 said:
Wait so bug is only Volte??
How about goodix fp???
Click to expand...
Click to collapse
Please read #3 : https://forum.xda-developers.com/showpost.php?p=74067496&postcount=3
No link?
Thread closed
First NO placeholders are allowed. All ROM threads must have a download link at time of posting
Second always seek permission to build and post someone else's work as per rule 12 the developer can request take down:
12. Sharing
XDA-Developers is based on the principle of sharing to transmit knowledge. This is the cornerstone of our site. Our members and developers freely share their experience, knowledge, and finished works with the rest of the community to promote growth within the developer community, and to encourage those still learning to become better. There are those, however, who take advantage of this model and try to make personal gains from the hard work of others.
In order to preserve the delicate balance between sharing for the good of the community and blatant self-promotion, regular members and developers alike must understand (and agree) to the following:
12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;
12.2. Courtesy - While most of the work released on our site falls under the umbrella of open source, that is not the only license model being used by developers on xda-developers. In order to prevent problems, we ask that if you decide to base your work on someone else's that you check the license model being used (as it might not be as permissive as one may think);
12.3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Dev Relations team (listed below) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
12.4. Developers can issue take down requests (by contacting the Dev Relations team) under the following circumstances:
- in-process builds start showing up on forums when the developer is not yet ready to release the work;
- cases in which another developer is too aggressively soliciting donations or misrepresenting the work (kanging);
- unofficial builds where an official build is already available;
In summary, we want people to have access to work and knowledge alike. Sharing is good and courtesy and ethics go a long way.
Developers with questions, comments, complaints, or concerns about our rules (or anything!) should send a PM to our Dev Relations team (efrant or sykopompos) or to a Moderator. We are here to help!
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.
INTRODUCTION:
The kernel is a computer program at the core of a computer's operating system with complete control over everything in the system. It is an integral part of any operating system. It is the "portion of the operating system code that is always resident in memory". It facilitates interactions between hardware and software components. On most systems, it is one of the first programs loaded on startup (after the bootloader). It handles the rest of startup as well as input/output requests from software, translating them into data-processing instructions for the central processing unit. It handles memory and peripherals like keyboards, monitors, printers, and speakers. In Android It is very important.
STORY:
As 'LYF' OEM has not released kernel source for the phone and never will. After many repeated tries to contact the OEM to release the Kernel Source, it seems they did not respond at all. After many refusals from the OEM, we decided to make the kernel source on our own.
And Here we are with the kernel.
Total Credits goes to shahnawaz_sheikh :angel:
What Works?
boot
mtp/usb
RIL
Notification LED - Fixed On 7th July
Flashlight - Fixed On 17th July
Sensors
Touchscreen - Fixed On 4th June by shahnawaz_sheikh
Display
Audio
Camera - Can't Fix Due to Unique Lens Used
And Everything! :laugh:
Nutshell: This is a stable Kernel source for the phone and everything works!.
CREDITS:
First Of All to everyone
Many Many Thanks To @shahnawaz_sheikh :angel:
My Brother @YashrajYadav | Yassuz
My Guidance @TipzTeam
My Mentor Mohd Faraz | androiabledroid
Me OfCourse
And EveryOne
NOTE:
This is the pure work of Me(@The_God_Speed) and the people mentioned above. If you may somehow uses this Please give them proper credits.
LINK:
Check Github :good:
Many Updates Coming. Make sure to follow on XDA and Telegram.
Support Group: Telegram
Version Info: Stable
Architecture: Both [arm + arm64]
Have Fun!!!
And
Once
Again
THANKS!
Reserved!
Nice!
Updated!
Just updated the kernel source of brach cm-14.1 ?
INFO:
Arm641. lineage-17.1 kernel = can boot roms from lollipop to all the way up to Android 10
Arm1. lineage17.1 kernel = can boot roms from Oreo to Android 10
2. cm-14.1 kernel = can boot roms from lollipop to nougat.
All the things mentioned above are well tested by me ??
So I have a j2xlte [SpreadTrum SC8830]. I'm interested in getting a custom kernel ready for it (the one on github is very broken)
After waiting for Samsung to give us the kernel and cherry-picking some commits: here's the current source
https://github.com/J2xlteDev/android_kernel_j2xlte/commits/working
Now I want to have upstream changes, like remilia has in their kernel
But after spreadtrum got renamed to Unisoc, it's really hard to find any information on it.
Can someone give the Spreadtrum common kernel repo or something? Would be cool
figured it out, just needed to clone upstream kernel source and cherry-pick some commits
Moderator Information,
Thread has been closed at OP's request.