yashsingh1/xdaforums huggingface dataset:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ungoogler:
I think I have a similar problem to this, I too tried flashing the modem from the original firmware but it was of no avail... OP were you able to fix this?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gleenfield97:
LOS (or any other custom ROM) doesn't touch the firmware, so the firmware still remains as Feb 2019 version.

So, you can re-stock even though the custom ROM has newer patch.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] edufur:
So when you say you are unable to reproduce the issue, does this just mean that you don't have a car with Android Auto to test it with? Or are you indicating that it actually works for you? Because I have tried this with every LOS for Moto x4 and it has never worked. Going back to stock always works.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
The former, which I should have described as "not in a position to test" (added to post in question). Thanks for making sure it was clear.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Quantumstate:
Now I've lost carrier data in all modes (LTE, H, 3G) running nightly 2019.2.13. Power off and reboot doesn't help. Diff tower doesn't help.

Any suggestions?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] edufur:
Is the problem still there when you roll back?

---------- Post added at 01:29 PM ---------- Previous post was at 01:21 PM ----------

For anyone that has used Android Auto, and has the ability to test LOS / AA with their vehicle, please do so. You will find that it doesn't work. I am a huge fan of LOS but I am not a fan of the fact that Android Auto (while it runs on the phone) does not launch within the car head unit. This is ONLY a problem with LOS. When running stock, this app works fine. I ask that for those who have not ever been interested in testing AA on their car, please do so and replicate the problem I have reported. I would like this to gain more traction but it only will if more people report that it is happening to them too.

I have submitted the bug here: https://gitlab.com/LineageOS/issues/android/issues/397

Please go there and give it a thumbs up and report this problem is happening to you in the comments section (after you have verified it of course).

Thank you. This is an awesome community.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
Has anyone here used TWRP booted on device to successfully restore a nandroid backup of stock and or LOS? If so, could you say why this is not working?:

Scenario:

Preparing to flash LOS from Stock for first time.Testing to make sure there is a way to restore nandroid of stock. Copy partitions has been run and TWRP has been installed (from within TWRP - not by fastboot) to slots A and B and device can be booted into stock or TWRP.

Nandriod backups of stock were created.

Issue:

After restoring nandroid backup of stock (boot, data, system) from TWRP at slot A, upon reboot device stalls on white androidone screen (with "Verity mode is set to disable" in upper left corner) and stays there for far longer than the cache rebuilds and boot should take. Force reboot and start into twrp OK but issue repeats.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
Two things:

1 I think you have to boot into the rom first, set the pin/fingerprint/pattern as the nandroid. Then boot into twrp and restore.

2 typically, I think you restore stock from factory images and just restore data. In the least, you works need to restore vendor/OEM too. LOS flashes the vendor/OEM partition too for treble reasons.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Quantumstate:
edufur: I haven't rolled back or forward because I have a whole big set of apps and config to contend with, and do not hardly use G**gle anything. Trebuchet is unable to save config so I'm pretty much invested. I'm about to go back to Nova again because Trebuchet is lame.

No data anywhere, on any band, on any tower. It's a bad scene, man.

ITM: I took a nandroid of stock using booted TWRP, but I haven't tried to reinstall it as the on-disk partitions are different. (see OP)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
I backed up all stock partitions (except the entire image which should not be needed) and attempted to restore the ones that have been required on previous devices. Maybe I wasn't restoring the proper partitions. In any event, once I switch to LOS I'm unlikely to go back to stock unless there is some critical need, so having no stock backup is OK as long as I can still push a stock image from the computer or flash with TWRP. On the other hand, being able to successfully backup and restore LOS installations is critical.

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

Also, Thanks to you, [MENTION=2790198]gee one[/MENTION], [MENTION=921457]munchy_cool[/MENTION], and [MENTION=7887589]SyberHexen[/MENTION] for the various bits of advise regarding the flashing process. [MENTION=921457]munchy_cool[/MENTION], I must concede that I was, as you suggested, over-thinking, but there was a reason for that. From the beginning, based on research, I saw a "cliff", aka the fact that stock restore and TWRP restore in general might be problematic with my desired TWRP setup so I was being very cautious and ended up revising my original plan to invest some time in stock.

Anyhow, the flash seems to have gone well except for one mistake of a weary monkey brain (see next post). I'll test it with my SIM to see if that reveals anything about the recent mobile network complaints.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
That happens to be the same symptom that can occur when wrong Gapps package is flashed. Something similar to that just happened to me when mistakenly flashed gapps for Android8 onto Android 9 - Pixel FCs during initial setup with black overlay covering interactive parts of display. Reflash with proper gapps package is OK, although I've not dug too deep into the settings.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ajayankg:
Google pixel launcher crashing

