[ROM Recommendation] - Working encryption, Android 10, Multiple users - Asus ZenFone Max Pro M1 Questions & Answers

[ROM Recommendation] - Working encryption, Android 10, Multiple users - Asus ZenFone Max Pro M1 Questions & Answers

Hi, I'm looking ROM with:
- Working encryption
- Android 10
- Multiple users
- Hidden & Protected apps ( in application drawer, like in Lineage and Havoc ) [optional]
- Option "Longpress back to kill app" [optional]
- Option "Clipboard access alerts" [optional]
I was using LineageOs 16 and it was fine, but update broken system and I had to reinstall stock.
In mean time Asus published update to 10.0 so I have tried it, I was missing launcher from Lineage and multiple users but besides that it was pleasant experience.
Then I have installed HavocOs 3.8 and it was great, it has nearly everything I need but unfortunately encryption is broken and this is big NO for me.
Can someone confirm that, encryption in unofficial Lineage 17 is broken? If no, is it ready for daily use?
I will probably get back to lineage 16, if I will not find ROM meting this requirements.

Related

[ROM][Official][4.4.4] CyanogenMod 11.0 Nightlies

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4.4 (Kit Kat), which is designed to increase performance and reliability over stock Android for your device.
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.
*/
CyanogenMod 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). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions:
First time flashing CyanogenMod 11.0 your device, or coming from another ROM?
Download the zip(s).
Optional: adb backup
Perform a NANDroid backup of your current ROM.
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Issues?
Report them on github:
https://github.com/M1cha/android_device_xiaomi_aries/issues
What's important: if you use xposed - pls disable it and try it again because it can cause problems in some cases.
Also the issue must contain important information like your phone model(mi2(s)(c)), and the exact build version of the ROM.
Download Links:
CyanogenMod:
Nightly:
Download: http://download.cyanogenmod.org/?device=aries
Google Apps addon:
Use 4.4 gapps:
Download: http://wiki.cyanogenmod.org/w/Google_Apps
Sourcecode:
ROM: https://github.com/CyanogenMod
Devicetree: https://github.com/CyanogenMod/android_device_xiaomi_aries
Kernel: https://github.com/CyanogenMod/android_kernel_xiaomi_aries
GENERAL COMMENT AND REQUEST:
We ask all the regular contributors here to please answer the "xxx is broken" or "yyy force closes" statements without an attached logcat with something like "LOGCAT or it didn't happen"
Feel free to be creative but DO NOT respond with wipe cache/clear data or any other attempted solution before the reporting user has taken the trouble to actually try to help solve the problem (e.g. by attaching a logcat, detailed steps to reproduce etc.).
We need to force more discipline in how issues are reported which will help us all find and squash bugs that may exist.
Just clearing data etc. may in fact cause us to never find the bug that caused the issue and just makes for lazy users.
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
CyanogenMod 11.0 Nightlies, ROM for the Xiaomi Mi 2
Contributors
m11kkaa
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Created 2014-09-15
Last Updated 2014-09-15

Troubleshooting/ FAQs
I am reading FAQs, am I ok?
You're the best , but I'm not sure how you'll fell after you've read these things...
How can I enable Developer/ Performances Settings?
Go to Settings>Info>Click several times on build
How can I enable 4 way reboot (Recovery, System, soft, Bootloader) ?
Enable developer options, then go to Settings>Developer and enable Advanced Reboot
Why there's no HDR on camera?
Cyanogenmod does not provide closed source software, like drivers for HDR, you need to install Miui camera, or another camera from playstore
Why is there no Play Store or <insert gapp here>?
Since there are 2 system partitions they're small, and kk needs about 800mb to have a rom + gapps. There are 2 things u can do: First: install this gapps package this. Second way: use the repartition script of XiaomiTool to extend them.
Why is performances profile resetted every boot?
You need to enable Settings>performances>CPU>Set on boot
Why the phone doesn't fly if I enable airplane mode?
It's a WIP (work in progress) feature, now it works only if you throw it at 11,2 km/s² toward the space. It looks like there's no fix for this (yet).*
How can I enable adb root?
Go to Settings>Developer>Root access> Apps and Adb
How can I hide apps from trebuchet (launcher)?
Click Menu>Protected Apps> Set a "password"> Hide them
How can I charge my phone?
It looks like the xiaomi charger isn't enough powerful to charge the phone with cm. Here's your fix: buy a small nuclear reactor (you can find a cheap one on amazon or ebay I think), place the phone between the uranium fuel rods, power the reactor on and let the phone charging for about an half hour. It will be charged and it won't discharge again anymore.*
(I'm running art, it's very good and i feel better running it) This app FC... What can i do?
Switch to dalvik
Today I updated the phone and it's in a bootloop now...
Nice to get know you're enjoying art, switch back to dalvik flashing this
Bugs
http://wiki.cyanogenmod.org/w/Known_Issues_page_for_aries
[DEV] How to build
http://wiki.cyanogenmod.org/w/Build_for_aries
Two Releases: Nightlies and Stable/Monthly
Nightlies and Monthlies are very different. YOU CAN NOT UPDATE FROM A NIGHTLY TO A MONTHLY WITHOUT A WIPE /DATA. Why? Simple, M releases uses a different branch and it's much older than the previous Nightly avaible, so this may cause bootloops.
So you can update from a Monthly to newer Nightly, but you cannot update from a Nightly to a Monthly. If you choose unstable branch (aka Nightlies) you shouldn't update via ota to Stable branch (aka Monthly), you need to wipe /data.
Other Info
http://wiki.cyanogenmod.org/w/Aries_Info

I'll be building Slim (and maybe Omni) for this soon, so I was wondering which vendor repo do you use?

Great I use themuppets https://github.com/TheMuppets/proprietary_vendor_xiaomi

Sorry for the possible spam, I just wanted to ask will this be now ''official'' thread for CM11 instead of the one on xiaomi.eu?

SkaldfraNorden said:
Sorry for the possible spam, I just wanted to ask will this be now ''official'' thread for CM11 instead of the one on xiaomi.eu?
Click to expand...
Click to collapse
yes

