yashsingh1/xdaforums huggingface dataset:
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Sadako8888:
Hi! In the last days I installed this official version of Lineage 18.1 for Moto Z Play, and due to incompatibility with some apps that I use, I went back to the official ROM, through the Rescue and Smart Assistant software.

The next day, using the phone normally, it restarts and the screen is off. I can't access fastboot mode, but the pc does detect it when connected via USB. Is my phone bricked? How can I solve that? Thank you
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] huzefaonline:
I think you should use the rescue and smart assistant software to repair the device
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] mark04:
I think the community would also appreciate knowing which apps were incompatible. Some of us are still sitting on the sidelides trying to decide whether now is the time to unlock the bootloader and flash something other than stock.

For my part, I need Microsoft Authenticator (required by work) and I would also hate to lose any of my banking apps.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Sadako8888:
After 2 days without phone, I repaired it again with Rescue and Smart Assistant, and the phone turned on in Fastboot mode, but left me without IMEI. So I reinstalled Lineage and was able to get it back. For fear of bricking it, once again, going down to the official ROM, I'll stay in Lineage.

They are 2 local apps from Argentina. I think the incompatibility stems from the local development of the apps, and not from the ROM, which so far works perfectly (except that you can't lock the phone with your fingerprint).

I use Microsoft authenticator, and it works perfect.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] mark04:
Thanks! Does the fingerprint sensor work at all? E.g. can you unlock the phone with it?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Sadako8888:
yes! u can unlock the phone but u cant lock it, i dont know why. I found out that NETFLIX is another app that is not compatible with the rom. The performance is so smooth, u should try it.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Unreal_man:
To developer: please bring back unlock by fingerprint. It's main reason why I still didn't flash this rom.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] mark04:
The post immediately prior to yours claims that fingerprint unlocking does work. Do you have information / experience to the contrary?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Unreal_man:
Excurse me. I meant lock ofcourse. Now I'm with AICP and have the same problem. When I flashed AICP 3 months ago, I'm also read about this rom, and developer wrote he won't return locking by fingerprint.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] gravit0n_:
Thank you so much for maintaining a ROM for this device. Apart from the 'sound bug' I didn't encounter any issues so far.

The speaker sound level lowers at random moments, not only during lock/unlock. It can be annoying during a speaker phone call. I hope to create a log soon.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Sadako8888:
Yes! the other day i was on a phone call and suddenly the volume drops to 0. Another bug that i found, its the camera. I used 3 different camera apps, and everyone of them, took some pictures with hdr, and some with grey tones. Also when u r filming, u can see the phone trying to mantain hdr, but it cant, so when u watch the video you can see the hdr option turning on and off constantly. Subjectively, (I can be wrong), I also consider that the audio quality in the videos is lower than in the stock rom.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] axelrvf:
Hey guys,

Fingerprint not working any more for me either. It was really helpful. I cannot lock (could not ulock anyway) or unlock screen any more.

I would appreciate it if you could make it functional again when locking and unlocking screen. Thanks
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] gti9070_lollipop:
nm
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] gravit0n_:
Only played with the default Camera app a bit, but I noticed it's buggy. When taking a picture in the dark it has trouble focusing (flash doesn't turn on to help?) and then the app occasionally slows/crashes. Also it takes a while before the picture shows up in the gallery left-bottom. But I don't have experience with the stock ROM to compare, I immediately flashed this LineageOS ROM.

Things like HDR I don't really care about, it's a post-processing effect, not real HDR.

UPDATE: When using Open Camera with camera's API it seems a lot more stable, also flash turns on during focusing in the dark. Camera2 API seems buggier, I think I read somewhere that this API isn't fully supported by the Z Play.

Fingerprint unlock works for me, latest build. Normally I have it turned off.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] axelrvf:
I am replying to my message because the problem was that the sensor near the front camera was covered.

There is still a problem that i'm facing, the problem is that if i use the fingerprint unlock for a number of times, it somehow stops working untill i reboot the phone.Any ideas?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] d2weber:
(To marcost22) First of all: thank you so much for bringing this awesome ROM to Addison after all the years. It gives my phone a second live.

I'm facing the same issue. After some time, it's not anymore possible to wake up the phone with the fingerprint sensor. When the screen is on an the Lockscreen is shown, the phone can be unlocked using the fingerprint sensor though.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] marcost22:
That's a decision that was made for me by the developers (as in the top people) of those roms; to make it better match the original behaviour of the phone. If it was up to me it'd have fingerprint lock

Yeah, unfortunately this is the pain from 3.18 moto's; camera SUCKS past the original version. I have been working on R-E the stack but it slow painful work so no promises.

