• Официальный комментарий
    Avatar
    Deniz K

    Hi Joshua, sorry to hear about the issue you are experiencing.

    First of all, for voice typing issues, we suggest downloading the Google app: How do I use Voice to Text with Microsoft SwiftKey on Android? – SwiftKey Support

    Please also try these troubleshooting steps to see if any performance troubleshooting with SwiftKey helps: Other troubleshooting for Microsoft SwiftKey Keyboard for Android – SwiftKey Support

    As your Microsoft SwiftKey Keyboard utilizes Google Voice technology to power this feature, unfortunately the accuracy of the words generated when using voice to text is not controlled by Microsoft SwiftKey, and not based on our predictions.

    Regarding the feature where you could tap on a predicted word from a drop down menu, this is actually not a feature of your Microsoft SwiftKey Keyboard.
    Действия с комментариями Постоянная ссылка
  • Avatar
    Joshua Angstadt

    I'm not sure how to respond to the "not a feature" part, this was 100% for sure something I could do until last week. If that feature is gone I'll probably stop using the product, that was extremely important functionality to me

    1
    Действия с комментариями Постоянная ссылка
  • Avatar
    Deniz K

    Hi Joshua Angstadt sorry for any confusion caused however the drop down suggestions are not a feature of your Microsoft SwiftKey Keyboard but your OS/device. You may try to check your device/Google app settings for this feature.

    -2
    Действия с комментариями Постоянная ссылка
  • Avatar
    Kevin Freels

    This is not a new problem and you will get a lot of running around because nobody seems to want to address the problem. If you go into your apps and find the Google app, not to be confused with chrome, an uninstall all the updates so you're left with the factory Google app, you're SwiftKey will return to the great keyboard that it always has been in the past complete with the drop-down work suggestions and much better speak to text recognition. I don't know what's going on and why this continues to be ignored or even what if anything can be done about it. I really don't like running my phone with the oldest available version Google. At the same time a properly working speech-to-text is critical to me. So for the moment I am choosing better speak to text over being properly updated. I'm not one bit happy about it. I've made multiple post about this and it seems to me that those posts eventually get deleted. But I keep checking back in the hopes that someone will have a fix for this or at least address it. Best of luck to you.

    6
    Действия с комментариями Постоянная ссылка
  • Avatar
    Joshua Angstadt

    Oh my God thank you, that did the trick. Like you mention I don't really love the idea of using a deprecated version of Google, the functionality he is a high enough priority to me that I'll live with it. Thank you!

    1
    Действия с комментариями Постоянная ссылка
  • Avatar
    Kevin Freels

    Glad to help. It really is a shame that no one will acknowledge this. I don't know if it's specific to Samsung or something else, but either way there is a Huge number of people out there likely getting a very bad impression of SwiftKey because of this. I've been using SwiftKey since it was a non-Microsoft beta product by some company.. I think I Italy although I may be wrong there. Lol So I KNEW something wasn't right. Some sleuthing eventually turned that up and it worked like magic.... Except even with autoupdate turned off it will eventually ignore you and run the update... Every freaking day or so. So your options now are 1)daily uninstall/rollback of Google app update, 2)crappy SwiftKey, 3)leave SwiftKey...... Someone really needs to address this...
    I couldn't help notice the SwiftKey response to you about the dropdown not being a feature of SwiftKey... Lmfao. Really? Um... It's the only keyboard that does it that I know of! It's done it since about year 3 or 4 of the public release. So my confidence that Microsoft will fix the current issue just dropped off a cliff.... They don't even know what features they have!

    1
    Действия с комментариями Постоянная ссылка
  • Avatar
    Kevin Freels

    Wow. Why are replies to comments in a thread where I've already been commenting on AND I solved the guys problem "pending approval"? Do you guys serious moderate every single post?

    1
    Действия с комментариями Постоянная ссылка
  • Avatar
    Deniz K

    Hi Kevin Freels, sorry for any confusion caused. The prediction bar is a feature of your Microsoft SwiftKey Keyboard however not the drop down suggestions you get when using Google's voice input.

    -1
    Действия с комментариями Постоянная ссылка
  • Avatar
    Kevin Freels

    Thanks for the clarification. Would you mind answering a couple questions that are Boggle in the minds of thousands of people? With these unanswered question out there at least to a lot of speculation which I don't think is positive. It would probably be a lot better if everybody there was just drink with us and let us know what was going on. If you're up for it, here are those questions.
    1.)For starters, SwiftKey goes a long way back. And it was so good that Microsoft bought them. They had an excellent speech to text database before Google head even started on one. Since Microsoft purchased SwiftKey it would seem that Microsoft would have additional resources they can throw at it that this other company did not. So why in the world does Microsoft rely on Google beat recognition instead of its own? That database is the one that people get SwiftKey for in the first place. If I had to guess, just due to the wide variety of sounds generated by human beings speaking and minor differences in the code, speech to text would be a price where one product works better for some people and the other product works better for others. Even if you didn't feel that speech to text was better, it doesn't matter. It would at least be different but instead you have it running off of Google speech to text which then means to me I'm going to get the same thing regardless of which program I use. Call reason I want to use with keys because I don't like there's. Maybe it is "better" overall. But I don't care about overall. I want better for me..

    3.) If I understand you correctly and please forgive me if I'm wrong, but what you're saying is that basically SwiftKey throughout speech to text and instead Simply Connected to Google to provide that feature. As stated at the top of the post where someone mentioned all the problems and then I told them to roll back the Google app and sure enough when I did get fixed it. So I have seen a number of people on multiple message boards keep saying the same thing and many of them are asking the question why doesn't Microsoft control this? Again please correct me if I'm wrong but I'm fairly certain there are other keyboards out there that don't lean on Google. So why is the biggest competitor to them leaning on Google? Like when I'm running a race I don't want to put my head on the back of guy's chest in front of me I want to beat  him.

    4.) I want to leave you with an idea that would make SwiftKey the be-all and end-all of keyboards. Nobody would ever want anything else and the idea is simple. You set up SwiftKey in such a way that it can connect to its own database the new Google, the old Google , or a third-party. Again, the reason I say this is because different people get better results out of different speech to text I can only imagine what it'd be like to get a keyboard that I like but be able to connect as SwiftKey already does is a Google speech to text or to a few others, or just enlarge the screen automatically. That would be so incredible that the only people that would end up keeping anything else will be people who are technologically week and uncomfortable messing with settings. Inquiring minds want to know

    1
    Действия с комментариями Постоянная ссылка
  • Avatar
    Deniz K

    Hi Kevin Freels thank you for your reply and for your feedback.

    I am sorry to hear that you are not happy with voice typing at the moment.

    Currently, there is no other voice-to-text provider available however I would suggest you to submit your idea as a feature request via https://aka.ms/sk-support. This is so we can keep track of requests. 

    I've also passed your feedback on for further evaluation.

    -1
    Действия с комментариями Постоянная ссылка
  • Avatar
    Kevin Freels

    Wait. What?
    As I said above, this keyboard was available the before Google speech to text API. But you might want to be aware if there is this a company out there that is a direct competitor of Google on quite a few things that was working on speech-to-text since before SMS was cool and Google was in diapers. had a search engine. They provided speech to text and this operating system called Windows XP. And they've gotten much better since then. They now have several apis available. One of them is called Azure. Another is called ping speech but I believe that was actually put back as being old. They also on another company that I don't know how long has been the gold standard in speech to text recognition. That company's name was Dragon, the makers of "Naturally Speaking", perhaps the best speech to text recognition software ever made. Am I ringing any bells? But if you have trouble finding someone who works there oh, I guess you could always step out and maybe check out IBM Watson, Amazon Polly, and even Twilio and Nexmo. I think there's another half dozen or so more.

    But thank you. That response just made my day.

    2
    Действия с комментариями Постоянная ссылка
  • Avatar
    Deniz K

    Hi Kevin Freels my reply refers to that currently, there is no other voice typing input available as another option as Microsoft SwiftKey Keyboard utilizes Google Voice technology to power this feature. Please do submit a feature request via https://aka.ms/sk-support if you would like to see other options.

    -2
    Действия с комментариями Постоянная ссылка
  • Avatar
    Kevin Freels

    And I apologize for all the lousy speech to text errors. It works a heck of a lot better when I roll back the Google update to factory, but it appears that they aggressively forced that update down your throathether you like it or not. Turn off automatic updates throw it back not only does it update on its own but the more you do it the more it updates itself during the day and when I hit five times a day just to keep my keyboard working right I gave up. If it is true that you can only use the Google API not something one of those other oddball companies like Microsoft for IBM, maybe the old API can be packed up and installed with the keyboard? I can't tell you that there are quite a few other speech-to-text keyboards out there for my phone and they have various levels of success when it comes to speech to text so I can't imagine these are all using the same engines in databases

    1
    Действия с комментариями Постоянная ссылка
  • Avatar
    Kevin Freels

    If I have to ask Microsoft SwiftKey to use a Microsoft speech to text engine instead of a Google speech to text engine while a great number of people are seriously complaining about the quality of a product that has declined dramatically then they need to hire me as their product manager. It would be absolutely absurd for me or anybody to have to ask Microsoft to use a Microsoft engine instead of a Google engine. If I paid for this keyboard, which I actually did a long time ago when it wasn't free, I would be demanding a refund for the simple fact that I bought a Microsoft product and it's not Microsoft through and through.

    1
    Действия с комментариями Постоянная ссылка
  • Avatar
    Kirsten O'Quinn

    @Kevin Freels I seriously love you, you have just saved me from major pain. I am a chronic speech to texter and this solution actually works! No clue what it'll do to my Google situation but I think it will be worth it. Thank you!

    3
    Действия с комментариями Постоянная ссылка
  • Avatar
    Kevin Freels

    Solving has become my own personal side-quest...... the source of the problem appears to be July 15th 2020 update where I actually found some articles like this one

    https://www.google.com/url?sa=t&source=web&rct=j&url=https://www.bleepingcomputer.com/news/security/google-warns-of-microsoft-swiftkey-losing-access-to-gmail-on-july-15/&ved=2ahUKEwjW5LPJmZDyAhWLZs0KHUy-BUAQFjAdegQIThAC&usg=AOvVaw0IsDQ5cgdVWwl6fsssJs2z

    As I did some more research one thing that popped into my mind was that speech to text and apparently handled by Android as a separate function from the keyboard. So on my Galaxy Note when I go into the setting specifically for speech to text recognition I can choose which engine I wish to use. SwiftKey does not have a separate speech-to-text engine. You're forced to choose Google or on my phone I can actually choose Samsung Speech to Text.

    So it dawned on me that what really needs to happen for Microsoft to release an app that is specifically speech-to-text oriented using whenever engine they used before. It can be Cortana or any of the others I mentioned in a previous post. That would pretty much solve all of these problems. Because some users do have better results using gboard or Google which are separate engines.

    Right now I've been running a full day with an app called AppBlock which is designed as an app that can help you regain control of your life and quit spending so much time on your phone. It allows you to actually block apps from launching even if you try to launch them intentionally. I said the same boat and chose only the Google app the block and set it to block 24 7. And so far the last day Google has not updated end this entire paragraph has been typed with speech to text through SwiftKey with the Google app rollback and so far I haven't even had to correct anything. Only manual typing I've done is paste that link up above. I'm not having any trouble with punctuation, pauses do not cause the keyboard to timeout, everything seems to be very accurate and I'm quite pleased.

    Even using new paragraphs works fine but did not just now trigger a new paragraph on accident and I just said it twice LOL.

    And there was a pause of almost two seconds just now it still got it right.

    Since I've come this far down the rabbit hole I might as well keep going. If I run into anything more I will post it here. In the meantime it would be great if Microsoft would consider creating their own Android speech-to-text engine and Publishing it as a separate app which would then allow a lot of people to be much happier because they could run gboard choose Microsoft speech to text oh, they could run SwiftKey and choose Google gboard speak to text and come up with the ideal combination that works for them individually.

    2
    Действия с комментариями Постоянная ссылка
  • Avatar
    michael n

    I've been using SwiftKey for many, many years. Long before MS bought it. All I know is that since it was taken over by MS, it's pretty much garbage now. I've read the entire thread and I'm going to try rolling back google (which I loath almost as much as microsoft) and I'm going to try AppBlock on my Note 20 5G. Kevin, your posts very helpful, thank you for putting in so much effort with this. 

    Microsoft, if you're listening, the ability to select a word in a sentence and choose another option because the word transcribed was incorrect, it really was part of SwiftKey. Either you're willfully ignorant or just completely brain dead. I believe it's the latter. "Too big to fail"? more like Too Big to give a Shite. 

    0
    Действия с комментариями Постоянная ссылка
  • Avatar
    Karen Mack

    @Kevin Freels
    Please keep up your personal quest!! This talk to text issue has made my phone life a living hell. I use talk to text all the time and I could not understand why, about a year or so back, suddenly it didn't know fourth grade grammar and would not learn any of my words. I had better talk to text on my very first series. Oh that was supposed to be Siri, because that's not a word that anyone ever uses haha. I'm going to try your suggestion. It would be amazing to have good talk to text again. It is just so frustrating to go backwards, not even backwards because like I said I started out with better talk to text, in this day and time. I talk to text can't even put in the correct version of there?! Oh and that sentence it didn't recognize A instead of I because a sound so much alike don't they? Ugh!

    0
    Действия с комментариями Постоянная ссылка
  • Avatar
    Kirsten O'Quinn

    Sigh, c'mon SwiftKey, fix this already.  I tried to voice text sleigh (in a very clear sentence about Santa) and got "slay" with no other options.  If your algorithms can't make sense of which homonym I want based on context, you really ought to bring back the option to pick from a list.  PLEASE.  Save all of us losing our minds.

    1
    Действия с комментариями Постоянная ссылка
  • OK. I have some news and I was able to make a dramatic improvement in the speech to text. It's not exactly how I would expect it to be and it was the 20th combination of things I tried and by then I was simply not doing a good job taking notes. I'll continue to try sorting it out but this appears to provide a not just decent, but very good speech to text result with SwiftKey. 

    I have a galaxy note 9 no some of this may not be the same on your phones.

    So I did something in my last attempt that continually overwrote the last word of the previous sentence with a "Z" when you started the next sentence. And it was about 70% of the time so  I couldn't even work around it. So I uninstalled gboard I uninstalled swiftkkey, I switched my keyboard back to samsung's and turned on samsung voice input.... Probably irrelevant on that last part....

    I will say that one thing nice about the samsung speech to text is the bottom has buttons for a few things... a period, a spacebar, an enter key, and something else. I think it would be great if swiftkey were able to do something similar. I think the best speech to text is a combination of speech and touch. 

    It was a fair experience. Better than what had been going on and tolerable. Next I thought I would take a step by step approach and switched to google voice typing. I went through all the settings and made sure they were as they should be. I noticed that the library had an option to download a local version to be used when offline so I did that. Next, I installed gboard. As I activated it, i left google voice typing on. All of a sudden, speech to text was excellent. Absolutely fantastic. I put it through the ringer by mumbling, whispering, pulling arcane words from various sources like astronomy, medicine, and physics to build a list of words 50 words long where it missed ....... TWO. I was so impressed that I was afraid to mess with it further. But that microphone key is just not in the right place, and neither are the "shift characters"..... NOTE: I don't know where in the process this happened but at one point I looked at the dictionary being used and noticed that it just said English and not English US. I believe it was after installing gboard but not certain. I tapped it and selected English US and now it says English US. I have no idea if this is important or not. I somehow doubt it but then again, a lot of this is nonsensical. 

    So I took it a step further in a counterintuitive way. I checked all the settings to make sure they were nearly the same as I would like in SwiftKey, then reinstalled it. When I activated it, I did so without turning off gboard or google voice typing. Samsung keyboard still activated and greyed out, i have samsung keyboard, gboard, google voice typing, and swiftkey all in the ON position..... and it works very well. 

    I do notice something I didn't see when using gboard. As I speak and words drop, they will actually change as I speak. I've seen a word actually change twice as the sentence went down. As I finished it was correct however. The quality again is very good. I still don't have the dropdown for correction. In fact, gboard has a function for correcting words. but to be honest, it's a non-issue. the speech to text is that good....as it should be after this length of time. Oddly, with each change the window that pops up for the speech to text was different even though other than the samsung, it's all google. 

    Finally, there is one other thing that's very nice...it's the timeout. If I stop talking, it waits a full 7-8 seconds before timing out! I can be in the middle of a long statement, lose track of where I was because of a distraction, regain it and continue all without it stopping! 

    So assuming what I did wasn't accidental it should be reproduceable. It would be great if someone else could help nail down these steps. For the moment, I'm not going to mess with it. I've fought this a long time and I want to use it....and pick it apart...without risk of losing it because I poked the wrong button somewhere. lol 

    1
    Действия с комментариями Постоянная ссылка
  • Avatar
    Kirsten O'Quinn

    @Kevin Freels - so you've switched entirely to gboard and Google voice? No more SwiftKey? Or you've combined them somehow? I used gboard for a week when SwiftKey and my phone update didn't get along. Didn't love it but the speech to text was definitely better. The typing was rough tho.

    0
    Действия с комментариями Постоянная ссылка
  • Avatar
    Kevin Freels

    @Kirsten O'Quinn I have Swiftkey running and it's working extremely well. 😁 I'll summarize the steps that I took to the best of my ability and try to build a steps list because I wasn't expecting it to work and didn't take notes. Some of these may have no actual impact but it's what I did. Try this and let me know if it works....
    1.) Uninstall Gboard, Swiftkey, and any other keyboards except Samsung.
    2.)Reboot and check for updates.
    3.) Install "speech services by Google"
    4.)Install gboard
    5.)go to settings>language and input>on screen keyboard and tap "manage keyboards"
    6.)Samsung keyboard will be enabled and greyed out. Turn on gboard and gooe voice typing
    7.)go back to Language and Input and tap on Spelling Correction
    8.) make sure it is ON and set language to English (United States)..... This is odd as it says "English" by default but when you tap it to get the selection list, "English" isn't a choice... Instead, you can English is separated into regions like UK, US, and the etc. Not sure if it matters or not but I did this so I'm including it.

    When you installed gboard it should have walked you through the setup and allowed you access to the settings.
    Go through and set it up as you would for SwiftKey. Pay close attention to the Text Correction and Voice Typing sections as I think some carry over. In Voice Typing make sure Use Voice Typing is ON and turn on FASTER VOICE TYPING and VOICE CONTRIBUTIONS. Go back to settings and tap DICTIONARY and under Personal Dictionary make sure it's English(US). Then back out to Settings and go to Advanced and under Learning turn on options for Personalization and Improve Voice Typing... if you want to.

    Now you should find your speech to text to be EXCELLENT. But as you know, I am It's just not SwiftKey quality.....

    I recommend rebooting here and testing again to make sure it all works well.
    Once you reboot, you will install SwiftKey. (I installed Beta but I don't think it matters). When you get to the option of Making it your default keyboard, do so. Set it up as you wish. Then go back to the settings> Language and Input>
    On screen keyboard and make sure that Samsung Keyboard, Gboard, Google Voice Input, and and SwiftKey are all listed as active. If not, you can tap Manage Keyboards and turn on what isn't currently active.
    Now SwiftKey speech to text should be excellent. I'm at a complete loss as to why this process worked or how it differs from a dozen other attempts and combinations. It may be as simple as a single option, database, and dictionary, etc. I have no idea why there are so many different dictionaries, why some are English (United States), some English (US) and others just English and I'm not going to try to find out. I don't know why multiple keyboards have to be active. The former programmer in me squirms when seeing multiple keyboards active simultaneously, each that is capable of running without the other. I guess I'm getting old and the new way to do things is to run multiple keyboard programs and let the system or software choose which parts of each to run which is probably why there is no answer to the problem that works for all or even most. The complexity would be enormous. Here we only have a few variables. Samsung keyboard, gboard, SwiftKey and Google voice input which appears to be a totally separate speak to text and text-to-speech service because gboard comes out of the box with its own speech to text and its own dictionary as does Samsung. I've also noticed that having the auto correction function turned on in gboard can make a complete mess of speech to text in SwiftKey. This is despite the fact that if you are voice typing as I am right now, tapping the settings COG will take you to Google Voice typing and not keyboard where you can actually change the setting causing the problem.
    I may experiment with this further at another time but for the moment I'm very pleased with the speech to text and I can still use SwiftKey. I still miss the drop down list of optional words that used to be part of SwiftKey which SwiftKey claims was never part of it. But I remember it and it was fantastic. I also remember an alternate dictionary that you can download for SwiftKey turning your text into Shakespearean. Of course that's when the SwiftKey actually controlled the database I doubt anyone at Microsoft knows anything about SwiftKey before they purchased it.

    Give that a try and see if it doesn't help. Would love to hear your results and also if you try anything else let us know how it goes as well. Because I'm still trying to figure out why there is a drastic improvement, but at the same time it's still not quite the same as it is in gboard. If I have some spare time I might dig in a little bit deeper but as it is, I'm kind of afraid to mess with it. LOL

    0
    Действия с комментариями Постоянная ссылка