[DISCONTINUED][ROM][PAYTON]LineageOS 18.1

Search This thread

ThE_MarD

Recognized Developer
Dec 10, 2014
3,457
3,929
Grande Prairie
LeEco Le Max 2
Moto X4
Heyyo @htsmi, glad to hear adoptable storage for FBE is working great for you (y)

As for volume? You can modify the values in /vendor/etc/mixer_paths.xml

You can see here it has been boosted twice already from the history tbh


Tbh if recommend cleaning your speaker grill and mic ports with a clean toothbrush dipped in isopropyl alcohol as they are probably clogged. If you check the thread history, this has worked well for them too
 
Last edited:

jw243

Member
Mar 21, 2016
49
14
I'm using the latest build of the MicroG-variant of this ROM and I'm having problems with scanning barcodes or qr-codes in some apps such as the Luca app or MyFitnessPal.

The camera opens within those apps, but it doesn't recognise nor scan the code. Apparently, this doesn't happen to other users with different operating systems.

On some other apps though, the barcode scanner does work, such as the Fitbit app. The scanner also works from within the camera app as well.

Has anyone else experienced this? Is it a bug of the ROM? Or is it related to using MicroG?

I would be extremely grateful if I could find a solution to this problem. Any suggestions would be greatly appreciated.
 
I'm using the latest build of the MicroG-variant of this ROM and I'm having problems with scanning barcodes or qr-codes in some apps such as the Luca app or MyFitnessPal.

The camera opens within those apps, but it doesn't recognise nor scan the code. Apparently, this doesn't happen to other users with different operating systems.

On some other apps though, the barcode scanner does work, such as the Fitbit app. The scanner also works from within the camera app as well.

Has anyone else experienced this? Is it a bug of the ROM? Or is it related to using MicroG?

I would be extremely grateful if I could find a solution to this problem. Any suggestions would be greatly appreciated.
I broke the camera so I'm always in marco focus distance 🤣
 

exzombie

Member
Jul 1, 2019
11
5
github.com
Has anyone else experienced this? Is it a bug of the ROM? Or is it related to using MicroG?
I have experienced that on LOS 17.1 with manually installed MicroG. Now I'm on the MicroG version of LOS 18.1, but I haven't had the chance to try the problematic app yet. Now that you reminded me, I'll try as soon as I can. I'm pretty sure the issue is payton-specific in some way because the same app scans QR codes without issues on the same setup, but a different phone.
 

Rootmaster906

Senior Member
Dec 2, 2020
353
16
Nexus 6
Samsung Galaxy Note 10
A friend of mine is having an issue. I sold him my Moto X4 and he is using a MetroPCS SIM card in it. For some odd reason the phone goes into a reboot cycle when he uses that card. I've always used an AT&t Verizon or T-Mobile SIM card and they work just fine. Any ideas?
 

jeremywh7

