yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] Gilbed:
Thank you! But I am not feeling comfortable using custom builds. Does anyone know if LineageOS is working on this to fix it in a future build? Or is it already working in the latest version now (3/21)? Thanks!!
[X Style (Pure) Android Development] xabr3:
I think in 15.1 it is all fixed.
[X Style (Pure) Android Development] Gilbed:
Thanks, but is that 15.1 stable enough already?
[X Style (Pure) Android Development] xabr3:
It is not even released...
[X Style (Pure) Android Development] Gilbed:
so you think they will not fix it in 14.1?
[X Style (Pure) Android Development] xabr3:
No.
[X Style (Pure) Android Development] parker.stephens:
Use my ROM or don't. I put instructions above and so did another guy about how to get the ROM working on your phone. Also, 3-21 does not include any other boot loaders.
[X Style (Pure) Android Development] big_marcolino:
Does anyone know a Pixel Mod for Moto X Pure with LineageOS? Works in 14.1 and 15.1? Thanks
[X Style (Pure) Android Development] Fabiett83:
New lineage-14.1-20180325-UNOFFICIAL-clark.zip on hashbang AFH

https://androidfilehost.com/?fid=746010030569964609

Bootloader are restricted to 0xA050 & 0xA052 so is for nougat baseband and modem.

I just flashed it and seems to be working just like 20180317.

I think the only change is the inclusion of the 0xA050 bootloader in the updater-script
[X Style (Pure) Android Development] big_marcolino:
Do you know the main difference between nougat baseband and marshmallow?
[X Style (Pure) Android Development] Fabiett83:
I'm sorry no, all I know is that official LOS 14.1 supports only MM modem because all those commits are still not merged:

https://review.lineageos.org/#/q/topic:clark_n

so I need to use hashbang's unofficial version.

LOS 15.1 will be based on the N modem/BL/BB so I don't need to change anything to try new versions, since downgrading & upgrading was the cause of my last brick.
[X Style (Pure) Android Development] Hashbang173:
I have an unofficial build for Nougat firmware with some fixes for VoLTE.

[MENTION=4465682]kb8no[/MENTION] I think you were having issues with VoLTE.

Let me know if this helps with VoLTE at all. If not, logs are welcome :)

https://www.androidfilehost.com/?fid=890129502657593935
[X Style (Pure) Android Development] kb8no:
It works! Enabled Enhanced 4G LTE on Verizon and I can make a call, audio works, and the call does not drop. I did not prove that VoLTE works cuz it was a CDMA call but breaking phone call is gone. :)
[X Style (Pure) Android Development] kb8no:
[MENTION=4630246]Hashbang173[/MENTION]

I have 2 identical phones. Phone A is mine and phone B is my wife's. Installed 3/26 on phone A and l it works as it should when I call phone B on CDMA.

So I installed 3/26 on phone B to see if I could make a VoLTE call. 3/26 on Phone B did not resolve the loss of audio and drop when I called Phone A.

So I called phone B from phone A and had my first beautiful HD VoLTE call ever. But phone B can only take incoming but not make outgoing. Seems very weird, I am only reporting what happened. Any thoughts?

I will get log for you but need some time cuz of work.
[X Style (Pure) Android Development] kb8no:
[MENTION=4630246]Hashbang173[/MENTION]

I swapped SIM's. Phone B did not work. Swapped back and now Phone A doesn't work. It only worked for a short time and not repeatable. I'll get a log .
[X Style (Pure) Android Development] Sir2taj:
Hi,

I have been facing a very strange issue with my dual sim indian variant xt1572 . Both the sims work fine on stock rom however on custom roms no sim is being detected . Have tried your latest build but no relief .

Flashing procedure -

Fastboot install nougat firmware

latest twrp installed

factory reset

flash lineage build

no sim detected .

Moreover the imei information should be shown for both the sim which isnt the case(attachment) .

Please guide .
[X Style (Pure) Android Development] kadopt:
Anyone know how to enable audio on 14th build of 15.1?

Thanks
[X Style (Pure) Android Development] big_marcolino:
The recent unofficial 15.1 is stable enough to use? I wanna flash here, but I don't know if it's worth it. If an official release was launched, I'll be able to update normally?
[X Style (Pure) Android Development] Alibaba0101:
Is there a reason why the official lineage builds are using interactive governors? I've noticed again, that the 6th large core gets spun down and overall the phones feels sluggish and has audtio clipping issues until i modify both governers to ondemand.

