yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] markboy08:
So I'm thinking of going from my stock, bootloader-locked. Nougat XT1575 to this ROM. A few questions:

Can anyone elaborate on the camera issue -- when you rotate the phone into portrait position to take a photo, does the screen show the subject in portrait, but the picture just gets save in landscape orientation? If so, does the picture get cropped, i.e. you lose quality, or is it simply displayed full scale sideways (which can be easily fixed with a photo editor?

Given that I am already on Nougat Firmware (see pic), is this sequence of steps about right (been a few years since I last flashed a phone):

Unlock bootloader

Flash TWRP (twrp-3.3.1-0-clark)

Boot into recovery and do a Wipe Data/Factory Reset, then the following flashes:

Flash this ROM

Flash GApps (ARM64 9.0 nano)

Flash Magisk for root

Am I on the right track?

Since I don't currently have root or an unlocked bootloader, any advice/tricks on best way to backup my current apps/data/config for the most painless port over to the new ROM (or restore if I have problems)? My understanding is that when you unlock the bootloader it wipes everything.

Thanks!!
[X Style (Pure) Android Development] kadopt:
[MENTION=6710465]markboy08[/MENTION]

1 - For the front facing camera, after the image is saved, orientation is not respected, to fix just rotate the image with any image editor. Rear camera works fine.

2 - Seems fine.

3 - Unlocking wipes you devices. Just save your personal data, don't migrate app data between different ROMs.

This ROM has an issue for some users where the device hangs for a while after some multitasking, I think July 14th build with patch does not have that issue, but I haven't confirmed that yet.
[X Style (Pure) Android Development] kb8no:
You are on track. You normally get Nougat firmware by getting to stock Nougat. You must be coming from a properly flashed stock Nougat firmware. If you got to Stock Nougat by fastboot and not OTA, flashing the modem zip doesn't always take on the first flash ("fail") so you need to watch each zip flash carefully. Simply re-flash the modem zip until it is successfully flashed. Incorrectly flashed Nougat firmware is one of the biggest headaches.

This needs to be a clean install so give up getting a "painless" flash. Save any data you want to keep including external SD and internal memory to your computer. Start over from scratch. Place on the SD card the LOS ROM and nano Gapps as usual. I also download MagiskManager apk and put that on the SD card as well. After booting into TWRP recovery, wipe everything except external SD card. You do not need to do a data/Factory Reset, just wipe everything in TWRP. Then flash LOS and Gapps. After it boots let it sit without touching it for 5 minutes. Then go through the Google login.

Install the MagiskManager app from the SD card. Follow your nose and let the app install the Magisk zip. Sometimes LOS doesn't like the formatting on your SD card and you have to re-format using the ROM even though TWRP didn't complain. Save yourself a headache and every time you boot LOS let it sit 2 minutes from the time the LOS boot screen quits and the lock screen starts. Read above for the reason. Re-install all your favorite apps. There is really nothing wrong with the camera. It just saves a normal portrait sideways. You can use the Gallery to rotate it 90 degrees if you care. Tether works just fine except it will crash the phone when you shut off tether, both WiFi or USB. Rarely, Chrome freezes and locks the ROM. Let it sit and it will come back.

Other than these nuances, it is very serviceable and I like it much better than stock. It has been DD since they fixed the camera. Once you are on LOS and you want to flash a new version or re-flash what you were using you are best advised to still use a clean flash but you don't need to wipe internal memory. You can try to dirty flash an LOS update and it works sometimes. Magisk will come along with any re-flash (very cool). I always keep a copy of LOS and Gapps on both the SD and the internal memory in case the external SD gets funny. You can always fastboot back to Stock Nougat. I back up my ROM's with TWRP saving to the SD card.

Enjoy.
[X Style (Pure) Android Development] markboy08:
Thanks! I got Nougat OTA (bootloader is locked). I am at Build NPHS25.200-22-1 Baseband "M8992_1255331.29.01.88.09R SUPER_NA" -- so I assume there is nothing I need to do firmware-wise?

I was thinking of using Helium for the initial backup prior to bootloader unlock, and then reloading what I can from the Helium backup after I update to LOS. After that, I'd plan to use Titanium, e.g. if I need to restore apps/config after a clean flash. Any pitfalls to this approach (e.g. would backing up on old ROM and restoring on new ROM using Helium mess things up -- I got the impression Helium does more of a "logical level" backup so it might be OK)?
[X Style (Pure) Android Development] kb8no:
[MENTION=6710465]markboy08[/MENTION] Your OTA Nougat is good to go. You can try Helium / Titanium but I would recommend you install everything from scratch with a complete clean install on your first flash of LOS. Then you will know what to expect. After that you can play around but typically you can just dirty flash a new build without Helium / Titanium. Sometimes there are enough changes with a new build that a dirty flash is not enough but you will then know what to expect. If you try them and you trash the ROM nothing bad happens, just re-flash it.
[X Style (Pure) Android Development] freeqwerty:
How is install this patch? Together with ROM and GAPPS?
[X Style (Pure) Android Development] kadopt:
[MENTION=7455330]freeqwerty[/MENTION]

Flash it after flashing the rom in recovery.
[X Style (Pure) Android Development] freeqwerty:
After install ROM and GAPPS need to wipe chache/dalvik or no? Am always wipe chache/dalvik.
[X Style (Pure) Android Development] kadopt:
[MENTION=7455330]freeqwerty[/MENTION]

In that case yes.
[X Style (Pure) Android Development] xabr3:
Only LineageOS camera works to take "real" pictures.

Others do not work of just take a screenshot of the preview.
[X Style (Pure) Android Development] kadopt:
Regarding device hanging ...

I've dirty flashed back (wiped Art cache, System and Cache partitions) to July 14th build with patch from august 1st build and now the device no longer hangs.

Something in memory management must be broken after that build.
[X Style (Pure) Android Development] kb8no:
[MENTION=3723165]kadopt[/MENTION] Djdill patch came from 7/21 for 7/14 ROM. You are talking about a patch from 8/1. Am I missing something here? BTW I flashed 714 ROM with 7/21 patch and it is snappy again! Tapatalk was hanging as well as Chrome and now Tapatalk loads the threads as it should.
[X Style (Pure) Android Development] kb8no:
[MENTION=3723165]kadopt[/MENTION] Djdill patch came from 7/21 for 7/14 ROM. You are talking about a patch from 8/1. Am I missing something here? BTW I flashed 7/14 ROM with 7/21 patch and it is snappy again! Tapatalk was hanging as well as Chrome and now Tapatalk loads the threads as it should.
[X Style (Pure) Android Development] kadopt:
[MENTION=4465682]kb8no[/MENTION]

No new patch. As I said I was in 8/1 build and downgraded to 7/14 build plus patch. De vice no longer hangs.
[X Style (Pure) Android Development] kadopt:
The fórum is messed up, either double posts or makes weird quotes...
[X Style (Pure) Android Development] kb8no:
Tether Tips: Both WiFi and USB tether work fine but closing them forces a soft reboot. If you configure WiFi tether settings after starting WiFi tether they will not stick after the forced soft reboot. The work around is to start WiFi tether from Android Settings before actually starting WiFi tether. Then configure your WiFi tether settings and your settings will stick. It's an inconvenience but worth waiting through a soft reboot when you need tether.
[X Style (Pure) Android Development] andrejazzz:
Hi all,

I flashed this rom to my mum's phone already when the camera was not working. I have experienced no major bugs ever since, congrats on the stability!

With the August 11 Rom, I run into two problems however. I am curious if I am the only one experiencing this problems, or that others recognise the nuisances.

The focusing does not always work with the camera app. 50% of the time resulting in not being able to take pictures at all or out-of-focus stills. For me it would be just annoying, but well... It's not my phone :p

A significantly more annoying problem is the following, which I hope you can help me with:

Incoming and outgoing calls from/to landlines are without problems. However, when calling from any cell phone (iPhone, Android, dummy phone) to the Moto X, the outgoing sound level is showing a wave-like behaviour. That is, when answering a call on the MotoX there are no signs of this problem. On the other side, the volume appears to be going up and down continuously, making cell-to-cell calls almost impossible. The signal is not the problem, since I tested at different locations and coverage is perfect (everywhere in the Netherlands). Also, when calling through a wired headset, the problems seems to vanish.

All in all I think this is a software issue, so I am curious if I am the only one with this problem.

Thanks for your help!
[X Style (Pure) Android Development] freeqwerty:
And so. After many attempts to install this ROM and the phone always restarted. I reinstalled with stock ROM 7.0 (I was NucleaROM 7.1.2). And for the second day I have no problem with this ROM, the battery is not warming up as before and the ROM is running very smoothly. Thank you so much. How can i root this ROM? Magick 19.3 working with this ROM?
[X Style (Pure) Android Development] kadopt:
[MENTION=7455330]freeqwerty[/MENTION]

Yes, just flash latest Magisk in recovery.
[X Style (Pure) Android Development] freeqwerty:
The phone is already rooted. Thank you.
[X Style (Pure) Android Development] svp123:
does this rom support project treble , plz let me know whoever have flashed this rom , if not any suggestions where to look
[X Style (Pure) Android Development] Strephon Alkhalikoi:
No. Project Treble, while mostly software, does have a hardware component. Motorola would have had to perform a low-level repartition of the internal storage in order for Project Treble to work. As the device's upgrade path ended at Android 7.0, and Project Treble was introduced with Android 8, Motorola never did this. In addition, phones upgraded to Android 8 aren't required to support Project Treble, so Motorola wouldn't have bothered in any event.

None of the custom ROMs support Project Treble because of this, so if looking for Project Treble support you won't find it here.
[X Style (Pure) Android Development] zohar_ml:
I gave my old pure to my son and installed this rom on it.

Everything is working great except for one issue.

While in phone call, if he set on the speaker of the pure the other side of the call hears himself with a very big echo.

It's as if the pure does not filter out of it's microphone the sound it just played in it's speaker.

I searched the forum for this issue, but did not find any mention.

Any idea about this?
[X Style (Pure) Android Development] svp123:
yes , this information is officialy correct but I have seen some older devices getting treble support by flashing a (special) rom and then flashing GSI roms, there are other implementations also which I have seen in this thread

https://xdaforums.com/project-trebl.../tool-capire-le-treble-terble-vendor-t3774629

that's why ive been asking if anyone tried to implement this
[X Style (Pure) Android Development] Strephon Alkhalikoi:
This has already been answered. No it hasn't, and if you need a reason as to why, the device isn't popular and as a result, there are not enough developers. If you want it, you're gonna have to do the work yourself.
[X Style (Pure) Android Development] zohar_ml:
So is it only me with this speaker echo issue? can it be modem firmware related?

I have build date jul 31 & baseband M8992_1255331.29.01.88.09R
[X Style (Pure) Android Development] freeqwerty:
I am also have this baseband , and no have a this problem with echo.
[X Style (Pure) Android Development] xabr3:
Any updates on this ROM regarding camera? :)
[X Style (Pure) Android Development] freeqwerty:
In this moment, this ROM no have updates.
[X Style (Pure) Android Development] joheli:
Now up and running on trainwreck-edition 2

