yashsingh1/xdaforums huggingface dataset:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@jtnc I'll try to get time to check it on my Payton then. When I was trying it out, it did work on mine on my test builds and tbh I posted test builds here and never got any feedback...

@aczlan, I'd recommend using a clean electric toothbrush to clean your microphone ports. It's probably the noise cancelling mic is blocked if you're saying only calls are affected. There's been other users in this thread reporting that same issue and saying this resolved it for them. Same for your speaker as it could be clogged causing the volume to be weaker too
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] aczlan:
Interesting, it looks clean, I will see if there is anything plugging it up.

Aaron Z
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
I second that notion, and this device is prone to such issues. In fact I would be active in this thread had I not ruined the bottom mic with a toothpick while cleaning it. That microphone facing toward the front of the phone exposes it to everything leaving a person's mouth in addition to their voice and exposes it to dust and detritus when the phone is placed face down while the microphones on the bottom edge don't have that problem. Phone calls were affected but apps which used the top microphone were able to pick up sound. Anyhow, that's just a long winded +1 for gently cleaning the microphone.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Heyyo @IronTechmonkey, my condolences on your mic, Is microphones expensive for Payton in your country?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] aczlan:
Well, I took it out to the garage and blew across the mic hole with compressed air and it seems to be working much better now.

Weird that it worked fine with the stock OS but to be fair, it sat on my desk for a few months since it was last used, so who knows how much crud it picked up there.

Aaron Z
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
Not particularly expensive but I wasn't ambitious about that because I had also broken the glass back which I was never fond of. It would though be a perfect device on which to practice replacing a microphone so maybe I will do that. It's a very nice device and I'm glad there is still some interest in development for it.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@IronTechmonkey there definitely is interest since my payton is still ok. I plan on LOS 19 for it once I get it to boot on at least one of my devices and then use that knowledge to get the rest to boot including payton lol...
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] htsmi:
Anyone had issues with random reboots? I think it may have something to do with WiFi tethering but it doesn't always seem to happen when that's on. Like a lot of Android stuff I can't find a good guide to troubleshooting it, but it has me worried and I don't know what to do other than wipe data and I don't want to do that if it's not going to fix it. Last device I had (potter) never did this, and it didn't even have official LineageOS.

I am using the Lineage4MicroG build with Magisk for root.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jeremywh7:
It's been over a month since I had a random reboot, and I do seem to recalll I'd been using wifi hotspot mode at that time. I had to manually reboot a couple weeks ago because the phone was getting really sluggish, which is actually the first time I'd had that happen. My previous phone (Nexus 5X) would have to be rebooted every few days because of that. Since installing the Jan sec patch build last Tues though, everything has been working great.

I guess something else you could try is to run w/o Magisk (I don't use it).
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] anas214812:
Device restarts once I put the Sim card..
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] rodrigopitanga:
Check this comment. Worked for MicroG-LineageOS 18.1 too.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] rodrigopitanga:
Please check my comment above.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] htsmi:
Thanks, my firmware is the most recent pie, though that may be a helpful reminder for others who have missed that. The thing is I do not have /proc/last_kmsg or /sys/fs/pstore/console-ramoops files, I do have a /sys/fs/pstore/annotate-ramoops-0 file but is empty. But maybe that is because I manually rebooted recently. I'll have to check it to see if has anything next time the reboots happen. Otherwise I can connect with ABD and try to get it to crash then, but it's pretty random.

And yeah I'd rather not use Magisk at all... but with LineageOS abandoning their su, I kind of need it or I couldn't even be doing this debugging, let alone use a DNS adblock or have any way of backing up my apps.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] htsmi:
I was curious, @ThE_MarD , if you know if the speaker volume levels are compiled in or if they are somehow editable with root. I can't seem to build LineageOS anymore with only 8GB of RAM that my computer has. I have a second payton running the last stock and the speaker is noticeably louder on it, and it's one of the few usability issues left for me as I sometimes need to use the speakerphone or show people videos and the volume is still just too low most of the time.

Question 2: Is there a specific firmware you recommend we use, I am using XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-6-13 but that version wasn't released for all the variants so are you using that or an earlier one for the source of the blobs?

Also I did want to say thanks for getting the adopted storage working, it seems to work fine, I just haven't switched back over to that setup on my main phone yet since I don't need the extra space with the 64GB model.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
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

History for audio/mixer_paths.xml - LineageOS/android_device_motorola_payton

Contribute to LineageOS/android_device_motorola_payton development by creating an account on GitHub.

github.com

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
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
ugh bad internet multi-post
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jw243:
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.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Francesco Libera:
I broke the camera so I'm always in marco focus distance 🤣
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] exzombie:
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.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Rootmaster906:
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?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jeremywh7:
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
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Rootmaster906:
Where? I don't see it
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Rootmaster906:
Here is current baseband
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Rootmaster906:
I think most current radio is .29
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jeremywh7:
Release lineage-19.1 lineage-19.1-20220322-UNOFFICIAL-payton - lineageos-for-payton - OSDN

Release lineage-19.1 lineage-19.1-20220322-UNOFFICIAL-payton - lineageos-for-payton #osdn

osdn.net

My baseband is M660_7045.36.01.100R
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
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)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jeremywh7:
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. ]
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@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. :)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jeremywh7:
Ah ya, sorry... fixed the double mention. :-)

What launcher is your payton using? Does MindTheGapps use Pixel Launcher (or not include a launcher)? Thanks!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@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
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jeremywh7:
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?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] skiwarz:
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.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] skiwarz:
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.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
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...
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] skiwarz:
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.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] 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
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
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.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] 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!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
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://xdaforums.com/t/rescue-and-smart-assistant-lmsa-motorola-lenovo-only.3951714//unread
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] skiwarz:
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...
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] 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
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] 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
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] 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.)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] 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
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] simonfunk:
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?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] 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?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] simonfunk:
Want me to grep any particular lines?

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)?

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?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] 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
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] simonfunk:
Thanks, will pursue!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] 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. :)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] 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.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] 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.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] 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.

https://xdaforums.com/t/official-tests-twrp-for-the-motorola-moto-x4-payton.4197459/
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Althaea:
Hi! Thank you very much for your reply and the link! (and sorry for the long delay...)