I also noticed on my lgv20 official lineage the governors are both set to schedutil which is not an option with the moto x pure. I assume this is kernel dependent? Aren't the official version all using the lineage kernel?
[X Style (Pure) Android Development] BruceWayne54:
how do you modify the governors to on demand? I'm having the same pfblems
[X Style (Pure) Android Development] Alibaba0101:
Use the kernel aduitor app from the playstore, under cpu you can change the governor for both small and large cores in addition to some other settings like cpu boot for input.
[X Style (Pure) Android Development] Hashbang173:
Odd behavior, hopefully the log shows the problem
[X Style (Pure) Android Development] ACardAttack:
Is there an unofficial for clark?

Biggest issue is getting camera to work, I don't think anyone has figured that out yet
[X Style (Pure) Android Development] kb8no:
Made a CDMA call with Enhanced 4G LTE Mode (Verizon) engaged with syslog. Same problem of cannot hear caller and caller cannot hear me on 3/26/18 test build. What is different is that phone call does not drop whereas on previous builds call would drop in less than a minute. If you disengage Enhanced then phone call works normally (of course no VoLTE). Let me know if syslog is adequate. I relearned how to take and send them so I can do it quickly now. Let me know what else you want me to try. It did work momentarily as I mentioned before it died. Indeed, strange.
[X Style (Pure) Android Development] ninormalen:
Can anyone share me a link to latest official lineage version for clark. Download section on lineageos.org is down.
[X Style (Pure) Android Development] big_marcolino:
https://androidfilehost.com/?fid=890129502657593935
[X Style (Pure) Android Development] Hashbang173:
Thank you for the log, I have another build for you. This build has a different IMS (VoLTE) stack. This has fixed many errors that I found in the log you gave me. Let me know if this changes anything at all, and logs are very welcome :fingers-crossed:

https://www.androidfilehost.com/?fid=962187416754472277
[X Style (Pure) Android Development] kb8no:
Still no audio calling out. I can call in. Syslog attached.
[X Style (Pure) Android Development] ACardAttack:
Thats a link for LOS14, but your post I replied to was about LOS15
[X Style (Pure) Android Development] big_marcolino:
Oh, sorry. https://androidfilehost.com/?fid=962187416754467790
[X Style (Pure) Android Development] kb8no:
[MENTION=4630246]Hashbang173[/MENTION]

This syslog was Verizon to ATT. I just called Verizon to Verizon both with VoLTE enabled. Still no sound either way but dialer acknowledged HD call and call dropped.
[X Style (Pure) Android Development] KC69:
Does the camera work on this version? There's a 3/19 on afh that never booted for me. It's not from Hashbang tho. Camera is the only thing keeping me on 14.1
[X Style (Pure) Android Development] skuppej:
I'm considering changing from AICP to LineageOS and I am still on MM bootloader/modem. I am not planning on updating to Nougat stock for a while, due to repeat issues I've had with the modem and needing to RMA my device each time I tried this.

What is the latest March nightly of this ROM that is still on MM?

I've read through the forum and it sounds like it is a mix. I know 2/28 is MM. How about the newer ones?
[X Style (Pure) Android Development] big_marcolino:
I don't know, I don't flash yet. I'm considering flash today, tomorrow or maybe not. It seems to have many bugs (camera, sound, call), according to what I read in the thread. Maybe I backup my 14.1 with TWRP and test this 15.1
[X Style (Pure) Android Development] ACardAttack:
Unlikely, still haven't heard anyone getting camera to work on Clark Oreo
[X Style (Pure) Android Development] kadopt:
Nice one!

[IMG="Nice one!"]http://www.firegoon.com/u/8i4h.png[/IMG]
[X Style (Pure) Android Development] kb8no:
Any feedback on today's release of unofficial 14.1 or 15.1?
[X Style (Pure) Android Development] kb8no:
I tried 4/1 and got that same counterfeit warning. April fools?
[X Style (Pure) Android Development] Strephon Alkhalikoi:
You're likely seeing that due to Google's new verification checks for its apps. About the only things to be done for right now are either to register your GSF ID for an exemption, install Magisk, or roll back to stock.
[X Style (Pure) Android Development] kadopt:
Using 15.1 currently, camera is not working, audio now works, NFC was cycling between enabled and disabled yesterday but today seems to work fine (can read cards). Didn't try any phone calls yet. Other wise working fine. No FC happened yet.

14.1 worked fine.

