• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[OFFICIAL][ROM][PAYTON]LineageOS 18.1

Search This thread

ThE_MarD

Senior Member
Dec 10, 2014
3,006
3,527
Grande Prairie
LeEco Le Max 2
Moto X4
Thanks @Afgil , hmm, unfortunately it didn't give me any hints as to what is causing it and I can replicate it on my payton too, so I think I'll need to maybe check props and other display related configuration parts and see if I can get lucky and pinpoint what is the error.

Off topic, I saw you have a smart watch, can you please tell me which and if you recommend it? I've thought about getting one, just not sure which and how much I'd be willing to spend heh
 

Afgil

Member
Sep 19, 2021
14
3
I am using an amazfit GTS 2 mini. 80€. It is not bad, i am using just for heart monitoring and fitness. It shows notifications with limited reply bit do bit makes calls. It has GPS include andò interfaces with smartphone for music. Battery good, it lasts around 3 days with my settings, doing fitness everyday.

There is another newer model having also storage and built in player.
 
  • Like
Reactions: ThE_MarD

Afgil

Member
Sep 19, 2021
14
3
Hello!
I have a new big issue here!
Once i was watching a video, once the Screen was in lock, once i was on messenger, once i was in the car, but the car was completely off.

In this 4 cases i got an incoming call, the phone was ringing and vibrating but

I was not able to reply! There was nothing on the Screen, i mean not the usual interface to reply the call.

NOR if i manually opened the phone app

I just had to wait the caller to end the call, then i received the SMS of lost call, and had in the hystory the lost call, so i was able to recall.

This is very annoing!!!
Do you nave any idea?
Could you do something?
Thank you
 

Vlad_mir

New member
Sep 27, 2021
2
2
Hello,

I'm new here, never messed with flashing ROMs before and not much of a developer. Just installed LineageOS 18.1 with TWRP (official LineageOS18 image didn't work), and I'm amazed with the results. It's almost like a got a new phone. Many thanks to team Lineage and whoever ported it to payton!

Now, I'm having one big problem with my XT1900-6: Connection with LTE is VERY spotty. Most of the time it's only GSM and GPRS or just disconnected from the network.

I checked APN settings for my carrier and it looks ok. @ThE_MarD mentioned "carrier overlays" but I couldn't understand exactly what are these.

So, my questions are:
a) I flashed my phone from stock, but without the carrier (Claro BR) chip. Does it have any influence on this matter?
b) If that's not the case, what logs should I get to begin looking into the problem?
c)Should I post it here? I got to LineageOs Gerrit page, but it looks like a developer's thing. It looked way out of my league...

Thanks, and sorry for the newbie questions!
 
Last edited:
  • Like
Reactions: ThE_MarD

ThE_MarD

Senior Member
Dec 10, 2014
3,006
3,527
Grande Prairie
LeEco Le Max 2
Moto X4
@Afgil , hmm, can you please logcat that? Maybe it'll give us a clue as to why in this case it isn't working for you. Hopefully we can find out all these graphical bugs... So far no luck from my testing...

Heyyo @Vlad_mir , that's great it's running good for you! Erfan was the main guy who got Payton working amazing on custom ROMs, so most of the thanks goes to him. :)

Just to check, before flashing LineageOS, were you on the latest build of Android Pie for your Payton?

You can post logs here and hopefully we can locate what the issue is.
 

Afgil

Member
Sep 19, 2021
14
3
@Afgil , hmm, can you please logcat that? Maybe it'll give us a clue as to why in this case it isn't working for you. Hopefully we can find out all these graphical bugs... So far no luck from my testing...

Heyyo @Vlad_mir , that's great it's running good for you! Erfan was the main guy who got Payton working amazing on custom ROMs, so most of the thanks goes to him. :)

Just to check, before flashing LineageOS, were you on the latest build of Android Pie for your Payton?

You can post logs here and hopefully we can locate what the issue is.