Seems to work fine on Thema first glance
[X Style (Pure) Android Development] big_marcolino:
[MENTION=1776875]randomblame[/MENTION] Don't forget to update OP description :)
[X Style (Pure) Android Development] randomblame:
Done
[X Style (Pure) Android Development] big_marcolino:
Why camera is broken and working at the same time in OP?
[X Style (Pure) Android Development] randomblame:
Typo fixed
[X Style (Pure) Android Development] Quigongentoo:
This makes me a bit excited! If you get this working.... I mean fully working... My beloved Pure can stay where it belongs, with me! Thank you for your time! I'm sure Santa will bring you some great stuff. ---money---. For being such a good code elf! :laugh:
[X Style (Pure) Android Development] randomblame:
Can anyone confirm if sensors are working on that last build? I have them now working sometimes on new builds but it takes a minute after boot for them to be up and running and it's inconsistent
[X Style (Pure) Android Development] moviefirst:
Hello randomblame,

I think only the wake up sensor is not working.
[X Style (Pure) Android Development] joheli:
Rotation works fine, the head-detection while making a Phone call too, I haven't tested the compass yet and the near-field moto-sensors are not working for meine

Running trainwreck-edition 2
[X Style (Pure) Android Development] randomblame:
And it works consistently across reboots? Possible my pure is just too physically broken
[X Style (Pure) Android Development] moviefirst:
After rebooting, the sensors didn't work immediately. 4 minutes after rebooting they're working again. I'm using the app devcheck to check the sensors. Only the near by sensors don't work.( Ambient)
[X Style (Pure) Android Development] randomblame:
I'm not seeing any obvious problems with sensors in logs this is a strange issue they should be up immediatly
[X Style (Pure) Android Development] moviefirst:
Maybe the app what I am using isn't reading immediately. But the near by sensors are not working.

