yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] Strephon Alkhalikoi:
I believe there are apps that can be used for screenshots. Whether they will work given the current state of the ROM I don't know. As to the camera, no camera app functions. In the past on other devices I was able to download a camera app that included its own binaries and that app would function. The problem with the camera here runs deeper than app level, and that solution does not work. If you need a camera, this is not the ROM for you.
[X Style (Pure) Android Development] kerdiaz:
I'm sorry for the offtopic but beside nuclear rom there's another working functional ROM for this phone?
[X Style (Pure) Android Development] Strephon Alkhalikoi:
Nothing running Android 9, as this is the only Android 9 ROM this device has. You'll have to use an older ROM. But before you do, get your volume buttons fixed.
[X Style (Pure) Android Development] randomblame:
[MENTION=5820564]kerdiaz[/MENTION] Built in camera can record video from front and back cameras and capture images using panorama mode

Snapchat can be used to capture images

Screenshots also work for capturing images in a camera app with full frame preview
[X Style (Pure) Android Development] randomblame:
Ok I thought we were talking about the dual SIM card variant issue. My style also has the cosmetic issue of not displaying baseband in the bootloader screen it seems to not effect anything. My pure properly displays it though and both are on the same modem flashed with the same procedure. Its weird
[X Style (Pure) Android Development] stevejohnson42:
Some of these may be dated - but ; see these links to threads

https://tinyurl.com/y5m4r6o9

https://tinyurl.com/y57hqxga

These are all Nougat ROMs ; read the OPs carefully - intent here is to steer you to ROMs that work once you taken / installed the stock Nougat ROM.

I have used NucleaROM and Hashbang's unofficial (?) LOS and could recommend both as solid daily drivers

Clark does not have the size of developer community that other devices have - but there are very excellent people still looking at it. From what I understand ( and do not claim to be an authority ) - the biggest challenge since Oreo has been getting the camera to work.

Good choices are there for you to try -- for the most part ( and I say this from standpoint -- I have not checked lately ) the ROMs have been developed to a solid stage , but developers have moved on to other devices. My recollection is that Hashbang has been applying security updates to the LOS ROM

Continued applause for the developers who have done and continue to work on this device.
[X Style (Pure) Android Development] zahidm:
Creating Device trees and blobs from Scratch, once it will be done i will share with you, really i just see that official trees are from Nougat in LOS 15.1 and 16.0 Repository, vendor trees are good enough, it will take one week at least after office time to set up all device trees and some changes in Kernel too... Because there are not so many Devs worked on PIE and OREO trees
[X Style (Pure) Android Development] randomblame:
My source is linked in the op and should require only minor changes to use to build for whatever Android 9 flavor you're after
[X Style (Pure) Android Development] Strephon Alkhalikoi:
[MENTION=1776875]randomblame[/MENTION]: I don't think you meant to quote me again. ;)

Just to add, upthread I confused the person you were talking to with the person I was talking to, and ended up making a mess. Sorry 'bout that.
[X Style (Pure) Android Development] randomblame:
Oops fixed it
[X Style (Pure) Android Development] Henry Hilliard:
Ok glad I haven't encountered a weird pure thing. Thanks, I'll try it out and let you know how it goes.

Thanks for the help
[X Style (Pure) Android Development] Quigongentoo:
How goes the battle with the camera? I haven't seen anything for a bit and I'm curious.
[X Style (Pure) Android Development] randomblame:
just installed a shiny new 1tb crucial ssd and I'm syncing lineageos onto it. Did something stupid and bought a new notebook tonight too 6 core i7 should get the job done
[X Style (Pure) Android Development] zahidm:
Better use a cloud service, the fastest way to compile a ROM.

Sync source 10min

Compile ROM 30-45 minutes Max
[X Style (Pure) Android Development] randomblame:
Not even slightly my style
[X Style (Pure) Android Development] Henry Hilliard:
So I worked up the nerve and flashed it. Baseband still says [not found] in bootloader but all connectivity works great. Definitely smoothest running rom I've used so far. Excellent work. I think literally the only thing keeping it from being perfect is image capture capability.

---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------

lol
[X Style (Pure) Android Development] PythonNut:
Okay I really hoped I could solve this on my own, but I can't figure it out.

