yashsingh1/xdaforums huggingface dataset:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
I've not noticed any problems over the past several weeks. After seeing your post I updated several apps including Google search app. The download speeds were fast as was the installation. For what this is worth, I have occasionally seen Play Store download speeds disproportionately slower than the network capabilities, something on the order of a few kb/s. Seems like some sort of throttling on their end. Additionally you would see very slow installations if the Play Store app and or underlying Google services are being automatically updated in the background. Apart from all that, this does not seem to be a ROM issue.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Ecthelion3:
Daydream

Just out of curiosity, has anyone tried to get Daydream VR running on the X4? There are instructions for forcing Daydream support onto devices not officially supporting Daydream, but the config files that should be modified do not exist in LOS 16. Does anyone know whether and how this works for LOS 16. Or has anyone tried with an older version of LOS on the X4 and can share his experiences about how good Daydream is working on the X4? Thx

---------- Post added at 08:17 AM ---------- Previous post was at 08:14 AM ----------

Thanks for the suggestions. I have tried with Voice Aloud and could see that TTS basically does work. From what I've checked it's the voice/language selection that is not working - at least on my device. But if TTS gets passed a language to use then everything is fine.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] sevenrock:
Yes, but you need some patches to be able to install com.motorola.fmradio

four patches for TheMuppets:

https://github.com/TheMuppets/propr...compare/lineage-16.0...sevenrock:lineage-16.0

and one for payton:

https://github.com/sevenrock/androi...mmit/b9911936358b57861b55701f0bcb083ce0e3752a

I am unsure whether these patches are needed because I did not test FMRadio

without them but they sync with Moto Pie ROM:

https://github.com/sevenrock/androi...mmit/49e1d9ad1602640aa48d7c61f7a1f398c195f886

https://github.com/sevenrock/androi...mmit/bfc69fffd8449078082e984fe472418e96062a33

https://github.com/sevenrock/androi...mmit/b07d9ee9fb783402fc56f3a4adcd4fe97b1ad9a8
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] btotta:
Guys, I got a system crash when I tried to use Miracast mirroring on the last version of LOS, anyone have the same problem?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
Can anyone confirm successful Dalvik cache clear in TWRP without this issue:

I cleared Dalvik cache in TWRP then after successful reboot into OS, within 1-3 minutes device spontaneously reboots back into TWRP. Occurs even after a factory reset. The first run screens appear as expected but device spontaneously reboots into recovery within minutes.

Oddly it occurs every time, except when the device connected to computer (attempting to log via ADB). In those cases it occurs within a minute of being disconnected. I was able to capture some log after quickly reconnecting once the showdown started but don’t know if that log contains anything about the cause.

[EDIT] Additional detail - while after this issue started occurring the white android splash screen would persist on screen for longer than usual. First boot after clean flashing March 30 build seems to be going better; no delay on AndroidOne screen. No spontaneous reboot to TWRP...yet.

Also, from previous flash of March 20 nightly TWRP was booting to B and everything was running fine. After flashing todays clean flash TWRP is booting to A and everything seems to be running fine. So, perhaps some problem with TWRP cache clear regarding slots.

[EDIT] Another clean flash then, merely creating a backup of everything except full image (with on-device TWRP) causes boot loop between OS and back to TWRP. I can understand how flashing or restoring could run afoul of the A/B Arrangement but I don't see how merely creating a backup to external storage could cause this.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Ecthelion3:
Regarding the TTS issues I am still having the problem that I can't use the settings dialog Settings -> System -> Language & Input -> Speech output. It crashes and I can see the following logcat output:

2019-03-31 17:44:17.730 26524-26524/com.android.settings E/AndroidRuntime: FATAL EXCEPTION: main

Process: com.android.settings, PID: 26524

java.lang.RuntimeException: Failure delivering result ResultInfo{who=android:fragment:0, request=1977, result=1, data=Intent { (has extras) }} to activity {com.android.settings/com.android.settings.SubSettings}: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference

at android.app.ActivityThread.deliverResults(ActivityThread.java:4398)

at android.app.ActivityThread.handleSendResult(ActivityThread.java:4440)

at android.app.servertransaction.ActivityResultItem.execute(ActivityResultItem.java:49)

at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)

at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)

at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1816)

at android.os.Handler.dispatchMessage(Handler.java:106)

at android.os.Looper.loop(Looper.java:193)

at android.app.ActivityThread.main(ActivityThread.java:6718)

at java.lang.reflect.Method.invoke(Native Method)

