• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[ROM][UNOFFICIAL]LineageOS-15.1[Albus][Moto Z2 Play][Discontinued]

Search This thread

leodexe

Senior Member
May 14, 2020
66
9
Punto Fijo
Doubt

Is there any support yet for LineageOS 17 on Moto Z2 Play?
I doubt. They haven't released LOS 16, so LOS 17 is even farther away. I'll just stick with any 64 bit ROM that has the least amount of bugs and keep stable over use (most custom ROMs get messy/buggy after some weeks of use)
 

leodexe

Senior Member
May 14, 2020
66
9
Punto Fijo
Stock Pie modem causes audio issues in Custom ROMs

Just tested AEX 5.8 and Lineage OS 15.1
̶F̶o̶r̶ ̶w̶h̶a̶t̶e̶v̶e̶r̶ ̶r̶e̶a̶s̶o̶n̶ ̶t̶h̶e̶ ̶a̶u̶d̶i̶o̶ ̶f̶r̶o̶m̶ ̶t̶h̶e̶ ̶s̶p̶e̶a̶k̶e̶r̶s̶ ̶s̶o̶u̶n̶d̶s̶ ̶c̶r̶a̶c̶k̶e̶d̶ ̶a̶n̶d̶ ̶d̶i̶s̶t̶o̶r̶t̶e̶d̶ ̶e̶v̶e̶n̶ ̶a̶t̶ ̶l̶o̶w̶ ̶v̶o̶l̶u̶m̶e̶ ̶l̶e̶v̶e̶l̶s̶ ̶w̶h̶e̶n̶e̶v̶e̶r̶ ̶t̶h̶e̶r̶e̶ ̶i̶s̶ ̶a̶ ̶c̶a̶l̶l̶.̶ ̶I̶t̶ ̶m̶i̶g̶h̶t̶ ̶b̶e̶ ̶a̶ ̶g̶e̶n̶e̶r̶a̶l̶ ̶b̶u̶g̶ ̶p̶r̶e̶s̶e̶n̶t̶ ̶i̶n̶ ̶t̶h̶e̶s̶e̶ ̶b̶o̶t̶h̶ ̶c̶u̶s̶t̶o̶m̶ ̶r̶o̶m̶s̶?̶ I come from using Stock Oreo and Stock Pie and I hadn't experienced this issue before.
Edit: This is a bug caused by the modem file from Stock Pie. To fix it simply reflash the modem from Stock Oreo again. http://www.mediafire.com/file/q8nbpybxc8mjyew/NON-HLOS-Z2P-STOCK-8-OREO.7z/file

I'd like to ask here if there is any way to disable the proximity sensor, since mine is broken, also my phone's touchscreen has suffered several cracks but my only problem with my phone is within the proximity sensor itself that stopped working at some point, you see, whenever I start a call, attend a incoming call, or replay a voicenote in Whatsapp, Telegram or Facebook the screen goes black until the call or the voicenote finishes, I tested with a proximity sensor tester apk and the sensor is always triggered even when nothing is pushing the sensor, and absolutely nothing isn't even remotely close to the phone, and when I push with my finger the touchscreen near the sensor, the phone, ironically deactivates the sensor, I must do the latter because with the proximity sensor always triggered I can't do the Moto Actions like shake twice to turn on the flashlight and sometimes it messes with my fingerprint unlock.
 
Last edited:

tzrlk

New member
May 24, 2016
3
0
Did all the installs and everything seemed to work fine, but I got into a recovery loop to TWRP. Found a thread that mentioned that factory mode would bypass it, and sure enough it did, but I can't really keep going through the bootloader every time I need to restart my phone. Anyone got any ideas on how to fix the boot so I can start the phone normally?

Also found that the bottom nav buttons are missing, any ideas on how to get them back?
 

leodexe

Senior Member
May 14, 2020
66
9
Punto Fijo
Did all the installs and everything seemed to work fine, but I got into a recovery loop to TWRP. Found a thread that mentioned that factory mode would bypass it, and sure enough it did, but I can't really keep going through the bootloader every time I need to restart my phone. Anyone got any ideas on how to fix the boot so I can start the phone normally?
Try issuing this command in fastboot mode
Code:
fastboot oem fb_mode_clear
Also found that the bottom nav buttons are missing, any ideas on how to get them back?
Try this
The on-screen buttons can be restored by adding "qemu.hw.mainkeys=0" to the build.prop file. You can use the "BuildProp Editor" app for example to do this.
 
Last edited:

tzrlk

New member
May 24, 2016
3
0
Try issuing this command in fastboot mode
Code:
fastboot oem fb_mode_clear

Try this

Swing and a miss, sadly. Still boots to recovery by default. Could it be something to do with permissions on the partition that are granted or waived during factory mode?

