yashsingh1/xdaforums huggingface dataset:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Heyyo @Wolf.Kuerschner , what version of fastboot and adb are you using? Can you please verify?

fastboot --version

adb --version

The wrong zip file format could mean the download is corrupted, so I recommend trying to download it again and check the checksum.

https://docs.hak5.org/hc/en-us/articles/360049922674-How-to-verify-the-SHA256-checksum-of-a-downloaded-file
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Wolf.Kuerschner:
Hi ThE_MarD!

Thank you for your fast reply!

fastboot --version

fastboot version 31.0.2-7242960

adb --version

Android Debug Bridge version 1.0.41

Version 31.0.2-7242960

I downloaded several firmware files. Here

lolinet mirrors - firmware, software, iso etc.

lolinet mirrors - powered by h5ai

mirrors.lolinet.com

no information regarding checksum is available, right? I tested the zip files with winrar, and it says they are ok.

Truly yours,

Wolf
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Wolf.Kuerschner:
I now understand the problem with the firmware recovery - the zip file contents has another format, and I don't have the recovery files for the installation.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Wolf.Kuerschner:
So, I looked for the firmware flash information and flashed the contents of the zip file. Now the phone trys to boot, I see the Moto logo, hear "hello moto", but then it restarts and restarts and restarts... Strange.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Wolf.Kuerschner:
OK, I used another of the roms for Payton X1900-7, and that boots and I can start WLAN and then start entering my personal data, and then Google App crashes. But at least a Motorola Firmware is starting again. I tried then to install Lineage Os, but it is stuck in the boot loop again. (at least for 1 hour now)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Heyyo @Wolf.Kuerschner , just to check, after flashing LOS Recovery did you perform a factory reset? Coming from stock ROM this must be done as they use a different encryption method
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Tom_Scott:
Hi together,

I would like to kindly repeat my question about experiences of LOS 18.1 together with Magisk.

In case Magisk is not supported by LOS 18.1 how can I made an update (not upgrade) of my older Lineage OS 16.1 to a newer one 16.1 in more easier way? I am satisfying with the LOS 16.1 so far but with one restriction that the camera is stuck sometimes that is a little bit worse.

Thank you

Tom
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] maelopam:
@Tom_Scott magisk works fine for me with this ROM.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Tom_Scott:
@maelopam You mean LOS 18.1, right?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Heyyo @Tom_Scott , LineageOS does not officially support mods likes Magisk and tbh I haven't tried it with 18.1, but I also haven't seen any users saying it doesn't work so I'm guessing it is fine
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Tom_Scott:
Thanks a lot for your answer. I will try it. But there still some questions. As I have flashed 16.1 two years ago I cannot remember all the steps I did. The description at the first page is also a little bit roughly for me.

- There some instructions on the fist page for upgrading coming from 17.1. - Does these steps also valid for upgrading from 16.1 to 18.1?

- Which GApps must I install (Motorola X4) ? - I guess arm64_11.0, right? Or arm_11.0?

- Must I also install this suspicious copy_partitions script again?

Thank you in advance

Tom
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jeremywh7:
Ref: https://wiki.lineageos.org/devices/payton/install#pre-install-instructions

"In some cases slot b can be unpopulated or contain much older firmware than slot a, leading to various issues including a potential hard-brick. We can ensure none of that will happen by copying the contents of slot a to slot b. This step is NOT optional."
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Tom_Scott:
I can translate this into my language but I don't understand. That's why I am asking. What is this script doing exactly?

(a) Does it copying stuff from slot A to B always the script is called?

(b) Does it copying stuff the active slot to inactive, does not matter slot A or B on every single call?

(c) Does it do (a) or (b) every times its calling or whenever a slot is updating

How can I determe the slot I am currently booting? What is when I install all the stuff on both slots manually by TWRP?

Thanks

Tom
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] payton_fischer1227:
Heyyo, new to custom ROMs here. I'm planning to flash LOS 18.1 on my moto x4 XT1900-1 as a daily driver, and I just want to make sure the instructions on LOS official website work as post #195 says the instructions lead to bootloop. Can anyone confirm that the LOS official instructions work or don't work? If they don't work where can I find working instructions? Ideally, I want to use TWRP for the initial install but then have LOS recovery so the Updater app works. Anything I should do to ensure that's the case?

Also- can anyone confirm that the sim card, magisk debloat, and app systemizer works? I need sim for daily use, and since MindtheGapps installs minimal gapps I'd like to uninstall some LOS stock apps and replace them with google apps. If anyone can confirm it works, that'd be great. I really don't want to run into bootloop/other issues- I wouldn't know how to fix them if they arose.

