yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] randomblame:
It's likely graphics mapper use the 7/28.2 build for now
[X Style (Pure) Android Development] Brandroid28:
was night light or live display gonna be implemented? only saw one reference some months ago
[X Style (Pure) Android Development] zohar_ml:
My kid phone just broke down, so I took my old pure out to give him. While looking to update the phone I found this thread.

I clean flashed the latest build (28V2) and I only gave it a very a short run but it all looks very good!

I see that I can take both horizontal and vertical video and the output is good. The rotated image problem is only in camera mode. Do you think there will be a fix for this soon?

Can this ROM act as a daily driver?

Thanks for this ROM!
[X Style (Pure) Android Development] Pantherrra:
I have, as many others here, used this as a DD for months now. Very happy about it, runs very smoothly. Main issues are tethering (works but soft reboot when you stop) and the camera issue you've described. Until recently, using the camera was not possible so I have good hopes more progress will be made soon.
[X Style (Pure) Android Development] DjDill:
So I tried again to go to 28th V2 and got into the same issue as before with 29th. No GSM and high CPU with logcat spooling QMI_FW xport_reg failed

See attached

All dirty flashing

So back to 14 -> 28th

Maybe 28v2 would work for me if I clean wipe.
[X Style (Pure) Android Development] randomblame:
Try a clean install and let me know I have a long weekend so I can dig into it more, Gsm should be working I didn't touch that so I suspect it's from dirty flashing
[X Style (Pure) Android Development] kadopt:
[MENTION=698697]DjDill[/MENTION]

So 28th build is ok for you? Only 28th v2 and 29th are broken?
[X Style (Pure) Android Development] randomblame:
New build in op. Solves the power drain and performance issues. Please test NFC, not sure if my phone is broken or if there is a regression in lineage, it was working in December when we last messed with it.
[X Style (Pure) Android Development] tigger360:
Hi all, I've had an issue while flashing the 20190801 build. I dirty flashed from the 28.2 build, and when my device switched on, the mobile network stopped working. My device no longer shows an IMEI and says that no SIM is inserted. I tried rolling back to 28.2, but the problem persisted. Anyone facing similar problems? Any suggestions for solutions? Thank you.
[X Style (Pure) Android Development] DjDill:
NfC works fine - tested

Dirty flashed over 28 V1

Working fine GSM works

smoother then 28th

First boot apps on sdcard didn't load .. restarted all fine :good:

Thanks for the hard work

---------- Post added at 08:46 PM ---------- Previous post was at 08:44 PM ----------

Try dirty flashing back to 14th then 28v 1 then flash this 1/08/2019 or

That worked for me
[X Style (Pure) Android Development] tigger360:
Thanks. That gave me errors and so I ended up wiping my \system partition and re-flashing 20190801, then Gapps and finally Magisk 19.3. Everything seems to be working now. Will report back in a few days.
[X Style (Pure) Android Development] Pantherrra:
Mm I performed a clean flash. Wiped dalvik, cache and data, then flashed 20190801, then Gapps. I still have the same problem with the camera: it looks as if a photo is taken, the image freezes, and then nothing is saved. Recording videos works fine. Anybody else having the same problem?

