[DISCONTINUED][ROM][PAYTON]LineageOS 18.1

[skiwarz]

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...

I think I found the appropriate apns-conf.xml settings to change... 3 days and no issue, I'll post when I'm sure it's fixed...

Is there anything I need to do to disable the livedisplay stuff? I'm on the April 5th build, and it's still there, able to adjust it and everything. I have all the settings under "LiveDisplay" turned off.

 

[ThE_MarD]

@skiwarz unfortunately all you can really do after a reboot is to change those color profiles to get your color saturation to the appropriate levels again as the bug is with Motorola's proprietary blobs

 

[IronTechmonkey]

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...

Indeed. Here is how it looked on a Moto G7 Power:

.

In that case, toggling color saturation back and forth between values fixed until next instance. IMO we are not missing much do to the fix in LOS, in fact I'm glad to have the option to be free of dependence on location fix for what is now called Night Light in stock. BTW, thanks for your continued work in development.

 

[Althaea]

Hi all! I would like to finally (…) update my Moto X4 from LineageOS 16 to a current version.

Q1: Would I need to go back to the stock ROM to get updated firmware?

Q2: I _think_ I had updated from 15 to 16 before that, but did not update any firmware for that. How do I find out which firmware version I have, and whether it needs updating?

Q3: Also, the 'stock rom' link at the start of this thread gives a 404... so if I need it, I have no idea where to get it... Would the official Motorola resetting software work? (bootloader unlocked, LOS 16 installed)

Thank you!

 

[IronTechmonkey]

Hi all! I would like to finally (…) update my Moto X4 from LineageOS 16 to a current version.

....

Q3: Also, the 'stock rom' link at the start of this thread gives a 404... so if I need it, I have no idea where to get it... Would the official Motorola resetting software work? (bootloader unlocked, LOS 16 installed)

Thank you!

Speaking only to the quoted portion above, I have used the Motorola RSA to reimage several devices including a Payton device on which some previous action caused it to register no version of baseband and which had issues with fastboot. On all devices including that problematic payton the reimaging was successful, and I was able to grab the boot file from the downloaded material in order to root with magisk. In case you need to or just one to start from latest stock, here is sd_shadow's thread for the Moto RSA. https://forum.xda-developers.com/t/...ant-lmsa-motorola-lenovo-only.3951714//unread

 

[skiwarz]

@skiwarz unfortunately all you can really do after a reboot is to change those color profiles to get your color saturation to the appropriate levels again as the bug is with Motorola's proprietary blobs

For what it's worth, I spent all day trying to find the source of this, I got as far as determining that it only occurs with a full restart. Ie doing "adb shell am restart" does not cause the color/saturation issue...

 

[Francesco Libera]

My power button stopped working many months ago. I was able to boot up the device trough fastboot using "volume down button + charging cable" combination. Today even the volume down button stopped working and I forgot to charge the phone because I'm an idiot . It died. I've only had bad experiences with repair shops. If no one else has any ideas, I would like to thank from the bottom of my heart everyone involved in this project, starting from Marc, Erfan and the Lineage Team for supporting this great phone that I loved till the end.
RIP

 

[ThE_MarD]

Heyyo @Francesco Libera , oh noes! Buttons tbh should be pretty cheap if you're willing to open up the device and fix it yourself tbh, that? Or open it up and short out the cables to the button that's broken in order to boot lol... If you're lucky?

The button might just need to be cleaned with isopropyl and a cotton swab if maybe there's crap stuck in it? Tbh I suspect that's why my volume down button on my Payton sucks and I have to massage it the right way in order to make it register, so it could be the case for you too? It seems Payton isn't a very good design for keeping crap from getting caked in the mics, speaker or buttons lol oof

 

[simonfunk]

Hey all, did my first Lineage install (18.1) on my Moto X4 and everything seems to work fine except the GPS. This was a few days ago and I've triple checked all related settings and such and given it plenty of time to come up, but OsmAnd still says "position unknown" and camera images have blank GPS info in their EXIF.

Is this a known issue? Or, any suggestions for further diagnosing it? (I searched a bit and didn't find anything definitive, some hint it might be a new problem with 18.1 but unclear how broadly or if there's a solution.)

 

[ThE_MarD]

