yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] pizzlewizzle:
yeah everything's been running great. haven't even really had many force closings. The headphone jack isnt working but if you pretend you have the new iPhone all is good. Bluetooth headphones/speakers are working great.
[X Style (Pure) Android Development] games906:
Ohhhhh okay thanks! I guess I'll wait until there are less bugs.
[X Style (Pure) Android Development] thebobinator:
So the front post says something about flashing the modem if upgrading? Is that something I need to do if going from current stock to a clean flash of this still? (I keep getting com.phone crashes and it wont recognize the SD card...)
[X Style (Pure) Android Development] capeorigins:
Dude good point lmfao
[X Style (Pure) Android Development] Doktaphex:
Headphone jack works perfectly for me on 11/03 build.

In aroma I told it to remove audiofx. Don't even know if it is actually in the build or not, but maybe that is why my headphones work.
[X Style (Pure) Android Development] Curlyfry2121:
Yes that made mine work too a while ago
[X Style (Pure) Android Development] Ltilt2:
Headphone has always worked. What doesn't work is Aux cable
[X Style (Pure) Android Development] guest592:
My sim still isn't working. Any solution yet?
[X Style (Pure) Android Development] StephenMilone:
So I flashed from the last 6.0 to 7.1 11/3 and got the phone crash problem. Then flashed the boot image provided by dgadelha and now i notice the sim connect, but then it drops and the crash starts again.

Flashed with nano gapps.

Any insight?
[X Style (Pure) Android Development] Ltilt2:
I had the same problem with Phone app crashing so what I did was do a clean install of the 11/04 rom and gapps. Everything is working great now with no Force closure issues.
[X Style (Pure) Android Development] Spirotot:
11/4 com.android.phone crash fix!

I tried that boot.img from a couple pages back, as well as manually wiping /system and re-installing AICP + openGAPPS (aroma). No luck fixing the com.android.phone crash that started happening with 11/4.

BUT. Then I deleted all the files in `/data/user_de/0/com.android.providers.telephony/databases/`. Rebooted, com.android.phone crashed a few times, but then stabilized, and I now have signal/data again. :)

EDIT: I should add, I'm pretty sure deleting those files will delete your SMS/MMS if you have any. I did not have any SMS/MMS to start with, so I didn't notice the difference.
[X Style (Pure) Android Development] lmulli:
This worked a treat on my install. Sim now detected and data back. No issues with com.android.phone crashing at all.

Thanks!
[X Style (Pure) Android Development] marekca:
After clean install 11.3, I got death of screen, long hold power button for force reboot was working.
[X Style (Pure) Android Development] kcipopnevets:
Odd question outta the blue but do the Nougat builds carry kexec support?
[X Style (Pure) Android Development] DrunkUncas:
In almost a decade of doing this, I can't recall an instance where a nightly update managed to break things so thoroughly.

The only thing the next update could possibly do to top this is to cause my phone to spontaneously combust.
[X Style (Pure) Android Development] lmulli:
I never back my devices up and seldom have any issues, and in fairness, the only issues with the 04/11 build were the no sim error and com.android.phone crashing, both of which are easily fixed as per the instructions given a few posts above this one.
[X Style (Pure) Android Development] ccic2491:
I've had a couple times on other devices where something like this happened. The first time I didn't have a backup so now I try to have one every time. I'd rather spend the extra couple of minutes letting TWRP do a backup so I don't have to spend hours trying to fix whatever's messed up or start from scratch.
[X Style (Pure) Android Development] jason2678:
Sorry. I'm afraid that is a proprietary Samsung feature.
[X Style (Pure) Android Development] caspersfi:
Delete
[X Style (Pure) Android Development] iwaskylester101:
Only complaints right now on the 11/04 build is the android.phone thing crashing and choppy audio recording video in snapchat. But snapchat for android is already the worst optimized app ever so that might just be them. Great work! :)
[X Style (Pure) Android Development] hometech99:
Didnt work..deleted twice even. Many reboots. Disabled Phone and had a different dialer. It pops up constantly. Ive already been back to stock, fastboot flashing boot.img, recovery, system,, etc
[X Style (Pure) Android Development] iwaskylester101:
Did you try actually factory wiping the phone in TWRP and re-installing the rom after deleting those? That worked for me.
[X Style (Pure) Android Development] hometech99:
I just Twrp wiped, and went back to 11-3 . It still had the error, but eventually stopped by disabling stock dialer.
[X Style (Pure) Android Development] iwaskylester101:
I also have some random reboots sometimes too
[X Style (Pure) Android Development] pinecone:
This ROM has a ton of potential. I had to revert back to cm13 because every thing was getting choppy even after a reboot. I'll be back on this soon though
[X Style (Pure) Android Development] buggerritt:
How did you get snapchat to work on a rooted device?