Was able to get the buttons back by editing the build.props file manually (using a guide I can't link to yet):
Code:
# boot into TWRP
# TWRP: Mount > System
adb pull /system/build.prop
# edit file
adb push build.prop /system/
adb shell chmod 644 /system/build.prop
# TWRP: Reboot > System
 
Last edited:

leodexe

Senior Member
May 14, 2020
66
9
Punto Fijo
Swing and a miss, sadly. Still boots to recovery by default. Could it be something to do with permissions on the partition that are granted or waived during factory mode?
Your recovery is the latest TWRP Treble 3.2.2_r23 64-bit, right?
Idk, as I haven't used default factory reset. If you can try flashing again the Stock ROM with the initial oem fb_mode_set and oem fb_mode_clear, as this issue is highly likely caused by an improper flash, in other words, flashing/updating the Stock ROM without the OEM commands.
 
Last edited:

tzrlk

New member
May 24, 2016
3
0
Your recovery is the latest TWRP Treble 3.2.2_r23 64-bit, right?
Idk, as I haven't used default factory reset. If you can try flashing again the Stock ROM with the initial oem fb_mode_set and oem fb_mode_clear, as this issue is highly likely caused by an improper flash, in other words, flashing/updating the Stock ROM without the OEM commands.

Yup, using that recovery.

I never saw mention of oem commands used in any of the guides, but I fiddled around with it a bit more and it looks like LOS boots up absolutely fine, but only as long as I go through the bootloader to do it (Boot -> bootloader -> "Start" -> LOS); running
Code:
fastboot oem fb_mode_set
helps to streamline that process. If
Code:
fastboot oem fb_mode_clear
is run at any point after that, it just goes back to booting TWRP first.

I'll try setting it to fb mode, then reformatting and reflashing everything before turning it back off.
 

JPT223

Senior Member

ozlacs

Member
Oct 31, 2015
20
1
prov. CZ
hi, just installed this rom on my Z2 Play.
seems all ok, only a question: how to activate classic navigation bar, instead of use fingerprint sensors?
thanks
 
Last edited:

lungan

Member
Oct 8, 2020
10
0
My fingerprint sensor doesn't work and there were no navigation keys. I did add qemu.hw.mainkeys=0 using the post on page #2. However, the fingerprint key/sensor still doesn't work? I would like to be able to navigate and unlock using the sensor.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 12
    LineageOS-151.jpg
    LIneageOS is a free, community built, after-market firmware distribution of Android re-branded CyanogeMod, which is designed to increase performance and reliability over stock Android for your device.
    Code:
    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.

    LineageOS is based on the Android Open Source Project and CyanogenMod with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS please visit Gerrit Code Review.

    Warning!!!


    • BackUp EFS partition before installing. .If you lose IMEI , use this backup to retrieve it in future.


    Installation

    First time LineageOS installation on your Moto Z2 Play:



    • Unlock your bootloader if you haven't done so already
    • Flash a custom recovery via Fastboot (64 bit TWRP is needed)
    • Copy Gapps (64 bit) and Lineage OS flash files to sdcard
    • Boot into Recovery
    • Format Internal Memory . I repeat Format.. (Not Wipe) (after format reboot to recovery)
    • Flash the LineageOS zip from SD card
    • Flash GApps from SD card
    • Reboot

    Upgrading from earlier version of LineageOS :


    • Push the new LineageOS zip to your SD card
    • Boot into Recovery (64 bit TWRP)
    • Flash the LineageOS zip from SD card
    • Flash the most recent GApps (64 bit) for 8.x
    • Reboot

    Downloads

    - LineageOS : Builds
    - Google Apps (arm64) : GApps

    Bugs


    • You tell me


    Reporting bugs


    • DO NOT report bugs if you're running a custom kernel
    • DO NOT report bugs if you've modifies system files
    • DO NOT report bugs if you've installed xposed and/or other mods
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    Code:
    adb logcat > logcat.txt

    Code:
    adb shell dmesg > dmesg.txt


    • If it is a random reboot, grab kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    Code:
    adb shell cat /sys/fs/pstore/console-ramoops


    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log


    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues or bugs reported in the lastest 5 pages of this thread. Any bug not reported in the bug report format below may be ignored.
    Code:
    Phone Informations
    * LineageOS version
    * Gapps version
    What you did:
    * Wipe data: y/n
    * Upgrade from previous official cm build: y/n
    * Restore with titanium backup: y/n
    You're using (if yes write which one) :
    * Task killer
    * Phone cleaner / Battery enhancer apps
    * Non-stock kernel
    * Modified kernel settings
    * Other mods
    Bug info:
    * Last version it worked on
    * Repro steps
    F.A.Q.


    • ROOT! ROOT! Give me root or i'll die!!! Where root is???
    • First of all DO NOT flash any SuperSu/SuperUser/SuperMan zip package to get root. Go to Settings>Developement Settings>Root access and select "Apps Only"
    • Why no nightly today?
    • Build failed. Check again tomorrow
    • When do I have to wipe data?
    • You must wipe data only when you're switching from another rom or migrating to Snapshot branch from Nightly and vice versa. You don't need to wipe data when you update in the same release channe (this applies to 13.0 -> 14.1 upgrades too)
    • Will you add <insert awesome feature here>?
    • I won't. If you write it, submit a commit to gerrit, where it will be reviewed.


    The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

    Kernel Source : Here
    Device Tree: Here


    XDA:DevDB Information
    LineageOS, ROM for the Moto Z2 Play

    Contributors
    HeltonMax, rahulsnair, vache, brunorochaa00
    Source Code: https://github.com/LineageOS

    ROM OS Version: 8.x Oreo
    ROM Kernel: Linux 3.x
    ROM Firmware Required: TWRP
    Based On: LineageOS

    Version Information
    Status:
    Stable
    Current Stable Version: 2019-03-17
    Stable Release Date: 2020-02-11
    Current Beta Version: 2018-01-13

    Created 2019-03-20
    Last Updated 2020-01-03
    5
    New Build

    Hello guys I compiled again, the new build is already in the Google Drive folder and for those who play Pokemon GO it works normally and the Security Patch is October
    2
    I have the ROM installed but the fingerprint button doesn't work and there are no on-screen buttons. How do you navigate the interface?

    The on-screen buttons can be restored by adding "qemu.hw.mainkeys=0" to the build.prop file. You can use the "BuildProp Editor" app for example to do this.
    1
    The JBL snap is fully functional?

    Neither of the two JBL MOD snap models works