Hi, a question about TDB: I (stupidly) formatted /sdcard before flashing CM11 (to get rid of MIUI folders), and I lost write permission. To fix that, I enabled TDB and installed MIUI on system2 and booted. However, I will never boot into MIUI again, I'm only interested in CM. Is leaving TDB enabled affects performance in any way? And is there a different way to restore permissions other than flashing MIUI?

isaacbh said:
Hi, a question about TDB: I (stupidly) formatted /sdcard before flashing CM11 (to get rid of MIUI folders), and I lost write permission. To fix that, I enabled TDB and installed MIUI on system2 and booted. However, I will never boot into MIUI again, I'm only interested in CM. Is leaving TDB enabled affects performance in any way? And is there a different way to restore permissions other than flashing MIUI?
Click to expand...
Click to collapse
Sdcard format is not working well on cwm cuz of tdb. U have to flash a fastboot package and or flash a stock miui with miflash.
Tdb doesn't affect performances at all.

Tdb doesn't mess with sdcard at all so it probably is a cwm bug.

Good to see we're moving to XDA!

m11kkaa said:
Tdb doesn't mess with sdcard at all so it probably is a cwm bug.
Click to expand...
Click to collapse
Another scenario in which this bug showed for me was this. Maybe this is useful to track the issue.
I installed CWM 6.0.5.0, and then WIUI (4.7.18) based on KK.
After formatting the sdcard from within WIUI, even without rebooting, at that point the internal sdcard couldn't be written any longer from within WIUI.

I'm using this ROM and i'm really impressed.
One thing though is that my battery is going down much faster than on miui.
Any tips?

Check if you have wakelocks and freeze with greenify

does anyone have problem with Gapps on CM11-M10 like me? Gapps force-close all the time although I had try to reflash the rom 2 times!

you either have to flash a very small gapps package or resize your system partition(s)

thienquang07 said:
does anyone have problem with Gapps on CM11-M10 like me? Gapps force-close all the time although I had try to reflash the rom 2 times!
Click to expand...
Click to collapse
Read FAQs

Great ROM!
So far everything has been running smooth. Performance is great, feels much speedier than Mokee OS. Battery seems to be going down a bit faster, but I've been setting everything up so that probably explains the battery drain.
Something that really annoys me though, is that music playback stutters whenever you touch something. Opening the app drawer, any app, upvoting a post on Reddit Sync, ... Everything makes the music stutter for a split second.

Mavamaarten said:
Great ROM!
So far everything has been running smooth. Performance is great, feels much speedier than Mokee OS. Battery seems to be going down a bit faster, but I've been setting everything up so that probably explains the battery drain.
Something that really annoys me though, is that music playback stutters whenever you touch something. Opening the app drawer, any app, upvoting a post on Reddit Sync, ... Everything makes the music stutter for a split second.
Click to expand...
Click to collapse
Disable "sound on touch"

linuxxxx said:
Disable "sound on touch"
Click to expand...
Click to collapse
Oh god. I'm glad the fix is that simple. Thanks a bunch, I really didn't think of that.
I even disabled the "Okay Google" hotword because according to some googling the issue was connected to that.

Video camera records video maximum 10 minutes. Could it be changed to unlimited?
And also sound quality is very poor in recorded videos. I looked through spectrums and it appears that they are cut above 8000Hz. Seems like on some stage signal is being sampled with 16000 Hz sample rate and, judging by some bubbling and other artefacts, it is made without prior antialiasing filtering. Output format acc 48000 Hz.

NitrogenOS Megathread