sent via Moto X Pure

over AT&T's crappy network
[X Style (Pure) Android Development] iwaskylester101:
I just installed and logged in. Snapchat has always worked for me on rooted devices but not with Xposed.
[X Style (Pure) Android Development] barakisbrown:
So what is difference between the phone app that is installed by default an the one you can get from the play store? I get the errors from app on the build even with a clean install but if I remove it and add the one from the play store, I am not getting any kinds of forcecloses.
[X Style (Pure) Android Development] Ken C:
I was getting the .Phone errors, on the 11/4 build, even trying to go to it from a backup. Did the clean install with the aroma method, it still crashes a couple times but usually stabilizes itself. At most I've done the second reboot and have the data connect. Haven't tried the video stuff myself but the phone seems to be working fine so far

Edit: for what is worth I was able to get the viper/arise zip work
[X Style (Pure) Android Development] guest592:
Looks like 06 has fixes for telephony stuff and SMS, maybe that solves the phone has stopped bug. Upgrading now. I followed the above instructions and it solved the missing sim issue but still have crashes at boot until muted.

---------- Post added at 01:54 PM ---------- Previous post was at 01:52 PM ----------

Also had a weird issue where all keyboards but voice input disappeared, couldn't type anything until I installed swift from apk. Still can't get google keyboard working again (error code 505 when installing from play store).
[X Style (Pure) Android Development] guest592:
10/06 stops the crashing bug as far as I see.

I noticed that Titanium backup crashes a couple of times upon opening, but if you keep on opening it eventually it loads. Anyone else have this?

Also, any way to reinstall AOSP keyboard if removed by gapps?
[X Style (Pure) Android Development] chris_dis:
How did you get arise to work? It's not processing for me.
[X Style (Pure) Android Development] hometech99:
Noâ?¦ it doesn't stop the phone bug. In fact , in addition to the popups, I get a white box that says select SIM card, and there is nothing on it to press. Doing the database deletion technique, a couple of restarts, wiping Cashes in t wrp, a couple of more restart, and finally it seems to be stopping. I am not on a dual sim phone.
[X Style (Pure) Android Development] buggerritt:
Do you have supersu installed?

sent via Moto X Pure

over AT&T's crappy network
[X Style (Pure) Android Development] rjyoung00:
Yes, I've noticed this with Titanium Backup as well.
[X Style (Pure) Android Development] iwaskylester101:
No
[X Style (Pure) Android Development] Ken C:
Bizarre as it sounds I just flashed like normal. I can't remember if it needed the drivers or not, but it didn't ask to install them. Thought it was odd but it's processing. Under my phone settings it has selinux set to permissive, I didn't change it myself. It was just a shot in the dark and it worked.
[X Style (Pure) Android Development] guest592:
Google voice keeps on crashing. Anyone got it to work?
[X Style (Pure) Android Development] Curlyfry2121:
Snapchat works fine just install the ROM and install Snapchat and login. Works for me.
[X Style (Pure) Android Development] caspersfi:
Yeah Snapchat works with Xposed. You just have to log in to Snapchat before activating Xposed.
[X Style (Pure) Android Development] Curlyfry2121:
True. But for Android N some Roms won't work with Snapchat because of the flags Google left in the ROM. The flags would tell Snapchat the device is rooted and it wouldn't work. But luckily this ROM works for it.
[X Style (Pure) Android Development] s3rgioru3las:
Latest build still has the no sim issue. Titanium Backup doesn't seem to be stable for android 7.1, at least, thats what other people are reporting on the playstore. And yes before you install any rom or activating xposed, log into snapchat and do a backup of snapchat's data. Otherwise, you may never be able to log in.

Edit: I stand corrected, doing a clean install, 11/06 seems to have fixed the no sim issue.
[X Style (Pure) Android Development] Prazaar:
First boot with 11/06 work fine.

