yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] positron103:
This is my report about this Rom. I have used it as a daily driver for 1 week.

And Google Assistant works! I just have to set it to the assist app.

System Stability: Its about 75% stable. It has some minor bugs and some major bugs. It has smooth animation. Sometimes it lags and on every boot it shows you a box telling you that system process isn't responding. Closing it or waiting will reboot the phone in a weird way which your screen will turn black for about 1-2 seconds and shows for you the lock screen. Powering Off the phone will take about 1 minute to power off the device and after using it to 2-3 days it will power off normally. Lineage OS Trust tells you at every boot that SElinux isn't enabled and this build was signed by public keys at every reboot.

SIM card and Hotspot: SIM card works and hotspot is also working but, when turn it off or sometimes on the device will reboot.

Camera: Use Snapchat.

Performance: Excellent! Amazing! Wonderful!

Battery Life: Idk about it but, I think it's better.

Everything else: Works fine!

Keep going! :good:
[X Style (Pure) Android Development] collinschen02:
I have a 1570, I use latest twrp to clean flash the 0219 build but get error 7. Before clean flash I was running RR 7.1 from. I very much want to try this pie, do I need to flash lineage 14.1 and clean flash it ?
[X Style (Pure) Android Development] moviefirst:
You have tot flash stock firmware 7.0 nougat first.

See the first page what randomblame described.

This is unofficial lineageos 16 for Motorola Clark. It is only compatible with nougat firmware - you must have the nougat bootloader and modem flashed on your device
[X Style (Pure) Android Development] collinschen02:
Thank you for your guidance,Do you mean this link ? Moto X Style XT1572 CLARK_RETLA_DS_7.0_NPHS25.200-15-8_cid12_subsidy-DEFAULT_CFC.xml.zip
[X Style (Pure) Android Development] moviefirst:
If you had stock 6.0 marshmallow before and never bin on nougat 7.0, I suggest you flash that same stock marshmallow firmware first. And then take the ota update to nougat and then flash the 9.0 pie ROM. That's how I did it. Be aware you have to have the same stock firmware as what you had before you flashed RRemix. Maybe randomblame knows a different way to flash it. Good luck!
[X Style (Pure) Android Development] collinschen02:
Thank you for your kind reply, my phone comes with 5.0, saddly in my country updates for Clark has been terminated for years still remain 5.0, I guess I will have to fastboot the 7.0 firmware and try your pie.
[X Style (Pure) Android Development] randomblame:
There are instructions for flashing nougat firmware via fastboot they pop up in there every few pages it seems
[X Style (Pure) Android Development] randomblame:
The crashing and instability sounds to me like you haven't wiped data between builds I always do and have never seen behavior like that. Paths change firmware and blobs move and until development settles down wiping properly between builds is important
[X Style (Pure) Android Development] kb8no:
Thanks for the explanation why dirty flash does not work. Dirty flash means wipe Dalvik and cache and then flash. Clean flash means wipe Dalvik, cache, system, data, internal storage and then flash. So when you flash a ROM it writes system new so that is like wiping system. So you ask for Dalvik, cache, and data, then system gets flashed over the old system, and the only difference between your suggestion and a clean flash is wiping internal storage. I have been doing clean flashes cuz when I tried just Dalvik, cache, and data it didn't work once for me and there's really nothing on internal storage anyway when you are flashing these every few days. So, why not just do a clean flash?

Comments on 2/19 build. "Process system isn't responding" comes up intermittently after a reboot but always several times after flashing. Seems scary and annoying but doesn't seem to hurt anything and settles down. This is unchanged on 2/19. I am using panorama for photos and it saves a credible photo when you hit the button twice. Snap chat turns me off when it wants my birthday to register, they don't need my birthday. WiFi tether can be configured now but still crashing when you shut it off after using it for tether as before. All the Google stuff seems to be working including OK Google, Google Assistant, and speech to text. MS Outlook connects to my work email just fine. 2/19 really seems smooth. Not getting much in the way of random crashes so far after the first few hours.
[X Style (Pure) Android Development] gs554424:
老哥，国行1570我尝试了刷基带刷备份各种尝试，都是无服务呀。

你弄好没：（
[X Style (Pure) Android Development] BIGWORM:
Just a reminder, though this is an international forum, let's keep the posts to English. There are multiple tools available for language translation, including Google Translate. Thank you. =)
[X Style (Pure) Android Development] randomblame:
Some have reported issues with asian variants if anyone wants to get me more info I might be able to look into it
[X Style (Pure) Android Development] Fabiett83:
XT1572 single SIM reteu.

