So, I searched a lot but couldn't find a solution that works. I was on 11S 05Q and I downloaded 12S OTA file from the official CM link. I'm rooted and had Xposed. But after installing the OTA via TWRP(2.8.6.0), I get the message "Unfortunately, the process android.process.acore has stopped" continuously. I have uninstalled xposed, cleared data for contacts and contacts storage multiple times but the error still keeps popping up. Also, if it helps, the preview crash report mentions "[CRASH]com.android.providers.contacts threw android.os.TransactionTooLarge Exception". So I believe it has something to do with the contacts data getting corrupted somehow. Is there anyway to resolve this issue? If I factory reset my phone through TWRP, will i lose all my media and will I have to reinstall all my apps again? I have the nandroid backup of 11S 05Q made through TWRP. If I decide to go back to 05Q by going through the restore option in TWRP, can it brick my phone because I read somewhere that 12S had new radio files. A detailed guide or link would be helpful. Thanks in advance.
I'm in the same boat, unfortunately. In my case, the trigger seems to be Facebook app. Did a lot of research, tried to fence FB off Contacts (and even Calendar) by changing Privacy Guard settings, to no avail. I was only able to get to the state when FB was still installed and not triggering the error permanently (in my case every 2-3 seconds really, making phone unusable), however the moment I tried to access Contacts or Phone apps, the error was back (means couldn't call anyone, which sort of defeats the purpose of having a cell phone). The ultimate solution (and the only, to my best knowledge) is to get an Android 5.1 - based ROM...
spanlength said:
So, I searched a lot but couldn't find a solution that works. I was on 11S 05Q and I downloaded 12S OTA file from the official CM link. I'm rooted and had Xposed. But after installing the OTA via TWRP(2.8.6.0), I get the message "Unfortunately, the process android.process.acore has stopped" continuously. I have uninstalled xposed, cleared data for contacts and contacts storage multiple times but the error still keeps popping up. Also, if it helps, the preview crash report mentions "[CRASH]com.android.providers.contacts threw android.os.TransactionTooLarge Exception". So I believe it has something to do with the contacts data getting corrupted somehow. Is there anyway to resolve this issue? If I factory reset my phone through TWRP, will i lose all my media and will I have to reinstall all my apps again? I have the nandroid backup of 11S 05Q made through TWRP. If I decide to go back to 05Q by going through the restore option in TWRP, can it brick my phone because I read somewhere that 12S had new radio files. A detailed guide or link would be helpful. Thanks in advance.
Click to expand...
Click to collapse
I have the same problem! I had it after updating yesterday. I did a factory reset and thought that fixed it but after opening trivia crack it came back. It's like everytime an account is added whether it's Facebook, a game, etc. It pops up with this error. I can fix it by booting into safe mode and wiping calendar and contacts storage in settings-apps. But once new account is installed it comes back. Could I wipe my entire device back to stock using 44s file via adb and then update to lollipop with zip? Maybe that will fix it.
---------- Post added at 04:00 PM ---------- Previous post was at 03:56 PM ----------
emelsk said:
I'm in the same boat, unfortunately. In my case, the trigger seems to be Facebook app. Did a lot of research, tried to fence FB off Contacts (and even Calendar) by changing Privacy Guard settings, to no avail. I was only able to get to the state when FB was still installed and not triggering the error permanently (in my case every 2-3 seconds really, making phone unusable), however the moment I tried to access Contacts or Phone apps, the error was back (means couldn't call anyone, which sort of defeats the purpose of having a cell phone). The ultimate solution (and the only, to my best knowledge) is to get an Android 5.1 - based ROM...
Click to expand...
Click to collapse
Boot into safe mode (power down phone and then hold both volume keys while starting until lockscreen appears). Then goto settings and apps. Find calendar storage and contacts storage. Wipe those and restore your contacts with a vcf file. Then reboot, this will fix it temporarily. As long as you don't add an account! I tried factory reset and thought that worked but it didn't. Might have to restore to stock 44s via adb. When will cyanogen have the full lollipop file available to install? All I see online is Ota zip, not full os.
I figured it out. Uninstall Facebook. Don't use Facebook app, use it though a web browser.
This is an Android 5 bug, as per Google it is fixed in 5.1 The bug is because of memory exception in contact storage. Potentially, it can come back from ANY application synchronizing contacts. In my case it was Nine Exchange Mail application. Cleaning contact storage, full phone reset - nothing helped, at the moment I tried to add my corporate email added through Nine - the problem came back. I removed Nine app, and added corp email through CM email app (Boxer). The app is Ok, but not giving as much features as Nine (Out of Office settings etc). For now it works, I just wonder when we will get the CM12.1 with this fix. This is really sad, but can't blame CM for this.
Here is the link for this problem description on AOSP issue tracker forum: https://code.google.com/p/android/issues/detail?id=95749
thanks...uninstalling updates to G+ app seems to help ...the popups have stopped <fingers crossed>
hopefully 5.1 has fixed this
To help gain more developer attention, please vote for the bug in Cyanogen's issue tracker: https://jira.cyanogenmod.org/browse/BACON-2820
Please also consider voting in Google's issue tracker (via Star at upper-left): https://code.google.com/p/android/issues/detail?id=95749
The Cyanogen defect report presently has just a single vote, reducing the likelihood it will be fixed anytime soon in 12.0. I'm hoping Cyanogen can back-port the necessary changes from 12.1 (Android 5.1.x) where this issue is already corrected.
Related
Greetings... I just ODINed back to stock, took the OTAs, ODINed CWM, and then flashed Tweaked Lite 1.0. So far it's awesome. Only issue is with Hangouts. I'm getting:
Couldn't sign in because we couldn't reach Google. Try again.
I've tried restarting, just waiting (multiple days), updating Hangouts, clearing data in Settings->Manage Applications, wiping cache from CWM and nothing seems to be working.
Any suggestions?
isutommyt said:
Greetings... I just ODINed back to stock, took the OTAs, ODINed CWM, and then flashed Tweaked Lite 1.0. So far it's awesome. Only issue is with Hangouts. I'm getting:
Couldn't sign in because we couldn't reach Google. Try again.
I've tried restarting, just waiting (multiple days), updating Hangouts, clearing data in Settings->Manage Applications, wiping cache from CWM and nothing seems to be working.
Any suggestions?
Click to expand...
Click to collapse
I had this issue and did this and it fixed it for me...
Clear updates and data from Google Hangouts and Google Play Services.
Delete Google Play Services using Root Explorer.
Reboot.
Try to open Hangouts and it will prompt you that you need Google Play Services.
Download and everything should then work ok.
Yeah this happens from time to time, still not sure on the reason or rhyme (#drseuss). Doing things similar to what jdawg334 outlined has helped me as well.
I finally got it to work. I couldn't get Root Explorer to delete Google Play Services successfully but with all the deleting of caches, updates, and force stopping services it finally was able to log in. Thanks for the help! Loving tweaked lite.
the tip is gold worth for my SGT7 3G in fixing time calculation .
Found more info here LINK, and here the step by step description:
uninstall updates for Google Play services
tried to open Hangouts which prompted me to update Google Play services
updated Google Play services
ran Hangouts
Works!
So thanks to PalaNIN on reddit.com.
Can't access internet
I was able to get past the Hangouts problem, but I can't seem to access the internet after flashing Tweaked Lite. I can access the Play store, d/l apps and updated installed ones, send and receive e-mails, etc., but if I open the default browser or Dolphin browser, I can't connect to the internet. I was given this Charge from a friend, and want to use it as a wifi device only. It was already updated to FP8 when I received it, so I rooted it, installed CMW, wiped data/factory reset, then just flashed the ROM. I didn't Odin back to any previous build, just went with the OTA already loaded on the phone. The internet seems to be the only thing not working.
*Edit*
Guess I didn't get past the Hangouts problem. I uninstalled the updates to Google Play Services, then reinstalled the update, but still get the message "Couldn't sign in because we couldn't reach Google. Try again."
zereoue said:
I was able to get past the Hangouts problem, but I can't seem to access the internet after flashing Tweaked Lite. I can access the Play store, d/l apps and updated installed ones, send and receive e-mails, etc., but if I open the default browser or Dolphin browser, I can't connect to the internet. I was given this Charge from a friend, and want to use it as a wifi device only. It was already updated to FP8 when I received it, so I rooted it, installed CMW, wiped data/factory reset, then just flashed the ROM. I didn't Odin back to any previous build, just went with the OTA already loaded on the phone. The internet seems to be the only thing not working.
*Edit*
Guess I didn't get past the Hangouts problem. I uninstalled the updates to Google Play Services, then reinstalled the update, but still get the message "Couldn't sign in because we couldn't reach Google. Try again."
Click to expand...
Click to collapse
Yeah the hangouts thing is obnoxious - I went back to stock a few times to see if I made the issue but I couldn't get it to work there either. Not sure why the browser is acting up though - haven't seen that myself... not sure what would be causing that issue unfortunately.
dwitherell said:
Yeah the hangouts thing is obnoxious - I went back to stock a few times to see if I made the issue but I couldn't get it to work there either. Not sure why the browser is acting up though - haven't seen that myself... not sure what would be causing that issue unfortunately.
Click to expand...
Click to collapse
I can't figure it out - not being able to browse the internet. It has worked once or twice, but I have no idea what changes to allow it. I restored a backup back to stock to check if I could browse then, and I could. I then reflashed TLite, but still had the same problem. I just restored the backup back to stock and I'll leave it there for now. I use the phone for wifi and a couple apps, so it should be fine for now. At some point I probably should try Odining back to a previous version, installing the OTAs, then flashing TLite. Would I want to repartition when going back to EP4D?
zereoue said:
I can't figure it out - not being able to browse the internet. It has worked once or twice, but I have no idea what changes to allow it. I restored a backup back to stock to check if I could browse then, and I could. I then reflashed TLite, but still had the same problem. I just restored the backup back to stock and I'll leave it there for now. I use the phone for wifi and a couple apps, so it should be fine for now. At some point I probably should try Odining back to a previous version, installing the OTAs, then flashing TLite. Would I want to repartition when going back to EP4D?
Click to expand...
Click to collapse
Wouldn't be a bad idea. Your usage matches my own (no sim card even), and I have yet to encounter any sort of browsing issues at all.
zereoue said:
I can't figure it out - not being able to browse the internet. It has worked once or twice, but I have no idea what changes to allow it. I restored a backup back to stock to check if I could browse then, and I could. I then reflashed TLite, but still had the same problem. I just restored the backup back to stock and I'll leave it there for now. I use the phone for wifi and a couple apps, so it should be fine for now. At some point I probably should try Odining back to a previous version, installing the OTAs, then flashing TLite. Would I want to repartition when going back to EP4D?
Click to expand...
Click to collapse
same deal here. it worked once. my theory is that it might have to do with Google Play Services. I'm thinking the Lite version blocks something or left a key file out.
found this: https://support.google.com/googleplay/answer/1647495?hl=en
and this: http://forums.androidcentral.com/go...ogle-hangouts-cant-sign-updated-solution.html
another hint
My situation was the same, google play services uninstall,reinstall doesn't help the login issue.
But at least : cleared hangouts data and google play services data, then on my PC I've log in to my gmail account and at the bottom left corner i've enabled "the new kind chat" (means Hangouts instead Talk) and then the hangouts on my phone immediately logged in to my account...
interesting...
Hey,
I noticed that messaging apps (for example whatsapp) crashes whenever I open a conversation that has attachments in it. Or if in the last 20/30 lines is no attachment (picture for.example) but I try to open the contact windows where it shows the name, status and media it crashes while loading the media. I tried clearing the cache of whatsapp and the system media app. Tried clearing cache and dalvik. Tried scanning the media with some apps. I deleted the newest pics i received because i thought maybe they were corrupted. Nothing helped. This occured after updating to 30O.
PS: I'm not going to wipe/reset my phone because I don't have the time to restore everything after such a reset.
Sent from my OnePlus One
Unfortunately for you the next step would be a factory reset. But if you're not willing to do that I guess you'll have to live with it. Or completely wipe the whatsapp data and start fresh with the app.
Transmitted via Bacon
I already thought that something went wrong when I updated to 30O so I just flashed the full ROM over my 25R with 30O OTA and now everything seems to work fine. Thank you for your efforts
Sent from my OnePlus One
"Unfortunately, Messaging has stopped."
I also had this problem. Kept getting this message when re-reading received messages, and, couldn't attach multimedia files. Found the answer from kspohn at an oneplus one forum. Thanks kspohn. It worked.
AT&T People without mms working here is the solution.
Call AT&T support. Go to wireless tech support when going through all the press # for (department name) mumbo jumbo.
Tell them you got a new phone and you need to activate mms on it by giving them IMEI number located on the packaging of your Oneplus One box particularly by the bar code sticker. This is like a SS for your specific phone
They will then ask you to power cycle the phone (turn it off for 10 sec) so call them originally with another phone.
They will then send a test mms to make sure it works. This only works for the global version of the phone so....... yea
Some At&T employees are aware of this phone... guy bro AT&T guy said it looked uber sweetles.
Hi,
Last Saturday I sideloaded the OTA file and successfully updated to Lollipop.
Directly after updating, the "me" contact was still populated with my info and also the picture from my G+ was present just like on Kitkat.
Yesterday I decided to give it a factory reset, since it is a major update and it is kind of an old habit to do so.
Since performing the factory reset this info is not populating. I've tried:
Clear data on contact storage, forcing a fresh sync.
Signing out of Google+ and back in
Removed my Google account and adding it back to the phone again.
Anybody with a suggestion how to fix this? Anything other then filling everything in manually since it should populate itself
Sander M said:
Hi,
Last Saturday I sideloaded the OTA file and successfully updated to Lollipop.
Directly after updating, the "me" contact was still populated with my info and also the picture from my G+ was present just like on Kitkat.
Yesterday I decided to give it a factory reset, since it is a major update and it is kind of an old habit to do so.
Since performing the factory reset this info is not populating. I've tried:
Clear data on contact storage, forcing a fresh sync.
Signing out of Google+ and back in
Removed my Google account and adding it back to the phone again.
Anybody with a suggestion how to fix this? Anything other then filling everything in manually since it should populate itself
Click to expand...
Click to collapse
It refuses to join with my contact record I have with all my information. I gave up and decided to let it be.
Sander M said:
Hi,
Last Saturday I sideloaded the OTA file and successfully updated to Lollipop.
Directly after updating, the "me" contact was still populated with my info and also the picture from my G+ was present just like on Kitkat.
Yesterday I decided to give it a factory reset, since it is a major update and it is kind of an old habit to do so.
Since performing the factory reset this info is not populating. I've tried:
Clear data on contact storage, forcing a fresh sync.
Signing out of Google+ and back in
Removed my Google account and adding it back to the phone again.
Anybody with a suggestion how to fix this? Anything other then filling everything in manually since it should populate itself
Click to expand...
Click to collapse
Google+ app --> Settings -->Account --> Contacts --> tick the "Keep contacts up to date" box.
krs360 said:
Google+ app --> Settings -->Account --> Contacts --> tick the "Keep contacts up to date" box.
Click to expand...
Click to collapse
Thanks for that mate, now it populated with my Google+ mug shot again
Downside of this method it also pumps all my G+ circles into contacts and that's something I don't like.
This "keep contacts up to date" setting has always been turned off on my phone(s) because of this.
After turning it off again, the my profile page went blank again. But the mug shot for owner info remained. So where one step further :good:
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.
Hi all
It all started last night when I added a second Twitter account to my official Twitter app. The dreaded android.process.acore appeared every second.
I've tried all the fixes - clearing the contact storage, removing my Google Account, deleting all my contacts from google.com/contacts, clearing the cache from recovery, restoring contact storage/Twitter from a Titanuim backup...
The only thing that gets rid of the message is disabling contact storage altogether. That, obviously, isn't a long term solution. The instant it's re-enabled I get the android.process.acore error messages again.
Does anyone have any other ideas? I'm worried if I take the plunge and factory restore It's still going to be there. I really don't want to do that if possible.
Thanks.
EDIT: Found the problem using Privacy Guard in CM12. I reset all the allowed/denied counters, enabled Contact Storage, let it error 3 times, disabled it and went back into Privacy Guard. Google and Telegram had accessed "red contacts" 3 times. Uninstalled Telegram and tried again. Still erroring. Uninstalled Google and all's well. Shame though, I use Google Now a lot. Looking for a fix for that now.
EDIT 2: Writted a post about the whole thing here if anyone wants to read it: http://techspert.info/2015/08/21/solved-android-process-acore-has-stopped-on-cyanogenmod/