at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.equals(java.lang.Object)' on a null object reference

at android.speech.tts.TtsEngines.parseEnginePrefFromList(TtsEngines.java:503)

at android.speech.tts.TtsEngines.isLocaleSetToDefaultForEngine(TtsEngines.java:367)

at com.android.settings.tts.TextToSpeechSettings.updateDefaultLocalePref(TextToSpeechSettings.java:502)

at com.android.settings.tts.TextToSpeechSettings.onActivityResult(TextToSpeechSettings.java:485)

at android.app.Activity.dispatchActivityResult(Activity.java:7489)

at android.app.ActivityThread.deliverResults(ActivityThread.java:4391)

at android.app.ActivityThread.handleSendResult(ActivityThread.java:4440)*

at android.app.servertransaction.ActivityResultItem.execute(ActivityResultItem.java:49)*

at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)*

at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)*

at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1816)*

at android.os.Handler.dispatchMessage(Handler.java:106)*

at android.os.Looper.loop(Looper.java:193)*

at android.app.ActivityThread.main(ActivityThread.java:6718)*

at java.lang.reflect.Method.invoke(Native Method)*

at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)*

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)*

Is this something in LOS 16?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] joecool1029:
Are you flashing TWRP from TWRP or from fastboot? I get error when trying to clear dalvik in TWRP but none of the behavior you have described. My usual update process (I build my own LOS):

- install new LOS over old from TWRP

- then install TWRP without rebooting

- reboot to bootloader (select recovery again)

- flash addonSU and opengapps

- reboot system
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
That's the same process I'm using. The ROM runs as expected and I can clear cache safely but any attempt to run a backup from TWRP on the device or TWRP img on computer via ADB results in the boot loop between OS and TWRP. Even if I don't flash TWRP and only run it via ADB this occurs.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] joecool1029:
I did run into a bootloop after restoring a LOS full backup coming from stock. I resolved it by flashing a LOS image on top after reboot to TWRP again. Then things were fine. I think it is an A/B thing and expected behavior.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Ecthelion3:
FYI, I could resolve the issues with TTS by installing another TTS engine. That 2nd engine seems to resolve whatever problem there were with only Google's engine installed.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] SyberHexen:
Have you tried restoring the system partition from the opposite slot? A/B logic

Last time I restored a full backup to slot A

In TWRP (A)

Restored boot, data, Vendor

Reboot TWRP (B)

restore system

Switch back to slot A and boot device
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
I followed the instructions from the original post to the letter, rebooting into recovery (on device) to flash gapps and SU. I've also tried doing all the flashing booted from twrp.img via adb without installing TWRP (which is what I assume you mean by "fastbooted to TWRP"). In all cases the result is a functional ROM that is destroyed by any attempt to create a backup with TWRP whether on device or via img through ADB.

As yet no one has confirmed successful TWRP backup and recovery so so I bump the question:

Has anyone been able to successfully create and restore a full device backup of Payton LOS 16 with TWRP booted on device or via IMG through ADB, and specifically which partitions were backed up and restored?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] SyberHexen:
Did you happen to see or try what I recommend?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
I had not seen that post yet. Thanks for flagging it. I'll definitely give that a try next chance I get.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] edufur:
Who exactly "handles" the bug reports on the gitlab system? Is it the Lineage Dev team itself? Or does it get relayed by the "owners?" It would seem there are only a couple of "members/owners" for the gitlab system. That seems like a small number, so not sure if that is just the folks that triage or not. My logged ticket from a week ago doesn't even look like its being looked into.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Quantumstate:
IronTechmonkey, I was referring to the side excursion you'd made to get the bootloops.

There is no way TWRP can successfully back internal or sdcard flash, as it can't penetrate encryption. If you have those parts enabled please disable.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
The bootloops happened every time, not just on that side excursion, which was taken just to have another testing point but the results there were the same as everywhere else.

Since the backups completed successfully I was probably not including data but I will check that out later to be sure. Also, I don't see how successfully creating a backup would cause the boot loop, but this does give me something to test. Thanks.

