yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] micahs:
So sorry to hear that.
[X Style (Pure) Android Development] dwa91:
What factory image are you using and is it compatible with your device (XT1572 vs XT1575)? Are you following the guide?

The instructions to the guide are the same for both versions of the phone, just be sure to download the correct factory image from the firmware center.
[X Style (Pure) Android Development] insomniac89:
Yeah, this is the same zip I used moving off of Randomblames Android Pie build in April

CLARK_RETUS_7.0_NPH25.200-22_cid9_subsidy-DEFAULT_CFC.xml.zip

Went ahead and skipped partition gpt.bin one, the rest loaded fine, however the phone boots to the dead android.
[X Style (Pure) Android Development] insomniac89:
Furthur, I was able to get on the deprecated 7.1.2 December 2018 of Lineage, I seem to have no problem getting on to custom, just not the stock one anymore.

Bootloader shows unlock status code 3

Fastboot shows as secure

Bootloader is A0.52 2017-06-09

Moto X Pure XT1575.

Fortunately have a trusty Nexus 5 as my DD until I can get this fixed, I fortunately need my cellphone's camera to consistently work for my job. But I'll keep trying.
[X Style (Pure) Android Development] dwa91:
That does sound odd. You are clearing everything before flashing stock right? It may be the image you have is corrupted. You might want to download a fresh copy and give it a go.
[X Style (Pure) Android Development] bsorli:
Sorry to hear and chin up, there is light at the end of the tunnel! Look forward to hearing bout your old and new smartphone (didn't you buy a new phone...) adventures.
[X Style (Pure) Android Development] kadopt:
Don't be greedy, ril is the must have of that list then gps/compass. :) I've been without camera and nfc since early february.
[X Style (Pure) Android Development] joheli:
Me too, but most of the time I carry a DSLR with me anyway and android Oreo ist Just a lot cooler ;)
[X Style (Pure) Android Development] joheli:
Yay.. up and running

Is it possible to turn on navigation gestures?
[X Style (Pure) Android Development] randomblame:
Yes in settings I'll set it as default in the future

Open up your phone's Settings.

Scroll down and tap on System.

Find Gestures and tap on it.

Tap on Swipe up on home button.

Toggle the switch to on — you'll notice the navigation buttons change immediately.
[X Style (Pure) Android Development] joheli:
That is were I looked for it too, but the option is not there...

I noticed the gesture-navigation popping up after reboot for a breef moment, however I can't turn them on :(
[X Style (Pure) Android Development] randomblame:
Weird it was working for me I'm at work at the moment or I'd test. Maybe it's system/advanced/gestures
[X Style (Pure) Android Development] joheli:
I have no GApps installed at all and I could get it to boot only twice, beacaus it gets stuck during boot animation very often, espessialy with GApps installed.

I am on bootloader A0.52 so the Nougat firmware should't be the problem.

Update: bootet now with GApps installed, still nothing under gestures-tab

Update: now it is working - sorry for bothering with that...
[X Style (Pure) Android Development] randomblame:
Next idea for camera sensor is to disable the need to read the sensors eeprom by the kernel driver or at least allow it to fail gracefully with the sensor initialized

Ril - I think just needs some changes in init now

Compass was working but I broke it by moving things around should be simple

GPS wrapper needs some attention its been -wnoerrored and cheatily fixed for a while and it needs brought up to snuff for clang
[X Style (Pure) Android Development] randomblame:
Ril is now working well enough to read my SIM card so that's something need to make sure I'm using the correct link and blobs for nougat modem
[X Style (Pure) Android Development] joheli:
I've been using the Rom since yesterday and for a "trainwreck-version" it works really well.

So great work [MENTION=1776875]randomblame[/MENTION]

However, I noticed some (probably known) bugs

-The phone gets really hot, no matter if I'm using it or not. I would guess that this is caused by a lot of cpu-activity through which the battery is drained pretty quickly

-The auto-rotate feature is not working (and yes I turned it on this time ;)

- strange bug which causes YouTube videos to load, and continue loading forever. When app is switched, the video starts playing for a moment (browser version works, however)

Greetings

Joheli
[X Style (Pure) Android Development] randomblame:
Yeah lots of wasted cpu cycles spent trying to turn on the broken nfc and radio and constantly logging. Next release will be better. I had the compass working for a minute last night before I broke it again treble is a nuisance
[X Style (Pure) Android Development] joheli:
That sounds like really fast progress, any idea what could cause the video bug? Because I am pretty sure it is not my internet connection
[X Style (Pure) Android Development] randomblame:
Yeah I have a fix for the video issue
[X Style (Pure) Android Development] randomblame:
Ril is now working perfectly tested calls and data ?
[X Style (Pure) Android Development] big_marcolino:
It looks like I'm going to start 2019 with LineageOS 16 stable on my phone (feeling optimistic)