Camera2 should be fully API-compatible, any weirdness comes from using patched blobs from Oreo in R HOWEVER the camera reports that it's HDR capable when it really isn't, stock moto does some framework hacks but the device itself cant handle the extra data coming from the sensor

To both of you, can you get me some logs? This isn't at all expected behaviour
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] axelrvf:
Can you please tell me how will i obtain the logs from my phone so i can send them to you?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Vergolacio:
After years of having apps and games crash continuously on stock, i can finally enjoy this phone to its fullest.

Thanks a lot!

Also, first time applying this kind of mods and the guides were top notch.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] marcost22:
From a pc while having adb debugging enabled in developer options you run

adb logcat -b all > aicp.log

then you attach aicp.log here
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Unreal_man:
Hi! Anybody have problems with network? I flashed this rom as a few month ago, and didn't get network connection at first. After reboot I got network, but this s*** always stops to work after some time. What can I do with this problem?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] marcost22:
Can you grab me a logcat? Do you mean WiFi network or Cellular network?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] rmaspons:
Moto XT1653-02.

Flawless instalation (latest version: lineage-18.1-20221123-nightly-addison-signed.zip).

Everything works: wifi, bt, data, took pictures (in some pictures colors appeared "washed out", could be because of HDR) and also videos. That being said: it is what it is. It´s an old phone. If you want, you can use it as your daily device... but it will be kind of laggy (I even disable menu animations). No sudden reboots, but apps sometimes stop working (they just freeze) and you have to open then again. That being said, I would really like to thank you for the effort. The phone is just a backup so I will keep ths ROM installed and trying new updates if there are any.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] cossak2007:
Have tried to install Lineage 18.1 & 17.1.

Lineage 18.1... installs and boots but screen unresponsive to continue setup after ROM has booted up.

START button unresponsive but hardware buttons work.

Same with the AICP Android 11 rom .

Lineage 17.1.... endless boot

What TWRP version are you using to install the rom?

Are you disabling forced encryption and dm-verity first with just formatting data or are using something else?

Also I can install official TWRPs 3.6 series and above, but the TWRP screens are unresponsive.

Is my stock version as in screenshot incorrect ?

What am I doing wrong ?

HELP !!!

Thank Terry
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Sadako8888:
Hi, u must use the official Lineage Recovery to install the Rom, dont use TWRP. Also, there is a bug in Motorola/Lenovo Rescue and Smart Assistant, cuz when u flash the original ROM, it breaks a part of the partition that contains the network data (that was my case). I ended up using this ROM, and im going to sell the phone SOON....
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Saurav2343:
Hi there!!

My variant is XT1653-02 using India.

Kudos to the developer.

Saw this post regarding a possible way to upgrade to android 11. But being new to all this, I feel bit hesitant to go ahead. Can someone please clarify some of doubts.

1) Whether the volte works on the latest build?

2) Is it possible to use the rom as daily driver?

3) Is it possible to revert back to official rom?

Please if someone find time do make a working video or images of the rom in action. It will be of great help.

Thanks.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] marcost22:
1) I don't know, my carrier doesn't give me volte so another user would have to answer this

2) It is, and i did for around 6 months until i switched to albus so that i could swap the battery on my addison

3) It is, it's just flashing the stock firmware again and it boots right up

I'd love to give you some videos/pictures but unfortunately my addison is still in pieces
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Saurav2343:
Thanks for the reply 👍.

Would wait till a fellow member find time to help me out, as I still use it as my routine device.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Saurav2343:
Hi all. I finally tried the rom, the experience was good, reverted back to stock due to the issue with the banking apps. Is there any possible way to make the rom recognize Playstore device certified.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Saurav2343:
Hi there, I followed the same steps with same results. Finally found that the network not recognizing was due to downgrading from higher android version. So, i downgraded further to android 7 and then used the rescue tool to move to android 8 os, and it worked. Everything else is reverted to stock except the unlocked bootloader warning on the boot screen ( even though the bootloader is locked, but due to the abscence of signed boot img i suppose the message is not going anywhere.

Would want to go with the rom , If you guys can help with device certification issue. I was using Havoc 4.19 on Asus zenfone max pro m1 - there the device shows certified how?

The developer took the effort to resurrect this old device, kindly if possible look into this as well. Thanks.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] marcost22:
Use magisk with zygisk and hide and changing the fingerprint to pixel 2. Unlike other roms LOS enforces a strict no modifications policy so this isnt allowed "shippable" behaviour
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Saurav2343:
Thanks for the clarification. Tried the magisk way -

Installed the latest version,

turned on the zygisk,

added the apps to hide,

Hide the magisk apk,

Installed the CTS fix, but still some apps mainly the banking ones found the root.

(Even tried the legacy Riru still with failed response)

