"Unfortunately, Google Play Services has stopped" - Google has abandoned older phone - Android Q&A, Help & Troubleshooting

"Unfortunately, Google Play Services has stopped" - Google has abandoned older phone
So, just Google this error and you will find no shortage of users complaining about this error message.
Heck check out the latest reviews on the Play Store: play.google.com/store/apps/details?id=com.google.android.gms&hl=en_GB
For some it's a couple times a day, for others a few times a hour, for others (like me) it's 4-6 times per minute. Rendering the phone completely unusable because the message locks up the UI. It happens right after a clean reboot, and happens regardless of force stopping/disabling the service! Clearing the data and cache makes no difference for me and the vast majority of users experiencing the problem. Removing all Google accounts and re-synching makes no difference. Downgrading and upgrading the services makes no difference. The only thing that cures it is to completely uninstall all updates to the service and let it ***** about being old, but then every other Google app complains it cannot run because Play Services needs updating. What happened to ethical and modular development standards Google???
I have a Samsung S3 (GT-I9300) running Android 4.3. Kernel 3.0.31-2735602. Build number JSS15J.I9300XXUGNH4. I had this issue on an older ROM and also on a custom ROM I installed in the distant past. The only way I was able to fix the problem was by performing a clean wipe. I am NOT prepared to do that for the 3rd time this year. The phone is perfect for my needs but rendered completely unusable by this devil service called Google Play Services. This service and the way it runs, updates and crashes displays no sense and logic.
Anyone have a de-facto solution for curing this?

I've gone to apkmirror and brought all versions of Google Play, Play Services and Google Apps to the versions they were From Feb 2015 and played with every combination. It makes no difference.

NJ247 said:
So, just Google this error and you will find no shortage of users complaining about this error message.
Heck check out the latest reviews on the Play Store: play.google.com/store/apps/details?id=com.google.android.gms&hl=en_GB
For some it's a couple times a day, for others a few times a hour, for others (like me) it's 4-6 times per minute. Rendering the phone completely unusable because the message locks up the UI. It happens right after a clean reboot, and happens regardless of force stopping/disabling the service! Clearing the data and cache makes no difference for me and the vast majority of users experiencing the problem. Removing all Google accounts and re-synching makes no difference. Downgrading and upgrading the services makes no difference. The only thing that cures it is to completely uninstall all updates to the service and let it ***** about being old, but then every other Google app complains it cannot run because Play Services needs updating. What happened to ethical and modular development standards Google???
I have a Samsung S3 (GT-I9300) running Android 4.3. Kernel 3.0.31-2735602. Build number JSS15J.I9300XXUGNH4. I had this issue on an older ROM and also on a custom ROM I installed in the distant past. The only way I was able to fix the problem was by performing a clean wipe. I am NOT prepared to do that for the 3rd time this year. The phone is perfect for my needs but rendered completely unusable by this devil service called Google Play Services. This service and the way it runs, updates and crashes displays no sense and logic.
Anyone have a de-facto solution for curing this?
Click to expand...
Click to collapse
Just set the location to "Device only" instead of "High accuracy", this stops the error completely until google fixes the issue...
EDIT: BTW, this has nothing to do with older phones, this happens on my Nexus 6...

luizffgarcia said:
Just set the location to "Device only" instead of "High accuracy", this stops the error completely until google fixes the issue...
EDIT: BTW, this has nothing to do with older phones, this happens on my Nexus 6...
Click to expand...
Click to collapse
Thanks but the setting you describe is not present on Android 4.3.

luizffgarcia said:
Just set the location to "Device only" instead of "High accuracy", this stops the error completely until google fixes the issue...
EDIT: BTW, this has nothing to do with older phones, this happens on my Nexus 6...
Click to expand...
Click to collapse
Source?

markus4000 said:
Source?
Click to expand...
Click to collapse
I am using this solution in my Nexus 6 right now... And really, its all over xda... Dont have a specific link right now.

luixffgarcia is right. I have looked everywhere and this was the only thing that solved that problem. Oddly enough, I got a message from Sprint earlier this week saying that if I didn't upgrade to lollipop they would disconnect my service.