Thank you for the reply

I flashed the 'open_gapps-arm64-9.0-mini-20190315' .All other gapps are working(gmail,map,keep,chrome etc) even the Arnova's google camera is working well.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
That should be correct version match but you might want to try MindTheGapps as OP recommends,as well as double-checking your workflow and making sure you are clean flashing.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
I missed this post earlier. Thanks. For stock I would do factory image and data as you mention. I still have to figure out what partitions to include for a full nandroid of LOS but can play around with that.

After flashing the ROM: TWRP is now booting to B. I neglected to observe if this started after the ROM flash (during the recovery-to-recovery reboot for Gapps and SU flash) or after the Gapps/SU flash. Not sure if next flash should be from TWRP in Slot B or Slot A but can play with that as well. Thanks again.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Quantumstate:
You know, I didn't know that sites like APKMirror and APKPure exist.

I've been installing only OpenGapps pico because I thought Play was the only game in town. But now it seems I don't need that with these apk mirror sites.

I don't know whether they'll know that I've bought a given app, but that's only been a few and not much of a sacrifice if they don't.

I am sick and tired of deinstalling G**gle Calendar/Contacts Sync, only to have them instantly reinstalled. And of turning off G**gle automatic sync, only to have it automatically all turned back on.

I'm now running a Radicale server at home (for Thunderbird) which I reach through a WireGuard VPN by the phone and DAVx5. I'd already deleted my G**gle account, but now it looks like I can do a clean install of Lineage without G**gle apps. About to try it.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
Many people wish they could go gapps-less and some manage to do so. You can probably find many threads and resources about that.

As to the previously mentioned mobile network issues: I tested with T-Mobile prepaid US (new, not "legacy") SIM while at a known good location. In 3G - performance was as expected. In 4G LTE - it was was around the fastest I've ever seen. So, it's not a universal issue with mobile networks. If you I think it's an LOS issue specific to your carrier then:

1) Search LOS Gitlab for similar reports.

or

2) Create a report.

Speaking of bug reports here is one for a minor UI issue in the countdown timer. It's not device-specific so I'm leaving the details at gitLab:

https://gitlab.com/LineageOS/issues/android/issues/426.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Quantumstate:
Unfortunately I've failed to implement my plan to be free of G**gle. fastboot doesn't work anymore.

I'd done a Lineage update (to today's), rebooted into recovery and as expected got AOSP recovery. I rebooted into bootloader which goes fine, and the phone shows up... but no other fastboot commands work.

# fastboot devices
ZY2252ZT49 fastboot

# fastboot boot twrp-3.2.3-1-payton\(1\).img
downloading 'boot.img'...
FAILED (remote: unknown command)
finished. total time: 0.001s
# fastboot flash recovery twrp-3.2.3-1-payton.img
(bootloader) partition-: not found
target didn't report max-download-size
sending 'recovery' (30184 KB)...
(bootloader) Requested download size is more than max allowed

FAILED (remote failure)
finished. total time: 0.000s

Tried these a hundred times and no change. Checked all settings in Dev mode and none would contribute to this. I have no OEM Unlock setting since I'm unlocked.

I can't install TWRP, so I can't install Lineage Gapps-free. What a stupid problem, with all the other things I have to do.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] big_edd:
I recently went round and round with fastboot issues as well.

Make sure you are running the latest version.

C:\fastboot --version
fastboot version 28.0.1-4986621

My issue turned out to be USB3 compatibility. I had a bunch of the unknown command faults no matter which usb port or drivers I used.

By plugging in a cheapo (and non-usb3) usb hub then the phone into that, fastboot works as expected.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] imrock:
Hi, I am looking to buy this device because it has official support for lineage os but I want to confirm if it'll work fine with VoLTE networks here in India (Jio). Also will the dual sim capabilities work fine with Lineage os 16?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] SyberHexen:
You may want to try the stock flash procedure only flashing gpt.bin and maybe bootloader.img

This normally fixes that issue.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
I run stock LOS without gapps on my daily driver. I have an old n5x that has gapps on it so that I can download a few apks to sideload onto my x4.

Similarly, I have a davical server and use davdroid/davX5 for calendar and contact sync.

The best way to control google is to remove it.

It can’t be bargained with. It can’t be reasoned with. It doesn’t feel pity, or remorse, or fear. And it absolutely will not stop, ever, until you are dead.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
Well said.

---

Back to LOS 16:

Is anyone able to create files in /system/etc while using LOS SU (or Magisk)? The last I saw this restriction in a ROM, it was addressed within the ROM, but I'm not sure if that is possible in this case. Also unable to use TWRP to create symlinks between /system/etc and /data/data (which is writeable).
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
I think if verity is enabled, it also has an error correcting code that will revert most changes at boot.

