yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] Pantherrra:
Was anybody able to fix this issue by now? I have tried to flash the firmware again, as described earlier (https://xdaforums.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235), which went fine (no errors), then flashed twrp, then clean flash of this 08/01. But still the same issues with the camera (photo seems to be taken but not saved). I'm out of ideas... Some suggestions? Thanks in advance!
[X Style (Pure) Android Development] freeqwerty:
Hello. Need flash GAPPS with this ROM? And the ROM working in the XT 1572?
[X Style (Pure) Android Development] Pantherrra:
Yes flash this rom, then gapps (before rebooting). And yes it works on xt1572
[X Style (Pure) Android Development] freeqwerty:
.

Thank you. What camera alternative do you use? When this camera is broken.
[X Style (Pure) Android Development] Pantherrra:
If everything goes right, your camera should be working, using the built in camera app, if I'm not mistaken. But only in one orientation
[X Style (Pure) Android Development] freeqwerty:
With last release? 8/1/2019 https://www.androidfilehost.com/?fid...31924117928331

Now am rooted my phone. Root keeps or no? do i have to search again Magisk Manager for android 9 PIE? Thank you.
[X Style (Pure) Android Development] Kenaz Rune:
I just I just want to give you a little bit of moral support here. I haven't bothered saying anything yet, but I too am having that problem with the camera with the most recent install and the ones prior. I've been dirty flashing since the initial install and I started from nougat.

The camera isn't important enough to me on this phone to go through too many hoops. I'm eagerly awaiting resolution. I'm just thrilled there's a pie implementation on it at all.

I've bastardized this rom with magisk, xposed, and microG, so I figure it could be one of those that's messed me up.

---------- Post added at 02:13 PM ---------- Previous post was at 02:10 PM ----------

Rooting with magisk holds firm. Always use the most recent magisk. it is ROM and Android version agnostic.
[X Style (Pure) Android Development] freeqwerty:
Everything is correct, but when it comes to entering the SIM card password, the phone restarts. Need wipe (internal storrage) with together Wipe data, cache, dalvik cache and system? Now am back to NucleaROM. The Lineage 16.0 will restarted evry time.
[X Style (Pure) Android Development] Psychopompos:
Lineage has a built in camera app. If you flash GAPPS, don't use the full stock or it overwrites the Lineage camera with the Google camera (I think). I was trying to use my stock moto camera (which had still been working on earlier versions for unknown reasons) and I started getting the freezing issue. Same with any of my downloaded cameras. Once I was told that people were actually referring to the stock Lineage camera, I realized what appears to be my issue. Hope that [MENTION=9564902]Pantherrra[/MENTION].
[X Style (Pure) Android Development] redwoodie:
Shutdown and boot issues 20190801 build

This ROM was working very smoothly for me with nano GAAPS after initial setup and downloading apps. I ran it for a day and a half without a reboot, then had some problems getting it to shut down--first few tries, nothing happened when I pressed Power Off. When it rebooted, it didn't seem to fully initialize (notification icons at top did not appear) and the message in the attached .jpg appeared. No matter which option (close or wait) is selected, the device seems to do something like a soft UI reboot--the screen goes black for maybe 5-10 seconds, then the UI reappears. At that point, either the initialization completes after 10-30 seconds and all seems to work well, or it repeats the error message once or twice more before things settle down (usually 2 UI reloads). Then all seems to work. All in all it's 2-5 minutes before the phone is stable and usable from power on.

I attached a Logcat (Matlog) from a few seconds after reboot. Not sure how to take one from cold start. This behavior happened once before I had flashed Magisk (the only time I had rebooted before flashing it), and then each time since then. Magisk is all good with root and Safetynet. Any ideas on this issue?

All, great work on this ROM to date, I was about to give up hope for the XT1575.
[X Style (Pure) Android Development] redwoodie:
Shutdown/boot issues files

I don't believe the files attached to my last post.
[X Style (Pure) Android Development] tigger360:
I get this at times. A dirty flash of your current rom version should fix that up at least temporarily.
[X Style (Pure) Android Development] Pantherrra:
Ok I feel like an idiot now! That indeed worked! I always installed the full gapps (why...) and that indeed got rid of the lineage camera. Thanks alot [MENTION=10060246]Psychopompos[/MENTION]! And [MENTION=9827837]Kenaz Rune[/MENTION] hopefully this fixes your issues as well.
[X Style (Pure) Android Development] freeqwerty:
Help me please. Am flashing lineage-16.0-20190801-UNOFFICIAL-clark + open_gapps-arm64-9.0-nano-20190816 all is well.

The phone charges and starts making updates and at one point it starts to restart and cannot continue forward. Enough to PIN SIM card and there. Now my firmware is 7.1.2 NuclearROM
[X Style (Pure) Android Development] jehova666:
@ freeqwerty

updated to stock nougat before installing nuclear rom ?

if you didnt, it is a modem problem...... as stated in first comment.

update to stock nougat-> then lineage 16

installed randomblame 1/1/19 without a hassle (open nano gapps) and no issue exept the known one and soft freezes by using the pic in pic function....(inspecting deeper trying to get logcat)

Best regards

[MENTION=1776875]randomblame[/MENTION] thank you for the rom
[X Style (Pure) Android Development] freeqwerty:
Could the problem be in my TWRP? My TWRP is version 3.1.1.0 I tried with twrp-3.2.1-0-clark-N-decrypt and twrp-3.3.1-0-clark phone restarts and does not boot. Am flash again recovery 3.1.1.0 and everything is right. Restore my backup with NucleaROM.
[X Style (Pure) Android Development] jehova666:
@ freeqwerty

in earlier versions of trpw was an problem with encrypted partitions see tread twrp hashbang....but this should been resolved in the actual twrp twrp-3.3.1-0-clark....as stated, work in my phone well, but nothing was encrypted....(and a full complete wipe)

sorry i´ll hope senior member could help you more ...

Best regards

J.Hova
[X Style (Pure) Android Development] freeqwerty:
Do I necessarily need to be with 7.0 because with 7.1.2 I have a restart problem. Now am have a custom ROM
[X Style (Pure) Android Development] kadopt:
No need to dirty flash the current rom, just wipe cache and art cache in recovery and it will boot without issues.
[X Style (Pure) Android Development] Techwizz01:
Quick bug report. I've been using this ROM as a daily driver since around April and almost everything I had an issue with has been fixed already. The main issue I know of that isn't addressed is that when you're in landscape mode your volume slider will be off the screen. Other than that, great ROM!

Thanks!

~Techwizz
[X Style (Pure) Android Development] kadopt:
[MENTION=9893710]Techwizz01[/MENTION]

Working fine here.

[IMG="vol_ok"]http://firegoon.com/u/pacnt.jfif[/IMG]

Also your image does not load.
[X Style (Pure) Android Development] freeqwerty:
For me obviously there is a problem with this ROM. :(
[X Style (Pure) Android Development] Pergmen:
Worked with no issues on my device. My SD card was mounted in a weird state state where only four files were visible/readable, but otherwise it's flawless. Marvelous work!
[X Style (Pure) Android Development] freeqwerty:
ROM works, but it starts to restart. I installed it from the SD card as well as from the internal storage. I don't know why it just doesn't work for me. I'm installing it with TWRP 3.1.1.0 Tell me where my error is please.
[X Style (Pure) Android Development] Strephon Alkhalikoi:
Using any modules with Magisk?
[X Style (Pure) Android Development] freeqwerty:
I'm not sure, but I have applications that work with Magisk. Two application is SD Maid and File Manager. at the end of the ROM installation, I write this: Failed to mount /dev/block/platform/soc.0/f9824900.sdhci/by-name/modem at/firmware: Device or resource busy.
[X Style (Pure) Android Development] randomblame:
Sounds like you are not on good nougat firmware
[X Style (Pure) Android Development] freeqwerty:
My firmware is custom ROM NucleaROM 7.1.2 based on nougat. Maybe need to back in stock firmware 7.0, to try again flash this rom? I do not know what to do.
[X Style (Pure) Android Development] Strephon Alkhalikoi:
You'd know if you had any modules installed as they likely would have come from the Magisk Manager repo. In my case it caused problems with the WiFi and MicroSD card slot that only corrected itself after several reboots.

Install your modem firmware a few times, as it's notorious for not installing correctly the first or second time.
[X Style (Pure) Android Development] kadopt:
NFC does not work. It keeps toggling on and off. Also memory management is dodgy as even with zram the device keeps eating up the ram.

I've tried several approaches to fix these issues:

- wiped the entire device including internal and external storage (didn't fix)

- changed data partition from f2fs to ext4 (as if it would make any difference lol).

Eventually I fastbooted stock nougat and some components didn't flash, and some other issues.

Booted it and made initial config, rebooted to twrp, wiped and flashed august 1st build, still no NFC.

Will check the ram usage after reconfiguring device.
[X Style (Pure) Android Development] randomblame:
Are you running out of ram? Are you hitting situations where it's a problem? I disabled adaptive lmk to try to eek out some more performance
[X Style (Pure) Android Development] kadopt:
I've not fully reconfigured my device yet but it's better after all that fastbooting. Before, without zram, was impossible to use the device and with zram, after a while of usage ram was at 2.1GB and zram was at 500MB of 1GB. When changing between apps they were always reloading and the device itself was sluggish, working like my old SGSIII that only has 1GB of ram on Nougat.

Now the device is fine and I'm not even using zram, ram load is about 1.8GB.

I use EX Kernel Manager to configure the device and check for cpu and ram load.

Still miss NFC though, :( but I use it mostly to pay for stuff.

Thanks!
[X Style (Pure) Android Development] zohar_ml:
Is it possible to enable double tap to wake?

The speeker volume is a bit low. Iv'e set Audio FX to +15 for all 5 lines, but it's still not very loud. Can it go higher?
[X Style (Pure) Android Development] timmtn:
More nitpicking from my side.

Is any one else getting random volume issues. I can set my call/ring and alarm volumes manually, but as soon, as I get a message or a call, they tend to jump up in volume level, so that ringtones and notifications are always quite loud.

One time I was looking at the volume controls under settings\sounds and when I received a message, the volume sliders actually moved on their own.. I was not able to replicate this though..
[X Style (Pure) Android Development] kadopt:
Double tap to wake requires kernel support.

Volume can be tweaked in mixer_paths.xml file located in /system/vendor/etc/ but you have to know what to adjust.

If you adjust the "116" value to a higher value like "125" headphones output will be higher but silent sounds may be truncated as the dynamic range is low in this rom for some reason or there's some weird audio processing on the background.

<path name="headphones">
<ctl name="SLIM_0_RX Channels" value="Two" />
<ctl name="HPOUT1L Input 1" value="SLIMRX1" />
<ctl name="HPOUT1R Input 1" value="SLIMRX2" />
<ctl name="HPOUT1 Digital Volume" id="0" value="116" />
<ctl name="HPOUT1 Digital Volume" id="1" value="116" />
<ctl name="HPOUT1 Digital Switch" id="0" value="1" />
<ctl name="HPOUT1 Digital Switch" id="1" value="1" />
</path>

What you want to edit may be here:

<path name="speaker-and-line">
<path name="speaker-and-headphones" />
<ctl name="HPOUT1 Digital Volume" id="0" value="128" />
<ctl name="HPOUT1 Digital Volume" id="1" value="128" />
</path>

Reboot device to apply changes.
[X Style (Pure) Android Development] redwoodie:
Shutdown and boot issues 20190801 build

I did wipe cache and Dalvik, it worked fine the first time but on the second reboot it was back to the earlier behavior. Have not tried the dirty flash. Possible app issue?
[X Style (Pure) Android Development] kadopt:
It will happen again, it only "fixes" for the current boot, you'd have to wipe it for every boot. Dirty flash will not fix it.

I think it's OS related.
[X Style (Pure) Android Development] kadopt:
My device crashed and corrupted some files. After that it would hang for no reason making it in unsusable.

I went for fastboot again and noticed I used the us build of nougat, corrected that for EU build as my device is European and now NFC works fine.

However ram usage is still high... Maybe the nand has broken sectors or something. Does anybody know an app to check the nand for defective sectors?
[X Style (Pure) Android Development] insomniac89:
I have this issue, everytime I connect a bluetooth device that has a headset, volume goes to 100 for media. I feel like I've blown my ear drums enough already, just trying to keep that in mind.
[X Style (Pure) Android Development] Kenaz Rune:
Install wave up from f-droid.. Then you can wave over your phone to wake it. No root.

If you install magisk on your phone, you can install viper audio FX which will give you a massive volume boost with the right setting. Plus, with speaker Optimisation you can make it sound better.
[X Style (Pure) Android Development] kadopt:
Can anyone try the built in barcode scanner on the camera and see if it can focus? Mine does not focus and neither does in wahtsapp web qr scanner. Thanks
[X Style (Pure) Android Development] Pantherrra:
I had similar problems. QR code reader by Duy Pham works fine for me
[X Style (Pure) Android Development] tigger360:
I've got the weirdest workaround for this when I use WhatsApp Web. Take a piece of paper and use a pen to make a hole in it. Put the hole in front of the camera in order to darken the corners of the image. For some reason, this brings the QR code into focus. You may have to play around with the positioning of the piece of paper in order to make this work.
[X Style (Pure) Android Development] kb8no:
It seems to be app dependent. Microsoft Authenticator is broke and will not focus. Google Messages Web works great. Same camera, same ROM.
[X Style (Pure) Android Development] kadopt:
Thanks for the feedback.

Another issue, are your devices working fine? Mine is using lots of ram and gets sluggish, stutters, hangs, etc. I'm not even using a sd card anymore just in case although I've tested it and it's fine. Using the latest build, clean flash.

[IMG="ram usage"]http://www.firegoon.com/u/bftyyn.jpg[/IMG]
[X Style (Pure) Android Development] Brandroid28:
had the issue with the QR scanner. had to take a pic of it on another device and mirror it to the TV for my scanner to recognize it

also have the issue with the phone hanging. haven't monitored my ram. sometimes it'll hang for a few minutes before responding, other times it'll restart systemui and all my apps, and other times I get tired of waiting and wipe the caches. happens several times a day
[X Style (Pure) Android Development] freeqwerty:
This ROM worked fine over one two hours with pico GAPPS. But I find a problem when opening Viber, Google maps and Sygic navigation. The phone restarts.
[X Style (Pure) Android Development] Pantherrra:
No problems with Sygic nav or google maps here
[X Style (Pure) Android Development] kadopt:
[MENTION=3641368]Brandroid28[/MENTION]

Hum, I was thinking it could be hardware related on my part, like the nand being worn out, but guess not.

I'll full wipe and flash the July 14th build as it was the best build for me and report back. These locks and hangs just makes me crazy...
[X Style (Pure) Android Development] freeqwerty:
With what GAPPS and TWRP?
[X Style (Pure) Android Development] kadopt:
TWRP V3.3.1.0

GAPPS nano ver. August 19th, 2019, .
[X Style (Pure) Android Development] jehova666:
confirmed not focosing

best regards
[X Style (Pure) Android Development] tigger360:
I have also been experiencing the phone randomly hanging. There are some apps that seem to do do this more than others such as Facebook and Instagram. I was just a bit reluctant to report this as I do not know how to take a log that may be useful for the dev. I may try that some time this week.

I'm running the 200190801 build along with Magisk and GApps.
[X Style (Pure) Android Development] freeqwerty:
tigger360 Magisk v. 19.3?
[X Style (Pure) Android Development] kb8no:
[MENTION=3723165]kadopt[/MENTION] After the boot finishes are you getting "loading widget" when the clock fails to load and then "Process System isn't responding" error message?
[X Style (Pure) Android Development] tigger360:
Yip
[X Style (Pure) Android Development] kadopt:
[MENTION=4465682]kb8no[/MENTION]

It wasn't before but now it is, it may be related to the media scanner or something... I use animeboxes app to download picures and after loading lots of pictures into the device that symptom starts, even if you then remove the images.

But if I erase ART cache in recovery them it does not hang in that boot.

Didn't had time to wipe and reflash my device with older rom because i have some work projects to finnish.
[X Style (Pure) Android Development] kb8no:
[MENTION=3723165]kadopt[/MENTION] So this is weird, there is somehow a problem with something hanging during boot. See if you can repeat this. turn off the phone, let it set for half a minute. Get a timer ready (from your other phone). Then reboot the phone. Don't touch the phone. Start the timer exactly when the LOS boot screen ends and the lock screen pops up. Don't touch. Let the boot screen time out, takes about 12 seconds. Watch the timer. At exactly 1'30" you will see the black screen turns to a dark screen. In about 10" the the lock screen pops up. Don't touch and let the lock screen time out, takes about 15". Leave it for a few seconds (or to about 2 full minutes). Then push the on/off button to bring up the lock screen. Pop in your code and start the home screen. No "loading widget" or "process system isn't responding" to be found. Can you reproduce this?
[X Style (Pure) Android Development] kadopt:
[MENTION=4465682]kb8no[/MENTION]

I can try that later but for me to see if the system bug is occurring, after booting the device bluethooth will not be enabled (was enabled before rebooting the device) and wireless won't connect to anything. Also the alarm icon won't show up (if you have an alarm set up).

System will need sometime to figure itself out when bugging.
[X Style (Pure) Android Development] kb8no:
[MENTION=3723165]kadopt[/MENTION] OK, so I set an alarm, had wifi and BT on, and tried my boot process above. You are exactly right,"loading widget" and "process system isn't responding" came up. So I tried different permutations of the above and discovered that if there is no alarm set, then my process above works with WiFi and BT starting as they were when I had closed it down. Somehow the problem is related to the clock widget because "loading widget" and unable to start an alarm are both clock widget related.
[X Style (Pure) Android Development] kadopt:
[MENTION=4465682]kb8no[/MENTION]

It just may be the alarm being set because I use Xperia clock widget instead of the stock one, and it doesn't display the alarm, only on the notifcation bar.
[X Style (Pure) Android Development] kb8no:
[MENTION=3723165]kadopt[/MENTION] Honestly, I use Chronus clock and not stock clock but the stock clock gave similar "loading widget" complaints when I did a clean install. So it is something deeper than just the app you use in your clock I think. Hummmmm I just uninstalled the widget entirely and I will try booting again.

---------- Post added at 09:49 AM ---------- Previous post was at 09:39 AM ----------

[/COLOR [MENTION=3723165]kadopt[/MENTION] uninstalled Chronus widget. Rebooted in the normal way and opened immediately first lock screen (no waiting per my boot process). No BT, no WiFi, qiuckly got "Process System Isn't Responding". Then I rebooted again using my boot process with the 2 minute wait and all is good. BT and WiFi were remembered and came up. No "Process System Isn't Responding". So setting an alarm blocks something on reboot. "Process System Isn't Responding" only happens when I don't follow my boot process with the 2 minute wait. Likely 2 different problems.
[X Style (Pure) Android Development] kadopt:
[MENTION=4465682]kb8no[/MENTION]

I use chronus but for the weather widget. Ill try to do some tests without the widgets and/or the alarm set or not.
[X Style (Pure) Android Development] kb8no:
[MENTION=3723165]kadopt[/MENTION] I want to believe that the "Process System Isn't Responding" holds a big key to the issues people are facing. We need to get a log of booting and the first 2 minutes when that settles down to see what's happening and post it for [MENTION=1776875]randomblame[/MENTION] . I know how to take a log but not how to start a log at boot nor how to catch a log when the ROM crashes (i.e. how to fix the tether). Do you know how to do that? I use an app called SysLog but cannot figure out how to get a log at boot or at crash.
[X Style (Pure) Android Development] Flying Jesus:
Some help needed. I tried this ROM for my xt1572 & every requirement was met yet, like all other roms I tried except for the ROM by antariksh, neither of my sims were being read by the system. Moreover, the ROM kept on auto-rebooting my phone every time I put it down and it'd bring it back to TWRP screen. The issue is persistent & maybe this is what you guys were talking about in the comments above (not sure since I haven't followed the thread from the beginning) However if anyone can suggest me anything regarding fixing the sim reading issue please do, will be much appreciated! UWU
[X Style (Pure) Android Development] kadopt:
Dual sim variants are not supported, it's written in bold in the first post.

Use stock ROM.
[X Style (Pure) Android Development] randomblame:
Looks like I'll be working on Los 17 soon lol
[X Style (Pure) Android Development] xabr3:
Maybe Los17 would make it easier on the camera. (Wishful thinking)
[X Style (Pure) Android Development] freeqwerty:
Now am with TWRP 3.1.1.0. When update twrp-3.2.1-0-clark-N-decrypt, twrp-3.3.1-0-clark, twrp-3.2.3-1-clark, phone don`t wipe nothing. When wipe with this version on TWRP phone restarting and don`t wippin nothing. Wipe Dalvik, Chache... and other work only with 3.1.1.0. Where is a problem?

Sorry, my english is bad.
[X Style (Pure) Android Development] gkm45:
Dear randomblame,

Thank u very much for reviving the Moto X Pure Edition Unofficial Pie ROM and providing support for it.

I love the phone very much but had to switch it due to no updates to Essential PH-01. I'm about to change the battery and leave this ROM and try to use it as my daily driver.

I'm a noob so I took a long time to decide to switch and glad to finally have switched it. I understand that u have some personal issues and yet u still decided to do this and that's specifically why I wanted to msg u and thank u.

If u r ever in Austin, beer and tacos on me!