yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] silvernirvash:
I downloaded the addonsu package after installing lineage os and root checker says I don't have root?? So I need to reinstall and start from fresh to have it work??? SuperSU says su binaries occupied.
[X Style (Pure) Android Development] Pastinakel:
To have root after installing the addonsu package, you'll have to enable it in developer options.
[X Style (Pure) Android Development] silvernirvash:
I found it! But supersu still says binaries are occupied. Should I uninstall supersu and reinstall it from the PlayStore???

Oh oh and do you know if substratum works with this rom??? I read earlier in the thread that an older version of the rom does not in fact support substratum but does the current version work??? If so can you suggest any themes that work??? I had anteres on RR but don't want to take the chance that it will cause some massive crash before asking around.
[X Style (Pure) Android Development] spatje:
Rom from 10/02 is very good.But the when i cal with phonespeaker on, they can't hear me. Mic is still not working? Is there an fix for?
[X Style (Pure) Android Development] xabr3:
Do we still need to downgrade to Marshmallow modem if coming from stock 7.0 ?
[X Style (Pure) Android Development] Spencervb256:
Yes
[X Style (Pure) Android Development] xabr3:
Hopefully LOS15 will fix this.
[X Style (Pure) Android Development] nathan_barstow14:
Is there no hope of this being fixed in LOS14.1 already?
[X Style (Pure) Android Development] Bwangster12:
Has anything from the stock 7.0 update been incorporated into the regular nightlies for 14.1 yet? Speakerphone mic also still doesn't work?
[X Style (Pure) Android Development] ACardAttack:
Anyone know if anyone is planning on ,or is working on a Oreo/LOS15 version for the X Pure?
[X Style (Pure) Android Development] OptoChip:
I may be wrong on this but I believe the need for the MM downgrade is because the Nougat "kernel" that Motorola released has to be incorporated into the Nougat kernels in order for the downgrade to go away. But because Android O is already around the corner there really isn't a big push to get the N kernel incorporated since most Devs would rather push towards getting O builds going.
[X Style (Pure) Android Development] nathan_barstow14:
I totally understand the desire to get LOS15 moving forward at this point, but personally I still can't shake the feeling that I'd love to see a LOS14.1 finished up correctly first. Overall it was great, but if integrating some of the official kernel into the AOSP branch is all it will take (not to make that sound easy), I'd donate a case of beer to someone that could pull that off. I never used root, but I prefer LOS over stock.

With that said - since I started running the official Nougat ROM there is one major (to me) issue which seems to be resolved that LOS14.1 always had... I have a Moto 360 v2, and on LOS14.1 anytime I'd walk away from my phone for longer than 10-15 minutes, my phone would forgot the pairing to the watch and I would have to go through the pairing process for a bluetooth device again. On this stock Nougat ROM so far I've left my watch at home for a whole day and when I came home they synced back up and kept working fine. It's incredibly frustrating, and I'm very hopeful that getting the official 7.x kernel integrated may help that. Honestly it may be in the modem, too, but we won't know until we can run LOS14.1 on the Nougat modem.
[X Style (Pure) Android Development] Bwangster12:
Additionally, camera never worked well and speakerphone mic didn't work at all when on calls.
[X Style (Pure) Android Development] nathan_barstow14:
Yeah the default Google Camera didn't work well but I always downloaded the Moto Camera from the Playstore and never had any issues. The speakerphone mic makes sense; Every time I tried to use it people said they couldn't hear me... I just assumed the mic sucked. I guess that is a problem I wasn't fully aware of.
[X Style (Pure) Android Development] Fabiett83:
[MENTION=4630246]Hashbang173[/MENTION] posted a LOS 14.1 test build some times ago with the 7.0 firmware integrated and working with the 7.0 modem

Sorry i have not tested speakerphone, but bluetooth coupled with my car worked well

in the post it was referring to the 20170810 build

the last one published in androidfilehost is 20170930 https://androidfilehost.com/?fid=817906626617935226

i tried his latest build but while restoring apps i come across an already mentioned F2FS bug and had to return to stock

i really hope he will find what causes this because i really like LOS14.1 over stock 7.0

(i know i posted the same thing in the X Style (Pure) General thread)
[X Style (Pure) Android Development] Bwangster12:
So it sounds like this built does have 7.0 factored in, but won't have the new KRACK security patches. Whereas, the new weeklies have these security patches, but I'm basically gauranteed to still have a camera that opens slowly and no mic when in speakerphone mode?

