Related
so did a battery pull trying to fix an sms problem and when i booted back up i started getting some FC and now lost most (not all) of my contacts and no longer can get into gmail and the market? the apps are there but when i click them they just look like they are opening and then i get put back to the home screen?? one of the pop ups i keep getting is the location consent? i have tried restarting a few times with no luck... also when i go to option and then to accounts and then add account, i no longer have gmail on there?
Recovery,
Wash,
Rinse,
Repeat.
Dnakaman said:
Recovery,
Wash,
Rinse,
Repeat.
Click to expand...
Click to collapse
just did that and all is back to normal... was hoping there was a way around wiping all and tsarting over though... hopefully it wont happen again! not sure what caused it...
Unfortunately, the best way to take care of these odd happenings is usually get back to a known good configuration, then try again to pinpoint the source of the error.
Glad to hear your back up and running though.
I believe I know the cause to this. Go SMS seems to beat the ever living hell out of Gingerbread when you uninstall it. I had this same exact issue and the cure was either do not remove Go SMS for any reason, or never install it.
adrynalyne said:
I believe I know the cause to this. Go SMS seems to beat the ever living hell out of Gingerbread when you uninstall it. I had this same exact issue and the cure was either do not remove Go SMS for any reason, or never install it.
Click to expand...
Click to collapse
Go SMS can also be a pain to upgrade and goes nuts with memory issues that aren't really there. I use it and love it but it's tempermental for sure.
GO apps (at least some) collect info and send it back to the developers without telling you.
jcase said:
GO apps (at least some) collect info and send it back to the developers without telling you.
Click to expand...
Click to collapse
Yippie. Go means stop.
The notification badge on my stock Messaging app icon is incorrectly showing 1 unread message.
I have a totally stock Droid RAZR MAXX HD running 4.4.2. My stock messaging app is version 4.4.2-10. SMS is set to "Messaging" (not "Hangouts"). All settings are default. Verizon Wireless is my service provider.
From my own troubleshooting, I have concluded that the problem is probably KitKat-related since stopping, disabling, and clearing (data, cache, and defaults) the stock messaging app has no effect. Also, this problem started after my OTA upgrade to KitKat (never had it before). Further, after completely disabling the stock messaging app, I alternatively installed GO SMS Pro, chomp SMS, and Verizon Messages and experienced the exact same problem with each.
Any ideas about how to fix this problem, without FDR'ing or rooting the phone, would be greatly appreciated.
clear dalvik?
you try clearing dalvik cache?
Great suggestion, but how do I perform it? Can you direct me to instructions on how to clear the Dalvik cache on a stock RAZR MAXX HD running KitKat? I can't find any that don't require a rooted phone. Thx much.
PW_Irvine said:
Great suggestion, but how do I perform it? Can you direct me to instructions on how to clear the Dalvik cache on a stock RAZR MAXX HD running KitKat? I can't find any that don't require a rooted phone. Thx much.
Click to expand...
Click to collapse
i never have stock recovery on, so i could be wrong, but i dont think you can do that in stock recovery.
which means you would have to put on a custom one and root, which i think you said you didnt want to do.
it is somewhat common to have random issues like this on a major software upgrade, especially one that jumped so many other builds.
i know you really dont want to do it, but clearing the corrupted data is really the best course of action, and it may be the only one honestly.
and if you are going to go that far, it is really best to just re-flash the phone encase something in the system is corrupt. just no point in going 1/2 way just to find out you still have the issue later.
sorry thats not the answer you were looking for, but sometimes it is not avoidable.
bweN diorD said:
i never have stock recovery on, so i could be wrong, but i dont think you can do that in stock recovery.
which means you would have to put on a custom one and root, which i think you said you didnt want to do.
it is somewhat common to have random issues like this on a major software upgrade, especially one that jumped so many other builds.
i know you really dont want to do it, but clearing the corrupted data is really the best course of action, and it may be the only one honestly.
and if you are going to go that far, it is really best to just re-flash the phone encase something in the system is corrupt. just no point in going 1/2 way just to find out you still have the issue later.
sorry thats not the answer you were looking for, but sometimes it is not avoidable.
Click to expand...
Click to collapse
Have the same problem - I find that if I delete a recent MMS message sent from me, then it goes back to normal.
PW_Irvine said:
Great suggestion, but how do I perform it? Can you direct me to instructions on how to clear the Dalvik cache on a stock RAZR MAXX HD running KitKat? I can't find any that don't require a rooted phone. Thx much.
Click to expand...
Click to collapse
baldbob said:
Have the same problem - I find that if I delete a recent MMS message sent from me, then it goes back to normal.
Click to expand...
Click to collapse
nice suggestion :good: i have never heard of that.
thanks
yeah dont think its possible on a phone that isnt rooted or has a custom recovery, whats the reason you dont want to to root?
Unfortunately, deleting all SMS and MMS messages did not solve the problem either, so I just FDR'ed the phone. Problem is gone on reboot of course, but so is 13 months worth of app configuration. I would root the phone this time except that the screen is also acting up on me and the phone still has 4 months left on the Costco warranty that I got (for free) with the phone. Wouldn't it be great if Android "L" allowed you to back up app settings along with apps without the need to root the phone first! Thx to all.
PW_Irvine said:
Unfortunately, deleting all SMS and MMS messages did not solve the problem either, so I just FDR'ed the phone. Problem is gone on reboot of course, but so is 13 months worth of app configuration. I would root the phone this time except that the screen is also acting up on me and the phone still has 4 months left on the Costco warranty that I got (for free) with the phone. Wouldn't it be great if Android "L" allowed you to back up app settings along with apps without the need to root the phone first! Thx to all.
Click to expand...
Click to collapse
Follow-up: same problem occurred following FDR. It is related to MMS messaging and it is solved by removing all MMS messages from phone. I did not have this problem with JB. It showed up after OTA upgrade to KK. Too bad for those who like to keep their MMS messages.
Hey, first off I did search but could not find anything that could help my situation. I started having inconsistent email send and receive several weeks ago. I would remove all email accounts (hotmail, yahoo, and exchange) and re add and it worked for a week or so. I did this a few times and it worked for a while but recently started getting "Exchange Services have stopped" errors/prompts.
I emailed support and they said to factory reset the phone, I tried that and it didn't work. Upon initial boot, I would get the exchange error immediately and most importantly it won't connect to Google services (cannot connect to google services) so nothing will work minus phone (won't take calls but will make calls) and text. No PlayStore or anything is available. I'm not 100% sure the factory reset is truly a full reset as I didn't have to go through the cyanogen setup as it just turns on and I add the accounts in the settings.
Phone is NOT rooted or flashed or anything, just a normal phone with a normal user.
Please help, your insight is appreciated.
Anyone???
What version of CM11s are you on.
11.0-xnph33r
I would try flashing/reflashing XNPH33R use this thread for instructions on how to. Its a informative thread for all 1+1 users to familiarize yourself with.
Will that void my warranty? I've already asked for a refund from OP. Haven't gotten a response yet but out of the 50 days I've had the phone, it's been inoperable for 10% of that time and been inconsistent (emails/texts) for the remaining 90.
Now I haven't heard back from OP, I hope they will play nice.
Cory0518 said:
Will that void my warranty? I've already asked for a refund from OP. Haven't gotten a response yet but out of the 50 days I've had the phone, it's been inoperable for 10% of that time and been inconsistent (emails/texts) for the remaining 90.
Now I haven't heard back from OP, I hope they will play nice.
Click to expand...
Click to collapse
No it shouldn't void warranty your just returning it to stock.
but it's already stock, right?
Thanks, I appreciate your help.
Cory0518 said:
but it's already stock, right?
Thanks, I appreciate your help.
Click to expand...
Click to collapse
Yes its already stock but a reflashing of rom may fix your problems.
Hey , mark.
One last question, on my last reset, I noticed the following error but it did finish the reset.
E: Failed to stat data/system/procstats/state-2014-08-25-03-19-00.bin
Cory0518 said:
Hey , mark.
One last question, on my last reset, I noticed the following error but it did finish the reset.
E: Failed to stat data/system/procstats/state-2014-08-25-03-19-00.bin
Click to expand...
Click to collapse
Have no clue maybe someone can enlighten us both.
Okay, guys, here's the problem. I have been pulling my hair out for days over this. On any Lollipop ROM I install, no matter what combination of gapps and AOSP ROM I install on my OPO, after completely and totally formatting caches, system, data, and /data/media, the problem persists:
Always after logging into an account, but not always the same one, I start to get an error "android.process.acore has stopped." It happens every few seconds and renders the device unusable. I have tried every fix I could find online, including wiping contacts storage data, contacts data, etc. I have formatted my phone several times, and each time the problem comes back. It only stops when I disable Contacts Storage in settings, which then in turn disables all contacts functionality.
This is getting totally ridiculous, and the only thing I can think of is that the AOSP version of contactsprovider.apk is totally corrupt. Any ideas?
I have the same problem... Did you succeed in resolving it?
flolep said:
I have the same problem... Did you succeed in resolving it?
Click to expand...
Click to collapse
Somewhat. The issue manifests itself when Facebook is synced with your contacts, and you use Facebook OAuth to sign into another app. For whatever reason, this causes the contacts app to go nuts, and the only way to fix it once it happens is to get rid of the Facebook app. It's a bug that is quite beyond me to fix. There is a modded Facebook apk floating around somewhere, that has had permissions modded so it's not allowed to use your contacts or register as an account in your phone. That works. It also works if when you install a new ROM, you sign into any apps that use your Facebook login before you install the Facebook app, that way you log into them with the browser and they never talk to the contacts app. Once you have installed the Facebook app, DO NOT EVER click "Sign in with Facebook" in any app on your phone, or you're screwed again.
That's pretty much what I've come up with thus far. Hope that helps.
EDIT: Here's the link to the thread with the modded Facebook apk: http://forum.xda-developers.com/showthread.php?t=2333637
I have the same issue on all CM12 based roms. It seems to happen for users with many contacts (hundreds). Uninstalling facebook seems to fix the problem for me. I have no such problems on my Nexus 5 with the same setup and facebook installed, so I wonder if it's not something specific to the bacon CM12 code.
prometheus1010 said:
I have the same issue on all CM12 based roms. It seems to happen for users with many contacts (hundreds). Uninstalling facebook seems to fix the problem for me. I have no such problems on my Nexus 5 with the same setup and facebook installed, so I wonder if it's not something specific to the bacon CM12 code.
Click to expand...
Click to collapse
It happens for other phones users... See here : https://productforums.google.com/forum/m/#!msg/nexus/Ip-hdFEQccY/OSFCz4Qj59oJ
Thanks for your partial solution @jkotzker... For me it's a no go because I am a big facebook user and I can install app with Facebook account linked at anytime... It's really really annoying to not log with Facebook account if the Facebook app is installed I don't know what to do... I tried everything like you.
I've recently been getting the same issue but mine says "unfortunately the process com.android.phone has stopped" everything was fine had this phone for about a month was on a lollipop ROM and that just randomly popped up. At first I thought it was the ROM so I switch to another lollipop ROM and got the same issue. So I went back to the latest ota kk ROM and til now I'm still getting the pop up. What's going on here? Please help
marcviado said:
I've recently been getting the same issue but mine says "unfortunately the process com.android.phone has stopped" everything was fine had this phone for about a month was on a lollipop ROM and that just randomly popped up. At first I thought it was the ROM so I switch to another lollipop ROM and got the same issue. So I went back to the latest ota kk ROM and til now I'm still getting the pop up. What's going on here? Please help
Click to expand...
Click to collapse
Oh yeah I've been trying to figure this out since cm12 unofficially came out for the note 4. Like all of you said it's fine for a while or sometimes it's messed up right away. I've had it work for two or three days then out of nowhere just have the error pop-up and never go away. Disabling google contacts storage also got rid of the error for me but of course I can't have the phone without google contacts and sync. This last time it happened just by downloading and signing into Dropbox, which isn't related to Facebook at all. This is belong frustrating because nobody seems to have a fix and it's the only thing stopping me from using cm 12. Is there any Dev that can help or work on this with a logcat?
Sent from my SM-N910T using XDA Free mobile app
pablo1215 said:
Oh yeah I've been trying to figure this out since cm12 unofficially came out for the note 4. Like all of you said it's fine for a while or sometimes it's messed up right away. I've had it work for two or three days then out of nowhere just have the error pop-up and never go away. Disabling google contacts storage also got rid of the error for me but of course I can't have the phone without google contacts and sync. This last time it happened just by downloading and signing into Dropbox, which isn't related to Facebook at all. This is belong frustrating because nobody seems to have a fix and it's the only thing stopping me from using cm 12. Is there any Dev that can help or work on this with a logcat?
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
I didn't find one...
I talked about this problem in xda temasek rom thread and ak kernel thread without success. I even sent a message on official cyanogenmod website, with last crash and logcat attached. No success. The problem happened in 2012 too... And since then, Google didn't have a solution for it.
It seems that Google is finally aware about this problem and the correction could arrive in "a future version"... Well. I want it now... Indeed, there seems to be only to increase the buffer transaction between applications and contact storage from 1MB to 2MB for example, to have it corrected. But no dev wants to do it because the problem cannot be reproduced! And it's rare! But we have it! It's incredible to have it back after a full wipe... And happening randomly, just after a random sync between application and Android system...
Any more updates on this issue/ anything else we can do to get this resolved? Even my partial, temporary solutions have stopped working, and I am getting really frustrated.
Glad to see I'm not the only one here with this issue. Took different search terms to eventually land me here since this such an old and somewhat common issue. Nonetheless... Same problem. OnePlus One running Temasek CM12. Disabling contacts storage.... Blah blah blah. Its rather disappointing there's no actual solution instead of a workaround. But, I'm finally happy to know its Facebook. An app I rarely use but do need unfortunately.
Edit: wondering if anyone has had any luck fastboot flashing the factory image? I know it's a pain in the ass to have to back up all your files, etc off the device so I'd like to know if anyone has had success or even tried this. Cuz, I really won't feel satisfied until I've resorted to this last measure if there's the possibility of eradicating the problem.
t3chn0s1s said:
Glad to see I'm not the only one here with this issue. Took different search terms to eventually land me here since this such an old and somewhat common issue. Nonetheless... Same problem. OnePlus One running Temasek CM12. Disabling contacts storage.... Blah blah blah. Its rather disappointing there's no actual solution instead of a workaround. But, I'm finally happy to know its Facebook. An app I rarely use but do need unfortunately.
Edit: wondering if anyone has had any luck fastboot flashing the factory image? I know it's a pain in the ass to have to back up all your files, etc off the device so I'd like to know if anyone has had success or even tried this. Cuz, I really won't feel satisfied until I've resorted to this last measure if there's the possibility of eradicating the problem.
Click to expand...
Click to collapse
I initially had this problem when I switched to lollipop, not sure how it fixed itself but I'm guessing it's the contacts sync like you posted here; only the first time I accidentally synced Fb contacts, and due to the massive number of friends on it, it crashed. But you can disable any sort of sync services on Fb and continue using the app for everything else, I've had no issues since.
Do you mean luck with fixing this issue after flashing the factory image or only returning to stock? Because I've had no issues returning to stock from lollipop by flashing the factory images through fastboot.
Aditya Srinidhi said:
I initially had this problem when I switched to lollipop, not sure how it fixed itself but I'm guessing it's the contacts sync like you posted here; only the first time I accidentally synced Fb contacts, and due to the massive number of friends on it, it crashed. But you can disable any sort of sync services on Fb and continue using the app for everything else, I've had no issues since.
Do you mean luck with fixing this issue after flashing the factory image or only returning to stock? Because I've had no issues returning to stock from lollipop by flashing the factory images through fastboot.
Click to expand...
Click to collapse
I meant with flashing the factory image via fastboot to stop the frustratingly obnoxious pop ups of the process stopping (w/o uninstalling FB). You answered my question.
So, get this... Resolved the error by uninstalling Facebook. Today I picked up a Moto 360 and you HAVE to install Motorola Connect to really personalize the device... Once I allowed it to see my Google+ account info the android.process.acore started again. I'm SO annoyed. Gonna try a factory reset again and see if that helps. The only way to stop it is to uninstall Motorola Connect and that really sucks cuz I want to (of course) mess with my watch. I know nothing of Android Wear yet or how to root, etc the 360 so.... Here I go. Boldly. Lol
I'm just curious why I haven't seen more people having this issue. It's been plaguing me now for almost 2 weeks. I'm ready to throw my Bamboo OPO out the effing window. WTF.
t3chn0s1s said:
I meant with flashing the factory image via fastboot to stop the frustratingly obnoxious pop ups of the process stopping (w/o uninstalling FB). You answered my question.
So, get this... Resolved the error by uninstalling Facebook. Today I picked up a Moto 360 and you HAVE to install Motorola Connect to really personalize the device... Once I allowed it to see my Google+ account info the android.process.acore started again. I'm SO annoyed. Gonna try a factory reset again and see if that helps. The only way to stop it is to uninstall Motorola Connect and that really sucks cuz I want to (of course) mess with my watch. I know nothing of Android Wear yet or how to root, etc the 360 so.... Here I go. Boldly. Lol
I'm just curious why I haven't seen more people having this issue. It's been plaguing me now for almost 2 weeks. I'm ready to throw my Bamboo OPO out the effing window. WTF.
Click to expand...
Click to collapse
It's mostly not because of lollipop, but might be the app itself, I read a few others having this problem on other forums with HTC, the solution they found was to clear data on contacts storage. Give that a try and see if it works, if not I'd suggest going back to Stock or probably the new OxygenOS which is supposed to be out by now. Check out @timmaaa index thread in the general section, it has all the necessary stock images you need. Report back and let us know if it fixed the issue for you
Aditya Srinidhi said:
It's mostly not because of lollipop, but might be the app itself, I read a few others having this problem on other forums with HTC, the solution they found was to clear data on contacts storage. Give that a try and see if it works, if not I'd suggest going back to Stock or probably the new OxygenOS which is supposed to be out by now. Check out @timmaaa index thread in the general section, it has all the necessary stock images you need. Report back and let us know if it fixed the issue for you
Click to expand...
Click to collapse
Yea, I tried clearing contacts storage numerous times to no avail. I can live without the app... At first I thought it was a requirement to change watch faces... But, I do have a backup of stock, rooted but I can't go back to KK after being so used to LP. I'm def going to jump on Oxygen just to try it out but I'm guessing I'll end up running stock CM12s. I can't wait. I'd much rather have a stock (w/root of course) or mostly stock device that actually works completely.
t3chn0s1s said:
Yea, I tried clearing contacts storage numerous times to no avail. I can live without the app... At first I thought it was a requirement to change watch faces... But, I do have a backup of stock, rooted but I can't go back to KK after being so used to LP. I'm def going to jump on Oxygen just to try it out but I'm guessing I'll end up running stock CM12s. I can't wait. I'd much rather have a stock (w/root of course) or mostly stock device that actually works completely.
Click to expand...
Click to collapse
The bug has been corrected by Google themselves with Android 5.1. Finally!.. So, like me, just try omni 5.1 or last cm12.1 unofficial and the error has gone! So good to use my phone.... Hmmm... How to say... Normally... Lol.
flolep said:
The bug has been corrected by Google themselves with Android 5.1. Finally!.. So, like me, just try omni 5.1 or last cm12.1 unofficial and the error has gone! So good to use my phone.... Hmmm... How to say... Normally... Lol.
Click to expand...
Click to collapse
Very nice. Glad to hear this... Xposed isn't compatible with 5.1 yet, right?
Two things to try…
Go into settings/apps , press the menu button and select "reset app preferences". Reboot
You Can also try entering the following in your commands:
Su (enter)
Killall rild (enter)
reboot
Should have read the entire post, glad that has been fixed by google, I experienced the same thing and it's a huge pain in the butt.
t3chn0s1s said:
Very nice. Glad to hear this... Xposed isn't compatible with 5.1 yet, right?
Click to expand...
Click to collapse
No. Not yet. But. Well. CM12 is already good functionality wise. And with this bug disappeared it's really a happiness.
---------- Post added at 12:42 AM ---------- Previous post was at 12:39 AM ----------
tmjm28 said:
Two things to try…
Go into settings/apps , press the menu button and select "reset app preferences". Reboot
You Can also try entering the following in your commands:
Su (enter)
Killall rild (enter)
reboot
Should have read the entire post, glad that has been fixed by google, I experienced the same thing and it's a huge pain in the butt.
Click to expand...
Click to collapse
Yeah, yeah. Already tried... Lol. I think I tried every single advice given in all the Android forums of the world on this bug lol. Well. Google finally heard us. +++
tmjm28 said:
Two things to try…
Go into settings/apps , press the menu button and select "reset app preferences". Reboot
You Can also try entering the following in your commands:
Su (enter)
Killall rild (enter)
reboot
Should have read the entire post, glad that has been fixed by google, I experienced the same thing and it's a huge pain in the butt.
Click to expand...
Click to collapse
Neither worked but thanks for the suggestion. I did find a Facebook work around. Found the Lite Version via a Google search (since its technically not available in the US) , installed it and it works fine. No android.process.acore FC's or repeated pop ups.
Update: This problem reared its ugly head again on CM12 and I ended up having to uninstall Twitter this time. So, now I'm on CM12s and as soon as I logged into my other Google account user Boxers email app I got the android.process.acore crash again. Uninstalling that app immediately stopped it. God I can't wait for 12.1 for our OPOs. This problem is absolutely ridiculous. I can't take this anymore. I really can't use ANY social media apps unless its like Tinfoil for FB or Twitter. I don't have any connected accounts except Google & Cyanogen.. Which I truly can live without but... Just for the hell of it.... Knowing I have a backup and I'm about to clean flash the latest stock build I tried to add Waze and it caused the crash all over again. Uninstalling Waze didn't help. I shouldn't have to deal with this. Only way to stop it is to disable contacts storage. Once it begins it doesn't stop. Effing Google with their half baked crap.
So, whenever im seeting up facebook messenger on my VIvo Nex S. It reboots itself before I can complete the setup. No matter what I do, it always happens. I thought it may have been something that I uninstalled using ADB but, I just did a factory wipe tonight, set my my phone back up, and without fail, it did it again. Anyone else expercing this or did experience this and have a solution for it? After I setup it up it never happens again, its just that initial time. It really bothers me.
Phaze1585 said:
So, whenever im seeting up facebook messenger on my VIvo Nex S. It reboots itself before I can complete the setup. No matter what I do, it always happens. I thought it may have been something that I uninstalled using ADB but, I just did a factory wipe tonight, set my my phone back up, and without fail, it did it again. Anyone else expercing this or did experience this and have a solution for it? After I setup it up it never happens again, its just that initial time. It really bothers me.
Click to expand...
Click to collapse
Did you do a factory reset with Erase All Data and selecting Format Phone Storage? If so, then perhaps contacting VIVO via Facebook might have a solution.
I had a problem with a VIVO update where my Android Message app would not open. I contacted them via Facebook. They had me perform some tasks and send it to them, and now I don't have that problem with their latest update. But I have to say I fixed my problem before they had a fix by Formatting Phone Storage in Erase and Backup setting.
My point is, if this is phone specific, they can fix the problem and add the solution to their future updates if you make them aware of it.