after rebooting phone crash again.
[X Style (Pure) Android Development] Ken C:
I got it to work. Still on 11/04 build. Didn't do anything special just went through the setup process. After I got to where you switch voicemail providers to GV the .phone crash started happening. I rebooted watched and prayed. Got the .phone crash a bunch of times before it stabilized.

I am getting a good amount of battery drain atm not sure if it's a setting of some sort.

I do have the weird display issue I had before going to 7.1 still, was kinda hoping something in the build would fix it. Unless y'all got any ideas, I've not come across a fix for that yet.

But I must say for me, it's not running that bad. Granted I'm not up to date on the builds. Been getting calls and texts like I should data is working fine. I've had a couple reboots but I think the device was choking on the inputs I was doing at the time. I'm on straight talk for what it's worth.

Edit : can confirm about TB starting deal haven't restored anything at this point but after it finally launched I got this
[X Style (Pure) Android Development] bmt10:
11/06 I think you mean? The same for me but only after a few reboots and several cache clears it was still crashing on first boot.

Also the same for Titanium Backup.
[X Style (Pure) Android Development] buggerritt:
That's probably why i can't get it to work.

sent via Moto X Pure

over AT&T's crappy network
[X Style (Pure) Android Development] iwaskylester101:
Ah yeah. Just flashed another ROM with SuperSu and tried to get snapchat to work and it wouldnt log in. I guess they detect it with SuperSu. It's quite annoying tbh
[X Style (Pure) Android Development] capeorigins:
I concur that on the 6th build, there is still no data. I'm glad I backed up haha
[X Style (Pure) Android Development] deejayburnout:
Just about to flash 06. Let's see how I get on. Getting a lot of crashes on it.
[X Style (Pure) Android Development] josdehaes:
Phone worked for a while on 6/11 nightly, but still not stable, lost connection after some time and the crashes reappeared. Restored MM.
[X Style (Pure) Android Development] NightBladeDK:
You with sprint or verizon?
[X Style (Pure) Android Development] iwaskylester101:
Sim card/phone issues on 11/6 still .
[X Style (Pure) Android Development] capeorigins:
T-Mobile actually
[X Style (Pure) Android Development] kitaco:
11/6 is fine for me. I had a hard lockup earlier and the screen wouldn't come on. Video doesn't work. Music is still laggy especially when I have Twitter open with SoundCloud in the background. Google Phone from the play store crashes with the phone permission.
[X Style (Pure) Android Development] MobileThrowAwayAcc:
Is anyone still having issues with Google photos and other apps being able to see pictures on the device?
[X Style (Pure) Android Development] kitaco:
I had to wipe EVERYTHING and do a FULL clean flash before I could save images.
[X Style (Pure) Android Development] Ken C:
Been using Google photos for a couple versions of the rom. Saw the warning about the gallery crashing the device so I installed a couple other galleries and never had the problem. Never opened the original gallery tbh. And the pic I posted earlier in the thread came from there and uploaded to tapa fine
[X Style (Pure) Android Development] rbraswell8:
I had been running the 11/2 build mostly because I only update once a week. it was running fine minus the video problems and it taking a while to see the sim card, then this morning on my ride into work, I get 12 reboots in a row, followed by com.android.phone error and the screen locking up several times in a row. currently doing a complete wipe and clean flash, and will delete the telephony files to see if it fixes.

clean flash of 11/6 worked!
[X Style (Pure) Android Development] MobileThrowAwayAcc:
Did it also upload to Google photos without issue?
[X Style (Pure) Android Development] jokenkil:
I don't see how you guys are getting the 12.1 builds to work. I have tried everything mentioned in the forum. I can't get the phone crashes to stop can't get the simple to be detected. I have been using the last 12 build with no issues after install new gallery app.
[X Style (Pure) Android Development] volldez:
X2
[X Style (Pure) Android Development] Digital DJ:
Hey guys, I'm just coming back to flashing/rooting/ etc.. and I'm wondering if this is a Android 7.1 based rom? It looks like it in the title, but the posted image in OP shows 5.1. Sorry for the noob question. I've just been out of the rotting game for awhile.
[X Style (Pure) Android Development] strafer69:
It is a 7.1 based ROM. Unfortunately since I'm on Verizon the volte does not work. The lack of simultaneous voice and data is a deal breaker for me. Otherwise it's an excellent ROM!
[X Style (Pure) Android Development] Digital DJ:
Ok cool, I don't care much for the data/call thing so I think I'll give it a run.
[X Style (Pure) Android Development] Ken C:
Yes it did.