That may be April's fool buy they even made a wallet app for the coins! ?
[X Style (Pure) Android Development] fritzophrenic:
All of the official builds to date are for Marshmallow bootloader/modem. Right now only unofficial builds support Nougat bootloader/modem. If I understand Hashbang's plans correctly, this will remain the case until Oreo goes official.
[X Style (Pure) Android Development] :
I dont like the direction android is going with the digital transaction and verfied this and verfied that. I was just locked out my phone for hours a couple days ago. Somehow I was logged out of my phone and had to sign back in then they had to verify it was me but I didnt have the options to verify. Then hours later I was logged back in without verifying. For one its no ones business who I am. I'm a user, what does my legal name and info have to do with anything. I'm just about to walk away from this surveillance state.
[X Style (Pure) Android Development] Strephon Alkhalikoi:
Goodbye?
[X Style (Pure) Android Development] :
Pretty close to goodbye. We'll see. If people just keep going with the flow and accepting whatever is done without question I'll have no choice. Technology isnt worth it for me.
[X Style (Pure) Android Development] Strephon Alkhalikoi:
See, your problem is, you think I somehow give a damn. You're only posting to get attention, so if you're going to leave, stop flapping your gums and GTFO.
[X Style (Pure) Android Development] :
My intention is to let the few who care know that there is someone else who cares. Calm yourself commoner.
[X Style (Pure) Android Development] Strephon Alkhalikoi:
You keep telling yourself that junior.
[X Style (Pure) Android Development] :
Yeah man. You keep doing you. Be at peace.
[X Style (Pure) Android Development] Daredevil 720:
So, I was running the latest nightly when yesterday my phone shut down due to low battery. I plugged it to the charger, tried to turn it on, and I got welcomed by a wonderful bootloop at the LineageOS logo.

After trying out many things, I had to wipe the phone and reinstall LineageOS. After doing so everything is back to normal except for one thing. There's a rectangular region in the middle of the screen where the digitiser fails to register taps. It's right where most of the small dialog boxes appear and I can't interact with them. For example I can't change the vibration duration in the settings because the slider dialogue appears in that region where the touch doesn't work.

Is this Android related or is my hardware failing?
[X Style (Pure) Android Development] Strephon Alkhalikoi:
Reinstall stock. If that region of the screen fails to function after the stock ROM is installed, then it's most likely hardware.
[X Style (Pure) Android Development] kb8no:
Apparently this is an April Fools joke.

https://www.reddit.com/r/LineageOS/comments/88xujd/loscoins_on_my_device_yesno/

https://www.google.com/amp/s/xdafor...ncement-lineage-team-introduces-t3771852/amp/

Kind of a sick joke.
[X Style (Pure) Android Development] Daredevil 720:
So today there's another part of the screen where the touch doesn't work as well, the navigation bar at the bottom. I refuse to believe it's hardware related, it can't be the navigation bar with pixel perfect accuracy!! Only thing that's confusing me is that the touch fails in TWRP as well.

Can someone tell me how to go back to stock without risking a hard brick?