{
"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"
}
Welcome to the NitrogenOS Q&A Megathread. Here you can find answers for the most popular problems and questions about NitrogenOS. I started this thread, so that new users don't repeatedly ask the same questions multiple times. While I am fairly new to coding in Java, I can definitely say I know a lot about Android phones and NitrogenOS, but you'll have to trust me on that. If you need any more help, you can even PM me and I'll try to reply as soon as I can.
You can find the original NitrogenOS thread here.
ROM info
Developer: xyyx
Latest Android version: 8.1 Oreo
NOS Download (latest): https://sourceforge.net/projects/nitrogen-project/files/kenzo/kenzo_test/8.1/
Bugs and updates
- A (very) small amount of users reported Google Dialer not working properly while installed through OpenGapps or the Play Store, you can still use stock dialer
1. Test or stable?!?!
Test in this case doesn't mean less stable. xyyx named the two versions a little confusingly.
Test means Oreo (Android 8.0 and 8.1) and Stable means Nougat (Android 7.1.2).
So let's make this a little less confusing:
Oreo (8.0) builds -> Download from here
Oreo (8.1) builds -> Download from here
Nougat (7.1.2) builds -> Download from here
2. Youtube PiP (Picture in Picture mode)
Google has patched PiP a long time ago, so it doesn't work with the latest Youtube releases. The last official release working with PiP is 12.34.55, which you can download from ApkMirror.
My preferred option however is iYTBP (injected YouTube Background Playback), a modified version of Youtube, but it gets a little confusing as there are multiple options.
You can download it from this thread.
Now the tricky part - choosing the right version. I always prefer the Vanced version, which can be found in the 2nd post. Again you have multiple options, but I will not go through all of them since they are explained pretty good in the post itself. While iYTBP enables PiP, it also blocks ads and adds a lot of useful settings and new updates come very frequently. There are multiple installation methods, but I prefer the Magisk one, since it offers options like detaching the Youtube app from Play Store. What this means is, that you don't have to disable auto-updates and it will not bug you to constantly update it.
You can try these methods:
Magisk Module (Easiest):
1. Open Magisk Manager
2. Go to Downloads
3. In the search bar type "Youtube", you should see two results
4. Choose either the normal or the black theme (I personally prefer the black one)
5. Press the download arrow and then "Install"
6. Wait for a while (it's a big package to download and unpack)
7. Reboot
This is by far the easiest option and the module is updated fairly often.
Manual:
1. Delete or uninstall any previous release of Youtube. If you installed it as a system app, disable it or delete the /system/app/YouTube folder. If you had to delete the folder, reboot.
2. Download the Youtube apk
3. Make a folder called YouTube (watch the caps!)
4. Move the apk to this folder and rename it as YouTube (again with the caps)
5. Copy/move the folder to /system/app (The directory should look like this: /system/app/YouTube/YouTube.apk)
6. Reboot
Magisk (manual):
1. Download the Youtube apk, the iYTBP universal installer and the use_this_settings.sh file. Check that they are in the downloads folder.
2. Edit the use_this_settings.sh file if you want. Since we're installing from Magisk, you'll need to set MAGINSTALL to YES (MAGINSTALL="YES"). I usually also enable detach (DETACH="YES"). This will make the Play Store think Youtube isn't installed and it will not bug you for updates.
3. Open Magisk Manager, go to Modules and press the + button. Now select the universal installer zip and flash it in Magisk.
4. Reboot
Recovery method:
Same as for Magisk, but MAGINSTALL is set to NO (MAGINSTALL="NO"). In case you didn't read the Magisk method, here is the recovery method...
1. Download the Youtube apk, the iYTBP universal installer and the use_this_settings.sh file. Check that they are in the downloads folder.
2. Edit the use_this_settings.sh file if you want. I usually enable detach (DETACH="YES"). This will make the Play Store think Youtube isn't installed and it will not bug you for updates.
3. Reboot to recovery, go to Install and choose the universal installer zip, flash it.
4. Reboot
If you open a video in fullscreen mode and press the home button, it should open it in PiP mode. If you want to change some advanced settings, you can go to your Account (the round icon with your profile picture) -> Settings -> iYTBP Settings
3. Goodix & FPC - What are they
Goodix and FPC are two different types of fingerprint sensors (or rather sensor manufacturers). They both work in Android 8.1 builds. Custom kernels or mods may break the fingerprint sensor functionality.
4. Rooting
tl;dr: rooting NitrogenOS is the same as rooting any other custom rom, just flash Magisk, SuperSU, phh's superuser or anything else.
Now for the extended version.
Magisk:
Magisk is a great open-source root manager, developed by topjohnwu. It features a feature rich app, but most people prefer it because of it's "modules", packages which can do a bunch of things, from installing apps like Viper4AndroidFX or Dolby Atmos, to modifying system settings, like the volume steps increase. Magisk also features an option called "Magisk Hide", which can bypass Android's SafetyNet.
Check out the Magisk thread.
You can directly download the latest version of Magisk from https://tiny.cc/latestmagisk
SuperSU:
SuperSU is an alternative root manager. It used to be developed by Chainfire, but has recently been purchased by another company. I still prefer Magisk, but SuperSU is a great alternative for new users. My problem with it though is, that it is not open-source and the new buyer is pretty secretive so I don't really trust them.
Check out the SuperSU website for the download link.
phh's SuperUser:
Another open-source root manager, but the great thing about this one is, that it's very minimalistic and very small in size.
Check out the SuperUser thread and phh's Build Bot.
5. Google Apps (gapps)
Google apps are a vital part of custom roms. You might not know this, but AOSP and CM based roms are made from Google source code. Google actually makes Android open-source, but the Play Store and other Google apps are not. That's why roms like NitrogenOS do not come with the Play Store preinstalled. That is where Open Gapps come in. They are prepackaged apps, updated almost daily. They come in various sizes and versions, but they can all be flashed in TWRP like a normal zip file.
Platform: arm/arm64/x86/x86_64 - RN3 has an arm64 processor (Think of it as a 64-bit CPU for phones)
Android: 8.0/7.1/7.0... - This is the android version, NOS is Oreo based so choose 8.0 (Or 7.1 for Nougat) [Check below for OpenGapps 8.1]
Variant: This is where it gets complicated. There are a LOT of versions to choose from. For more in-depth resources check the OpenGapps' package comparison.
But OpenGapps are a lot more customisable, to the level where you can choose individual apps you want installed. The easiest way to do this, is to flash the Aroma package, which enables you to choose exactly which packages you want installed. Another option is to configure any of the selected packages using a gapps-config.txt file. You can learn more about that in the Advanced Features and Options section.
You can download daily builds for any Android version from https://opengapps.org/
6. TWRP (Recovery)
A recovery is a partition, used to flash files like ROMs, gapps and any other modifications. You do (in most cases) need an unlocked bootloader to use it. Unlocking your bootloader will not be described on this thread, as there are a lot of resources for our device.
Official TWRP - This is the official TWRP (Team Win Recovery Project) for our device
You can find the latest updates for TWRP on their website.
Red Wolf - This is a modified version of TWRP, my absolute favourite because of it's custom features.
Flashing TWRP:
If you don't have a custom recovery installed and you have unlocked your bootloader, then download the latest version of your preferred recovery and follow these steps:
1. Download Minimal ADB and Fastboot on Windows, or use sudo apt install android-tools-adb android-tools-fastboot if you're on Linux.
2. Enable USB Debugging (Settings -> About phone -> Press "Build number" 7 times to enable Developer options). You should find the Developer options in settings above "About Device". Find USB Debugging and enable it.
3. Connect your PC to the phone via a cable. Open Minimal ADB and Fastboot (which will open CMD) or Terminal on Linux and type this (same for both OSs): adb devices. Select "Always allow on this computer" and confirm access on your phone.
4. Reboot your phone to fastboot/bootloader (By holding Power and Vol-, releasing the power button after a vibration and holding the Vol- button until you see the Xiaomi mascot).
5. Type (In CMD/Terminal): fastboot devices, to confirm if the phone has been recognised, then fastboot flash recovery /path/to/recovery.img
6. After it has succesfully finished, remove the cable and reboot directly to recovery (Power and Vol+, release power after vibration, but keep holding the Vol+ button until you see the TWRP or RedWolf logo).
If you do already have a custom recovery installed and just want to update it, flash the .img or .zip file in your already installed recovery and select "Reboot to recovery".
7. NOS asks me for a password after flashing?!!?!?
This is actually not NitrogenOS's fault, it's a byproduct of your previous rom, most often MIUI. What this means is, that your internal storage is encrypted and the only way to fix this, is to backup everything on your internal storage, which you can do by connecting your phone to your pc while in recovery. You should be able to access the phone's storage and move the files from there. If you for some reason can't do that, you can still put in an sdcard and copy the files to it in TWRP. Bottom line, backup the files and then go to "Wipe" and find the "Format data" button. You might see a "wipe data" button, but this is not the same. When you "wipe data" you are wiping your system, cache, dalvik cache and data partitions, but formatting data will format your internal partition as well and thus remove the encryption.
You can finally reflash NOS and gapps or whatever other modification you want.
8. Firmwares
Check out this link to download the latest firmware for our device.
What is firmware? - It's what connects hardware to software (don't confuse it with a kernel). It's what, for example, makes the camera work.
Do I really need firmware - Yes (but it's already installed, even after completely wiping the stock rom, since it's on separate partitions).
Do I need the most up-to-date firmware - Actually no, the only difference you will notice is in the signal and WiFi strength. If yours are good enough, you don't need to update, otherwise feel free to download the newest version from the link above.
What is emmc_appsboot.mbn? - It's a bootloader update. Bootloader or fastboot is the partition in which you have unlocked your bootloader and flashed the recovery. If you have officially unlocked your bootloader, then you can flash firmware with emmc_appsboot.mbn, but if you have unofficially unlocked your bootloader, do not flash these files as they will re-lock it. But you can still flash the version without emmc_appsboot.mbn.
Kenzo? Kate? - Kate devices are the same as kenzo ones but are a little bigger.
Some comparisons:
Kenzo
Size: 150 * 76 * 6.85 mm
Weight: 164g
Kate
Size: 152 * 76 * 6.85 mm
Weight: 167g
Model numbers:
Kenzo: 2015116
Kate: 2015161
Kate devices are 32/3 GB, and some kenzo devices are as well (some are 16/2 GB), not really sure about this part.
Global stable or developer? - Most people use developer roms, but again, this is not the actual ROM, just the firmware extracted from the rom, it doesn't really matter which one you choose.
When do I need to flash firmware? - If you're coming from MIUI8 (or 9), then you probably have the newest firmware. In this case you don't need to flash it, because MIUI roms already have firmware included in the update. If you're coming from a CM or AOSP based rom you also probably don't have to flash it, but I suggest you update it just in case. If your signal is good enough though, there really is no need.
9. How to flash the rom
Flashing is pretty straight forward. Just go to the Install section of TWRP and flash it like any normal zip, nothing special.
If you're coming from MIUI, then the full procedure is this:
1. Unlock your bootloader (google it, useless explaining it here)
2. Flash TWRP
3. Make a full device backup (Nandroid backup)
4. Copy or move all important files from the internal storage to an sdcard or your pc
5. Format data, or in other words, wipe EVERYTHING (excluding external storage) - This will delete all your photos and anything else in internal storage
6. Flash the latest NOS "test" build (Oreo)
7. Flash gapps (I recommend opengapps.org, check above)
8. Reboot to system
10. OTA?
What is OTA? - OTA means Over The Air (Update)
Does NOS have OTA? - Actually yes and no, newer updates (from March 2018 on) do have partial OTA (it does check for updates and notify you, while also giving a direct download link to SourceForge, but you will have to manually flash every update in your recovery.
What about incremental updates? - Sorry, but no. You'll have to download full packages every time. If you have a bandwidth cap then just download an update every week or two, you can check the changelog to see if you think it's worth updating to.
11. Google Camera
If you're having problems with the official Google Camera or just want some added features then look no further than modded camera apps. Check out this thread by emime12, it's very frequently updated and features a lot of different camera mods, including Google Camera, MIUI Camera, MOTO Camera and many more.
Recommended settings:
3x3 Grid - For better photos
I usually disable "Save location" and "Camera sounds"
Model: Pixel XL (corr) - default
Config camera HDR+: NEXUS 6
HDR+ parameters: Default
Panorama resolution: High
Advanced: Enable both
Experimental: I usually leave this disabled but it's your choice.
Back camera video resolution: UHD 4K (30 fps)
In case your camera doesn't work check if you have these two files and delete them:
/System/framework/com.google.android.camera.experimental2016.jar
and
/System/etc/permissions/com.google.android.camera.experimental2016.xml
Credits go to: @emime12 and Njaiker.
You can find more info about problems and updates on emime12's thread.
Settings may differ a lot, so check emime12's recommended or just test until you find ones that work for you
12. RAM Management - Low free RAM
Android's RAM (Read Only Memory) management doesn't work like Windows'. Android manages RAM very well, "Free RAM is wasted RAM" is a very common expression on XDA. Android loads the first couple of apps into the RAM and priorities the open one. More used ram means more apps loaded in ram which means faster load times. Don't worry about it too much and just enjoy the fast loading speeds.
13. VoLTE?
VoLTE should work on Android 8.1. Magisk, Viper or any other mods may break it.
14. Custom kernels
While there are a lot of custom kernels, I suggest you stick with the stock one, as it is made specifically for NOS and thus it is the most stable. If you still want a custom kernel, you can try Radon or Agni but they might break VoLTE or your fingerprint sensor.
Agni XDA Thread - By psndna88
Radon XDA Thread - By Umang96
15. Daily driver or not?
Yes, NitrogenOS Oreo is very stable, definitely enough for a daily driver. It is the best Oreo rom for our device (in my opinion), as it offers just the right amount of customization and stability.
15. GPS
Some users have reported low accuracy, but you should be fine if you turn on High Accuracy mode and/or install Faster GPS.
Update: In recent updates GPS shouldn't be a problem anymore as xyyx has fixed it, but some users have still reported low accuracy.
16. Viper4Android FX
(There may be other ways, but I haven't tested them yet so I can't confirm if they work) By far the easiest way to install Viper4Android FX is using Magisk. There is Magisk module called ViPER4Android FX Materialized. Download and install that module from the Magisk repo, choose your preferred installation option (By pressing Vol+ or Vol- to select which version you want installed and if you want it materialized - for newest materialized version press Vol+ 2 times) and finally reboot. Try playing some music and open the Viper app. Turn on the "Master Power" switch and the "Playback Gain Control" (the easiest way to tell if it worked). If after a little time the volume increases, it means that Viper4Android FX works. If not, press the three dots and choose "Exit" (without turning off the master power or gain control). Now open the app again and it should work. You can also check that in the side menu under "Driver status", if it's enabled and processing, then everything works.
You may or may not have to exit and re-enter the app after reboot to enable processing (in my case I had to).
I would show you my recommended settings (as requested), but to be honest I only use:
Headset
Viper Bass (Natural bass, 40 HZ frequency, 8 dB)
Viper Clarity (Natural, 6 dB)
Sometimes I use Field surround with default settings
Phone speakers
eXtra loud (Slight, 4x max gain, -1.9 dB max output)
Bluetooth device
Playback gain control (Moderate, 6x max gain, -1.9 dB max output)
If I'm at a party with my bluetooth speaker I pump it up to Extreme and 8x max gain
Viper Bass (Natural, 40 HZ frequency, 8 dB), 17 dB for parties
Viper Clarity (Natural, 3.5 dB)
I don't use equalizers or if I do, they are song-specific. I also don't USB/Dock, so I can't recommend anything there.
Of course these settings can vary depending on the song, so choose those, which you like the most and don't stick with just those I chose, try all the functions to see which you prefer.
17. AdAway (Root)
AdAway is a great open-source root ad blocker, which can automatically download and update sources and works by adding those to the hosts file. It work well on the internet, but also inside apps (most of the time).
Check out the official AdAway website. You can also download it from F-Droid.
Adaway v3.2 (60) (direct download link)
Adding custom host sources:
Go to "Host sources" and add your own sources or check out these: AdAway's host sources
Be careful when adding all of them, since some can block legitimate links like goo.gl.
AdAway also offers an option to scan for Adware, which can be found under "Scan for adware". This will bring up a new window, press "Start scanning". If you don't need/want the mentioned apps you can uninstall them, but AdAway can't block their ads.
You can also check out my recommended settings:

wow,really appreciated that sir., it is very helpful specially for those who wanted to try, flashing rom or any mods on their device like me. thanks and keep up the good work sir God bless!

i think i can add up little bit here.
1) u r on miui & u want to flash nitrogen so u go to recovery and backup ur current rom in case if u dont like nitrogen u can restore back to miui with all ur setting & app. now assume u r on nitrogen, after 4-5 days u dont like nitroge & u decided to come back to miui, so u go to recovery and restore yr backup that u have taken earlier. after success booting the screen with pin or password will appear. so u would enter/guess any previous password, pin u used earlier but it will not open. here the real problem come. i have also faced same issue & got upset searching endless solution on google . u will get mad on u. security bypass will also not work. after spending endless hour i come with solution. download aroma zip search on net. flash it through recovery this will help u to get in system its ike file manager. then head to data, system and delete all file u see below
locksettings.db, locksettings.db-shm, locksettings.db-wal, gatekeeper.password.key, gatekeeper.pattern.key
and then restart, yr problem would be solve.
2) nitrogen os does not support video calling via jio. none custom rom other then then miui support.
3)xposed is not available for oreo.
4)i have used nitrogen oreo for about 2 weeks it is stable but not as miui. some time r net would not work, jio call drop, lagging u have to restart on every time u faced problem. i suggest that wait for some time to roll out nought port for kenzo with zero bug & this will happen soon.

saifuk said:
i think i can add up little bit here.
1) u r on miui & u want to flash nitrogen so u go to recovery and backup ur current rom in case if u dont like nitrogen u can restore back to miui with all ur setting & app. now assume u r on nitrogen, after 4-5 days u dont like nitroge & u decided to come back to miui, so u go to recovery and restore yr backup that u have taken earlier. after success booting the screen with pin or password will appear. so u would enter/guess any previous password, pin u used earlier but it will not open. here the real problem come. i have also faced same issue & got upset searching endless solution on google . u will get mad on u. security bypass will also not work. after spending endless hour i come with solution. download aroma zip search on net. flash it through recovery this will help u to get in system its ike file manager. then head to data, system and delete all file u see below
locksettings.db, locksettings.db-shm, locksettings.db-wal, gatekeeper.password.key, gatekeeper.pattern.key
and then restart, yr problem would be solve.
2) nitrogen os does not support video calling via jio. none custom rom other then then miui support.
3)xposed is not available for oreo.
4)i have used nitrogen oreo for about 2 weeks it is stable but not as miui. some time r net would not work, jio call drop, lagging u have to restart on every time u faced problem. i suggest that wait for some time to roll out nought port for kenzo with zero bug & this will happen soon.
Click to expand...
Click to collapse
Thanks for the tip, will update the thread.

@JustMeErazem volte on 2nd sim works well. I myself use it. After flashing magisk just v need to hide root from all system apps to make sure volte works flawless even after reboot. Plz edit it in the description. I hav been using nos since many time so with experience i am giving my feedback. Thanks?

@saifuk what kind of nougat port u are expecting of ?

Aditya1011 said:
@JustMeErazem volte on 2nd sim works well. I myself use it. After flashing magisk just v need to hide root from all system apps to make sure volte works flawless even after reboot. Plz edit it in the description. I hav been using nos since many time so with experience i am giving my feedback. Thanks
Click to expand...
Click to collapse
I haven't rooted my phone, VoLTE still not working.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
@justmerazem Change VoLTE point again to previous. I installed NOS on mine & my other two friends' phone. They've not used magisk or superSU nor me. But VoLTE doesn't work on 2nd Sim for us.

AtomR said:
I haven't rooted my phone, VoLTE still not working.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
@justmerazem Change VoLTE point again to previous. I installed NOS on mine & my other two friends' phone. They've not used magisk or superSU nor me. But VoLTE doesn't work on 2nd Sim for us.
Click to expand...
Click to collapse
Flash latest firmware of developer rom. And volte is sure shot working.

Aditya1011 said:
Flash latest firmware of developer rom. And volte is sure shot working.
Click to expand...
Click to collapse
Mate, I'm already on 7.9.22 firmware. Lots of people are reporting it. Yours is working, must be some kind of random.