One thing that still puzzles in spite of the helpful information shared today, is that no one has yet confirmed that they have actually successfully used TWRP to backup and restore, or if they have I've missed it.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
I would expect that even without counting the individual device maintainers and contributors there are more people involved in LOS Gitlab than just those 4 "owners". The Gitlab ticketing system seems more automated and less robust than the OS Jira ticketing system from last year and I'm not yet familiar with it but based on LOS Jira: Tickets would get assigned to the most appropriate person, perhaps the device maintainer or a contributor for device specific issues, perhaps someone else for non-device specific issues. In the old system I'd seen some tickets sit through multiple LOS/Android version before getting fixed, and seen some fixed relatively quickly, and some fixed in one version only to regress in the next LOS/Androiod version, and some never fixed. To your point, the new system seems slow of pace, but it is what we've got and it’s still a good place to report issues because it does vet them somewhat and requires logs. That's not to say that the XDA threads are not also good places to report things but that depends on the thread and the developer.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
I have backed up and restored from twrp. I was using the ramdisk from the 3.2.3-0 version that is floating around. The official version couldn't decrypt data on LOS16, despite working fine in LOS15.1.

I am using a homebrewed rom and I insert the twrp ramdisk into my boot.img and the sign it with my own keys.

If the verity keys change, it will probably break decryption. They probably change or the boot image is unsigned any time something else is flashed in recovery... maybe.

Try this:

backup up data,

Flash or wipe to something else,

reboot into the os, set the lock to whatever was in use in the backed up ROM (pin,pattern,etc)

Reboot into twrp and then restore data.

The trick here is to boot into the os first, before restoring... maybe. It works for me, but my use case might be different than yours.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
Thanks again for the helpful advise. I think I’ve already learned that trick (perhaps from one of your previous posts) as I disable lock before doing any flashing, backup or recovery.

Also, the problem Is occurring before getting to any attempt at restore: Every time I create a backup in TWRP (booted on device or via img through adb) the device starts boot looping from OS (after home screen appears) back to TWRP and stops at TWRP. If TWRP is not installed it boots to LOS recovery then immediately back to OS, continuing that circle unattended. Create backup = bootloop.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Quantumstate:
Well I had just done full backups of the phone to my backups server, and I was just about to turn to TWRP backup, but I'm sure not now...

I've spent way too much time on it to ruin it right away.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
Ya, I'd say it's not worth the risk unless you are prepared to clean flash.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Ecthelion3:
Is it just me or are there others having the problem that, with the phone inside the pocket, the fingerprint sensor often tries unlocking inside the pocket until the sensor gets disabled? I then have to use the PIN and the sensor gets reactivates again, so that it's only temporary. But is the a solution to this?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Quantumstate:
Are you wearing spandex pants? With no underwear? Or do you generate an electric field?

This hasn't happened to me. I keep it in the back pocket of tight jeans. And I wear underwear... (briefs)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
I thought there was a pull request to use the proximity sensor to disable the fingerprint scanner to prevent this? Maybe it's not implemented yet? What is your build date?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Ecthelion3:
There is a setting to prevent unwanted activation of the display that uses the proximity sensor. I have already activated this, hoping that it would solve my problem with the fingerprint sensor. But to no avail. I have installed today's LOS 16 build.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Nicholas6706:
Yeah I'm having the fingerprint issue as well where it times out from triggering inside my pocket
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Ecthelion3:
Good to know that I'm not the only one. So it's at least two people looking for a solution.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] edufur:
did you guys officially log this bug? you should do that if you havent. as it stands, its hard enough to get attention with things that are logged. there are open bugs from several months ago. I have one out there for 2 weeks ago.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
Since its purchase and throughout testing my X4 has been perched on an old fashioned rubber/cloth mouse pad and never used as a daily or taken outside, but while holding the device in hand even without shaking the phone, just moving around, there is a rattling sound of a loose part in the upper section of the device.

Research indicates that this could be caused by the sensors and focus mechanism for the camera, and testing supports that claim since the sound does not occur while the camera is active (in native LOS camera or compatible older Motorola camera app). Not just the camera app must be active but the camera focus must be in use which does not occur while in camera app menus.

Attached is a recording of the sound (mp3 within zip file), captured from a Moto G4 Athene which was on a mousepad while the X4 was lightly shaken approximately 4 above the Athene device. The sound is loud enough that it would almost certainly be heard in phone conversations while walking.

So, questions:

1) Does anyone else experience this in LOS?

2) Has anyone experienced this in stock?

3) Getting down to the nitty gritty; Might there be any way to mitigate this with software without consuming battery or verging on privacy issues by having a mock camera function occupy the focus sensors?

[EDIT] Comparative testing on Moto G 4G (Peregrine), Moto G3 (Osprey), and Moto G4 (Athene) across various iterations of LOS 14, 15 and 16 reveals a possible trend: The issue is more noticeable in LOS 15/16 than LOS 14. Perhaps there is some hope for a "parking" mechanism for the camera parts. Now I'm even more curious to know if this occurs in Stock (which external sources do seem to indicate).
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] smartsoldier:
I saw a special version of Lineage floating around for OnePlus so I figured maybe I could find one here for my MotoX4:

Recently my battery temp sensor started malfunctioning to where it thinks its always -32C, so of course it refuses to accept a charge. Unfortunately I am out of warranty so in an effort to prolong the life of my device I was hoping I could find a way using Lineage to disable the temperature protections so I can charge it again. Is this available in normal Lineage, or with an additional rooted app, or maybe a special version of Lineage?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
Hardware problem resulting in need for specialized ROM or app which would break normal protections? Yikes, that's off topic in several different directions for a Lineage OS development thread, especially considering that it does not relate to an issue or desired reasonable change in this ROM. You'll get better results by searching for and posting in forums/threads based on the underlying issue then working your way to proposed solutions.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] smartsoldier:
Understood. I am only able to get into Recovery Mode by doing fastboot boot twrp.img and then of course its the twrp recovery, but I want to use the Lineage OS version. Is there a separate img from Lineage I can get to do it this way?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
The LOS recovery is built into the ROM. If you flash just the ROM gapps and SU you should then be able to reboot to the LOS recovery.

The last time (and the only time so far) that I checked out the LOS recovery it was very minimal and I was unsure how to use it. That being said there have been many new commits which seem to be adding features and functionality to it, and there are other people here who probably know how to use it.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Ecthelion3:
No, I haven't logged this bug. First thing is that AFAIK for logging a bug logcat output should be provided. Since the problem with the finderprint scanner getting deactivated gets triggered at some unknown time while the device is inside my pocket, it's hard for me to provide a meaningful logcat. Second, and related to the first point, without such a logcat output I think the bug would have only little chances of ever getting looked at.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] edufur:
Well, that is a good point. But I don't think that logcat is an absolute requirement. And certainly when you have others experiencing the same thing, as long as they contribute a "me too" of sorts to the bug, you might get some traction.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] IronTechmonkey:
Some problems are indeed quite difficult to capture in a log. In such cases the best we can do may be to try to find ways of forcing the issue to happen or to find any precursor indicators that would be clue to start logging. Much easier said than done in your case.

If the rules from the previous Jira system are still in effect a log would be required for the initial ticket (which may be summarily rejected without log) but to your point logs are not required for supporting notes from other people experiencing the same problem, and those additional reports do help.

[EDIT]Logs still required for initial report:

https://wiki.lineageos.org/bugreport-howto.html
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Ecthelion3:
Meanwhile I filed an issue for the problem with the fingerprint reader: https://gitlab.com/LineageOS/issues/android/issues/538
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] bororock:
Hello,

I have recently installed lineage os 16.0 on my moto x4 but I have to major issues:

1. I can call friends, but I am not able to hear them and they are not able to hear me.

2. If I play MP3 or other media, the media player plays the song too slow, therefore there is no sound neither. I tried different mediaplayers. I see that the device plays the song as the timestamp is increasing really slowly.

If someone can help me, this would be awesome. Thank you!

PS; I tried this what is written in the /fix_the_no_sound_in_calls/ thread on redddit but it didn't work.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Quantumstate:
bororock something went wrong with your flash. Did you carefully follow the OP?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] TrancëJay:
Does this rom support 1080@60fps video recording like stock one?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] sketchman16:
This is almost unbelievably good. I'm going on 23 hours unplugged and I'm at 77% battery with ~2 hours SOT. IDK if stock is this good, and it's just the hardware doing it, but it's awesome.

Only issue I've noticed so far is recents will randomly just not work. I touch the button 10-12 times before I just give up and wait, then it works later with no reboot or input on my part.

I'll try to get a log if I can catch it again.

EDIT: Plugged it back in with 40% left at ~6.5 hr SOT. WiFi and mobile on the whole time and I even used GPS for probably 1hr or close to it. No kernel parameter changes and no other changes that would improve battery life.

Haven't had any more issues. Recents thing might have been a settling issue. Hasn't happened again.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Quantumstate:
Something is wrong with mine.

Carrier data only works immediately after a reboot. But then the little X is in the signal strength indicating no data. This is a problem.

But worse, whenever the phone rings there is no popup to answer. I have to unlock the phone, then still no popup while it's ringing away. I have to pull down the top to get an Answer button.

These two problems have persisted for two weeks, through 4 lineage updates. I have to go back to stock if this can't be fixed. How can these still be problems in the 21st Century?