{
"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
Related
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.2 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
{
"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"
}
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.
*
*/
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.
This thread is for Official LineageOS 14.1 builds for chagallwifi (SM-T800) The following will not be supported here:
Custom kernels
Mods
Xposed
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Have not attempted a clean flash
First time flashing LineageOS 14.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Install the Google Apps addon package (Optional)
Reboot
Make sure you have the Marshmallow bootloader. Guide is in the comments below.
There will be a new build every week, every Monday.
The builds will no longer be personally tested by me before being uploaded (but everything will probably be fine)
Change logs will no longer be posted within every new build, but instead when the changes are uploaded to GitHub. I will try though to post changes for major bugs or fixes as they are released.
Some builds might feature only minor changes, ie. only updating the LineageOS source
Chagallwifi Download
Google Apps:
Beans GAPPS 7.1.2
Kernel
https://github.com/LineageOS/android_kernel_samsung_exynos5420
Device Tree
https://github.com/LineageOS/android_device_samsung_chagallwifi
Aytex, who made all of the banners on this post.
@Barracuda77777 (For helping along the way)
@UpInTheAir for his kernel magic and misc fixes
@crpalmer (for picassowifi device and kernel gits - the base @Barracuda77777 and @nvertigo67 started of from)
@eousphoros (for his device git)
@nvertigo67 (for his work on chagallwifi)
@Nexorrr (for his work on chagalllte)
Fingerprint is disabled
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: https://play.google.com/store/apps/details?id=com.tortel.syslog
For OTA updates to flash correctly:
Update your TWRP to 3.1.0-1 (USE THE 2017-05-04 BUILD OR LATER. DO NOT USE A BUILD FROM BEFORE THIS DATE)
You can get Official TWRP 3.1.0-1 for chagallwifi from this link!
TWRP for CHAGALLWIFI
This updated TWRP recovery image contains a fix that will allow it to flash OTA updates properly!
How to update to Marshmallow bootloader (required for 20170324 and later builds)
Updating the bootloader is very quick and doesn't wipe data or repartition the device.
If the last Samsung ROM you had was 6.0.1 Touchwiz, you already have Marshmallow bootloader and don't need to follow these steps. (If you were on MM, and it still won't boot, follow the steps below)
1. Download the bootloader-only Odin package: T800XXU1CPK2.tar.md5
This has the latest Marshmallow bootloader (December 2016)
https://www.androidfilehost.com/?fid=457095661767146298
2. Download Odin 3.11
You can skip this if you already have a working Odin
https://www.androidfilehost.com/?fid=673368273298937183
3. Shutdown your tablet and start it up by holding Power+Home+Volume Down to enter Download Mode. Volume Down is the one right next to the power button. Really shut it down and use this key combination, if you use Advanced Restart, or go into download mode via TWRP the bootloader won't change.
4. Make sure the screen of your tablet has a green android symbol with a "Downloading..." text
5. Open Odin3_v3.11.1.exe and follow the instructions in this image:
If anything is missing, you WON'T flash bootloader successfully.
6. Click Start. Your tablet will automatically reboot back into your ROM.
7. To verify you have the new bootloader, you can run in terminal emulator "getprop ro.bootloader". It should say T800XXU1CPK2.
Thanks @ZakooZ for the post!
Deathly Adiutor App
Deathly Adiutor is an open-source, modified version of Kernel Adiutor made specifically for Exynos 5420 devices.
Features
Power Saving:
S-Pen Power Saving - Same as in Touchwiz, disables S-Pen detection if it's inserted in the slot
S-Pen Input Booster - Instantly increase CPU frequency when the S-Pen touches the screen
Touchscreen Input Booster - Instantly increase CPU frequency when you touch the screen
Touchkey Input Booster - Instantly increase CPU frequency when you touch the capacitive buttons
Touchscreen Glove Mode (Not all screens support this)
CPU Control:
CPU Settings reworked - Deathly adiutor back-end was cleaned up to work specifically with our CPU
CPU Thermal - Control all thermal throttling points for the CPU (make your device run colder... or even hotter)
GPU Control:
GPU Time in States - Same as CPU Time in States (Times in each frequency)
GPU Frequency Control (not yet supported on Nougat)
GPU Voltage Control (not yet supported on Nougat)
GPU Governor Control (not yet supported on Nougat)
Battery control:
Full power statistics - See current and maximum charging currents and current source of power
Unstable power source detection - Lowers current until the power source is stable
Customize charger current limits - Make your device charge faster (safe, if the charger can not supply enough current, the board will dynamically decrease the current)
Screen-On current limiter - Limit charging if screen is on (to avoid overheating)
Speakers:
Privacy mode - Disable main speaker if headphones are plugged in
Earpiece volume
Left/Right speaker volume
Speaker equalizer
Headphones:
Left/Right channel volume
Mono output mode
Headphone equalizer
App Themes:
Light theme - White and Red
Dark theme - Grey and Red
Credits
This post was written by @ZakooZ
This app is brought you by the exynos5420 developer team: @deadman96385 @thompatry @ZakooZ @Orion116 @mosimchah @joshndroid @Andmoreagain @thermskin, @javelinanddart, @tincho5588, @ShevT @DarkExistence
Translators:
@ShevT - Russian
The following people deserve distinction for their major contribution:
@tincho5588, responsible for 80%+ of the code for the new features
@deadman96385, the main maintainer of the Deathly kernel and most of the remaining code
Downloads
The app can be found in the Play Store:
Free version (with ads): https://play.google.com/store/apps/details?id=com.exynos5420.deathlyadiutor.ads
Donator version (no ads): https://play.google.com/store/apps/details?id=com.exynos5420.deathlyadiutor.adfree
Helping the developers
You may have noticed there's 2 versions of this app, one ad-free for donators and one with ads.
You can help us by clicking ads you're interested in for the free version, or purchasing the donator version!
We will use the money generated by this app as common money for the developers of the team. It will be used to pay for our web-hosting (we own a gerrit server and a domain name, exynos5420.com). It will also be used to buy a new device if one of ours breaks.
Translating the App
You can also help us by translating the app to your language:
1. You can start by looking at the full english language file: Link
2. Then compare it to your unfinished language file. You can find it here, under values-xx/strings.xml, xx being your language abbreviation.
3. You can then fill-in the missing strings in your language file. Here's an example of what a proper update looks like.
4. Then you can submit your translation by using our gerrit. If you don't know how to use gerrit, just PM the translation to your favorite developer and he'll get it merged!
Thx for your work
Looking forward to testing it out
Thank you very much for your work!
It doesn't works for me, I only see boot animation and it doesn't start even after 20 minutes. I tried Paulicat version and works fine. Whi? I did a clean flash.
Same for me. Bootllop after flashing ROM and latest Gapps (nano).
Yeah, bootlooping.
BananaPrime said:
Yeah, bootlooping.
Click to expand...
Click to collapse
I installed with a full wipe (including internal sdcard), using latest pico gapps.
No issues...
I also recently updated my bootloader to Mashmallow, but I doubt that's what makes mine bootup while some bootloop.
Bootlooping? How far does it boot ?
Please be 100% certain that you wiped dalvik, system, data and cache in twrp and try flashing without gapps. Did you change anything such as flash custom kernels etc?
Could one of you take a logcat during boot for me please. It has to be user error seeing as mine is working fine, and others are working fine. The number of downloads - complaints shows that.
Just plug your tablet into you PC while it's booting (make sure you have adb installed)
Then , once you start to see the screentype adb logcat into your terminal (./adb logcat if windows or Linux)
Thanks
Just upgrade from @Paulicat's Jan 17th build to this Jan 25th build; just flashed lineage, open gapps nano and SuperSU (in that order, in one go) and rebooted.
Looks like the video problems of the previous release are not present here; I can now play YouTube Videos at high res and use the HW codecs of MX Player without stuttering; previously I had to drop from 1080p to 720p or use the MX+ codecs to make it play smooth.
The WebView component apparently still have problems; using for instance FlipBoard to read articles causes a crash/weird screen flickering from time to time, associated with a crash. The log reports a WebView crash (there's first a "OpenGLRenderer: GL error: Out of memory!" followed by a google-breakpad dump of "WebView:55.0.2883.105" "A arm 04 armv7l samsung/lineage_chagallwifi/chagallwifi:7.1.1/NMF26V/e609fadfba:userdebug/test-keys" "webview" "OpenGL ES 3.0|ARM|Mali-T628" and a long hex dump.
Finally, GPS does not work out of the box; the gpsd still misses a few libraries. I've copied them from elsewhere (RR, if I recall correctly) and have placed libsec-ril.so and libxml.so in /system/lib -- and then GPS works instantly (as far as I can tell it may lock on faster than on the previous build).
I guess the WebView has to be fixed upstream, but maybe the missing gps related libraries could be included in the next build?
Thanks for your great work!
- Per.
pnomandk said:
Just upgrade from @Paulicat's Jan 17th build to this Jan 25th build; just flashed lineage, open gapps nano and SuperSU (in that order, in one go) and rebooted.
Looks like the video problems of the previous release are not present here; I can now play YouTube Videos at high res and use the HW codecs of MX Player without stuttering; previously I had to drop from 1080p to 720p or use the MX+ codecs to make it play smooth.
The WebView component apparently still have problems; using for instance FlipBoard to read articles causes a crash/weird screen flickering from time to time, associated with a crash. The log reports a WebView crash (there's first a "OpenGLRenderer: GL error: Out of memory!" followed by a google-breakpad dump of "WebView:55.0.2883.105" "A arm 04 armv7l samsung/lineage_chagallwifi/chagallwifi:7.1.1/NMF26V/e609fadfba:userdebug/test-keys" "webview" "OpenGL ES 3.0|ARM|Mali-T628" and a long hex dump.
Finally, GPS does not work out of the box; the gpsd still misses a few libraries. I've copied them from elsewhere (RR, if I recall correctly) and have placed libsec-ril.so and libxml.so in /system/lib -- and then GPS works instantly (as far as I can tell it may lock on faster than on the previous build).
I guess the WebView has to be fixed upstream, but maybe the missing gps related libraries could be included in the next build?
Thanks for your great work!
- Per.
Click to expand...
Click to collapse
Glad most things is working for you!
Yep, this build has a more updated device tree then what Paulicat had so there are a few fixes!
GPSD is being investigated by @deadman96385 and should be an easy enough implementation
Thats the first time I have heard about the webview implementation, would you mind sending a full log? Thanks for letting us know!
DarkExistence said:
Glad everything is working for you!
Click to expand...
Click to collapse
So far, it's better -- also appears more "smooth" and fluid in use, I think
GPSD is being investigated by @deadman96385 and should be an easy enough implementation
Click to expand...
Click to collapse
Yep, possibly just a few missing libraries or a different linking method, or something. Good you're working with @deadman96385 on this also; he already responded to this in the other thread when I debugged and reported it related to the previous build.
Wiped all for 3 times, it doesn't boot.
Eboshi Moriyama said:
Wiped all for 3 times, it doesn't boot.
Click to expand...
Click to collapse
I have a f2fs data partition. Perhaps that ist the reason for the bootloop?! (i have the bootloop too)
Clean flash - boot OK - flashed pico OK - flashed superSU OK - boot OK
No prob at all :good:
kaodd said:
Clean flash - boot OK - flashed pico OK - flashed superSU OK - boot OK
No prob at all :good:
Click to expand...
Click to collapse
tried again with clean ish flash - bootloop
tried dirty over RR 7 - boot ok - total frozen :laugh:
start with 3-fingers in recovery, u know what i mean
starting again lineageOS Darky-Edition
nice boot animation, kinda posh will try xposed too
My T800 is currently happily running the now out of date [AOSP 7.0][T700/T705/T800/T805] by @Schischu so I'm looking to upgrade. Here are apps I'd like to know work before I give this ROM a try. If anyone can tell me if they work or not I'd appreciate it. If any of them are considered mods I apologize in advance as I've read the OP mods policy. In any case I'd never ask for their support or inclusion in the ROM as that's my responsibility.
Here's my list:
Viper4Android
Substratum
LastPass (some other 7.1.1 ROMs have issues with this app)
Netflix
Plex
Thanks
{
"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"
}
Code:
/*
* Your warranty is now void.
*
* Syberia Team 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.
*/
Read the whole OP! Be respectful to each other and don't ask for ETAs, it's considered as being rude!
Syberia Project (aka Syberia OS) is a custom ROM for Xiaomi MI A3 that implements various features. This project was designed by our "Syberia Team" from scratch based on AOSP source code with some CAF fixes and improvements. Our team: @DennySPB, @blinoff82, @alexxxdev. Also many thanks to our designers @rlshukhov and @a18h for logos, wallpapers and bootanimations.
If you like our work you can buy us a cup of coffee or a glass of beer
Here
Code:
Monet
VoLTE, VoWiFi
LineageOS LiveDisplay
MicroG support
Pocket Judge
Call recording
Statusbar items switches
Three finger swipe to screenshot
Extended powermenu
...Settings and features will be gradually added.
SyberiaOS ROM Download
Recovery Download
Magisk Download
First time clean installation:
Code:
- Unlocked bootloader is required!
- You must have installed FW11 based ROM.
1 - Boot your device into fastboot mode:
adb reboot bootloader (or power off and power on again
while pressing Power + Vol Down)
2 - Flash Syberia recovery via fastboot
fastboot flash boot <name of the file>
3 - Reboot to recovery
4 - Perform factory reset (formatting data is important)
5 - Here you have 2 choices to install rom
1) Install > Sideload from ADB
on PC open terminal and type - adb sideload <rom zip name>
2) Install > install from sdcard or OTG
Just copy rom to the sdcard or OTG and install from it.
6 - Reboot to system, wait until rom booted, then reboot
in recovery again.
7 - Now you can install other zips (gapps, magisk etc) if needed by
using the methods described in the 5'th line of guide.
8 - If you flashed gapps, factory reset once more is a Must!
Updating:
Code:
1. Reboot into recovery
2. Here you have 2 choices to install rom
1) Install > Sideload from ADB
on PC open terminal and type - adb sideload <rom zip name>
2) Install > install from sdcard or OTG
Just copy rom to the sdcard or OTG and install from it.
3. Reboot to system
Code:
- You tell me only with logcat (screenshots)
Attention! We are not responsible for the operability of your device if you use third-party kernel, Xposed Framework or unverified Magisk modules.
Official website
Syberia Project Github
Syberia Project Gerrit
Device Source
Kernel Source
Official Telegram Group
Announcements Telegram Group
Development Telegram Group
Device Support Group
Code:
- LineageOS
- AOSPA (aka Paranoid Android)
- Nitrogen Project
- Benzo Rom
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
{
"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"
}
Code:
*** Disclaimer ***
I am not responsible for any damage you made to your device.
You have been warned.
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today.
Features:
https://github.com/crdroidandroid/crdroid_features/blob/12.1/README.mkdn
Extra features (implemented by the maintainer):
Code:
* Ability to disable touchscreen buttons
* Audio amplification
* Bluetooth aptX codec
* Clear Speaker
* GrapheneOS Camera
* Improved battery saver at kernel level
* LED indicator on offline charging (red when 0-99%, off when 100%)
* Mi Sound Enhancer
* Properly calibrated sensor-based Doze mode
Flashing Instructions:
Pre-installation:
OrangeFox recovery (Download from here)
Gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
Firmware (Download from here)
First time installation (Non-standard - read):
Spoiler
Install OrangeFox recovery from the "Pre-installation" section or any other recovery with FBE encryption support
Download the latest crDroid ROM & the latest Gapps package (Optional)
Boot into recovery
Perform a wipe of
Dalvik / ART Cache
System
Vendor
Cache
Format data is MANDATORY using OrangeFox recovery (or any other recovery with FBE encryption support)
Flash crDroid ROM
⚠ The ROM is encrypted by default. This is a crDroid requirement! ⚠
If you don't care about encryption, you can disable it within OrangeFox recovery: demonstration (you should see "Disable FBE" button instead)
Note: encrypting via ROM's settings is no longer supported in crDroid, so you will not be able to enable encryption in any other way (except clean install or as shown in the demo above).
Flash Gapps [NikGapps SL ARM64-Core] (Optional)
Flash Magisk Root (Optional)
Reboot to the system
Update installation:
Spoiler
Download the latest crDroid ROM
Reboot to recovery
Flash crDroid update
Note: you don't need to flash Gapps/Magisk again
Wipe Dalvik / ART Cache
Reboot to the system
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_xiaomi_rova
Download:
ROM https://crdroid.net/rova/8
Changelog: See here
Known issues:
You tell me
Visit official website @ crDroid.net
crDroid rova Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
It looks really nice. I think I'll be testing it soon. Thanks.
Is there anyone using this room ? How about stability and battery life ?
Hello,
I've tested the ROM for 3 days and it works fine. Battery life is really great, for me with a normal use I can have 2 days of battery life, including wifi and network use.
I like a lot all the customizations options, really nice.
I recomend this rom.
hi do i have to download latest version of orange fox or R11.1(3) or older. im trying to install to stock rom.
mm.ycel said:
hi do i have to download latest version of orange fox or R11.1(3) or older. im trying to install to stock rom.
Click to expand...
Click to collapse
install latest version for cr8, it's using FBE encryption
ok now i flashed latest version but boot orangebox.....img command giving me long orange lines on screen.
mm.ycel said:
ok now i flashed latest version but boot orangebox.....img command giving me long orange lines on screen.
Click to expand...
Click to collapse
your device is riva. Read "Miscellaneous" spoiler
Update for crDroid 8
Spoiler: Changelog
- Synced with crDroid 8.7 sources (July security patches). Read official changelog:
* https://crdroid.net/blog/2022-07-14-crDroid-8.7
* https://crdroid.net/blog/2022-07-24-changelog-july-24
* https://crdroid.net/blog/2022-08-05-changelog-august-5
- Upgraded kernel to 4.9.323-2.1-iusmac
- Reduced battery drain when using "Pocket Detection" feature
- Added Smart Charging feature (Settings > Battery > Smart Charging)
- Improved GPU power hinting
- Added Userspace Reboot (adb reboot userspace)
- Fixed empty "Internet" tile in Quick Settings
- Added more Dirac presets
- Improved display latency & responsiveness
- Switched to UClamp for boosting & capping
- Updated GrapheneOS Camera App to v45
- Added native support for "Ok Google" hotword feature
- Increased CPU boosting to 1.2s on Lock Screen
- Improved RAM pressure management
- Fixed "laggy" start of boot animation
- Enabled VoLTE and VoWiFi for all carriers
- Upgraded blobs/configs to Android 11 (R) for:
* Audio
* Media
* Display
* Telephony (RIL/IMS)
* Bluetooth
* WiFi
* GPS
* Sensors
- Fixed call volume control for both speakers and for Bluetooth earpiece
- Fixed broken screen recording (now ~30fps instead of ~10fps)
- Fixed detection of headset buttons (hook, Vol+, Vol-)
- Made the extra features searchable in Settings app
- Switched to performance governor for GPU power hinting
- Add support for Google Phone call recording
(!) requires any Text To Speech (TTS) app for working
I see that the instructions say that I need firmware V10.1.1.0.NCKMIFI.
Can I come from 10.3.2 OCKMIXM?
First time to flash this phone. I still have to enable unlocking through the Mi Account
ayunatsume said:
I see that the instructions say that I need firmware V10.1.1.0.NCKMIFI.
Can I come from 10.3.2 OCKMIXM?
First time to flash this phone. I still have to enable unlocking through the Mi Account
Click to expand...
Click to collapse
you need to downgrade to the latest nougat firmware or you will get in trouble with everything (roms, kernels, recoveries etc.).
I've now downgraded using the link below and have installed the NCKMIFI firmware. After numerous tries with Mi Unlocker and trying to get OrangeFox working, I finally got the ROM installed (with FBE disabled). For those with Mi Unlocker failing to unlock, try using Find Me through i.mi.com. I also had to flash the NCKMIFI firmware even though I used the All-in-One procedure for iusmac's OrangeFox recovery to correctly detect partitions. I didn't use the rilfix and sensorfix zips.
Downgrader: https://forum.xda-developers.com/t/guide-rollback-downgrade-firmware-from-oreo-to-nougat.3938904/
Everything in this ROM is pretty fast! It feels like a new phone compared to stock firmware. So much free space too. Pretty unbelievable for such an old and low-spec phone (SD425/2GB RAM/16GB storage). Funny how I was happy to see 100% health of the phone's eMMC too! Whew.
I also installed Nikgapps core as per instructions though I wonder if Basic wouldn't slow this down too much -- but I installed most of the Basic's apps anyway except for Dialer through the Play Store.
===================================
But something seems wrong with Mobile Data. I'm using two sims but have also tried one sim.
1: Somehow, my primary sim's data is not working even though APN etc is set. My secondary sim works with mobile data though. Tried switching them around and using the primary sim alone to no avail. In dual-sim, the mobile data QS tile says that it is Not set to use data when this SIM's data connection is activated.
The primary sim was working in my stock ROM as SIM1 and is tested working in other phones. The primary SIM's network is Globe Telecom in the Philippines.
2: The Data Disabled indicator seems to be inconsistent.
Using the secondary sim's data (in dual-sim or single-sim), I get data but:
----- 2.1: when data is on and the indicator is on, the data disabled indicator (!) still shows up.
----- 2.2: when data is on and the indicator is off, the data disabled indicator (!) still shows up.
----- 2.3: when data is off and the indicator is off/on, the indicator(!) works correctly
3: The switch data card in QS seems confused? The points below are in dual-sim.
----- 3.1 When using SIM1 for data (seen in QS and in SIM settings), the switch QS tile says SIM2 is active.
----- 3.2 When using SIM2 for data (seen in QS and in SIM settings), the switch QS tile says SIM1 is active.
This is contrary to how switch data works with Android 12.1 (EvolutionX ROM) on my Mi A1 phone where it shows the current active data sim.
So that's my only problem now, mobile data being inconsistent with dual-sim. And somehow mobile data not working with the Globe Telecom (primary) sim even with switching them around. Luckily, this primary sim isn't being used so much for data as the secondary one has free data for messaging services so the 2nd one is being used a lot more anyway.
I hope these get solved as they are the only things I think that is wrong with this ROM
After trying to get things right, I got it. What I did was to downgrade from miui11 oreo to nougt, install given orangefox, format data, then flash crdroid, gapps and magisk.
After setting everything up, I can say that its awesome. This gives me a lot of customizations to play with, and most importantly, android12 update. Thanks a lot for helping me revive my old phone.
Is this custom rom safe for banking transaction? Thx
It is giving very poor battery life and has overheating issue.
This was not the case with android 11 nitrogen OS which gave superb battery life.
Is there any solution or explanation to what could have gone wrong?
Else everything is superb.
Thank you
Jyoti_re said:
Is there anyone using this room ? How about stability and battery life ?
Click to expand...
Click to collapse
Good stability but poor battery life with overheating issue.
Cant say if only in my case or all devices.
Update for crDroid 8
Spoiler: Changelog
- Synced with crDroid 8.8 sources (August security patches).
Read official changelog:
* https://crdroid.net/blog/2022-08-11-crDroid-8.8
* https://crdroid.net/blog/2022-08-19-changelog-august-19
* https://crdroid.net/blog/2022-08-30-changelog-august-30
- Upgraded kernel to 4.9.326-2.2-iusmac
- Switched to HW compositing for EGL & SurfaceFlinger
- Disabled zRAM writeback job (caused "lagginess" on long-term usage)
- Optimized graphics & high resolution video playing
- Improved disk I/O performance
- Fixed smart charging not resuming when overheated
- Fixed smart charging sometimes not working in deep sleep
- Backported FMRadio app from LineageOS 18.1
* adapted code base to Android 12+
* added full wireless support (uses builtin antenna)
* improved UX
* redesigned UI
* added dark mode + "Material You" colors
- Updated MTP USB IDs from Mi 10
- Added "Reboot to Fastboot" item to advanced reboot menu
(!) It will reboot you to recovery builtin fastboot. It doesn't work
specifically on OrangeFox R11.1(4). Wait for R11.1(5).
- Updated GrapheneOS Camera App to v47
- Added thermal mitigation and sensor-based (battery, skin, CPU/GPU)
overheat warning pop-ups
Update for crDroid 8
Spoiler: Changelog
- Synced with crDroid 8.9 sources (September security patches).
Read official changelog:
* https://crdroid.net/blog/2022-09-11-crDroid-8.9
- Improved disk I/O performance
- Increase zRAM to 1.5G
- Optimized graphics render engine
- Updated FMRadio to v3.1:
* Fixed colors for Pure dark
* Fixed RDS retrieving
- Optimized builtin screen recorder
- Updated GrapheneOS camera to v48
Awesome ROM. Obviously this phone is lagging a lot, maybe due to RAM issues, but ROM has no issues. Who would have thought this phone getting Android 12? lol
iamsonal said:
Awesome ROM. Obviously this phone is lagging a lot, maybe due to RAM issues, but ROM has no issues. Who would have thought this phone getting Android 12? lol
Click to expand...
Click to collapse
Thank you, appreciate that! The laggs increase proportionally to quantity of apps on the background and how heavy they are. The main trick is to use alternative less heavy apps, and the most important to disable all non-sense/meaningless notifications to the apps.
{
"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"
}
Code:
#include <std_disclaimer.h>
*
* 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.
*
LineageOS is a free, community built, aftermarket firmware distribution of Android 12L (Sv2), which is 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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Githup repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended LineageOS recovery in the official installation instructions link below.
You can use TWRP for installation, however it is no longer officially supported since we do not have full control of its update cycle and potential issues.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
Installation Instructions:
Backup your data and see the next post below
Recommended TWRP Image:
twrp-3.7.0_9-0-kuntao.img
ROM Download Links:
Google Drive | SourceForge
Recommended Google Apps Package:
NikGapps-core-12.1
NikGapps-SetupWizard
NikGapps-AndroidAuto
Or
MindTheGapps-12.1 (Google Drive mirror)
Root Access:
Magisk v25.2 (more stable experience)
Magisk v26.1 (more updated build)
Recommended Useful Add-on:
p2oggle-1.2
Source Code:
https://github.com/LineageOS
ROM Firmware Required:
Any version of stock 6.0. Recommended P2a42_S251_171107_ROW
Acknowledgements:
Thanks to @mikeioannina for his hard work regarding kuntao and to all other Lineage OS developers
Special thanks to @Astridxx for the device tree sources and for helping me out and to @en666 for early testing the initial build
Important Notes:
As you can see from my profile, I'm not an experienced developer. I've made some builds as a considerable amount of users showed interest in having their devices updated with latest LineageOS code. Therefore, my main objective here is to bring the latest Android security patches to kuntao making monthly builds.
To be clear, I'm more in a situation of "user became builder" than of "ROM developer". Please, understand this.
Long live to our beloved kuntao!
XDAevDB Information
[ROM][12.1][UNOFFICIAL] LineageOS 19.1 for Lenovo P2
Contributors
@Astridxx ,@XiaoAk ,@Sohit5s, @mikeioannina
ROM OS Version: 12.x
ROM Kernel: Linux 3.18.x
Based On: LineageOS
Version Information
Status: Stable
Created 2023-02-22
Last Updated 2023-06-11
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!
{
"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"
}
Code:
#include <std_disclaimer.h>
*
* 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.
*
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is 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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Githup repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
Installation Instructions:
Backup your data and see the next post below
Recommended TWRP Image:
twrp-3.7.0_9-0-kuntao.img
ROM Download Links:
Google Drive | SourceForge
Recommended Google Apps Package:
NikGapps-core-13
NikGapps-SetupWizard
NikGapps-AndroidAuto
Root Access:
Magisk v25.2
Source Code:
https://github.com/LineageOS
ROM Firmware Required:
Any version of stock 6.0. Recommended P2a42_S251_171107_ROW
Acknowledgements:
Thanks to all Lineage OS developers
Special thanks to @Astridxx & @XiaoAk for the device tree sources and to @Astridxx for (once again) helping me out
Important Notes:
As you can see from my profile, I'm not an experienced developer. I've made some builds as a considerable amount of users showed interest in having their devices updated with latest LineageOS code. Therefore, my main objective here is to bring the latest Android security patches to kuntao making monthly builds.
To be clear, I'm more in a situation of "user became builder" than of "ROM developer". Please, understand this.
Long live to our beloved kuntao!
XDAevDB Information
[ROM][13][UNOFFICIAL] LineageOS 20 for Lenovo P2
Contributors
@Astridxx ,@XiaoAk
ROM OS Version: 13.x
ROM Kernel: Linux 3.18.x
Based On: LineageOS
Version Information
Status: Stable
Created 2023-03-05
Last Updated 2023-04-20
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.