Apart from that I don't see any other bugs. Booting goes fast, although trebuchet (?) always seems to load twice. And handwave gestures don't work neither but that has always been so, no? But it seems to run really smooth. I'll report back later if I find other bugs.
[X Style (Pure) Android Development] Brandroid28:
other times I've had this problem, I had to uninstall magisk before updating the ROM. then flash magisk after you've booted once
[X Style (Pure) Android Development] jorgemo57:
I also have the same problem as Pantherrra (# 835) :( , the camera takes the photo but it is not saved anywhere ... everything else seems to work correctly so far ... I will report errors if I can find them ... many thanks for the good work !!! ... continue with him please !!! ..
[X Style (Pure) Android Development] tigger360:
Are these in the stock camera app? I'm having similar troubles in apps that use the "screenshot of viewfinder" method, but the simple work around is to take pictures using the stock app and import them from gallery.
[X Style (Pure) Android Development] jorgemo57:
Correct, I am using the stock camera ... I will try some alternative tests and also with your method to see if I achieve any positive result, thank you very much !!! ...
[X Style (Pure) Android Development] zohar_ml:
Dirty flash from 28v2 without any problem.

Camera and phone working great
[X Style (Pure) Android Development] kb8no:
I only had problems with battery on 7/29. Reflashed 7/28 v2 and it was back to my DD and working well. I just flashed 8/1 and seems good. I have only been dirty flashing. My camera stock camera has always worked except for the known wrong rotation on portrait which doesn't bother me much.
[X Style (Pure) Android Development] Psychopompos:
I have the same camera issue as well, but 8/1 fixed my battery drain. I'm sure this will eventually all get sorted, and I want to thank everyone in this thread for their efforts!
[X Style (Pure) Android Development] AgathosAnthropos:
Now that I actually tried to activate my phone for full use (was going to try it for a DD). But I keep getting mobile radio power off (even in the *#*#4636#*#* menu). And it won't really do anything with LTE/CDMA (on Sprint). Thoughts anyone?
[X Style (Pure) Android Development] joheli:
Now, that the ROM is as stable as it is (except for one or two minor issues here and there), is it possible to look into activating the ambient display with the near field sensors and the night display? They used to cause some problems in the past.

And btw a big thanks to randomblame an all other contributors to making this ROM exist!

Regards, Joheli
[X Style (Pure) Android Development] kb8no:
I worry about whether you are on bone fide nougat firmware that is not hacked. Try flashing stock Nougat clean install. Prove you are on Nougat firmware.and that Skype works on stock.. Then clean flash 16.0 and see what happens.
[X Style (Pure) Android Development] kb8no:
I am using 7/28 v2. My battery was getting weak and funky as they do. I could see it coming and had an Ebay 3300 mAH aftermarket battery on stand by. In installed it 5 or 6 days ago and my battery lasts a whole day without need for a top up charge. It is typically still about 20-30% by bedtime. That is as good as it can get with this phone. I'd say that 7/28 v2 is very tight with power usage. Nice job [MENTION=1776875]randomblame[/MENTION].
[X Style (Pure) Android Development] kadopt:
NFC does not work in August 1st build, can anyone confirm? It's working in 14th build
[X Style (Pure) Android Development] randomblame:
Yeah I think it's dead need to mess with it
[X Style (Pure) Android Development] AgathosAnthropos:
Turns out I didn't have a clean flash of the Nougat firmware due to a bad USB cable. All better now, thanks for at least helping get me going in the right direction.
[X Style (Pure) Android Development] kb8no:
[MENTION=9796853]AgathosAnthropos[/MENTION] it's surprising how the concept and execution of a clean upgrade to Nougat causes so much pain. Moto stock flashing is so non-intuitive doubling the pain. Glad it is working for you. Do not take any OTA upgrade of stock nougat as it has no advantage and as a new bootloader you can't go back.
[X Style (Pure) Android Development] randomblame:
I thought the problem was fixed with the modem assert lol
[X Style (Pure) Android Development] kb8no:
I hope I don't embarrass myself here discussing nuances with the Queen. LOL. When you upgrade from Marshmallow to Nougat you upgrade the firmware. When you are on the wrong firmware all sorts of things don't work and blow up in your face. Hence the endless problem explaining the difference between Hashbang's LOS 14.1 official (Marshmallow firmware) and unofficial (Nougat firmware). Complicating things is that you can't just downgrade from Nougat to Marshmallow as far as I know so you are stuck on Nougat once you upgrade firmware, yes? This is not necessarily true with other hardware manufactures and people have done this with other phones before and that is still in their memory.

Firmware includes modems, boot loaders, and a bunch of other things unique to Motorola and uniquely needed for the hardware, yes? So Hashbang addressed the wrong firmware problem so you couldn't load his 14.1 ROM's on the wrong firmware with a blacklist "assert" and he used the bootloader version as a marker of which firmware you have on your phone, yes? He continued that into his Android 8 and you continued it into Android 9, yes? The assert does not check for the modem version. So if you try to mess around flashing different modems and/or get a bad flash, only the bootloader assert will save you but if you happen to have the firmware all screwed up but the bootloader is good then you can get all kinds of nonstandard goofy badness without knowing that it is a firmware problem.

It has taken me years to sort of understand this. Is my paraphrase broadly correct?

BTW... Any luck on the tether problem? I need my tether for work and after shutting off the tether and recovering from the forced reboot the phone takes awhile to settle down and it is not smooth reboot.
[X Style (Pure) Android Development] Pantherrra:
Could this explain the camera issues me, [MENTION=8408091]jorgemo57[/MENTION] and [MENTION=10060246]Psychopompos[/MENTION] are experiencing as well? I was pretty sure I did this correctly but I can't remember exactly. How do I verify this so I can rule out this option?
[X Style (Pure) Android Development] kb8no:
Yes, I think so. This thought actually passed through my mind when I read your posts. Doesn't make sense that your camera wouldn't work. Firmware incompatibilities gives seemingly weird symptoms that don't make sense. Flashing Moto X Pure stock Nougat is such an unusual process. And you have to prove that each one flashed and sometimes a piece doesn't flash and have to be flashed again. So try it, only cost is time. Flash a clean Moto stock Nougat. Prove that it works. Then flash randomblame 16.0 and see if it works now. It's free and nothing bad happens.
[X Style (Pure) Android Development] randomblame:
Actually the current assert checks the modem firmware rather than the bootloader but that doesn't mean there won't be other issues from incompatible firmware I just thought the ril incompatibility issue was solved but evidently it is not. Haven't had time yet this week to get any work done too much other nonsense in my life if you can catch a log up to that soft reset it would be handy
[X Style (Pure) Android Development] Psychopompos:
I was thinking this as well. I wiped and returned to [MENTION=1689574]HashBang[/MENTION]'s Nougat, then returned to the 7/28 v2 from [MENTION=1776875]randomblame[/MENTION] . That made progress - my NFC is working, the built in Lineage camera works, but the Moto camera is still not working for me (but perhaps I'm mis-remembering that it is working for others). In any event, the other downloaded cameras are also not working. All else seems to work just fine, so the camera issue seems odd. I was hoping not to trouble to flash full stock Nougat, but that seems to be the necessary missing step.
[X Style (Pure) Android Development] insomniac89:
[MENTION=10060246]Psychopompos[/MENTION] This is the same for everyone I think, only the lineage camera app or the O2cam/Snapchat ones that use lower red screen capture tricks
[X Style (Pure) Android Development] DjDill:
Appears to be working for me.. I was able to beam stuff just now

See attached
[X Style (Pure) Android Development] kadopt:
[MENTION=698697]DjDill[/MENTION]

For me NFC doesn't event stay on, it kept toggling itself on and off, so I went back to 14th build.

I have to refresh the device anyway to in the weekend I'll try again.
[X Style (Pure) Android Development] jorgemo57:
.. Hello everyone! .. I share a small history and some "curiosities" ... when I said that my stock camera did not "save" the photo was in build 07/29, try to see if it worked with "Open Camera "(by Mark Harman) or with" Manual camera "(by Lenses Inc.) and there was no change ... seeing this I decided to make a" clean flash "and installed 07/28 v1..here" stock camera "worked well with the well-known "failure" of saving the photo at 90 ° ... "Open Camera" did not work in any way ... and here the first "curiosity" .. "Manual Camera" took two photos correctly (but rotated 90 ° ) but from the third photo the app stopped working ... that is to say, it behaved again as in 07/29 ... while doing these checks I read in forum the message # 842 of [MENTION=10060246]Psychopompos[/MENTION] that talked about the good battery performance of the build 08/01 therefore I decided to try it ... I made the flash (dirty) and .... "stock camera" working as we know .. "Open Camera" and "Manual Camera" don't work, t they take the picture but they don't save it ... so, let me know why, it occurred to me to install the app "Cameringo" (by Perraco Labs) .. here the second curiosity begins, the app works correctly and without, until now, turn the photo, which also does not look like a "screenshot", the information of my last photo says this: 8.3MP 2160x3840 1.4 MB .... quality does not seem to be lacking, the colors are crisp and bright, some of you confirm it ?? .. thank you very much !!!! ... for the moment I am not going to move from 08/01 ... the battery really has a very good performance ... during the weekend I will test if NFC works ... a Last thought, it is like very crazy all this, no ?? .. greetings to all !!! ..

PS: I hope Google's online translator is doing the job well :RE ....
[X Style (Pure) Android Development] randomblame:
The cameras should be working at native resolution in the built in camera app. The only breakage is in post processing now which prevents the images from being rotated based on device orientation. The open source Hal is hacky but it works where as the wrapper and ancient blobs are no longer workable
[X Style (Pure) Android Development] Psychopompos:
Gotcha [MENTION=6672417]insomniac89[/MENTION]. In that case, mine seems to be as fully functional as any. Sim is recognized, Lineage cam works (although it saves 90 degrees off as reported), NFC works.

Up until a build or three ago, I had functional Moto camera app, but not Lineage camera. Then the Moto camera started doing the 'image freeze but not saving' thing. Since my original camera apps had been working (just not the Lineage camera), I misinterpreted what others were experiencing. Apparently, on one flash or another I may have simply overwritten whatever lucky fluke I had and brought myself in line with the rest.
[X Style (Pure) Android Development] AgathosAnthropos:
That's interesting. I kept wondering if I should stop trying to hack something in the new HAL or try to go back to the old blobs/hal, apparently I made the right choice of stuff to try :)
[X Style (Pure) Android Development] randomblame:
Yeah fixing the oss Hal is the ideal solution for sure otherwise the blobs need hex edited and the wrapper needs redone
[X Style (Pure) Android Development] kb8no:
So I have had great luck with the camera and don't care much about the sideways portrait photos. I have been dirty flashing like a banshee and camera continues to work after it was jumps started. However, I took a few videos of my rain gutters during a down pour to demonstrate to my contractor. Next time I went back to the camera it did the "freeze and not save" trick. Never had this problem before. No amount of back flashing to previous builds would make the camera work. I then did a complete clean flash including internal memory. Camera now works again. Just in case this tidbit of information might be a clue, I am sharing this experience.
[X Style (Pure) Android Development] Pantherrra:
Thanks for sharing, and interesting. I'm still stuck with this as well. I'm wondering what you've flashed before, starting from stock. Have you been flashing roms other than randomblame's? I've been going through these posts again and it just seems hard to draw any conclusion with everyone having a different flashing history (including clean flashes). Maybe just for clarity we should all report flashing history + symptoms, just to have some insights, before I start thinking these issues are idiosyncratic... :) Then again, I'm still using this as my DD and very happy about it.
[X Style (Pure) Android Development] kb8no:
Way back history and I have 5 phones but this phone I took OTA Nougat and then only Hashbang 14.1 & 15.1 and randombang 16.0. I'm quick to clean flash but dirty flash 16.1 lately. I think you can't go wrong with clean flash.
[X Style (Pure) Android Development] ac2323:
I ran a full wipe/clean flashed 8/1/2019 and lost mobile data access, coming from stock Nougat. Modem check during flash was successful (running min version). Model is XT1575 on Sprint. Restoring backup restores mobile data functionality, so seems like an issue with LOS 16.0. Any ideas?
[X Style (Pure) Android Development] kb8no:
I use ATT and Verizon and never tried Sprint. My question is if you checked the APN? They do not always important correctly. You don't flash modem with LOS because it is firmware so am I confused?
[X Style (Pure) Android Development] ac2323:
I didn't check the APN settings but from my quick glance, APN settings could not be set from within the OS. I was planning on using this as my daily driver but as soon as I noticed the issue, I had to revert to Nougat as it was a dealbreaker for me.

I noticed that I am having the "missing baseband" from the fastboot screen issue that some in this thread had, though I don't know if that was an issue before I flashed and just didn't notice.
[X Style (Pure) Android Development] kb8no:
APN can be set by network - mobile network advanced. If Sprint is like ATT & Verizon the SIM will import several options and if you are lucky it will pick the correct one. Install and first boot ROM with SIM installed. Sometimes it picks none and you have to make the choice.

Missing baseband is likely your real problem. Do you have missing baseband in stock Nougat? I can not remember exactly how that went but I think it happened messing around between Marshmallow and Nougat firmware. You need a clean transition to Nougat and then only use Nougat ROM's. Reflash stock Nougat and make sure each piece flashed. If not, flash that piece again. Modems notoriously require more than one flash. Once you have working Nougat with all the firmware including baseband and bootloader you never again have to mess with firmware again, they are just there. Then 16 should install correctly.
[X Style (Pure) Android Development] ac2323:
I just checked and I do not have missing the baseband in stock Nougat. I've only ever updated the firmware via official OTA updates.
[X Style (Pure) Android Development] kb8no:
Sorry, i don't want to offend you but I want to keep it basic. Check APN in Stock and make note of whats there and what is checked. If you took the Nougat OTA you have Nougat firmware including modem baseband and bootloader.

What TWRP version do you have? It can't hurt to have the latest TWRP. Confirm you have an unlocked boot loader but if you made a backup of stock you must have a working recovery and unlocked bootloader.

Download 16.1 8/1/19 again in case your last download was corrupted. Download latest Gapps nano again. Move those to ext SD card.

Clean flash with TWRP. Wipe everything except ext SD. Now flash only 16.1 and Gapps nano from ext SD together, nothing more or nothing less. Allow TWRP to change system and reboot system.

When you get to lock screen give the ROM time to initialize the SIM, you can see the bars and LTE indicators in the notification bar of the lock screen. It will probably not initialize or connect right away.

Don't unlock the lock screen and jump into the ROM yet. Let it sit for 10 minutes for good measure. Then see if you have LTE and make note. Then unlock the screen and jump into the ROM. Double check the APN and confirm it was imported correctly.

It should work.
[X Style (Pure) Android Development] timmtn:
Just installed. seems to work as intended. Strange with the camera rotation issue.. Shows how many bloody little bits have to align perfectly, for modern electronics to work =)

