Doulos Adonai
Newbie
I have been dealing with a repetitive Android/Google Keyboard Speech to Text Bug that has shut down my ability to write longer essays using voice to text while mobile. I had a ZTE Unico phone for 3 years which served to me without problem in writing countless essays while mobile through utilization of voice to text through Google Keyboard. About 2 months ago my texts to my family and readers began to be filled with the words "comma" and "exclamation point". I got complaints and people sending back my texts and documents, not knowing a thing I was trying to say.
After a couple of days of this, I figured out what was wrong. I am writing on Dragon right now flawlessly and while not perfect, Google Keyboard voice to text used to be very effective with just a little bit of solid editing to weed out the misprints where Google (which is actually Android's voice to text unit) did not understand me. I thought it was the phone at first so I switched from a ZTE Unico with an earlier android to a ZTE Lever with android 5.1. The Android/Google Keyboard Speech to Text Bug followed me and that's when I started to ask around and discovered one here, to there, were having the same problem.
In fact, on the forum there was a very helpful gentleman with an SG 4 I believe it was, who was having the Android/Google Keyboard Speech to Text Bug as rampant as my own. He adjusted on his SG 4, the speech rate which I cannot do on the ZTE Lever and his error rate went down to a level he could deal with regarding the voice to text needs he has. Great, but I cannot adjust voice to text speech rate on my phone as that is not an option and I have a much greater need for accuracy with the essays I write. I tried adjusting every possible combination of adjustments on my phone to deal with the Android/Google Keyboard Speech to Text Bug. I adjusted Enhanced Keyboard to Simple Speech Recognition, I even turned off automatic word correction and every other adjustment to no avail, including downloading Flesky keyboard app which was a neat keyboard but it still uses Google Keyboard and Android for voice to text.
For 2 months now, I have not been able to utilize voice to text for any significant writing because of the Android/Google Keyboard Speech to Text Bug. This has shut down my ability to use mobile and I can't afford another phone, which did not help the problem in the first place. If there are any android developers in this forum and any representatives of ZTE mobile phone development, I hope with all my heart that you will take notice of this simple request. Please do something to standardize the response to the word "comma" where the default response on our mobile phones is the punctuation mark "," and NOT the word spelled out "comma". There are even times when it sets the proper punctuation mark in place and as I continue to speak it switches the punctuation mark, which is absolutely correct, to the word "comma" spelled out! Every time I say that word, it is spelled out without exception. It seems like a very simple fix and if I could do it I would, but that is not my realm of expertise.
The other people I have spoken to who have the problem are not writers who compose extensive essays and so they just try to deal with it. I do not have that luxury. In the initial malfunction symptoms of the Android/Google Keyboard Speech to Text Bug, the verbal prompt I had used for years, "exclamation point", was spelled out every time I wanted to set the punctuation in place that these words represent, "!". I never get the correct punctuation when saying "exclamation point" but simply the words spelled out. I read extensively about this issue and one guy switched to "exclamation mark" instead and it began to actually put the punctuation in place and this is currently working for me most of the time so "comma" being spelled out each and every time is my final and completely debilitating issue with the Android/Google Keyboard Speech to Text Bug.
Is there anyone out there who can develop a fix for this issue for us who got hit with it??
After a couple of days of this, I figured out what was wrong. I am writing on Dragon right now flawlessly and while not perfect, Google Keyboard voice to text used to be very effective with just a little bit of solid editing to weed out the misprints where Google (which is actually Android's voice to text unit) did not understand me. I thought it was the phone at first so I switched from a ZTE Unico with an earlier android to a ZTE Lever with android 5.1. The Android/Google Keyboard Speech to Text Bug followed me and that's when I started to ask around and discovered one here, to there, were having the same problem.
In fact, on the forum there was a very helpful gentleman with an SG 4 I believe it was, who was having the Android/Google Keyboard Speech to Text Bug as rampant as my own. He adjusted on his SG 4, the speech rate which I cannot do on the ZTE Lever and his error rate went down to a level he could deal with regarding the voice to text needs he has. Great, but I cannot adjust voice to text speech rate on my phone as that is not an option and I have a much greater need for accuracy with the essays I write. I tried adjusting every possible combination of adjustments on my phone to deal with the Android/Google Keyboard Speech to Text Bug. I adjusted Enhanced Keyboard to Simple Speech Recognition, I even turned off automatic word correction and every other adjustment to no avail, including downloading Flesky keyboard app which was a neat keyboard but it still uses Google Keyboard and Android for voice to text.
For 2 months now, I have not been able to utilize voice to text for any significant writing because of the Android/Google Keyboard Speech to Text Bug. This has shut down my ability to use mobile and I can't afford another phone, which did not help the problem in the first place. If there are any android developers in this forum and any representatives of ZTE mobile phone development, I hope with all my heart that you will take notice of this simple request. Please do something to standardize the response to the word "comma" where the default response on our mobile phones is the punctuation mark "," and NOT the word spelled out "comma". There are even times when it sets the proper punctuation mark in place and as I continue to speak it switches the punctuation mark, which is absolutely correct, to the word "comma" spelled out! Every time I say that word, it is spelled out without exception. It seems like a very simple fix and if I could do it I would, but that is not my realm of expertise.
The other people I have spoken to who have the problem are not writers who compose extensive essays and so they just try to deal with it. I do not have that luxury. In the initial malfunction symptoms of the Android/Google Keyboard Speech to Text Bug, the verbal prompt I had used for years, "exclamation point", was spelled out every time I wanted to set the punctuation in place that these words represent, "!". I never get the correct punctuation when saying "exclamation point" but simply the words spelled out. I read extensively about this issue and one guy switched to "exclamation mark" instead and it began to actually put the punctuation in place and this is currently working for me most of the time so "comma" being spelled out each and every time is my final and completely debilitating issue with the Android/Google Keyboard Speech to Text Bug.
Is there anyone out there who can develop a fix for this issue for us who got hit with it??