Yes guys, there are solutions that work for some people but it's totally dependent on the version of Android. Generally, the older the version of Android (in my case 4.3 running on a Galaxy S3), the less likely any of these fixes are going to work. I do not even have the option that is mentioned above.
In the last few days I've seen the number of 1 star votes for Google Play Services jump drastically.

Well just FYI
I use XPosed on my LG G2 Android 5.0.1 and the module Amplify caused the issues for me. It's not the entire module but some wakelock that I had blocking enabled. This worked previously so it seems like they updated something in their library that would cause it to crash if the wakelock is blocked. For now I just reset Amplify to default settings and I dont have any issues anymore.
Hope this helps.

Related

[Q] Capacity for NFC services full

Ever since the lollipop update, my phone has been getting this Capacity for NFC services full: Not enough capacity to enable to service. Try disabling one or more services. I do not have NFC on, and when i do turn it on the same thing happens. It gives the option to cancel or change service. When i click on change service it goes to setting and says, Unfortunately, Settings has stopped. How do i stop this error?
Same issue here
Hi there.
Unfortunately I don't have a solution but just wanted to let you know that I have exactly the same problem. My Sony Xperia Z2 updated to Lollipop last friday and since then I get this annoying "capaciteit voor NFC-services is vol" message (it's in Dutch ) When I click on 'change settings' a new window is opened where it is not possible to change any setting. Switched NFC on and off but doesn't seem to do anything. The message keeps popping up irregularly...
Very annoying issue. Hope someone finds a solution.
Exaclty the same issue here
Vanaglory said:
Ever since the lollipop update, my phone has been getting this Capacity for NFC services full: Not enough capacity to enable to service. Try disabling one or more services. I do not have NFC on, and when i do turn it on the same thing happens. It gives the option to cancel or change service. When i click on change service it goes to setting and says, Unfortunately, Settings has stopped. How do i stop this error?
Click to expand...
Click to collapse
Unfortunately I am also haveing the same issue. It's very annoying.
Vanaglory said:
Ever since the lollipop update, my phone has been getting this Capacity for NFC services full: Not enough capacity to enable to service. Try disabling one or more services. I do not have NFC on, and when i do turn it on the same thing happens. It gives the option to cancel or change service. When i click on change service it goes to setting and says, Unfortunately, Settings has stopped. How do i stop this error?
Click to expand...
Click to collapse
Try Factory Reset
There must be a better way than just a factory reset, and not sure if that would actually solve the issue.
Just chiming in that I updated to Lollipop on my Z3 last night and am encountering the same issue.
dreamoo said:
There must be a better way than just a factory reset, and not sure if that would actually solve the issue.
Just chiming in that I updated to Lollipop on my Z3 last night and am encountering the same issue.
Click to expand...
Click to collapse
Just got this problem myself this morning on my Z2 running Lollipop. Did you manage to find a fix?
I can't seem to find anything other than this post concerning this issue.
Thanks.
Same Problem
I did a factory restore and I am still getting the same issue.
Same here
I'm experiencing the same thing. Upgraded to Lollipop last month, but this only started a couple days ago. Not after installing a new app. Got low on disk space, which triggered a back up alert. Cleaned out my pics, but then started getting this error.
Xperzia Z3 Compact
Model D5803
Bell Mobility Canada
Android 5.0.2
Kernel version
3.4.0-perf-g72984dd
[email protected] #1
Fri Feb 27 18:06:32 2015
Build Number 23.1.A.0.726
Vanaglory said:
Ever since the lollipop update, my phone has been getting this Capacity for NFC services full: Not enough capacity to enable to service. Try disabling one or more services. I do not have NFC on, and when i do turn it on the same thing happens. It gives the option to cancel or change service. When i click on change service it goes to setting and says, Unfortunately, Settings has stopped. How do i stop this error?
Click to expand...
Click to collapse
I think I figured it out. Suggested a bunch of apps that had bee recently updated on reddit, and the common denominator was the Scotiabank app, updated a few days ago.
Uninstalled, no NFC errors. I have written the dev, and hope for a response soon. That seems to be the cause, so check it out and post if it works for you.
Solution: Clear Google Play Services and NFC Service Data in Safe Mode
Don't know if this is a solution but it worked for me.
1) Boot into Safe Mode.
2) With NFC off, clear all data from NFC Service and Google Play service via Settings>Apps>All.
2.a) Clear data from any Mobile Payment/Banking App and any NFC enabled app.
2.b) Under the running apps, select via the top right dots to view cached apps.
2.c) Delete (Stop) them all. It can be tedious as some won't stop before others but persist and it can be done.
3) Restart phone and error is gone.
thanx, worked for me as well. remainings of android pay caused the problem on my mobile.
Hi Guy !
Same problem here.
Unfortunately no Scotia Bank, noting...
And when i get this message, it says that is current capacity used is.... 0%!!!
I begin to hate this phone :s
Thanks if you have any tip.
Laurent
I've got a Z3 compact that I recently downgraded from LP to KK (no root). Upon booting into KK for the first time, a toast notification appeared stating that the NFC firmware was being updated. After that, the google play services updated and then this stupid "Capacity for NFC Services Full" message kept popping up. It only seems to pop up randomly and only goes away when I disable NFC, but I can't seem to get rid of it using any of the methods mentioned in this thread. Has anyone else ran into this? I've completely wiped my phone twice and continue to have the same issue.
All google searches result in useless forum threads about the Scotia Bank app causing this issue. I don't have that app, so it's gotta be something else.
PuffDaddy_d said:
I've got a Z3 compact that I recently downgraded from LP to KK (no root). Upon booting into KK for the first time, a toast notification appeared stating that the NFC firmware was being updated. After that, the google play services updated and then this stupid "Capacity for NFC Services Full" message kept popping up. It only seems to pop up randomly and only goes away when I disable NFC, but I can't seem to get rid of it using any of the methods mentioned in this thread. Has anyone else ran into this? I've completely wiped my phone twice and continue to have the same issue.
All google searches result in useless forum threads about the Scotia Bank app causing this issue. I don't have that app, so it's gotta be something else.
Click to expand...
Click to collapse
It's caused by latest versions of google play services app. Older versions doesn't have this bug. Uninstall google play services update and "Capacity for NFC Services Full" message is gone forever. But I know It isn't a solution Only google can fix it...
Makiavell said:
It's caused by latest versions of google play services app. Older versions doesn't have this bug. Uninstall google play services update and "Capacity for NFC Services Full" message is gone forever. But I know It isn't a solution Only google can fix it...
Click to expand...
Click to collapse
Yeah, I figured Google Play Services was the issue, but if I uninstall and roll back to the original version the phone ships with, it isn't compatible with Google apps (music, youtube, etc). I was just hoping there was a better fix. For now, I've simply disabled NFC and turn it on before I use Android Pay. The extra clicks aren't really a big deal since I don't have a fingerprint scanner and need to touch the screen to unlock anyway. Plus, I don't use AP often enough to bother me. Thanks for the confirmation though!
Edit - after further thought, if Google Play Services is the cause, then why aren't more people affected by this and why wasn't my device affected all along. I only recently rolled back to KK and this issue started. The Google Play Services version is still the same, right?
As an Android developer who is working on NFC payment in a mobile wallet, I can tell that our team identified the source of the problem to reside in Sony's Android modifications. No other platform produces these errors. I can't yet link the forum thread, but google for "sony xperia off host apdu service capacity full", the result from talk.sonymobile.com will show further details.
So you can probably stop looking for the cause in Google products, or 3rd party wallet/banking apps. They (we) also suffer from this issue.
Sony isn't responding in the referenced thread, so this may not be fixed soon.
Sorry to tell bad news.
my phone has this issue today, it began right AFTER i did a factory reset... just wanted to clear it off and start again... now this??
davidkeithhaines said:
Don't know if this is a solution but it worked for me.
1) Boot into Safe Mode.
2) With NFC off, clear all data from NFC Service and Google Play service via Settings>Apps>All.
2.a) Clear data from any Mobile Payment/Banking App and any NFC enabled app.
2.b) Under the running apps, select via the top right dots to view cached apps.
2.c) Delete (Stop) them all. It can be tedious as some won't stop before others but persist and it can be done.
3) Restart phone and error is gone.
Click to expand...
Click to collapse
The scary thing is this post was made 30-JAN-2016 and it's still being experienced.
Bought a Chinese Refurb Xperia Z3 Compact.
Android 4.4.4
Build 23.0.A.2.98
I'd only installed FTP Server Pro (to test 802.11ac bandwidth) by The Olive tree on an otherwise stock Z3C and after enabling NFC, the "NFC full" error message started popping up.
I followed the instructions above and managed to clear the cache/data on everything except one Twitter service which I couldn't stop.
After a reboot from safe mode, the phone is not showing the NFC error message.
I have enabled NFC and used it with a couple of NFC Bluetooth speakers and NFC tags around the house and it's working without errors.
Fingers cross, I won't see this message again.
Thnx
My Z3 Compact was running Android 5.0.2 since 2.5 years and I never encountered this pop-up. I never used NFC.
I changed to another mobile operator, and as soon as I replaced the SIM in my phone, I started getting this pop-up, saying that the space is 174% used.
I suspect the SIM being pre-configured for Orange Cash, although the application is not installed on my phone.
I tried the various workarounds mentioned in this thread and on Sony's forum, but none worked.
This phone is rooted, and I often get this pop-up when some "sudo" tasks are launched (kill process, freeze application, ...).
I have run out of ideas...
For those who still strugle with this shi* and clearing cache is not working:
1. Download and install any payment app, doesn't matter, won't use. I have Tap & go
2. Enable NFC
3. Go to Touch & pay in device section
4. Change from google play to installed app.
You can now disable NFC, no popup should occure

