Has anyone had any issues registering within the ChatOn app? I am able to get my verification code via text msg (which is automatically filled in and skips to next step), but when I enter my name I get an endless "Waiting..." progress meter. (Trying to register through the website only refers me back to the app.)
I tried this over LTE and wireless without any success. I did notice the keyboard icon in the notification bar, and the notice says "Ongoing: Select input type" (or something similar), so I wondered if it got stuck on that step somewhere. I do select my keyboard there (Swiftkey) without any result.
I've also tried using the default Samsung keyboard, but same thing.
Have you tried to uninstall and reinstall the app?
Tutsumi said:
Have you tried to uninstall and reinstall the app?
Click to expand...
Click to collapse
Yep, I did that a few times. But I forgot that this is no longer an issue. Shortly after posting the thread, the I was able to complete the installation.
I've since disabled the app. I was under the impression it was a catch-all messenger, not that it required setting up on other peoples' phones too. I really just wanted to have something that I could both MSN in general and BBM my sister (who's stuck on BB).
Thx
Here my problem: a few weeks ago Commandr was introduced here on xda. I've tested it and everything just worked fine. Then, the developer made an update so you don't have to use "Note to Self" anymore with using Androids Accessibility option...this broke the "Ok, Google" feature. It seems that it's not easy to repair that.
First, I turned the Accessibility option out, uninstalled Commandr, set Google Search back to factory version - it was just not working. The option was still in the menue of the Search app, but it was not shown nor just even in the App and in the Search widget (Nova Launcher, "Ok, Goolge" turned on). So I've made a complete backup of everything (with Titanium, except Search and Commandr, then coppied the internal memory to computer, at least /storage/emulated/0), whiped everything with TWRP and installed latest firmware (LG G2, D80220f). After installing "Ok, Google" worked just fine again, what I expected. So I started restoring. I started with internal storage, so there was no app restored and I stopped PlayStore when it wanted to restore my apps. I had not restored everything from internal storage, only this part, restarted the system for the first time...and "Ok, Google" was just broken again
So I think there has to be something in these folders that stops the Google Search working, but I have no idea what that can be. For testing I erased /Android/data/com.google.android.googlequicksearchbox because I thought there is something that stopped the Search from using the microphone. Nothing changed.
But it's interesting, that sometimes when I quit the Search, the microphone in the Search Widget turns black for a moment as if it would work again, but it doesn't. In the debug settings of the app (opened with Unleash the Google) in the config flags under hotword_supported_locales, de-DE is listed, so I should be able to use it because this locale is which I need and have.
Does anybody knows help?
Interesting. Went back to D80220D, "Ok, Google..." just working fine. Reinstalling Commandr, same problem. Thankfully I hade an TWRP-backup.
Any idea to this behaviour?
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
So basically the problem is that when I try to train Google Assistant voice recognition, at the screen where it asks me to say OK Google, I can say it however many times I want but it just won't recognize the phrase. The recognition does seem to work when I simply launch the search and use the phrase. It doesn't let me train it though. What's weird enough is that there's a screen which gives me options to remove the existing voice model and retrain it, both of which aren't greyed out indicating I can press them, but when I do - nothing happens.
Now I'm using OnePlus 6, and I've just updated to OOS 10.3 (i.e. the newest android) and this seems to be when the problem has begun, however, it's been pretty long since I trained it before, so it may not be connected.
Either way, I tried all the possible solutions I found online, especially on Google's Support forums, namely:
1. Rebooting the phone - didn't work.
2. Clearing cache and app data of the Assistant and Google - didn't work.
3. Reinstalling Assistant - didn't work.
4. Logging the phone remotely via Google's settings on PC, and removing the voice models from there - didn't work.
5. Logging out of Google and logging in again on the phone - didn't work.
Please help. The Google Support forums are absolutely useless.