Hi guys, i was playing a game called F18 Carrier Landing, when my phone froze. I long held the power button so that it could reboot. After it rebooted, i unlocked it, and it gave me the interface as if i freshly flashed a new rom or i did a factory reset (the interface asking about google and setting up accounts). So, i completed that and once my home screen popped up, i faced a few force closes, from titanium backup, my anti-virus software Avast, and various other applications. I was very freaked out at this point. I remember reading something about fixing permissions if i faced constant force closes, so i rebooted to recovery and fixed permissions. Booted up fine, still missing data, but no force closes. But my google maps does not seem to work, i open it and it opens to the orange-ish checkerboard backing, but then force closes. I'm not exactly sure what to do at this point. Can anyone advise me on what to do or if this ever happened to them? For reference, i'm still on Froyo (don't ask why) 2.2.1, ROM's Audiophile Redux by Raver. If you require additional info to help me find a solution, i will gladly comply. Thanks!
EDIT1: I uninstalled my Maps with Titanium and restored a really old version from September of last year, and it seems to be working. Or atleast it opens and loads.
EDIT2: It seems to only load apps stored on my internal/phone storage. As i checked Applications in settings, the SD tab was empty as if there are not apps from the SD card installed, what can i do about this?
This has happened to many of us on GB. Crazy it happened on Froyo. You are going to need to reinstall your missing apps. If it is similar to what happened to us your phone factory reset on it's own.
Alright thanks, when it happened i thought it was a pretty serious problem, but as i restore my apps from Titanium, i realize it's not that bad. Just glad to know i wasn't alone on this ordeal. I plan on hopping onto AOKP or maybe MIUI when my contract ends, this phone is just to valuable to me at the moment. They both seem so fast and amazing, plus AOKP has themes. K, so quick question, do you know the reason behind this, i mean, is my SD corrupted or something? I can still play the music and the videos from it on my phone, but i don't understand why it wouldn't read the apps on the SD.
None of us have nailed down the cause unfortunately.
Thanks anyways, up and running with most of my apps back. Gotta get around to flashing a new ROM someday. So many good one's coming out!
Sent from my SGH-T959V using Tapatalk 2
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.
Let me start off by saying Im not a n00b at this stuff by any means...I did however decide to go cell phoneless for a couple years, so Ill admit Im probably way behind on everything, but I usually dont have any problems. I got my S5 brand new around Christmas, it had 4.4.4 already loaded on it. I decided instead of going crazy like I did with my GS2 and Vibrant, wanting to customize every aspect of it, Id keep it simple, root it, debloat it myself and be done with it. I rooted it no problem, but everytime I rebooted my phone Google Maps and S Health would force close repetitively, until I went into the priv-app folder and reinstalled Health Services and same with Google Maps. Theyd work fine until I rebooted then it was a rinse was repeat situation every time. I updated to Lollipop through Odin, Rooted it, same issue, same 2 apps. While its not The worst problem to have, it is very tedious. So for the time being, Im unrooted, and I really hate the 734 apps sprint preloads on their phones, and Id like to change a couple things in the build.prop, but Im going with the less annoying option for now. Anyone else have a similar or even the same issue?
Also I guess I should mention Ive tried doing a full Factory Reset, wiped cache and dalvik, and before I have time to login to sync my accounts to my phone, if its rooted they force close over and over.
tommy p said:
Anyone else have a similar or even the same issue?
Also I guess I should mention Ive tried doing a full Factory Reset, wiped cache and dalvik, and before I have time to login to sync my accounts to my phone, if its rooted they force close over and over.
Click to expand...
Click to collapse
Is this when you are simply rooted? Or after you have debloated? If so, maybe you removed or disabled something important.
I have tried to keep it simple so far as well. I updated to Lollipop OTA. Even though I took the normal OTA update something about the phone was not right. Maybe some old settings or data causing problems. I did a full data wipe and then flashed this stock ROM. It is Deodexed and has a few things removed, but it mostly stock. I also ran the Debload tool included in that thread to rid myself of all of the Sprint apps. The phone has been super stable and smooth.
This happens once its rooted before I remove anything. I learned a long time ago to be careful what I remove, lol. But like I said, once the phone boots up before I even have the chance to set it up S Health and Google Maps force close and continue to do so until I go into the folder I believe its /system/priv-apps/ and reinstall the Health Service and same with Google Maps. and Ive wiped the phone clean, clearing it of any settings. I knew it wouldnt work, but figured I had tried everything else, but I even tried moving them to my external sd. I guess its just one of those things, Ill either figure it out or just keep it unrooted for a while.
That doesnt mean if someone has any ideas I dont want to hear them though.
After many long attempts to fix this I have come up empty handed. I believe the Hardware is either corrupted or damaged but need an expert to help confirm. (it doesnt even seem worth it at this point to fix, but i want to try anyways, its my kids tablet) I will add as much detail as possible.
First the tablet would get stuck in booting (A9 screen) found that this is due to a corrupted firmware. I flashed a firmware onto the device and it was able to boot up, however still with a few issues. google play store when updated would instantly crash "google play store has stopped" the second you clicked to use it. the only fix i found for this was to uninstalled the google play store update back to factory and it would worked, with the problem of some apps had to be downloaded over and over until it decided to complete, often finishing with a package file invalid. but i managed to get a few games and whatever and gave it back to my daughter.
after about a week everything crashed at once on boot up. process.google.gapps would crash over and over and over as soon as you click ok, many other apps crashing as well and just repeating google account manager, Key chain, RS OTA, and others i cant remember at this time (the problem is currently not occurring or i would go get this information.) mostly the gapps process was crashed over and over making the tablet unusable due to constantly trying to click these errors.
Odd behaviour, during that i managed to click and quickly select settings, and went in and deleted a bunch of apps or uninstalled updates on ones that were crashing, i could uninstalled enough to stop all the errors.. then i rebooted the tablet.. and all the errors were back, and everything i uninstalled was back too, how the f**k?! lol.
i attempted such things as going into recovery and deleting all the cache and media, nothing. so i flashed it again.
the above error return after some time. and i flashed it again (my daughter wanted it working this seems to be my only quick and temporary fix, i have disabled many apps and stopped it from automatically updating, however i still found some settings after being changed, to be undone back to the way it was before i changed it after rebooting the tablet. again it always crashes when google play store updates. this time i rebooted the tablet and went to update the store, and now the app can NOT be found in the store. there does not even seen like a way to update the tablet like "here is your only buggy version, have fun"
CORRECTION: Google Play Store could not be updated because after restarting the tablet the updates were back, as if i had never uninstalled them. i didnt bother checking the first time because this is very unusual.
I am willing to root, change, hack, smash, throw out the window, put it in the hydraulic press at work...i dont care lol
i believe the hard drive has damage.
(i didnt run thru all the attempts i have made to fix things, cause i could write a novel. Thank you for reading.
- Kontr4 -
Hello,
Since about a couple of weeks ago, the Play Store started getting really slow. Updates get stuck at "download pending", and sometimes they do download. Other app downloads get stuck at 100% downloaded for a long time before installing. I can leave my phone on updating all night and in the morning it is still not done. This happens both on LTE and on Wi-Fi, and I do have very fast Wi-Fi. I am on the OxygenOS Open Beta 10. I did not do any changes to my phone when this started happening.
I have tried all of the following to fix the problem, but it doesn't help:
Rebooting the phone
Uninstalling Play Store updates
Deleting and adding Google Account
Clearing cache
I tried wiping the phone and using OxygenOS 9.0.2 - same problem.
I have clean-wiped the phone, deleting even internal storage, and flashed OxygenOS clean stock, and still it does this. (it also has new problems, like Magisk doesn't offer root authorization anymore even though it installed and working according to Magisk Manager...)
The only way I could get the Play Store to work properly was to use a custom ROM, HAVOC 2, but that ROM has problems with the front camera in some apps.
It almost seems like the Play Store detects OOS and decides to act funky. Has anyone faced this problem, or resolved it? Should I contact Google and see if the problem is their Play Store?
I almost feel like, since I have tried with clean wiping and using stock ROMs, and things that weren't broken before just started breaking for no reason, that there is a problem with the hardware itself. It makes no sense that the problems carry over into stock ROM when I have wiped everything several times.
Uninstall or disable the google app.
That fixed it for me.
Let me know if that works.