Who is the regular maintainer for Clark? Is Hashbang doing unofficial test builds that get made into official builds? I know Hashbang is a very well known developer, but I'm confused as to what he is doing and when/if it gets baked into the regular weekly releases.
[X Style (Pure) Android Development] Bwangster12:
https://xdaforums.com/moto-x-style/development/marshmallow-6-0-ota-modem-band-12-t3267680

Is this what I'd need to flash before flashing the latest LineageOS nightly, if I'm currently on stock rooted 7.0?
[X Style (Pure) Android Development] Fabiett83:
The official clark mantainer is [MENTION=4630246]Hashbang173[/MENTION] (https://wiki.lineageos.org/devices/clark)

I reflashed his unofficial build only to answer you:

-i called my wife and workplace with speakerphone and they hear me well

-i launched several times the lineageos camera (snap) and most of the times it takes 2-3 sec to have the preview, sometimes is instant, and one time it gave error connecting

-i tried the two motorola apps, camera and cameraone, and it always take 4-5 sec to the preview, but these two can't save to external storage

-for the security patches, we have to ask [MENTION=4630246]Hashbang173[/MENTION] for an updated build, i think he's working on htc flounder at the moment (https://review.lineageos.org/q/owner:hashbang173%40gmail.com,25)

PS: fearing the F2FS bug this time i formatted DATA (including internal storage) to EXT4 before installing lineageos and everything seems to work well
[X Style (Pure) Android Development] Bwangster12:
I appreciate the update... I'm tempted to get off Stock 7.0 with the KRACK issue, but it seems that the only choices I have right now are Omnirom (which I don't know much about, nor do I even see much talk in here about how it works on Clark) or LineageOS, but that has the bugs in the official build.
[X Style (Pure) Android Development] Hashbang173:
Here is an updated build based on the official 7.0 update and kernel: https://www.androidfilehost.com/?fid=962021903579486327

Feel free to use it and report any bugs you encounter.
[X Style (Pure) Android Development] Bwangster12:
This obviously doesn't have the KRACK patches though right?

Just so I understand... These are essentially test releases that are released before they get worked into the nightlies?
[X Style (Pure) Android Development] Hashbang173:
It should have most if not all patches (I'll look into if any are missing later).

https://review.lineageos.org/#/q/topic:krack-n+(status:open+OR+status:merged)
[X Style (Pure) Android Development] Bwangster12:
Do these get merged into the official builds? If I flash this and then later on want to update, do I have to clean install?
[X Style (Pure) Android Development] Fabiett83:
Thank you [MENTION=4630246]Hashbang173[/MENTION], i knew you where reading!

i flashed your latest build over the last and for now all seems good.

As i wrote before, at the moment my data partition is formatted ext4, if you think something changed and need a test i can change it again in F2FS, i only need to backup and restore whatsapp!

I don't know how to test the KRACK patches, but sincerely i don't really care if someone can steal my wi-fi password, the signal does not go beyond my property...

The changes will be merged when the developers say they are ready, and when they will get merged we can simply install the official build over the unofficial, if i remember well
[X Style (Pure) Android Development] GRVsingal:
Can I flash it over the stock 7.0 ?
[X Style (Pure) Android Development] Bwangster12:
I was wondering the same thing. I'm assuming if it's based on 7.0 that it has the right modem compatibility?
[X Style (Pure) Android Development] Hashbang173:
Yes, you should be able to
[X Style (Pure) Android Development] Bwangster12:
Alright, I'm definitely experiencing some weird stuff. After first boot, I notice a lot of apps crashing. After I got through that, I rebooted into recovery cause I wanted to do a new clean install, and when I wiped, TWRP just vibrated and rebooted.

Now, it seems that same thing happens every time. If I go into recovery and try to wipe, it vibrates and reboots. Only formatting data fixes it. Also, after every boot I get a ton of apps crashing.

Trying to use OpenGapps Aroma.
[X Style (Pure) Android Development] xabr3:
Keep us posted :) Are you using this build? https://www.androidfilehost.com/?fid=962021903579486327
[X Style (Pure) Android Development] Bwangster12:
Yes, sorry for not clarifying. I've had to restore back to my stock backup.

Worth noting, the first time I clean installed it, I didn't even install Gapps (the file was corrupt when I went to flash it)... and still had apps crashing on boot up.
[X Style (Pure) Android Development] Fabiett83:
When i clean flashed the 20170930 build nothing crashed, it worked well for some days.

Only after restoring some games with titanium backup some apps started crashing, and that is the reason that made me restore my stock backup.