If you could provide a link to guide how to apply the fingerprint

Or

Maybe this is how it is supposed to be 😂

Will definitely flash the rom once I get hold of any other device. Until then stuck with Android 8😅

Thanks for taking you time off to reply. Really appreciated 👍.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] marcost22:
Eh, you need to add google play services to the hidden list. Here's a guide some guy on the telegram chat made way back when, hopefully it works for you https://t.me/Z2PlayGSI/35382
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Saurav2343:
Appreciated.

Will try and revert.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] maritn76:
I have installed the lineage 18.1 ROM and it works like a charm on my moto Z play.

Congratulations to the developer for maintaining this device.!!!!

Is there a chance that lineage 19.1 will arrive?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] LouizFC:
I am having a problem with the touch-screen, it became irresponsive after flashing the ROM. I tested everything else with an USB C mouse and it works fine, the touch-screen was working on stock.

Is this a known case, are there any known fixes?

Before flashing I had OPNS27.76-12-22-9, but it presented some issues with IMEI so I decided to flash Lineage. The IMEI issue was fixed, but now the touch screen does not work
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] marcost22:
I'm guessing you had a screen replacement?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] LouizFC:
You guessed quite right, I had a screen replacement in the past
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] marcost22:
Not a true guess, it's a known issue with counterfeit screens that don't adhere to synaptics reset procedures. As timings were tightened to include newer devices (Z2 play for example) this screens stop working. As we use a unified kernel, this issue arises. I haven't found a way to identify them in sw to use a workaround

Could you get me a logcat by any chance?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] LouizFC:
Thanks for the quick response. I think I could, the only issue is that I cannot authorize ADB on the device because of the USB C mouse. I will get a way to access the device remotely, I think RustDesk can do it.

When I generate the logs, should I add them here or shoud I PM them to you?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] marcost22:
Both are good.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] :
I also replaced the screen, and the LineageOS18.1 20230322 version is still giving me problems with the touch screen, I went back to the stock rom and the touch screen works normally. MOTO Z play XT1635-02 (Translated by DeepL)
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] djordjei:
Can someone please confirm if the projector mod works fine with this rom? Thanks!
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Wario991:
thanks

I have a problem logging in to ROM, the first login asks me for a password
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] smogan:
SD Card is not recogniced!

I have two Addisons. On both I installed this ROM. Phone number One is a singe-sim device. Here everythin is okay. SD Card is visible in system with full access as expected.

Phone number Two is a doube-sim device. SD Card access under TWRP works fine. Inside this system the card is not show in any way. Tried different cards. The phone behaves as if there is no card slot. Reinstalled Lineage OS nightlies a couple of times. Always the same. Reverted the phone back to stock ROM... SD-Card works fine.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Andrea25:
This ROM is amazing the best I have tried so far. Is there any work around to get the SD card to work? My device model is XT1635-02 and the SD card doesn't seem to be recognized by the files app.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] SoundDrill:
In my experience, you simply use a recommended play store like mindthegapps and log in while configuring the device(instead of after). Might be hit or miss, most of my custom ROMmed phones have play certification.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] SoundDrill:
Has anyone had success with newer GSIs? I can't find any A only 12 or 13 GSIs.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] SoundDrill:
I have successfully booted many A/B roms.

Booting:

1. Phh's Roar(android 11), arm64, ab, floss(latest build at the time of testing)

2. Phh's AOSP(android 12), arm64, ab, floss(latest at the time of testing)

3. LineageOS 20 TD(android 13), arm64, ab, bvN. (hit or miss)

4. CarbonOS 9 by NipponGSI(android 11), AB

Method I've used:

0. Install LineageOS from here, and TWRP/PBRP.

1. Backup your data, EFS and relevant partitions using TWRP or my PBRP build(lemy me know of any problems in my thread)

2. extract .xz file

3. Copy the img file to your usb drive(connect via usb otg) or sd card.

4. Mount system partition and wipe it. If it fails, simply reboot to recovery and try this step again

4. Flash it as the system partition

5. Reboot to recovery(might bootloop otherwise)

5. (This is important) Wipe the following partitions using advanced wipe:

Dalvik/ART

Substratum Overlays

Magisk Modules

Data(back it up manually or using recovery)

Internal Storage

Cache

