Google Glass kernel GPL source.
Currently there is a tarball of the kernel source in downloads.
notle_defconfig should work as the kernel configuration target
Update: The kernel source for the xrr02 build is now available in AOSP on the "glass-omap-xrr02" branch of the kernel/omap project. As this is the recommended way of acquiring the kernel sources, this project will be redirected , and the download deleted, in a day or two.
Original link: https://code.google.com/p/google-glass-kernel-source/
direct download for kernel.tar: https://code.google.com/p/google-gl...s/detail?name=kernel-glass-XE04.0-RC06.tar.xz
maybe anyone need this,i readet thatcurrently glass betas run on Android 4.0.4,so maybe can help anyone here.when not sorry.Greeeeetz
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.
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.....
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.
Hi all,
For those of you, like me, who are interested in learning more about developing for custom ROMs, the following links will be helpful for finding .
First is the inclusive list of open source kernel releases by Xiaomi: https://github.com/MiCode/Xiaomi_Kernel_OpenSource
At the bottom of said list is the Xiaomi 13 (fuxi).
Second is the device tree (based on Lineage OS and said to be WIP) by YuKongA: https://github.com/YuKongA/device_xiaomi_fuxi
What is the primary difference between official xiaomi 13's device tree https://github.com/MiCode/kernel_devicetree/tree/fuxi-t-oss and https://github.com/YuKongA/device_xiaomi_fuxi ?
YuKongA's contribution is for Lineage OS, or instead of MIUI it's AOSP. I think.
To give additional information, the Lineage-derived device tree likely originates from: https://github.com/imasaru/android_device_tree_template
Also, the kernel includes a lot of stuff for the hardware and is accompanied by a kernel device tree, which is a kind of 'table of contents' (unless I'm mistaken about the analogy).
"The 'Open Firmware Device Tree', or simply Devicetree (DT), is a data structure and language for describing hardware."
Linux and the Devicetree — The Linux Kernel documentation
I imagine a lot of compatibility issues are lining up the system image and the kernel+device tree.
...
(At this point, I'm really just spouting off some things as I'm learning, so feel free to correct or ignore me as I'm going along!)
Aquariuslt said:
What is the primary difference between official xiaomi 13's device tree https://github.com/MiCode/kernel_devicetree and https://github.com/YuKongA/device_xiaomi_fuxi ?
Click to expand...
Click to collapse
1/Xiaomi Kernel OpenSource
2/Xiaomi fuxi prebuilt
Veiranx said:
To give additional information, the Lineage-derived device tree likely originates from: https://github.com/imasaru/android_device_tree_template
Click to expand...
Click to collapse
You can find older ones.