yashsingh1/xdaforums huggingface dataset:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] st0nedpenguin:
Yeah I let the stock updates install all the way up to the most recent Pie, then went straight to LOS with no copied partitions. I think I read somewhere that Motorola themselves actually started using the A/B system for their own updates.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] xdan8r:
Greetings. Just flashed los 16 on xt1900-1 coming from stock+magisk oreo and am having a problem where locking the phone (either via power button or after screen sleep) causes it to become unresponsive and I have to hold down the power button to reboot. Has anyone seen this before and/or know the fix?

When upgrading, I first went to stock pie using the latest RETUS zip and the flash-all.sh script in another thread. Then booted to verify it was pie. Then booted twrp and flashed the copy partitions and los 16. It was all going great until the screen locked. I know from previous phones that some of the lock screen stuff is in one of the random .bin files that was part of the flash-all step so I assume I have an oreo/pie mismatch in one of those files. I still haven't fully wrapped my head around the a/b slot stuff so don't know if some of the files might be different in the two slots. Is there some way to find out if the installed versions of all those .bin files are correct?

Any suggestions to fix this lock screen problem would be greatly appreciated. Thanks!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Randy Power:
I'm just a user, so I may get some things wrong here...

The "can't awake from idle mode" seems to be a bug introduced in build 20190925. I was hoping it was fixed in 20190927, but that does not seem to be the case.

0927 includes this change: Revert "lpm_levels: Return true for CPU WFI mode allow check"

... which says: "Reason for revert: Breaks payton idle mode" (https://review.lineageos.org/c/LineageOS/android_kernel_motorola_msm8998/+/259442/)

I'm holding on 0923 for my daily driver phone, but I have a second one to experiment with. I've tried a clean install of 0927 and then also using the built-in updater to download and 'update' to 0927. In both cases, the lock bug remains.

If I can do anything else to troubleshoot, let me know.

Edit: Unfortunately the built-in updater and LOS Recovery do not allow installing an older version, so once on one of these broken versions, I could not downgrade. I ended up using TWRP (launched with 'fastboot boot my-trwp-image'), did a full wipe/reset, and reinstalled 0923. If there's a way around this in the future, please share.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] exzombie:
Is it not possible to just switch to the previous slot using TWRP? I didn't have a need to try yet, it would be good to know before I need it …
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Randy Power:
As far as I know, TWRP has no controls for switching slots. Maybe I'm wrong, but I don't see it.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] MeowDotEXE:
Good to know that I'm not the only one with that issue. Thought I screwed somehting up. I'll try to downgrade to 0923, I've already gone 2 days with an only semi-usable phone.

EDIT: Also, TWRP can't seem to decrypt /data anymore. Any idea as to why that might be?

---------- Post added at 08:01 AM ---------- Previous post was at 07:54 AM ----------

It's in the reboot menu.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] xdan8r:
Thanks for the info. At least there may be some hope of it being fixed soon. Can't believe I chose to upgrade on exactly the day the build was broken!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] p-ho:
I can confirm this issue.

I've tried twrp-3.2.3-1-payton and twrp-3.3.1-0-payton. Both failed to decrypt /data.

(Using the PIN-based encryption)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] t3ch42:
Trouble with ota update.

Anybody had issues with the ota updates lately? Have not been able to update for the last few releases. Would talk forever to install close to 2/hours or so. After rebooting, would bootloop about 19 or 15 times until it timed out I guess and go to the working slot.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Randy Power:
If your problem started with 0925, then it's the idle/lock bug we've been discussing.

I started looking at submitting a bug report for it but I haven't done that before for Android, so it's going to take me a little time to set up and grab the logcat.

Someone submitted a bug report a couple of days ago but I think they gave up after not getting the device (payton) set right and it being rejected repeatedly. https://gitlab.com/LineageOS/issues/android/issues/1226
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] sevenrock:
https://gitlab.com/LineageOS/issues/android/issues/1227
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Randy Power:
A family member with a different device has the same symptoms since 0925: Moto Z2 Force.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] t3ch42:
If that is the case, not sure the two are related. I'm on the 9-19 build.

Can I sideload the image to force the install instead of installing online through the ota?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Randy Power:
Agree. And I don't think you can force by side loading but don't take my word for it.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Randy Power:
Early indications are that the idle bug freeze/boot loop problem is resolved.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] xdan8r:
Yes, the 9/29 build fixed it for me. Looks like they reverted a bunch of stuff from the 9/25 build.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Online Gravy:
I updated to the 9-23-19 build and everything is working except wifi. It either connects with an x or it vanishes all together
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] t3ch42:
Well, you were right. Side loaded and still had the same issue. Rebooted and continued to reboot quite about 9 or 10 times. Like I said, I'm on the Sept 19 build and can't update.