Thanks for the hard work you devs put into this-- so happy there's a community out there to keep this device alive.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@Tom_Scott , you cannot directly upgrade from 16.1 to 18.1 as that is not supported. You must do a factory reset, flash 18.1, reboot to recovery, flash GApps (arm64) and then reboot to system.

You do not need to flash copy-parititons again if you already did when you installed 16.1 as both slots would already have matching firmware.

Heyyo @payton_fischer1227 :) I just double-checked the official install instructions and it is missing a step after flashing LineageOS ROM you must reboot to recovery and then you can install add-ons like GApps and then reboot to system.

The reason is our device is A/B partitioned, so it always flashes the ROM to the inactive slot and then it tells the bootloader to switch to that slot upon reboot. It is only at that point that it is safe to install add-ons.

I'll have to review the wiki page for Payton installation instructions though, so thanks for the heads up!

Sim card definitely works (or we wouldn't be allowed to go official if we had major bugs like that ;) ) but for uninstalling stock ROM apps? Tbh I wouldn't recommend that as installing ROM updates would reinstall them and also the stock ROM looks for those apps sometimes which can cause issues. It would be safer to install other apps and then set those as your default app for telephone/messenger/etc and then just disable the stock ROM app.

As for systemizer? I have no idea what that mod is, sorry. Hopefully someone else can comment on that
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] payton_fischer1227:
@ThE_MarD Thanks so much! Flashed LOS 18.1 with no issues. Just one picky thing- MindtheGapps doesn't come with Digital Wellbeing, any way I can install and enable it? Simply installing an apk doesn't do anything.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Tom_Scott:
Thank you again. What do you mean with "factory reset"? Do you mean at OS level or at Recovery level (I. e. by TWRP)? Does "Factory Reset" mean wipe /data and some other partitions?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Wolf.Kuerschner:
Hi,

yes, I did perform factory resets. I tried both ways, directly from recovery environment, and also from the phone boot environement. But that did not change anything. I just get the LOS start animation, and than nothing happens for a long time, until (after a few ours) a short error message is displayed and the phone reboots.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Wolf.Kuerschner:
fastboot getvar current-slot

if you want to switch slots:

Fastboot set_active a

or

Fastboot set_active b

(fastboot reboot)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] JimDandy68:
Anyone experiencing greater battery drain with the release from the 13th? I happened to put in a new battery at the same time, so have no idea what's to blame. General perfomance is greatly improved, so at least that's a win. Is it possible I need to calibrate the phone to correctly work with the new battery, and if so, what's the best method? Thanks
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Wolf.Kuerschner:
Ok, here are the steps I am performing - were is the mistake?

After installation of Motorola firmware:

Device starts normal, I can enter my data in the Motorola android system.

If I boot from bootloader to “recovery”, I get “No command” (android droid laying on the back with black ! in red rectangle on it's chest)

Press power+volume down, until bootloader

Then in CMD I enter:

Fastboot flash boot lineage-18.1-20210608-recovery-payton.img

Then restart to recovery

LOS recovery starts

I go to Advanced: Enable ADB

Then Apply Update from ADB

In CMD I type and see:

adb sideload copy-partitions-20210323_1922.zip

Waiting until device says [OK]

Then in LOS recovery: Factory reset

-- Wiping data…

Formatting /data…

Data wipe complete.

Then in CMD

adb sideload lineage-18.1-20210608-nightly-payton-signed.zip

serving: “’lineage…” (~47%)

On the device:

Now send the package(…)

Supported API: 3

Finding update package…

Verifying update package…

Update package verification took 42,7 s (result 0)

Installing update…

Step 1/2

Step 2/2

In CMD: Total xfer: 1.00x

Factory reset in LOS

Then

Reboot system

Result:

Endless boot animation, then finally:

Recovery Version 18.1

Active slot: b

Can’t load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device

Try again

Factory data reset

E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory

E:emulated failed to bind mount /mnt/staging/emulated/media/0 on /storage/emulated: No such file or directory

If I switch to b:

Fastboot getvar current-slot

Fastboot set_active a

Then the Motorola boot screen (red circle with red M in the middle) is shown for a long time, and nothing else happens.

So, were do I do the mistake?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] H0ss1:
i think you are missing the install of the Mindthegapps (google apps) after you flash the LOS build and before the first start.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jtnc:
I'm having no issues with the 20210713 release. Definitely much better performance than 20210615. No weird lags when typing. Haven't noticed and real difference in battery life in the last 24 hours vs earlier versions.

I've always been told it may take a day or two to get accurate battery predictions when a new battery is added. Though I don't recall if I noticed that back on my S3.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] JimDandy68:
Thanks for the feedback. Yeah, I'm still trying to determine what's to blame. I'm using FKM and related apps to try to see what's happening during idle time, which is the culprit, and am currently trying to decipher a bugreport using Battery Historian.