But since then I started noticing apps not doing certain things here and there, then this morning it just started bootlooping continuously so I just flashed my copy of the 11/6 build. Clean flash, did the aroma install deal just in case. I got the phone crash a couple times on initial start up but it connected faster this time without a second reboot or going bonkers for 5 minutes. We'll see what happens. Just updated and seems to be running ok, but haven't done anything with it
[X Style (Pure) Android Development] rbraswell8:
anybody else having issues with android wear with the 11/6 update? I downloaded it after a clean flash and I get "This phone has been flashed with an unsupported configuration for companion. you must re-flash it as either signed/user or unsigned/userdebug."
[X Style (Pure) Android Development] rjyoung00:
Is long press on the navbar working for anyone? Just did a clean install of 11/06 and set up the navbar with long press back as force close app but it not working. Long press on home button seems to work, just not the "force close app" action.
[X Style (Pure) Android Development] StephenMilone:
It's the Android wear update. Happening in the MM build too
[X Style (Pure) Android Development] rbraswell8:
So no more smartwatch with a modded phone? That's awfully rude and shortsighted of them.
[X Style (Pure) Android Development] datchico305:
It's working for me on latest build
[X Style (Pure) Android Development] rbraswell8:
my bad, reboot fixed it.
[X Style (Pure) Android Development] hometech99:
com.phone.android has stopped.

I tried deleting databases, clean flashing 11-2 and dirty forward no go, clean flash 11-6, etc.

Keep getting that pop up and closing it hundreds of times, rebooting, etc...cant get rid of it.

---------- Post added at 07:49 AM ---------- Previous post was at 07:46 AM ----------

X3
[X Style (Pure) Android Development] DrunkUncas:
Voice stopped working for me months ago on TruPure, and hasn't made a comeback on 7 or 7.1.

No crashes, however.
[X Style (Pure) Android Development] Ken C:
I got 11/06 running for me after my last post where I was getting a boot loop on 11/04. Got what I had for apps working. Google voice, viper, AdAway, and TB seems to be working, haven't restored data with it yet. Each time I'd install one of these apps I'd get the phone crash issue but it either sorts itself out, or a second boot usually does the trick. Taking my time adding apps back in case it starts acting up.

On another note, has anybody noticed the backups having differing amounts of files in them? I'll have one with 10 then one with 7 etc. Probably why my backups weren't restoring correctly
[X Style (Pure) Android Development] rjyoung00:
Has anyone noticed the mic doesn't seem to be working for any app other than phone?

Clean install of 11/06 had the same thing on 11/03 as well.
[X Style (Pure) Android Development] valq:
Lol, why is it both cm13 and aicp are perma-borked.

Both are entirely unusable as a daily driver & I wouldn't even know what version to go with anymore.

I'm running 8-31 cm just because I have a backup but idk where to even find newer versions that aren't completely messed up.

It seems to me for both of these CM based OS's, development has run them into the dirt.

So much for the future of this device's development.
[X Style (Pure) Android Development] iwaskylester101:
Exactly. CM13 runs like complete trash now
[X Style (Pure) Android Development] pizzlewizzle:
Wow give it some time. There have only been 7 builds since this ROM was rebased to Android 7.1... If you don't like it go back to stock. These things take time and DEVs have been putting massive amounts of time to get this running for us. Official nightlies haven't even started for CM 14.1!
[X Style (Pure) Android Development] iwaskylester101:
I mean I completely understand I'm just stating. Also talking about CM13 not 14
[X Style (Pure) Android Development] Doktaphex:
Take your ungrateful, unhelpful comments back where you came from. Go and develop your own version of Android 7.1 and get it running as smoothly as this ROM is running right now without even having updated Motorola proprietary blobs.

You are entitled to have an opinion, but right now, it's wrong!
[X Style (Pure) Android Development] alero5752:
I agree with you. I keep on reverting back to CM13, which itself has been buggy lately, yet not as badly as CM14 or AICP7.1. I just want a stable custom ROM that gives me features that Stock does not. I'm so tired of re-flashing to something else over and over again.