I have the European version of the XT1572. Before going to custom ROMs I was on the latest official Nougat (7) release. I unlocked the bootloader, installed TWRP 3.2.1-0 using fastboot, flashed the MM modem from this post (https://xdaforums.com/showpost.php?p=75610090&postcount=2) directly through TWRP and then installed the latest official LOS14.1 nightly with pico GApps. My bootloader version was/is 0xA052 and I had to edit the updater-script in the official LOS14.1 zip to get it to install. I should also mention that the bootloader won't tell me which baseband is installed, although telephony/4G works fine.

Based on all this information, what is the best route about going back stock? I have to tell you that for the life of me I can't find a stock Nougat firmware image for the European version of this phone, only Marshmallow 6.0.1.
[X Style (Pure) Android Development] ghurkan:
Hello everyone. First of all, [MENTION=4630246]Hashbang173[/MENTION], thank you for all of your effort. I've been using both AICP and your unofficial LOS. They are great.

Second, I need some help with random crashes and reboots with unofficial LOS.

I'm currently on 20180317 Unofficial, Nougat modem, standard kernel, Magisk root. I don't use adiutor, even though I have it installed.

Here is what happens: Randomly, my phone stops responding. This can happen when I try to pull down notification bar, or when I first unlock it, or while taking any other arbitrary action. After that, the UI usually stops, so navigation bar and status bar vanishes. Screen can be turned on and off by pressing power button but nothing changes contextually. Lastly, battery drains dramatically. I have lost %20-30 battery before when I was waiting it to recover. Only recovery is force reboot btw.

I can't get any logcat, because when I reboot the logs get cleared. Also I can't get logcat because, well, can't do **** when it is unresponsive.

Can you guys help with this issue?
[X Style (Pure) Android Development] TheYoz:
If it's occurring in TWRP then its 100% hardware related. Are you using any other charger other than the one provided with the phone? I know that in the past, over voltage can cause dead spots on the screen.

Try fast boot flashing back to Stock Nougat. Just make sure you don't roll back to MM or you will be f*&ked. There is a download link somewhere here in the forums where you can get it. I doubt that will fix it though if this is happening in recovery.

---------- Post added at 10:29 AM ---------- Previous post was at 10:23 AM ----------

Honestly, I don't think the unofficials are really recommended for a daily driver. I used it for a few weeks and I was experiencing the exact same thing as you state. I rolled back to stock Nougat and all is well. I'll wait for official Nougat and Oreo builds with the N modems before I flash customs back on this phone.
[X Style (Pure) Android Development] fritzophrenic:
I have seen several reports of (and personally experienced) narrow bands of the screen becoming unresponsive due to hardware in the Moto X Pure. When I had mine, my phone was still in the warranty period and Motorola sent me a replacement device for free. Obviously outside of the warranty period you'll need to send them some money but it's still (probably) cheaper than a brand new phone. As it is a hardware issue, they didn't give me any problems for my unlocked bootloader, although I did wipe and restore stock before sending in my old device.

I agree with the poster that suggests the issue applying to TWRP indicates hardware.

You can download simple apps that just show dots/lines while you trace your finger, to see exactly where the dead area extends. Or a drawing/handwriting app of some kind. Or use a Google Keep if it's on your device already.

As a temporary workaround: enable all the screen rotation settings so you can rotate the nav bar to the other side of the phone. But obviously it's not a nice thing to deal with long term.
[X Style (Pure) Android Development] :
Kinda sick indeed. Definitely got me lol. What a relief!
[X Style (Pure) Android Development] Daredevil 720:
For the time being I just lowered the DPI in order to make the navigation bar taller. That should do it until another screen part fails at least.

I haven't been using any other charger lately. I think I must have laid on my phone a few days back and that the screen failed due to the pressure.

Please help me find a stock Nougat ROM for the European XT1572 so I can go back to stock and sell this phone to anyone willing to replace the screen. I can't be bothered with Motorola service.

Thanks!
[X Style (Pure) Android Development] muelo1000:
What a relieve !!! lol I was like "LOSCoins " .... Nooo Thank you !!
[X Style (Pure) Android Development] ghurkan:
Well, you're right, they may not be the best ones for a DD, but I like my customisations :D Also I got used to random boots or lags now and then but this battery drain thingy is killing me and my phone. I just got another while trying to reply your post. I attached an SS for an example.

After this last reboot I may revert to stock and wait until some improvement but going stock and back process bothers me more. Maybe try another nougat modem rom for a while?..
[X Style (Pure) Android Development] kadopt:
[MENTION=4576163]TheYoz[/MENTION] [MENTION=7804913]ghurkan[/MENTION] I'm using unofficial 15.1 and don't have any random reboots or lags, only issues are non working camera and audio quality gets dodgy if the sounds go too quiet. Been using it for 5 days now.

I've also went from stock mm to stock nougat and back (with fastboot and stock recovery zip flashing) without issues. Using Euro XT1572 btw.
[X Style (Pure) Android Development] Daredevil 720:
Any link for the stock Nougat ROM?
[X Style (Pure) Android Development] kadopt:
No, I fastbooted mm, then applied various updates with stock recovery untill I reached latest nougat. You have to flash then reboot the device and start Android so it can update itself after every update.

I can see the necessary files for it if you want.
[X Style (Pure) Android Development] stevejohnson42:
https://xdaforums.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142

Read the OP very carefully - this is how I went to stock Nougat -- for about 10 minutes ; then went to custom ROMs that were based on the N Modem
[X Style (Pure) Android Development] Daredevil 720:
Considering I was already on stock Nougat before going custom, won't I hard brick the phone if I go back to stock MM and take the OTAs to Nougat? That's what I've read. :(

This is for the RetUS XT1575 version. Not really sure if I can apply it to my own.
[X Style (Pure) Android Development] stevejohnson42:
Agree - it is a very specific solution for one of the variants ; I wasn't sure what you had - you did what I suggested ; read the OP carefully -

It was the only place I was aware of for Nougat stock files -- so I tossed it out there hoping it was the same variant you had
[X Style (Pure) Android Development] TheYoz:
There are ways around it, but I'd suggest just staying with stock N until something more stable is released. You can very well brick your device if you don't follow the downgrade instructions precisely. And for the above user, a camera not working, to me at least, isn't DD worthy. The people that use the N and O unofficials are more for testing and sending logcats to the dev. I'm not sure why everyone uses these then complains that certain things don't work.
[X Style (Pure) Android Development] kadopt:
I didn't brick mine.

I fastbooted this "XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5.zip", allowed android to boot to welcome screen,

then flashed all mm and n updates from stock recovery one at a time, always allowing android to boot to welcome screen between updates.

Blur_Version.24.211.58.clark_reteu.reteu.en.EU.zip

Blur_Version.24.221.1.clark_reteu.reteu.en.EU.zip

Blur_Version.24.221.5.clark_reteu.reteu.en.EU.zip

Blur_Version.24.231.13.clark_reteu.reteu.en.EU.zip

Blur_Version.25.11.15.clark_reteu.reteu.en.EU.zip

Blur_Version.25.211.8.clark_reteu.reteu.en.EU.zip

All from here https://dl.prazaar.de/?dir=Android/Motorola/XT1572
[X Style (Pure) Android Development] rafmal000:
LOS Crashed and is now in a bootloop

Basically, LOS completely froze (for the fifth time in 2 months) for about 20 minutes and my phone was totally unresponsive. The weird thing is I couldn't hard-reboot it either, as all 3 buttons were unresponsive. Holding power+voldown/power+volup did nothing. The screen just turns off for about 20 minutes until the phone either randomly starts working again or it reboots itself. This has happened 4 times before, but the weird thing is now it's stuck in a bootloop after the latest crash. The bootloop occurs after it asks for my decryption PIN, so at least it can partially load the OS.

This occurred with one of Hashbang's February builds (can't remember which one specifically). I tried updating to one of the more recent builds (0325, 0326, and 0331 IIRC) but the bootloop is still there. Is there anything else I can try without losing anything (apps, settings, etc)? I was thinking about wiping the boot partition and re-flashing LOS. Would that work?
[X Style (Pure) Android Development] biggy238:
I updated to 4/1 nightly, got had by the stupid ass joke, and now my phone refuses to identify the SIM?