(if you see a system_root error, it's alright, just reboot to system)

Now you can boot!

I've tried this with lineageOS 20 trebledroid and a couple of phhusson's roms but I want to see what people find is working. I want people to share what GSIs they had good luck with.

If something is still bootlooping, reboot to recovery, and format data by typing "yes". If it still bootloops, try undoing magisk or installing lineageOS boot.img(you can get this from the zip or from lineageOS downloads) to properly undo magisk. This fixed my bootloop with lineageOS 20 TD.

I myself don't know much but common consensus seems to be that A/B seamless updates partitions and AB GSIs are the same. THEY ARE NOT, despite the confusing naming.

AB GSIs are simply GSIs that need System As Root. You can check this with hack5's Treble Info app.

I've seen tools like MakeMeSAR.zip that try to solve this problem, but I haven't tried them.

Since our addison has System As Root support and can boot AB GSIs, it is not an A only device, while it does not support seamless updates.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] wokawoka:
I would also need to know that before flashing the rom, I still use my old moto Z play as a projector from time to time.

Is there by chance anyone that can confirm that the projector mod works with this rom?

Thank you in advance!
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] SoundDrill:
if your bootloader is unlocked, I'd suggest flashing and finding out
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] wokawoka:
yeah, but in case the projector would not work I would have to look for the stock files

I thought that maybe someone else already did try that

I will try as soon as I will have some spare time

Thank you
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] id4:
I did not expect any support for this old device, very nice work.

I've been using it for a few weeks now, the only issue that came up is that nfc extended length is not supported, while it works on stock. It is a feature that is required for authentication with some European identity cards and apps, like the AusweisApp2.

I found a fix for other devices in the Lineage issues, which also work on this. Enabling it in the libnfc-nxp.conf, just appending:

# Extended APDU length for ISO_DEP
ISO_DEP_MAX_TRANSCEIVE=0xFEFF
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] SoundDrill:
I highly suggest a pull request to the device tree
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] dediggefedde:
Thank you for still supporting the Moto Z play!

I followed the instruction, but after sideloading the LineageOS zip-file, the phone screen is now stuck on "patching vendor image unconditionally..." for roughly an hour.

"patching sytem image unconditionally..." seemed to be completed.

I use win10 powershell to sideload with adb. There the progress is stuck on 47%:

"serving: 'lineage-18.1-20230922-nightly-addison-signed.zip' (~47%)"

How long does patching usually take?

Should I just try again or is there some incompatibility?

My version is XT1635-02 and I use the latest adb and fastboot with the recovery.img from the wiki.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] SoundDrill:
Cancel it once, reboot to recovery and try again

that fixed it for me whenever I had the issue
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] dediggefedde:
Thanks! I had some trouble figuring out how to cancel on the phone. I'm still not sure because of some delay, but I think it was keeping power + volume-down pressed for 4 seconds.

Now I tried again, and the patching was done within 5 minutes.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] dhirubro:
Thank you very much. It has been two days since i finished upgrading my Moto Z Play to Lineage. From VoLTE to Banking apps and UPI, all is working fine. Now i can also run the apps which are not compatibale with Oreo. Thanks again.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] djdelarosa25:
Thanks for the ROM! Would be nice if SD card support was added.

EDIT: Whoops. Looks like a simple reboot fixed it. I had no idea why it didn't detect both my SIM card and my SD card on the first boot.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] mark04:
Many thanks for the devs for this stable LOS, which has doubtless saved many tens of thousands of $$ by letting us keep a nice phone for a few more years!

The ROM has been mostly trouble-free for me until this morning, when I woke up to endless "Google Play services keeps stopping" messages. A number of my other apps which depend on play services have also stopped working. The phone is pretty much stock apart from running LineageOS, meaning no magisk, not rooted, etc.

Any idea what could be going on? My phone got the September 22 update and says there is nothing newer. This problem started very suddenly overnight. I smell a Google screwup here but have no idea how to fix it.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Sadako8888:
Hey man, do u have the Nougat Stock Rom for Moto Z Play? Where do u download it? Im stuck with no imei in Lineage nor Oreo Stock Rom. It will be very helpful if u send me the links so i can restore network on my device.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] mark04:
So it seems the problem was memory corruption somehow affecting play services. I have had very occasional (once a month?) freezes where my phone won't wake up, and when that happens I perform a hard restart. Usually everything is fine but this time it seems to have caused my play-services issues.

I tried all sorts of things to fix it, including re-flashing LOS and MindTheGapps (without factory reset or wiping anything). No dice. Finally I tried uninstalling com.google.android.gms with adb, and to my surprise that worked. I was prompted to log in to my google account (and I guess it automatically re-installs at that point), and everything has been fine since then.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] SirRGB:
yep, lineage merged it officially for griffin and it applies without issues like this.

addison: Bring back extended APDU · Moto-experimental/android_device_motorola_addison@a5a2042

* Fixes the bug provided in the references below. Reference: https://forum.xda-developers.com/t/rom-11-crdroid-7-26-vanilla-gapps-for-griffin-unofficial-15-jan.4296739/page-3#post-86503015 Change-...

github.com