[ROM][21 Sep] AICP 15 [10.0][4G LTE][Unofficial | Enforcing | VoLTE] - Xiaomi Redmi 5 ROMs, Kernels, Recoveries, & Other

[ROM][21 Sep] AICP 15 [10.0][4G LTE][Unofficial | Enforcing | VoLTE] - Xiaomi Redmi 5 ROMs, Kernels, Recoveries, & Other

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS) we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q with a base of AOSP repositories and some additions from LineageOS for device specific repositories.
If there are any bugs, either we will sort them out, if it concerns our code base. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
DU team
Resurrection Remix team
AOSiP team
Community
...
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 15.0
AICP 15 rosy - Unofficial
Google Apps
- Open GApps
Only Pico/Nano are the recommended Open GApps packages
Please check Open GApps Package Comparison for full details
- Flame GApps
Only Basic is the recommended Flame GApps package
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
(link the best one for your device, there are several variants out there right now, nano/micro GApps from opengapps.org is almost always a good choice though)
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. Information about Xposed, EdXposed or Riru Core can be obtained from the XPosed General forums .
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is the usual behaviour on flashing a new official build by (or using) the build-in updater service.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Q. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, and Data (you might need to format the data partition!).
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work), GApps are already included for some a/b devices.
6. Reboot and set up your device, enable developer settings and in them OEM unlock/Advanced reboot/USB tethering.
7. Reboot back into TWRP recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.3 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
TWRP recovery is needed to be able to flash using the built-in OTA app.
Please make sure that you are on the latest TWRP recovery, keep in mind that this could also be an unofficial version!
On encrypted devices you will have to enter your PIN/password in TWRP before the process starts.
If you want to contribute to AICP, or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
(mention all the devs who have contributed to your device tree, kernel, vendor, etc,
only mention the main ones though, probably the top four or so, otherwise this list will be a mile long xD)
You want to see a "normal" night at the "DEV office", click here!!
Flashing Instructions:
You need to flash manually via recovery because OTA update doesn't seem to work with twrp/orangefox.
Clean Flash
• Downloaded the new rom build to your phone using the direct link or XenonOTA app
• Reboot to recovery
• Take full backup in twrp
• Wipe (system, vendor, data, cache, dalvik)
• Flash the new build
• Flash GApps package
• Reboot - The first boot can take up to 5 minutes
Dirty Flash
• Downloaded the new rom build to your phone using direct link or updater app
• Disable Magisk modules if you're using any
• Reboot to recovery
• Take full backup in twrp
• Wipe (system, vendor, cache, dalvik)
• Flash the new build
• Flash GApps package
• Reboot
What's working:
• Audio
• Bluetooth
• Call recording
• Camera/Camcorder/Flash
• Charging/Offline-charging
• Cast
• Doze/Deep-sleep
• Fingerprint
• FM radio
• Google voice assistant
• GPS - With location services
• Hotspot/Tethering
• IR
• Sensors
• Torch
• RIL (Calls, SMS, Data)
• VoLTE
• Wi-Fi
SELinux Status:
• Enforcing [without neverallows]
Known issues:
• GPS - Without location services
Untested:
• Device Encryption
Notes:
• ROM built with doge kernel, so report bugs only if you're using doge kernel
• Join, Telegram Group for support
Necessary config changes for gcam:
1) Video recording resolution should be set to 1080/720p
2) HDR mode should be turned off for selfie cam
Device Source:
• Kernel Source
• Device Source
• Vendor Source
XDA:DevDB Information
AICP, ROM for the Xiaomi Redmi 5
Contributors
xDoge
Source Code: https://github.com/AICP/
ROM OS Version: Android 10
ROM Kernel: Linux 3.18.x
ROM Firmware Required: Oreo
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 15
Created 2020-05-17
Last Updated 2020-09-21

ChangeLog
20200921
Code:
[COLOR="DimGray"][B]ROM Changes[/B]
• September security patch[/COLOR]
20200826
Code:
[COLOR="DimGray"][B]ROM Changes[/B]
• August security patch
• Doze changes
[B]Kernel Changes:[/B]
• Revert - Possible fix for "touch screen not responding for few seconds"
• Fixed idle battery drain. [Thanks to @Vishalcj17][/COLOR]
20200716
Code:
[COLOR="DimGray"][B]ROM Changes[/B]
• July security patch
[B]Kernel Changes:[/B]
• Possible fix for "touch screen not responding for few seconds"[/COLOR]
20200609
Code:
[COLOR="DimGray"][B]ROM Changes[/B]
• June security patch
• FM radio fixed[/COLOR]
20200517
Code:
[COLOR="DimGray"][B]ROM Changes[/B]
• Initial unofficial build
• Enforcing selinux[/COLOR]

FAQ
1) When official?
I haven't decided if I want to go official or not.
2) Will there be regular updates?
Atleast once/month, usually after aosp security patch is merged.
Apart from that, Ill release a new build in case of major bugs that breaks the ROM to be used as daily driver.
3) Reporting bugs
DO NOT Report bugs if
• if you didn't perform a clean install.
• if you're running a custom kernel.
• if you've installed Xposed.
• if you're using battery/thermal mods.
4) How to report bugs?
• Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
• Mention what custom stuffs you've installed in the rom, like Magisk modules, etc.
• If the problem disappears after disabling selinux, disable SELinux and grab logs using SysLog app.
• If its a random reboot, grab dmesg. [Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless.]
5) Disabling SELinux
Needs root. You can disable SELinux via the following options.
• SELinux Mode Inverter Magisk module
• SELinuxModeChanger App
• Terminal Emulator App
To disable SELinux using a terminal emulator, run the following commands
Code:
> su
> setenforce 0
6) Taking Logs
Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.
• Using adb
• Using MatLog app
• Using SysLog app for audit logs

mine

the recorder can input audio internal?

Best Q rom for rosy, thanks dev for your work.
Hope you will maintain update this rom.

Battery
Thanks for the rom but i have problem with the battery and some ghost touches here and there. You planning any update in near future? Thanks

New build is up.
20200609
Code:
[COLOR="DimGray"][B]ROM Changes[/B]
• June security patch
• FM radio fixed[/COLOR]
Ryiiiiii said:
the recorder can input audio internal?
Click to expand...
Click to collapse
AFAIK, yes.
tridi001 said:
Best Q rom for rosy, thanks dev for your work.
Hope you will maintain update this rom.
Click to expand...
Click to collapse
Yes, Ill maintain this ROM. Thanks.
nokiagye said:
Thanks for the rom but i have problem with the battery and some ghost touches here and there. You planning any update in near future? Thanks
Click to expand...
Click to collapse
What issue with battery? Ghost touches are known issue. Blame xiaomi for releasing broken kernel source.

New build is up.
20200716
Code:
[COLOR="DimGray"][B]ROM Changes[/B]
• July security patch
[B]Kernel Changes:[/B]
• Possible fix for "touch screen not responding for few seconds"[/COLOR]

Anyone guide me to set fingerprint? I cant find option for this

New build is up. Clean flash "necessary".
20200826
Code:
[COLOR="DimGray"][B]ROM Changes[/B]
• August security patch
• Doze changes
[B]Kernel Changes:[/B]
• Revert - Possible fix for "touch screen not responding for few seconds"
• Fixed idle battery drain. [Thanks to @Vishalcj17][/COLOR]
navinmholkar said:
Anyone guide me to set fingerprint? I cant find option for this
Click to expand...
Click to collapse
Settings -> Security -> Fingerprint.

LinuxPanda said:
New build is up. Clean flash "necessary".
20200826
Settings -> Security -> Fingerprint.
Click to expand...
Click to collapse
Can't find option in security. I checked fingerprint sensor via app and it's shows "fingerprint is not available or using by another app"

navinmholkar said:
Can't find option in security. I checked fingerprint sensor via app and it's shows "fingerprint is not available or using by another app"
Click to expand...
Click to collapse
Did you clean flash and using Oreo firmware? If so, then please give logs.

