[DISCONTINUED][ROM][PAYTON]LineageOS 18.1 - Moto X4 ROMs, Kernels, Recoveries, & Other Develop

[DISCONTINUED][ROM][PAYTON]LineageOS 18.1 - Moto X4 ROMs, Kernels, Recoveries, & Other Develop

Important extra links
Payton Stock firmware:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Copy partitions link for download can be found on the LineageOS Wiki install instructions for Payton page here:
Install LineageOS on payton | LineageOS Wiki
wiki.lineageos.org

Heyyo, a new test build is up! The link can be found on the first post under the unofficial test builds link. lineage-18.1-20210119-UNOFFICIAL-payton contains some audio tweaks for echo-reference, speaker volume boost as well, so please test all voice call and audio recording functions.

ThE_MarD said:
Heyyo, a new test build is up! The link can be found on the first post under the unofficial test builds link. lineage-18.1-20210119-UNOFFICIAL-payton contains some audio tweaks for echo-reference, speaker volume boost as well, so please test all voice call and audio recording functions.
Click to expand...
Click to collapse
For wifi display we can update wfd from caf
Seems works on other roms

Heyyo @dhinesh_cool , the CAF blobs you are referring to are from Board Support Packages, which do not have any transferrable rights as it isn't publicly available like a stock ROM for a device.
LineageOS does not allow blobs from BSP because of that, to avoid any potential legal issues.
So hopefully another solution presents itself... Or if we're lucky? A better solution replaces Miracast

ThE_MarD said:
Heyyo @dhinesh_cool , the CAF blobs you are referring to are from Board Support Packages, which do not have any transferrable rights as it isn't publicly available like a stock ROM for a device.
LineageOS does not allow blobs from BSP because of that, to avoid any potential legal issues.
So hopefully another solution presents itself... Or if we're lucky? A better solution replaces Miracast
Click to expand...
Click to collapse
Ahh that bad
Another question is offline charging works?

Offline charging works, but the animation is broken.
Edit: Is the selinux permessive?

@dhinesh_cool oh snap, offline charging animation is broken lol... We will have to check into that then.
@Sujanth the test builds I released are selinux enforcing. I did just try testing with permissive and it still failed, so the issue lies elsewhere... I'll try some stuff and see what we need to do to solve it

Ok. I played cod and scwitch to telelgram. Then I switch back to cod. But the game loads from the beginning. In other rom it doesn't happen. I think the ram management could be impoved.

