After taking update I got excited. Loved the theater mode and different watch faces. However two days in I'm having issues.
X1 remote will no longer work.
Gmail, hangouts, etc notifications are no longer working, rarely will get notified.
Also android wear app has issue forgetting and reconnecting to watch. Have to reboot watch to get it synced. Watch will not display the cloud with slash symbol and will act like it's connected to my phone even tho it's not online. Then after launching voice search it will finally say off-line.
So what should I do? Reset? Roll back to kitkat?
I have read some people with phones running lollipop that they aren't used to priority notifications. But my lg g3 is on kit kat so that's not my issue here.
Sent from my Verizon LG G3 using Tapatalk
jfriend33 said:
After taking update I got excited. Loved the theater mode and different watch faces. However two days in I'm having issues.
X1 remote will no longer work.
Gmail, hangouts, etc notifications are no longer working, rarely will get notified.
Also android wear app has issue forgetting and reconnecting to watch. Have to reboot watch to get it synced. Watch will not display the cloud with slash symbol and will act like it's connected to my phone even tho it's not online. Then after launching voice search it will finally say off-line.
So what should I do? Reset? Roll back to kitkat?
I have read some people with phones running lollipop that they aren't used to priority notifications. But my lg g3 is on kit kat so that's not my issue here.
Sent from my Verizon LG G3 using Tapatalk
Click to expand...
Click to collapse
Uninstall android wear app, reset android watch. Re-download android wear app from play store, re-pair watch with app. Start fresh...
Sent from my LGLS740 using Tapatalk 2
Another bug is the voltage between pins on lollipop (we lost the lg fix), that causes deterioration; and while theater mode is activated, the alarms will not vibrate.
I didn´t have any problems with gmail, hangouts, or disconnections.
Today no issues after following reset and reinstall instructions. I have been able to receive vibrations with theater mode.
Will research this deterioration thing. Haven't heard of it.
jfriend33 said:
Today no issues after following reset and reinstall instructions. I have been able to receive vibrations with theater mode.
Will research this deterioration thing. Haven't heard of it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/g-watch/help/update-solving-corrosion-how-detect-t2880710
We´re researching about this, maybe it´s not a bug really.
Wish I could stop this battery use from Google fit. It's disabled.
I obviously can't complain about battery life. I get 3 or 4 days easily with it turned off at bedtime, always on screen disabled,and brightness at 1.
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
Just noticed my watch is downloading a system update, ut has paused as battery is too low, I am already on the December Patch, is this just a security patch or something else?
Wear OS 1.0 with the February security patch.
I look on the internet and see it keeps saying the lg watch style having the Wear OS 2.0. I look at my watch and it is the Wear OS 1.0. I see listed above Oytsejam1138 mention Wear OS 1.0 with the February security patch. It is bragged about how 2.0 is so much better, that it is such a leap forward. So anyone knows with the situation is? I see they sell them with 2.0, at least that is what I believe I am reading.
Another question but a change of topic. I have the lg g4 h811 phone and the lg watch style. I can use my phone to add to the grocery list or my other lists but the watch cannot through the Google assistant interface. On my watch I have to open the "Keep" app. and choose the list I want to add something to then hit + and one by one add to the list. That is so slow. I grab my phone and say "Ok Google, add to my XXXXX list" and is asks what I want to add. I say something, the app. asks "what else" and I go on from there until I tell it I am done. The question is, shouldn't my watch be able to do that? On my watch I can say, "note to self". My watch (typed text) asks me what I want inside the note to be. I tell it and it saves it in the "Keep" app. I can see them when I open my "keep" app on my watch or phone.
Change of topic again. (I should really make different posts and not compile all this here). Suddenly my watch has started to something. When I open the "Keep" app. it starts to sink and it never stops until I close it and randomly when I reopen it right back up again it is all synced up. Lots of times it never syncs.
Yeah, I'm also wondering about wear 2.0. Just got this along with a Huawei Watch 2 Classic, and I cannot get the watch to update to wear 2.0, event though it says everywhere it is supposed to have it.
I contacted technical and they said to first go into settings of the watch and do an update. I went into Setting./ system / about then chose update. The next step they said in the software in your phone OS to disconnect your watch. Now the next step really did not make sense because they told me to factory reset my watch. Now uninstall the app from the phone and reinstall the latest version. Now lpair your watch with your phone and let the watch update.
My results were bad. My wach went back to when I first bought it and I had to reinstall everything I had on it again. Waste of time. Since than I see my watch updated to 1.1. I don't understand because no where does my watch tell me I am running 2.0... It says Wear OS by Google 1.1.
But it does have Home App 2.11.0. xxxx Are they trying to say the term Home App is the Wear OS? then what does the term Wear OS by Google mean.
Same here Wear 1.1, no updates to Wear 2.0
What the hell? Why is nobody talking about this? Well, except from us.
Edit: I think I figured it out. Wear OS reset and renamed Android Wear. So Wear OS 1.1 is the update to Android Wear 2.0. No?
I think your right. I looked at the Wear OS app on my phone and it shows that it is Wear OS 2.11.0.XXXXX and on my phone that version number matches the information given by my watch as: Home App 2.11.0.xxxxxx. I think the watch Home App is the same as saying Wear OS. and our Wear OS on the watch is what you said, version 1.1 is the same as Wear OS 2.1.0.XXXX. I think our watches are up to date. The terminology is screwy. The watch titles one way and the phone app title's the same thing a different way.
On the watch: Home app 2.11.0.xxx
On the phone: Wear OS 2.11.0.xxx
On our watch: Wear OS 1.1
So I've been trying to connect my m20p to my Huawei W1, every time I get to the bit where it says I need to allow Notifications it just crashes and goes back to asking me which account I want to link and the watch just loops "continue set up on phone"
If I skip the the Allow Notification bit, the watch does pair and I can load apps, so I have linked my account, but I can not get notifications to work...
The watch has just updated to the latest version of Wear OS (though it didn't work with the m20p before that either) and works absolutely fine with other phoes, including a Pixel 2 on Pie.
Getting a bit pissed off with this phone tbh.
I found that clearing the cache & data from the google framework fixed quite a few little issues like this
Hi thanks can you let me know how you did this? I could only find cache?
Did that but it is still crashing as soon as I try to enamel notifications on the setup...
Hi
I fixed the wear OS issue by granting access to notifications to the wear OS application.
In settings search notification access > select notification access > toggle wear OS
Brilliant. Thank you!
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.