gapps eating too much

Hello guys
I have an old pronlem -- all the gapps I have tried(slim, pico, delta) are eating too much at all the roms ive used(purity, sultan, orion os, aosparadox, exodus)
Even amplify does not help.
What can you reccomend?
To be precise, its Google Play Services that's eating away at your battery, the recent updates have increased this threshold even more so, I'm pretty blank on how to tackle this, maybe someone else can help.
Joshwin Aranha said:
To be precise, its Google Play Services that's eating away at your battery, the recent updates have increased this threshold even more so, I'm pretty blank on how to tackle this, maybe someone else can help.
Click to expand...
Click to collapse
Well, I have tried almost everything and I can't blame anyone except google for this. Peculiar thing about this is that it happens on mobile data, almost never on wifi. Mobile Radio is active half of the times. You will see google play services, gmail, google app and other google apps in battery stat.
What I have tried so far: amplify, greenify, all possible location combo, blocking alarms, wakelocks, wiping google play services, google accounts, blocking permission to google apps. Most of these things broke functionality .
Solution: Just ignore. There are various threads on google forums,xda and not even a single working solution. If someone finds it, I am keen to try that (unless it asks for my credit card).
saurabh40629 said:
Well, I have tried almost everything and I can't blame anyone except google for this. Peculiar thing about this is that it happens on mobile data, almost never on wifi. Mobile Radio is active half of the times. You will see google play services, gmail, google app and other google apps in battery stat.
What I have tried so far: amplify, greenify, all possible location combo, blocking alarms, wakelocks, wiping google play services, google accounts, blocking permission to google apps. Most of these things broke functionality .
Solution: Just ignore. There are various threads on google forums,xda and not even a single working solution. If someone finds it, I am keen to try that (unless it asks for my credit card).
Click to expand...
Click to collapse
Well the thing is, Google Play Services (GPS from here on out), handles literally everything that Google Apps do on your device, from Geo-Positioning (Maps) to Sync (SyncAdapter) to Emails (Gmail/Exchange) to everything. To put in view, apps that crash on our devices, give a pop up, saying "XYZ apps has stopped working" and gives us 2 options "OK" & "Report", now if you "Report" the error, you'd think the report (and device logs!) go to the developer of the app, Yes ? NO! These are sent to the Almighty Overlords at Google, aside from the data-mining issue here, this just astonished me beyond belief. So that being said, what my personal view is, Google is, like every new Android Iteration, upgrading the old apps to use the Android N-ish architecture & stuff, and maybe, just maybe that this new stuff that's being implemented is better off in Android N, and not in LP or MM. But then again, I might be horribly wrong about all of this
Joshwin Aranha said:
Well the thing is, Google Play Services (GPS from here on out), handles literally everything that Google Apps do on your device, from Geo-Positioning (Maps) to Sync (SyncAdapter) to Emails (Gmail/Exchange) to everything. To put in view, apps that crash on our devices, give a pop up, saying "XYZ apps has stopped working" and gives us 2 options "OK" & "Report", now if you "Report" the error, you'd think the report (and device logs!) go to the developer of the app, Yes ? NO! These are sent to the Almighty Overlords at Google, aside from the data-mining issue here, this just astonished me beyond belief. So that being said, what my personal view is, Google is, like every new Android Iteration, upgrading the old apps to use the Android N-ish architecture & stuff, and maybe, just maybe that this new stuff that's being implemented is better off in Android N, and not in LP or MM. But then again, I might be horribly wrong about all of this
Click to expand...
Click to collapse
Though you are right about first half (can't say much about later part, as I don't understand why it should make google services go crazy )
This problem traces back to Kitkat and probably jell bean but only thing which I do not understand is why only in mobile data ?? I don't see any of them popping up in wifi .
Just when I thought I could ignore it, it started non stop feast on mobile data. I had to stop background data for this. Damn you google.
try A-gapps, it allows battery optimization for google play services (open-gapps etc don't allow this)
it helped me to have less battery drain by google play services
http://forum.xda-developers.com/android/general/gapps-gapps-6-0-1-minimal-t3276606
Yeah... Mine are pretty obese too

Google maps and youtube crash

I have this issue. If those app are greenified, they crash when i open.
Have the same issue 65 views zero answers...
jenaplisken said:
I have this issue. If those app are greenified, they crash when i open.
Click to expand...
Click to collapse
azamet90 said:
Have the same issue 65 views zero answers...
Click to expand...
Click to collapse
Two apps I regularly Greenify on a half dozen different devices running rooted ROMs representing Android 5.1-7.1. No issues to date. Obviously there is a common thread that most Greenify users don't encounter.
Same issue on randomly changing apps any solutions?
I have a mate 10. Periodically since purchase random apps will crash as soon as they are opened rendering them unusable. So far it's happened to google maps, messages, dialler, drupe, calendar and currently google wifi. I'm using an unmodified, standard rom. I've updated, cleared cache, uninstalled apps, soft reset and factory reset with no resolution. As randomly as they start to crash, they stop, could be a day or a month. I see others complaining of similar issues. Has anyone come across a cause or a fix?
kirst3n said:
I have a mate 10. Periodically since purchase random apps will crash as soon as they are opened rendering them unusable. So far it's happened to google maps, messages, dialler, drupe, calendar and currently google wifi. I'm using an unmodified, standard rom. I've updated, cleared cache, uninstalled apps, soft reset and factory reset with no resolution. As randomly as they start to crash, they stop, could be a day or a month. I see others complaining of similar issues. Has anyone come across a cause or a fix?
Click to expand...
Click to collapse
This concern is best addressed in your device forum (unrelated to Greenify).
https://forum.xda-developers.com/mate-10

Long time installation apps

Hi,
After the last update, (965f) I've been struggling for a very long time installing Apps. Whether it's with Google Play or downloaded Apps. Does anyone have experience with it? I apologize for my bad English
That was the first thing I noticed coming from a OnePlus 5T, installing apps is twice as slow on the S9+.
Yes thats true. My S6 Edge and S7 Edge they are much faster then S9+ (but after last update). I dont understand why
****ty NANDs, probably. Anything that pushes the memory is slower - installing apps, copy/pasting, scanning, etc.
Did you enabled McAfee Antivirus on the System Maintenance app?
No, i have disabled McAfee
Solved with Hard reset.
https://forum.xda-developers.com/galaxy-s9-plus/help/slow-app-updates-installation-t3793278/page2
I FOUND A FIX!
I finally fixed my problem you need to disable Google app the white circle with the colorful G in the middle by Google LLC im not sure why it causes this my moms s9+ where i bought from the same samsung store doesnt have this problem hopfully someone can find the root cause of this. Disable Google uninstall any updates and make sure auto update is turned off it fixes all the problems.
Edit: When either bluetooth or google app is disabled this problem doesnt arise. The actual root of the problem was caused by Logitech Bluetooth adapter being in my house I unplugged it and it all went away. I discovered this by finding an issue tracker made to google by a user from a different thread.
Thread available here with 12 pages of posts https://forum.xda-developers.com/gal...3617403/page12
issue tracker available at that thread is here below
https://issuetracker.google.com/issues/77666592

Looking for help running very old & abandoned app on Android 10+

So there's an app I've been using for many years: Simple Checkin for Foursquare
It's essentially a lightweight app/client for the once-popular Foursquare location checkin service.
The app has been abandoned by it's developer and hasn't been updated since 2016. I have searched but have not found another app to replace it (that works) so I still use it.
My daily driver for the past few years has been an LG V35 that's stuck on Android 8. It's actually been a great phone for me which is why I've kept it so long but is really starting to show it's age, some more modern apps are getting noticeably laggy.
I bought a new phone that came with Android 10 and it's good other than this particular app doesn't work at al. When I install (or launch it after clearing data) I'm given a warning that the app is designed for an older version of android and may not work properly before it prompts me to log into the Foursquare service, once that part is completed the app just crashes. Any time I try to launch the app after that it crashes immediately (never even loads the UI).
I've tried this on 2 different Android 10 phones and it's the exact same result. The app works fine on both Android 8 and Android 9.
I'm wondering if there's some kind of workaround for this problem or if I'm really stuck here. I have reached out to the developer of the app and he told me that he's not working on this app anymore and has no plans to update it.
Thanks in advance
Which phone?
The ancient freeware WPS office runs on my N10+'s Android 9 and 10. 10 hasn't caused many issues except it gutted Karma Firewall's valuable logging feature. On Samsung's at least scoped storage isn't fully active and Samsung has greatly modified Q to maintain functionality and the UI.
One reason I'll never load Android 11
Overlay apps generally crash on Q...
Try checking all settings on the app.
Check accessibility permissions, does it need Administrator permissions?
Clear system cache and app data.
Try disabling the internet and see if it loads.
If so then find which app is diming it out and firewall block it.
Try temporarily disabling Google play Services.
Playstore may be another trouble maker.
Try reinstalling it with internet disconnected.
See what apks popup (running services/app cache) when you try to load it as that may give you a clue to the perp apk.
Play with it... may be a dead end or not.
blackhawk said:
Which phone?
The ancient freeware WPS office runs on my N10+'s Android 9 and 10. 10 hasn't caused many issues except it gutted Karma Firewall's valuable logging feature. On Samsung's at least scoped storage isn't fully active and Samsung has greatly modified Q to maintain functionality and the UI.
One reason I'll never load Android 11
Overlay apps generally crash on Q...
Try checking all settings on the app.
Check accessibility permissions, does it need Administrator permissions?
Clear system cache and app data.
Try disabling the internet and see if it loads.
If so then find which app is diming it out and firewall block it.
Try temporarily disabling Google play Services.
Playstore may be another trouble maker.
Try reinstalling it with internet disconnected.
See what apks popup (running services/app cache) when you try to load it as that may give you a clue to the perp apk.
Play with it... may be a dead end or not.
Click to expand...
Click to collapse
Thanks, I'll try that.
FWIW the two Android 10 phones I've tried are a Motorola One 5G Ace and a Unihertz Titan
Try using Apk Export to copy it. This is app I use, freeware.

Categories

Resources