What is a Tachyon?
Wikipedia calls it a "hypothetical" particle that most scientists claim doesn't exist.
That is what this kernel is: A kernel for Treble, something Motorola claims they never will release for our device.
Why upstream?
Well, DirtyUnicorns put it best on G+ : https://plus.google.com/+DirtyUnicornsOfficial/posts/2MpHCwKqh5J
This kernel will stay updated to the latest upstream from Linux-stable tree maintained by @nathanchance on git for msm
What is EAS?
Energy Aware Scheduler is a scheduler that knows how much energy is used on each frequency and how much power it uses to give best power/performance ratio. This kernel is slowly getting updated to the latest EAS patches from Linaro.org. For more information, check the below link.
https://www.linaro.org/blog/energy-aware-scheduling-eas-project/
Features:
Upstream kernel from source
Edits to avoid Safetynet/CTS (If you have root, it will fail signature check inherently without SUhide or Magisk hide)
Built With the Latest Clang for Android with Linaro as the cross compiler
OC GPU (changed 710 MHz to 750 MHz)
Same Adrenoboost tweaks as the Pixel 2 ElementalX kernel.
Wakelock fixes by Boeffla
EAS implementation (still work in progress)
Bugs/Issues:
hit and miss on MotoMods
Download:
Google Drive
Instructions:
Download ZIP to phone
Boot to TWRP.
Flash and follow prompts in Aroma
If you need to flash any GSI zips to boot your GSI, flash them again.
Reflash root if you want root.
Version Information
Status: Beta
Current Stable Version:
Stable Release Date:
Created 2019-02-06
Last Updated 2019-02-06
Source: https://github.com/Uzephi/Nash_AOSP
Git Branch: o9x-tachyon
Compiler: Clang 8.x.x
Cross Compiler: Linaro 7.x
Branch: Android 9.0.y
Kernel Version: 4.4.y
defconfig: nash_defconfig
Credits: @joemossjr - for collaborating and getting this working and debugging w/ me to get the best possible experience for our community. @invisiblek for all the work he's done for our device tree @npjohnson for his work on our device tree. @erfanoabdi for his amazing work getting treble running and his other work on our device.
Thanks and Mentions:
@Lord Boeffla for his wakelock code. @nathanchance for the assistance and amazing guides and keeping msm-8998 up to date with linux-stable @jbats for keeping up to date with linux-stable for me to merge into this kernel.
@flar2 for his work on our chipset, msm8998
All other developers shown in commit history.
(Quoted from Nathan Chance)
A note about donations
Quite a few people have asked to donate to me in the past and I have turned them down. I am not in this for the money, this is my hobby, something I truly enjoy. If you truly want to donate to something (it is not expected in the slightest), I recommend an entity like the Open Source Initiative, the Free Software Foundation, XDA, or any one of the people I have thanked in the OP. Additionally, you are free to copy any and all of my work; the only thing I request is that you not ask for donations as well (though I can't really enforce this lol). Thank you.
Changelog:
08/14/2018:
Initial release
02/06/2019:
Rebase for Pie
EAS Progress:
Schedutil is a form of EAS. I am currently working on fixing it to get it more in line with how smooth EAS runs on the Pixel. (yes, that means Energy Aware has always been in the AOSP kernels, we just never talked about it. Now that I am updating it to the lastest from Linaro, I am being open about it).
Known issues: GSIs don't work.
Hey there Uzephi. This is for the latest 8/14 build of lineage, right? Because after flashing, I'm stuck on the lineage splash screen.
fossiltkm said:
Hey there Uzephi. This is for the latest 8/14 build of lineage, right? Because after flashing, I'm stuck on the lineage splash screen.
Click to expand...
Click to collapse
Apparently the Tamien vibrator changes haven't been merged yet and are still in Gerrit. I am reverting and will release the fixed kernel in about half an hour.
Updated. same Download link, will now work with Lineage Official that released today. (old build worked on test-keys on 0808)
Uzephi said:
)
Click to expand...
Click to collapse
hi mate, so basically this kernel is not for stock rom right?
thanks
ilovemeow said:
hi mate, so basically this kernel is not for stock rom right?
thanks
Click to expand...
Click to collapse
It's only for Treble. The kernel mounts vendor, so even DU won't boot it.
4.4.148 updated, pushed, and uploaded to Drive. No other changes
sorry for my stupidity, but which roms are actually compatible with this kernel?
Debuffer said:
sorry for my stupidity, but which roms are actually compatible with this kernel?
Click to expand...
Click to collapse
Any ROM built for the Z2 force that is treble enabled. Currently running into a no boot with GSI images and working on fixing that. Currently I think that's only Lineage officials built after 08/14. I don't know if DU has gone treble yet.
link updated to 4.4.150. added back CRC as well. Still no verification if that fixed GSI boot issues
anyone else have screen flip recovery issues after flashing this? everytime my recov screen does a 180 no matter if its twrp, lineage rec, etc
jasperbastianrain said:
anyone else have screen flip recovery issues after flashing this? everytime my recov screen does a 180 no matter if its twrp, lineage rec, etc
Click to expand...
Click to collapse
Its a known issue. Stock lineage kernel does this as well. Best thing to do is just boot twrp.
Edit: 4.4.152 merged and Gdrive updated.
4.4.153 has no changes for us. I merged just to be in line with linux-stable but not releasing a build.
Uzephi said:
Its a known issue. Stock lineage kernel does this as well. Best thing to do is just boot twrp.
Edit: 4.4.152 merged and Gdrive updated.
Click to expand...
Click to collapse
I've only had this issue with this kernel, every other kernel I've tried stock or custom have all been able to load twrp correctly. For some reason though I haven't been able to flash any ROMs with the newest twrp, I always have to use 3.2.2.1 official or the 3.2.2.1 for treble.
Updated to 4.4.154. If you are having issues with TWRP, try flashing the installer after the kernel, I haven't had an issue doing it this way.
will this work with Lineage Unofficial builds??
blake .l said:
will this work with Lineage Unofficial builds??
Click to expand...
Click to collapse
Yes
Related
LineageOMS for Xiaomi Mi 5s (capricorn)
aka LineageOS 14.1 bundled with substratum & OMS
PSA: LineageOS 14.x is dead. Please switch to LOS 15.x. This ROM is no longer updated.
Unofficial ROM built by iamnotstanley (me). Updates every Tuesday.
This is a pure LineageOS 14.1 based ROM with full OMS and substratum theme engine support. Today the LineageOS 14.1 doesn't support any theme engines by default, and this ROM fixes it.
I'm only including the latest OMS commits for Nougat and the latest substratum theme engine apk from apkmirror.com.
Working:
Everything
Working OTA updater with OTA server (please share feedbacks about the download speeds, download stability, etc.)
Bugs:
Same as in LineageOS 14.1, OMS & substratum
Downloads:
Builds
GApps (opengapps.org) Recommended: ARM64 - 7.1 - nano
LineageOS extras
MIUI firmware update zips Requirement: MIUI 8.1.4 or newer firmware
Sources:
LineageOMS for capricorn (my own repos)
substratum
LineageOMS
LineageSubstratum
LineageOS
Xiaomi vendor blobs
XDA:DevDB Information
LineageOMS | LineageOS 14.1 bundled with substratum & OMS, ROM for the Xiaomi Mi 5s
Contributors
iamnotstanley, LineageOS team, substratum team, MJPollard, nathanchance
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: MIUI 8.1.4 dev firmware (LOS14.1 requirement)
Based On: LineageOS 14.1
Version Information
Status: No Longer Updated
Created 2017-11-07
Last Updated 2018-03-03
Screenshots
Changelog:
2018-01-10
+ upstreamed LOS source
+ updated Substratum apk: v914 -> v931
* MIUI 8.1.4 or newer firmware required
2017-11-14
+ upstreamed LOS source
+ updated Substratum apk: v912 -> v914
* uploading sha256 checksums besides md5 checksums from now
2017-11-08
+ working OTA updater
+ upstreamed LOS source
2017-11-07
* first build
- no OTA updates
Cool rom bro thanks....will check it these days
What method did you use to build? Cherry pick or the provided manifest? I had problems with the latter when I tried.
Edit: I see you manually merged them. Good job.
mesziman said:
What method did you use to build? Cherry pick or the provided manifest? I had problems with the latter when I tried.
Edit: I see you manually merged them. Good job.
Click to expand...
Click to collapse
Yes, I tried with the merge_script, but it failed because the outdated LineageSubstratrum repos, so I merged it manually. It was easier than fixing the merge_script somehow, and now it's perfectly fits to my build script.
New build!
2017-11-08
+ working OTA updater
+ upstreamed LOS source
It is Tuesday so new build and an another bump post!
2017-11-14
+ upstreamed LOS source
+ updated Substratum apk: v912 -> v914
* uploading sha256 checksums besides md5 checksums from now
(from next week I won't post changelogs to separate posts, only to the reserved post in the top)
By the way anyone using this ROM now or just me? I keep updating this, I just wrote a little patcher script for the easier and more automated ROM building. (Later I'll migrate to a LineageOMS + microG ROM, if anyone want I can share that too, but with the right resources it is very easy to build it for yourself.)
Thanks @iamnotstanley, this rom is pretty good, used it for almost 1 month and still no problem so far :3
Btw, i just saw some OTA update notifications, should i update it? Won't it wipe my personal data ? (tho i do backup before, but.... restore them is really painful =_= )
Dark Hunter said:
Thanks @iamnotstanley, this rom is pretty good, used it for almost 1 month and still no problem so far :3
Btw, i just saw some OTA update notifications, should i update it? Won't it wipe my personal data ? (tho i do backup before, but.... restore them is really painful =_= )
Click to expand...
Click to collapse
Thanks for the feedback!
I release a new build every week (you can look at the LOS14.1 technical changelog here). I recommend to make a full nandroid backup with TWRP and update the rom. It won't wipe your personal data, it's like any other OTA update, it'll only wipe your system partition, so if you have Magisk or any other mod you'll need to flash it again.
iamnotstanley said:
By the way anyone using this ROM now or just me? I keep updating this, I just wrote a little patcher script for the easier and more automated ROM building. (Later I'll migrate to a LineageOMS + microG ROM, if anyone want I can share that too, but with the right resources it is very easy to build it for yourself.)
Click to expand...
Click to collapse
I'll be installing as soon as I got unlocking finished. Thanks for your work!!
Regards
Dark Hunter said:
Thanks @iamnotstanley, this rom is pretty good, used it for almost 1 month and still no problem so far :3
Btw, i just saw some OTA update notifications, should i update it? Won't it wipe my personal data ? (tho i do backup before, but.... restore them is really painful =_= )
Click to expand...
Click to collapse
Please, what is the name of that sub theme in screenshot?
rhyme4u12 said:
Please, what is the name of that sub theme in screenshot?
Click to expand...
Click to collapse
It's StreamLined theme.
Thank you for your work!:good:
Ths you!!!
Sent from my MI 5s using Tapatalk
I see new version i available but OTA don't see anything.
dariusz666 said:
I see new version i available but OTA don't see anything.
Click to expand...
Click to collapse
Thanks for the report. Well, I'm always upload the builds to my OTA server as soon as I built them.
I tested the updater on my device, and the response is a bit slow (mainly because the OTA server software that I'm using), but working, and the download speed is fine for me.
If it happens again, wait a few minutes and try again or download it from sourceforge.
EDIT: I think I solved this response lag issue. Now the OTA update check is much faster for me than before.
Yes. Everything works fine and download very fast. Great job.
:good:
Just uploaded the new weekly build. You'll need to update the firmware to version 8.1.4 or newer before updating to this build. You can download it from fjtrujy/capricornCNFirmware repo.
Also sorry for the OTA server downtime, I had issues with my domain service, but I already fixed it.
I'll update my RR build tomorrow, sorry for the late updates, I don't really have time this week.
By the way, I started using Telegram again, if anyone wants to send me a message about anything, you can do it there.
How is battery?
francesco0597 said:
How is battery?
Click to expand...
Click to collapse
I think it's very good. There isn't much change in the code so nearly same in the official LOS14.1. I can achieve 5-7 hrs of sot with the stock kernel and day-to-day usage.
This project is now "End-of-Life" (EOL). Thanks to all of you for the kind support...
/* Introduction */
I built all these kernels with an aim to simply experience and compare the advantages (and sometimes the issues) of higher GCC versions (7 and above) with that of stock kernel (typically built using Google’s stock GCC-4.9.x tool-chain) as well as my own SmartPack-Kernel (built using stock as well as various custom tool-chains). All the credits goes to haggertk and all the others developers associated to Lineage-OS (especially the klte team) as I simply build from their source using latest tool-chains (Of-course, it requires significant modifications on the source code. For more details, please visit GitHub source).
/* DISCLAIMER!! */
Code:
I am not responsible for any damage to your device. Everything you are doing on your device is on your own risk.
I only own kltelgt (Korean variant). Hence, kernels under the category 'kltekor' are only tested by myself.
Please note that flashing any custom Kernel including mine will void your warranty.
/* What is Stock-Kernel and how it is different from official LOS Kernel? */
As the name itself says, these are simply stock Kernels build from official Lineage-OS kernel source code, however, using custom tool-chains of higher GCC version such as GCC-7.x/8.x. If you want to know more about Kernel’s in general, I suggest you to read this in-depth guide by @Saber. You may probably use these web-links to know more about Linaro, UBERTC and Bleeding Edge Toolchain.
/* What is included */
Separate GCC-7.x/8.x builds for the supported devices. You guys can freely test, compare and stay with the one you like more.
/* What you can expect */
Much better performance/SOT, and also some bugs in the worst case.
/* Supported devices */
klte: SM-G900F, SM-G900V, SM-S902L
kltekor: SM-G900K/L/S
/* Compatibility */
This kernel is only meant to work on Lineage-OS 14.1 and nothing else. However, it may work on other LOS-14.1 (and AOSP) based Nougat ROMs (Please try at your own risk).
This kernel will NOT work in Samsung Stock and other TW ROMs.
/* How-to-Install */
1. Download and copy Kernel into your phone
2. Go to recovery (TWRP recommend)
3. Flash Kernel
4. Reboot and Enjoy
/* What I can offer */
Regular updates with each LOS release.
Try to keep the tool-chains as up-to-date as possible.
/* What I can’t offer */
I may (and mostly will) not add new features. Because, my intention is simply not that for this Kernel. For those who are looking for a more feature rich Kernel, I advised you to try other existing good kernels including my own SmartPack-Kernel.
I never attempt to fix bugs in the LOS kernel source that are really difficult or very much time consuming.
/* Features */
Build from latest Lineage OS source code.
Build using Linaro 7.3 (GCC-7.3.1)/Bleeding Edge Toolchain 8.2 (GCC-8.2) tool-chain.
Anykernel concept for compatibility with maximum devices and ROMs.
Features: All the features available in the stock LOS Kernel (neither removed nor added).
For advanced kernel tweaking, you may use Offical Kernel Auditor.
/* Downloads */
GitHub release page
/* Acknowledgements */
@haggertk
@nathanchance
@ZaneZam
@Saber
@osm0sis
@Grarak
Many other XDA developers
XDA:DevDB Information
Stock-Kernel, Kernel for the Samsung Galaxy S5
Contributors
sunilpaulmathew
Source Code: https://github.com/SmartPack
Kernel Special Features: Built using GCC-7.x/8.x
Version Information
Status: Nightly
Created 2017-11-18
Last Updated 2018-11-01
Frequently Asked Questions
Q1: Is this kernel compatible with ROM(s) a/b/c?
Ans: I do not know. All of my kernels are based off and tested only on Lineage-OS. However, if your ROM(s) a/b/c are based on Lineage-OS (and uses the same kernel source code), it will most probably work.
Q2: Which version of kernel should I use?
Ans: I recommend to use the latest if you are on the latest Lineage-OS. For other ROMs with an old built dates, you probably need to find an old version of my kernel with a comparable build date (though you are advised to stay with the latest, if possible).
Q3: How about performance/SOT?
Ans: Since SOT, performance etc. are largely based on several factors such as ROM, installed apps etc. No one else can exactly predict the performance/SOT of your mobile. So, you should test and find out that by yourself.
Q4: Can you tell me the best settings for performance/SOT?
Ans:Again, that depends on several factors. I can only say my favorite settings that gives me best results in my favorite ROM.
Q5: Which are the best CPUfreq gov/CPU hotplug/IOScheduler/TCP congestion algorithm for battery life/performance etc?
Ans:Again you need to find out those things yourself. To get more idea, I suggest you to read this awesome guide by @saber.
Q6: Could you add feature x and y to this kernel?
Ans: Mostly No. Because, my intention is simply not that for this Kernel. For those who are looking for a more feature rich Kernel, I advised you to try other existing good kernels including my own "SmartPack-Kernel".
Q7: When will you release a new version of this kernel?
Ans: New updates will arrived with each LOS release with some changes in the kernel source code.
Q8: I found a bug, what do I do?
Ans: Please provide as much information as possible (such as what feature, what didn\'t work, screen-shots or logcat if possible) and post in this thread.
Change-logs
Lineage-OS 14.1
Thank you Sunil.
Your stock kernel (ubertc-8) is working very smoothly on Crdroid 3.8.2...
Nice job.:good:
Drhedphuk said:
Thank you Sunil.
Click to expand...
Click to collapse
itsclarence63 said:
Your stock kernel (ubertc-8) is working very smoothly on Crdroid 3.8.2...
Nice job.:good:
Click to expand...
Click to collapse
Thank you very much guys... Enjoy...
Thanks it's great and stable I flashed linaro
Great stuff bro. I was looking for this. Thanks again!
seprator said:
Thanks it's great and stable I flashed linaro
Click to expand...
Click to collapse
airidosas252 said:
Great stuff bro. I was looking for this. Thanks again!
Click to expand...
Click to collapse
Thank you very much friends for testing as well as for the nice words
I tried both toolchains but ubertc doesn't overheat my device like linaro so I stick with ubertc from now
New builds (v2)
New builds are uploaded and can be found in the GitHub release page...
Enjoy...
For g900d please
I have been running your Kernel Built using Linaro-GCC-7.x/UBERTC-8.x for the last few days on my g900v with resurrection remix 7.1.2 and I have noticed that my battery seems to be lasting longer. I am liking the overall smoothness of this kernel as well. Thanks Buddy, keep up the good work!
joey118 said:
For g900d please
Click to expand...
Click to collapse
Extremely sorry friend. I do not want to add one more device as it requires a lot of time from my side (1 device=2 build). Further, I do not think that many klteduos users will use my Kernel (so it will be ultimately waste of energy and time). However, any one can easily build klteduos or any other variant that are officially supported by Lineage-OS from my fully up-to-date source (sources of both Kernel and toolchain can be found here).
swiftbones74 said:
I have been running your Kernel Built using Linaro-GCC-7.x/UBERTC-8.x for the last few days on my g900v with resurrection remix 7.1.2 and I have noticed that my battery seems to be lasting longer. I am liking the overall smoothness of this kernel as well. Thanks Buddy, keep up the good work!
Click to expand...
Click to collapse
Thanks for the nice words and happy to know that you guys like it... cheers...
New builds (v3)...
New builds are uploaded and can be found in the GitHub release page.
Cheers...
New builds (v4)...
New builds (v4) are uploaded and can be (along with change-logs) found in the GitHub release page.
Enjoy...
sunilpaulmathew said:
New builds (v4) are uploaded and can be (along with change-logs) found in the GitHub release page.
Enjoy...
Click to expand...
Click to collapse
what is the difference between the 2(of each) in your v4 release (first time about to test) one is 6.56mb the other 6.26mb?
EDIT: nvm stupid me i dint see the other ones were kltekor...sry about that.
Good evening, I would like to change my galaxy s5 sm-g900f. I linkageos 14 + g-app stock I uninstall because the autonomy is very reduced and the device heats. I would like to test UBERTC-8.x, I read on the site that the autonomy is better and also the overheating. But how do I have to reinstall the all lineageos + g-app or install only UBERTC-8.x + g-app. Of course by doing everything wipe.
thank you in advance
MaCaLuBi said:
Good evening, I would like to change my galaxy s5 sm-g900f. I linkageos 14 + g-app stock I uninstall because the autonomy is very reduced and the device heats. I would like to test UBERTC-8.x, I read on the site that the autonomy is better and also the overheating. But how do I have to reinstall the all lineageos + g-app or install only UBERTC-8.x + g-app. Of course by doing everything wipe.
thank you in advance
Click to expand...
Click to collapse
If you are already using Lineage-OS, simply go to TWRP and flash this Kernel and all done.
If you are on a stock TW based ROM do the following
1. Go to TWRP
2. Wipe system and data
3. Flash Lineage-OS-14.1
4. Flash Gapps
5. Flash this Kernel (UBERTC or Linaro)
6. Flash magisk/ modules/su-addons, or any other stuff you like
7. Wipe cache/dalvik cache
8. Reboot and enjoy...
New (v5) builds...
New builds (v5) are uploaded and can be (along with change-logs) found in the GitHub release page.
Enjoy...
Hi Guys!
This thread is dedicated to latest Linux Stable Kernel version based of recently released Oreo Kernel for Mi A1.
In simple words it is "Android kernel trees with linux-stable merged into them".
https://github.com/android-linux-stable/tissot
You can compile it and flash it using "AnyKernel" or build it into your own ROM.
Current Version: 3.18.103
XDA:DevDB Information
[LINUX STABLE KERNEL][Mi-A1] 3.18.103, ROM for the Xiaomi Mi A1
Contributors
pvineeth97, nathanchance
Source Code: https://github.com/android-linux-stable/tissot
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Version Information
Status: Stable
Current Stable Version: 3.18.103
Stable Release Date: 2018-04-09
Created 2018-03-25
Last Updated 2018-05-10
Great
Thanks for making this thread :good: I've subscribed so if there are any issues, I can address them.
EDIT: I also have a Telegram chat for support: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
hi great work. appreciated.
After browsing around a little bit, I have noticed two things:
1. There aren't many (if any) kernels based purely on Xiaomi's stock source, which is what this tree is based on.
2. There are several kernel bases for custom ROMs.
As a result, this tree probably won't be of much use to developers and it's not really easy for me to make a custom branch like I have done for the other trees. As a result, I am offering to merge in the android-linux-stable/msm-3.18 tree which most kernels seem to be downstream from so you have a clean way to update for the future if you don't feel comfortable doing the full merges yourself.
Alternatively, if your tree is almost up to date anyways (3.18.100 or 3.18.101 seem to be common), you can just git merge the latest tag in (v3.18.102 at the time of writing this) and watch the conflict notes for the ones that pop up in the msm-3.18 tree. I'm accessible via this thread or the Telegram group linked above if you have any questions or concerns!
nathanchance said:
Thanks for making this thread :good: I've subscribed so if there are any issues, I can address them.
EDIT: I also have a Telegram chat for support: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
Click to expand...
Click to collapse
Thanks. Great work. :good:
Edit :
How to flash this Kernel ?
What's the benefit using this Kernel.
I will try to compile later kernel
nathanchance said:
Thanks for making this thread :good: I've subscribed so if there are any issues, I can address them.
EDIT: I also have a Telegram chat for support: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
Click to expand...
Click to collapse
Your presence here is an inspiration!
I'm trying to port omni to mi a1 (keyword: trying... I'm starting to learn the whole process from scratch so, not there quite yet.)
And I hope this kernel will be useful.
Does this mean WireGuard is supported by default?
gusbalaa said:
How to flash this Kernel ?
What's the benefit using this Kernel.
Click to expand...
Click to collapse
This is just a reference for kernel developers. You need to compile a build and make flashable of it.
radogost said:
Does this mean WireGuard is supported by default?
Click to expand...
Click to collapse
No, this is just stock kernel with Linux kernel stable changes merged.
Sent from my Redmi Note 4 using XDA Labs
krasCGQ said:
This is just a reference for kernel developers. You need to compile a build and make flashable of it.
No, this is just stock kernel with Linux kernel stable changes merged.
Click to expand...
Click to collapse
I need to compile it self ?
to make it able to flash, i don't expert about Kernel / ROM.
Thanks.
RELEASED: 3.18.103
https://github.com/android-linux-stable/tissot
Disclaimer
Always backup boot.img before flash.
Do with your own risk.
Requirements
AOSP android 10, No support for MIUI rom!
Latest TWRP or any custom recoveries
Now support for new and old camera blobs
ROMs with default HMP kernel, No eas ROMs support.
Features
Using Anykernel3 flashable by osm0sis.
Simple, no weird feature in here.
Compiled by AOSP clang 11.0.4.
Latest CAF and changes from AOSP kernel 4.4 common (Linux version 4.4.238).
Kcal RGB Colours control.
How to use
Flash the zip through twrp
Reboot and done.
Credits and Thanks
LineagesOS for base patch Xiaomi.
osm0sis for Anykernel3.
Anyone in Contributors
Downloads
Again, please make sure you read the Requirements.
Rain kernel latest release downloads with changelogs
XDA:DevDB Information
Rain, Kernel for the Xiaomi Redmi Note 7
Contributors
rainforce279
Source Code: https://github.com/ryan-andri/android_kernel_xiaomi_lavender
Kernel Special Features: See at Features.
Version Information
Status: Stable
Current Stable Version: 11102020
Stable Release Date: 2020-10-11
Created 2020-09-19
Last Updated 2020-10-11
Changelogs
Code:
[B]Build - 11102020[/B]
[LIST][*]Build with AOSP Clang 11.0.4
[*]power: msm-core: Fix mutex not getting unlocked in error path
[*]ARM64: defconfigs: lavender: make savedefconfig for old and new cam
[*]msm: camera: make new camera blobs support optional and not device specific
[*]ARM: dts: xiaomi: turn green led as white node (should fix led issue on some rom)
[*]add toggle for disabling newly added USB devices
[*]Revert "mm: change max readahead size to 512KB" (depend on rom support)
[/LIST]
Note
For more detail changelogs, you can check the source directly.
Report issue with dmesg log please.
Make sure to not using any magisk modules for tweaks (Avoid conflict with kernel).
Thank you and have a nice day.
Reserved
Hi! Great new kernel I just want to report that double tap to wake isn't working when I flash this on PE+ rom (oldcam rom). I know that it is maybe due to the fact that oldcam is not supported but can we expect to atleast get the d2tw working
guntlet213 said:
Hi! Great new kernel I just want to report that double tap to wake isn't working when I flash this on PE+ rom (oldcam rom). I know that it is maybe due to the fact that oldcam is not supported but can we expect to atleast get the d2tw working
Click to expand...
Click to collapse
dt2w work fine for rom with device tree based from los. seem dt2w sysfs might be different, but for sure i'll check it. Thank you.
rainforce279 said:
dt2w work fine for rom with device tree based from los. seem dt2w sysfs might be different, but for sure i'll check it. Thank you.
Click to expand...
Click to collapse
Yeh got it, Thanks
New build is up!
Enjoy and Thank you.
rainforce279 said:
New build is up!
Enjoy and Thank you.
Click to expand...
Click to collapse
Any chance for old cam?
noobSU said:
Any chance for old cam?
Click to expand...
Click to collapse
will try it for next build.
I installed rain kernel on PE+, no issue so far. for oldcam ROMs, just flash newcamblobs.zip.
but when first install the kernel, it's aborting, say there no ramdisk to unpack. need magisk installed before to get kernel installed. thank you.
edit: seems led is not working on ROM that not based on los tree.
fadhlanisatria said:
I installed rain kernel on PE+, no issue so far. for oldcam ROMs, just flash newcamblobs.zip.
but when first install the kernel, it's aborting, say there no ramdisk to unpack. need magisk installed before to get kernel installed. thank you.
edit: seems led is not working on ROM that not based on los tree.
Click to expand...
Click to collapse
Theres no issue in latest twrp for me, about led i'll check it asap. Thank you.
New Build released!
now support for old camera blobs.
drop caf variant, upstreamed stable for daily.
cleanup changelogs since caf variant droped.
Led issue on some rom should be fixed now.
Trying Nov 7 build but I got sdcard needed format notification. Missing exfat support?
1n00bB said:
Trying Nov 7 build but I got sdcard needed format notification. Missing exfat support?
Click to expand...
Click to collapse
can you provide dmesg log ?
rainforce279 said:
can you provide dmesg log ?
Click to expand...
Click to collapse
I'm ROM hopping but now back to LOS to get dmesg aaand it's working now
Sorry, my bad
Is this project discontinued? or just in a hiatus for the moment
guntlet213 said:
Is this project discontinued? or just in a hiatus for the moment
Click to expand...
Click to collapse
no, sorry bit busy with rl for now.
will release new version asap.
WETA Kernel SM-G998U/U1/0 Snapdragon only
*** This will only work on Snapdragon devices with an unlocked bootloader..
SM-G998U/U1 - SM-G9980
Telegram thread at bottom of this post
See post #2 for install steps
Changelog...
R5.02
Telegram thread merged into N20.S20 group, check new links.
Upstreamed to 5.4.127
all modules now inlined, no need for magisk helper module.
added wireguard
Power usage tweaks
More
R4.04
Upstreamed to 5.4.123
R4.03
Upstreamed to 5.4.122
R4.02
Upstreamed to 5.4.121
R4.01
Upstreamed to 5.4.120
R4
Testing phase complete
Upstreamed to 5.4.119
R3
Rebased off UAG source code
R2
Upstreamed to 5.4.118
Fixed Torch/Flash
R1
built using CU8 kernel source
Upstreamed to 5.4.117
Fully permissive
KNOX disabled
Wireguard
Misc debugging disabled
Kernel Downloads
Telegram thread
--------------------->
Beer fund
XDA:DevDB Information
Kernel for the Samsung Galaxy S21 Ultra
Contributors
Mentalmuso, mentalmuso
Source Code: - Kernel Source
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R1
Created 2021-05-10
Last Updated 2020-05-10
*** Be aware, there may be a need to wipe data if you desire to go back to stock kernel, my suggestion is to backup your stock BOOT partition and DATA before flashing. This way you can return to your original setup easily. It is unknown at this stage what data is causing an issue going back to stock. If you find it, be sure to share.
* You must have bootloader unlocked and rooted your device with Magisk before flashing this kernel. Magisk is essential for camera and wacom.
* Boot times are approx 60-75sec at the moment, itll sit on the yellow triangle splash for approx 60sec and the bootanimation for 5sec.
* When flashing this kernel, an AnyKernel helper module is installed. This is a Magisk Module that is essential for the operation of Camera and Wacom. Removal of this module while running this kernel will break camera and spen.
* Kernel zip labels have either a P or E in them, P=Fully Permissive, E=Enforcing (switchable)
To install
download and flash the kernel installer zip in TWRP or any custom recovery
--->
mine 2
Amazing to see some development, i thought this phone thread was gonna be dev dead
I am a little surprised myself.
Status update
I have found a couple of bugs I'm working on, #1 camera module only loads on permissive version of kernel, #2 the flash doesn't work, #3 random reboots maybe 4-5 times a day.
Working on having a stable R2 this week.
Edit: so it seems the hourly bootloop happens on stock kernel for me also. So it isn't an issue with this kernel. Though I do need to fix the flash
WETA Kernel R2
Upstreamed to 5.4.118
Fixed Torch/Flash
--->
WETA Kernel R3
Starting from scratch with different source code. It seemed there were problems booting for most. The new test kernels have been successful.
This is a basic start, with the intention of upstreaming and testing along the way.
--->
WETA Kernel R4
Upstreamed to 5.4.119
* Testing was successful with the different source code kernel
* Remember you MUST have magisk installed Pryor to flashing this kernel, this kernel needs it's ak3-helper magisk module for camera operation.
--->
I have used your Kernels in the past for other devices, really loved them. Was wondering if you plan to make a custom kernel for the s21 ultra Exynos in the future ?
Excuse my ignorance but please elaborate on "knox disabled"? I have unlocked bootloader/magisk and knox is already disabled as far as I know. Would this mod to the kernel allow me to use knox locked features that have been lost, eg biometric security for some apps? Thank you for your work, look forward to trying it out
dsdavis6 said:
Excuse my ignorance but please elaborate on "knox disabled"? I have unlocked bootloader/magisk and knox is already disabled as far as I know. Would this mod to the kernel allow me to use knox locked features that have been lost, eg biometric security for some apps? Thank you for your work, look forward to trying it out
Click to expand...
Click to collapse
Kernel based Knox ncm is disabled, it has nothing to do with your "Knox fuse" which is blown when your bootloader is unlocked.
paul_cherma said:
I have used your Kernels in the past for other devices, really loved them. Was wondering if you plan to make a custom kernel for the s21 ultra Exynos in the future ?
Click to expand...
Click to collapse
I don't plan on building anything for devices I don't hold in my hand. Reliable testing is hard otherwise
WETA Kernel 4.02
Upstreamed to 5.4.121
--->
Just a note regarding boot times, I can achieve a 35sec boot time, though in doing so it breaks double tap to wake, and fingerprints. I won't release a version with those broken items.
WETA Kernel 4.03
Upstreamed to 5.4.122
--->
WETA Kernel 4.04
Upstreamed to 5.4.123
--->