I installed the app google phone and worked well.
Today i was going to extract the logcat, but there was the notification of update.
I applied the update and removed the google phone app to make the test.

I don't know what happened, but now it is ok. and works well.

by the way the problem of flickering is instead always there.
do you have a suggestion to enable by default the option for Hw overlay?
thank you
 
  • Like
Reactions: ThE_MarD

htsmi

Member
Jul 15, 2016
47
14
@htsmi hmm that sucks it didn't work... I guess the safest bet is to stick with FDE then...
FDE doesn't work either on 18.1, at least without more debugging which is beyond my level. It fails to encrypt and then bootloops. So I'm stuck with unencrypted portable storage. At least I got a 64gb model recently so I've got a little more internal space.
 

ThE_MarD

Senior Member
Dec 10, 2014
3,006
3,527
Grande Prairie
LeEco Le Max 2
Moto X4
@htsmi , We might be able to use FBE on adaptable storage if we do the prop as mentioned here



On devices that launched with Android 10 or lower, use the following properties:

  • ro.crypto.volume.contents_mode selects the contents encryption mode. This is equivalent to the first colon-separated field of ro.crypto.volume.options.
  • ro.crypto.volume.filenames_mode selects the filenames encryption mode. This is equivalent to the second colon-separated field of ro.crypto.volume.options, except that the default on devices that launched with Android 10 or lower is aes-256-heh. On most devices, this needs to be explicitly overridden to aes-256-cts.
  • ro.crypto.fde_algorithm and ro.crypto.fde_sector_size select the metadata encryption format on adoptable storage. See the metadata encryption documentation.
  • Caution: On devices that launched with Android 10 or lower, the default filenames encryption mode on adoptable storage was not valid on most devices, and it differed from the default mode on internal storage. Therefore, on such devices it must be explicitly overridden, usually to aes-256-cts.
 
  • Like
Reactions: Francesco Libera

TomBz22

Member
Nov 25, 2014
6
1
I'm trying to install this and I'm stuck on the boot animation. I've followed the instructions here: https://wiki.lineageos.org/devices/payton/install

Unlocked the bootloader, used fastboot to boot into twrp, sideloaded the copy-partitions.zip, formatted the data (and also chosen all options in wipe), sideloaded lineageos nightly and it hangs at the boot animation.

Eventually, after around 35 minutes, it drops into the lineageos recovery.

Where should I go from here? I can get back into the bootloader, recovery and twrp so it's not bricked but LineageOS itself never boots.

I've tried the process multiple times and all the options in the wipe list.
 

ThE_MarD

Senior Member
Dec 10, 2014
3,006
3,527
Grande Prairie
LeEco Le Max 2
Moto X4
Heyyo @TomBz22 , tbh for the first install I find it is easier to just use Lineage Recovery as our device is A/B so TWRP gets removed after flashing a ROM install anyways. Also, sometimes I've noticed that TWRP format data doesn't always work correctly too...

Just to check, were you on the latest build of Android Pie for your payton? It is a requirement to be on Android 9.0 firmware before flashing the ROM.
 

TomBz22

Member
Nov 25, 2014
6
1
Heyyo @TomBz22 , tbh for the first install I find it is easier to just use Lineage Recovery as our device is A/B so TWRP gets removed after flashing a ROM install anyways. Also, sometimes I've noticed that TWRP format data doesn't always work correctly too...

Just to check, were you on the latest build of Android Pie for your payton? It is a requirement to be on Android 9.0 firmware before flashing the ROM.

ah, thanks. It's a brand new phone, and was on Android 7 stock.

edit: Thank you, installing the stock Android 9 ROM and then Lineage works perfectly.
 
Last edited:
  • Like
Reactions: ThE_MarD
Hello!

I have a small issue with speaker volume. It is very low! Never had this problemi with stock ROM.

Any idea?
When I installed LineageOS 18 for the first time, the overall sound was cleaner than STOCK ROM sound despite the lower volume. I think there are 2 audio modes: a "normal mode" and a "phone calls mode" that introduces a compressor that squeeze the sound to make it louder reducing distortion but at cost of less quality. And I think STOCK ROM was always set to "phone calls mode" as I remember how it used to sounds like. I made a test yesterday: play a song on YouTube Music app... great clean sound. meanwhile I started a phone call and ended it few sec later. The playback continues but now with the "phone calls mode" audio. I stop the playback. audio returns to normal mode.

XT1900-7, 12 October Build
 
  • Like
Reactions: ThE_MarD

htsmi

Member
Jul 15, 2016
47
14
Hello!
I have a new big issue here!
Once i was watching a video, once the Screen was in lock, once i was on messenger, once i was in the car, but the car was completely off.

In this 4 cases i got an incoming call, the phone was ringing and vibrating but

I was not able to reply! There was nothing on the Screen, i mean not the usual interface to reply the call.

NOR if i manually opened the phone app

I just had to wait the caller to end the call, then i received the SMS of lost call, and had in the hystory the lost call, so i was able to recall.

This is very annoing!!!
Do you nave any idea?
Could you do something?
Thank you
I just had a similar issue with an incoming phone call while I was on the line with another phone call. There were incoming call beeps but no way to answer the call until I missed it. I'll try to reproduce this and see if I can get a logcat.

Another issue I've noticed is that notifications will stop sounding at a certain point, and the only way I can get them to start again is rebooting. It still vibrates though. It may have something to do with bluetooth audio which I use occasionally, google really confused notification and media audio streams and volumes in recent versions and it seems like a lot of bugs resulted from that.
 

wkn000

Senior Member
Jan 19, 2017
69
40
MotoCamera2 also not working for me after today build update (using com.motorola.camera2_7.2.32.61.apk, which worked flawlessly on LOS 17.1). I did a reinstall too, App starts, ask for permissions and afterwards it goes in "background). Try to select in task manager lets the app crash (App closes too often/Close App popup).
 
  • Like
Reactions: Francesco Libera

Afgil

Member
Sep 19, 2021
14
3
MotoCamera2 also not working for me after today build update (using com.motorola.camera2_7.2.32.61.apk, which worked flawlessly on LOS 17.1). I did a reinstall too, App starts, ask for permissions and afterwards it goes in "background). Try to select in task manager lets the app crash (App closes too often/Close App popup).
Apk? I don't have apk i'm using the .zip file to ne installed from recovery, ad one can find in this forum section mods. And that do noto work.
 