Does anybody know of any issues with magisk lately?

Stuck...
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Randy Power:
0929 and 0930 have resolved the idle/lock issue but ... Reboot from a running device throws my device into a boot loop. This happens from the Power button+reboot button and also from the Updater after downloading+installing an update. Power off and start works fine, and also moves to the updated slot if I just ran Updater.

Edit: oops I meant to add that I know you had a different problem than lock/idle, but shared in case it's helpful. Maybe you could update to 0929 or 0930.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] t3ch42:
Thanks! That worked like a charm! Was able to update to the 9-30 image. Hope that takes care of the issue but your symptoms seem quite similar. Will report back after next ota attempt.

Update: the reboot issue us still present, but as described, can turn off and switch to the installed slot for updating firmware. If the phone begins to reboot, place the phone in bootloader mode by holding volume down and power until the screen shows. At that point power down and then power on from off.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Randy Power:
Glad to hear at last have a workaround.

FWIW -- I've updated both of my X4s to 1002 and now both reboot without looping. [MENTION=4796095]t3ch42[/MENTION], I'm curious if this new build will resolve your Reboot symptom too.

Hooray and thank you, devs!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] t3ch42:
No joy yet...?

On the 10-2 rev and still have the reboot issue. Glad that its working out for you. Means it will probably be soon for me too!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Randy Power:
Bummer. At least you have a workaround.

Did you update with the Updater or manually download and install via (Lineage?) Recovery?

I updated both of mine via Updater.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] t3ch42:
I updated via updater. Get this. Tonight with the 10-3 update it ended up soft bricking with no bootable a/b slot.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Randy Power:
Oh no! What an awful stretch you're having.

I just updated seamlessly to 10-03 on my backup device. But with your experience, I'm nervous to do the same on my daily driver.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jw243:
Yesterday, I updated OTA to the MicroG-Version from October 3rd. I had the bootloop upon restart, too, but I could resolve it by booting into bootloader mode and power it off from there. After that, the phone would boot normally.

At first, it seemed to work well. However, I inserted a SIM-card, left the house and was on LTE for the first time. Suddenly, the phone froze, restarted and went into bootloop again. This happened over and over again. It also happened later today, when I was on Wifi again.

It seems that the issue has not been resolved with the last update, at least for me.

I hope, the next update will have this issue resolved.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] t3ch42:
Well, all was not lost. After a mad dash for information and reinstallation of drivers, I came across a post on reddit that was helpful. I was able to flash the gpt partition and that corrected the issue of no bootable a/b slot. I booted to twrp and changed the slot to b from a and the x4 booted to the 10-3 image.

Still curious why I can't reboot. Will need more time that I don't have...
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Online Gravy:
try flashing the latest stock rom from the bootloader

https://xdaforums.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348

https://mirrors.lolinet.com/firmware/moto/payton/official/RETAIL/

then boot twrp from bootloader and continue from there
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] sevenrock:
reverting this commit fixed the bootloop for me:

https://github.com/LineageOS/androi...mmit/044c32875f34a724ee732930106638cd79e94673
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mkfsf2fs:
Hey,

after some time I have looked at the FM radio issues again. I found that currently there is a merge request in the LineageOS review system.

FM: Add backward compatiblity support for oreo FM configs

It seems promising but has been in review for about a month now. I wonder whether it will be merged eventually.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] scott8281:
Does this reboot issue only occur when updating through the updater? I'm currently still on the August 27th build. I've been thinking about updating but I always ADB sideload. Are there any major changes in the last month that would even be worth updating for?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] t3ch42:
I can't speak for everyone that has dealt with the issue, but it occurred both through sideloading and through the updater. My issues started when I tried to update from the Sep. 19th update. Ever since I tried to update from that version, I have had issues with the reboot bug.

But there is a workaround for it discussed a few pages back if it does occur. I hadn't seen too many people discussing the issue; may be safe to update...

As far as reasons to, not sure if anything too spectacular has been added.

Good luck!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Stillwinds:
Hi, I've just freshly installed the latest build of LOS 16 on my moto x4 XT1900-2 (the nightly build released yesterday Oct 7). I also installed MindTheGapps (Jun 15 2019 version). Not rooted.

Everything seems to be working well, except that whenever I call someone on speaker phones (Duo, Messenger video calls) the recipient hears their own voice echoed back at them.

I did some searching and I can't seem to find an a definitive answer. I don't have a case that blocks the microphones. I tried using earphones and the echoing disappears from the recipient. So it must be that the noise cancellation isn't working? I never had this an issue in the Motorola stock ROM.