Great work

When you will launch a new version?
[X Style (Pure) Android Development] mddunner:
I mean no offense to any other brilliant developers on here, but this is the quickest development progress I've seen in a while. Mad props.
[X Style (Pure) Android Development] randomblame:
Video playback fixed trying to get Bluetooth back then I'll disable broken nfc service and build a userdebug build for another release

GPS fixed too
[X Style (Pure) Android Development] xabr3:
Awesome work! :) any progress on the broken camera?
[X Style (Pure) Android Development] joheli:
Wow that's some really fast progress there. Are you doing that full-time?

Also iit would be great to have another trainwreck-build depending on how long it takes to get bluetooth working before or after it (so form now on in two hours, lol)

Great Work and props to randomblame

greetings, joheli
[X Style (Pure) Android Development] randomblame:
*New build available in op, with working ril, gps, video. bootloops are gone, nfc service disabled so battery should last longer and heat should be down. seems pretty stable. no bluetooth, camera, nfc, sensors intermittent

let me know how it works
[X Style (Pure) Android Development] insomniac89:
So it turns out the solution was to skip partition. Now rocking stock again for a bit for a vacation. If anyone runs into that issue, that may work for you, ymmv.
[X Style (Pure) Android Development] dwa91:
Huh...that is weird but not unheard of. I know there were a couple of different version of Nougat based on the carrier (for instance v23 for Verizon folks). Wondering if that is the root of the problem. Glad you are back up and running.
[X Style (Pure) Android Development] bsorli:
How did you skip the partition during installation?
[X Style (Pure) Android Development] kadopt:
New build by [MENTION=9796853]AgathosAnthropos[/MENTION]

Get it here (lineage-16.0-20190714-UNOFFICIAL-clark.zip, MD5: 10b34d8d14fd76f7da73a29a37ed6411)

Flashed it and booted fine.

I have no change log but android security patch is from July 5th, 2019.
[X Style (Pure) Android Development] AgathosAnthropos:
Ha, thanks for linking it. Just uploaded last niight and havent had a chance to post before you found it :). (I have a slow internet connection at home so it uploaded overnight)

Built from latest a couple days ago, no new updates on camera.

I'm working a 15.1 build too but have some issues with the build, I'll let everyone know when it's ready.

Sorry for the real world issues [MENTION=1776875]randomblame[/MENTION] hope everything ends up okay for you and yours
[X Style (Pure) Android Development] kb8no:
The talk before was after flashing stock Nougat, Verizon offered an OTA Nougat update. Nobody could figure out what if anything changed at the time and it had no advantage. Yes, v22 was stock and v23 was Verizon OTA. I decided to take the upgrade and was also able to see no difference but for one. It updated the bootloader version and since you cannot flash an older bootloader over a new one I was blocked and never able to flash stock Nougat again on that phone. "Preflash validation failed" was the error. This may likely be the same issue. I'd have to study history to get the details. I have 4 of these. Needless to say, I never took that Verizon Nougat upgrade again. I have never understood or unraveled how to downgrade the bootloader.

---------- Post added at 07:45 AM ---------- Previous post was at 07:39 AM ----------

Dirty flash?
[X Style (Pure) Android Development] AgathosAnthropos:
Yeah, should be able to.
[X Style (Pure) Android Development] kadopt:
Yes, from his previous build and that was dirty flashed from last randomblame's build.
[X Style (Pure) Android Development] kb8no:
[MENTION=9796853]AgathosAnthropos[/MENTION] 16.0 build has same problems with SIM issues, tether, and chrome freezing. Camera continues to work. I did clean flash. Eager to see if you can put your camera changes into Hashbang 15.1 because that is a solid build.
[X Style (Pure) Android Development] AgathosAnthropos:
Finally got it built and wiped then flashed onto my device

Booting into it and setting up now. If all initial testing goes okay, I'll upload tonight or let ya know it's still not working.

Well, it's booting and running okay it seems but the camera still doesn't work with my patches. It's worse than on 16 so I'll let you know when I get something going.
[X Style (Pure) Android Development] slyger:
Can you dirty flash this over LOS 14? Or do you need to upgrade to Nougat first?