dirty flash all is ok
thanks

navinmholkar said:
Can't find option in security. I checked fingerprint sensor via app and it's shows "fingerprint is not available or using by another app"
Click to expand...
Click to collapse
I clean flashed it, but before that i am on havoc os so that is issue? Can i flash oreo firmware zip now and then flash new update? Sorry for bad english.
---------- Post added at 12:10 PM ---------- Previous post was at 12:08 PM ----------
LinuxPanda said:
Did you clean flash and using Oreo firmware? If so, then please give logs.
Click to expand...
Click to collapse
I clean flashed it, but before that i am on havoc os so that is issue? Can i flash oreo firmware zip now and then flash new update? Sorry for bad english.

tridi001 said:
dirty flash all is ok
thanks
Click to expand...
Click to collapse
I had issues in settings with dirty flash and D2TW setting disappeared, so said that clean flash is necessary. Thanks for the feedback.
navinmholkar said:
I clean flashed it, but before that i am on havoc os so that is issue? Can i flash oreo firmware zip now and then flash new update? Sorry for bad english.
Click to expand...
Click to collapse
I'm not sure if that could be the issue.
But flashing firmware zip won't cause any issue even if you're flashing firmware after flashing ROM. You may try flashing the correct firmware as they're are global & Chinese firmware. Thanks.

New build is up.
20200921
Code:
[COLOR="DimGray"][B]ROM Changes[/B]
• September security patch[/COLOR]

Great rom very stable

When A11 version ??

Related

[ROM][OFFICIAL][laurel_sprout] Syberia Project [12L][OSS]

Update 11/07/2022
Changelog:
Fixed GPS logspam after caf update.
Updated GPS blobs to a12.
Updated GPS stack to LA.UM.9.11.r1-05600-NICOBAR.QSSI12.0
Ported DolbyAtmos from MOTO G PRO.
Implemented VPN tethering support.
Fixed QS clock size and placement.
Bring back "old" style QS brightness slider (temporary, until new style is fixed).
Spoiler: Archive
Update 30/06/2022
Changelog:
Removed mic boost.
VoiP changes.
Added keylayout for wired headphones.
Again increased haptics a bit.
Dropping prebuilt camera stack and building OSS camera stack.
Reworked Syberia UI Style.
Notes:
This build contains big changes for UI, so to avoid issues "clean flash" recommended
Update 01/06/2022
Changelog:
Implemented UDFPS dim layer (no brightness flicker)
Another VOiP fixes.
Added custom UDFPS animations and icons.
Added missing FM radio.
Increased haptics strength a bit.
Improved UDFPS scanning speed.
Update 17/04/2022
Changelog:
Improved boot time for ~3sec.
Fixed some system errors from log spam.
Added new NTP servers for faster Location.
Improved GPS stability and accuracy.
Enabled LiveDisplay HAL for picture adjustment.
Improved UDFPS callback delay’s.
Lowered size of UDFPS scan circle-point (theoretically this change should increase scanning speed but requires a good finger scan)
Imported from stock Health HAL (fixes charging calculations)
Upstreamed kernel to 4.14.275
Selinux Enforcing
Update 28/09/2021
Changelog:
Initial Build
Switched to ICE FBE encryption
Vendor updated to CAF LA.UM.9.11.r1-04500-NICOBAR.0 (except camera, audio, gps and DRM)
Switched to AOSP BT impl
Bugs:
Some modes in MIUI camera are not working

Reserved

This is fantastic!
But no matter what I do I can't install even core gapps. I flash them via adb sideload, perform a factory reset and nothing.. I feel like I've tried everything. There's no problem with Magisk tho. Can you please include some gapps in the rom?

Amazing news! Official ROM and latest Android version!
Hopefully the permissive SELinux can be sorted out with enough logs, but still, very nice work so far.

Does anyone can help me about the recovery via fastboot installation? I mean is there need to change slot e.t.c... And after recoverie's flashing, how we reboot to recovery, via a simple fastboot command?Thanks.

jeff.rey said:
This is fantastic!
But no matter what I do I can't install even core gapps. I flash them via adb sideload, perform a factory reset and nothing.. I feel like I've tried everything. There's no problem with Magisk tho. Can you please include some gapps in the rom?
Click to expand...
Click to collapse
Yeah, a12 not so fast at gapps bringup, we have limited chose to BitGapps, Nikgapps or FlameGapps, and Nikgapps with FlameGapps have some issues while flashing it on some devices (already reported to the dev), and only BitGapps works fine, but there are only Minimal package.
However i created a modified Nikgapps(stock) package - download

papafan said:
Does anyone can help me about the recovery via fastboot installation? I mean is there need to change slot e.t.c... And after recoverie's flashing, how we reboot to recovery, via a simple fastboot command?Thanks.
Click to expand...
Click to collapse
Generally speaking, IMHO doesn't matter how you got into recovery be it by command or power+vol+

maluus said:
Generally speaking, IMHO doesn't matter how you got into recovery be it by command or power+vol
Click to expand...
Click to collapse
And the slots? Is there any need to change them during flashing?

papafan said:
And the slots? Is there any need to change them during flashing?
Click to expand...
Click to collapse
When you flash something over fastboot you are to manage slots. When you do by recovery it manages slots. So up to flashing the recovery you'll manage slots. Afterwards flashes are done by recovery. Since recovery changes slots when you flash rom or update. Both slots should have the same firmware level (e.g. android 11 firmware.) If you have incompatible firmware on other slot it may cause problems on next update or full flash. IMHO op should explain a bit more about slot management. The same process is known to cause unwanted problems before. You can check the lineageos 18.1 oss thread for it.

Magicxavi said:
Update 28/09/2021
Changelog:
* Initial Build
* Switched to ICE FBE encryption
* Vendor updated to CAF LA.UM.9.11.r1-04500-NICOBAR.0 (except camera, audio, gps and DRM)
* Switched to AOSP BT impl
Bugs:
* Some modes in MIUI camera are not working
* Selinux Permissive
Click to expand...
Click to collapse
Hi,
Is it possible to safely install this ROM from android 10 stock EU version? (or, must I already be under A11 and in this case what should I do?)
I'm still stuck on A10 and the September 2020 security patch on my French version of the Mi A3
Sorry I'm a beginner

I think you must first update to a11. Do factory reset on your a10 first.

NikBos said:
I think you must first update to a11. Do factory reset on your a10 first.
Click to expand...
Click to collapse
Problem is that I still do not have the possibility to do OTA to A11...
In France we are literally blocked on A10 and the September 2020 security patch...

Then you can flash it with mi flash.

NikBos said:
Then you can flash it with mi flash.
Click to expand...
Click to collapse
I don't understand what to do in order not to lose my data, I would just like to update.
If I want to install the update without fear I have to make a backup. OK
To make a full backup I need TWRP. OK
To install TWRP to be able to make my backup and not lose any data I have to root my device with magisk. OK
If I root my device with magisk it makes me wipe all my data...

Hobbi1 said:
I don't understand what to do in order not to lose my data, I would just like to update.
If I want to install the update without fear I have to make a backup. OK
To make a full backup I need TWRP. OK
To install TWRP to be able to make my backup and not lose any data I have to root my device with magisk. OK
If I root my device with magisk it makes me wipe all my data...
Click to expand...
Click to collapse
If I were you I wouldn't rely on twrp for backup. Because once you update to A11 you ll have problem with twrp hence restoring it. On the other hand even if you are able to restore it somehow, probably you would end up with a bootloop anyway. Because when android version changes, data partition backup of other versions won't be compatible with newer one. I suggest you to have per app backup within os.

New update is out!

New update is out!

everything working fine, new icons and animations for udfps are pretty good and now it recognizes really fast. one thing i noticed is that the screen flicks when unlocking with figngerprint but just a little bit, its not something that really bothers as before. updating was fine without even needing to make a backup. anyways ty for, basically, the best rom for mi a3, if it wasnt that, i think we all would have already changed it. keep up the good work!