Can anyone point me to a solution?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Richy19:
Is it possible the bootloop issue only occurs when updating from a version prior to 0925? I was on the 23rds nightly (last good one afaik) and updated to today's and got bootloop, yet people saying they have fresh installed from October builds and updated don't have this issue?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] st0nedpenguin:
Updating from the build from the 23rd mongled my install so bad I had to clean install everything. I haven't updated since, this is my only phone and I can't afford for it to be unusable.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] frabe8378910:
I can also confirm that updating from 09/22 led to a boot loop and the phone failing back to the former slot. I manage five moto x4 which all were on 09/22, have been updated to OTA to 10/xx and led to a boot loop.

One the first update I shut off the phone during boot loop, which led to a soft bricked phone. I reflash stock rom and flashed a fresh 10/02 lineage to recover. For the second update some days later, I just let the phone reboot long enough and it started "normaly". So I though the update worked in the end. I did not check the installed version because I was busy with other things, but started to update all other phones.... :eek:

After the last phone had successful booted, I finaly DID check the installed version and recognized that the boot loop does not end with a successful install. Instead the boot process timeout and fall back to the former slot. :laugh:

So far all phones have been OTA updated successfully several times over last month, there must be something wrong with lineage versions later then 09/22.

I did not have enough spare time 'till then, to test an update on one phone a manual/different way.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] noogi:
I also noticed sporadic boot loop when restart phone.

ROM from 07.10 and clean install
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Skeeterdrums:
Also ran into this intermittently. I'm running the October 9th nightly.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jw243:
I just tried to install the brand new MicroG version from today (2019/10/10), rebooted into sideload and sideloaded addonsu. Still bootloop upon reboot!

Powered phone down, went straigth into TWRP, wiped the phone and installed MicroG version 2019/09/19 and addonsu. No Bootloop! LineageOS starts normally.