Heyyo, another test build is going up! The upload should be done within 30 minutes of this post and link to test builds are in the first post. lineage-18.1-20210202-UNOFFICIAL-payton contains fixes for the offline charging animation and for WiFi hotspot with WPA2 (it isn't merged yet on LineageOS, but hopefully it does before we go official on 18.1).
There is also some echo-reference changes so if someone could please test it with VoIP apps and see if there's still echo or not

Audio from front facing video is working?

ThE_MarD said:
Heyyo, another test build is going up! The upload should be done within 30 minutes of this post and link to test builds are in the first post. lineage-18.1-20210202-UNOFFICIAL-payton contains fixes for the offline charging animation and for WiFi hotspot with WPA2 (it isn't merged yet on LineageOS, but hopefully it does before we go official on 18.1).
There is also some echo-reference changes so if someone could please test it with VoIP apps and see if there's still echo or not
Click to expand...
Click to collapse
Offline charging is working now. Thanks.I am testing the other fixes and write then back.
Edit: Hotspot with WPA2 also works with 2,4 GHz band. But with 5.0gHz band i can't find the hotspot. Need any logs?
I did also a whatsapp call, no echo or mic problems.
But volume of the speaker is low. Can you fix it?
And radio FM doesn't work.
When I want to call somebody, the telephone screen is not coming, but you hear the call tone.

How to upgrade to this ROM from Lineage 17.1? Thanks.

Heyyo @derienardani , yes that was fixed on 18.1 like it was on 17.1.
@Sujanth , WiFi Hotspot WPA2 on 5GHz works fine for me, albeit there's more changes coming to it so I'm unsure yet what will be the final form of it... I'll post a new build when it changes again.
As for speaker volume? It was increased from 32 to 34 and no plans to go higher as some users said at 36 they get distortion.
FM Radio is a known bug that we are still looking into.
For the telephone bug? Please ensure you have a default phone app selected
@artu72 the upgrade instructions for 18.1 are the same as 17.1 except for GApps MindTheGapps is the recommended one to use either addon-v2 or v3 is fine.
MindTheGapps - Google Drive

Heyyo, a new test build is going up! As always it is in the first post and is uploading meow so it'll be about 30 minutes. lineage-18.1-20210211-UNOFFICIAL-payton contains some perf fixes so that cpufreq also properly scales up and down.

ThE_MarD said:
Heyyo @derienardani , yes that was fixed on 18.1 like it was on 17.1.
@Sujanth , WiFi Hotspot WPA2 on 5GHz works fine for me, albeit there's more changes coming to it so I'm unsure yet what will be the final form of it... I'll post a new build when it changes again.
As for speaker volume? It was increased from 32 to 34 and no plans to go higher as some users said at 36 they get distortion.
FM Radio is a known bug that we are still looking into.
For the telephone bug? Please ensure you have a default phone app selected
@artu72 the upgrade instructions for 18.1 are the same as 17.1 except for GApps MindTheGapps is the recommended one to use either addon-v2 or v3 is fine.
MindTheGapps - Google Drive
Click to expand...
Click to collapse
I haven't installed any other phone apps. So i don't think I need to select it. Same bug also present in corvus a11.

Hi, first time using Lineage OS here. After sideloading LineageOS, i am just not able to install Gapps. Tried using MindtheGapps 11, tried sideloading, flashing, nothing happened. Either the phone starts to bootloop or it boots to recovery or it boots to Lineage OS without any google apps. Can someone please tell me where i am going wrong?
Edit: I realised i was flashing the wrong GApps, so i tried flashing ARM64 Android 10 nano pack. The screen gets stuck at the LOS boot logo before booting back to TWRP.
SOS

Heyyo @warhead1721972 , please ensure you are following the instructions. After flashing LineageOS ROM, you must reboot to recovery and then flash GApps.
A/B devices are different than traditional A-only devices as the ROM is always flashed to the inactive slot (IE, if A is active, the ROM will be flashed to B) so after the ROM flashes successfully it tells the bootloader that next reboot to switch slots. The reboot to recovery then switches to that slot (in our example, it switches to B) so that we can flash GApps on top of the newly flashed ROM.
Installing updates via the LineageOS Updater does use addon.d scripts to keep the installed GApps, but any manual flashing of ROM (either first time or manually upgrading) requires manually rebooting to recovery and flashing GApps as it does not use addon.d scripts.

ThE_MarD said:
Heyyo @warhead1721972 , please ensure you are following the instructions. After flashing LineageOS ROM, you must reboot to recovery and then flash GApps.
A/B devices are different than traditional A-only devices as the ROM is always flashed to the inactive slot (IE, if A is active, the ROM will be flashed to B) so after the ROM flashes successfully it tells the bootloader that next reboot to switch slots. The reboot to recovery then switches to that slot (in our example, it switches to B) so that we can flash GApps on top of the newly flashed ROM.
Installing updates via the LineageOS Updater does use addon.d scripts to keep the installed GApps, but any manual flashing of ROM (either first time or manually upgrading) requires manually rebooting to recovery and flashing GApps as it does not use addon.d scripts.
Click to expand...
Click to collapse
First i sideload the rom zip in slot A along with TWRP and then i reboot to the recovery to set the current slot to B and then flash GApps. On flashing it, there are no errors, but on booting up the system for the first time, i get redirected to TWRP. Is something wrong with my phone?
Till now i have been using ViperOS for quite some time, until i wanted to try something new. Really wanna give LOS a try.

@warhead1721972 , just to check since you're using TWRP, when you switched ROMs are you wiping Dalvik, cache, data and system?
Also, are you reinstalling TWRP after flashing LOS? Because if you are, you must use the TWRP installer zip and not flash the TWRP image as that kernel isn't compatible with the ROM.

Related

[ROM][OFFICIAL] LineageOS 14.1 for Nexus 9 (flounder)

Reserved
This post is for Nexus 9 (LTE) model.
Important Info
The newest lineage 14.1 flounder_lte (LTE) builds rely on proprietary vendor and firmware components from the N4F27P (October 2017) monthly update from google. This means your device needs to have the vendor and bootloader img from that update. They can be extracted from the factory image on google's site here. Or you can use the ones linked below that I already extracted:
* vendor-flounder_lte-n4f27p.img
* bootloader-flounder_lte-3.50.0.0143.img
The vendor img is flashable with twrp or fastboot, but for the bootloader img use fastboot.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS: https://download.lineageos.org/flounder_lte
LineageOS servers no longer make 14.1 builds for any devices. You can use my builds here. My older builds are here.
Google apps: http://opengapps.org/?arch=arm64&api=7.1&variant=nano (Use arm64 / 7.1)
su addon zip (for root): Install zip / Removal zip
NOTE#1: After su addon install, root is disabled by default. You can enable it in developer options.
NOTE#2: My unofficial builds do not force encrypt.
Weather Provider Addon (Optional)
For those that like the lineage cLock widget, here's the OpenWeather apk you need to get weather info.
https://mirrorbits.lineageos.org/WeatherProviders/OpenWeatherMapWeatherProvider.apk
Note: You'll need an api key from OpenWeather.
Stats
https://stats.lineageos.org/
Credits
Many thanks to the LineageOS team and all the contributors out there in the community :good:
Contributors
Hashbang173, razorloves
Source Code:
Main device tree: https://www.github.com/LineageOS/android_device_htc_flounder_lte/tree/cm-14.1
Inherited device tree: https://www.github.com/LineageOS/android_device_htc_flounder/tree/cm-14.1
Kernel tree: https://www.github.com/LineageOS/android_kernel_htc_flounder/tree/cm-14.1
Vendor tree: https://github.com/TheMuppets/proprietary_vendor_htc/tree/cm-14.1
Android version: 7.1.2 Nougat
Kernel version: Linux 3.10.103
Status: Nightly

Wooooh! It's here

Can Nexus9 (lte) use this rom? If flash this rom only can not use lte,i can accept it.

Yeah! This is great news!
Will definitely flash this rom on my laggy N9

Can I dirty flash from the unofficial builds or should I do a full wipe?

Will it work on the LTE version? I don't mind if LTE does not work as long as I can try out the ROM without getting boot loops.

hextence said:
Will it work on the LTE version? I don't mind if LTE does not work as long as I can try out the ROM without getting boot loops.
Click to expand...
Click to collapse
I think so!

LTE version?
For people who need LTE

perfec

Is the Nexus 9 LTE going to have official support?
Sent from my iPhone using Tapatalk

Thank you very much! I hope it is less laggy than the stock firmware.

vendor image is critical at time of OS installation
Hi there.
First of all, thanks so much for the official N9 build for Lineage. Really appreciate it.
I wanted to describe my experience this morning. I should start by saying that I am *not* a hacker, just an enthusiastic user. I can follow instructions, and have been using non-stock ROMs since Cyanogen 7.
I was upgrading from the most recent version of Cyanogen. Before I started, I upgraded to the latest TWRP. Then when booting into recovery, found that my decryption passphrase didn't work. I downgraded version by version until twrp-3.0.2-0-flounder.img which is apparently the latest that worked. After installing Lineage OS, I upgraded to the newest TWRP again.
More importantly, I wanted to point out that by following the instructions on the Lineage OS wiki for the Nexus 9, I almost got to the point of thinking I had bricked my device.
The main reason is that the instructions don't mention the Vendor image issue at all: https://wiki.lineageos.org/devices/flounder/install
After wiping, installing Lineage OS and GApps pico, I rebooted. When it got to the decryption passphrase, I got the pop-up warning about the Vendor image being mismatched. No problem, I thought, as I've seen that before on Cyanogen installs. I put in my decryption passphrase. The screen remained unchanged for a couple of minutes, then I got something I'd never seen before. A page notifying me that my passphrase was correct, but the system was corrupt, and an option to fix it (no other option was available except to force power-off). So I took that option and it rebooted into TWRP. It boots into recovery and apparently runs a script and reboots the system again. But the same issue occurred again, nothing was fixed.
No problem, I thought, I'll just power-off, boot into the bootloader, enter recovery, and try again. Except that after installing Lineage, I found that volume-down+power button no longer started the bootloader!!! I tried many times, but the best I got was the device booting into the system and getting the same problem where it said the system is corrupt. It was at this point that I thought I had bricked the device - can't boot into system, can't get to the bootloader, so can't get to the recovery.
After many attempts, I tried one last thing:
Boot into system
On the corruption notification screen, I pressed the button to "fix" the system corruption
when the device rebooted into Recovery to run the script, instead of entering my passphrase, I hit cancel. This cancelled the script process but left me in recovery. I then selected reboot -> bootloader. Success!!
I was then able to connect the device to my laptop and copy the Vendor image I had extracted from the official Google system image using
Code:
fastboot flash vendor vendor.img
I then rebooted, and everything worked fine.
So it seems that in this instance, it may be critical to install the Vendor image before the first reboot. In earlier versions of Cyanogen when I had a vendor image mismatch it never prevented the device from booting and I was able to update it later on.
In which case, whoever has access to the wiki on the Lineage website - could you add those instructions in?

Just to add - I now seem to have bricked the device. Everything was working fine. I rooted the device using the supplied zip. It booted up fine. Now it won't reboot. It gets to the decryption passphrase field - verifies the password, continues to boot, and never finishes.
I can't get into the bootloader. Volume down+power doesn't work. Is there another way to do this?

Was using stock android on my Nexus 9. Already had root with the latest TWRP recovery installed. Did not run into any issues during the install(forgot to flash the Gapp at first, but could do it later in recovery, again no issues)
This is the first time I am using a Custom ROM. Got some questions .
1. I have the default apps for the lineage OS along with the same Gapps, How to remove the default lineage OS apps?
4. If anyone can share the advantages of the Nightly over custom ROM , it'll be great.
Other than these, no other major issues so far. will update the thread with the user experience

For anyone with LTE model please test this build. Let me know if there's any issues with lte or anything.
https://www.androidfilehost.com/?fid=889764386195906667
Here's the N4F27E vendor img for the LTE model, if you need it.
vendor-volantisg-n4f27e.img
thanks
No more testing needed. Results were good. Nightlies started for LTE model.

yhvo2gt9 said:
Just to add - I now seem to have bricked the device. Everything was working fine. I rooted the device using the supplied zip. It booted up fine. Now it won't reboot. It gets to the decryption passphrase field - verifies the password, continues to boot, and never finishes.
I can't get into the bootloader. Volume down+power doesn't work. Is there another way to do this?
Click to expand...
Click to collapse
Decryption passphrase in TWRP? Or Lineage?
---------- Post added at 04:51 PM ---------- Previous post was at 04:49 PM ----------
Just to let you all know, I got Lineage up and running, restored from my gmail account. I had stuck with 6.0.1 stock, 7 never cooperated, it was still getting laggy and what not. I will post more details about the install in a bit, but I just wanted to let any curious parties know this build seems to be working OK

Is the poor volume fixed in the official build or do we still need to flash a custom kernel to fix it?

I just flashed a minute ago. I've been waiting for this to be released. I switched over to Lineage on my OnePlus when it first came out. The nexus has been way too laggy on the latest stock releases. I hope this helps. I received a vendor image mismatch error on boot up but so far no issues. I'm going to flash gapps and will report back later. Thanks for working on this!!

The LTE one appears to be working fine in my tablet. Thank you
Sent from my iPhone using Tapatalk

[ROM] [TREBLE] [11.0] [Official] AICP 16.1 (Pro3 aka zl1, zl0, X727,X720,X722)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS), we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q-R with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.
If there are any bugs we will sort them out if it concerns our codebase. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
DU team
Resurrection Remix team
AOSiP team
Community
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 16.1
Download link: https://dwnld.aicp-rom.com/
Please note that official builds will be deleted from our servers every month due to maintenance services.
Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.
Test builds:
https://evensharksneedwater.com/aicp/mosimchah/zl1/11/
Mirror: https://drive.google.com/drive/folders/14XFfejcvr3tA4Eg8x-uYgMu2ztl-lZQ7?usp=sharing
20s firmware https://androidfilehost.com/?w=files&flid=165490
If you're dirty flashing, you might need to delete the locksettings.db file in /data/system
TWRP:
[RECOVERY][OFFICIAL] TWRP for the leeco le pro3 (x727,x720,x722,zl1,zl0)
#include /* * 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...
forum.xda-developers.com
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
We recommend MindTheGapps as it has been thoroughly tested and it works well with the ROM, some other minimal GApps packages still have issues, however feel free to try other GApps if you want to, just try MindTheGapps if you have any GApps related issues
MindTheGapps: https://androidfilehost.com/?w=files&flid=322935
Mirror: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Does this ROM include GApps or do I have to flash them separately?
A. No, we do not include prebuilt GApps, because of possible licensing issues with Google Software and because some users do not want GApps preinstalled as they want to use alternative services like MicroG or just prefer flashing a GApps "flavor" of their liking.
Q. Does this ROM use the camera or gallery app from stock?
A. It depends on the device. In most cases these apps include proprietary libs/code and cannot be included in the device trees on Github or we risk having the ROM banned from Github. In this case, we might try to make them installable (separate from the ROM zip), or we might provide a version of these apps with the ROM that doesn't include any proprietary libs. It's also sometimes the case that these apps are simply not included because we didn't feel the need to do so for the device in question.
Q. Does this ROM have Extended/Scrolling screenshot?
A. No, extended screenshot was implemented using an app extracted and modified from manufacturer firmware/system images and is proprietary as well. It led to the closing of many ROM's sources on GitHub.
Q. Does this ROM have FaceUnlock?
A. No, FaceUnlock was also an app extracted and modified from some manufacturers. Even Google removed the Trusted Face (FaceUnlock) feature for security reasons on Android 9.0/10.x. Adding the modified feature did the same to ROM sources as described above.
Q. Can you add (insert favorite weather provider)?
A. No, we cannot add more weather providers as the implementations change and we (the ROM) now have to pay for most services, and that is not cheap, so we decided to use the best free service that we could find, the only way to add your own is for users to apply for their own API key to use their preferred service.
Q. Does this ROM have private official builds with the above proprietary libs included?
A. No, we believe in open source software, this way users know what's in the build and can replicate it themselves, all official builds are built on our build servers using the public sources from github and no one can (or would) add their own private sources to the build.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is the usual behavior on flashing a new official build by (or using) the build-in updater service.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache, and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to lose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to lose root. Now swipe to flash and reboot afterward.
Using the ROM:
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. Do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get, and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section on the AICP Extras main page.
The ROM should contain everything you need to enjoy Android R. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM zip file.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, and Data (you might need to format the data partition!).
4. Flash the ROM zip file.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work)
6. Reboot and set up your device, enable developer settings and in them, OEM unlock/Advanced reboot/USB tethering.
7. Reboot back into TWRP recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.4 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
TWRP recovery is needed to be able to flash using the built-in OTA app.
Please make sure that you are on the latest TWRP recovery, keep in mind that this could also be an unofficial version!
On encrypted devices, you will have to enter your PIN/password in TWRP before the process starts.
If you want to contribute to AICP, or if you want to see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
GitHub - AICP/kernel_leeco_msm8996 at r11.1
Contribute to AICP/kernel_leeco_msm8996 development by creating an account on GitHub.
github.com
Device tree source:
GitHub - AICP/device_leeco_zl1 at r11.1
Contribute to AICP/device_leeco_zl1 development by creating an account on GitHub.
github.com
GitHub - AICP/device_leeco_msm8996-common
Contribute to AICP/device_leeco_msm8996-common development by creating an account on GitHub.
github.com
Vendor source:
Follow this guide if you want to extract the vendor blobs: https://wiki.lineageos.org/extracting_blobs_from_zips.html
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
andr68rus,
infrag,
darkobas,
jrior001,
codeworkx,
villarleg,
ThE_MarD,
Lucchetto00,
mosimchah
Information:[/U[
ROM OS Version: 11.x
Kernel: Linux 3.18.140
ROM {Firmware|Vendor} required: 20s or newer
Status: STABLE
Release Date: 12-22-2020
You want to see a "normal" night at the "DEV office", click here!!

reserved

This is fabulous! Possible to dirty flash from 15?

New test build,
Changes:
1. Added back the button lights settings
2. Fully fixed IR, credit to @ThE_MarD
3. The rom should now be able to boot without gapps installed (still fine with gapps of course), credit to @ThE_MarD
Download:
https://evensharksneedwater.com/aicp/mosimchah/zl1/11/aicp_zl1_r-16.1-EXPERIMENTAL-20201224.zip
md5:
https://evensharksneedwater.com/aicp/mosimchah/zl1/11/aicp_zl1_r-16.1-EXPERIMENTAL-20201224.zip.md5sum

FedEx UPS said:
This is fabulous! Possible to dirty flash from 15?
Click to expand...
Click to collapse
haven't tried so I can't say for sure, I'd say make a backup in twrp before trying that though

mosimchah said:
haven't tried so I can't say for sure, I'd say make a backup in twrp before trying that though
Click to expand...
Click to collapse
Dirt flashed, so far so good! Thanks for the special Christmas gift and happy holidays!

I've installed this rom in my Zl0 and i noticed a bit of lag, also fingerprint isn't working and proximity sensor on calls. Didnt test notification light. Also in charge battery bar isnt going low just the percentage does. How can i enable my torch while screen is off and press continuously the power button? already assigned the button in the menu. Other than that rom is clear and neat. Thank you

**update my phone was after a qfil recovery and i cant operate fingerprint, proximity, auto rotate and flashlight. So its not of this specific rom related as i tested other roms i used in the past. Has anyone has an idea how to repair ?

Mobile Hotspot not working with security enabled (WPA2-Personal) - only disabled/nonsecure WIFI works. Had to go back to older version (15.0). FYI, tried with the new Lineage pre-release as well and same issue with hotspot.
Noitced - that hotspot shows one device connected for a few seconds then disconnected and get the message that failed to authenticate and will need to retry to enter password again.

The battery icon in the status bar doesn't show the actual battery level always full. Opening "Google Services & preferences" and Digital Wellbeing detail statistics always crash. The last one may or may not related to the GApps. I use FlameGApps as recommended. Haven't thoroughly tested other functions.

Gave this a go with a clean flash. Does the basic gapps not include a camera app? Not seeing it but otherwise working well.

On my phone Camera and Fingerprint didn't work after clean flashing of Android 10 or 11 ROM. You first need to wipe System, Cache, Davlik and Data, and then format Data. After that flash Android 9 (for example LineageOS 16 or AICP 14), and when that ROM boots go back to TWRP, do Factory Reset and then flash Android 10 or 11 ROM and Camera and fingerprint will work.

MasterChief2 said:
On my phone Camera and Fingerprint didn't work after clean flashing of Android 10 or 11 ROM. You first need to wipe System, Cache, Davlik and Data, and then format Data. After that flash Android 9 (for example LineageOS 16 or AICP 14), and when that ROM boots go back to TWRP, do Factory Reset and then flash Android 10 or 11 ROM and Camera and fingerprint will work.
Click to expand...
Click to collapse
Thanks tried this still didn't work. Not sure what to do at this point. Pretty sure I'm on 20S firmware although I'm not seeing where that is in the phone settings.

Have any of u succeeded on installing magisk? I've tried both the latest versions and the 20.3 that says above and the manager does not recognise the root. If I use a magisk remover zip upon the shell it says magisk installation found and proceed normally. But on manager nothing . thanks in advance
Update: the beta 21.2 with the canary version of manager worked like charm

Timmons said:
Thanks tried this still didn't work. Not sure what to do at this point. Pretty sure I'm on 20S firmware although I'm not seeing where that is in the phone settings.
Click to expand...
Click to collapse
Timmons said:
Thanks tried this still didn't work. Not sure what to do at this point. Pretty sure I'm on 20S firmware although I'm not seeing where that is in the phone settings.
Click to expand...
Click to collapse
you didnt do it correctly then, it does work, boot android 9 clean then you can go back to twrp and flash whatever

On x722 I didn't do any of the above. I was on aicp 10 and I just wiped data,system,dalvik,art,and cache, installed the ROM , gapps, booted, installed magisk. I saw some strange battery drains, I installed the latest black screen kernel and everything works like charm.

new twrp builds are out, I am now the official maintainer https://forum.xda-developers.com/t/...leeco-le-pro3-x727-x720-x722-zl1-zl0.4217101/

mosimchah said:
new twrp builds are out, I am now the official maintainer https://forum.xda-developers.com/t/...leeco-le-pro3-x727-x720-x722-zl1-zl0.4217101/
Click to expand...
Click to collapse
Great job. Thanks mosimchah

New build,
Changes:
1. Cleaned up the dependencies for the fingerprint blobs
2. Cleaned up the dependencies for the camera blobs
3. Fixed the hotspot not fully working, credit to @ThE_MarD
4. Added back live display
5. Added back pulse
6. Added optional navbar styles
7. Added some power menu options
8. Added back the Phonograph music player from Omni
9. Improved the "about device" section in settings
10. Added an option to switch between Celsius and freedom units for the lock screen charging info
11. Gesture nav additions and improvements
12. Lots of misc fixes, additions, and improvements
Full changelog:
dogbin - livedisplay-r
==================== 01-16-2021 ==================== * frameworks/base 41a4baab5c48 fwb:co
del.dog
Download:
https://evensharksneedwater.com/aicp/mosimchah/zl1/11/aicp_zl1_r-16.1-EXPERIMENTAL-20210116.zip
md5:
https://evensharksneedwater.com/aicp/mosimchah/zl1/11/aicp_zl1_r-16.1-EXPERIMENTAL-20210116.zip.md5sum

On the new testbuild there is no turning off button, only restart.

[DISCONTINUED][ROM][PAYTON]LineageOS 19.1 (Android 12.1)

Important extra links
Payton Stock firmware:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Copy partitions link for download can be found on the LineageOS Wiki install instructions for Payton page here:
Install LineageOS on payton | LineageOS Wiki
wiki.lineageos.org

Heyyo, a new test build is going up! lineage-19.1-20220416-UNOFFICIAL-payton contains Moto Camera 2 app and fixes for offline charging as well
Release lineage-19.1 lineage-19.1-20220416-UNOFFICIAL-payton - lineageos-for-payton - OSDN
Release lineage-19.1 lineage-19.1-20220416-UNOFFICIAL-payton - lineageos-for-payton #osdn
osdn.net
VERY special thanks to SevenRock for doing the majority of the LOS 19.1 trees for Moto sdm660 and payton

I decided to take the plunge tonight, waste a few hours and try out the 20220416 test build. So far so good, though I'll grant you I've only had it running for a couple hours. The install going from 18.1 to 19.1 went smooth. I'm not sure if audio will end up a little weak when calling someone. When I did a Voice call from my google number to my phone number, and then played back the message, my voice sounded a bit weak vs the voice mail prompts. I need to try it with a real phone call and see if others think I sound weak.
Apps seem to be running fine so far, though I'm a fairly light user. The only issue I've seen is TWRP 3.5 seems to get stuck in a boot loop when rebooting to recovery from lineageOS 19.1 but didn't when rebooting from TWRP. My new laptop doesn't seem to like fastboot, so I need to try lineage recovery install from another computer and see if that fixes it. I know TWRP isn't officially supporting Android 12 yet, and suspect this isn't an issue with your build. This did prevent me from trying Magisk, so that will need to wait too.
Can't say I'm a fan of the new "Material You" theme. The new quick tiles are annoyingly large. I need to figure out how to get a sound toggle tile to work right. But again, those are general OS issues and nothing to do with the build you did!
I'll see how it fairs over the next couple days and let you know, but so far seems good. Thanks for the build!

I installed this rom but can't get Magisk installed. Anyone know how?

Heyyo guys, for TWRP please try my latest test build
[OFFICIAL&TESTS]TWRP for the Motorola Moto X4 (Payton)
#include /* * 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...
forum.xda-developers.com

I installed the 16 Apr build Sun night using NikGapps 13 Apr stock (excluding Pixel Launcher since I'd had issues with it on the prev build) and the Fi add-on. Other than having to clear storage/cache for Conn Services and Fi, everything has been working really well. Setup was much smoother this time, MotoCam2 is really nice, and also no random reboots like on the 22 Mar build.
When upgrading from the 22 Mar to 16 Apr build though, I got a boot loop and had to clean install. I'd had the same issue in the past back when I used the unofficial 18.1. Is this a known issue? Official 18.1 builds never had this problem. I guess next time I'll first try disabling security unlock.
Btw, is this really 12.1 and not 12.0? The phone settings only indicate '12'. I used the 'S' gapps and not 'SL', fwiw. Thanks!

The 4/16 build has been running fine for me the last few days. I may need to decrypt to get a working recovery it seems. Other than that the couple things that look like they're missing from settings are:
I don't see anywhere to adjust the color palette. It's purely based on wallpaper derived colors. Sounds like stock 12 supports modifying, does lineageOS not? I really don't like having my colors dictated by the wallpaper.
Accesibility/Vibration & Haptic strength -- this menu has no haptic strength control despite the name. It'd be nice if it did. I know this has existed in at least some of the past ROMs, though can't recall if that was Havoc or LineageOS.
Otherwise bluetooth, wifi, calling, messaging all seem good as does interaction.
I also ended up using NikGapps 13 simply because that was what I had good luck with on 18.1.
I'm not sure about the bootloop jeremywh7 saw as I went directly from 18.1 to the 0416 19.1 build with a clean install. If there's another test build and once I get a recovery working, I can try doing a dirty flash for an upgrade. I know on 18.1 I was able to dirty flash w/o a problem.

So far so good but I haven't done extensive testing yet. I got Magisk working.

Nice

Heyyo @jeremywh7, LineageOS 19.1 is Android 12.1 so you must use Android 12.1 (12L) GApps which might be your bootloop issue.
The color palette is indeed picked by the wallpaper which is annoying... It thinks my background of my family should mean my color is a skin-colored pink... oof lol

ThE_MarD said:
The color palette is indeed picked by the wallpaper which is annoying... It thinks my background of my family should mean my color is a skin-colored pink... oof lol
Click to expand...
Click to collapse
Yeah, I'd agree that's not a great choice on it's part! So I take it that for LineageOS 19.1 at least it's expected to have no control of this? I was under the impression that with stock Android 12 you could disable the automated picker and manually choose a color which I don't see in 19.1. If true that sounds like going with a 3rd party tool do do so

@ThE_MarD
Congrats!!! First official Lineage OS 19.1 payton build from the roaster
My question: Is it safe to dirty flash 19.1 as upgrade from an (last) official build of 18.1 (No GApps installed)? Wait for TWRP 3.6.1_11 or latest 3.6.1_9 is working for that?

Heyyo. Exciting times! First official build of LOS 19.1 for payton is up!
@jtnc, tbh no idea as I haven't really checked into the material you stuff lol...
@wkn000 you can upgrade without wiping data, please follow the instructions in the first post.
You can use the latest test build of TWRP or use Lineage Recovery

I did a factory reset and have flashed the first official build of LOS 19.1. I then immediately sideloaded NikGapps-core-arm64-12.1 before the first boot but I only got the LOS startup dialog, and there doesn't seem to be any Gapps.
I also tried the same proceedure but using MindTheGapps-12.1.0 (20220416), but no still no Gapps.
Are there any tricks for loading Gapps using adb and lineage recovery, or does this only work with TWRP.

WackyDoo said:
[...] I then immediately sideloaded NikGapps-core-arm64-12.1 before the first boot but I only got the LOS startup dialog, and there doesn't seem to be any Gapps.
Click to expand...
Click to collapse
Immediately, w/o a reboot? You have to reboot into recovery after flashing an A/B ROM (to switch to the newly flashed ROM - #6 in the install steps) before flashing Gapps/etc. ;-)

jeremywh7 said:
Immediately, w/o a reboot? You have to reboot into recovery after flashing an A/B ROM (to switch to the newly flashed ROM - #6 in the install steps) before flashing Gapps/etc. ;-)
Click to expand...
Click to collapse
I was following the upgrade instructions ( https://wiki.lineageos.org/devices/payton/upgrade ) since I was coming from the previous version of LineageOS?? The upgrade instructions specifically mention that we should not reboot before flashing extra addons like gapps.
I will try the install instructions linked in the OP later, skipping the unlocking and, I guess, not running the copy_partitions script since I already ran than with the previous ROM.

I followed the same instructions and got the same result coming from the previous lineage version. I went back into the lineage recovery, reflashed the GAPPS and rebooted. Had a little trouble signing into my Google account as the 2 step authentication notification struggled to come through on the phone. I got around this by setting myself up as another user rather than the "owner". Everything seems to be working OK except the bluetooth connection to my car. The phone is connected and contacts appear on the car dashboard along with the battery and signal strength indicators- but calls don't come through the car - only to the phone's own speaker and microphone.

I followed the instructions and it updated to 19.1 without issue. Now, though, about every 5 minutes or so I get a "popup" or whatever it's called that says "Intent Filter Verification Service keeps stopping". Somewhat annoying. If I "force stop" the Intent Filter Verification Service app, it stops doing it, obviously. But upon reboot it starts right back up again. I don't have any of the gapps installed, but I do have microg, unsure if that's related. Overall though, it works pretty well.

To avoid boot loops,
Keep in mind to reboot to recovery between each sideload
Sideload lineage 19
Reboot to recovery
Sideload gapps
Reboot to recovery
Sideload Magisk
Power Off

[ROM][12.1][UNOFFICIAL] PixysOS [PL2]

Hey, really appreciate your work!) Specific bug for your rom is inability to setup magisk, because stock rom recovery "Failed to clear BCB message" error, adb sideload method doesn't works in it too. If i flash boot TWRP, then I can't boot rom, it stucks on boot logo. General bugs for all roms, such as hanging vibration (12.1 bug), gcam, that after some time of use can't take photos are here. Again. thanks for your work!!

Hi, thanks for your reply! Magisk works on this ROM, I just tested the version 24.3.
You need to boot into TWRP (twrp-3.4.0-0-PL2_sprout-11.0-20200909.img), select adb sideload option and flash latest Magisk zip. Then reboot and check the magisk app. Now you are successfully rooted. ;-)
Note: If you are installing Magisk right after flashing rom, don't forget to switch slot first!

I tried to install magisk right after I installed rom. For example now I am on a slot B, rom is installed on slot A. Magisk would setup on current slot, not as rom, that would setup on inactive slot -> I need go to the A slot to setup magisk. If I try to do that through stock rom recovery on slot A, I get error, because ADB sideload isn't working. If I try to "fastboot flash "twrp"" on slot A, then I can install magisk, but I am stuck on the rom boot logo. If I try to use twrp install.zip file from TWRP on slot B, then I get would the same problem (boot logo) on slot A. ADB sideload is installing magisk in current slot, that's why I can't do it from slot B to setup magisk on slot A. It's a bit sadly. And the second question to you, why our community vendor has general GCam problem, that is on all roms? Maybe you can contact to developers of it to fix that problem? Because it's really shame bug)

Just tell me about the experience you had with the Rom. is it smooth or not

Magisk must be installed in the same slot as the ROM. I ttied it and it works for me.
GCam problem is probably related to vendor or kernel source. Because I'm using Lineage trees to build this rom, It must be fixed by LineageOS developers.
My experience wih rom is very good, don't expect smoothness as stock, but the fact that this is an Android 12, result is really good. Small lags are ocassionally present.

Gcam not working fix it

Machi007 said:
Magisk must be installed in the same slot as the ROM. I ttied it and it works for me.
GCam problem is probably related to vendor or kernel source. Because I'm using Lineage trees to build this rom, It must be fixed by LineageOS developers.
My experience wih rom is very good, don't expect smoothness as stock, but the fact that this is an Android 12, result is really good. Small lags are ocassionally present.
Click to expand...
Click to collapse
I know that magisk have to be installed in the same as rom slot. That's why I had problems with that. If you would fix stock rom recovery, then there are no problems would be)) Yeah, rom is pretty smooth, on my opinion it works as the 10 stock, but of course android 11 custom roms work better and that's absolutely normal)

Rbargujar said:
Gcam not working fix it
Click to expand...
Click to collapse
If you tell me how to fix then I will do it. --- If you want perfect ROM then forget about custom and use stock.
FarLine99 said:
I know that magisk have to be installed in the same as rom slot. That's why I had problems with that. If you would fix stock rom recovery, then there are no problems would be)) Yeah, rom is pretty smooth, on my opinion it works as the 10 stock, but of course android 11 custom roms work better and that's absolutely normal)
Click to expand...
Click to collapse
I don't understand why to use stock recovery when we have TWRP.

Machi007 said:
If you tell me how to fix then I will do it. --- If you want perfect ROM then forget about custom and use stock.
I don't understand why to use stock recovery when we have TWRP.
Click to expand...
Click to collapse
Because if we try to use flash boot twrp on rom slot, then rom can't boot, it stuck on boot logo)

OK, I didn't try to flash Magisk zip right after ROM flashing... I have fully configured ROM with installed apps etc. and in this state I booted into TWRP flashed Magisk zip and ROM normally booted, I just found Magisk in apps and everything worked. This is my experience.

Machi007 said:
OK, I didn't try to flash Magisk zip right after ROM flashing... I have fully configured ROM with installed apps etc. and in this state I booted into TWRP flashed Magisk zip and ROM normally booted, I just found Magisk in apps and everything worked. This is my experience.
Click to expand...
Click to collapse
Maybe) In my experience, if I flash TWRP after flashing rom the rom doesn't boot, at all. Maybe I have done something wrong, but any way, if you will fix the stock recovery, it would be better!)

I need to clarify this: You are trying to flash TWRP using twrp-installer zip? If yes then this will not work on Android 12 ROM!
Do this to temporary boot TWRP (in download mode):
fastboot flash recovery twrp.img <----- this command returns error because our phone does not have the recovery partition, but it is mandatory to execute this command first --- then:
fastboot boot twrp.img <----- this command temporary boots TWRP on your Nokia 6.1 and now is the right time to install Magisk...
I recommend THIS TWRP version, just download the file and rename to twrp.img.

Machi007 said:
I need to clarify this: You are trying to flash TWRP using twrp-installer zip? If yes then this will not work on Android 12 ROM!
Do this to temporary boot TWRP (in download mode):
fastboot flash recovery twrp.img <----- this command returns error because our phone does not have the recovery partition, but it is mandatory to execute this command first --- then:
fastboot boot twrp.img <----- this command temporary boots TWRP on your Nokia 6.1 and now is the right time to install Magisk...
I recommend THIS TWRP version, just download the file and rename to twrp.img.
Click to expand...
Click to collapse
I tried to use twrp installer first, it did not worked for me, then I tried to use fastboot flash boot method, that is recommended for this TWRP. Using both flash recovery and boot method is new for me, so maybe it will be ok. But flash boot method doesn't work. And yeah, I used recommended from you Raghu's TWRP.

New build uploaded: PixysOS v5.1.3
- June security patch
- Fixed WiFi hotspot
- Google Camera should work much better now
- Build based on latest PixysOS sources with latest improvements and new functions added by ROM developers
And I would like to thank Raghu Varma which helped me a lot with fighting bugs!

Machi007 said:
New build uploaded: PixysOS v5.1.3
- June security patch
- Fixed WiFi hotspot
- Google Camera should work much better now
- Build based on latest PixysOS sources with latest improvements and new functions added by ROM developers
And I would like to thank Raghu Varma which helped me a lot with fighting bugs!
Click to expand...
Click to collapse
Maybe would try later, thanks for your work!)