In that moment i noticed that twrp restart when restoring data, it' because data partition becomes damaged, i had to format (not wipe) to restore it.

---

Well, nothing matters anymore! i bricked my X Style!

Today i wanted to try again with F2FS data partition so i restored the original 6.0.1 MPHS24.107-58-5 firmware to advance to the official 7.0

but 7.0 OTA needs 6.0.1 MPHS24.107-58-13 so first i sideloaded the 47MB OTA to advance to 6.0.1 MPHS24.107-58-13...

Now my phone has black screen and the pc sees it as "qualcomm hs-usb qdloader 9008"

my research tell me that without the "blank flash" files it's impossible to save, so i'm out!
[X Style (Pure) Android Development] Yemble:
I'm pretty sure that CrashXXL has a service for recovering a phone bricked in this way. There is a charge, but probably not that much. Suggest you send him a PM. You'll find him on the Moto X Turbo 2 page
[X Style (Pure) Android Development] dsg29:
I had the same issue..it appeared to be triggered be wiping the dalvik/art cache...
[X Style (Pure) Android Development] Bwangster12:
After I flash the ROM? I don't think I was doing that.
[X Style (Pure) Android Development] dbolivar:
If someone in this situation successfully recovers his/her phone without a hardware repair, let me know. My XT1572 is also bricked that way, I've even started a bounty here:

https://xdaforums.com/moto-x-style/help/bounty-xt1572-blank-flash-files-t3686807

P.S.: sorry for the OT, everyone is welcome to continue this topic in my thread.
[X Style (Pure) Android Development] Hashbang173:
If you're having any TWRP issues, try this version of TWRP: https://www.androidfilehost.com/?fid=889964283620759972

As for the apps crashing, this has been a regression on my part and will be fixed soon.
[X Style (Pure) Android Development] JTaylor69:
Not sure if related, but I cleaned out cache via storage manager yesterday and continued as normal.

Phone died a few hours later due to low battery and after charging and rebooting, it was stuck on the boot animation. It kept repeating the small vibrate it does as it's close to finishing boot and was stuck like this for an hour (I gave it time incase it was cache related).

Flashed the 16th October nightly as a clean flash and that didn't work either.

Went into bootloader to find that the baseband had became unknown.

Flashed my modem and tried rebooting, but was still stuck.