Hence, the problems are still not sorted out!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] st0nedpenguin:
I really don't wanna sound like I'm whining or ungrateful or anything, but it's kinda wild when issues like this pop up and are neither addressed nor acknowledged for so long.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jw243:
Just to check, it`s not a problem of the MicroG version. I installed the newest official nightly (2019/10/10). Same behaviour! Bootloop upon first boot after installation!

I revert back to MicroG version 2019/09/19 until things are sorted out!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] uvo23:
I've got the 9/30 nightly. Installation worked but when I restart I get a bootloop.

To get it fixed I have to press and hold 'Power' an 'Volume down' to get to the bootloader. Then I do a normal start. It seems like switching to the bootloader changes the slot.

There is no bootloop if I shut down the phone and power it up.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ruser453:
I'm new to installing custom ROMs and I've wanted to get a phone with LineageOS. I tried to do this on the Moto G7 using the unofficial one on that XDA thread, but I could not get it work no matter what, so I have a few questions regarding the install on this phone to ensure I do it successfully this time:

1) Is the installation procedure in this case install/update to stock --> copy partitions --> Wipe and Format Data --> Sideload LineageOS onto Slot A --> Reboot into recovery (Lineage Recovery or the installed TWRP) --> Flash other stuff after rebooting into recovery? When I tried this on my Moto G7, Lineage would ALWAYS fail to overwrite the stock android or there would be no OS installed and this happened even when I followed this verbatim and even when I tried installing the stock and lineage to both slots. I want to be clear about the install procedure and which slots to install to this time to avoid those mistakes.

2) Is there ever a point in the install where I have to change slots manually or install the stock rom to both slots? I could not get a consistent answer to this from the Moto G7 thread or in other threads when I last tried this.

3) Does TWRP 3.3.1-0 cause issues with LineageOS? I've heard from some people that it does. If so, which version works best?

4) The Firmware in post 2 appears to be different from a stock rom which is much larger. Am I supposed to flash that before I do anything, am I supposed to flash the stock first, or can I just do the partition copy after updating fully?

I'd like to clarify these things before I try this again to avoid the same problems I ran into last time.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] sevenrock:
This commit will fix the bootloop:

https://github.com/sevenrock/androi...mmit/c1398643ceb41da90efbe17dd0cfede330c97228
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] noogi:
Still no changes according to https://download.lineageos.org/payton/changes/

I hope some work is going on..
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] sevenrock:
Fix was committed several minutes ago:

https://github.com/LineageOS/androi...mmit/50c838ef6b0c136de467fd435070582ba05e2ec3

You should see it in the coming days, please test the upcoming build including the fix

and report back whether the bootloop is fixed or not, thanks.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] st0nedpenguin:
Many thanks for getting this one fixed. I guess I can safely update again.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] leetripper:
The bootloop is fixed for me. But I had to go back to OpenGapps 20190921. With newer Gapps installed, LineageOS doesn't boot, boots into recovery instead.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] noogi:
try Mind the Gapps..
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] leetripper:
I know. I thought, it might be useful for people, who use, OpenGapps...
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Skeeterdrums:
I took the update (dirty flash) but can't get Google services to work. Any way to fix this without a full reflash?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] leetripper:
You can wipe data for Google Play Store and the Google Play Services app. Then restart your device...
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] frabe8378910:
Just did an update of magisk to 20.0, rebooted and did an OTA update to lineage 13.10.2019. I did not do anything else - just OTA, no clean up, no clear cache ...

This went through without any hassle. I did check the version and it was indeed 13.10.2019. So I did the same procedure to 3 more motoX4. All went smooth.

So I'd say, boot loop seemed to be fixed.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] dyb-:
Do you use OpenGApps or MindTheGApps?

E: Nevermind, did an OTA Update to 14.10.2019 by my own. Everything worked fine (and in my perception even smoother than before). Using OpenGApps is no trouble for me.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] SB00:
Are you guys updating the nightly from the phone, or downloading the zip and flashing through recovery? I just flashed Lineage this last weekend and I noticed I had a notification about the update but didn't know if there was a certain way I was supposed to install it.

Same goes with Magisk. Can I update via the app, or do I need to flash the zip through recovery?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] frabe8378910:
I did the magisk update with the magisk manager and direct install. For lineage I just did an OTA update directly on the phone. I normaly do an OTA update every 2-4 weeks.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] renanmarcs:
I had an issue that 4G (LTE) connectivity is enabled automatically and this cause unexpected costs in my bills, I need to stay always using 3G (WCDMA) to avoid this issue. I've already enabled WCDMA only in Data mobile settings and disabled "Mobile data always active" in developer options. Anyone here has this problem or know how to solve it?

I've found an option called "Smart network switch" when searching in settings, but when I click on this option does not open the desired screen to see the option. I suspect that could be this thing... Anyway to enable this settings by build.prop or something like that?

I'm talking about this configuration: https://devicehelp.singtel.com/sams.../turn-automatic-use-of-mobile-data-on-or-off/
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] oz42:
OTA is broken for some time, the updater crashes after downloading. So I can only update with recovery.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] math_rossetto:
My wifi and mobile network are not working after flashing the rom and i have the slightest idea of why... ?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] timtaw:
I have very similiar questions.

What is the correct sequence?

Fastboot Copy Partitions Zip

Fastboot TWRP

In TWRP: Wipe -> Format Data

In TWRP: Wipe -> Advanced Wipe -> Check "System" only

In TWRP: sideload the LineageOS zip

In TWRP: Reboot System

Repeat Steps 3-6 in order to deal with Android A/B

Install firmware files.

Is that correct?

For me, TWRP can't decrypt the partitions. Using twrp-3.3.1-0-payton.img.

I'm puzzled by that either. I already did install LineageOS without installing the firmware drivers first. Now sound, video and fingerprint aren't working because of missing firmware files as described by a few people here on this thread. Can I just flash the firmware files and everything will work or do I have to go back to Stock ROM, flash the firmware files, re-install LineageOS and lose all settings?

When flashing the firmware drivers, which ones do I have to flash without overwriting LineageOS and/or losing any settings? The firmware file from post #2 contains these image files:

abl.img
bluetooth.img
cmnlib64.img
cmnlib.img
devcfg.img
dsp.img
dto.img
fsg.img
hyp.img
keymaster.img
logo.img
modem.img
pmic.img
prov.img
rpm.img
storsec.img
tz.img
vbmeta.img
xbl.img

Cheers,

Robert
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] st0nedpenguin:
The weird thing is, for the longest time it worked for me but now it doesn't.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jw243:
If you remove the screen lock (PIN, Pattern, Fingerprint...) before booting into TWRP, then TWRP is able to decrypt the data partition.

It is, however, a bit tedious to scan your fingerprint(s) again afterwards.

---------- Post added at 02:43 PM ---------- Previous post was at 02:27 PM ----------

Has anyone got a stable system consisting of the following components?

LineageOS 16

AFWall 3.1.0

Activated Private DNS

Inserted SIM / using mobile data

My system crashes constantly with this combination using a late September / early October built of LineageOS.

If your system is stable with these components, which version of LineageOS are you using?

Thanks!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] st0nedpenguin:
That's not even guaranteed either. If I remove mine it still won't decrypt in TWRP.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Randy Power:
This has been my experience as well.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] st0nedpenguin:
It's extra weird though because for the longest time I could just input my PIN in TWRP and it'd decrypt fine, then it got to the point where I had to remove it to decrypt, and now even removing won't let it decrypt.

And I've been running the same TWRP release the entire time.