Perfomance is truly better, but this battery issue is a mystery. It is also an OEM battery from a reputable source (I'd say clearly OEM, and is labelled as such).

EDIT: Battery Historian is showing that almost all of my overnight battery drain is UNACCOUNTED for. I searched XDA and found this post. I'm wondering if I screwed something up in the phone when replacing the battery. As meticulous as I tried to be, I couldn't locate one of the tiny screws I'd removed in the process. Maybe it's in the phone causing an issue? Odd, because it went back together fine and is otherwise working very well.

FWIW, and for anyone else trying this, my screen (my wife's old phone, and it really came to me this way) had delaminated from the body long ago. The shiny backing around the LCD, part of which holds things like the fingerprint sensor in place, had pulled off of the screen but was still attached adhered to the midframe. In the process of removing the old adhesive, most of that backing is now gone, so I have bleed all around the edges and can see the midfame through areas on the top and bottom of the phone. This is a design flaw of the phone, as far as I'm concerned, but it is what it is.

I may end up taking it all apert again at some point to see if I can find that rogue screw. In the meantime, I think I'll just be powering it off a lot. I'm off on a trip shortly.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] tleydxdy:
Do anyone have this issue https://xdaforums.com/t/official-rom-payton-lineageos-18-1.4220959/page-8#post-85103739 ? I have the mexico version but I flashed it with the android one firmware (this was a long time ago). could that be the cause of this?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Wolf.Kuerschner:
Hi, I thought the Google apps are optional, that is, LOS will run smoothly without the installed Google apps? Therefore I did not install them!

If anybody is installing LOS on Payton from scratch, please check with my listing (see above) of the required steps, and if it works with another device, than maybe my device has a defect? But I never noticed any strange behaviour with stock rom!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Heyyo folks! I just got back from a family camping trip so I'll try to catch up on this thread hehe

@Wolf.Kuerschner , the steps I did before on my payton was...

reboot to bootloader

fastboot --set-active=a

fastboot reboot bootloader

flash fastboot payton ROM (I did the last Google Fi build since mine is a Google Fi unit, but up to you which one you wish to do as long as it is based on pie. The last Google Fi build was XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-6-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC)

fastboot flash boot with Lineage Recovery image

reboot to recovery

adb sideload copy-partitions-20210323_1922.zip

Factory Reset > Format data/factory reset

adb sideload latest LineageOS build for payton

reboot to recovery

(optional, but I did this) adb sideload MindTheGapps-11.0.0-arm64-20210412_124247.zip

reboot to system

Those instructions are pretty much the same as the LineageOS Wiki install instructions for payton, except I explicitly mentioned that fastboot stuff for the first four instructions.

The GApps is definitely optional as you can use LineageOS (or any AOSP based custom ROM should be the same too) without any GApps.

Just as the wiki mentions for payton that the adb sideload 47% thing is an AOSP bug. Then it will usually say something like "failed to read command: success" even though it does succeed.

Sometimes LOS Recovery will show failed to read data/media/0 but that's usually only after a factory reset where it formats the userdata partition and if you reboot to recovery before rebooting to system so the partition isn't set up for use.

@payton_fischer1227 glad to hear it's working good for you! Tbh for Digital Welbeing I'm unsure of sorry... if that is important to you, you can always reboot to recovery and try to flash a different GApps package such as Open GApps using arm64 nano or micro

I also re-double-checked the LOS wiki install instructions for payton and they are correct. I didn't notice the "adb reboot sideload" command which tells LOS recovery to reboot and instantly go into sideload for sideloading GApps so the instructions are safe to use there
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Francesco Libera:
Have you locked fps at 30, maybe?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Heyyo, a new test build is up! Link as always is in the first post. lineage-18.1-20210724-UNOFFICIAL-payton has more mic boost and speaker boosts to check for any distortion issues or if they're good
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] patomovil:
Hi folks, thanks @ThE_MarD for this ROM! I used LOS 16 and then LOS 17 as a daily driver on this phone in 2019 and 2020. They both seemed very stable and functional to me. I read through this LOS 18 thread back in April and saw that things were still a bit rough around the edges for LOS 18. But I see that there haven't been any LOS 17 releases since March, and security updates are important to me. So, what's the summary of the LOS 18 situation right now? What's still rough around the edges? Volume, calls dropped, small details that amount to a few paper cuts? I want to set up the phone for someone who has little patience for things not working, so I'm trying to avoid giving them the phone and then finding out it has rough spots.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Heyyo @patomovil , thank you for the kind words! For 16.0 and most of the work on 17.1 was due to other Motorola sdm660 maintainers as I joined payton right around when 18.1 bring up was happening

For 18.1 bugs? The only big bug is that Wifi Display (Miracast) is broken on official builds. There's a test build with an experimental fix that works but it isn't merged.

As for carrier issues? That tends to depend on APN settings or carrier overlays. If there is any incorrect or missing APN settings or carrier overlays? They can always be submitted to LineageOS Gerrit
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ferrazrafael:
@ThE_MarD Magisk is working fine with LOS 18.1.

Im having a problem that in every update the new rom is downloaded and installed but when Im supposed to receive a notification asking me to reboot the device, nothing happens and if I enter on to the update app again it tells me to download the rom all over again. But if I just reboot after that, rom installation will complete normally. I think this is some kind of bug on the update app. You can look in to it? Or I need to report this elsewhere?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@ferrazrafael hmm, for me it downloads fine and notifies me fine too on both my A/B devices (Payton and Z01R). No idea if Magisk or any battery optimizer mods or the likes can cause issues as tbh I haven't used Magisk on any of my devices in years
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ferrazrafael:
I don't have any battery optimizer installed. There is some way to look if the app is broken somehow? Like a debug log?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] htsmi:
So, I am looking at upgrading to this from an older version of 17.1, it looks promising but a few questions:

I assume that there is no adoptable storage right? In the past I had to build custom with FDE to get this working, just seeing if I will have to attempt that again. I download lots of offline maps and music on Spotify so this is pretty essential for me.

Anyone used this with microG?

Does magisk su work as expected since that seems to be the only option anymore?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ferrazrafael:
Magisk SU works. What is FDE? I coudnt make sd cards work properly with Moto X4 and this ROM. It seams that adoptable storage wasnt supported by the stock rom and maybe that is why it isn't supported in LOS. Link2SD didn't worked as well.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] htsmi:
Full disk encryption. Officially deprecated by Google but it still can be built for legacy devices, at least up to pie. The issue with this device is that the kernel is too old to support adoptable storage with the new file-based encryption. I have a working build of 17.1 from last December with FDE and adoptable storage but it suffers from this bug so I can't really encrypt it securely. I'll share my build if I get it working here.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@ferrazrafael , you can check logcat to see if there's any errors, otherwise you can check your notification settings just in case maybe it is muted?

@htsmi since Payton is stuck on 4.4 kernel, it is still an issue afaik. You might be able to force FDE on only the sdcard like beryllium (Poco F1) does?

android_device_xiaomi_beryllium/rootdir/etc/fstab.qcom at lineage-18.1 · LineageOS/android_device_xiaomi_beryllium

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

github.com

There could be more changes required tbh, maybe BoardConfig includes?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] zerolam:
I can use google pay with magisk + magiskhide props config

Updated: installing mindthegapps will install gpay but you can't find the app of gpay (mind thegapps). you can install gpay from play store.

If you want to config gpay pre-instaled with mindthegapp without installing gpay from play store, you have to long press power button for few seconds > 3 dot near your card> view all

This is the only way i can find to config gpay without installing gpay from play store.

If some one finds another way please let me know.

Thank you so much
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] dashingdon:
Thanks for all the hardwork on the port. I flashed on to my google fi android one variant . Except outgoing calls and SMS on cellular everything else is working.

What are the APN settings I need to apply ? If anyone can guide that would be awesome. I am in the US , google fi. thanks in advance.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] zerolam:
I tried gcam by Wichaya and others

Real time google lens suggestion doesn't wok

I have to use Google Lens after taking a photo

how to fix this?

thank you so much
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] dashingdon:
Just posting an update on my own request.

For some reason, (New) SIM did not get activated properly on Moto X4. I reactivated FI SIM in Nexus 5X and re-inserted back into MOTO X4. Everything is working flawlessly. Thanks.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] zerolam:
@ThE_MarD

issue report

Brightness Control issue with video and log

brightness goes up to the highest when I slide to the end of the left

---------------------------------------------------------

another issue:

setting > system > buttons > when [enable on-screen nav bar] is disable >

home button (fingerprint)

"double tap action" works including "turn screen off"

"long press action" doesn't work

thank you so much
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] andyrtr:
I'm running into a minor but annoying issue since 18.1 update: Auto-brightness drops to a much too low value from time to time. It works at "day time" but when the redshift kicks in at sundown it shift to a minimum brightness even at relative bright ambient light. And the minimum seems to be much lower than on 17.1 so I have to lift it up to aprox. one 3rd of the slider but it sets it back to minimum from time to time again.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] st0nedpenguin:
Yeah this has been happening with every 18.1 build for me. Small problem but still kinda annoying.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] H0ss1:
anyone with issues during calls? any counterpart on my calls can't hear me well.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] maelopam:
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.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] freed_de:
@H0ss1 @maelopam The volume issues were fixed in a release in early August. Try an update.

Best regards Freed
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] H0ss1:
Hi, im actually up-to-date to todays build but the issue persists. its not like the volume is low, its more like the voice/sounds are incomprehensible