Senior Member
Sep 16, 2013
261
127
Indy
Motorola Atrix 4G
Moto X
For some odd reason the phone goes into a reboot cycle when he uses that card. I've always used an AT&t Verizon or T-Mobile SIM card and they work just fine. Any ideas?
I assume this X4 was on the lastet (final) OEM ROM (or updated to it's radio firmware) when you installed LOS? First make sure the sim is installed properly. I switched mine from ATT to Google Fi in Jan. No reboot issues but I did have significant radio issues. Running `fastboot erase carrier` helped, but I'm awaiting @ThE_MarD 's LOS 19.1 to do a clean reboot. Speaking of, I notice there's an unofficial 19.1 up... tempted to try it out. :p
 
  • Like
Reactions: Rootmaster906

Rootmaster906

Senior Member
Dec 2, 2020
353
16
Nexus 6
Samsung Galaxy Note 10
I assume this X4 was on the lastet (final) OEM ROM (or updated to it's radio firmware) when you installed LOS? First make sure the sim is installed properly. I switched mine from ATT to Google Fi in Jan. No reboot issues but I did have significant radio issues. Running `fastboot erase carrier` helped, but I'm awaiting @ThE_MarD 's LOS 19.1 to do a clean reboot. Speaking of, I notice there's an unofficial 19.1 up... tempted to try it out. :p
Where? I don't see it
 

Rootmaster906

Senior Member
Dec 2, 2020
353
16
Nexus 6
Samsung Galaxy Note 10
I assume this X4 was on the lastet (final) OEM ROM (or updated to it's radio firmware) when you installed LOS? First make sure the sim is installed properly. I switched mine from ATT to Google Fi in Jan. No reboot issues but I did have significant radio issues. Running `fastboot erase carrier` helped, but I'm awaiting @ThE_MarD 's LOS 19.1 to do a clean reboot. Speaking of, I notice there's an unofficial 19.1 up... tempted to try it out. :p
Here is current baseband
 

Attachments

  • 6e3113ad0000e216350aee513958cc07.0.jpg
    6e3113ad0000e216350aee513958cc07.0.jpg
    52.5 KB · Views: 12

jeremywh7

Senior Member
Sep 16, 2013
261
127
Indy
Motorola Atrix 4G
Moto X
Heyyo @jeremywh7, ya caught me lol, yes I do have a LOS 19.1 test build up. It's pretty much what pre-official payton will be like. If you guys wanna test and report back? Please let me know (y)
Thank you very much! :) Did you want to start a new thread for it? If so I'll move this post to it later. ;-) Are you currently running 19.1, and if so what Gapps (if any)? Here are my notes on anomalies from my install (via sideload) this morning...

-I did a factory reset/data format in LOS 18.1 recovery, installed lineage-19.1-20220322-UNOFFICIAL-payton.zip, rebooted to recovery and installed NikGapps 'stock' [which is like OpenGapps 'Mini' but with Gboard, Dialer, and Drive, and without Youtube) and then their GoogleFi add-on. I 'Reboot to System' which apparently failed and sent me to recovery which told me I needed to wipe /data (again). It booted into setup after that.
-After tapping 'Accept' at the Google Services page, it had me set security (I did a pattern), but then it went into a constant cycle of going back to the Google Services page. Even after a another reboot.
-After this reboot, and all others since, I get a message after booting that says, "There's an internal problem with your device. Contact your manufacturer for details." Is this a new A12 thing - perhaps cuz our vendor image isn't current?
-After trying various things, I decided to do another factory reset/data format in LOS recovery. And this time I skipped setting the security pin/pattern/etc. Went through without a problem this time!
-Another bigger problem I figured out though, is that I couldn't use Home nor Recents, and Pixel Launcher (which replaced the stock launcher) would sometimes crash. I couldn't back out to exit (most) apps either, so the only way to go to another app would be through Notifs->Settings->Apps.
-I then switched to a different launcher (first MS' which I uninstalled 5min later...) to my old go-to, Lawnchair (2, now), which worked, except that the Home and Recents still don't work (and I still occasionally get Pixel Launcher crash messages). I suspect it's due to Pixel Launcher messing something up.

I think my Google Fi network issues might be fixed, but only went to the gas station and grocery store today.

Anyway, let me know your thoughts and experiences, and if you want any logs or anything (or want me to test any other builds). It's my primary phone, but I have no issue messing with it. ;-) And thanks for all the work on payton!!!

[Edit 11 Apr '22 - Google Fi does now work a-ok on this clean flash. I was out and about all day Sat and was on LTE the whole time. :) I also uninstalled the /system Pixel Launcher using the NikGapps config file, which fixed the random crash messages from it. Still no Home/Recents, but the Feed works now. I was going to just wait for an updated 19.1 build to try, rather than reinstall the 0322 build. ]
 
Last edited:

ThE_MarD

Recognized Developer
Dec 10, 2014
3,457
3,929
Grande Prairie
LeEco Le Max 2
Moto X4
@jeremywh7, please only quote or mention and not both at the same time as I'm getting double notifications for the same post

For GApps? I recommend MindTheGApps for LineageOS 19.1 as it seems to be the only one that's really stable at least in my testing. The others gave me stability issues and Open GApps beta builds haven't been updated in a while so no idea how that one even is...

We will be shipping MotoCamera on LOS 19.1, so no more need to hunt down specific builds of it for us. (y)

Major thanks goes to the Moto sdm660 dev community, mainly sevenrock who did the majority of the bringup for A12.1. Tbh I've been so busy with family, work and my other devices (I own a bunch and only zippo, heart and payton are on the LOS 19.1 initial devices list so far oof, my x2 and Z01R aren't ready still) that I haven't had much time for payton. Any donations should be to the rest of the guys working on Motorola devices this time around. :)
 
  • Like
Reactions: Francesco Libera

jeremywh7

Senior Member
Sep 16, 2013
261
127
Indy
Motorola Atrix 4G
Moto X
@jeremywh7, please only quote or mention and not both at the same time as I'm getting double notifications for the same post

For GApps? I recommend MindTheGApps for LineageOS 19.1 as it seems to be the only one that's really stable at least in my testing.
Ah ya, sorry... fixed the double mention. :)

What launcher is your payton using? Does MindTheGapps use Pixel Launcher (or not include a launcher)? Thanks!
 

jeremywh7

Senior Member
Sep 16, 2013
261
127
Indy
Motorola Atrix 4G
Moto X
@jeremywh7, MindTheGApps is a minimalistic GApps package meant for stability, it does not include any form of pixel launchers. For those I'd recommend see what other users use
Ah ok. So the question is whether the issue I'm seeing is due to NikGapps (which I've never used before) or LOS 19.1 (or voodoo?). ;-) I've used Pixel Launcher, though, on countless devices and ROMs (incl A12 on klte). Anyone else tried on the unofficial LOS 19.1, and if so what launcher are you using?
 
  • Like