Is anyone able to check if Duo Mobile 2fa is working?

I did all the steps, installed the rom, It siad "Fhasing A/B Zip to ianctive slot: B" after I try to change the slot and reboot, it says no OS installed... Is anyone else having this issue?
I did the Nokia Partition Tool, rebooted to bootloader, booted into the 3.4 TWRP it suggested and did the steps, It still said the error and rebooted back into TWRP*
EDIT: I was redoing it for the 3rd time as I typed this message and it magically worked.

Just a request, if it isn't too much to ask for...
Would it be possible to provide a vanilla build too? Perhaps then the installation would fit on the device without repartitioning -- I have made a couple of observations that have made me arrive at this conclusion:
My experience with LineageOS 19 is that the build + MindTheGApps package fits on the stock system partition without the need for repartitioning.
On the official PixysOS downloads page, I see that the size difference between Android 12 vanilla and GApps builds for one of the devices is something like 600 MB.
I am downloading the build at this instant, and I'm going to try fiddling around with the system image to make it fit on my PL2 before resorting to repartitioning (because we all know how much of a pain that can be ). I intend to install it later in the day, so I don't yet have feedback on the build itself.
Cheers! And thanks for your effort and time!
EDIT: I must also add that for a) people who prefer to use only core Google apps like GMS and Play Store (e.g. myself), and b) people who do not want to use even core Google services, a vanilla build would be ideal.