Heyyo @simonfunk , there's a chance your device is on the incorrect device firmware. I'd recommend flashing back to the latest stock ROM build for your variant and then trying to switch to LineageOS again

 

[simonfunk]

Heyyo @simonfunk , there's a chance your device is on the incorrect device firmware. I'd recommend flashing back to the latest stock ROM build for your variant and then trying to switch to LineageOS again

This is the first non-stock install I've done on this phone, so it was the stock ROM already, unless I'm misunderstanding your suggestion?

 

[ThE_MarD]

@simonfunk , hmm, well if you submit logcat to this thread we can double-check, but usually something like GPS not working is device firmware or persist partition.

You can try to just download the stock ROM and then flash the persist.img to your persist partition and see if that fixes the issue? The link for stock ROM is in the second post of this thread.

Just to check too, you were on stock ROM Android pie before coming to LOS?

 

[simonfunk]

@simonfunk , hmm, well if you submit logcat to this thread we can double-check, but usually something like GPS not working is device firmware or persist partition.

Want me to grep any particular lines?

You can try to just download the stock ROM and then flash the persist.img to your persist partition and see if that fixes the issue? The link for stock ROM is in the second post of this thread.

If you mean this link, it's giving 404 atm: https://mirrors.lolinet.com/firmware/moto/payton/official/

Wouldn't overwriting persist.img permanently lose some relevant hardware data (calibration values and such)?

Just to check too, you were on stock ROM Android pie before coming to LOS?

It's possible it was (stock ROM) Oreo, now that you mention it (but unlikely anything before that, based on purchase date--Feb 2018). It was my wife's phone, and she doesn't recall what the last update was. Would that be enough to cause problems?

 

[ThE_MarD]

@simonfunk you can search your logcat for anything related to GPS and persist too and see if there's any errors there

It looks like they relocated the old device firmware to another server, so I updated the link in the second post and here it also is:

lolinet mirrors - firmware, software, iso etc.

lolinet mirrors - powered by h5ai

mirrors-obs-2.lolinet.com

Persist is a read-only partition and tbh I've reflashed persist on quite a few of my devices after breaking it when trying all kinds of changes over the years, so it is safe to overwrite. If you want? You can make a backup image of it before you flash a new image to be safe.

Here's the terminal command to make a backup of it:

dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persistbackup.img

Our device tree and vendor blobs are based on pie for most of the important payton blobs, so odds are yeah it may not work correctly with oreo blobs

 

[simonfunk]

Thanks, will pursue!

 

[simonfunk]

After re-installing stock Pie and then re-installing Lineage, I finally solved the problem by installing a different version of OsmAnd! And I was using Telegram to file-transfer (not image-transfer!) my camera images to my linux machine to read the exif gps data, and it turns out Telegram strips (only) the GPS data from exif, even when sending them as raw files, not images(!). So, a confluence of my own issues, not a Lineage problem. Sorry to bother y'all, thanks for the help, and maybe someone can learn from my mistake.

 

[Dukenukemx]

Can anyone help I tried updating my Moto X4 to a newer version of LineageOS 18.1 and now it just boots into TWRP.

 

[Dukenukemx]

I solved my problem by going back to TWRP 3.5.2. DO NOT upgrade beyond this otherwise it just always boots into TWRP. I ended up installing 19.1 instead of this rom.

 

[ThE_MarD]

Heyyo, Glad to hear you got it solved @simonfunk! Enjoy!

@Dukenukemx it seems the prebuilt bootctrl HAL and libgptutils to try and maintain compatibility with stock ROM is meow causing issues. I have a test build of TWRP for payton based on TWRP-11 branch and source-built bootctrl HAL and libgptutils.

[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

 

[Althaea]

Speaking only to the quoted portion above, I have used the Motorola RSA to reimage several devices including a Payton device on which some previous action caused it to register no version of baseband and which had issues with fastboot. On all devices including that problematic payton the reimaging was successful, and I was able to grab the boot file from the downloaded material in order to root with magisk. In case you need to or just one to start from latest stock, here is sd_shadow's thread for the Moto RSA. https://forum.xda-developers.com/t/...ant-lmsa-motorola-lenovo-only.3951714//unread

Hi! Thank you very much for your reply and the link! (and sorry for the long delay...)