This is a bit different than most postings here, as I'm not directly providing any binaries to install on your phone and instead providing a simple tool, rattlesnakeos-stack, to build your own customized ROM based with latest AOSP on a regular basis, with your own signing keys, and your own OTA updates. This probably will be interesting to a small subset of users as it requires some technical knowledge and costs money to run this infrastructure in AWS to produce your own builds.
You can read more about the project here: https://github.com/dan-v/rattlesnakeos-stack
I'm generally more active on the subreddit if you have any questions: https://www.reddit.com/r/RattlesnakeOS/
XDA:DevDB Information
RattlesnakeOS [Pixel 3a XL], ROM for the Google Pixel 3a XL
Contributors
dantheman78
Source Code: https://github.com/dan-v/rattlesnakeos-stack
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: v9.0.35
Stable Release Date: 2019-09-08
Current Beta Version: v10.0.0-beta.1
Beta Release Date: 2019-09-12
Created 2019-09-13
Last Updated 2019-09-13
Thanks so much! Can you put a more in depth guide on how to make it custom? Like... Where are the sources for kernel and system pulled to, etc.?
Magnetox said:
Thanks so much! Can you put a more in depth guide on how to make it custom? Like... Where are the sources for kernel and system pulled to, etc.?
Click to expand...
Click to collapse
Right now the customizations are a bit limited as they were initially meant just to apply patches to the AOSP source tree. There is support for executing shell scripts during the build process that could do pretty much whatever you want though. Both of these options (patches and shell scripts) are lightly documented here: https://github.com/dan-v/rattlesnakeos-stack#customizations. If you wanted to swap the kernel for example (by default it uses the prebuilt AOSP kernel), you could use a shell script that builds the kernel out of tree or pull down a pre-built kernel and copy it over the prebuilt kernel for your device. I unfortunately don't have any detailed examples of this to point you to though.
For 9.0 there was a series of patches contributed by the community (https://github.com/RattlesnakeOS/community_patches) that did small things like give you ability to control network/sensor permission or increasing password length, etc. For 10.0, none of these patches are currently ported over yet.
This is actually an interesting project. Will have a look for sure.
Related
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
WARNING: You'll most probably loose ALL your data, and might break your phone. Please use with extreme caution!
This is a fully custom ROM for the Huawei Mate 9, derived from the AOSP Pie device tree for the HiKey960 development board, with minimal usage of the existing Huawei vendor stack.
This ROM does include Gapps for Pie.
IMPORTANT: See the broken features below. Most importantly: Phone and cellular is currently entirely non-functional, as there is no RIL implemented. If I can get away with it, I'm not importing code from Huawei's existing vendor stack. The graphics stack is fully sourced from the HiKey960 development board sources, as provided by Google on the Driver Binaries page for AOSP; the only blobs which are sourced directly from the Mate 9 system images are the device firmware blobs from /vendor/firmware.
Working features:
Basic graphics hardware acceleration & 3d support.
Wifi
Bluetooth (partial: kernel wakelock permanently held, preventing deep sleep. Generally functional, you will need to bring over your MAC address and configure it yourself.)
Touchscreen
Notification LED
Screen brightness
USB
Fast charging
Vibration
Battery information
Broken or not hooked up yet:
Reboot / shutdown: always cycles to eRecovery. (BFM is disabled, so the loader doesn't know that boot was successful.
Audio via wired headset, earpiece, speaker. (Bluetooth audio works. Over USB-C, untested.)
Cellular. (No RIL yet.)
SD card.
Camera
Fingerprint sensor
NFC
Any and all sensors.
GPS
More that I have yet to list, I'm sure.
Installation Instructions
Make note of your bluetooth hardware address.
Factory reset your device, preferably using stock recovery. TWRP builds will not work once this ROM is installed.
Install the kernel, ramdisk, and system image with fastboot.
Boot the system
Once booted: adb shell setprop persist.service.bdroid.bdaddr <your bluetooth hardware address>
Notes
The image is pre-rooted (it is an AOSP "eng" build). ADB is on by default, running as root, with no authentication.
Even though it is pre-rooted, I still recommend installing Magisk for the time being. Use the ramdisk image provided here with "Patch Boot Image". Magisk 17.1 with Magisk Manager 5.9.1 work. (Installing Magisk also works around a few other issues - for example, Developer Options is completely inaccessible on the default install.)
Changelog
2017-09-03: Initial release.
Download
GitHub release
Thanks
@wirmpolter for the Serenity kernel (which is used as the basis for the kernel image)
@TheHitMan for BiTGApps Pie
Sources
ironydelerium/device_huawei_mha on GitHub
ironydelerium/vendor_huawei_mha on GitHub
ironydelerium/Serenity on GitHub
XDA:DevDB Information
Custom AOSP Pie for Huawei Mate 9, ROM for the Huawei Mate 9
Contributors
irony_delerium, wirmpolter
Source Code: https://github.com/ironydelerium/device_huawei_mha/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: EMUI 8.0
Based On: AOSP
Version Information
Status: Alpha
Beta Release Date: 2018-09-03
Created 2018-09-03
Last Updated 2018-09-03
Reserved
Reserved
Wooohoo .. is amazing .. more roms .. thanks .. dev ..?
You are amazing Man. I hope you will do it fully functional as soon as. Thanks bro.
Thank you much.
I tried this ROM. But too much bugs. I had to roll back to original EMUI ROM.
Hope you can fix the bugs in future.
Thank you very much for your efforts anyway.
luyongfeng said:
Thank you much.
I tried this ROM. But too much bugs. I had to roll back to original EMUI ROM.
Hope you can fix the bugs in future.
Thank you very much for your efforts anyway.
Click to expand...
Click to collapse
I'm planning on it.
There's a lot of work to do - cellular, audio, basic sensors, camera - none of those things are even there yet.
What's there works, unfortunately as you can tell, that's not a lot yet.
Are you still working on the rom? Any progress? tried to build lineage?
I am still working on it.
Not even considering Lineage at this point - just trying to get a complete device tree constructed, of which there are a lot of pieces to construct (not the least of which because I'm basically building it up from scratch, instead of using Huawei's vendor image).
Development in Kirin is very difficult. So far only see aosp rom in Honor 8 pro based on 7.1. Which is very similar to Mate 9
If you still want to run an SGSI (we have device specific roms now), I strongly recommend vanilla aosp. It is by far the smoothest and just simply works without issues. I will maintain AOSP for security patches until i'm using device specifics as a daily (still some bugs left). Go for my AEX or POSP now
What is this thread?
This thread is hosting my personal builds of sGSI's. As we don't have stable device specific Pie roms yet I believe this is still in high demand for you people that love AOSP roms and are patiently waiting for development. Until we have a stable device tree (which would translate into stable device specific roms) I will be mainting these builds. Aside from a few minor quirks these builds should work fine for daily usage.
What are the quirks?
For getting bluetooth to work you need a permissive kernel. You can use the magisk module provided in my mega library.
The statusbar padding is a bit off by default (fix is in my library as well)
AOSiP has longer boottime
What ROMS can I choose from?
For now my stable sGSI's are AOSiP, Pixel Experience and AOSP.
What vendor/firmware/kernel to use for what rom?
AOSiP:
S9/S9+ needs BRK3 vendor/firmware and endurance AOSP kernel
N9 needs ARH6 vendor/firmware and endurance GSI kernel
Pixel Experience:
S9/S9+ needs BRK3 vendor/firmware and endurance AOSP kernel
N9 needs ARH6 vendor/firmware and endurance GSI kernel
AOSP:
S9/S9+ needs BRK3 vendor/firmware and endurance GSI kernel
N9 needs ARH6 vendor/firmware and endurance GSI kernel
Flashing instructions
1. Wipe everything
2. Flash firmware
3. Flash vendor
4. Flash gsi to system
5. Reboot recovery
6. Flash gapps
7. Flash kernel
8. Reboot
Note: skip step 5 and 6 for roms with gapps included
If you have an issue flashing gapps because of insufficient space, do the following in TWRP. Advanced wipe -> System Partition -> Repair or Change File System and Repair and Resize
Downloads:
This is my MEGA library where I host all the files you need for running your sGSI (and some extras): https://mega.nz/#F!wFFQUYbI!GZvNOBSn1wVn8U9mQDzBiw
Source code
https://github.com/TheCrazyBeaver/device_phh_treble
Credits:
Phhusson for his generic device tree
Codefox for being my main honi, the semi generic device tree and foxytreble
AzzyC for being my second honi
Eamo5 for his godlike endurance kernel
P.S. Note 9 plebs are welcome here but I won't make a thread in Note 9 forum as I don't own the device
XDA:DevDB Information
[sGSI 9.0] AOSiP / Pixel Experience / ViperOS //Personal Builds [S9/S9+/N9], ROM for the Samsung Galaxy S9
Contributors
CrazyBeaver2377, CrazyBeaver2377, CodeFox
Source Code: https://github.com/TheCrazyBeaver/device_phh_treble
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: BRK3 Vendor / Firmware
Based On: AOSP
Version Information
Status: Beta
Created 2019-02-04
Last Updated 2019-02-11
XDA:DevDB Information
[sGSI 9.0] AOSiP / Pixel Experience / AOSP //Personal Builds [S9/S9+/N9], ROM for the Samsung Galaxy S9
Contributors
CrazyBeaver2377, CrazyBeaver2377, Codefox, Rainbow_Dash
Source Code: https://github.com/TheCrazyBeaver/device_phh_treble
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: BRK3 Vendor / Firmware
Based On: AOSP
Version Information
Status: Beta
Created 2019-02-04
Last Updated 2019-02-13
reserved
Cheers, moving to your builds from now on mate
Thanks will try it tomorrow
arh6 vendor in Note9 does not install. In Download mode it gives the error : SystemDev Check Fail.Device:2 Binary 1....
Everything else works ok.
I just uploaded AOSiP, beware this is not tested yet by anyone so it might not boot!
Edit: AOSiP reported working!
Nice work I liked it
Please don't stop on this thread and tell us about any updates
"The Guy".
Thanks for all your releases man! PE is awesome along with Viper!
Since we are on the plate of AOSP roms, can we bring Euphoria back?
Or even Hazy / Discovery rom?
Thank you for all your work!
oreo firmware/vendor for a pie rom? didn't understand that though
carlesmc said:
I can`t flash on system ( twrp)
Click to expand...
Click to collapse
What do you mean exactly? You need to press the install image button and then install the system.img to the system partition.
here
edit
awesome job man
CrazyBeaver2377 said:
What do you mean exactly? You need to press the install image button and then install the system.img to the system partition.
Click to expand...
Click to collapse
I get the following error:
Cannot flash images to system
Thanks beaver! Awesome to see you publishing your work here too // macke @ teleg
Finally something new and fresh, good work ? don't give up !
What do you think about ResurrectionRemix v7.0 Pie?
Have you tried it?
Sent from my SM-G965F using Tapatalk
carlesmc said:
I get the following error:
Cannot flash images to system
Click to expand...
Click to collapse
You might need to upgrade to latest TWRP
a0007 said:
What do you think about ResurrectionRemix v7.0 Pie?
Have you tried it?
Sent from my SM-G965F using Tapatalk
Click to expand...
Click to collapse
I build what I personally like, hence personal builds. And to be honest I don't like RR (overfeatured)
If there is high demand for one particular rom I might build it and drop one that is in low demand.
As I don't want to use up too much storage and time fixing build errors I want to stay with 3 ROMs maximum.
carlesmc said:
I get the following error:
Cannot flash images to system
Click to expand...
Click to collapse
Its weird and I've had it before, just don't erase system before trying to flash, just do a factory reset, then flash the image over system, I had that error but using this works every time
CrazyBeaver2377 said:
I build what I personally like, hence personal builds. And to be honest I don't like RR (overfeatured)
If there is high demand for one particular rom I might build it and drop one that is in low demand.
As I don't want to use up too much storage and time fixing build errors I want to stay with 3 ROMs maximum.
Click to expand...
Click to collapse
Aosip working nicely on S9 here mate:good::good:
Thanks for you work , I'll flash viperOS on my N9 later tonight, thanks again.
DISCLAIMER:
1. If you don't know anything about custom ROMs please don't install this ROM.
2. If anything happens to your phone, or you brick your phone after installing this ROM, I will not be responsible for any damage whatsoever.
3. Your phone warranty may be void.
NON-LINEAGE CHANGES:
1. Native signature spoofing support is there. Can be granted to apps in settings.
2. Cloudflare(1.1.1.1) is now the system-wide DNS instead of Google DNS(8.8.8.8).
3. Motion Sensor permission will be asked when an app makes a request.
4. Although the Security Patch Level is still shown to be June-05-2021(read more here), all possible security fixes have been merged till Nov.
PREREQUISITES:
1. Officially unlocked bootloader.
2. Latest TWRP installed.
FLASHING PROCEDURE:
1. Reboot to recovery
2. PERFORM FACTORY RESET
3. Wipe Cache, System, Dalvik
5. Flash ROM
6. Flash Gapps(or use microG)
7. Reboot system
P.S.- Keep in mind that I merely followed the guide and did accordingly. I am not a ROM dev or anything. Thus, I can't fix any bugs that you may face.
I will try to update the ROM, at least, once every 3 months.
Download Link- https://sourceforge.net/projects/li...e-14.1-20211120-UNOFFICIAL-kenzo.zip/download
Device Tree:
GitHub - kodeaqua/device_xiaomi_kenzo: Default device tree for Kenzo. Making it compatible for AOSP ROMs.
Default device tree for Kenzo. Making it compatible for AOSP ROMs. - GitHub - kodeaqua/device_xiaomi_kenzo: Default device tree for Kenzo. Making it compatible for AOSP ROMs.
github.com
Kernel Source: https://github.com/magicxavi/kernel_xiaomi_msm8956
ROM source: https://github.com/LineageOS and https://github.com/syphyr
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Lineage OS
Security Patch Level: 5 June 2021
k
kk
This is just what I wanted. My father is using my Kenzo since the last 2 years and the little issues in P+ ROMs weren't something that he could deal with. So I had installed AEX 4.6 by Magicxavi. But it was EOL in Feb 2020. For updated security patches my only other option was LOS 14.1 by e/foundation which wasn't what I wanted as it had microG built-in causing several apps to not work/crash. Plus active drain in Nougat is 10-12%/h vs 15-16%/h in Pie+ and multitasking is way better as RAM usage is much lower. Gonna try this when I return home next.
Thanks.
thanks bro..
What about the three-month update?
qmag said:
What about the three-month update?
Click to expand...
Click to collapse
Can't. My exams are ongoing. proly won't be updating until next month
Tested the build over the last few days. Seems stable enough. Battery backup seems decent. Little over 13%/h AD and 0.6%/h ID, primarily web browsing and WA. It could be better as Jio coverage, despite LTE-CA, isn't really good indoors compared to Vi in my locality. RN3 is now being retired as a primary device in favour of RN10 Pro.
One issue I have noticed (which could be related to something at my end) is that the home screen seems to sort of redraw everytime I go back to it from any app. It's quite jarring.
Edit: Goodix fingerprint sensor doesn't work.