Vedanth Padmaraman said:
Just a request, if it isn't too much to ask for...
Would it be possible to provide a vanilla build too?
Click to expand...
Click to collapse
I'll consider it, maybe from the next build I'll provide both versions.

[OFFICIAL][ROM][PAYTON]LineageOS 20 (Android 13)

Important extra links
Payton Stock firmware:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Copy partitions link for download can be found on the LineageOS Wiki install instructions for Payton page here:
Install LineageOS on payton | LineageOS Wiki
wiki.lineageos.org

Hi! Working properly.
In this release adaptive storage is perfect.
VoLTE working. Only battery consumption is slightly higher.

Did an upgrade install from last lineage 19 build, and seems to be working fine, so far. Cannot test phone calls, as it seems AT&T towers block this phone, and Consumer Cellular uses AT&T towers in my area.

I gave this a shot over the weekend. I had some initial problems on the first install, but tried a second clean install and things were generally stable. I was able to make calls, though didn't try receiving any. Apps seemed to work as expected (though I'm not a heavy user).
What I hadn't tried was any SMS messages until this morning. I received one and it promptly rebooted the phone. I then tried sending a text from my GVoice account to my phone SMS account and as soon as the phone tried to receive the message, it'd reboot. I gave it a quick try at getting a log of this happening, but failed. I've reverted back to 19.1 as this is my daily phone. I'll probably give it a try again this weekend and can try and get a log capture then.

I also upgraded to LOS20, no problems, also sending and receiving SMS works fine.
@ThE_MarD : You and your team did a good job! Thanks
I noticed one problem: I get a hint - "App updates are ready - Connect to a network to continue", but I'm already connected to wifi. No updates possible!
After a system reboot everything is ok I thought, but after some minutes "App-Updates....

Heyyo @woodpe , thanks man but it was definitely SevenRock who handled LOS 20 for payton I just did the builds and XDA threads heh I guess he'd rather do the hobby side and less the PR side
For that message, can you please send logcat and maybe a picture of what you're seeing? Which GApps did you use btw?

I use MindTheGaps13 arm64 from the link in the instructons. I hope logcat I did is ok (I'm an old guy(74) but I've never done one before)!
Attached you'll find the pictures and log.txt
Thanks

Sorry, can't attach log.txt (3,1 MB)
Solved, zipped the file!

Anyone else tried this on Verizon? And if SK, can you send SMS texts? On my reinstall it seems like everything is working fine other than sending a SMS. When I do that I get a message failed error, both with the aosp and google message apps. I can receive messages fine though. See screenshot or attached log.
I see messages about RCS not working I think in the log, not sure if this is related or not. 19.1 works fine.

One question: when I enable USB debugging in the Developer options it is disabled after a reboot.
Any solution possible?