Or is a full wipe and fresh install the way to go? I no longer use this phone for calls so it's purely a media/gaming device at this point.
[X Style (Pure) Android Development] AgathosAnthropos:
It won't work. Going to the 16 image you have to wipe, flash nougat, then you can go to 16
[X Style (Pure) Android Development] insomniac89:
Hashbang has retired his Moto X Pure, right? Does it make sense to push an Oreo build over a pie one?
[X Style (Pure) Android Development] kb8no:
Hashbang made a 16 build for us recently and told us it booted so he has a phone. Look back at his posts. He still is the keeper of Moto X Pure TWRP. He will drop us a bone now and then.

We are not putting a 16 build on 15. Its the dang camera we're trying to get to work on 15 or 16. Hashbang 15 is a great ROM but no camera. We have camera on 16 but ROM is not solid. Camera is more a Moto problem than LOS.

A working 15 with a camera would be a gift and much better than 14. There is reason to think the same genius trick he played on 16 will work on 15. Fingers crossed.

The view from Duluth.
[X Style (Pure) Android Development] DjDill:
DRM fix - Chrome fix - Netflix fix

Hello awesome community! :highfive:

TL DR

- flash the attached zip for working Chrome and Netflix

So I played around with the below all day on the below rom

Thank you for your good work [MENTION=9796853]AgathosAnthropos[/MENTION] for getting the camera working

& [MENTION=1776875]randomblame[/MENTION]

I managed to find the code that is causing issues with Netflix not opening and Chrome hanging in AgathosAnthropos build. The Log kept spitting out

Issues with IDrmFactory all the time over and over again.. found a thread on XDA reported issues with Netflix too :

https://xdaforums.com/g4/development/lineageos-15-1-lg-g4-t3782722/page67/amp/