Noticed on mine, that after flashing, half the data on my SD card was not readable by the phone.. fortunately it worked fine when plugging into my laptop, so I was able to make a backup. After formatting it, in my phone, it appears to be working fine.

I am missing a setting, in order to disable the charging LED though..
[X Style (Pure) Android Development] kb8no:
Wonderful! If you read back the smart people explain about rotation being done in post processing as an add on process in the camera and their workaround ended before it got to the add on processing. They are still working on it but it is outside my box, for sure. SD card formatting has always been touchy and your experience is common. You should now be good to go with your SD. If your biggest problem is the charging LED you are sitting good. I believe there is a way to fix that but I do not think it is in an Android setting. Maybe somebody listening in will know the answer and let you know. There was no APN problem then?
[X Style (Pure) Android Development] timmtn:
Normally I remove my SD card during any sort of wiping and flashing, just to make sure.. One time, I somehow managed to wipe my SD card while changing ROM.

I have had no APN issues. But I can see that it has the whole list of all the APNs running on the same network. But it appears to have selected the correct one automatically. I have seen this before on custom roms, where it would sometimes select the wrong APN, and I would have to clean out everything except the correct one, to make sure it did not suddenly cycle to the wrong ones.

The charging LED, is actually kind of a dealbreaker for me.. And until I installed this ROM, I did not know that the phone had an LED under the top speaker. I was hoping to keep my phone unrooted, because of some banking apps, that wont work when rooted. But I will probably need Root to disable it, since there is no setting under Display/LED.
[X Style (Pure) Android Development] kb8no:
If you are doing a clean flash you should wipe your internal memory and you must have an external SD with your zips. If you are worried about your SD then back it up.

Use Magisk to gain systemless root and your banking apps and other things like Netflix will work too.

Your experience with APN is how it is supposed to work. Even if it picked the wrong APN like it sometimes does just make the correct selection. No need to delete everything else.

Maybe someone will tell us how to turn off the charge light.
[X Style (Pure) Android Development] timmtn:
I rooted by installing SU through TWRP, and found an app that lets me disable the light.. oddly enough the banking app still works. Despite not working on Ressurection remix, which was using Systemless Root.. Fairly confusing stuff =)

Anyway. I will stop flooding this thread now. Just wanted to let the Devs know that the ROM seems to work quite well.

On with the Fixxerizing of the Blobs and whatnot..
[X Style (Pure) Android Development] xabr3:
Not sure, found this:

"To turn that off, go to settings, then notifications and then touch the settings icon in the top right corner. There you will see an option about battery light. "
[X Style (Pure) Android Development] Strephon Alkhalikoi:
And if that doesn't work, a LED control app with color set to black should.
[X Style (Pure) Android Development] timmtn:
Damn. It works =)

Thank you good sir.