I have an XT 1575. I've been using this ROM for a while now, but since I started I've been experiencing a weird issue: after booting, the OS seems to get suck. Wi-Fi and cellular don't work, apps that are supposed to start at boot do not, and I can't power off or reboot. After a nondeterministic, but usually short period of time the screen will go black and the system will do something that looks like a soft reboot. After this, everything may start working fine or it might repeat this cycle more times. Eventually the loop will break although it can sometimes take hours. Wiping data did not help. This was on the 2.0149 modem. I was mostly fine with this arrangement since I don't reboot often.

The new build requiring the newer modem came out so I flashed the modem (in the recommended manner, flashing it twice). The ROM now flashed fine, saying the modem is 2.0185. However, the problem from before was still present, except cellular never works, even after Wi-Fi starts working. Wiping data doesn't help here either. I noticed at this point that the bootloader also shows baseband as "not found" although I don't know if that is new or not.

Any ideas or details I'm leaving out?
[X Style (Pure) Android Development] Strephon Alkhalikoi:
Nope. I've encountered this as well on a completely clean install. Unfortunately, a logcat doesn't appear to reveal much. I however should try again.

The baseband reporting itself as "not found" is a different issue unrelated to the system reboots.
[X Style (Pure) Android Development] PythonNut:
To be clear, the main issue is cellular not working at all. I'm fine with the reboots—I can just wait them out. But not having any mobile data more difficult to ignore.
[X Style (Pure) Android Development] Strephon Alkhalikoi:
Ironically, I booted the phone tonight and didn't have a single force close before being able to use it. A difference between you and I is that my cellular did work before and after fixing the "not found" complaint in the bootloader. That's how I know the "not found" problem isn't related to the force closes in the ROM.

In your position, I would start from scratch and install the full Android 7 ROM again, but spend some time "hammering" the modem into the device, i.e. flash the modem some five or six times in a row. It should fix the "not found" complaint and may resolve your cellular issues as well.
[X Style (Pure) Android Development] Jfirst:
I've had the exact same symptoms with magisk if I put Magisk into core only mode those problems go away from me
[X Style (Pure) Android Development] xabr3:
Any updates on the camera issue? :)
[X Style (Pure) Android Development] kadopt:
[MENTION=6906944]PythonNut[/MENTION] [MENTION=2807229]Strephon Alkhalikoi[/MENTION] [MENTION=7437322]Jfirst[/MENTION]

I wipe dalvik/art cache on every reboot and always starts fine (no system hanging or lack of comms), takes a little longer to boot because of the necessary cache rebuild.
[X Style (Pure) Android Development] Strephon Alkhalikoi:
I just wait patiently and it eventually gets there.
[X Style (Pure) Android Development] randomblame:
Sorry been busy I'll try to make some time want to experiment more with the camera wrapper
[X Style (Pure) Android Development] PythonNut:
Thanks a lot! That fixed both of those issues. I'm surprised that just flashing the modem was insufficient, but I guess I don't have good understanding of what's going on.

Also my apologies for cluttering this thread with something that ended up being completely unrelated to this ROM.
[X Style (Pure) Android Development] randomblame:
Shiny new notebook is sitting on my desk getting set up for Android builds

Running into trouble with Ubuntu 19.4 and it's included version of ncurses
[X Style (Pure) Android Development] R77:
I have a problem with magisk it boots up fine when I don't flash it. I have no problems with the ROM but when I flash Magisk Version v18.1 it flashes successfully but when I reboot it just stays in the Android logo it turns off reboots and does the same it never leaves the Android logo. I even installed the Magisk Manager Version v7.1.1 and flashed Magisk in twrp but it still does the same. Is there a solution for this?
[X Style (Pure) Android Development] Strephon Alkhalikoi:
Not a ROM issue. Magisk 18.1 worked perfectly on my device here, and I had no issues with updating to Magisk 19. Ask your question in the Magisk forum, and provide logs.
[X Style (Pure) Android Development] xabr3:
That's awesome. :)
[X Style (Pure) Android Development] randomblame:
Pretty confident that I can get camera working. I think I've got nfc sorted out on pie need to fix Bluetooth next to quiet the logs and see straight then I'll figure out what's up with wifi, moving stuff to /system/vendor as demanded by the goddess trebble and likely missed a path somewhere but the logs are noisy atm
[X Style (Pure) Android Development] xabr3:
Awesome. Keep up the good work. Will make a donation soon.
[X Style (Pure) Android Development] moviefirst:
Great work!?
[X Style (Pure) Android Development] randomblame:
Gonna have to try a build of 15.1 with this camera fix the blob/bionic incompatibility is fixed
[X Style (Pure) Android Development] frank0312:
The camera was the only problem in the previous build of Android Oreo 8.1 for moto xt1572.

Do you have a fully functional build of Android Oreo with working camera?
[X Style (Pure) Android Development] swieder711:
Im encouraged by your progress.

Maybe I can put off my upgrade to a pixel 3 xl until some of the critical problems are fixed (memory mgmt, speaker rattle, screen burn).

Keep up the great work.
[X Style (Pure) Android Development] kadopt:
not really just the camera...

NFC does not work, the file system is kinda dodgy (sometimes some files would appear as empty to some aplications after being made by other app, reboot fixes the issue), realtime audio from the headphone jack can become choppy depending on cpu usage, audio from the speakers is dodgy if the audio is kinda silent or the volume is too low, if you use a very bright wallpaper the shade from the notification pulldown is full back instead of semi transparent.

Not remembering anything else right now... still using the latest 15.1 from hashbang.
[X Style (Pure) Android Development] randomblame:
Thanks for the list, nfc is partially working in my latest pie builds the hardware detects the other device vibrates and the stack crashes though at the moment I think that is due to the broken Bluetooth. I have a new build of 15.1 to test after work
[X Style (Pure) Android Development] :
I'm going to be retiring my Moto X Pure (xt1575) toward the end of the month. Its in great condition. It was updated to Nougat baseband and is currently running AEX rom. If youre in the US and if it would fit your needs, I'll donate it to you at that time.
[X Style (Pure) Android Development] big_marcolino:
Hello [MENTION=1776875]randomblame[/MENTION]

I have a doubt. Is the priority to solve 15.1 problems or to launch 16.0?

Thanks for the great work
[X Style (Pure) Android Development] kadopt:
I think the idea is to have a good base in 15.1 (bug fixing, etc) then go to 16.x.
[X Style (Pure) Android Development] randomblame:
My priority is to have fun playing with this thing to be honest. The problems with 15.1 and 16.0 are not exclusive what benefits one will benefit the other this is the same code base with a few extra issues in pie. I started with what was most interesting to me ? as time permits I will try to fix everything I can

I have some more changes in mind for the camera wrapper pretty sure I know the root cause of the broken rear sensor

Edit added some waits in wrapper didn't help, moving to a newer version of the msm camera kernel driver didn't do the trick, eeprom of the sensor isn't being read by the kernel camera driver not sure why this is happening now or if this functional has always been broken
[X Style (Pure) Android Development] randomblame:
WiFi is up on pie - sent from my pure running android 9
[X Style (Pure) Android Development] joheli:
Would It be possible top gerade a downloadable/flashable Rom at thus point? If WiFi ist up, It sounds somewhat usable.

So exited for a piece of pie...
[X Style (Pure) Android Development] randomblame:
Sure I'll put together a Trainwreck edition, its compatible with nougat firmware only at this point
[X Style (Pure) Android Development] joheli:
I'm currently on LOS 15.1 but I'll see If I can get It up
[X Style (Pure) Android Development] randomblame:
bluetooth fixed
[X Style (Pure) Android Development] randomblame:
Link to trainwreck edition added to OP please note the items that do not work listed above the download link.

Will bootloop if on marshmallow firmware, also it will sometimes bootloop just for fun because of a race condition in init with broken ril
[X Style (Pure) Android Development] xabr3:
Really nice! Hope u get ril, nfc, camera, gps and compass fixed. :) Keep up the good work.
[X Style (Pure) Android Development] R77:
Can you share on how flashed successfully so I can try it?
[X Style (Pure) Android Development] Strephon Alkhalikoi:
In TWRP I flashed (in order) the ROM, GApps, and then Magisk. Cleaned up caches in TWRP and rebooted.
[X Style (Pure) Android Development] R77:
It was opengapps that you flashed and Magisk 18.1?
[X Style (Pure) Android Development] randomblame:
Let me know if this new build has any issues haven't had a chance to test much my battery crapped out on me
[X Style (Pure) Android Development] Strephon Alkhalikoi:
Yep. In fact, I just installed today's update, followed by the GApps package and Magisk 19, without issue.

I have more to try out, but the system force closes I was having are apparently resolved.
[X Style (Pure) Android Development] hasekev99:
It works for me, thanks ...
[X Style (Pure) Android Development] kb8no:
I have been using a clean flash wiping everything except SD card from previous experience. Are you suggesting that dirty flash is now working fine?
[X Style (Pure) Android Development] hasekev99:
I flashed dirty and it works ...
[X Style (Pure) Android Development] Strephon Alkhalikoi:
As a force of habit, I always wiped system and the caches before flashing a new version of the ROM. I never wiped data, unless it was to try and resolve an issue such as the baseband version not displaying in the bootloader. But, just to make one thing clear, you have not been clean flashing the ROM. A clean flash requires wiping data as well as everything else.
[X Style (Pure) Android Development] hasekev99:
Hello, have a question. Had my phone fully charged last Sunday. After that I turned off the phone. Now a week later I wanted to turn the phone back on, but the battery was empty. Is this a known mistake? In advance best thanks
[X Style (Pure) Android Development] kb8no:
No. I have been clean flashing and wiping data because very early I found it necessary. You now confirmed my suspicion that I can now dirty flash and not wipe data. TY. When she finally enables SELinux I hope we can still dirty flash that build too.

---------- Post added at 12:08 PM ---------- Previous post was at 11:55 AM ----------

I have noticed this as well. I cannot remember anyone posting about it. This phone is prone to surprise battery failure but what happens is that the battery dies prematurely when it is on with say 20 to 40% battery left. I had that problem on this phone and one other phone and replacing the battery fixed the problem. It takes some days to go dead so in daily use I have not had a problem.
[X Style (Pure) Android Development] hasekev99:
But what should I do now, the battery is still firmly installed
[X Style (Pure) Android Development] kb8no:
If you use it daily and have no problem then just charge it if you leave it off > 1 week and do nothing else. That is what I am doing. If you have other battery problems as I described, get a new one from eBay for $10 and install it. You have to take the phone apart, I just googled it and followed the many tutorials. I have done lots of repairs on this phone and it is easy now but daunting the first time.
[X Style (Pure) Android Development] R77:
What TWRP version do you have?
[X Style (Pure) Android Development] Strephon Alkhalikoi:
3.2.3-1.

---------- Post added at 10:51 PM ---------- Previous post was at 10:46 PM ----------

I misunderstood your post slightly. Glad I could help resolve that concern. As to SELinux, I honestly don't expect to see an enforcing kernel. Other devices I have running Android 9 custom ROMs all have permissive kernels and have had significant issues when the kernel is set to enforcing.
[X Style (Pure) Android Development] R77:
Managed to get to work with TWRP 3.2.3-1 the problem now is that my SD card is not recognized. It shows as disk the contents are there not as folders but as some type of files with a question mark in the middle when I click it it shows open as menu Text, Audio, Video, Image, other. Any help?
[X Style (Pure) Android Development] Strephon Alkhalikoi:
Sounds as if your MicroSD is corrupt. Pull off whatever you can and format it.
[X Style (Pure) Android Development] randomblame:
It just hasn't been a priority yet but I have put some time into updating our sepolicy there's no reason it won't work
[X Style (Pure) Android Development] kadopt:
I got something like that when I upgraded from hashbang to randomblame builds, the SD card contents should be listed fine in twrp, copy everything from there to your pc and format it to vfat or exfat then restore the files.
[X Style (Pure) Android Development] R77:
Well right now I have AEX 7.1.2 ROM by obsolete and able to see contents in SD card. If I format it will I be able to use the SD card for AEX if I decide to revert back?
[X Style (Pure) Android Development] randomblame:
public service announcement - tomorrow is april 1st. If anything unusual happens on your device this week I am sorry
[X Style (Pure) Android Development] kb8no:
Oh! No! I haven't yet recovered from the bad episode a few years ago.
[X Style (Pure) Android Development] randomblame:
Well they promised to do better this year so here's hoping it's chill lol I've been keeping an eye out for suspicious commits and haven't seen anything yet
[X Style (Pure) Android Development] kadopt:
It's not like your data is corrupted, so you may have to copy everything again. Can't really confirm that.
[X Style (Pure) Android Development] kb8no:
"Process system isn't responding" error still occurring as before when when the clock widget won't start.
[X Style (Pure) Android Development] kadopt:
Reboot, wipe dalvik/art cache and see if it fixes your issue for that session.
[X Style (Pure) Android Development] Quigongentoo:
Just a quick item of note. I did a full wipe. Every thing went well until network setup. Since I recently hid my wireless ap names I had to try to add a network to connect to. It let me put the info in but then when I was done it wouldn't connect. Tried several times with no luck. Double checked everything so I know the names and passwords were right. Has anyone else ran into this?
[X Style (Pure) Android Development] Strephon Alkhalikoi:
Check your bootloader. I bet your baseband isn't properly installed, which you'll see if "not found" or a baseband version older than 09.R is reported in the bootloader.
[X Style (Pure) Android Development] Xp4:
Xt1572 RETEU Bug Report

Hello [MENTION=1776875]randomblame[/MENTION]

In XT1752 RETEU Dual SIM the bug report is the following:

1. Sims are not read

2. Dual SIM/ Mob Network Menu doesn't work (APN in settings etc, it closes very fastly).

3. RIL doesn't work.

4. Data doesn't work.

5. Not any SIM icon is displayed in status bar.

6. Phone number isn't listed in about device

Even though i'm supposed to be a comp engineer idk how a total LineageOS dev process work, so i would propose you, if you consider, that i can send you my device, for testing purposes, to you to see what's really happening with DUAL SIM variants.

Otherwise you could direct message to me to see if anything i can do can workout for you (logcats, etc).

Regards to all XDA community, and thanks for your effort, time and excellent work.
[X Style (Pure) Android Development] ACardAttack:
It's been a long time, nearly a year since I've messed with my old X Pure, I want to use it for playing emulators and would like to update to the rom for ideally better battery life (and not installing and google services to help with that)

I have the Marshmallow modem, I assume I still need to relock bootloader, upgrade modem officially and then unlock bootloader and reflash twrp? Or is there a way I can flash the modem in twrp?

Thanks
[X Style (Pure) Android Development] Strephon Alkhalikoi:
No flashing the modem in TWRP. Flash the entire stock ROM and repeat the install of the modem half a dozen times to ensure it doesn't silently fail.
[X Style (Pure) Android Development] kadopt:
[MENTION=5387970]ACardAttack[/MENTION]

No need to lock the device, just flash the entire stock rom with fastboot then reflash just the modem a few times because the modem for some reason may not stick.
[X Style (Pure) Android Development] Kenaz Rune:
Issues I am having with this build

Thanks for building this ROM for this phone. When I saw it, I decided it was worth replacing the USB port and battery to bring it back to life and am loving it as a backup phone.

I am experiencing an issue with the 3/30 build. I have some add-ons that might be causing it. Basically, after I installed the ROM (with a dalvik/cache wipe), the screen blanks out every few moments, and I have to press the power button to bring up the lock screen, type in my code and continue.

I am using EdXposed and had a beta of GravityBox for Pie running (worked fine on 3/3 release). I reverted the first time I tried it as removing that app and the OmniSwitch APK didn't end the problem. For the moment, on my second try, it appears turning off GravityBox is sufficient to solve the problem. I'll keep an eye on it.
[X Style (Pure) Android Development] Strephon Alkhalikoi:
Is there an echo? I thought I said that. ;)
[X Style (Pure) Android Development] aybarrap1:
I think the main part being covered is that there is no need to relock the bootloader which you did not specifically mention.
[X Style (Pure) Android Development] Strephon Alkhalikoi:
Yep, I missed him asking about locking the bootloader.
[X Style (Pure) Android Development] Kenaz Rune:
It looks like the problem was in fact GravityBox. I guess something changed in the ROM that wasn't compatible with that beta.
[X Style (Pure) Android Development] Hybrid Theory:
Is it possible to change the Selinux to enforcing? This mechanism prevents escalation attacks and it keeps apps from accessing data for other apps like bank apps. I checked getenforce in the terminal it says enforcing but trust keeps saying Selinux isn't enforcing so I'm a little confused.
[X Style (Pure) Android Development] Strephon Alkhalikoi:
Searching back about a page would have given you an answer straight from the developer. In short, it's possible but won't likely happen until the kinks, namely the camera, are worked out.
[X Style (Pure) Android Development] randomblame:
new build up
[X Style (Pure) Android Development] Hybrid Theory:
You are right if it's on enforcing camera stops working but it works on permissive.
[X Style (Pure) Android Development] Kenaz Rune:
Downloading now. Is there a brief description of changes somewhere?