Is there something I can to, or jump back to the original nightly?

Edit: NM. I wiped all but data and flashed 03/07 again.

I didn't pull the log, but it post something along the lines of the modem resource not being available.
[X Style (Pure) Android Development] kb8no:
I am on Nougat firmware.I lost my SIM and IMEA. Not due to stupid ass joke. I have 4 of these phones (love them). I can't remember the details but I was close to brick. I flashed stock and IMEA returned. BAM.
[X Style (Pure) Android Development] edison0354:
Same issue for me...

Flash stock, boot once, then clear data and cache to flash lineageos to get SIM worked. But when updating lineageos, it doesn't work again...

Even I backup modem partition in TWRP when it's still working, then upgrade lineageos and restore modem doesn't work...
[X Style (Pure) Android Development] biggy238:
No, no. I know the problem was unrelated to the joke, but just imagine the level of fury thinking you're jumping to an update, then the joke is played AND the SIM won't read after that update.
[X Style (Pure) Android Development] bastardtrees:
Sim not working is fixed by uninstalling Xposed and magisk and both substratum rescue zips

Then removing the actual sim card itself before installing the update

The IMEI and baseband always always disappears after every update if you don't remove the Sim before installing
[X Style (Pure) Android Development] kb8no:
I have dirty flashed every unofficial on this particular phone since 2/10 without ever loosing IMEI. Tried 4/1 and found the very bad joke, immediately restored 3/31 so fast I would not have noticed SIM and refuse to flash 4/1 again. I do not use substratum or exposed. Using SuperSU currently but have used Magisk.

2 other phones similar experience. Only time I lost IMEI was on 4th phone using 15.1 unofficial 2/10 and TWRP official coming from 15.1 unofficial 1/29 with unofficial recovery. I was using Magisk with the data f2fs formatting monkey business.

So can we isolate when this started and under what circumstances? Something changed and is causing this and it is intermittent.
[X Style (Pure) Android Development] :
HB put out a new update. I havent tried it yet but downloading now