[Q] Location Services Error - Galaxy S II Q&A, Help & Troubleshooting

Sometime in the last week or two, my location services have completely gone away. On Maps, I get "waiting for location" and then "Your current location is temporarily unavailable." When I go into GPS Status, there are no satellites seen. Both satellites and Google location services are activated.
When I do a complete wipe, functionality comes back. Immediately after reinstalling my apps (without restoring data), functionality is still there, but after a short time the problem resurfaces. I haven't determined if it is an app or if the problem occurs after a service starts.
The only things that occurred prior to the problem resurfacing were the passage of time, opening several apps that require root - including SetCPU, SD Maid, AdFree, BatteryCalibration, and Titanium, and the receipt of 2 phone calls.
Is there any way, short of freezing/uninstalling apps and services one at a time, that I can figure out what's doing this?
It happens with both CM7 and CM9 nightlies.
Thanks.

hmmm, looks like a bug found its way...
anyway have u tried using fasterfix from the play store

try this
http://forum.xda-developers.com/showthread.php?t=1447599

Related

[Q] Anyone else getting terrible Google Services wakelocks on JB?

This started around the time I wanted to check and see if my GPS was still working after the update. I went through the hoops to get google maps to be able to use the GPS and it was working fine. But shortly after, I noticed excessive battery drain, and BBS showed me that my phone was not sleeping at all.
I am now seeing 3 partial wakelocks from google services framework: Checkin Handoff, Event Log Handoff, and SystemUpdateService.
Tried several of the usual things to track it down and in the process I'm seeing some oddities:
1. Using autostart manager, I unchecked the checkin and SystemUpdate-related autostarts for Google Services Framework, but they won't stay disabled. Generally speaking, the autostart manager is working - other receivers stay disabled.
2. Settings -> Accounts & sync -> Google -> Maps & Latitude brings up a location settings screen in maps. This has an option for Automatic check-ins which is checked. I un-check it, it says in a toast message that it saved, but if I exit out and come back in, it's still checked.
I'm thinking those two issues are caused by the same thing that's keeping these wakelocks going. Any ideas?
Oh, also, the only checkin-type message I find in logcat is this (repeated often). Indeed, there is no /data/data/com.google.android.gsf/.checkin.CheckinService - should there be?
04-11 09:46:28.412 W/ActivityManager( 553): Unable to start service Intent { cmp=com.google.android.gsf/.checkin.CheckinService }: not found
[Q] do you have /data/data/com.google.android.gsf/.checkin.CheckinService?
Answering myself trying to change the thread title.
Someone who has stock JB, please check and see if you have the abovementioned file. If so can I have it please? (or if it's data I'd like to know what goes in there).
Made a little progress.
I was actually able to disable the autostarts using "Autorun Manager" instead of "Autostart Manager". I'm not sure exactly why unless it is because these autostarts have $ characters in them.
This makes the wakelocks go away.
I'm still curious why I can't turn the setting off in maps and whether the 'not found' error is anything important.
Exactly the same issue (although mine is an S3 running Omega Rom 4.1.2).
Constant Wakelock for 3hrs 36m all of a sudden (seen with Wakelock Detector). Used "DisableService" app to disable all sub-services under Google Services Framework. Play store seems to still work OK.

[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

S2 GT-i9100 Google Play Services randomly causes *unimaginable* battery drain

Hello Everyone
Start off by saying I have little to no Android knowledge (rooting, custom ROMs, modding or programs for such things), however I have basic knowledge of linux and the command line.
My S2 GT-i9100 rapidly heats up and its battery is *unimaginably* and randomly depleted by Google Play Services and quickly renders it useless as a device. I want to fix it and not turn it into a brick.
I got the phone from a family member from Europe (I live in Australia), who had used it for about 6 months. When I got it, it was already unlocked and rooted by some phone place over there. I didn't have any problems.
Recently however Google Play Services (size 127 MB) has randomly started doing *something*, this despite no mobile broadband and almost no internet usage from wifi either to invoke it. Considering it is on ICS (no idea how to upgrade, or whether i should upgrade, or what to upgrade to) it has to be either a bug or a virus considering all those Android exploits in the news recently.
To fix it whenever it occurs, I clear the RAM twice then go into the list of Applications and Force Stop Google Play Services (more than once if the button isn't greyed out).
I tried to disable the components of Google Play Services(listed below) but the problem continued AND it erased the names of my contacts meaning I was left with a bunch of numbers with no name.
Google Bookmarks Sync
Google Play services
Google Services Framework
Google Account Manager
Network Location
Google Contacts Sync
Some details:
Wi-Fi use only (and nonexistent nowadays), no mobile broadband
GT-i9100 running Android 4.0.3 (ICS)
ROM, unknown if original / custom, has a T-Mobile animation screen on bootup and shutdown
It also has a yellow triangle at the bottom when I turn it on (don't care about cosmetics)
Rooted with CWW (no idea about how that works or what it means) and SuperSU (i do know how root user works in linux)
Root Browser + Terminal Emulator installed (my doing)
Google Authenticator + Microsoft Account Authenticator (i don't wanna screw up anything with these, got codes for google authenticator, need to research microsoft)
Call history and text messages (I would like to keep these and would like to know how to backup the phone first of all)
So I'm looking to figure out what would be the best course of action to fix this without screwing up anything. I know the standard solution would be a factory reset but I don't have any backups (also don't know how to), don't want to brick the phone and don't know what it would actually do, and even if it worked, how to root the phone again.
Any help would be greatly appreciated.
Hi,
i had the same massive battery draining. Problem was Google Fit App. After uninstalling the app the battery draining is gone. I think this app prevented the google services to fall in "doze" mode. Perhaps you have a similar app!?

Problem with Firebase based apps

After spending some time developing applications, I made an application that makes use of O's notification channels. I used Firebase's job dispatcher to schedule the notification firing service. The first time I deploy the application on my smartphone (I believe I had a mistake there), I suddenly saw that Google Play Services crashes, the app crashed and the whole system rebooted shortly.
When it booted up again, weird things started happening like launcher crashing and restarting a couple of times, various applications crashing for no reason (I believe they're related to Google Play Services, or Firebase? dunno) so I thought that my (only thing) google-play-services related code concerning the service scheduling had to do with it, I deployed a new build that just cancels the service with the same service tag used.
Everything seemed fine, for the crashing mania stopped and everything was less frustrating, and finally I could open Settings > Apps again without crashing the Settings app. But lately it started happening again with google play services, I got mad and uninstalled the application causing the problem, but now any application that uses google play services crashes on start and are unusable at all. My phone is semi-usable and this is disgusting right now.
I'd be glad if anyone could help me fix this problem either with Firebase job dispatcher, Google Play Services or the whole system/phone with the least losses as possible.

Categories

Resources