Related
Anyone else dying to play Words with Friends on you new Inspire but keeps getting the force close everytime you run the app? I tried rebooting and reinstalling this app but to no avail.
Running on stock rom, waiting for my extra microsd card to arrive so I can root and install custom roms.
Askal007 said:
Anyone else dying to play Words with Friends on you new Inspire but keeps getting the force close everytime you run the app? I tried rebooting and reinstalling this app but to no avail.
Running on stock rom, waiting for my extra microsd card to arrive so I can root and install custom roms.
Click to expand...
Click to collapse
Same issue here on custom ROM, been happening for a day or so since Words with Friends updated. Extra frustrating is the fact that the app resets itself after FC, forcing me to re-enter account info.
Good to know I'm not the only one. I hope we get an update to fix this issue soon...
Working fine here. I had issues when I did the update without un-installing it first but after I did that everything is good. I'm running CM7 if that matters.
I gave up on words with friends and went back to wordfeud. Hopefully the devs of words with friends will get it straightened out soon.
Sent from my HTC Inspire 4G using XDA App.
Aha! I actually tried installing the app again today and it now works. They must have fixed the issue and I'm glad they did.
Words with Friends worked for me on stock ROM since day 1. The first day I rooted and flashed Anrdoid Revolution, I installed Words with Friends and it worked fine. I've seen 1 FC from the app since I've had the phone, but all I had to do was restart the app and it loaded right back to my games
It worked for me for a little while but now it pops up with some wierd web address
Have you tried rebooting and/or installing the app?
Sent from my Desire HD using XDA App
tejas offroad said:
It worked for me for a little while but now it pops up with some wierd web address
Click to expand...
Click to collapse
If you are using Android Revolution(or some other custom ROMs), the hosts file blocks the ads in the app. Either revert to a non-adblocking hosts file or a different ROM.
they just had an update, uninstall words and redownload. i havnt had a fc since then. good luck
even on the latest version, I can't even play! Just force closes when I log in!
Judging by the stack trace I think something in the logon was breaking it. I saw in the stack trace that the app was trying to parse a null value as an integer, which isn't so cool.
I just set up for a packet capture -- but I'm now able to log in again and the game is working fine. Hopefully they don't break their login protocol again, and ideally they make the app a little more robust if the server sends back unexpected data.
I was also getting tons of FC's on custom roms until i ran a fix permissions in CMR. Now it works perfectly
So what do you guys suggest for those who are using unrooted, stock ROMs? Any suggestions?
I go into the apps settings and clear the cache and force close it.. this usually makes it reload the game data which takes a few min, but it works again for me for a while. I do need to tweak the hosts file blocking ads. It causes huge broken ads that make the game unplayable at times.
Yeah when wwf starts acting up again and comes up with a force close (or any bug at all!) all the time, clear your cache and data and try again. Reboot in between if you have to. If that doesn't work, try uninstalling, rebooting and reinstalling again. Sometimes you just need to reboot to fix the issue is what I found out based on my phone. Hope this helps!
So here is what I'm dealing with. A couple of weeks ago apps on my phone kept crashing. I was seeing a constant "Google Play Services has stopped" message and I was completely unable to use my phone. I ended up saying screw it and I did a factory reset.
The problem was still happening after a reset so I figured I should do a full wipe (Dalvik, cache, system, data) and reinstall the ROM (Cyan 11). Unfortunately that still didn't fix the problem.
Since then I've tried everything. I've ran "Fix Permissions" which seemed to work for about a day and then it started again. Sometimes rebooting the phone fixes the issue for a day but it always comes back. It's not always Google Play Services. It seems to be any random app on my phone that starts to constantly crash. Sometimes this happens from the phone's home screen, other times when I go into the app (gmail seems to be a problem more often than not). The phone was also just randomly rebooting, sometimes a few times a day and sometimes when trying to update apps I'll get various errors (package not signed, error 960, etc).
I finally decided that Cyanogenmod might be the problem. I've replaced my recovery (was CWM) but now I have TWRP. I downloaded Paranoid's latest ROM for the S3, did a factory reset, wiped Dalvik, system, data and cache. I also told TWRP to fix the file system in hopes that it would help and then I told it to Fix Permission.
Once I installed the ROM and the Google Apps, phone boots, I sign in....apps start crashing. I'm so lost. I don't know what else to do. Why would a phone that is freshly wiped have problems with apps crashing. This was happen with both Cyanogenmod and Paranoid. I'm running the same version/download of Cyanogen on my gf's S3 and it's been fine. The phone has been rooted since I got it almost 2 years ago and running Cyanogen this whole time. I only switched to Paranoid in hopes it would fix this problem.
Does anyone have any ideas on something I should try? Right now my phone is a pain to use, I'm constantly clearing crash pop ups and then just today it suddenly lost my google account and all my data was gone. No contacts, gmail empty, etc.
Silly but serious question, is play services installed? I've seen several people try to install Google Apps without play services installed and it will give this error without it being installed. I can't produce a screen shot for you as I'm not on a locked bootloader
From my CM11 S3
Well, although I've never specifically installed Google Play Services, it should be part of the Google Apps zip file I'm flashing along with the ROM. This is happening with 2 different ROMs with their respective Google Play App zip files.
I also just checked and it is listed in Apps>All.
rckymtnrfc said:
Well, although I've never specifically installed Google Play Services, it should be part of the Google Apps zip file I'm flashing along with the ROM. This is happening with 2 different ROMs with their respective Google Play App zip files.
I also just checked and it is listed in Apps>All.
Click to expand...
Click to collapse
Alright, I've seen this issue on several different posts. Just a suggestion, it's worth a try at this point.
Try removing play services from the system file, make a backup first. Reboot and then reinstall the backup you made, it should push it back into data/app
From my CM11 S3
Certainly can't hurt. I'll give it a shot this evening and see if it helps.
rckymtnrfc said:
Certainly can't hurt. I'll give it a shot this evening and see if it helps.
Click to expand...
Click to collapse
By chance did you get a moment to try this?
From my CM11 S3
I didn't. I don't know why but the phone seems to be working correctly now. I don't understand why. I didn't do anything but suddenly things aren't crashing. It's been stable for 24 hours now. I didn't do anything so I don't know why but I'm just holding off until I see a crash. Still confused but glad it's working (except my GPS).
I'm honestly afraid to reboot it now. It hasn't worked this well in weeks. Normally I'll open gmail and get a crash 99% of the time. I reboot and it works for a bit but then starts crashing again. Same thing with other apps. Maybe it heard me talking about wanting to throw it out a window and it's got scared. =)
rckymtnrfc said:
I didn't. I don't know why but the phone seems to be working correctly now. I don't understand why. I didn't do anything but suddenly things aren't crashing. It's been stable for 24 hours now. I didn't do anything so I don't know why but I'm just holding off until I see a crash. Still confused but glad it's working (except my GPS).
I'm honestly afraid to reboot it now. It hasn't worked this well in weeks. Normally I'll open gmail and get a crash 99% of the time. I reboot and it works for a bit but then starts crashing again. Same thing with other apps. Maybe it heard me talking about wanting to throw it out a window and it's got scared. =)
Click to expand...
Click to collapse
As long as it works that's all that matters. That is odd that all of the sudden it started just working fine
From my CM11 S3
Yeah, just like how it 'broke'. It was working one minute and then suddenly throwing crashing all over. This phone is possessed. At least I can upgrade in April. If I see the problem return, I'll try the above suggestion and report back.
rckymtnrfc said:
Yeah, just like how it 'broke'. It was working one minute and then suddenly throwing crashing all over. This phone is possessed. At least I can upgrade in April. If I see the problem return, I'll try the above suggestion and report back.
Click to expand...
Click to collapse
I know that feeling, I've soft bricked mine more than once. Thankfully I just recently ditched VZW so I'm not locked down to there phones anymore. I kept my S3 and took it with me
From my CM11 S3
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.
I'm using stock Android 5.0.1 on my G3 on AT&T (D850).
Recently my phone has been really buggy. I was randomly using the web browser and then my phone started freezing up, and then wouldn't load up apps. It restarted itself and when it did half my contacts had no names.
No browser was working so I factory reset the phone but then my problems continued:
-all web browsers will still randomly crash when browsing
- apps will get a "Unfortunately, X has stopped" error. Most common is Google Play Services (which I've uninstalled updates and cache several times) but other apps like Messaging or even Settings can fail
- some apps just won't open over time. They'll work fine but then force close, and then any subsequent attempt to open it will force close it immediately
I still have a month on my warranty but would rather not send my phone in. Do you think that rooting my phone and installing a new ROM would fix these issues? If so which rooting method would you suggest and any suggestions on ROMs would be appreciated
dragonx254 said:
I'm using stock Android 5.0.1 on my G3 on AT&T (D850).
Recently my phone has been really buggy. I was randomly using the web browser and then my phone started freezing up, and then wouldn't load up apps. It restarted itself and when it did half my contacts had no names.
No browser was working so I factory reset the phone but then my problems continued:
-all web browsers will still randomly crash when browsing
- apps will get a "Unfortunately, X has stopped" error. Most common is Google Play Services (which I've uninstalled updates and cache several times) but other apps like Messaging or even Settings can fail
- some apps just won't open over time. They'll work fine but then force close, and then any subsequent attempt to open it will force close it immediately
I still have a month on my warranty but would rather not send my phone in. Do you think that rooting my phone and installing a new ROM would fix these issues? If so which rooting method would you suggest and any suggestions on ROMs would be appreciated
Click to expand...
Click to collapse
Did you perform a factory reset? Try that first.
Sent from my iPhone using Tapatalk
I did two factory resets. Nothing changed
If you are on 21r, I think it is something with the update. My phone went crazy the first go even after factory reset. I reverted back to KK, installed all updates again, and haven't had much issue. Occasionally, something glitches but not a show stopper. I'm thinking the update to patch stagefright is buggy.
Sent from my LG-D850 using Tapatalk