They are not showing on the screen. 4 little red lights.
[X Style (Pure) Android Development] Nuzzlet:
Will be flashing as soon as the cameras are working. I can't program, but can I donate to the project?
[X Style (Pure) Android Development] randomblame:
There is a button, donations will go towards a less broken pure to work on mine has had it. ?
[X Style (Pure) Android Development] big_marcolino:
Me too
[X Style (Pure) Android Development] randomblame:
Sensors work fine after device sleeps while not plugged in. Weirdness.
[X Style (Pure) Android Development] :
You've been working on roms since Ice Cream Sandwich! The good ol days...
[X Style (Pure) Android Development] randomblame:
Far longer than that I'm afraid, I think my first Android work was on my LG incite which shipped with Windows mobile there was a tool called haret used to load the Linux kernel and take over the system from within winmo and from there I had linux 2.6.27 ported and donut. Had to write a driver for that lcd from scratch and touch never worked but it was fun
[X Style (Pure) Android Development] Fabiett83:
You made me remember my old HTC Touch Diamond... i think i still have it somewhere...

The diamond too shipped with WM6.1 but with HARET it was possible to boot android from SD...

Thank you for your work, i will jump on the PIE Train when the camera will work, even if bad, i use it everyday.
[X Style (Pure) Android Development] gcdevelops:
hello,