Are changes lost at reboot?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
Boot splash screen states "Verity mode is set to disabled". Regarding regular use I've lost no changes to app or personal data through reboots, and regarding changes to edits made in /system/etc, I cant write to that location at all so that is moot.

In LOS 16 for Payton are you (or anybody else) able to create files in /system/etc while using LOS SU (or Magisk)?

[EDIT] Due to limitations of the native LOS file manager it is best to test this with a file manager app which would have more access in the same situations; such as MiXplorer or Total Commander, others.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Quantumstate:
Excellent. I've just rebuilt my phone with apps exclusively from F-Droid, and for apps that weren't there, I got them from APKPure. I found everything and have no GApps installed. A couple apps -require- Play (Copilot, Car2Go), so they are now booted with extreme prejudice.

But my phone is intermittently hanging. Just a complete hang and I have to hard-reset. And PrivacyGuard can't remember its settings from one reboot to the next. If I leave it alone for an hour it's fine, but as soon as I pick it up I have about 60 seconds. I hope these are just something with the March 23rd nightly.

What is 'verity' and how do you disable it?

I too would like to make some 'adjustments' to /system/etc/hosts but my phone won't stay unhung long enough for me to do it. I used to mount -o remount,rw /system to fix that, but it may be that an Android thread is now watching that like a hawk. In #Terminal all I have to do is type '/syste' and it reliably hangs.

FAHAHAHA!

Word.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
That message started appearing immediately after unlocking bootloader on xt1900-1 AndroidOne variant.

There's clearly something wrong with your device beyond LOS 16 specific issues because those problems don't happen in clean flash of just ROM or just ROM and gapps. In other words - off topic.

Likewise in the past for me on different device. Will try it on X4 device once I re-learn the command and syntax.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Quantumstate:
That is the command and should be the syntax. I use Termux. Be sure to su.

lol, very informative... nm I've got it.

And, my hanging problem is not OT. I've found that it was Trebuchet Notification. As soon as I turned that off (in Settings|Apps) the hangs stopped. I run Nova because Trebuchet is so dreadfully limited.

Trebuchet can't even back up its own settings, so you have to reconstruct everything -- I for one have 5 pages filled with apps, in just the right places I like, and sorted by function (Entertainment/News, Multimedia, Home/Weather, Calendar/Email, Utilities) and in 3D folders, and widgets just so.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
Then certainly, if you think that is an LOS bug you would create a viable bug report that the developers could work with ;)

I'd try to reproduce it but "Flava Flav's got problems of his own". :silly:

By syntax I meant the command, switches and proper path. The problem is that the command as commonly shared (as you describe) is specific to the "system" mount point and whatever the proper mount point is on this device, it is not "system".

- There is no mount point called system as viewed in terminal "cat /proc/mounts" or in the Aida64 app.

- In TWRP system is at "/system/system"

- Perhaps once the proper mount point is identified that command can be used.

[EDIT]

... and to [MENTION=2790198]gee one[/MENTION]'s point". Perhaps that means / (root) (Device: /dev/root) is what would have to be remounted as RW but I'm not messing with that until I learn more.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Ultramanoid:
Install FX from its thread in XDA :

https://xdaforums.com/showpost.php?p=79108538&postcount=4458

Get the full version just in case, not micro. Check for 'home' and section 'filesystems'.

It has a full-fledged storage filesystem analyzer with details of all mount points and partitions, including those not seen by most file managers. Lots of info in there to debug and see what's going on. ( You may need to activate full-functionality in FX which is limited in time, paid after a few days, but there's no tracking, analytics, Google dependency, or adware=spyware crap. )

Edit : It includes fixes for Android's storage framework bugs that are not solved by Google or Lineage, so it may help.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] CJ1169:
Been riding the nightly from the Sunday after LOS 16.

Works well so far. Some stability bugs with wifi.

Notably, the FM radio capabilities are missing. A few people have mentioned that.

Is this an issue with only some people or is everyone affected? Anyone have FM radio access?

If its select people, I can provide logs so long as I'm told which logs to post.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
In Moto X4 LOS16 is the FM radio supposed to be separate app as is the case in previous lineage versions and stock, or is it incorporated into something else such as the Music app?

For what this is worth, the FM radio app is not present in the March 22 build on my xt1900 - 1 nor is there any other way to play FM radio.

In any event, if you are interested in finding out what's up or trying to get it fixed then you could try this.:

If you search this thread for instances of [FM radio] you will find a post from device maintainer about it being fixed sometime in last year, followed several months later buy a report of something being broken. You should search for these post yourself since you've reported this problem and are in a better position to assess previous reports.

