[UNOFFICIAL] LineageOS 18.1 for Xiaomi Mi Note 10 Lite (toco) - Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries,

[UNOFFICIAL] LineageOS 18.1 for Xiaomi Mi Note 10 Lite (toco) - Xiaomi Mi Note 10 Lite ROMs, Kernels, Recoveries,

{
"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"
}
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
The device side sources can be found here:
android_kernel_xiaomi_sm6150
android_device_xiaomi_toco
android_device_xiaomi_sm6150-common
Installation
These Instructions are based on the LineageOS Wiki instructions.
Basic requirementsIMPORTANT: Please read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
Make sure your computer has adb and fastboot. Setup instructions can be found here.
Enable USB debugging on your device.
Unlocking the bootloaderNOTE: The steps below only need to be run once per device.
WARNING: Unlocking the bootloader will erase all data on your device! Before proceeding, ensure the data you would like to retain is backed up to your PC and/or your Google account, or equivalent. Please note that OEM backup solutions like Samsung and Motorola backup may not be accessible from LineageOS once installed.
TIP: It is highly recommended to have the latest official MIUI package installed on the device, before proceeding with unlock.
NOTE: The following instructions require a machine running Windows 7 or newer.
Create a Mi account on Xiaomi’s website.
TIP: A Mi account is required to unlock the bootloader. Beware that one account is only allowed to unlock one unique device every 30 days.
Add a phone number to your Mi account.
Insert a SIM into your phone.
Enable developer options in Settings > About Phone by repeatedly tapping MIUI Version.
Link the device to your Mi account in Settings > Additional settings > Developer options > Mi Unlock status.
Download the Mi Unlock app (Windows is required to run the app).
Run the Mi Unlock app and follow the instructions provided by the app.
NOTE: The app may tell you that you have to wait up to 30 days. If it does so, please wait the quoted amount of time before continuing to the next step.
After device and Mi account are successfully verified, the bootloader should be unlocked.
Since the device resets completely, you will need to re-enable USB debugging to continue.
Installing a custom recovery using fastboot
Download a custom recovery - you can download the recommended lineage recovery here.
Connect your device to your PC via USB.
On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
With the device powered off, hold Volume Down + Power. Keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
TIP: If you see no permissions fastboot while on Linux or macOS, try running fastboot as root.
Flash recovery onto your device:
fastboot flash recovery <recovery_filename>.img
TIP: The file may not be named identically to what stands in this command, so adjust accordingly.
TIP: Some devices have buggy USB support while in bootloader mode, if you see fastboot hanging with no output when using commands such as fastboot getvar .. , fastboot boot ..., fastboot flash ... you may want to try a different USB port (preferably a USB Type-A 2.0 one) or a USB hub.
Now reboot into recovery to verify the installation:
With the device powered off, hold Volume Up + Power. Keep holding both buttons until the “MI” logo appears on the screen, then release.
Installing LineageOS from recovery
Download the UNOFFICIAL LineageOS installation package for Xiaomi Mi Note 10 Lite (toco) that you would like to install or build the package yourself.
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Up + Power. Keep holding both buttons until the “MI” logo appears on the screen, then release.
Now tap Wipe.
Now tap Format Data and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage.
Return to the previous menu and tap Advanced Wipe, then select the Cache partition and then Swipe to Wipe.
Sideload the LineageOS .zip package:
On the device, select “Advanced”, “ADB Sideload”, then swipe to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
check
TIP: If the process succeeds the output will stop at 47% and report adb: failed to read command: Success.
(Optionally): If you want to install any add-ons, repeat the sideload steps above for those packages in sequence.
Once you have installed everything successfully, run ‘adb reboot’.
WARNING: Depending on which recovery you use, you may be prompted to install additional apps and services. We strongly advise you to opt out of installing these, as they may cause your device to bootloop, as well as attempt to access or corrupt your data.
Downloads
Download UNOFFICIAL LineageOS 18.1 for Xiaomi Mi Note 10 Lite.
Download UNOFFICIAL LineageOS recovery for Xiaomi Mi Note 10 Lite.
Donate to support development:
Donate via PayPal to NeoArian
Donate via PayPal to LineageOS

Note that these builds include Google Apps. A vanilla version will be available later.
This project does not rely on MIUI vendor, the vendor image is being built with the ROM and huge parts of it are being built from source.
Changelog
Here you can find all changelog's.
2021-05-20
Code:
* Fixed Dynamic system updates -> You can now launch the Android 12 DSU from developer settings (Note that it does not have much of the new design yet. If you look for that go for other GSIs).
* Update vendor security patch level to 2021-05-01
* Removed unused notification light settings
2021-05-18
Code:
* Reverted default Pixel Blue accent colour back to lineage teal (pixel blue can be selected from styles and themes now)
* Fixed Microphone during calls
2021-05-14
Code:
* Fixed brightness during FOD
* Updated to may Android Security Bulletin