I just did the installation and the rom is fantastic!
Leaving Miui..
Everything seems to work very well.
Congratulations to those involved!!
Sorry for my english, I'm from Brazil

[UNOFFICIAL] [ROM] Spark-OS - Stable- for Mi A3 (Laurel Sprout)

Additional Screenshots
Updated: 20-March-2023
For more screenshots, check telegram channel.

23. Changelogs 02-05-2023 <<Optional Update - February 2023>>
Still February patchImprovements in UI/UX - Bigger FP layout, adjusted corner cutouts and paddingsFaster App launchesPrebuilt system intelligence and no more crashesVoice Improvements (Better sound in recordings and voice notes)Fully functional call recording in google dialer ( Install Google app from playstore to use this feature )Mic fixes in some apps (Duolingo, etc)Note:1. Users can dirty flash if you're from any Spark 13.5.5, but if you want cleaner experience, Clean flash recommended. For others, clean flash mandatory!!2. For your info, Next monthly release will be delayed... (no comment)
22. Changelogs 01-04-2023 <<Optional Update - February 2023>>
Addressed wifi denials - Wifi should be even faster and stable nowAddressed camera server denials - Most Gcams should workBluetooth HD audio (broken in previous build) is fixed. Tested: APTX, SBC. LDAC should work probablyReworked night light implementation and fixed a fingerprint_hal denialRemoved certain performance props that have been hogging battery and memory21. Changelogs 12-03-2023 <<Fixes - February 2023>>
Improvement in all aspects (App rendering, UDFPS, Performance) and with a lot of goodies inside (both device and source side changes)Note: This build is almost a complete package. If you face any major bugs, feel free to report in this thread with logs. Perform a clean flash. Dirty flash will not boot into system
20. Changelogs 13-02-2023 <<Monthly UPDATE - February 2023>>
Fixed CTS. Safetynet passes with or without rootTuned UI paddings a little bitIntroduced battery-StatsSome under the hood changes
19. Changelogs 16-01-2023 <<Monthly UPDATE - January 2023>>
Scrolling and app rendering improvementsAddressed audio denialsFixed volume controls in VOIP appsSwitched back to Laurel's fingerprintUI TweaksReadme:UDFPS on AOD and off-screen is buggy and has been removedFlash 912 Kernel for smoother experience
18. Changelogs 22-12-2022 <<Monthly UPDATE - December 2022>>
FOD Improvements (Now faster than previous versions)Implemented AOD-DT2W in sourceUpdated power profile to A13 sourceRemoved prebuilt camera as of nowFixed screen-recording lagsReadme:Rom's source has been rebased after Google's December Patch. You may face some cosmetic glitches rarely in launcher and in AOD's DT2W. They will be fixed in upcoming releases.If you encounter any app-installation or out of space problems in playstore, clear data on playstore, playservices and reboot system. Then, proceed to app installation normally.17. Changelogs 15-11-2022 <<Monthly UPDATE - November 2022>>
App Lock and Face Unlock are backFPS and UI improvementsWorkarounds in automotive librariesSome Under the hood changes16. Changelogs 09-10-2022 <<Monthly UPDATE - October 2022>>
Added AndroidAuto-stub as system appFM Radio and Pixel Unlimited photos are backSeveral under-the-hood performance and battery optimizations**Users who dirty flash kindly check apps' network-permissions. If disabled, enable them or do a clean flash.15. Changelogs 27-09-2022 <<Bug fix Update - September 2022>>
Fixed app-incompatibility issues from playstore installationFixed microphone delays in most apps and callsUI tweaks14. Changelogs 16-09-2022 <<Android 13 Upgrade - September 2022>>
Upgraded to Android 13. Initial Build=============================================================
13. Changelogs 24-08-2022 <<Optional UPDATE - August 2022>>
Added missing automotive blobs from stock v12.0.22.0 (android car integration)Reduced the number of CPU's running on the background to 1Updated some halsDisabled VSync on cpu rendered apps (fps optimization)Some under the hood tweaks
12. Changelogs 19-08-2022 <<Monthly UPDATE - August 2022>>
Switched back to A12 QS styleFixed Adaptive Brightness, AOD overlaysRemoved XiaomiParts, Improvized Haptics and Reduced boot-timeUpdated Adreno blobs to LA.UM.9.16.r2-02500-MANNAR.011. Changelogs 23-07-2022 <<Monthly UPDATE - July 2022 (2)>>
Second and complete Release of this monthFixed Brightness slider glitchRemoved Lawnchair, Spark launcher set as default (source side)GameSpace ImprovementsUI Optimizations
10. Changelogs 19-07-2022 <<Monthly UPDATE - July 2022>>
July Raven FPFixed mic issues in app voice calls (voice may have some delay initially)Android 11 QS style (source side) - (Note: As of now, no toggle switch go back to A12 QS style)
9. Changelogs 02-07-2022 <<OPTIONAL UPDATE - June 2022>>
Fixed FOD max Brightness bug. Stock like FOD experienceUnder the hood optimizations8. Changelogs 26-06-2022 <<OPTIONAL UPDATE - June 2022>>
Improvements in Wifi, VoIP and Location services(Users can dirty flash if you're from 19-June-2022 Spark 12.4)7. Changelogs 19-06-2022 <<UPDATE - STABLE-ANDROID 12L - June 2022>>
Stock like FODLawnchair as defaultFixed GPS reception on some apps with accuracyNew encryption props addedSome Feature addons and improvementsRaven June FP6. Changelogs 16-05-2022 <<UPDATE - STABLE-ANDROID 12L - May 2022>>
Magisk (root) supported, no more bootloops or crashes.Launcher3 with D2TS as defaultWifi Hotspot client listUpdated Pixel PropsSpark-OS Recovery includedIgnore-window-secure-flags supportUpdated translations.
5. Changelogs 05-05-2022 <<UPDATE - BETA-ANDROID 12L - May 2022>>
Note: ROOT/Magisk doesn't work. Those who don't root can flash the buildNuked Pixel launcher, Launcher3 with D2TS as defaultWifi Hotspot client listLight QS tilesIgnore window secure flags supportUpdated Raven FP to May 2022Removed Xiaomi parts and most Gapps (causing system img to exceed its size)Some additional tune-ups in UI
4. Changelogs 09-04-2022 <<UPGRADE - ANDROID 12L - April 2022>>
Fixed volume control in wired headsets during calls on VOIP appsFixed some cosmetic bugs (lockscreen wallpaper, etc)Updated Raven FP to April 2022Pixel launcherFixed Face unlock registration on app lock
3. Changelogs 02-03-2022 <<FEATURES UPDATE - February 2022>>
Mic OptimizationsAdded Face UnlockQuick TapApp lock and more2. Changelogs 25-02-2022
Minor system optimizations for enhanced stability<<OPTIONAL UPDATE>>
1. Changelogs 13-02-2022
Initial BuildLawnchair as default launcher and much more.

--Reserved--

what gapps package is included?

Kieling said:
what gapps package is included?
Click to expand...
Click to collapse
Default gapps that comes with the source

Can you post a video recording of the fod testing on telegram or something, it would be good

Elhabib8 said:
Can you post a video recording of the fod testing on telegram or something, it would be good
Click to expand...
Click to collapse
Recording of FOD is posted Here. You can also check the telegram channel

Two questions: The los recovery isn't built in rom, so we must flash the zip. installer. Isn't? The magisk zip must be sideloaded and no installed from cd card. Correct?
Did anyone test the rom?

papafan said:
Two questions: The los recovery isn't built in rom, so we must flash the zip. installer. Isn't? The magisk zip must be sideloaded and no installed from cd card. Correct?
Did anyone test the rom?
Click to expand...
Click to collapse
Yes. LOS recovery is not inbuilt. You have to sideload the zip after sideloading the rom. After rebooting to recovery flash magisk by the same procedure.
I haven't tested "installing from SD Card functionality". From telegram groups of other popular custom roms, some people install through this SD card procedure. People who use the method may share their experience.

bro there is bug in Udfps animations they all are little off position...
and i request can u add Quick tap feature in the next build...
And i have suggestions for users to Better FOD
:- Use batt 912
:- Better if u use only stock icon and stock FOD animation
:- change FOD Press colour to white(one which has red colour inside)
:- This one makes the FOD very accurate but at one cost which is u gotta change ur SElinux to permissive...

Bhavishchhabra said:
bro there is bug in Udfps animations they all are little off position...
and i request can u add Quick tap feature in the next build...
And i have suggestions for users to Better FOD
:- Use batt 912
:- Better if u use only stock icon and stock FOD animation
:- change FOD Press colour to white(one which has red colour inside)
:- This one makes the FOD very accurate but at one cost which is u gotta change ur SElinux to permissive...
Click to expand...
Click to collapse
Didn't notice the animation offset earlier as I have not used it. Yes, the Quicktap has been added already in device tree, it will be available once the source is updated. Good suggestions!

Bro my device security level Is still L3...how to change it to L1?

The mainer bug I am facing is I can't change wallpaper in lockscreen. The monet engine I think needs optimization... I would prefer in lockscreen clock more fonts. The left shortcut in lockscreen doesn' t work.
My first thoughts. Thanks.

Bhavishchhabra said:
View attachment 5540865Bro my device security level Is still L3...how to change it to L1?
Click to expand...
Click to collapse
Try going back to stock preferably December 2021 update, Flash persist partition ( check google or here) and lock bootloader. Then Update to latest available patch. Check if it changes to L1.
If you are still stuck on L3, you cannot come back to L1. It depends on your luck.
Note: Remember you are messing with persist. If you do anything wrong, You may end up messing your Sensors, IMEI, etc.

papafan said:
The mainer bug I am facing is I can't change wallpaper in lockscreen. The monet engine I think needs optimization... I would prefer in lockscreen clock more fonts. The left shortcut in lockscreen doesn' t work.
My first thoughts. Thanks.
Click to expand...
Click to collapse
Some users of Spark-rom of other devices reported the same monet issues. It is due to lawnchair shipped with the source. But, on my device monet works fine even on lockscreen.
Try clearing data on lawnchair, btw, if you have rooted and if lawnchair asks root permission, don't give! All others ( Fonts and shortcuts) too depends on ROM's source.

manojkrishkumar said:
Some users of Spark-rom of other devices reported the same monet issues. It is due to lawnchair shipped with the source. But, on my device monet works fine even on lockscreen.
Try clearing data on lawnchair, btw, if you have rooted and if lawnchair asks root permission, don't give! All others ( Fonts and shortcuts) too depends on ROM's source.
Click to expand...
Click to collapse
About the lockscreen wall paper? I can't change it, takes only the wall of main screen.

papafan said:
About the lockscreen wall paper? I can't change it, takes only the wall of main screen.
Click to expand...
Click to collapse
I've tested it in 25-02-2022 build. Lawnchair is the one creating the problem, when I tried to port pixel launcher it creates stability issues. They have to fix in source.

Bhavishchhabra said:
bro there is bug in Udfps animations they all are little off position...
and i request can u add Quick tap feature in the next build...
And i have suggestions for users to Better FOD
:- Use batt 912
:- Better if u use only stock icon and stock FOD animation
:- change FOD Press colour to white(one which has red colour inside)
:- This one makes the FOD very accurate but at one cost which is u gotta change ur SElinux to permissive...
Click to expand...
Click to collapse
New UDFPS animations, Quicktap, Face unlock are added and offsetting is fixed

[ROM][11][UNOFFICIAL] LineageOS 18.1 for Lenovo P2

Installation Instructions
Remember, making a backup of your data before proceeding is recommended
If you are coming from Stock ROM, please refer to the instructions below:
Install LineageOS on kuntao
If you are coming from the latest official build, please follow these to a clean flash:
1- Wipe:
- Dalvik
- System
- Data
- Cache
- Internal Storage (optional)
2- Flash ROM ZIP, Gapps, Magisk addon, etc
3- Clean Cache
4- Reboot to system
5- Wait until it boots for the first time (may take some minutes)
Update Instructions
For updating from one of my builds to another, please do the following:
1- Download ROM ZIP and copy to the phone
2- Reboot to recovery
3- Flash ROM ZIP
4- Reboot to system

Boot loop/Boot inside TWRP Fix Instructions
1- Reboot to recovery
2- Wipe > Format data (careful, will erase everything and remove storage encryption)
3- Then repeat wipe from step 1 of Installation Instructions
4- Reboot to recovery again
5- Copy the ZIP files (ROM, Gapps...) to internal storage
6- Flash ZIP files again
7- Reboot to system
8- Wait for the boot and encryption process (may take some minutes)
9- Phone will reboot automatically and then start the system
10- Finish the setup wizard (Wifi, Google acc, etc)
10.1- Reboot the system in order to finish installing Magisk App (optional)
SafetyNet Status Fix Instructions
1- Make sure Magisk was properly installed
2- Open the Magisk App
3- Open App settings (wheel on the top right side of the screen)
4- Enable "Zygisk"
5- Enable "DenyList"
6- Open "Configure DenyList"
6.1- Click the three dots on top right corner of the screen
6.2- Enable "Show system apps"
6.3- On "Google Play services": Enable "com.google.android.gms" & "com.google.android.gms.unstable"
6.4- On "Google Play Store": Enable "com.android.vending"
7- Click on the back arrow (on top left)
8- Reboot your system
9- Test again (now it should pass)
Note: For Magisk versions below 26.x, it might not be needed to follow steps 6.1 and 6.2 as the system apps should be already being displayed.
ROM Change log
Code:
01/28/2023
- Initial release
01/31/2023
- Sync latest LOS source
02/20/2023
- Update LOS modules
-- packages/modules/NeuralNetworks
-- system/connectivity/wificond
- Sync latest LOS source
- Merge February security patch
03/28/2023
- Update LOS components
-- Manifest: Sync x86_64 webview prebuilts again
-- Update zlib source
- Sync latest LOS source
- Merge March security patch
04/21/2023
- Device Tree: Change proprietary blobs from official sources to themuppets' ones
- LOS: apn: update for T Star, Vibo and AURORA
- Sync latest LOS source
- Merge April security patch
05/10/2023
- Device Tree: Updates translations
- Sync latest LOS sources
-- Track vendor/crowdin
- Merge May security patch
06/12/2023
- Fetch latest Device Tree
-- Merge updated translations
- Sync latest LOS sources
- Merge June security patch

ROM ScreenshotsAttached below

February 2023 ReleaseChangelog: Plz, read first post
Download URLs: GDrive | MEGA | SourceForge
Enjoy!

Thanks very much for keeping this alive.

Hi,
I have a stock ROM 7, but I would like to install a newer version of Android because some app doesn't install anymore on Android 7... So, I would like to try LineageOS 18.1. I have already unlocked and rooted my p2a42.
I've read for around 3h lots of posts and opinions on this forum. There is a huge information on it, you are awesome!!
However, I don't know where to find a "build" for my p2a42. When following the "instruction" link (https://wiki.lineageos.org/devices/kuntao/install) it's required to "build" an installation package. However, it seems that p2a42 is not anymore recognised (https://wiki.lineageos.org/devices/kuntao/build).
Furthermore, I've read that the proposed MEGA links are just for updating from previous LyneageOS versions. So, any advise on how to install LyneageOS in my stock ROM 7?
Thanks!

escombralls said:
Hi,
I have a stock ROM 7, but I would like to install a newer version of Android because some app doesn't install anymore on Android 7... So, I would like to try LineageOS 18.1. I have already unlocked and rooted my p2a42.
I've read for around 3h lots of posts and opinions on this forum. There is a huge information on it, you are awesome!!
However, I don't know where to find a "build" for my p2a42. When following the "instruction" link (https://wiki.lineageos.org/devices/kuntao/install) it's required to "build" an installation package. However, it seems that p2a42 is not anymore recognised (https://wiki.lineageos.org/devices/kuntao/build).
Furthermore, I've read that the proposed MEGA links are just for updating from previous LyneageOS versions. So, any advise on how to install LyneageOS in my stock ROM 7?
Thanks!
Click to expand...
Click to collapse
Hello,
To install LOS18.1 you should have a TWRP recovery already installed on your phone. Afterwards you have to download the ROM ZIP from any of the URLs on the first post (this will contain the OS, you can download the latest version, this is the build you are looking for). Then in order to have access to the Google Services (GMail, Play Store, etc) you must install GApps (URLs linked on the first post too).
Backup your data, perform step 1 of install instructions (wipe part) then copy the downloaded files to the phone's internal storage, then you can follow the other steps. This should give you the LineageOS custom OS based on android 11.
Note that the Stock ROM is Lenovo's android OS. LineageOS is another OS based on AOSP. So by installing LOS you will be switching the OS part of your phone.
I hope I could clarify the process to you, if you have any other questions please feel free to post them here

Thanks for the reply. It runs flawlessly.!!

March 2023 ReleaseChange log:
- Update LOS components
-- Manifest: Sync x86_64 webview prebuilts again
-- Update zlib source
- Sync latest LOS source
- Merge March security patch
Download URLs: GDrive | MEGA | SourceForge
Notes:
- Release was a bit delayed because of testing process (thanks @en666 for being our tester)
- Starting from next release, only the most updated build will be available on Google Drive (due to storage limitations). Mega & Source Forge will remain normal, so if you need a past build, refer to one of the URLs from first post, thanks for understanding.
Enjoy!

First time installing. No issues aside from looking up some instructions for twrp and adb and ignoring some that are on the lineageos page. Came from Android 7, so far it works great. Installed this on my dads P2, thinking I'll try your lineageos 20 on my own P2 and see how that goes. Thank you for keeping this phone alive.

April 2023 Release
Change log:
- DT: Change proprietary blobs from official sources to TheMuppets' ones
- LOS: apn: update for T Star, Vibo and AURORA
- Sync latest LOS source
- Merge April security patch
Download URLs: GDrive | MEGA | SourceForge
Notes:
- If clean flashing, please use NikGapps because OpenGapps will cause system to not boot (URLs already updated on OP)
- Magisk v26.x can be flashed through TWRP as usual, and IFAIK it works even without the "additional setup", so you can ignore it (trying to install Magisk via its app doesn't work, it keeps flashing boot image indefinitely)
- As stated on previous release announcement, only the most updated build is available on Google Drive, the other ones were purged (reason: storage limitations)
Enjoy!

Regards,
some one have problem with dirty flashing/upgrade from March ?
So, uninstalled Magisk, decrypted and after upgrade which passed fine I can't get to Normal screen just returning to Recovery after some time. Every time. Made backups, earlier, so no warry.
THX

Hey guys!
For those who did a clean install with the latest April release, can you please check if the phone is using Galileo satellites now with the blobs from TheMuppets?
Thanks!

3volution3 said:
Hey guys!
For those who did a clean install with the latest April release, can you please check if the phone is using Galileo satellites now with the blobs from TheMuppets?
Thanks!
Click to expand...
Click to collapse
Hello,
I'm not currently on EU, so I couldn't test it out. I asked one of the testers and he said that unfortunately Galileo satellites weren't being used to GPS/GNSS.
Furthermore, according to GSM Arena and LineageOS wiki, our P2 doesn't support Galileo satellites.
Regards.

leo_97 said:
Hello,
I'm not currently on EU, so I couldn't test it out. I asked one of the testers and he said that unfortunately Galileo satellites weren't being used to GPS/GNSS.
Furthermore, according to GSM Arena and LineageOS wiki, our P2 doesn't support Galileo satellites.
Regards.
Click to expand...
Click to collapse
Alright, thanks. Galileo support just needs an update from the manufacturer. The hardware for GPS and Galileo is the same as long as the chipset supports it (which in the case of our P2 it does). A few devices from other manufacturers got the update, but unfortunately the P2 didn't. I was just wondering if the blobs from TheMuppets were updated with files from a more recent SD625 device with Galileo support, but apparently not. They are just the same'ol blobs.

May 2023 Release
Change log:
- Device Tree: Updates translations
- Sync latest LOS sources
-- Track vendor/crowdin
- Merge May security patch
Download URLs: GDrive | MEGA | SF
Notes:
- If clean flashing, please use NikGapps because OpenGapps will cause system to not boot (URLs already updated on OP)
- Magisk v26.x can be flashed through TWRP as usual, and IFAIK it works even without the "additional setup", so you can ignore it (trying to install Magisk via its app doesn't work, it keeps flashing boot image indefinitely)
- If dirty flashing, flashing Magisk ZIP again may be needed
Enjoy!

June 2023 Release
Change log:
- Fetch latest Device Tree
-- Merge updated translations
- Sync latest LOS sources
- Merge June security patch
Download URLs: GDrive | MEGA | SF
Notes:
- If clean flashing, please use NikGapps because OpenGapps will cause system to not boot
- Magisk v26.x can be flashed through TWRP as usual, and IFAIK it works even without the "additional setup", so you can ignore it (trying to install Magisk via its app doesn't work, it keeps flashing boot image indefinitely)
Enjoy!

[ROM][12.1][UNOFFICIAL] LineageOS 19.1 for Lenovo P2

Installation Instructions
Remember, making a backup of your data before proceeding is recommended
If you are coming from Stock ROM, please refer first to the instructions below:
Install LineageOS on kuntao
If you are coming from astridxx previous build (aka lineage-19.1-20220822-UNOFFICIAL-kuntao) or my initial build (aka lineage-19.1-20230222-UNOFFICIAL-kuntao) or any version of LOS18.1 or below, you must perform a clean flash. Clean flash instructions:
0- Make a backup (optional, but recommended)
1- Reboot to recovery
2- Format data (will delete all your data!)
3- Reboot to recovery again
4- Wipe > Advanced Wipe:
- Dalvik
- System
- Vendor
- Data
- Cache
- Internal Storage (optional, but recommended)
5- Flash ROM ZIP, Gapps, Gapps add-ons, Magisk add-on, etc
6- Reboot to system
7- Wait until it boots for the first time (may take some minutes)
Update Instructions
NOTE: Dirty flash from any of the aforementioned builds is not supported, device trees were changed. You have been warned!
For updating from one of my builds to another (aka dirty flashing), please do the following:
1- Download ROM ZIP and copy it to the phone
2- Reboot to recovery
3- Flash ROM ZIP
4- Clean cache
5- Reboot to system

Known Issues- Storage encryption is partially broken (if your /data partition is unencrypted, trying to encrypt it using ROM menu will result in a dead OS; if already encrypted, storage encryption may or may not work. IFAIK, it's a kernel side issue)
- Device may not go to deep sleep
- Storage forceencrypt flag is disabled (to encrypt /data partition follow the instructions below)
- TWRP backups are broken (read notes below)
- You tell
Google Play Store Update Bug
If Google Play Store app keeps failing to find updates for apps with message "Something went wrong. Try again.", just clear its data and then it should work again
SafetyNet Check Fails
If your device is rooted, please, follow the instructions contained here
Magisk is Gone After First Boot
Please, just reflash Magisk again (i.e. Reboot to recovery > Flash ZIP > Reboot back to system)
How to encrypt data partition
0- Backup your files (this process will erase everything)
1- Boot to TWRP recovery
1.1- Wipe > Format data > Reboot to system
2- Settings menu > Security > Encryption & credentials > Encrypt phone
3- Reboot to system again
Error restoring TWRP system backups
It looks like TWRP backups are broken for now, so please, if this is a must have for you, you can try to install OrangeFox recovey and follow these instructions (thanks @Zdeslav for that)
ROM Change logs
Code:
02/22/2023
- Initial release
02/27/2023
- Sync latest LOS sources
- Device Tree change: Use old A12L dt instead of los
- Add Lenovo Parts menu (fp gestures, USB fast charge, in-call audio gain, screen kcal)
- Updates phone vibration strength
- Add fix to device deep sleep issue
- Many more changes
03/29/2023
- Fetch latest Device Tree sources
-- vendorsetup.sh: Add Trebuchet patch
-- AOSP WFD doesn't support protected Wi-Fi Display buffers
-- Overlays:
--- Enable voWIFI support
--- Disable IMS features for Turkiye networks
-- Don't warn user about FC in Vanced microG
-- DT rootdir:
--- Add cpuset for the camera daemon
--- Remove permission restrictions to the socket file
--- Restore iio sensor device6 on boot
-- Bump graphene camera version to 60
-- Don't force enable ims features
-- sepolicy: Address sensor hal denials
- Update LOS components
-- Manifest: Sync x86_64 webview prebuilts again
-- Update zlib source
- Sync latest LOS source
- Merge March security patch
04/09/2023
- Fetch latest Device Tree sources
-- Add navbar enable/disable support
-- fs: Revert sdfat update for OTG
-- block: Add zen io scheduler
-- dts: Decrease BCL low battery threshold to 5%
-- DeskClock:
--- Wallpaper based text coloring for digital
--- Adapt digital clocks to S style
--- Remove night mode
-- Trebuchet:
--- Kill haptics in recents
--- Make overview scrim transparent again
-- Nfc: Fix Mifare Classic reading
- Update LOS components:
-- lineage: Track the FMRadio App and dependencies
- Sync latest LOS source
04/19/2023
- Fetch latest Device Tree sources:
-- sepolicy: Silence tracingproxy_service neverallow denial
-- sepolicy: Allow system_app to access storaged via IPC
- Sync latest LOS source
- Merge April security patch
05/09/2023
- Fetch latest Device Tree sources:
-- Bump graphene camera version to 62
-- devicesettings: Protect broadcast to fingerprint gestures
-- rootdir: Remove permission restrictions to the socket file
- Sync latest LOS source
- Merge May security patch
06/11/2023
- Fetch latest Device Tree sources:
-- parts: Update few parts icon
-- vendorsetup.sh: Use depth=1
-- Remove pixel_2016_exclusive
-- Bump graphene camera version to 63
- Sync latest LOS sources:
-- Additional zstd cmdline tools
-- zstd compression support for rsync
-- 2023-06 ASB patching: packages/apps/Traceur
- Merge June security patch

ROM Screenshots
Attached below. Others are available here.

February 27th 2023 Release
Changelog:
- Sync latest LOS sources
- Device Tree change: Use old A12L dt instead of los
- Add Lenovo Parts menu (fp gestures, USB fast charge, in-call audio gain, screen kcal)
- Updates phone vibration strength
- Add fix to device deep sleep issue
- Many more changes
Download URLs: GDrive | SF
Dirty flash still not supported (tree changed), please make a clean flash

Thank you so much for keepng Lineage alive, its very much appreciated.

@leo_97 thank you for this new build! Installed it straight away and now the phone is running since then and also, I've flashed with battery at 67% and atm, after a quite hard usage to test out the new features, I'm on 13%. Basically, so far so good!
p2a42, twrp 3.7, rooted, unencrypted

Thank you @leo_97 !
I was frustrated that Lineageos 18.1 was no longer maintained when I saw this update!
It's amazing
To all users and developers who tested and created this ROM, is it time to switch on this version ?
Or is it better to wait ?
For example, automatic update is possible after install ?

bidulez said:
automatic update is possible after install ?
Click to expand...
Click to collapse
No

bidulez said:
Thank you @leo_97 !
I was frustrated that Lineageos 18.1 was no longer maintained when I saw this update!
It's amazing
To all users and developers who tested and created this ROM, is it time to switch on this version ?
Or is it better to wait ?
For example, automatic update is possible after install ?
Click to expand...
Click to collapse
You are welcome
If it's time to switch, I believe it's a matter of personal decision. Maybe you could wait the next build and then decide...
If with "automatic updates" you mean OTA updates, then the answer (as already pointed out by @utwer ) is no. But once the trees are stable enough, I hope every user will be able to just update to the newer versions flashing ROM ZIP through TWRP (just like it's done on LOS18.1)
BTW, IDK if you already saw it, but we are maintaining a monthly build of LOS18.1 which you can download from here. The source tree used there is far more tested (as it's older) than this one. Anyway, except by the encryption thing, you shouldn't have any problems using this LOS19.1 ROM as our amazing developers made an excellent job here.

Reg, Ive installed it and I may say it is quite good. Not tried to root it yet. Dont have direct problems with ROM and functionality, for me everything works. Camera, Location, GSM, Data, WiFi. With developer options I've turned off Animation scale on three options to OFF, and is good. Stable reliable.
MindTheGapps-12.1 works every app from Google, Phone, Contact, Gmail, maps...etc...
What I need root mostly is for Call recording (Skvalex) and Viper4Android.
Some words about twrp-3.7.0_9-0-kuntao.img,
With this I have only problems, so far I lost a few backups and I need to install it all over again a few times allready. Disappointed very. I can't rally on this when I make a nandroid ba.ckups.
Also lost backups for LOS18.1 and I am been very pis....ed off. Error 255 on System recovery, other Data, Boot, EFS, Vendor, etc.. recovery is good.
So I've installed OrageFox for Kuntao. Tried several backups to restore already and I may say I am very satisfied. Puh
What is on my mind, when I installed a Magisk 25.2, no matter of LOS 18.1 or 19.1 with very few modules, after 7-8 reboots I've got boot loops which is beyond repairable.. Try to remove modules in TWRP in file manager, uninstall whole magisk, no way, but what it is seems that DATA got corrupted some how, everytime.
There were also installed TWRP mentioned above.
Now I am with OrangeFox and I will try tomorrow to Root it and see is there any connection between Magisk and recovery software (OrangeFox or TWRP).
Reg

Tried quickly this ROM yesterday. In general all working, but didn't test much.
Few feedbacks:
-Scaler for brightness level is weird, very different from the original Lenovo roms. Anyway, not really important, but something that I noticed.
-Missing haptic feedback when using the fingerprint reader as a gesture button. Again, not critical, but I am really accustomed to it and thus I noticed immediately.
-Missing haptic feedback intensity regulation, or could not find it. It's there for general call/notification vibration, but if I remember correctly lineage could also change haptic.
Impressed that you could integrate also some lenovo features, even if of course not all of them
If you want me to test something more specific, please let me know. Ah, my model is the 4 GB/ 64 GB combination.
Cheers!

leo_97 said:
You are welcome
If it's time to switch, I believe it's a matter of personal decision. Maybe you could wait the next build and then decide...
If with "automatic updates" you mean OTA updates, then the answer (as already pointed out by @utwer ) is no. But once the trees are stable enough, I hope every user will be able to just update to the newer versions flashing ROM ZIP through TWRP (just like it's done on LOS18.1)
BTW, IDK if you already saw it, but we are maintaining a monthly build of LOS18.1 which you can download from here. The source tree used there is far more tested (as it's older) than this one. Anyway, except by the encryption thing, you shouldn't have any problems using this LOS19.1 ROM as our amazing developers made an excellent job here.
Click to expand...
Click to collapse
So for 18.1 we can just flash the newer versions via TWRP and do not have to reinstall the entire ROM?

Zdeslav said:
Reg, Ive installed it and I may say it is quite good. Not tried to root it yet. Dont have direct problems with ROM and functionality, for me everything works. Camera, Location, GSM, Data, WiFi. With developer options I've turned off Animation scale on three options to OFF, and is good. Stable reliable.
MindTheGapps-12.1 works every app from Google, Phone, Contact, Gmail, maps...etc...
What I need root mostly is for Call recording (Skvalex) and Viper4Android.
Some words about twrp-3.7.0_9-0-kuntao.img,
With this I have only problems, so far I lost a few backups and I need to install it all over again a few times allready. Disappointed very. I can't rally on this when I make a nandroid ba.ckups.
Also lost backups for LOS18.1 and I am been very pis....ed off. Error 255 on System recovery, other Data, Boot, EFS, Vendor, etc.. recovery is good.
So I've installed OrageFox for Kuntao. Tried several backups to restore already and I may say I am very satisfied. Puh
What is on my mind, when I installed a Magisk 25.2, no matter of LOS 18.1 or 19.1 with very few modules, after 7-8 reboots I've got boot loops which is beyond repairable.. Try to remove modules in TWRP in file manager, uninstall whole magisk, no way, but what it is seems that DATA got corrupted some how, everytime.
There were also installed TWRP mentioned above.
Now I am with OrangeFox and I will try tomorrow to Root it and see is there any connection between Magisk and recovery software (OrangeFox or TWRP).
Reg
Click to expand...
Click to collapse
So,
Resolved issue of bootloops:
after you install SU like Magisk, and wan to freeze apps by Titanium Backup or Neo-Backup, Apps which causes bootloops are ROM's Phone and Massages (In my case, for 16.1, 18.1, 19.1), I freeze Audio.apk who need to be shutdown for Viper4Android app who takes audio management and freezing is OK.
But Phone and Massages which are frozen cause bootloops, so you need to return from freeze state somehow in TWRP or OrangeFox with file management or revert backup. Revert backup is easier .
Camera; found issue when suddenly is out of work and cannot be connected to app. Also have problems with video cast Skype, Viber, Whatsapp, Telegram video is frozen. Hardly switch in Camera app from Camera mode to Video mode and vice-versa.
Clock & Info; missing dock icons and info, can't "capture" moment for reason when they disappear but after a while all is returned again.
P2oggle, left switch button work okey in form of 0.4 version.
Reg,
thanks on the development for this 19.1 ROM.

Zdeslav said:
Camera; found issue when suddenly is out of work and cannot be connected to app. Also have problems with video cast Skype, Viber, Whatsapp, Telegram video is frozen. Hardly switch in Camera app from Camera mode to Video mode and vice-versa.
Clock & Info; missing dock icons and info, can't "capture" moment for reason when they disappear but after a while all is returned again.
P2oggle, left switch button work okey in form of 0.4 version.
Reg,
thanks on the development for this 19.1 ROM.
Click to expand...
Click to collapse
Hello,
I've been using this ROM as my daily driver and couldn't confirm this camera bug, could you please give a few extra details? I tested on Telegram app. Which version are you using? The Play Store's one or the one from Telegram's official website? Did you give the app "While using app" permission or "Ask every time" permission for camera? Are you sure the QS Tile "Camera access" is activated (available) when the mentioned bug occurs?
Regarding the Clock widget, yes, there's a small glitch and I'm not sure on how to fix it, if it doesn't load at all, a system reboot should fix it.
P2oggle v1.2 is 100% working as far as I can tell, so you guys can try it too if you want.
MKbis said:
-Scaler for brightness level is weird, very different from the original Lenovo roms. Anyway, not really important, but something that I noticed.
-Missing haptic feedback when using the fingerprint reader as a gesture button. Again, not critical, but I am really accustomed to it and thus I noticed immediately.
-Missing haptic feedback intensity regulation, or could not find it. It's there for general call/notification vibration, but if I remember correctly lineage could also change haptic.
Click to expand...
Click to collapse
I'm not sure if it's possible to "fix" the brightness slider.
If with "haptic feedback" you mean the phone vibration, you can just adjust it to your liking in Settings > Lenovo parts > Vibration strength, it should affect fp reader too, dunno if it affects call vibration but IFAIK it should.
Regards

Leo_97
I've been using this ROM as my daily driver and couldn't confirm this camera bug, could you please give a few extra details? I tested on Telegram app. Which version are you using? The Play Store's one or the one from Telegram's official website? Did you give the app "While using app" permission or "Ask every time" permission for camera? Are you sure the QS Tile "Camera access" is activated (available) when the mentioned bug occurs?
Click to expand...
Click to collapse
Yes on latest Telegram app from web site, tried with Google Meet, Whatsapp, Viber.., always breaking connection with API/drivers. Yes I gave all permissions to Camera. If I am not giving permissions for camera, I have always noticed to confirm what I am giving, so I am excluded from this solution. And clean storage and cashe from app regular but not prevail.
But, in a while after installed a new ROM without giving SU/Root I noticed this behavior, right after I wrote earlier post up. My bad .
Choppy startup of camera, can't easily transfer from video 2 camera and vice-versa, so I tell to my self to test intensively.
Regarding the Clock widget, yes, there's a small glitch and I'm not sure on how to fix it, if it doesn't load at all, a system reboot should fix it.
Click to expand...
Click to collapse
Yes after a while it is returned back without reboot. weird.
P2oggle v1.2 is 100% working as far as I can tell, so you guys can try it too if you want.
Click to expand...
Click to collapse
Didn't know about P2oggle v1.2 app, thx

March 29th 2023 Release
Changelog:
- Fetch latest Device Tree sources
- Update LOS components webview & zlib
- Sync latest LOS source
- Merge March security patch
- Many more changes
Full change log available on the bottom of this post
Download URLs: GDrive | SF
Note: Please, before flashing, carefully read the instructions from the 3rd post above to avoid breaking your system.
Enjoy!

Big Thank you for this release. Will try it. - test

Great job, dude.
Previous versions had some buggy charging driver that left a wakelock running after each charging, and u had to restart phone each time or leave it to slowly drain battery by not going to sleep.
Somehow this problems seems to be gone in your build and that is awesome.
I've been using the build for about 2 weeks now and so far everything seems to be working fine.

April 09th 2023 Release
Change log:
- Fetch latest Device Tree sources (lots of changes)
- Update LOS components:
-- lineage: Track the FMRadio App and dependencies
- Sync latest LOS source
- Many more changes
Full change log available on the bottom of this post
Download URLs: GDrive | SF
Note: Dirty flash is unsupported for this build, please make a clean flash
Enjoy!

[ROM][13][UNOFFICIAL] LineageOS 20 for Lenovo P2

Installation Instructions
Remember, making a backup of your data before proceeding is recommended
If you are coming from Stock ROM, please refer first to the instructions below:
Install LineageOS on kuntao
If you are coming from any version of LOS18.1 or LOS19.1 or from any ROM that isn't android 13 based, you must perform a clean flash:
0- Make a backup (optional, but recommended)
1- Reboot to recovery
2- Format data (will delete all your data!)
3- Reboot to recovery again
4- Wipe > Advanced Wipe:
- Dalvik
- System
- Vendor
- Data
- Cache
- Internal Storage (optional, but recommended)
5- Flash ROM ZIP, Gapps, Gapps add-ons, Magisk add-on, etc
6- Reboot to system
7- Wait until it boots for the first time (may take some minutes)
8- If Magisk is missing after finishing the setup wizard, please reboot to system
Update Instructions
For updating from one of my builds to another (aka dirty flashing), please do the following:
1- Download ROM ZIP and copy it to the phone
2- Reboot to recovery
3- Flash ROM ZIP
4- Clean cache
5- Reboot to system

Known Issues
- Storage encryption is broken ( FDE was deprecated in a13 )
- Network traffic monitoring ( 4.9 kernel required for this )
- GPU monitoring ( 4.9 kernel required for this )
ROM Doesn't Boot After Flashing
Make sure you formatted /data partition (see installation instructions step 2)
SafetyNet Status Fix Instructions
1- Make sure Magisk was properly installed
2- Open the Magisk App
3- Open App settings (wheel on the top right side of the screen)
4- Enable "Zygisk"
5- Enable "DenyList"
6- Open "Configure DenyList"
6.1- On "Google Play services": Enable "com.google.android.gms" & "com.google.android.gms.unstable"
6.2- On "Google Play Store": Enable "com.android.vending"
7- Click on the back arrow (on top left)
8- Reboot your system
9- Test again (now it should pass)
ROM Change logs
Code:
03/05/2023
- Initial release
03/30/2023
- Fetch latest Device Tree
-- Sepolicy:
--- Address sensor hal denials
--- Address launcher3 denials
--- Allow some apps to access debuggable prop
-- rootdir:
--- Create STSensorHAL folder on data
--- Restore iio sensor device6 on boot
--- Add cpuset for the camera daemon
-- overlays:
--- Disable IMS features for Turkiye networks
--- Enable voWIFI support
-- prop:
--- Disable Bluetooth APCF Extended features
--- Enable ro.hwui.render_ahead and set it to 20 frames
-- Enable selinux ignore never allow flag
-- Don't force enable ims features
-- Remove aptX(HD) encoder shared libs
-- vendorsetup.sh: Add Trebuchet patch
- Update LOS components
-- Manifest:
--- Sync x86_64 webview prebuilts again
--- March 2023 Quarterly Platform Release and Security update
--- gs101 March 2023 Quarterly Platform Release and Security update
-- Update zlib source
- Sync latest LOS sources
- Update platform to android-13.0.0_r35
- Merge March security patch
04/20/2023
- Fetch latest Device Tree:
-- Set default livedisplay mode to 0
-- vendorsetup.sh: Add DeskClock patch
-- trebuchet:
--- Make overview scrim transparent again
--- Kill haptics in recents
-- nfc: Fix Mifare Classic reading
-- sepolicy:
--- Silence suspend_control_service neverallow denial
--- Silence tracingproxy_service neverallow denial
--- Silence fsck_untrusted neverallow denial
--- Allow system_app to access storaged via IPC
-- overlay: Allow gms to access persistent data partition
-- props:
--- Silence ResourcesCompat spam
--- Remove hwui skia atrace properties
--- Disable virtual displays writeback
-- Revert "sepolicy: Allow some apps to access debuggable prop"
- Sync latest LOS sources:
-- lineage: Track the FMRadio App and dependencies
-- Move Trebuchet to default.xml
-- overlay:
--- Disable immersive mode confirmation
--- Move default status bar height to no-rro
-- soong: Bring bootloader_message_offset back
-- envsetup: aospremote: Take .gitupstream into account
- Update platform to android-13.0.0_r41
- Merge April security patch

ROM Screenshots
Attached below.

Great work! Will test it when I have time, been waiting for this..

Hi all. I read these P2 forums for long time, but never participated. I love our P2 phone, riding a P2 since the release date and never changed. Now I got a message from my bank that the android version is too outdated to use their banking app, and they want me to switch to a newer OS. I could have ditched the P2, but couldn't. Therefore....easiest solution was to buy a second one xD I will test on the backup unit some of the roms available here, probably starting from the roms of @leo_97 . I need a stable daily driver, thus when I find something that works for me I will freeze it there for some time. But, in the meantime, I can help out with testing, starting from mid April onwards thus, feel free to contact me, and I will be a bit more active (and not passive) here in XDA for the coming months.
Cheers to all, and thanks @leo_97 , @Astridxx, @XiaoAk (and @mikeioannina for all the past efforts on P2!).

Hi
I just tested it on a P2 for a few hours and it works great! Thanks!
Is there any way to get full device encryption to work?
If I understand correctly, someone can access the phone's files even if you have a pin or password as it is now.

MKbis said:
But, in the meantime, I can help out with testing, starting from mid April onwards thus, feel free to contact me, and I will be a bit more active (and not passive) here in XDA for the coming months.
Click to expand...
Click to collapse
I'll PM you right away.
Draywen said:
Hi
I just tested it on a P2 for a few hours and it works great! Thanks!
Is there any way to get full device encryption to work?
If I understand correctly, someone can access the phone's files even if you have a pin or password as it is now.
Click to expand...
Click to collapse
You are welcome
So, IFAIK we don't have a way to make FDE work on A13 ROMs, A13 moved to FBE (File Based Encryption) which is not supported by 3.18.x kernel and we don't have rn a patch available that could enable it on our kernel version.
Regarding data access, I believe so. Without storage encryption, booting into recovery will already give access to the files. IIRC to this date encryption is fully working only on A11-based ROMs and maybe on some A12 ones.

Okay, so I'm stuck in a boot loop. I flashed the ROM from the link above but the phone won't start up. I just get the Lineage booting screen with the circle moving right to left. I've left it for 15 minutes just in case the first boot was slow but nothing else happens. I've tried to restore my original backup which was Lineage 17.1. It seemed to work, no errors from TWRP but now i just get the Lenovo screen and then it boots to fastboot mode. I flashed Lineage 20 for a second time but the same happened. I tried a different backup from August last year, again it just boots to fastboot.
Any ideas?
Cheers, Si.
EDIT: I've just noticed that I missed out step 3, reboot to recovery between Data wipe and flash ROM.
Now it boots no problem.
Cheers, Simon.
EDIT AGAIN: I still can't revert to either of my previous backups of Lineage 17.1. I would really like to be able to do this. Can anyone suggest why it will only boot to fastboot mode after a seemingly successful restore?
Thank you,
Simon.

@simes303
Don't know what the problem is, but I'd flash stock via fastboot. Then reinstall TWRP and restore LOS.
When things go wrong it's better to start from scratch rather than tinkering around and doing temporary fixes.

how is the battry life anyone?

eried1 said:
@simes303
Don't know what the problem is, but I'd flash stock via fastboot. Then reinstall TWRP and restore LOS.
When things go wrong it's better to start from scratch rather than tinkering around and doing temporary fixes.
Click to expand...
Click to collapse
Hi,
How is this different from flashing stock with TWRP?
Cheers, Si.

Used briefly but battery life seems worse, its like draining. Using 12L Lineage os and its way better.

mahmutpekkara said:
Used briefly but battery life seems worse, its like draining. Using 12L Lineage os and its way better.
Click to expand...
Click to collapse
how long does it last

laggy_boy said:
how long does it last
Click to expand...
Click to collapse
Didn't test much but its way waay noticable, you wouldn't want to use when you see the difference (didn't differ with or without gapps)
btw thx to all devs, using lineage os a12.1 and its good on battery

Battery life for me is considerably better than the Lineage 17.1 that I was using before, no question. I'd estimate almost twice the duration. I'm very happy with this ROM, thanks to all involved in developing it.
Simon.

I've actually just bought a brand new 64 Gb Lenovo P2 pretty cheap from eBay and I will definitely be flashing this Rom onto it.
Thanks again,
Simon.

Hi,
Does this ROM have USB OTG support? I can't get the phone to connect to either my external SSD drive or my bicycle helmet camera since I flashed this ROM. Both these things connected via OTG cable to my phone when I was running Lineage 17.1 and they also connect to the new P2 that I bought recently that still has stock OS. I've tried three OTG checker apps which all state that my phone is OTG compatible.
Thanks, Simon.

March 30th 2023 Release
Changelog:
- Fetch latest Device Tree sources
- Update LOS components webview & zlib
- Sync latest LOS source
- Merge March security patch
- Many more changes
Full change log available on the bottom of this post
Download URLs: GDrive | SF
Enjoy!

simes303 said:
Hi,
Does this ROM have USB OTG support? I can't get the phone to connect to either my external SSD drive or my bicycle helmet camera since I flashed this ROM. Both these things connected via OTG cable to my phone when I was running Lineage 17.1 and they also connect to the new P2 that I bought recently that still has stock OS. I've tried three OTG checker apps which all state that my phone is OTG compatible.
Thanks, Simon.
Click to expand...
Click to collapse
Hello Simon,
Yes, it does have OTG support. IFAIK it should work correctly with both FAT32 and NTFS partition types on external storage devices.

Database Users

welcome