What irritates me the most is that the bugs kick in when I need the phone most. They never occur when I'm at home doing nothing. Grrrr...
[X Style (Pure) Android Development] iwaskylester101:
Exactly. But these ROMS are definitely a privilege so not complaining at all I just wanted to state this so maybe the devs could look into it
[X Style (Pure) Android Development] pizzlewizzle:
Go back to stock until 14.1 is up to your standards as a DD. Development has stopped on CM13. Devs are aware of the bugs and trying to fix them ASAP
[X Style (Pure) Android Development] iwaskylester101:
Smart idea tbh. Thanks man
[X Style (Pure) Android Development] valq:
Just so we're clear, AICP WAS cm13 based and before it went to V7 is when cm13 started to get "over developed".

So, AICP & CM13 had the same bugs for a bit.

When it got to the point where cm13 was being continually overdeveloped, CM14 came into existence AICP went to 7, then 7.1.

Neither of these builds have been stable since late September.

I'm not hating or being ungrateful.

Just kinda making a note of the only CM/based builds we have are super duper broken.

-Cm13 from being overdeveloped and dropped once an outcropping of bugs got worse. (And AICP 6.1)

-Cm14 (and AICP 7.1) are new builds with new problems, I agree.

But, it just kinda annoying to have an old version broken and abandoned, only to have a new, just as equally broken (from being new) build come into existence.
[X Style (Pure) Android Development] caspersfi:
So much I'd like to say here but for an old timer like myself it's "been here done that".

So I'll just tell ya. This is a Development thread/forum/ROM. Yep, you flash this and their is a good chance their will be bugs.

If you don't want bugs, please go back to stock.
[X Style (Pure) Android Development] valq:
I agree entirely. I have bugs on the build I'm running now. Useable tho.

I've been flashing firmware since BlackBerry was more relevant than the IPhone.

Its never good form to continually develop a build, ignore the bugs, develop more, add more bugs, see there are bugs.....

And then ditch it.

Idk.

It just doesn't sit right.

Right when things got bad with CM13/AICP 6.1, the changelogs didn't seem to address any of the new reported bugs for like 2 weeks before it was dropped.

Added features. But no bug addressing. Overdeveloping.

All that being said. I'm really looking forward to AICP 7.1 and think they're doing a bang-up job at ironing out everything
[X Style (Pure) Android Development] 12paq:
You're missing a few very basic and important things.

The developers of all theses builds completely volunteer all their time and effort. They owe no one for anything. The quality of their builds and the amount of bugs is irrelevant to you the user. You're not entitled to any level of quality whatsoever. If you don't like it, move along quietly or better yet learn to build yourself.

This is a developer forum. Even my above comments do not belong here. Please take this to the "general" section if you wish. And please remember, these developers owe you nothing. Not quality, not timely updates, not bug squashing. They simply owe you nothing.
[X Style (Pure) Android Development] iwaskylester101:
That's the one thing that amazes me about all of these ROMS. Someone makes these amazing OSs on their free time and thousands of people use them.
[X Style (Pure) Android Development] NOSTALGIA:
everyone, we should be on topic.. .. keep your non rom related questions away from this thread
[X Style (Pure) Android Development] hometech99:
Im on 11-4 build currently stable.

I had 11-3, dirty flashed to 11-4.

When I had the crashing com phone, I went to the phone app and disabled it. That didnt stop the popups. I then went to a file manager, and deleted the database files in com provider telephony (multi selected them and deleted )..immediately I shut down the phone , then restarted . I got the pop-up twice, then no more. Its been over 12 hrs. So I'll see how it goes. Not going to try 11-6 yet. Hopefully newer update can fix this.
[X Style (Pure) Android Development] seukumeama:
no more build ? whats happened with nightlies ? i see other devices was build today
[X Style (Pure) Android Development] iwaskylester101:
They're probably trying to squash the current bugs before they release a nightly I'm assuming
[X Style (Pure) Android Development] lmulli:
The only build for today that I can see is for the antique Samsung i9300.
[X Style (Pure) Android Development] s3rgioru3las:
Anyone having an issue with a black screen (but the phone itself is on), and battery draining rapidly in this state? I've caught my phone with a dead screen about 3 times now and when rebooting, finding a drastic unwarranted reduction in battery. This first happened on the first 7.1 build, and happened again on 11/06 build. I cannot replicate it and seems to happen randomly. This was after clean installs, mind you.
[X Style (Pure) Android Development] marekca:
On every built 12.1 I got random sceeen of death, only force reboot help.