I have developed a Ionic app that uses Android Speech Recognition API via a Cordova plug-in. It worked fine a few days back, but one day it stopped working. I did not change any source code. Sometimes it immediately returns me an error: ERROR_NO_MATCH. Sometimes it worked for one second, gave me one or two words and stopped listening abruptly, regardless that I was still talking to it.
I reflected what has happened in recent days that may have caused problem.
Changes to Google speech recognition server? It is not likely. I did not
find anything about it from the web. But a weird thing is: I installed some other simple voice-to-text apps, they all seem to terminate listening prematurely.
Changes to my computer? I have re-imaged my hard drive and reinstalled everything.
Changes to my mobile phone? Maybe some auto update has affected the voice recognition part.
Anyone has the same problem? Any help is appreciated.
Edit 08/09/2016
What I have tried:
Factory reset of my mobile phone
Building the app with different Android API levels
Uninstalling all updates to Google App, and disabling it
However, none worked.
Related
I'm developing a Spotify-app on Android. The app already runs on Nougat and Oreo, but I'm still having problems with Android 6.0.
The Problem is if I install the app via Playstore, I'm stuck on the loading screen because I don't receive a correct response.
But now, if I install the exact same app from Android Studio, it works without any problems. This also makes debugging very difficult, because I can't use the debugger for Playstore apps.
Do you have any Ideas why? I've got the same problem on all 3 devices that run Android 6.0
I don't really have an answer for that, but I can't even get that far. Which Spotify API are you using? If you're able to get it to get that far, I may have hope haha
An app I published crashes on certain specific devices. I keep receiving messages from the users that just "can't open" the app. This of course lowers the rating on Google Play.
On Android Vitals there's no reference of these crashes, all crashes I receive are managed and happen after the app start, but if I filter for device model or Android version looking for those that tell me that the app didn't open, I find absolutely NOTHING.
I installed crashlytics, and I was astonished by the fact that I received completely different error communications, so Android Vitals seems just partial?
And anyway, still NOTHING about early crashes.
I tried to install the app on the official Samsung online emulator for some devices that are suspected to crash, and still... guess... NOTHING. So I can't even test it and I'm completely helpless.
How can I do to stop this bad app behaviour, that reduces the number of my happy users? I need a really reliable way to detect ALL crashes.
thank you.
Use a Crash Reporting Tool such as Firebase Crash Reporting. Everyone professional uses such tool
https://firebase.google.com/docs/crash/
As already mentioned, you can use a crash reporting tool/framework, additionally you should be aware, that offline crashed might not get reported and if the user doesn't allow you to use the internet, there is no way around that, as far as I'm aware.
In the meantime you could try excluding the devices that you suspect to produce crashed while you are trying to fix it (if you care about the rating).
I have implemented Android Speech Recognition as a service on Android 4.1 & 4.2 recognition solution in my application.
Everything is fine until Android 4.2 OS version, but above the recognition doesn't work. I tested my solution on Kitkat and Lollipop.
The service starts run 2-3 times(i can see the log in the handler), then stops without any error. Here they mentioned about a similar problem, but no solution.
I refreshed Google Play Services to 7.5, but not that is the source of the problem.
Any suggestion is appreciated!
Update:
The suggested solution, to observe if the service runs, just a partial solution, i can restart listen the recognizer with startListening method, but it's not listening at all. I'm considering to use other recognition service, like sphinx. It is so embarrasing, when OS version changes and your app will be wrecked...
I'm aware about the fact, this API is not intended to be used for continuous recognition - as mentioned in documentation.
Today I noticed that offline speech recognition doesn't work anymore.
It worked before because I was able to use it for my app and I'm completely sure that I was offline and everything was working fine then.
I wanted to test my app today and it couldn't understand what I said no matter how loud I said it.
Then I turned the wifi on and it was working perfectly. I'm using the same phone though, sony xperia L, same OS, Android Jelly Bean 4.2.2. I have no idea what happened. Has Google changed something or what? And it's not just my app, other apps that need speech recognition won't work offline as well. Can someone explain this and tell me if there something I can do to get offline speech recognition again, or at least make it work for my app?
Thanks in advance!
EDIT: i've tested it on xperia z2 now and it has the same problem, so it's not only my phone, i believe there was an update with some bugs from google, what do you think?
is it going to be fixed or do i have to fix it?
i want my app to work offline
EDIT 2: i solved my problem by uninstalling all updates on Google App and getting back its factory version.
I'm a fairly new Android developer working on an app that I would like to have speak text that the app supplies. I have found several examples on using the Text to Speech feature on Android phones, such as this one)
and I've been able to get them to work much of the time, but they don't consistently work without problems on the Eclipse Emulator or the HTC phone I use to test. Problems include the speech working sometimes and sometimes not, or the app causing the phone to go to google play to download "SpeechSynthesis Data Installer" even though the phone has already demonstrated the ability to do text to speech and even though the store says that the item is already installed on the phone. I won't go into all the examples of issues but there are several more that I have come across in a few hours.
My question is has anyone put the Text to Speech feature in an app put in the marketplace or on multiple phones and found it to be relatively reliable, simple and straightforward, or is it an unreliable and inconsistent feature no matter how well it is implemented? Thanks.