This is my first post, so first a friendly hello to all.
I have the test build on my second X4 since today. The upgrade and the installation of MindTheGapps with the lineage recovery were without problems. Everything important to me seems to work: Phone calls, SMS, wifi, mobile data, GPS, bluetooth and NFC connection to my bike computers and to the "Teufel Boomster" with apt-x HD audio. I have not noticed any bugs or issues so far. USB debugging is still enabled even after a reboot.
A big thank you to all developers, I love my two X4 and hope they will be supported for a long time.
One question: will the next test builds and the first official build of LineageOS 20 be offered as an update or do I have to install them as an upgrade again?

@paukenschlag
I was able to upgrade from 17.1 to 18.1 and further to 19.1 now just by dirty flash zip from SD with TWRP. No GApps installed, Magisk had to be reinstalled. That's all for me.
I guess upgrade to 20 will be same way.

some bank apps will not work with public keys and not last security patch
security error UA599 R:4,5

wkn000 said:
@paukenschlag
I was able to upgrade from 17.1 to 18.1 and further to 19.1 now just by dirty flash zip from SD with TWRP. No GApps installed, Magisk had to be reinstalled. That's all for me.
I guess upgrade to 20 will be same way.
Click to expand...
Click to collapse
I reinstalled the test build with the lineage recovery and a factory reset, this time without gapps - no problems.

Seems to work fine for me with MindTheGapps. Im using this version: MindTheGapps-13.0.0-arm64-20221025_100653

Noticed:
Changelog 27 - Thriving Thirteen, Amazing Aperture, Careful Commonization
X_X
lineageos.org

Heyyo, as @rseiler mentioned LineageOS 20 official is out and payton build is ready for download!

Downloaded, installed (with twrp-3.6.2_11-0-payton, encryption disabled), restored Magisk and MicroG and... IT WORKS!!!
Many thanks to all maintainers (represented by ThE_MarD here) of this new build version, well done!

Installed the official build on both my paytons, each with lineage recovery, one with MindTheGapps, one without. No problems with the installation, everything seems to work. Thanks to all!

Better Mobile App

welcome