@Aditya1011 Mate, what happened? No reply? Huh. Latest firmware. No magisk, no any kind of root. No sound mod. Still Volte not working on 2nd Sim on 3 different Kenzos.
@JustMeErazem Please include in your post that VoLTE is indeed buggy.

how to install via dualboot patcher as secondary rom?

AtomR said:
@Aditya1011 Mate, what happened? No reply? Huh. Latest firmware. No magisk, no any kind of root. No sound mod. Still Volte not working on 2nd Sim on 3 different Kenzos.
@JustMeErazem Please include in your post that VoLTE is indeed buggy.
Click to expand...
Click to collapse
Idk bro y that happening to u. Flash miui EU rom n thn the nos rom. Mayb that should work.... Bcuz I had done that for the 1st time whn my volte wasn't working at any cost. Best of luck.

smjhh said:
how to install via dualboot patcher as secondary rom?
Click to expand...
Click to collapse
I don't think dual boot patcher supports oreo roms. Try asking on their thread to see if it does.

Google HDR camera 5 or 5.1 work with this ROM??

sagar13190 said:
Google HDR camera 5 or 5.1 work with this ROM??
Click to expand...
Click to collapse
Read op!

I tried google HDR camera v5 n v5.1 on lineage Oreo, MAOSP Oreo nitrogen Oreo ROM bt its not working...bt in ROM based on nogut 7.1.2 its work great

sagar13190 said:
I tried google HDR camera v5 n v5.1 on lineage Oreo, MAOSP Oreo nitrogen Oreo ROM bt its not working...bt in ROM based on nogut 7.1.2 its work great
Click to expand...
Click to collapse
It works for many users. Did you flash my zip or install an apk?

Sim card detection issue
Sometimes nitrogen os Oreo does not detect sim cards after reboot so I changed ROM and installed aosp extended. I know that Xyyx has already mentioned this as bug. Due to this bug it is not daily driver. Hope xyyx will fix this as soon as possible. If you have solution, please share it.

dhavalmehta said:
Sometimes nitrogen os Oreo does not detect sim cards after reboot so I changed ROM and installed aosp extended. I know that Xyyx has already mentioned this as bug. Due to this bug it is not daily driver. Hope xyyx will fix this as soon as possible. If you have solution, please share it.
Click to expand...
Click to collapse
Dude, it's really not a big problem, it detects it like 95% of the time. Just reboot and you're done. Or wait about 2 min and it should detect it. You could also just remove the sim and reinsert it. But since the latest few updates for me it gets detected 100% of the time. So update to 28/10/2017 build and you should be fine.

@JustMeErazem You're giving flase info. to others saying that VoLTE works on both sim. Actually, it works only on first sim. Tried, tested on 3 different Kenzo's. Clean flashed.
Conclusion: VoLTE doesn't work on 2nd sim.

OPEN BETA for 17.1 UNOFFICIAL LineageOS T550 rom

BEFORE YOU decide to try this rom, please read all of post 1 and 2.
The UNOFFICIAL LineageOS 17.1 T550 ROM
BACKUP YOUR DATA AND OLD ROM BEFORE trying my rom.
Let me be clear, I have the SM-P550, NOT the SM-T550.
So I built a SM-P550 rom which is almost the same as the SM-T550 except the "P" stands for Pen.
I believe my P550 rom with minor modifications will work on the T550, but I have no T550 to test it on. I believe it will work because I have used virsys T550 rom on my P550 and it works, but the X-axis touch is inverted.
So I built SM-P550 with code to fix the X-axis touch inverted problem and it's one of line code. If I leave that one line of code out, then the X-axis will be correct for the T550. I have tested my 17.1 T550 rom on my P550 and it works, but again with the X-axis inverted. Just remember I don't have a T550 to test it on so you may run into bootloops, stuck at boot animation, etc.
If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT attempt this ROM. You must know how to use these tools to revert back to your old rom. I'm not a Windows user so do not expect any help from me. My main OS is Lubuntu 20.04 LTS and all my roms are built on this platform.
If you are new to flashing custom roms, do NOT attempt this.
If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.
Again, the T550 rom that I built does boot and function on my P550, but I have no T550 to verify.
BACKUP YOUR DATA AND OLD ROM BEFORE trying my rom.
The rom has the latest monthly 2021 security patches.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. camera
8. touchscreen X-axis works properly
9. Google play store - use pico apps
10. flip flap smart cover
11. audio over bluetooth
What doesn't work
1. LineageOS FM Radio app does not work. The P550 and T550 don't have the LTE chipset for it to work.
2. The stock Jelly browser crashes a lot. Use a different browser. There's lots of better options that are more stable and reliable than the built in Jelly browser.
3. Home screen text may look fuzzy.
Text on home screen looks funny/fuzzy. This only seems to affect the home screen and nowhere else. I have seen the same problem on the SM-T350, SM-T560NU, SM-P550 and Nexus 7 2013.
Problem is with stock trebuchet launcher and/or its fonts. I tried rootless pixel launcher from fdroid as a quick and simple test and see no problems with home screen text. Rootless pixel uses a different font though. A future LineageOS update could resolve the problem?

FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.
Q1) Why are you releasing a ROM for a tablet that you do not own?
A1) I don't own the SM-T550, but have the SM-P550. I also build roms for the SM-T350 and SM-T560NU. All these platforms use the same msm8916 code base. As such, all my work from the SM-T350, SM-T560NU and SM-P550 could possibly benefit SM-T550 users. For one P550 owner, there are probably twenty T550 owners.
Q2) What if my app, xyz, doesn't work?
A2) I won't answer questions regarding why your app doesn't work. If your app, whatever it is, doesn't work, then go back to your old rom. It's difficult enough building and maintaining these roms. Remember, I'm an unpaid volunteer making a rom for free for your benefit, not mine as I don't even have the T550.
Q3) Your rom is laggy and buggy.
A3) If you find the above, then go back to your old rom. There's only so much software can do on a 2015 budget level tablet. Remember a budget tablet will have the slower SoC/CPU and less DRAM than a top of the line model. Your tablet will also run slower when you use gapps (google apps). You can run a lot of software without using gapps. Research newpipe, microg, youtube vanced, aurora store etc.
Q4) What TWRP should I use?
A4) Use 3.4.0.0. Get it at
Download TWRP for gt510wifi
Download TWRP Open Recovery for gt510wifi
dl.twrp.me
Q5) Why should I use this rom?
A5) You don't. I only offer it because I have built the SM-P550 and it was an easy change to make a SM-T550 rom. If you don't like this rom, then don't use it. Yes, it's that simple.
Q6) Can you build SM-T555 (LTE) or a crDroid version of the SM-T550?
A6) No. All the source code is open source and my changes are in the repo diff file. You can use these two with the roomservice.xml to build your own rom.
Q7) Will you offer monthly updates with security patches?
A7) That all depends on if I continue to have high speed Internet and on the reaction of the posts in this thread. If people are going to complain, then I have NO incentive to make an update. Remember, I don't have the T550 so I get zero benefit from making this rom for myself.
Q8) Can you help me? I'm a newbie. Can you provide step by step instructions?
A8) There are lots of tutorials, videos, etc on how to flash roms. Do your own research.
Q9) Can I report a bug with respect to the rom?
A9) Yes, but you need to supply a) how to recreate it b) a logcat c) a github commit showing how it was fixed. Even then, if I don't have the means to recreate it, I won't be working on it.
Q10) Can I build this rom? Where are the source and kernel source files?
A10) Yes. The kernel source files are at
Samsung MSM8916 Devices
Samsung MSM8916 Devices has 68 repositories available. Follow their code on GitHub.
github.com
aala27 - Repositories
aala27 has 7 repositories available. Follow their code on GitHub.
github.com
Q11) Okay, I understand the consequences and that this is beta rom and willing to take the risks outlined, now where can I find the rom?
A11) Downloads are at
retiredtab - Browse /SM-T550/17.1 at SourceForge.net
sourceforge.net

Hi rretiredtab
I have a T550 with the latest virsys image 16.0 from March 2020.
It is more or less stable, but I think, it will be always slowlier. Empty dalvic and cache does not help.
I'm ready for a new challenge. If I can help you, please let me know.
Best regards
Schaagi

Hi retiredtab,
I ready to try this rom

Schaagi said:
I have a T550 with the latest virsys image 16.0 from March 2020. It is more or less stable, but I think, it will be always slowlier. Empty dalvic and cache does not help.
Click to expand...
Click to collapse
My 16.0 rom for the SM-P550 is based on virsys repos. However, I was only able to make 2 builds using his repos before a LineageOS update in Sept 2020 caused it to get stuck at the boot animation.
Then I tried virsys 17.1 repo and it too gets stuck at the boot animation. I know virsys built crDroid Android 10 rom and uploaded it sometime June 2020, but his Android 10 repos on github are dated March 2020 so whatever patches he did to get crDroid working isn't on github.
I don't know if 17.1 will be faster than 16.0. The 17.1 builds, by default, use an overclocked CPU and GPU in the kernel code. However, I don't know if you will see any real world differences in performance from the overclocking.
In addition, I don't know if virsys March 16.0 March 2020 is overclocked or not. You can always download an utility like CPUinfo at
CPU Info | F-Droid - Free and Open Source Android App Repository
Information about device hardware and software
f-droid.org
to see if the CPU is running at 1.2Ghz or 1.6Ghz (overclocked).

@Schaagi and @Simone101, please let me know if the T550 ROM boots or not after you have installed it. I'm pretty sure it will, but would like to know ASAP.
Then, afterwards, you can let me know how it works over a 24 to 48 hour period. I'm interested to see if it randomly reboots or crashes.
As for speed and performance, just remember it's a 5 year old entry level tablet and unless LineageOS is written in assembler language, it will never match a top of the line model tablet.
Thank you.

I've installed your image as clean-install. It boots !!!
At the beginning of the setup process there is a bluetooth error, that repeats after every new boot.
First installation without opengapps -ok
Second one with opengapps - ok
Restore Data from previous image - ok
As next I will try to install magisk.
Wow, good job. I will check it for the next days and give feedback later.
Best regards
Schaagi

Schaagi said:
At the beginning of the setup process there is a bluetooth error, that repeats after every new boot.
Click to expand...
Click to collapse
Can you provide a screenshot of the error please?
I haven't seen the bluetooth error before on my SM-P550 and I reboot my SM-P550 a lot because I'm always flashing new builds.
I don't use bluetooth at all, but when I turn it on, I can see my neighbor's 65 inch TV. Also, I can pair two tablets together using bluetooth.

Meanwhile I have installed Magisk 21.1 and it works too
I've attached 2 screenshots from Bluetooth error.

Schaagi said:
I've attached 2 screenshots from Bluetooth error.
Click to expand...
Click to collapse
The above is why we need BETA testers.
Okay, I ran into the bluetooth error problem on the SM-T350 and it was due to a missing bluetooth library.
In my SM-T350, I have
Code:
# RT 17.1 copy bluetooth file otherwise bluetooth keeps crashing
PRODUCT_COPY_FILES += \
vendor/samsung/msm8916-common/proprietary/vendor/lib/libbtnv.so:$(TARGET_COPY_OUT_VENDOR)/lib/libbtnv.so
Those 3 lines of code are not in the T550 build. It's easy to add and I can create another BETA build. It's building right now and probably be done in the next 2 hours or so.
If you want to add the libbtnv.so file yourself, here are the instructions
1) Boot into TWRP 3.4.0.0.
2) Click Mount. Choose System.
3) On your computer, goto
proprietary_vendor_samsung/libbtnv.so at lineage-17.1 · Galaxy-MSM8916/proprietary_vendor_samsung
proprietary_vendor_samsung. Contribute to Galaxy-MSM8916/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
4) Click download.
5) Goto the directory where the libbtnv.so is saved.
6) Plug in microusb cable to tablet.
7) Then use adb to push the file using the command
Code:
$ adb push libbtnv.so /system/vendor/lib/libbtnv.so
libbtnv.so: 1 file pushed, 0 skipped. 48.5 MB/s (16128 bytes in 0.000s)
8) Check to make sure file was pushed.
Code:
$ adb shell ls -al /system/vendor/lib/libbtnv.so
-rw-r--r-- 1 root root 16128 Dec 19 21:24 /system/vendor/lib/libbtnv.so
9) Reboot into system and bluetooth error should be gone.
OR
Just wait until my next build is done to get rid of the bluetooth errors. I'm confident the error is due to the missing bluetooth library file.
I will send you and Simone101 a PM when the new build is done.