Great work! Thank you, Arian!

simplytb said:
Great work! Thank you, Arian!
Click to expand...
Click to collapse
I have uploaded a new build.
Download: https://sourceforge.net/projects/ep...ge-18.1-20210514-UNOFFICIAL-toco.zip/download
Changelog:
* Fixed brightness during FOD
* Updated to may Android Security Bulletin

Thanks for your work sir

Good job.

thanks!

Hi NeoArian problem with microphone

@NeoArian Hi! I tried the rom, and everything is great! thanks! But the rom has problems with the microphone seems to not be working properly. It doesn't work on the Phone dialer, but it works on video camera and other apps but with bad audio quality and low volume on the microphone. I decided not to go back to MIUI, cause this is way way better, so I'll just wait when the fix comes up. Cheers!

Good evening!
Thanks for the reports about the microphone issue. I have fixed it and uploaded a new build: https://sourceforge.net/projects/ep...ge-18.1-20210518-UNOFFICIAL-toco.zip/download
Changelog:
• Reverted default Pixel Blue accent colour back to lineage teal (pixel blue can be selected from styles and themes now)
• Fixed Microphone during calls
Greetings, Arian.

Would it be possible to provide a list of the included Gapps?

Jisaka said:
Would it be possible to provide a list of the included Gapps?
Click to expand...
Click to collapse
Sure. My repository with the GApps can be found here.
The exact list of google apps can be found here. All the files from this list are extracted from the latest Google Pixel 5 factory image (which can be found here: https://developers.google.com/android/images).

NeoArian said:
Good evening!
Thanks for the reports about the microphone issue. I have fixed it and uploaded a new build: https://sourceforge.net/projects/ep...ge-18.1-20210518-UNOFFICIAL-toco.zip/download
Changelog:
• Reverted default Pixel Blue accent colour back to lineage teal (pixel blue can be selected from styles and themes now)
• Fixed Microphone during calls
Greetings, Arian.
Click to expand...
Click to collapse
Thanks for the update @NeoArian! Everything works fine already. Thanks alot!

please users of this rom I have a question. does the fast charge function work? Thank you

MKey_CZ said:
please users of this rom I have a question. does the fast charge function work? Thank you
Click to expand...
Click to collapse
Good Morning,
Fast Charging does not work correctly. It's limited to 15-20W instead of the possible 30W. The bad thing about it is that xiaomi has been doing something in system which i'm not aware of currently. Fastcharging does not work at all with MIUI vendor + MIUI kernel with an AOSP system image, i have at least got to the same state with OSS kernel and built vendor image but i didn't figure out what unlocks the real fastcharging.
Greetings, Arian.

Good Evening.
I have uploaded a new build. https://sourceforge.net/projects/ep...ge-18.1-20210520-UNOFFICIAL-toco.zip/download
Changelog
* Fixed Dynamic system updates -> You can now launch the Android 12 DSU from developer settings (Note that it does not have much of the new design yet. If you look for that go for other GSIs).
* Update vendor security patch level to 2021-05-01
* Removed unused notification light settings
Greetings, Arian.

Thanx a lot for the effort but i have a qst do i have to reflash the phone for Every update toi make ? Or there IS another way to update thanx again

Aymenbekkari6s said:
Thanx a lot for the effort but i have a qst do i have to reflash the phone for Every update toi make ? Or there IS another way to update thanx again
Click to expand...
Click to collapse
You can flash the new updates without any wipes. Just go into recovery and flash the new zip. If you use lineage recovery connect your phone to your computer and use adb sideload.
I will setup automated weekly build with OTA functionality later.

NeoArian said:
You can flash the new updates without any wipes. Just go into recovery and flash the new zip. If you use lineage recovery connect your phone to your computer and use adb sideload.
I will setup automated weekly build with OTA functionality later.
Click to expand...
Click to collapse
Thanx bro ^^ do you suggest that i use TWRP or lineage recouvert ?

Aymenbekkari6s said:
Thanx bro ^^ do you suggest that i use TWRP or lineage recouvert ?
Click to expand...
Click to collapse
I would recommend lineage recovery if you are able to use ADB sideload to update. TWRP would probably also work fine but I did not confirm that.

Related

[7.1.2][UNOFFICIAL] LineageOS 14.1 for Lenovo P2

#rezerved for me

How to install Root for Apps on Android Nougat Custom Rom
Download and transfer the Lineage SU addon zip file from the download link above to your device’s storage.
Boot your device into TWRP recovery.
Tap on Install and select the Lineage SU addon zip file that you transferred to your device in Step 1.
After selecting the .zip file, do Swipe to Confirm Flash on the bottom of screen to begin the flashing process.
Once Lineage SU addon is flashed, you’ll get Reboot System option, select it.
How to Enable Root for Apps on Lineage OS
Once you’ve installed the Lineage SU addon zip, do the following to enable root for Apps on Lineage OS:
Enable Developer options: Go to Settings » About phone » Tap seven times on Build number.
Go back to Settings main menu and open Developer options from there.
Look for Root access setting, and set it to Apps and ADB or Apps only, as per your need.
That’s all. Your Android device running on Lineage OS should have full root access for apps now.
If you ever need to disable root access, just go to Settings » Developer options » Root access and select the Disabled option from there.
Download;
addonsu-arm64-signed.zip

Great job, no idea how you build new kernel 3.18.31 for lineage14.1

Thank You!

i want to Root LOS 14.1
is it the same way?? or should i do anything more??? !!
i am thinking of SystemRoot..
please give your suggestions ..

nandakis4 said:
i want to Root LOS 14.1
is it the same way?? or should i do anything more??? !!
i am thinking of SystemRoot..
please give your suggestions ..
Click to expand...
Click to collapse
LineageOs AdeenSu
Download And Flashing
Developer Setting>Root

@wzedlare kindly you fix framework folder, it look so ugly with boot oats and boot arts, i have file folder framework to manage throw thems, but make home button not wake up the screen light when it pressed, i hope it will be fix for next release

Thanks! Very good job. It may be crazy but I think I stay with Android 6, because I love the led notifications.
But maybe I will flash it, because who give a F?
Do you need to format as ext4 or other filesystem?...
Will my SD work, it's exfat??
---------- Post added at 13:27 ---------- Previous post was at 13:16 ----------
hendibudi said:
@wzedlare kindly you fix framework folder, it look so ugly with boot oats and boot arts, i have file folder framework to manage throw thems, but make home button not wake up the screen light when it pressed, i hope it will be fix for next release
Click to expand...
Click to collapse
Why not fix it yourself?

hendibudi said:
@wzedlare kindly you fix framework folder, it look so ugly with boot oats and boot arts, i have file folder framework to manage throw thems, but make home button not wake up the screen light when it pressed, i hope it will be fix for next release
Click to expand...
Click to collapse
They(boot.oat) are being generated automatically if you compile any custom rom.Home button wakes up the device, I won't disable that feature.It is useful for everyone.
ilmervanhattem said:
Thanks! Very good job. It may be crazy but I think I stay with Android 6, because I love the led notifications.
But maybe I will flash it, because who give a F?
Do you need to format as ext4 or other filesystem?...
Will my SD work, it's exfat??
---------- Post added at 13:27 ---------- Previous post was at 13:16 ----------
Why not fix it yourself?
Click to expand...
Click to collapse
You don't have to format anything.Just make your wipes and flash it.

ilmervanhattem said:
Thanks! Very good job. It may be crazy but I think I stay with Android 6, because I love the led notifications.
But maybe I will flash it, because who give a F?
Do you need to format as ext4 or other filesystem?...
Will my SD work, it's exfat??
---------- Post added at 13:27 ---------- Previous post was at 13:16 ----------
Why not fix it yourself?
Click to expand...
Click to collapse
I am sorry, i just junior member on xda, i didn't mean that, i just want to give little contribution to revive our community user p2 experience

WiFi is not working here...
When I turn on WiFi it turns off instantly...
Fawk
I've used the 'super' version of gapps for 7.1 (64bits) btw. Also tried it with TWRP 3.0.2.0 and the aroma installer of gapps, same WiFi error.

Hi there, i am thinking of buying this device for my gf because she needs something with a ****load of battery power. So this device seems the obvious choice. But i have a question:
i noticd that on every rom there is no led and no fingerprint. Is this something that will be added in the future or is it not possible due to unavailabe firmwares?
Kind regards

DDQW said:
Hi there, i am thinking of buying this device for my gf because she needs something with a ****load of battery power. So this device seems the obvious choice. But i have a question:
i noticd that on every rom there is no led and no fingerprint. Is this something that will be added in the future or is it not possible due to unavailabe firmwares?
Kind regards
Click to expand...
Click to collapse
I couldn't fix them, that's my fault.It is not caused by firmware or something.I don't know what will happen in the future.
ilmervanhattem said:
WiFi is not working here...
When I turn on WiFi it turns off instantly...
Fawk
I've used the 'super' version of gapps for 7.1 (64bits) btw.
Click to expand...
Click to collapse
Flash stock rom and use it for ten minutes, wipe data,system,cache,dalvik cache (don't wipe your internal storage, wiping it causes bugs.), then flash the rom.

wzedlare said:
Flash stock rom and use it for ten minutes, wipe data,system,cache,dalvik cache (don't wipe your internal storage, wiping it causes bugs.), then flash the rom.
Click to expand...
Click to collapse
OK my friend.
Got some error and passcode error when restoring. Will try some things and talk to you later.
UPDATE: wifi is working but have to root.
UPDATE: Rooted with version 2.79
UPDATE: Now restoring 484 apps with Titanium Backup
UPDATE: ROM is working smooth af, for how much I experienced by now

i was wondering why i couldnt get gapps to install , then realised i was trying to install the wrong version lol

The Mero said:
i was wondering why i couldnt get gapps to install , then realised i was trying to install the wrong version lol
Click to expand...
Click to collapse
7.1 > arm64 > choose whatever you want, pico is the smaller zip.

cpu-z is saying governor is stuck on performance .. constantly running at 2016mhz on all cores .
Is it possible to change it to dynamic ?

The Mero said:
cpu-z is saying governor is stuck on performance .. constantly running at 2016mhz on all cores .
Is it possible to change it to dynamic ?
Click to expand...
Click to collapse
Use a kernel editor?

which one would be safe / recommend to use ilmervanhattem ?
I wouldnt have a clue where to start ,

[ROM][7.1.2][OFFICIAL] LineageOS 14.1 - SM-T805

LineageOS 14.1
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Disclaimer
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.
*
*/
Installation
If you are installing custom ROM for the first time ever:
1. MAKE THE BACKUP OF ALL YOUR DATA!
2. UPDATE THE TABLET TO LATEST MARSHMALLOW ROM VIA ODIN!
Generic installation procedure:
1. MAKE THE BACKUP OF ALL YOUR DATA!
2. DOWNLOAD THE ZIP(S)
3. INSTALL A COMPATIBLE RECOVERY
4. WIPE YOUR DATA (FACTORY RESET)
5. FLASH LINEAGEOS
6. FLASH THE GOOGLE APPS PACKAGE (OPTIONAL)
7. REBOOT
NOTE: To have seamless OTA updates, it is REQUIRED to flash TWRP 3.2.3-1 or newer (build date 25.10.2018 or newer)!
One-time migration to official builds without losing your data:
1. DOWNLOAD MIGRATION SCRIPT
2. BOOT RECOVERY AND UNLOCK YOUR DATA PARTITION IF IT IS ENCRYPTED
3. FLASH THE MIGRATION SCRIPT
4. FLASH THE OFFICIAL ROM
5. WIPE DALVIK AND CACHE
6. REBOOT
NOTE: If modem and RIL stops working after migration, then it is MANDATORY TO FLASH THE LATEST MARSHMALLOW STOCK ROM VIA ODIN and perform a clean installation of LineageOS!
Going back to unofficial builds without losing your data (if necessary):
0. DOWNLOAD MIGRATION SCRIPT
1. BOOT INTO RECOVERY, UNLOCK THE DATA PARTITION IF IT ENCRYPTED AND ATTACH USB CABLE
2. PUSH THE MIGRATION SCRIPT TO THE TABLET:
Code:
adb push migration.sh /migration.sh
3. OPEN ADB SHELL ON PC AND PERFORM THE MIGRATION:
Code:
chmod +x /migration.sh
sh /migration.sh unofficial
4. FLASH THE UNOFFICIAL ROM
5. WIPE DALVIK AND CACHE
6. REBOOT
Downloads / Changelogs
ROM
su addon
Google Apps (GApps)
Changelogs (Mirror)
Changelogs (Official)
Credits
Android Open Source Project (AOSP)
LineageOS Project
Team Exynos5420
@Barracuda77777, @UpInTheAir, @crpalmer
@eousphoros, @nvertigo67, @Nexorrr
and all the supporters, testers and advisors

Bugs
Messenger app calls using BT headset have no sound
Voice call using the built-in mic have an unsuppressed echo
HDMI audio is played on internal speakers
Widevine DRM security level is L3
Bug Reporting
Other issues?
Before posting in this thread, make sure of a few things:
You used the search function of the forums.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread.
Logs! You can use this: SysLog
Source Code and Development
Kernel
Device Tree
LineageOS Code Review
LineageOS Bug Tracker
LineageOS Jenkins Server

Woo-hoo, congratulations!!! Finally T805 is official [emoji41]
Надіслано від мого SM-G965F, використовуючи Tapatalk

Those who already have installed the unofficial version - can they now simply use internal upgrade functionality to get on the official one?

Maheshwara said:
Those who already have installed the unofficial version - can they now simply use internal upgrade functionality to get on the official one?
Click to expand...
Click to collapse
https://wiki.lineageos.org/signing_builds.html#test-keys-to-your-own-release-keys-or-vice-versa yes it is possible.

Migration did not work for me:
Unofficial to official migration
Error: /data/system/packages.xml not found
Click to expand...
Click to collapse
Nonetheless, tried to flash the official zip what failed with ERROR 7. What to do now?

The instruction moved to post #1

Do we need to root the t805?
Thanks

J4G3D said:
Do we need to root the t805?
Thanks
Click to expand...
Click to collapse
Do you mean rooting the stock firmware before flashing TWRP? No, not needed as zip will overwrite BOOT (kernel + ramdisk) and SYSTEM and CACHE and DATA will be wiped on factory reset.
If you meant not this but "should we flash addonsu after LineageOS", I'd say it is up to you, but I prefer having root access for DriveDroid and other root-only apps. If you need to pass SafetyNet, you can always turn it off in Developer settings.

gellmar said:
If you need to pass SafetyNet, you can always turn it off in Developer settings.
Click to expand...
Click to collapse
Or install Magisk ???

Maheshwara said:
Or install Magisk ???
Click to expand...
Click to collapse
Or install Magisk. But I made all official and unofficial builds to pass SafetyNet if root is turned off. Presuming you need root for special tasks, you can turn it on, do your work and turn it back off and SafetyNet will not suffer.

gellmar said:
Do you mean rooting the stock firmware before flashing TWRP? No, not needed as zip will overwrite BOOT (kernel + ramdisk) and SYSTEM and CACHE and DATA will be wiped on factory reset.
If you meant not this but "should we flash addonsu after LineageOS", I'd say it is up to you, but I prefer having root access for DriveDroid and other root-only apps. If you need to pass SafetyNet, you can always turn it off in Developer settings.
Click to expand...
Click to collapse
Thanks, I managed to flash it perfectly. Well the first time i had a error in TWRP. But I then tried again, this time erasing all internal data and it flashed fine.
Where I am stuck now is gApps. I get error 20 and ive tried various "fixes" in terms of install procedures found on xda.
What check boxes should we pick in the gapps site you've linked us to?
Any tips/advice?

J4G3D said:
Thanks, I managed to flash it perfectly. Well the first time i had a error in TWRP. But I then tried again, this time erasing all internal data and it flashed fine.
Where I am stuck now is gApps. I get error 20 and ive tried various "fixes" in terms of install procedures found on xda.
Any tips/advice?
Click to expand...
Click to collapse
Last time I checked with OpenGapps arm - 7.1 - pico it flashed fine right after LineageOS and addonsu. Try rebooting again into recovery and installing gapps I mentioned and factory reset again.

gellmar said:
Last time I checked with OpenGapps arm - 7.1 - pico it flashed fine right after LineageOS and addonsu. Try rebooting again into recovery and installing gapps I mentioned and factory reset again.
Click to expand...
Click to collapse
Arm or arm64?
edit: sorry just saw you said arm.
All installed now.
I was about to sell this tablet, due to lack of updates. But stumbling across XDA has no doubt forced me to keep this tablet, which I think is still a top tablet.
Anyway, ll seems good so far, many thanks for the hard work!

J4G3D said:
Arm or arm64?
edit: sorry just saw you said arm.
All installed now.
I was about to sell this tablet, due to lack of updates. But stumbling across XDA has no doubt forced me to keep this tablet, which I think is still a top tablet.
Anyway, ll seems good so far, many thanks for the hard work!
Click to expand...
Click to collapse
Hey J4G3D, I've got a T805 my kids use mostly for Netflix, or I put movies on it when we go on road trips. I'm gonna try this out!! I didn't see any detailed instructions in the first post so did you selected arm, 7.1 and Stock for the google apps?
Thanks.

MannyMania said:
Hey J4G3D, I've got a T805 my kids use mostly for Netflix, or I put movies on it when we go on road trips. I'm gonna try this out!! I didn't see any detailed instructions in the first post so did you selected arm, 7.1 and Stock for the google apps?
Thanks.
Click to expand...
Click to collapse
Hi
I rooted my device, just because it seemed simple to do so. Here:
https://www.theandroidsoul.com/root...10-5-lte-sm-t805-one-click-cf-auto-root-tool/
-Then I loaded custom recovery.
-Backed up anything I needed backing up
-Put the rom file, gApps (arm, 7.1, pico) onto a sd card
1. Boot into Recovery Mode (TWRP)
2. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
3. Swipe to Wipe at Bottom of Screen,
4. Back to Main start screen,
5. Wipe > Format Data,
6. Type 'Yes' and press blue checkmark at the bottom-right corner,
7. Go Back to Main Start Screen to -VERY IMPORTANT---> Install Rom and GApps,
8. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe
9. Reboot System
Job done.
Battery life appears to be much, much more stable now too. Apps also appear to be more stable, sky news used to crash every time I used it, at least once. Now it doesn't
Only bug i can see so far are the weather app not showing as a widget on the main screen under the clock. All is set and the recommended weather widget downloaded, but the weather just don't seem to appear. Also when having a pin on the lock screen, its only unlock-able via landscape mode and not portrait mode.

J4G3D said:
Only bug i can see so far are the weather app not showing as a widget on the main screen under the clock. All is set and the recommended weather widget downloaded, but the weather just don't seem to appear. Also when having a pin on the lock screen, its only unlock-able via landscape mode and not portrait mode.
Click to expand...
Click to collapse
I have a perfectly working weather setup (including lockscreen weather) using OpenWeatherMap provider:
0. Remove all other weather providers, if downloaded
1. Install the OpenWeatherMap provider from LineageOS Extras
2. On the main screen, long-tap to have widget panel appear, then press "Widgets".
3. Add cLock widgetby long-tapping it to position on Main screen.
4. Under cLock widget settings open, select OpenWeatherMap as weather source on Weather tab and press a gear to enter website API key. When a permission dialog for GPS pops up, enable High Accuracy mode (that's esssential!)
5. Press OK everywhere to apply settings (dont use back button!)
6. Go to Settings - Security - Lock Screen and tap the gear to see Lockscreen Options. Tick the "Show weather on lockscreen" mark.
7. Let it load the weather and enjoy the notification in lockscreen.
Once you remove the cLock widget off main screen, the lockscreen weather will disappear.
Lockscreen rotation is enabled in Settings - Screen - Screen Rotation - Enable lockscreen rotation.

gellmar said:
The instruction moved to post #1
Click to expand...
Click to collapse
Got it with this instruktion. Thanks. Running the migration script via ADB while system is running did not work, but doing it via recovery was fine.

Hello! Thanks for your work! Excellent firmware! The tablet is back in service!
For information the received messages are not displayed on the application icons only in the status bar.

J4G3D said:
Hi
I rooted my device, just because it seemed simple to do so. Here:
https://www.theandroidsoul.com/root...10-5-lte-sm-t805-one-click-cf-auto-root-tool/
-Then I loaded custom recovery.
-Backed up anything I needed backing up
-Put the rom file, gApps (arm, 7.1, pico) onto a sd card
1. Boot into Recovery Mode (TWRP)
2. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
3. Swipe to Wipe at Bottom of Screen,
4. Back to Main start screen,
5. Wipe > Format Data,
6. Type 'Yes' and press blue checkmark at the bottom-right corner,
7. Go Back to Main Start Screen to -VERY IMPORTANT---> Install Rom and GApps,
8. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe
9. Reboot System
Job done.
Battery life appears to be much, much more stable now too. Apps also appear to be more stable, sky news used to crash every time I used it, at least once. Now it doesn't
Only bug i can see so far are the weather app not showing as a widget on the main screen under the clock. All is set and the recommended weather widget downloaded, but the weather just don't seem to appear. Also when having a pin on the lock screen, its only unlock-able via landscape mode and not portrait mode.
Click to expand...
Click to collapse
Hey J4G3D, I had no luck. My Tablet however is an SM-T805W. It's a Canadian LTE tablet with Rogers as the carrier. I've been doing some reading and it doesn't look to good for my device. Haven't given up yet so the quest goes on!! Thanks for the instructions though!!
Cheers.

[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

[ROM][13.0][OFFICIAL] SparkOS [AOSP][STABLE][30/05/2023]

{
"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"
}
SparkOS is an AOSP based ROM, packed with many features without sacrificing stability and performance.
In short a fully functional operating system as stable and customizable as it should be.
Code:
/* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
Device Specific Issues:
• None
Requirements
• You must be on Latest firmware v11.0.3.0 or v11.0.2.0
• You must use any of the recommended recovery (links are given below).
Downloads
Get the latest SparkOS Build for vince: Download
Firmware: https://xiaomifirmwareupdater.com/firmware/vince/
Nikgapps: https://nikgapps.com/
Mindthegapps (Use arm64 only): http://downloads.codefi.re/jdcteam/javelinanddart/gapps
Magisk: https://github.com/topjohnwu/Magisk/releases
Recommended Recoveries:
- TWRP by Starlight
- Orangefox R11.0 Beta
- Read the latest changelogs from: Here
Notes
• Build type: User
• Encryption not supported, Decrypted by default
• Selinux is Enforcing
• FMRadio Included
• Do not flash recovery.img available on the spark download website
Flashing Instructions:
Clean flash (Coming from a different ROM):
• Download ROM
• Download Custom Google Apps Package (Like Nikgapps core/basic or Mindthegapps) if the ROM is Vanilla variant (On GApps ROM variant Google Apps are included, don't flash a separate Custom Google Apps package)
• Reboot to Recovery.
• Wipe System, Data, Vendor, Cache, Dalvik/ART cache partitions
• Flash latest stable firmware v11.0.3.0 before flashing ROM
• Flash ROM zip
• Flash Custom Google Apps Package if the ROM is Vanilla variant
• Reboot to system
To get root access, Reboot to recovery after ROM setup and flash Magisk.zip
BOOTLOOP SITUATION: If you are coming from stock/custom MIUI or any ROM which had data ENCRYPTION, you will face bootloop and can not boot into the system. In such case you need to FORMAT data after flashing the ROM. Otherwise the ROM won't boot (Read detailed instructions from here)
Dirty flash (Updating to a newer build):
• Download the new update ROM zip
• Reboot to recovery
• Do not wipe anything
• Flash the new update ROM zip
• Flash the same Custom Google Apps Package again you flashed before (For vanilla users)
• Flash Magisk again if you are rooted before (For rooted users)
• Wipe Cache and Dalvik/ART cache
• Reboot to system
Important note regarding SparkOS 13.6 update
This is a huge rebase of the ROM's source code after the March update, So Clean flash is MANDATORY for all users. Some bugs from previous versions have been fixed in this version and some new features can be noticed. Some customizations have been temporarily removed (eg: Smart charging, QS row & column customisation etc) and will be added in future releases (Read official community post).
You should be aware of some known source bugs in this release before updating to 13.6. These bugs are not device specific and are present in all Spark official devices which will be fixed in the next update.
Known bugs are;
1. Launcher settings are crashing with light theme (works fine with dark theme). You can use a different Launcher but I think Pixel launcher Extended will not work anymore as spark is now completely based on lineage
2. Shortcut buttons glitches in recent panel.
3. Visual glitch on Quicksettings/Statusbar after a reboot (Restarting SystemUI fixes it for now)
Join our Telegram Group https://t.me/SparkOSChannel
Buy me a Coffee https://paypal.me/spyroskal
See our website https://spark-os.live/
Device Support Group https://t.me/anandhansprojects_chat
Source Code
SparkOS http://github.com/Spark-Rom
Device Tree and Vendor Tree https://github.com/Spark-Devices
Kernel Tree https://github.com/aospa-vince/android_kernel_xiaomi_vince
ROM OS Version: Android 13.0
Spark-OS Version: Android 13.6
Security Patch Level: May 2023
ROM Kernel: Linux 4.9.x
Stable Release Date: 30.05.2023
Latest Release Date: 30.05.2023

This is great. Seems to run well - but can't get it to play nice with Viper4Android.

droident said:
This is great. Seems to run well - but can't get it to play nice with Viper4Android.
Click to expand...
Click to collapse
No issues with viper4Android here.
Check if you've rooted properly?
Or maybe you are using a mod version of viper4Android.

Been using it for half a year and it's the best Android 13 rom I tried (not that there's many that are up to date)

anandhan07 said:
No issues with viper4Android here.
Check if you've rooted properly?
Or maybe you are using a mod version of viper4Android.
Click to expand...
Click to collapse
I used the repackaged v4a from github. Clearly something went wrong here if it's working at your end. I'll try again later when I'm home as I'll need to install from scratch having reverted to A12. Guessing maybe I just needed to reboot again or something. Here's the version I used:
GitHub - programminghoch10/ViPER4AndroidRepackaged: A refined ViPER4Android installer.
A refined ViPER4Android installer. Contribute to programminghoch10/ViPER4AndroidRepackaged development by creating an account on GitHub.
github.com
I have to say the smooth responsiveness on these new A12/A13 ROM builds is surprising given how often A11 would lock up for me. Maybe my device just finally needed a reset idk.

OK. Mystery solved. Turns out that Viper4Android does indeed work - it just needed an extra reboot.
So I flash it > reboot > v4a App appears on next boot but doesn't work > reboot again > v4a works.
Weird but makes sense. Sorry for the confusion.

I couldn't receive this kind of google login authorization on this rom "is it you trying to sign in". Device wasn't appearing in google account double verification. No problem in a13 elixir.
Also sadly no option 2g connectivity.
Rom itself seems smooth. ATM moved back to A10

I have problem, the screen show on/ off at redmi boot logo

CPU cores seam to be locked to 1400 mhz

Hello İ installed latest Spark OS gapps build on my a205f i loved the rom but it has a bug phone screen freezes cant close the screen no reaction to calls,notifications,holding down the power button the only solution is to wait for the battery drain it happened 2 times what can i do i guees this build is laggy

This is possibly a long shot but any chance of modified files for higher quality audio on Bluetooth SBC (or AAC)? It used to be you could patch it in via Magisk but the module no longer works on newer android versions and if I'm correct the edits need to be made before a ROM is built. If you're able to, any chance of some experimental files for me to try out?
I think the values are in a2dp_sbc_encoder for SBC, a2dp_aac for AAC. A2DP_XXX_DEFAULT_BITRATE 000 where XXX is SBC or AAC and 000 is the bitrate in kbit/s.

Mr.Bra said:
Hello İ installed latest Spark OS gapps build on my a205f i loved the rom but it has a bug phone screen freezes cant close the screen no reaction to calls,notifications,holding down the power button the only solution is to wait for the battery drain it happened 2 times what can i do i guees this build is laggy
Click to expand...
Click to collapse
This is sparkos for vince aka Redmi 5 plus. Not for a205f

droident said:
This is possibly a long shot but any chance of modified files for higher quality audio on Bluetooth SBC (or AAC)? It used to be you could patch it in via Magisk but the module no longer works on newer android versions and if I'm correct the edits need to be made before a ROM is built. If you're able to, any chance of some experimental files for me to try out?
I think the values are in a2dp_sbc_encoder for SBC, a2dp_aac for AAC. A2DP_XXX_DEFAULT_BITRATE 000 where XXX is SBC or AAC and 000 is the bitrate in kbit/s.
Click to expand...
Click to collapse
will see

Latest Vince just got released yesterday - thank you
https://sourceforge.net/projects/sparkosofficial/files/vince/Spark-13.3-Official-vince-20230105-gapps.zip/download

Hi,
I installed this rom, until I see it I'm liking it, but the screen rotation doesn't work.
Any idea?
Thanks...

Hello everyone, just flashed this ROM on my Vince (coming from Elixir 3.3 - A13).
Since I use this phone to debug my apps, I need to connect Chrome DevTools to it.
What I've done so far:
- wiped everything
- installed Spark-13.3-Official-vince-20230105-gapps
- installed Magisk 25.2
- registered my Google account
- updated all apps (through Play Store)
- enabled Developer options, then USB debugging
Now, when I launch Chrome DevTools on PC, I can see the phone but the webpages list is empty; it also doesn't show any WebView instance (see the screenshot below).
Remote debug was working with Elixir 3.3 on the same phone and PC, so I suppose the difference is in some ROM setting... something to be changed here, but I'm out of ideas...
Does anyone have any suggestions about this?

maxi_power said:
Hi,
I installed this rom, until I see it I'm liking it, but the screen rotation doesn't work.
Any idea?
Thanks...
Click to expand...
Click to collapse
First, make sure you have enabled auto rotate screen option. It is disabled by default.
If it's enabled send a screenshot from sensor test app (available in playstore). ROM doesn't have issues auto rotates screen.

nicorac said:
Hello everyone, just flashed this ROM on my Vince (coming from Elixir 3.3 - A13).
Since I use this phone to debug my apps, I need to connect Chrome DevTools to it.
What I've done so far:
- wiped everything
- installed Spark-13.3-Official-vince-20230105-gapps
- installed Magisk 25.2
- registered my Google account
- updated all apps (through Play Store)
- enabled Developer options, then USB debugging
Now, when I launch Chrome DevTools on PC, I can see the phone but the webpages list is empty; it also doesn't show any WebView instance (see the screenshot below).
View attachment 5804415
Remote debug was working with Elixir 3.3 on the same phone and PC, so I suppose the difference is in some ROM setting... something to be changed here, but I'm out of ideas...
Does anyone have any suggestions about this?
Click to expand...
Click to collapse
Can you send logcat?
I am not using this feature. I will test this later.

anandhan07 said:
First, make sure you have enabled auto rotate screen option. It is disabled by default.
If it's enabled send a screenshot from sensor test app (available in playstore). ROM doesn't have issues auto rotates screen.
Click to expand...
Click to collapse
Hi, thanks for the answer.

maxi_power said:
Hi, thanks for the answer.
Click to expand...
Click to collapse
Seems like you messed up persist
So flash persist.img via recovery (in persist partition) and reboot into system. Do not wipe anything.
Link of pesrist.img: https://t.me/anandhansprojects_chat/15693

[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