It would also be a good idea to search LOS Gitlab to see if this is a known issue for this device, and if you don't find anything there perhaps create a ticket.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
Thanks. FX shows the same items as Aida64 but with some more details. In both: / (root) at Device: /dev/root seems to be the moist likely location for system as it seems to be the only one that is presently mounted as read-only AND flagged as re-mountable. This may also be what [MENTION=2790198]gee one[/MENTION] was previously referring to. That being said I'm not quite ready to try remounting that as RW.

Also, I finally got to searching LOS Gitlab for related issues and found this one: Moto X4 (Payton) Does not allow TWRP to decrypt FS after setting up LineageOS 16 from 2019-03-11: https://gitlab.com/LineageOS/issues/android/issues/318. Perhaps, not directly related but this is one of the things that must be accounted for when flashing via TWRP.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Quantumstate:
I have tried remounting / and it complains that /dev/root is mounted read-only. {der} So I tried remounting /dev/root rw but it says the same thing.

Android 'O' brought significant permissions changes so most remount apps no longer work, and I haven't found one that does in F-Droid or APKPure. (and APKPure gets everything from Play)

/ apparently isn't a squashfs (which would be hopeless), but I am suspicious of that 'seclabel' option. (selinux) This is probably the cause and so the setenforce script would need to be added, and run as root.

And yes, TWRP not getting access to the sdcard nor internal storage is a hassle. Wish TWRP would fix this. Supposedly someone is working on it, but it doesn't look like it.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
That's interesting, because / is flagged as re-mountable. Thanks for testing. I'll play with that when I have a chance.

I did not have any problems accessing those locations in TWRP, in fact once I found the location of /system/system/etc it was TWRP that was able to copy a file there while nothing else could. Also, I do disable screen lock in LOS before using TWRP.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Quantumstate:
Just to be clear, I used # mount -o remount,rw /dev/root/ / and it fails.

Hm, disabling screen lock shouldn't de-encrypt the flash memory. Ya you can get access to the system parts but not internal nor external SD cards, at least in cleartext.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
I did not say that disabling lock screen decrypted flash memory. Merely that I had disabled it. and that point was pertinent to flashing with TWRP (which I am documenting)

I would not have reported that TWRP had write access to drives if that were not so. TWRP can indeed write to internal and external SD cards as well as /system/system.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Quantumstate:
Ok, Ok, not meaning to eat anyone else's dinner here. I'll stand down.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
Your willingness to engage and even test a few things is very nice. It's just that once we get a few thread pages from the original report and the added details across multiple posts, then some of the suggestions become out of tune with the reported scenario. This somewhat "comes with the territory" of communal troubleshooting but that makes it no less frustrating. It's also a good reason to open up a new thread about this, which I think I'll do. I hope you don't hesitate to post there. :)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Ecthelion3:
TTS problems

Hi, since moving from stock to LOS 16 I am having problems with using Text-to-Speech (TTS). I have installed the Google TTS package from the Play Store. When starting TTS output I get asked to choose an output language and then a voice for the language. But in this last step there is no button to confirm the selection. And when simply pressing back and leaving the selection it does not seem to get saved, because the app triggering TTS then simply stops TTS output with a message that the functionality is not available. Any ideas how to solve this?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Skeeterdrums:
I used the Google tts package successfully through Tasker, but that's about it at this point. Not sure what context you're trying to use it in though.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] dougo007:
I would check two places.

In the Android language settings, you should be able to set the language for TTS there.

Then, check the app settings to see if there is a setting there that needs to be set.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] guibyn:
Best ROM so far! Thanks guys!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Ecthelion3:
Thanks for the suggestions. Indeed, among the language settings, there is a setting for TTS output. Unfortunately when trying to access this setting, the settings dialog that shortly comes up immediately crashes. I will try to check the logcat output to get an idea what might be the problem.

Will do so. But given the weird behaviour of the TTS settings dialog (see above) my fear is that it's not related to the app (which also works fine on another, non-LOS smartphone).
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
Seems quite similar to the types of FCs that occur when there are issues with gapps or Google services. E.g. A normally successful dirty flash may fail because of a particular update to the ROM or gapps. Similar things can also occur in clean flash but that is less common..

Diagnostic suggestions:

- For comparison, remove the app that you are currently using to test and see what happens with any other one. I use an app named @ Voice Aloud for such tests.

- Test from a clean flash of latest LOS build and Mindthegapps, with no 3rd party mods, before installing any apps except the ones needed to conduct the test, to see if it is reproducible there.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] edufur:
Is it me, or does this ROM seem a little slow on the performance side of things? Specifically, and consistently, when I am installing things from the Play Store, downloads take a bit longer (on my home wifi), and the actual final install process takes quite a bit longer.