yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] rowlers:
Turned WiFi on, phone rebooted. Now It won'y boot past the AICP logo.

I've tried booting to recovery and clearing Dalvik/ART, this didn't work. I'm now trying a dirty flash the 7 June AICP. Anything else I can try? I really don't know what caused it!

I'm not blaming the ROM, although it has randomly rebooted lots of late, but this is the WORST phone I have had for rebooted and lockups and will be my LAST Motorola.
[X Style (Pure) Android Development] zenstonetiger:
That's a shame. I've never had issues with MotoX phones. I wonder if you got a defective unit.
[X Style (Pure) Android Development] rowlers:
Full wipe and back working again.

It is nearly 18mths old now and to be fair I ahve always managed to recover it, but I have had to "fix" it many many times!

Phew.
[X Style (Pure) Android Development] BigBadger:
OTA Update seems to be working now. last update went fine.

Gallery FC is still happening. Maybe just me?
[X Style (Pure) Android Development] redemptionx11:
I've been having a lot of heat issues on the last week or so of nightlies. Phone gets really hot watching YouTube, multitasking, or charging. Anyone else having trouble like this? Kernel adiutor said the CPU temp got up to 143F. When I saw that I tossed it in the freezer for a minute. Haha.
[X Style (Pure) Android Development] BigBadger:
Can't say that I have noticed anything like that.
[X Style (Pure) Android Development] buggerritt:
2 days ago, my phone wouldn't get cool until I turned it off. It was ridiculously hot. Don't know why. It's all good now though.
[X Style (Pure) Android Development] Tanker Bob:
I've been running the 6/14 build the last two days. The battery life has been excellent - much better than previous versions. Stability isn't an issue. The only problem that I found is that when making a call with a BT headset, the phone initially uses the headset, but quickly switches to speaker. The BT headset can be selected manually before the call dials if you're fast enough, keeping things quiet.
[X Style (Pure) Android Development] tech_infinity:
I updated from 15/6 to 16/6 and now magisk does not work at all :(
[X Style (Pure) Android Development] ms.journie:
It happened to me as well. Download and flash magisk and it will work again!

---------- Post added at 08:09 AM ---------- Previous post was at 07:29 AM ----------

This is just a merged newest magisk v13 beta with a working magisk manager apk while we wait for an official update from developer

https://xdaforums.com/attachment.php?attachmentid=4183222&stc=1&d=1497573624
[X Style (Pure) Android Development] fdc77:
from Google+ AICP

"AICP is going to build rootless builds.

This change will happen during a short period of time"
[X Style (Pure) Android Development] tech_infinity:
Here's the full post about aicp going rootless from the aicp google plus page: https://plus.google.com/115015009651694560786/posts/6maZJszPyx3

PS: it has download links to direct root solutions.
[X Style (Pure) Android Development] Tanker Bob:
Thanks for the link. Interesting. I flashed the 6/17, which is apparently not rooted, and also flashed Magisk 12.0. Magisk manager 4.3.3 was already loaded so didn't have to install it. I still got a CTS profile mismatch on SafetyNet checks, just like I did in 6/14. I'm not using any modules. However, Android Pay still seemed to work.

So, I downloaded Magisk 13.0 beta and flashed it dirty. It runs fine and now passes the SafetyNet check. Looks like I'll be sticking with 13.0.

The rootless AICP approach seems like a big step backwards to me., even given the linked explanation.
[X Style (Pure) Android Development] DonKilluminati23:
Also not thrilled with this decision. It's not the end of the world, but losing features is a pretty sour cherry on top of a sundae I didn't enjoy, particularly.
[X Style (Pure) Android Development] Sin10:
its not good ... i am not happy with AICP systemless root.

Flashed Magisk again. Now my viperfx module work again, but it lost all settings ...

i think, i will never update fast to a new nightly build.
[X Style (Pure) Android Development] whodatfan:
Anyone know what I need to do as far as Magisk is concerned to be able to log in to snapchat? Can you hide root with Magisk to log in? What I normally do with my 6p and Pixel XL is wait to flash SU until I log in to snapchat. But on this ROM with nightlies and Magisk, I'm not sure what to do. I gave my Moto X pure to my daughter who is using it with this ROM. I don't have any experience with Magisk as I have never used it. I can't do anything with SU. It kicks me out maybe because it is controlled by Magisk?
[X Style (Pure) Android Development] tech_infinity:
Don't know about how, but now this rom comes unrooted without magisk or SuperSU. So just make a clean flash with the latest nightly, install snapchat, log in and then flash root.
[X Style (Pure) Android Development] thebeardedchild:
Is there a way to make the navbar buttons closer together in this ROM? I'm coming from Lineage, where I was able to do that, but I can't seem to find any comparable settings here in AICP. With the robust navbar options I'd think it'd be there somewhere....
[X Style (Pure) Android Development] BigBadger:
June 19 nightly seems really stable

Not sure it it just took the flashing of many nightlies to squeeze out the gremlins or if the June 19th build is simply full of goodness. My phone has been very smooth and I have not had to restart at all.
[X Style (Pure) Android Development] ShadyUnicorn:
Changing the DPI is all I can think of. I'll update if I find a setting for it.
[X Style (Pure) Android Development] ShadyUnicorn:
microphones not working on latest build for me (also tried the build on the 17th and had the same problem), anyone got a fix, because this seems to be the only problem.
[X Style (Pure) Android Development] BigBadger:
By 'microphones' do you mean something plugged into the 3.5mm socket? The phone's microphone is working for me in all builds. (calls, audio recorder, 'Okay Google', etc.)
[X Style (Pure) Android Development] ShadyUnicorn:
No? Phone calls don't work. On crdroid at the moment, and getting the exact same thing again. :eek:
[X Style (Pure) Android Development] mominn8266:
Probably a "duhhh" advice, but does the phone app have the permissions enabled to access the microphone?

Other than that it seems like a hardware issue if multiple roms are giving the same issue. Last resort, I would go completely stock and see if that fixes it.
[X Style (Pure) Android Development] ShadyUnicorn:
Phone app has the permission, may try stock, thanks.
[X Style (Pure) Android Development] BigBadger:
Hmm. Might be something you are doing. I do dirty flash of nightly with the temp magisk fix tacked on. Followed by cache wipe. No microphone problems.
[X Style (Pure) Android Development] mominn8266:
What is this temp magisk fix? Thanks
[X Style (Pure) Android Development] Henryy97:
Which rooting method (that is not systemless) do you guys use for the latest nightlies? :)
[X Style (Pure) Android Development] HatchetJackk:
I'm running the 6/09 build with great results. Is there any reason to upgrade to the latest nightly or is it just minor fixes?
[X Style (Pure) Android Development] Tanker Bob:
Check out this link. They have a number of fixes and workarounds for different issues and devices until the developer finishes his exams. Use at your own risk!
[X Style (Pure) Android Development] Zzoro:
Ambient display (hand wave) works time to time. Is there any fix?
[X Style (Pure) Android Development] nima2011a:
tnx for your job man... I have a Problem!! my device is moto x style dual sim XT1572, I installed this rom but none of my sim cards was not detected!!!! plz someone help me to solve this issue :(
[X Style (Pure) Android Development] Tanker Bob:
The 6/25 build did not recognize my AT&T SIM. I reverted to 6/24 and all is well. Battery life on 6/24 is pretty good as well. Looks like someone goofed today!
[X Style (Pure) Android Development] nima2011a:
isn't there anybody to help me??????
[X Style (Pure) Android Development] ms.journie:
I have no problems here.
[X Style (Pure) Android Development] Tanker Bob:
Interesting. Thanks for letting me know. Well, it's late here. I'll try 6/26 when it comes out tomorrow and see how that goes.

---------- Post added at 10:24 PM ---------- Previous post was at 10:17 PM ----------

I don't have your specific model phone, but I'd recommend making sure that your modem baseband driver and bootloader are up to date. There are dedicated threads on xda-developers with drivers, bootloaders, and instructions.
[X Style (Pure) Android Development] GchildT:
Same thing happened to me. Downgrading didn't bring my sim back and I don't have an EFS backup. I'm hosed! May have to go to stock. Flashing stock modem didn't work for me either.
[X Style (Pure) Android Development] nhizzat:
So quick unlock isn't an option for this ROM, is it possible to enable it short of making a new build?
[X Style (Pure) Android Development] kellerman40:
The HSPA seems to be very slow on 6/24 nightly. Doesnt seem to switch to HSPA+ and the speeds are slow. LTE seems okey tho.
[X Style (Pure) Android Development] Tanker Bob:
LTE seems fine here on 6/24. Since that's the last version that recognized my SIM, I have several days' experience with it now.

---------- Post added at 03:45 PM ---------- Previous post was at 03:43 PM ----------

Wow, sorry to hear that. This is probably a dumb question, but did you erase the cache and davlik cache when you downgraded? I always do that on downgrades and it has worked so far for me. Before downgrading to stock, you might also try a factory reset on 6/24 and see if your SIM comes back.
[X Style (Pure) Android Development] GchildT:
Yes I always do that as well. I had to flash stock, which only take a few minutes. Then restore my 06/23 backup. Flash most current modem again, then backup the EFS part after i made sure that mobile data was working. Back to normal again.
[X Style (Pure) Android Development] Tanker Bob:
Excellent!
[X Style (Pure) Android Development] kellerman40:
Why would you reflash the modem? Does the rom mess with the modem partition?
[X Style (Pure) Android Development] tech_infinity:
Seems like the problem where torch wouldn't work after a reboot until you press the edit icon is gone :)

Yay :D

Thanks [MENTION=4630246]Hashbang173[/MENTION]
[X Style (Pure) Android Development] GchildT:
I had to reflash the Modem because my EFS partition somehow became corrupt. Flashing stock downgraded back to the orignal marshmallow modem. That got my data back, but when I restored my backup I lost data again, but regained it after flashing the most current modem/baseband. I'm not sure it was all necessary but that's how i got it to work.
[X Style (Pure) Android Development] redemptionx11:
Damn. I bet that was stressful. I freaked out when I lost my data cause I lost all my dog's pics and my memes!
[X Style (Pure) Android Development] GchildT:
It wasn't too bad. It's good to have a recent backup. I probably backup once a month. That's good enough for me. And periodically backup your /sdcard part. I didn't lose anything but time. :good:
[X Style (Pure) Android Development] kellerman40:
Seems still to be glitchy, even after a clean flash.
[X Style (Pure) Android Development] Tanker Bob:
The 6/28 build recognizes my SIM again. Everything seems to be working.
[X Style (Pure) Android Development] redemptionx11:
As it turned out, I didn't lose as much as I thought thanks to google automatically backing up some stuff. :)
[X Style (Pure) Android Development] GchildT:
Awesome!
[X Style (Pure) Android Development] faris:
Seems they just released the official 7.0 update. Will this help fixing the unusable speakerphone for calls?
[X Style (Pure) Android Development] kellerman40:
yayy!! these are definately great news!:good: this should help a lot for the devs.
[X Style (Pure) Android Development] Hemidrosis:
Once the kernel source is released, issues will be fixed.
[X Style (Pure) Android Development] Tanker Bob:
7/1 build doesn't find my SIM again. Reverting back to 6/29.

---------- Post added at 10:14 AM ---------- Previous post was at 09:16 AM ----------

Going back to 6/29 didn't recover my SIM recognition, so I downloaded 6/30 and tried again. That worked! I now have my SIM back on 6/30. This SIM recognition issue seems to be recurring. More frequent backups seem warranted at this point.
[X Style (Pure) Android Development] videogmike:
Anything I try after 6/26 doesn't seem to find SIM
[X Style (Pure) Android Development] fliperpl:
for me it is working fine i am on 07/03 build, one of the greatest rom i have been using so far
[X Style (Pure) Android Development] tech_infinity:
Sim detection works fine here. Did you check whether sim works after a reboot.
[X Style (Pure) Android Development] videogmike:
Hadn't tried 7/3 yet. Just did and did another reboot. No go.
[X Style (Pure) Android Development] GchildT:
Same here... What gives!?
[X Style (Pure) Android Development] Tanker Bob:
I hadn't gotten a build to recognize my SIM since 6/30, even with restarting after flashing. I noticed today that 7/4 failed to finish its installation script. So, I used TWRP to reinstall 7/4 over itself, then flashed Magisk separately. I did not clear cache or Dalvik cache after reflashing. That worked! I am now running the 7/4 build with working SIM and root. The whole process took a bit of time, but everything appears to be working.
[X Style (Pure) Android Development] kellerman40:
Seems that after upgrading to the new stock 7.0 partition table, bootloader and everyting else, no LOS based rom works at all. Just bootloops.

Stock 7.0 works good tho.
[X Style (Pure) Android Development] Tanker Bob:
Where did you get the stock 7.0? It sounds like something is locked down. Can you get TWRP to work on it?
[X Style (Pure) Android Development] GchildT:
Did the install script finish the second time? What did you do to install through TWRP if it kept failing?
[X Style (Pure) Android Development] Tanker Bob:
Yes, it finished the second time. The first time, I used the AICP updater, adding the most recent Magisk 13.0 beta zip before telling it to install. The script did not show the unpacking modem line or the finish with Result 1 line. The script went directly to the Magisk installation which seemed to finish normally.

The second time, I rebooted into TWRP, then selected the 7/4 built to install. That time, the script finished with the usual unpacking modem line and Result 1 finish. I restarted w/o wiping cache and Dalvik cache. The Moto booted fine and the SIM worked. I then rebooted back to TWRP and installed the Magisk 13.0 beta zip, then restarted without wiping.

Does that answer your question completely?
[X Style (Pure) Android Development] GchildT:
Thanks! Nope still doesn't work for me. Everything works but still no SIM. Restoring backup.
[X Style (Pure) Android Development] kellerman40:
https://xdaforums.com/moto-x-style/general/ota-moto-x-style-android-7-0-nougat-t3630248

Latest TWRP works just fine, tried AICP and DU, both bootlooped.

Flashed Stock 6.0.1 EU, the 7.0 update didnt show up yet, so I flashed it via stock recovery.
[X Style (Pure) Android Development] Tanker Bob:
Thank you for the link. I see that you are on the EU version. I'm on the US version. I'd like to have official release for XT1575 for grins, but have no plans to leave AICP. I really like this ROM a lot.

Odd that TWRP works but that the ROM boot-loops. Sounds like a bootloader issue, but I could be way off. I'm sure that the devs will figure it out.
[X Style (Pure) Android Development] Mvsmota:
Same problem here, doesn't matter the rom, every single one of them is bootlooping for me( at least the 7.x ones). Luckily I managed to make a RR 6.0 to work
[X Style (Pure) Android Development] kellerman40:
Ir restored 7.0 backup, you can also flash 7.0 system partitions over fastboot
[X Style (Pure) Android Development] Ijspegel:
Format data? Tried An Aosp based ROM?
[X Style (Pure) Android Development] Mvsmota:
I formatted data before installing new roms(did a full wipe), I tried even changing the data type from f2fs to ext4 to see if it works, but still bootloops. And I did try an AOSP one. All the ones I tried: AICP 12.1, CosmicOS 2.0, RR 5.8.2, LineageOS 14.1, Vallidus 14.2, 14 and 13.9

Still no one works, some of them even got to finish the boot, showed me the battery and the clock but restarted again(Vallidus and RR)

I did install a stock 6.0 before installing a 6.0 rom one, so I even tried again to install a 7.x one but no luck
[X Style (Pure) Android Development] fdc77:
+1

i can confirm, maybe the problem is caused by the new GPT partition table flashed by nougat OTA.
[X Style (Pure) Android Development] Tanker Bob:
I just flashed the 7/6 build over 7/4 and everything seems to work fine, including the SIM. All scripts completed normally. Magisk 13.0 beta initially didn't pass the safety check, but turning off Magisk Hide and turning it back on again fixed that. Happy days are here again!
[X Style (Pure) Android Development] lknnnn:
0707 build still can't recognize SIM.I tried everything I know,finally back to 0620 backup.
[X Style (Pure) Android Development] videogmike:
Do we think hashbang still monitors this thread or has anyone posted in the g+ group yet? Usually this kind of thing only hangs around for 1 nightly since I've been using AICP for the last few months.
[X Style (Pure) Android Development] rsmiff:
Yes the speaker LED works, white only and always on. It does not blink and goes off once the notification is cleared. The settings are under Sound & Notifications, Notification Light. It also works for charging but then it's like a night light. I turn that off.
[X Style (Pure) Android Development] deathwater:
Nm.

Performed the update. stuck on AICP is upgrading... Finishing boot.

Had to press power button to clear the screen. :good:

Flashed because im having the issue where if I hit a zero cell area, I get thrown into roaming and never come out. Had to soft reboot to get service restored.

AT&T

Also, not able to pair Moto 360 gen 1. Pairs once and never again.
[X Style (Pure) Android Development] patt2k:
you have to factory reset 360 everytime you have new rom / switch device etc.
[X Style (Pure) Android Development] deathwater:
Sorry, I did factory reset it. It pairs, starts loading the software and drops connection. Phone and watch are right next to each other every time. Tried factory resetting watch several times, uninstalling and reinstalling Moto connect, all same issue. Watch will not stay paired with the phone.
[X Style (Pure) Android Development] patt2k:
Weird as I did not have those issues with my 360. But I barely use it tho.
[X Style (Pure) Android Development] deathwater:
I'll try to test with my Fitbit and Razer fitness trackers.
[X Style (Pure) Android Development] joshw0000:
I'm using a G Watch R without any issues. I had to manually add it to the list of Smart Lock Trusted Agents. Usually it prompts me when I sync it to a new rom/phone.
[X Style (Pure) Android Development] erikjonpeterson:
I'm using the Huawei watch, no issues.
[X Style (Pure) Android Development] deathwater:
I tried to add it to the trusted list but it disconnected before I had a chance to complete it.

---------- Post added at 04:39 AM ---------- Previous post was at 04:39 AM ----------

Damn. I'll try again tonight with the updated rom. Thank you everyone.
[X Style (Pure) Android Development] zige:
Where to find build 10/31 which people are talking to have great battery? I'm using 11/01 and it has major battrry drain... Older which i found is 10/26.
[X Style (Pure) Android Development] rsmiff:
I've been running this 10/30 build, on Verizon. Has been my daily since.
[X Style (Pure) Android Development] bartjeh1991:
Tried flashing latest build on XT1572. ROM is blazing fast, and seems no issue's so far. Will report some testing results.
[X Style (Pure) Android Development] daniel.1983:
I also wanted to install this ROM on my XT1572, but some of the users spoke about heat issues and other stuff with the style variant. I'm looking forward to your feedback ;)
[X Style (Pure) Android Development] Philomene:
Hello

installed the last nighlty on my XT1572. No problem until now. All seems ok
[X Style (Pure) Android Development] joshw0000:
So far she's running pretty smooth on Verizon. I've finally got it set up to my liking so I can't say anything for battery yet except it's clearly not worse than the stock rom's battery.

The only thing this phone is missing is double tap to wake. Anybody cooking a kernel with that mod?
[X Style (Pure) Android Development] patt2k:
Hey hashbang just wondering about any potential fix to signal in status bar? Shoes slightly less. Look at my widget and status.
[X Style (Pure) Android Development] sbcrumb:
Glad someone else noticed this. I was going to flash back to stock to see if it was just my imagination. What is that widget you are using to give you the real signal level?
[X Style (Pure) Android Development] patt2k:
Yes sir look now. The bars been like that since the first build I think.
[X Style (Pure) Android Development] sbcrumb:
[MENTION=1659045]patt2k[/MENTION] What wiget is that?
[X Style (Pure) Android Development] patt2k:
Network signal info I think Pro either pro or without pro. You can find it in playstore:)
[X Style (Pure) Android Development] TalionDread:
Does anyone else have issues using the Amazon Alexa App with all of these nougat releases? The only one it seems to work on is the 1572 nougat EU firmware that was posted. When I try to open it it'll ask for login credentials then force close after it loads. I've tried all the usual crap and it happens right after a clean install as well. I don't have any issues on Marshmallow with it.
[X Style (Pure) Android Development] redemptionx11:
I'm having trouble with the Alexa app too. Dunno if it's ROM related though.
[X Style (Pure) Android Development] smootdawg:
My Alexa app does the exact same thing you mentioned. I've had to go find an older version (pre-2.0) and sideload it in order for it to work. I'd love to hear if anyone can use the latest builds of the Alexa app with this ROM.
[X Style (Pure) Android Development] Zzoro:
Ambient display doesn't work, Audio FX doesn't work. On the latest build I've got a sim card error.
[X Style (Pure) Android Development] redemptionx11:
Damn. I tried grabbing an old version but couldn't get it to work either.
[X Style (Pure) Android Development] k3mik4l:
Why with every nougat rom I try to flash I get a bootloop? I'm on stock marshmallow rooted with TWRP. I've tried aicp, du, and a few more . Any help would be appreciated. I'm using a moto x pure.
[X Style (Pure) Android Development] kellerman40:
So can we do something about the roms bootlooping on official nougat firmware?
[X Style (Pure) Android Development] tech_infinity:
Most probably Hashbang is already looking into it, It'll probably take some time. He reads the forums regularly so he's probably aware of this issue.
[X Style (Pure) Android Development] malkuu:
i am having brasil edition Retla Dual sim x style these roms does not detect my sim cards which rom could i flash on this varient some one help me plz
[X Style (Pure) Android Development] GchildT:
I've posted about out SIM issues from the latest builds in the G+ group. Hopefully we get a response.
[X Style (Pure) Android Development] malkuu:
can u give me the link of group
[X Style (Pure) Android Development] GchildT:
https://goo.gl/HpgLmU
[X Style (Pure) Android Development] Hashbang173:
For those who are having sim issues on recent builds, can you give me the output of getprop? You can do this with adb

adb shell getprop
[X Style (Pure) Android Development] buggerritt:
I was having sim problems with builds after July 9th until I did a clean flash yesterday. I'd been dirty flashing every day for over a month. I was actually noticing several problems for a while, like the phone getting really hot and freezing with very little running. Clean flash does wonders.