The new BETA build is finished, but having problems uploading to host server right now. I will try again in a couple of hours to upload. I will PM when I get it uploaded.

I've installed the new image and bluetooth error has gone.But I'didn't test the functionality of bluetooth at the moment.
Will check more in detail and inform you about the results. Thank you.
Regards
Schaagi

@retiredtab
I want to test your ROM , where I can download it.
At the moment I use the cdroid 10 by virsys
My CPU runs at performance mode with 1600 MHz.

bierma32 said:
At the moment I use the cdroid 10 by virsys
Click to expand...
Click to collapse
Over at the T550 thread, it seems that some people who are using crDroid 10 are reporting
1) camera not working
2) brightness not working
3) browser crash (that's you)
#1 and #2 work on my build. As for #3, if you are using the built in Jelly browser, I have noticed that if you open more than 4 windows, it crashes sometimes.
While not perfect, I found that smartcookieweb app works better than Jelly.
Releases · CookieJarApps/SmartCookieWeb
A secure, open source web browser for Android. Contribute to CookieJarApps/SmartCookieWeb development by creating an account on GitHub.
github.com
The Brave browser seems to work the most reliable. You can use Aurora store to download it from play store or try downloading brave apk somewhere.
On a daily basis, I use smartcookieweb as it has built in adblocker and suits my daily browsing needs.

@retiredtab
Both cameras works on Cdroid for me.
Yes, browsers crashes after some times, I use opera mini.

Bluetooth works for, tested sending and recive images.
GPS is not working, will try it again next time.
Magisk 21 works.
WiFi works.

Hi retiredtab,
Nice to see that anybody has try to give us an update for this fossile
Please let me knoe where can I download and test your build.
regards,
L

bierma32 said:
GPS is not working
Click to expand...
Click to collapse
No need to retest GPS. I already know what's wrong. This is the same problem I had with the T350.
The T550 build is missing the commands
Code:
# GPS
PRODUCT_COPY_FILES += \
vendor/samsung/msm8916-common/proprietary/lib/libloc_api_v02.so:$(TARGET_COPY_OUT_VENDOR)/lib/libloc_api_v02.so \
vendor/samsung/msm8916-common/proprietary/lib/libloc_ds_api.so:$(TARGET_COPY_OUT_VENDOR)/lib/libloc_ds_api.so
Now I did test the T550 build on my P550, but it looks like when I made the final image, some of my scripts or commits didn't get copied, like the above, over when I initially changed some P550 naming/parameters to T550.
Some background. I had only 1 hard drive for the P550 and T550 code. I did test bluetooth and gps on my P550 and both work.
After I tested everything, I then later split the P550 onto one hard drive and the T550 to another so I wouldn't get confused when compiling and making changes. I suspect now that I forgot to copy over my T350 script to fix gps and bluetooth onto the new T550 drive.
To fix gps without having to re-download another 440MB file,
1) Boot into TWRP 3.4.0.0.
2) Click Mount. Choose System.
3) On your computer, goto
proprietary_vendor_samsung/libloc_ds_api.so at lineage-17.1 · Galaxy-MSM8916/proprietary_vendor_samsung
proprietary_vendor_samsung. Contribute to Galaxy-MSM8916/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
and
proprietary_vendor_samsung/libloc_api_v02.so at lineage-17.1 · Galaxy-MSM8916/proprietary_vendor_samsung
proprietary_vendor_samsung. Contribute to Galaxy-MSM8916/proprietary_vendor_samsung development by creating an account on GitHub.
github.com
4) Download both files above (libloc_ds_api.so and libloc_api_v02.so).
5) Goto the directory where both are saved.
6) Plug in microusb cable to tablet.
7) Then use adb to push the file using the command
Code:
$adb push libloc_api_v02.so /system/vendor/lib/libloc_api_v02.so
libloc_api_v02.so: 1 file pushed, 0 skipped. 7.6 MB/s (116316 bytes in 0.015s)
$adb push libloc_ds_api.so /system/vendor/lib/libloc_ds_api.so
libloc_ds_api.so: 1 file pushed, 0 skipped. 29.5 MB/s (26132 bytes in 0.001s)
8) Check that both files exist.
$adb shell ls -al /system/vendor/lib/libloc_api_v02.so
-rw-r--r-- 1 root root 116316 Dec 7 2020 /system/vendor/lib/libloc_api_v02.so
$adb shell ls -al /system/vendor/lib/libloc_ds_api.so
-rw-r--r-- 1 root root 26132 Dec 7 2020 /system/vendor/lib/libloc_ds_api.so
9) Reboot into system and GPS should be work now.
I'm making a new BETA image again and before I upload it, I will retest everything again on my P550. It's a bit awkard as everything is mapped backwards on the X-axis.
I'll post here when it's up.

Well it was around 1AM in the morning when I saw the gps not working post and now it's 2:13AM. I'm just waiting for the last 5 minutes of my new build, but the host server is having major problems right now.
So I'm going to sleep and will try uploading the new image tomorrow after I retest everything with the P550 running the T550 image. Everything will be mapped backwards for me on the X-axis while testing.
Dec 21 BETA build up. Androidfilehost is having major problems so I put it up on sourceforge.net. No way I could go to sleep with this hanging over my head. It's 2:30AM. Now I'm going to sleep in tomorrow.
Dec 21 build has gps fix.

Ooh i want really like to test!

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

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

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

ROM Screenshots
Attached below. Others are available here.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

ROM Screenshots
Attached below.

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

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

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

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

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

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

how is the battry life anyone?

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

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

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

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

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

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

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

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

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

Database Users

welcome