does anyone has tried device encryption with this rom?

plus another question, I am actually using the latest lineageos 14.1 by hashbang on my xt1572, nougat modem. I am very happy with this rom, so i am not so sure to change for now, is there someone who has tried both roms? wich is better? thanks in advice
[X Style (Pure) Android Development] kb8no:
I don't use encryption, someone can jump in. Most all of us on this ROM used hashbang 14.1 and migrated here full time when they got the camera working. This is much more fun. Make a backup of 14.1 and try this! No risk. Few little workarounds that you can read about which does not make me want to go back. Be sure to use Gapps nano or pico. Bigger Gapps over wrights the working Lineage camera. There is some kind of boot delay and be sure to just let it sit for a few minutes or you will get error messages. Tether works but gives soft reboot when you turn it off. Randomblame's latest ROM's are borked and we are using an older 07/14 ROM with a patch. Just read back a bit to find it. That's it for now.
[X Style (Pure) Android Development] freeqwerty:
Use this combination, work perfect. Тhe battery also lasts much longer.
[X Style (Pure) Android Development] Kenaz Rune:
Will we see any more updates for this rom?
[X Style (Pure) Android Development] AgathosAnthropos:
I've been working on doing a latest 16.0 build (w/o any new updates for bugs like system crash on startup or NFC) but I'm having issues with my PC and the builds keep not booting correctly, so hopefully soon but no guarantees.
[X Style (Pure) Android Development] Pantherrra:
I've noticed that the sound volume through my bluetooth headphones is remarkably low. I have tried to fix that with ViPER4Android FX, as mentioned before here, but the extra gain is insignificant. Anybody else got an idea? Other than that: still using this ROM as my DD and very happy with it. Thanks again to all the contributors!
[X Style (Pure) Android Development] Fabiett83:
I don't think it's your PC, i made a clean build from randomblame's repo with my pc and it's bootlooping for me too.

i'm trying to understand what's happening with logcat right now.

Found a Zygote error in logcat:

java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {
com.qualcomm.qcrilmsgtunnel: android.permission.INTERACT_ACROSS_USERS,
com.qualcomm.atfwd: android.permission.INTERACT_ACROSS_USERS,
com.quicinc.cne.CNEService: android.permission.PACKET_KEEPALIVE_OFFLOAD}

adding privapp-permissions-qti.xml in system/etc/permissions made my build boot
[X Style (Pure) Android Development] AgathosAnthropos:
Thanks, that got it to build and start but Play services crashed on unlock and tried to reboot and now back to boot loop to TWRP, so I may attempt full wipe and reload.

Did a clean and reflash of everything is now working okay. In case anyone wants an update - it has the above file already applied so it should just work.

https://www.androidfilehost.com/?fid=1899786940962612766

md5:

7d79c398ed07284081949cb553391a1c lineage-16.0-20191019-UNOFFICIAL-clark.zip
[X Style (Pure) Android Development] tigger360:
Thanks for this. I'll be sure to give it a try.