I had to completely restore my TWRP backup of stock (this is why it's recommended when first flashing) which brought the phone back to life, or so I thought.

No signal, no WiFi and no IMEI which had me sweating.

Reflashed the modem again and everything started working (phew).

Flashed the 16th October nightly again and everything is working fine.

In fact, I actually no longer have poor performance that I did have, so it was worth it in the end.
[X Style (Pure) Android Development] Hashbang173:
Some of the system apps crashing should be fixed in this build: https://www.androidfilehost.com/?fid=817906626617941103
[X Style (Pure) Android Development] antariksh:
Coming from Rooted Stock 7.0

All I have to do is Flash the TWRP you provided and then flash the ROM?

Or is there anything in between? Just want to confirm because I don't wanna end up bricking the device.

P.S: It's XT1572 RETAIL ASIA
[X Style (Pure) Android Development] jordanhaughee:
Modem (Cell) Issues

Hey guys,

I'm new to custom ROMS on this phone. I flashed the newest Linage Official Clark ROM on this phone. Everything works but my Cell Service. I have tried flashing the Pure Modem, and Marshmellow Modem with the 12 update. Nothing makes cell service come on. I am in the US with Sprint. I flashed a 6.0 ROM and my cell works fine. All other connections work (wifi, bluetooth).

I can look at the cell connections and I see a bunch of APNs but it refused to connect. My baseband version is: M8992_1255331.29.01.88.02R Any ideas?

Thanks
[X Style (Pure) Android Development] fdc77:
try this:

https://xdaforums.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
[X Style (Pure) Android Development] Zzoro:
I have the same problem.
[X Style (Pure) Android Development] Zzoro:
How can I flash the update of stock LOS over this rom without wipe? I tried, but received error 7.
[X Style (Pure) Android Development] Fabiett83:
I'm glad it has worked for you, but yesterday i tried at work & at home but phone never got to start the bootloader.

Today I brought it to a care center &, since i am in the italian 24 months warrantly, Motorola should fix it.

I will update in two weeks (estimated).

When the phone comes back I will definitely make a copy of the memory in "my" loader.img, hoping I never need it!
[X Style (Pure) Android Development] Doktaphex:
Hey dude, does WhatsApp calling work with this version? I tried the one from 09/30 and everything was great aside from the crashing apps at start up and the fact that WhatsApp voice calling didn't work. Voice on both ends was really choppy, like half of every word was cut off.

Didn't actually try regular phone call maybe it had the same issue?

I may try the latest tomorrow to see if the problem still exists, in case you don't have an answer. If it does still persist, I will try to get a log to see if it presents anything useful.
[X Style (Pure) Android Development] obsolete1:
What kernel sources are you using for this build if you don't mind me asking.
[X Style (Pure) Android Development] lmulli:
Probably https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPH25.200-15 for the Kernel.
[X Style (Pure) Android Development] hoppermi:
https://github.com/HashBang173/andr...tree/cc4f6f347b94996f7cfe47ce6cce795430d670e3

This is the source he linked a while back
[X Style (Pure) Android Development] obsolete1:
Thanks must have missed it
[X Style (Pure) Android Development] Hashbang173:
I wouldn't recommend using that kernel tree, it's outdated

I've been using this branch on my GitHub lately for lineage-15.0: https://github.com/HashBang173/android_kernel_motorola_msm8992/commits/lineage-15.0-new

I've been using this branch for my new cm-14.1 builds: https://github.com/HashBang173/android_kernel_motorola_msm8992/commits/cm-14.1_new
[X Style (Pure) Android Development] obsolete1:
Thanks, I tried that kernel and I was still getting "Insert SIM" error and was unable to select that correct band from the 4636 menu. So I think I'm missing something else.
[X Style (Pure) Android Development] Alibaba0101:
Anyone having problems with the app permissions getting reset after every restart? It started around a month or so ago with the new builds. Now every time i restart the phone all of the app persmissions reset to zero. I even disabled privacy guard thinking that was the cause but it's still happening.
[X Style (Pure) Android Development] Sir2taj:
Volume comes back to mid from max level after a few seconds of music playback ; switching between front and rear camera's is slow . Kindly suggest remedies .
[X Style (Pure) Android Development] TheYoz:
Any luck with flashing with stock 7.0 to LOS without downgrading modem?
[X Style (Pure) Android Development] t895:
That's not possible, until the new modem is implemented into the ROM, you won't be able to use the 7.0 modems. And plus, it's really not much of a problem to downgrade since it doesn't have any sort of verification step in place that could stop you
[X Style (Pure) Android Development] obsolete1:
This is LOS 14.1 with the updated 7.0 modem

https://www.androidfilehost.com/?fid=962021903579486327
[X Style (Pure) Android Development] GRVsingal:
So, I can just flash it over 7.0 stock and won't face any bootloops or failed radio issues etc. Right??
[X Style (Pure) Android Development] obsolete1:
Do the usual wipe data/caches form TWRP (I format mine as well) and flash that LOS with GAPPS and you'll be good to go.
[X Style (Pure) Android Development] Hashbang173:
You seeing any advantage in that build of mine than my more recent one? https://androidfilehost.com/?fid=817906626617941103
[X Style (Pure) Android Development] obsolete1:
Nope. Did not know that there was a newer build sorry.
[X Style (Pure) Android Development] TheYoz:
Thanks guys I'm gonna test the one [MENTION=1689574]HashBang[/MENTION] just posted.
[X Style (Pure) Android Development] TheYoz:
So far so good. Game from stock 7.0 and no issues. Thanks hash.
[X Style (Pure) Android Development] tecsironman:
Yes.. Stock 7.0 was killing me...
[X Style (Pure) Android Development] tecsironman:
[MENTION=4630246]Hashbang173[/MENTION]. Having a issue while dialing out I cannot hear the person and they cannot hear me. If they call me I can hear them and they can hear me. Running your unofficial in the post above.
[X Style (Pure) Android Development] Hashbang173:
What carrier are you on? I'm thinking this could have to do with VoLTE
[X Style (Pure) Android Development] tecsironman:
Verizon. Let me test that and report back..

---------- Post added at 08:27 PM ---------- Previous post was at 08:15 PM ----------

Update.. That's exactly what it is. Good call.

Everything is smooth running except for sound. When choosing a ring tone the sound starts loud the goes soft. Otherwise great work.
[X Style (Pure) Android Development] Hashbang173:
See if VoLTE is fixed in this build: https://www.androidfilehost.com/?fid=962021903579489648

If it's not fixed, try to give me a logcat if you can

Also, for those that were having audio issues while the screen was off, see if that is fixed in this build.
[X Style (Pure) Android Development] tecsironman:
Right on. I'll let you know later tonight. This work WiFi is a crazy 4mb a sec. Thank you
[X Style (Pure) Android Development] tecsironman:
Poor androidfilehost. Busy night for them.

---------- Post added at 05:30 AM ---------- Previous post was at 04:38 AM ----------

@hashbang173. Brilliant volte works great but just letting everyone know when you enable enhanced lte reboot your phone. I had to because the device had 0 signal.
[X Style (Pure) Android Development] Kefir.net:
No SIM detected after this update, rolling back doesn't help.
[X Style (Pure) Android Development] tecsironman:
Been working fine. Only issue is when someone calls me no sound on volte but I can call them and it works.. I'll post a log in a little bit once I get a break.
[X Style (Pure) Android Development] Ueihtam:
Hey guys, i need some advise. I was on stock 7.0. Then flashed the hashbang lineage-14.1-20171102_204413-UNOFFICIAL-clark.zip and nano opengapps.

Wanted to try to flash last LOS Nightly but i'm getting a "

can't install this package on top of incompatible data

" error.

Any idea why ?

PS: Nevermind had to downgrade to stock 6.0 first
[X Style (Pure) Android Development] justmoto92:
My current Moto X Pure is still running stock 6.0 marshmallow (systemless root, TWRP and bootloader unlocked). Should I update to

stock Android 7.0 Nougat

before upgrading to LineageOS 14.1?

Thanks! :)
[X Style (Pure) Android Development] antariksh:
You can directly Flash the Official Lineage Builds on Stock 6.0.