Applied the same change to manifest.xml only and managed to get DRM working. This inturn fixed Chrome crashing / locking up. Also apps like 'DRM info' start working (before they just didn't open at all)

Then spent the rest of my day making a easy flash able file for everyone. ( See attached)

Download and restart to twrp then flash and DRM will be working again.

For the devs to fix in the source or if you wish to manually edit the file:

/system/vendor/etc/vintf/manifest.xml

New change line 62:

Remove the stuff that is in the line from 62

Replace with the below

<hal format="hidl">
<name>android.hardware.drm</name>
<transport arch="32+64">passthrough</transport>
<version>1.0</version>
<interface>
<name>IDrmFactory</name>
<instance>default</instance>
</interface>
</hal>

End before this line about line 72

<hal format="hidl">

<name>android.hardware.gatekeeper

If you merge this in to the source tree then the next build should be working. Until then flash the zip to change the file. I put in a line to backup the current manifest Incase something goes wrong.

Let me know if you have any issues :good:
[X Style (Pure) Android Development] kb8no:
[MENTION=9796853]AgathosAnthropos[/MENTION]

We won the lottery, or at least we won at Bingo! I did a clean flash of [MENTION=9796853]AgathosAnthropos[/MENTION] latest ROM with camera working followed by [MENTION=698697]DjDill[/MENTION] recent zip and then gapps. I also installed my Verizon SIM before booting so it was initialized at the time of the first boot and Goggle login. I did not flash Magisk zip. It took it's usual good time to boot and the login to Google was usual without glitch. When the ROM came up it was on Verizon LTE rock stable and the Verizon APN was imported perfectly - BAM! Google Chrome worked BAM! Camera worked - BAM! GPS worked and took a fix quickly - BAM. Went to check out the WiFi tether and it worked with default SSID and PW - BAM! I was able to change the PW normally but what did not work was if you try to change the SSID it will do a hard reboot and won't stick as before. Went to check USB tether and it worked - BAM! However, when you turn USB tether off it will do a hard reboot as before. Everything Google I checked works. My usual apps work: Weatherbug, Corporate Outlook, YouTube, SMS, Phone call, Speedtest. and Tapatalk. I then installed Magisk using the Magisk Manager app downloaded from their site and it worked. I will keep pushing it but I think we have a DD here and I am setting it up as such. It's been a very long wait! Interested in the experience of others.
[X Style (Pure) Android Development] insomniac89:
I'll give it a try tomorrow and let you know how it works for me. The camera was very spotty for me, would work once or twice with the noted image rotation issue, but this new Chrome Fix is nice :) Thanks [MENTION=698697]DjDill[/MENTION] and [MENTION=9796853]AgathosAnthropos[/MENTION]
[X Style (Pure) Android Development] kb8no:
[MENTION=6672417]insomniac89[/MENTION] The rotation issue is a very small price to pay for a working camera. Most pictures would be taken in landscape which shows up in in the usual orientation. Rotating a few portraits 90 deg clockwise is not much of a burden. Otherwise I haven't found any issues with the camera and it has worked well. I don't push it hard.
[X Style (Pure) Android Development] Pantherrra:
Coming back from holidays to read progress has been made! Nice! How is the experience so far? Is there a build available that has the changes from agathosanthropos and djdill implemented? I'm still on an old build from randomblame so I assume I can not just flash djdill's work on top?

Big thanks to all the contributors btw!
[X Style (Pure) Android Development] kb8no:
Yep, progress made! [MENTION=9796853]AgathosAnthropos[/MENTION] last build fixed the camera using [MENTION=1776875]randomblame[/MENTION] last build and his camera changes with 7/5 security update. [MENTION=698697]DjDill[/MENTION] zip over that build fixes the Chrome problem. [MENTION=5689799]agantho[/MENTION]sAnthropos has not yet made a new build with the zip. I hope he will get that done soon. Still some cleanup of some small things left but I'm happily using it as my daily driver now. Honestly, the known tether glitches are all I have found but even that is usable. Very smooth, very nice. This is much better than Hashbang's last 14.1 build. Try it.
[X Style (Pure) Android Development] randomblame:
building for clark today

incorporated AgathosAnthropos's camera hax and djdills manifest change for drm, not sure why hwbinder wasn't working there but that's interesting. Made a couple other experimental changes and of course synced with the latest lineage goodness. Link in op
[X Style (Pure) Android Development] kb8no:
[MENTION=1776875]randomblame[/MENTION] Can you fix the tether next? I'll try it out when I get back from my haircut. Dirty flash I hope.
[X Style (Pure) Android Development] bsorli:
I'm hopeful that randomblame's (so glad you're back and big thumbs up with everything that's been happening) build compilation finally brings things together. It has been FANTASTIC all the work everyone has done to bring some life camera wise and many many fixes for Chrome, Netflix, and security updates. I'll have more time next week to test drive, but I have a roof to repair and looking forward to hearing from anyone who's had a chance to try out randomblame's new build???

Can anyone reference the Chrome and Netflix DRM fixes and how this affects future updates? I don't use Chrome much, but I know all too well that Google likes pushing updates for everyone of their apps. Suspect similar too using YouTube Vanced, probably have to shutoff auto-updates on these specific or related (YouTube) apps. Thanks everyone!!! Sorli...
[X Style (Pure) Android Development] kb8no:
[MENTION=1776875]randomblame[/MENTION] Dirty flashed new ROM just fine. Couple reboots needed to settle down. Camera and Chrome works. 7/5/19 security patch. Magisk happy. Using as my DD.
[X Style (Pure) Android Development] randomblame:
More work today new build fixes drm PROPERLY using hwbinder transport and added clearkey plugin, some performance and memory optimizations also. Netflix working

new build in op
[X Style (Pure) Android Development] kb8no:
On the surface it is the same but dirty flash was not hesitant after boot and did not need any reboot. It was not bad before but it is even smoother and snappier now.
[X Style (Pure) Android Development] randomblame:
messing with usb tethering
[X Style (Pure) Android Development] kb8no:
As you have no doubt noted, WiFi and USB tether work when you start them but they hard reboot when you shut them off, USB or WiFi. So it's gotta be the same problem for both USB and WiFi, a final common pathway. So it is not a hard stop, not maybe the highest priority before, and has a workaround, but it is annoying.
[X Style (Pure) Android Development] randomblame:
Ah I thought it was only usb tethering that was borked that is helpful
[X Style (Pure) Android Development] DjDill:
Hey [MENTION=1776875]randomblame[/MENTION]

Next rebuild if you can add the below in manifest.xml please

Stops logcat complaining about mapper being missing

Added below android.hardware.gnss

<hal format="hidl">
<name>android.hardware.graphics.mapper</name>
<transport arch="32+64">passthrough</transport>
<version>2.0</version>
<interface>
<name>IMapper</name>
<instance>default</instance>
</interface>
</hal>

Also having problems with mic volume with Facebook Messenger etc when on speaker call / video with the stock volumes.

Don't know if this being happening for anyone else and I mentioned it a few months back but it doesn't appear anyone else is having the problem

Changed line 23/24 in mixer_paths.xml

<ctl name="IN2L Digital Volume" value="150" />
<ctl name="IN2R Digital Volume" value="150" />
[X Style (Pure) Android Development] randomblame:
Done https://www.androidfilehost.com/?fid=6006931924117926152
[X Style (Pure) Android Development] DjDill:
Super fast! Thanks for the effort :)