I know it might be a little early to tell, but how does the battery life on this build compare to that of randomblame's latest build? I'm kinda struggling to get decent battery life on that one.
[X Style (Pure) Android Development] AgathosAnthropos:
It's not my DD, so not sure. Just made sure it booted and a few things worked. It chewed through battery on first boot but I've got original battery and it doesn't seem as good anymore.
[X Style (Pure) Android Development] kb8no:
AgathosAnthropos 7/14 build with patch (see post 953 for links) has no battery problems. randomblame 2 subsequent builds had regressions including poor battery life so we use 7/14 build and not randomblame builds right now.
[X Style (Pure) Android Development] Fabiett83:
Thank you,

I installed your rom over my 20191017 build without wiping and it's working.

If i understood correctly you rolled back 07/28 and 29 randomblame commits, which I had not done.

I will compare the battery life of yours and my build in the next days.
[X Style (Pure) Android Development] kb8no:
Dirty flashed 10/19 over 7/17 patched. It booted fine with 10/5 security patch. Thank you! The glitches are the same which you said were not addressed. Sure would be nice to get the system crash on boot thing fixed. Any chance?
[X Style (Pure) Android Development] xabr3:
So, what is the best build until now, without crashes and with good battery life?
[X Style (Pure) Android Development] AgathosAnthropos:
This is what I was going to try looking at next. Also, does NFC work for anyone/everyone?
[X Style (Pure) Android Development] carl.13:
Thanks so much. Have revived my old moto x pure, which I love because of the wide screen and stereo speakers. Nothing like it now.

Alas, I fear the battery's now past it's best & screen has dreaded blue and red blotches.

Being a stroke victim it is going to be a problem to replace. On the bright side, I understand there are new, boxed units to be had.

Everything seems to work, but can't test NFC. {charging led, thanks. Am I missing something can I use this for notification}

Magisk,& Rooted.

Look forward, if you have time, to Android 10.

Thanks again, Carl
[X Style (Pure) Android Development] moviefirst:
Is it possible to get handwave gesture to activate the screen when getting notifications?

And when getting notifications the led doesn't activate.

When charging the led is working.

Thx for the build
[X Style (Pure) Android Development] carl.13:
I use kinscreen from play
[X Style (Pure) Android Development] moviefirst:
That is also a solution, but I know that this feature was also implemented in Lineageos as standard.

But thanks for your response in any case.

Edit: The feature is called 'handwave' an it is in the settings ambient display-proximity sensor-handwave pulse notifications on handwave.

I found it on my Xiaomi mi 8.
[X Style (Pure) Android Development] kb8no:
Build 7/14 with patch had Settings > Apps and notifications > Notifications > Battery light defaulted to Enabled. All notifications worked including the battery charging light. Changing it to disabled turned off all notifications including battery charging light.

This seemed non intuitive to me that disabling all notifications was buried under disable battery light.

In this 10/19 build this setting was defaulted to disabled so notifications including battery light did not work. This was a default change. I enabled the setting and battery charge light began working but not notifications light.

You might consider this a regression but controlling notifications should not be placed under battery charge light setting. If the place to control notifications could be found maybe this is how it is supposed to work.
[X Style (Pure) Android Development] kb8no:
After flashing 10/19 build with an apparent good dirty flash I am getting the type of hangs that we used to get. It is mostly noticeable in apps with long scrolls like Chrome, Tapatalk, and Gmail. It hangs and if you wait it gradually catches up or the UI will crash or you will get a cold reboot. These are the things that the 7/14 build with patch fixed. Anybody else have this problem? Dirty or clean flash make a difference?
[X Style (Pure) Android Development] AgathosAnthropos:
Sorry, I figured randomblame dropped it in. I'll verify its in and kick out another build soon. Should I revert device changes to ~7/14? Been working on building a 17.0 but it's slow going.
[X Style (Pure) Android Development] kb8no:
I am back on 7/14 with patch and it is good again. I thought you maybe worked off Randomblame regressions cuz that is how it was behaving. We first need to revert to a clean build of 7/14 with patch built in and post it for those new. BTY, backup of your new build failed for me.

In my opinion we/you need to fix the UI problems next. I use it as a DD but I can't recommend or share it to, for example, my wife. Then we have a serviceable 16. Random blame could have some pearls beside her regressions we shouldn't overlook. Your 16 is sooooo close! This is a great ROM.

Then push into 17.
[X Style (Pure) Android Development] moviefirst:
Los 17 ?