Top Liked Posts

  • 1
    MotoCamera2 also not working for me after today build update (using com.motorola.camera2_7.2.32.61.apk, which worked flawlessly on LOS 17.1). I did a reinstall too, App starts, ask for permissions and afterwards it goes in "background). Try to select in task manager lets the app crash (App closes too often/Close App popup).
  • 3
    @Afgil , hmm, can you please logcat that? Maybe it'll give us a clue as to why in this case it isn't working for you. Hopefully we can find out all these graphical bugs... So far no luck from my testing...

    Heyyo @Vlad_mir , that's great it's running good for you! Erfan was the main guy who got Payton working amazing on custom ROMs, so most of the thanks goes to him. :)

    Just to check, before flashing LineageOS, were you on the latest build of Android Pie for your Payton?

    You can post logs here and hopefully we can locate what the issue is.
    1
    @htsmi hmm that sucks it didn't work... I guess the safest bet is to stick with FDE then...

    @Afgil hmm, any chance you can get a video of that and also logcat please?

    I've tested out different brightness configs that AndrewHexen made for sdm632-common and luckily they seem to work great on payton so I'll release a test build with it. I'm just waiting on also being able to add some vendor blob updates with it as lake got a new OTA on the stock ROM.
    1
    Ok i found a way to give you all the informations. in the video the flickering is well appreciable at 00:13 and 00.20, but it was more frequent.

    thank you
    the video was not loaded. you can find it in the zip
    1
    I am using an amazfit GTS 2 mini. 80€. It is not bad, i am using just for heart monitoring and fitness. It shows notifications with limited reply bit do bit makes calls. It has GPS include andò interfaces with smartphone for music. Battery good, it lasts around 3 days with my settings, doing fitness everyday.

    There is another newer model having also storage and built in player.
  • 7
    2okPze5.png



    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 a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.



    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.



    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.



    Introduction

    This is the official Lineage OS thread for the Motorola Moto X4, codename payton.



    We support all the T-Mobile, International, and Project Fi variants, as their bootloaders are unlockable, while we can't support the Verizon and AT&T variants, as their bootloaders are permanently locked.



    How to install via Lineage Recovery

    Please follow the official instructions



    HOW TO UPDATE LINEAGEOS WITH LINEAGE RECOVERY

    Please follow the official LineageOS Wiki instructions for our device




    How to install via TWRP

    1. Boot the newest TWRP .img from the Official TWRP Project Site.
    2. IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
    3. In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
    4. ADB sideload the newest weekly
    5. (Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need to be re-installed every update), and has no addon.d-v2 persistence.
    6. Click "Reboot", then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
    7. (Optionally) Flash GApps
    8. Reboot


    How to upgrade from 17.1 via Lineage Recovery

    Please follow the official instructions



    How to upgrade from 17.1 via TWRP

    1. Boot the newest TWRP .img from the Official TWRP Project Site.
    2. IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
    3. In TWRP, click "Wipe", then select "advanced" and select "cache" and wipe.
    4. ADB sideload the newest weekly build or copy it to your device and install the zip
    5. (Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need to be re-installed every update), and has no addon.d-v2 persistence.
    6. Click "Reboot", then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
    7. (Optionally) Flash GApps
    8. Reboot


    Notes

    Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status. (Magisk works fine, though is not supported.)
    Official Lineage OS builds ship with full treble compatibility, with VNDK runtime enforcement! This means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run any GSI (yes, even Pie!) without need for hacks or additional flashable zips. We relabeled /oem as /vendor (as /oem isn't used in custom ROM's anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image. Please don't report GSI bugs here, report them instead to the GSI's maker.


    Download

    Official:


    Unofficial test builds:



    Google Apps (GApps)

    MindTheGapps:


    GCam Mods


    XDA:DevDB Information

    Lineage OS 18.1, ROM for the Moto X4



    Contributors

    erfanoabdi, ThE_MarD, Lineage Team

    Source Code: https://github.com/LineageOS

    ROM Firmware Required: Official Pie
    5
    Heyyo @doug.passerini , I asked other Motorola maintainers and they said that the provided fingerprint kernel drivers are very bare, so it isn't something that would be simple to do as we would need to entirely recreate the driver from scratch and tbh it's well beyond my skill level... o_O
    5
    I'm on a May version of the build and have been having this issue since the beginning. I use a headset because of this, or I have to talk loudly.
    @maelopam @ThE_MarD

    I finally found the solution to the Mic issue. It was dust inside the tiny Mic hole (along side the finger printer) in the front of the smartphone. Also cleaned the tiny hole in the back side of the phone. Used isopropyl alcohol on both hole and vouila! Problem fixed!

    Source: https://www.reddit.com/r/MotoX4/comments/83cwss/_/dvhjaf3
    4
    Heyyo, can anyone with quick charging issues please submit logcat? It's working fine for me, so I'm unsure if maybe your charging blocks are different? We haven't changed anything to do with chargers since 17.1 so it should just work the same as 17.1 did.

    @ferrazrafael , that has to do with SafetyNet. Netflix won't natively install on any device that SafetyNet fials on. You will need to either sideload the apk from somewhere or use Magisk Hide and maybe other stuff (I dunno, I don't install any root on my devices as it weakens security as root itself is a security bypass).
    4
    Heyyo, so it turns out Google changed the way attestation works, so Topjohnwu confirmed he needs to update Magisk so that Magisk Hide works again. No point reporting SafetyNet bugs in this thread and just wait for Magisk to be updated.