I will see what else I can debug out and let you know

I have been using this now for about 2 weeks. Pretty dam stable
[X Style (Pure) Android Development] Pantherrra:
I dirty flashed this build (20190729) over an older one (20190227). Flashing and booting went fine. Booting goes faster than before with the older build. Everything seems to work as described in previous posts (chrome etc). The camera doesn't seem to work for me though. Contrary to the older build, the camera does start (e.g. in Camera MX, Camera ZOOM FX, whatsapp), it seems to capture the image (as in the image freezes) but then it blocks and the image is not saved. Making videos is not a problem (nice!). I have tried different camera apps and in portrait/landscape mode. Could this be because I dirty flashed over an older build (instead of the previous build)? I've also noticed that the standard android camera app refuses to start. Anybody else noticed this behaviour?

Thanks again to all the contributors and to [MENTION=1776875]randomblame[/MENTION] for putting this together so fast!
[X Style (Pure) Android Development] randomblame:
Sorry I was experimenting on camera Hal I may have broken it on that last build here is the previous one https://www.androidfilehost.com/?fid=6006931924117926049
[X Style (Pure) Android Development] Pantherrra:
No worries! :) Can I dirty flash that over the newer build?
[X Style (Pure) Android Development] randomblame:
Yep
[X Style (Pure) Android Development] kb8no:
My camera was not broke with dirty flash. Try a clean flash. BTW, no reason to use screen shots, use the real camera.
[X Style (Pure) Android Development] insomniac89:
Hey guys, I have some interesting news. I guess I never really tried it before, but my photos seem to be ok in landscape, or is this only me?
[X Style (Pure) Android Development] xabr3:
Camera is partly fixed, it only takes pictures in landscape without post processing. (movie all works)
[X Style (Pure) Android Development] kadopt:
I tried both 28th v2 and 29th builds and noticed that cpu load stays at 30% or more with all 4 small cores at 1.4 GHz. Also logcat gets kinda busy.

I don't have any logs or prints but can try to produce some later today as I flashed those builds yesterday night and I need a stable device so I rolled back to 14th build by AgathosAnthropos and is now fine.

[edit]Everything was dirty flashed[/edit]
[X Style (Pure) Android Development] DjDill:
Yep can confirm 29th build is bugged out

Log cat complaining over and over again:

xport_reg Failed for service_id=0x35 version=0x1001 on 12

In boot ::

'pm-service doesn't have permission' .*

I hope that helps I have rolled back to 27th build

lineage-16.0-20190728-UNOFFICIAL-clark.zip

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

That worked but I lost Sim .. back flashed to

lineage-16.0-20190714-UNOFFICIAL-clark.zip

And applied DRM fix.. working again I am sure I can flash forward again now but for all the way to the 29th

---------- Post added at 09:01 PM ---------- Previous post was at 08:46 PM ----------

Worked fine flashed forward again working stable and GSM working
[X Style (Pure) Android Development] randomblame:
So the problem was from dirty flashing? What builds have the issue? My pures USB port is pretty trashed lol and I'm at work today
[X Style (Pure) Android Development] kb8no:
I have flashed 14th with DjDill zip, 28th v1, 28th v2, and 29th all of them dirty flashed. All of them worked fine, camera, everything but tether. 28th v1 felt just like 14th and first boot little ragged on both of them. 28th v2 had huge improvement in performance and a smooth boot and was amazing. 29th seemed to preform the same as 28th v2 but immediately I noticed battery consumption was a problem on 29th. Tried to take it to work today and had to keep it on charge so it would run (can't work without my phone). That agrees with [MENTION=3723165]kadopt[/MENTION] and [MENTION=698697]DjDill[/MENTION] of high CPU load on 29th. [MENTION=3723165]kadopt[/MENTION] said 28th v2 as well but the builds came out so fast I could not say if the battery consumption was bad on 28th v2 and I was likely not paying attention being blown away by the speed and lack of lag. Never did any of these last 3 builds make the bork the camera. It was my comment that maybe [MENTION=681076]pantherr[/MENTION]a needed a clean flash and that is why his camera was not working but not my case. I am going to flash 28th v2 and see if it has high battery drain as well. If so I will go to @28 v2.

Note: 28th v2 is working fine regarding battery life. It may have its flaws, who knows, but it is the best one so far. 29th is the culprit on my phone.