I can confirm the system crash and the return to lock screen, clean flashing, at least in the 11 13 and 19 versions, I don't remember it before but I always return to hashbang 14.1 after some hours and may have missed those before.

I too don't want to register in snapchat only to make some test photo, maybe I will try again the panorama trick, the last time the result was all blurred.

Still, thank you [MENTION=1776875]randomblame[/MENTION] for your work
[X Style (Pure) Android Development] kb8no:
I posted a photo using panorama in the wrong forum. Panorama is usable. https://xdaforums.com/member.php?u=4465682
[X Style (Pure) Android Development] Fabiett83:
I must admit that the fast double tap method gives good photos, I was waiting too long for the second tap.

But still gives 952x720 photos, not exactly 21mp..

Today i will get logcat from the system force close and try some more camera software.
[X Style (Pure) Android Development] collinschen02:
I couldn't. As the developer said I need to have stock 7.0 first to try 9.0.
[X Style (Pure) Android Development] Fabiett83:
XT1572 reteu, lineage-16.0-20190219-UNOFFICIAL-clark.zip, open_gapps-arm64-9.0-stock-20190221.zip, Magisk-v18.1.zip, clean flashed tonight

this is what happens every reboot, with screenshot of every step:

-after boot, the PIN request and the lock screen has a this tinted background and the wifi is not working

-after unlocking the launcher has a black background, no widgets and no wifi

-i noticed that even the SD in not working

-the system is not responding screen appears

-if i tap close the phone goes to a 5 sec black screen and returns to lock screen with the right background and the wifi connects

-the launcher now has the correct background and widgets

-the SD works

attached logcat.txt in zip

I noticed that leaving the phone at the pin screen for 2/3 minutes it does the "software reboot" and everything becomes normal (background, wifi, SD, no system force close)

attached logcat_waiting.txt in zip with this case
[X Style (Pure) Android Development] moviefirst:
Try flash gapps nano without magisk and look what happens. That's what I'm using.
[X Style (Pure) Android Development] Fabiett83:
removed magisk but nothing changed

formatted system and installed only lineage-16.0-20190219-UNOFFICIAL-clark and open_gapps-arm64-9.0-nano-20190221

the first boot did exactly the same as before, i had to reset the default dialer, rebooted and now the problem disappeared

seems that the problem is in the stock opengapps, i will try the intermediate packages to find the cause.
[X Style (Pure) Android Development] positron103:
I've done a clean wipe. But Sorry for this next silly question. Do a I need to clear internal storage? And I've never done a dirty wipe before. How can I do a dirty wipe? And Can I do a dirty wipe on this Rom?
[X Style (Pure) Android Development] moviefirst:
I didn't wipe internal storage. Dirty wipe , boot into twrp, select wipe then advance wipe, select Dalvik/Art Cache, system, data, cache then swipe to wipe then reboot system. That's my way! On this ROM.
[X Style (Pure) Android Development] kb8no:
I always use gapps pico by habit since back in the day of not enough memory to flash anything more. It is the smallest amount of gapps and you basically get only play store and has the least variables.

With this ROM I always clean flash. Wipe everything except the SD card. Again, the least variables. When development moves from course tuning to fine tuning the OP herself said we can move to dirty flashing.

Try it.
[X Style (Pure) Android Development] randomblame:
Those who are having crashy launchers are you using googles launcher or are you using trebuchet? I think this is an issue with the Google app
[X Style (Pure) Android Development] moviefirst:
I'm using trebuchet without crashes.
[X Style (Pure) Android Development] randomblame:
Does anyone know if this thing has serial debug output of any sort? Trying to get early kernel logs in a situation where ramoops is broken. Serial output would be much better than feeling around in the dark though I noticed Motorola made some changes to ramoops in kernel

I think tonight I'm going to make a new branch of the 3.10 kernel and consolidate all these dts files into one super basic setup and see what I need to do a minimal boot without panic cutting out basically everything. Then I'll transplant the new clock drivers and the new pinctrl driver and basically see if it breaks and where it breaks and transplant the result to 3.18 I know I can get this working I'm just fighting too many things at once

Found this commit with really good documentation on pinctrl here saving it for reference

https://patchwork.kernel.org/patch/10339127/
[X Style (Pure) Android Development] gildenilson:
Do you have any mirror link? Android file host isnt working right now!
[X Style (Pure) Android Development] mostafasalimi:
The SIM card will not be identified. I have xt1572 region asia dual sim...pleas help.
[X Style (Pure) Android Development] randomblame:
I'm afraid that variant is untested so far people have been reporting the same problem. Are you on the nougat modem? I don't have that device so I'm unable to do much. Get me a bug report and I can look at it
[X Style (Pure) Android Development] randomblame:
Pulled down pure caf 3.10 made new plain device tree compiled booted and no ramoops. So I pulled the working version of ramoops from our kernel and modified the board files to specify exact memory addresses as ours do for ram oops and compiled and booted and no damn ramoops sooooooo I am moving to mainline v5.0rc7 and trying again with my changes to ramoops and board files and then I'm gonna sleep. Wtf has Motorola done that only their 3.10 and 3.18 kernels allow ramoops to work it's like the memory map is all wrong? Why do they have to PATCH pstore to accept SPECIFIC memory addresses rather than use the start address and a max size like everyone else. Even on their latest 4.9 kernel they get tricksy with pstore.
[X Style (Pure) Android Development] positron103:
Can custom kernels used in this Rom? I heard that franco kernel is the best for performance.
[X Style (Pure) Android Development] randomblame:
I'm just trying to solve the mystery of why only Moto kernels spit out debugging info to ramoops right now. Only 3.10 and 3.18 Moto kernels seem to give me anything though a 4.4 Moto kernel I messed with a little while ago was also outputting to pstore but it was compressed. If I can solve the mystery it opens the door to a 3.18-4.x caf kernel which would be easier to work with than a Motorola kernel because there is less out of tree code. I have very little hope of a fully functional kernel upgrade for this thing right now this SOC was a failure for qcom and they ditched it quickly in their codebase snapdragon 808 and 810 (based on the same die) we're the only qcom chips to ship with an a57 cluster and the 64bit/32bit big.little mismatch was a hopelessly stupid idea from the start. Basically they shipped it and then erased it from their codebase never to support it again unlike most of their chips so all we have is their old code which is very sketchy and incompatible with new kernels and we have a very incomplete attempt at mainline support some kind people worked on that consists of a new version of the clock drivers and pinctrl drivers. I've gotten the new clock drivers working in 3.18 bit it does not include support for bringing up the gpu and the new pinctrl is borked too so I've tried to adapt the old code and incorporate it but it's a hell of a lot of work for a tiny jump to a 3.18 base. If I could get a newer less messy kernel debugable it would be better incentive to work on it but alas something screwy is going on.
[X Style (Pure) Android Development] randomblame:
Spent the evening trying to move cameraservice to hwbinder, pulled caf oss hal and started reapplying changes to it cleanly and messed around with TWRP which I'm still having issues building with lineage16

Also something to note in Android 10/Q camera hal1 will be deprecated - this sucks for Clark because we use it. Hal3 works-ish but it's slow and buggy so it will need love. Oh well what is a new version of Android if not an opportunity for Google to break the camera in new and exciting ways?
[X Style (Pure) Android Development] kb8no:
Please teach... In generalities, what is it that wants a new twrp?
[X Style (Pure) Android Development] randomblame:
Me. ? It isn't necessary I can always pull Oreo source and compile it in there

Anyways If I can coax camera to work with hwbinder the last service using the passthrough transport is sensors and then it's all migrated which is good because who knows when that will be deprecated. If I can get camera working better I'll start cleaning up my commits and submit them to Gerrit I suppose since hash is busy
[X Style (Pure) Android Development] randomblame:
https://review.lineageos.org/c/LineageOS/android_device_yu_lettuce/+/242355

This is an interesting idea
[X Style (Pure) Android Development] Hashbang173:
Yeah pretty busy right now. LineageOS would require camera to be fully functional: https://github.com/LineageOS/charter/blob/master/device-support-requirements.md#camera

If you get a clean tree I can push it directly to the LineageOS GitHub repo bypassing code review since there are so many commits.

OSS sensors working OK?
[X Style (Pure) Android Development] randomblame:
That sounds like a much easier plan I'll start work cleaning up after myself. Yes oss sensors is working well but for whatever reason only through the passthrough transport and not hwbinder. running it through binder results in no boot. This was probably the same behavior with the blobs. Working on camera more tonight still need to fix sepolicy too for official builds
[X Style (Pure) Android Development] Itz_GoodPlayer:
Nice! There are some bug that are too minute, but anyway i report them:

Major:

- When using Trusted Face from Smart Lock, sometimes in lockscreen, system crashes and reboots.

- GPU is not working fine. In some animations and Ej, Instagram Stories, FPS drops a lot.

Not very important:

- LiveDisplay not working. Also no Night Light.
[X Style (Pure) Android Development] positron103:
A flashable zip file if someone wants to change his font without root access. Fully works and boots without issue.

How to flash it:

1- Download the font that you want in the link below.

2- Make sure that your phone is at least 60% charged.

3- Make sure that you're on the latest build for this ROM.

4- Take a Backup (optional)

5- Wipe Dalvic Cache and Cache (optional)

6- Flash the zip file.

7- Enjoy!

Link: https://xdaforums.com/android/themes/fonts-flashable-zips-t3219827

Tested On: X1575

Note: I have only tried the Google Sans Font and it works without any problem. I don't know about any other fonts.
[X Style (Pure) Android Development] mostafasalimi:
yes ,im used android nougat but not detection sim...my phone model 1572 region asia dual sim
[X Style (Pure) Android Development] randomblame:
Let me get specific is the modem firmware on your device the version that shipped with official nougat from Motorola? I am not sure that your variant was officially updated and the modem firmware may be incompatible with the blobs in this rom.
[X Style (Pure) Android Development] randomblame:
Lol I just spent a couple hours sanitizing my commits and then I got to one where I started over - Why did I do this to myself
[X Style (Pure) Android Development] xecutionkrk:
So far camera not working for me. Good job top
[X Style (Pure) Android Development] randomblame:
December 16 I posted this before rear camera was working need to figure out why image capture was partially working then and bring it back

Actually looking at my commit history from then I have some ideas to test tonight starting with using generated kernel headers in the camera hal ?
[X Style (Pure) Android Development] mostafasalimi:
my phone detail rom.
[X Style (Pure) Android Development] randomblame:
Please get me a bug report from los16
[X Style (Pure) Android Development] randomblame:
Quick note pixel launcher does not work. Trebuchet is icky with gestures enabled. "Customized pixel launcher" in the play store is beautiful.
[X Style (Pure) Android Development] kachelspk:
I wanna build this ROM by myself. I tried:

1. clone device tree to device/motorola/clark.

2. run ./extract-files.sh, but some files were not found.

3. brunch clark. It failed because missing some files above. :(
​

Could you guide me how to build it?

Where I put kernel project?

Thanks you verify much.
[X Style (Pure) Android Development] randomblame:
This is the vendor stuff with the correct hexedited blobs

https://github.com/randomblame/proprietary_vendor_motorola_clark

Kernel goes in kernel/Motorola/msm8992 dir
[X Style (Pure) Android Development] randomblame:
New build in OP

Test wifi hotspot and let me know if that glitchyness is gone please

:svetius:
[X Style (Pure) Android Development] daurwid:
I am unable to change the security lock screen method to PIN or Pattern. I'm assuming it has to do something with Smart Lock not working properly.
[X Style (Pure) Android Development] randomblame:
Works for me
[X Style (Pure) Android Development] kb8no:
No change. :( Tether works. Able to change PW and SSID and that works. However, as soon as you attempt to turn WiFi tether off either from settings or notification drawer it immediately does a hard reboot after ~ 10 second freeze. This is just as on 3/19 build.
[X Style (Pure) Android Development] Itz_GoodPlayer:
Same here. Hotspot work, but after turn off, system reboots.
[X Style (Pure) Android Development] moviefirst:
Same here. Reboots.
[X Style (Pure) Android Development] josuearisty:
It was happening to me in the build before this one too.

Enviado desde mi XT1575 mediante Tapatalk
[X Style (Pure) Android Development] randomblame:
That's really odd I spent a half hour trying to provoke it into crashing or bugging out and got nothing it just works for me
[X Style (Pure) Android Development] moviefirst:
randomblame, can you take a look at this?

The bootloader with software status modified is giving the issues, witch are screen lock, hotspot reboot. I have 2 moto x style. Maybe this is causing the problems.
[X Style (Pure) Android Development] Fabiett83:
The baseband on the white ends in 02R but in the black ends in 09R, maybe it's because of this?

Mine ends in 09R, I will try the new 0227 build tonight and see what happens
[X Style (Pure) Android Development] kb8no:
09R baseband is Nougat firmware / modem. 02R I am quite sure is Marshmallow firmware / modem and will not work with this ROM. That being correct, you need to flash Stock Nougat to get the 09R firmware. Then you can flash this software. See the OP.
[X Style (Pure) Android Development] moviefirst:
I'm using the 02R as my daily driver for about 2 months now. With randomblames builds. The only issues are the screen lock patterns and the hotspot, and it was official on stock 7.0 nougat before I flashed 9.0 pie.
[X Style (Pure) Android Development] kb8no:
well, I can't explain everything. 02R is an old baseband. I am sure that 09R is what it is supposed to be. For all the work you are putting into this, I would reflash stock Nougat and see what baseband you get? Your white phone doesn't like something. If you get 09R then do a complete clean flash including data internal SD and use pico GApps after flashing stock again. Can't hurt.
[X Style (Pure) Android Development] daurwid:
Mine is a black version of the XT1575.

I used the XT1575_CLARK_RETUS_7.0_NPH25.200-22_cid9_subsidy-DEFAULT_CFC.xml.zip to load the system to stock because I needed the bootloader updated to A0.52.

This stock image shows a baseband of M8992_1255309.10.01.68R FSG-8994-01.94.11_SUPER_NA+VZW

Loading the latest Lineage-16.0 rom lineage-16.0-20190227-UNOFFICIAL-clark.2.zip the baseband does not update.

Still unable to set PIN or PASSWORD as a screen lock option. Each time I try to set them it resets back to SWIPE or NONE.

Am I using the correct stock rom? Which rom should I use to get the baseband ending in 09R or 02R? Is this even the issue?

edit: Also to add that I used no Opengapps in testing. I am able to set the PIN/PASSWORD when using the stock rom.
[X Style (Pure) Android Development] kb8no:
[MENTION=9539450]moviefirst[/MENTION] [MENTION=9767697]daurwid[/MENTION] This is the stock factory Nougat firmware that you must flash correctly. CLARK_RETUS_7.0_NPH25.200-22_cid9_subsidy-DEFAULT_CFC.xml

This is the modem that a correct flash of this firmware will produce. M8992_1255331.29.01.88.09R

68R is a Lollypop modem. 02R is a Marshmallow modem. You need the 09R Nougat modem. This is a Lineage 16 development forum for those who have Nougat firmware. Until you get a Nougat firmware on your phone you are on the wrong forum. You should be on a firmware forum that teaches you how to properly fastboot the firmware. This is the original forum that everybody refers to: https://xdaforums.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142 Go there and figure it out and don't come back until you get it right. I spent a lot of time there before I really understood it and it is complicated but fundamental. I expect you are flashing it wrong and when you get it right it will work. If you cycle back through this forum there is a link to another forum of someone who recapitulated the original forum and it might be helpful too. Good luck and hope to see you back soon!
[X Style (Pure) Android Development] randomblame:
You need this : hint the name of the repository is where it goes in your build directory for some reason lineageos took it out of the manifest so you have to stick it in manually

https://github.com/LineageOS/android_system_qcom?files=1
[X Style (Pure) Android Development] randomblame:
So is it confirmed that tethering is fine with the correct modem? I really need to start testing and deploy hashes modem assert prop
[X Style (Pure) Android Development] kb8no:
No. I have correct modem and it reboots when it is shut off as before.
[X Style (Pure) Android Development] randomblame:
Ok so it's just the screenlock stuff hmm, interesting that the ril was working at all. Now we know there is a version of the mm modem that fails like this. We are learning yay ? thanks [MENTION=9767697]daurwid[/MENTION] and [MENTION=9539450]moviefirst[/MENTION] for the helpful info those modem flashes tend to fail and fool us
[X Style (Pure) Android Development] daurwid:
I confirm as well that the hotspot will cause the phone to reboot upon hotspot being turned off.
[X Style (Pure) Android Development] moviefirst:
I flashed from 02R modem to 09R modem (firmware) and can confirm that my screen lock pattern is fully functional now.
[X Style (Pure) Android Development] randomblame:
https://github.com/MotorolaMobility...62bd547c/drivers/media/platform/msm/camera_v2

Kinzie got nougat and was getting updates after us I wonder if they have any useful stuff to pillage maybe some slightly newer blobs