Related
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.
[Android 5.1] Hangout constantly crashes on launch. + "Google Apps has stopped"
I upgraded to 5.1 on Monday by flashing the factory image. After the first boot and flashing root/recovery etc, I checked everything is running smooth and rebooted the device once more. Ever since then, Google Hangout crashes every time I try to open it; with this error -
Unfortunately, Hangouts has stopped.
Click to expand...
Click to collapse
I cleaned its cache, cleared data, uninstalled updates, updated from play store.
I cleaned all system cache from Settings > Device > Storage.
I cleaned Dalvik-cache and cache partition by going to recovry.
Nothing seems to fix it. It still crashes with the same error. From time to time, I'm also getting this error -
Unfortunately, Google Apps has stopped.
Click to expand...
Click to collapse
But all other Google apps are working fine. Anyone else having this issue?
Hangout - 3.0.87531466
Play Services - 7.0.93 (1778921-438)
===============================================
UPDATE -
POSSIBLE CAUSE AND SOLUTION
After spending 2 entire days on it and flashing the 5.1 factory images 3 times, I found out that it was being caused by LBE Security Master's Active Defense mode. This is like a live AppOps. It grants/denies permissions to apps at run time. Even though I had given full permission to Hangout, it was still crashing for unknown reasons. But after I disabled the active defense mode and rebooted the device, everything is running fine now.
So, if you are using any permission control app like LBE or AppOps, try disabling that and reboot your device. Yes, reboot is necessary. Just disabling doesn't fix it.
bagarwa said:
I upgraded to 5.1 on Monday by flashing the factory image. After the first boot and flashing root/recovery etc, I checked everything is running smooth and rebooted the device once more. Ever since then, Google Hangout crashes every time I try to open it; with this error -
I cleaned its cache, cleared data, uninstalled updates, updated from play store.
I cleaned all system cache from Settings > Device > Storage.
I cleaned Dalvik-cache and cache partition by going to recovry.
Nothing seems to fix it. It still crashes with the same error. From time to time, I'm also getting this error -
But all other Google apps are working fine. Anyone else having this issue?
Hangout - 3.0.87531466
Play Services - 7.0.93 (1778921-438)
Click to expand...
Click to collapse
What was your installation process for Play Services 7.0.93?
Aerowinder said:
What was your installation process for Play Services 7.0.93?
Click to expand...
Click to collapse
I had that version after flashing the 5.1 factory image. I guess Google pushed that to my device. It's not sideloaded.
bagarwa said:
I had that version after flashing the 5.1 factory image. I guess Google pushed that to my device. It's not sideloaded.
Click to expand...
Click to collapse
That is strange. I have the same version of Hangouts, but my updated version of Play Services is 6.7.76 (1745988-438).
bagarwa said:
I upgraded to 5.1 on Monday by flashing the factory image. After the first boot and flashing root/recovery etc, I checked everything is running smooth and rebooted the device once more. Ever since then, Google Hangout crashes every time I try to open it; with this error -
I cleaned its cache, cleared data, uninstalled updates, updated from play store.
I cleaned all system cache from Settings > Device > Storage.
I cleaned Dalvik-cache and cache partition by going to recovry.
Nothing seems to fix it. It still crashes with the same error. From time to time, I'm also getting this error -
But all other Google apps are working fine. Anyone else having this issue?
Hangout - 3.0.87531466
Play Services - 7.0.93 (1778921-438)
Click to expand...
Click to collapse
I am having the same issue with hangouts. I've taken the same steps to try to fix it.
As part of troubleshooting, I momentarily disabled hangoouts via app settings, then I started to see the "Google App" error. After re-enabling I didn't see this error anymore.
I have not tried removing hangouts completely, as it seems this would break other things.
Any possible solutions?
EDIT: The Google App error is actually persisting.
My issue is hangouts keeps getting killed by the Low memory killer even though I have 1gb free ram.
I did some monitoring, hangouts Noe has to run its own process that I've never seen before and after a minute it caches itself, and I guess the cache is dumped later since I haven't opened hangouts in 5 minutes, I have to restart the app every time I need to use it. I also don't receive any messages during that time because the app has been killed. Any ideas?
chabsie said:
I am having the same issue with hangouts. I've taken the same steps to try to fix it.
As part of troubleshooting, I momentarily disabled hangoouts via app settings, then I started to see the "Google App" error. After re-enabling I didn't see this error anymore.
I have not tried removing hangouts completely, as it seems this would break other things.
Any possible solutions?
EDIT: The Google App error is actually persisting.
Click to expand...
Click to collapse
POSSIBLE CAUSE AND SOLUTION
After spending 2 entire days on it and flashing the 5.1 factory images 3 times, I found out that it was being caused by LBE Security Master's Active Defense mode. This like a live AppOps. It grants/denies permissions to apps at run time. Even though I had given full permission to Hangout, it was still crashing for unknown reasons. But after I disabled the active defense mode and rebooted the device, everything is running fine now.
So, if you are using any permission control app like LBE or AppOps, try disabling that and reboot your device. Yes, reboot is necessary. Just disabling doesn't fix it.
bagarwa said:
POSSIBLE CAUSE AND SOLUTION
After spending 2 entire days on it and flashing the 5.1 factory images 3 times, I found out that it was being caused by LBE Security Master's Active Defense mode. This like a live AppOps. It grants/denies permissions to apps at run time. Even though I had given full permission to Hangout, it was still crashing for unknown reasons. But after I disabled the active defense mode and rebooted the device, everything is running fine now.
So, if you are using any permission control app like LBE or AppOps, try disabling that and reboot your device. Yes, reboot is necessary. Just disabling doesn't fix it.
Click to expand...
Click to collapse
Actually I'm using LBE as well and I suspected that it could have been the cause, and as you experienced, I removed all restrictions from the hangouts app and the problem still persisted.
My theory now is that a restriction that we've set on another app (or apps) is indirectly causing this issue with hangouts.
Does anyone know specifically which system apps could be connected to the functionality of Hangouts?
UPDATE: I've disabled restrictions on Youtube, Calendar, and Drive. This appears to have solved the problem.
Hangouts is working normally thus far and I haven't seen any error messages. Will update if things change.
I have a feeling that it's Drive.
What s
Is LBE? I'm stock phone sideloafed 5.1 and I have actually disabled hangout prior to upgrade now getting this error
Lee
Google play services "keep awake" disabled could cause it
I let all my apps keep awake in app ops and so on, but still have an issue with hangouts. It gets killed by system 5-10 minutes of not using it even if I leave it in background
2nd Update:
The problem is persisting again... my hypothesis has been disproved.
Any other suggestions or discoveries would be appreciated. I'm trying to find a way to fix Hangouts while keeping privacy settings in place as much as possible...
If XPrivacy was working for Android 5.0+ this issue would disappear.
I re enabled hangouts and updated it and not had the issue since
Play Service 7.0.96 from http://www.apkmirror.com/apk/google-inc/
Hangouts (+LBE) works fine by 5.1
Nexus 5 32GB, Android 5.01
Hangouts crashes occasionally for me also, and I don't have LBE or anything. I sideloaded 5.1 via nrt but my play services still says 6.7.76. Is that going to be a problem? Won't it just update itself eventually? Does the image not contain play services?
(I have the N6 but I thought the issue would still be relevant)
I had a similar issue, so I rolled back hangouts to 2.5x and it's working fine now, YMMV. of course this may not be a viable solution to you but a working older version is better than a non-usable latest version.
Cheers!
Well, the only thing I can think of, in my circumstances, is that I had hangouts disabled when I updated to 5.1 (I don't use it). So yesterday I enabled it, cleared data, and disabled it again, and so far no crash. Maybe something got changed in the update and it didn't like the fact hangouts was disabled. Again, your issue may vary.
spark001uk said:
Hangouts crashes occasionally for me also, and I don't have LBE or anything. I sideloaded 5.1 via nrt but my play services still says 6.7.76. Is that going to be a problem? Won't it just update itself eventually? Does the image not contain play services?
(I have the N6 but I thought the issue would still be relevant)
Click to expand...
Click to collapse
The new play services pretty much renders your phone useless due to nonstop update wake lock, (read more on the cataclysm ROM thread, like last 30 pages). The only way to fix the wake lock so far is to flash the cataclysm ROM patch (idk if it will work with stock ROM but it should) and it blocks the wake lock.
See attached picture below, that's how bad the new google play services is.
As for hangouts I got UKM and lowered the low memory killer to a minimum and disabled laptop mode (I'm using elementalX) and hangouts works just fine for me now.
russian392 said:
The new play services pretty much renders your phone useless due to nonstop update wake lock.
Click to expand...
Click to collapse
Sounds like I should stick with what I've got then! Though having said that I think gp will update automatically when it's released, being a core system component?
spark001uk said:
Sounds like I should stick with what I've got then! Though having said that I think gp will update automatically when it's released, being a core system component?
Click to expand...
Click to collapse
Yes, it would.
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.
Can anyone help me figure out why Google Messenger is showing all my contacts as Unknown Sender. Everything works fine if I use Textra or the native sms app. I'm using an Honor 8.
The exact same thing just started happening to me with my Honor 8. I don't know what caused it. I'm on the 7.0 EMUI 5.0 Official build, and it just started happening last night
nedthehead said:
The exact same thing just started happening to me with my Honor 8. I don't know what caused it. I'm on the 7.0 EMUI 5.0 Official build, and it just started happening last night
Click to expand...
Click to collapse
I tried reinstalling it but it still persists.
It also stopped working for me with the update to 7.0. Extremely annoying considering its my go to SMS app and I can't stand the stock one :/ Considering a factory reset...Unless anyone knows of a fix. I've played around with every permissions setting and have zero luck thus far.
I've had this happen to me too. It's very frustrating. I'm considering a factory reset, but would be even angrier if that doesn't fix the problems. In addition to every conversation switching from "Unknown Caller" is that the keyboard or reply option is completely gone. I had to switch back to the native app.
Other issues I have with EMUI are that Google Camera doesn't work, although I heard that Google is only allowing that to be installed on Nexus devices. It doesn't show up in a Playstore search anymore. Attempts to side load it have failed.
Another issue I have is that the Email app won't dismiss the unread count bubble all the time. It seems to be intermittent. A reboot or several hours clears this issue up for awhile.
(Sorry for multiple bug reports in this thread, but Google Messenger not working is really bothering me most.)
I have had the Note 8 for about 2 weeks now and earlier this week I just started noticing the freezing problem with the contacts and messages application. I have tried clearing data/cache. I have tried going into safe mode and removing third party apps. I have factory reset my phone as well. I have noticed that holding the contact down to select it will work, but simply tapping it freezes the phone. This goes for both the default messages and contacts apps.
korakesion said:
I have had the Note 8 for about 2 weeks now and earlier this week I just started noticing the freezing problem with the contacts and messages application. I have tried clearing data/cache. I have tried going into safe mode and removing third party apps. I have factory reset my phone as well. I have noticed that holding the contact down to select it will work, but simply tapping it freezes the phone. This goes for both the default messages and contacts apps.
Click to expand...
Click to collapse
The contact app is the same for both messaging and phone. It's a stand alone app. I've seen a few people with this issue, and am curious what causes it. I have had no issues with my so my guess is it has something to do with your setup.
Take a look at the below and see if any work
1.) What version of Contacts is in stalled on your phone?
I'm running v 3.4.04.4 Contacts and v 1.0.01.25 contacts storage. If you are not on either of those go grab the APK from APK MIRROR
2.) Check your account settings
Start with you Google account and see if there is a sync error. If not there then check Samsung cloud. If not there check your sync settings in the contact app. If there is any issue syncing it could be causing the crash.
3.) see if all of your contacts cause it to crash or just a specific one.
It could be an issue with something one app is trying to add to your contacts. I've seen linked in cause contacts to crash, and I've seen Facebook cause contacts to crash. If either of those are syncing with your contacts (check permissions) they could be causing the issue.
4.) Finally back on my S7 edge for some reason the contacts sync got jacked up when moving from my Note 4. The only thing that fixed it was running this app (https://play.google.com/store/apps/details?id=ru.ivary.ContactsSyncFix) Haven't had an issue since.
If any of these work let me know so we can help spread the word. Thanks.
korakesion said:
I have had the Note 8 for about 2 weeks now and earlier this week I just started noticing the freezing problem with the contacts and messages application. I have tried clearing data/cache. I have tried going into safe mode and removing third party apps. I have factory reset my phone as well. I have noticed that holding the contact down to select it will work, but simply tapping it freezes the phone. This goes for both the default messages and contacts apps.
Click to expand...
Click to collapse
Hi. I had similar problem. Try find solutions on web, none. Complaint to samsung facebook, no response. So I decided to;
1. Do System Update... but it says I have the latest installed already.
2. Open PlayStore, found out I set Auto Update to OFF. So I manually update everything (except Games apps)
3 Open Galaxy Store also Auto Update turned OFF. So do manual update everything (except games again)
4 Restart Phone
Dont know which steps solved it, but I dont have issue with Contacts or Message anymore. Its been more than 3 days now... no issue. So I guess you can try the above and see if it helps.
Its started to happen to me but while im in a game not on the phone or messenger.
frome901 said:
Its started to happen to me but while im in a game not on the phone or messenger.
Click to expand...
Click to collapse
If it's in game and not the contacts app try adjusting your performance mode in Gamer Tuner.
If it's not that then the game is probably the issue.
ShrekOpher said:
If it's in game and not the contacts app try adjusting your performance mode in Gamer Tuner.
If it's not that then the game is probably the issue.
Click to expand...
Click to collapse
Sorry for the late post it was the sync to the samsung back-up server i turned it all off since i don't much of the samsung stuff and haven't had any issues since
frome901 said:
Sorry for the late post it was the sync to the samsung back-up server i turned it all off since i don't much of the samsung stuff and haven't had any issues since
Click to expand...
Click to collapse
Try the app I used in my for suggestions. Pasted below. It fixed any issues I had.
4.) Finally back on my S7 edge for some reason the contacts sync got jacked up when moving from my Note 4. The only thing that fixed it was running this app ( https://play.google.com/store/apps/details?id=ru.ivary.ContactsSyncFix ) Haven't had an issue since.
https://play.google.com/store/apps/details?id=ru.ivary.ContactsSyncFix
ShrekOpher said:
Try the app I used in my for suggestions. Pasted below. It fixed any issues I had.
4.) Finally back on my S7 edge for some reason the contacts sync got jacked up when moving from my Note 4. The only thing that fixed it was running this app (https://play.google.com/store/apps/details?id=ru.ivary.ContactsSyncFix) Haven't had an issue since.
Click to expand...
Click to collapse
Not that i need it since shutting off the Samsung syncs worked for me but your link is no good
frome901 said:
Not that i need it since shutting off the Samsung syncs worked for me but your link is no good
Click to expand...
Click to collapse
Thanks should be fixed now. Definitely a helpful app
https://play.google.com/store/apps/details?id=ru.ivary.ContactsSyncFix