Reactions: ThE_MarD

skiwarz

Member
Jan 31, 2018
48
9
I have had a few call quality/dropping issues, but I think they are due to cell data connectivity issues as it is not keeping the APN that I have selected (keeps switching to TRACFONE.VZWENTP when it should be using VZWINTERNET).

Aaron Z
My APN keeps switching like this too. Should always be on VZWINTERNET but occasionally (once a day or so) switches to VZWENTP or de-selects all APNs entirely. Then I have to dig down into the settings to set it back to VZWINTERNET.
 

skiwarz

Member
Jan 31, 2018
48
9
Another question/issue I have, seemingly related to [settings -> Display -> Colors]: After every reboot, The color saturation seems to be maxed out, even beyond what "Saturated" gives. Changing the setting to "saturated" and then to "boosted" seems to refresh/reset it to what is normal. But after rebooting, it's back to full-blast.
 

ThE_MarD

Recognized Developer
Dec 10, 2014
3,457
3,929
Grande Prairie
LeEco Le Max 2
Moto X4
Heyyo @skiwarz, tbh I'm unsure if there's a way to essentially disable APN switching, other than modifying the APN configuration and deleting the one you don't want.

As for the color bug? That is a problem with how Motorola's screen calibration is setup... afaik all Motorola devices have that issue and why we eventually ended up dropping LiveDisplay color profile support because upon reboot it would make your phone look like the screen was damaged the colors were so messed up lol...
 

Top Liked Posts

  • There are no posts matching your filters.
  • 9
    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
    7
    Heyyo, a new test build is up! lineage-18.1-20211022-UNOFFICIAL-payton contains tweaks to the brightness during always on display and also some blob updates from the latest Lake build released.

    Mainly need automatic brightness tested in all scenarios (AOD, in light areas, dark areas, while charging in dark areas, etc)


    As for LineageOS 19.0? I have it synced on my PC meow, I just need time to start building it for all my devices
    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
    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
    4
    Important extra links

    Payton Stock firmware:

    Copy partitions link for download can be found on the LineageOS Wiki install instructions for Payton page here: