yashsingh1/xdaforums huggingface dataset:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Sebalexx:
Confirm this for the 1900-7 here, after knowing where to find the settings... ;)

Didn't test with real notifications, but while changing settings the LED is flashing like it should.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Quantumstate:
Looks like Lineage uses Trebuchet. But there is no way in it to save your settings, like there is in Nova.

It's a real hassle to rebuild my 5 screens with all the apps in the right places without backup.

Also there doesn't seem to be a way to set which is your home screen. In Nova it's long-press, and it's there in the context menu.

How can these features be missing?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
With apologies for a bit more OT, I have the device in hand and would like to share a few details about it which I've not seen described elsewhere and which may at least indirectly help development.

- Pre-installed Android 8.1.0 June 2018 Security,

- Upon connection to Wifi an inefficient sequence of security updates is being applied, then Pie.

- Has physical LED (not tested) visible by shining flash-light at particular angle on top bezel very close to the left end of the speaker

- SIM/SD both in one flimsy carriage which ejects from top with press of provided poker.

- Installed OS has so little to play with, damn the guarantee, onwards to LOS in fairly short order.

- In some light the back cover seems as red as a Baboon's bum, and in other light as blue as a Mandril's fanny.:silly:

Again, apologies for the off topic but, as was the case for me this device is a likely target for people who have seen their mid-to-low range devices bumped off of the LOS build roster (all 3 of my devices), so I share this in hopes that it might drive interest in the device and ROM. Also at least I'm not just grousing about things I don't like which the developer could not do anything about even if I had provided reasonable details and or logs in the correct thread.

:rolleyes:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
I'm preparing my first flash of LOS 16 after allowing stock to update as much as possible (Pie - Feb 2019 security). I had already found and am planning to follow the instructions in post 2. Thanks for specifying where that sits, at the beginning, of the workflow. I do have a question: I've never had to do that in LOS 14 through dozens of flashes across 4 devices and a few in LOS 15. The reason for it must be more specific than "On-disk partitions in Lineage are different than those of stock". Is it only applicable to LOS 16? or only to devices of this generation? or specific to this model?

---------- Post added 18th March 2019 at 12:24 AM ---------- Previous post was 17th March 2019 at 11:39 PM ----------

I must be missing something. If TWRP and copy partitions have been installed/flashed prior to this step, and the ROM, Gapps and SU are to be installed/flashed in later steps, specifically what is being flashed here at step 3?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gleenfield97:
The step is to ensure slot A's and B's modem, fsg, bluetooth and dsp partitions contain Pie firmware. See this firmware ZIP prepared by [MENTION=7887589]SyberHexen[/MENTION].

---------- Post added at 10:15 AM ---------- Previous post was at 09:48 AM ----------

It's specific to this model. The reason is,

=======================

Other models with similar quirk probably have similar workaround. LOS 16 doesn't require A/B slot, but utilizes it if available. The LOS 16 ROM of this A-only device doesn't involve "copy partition".
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
I understand the general reasons for the tweak and you provided more helpful detail (thank you) but I did not ask what the step is for. I asked: "specifically what is being flashed here at step 3" to which I should have added the clarification - "and how does that relate to the instructions outlined in the OP?.

So, the firmware you referenced at your step 3 is PAYTON_RETAIL_9.0_PPWS29.69-26-4__A-B_FIRMWARE_ONLY.zip but I still don't see how that fits into the instructions in the OPs which seem to be saying:

- unlock bootloader

- boot twrp via adb from computer

- flash "copy partition" from computer

- wipe > format data

- install TWRP

- Flash ROM

- reboot to recovery

- flash gapps and SU

I'm hesitantly considering this but still doing research:

- unlock bootloader

- intall TWRP

- flash "copy partition"

- wipe > format data

- Flash ROM

- reboot to recovery

- flash gapps and SU

Either way, where would that particular firmware package fit in that workflow, and where else is the need for it when flashing LOS16 on this device stated?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] fubar73:
Sorry if this has been covered already but is there any way to get fm radio to work?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gleenfield97:
Since you're on Pie Feb 2019, it means you already have Pie firmware so step 3 doesn't apply to you.

If it can't be updated or it's using Oreo custom, then you need to flash Pie-firmware.zip.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] krossifix:
The video with the installation instructions was amazing. All I had to do was just download the required files and follow along. Able to confirm everything works perfectly on XT1900-2 including the headphone jack.

I hope the project progresses to release stable builds. :fingers-crossed:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ptn107:
Here's my list: https://pastebin.com/DTPnsV6y

I'll go through it and make only the img's you said.

---------- Post added at 04:33 PM ---------- Previous post was at 03:50 PM ----------

Ok. Done.

https://drive.google.com/file/d/1YTWW2wagI5ZlAThnAeneAgPb5dbNQ8eF/view?usp=sharing

File sizes were similar but checksums are definitely different.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
all images are from same build. none are mixed.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] MeowDotEXE:
I meant when flashing from 8.1.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
Thank you so much. :highfive:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
uploading 8.1 firmware. use that and you should be good. check back second post after 5 mins please.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
build should be stable.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
Moto camera app is known to not work with custom roms.

do you know any other app where we can test if both rear cameras are working?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] domdom2020:
Deletes Fastboot -w not all data (was at least so for me)? In addition I switched from Lineage OS to Resurrection Remix and I had not deleted the internal memory. I did not get in. The cell phone had remembered despite my password but did not let me in. and so he let me in and the phone works great just perfect.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
remove password before flashing and switching roms.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ptn107:
Hooray! Installed just fine from stock 8.1.0 and I kept my 8.1 firmware. Thanks for this!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] assmist:
This one works on the EU 64gb /4 gb XT1900-7 version as well :good:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] pbjr92:
Ok, I tried again and it worked (just one problem with Play Services, but solved installing new one from apkmirror).

I misunderstood the slot A/B thing. Headphone working again tg
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] wonderfullyrich:
Thanks munchy_cool. I really don't want gapps, but apparently can't live without play services.

I finally got it working. Not sure what was lingering, but adding data format

I've tried several variations on your instructions and this is basically what worked:

--Flashing to Stock PAYTON_FI_8.0.0_OPW27.57-25-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Or XT1900-1_PAYTON_RETAIL_8.0.0_OPW27.57-40_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Or firmware_27.251.12_payton_retail_xt1900-1.zip using ./flashall.sh. Any one of which works.

--skip through the wizard

--reboot bootloader

--fastboot -w

--fastboot boot twrp-3.2.1-1-payton.img

--factory reset

--format data

--reboot bootloader

--fastboot boot twrp-3.2.1-1-payton.img

--copy twrp-installer-payton-3.2.1-1.zip and lineage-15.1-20180612-UNOFFICIAL-payton.zip (or lineage-15.1-20180609-UNOFFICIAL-payton.zip, again both work) to internal sd

--install lineage, add zip twrp-installer

--wipe cache/dalvik

--main menu, switch slots, reboot recovery

--copy open_gapps-arm64-8.1-pico-20180612.zip

--install gapps

--wipe cache/dalvik

--reboot system

--skip through the wizard

--connect wifi

--launch play and login

--reboot bootloader

--recovery

--copy Magisk-v16.0.zip

--install magisk

--reboot system

BTW, Anyone have a quick digest of what the Slot A & Slot B elements are? I get that the are different existence, but I was curious about the background. My first interaction with them.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
https://source.android.com/devices/tech/ota/ab/
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] igna.98:
The app works for me, but only single camera modes. You can try installing it through play store. I don't know another app.

However, some months ago I installed lineage 15.1 (https://xdaforums.com/moto-g5s-plus/development/lineageos-moto-g5s-plus-t3738302) in Moto G5S Plus, which also has dual camera, and portrait (depth) mode was working in Moto camera. Some users reported that it works in aosp extended too. But it doesn't work in other ROMs like pixel experience.

Here you have more info: https://xdaforums.com/moto-g5s-plus/themes/moto-camera-100-functional-oreo-roms-t3771344
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] krossifix:
Indeed it is..

Low media volume on speaker is the only missing piece of the puzzle but I can live with that..

It has been 15hrs and 16min since the last full charge on device. A bit of phone calls, YouTube and some casual gaming and she still has 45% battery left. Very impressive.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ptn107:
Anyone try the build from yesterday?

https://androidfilehost.com/?fid=818222786056037557
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
and you really think if the build was good we wont't post it here.

and instead of asking, why not give it a try if you are so curious?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ptn107:
The only one I see posted is 20180612. 6/14 isn't posted here.

I did install 20180614 from afh just moments ago. No issues.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Sebalexx:
I'm not able to explain exactly, but steps in this order worked. (But Pie wasn't updated, in original ROM, did not find the update)

- unlock bootloader

- boot twrp.img via fastboot

- install copy partitions from twrp

- install ROM from twrp (now on slot A, it will be installed to slot B)

- install twrp.zip from twrp (will be installed to both slots A/B)

- reboot to recovery (slot after boot is B, shown in the reboot menu)

- flash gapps/SU (will be installed to slot B)

EDIT:

- wipe - format data

- reboot - system

So the new ROM is always installed on the not active slot,

twrp is always installed on both slots and

gapps/SU is allways installed on the active slot.

I didn't flash any other firmware.

Flashing twrp via fastboot would destroy the boot image, I've read somewhere I don't find right now.

Edit:

Maybe I should have flashed Pie original first... I'll see if everything is working like it is now.

---------- Post added at 11:03 AM ---------- Previous post was at 10:48 AM ----------

https://twrp.me/motorola/motorolamotox4.html
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
That's what I thought, and in my opening post about this I described following native stock updates to Pie, but I suppose that critical detail was missed when step 3 was suggested, so I kicked the tree until the answer that could be seen in the branches fell out. Thanks
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
The details you are providing are very informative and helpful but please avoid assuming others are working within the same scenario as you were at this point (stock not yet updated to Pie) especially when otherwise is described in initial post. That could result in someone following the wrong path and breaking something. Well, not me because I'm an old cynic and Pro workstation builder, but you know what I mean. :)

Regarding the workflow could you confirm that the details that I've added in brackets and bold type are correct?:

- unlock bootloader

- boot twrp.img via fastboot

- install copy partitions from twrp

- install ROM from twrp [still running from PC via ADB] (now on slot A, it will be installed to slot B)

- install twrp.zip from twrp [still running from PC via ADB] (will be installed to both slots A/B)

- reboot to [TWRP] recovery [on device] (slot after boot is B, shown in the reboot menu)

- flash gapps/SU (will be installed to slot B)

EDIT:

- wipe - format data

- reboot - system

Could that have been a reference to this; Using native LOS recovery deletes TWRP so TWRP would have to be instqalled to the device before each flash? Anyhow it seems to be the case that some people are flashing from TWRP on-device and playing with that should not bork anything so I can test that. In any event, thanks again for the informative details.

[EDIT] General Suggestion:

How about a Q&A thread where these flashing questions and others could be discussed. Although the flashing instructions are important to us (and in my opinion they are unclear) these conversations don't inform development for our maintainer.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Sebalexx:
I didn't flash the original rom, because it is not mentioned in the install instruction of post #1. :confused:

Maybe I misunderstood?

Yes, sure, thought that was clear, since there is no other way of using twrp on the device to install the zips.

So:

"fastboot boot twrp-3.2.3-1-payton.img" and after installing "copy partitions", "ROM" and "twrp.zip" reboot to recovery/twrp, which is now available on the device, to change the current slot and install gapps and SU. Without this reboot you would stay on the wrong slot for installing gapps and SU.

After the twrp zip is installed twrp = recovery, but twrp needs to be installed again after each update.

As described in Post #1 twrp is gone after flashing or updating Lineage.

So installing Lineage update in twrp and then installing twrp.zip right after should work without having to fastboot twrp.img to install twrp.zip again, i think so at least.

As i read, one problem of twrp is based on encrypted /data, didn't test it, but to access data it seems to be needed to remove fingerprint/pin/... in front of booting to twrp.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Sebalexx:
Although registered and reading many years, I'm to noob to discuss this. ;)

One also critical point in my opinion is, that in the Lineage wiki the need of installing "copy partitions" isn't mentioned... ?

Or am I wrong?

With gapps installed and google account set up, playstore google camera and this camera are working. Also some other gcam mods are starting now. Maybe it was the missing google account, what prevented the startup in first.

I also tested Moto Camera 2, wide angle cam is switchable and working, front facing cam is able to set to 16 MP, but in low light in this setting only 1920x1080 is stored, at good lighting a warning appears (also at startup): "MCF failed to initialize due to missing required libraries. Some features may be disabled. See log for details." and the cam app hangs "processing".

So there seems to be some auto function for using less resolution in low light, high resolution isn't working at good lighting tough.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
There have been past instances where flashing true stock full factory image was required to proceed with CM flashing. That is not the case here but there are similarities which is why I mentioned it. It may not be worth the trouble for you to bother going to full Pie stock if you plan to stay with LOS (unless you just want to capture a nandriod of stock Pie which is what I did - easier for me since I started at Pie).

Off Topic

Not quite that clear. I understand the difference between booting TWRP via ADB and booting from an on-device installation, and I understand the reasons for running it via ADB at the start in this case. The fact that a previous step used one method does not preclude another method being used in a later step when not specified, and the context of the question made the need for clarity on that point important. You had that clarity because you were imagining your own workflow but when documenting for others the instruction should be absolute. "Install ROM from TWRP" could mean TWRP booted on computer or TWRP installed on device. When someone reads a line of instruction there should be no doubts about what to do nor reliance on context without specific reference - hence my edits in bold. The information you know and your willingness to help are worth those few extra words. Anyhow, that'll be the last of my documentation coaching (25 year Pro at that stuff, hard to stop) because it's making be cranky and I'm shredding this thread, so onward to the nity gritty.

Done with off topic.

LOL, again the clarity (but at least no coaching): Which of these was intended?:

2) twrp needs to be installed again after each update if the update was applied by LOS updater.

3) twrp needs to be installed again after each update if the update was applied by TWRP on device.

1) twrp needs to be installed again after each update if the update was applied by either TWRP on device or LOS updater.

Thanks again (out of TYs).
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
Replying to post edit:

There is a difference between being being "new" but willing to try things and learn, and, being a "noob" willing to complain but not try to help themselves (or others). You are not a noob, and you've provided helpful pieces information that I had not found. Thank you.

Good catch. If we create a Q&A thread we can kick ideas around and create better documentation here without burying actual bug reports, then see if Lineage would accept it in their Wiki. :)

[MENTION=6298645]erfanoabdi[/MENTION], would you mind if we created a FAQ thread for Payton LOS, or might you be willing to do so? In any event thanks for giving Payton some LOS.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Sebalexx:
I remember this from other devices too, maybe it was a mistake I made, as said. Post #1 says required is Oreo, so i didn't thought much about it.

I just tried to describe the steps as I did them. If there would have been another boot of twrp I would have added another step for it.

I'm also not daily writing english, so it is harder for me to be exact. But nice of you to add clarity.

Post #1 says "every update", after using the updater twrp was gone, that's what I can say.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
This is a good discussion regarding documentation for people getting started on this device, and to your point language is a factor, but we are getting off topic for the development thread Let us see what happens with the request for a Q&A thread and continue there.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Sebalexx:
Thank you.

I also had to read way to much to be sure not to brick the X4 right away.

This short Video was helpful and easy to follow, however the first fastboot of twrp is missing.

And now I'm still not sure if I better flashed Pie first... :confused:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] fubar73:
Anyone know if there is a way to get fm radio to work with lineage os 16?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Ultramanoid:
Sorry, but to be crystal clear regarding TWRP.

From https://twrp.me/motorola/motorolamotox4.html :

Does that not mean TWRP will persist in the device to flash Lineage builds from that moment ?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] :
Is it safe to OTA update now? Thanks.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Sebalexx:
At least not after an update with the Lineage updater, because it will replace TWRP with the Lineage recovery.

Not sure about flashing via install or sideload in TWRP.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Hoonanigans:
FM-Radio lost after upgrade to Lineage 16.0

I have the same problem. I upgraded from the last 15.1-build to 16.0-20190316-nightly (using twrp). Everything is fine just the FM-radio got lost.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gillyboatbruff:
If I am coming from stock, do I still need to install the copy partitions zip first, or is that no longer needed with the most recent builds?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] SyberHexen:
Specifically regarding my Payton A/B FIRMWARE ONLY zips..

I dumped the files from latest official factory firmware for RETAIL & PAYTON_FI

Unfortunately to my knowledge and current experience with this device..

bootloader.img only flashes the following slot_a partitions

<abl.elf, cmnlib64.mbn, cmnlib.mbn, devcfg.mbn, hyp.mbn, keymaster.mbn, pmic.elf, prov64.mbn, rpm.mbn, storsec.mbn, tz.mbn, xbl.elf>

so you miss out on Flashing these partitions to slot_b
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
I think [MENTION=5574802]Neffy27[/MENTION] already has an FAQ thread. I think they would probably be open to adding more info.

https://xdaforums.com/moto-x4/help/moto-x4-f-q-s-thread-t3814393/page3
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] TheBassDude:
Updated to 3/18 build today and got stuck with an error saying "Can't load Android System. Your data may be corrupt." Tried rebooting several times including booting into TWRP and wiping the cache to no avail. Ended up doing a factory reset and am setting it back up now.

Any ideas what happened there?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Sebalexx:
Still trying to get Open Camera and Google Camera mod to be able to use the wide angle cam. Because Moto Camera 2 isn't really working properly.

Should adding the package names in build.prop maybe do the trick?

I never played with build.prop - there are 2 of them, if i edit the one with the quoted line, the changes revert after reboot.

I just don't have enough knowledge - any advice? Probably useless, the way I'm trying?

It would be really nice to be able using the wide angle cam with Lineage...
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] edufur:
Androind Auto not working fully

Can someone tell me how to get Android Auto to completely work with this ROM? I am able to install the app, and it even runs... but I cannot get it to appear in the head unit. This is only a problem in the Lineage ROM. I tried 15 and this one and it doesn't work. It works on the stock rom, even when it is rooted. But it will not work on this one. Please help. Pulling my hair out!