But if want the Unofficial Lineage Builds ( built on Nougat Kernel & Modem ) then you gotta update to Stock 7.0 first.
[X Style (Pure) Android Development] tecsironman:
Anyone able to edit their apn?
[X Style (Pure) Android Development] Spencervb256:
When you're in that screen, hit the three dots, then save, after that go back into it and select your son and you should be able to edit
[X Style (Pure) Android Development] tecsironman:
No dice. I either have restore to defaults or while in that apn delete save and discard. I've tried everything and nothing is working. I can now send mms correctly but just trying to figure out my volte issue
[X Style (Pure) Android Development] Spencervb256:
Oh man, I don't know what that would be. Sorry
[X Style (Pure) Android Development] tecsironman:
Either way mms is working if you restore defaults if your on Verizon and it doesn't work.

VoLTE works when someone calls me but not the other way around.
[X Style (Pure) Android Development] Andromendous:
For some reason no matter what I flash It just gets stuck in a bootloop... tried the newset nightly and slimrom.
[X Style (Pure) Android Development] antariksh:
If you are able to boot it into Fastboot mode then try to flash 6.0 modem and then flash the official nightly.

Otherwise you can try flashing the Unofficial nightly provided by Hashbang173
[X Style (Pure) Android Development] Andromendous:
Thanks for the reply. Unfortunately, I did that, I got it to boot, but now if I reboot, sometimes I'll have service, sometimes It says no sim detected. Also sometimes it gets stuck on the bootloader screen, and the battery percentage will drop 30-50%. Is there any way to just reflash the 7.0 modem and go with Hashbangs updated version? Also I saw someone say something about it bricking the phone if I flash a factory image back to 6.0 and update to 7.0 via ota is this true? Does this mean I'm stuck this way??
[X Style (Pure) Android Development] antariksh:
You can try to downgrade to 6.0 and then OTA back to Nougat. Even if it gets Hardbricked, there's a solution to it now.

Better take this query to Q/A Section or search the one's already made.

I haven't tried flashing any ROMs after updating to Nougat so I can't say much to this.
[X Style (Pure) Android Development] t895:
It will brick the phone because during the ota going from 6.0 to 7.0 it patches the bootloader without checking for incompatibilities. I wouldn't try it because there is a lot of varied success in un-bricking. Just flash the 6.0 modems, wipe, and flash HashBang's updated version
[X Style (Pure) Android Development] Andromendous:
What about downloading the ota zip and pulling out the modem files and just flashing those? Think it would work?
[X Style (Pure) Android Development] antariksh:
We don't have Factory Images of Nougat 7.0

You can't flash Modem of OTA Zip. You can only flash the entire zip.
[X Style (Pure) Android Development] t895:
No, we have a full image as seen in the un-bricking thread.

It's only for the XT1572 retla version, but it's there

https://androidfilehost.com/?fid=961840155545596639
[X Style (Pure) Android Development] Andromendous:
Is it safe to flash that modem to my 1575?
[X Style (Pure) Android Development] antariksh:
Nope. It's XT1572 RETLA, possibly dual SIM.

XT1575 is not Dual SIM.