[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.
My Google Play Store Stopped working + google play Games and also facing syncing problem with gmail and calendar , (no issue with internet connection) even after full reset .
also i am not able to add any other google account.
Nexus 5 Android 5.1.1 + rooted + xposed+ default kernel
and today i did clean cyanogen 12 installation but after adding my account this problem arrive again after some time
Have you tried narrowing down the issue, maybe a fresh install (don't root or install Xposed), add your account, run it for a day or two, or at least longer than you know it takes for the problem to occur. Just to make sure it's not an Xposed issue. I've never had issues just with rooting, but it always helps to eliminate any other possibilities.
I've seen something similar to this, and I never really figured it out. I'm using stock image, just root, but my issue was several google sync would not work, like contacts, calendar, and a few others. I tried removing the account and adding it back, it worked like you state, a few hours maybe, then it would have sync errors again. I re-imaged fresh, and I believe when I initially configured the phone the first time, I added my account when it asked instead of skipping it, like I do occasionally. It's been going strong since, but I still don't know if that was a correct "fix"
cyanogen have a setting to remove root access so i did , but the problem still there. i am 80% sure that this is not a root problem .
so i removed my google account but now i cant add any of my google account with my phone (Error -As shown in last screenshot)
i did a fresh start before so again its specifically related to my that google account (as i think)
possible cause of this problem -
1- Latest Stagefright Patch update by google on my nexus 5 (Problem occurs sometime after update)
2- Freedom app , which is used to activate some of my app . i tried this app 2 or 3 days before .http://onhax.net/freedom-iap-apk/
i found one quick solution
i Removed host file from Etc folder in root directory and now problem gone
One question, do you use or previously used an Ad-block app?
yup is that app cause problem?
Sup fellas just posting this from my phone
Basically I rooted it with CFAUTO root I found on a site that seemed trustworthy due to its credibility found on various sites.
Root works perfectly along with Xposed for awhile but eventually a week later every single app will start force closing, or immediately fail to launch on touch. From instagram to KiK to play store itself.
Rebooting is not a good solution as it resolves into a boot loop.
This has been happening consistently for a few weeks. The only solution to get my phone back up and running is to do a factory reset (which in turn means setting everything up again to my preferences. )
This pretty much led me to leave the phone as it comes plus a few common apps and just rely on my iPad more.
Does anyone have a solution? I followed the tutorial down to the T. Video and guide. I'm considering switching to stock but want to see if anyone else had this issue or was able to fix it
I would say to use this guide.
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
Havent tried CFAUTO root, and I dont think its recommended.
I had a similar issue with apps force closing, though I didn't use cfauto root.
The issues I had, after finding out from much trial and error, was that after I rooted my apps would update before Google play services. This would cause problems because the updated apps needed the updated play services to run.
Revert back to stock, then make sure that Google play services is up to date before updating any other app. After play services are up to date, make sure your play store is up to date. Then go ahead and update all of your apps. Next reroot your phone.
Like I said before I didn't use cfauto root, but I hope this helps.
Hello,
Since about a couple of weeks ago, the Play Store started getting really slow. Updates get stuck at "download pending", and sometimes they do download. Other app downloads get stuck at 100% downloaded for a long time before installing. I can leave my phone on updating all night and in the morning it is still not done. This happens both on LTE and on Wi-Fi, and I do have very fast Wi-Fi. I am on the OxygenOS Open Beta 10. I did not do any changes to my phone when this started happening.
I have tried all of the following to fix the problem, but it doesn't help:
Rebooting the phone
Uninstalling Play Store updates
Deleting and adding Google Account
Clearing cache
I tried wiping the phone and using OxygenOS 9.0.2 - same problem.
I have clean-wiped the phone, deleting even internal storage, and flashed OxygenOS clean stock, and still it does this. (it also has new problems, like Magisk doesn't offer root authorization anymore even though it installed and working according to Magisk Manager...)
The only way I could get the Play Store to work properly was to use a custom ROM, HAVOC 2, but that ROM has problems with the front camera in some apps.
It almost seems like the Play Store detects OOS and decides to act funky. Has anyone faced this problem, or resolved it? Should I contact Google and see if the problem is their Play Store?
I almost feel like, since I have tried with clean wiping and using stock ROMs, and things that weren't broken before just started breaking for no reason, that there is a problem with the hardware itself. It makes no sense that the problems carry over into stock ROM when I have wiped everything several times.
Uninstall or disable the google app.
That fixed it for me.
Let me know if that works.
So, Some days ago, out of the blue I was trying to pay with google pay and an error "you no longer can pay at store with google pay" came up.
Then I check payment methods, tried to change for other and found the error that google pay wont work on my phone since is "modified in some way"
I have 100% stock room, with magisk root. I did not installed anything recently, not even updated google pay app recently.
Anyway, I read some guides, found that my phone did not pass the SafetyNet Check. cleaned data from google play services and google play itself. run the test again and now it says true (pass) and my google play says device certified, but still no luck with google pay. I hided root for that app and other google apps just in case, cleaned data, but still says same error.
Any thought? Something that I could try?
thanks!
I had the same problem, ended up fixing it by switching to Magisk Canary release channel. AFAIK the fix has not been released in stable Magisk yet.
I can confirm that Magisk Canary Channel (v19003) fixed this issue for me on OP6.