Microsoft SwiftKey Android Support Forums

Hi guys,

How to submit a feature request

If you've had a really good idea and want SwiftKey to hear all about it, the best way to do that is to submit it via the 'Feature Request' form here:

https://support.swiftkey.com/hc/en-us/requests/new

We look forward to reading all your requests and improvements.

The best way to post a question

When I write something, text always appears underlined until the word is completed. This feature is very irritating, how do I get rid of it?

I use Huawei Mediapad T5 and automatic text correction is turned off. 

I'd like to be able to use same themes that I have on my SwiftKey Beta keyboard, if I'd switch to SwiftKey keyboard public non beta version. The themes won't sync, also the settings won't sync. And that's awful, it should be available in 2019.
Also does anyone know a list of all codes and coupons for SwiftKey themes? Screenshot of themes that are no longer available: https://photos.app.goo.gl/CfgNbP4CaenDhyEs7

I have always NOT used the Android default vibration and had keypress vibration set to 3 ms in the Swiftkey options. I just updated to Android 13, and the vibrations are all out of whack. It feel like every few vibrations, an extra one gets added and it's difficult to type. It's the same issue as this:
https://www.reddit.com/r/GooglePixel/comments/wqw6a5/android_13_and_haptic_feedback_for_typing/

That's specific to the Google keyboard, but I'm having the same issue. Is there any way to fix this?

It seems that the latest SwiftKey update (8.10.21.3) introduced a new bug. I use SmartOffice for my documents. (Yes, I know it's not a Microsoft product, shame on me.) Now, when I try to edit them, SwiftKey pops up but with limited functionality. The word suggestion bar doesn't appear, words don't automatically space and the number key doesn't stay on for more than one character. 

I'm using Vivo X70 (Android 12) and Samsung Tab S4 (Android 10). SmartOffice is version 3.13.10.

Hi,

I've been using Swiftkey for many years, I really love this keyboard and features. I recently switched to a galaxy fold, and can't match the keyboard to a foldable use case.

Swiftkey has a one-handed layout, which is perfect for the main screen where I can't use swiping in any comfortable and precise way with the normal all-screen layout.

The problem is that if I set it to one handed layout, for some reason the keyboard on the external narrow screen is also narrower, even though simple logic dictates that the very narrow external display is already one-handed and shouldn't be resized.

I can't find any setting to disable this, I have to change the layout setting every time I switch displays which is stupidly annoying and making this keyboard useless on foldables.

Even the split ("thumb") layout follows to the external display, which is even stupider.

Samsung keyboard already has this obvious feature, there are settings to configure default layouts for main display and external display, the external one even has different settings for portrait and landscape modes.

Is there any way to force the keyboard to stay on full layout on the external display and one-handed layout on the main display? Or do I have to abandon Swiftkey for Samsung keyboard?

Thanks

Dear guys of Swiftkey,
please...

Please just be considerable of what so many people want from you since over 2 years now - just do us all the kind favour and implement this feature that can' t be so hard to implement developerwise... Just implement an easy option to shut off this autospaces that are annoying for soo many people and it' s what so many people want.

Don' t you just realize, that this is a really major request? You should also consider that really many people must be annoyed by this feature missing, who each day loose their nerves and useful time backspacing this additional spaces and just don' t want to take this efford to find out how to contact you and to write you such a message like us in this forum... Don' t you think they do just find this a pity that this small missing annoying feature is putting your for the rest perfectly customizable and greatly working virtual keyboard tool into a bad light just for such a small additional efford from your side?

I just don' t want to sound rude to you at all, and ask you politely to implement this feature. It' s about time this issue will be fixed. It should be also in your interest to improve your great app further somehow...

Kind Regards

Riccardo Pierucci

P. S. : Please don' t consider this as a double post - I wrote a similiar comment into another Thread about the same issue - where there where so many people asking you for this feature implementation, that they filled out 4 long forum pages with this request to you asking you for this since whole two years.

Hi!

I really like Swiftkey, its awesome for two of my spoken languages, Swedish and English but really bad for my third spoken language, Chinese (manadarin). 

Not only does the Chinese input for swiftkey not learn the phrases I commonly use, it also constantly gets what I am writing wrong. Chinese is most commonly written phonetically with a system called "pinyin" where you use a normal 26 keyboard to write how a word is pronounced, then you chose the correct character (word) for that pronunciation. Chinese is special in the sense that it can have a lot more then one character (word) for one pronunciation. What swiftkey does wrong is that it not only is not able to guess what character I want to write according to the context as all other Chinese inputs do, like the default windows Chinese input etc, it sometimes does not even chose characters for the pronunciation I've written! 

For example, I can write the pronunciation "yu" and get a list of characters pronounced "yi", or write "jian" and get characters pronounced "yuan" etc. This is extremely frustrating and writing something that might take seconds with other input methods can take minutes with Swiftkey as it takes forever to sit and chose among 100s of characters with the pronunciation I did not write. Its like if you would write the English word "doctor" spelled correctly and then the first choice on the list is dictator, then proctor, then drought and then you have sit and scroll down a list until you finally find "doctor".

I have been using swiftkey for more than a year and there has been exactly 0 improvements with the Chinese input. From a market standpoint I really cant see why you would not put any effort in improving the input for a language that is spoken by 25% of the world population, while the Swedish input (a language that is spoken by about 0.1% of the population) is working perfectly. Not that I complain about the Swedish input working well, I just really dont understand how you prioritize.

Please fix this asap, its LONG overdue. 

When writing I Greek the question mark character is this - > ;

SwiftKey should treat it as such and it current doesn't. Actually, after the last update the behavior of the Greek question mark has deteriorated and acts inconsistent in comparison to before the update.

All too often I reread my text to see that the letter "u" was placed where I definitely meant "I", which naturally changes the entire meaning of the sentence. I never use "u" as a diminutive of "you". I can long press it in my pr edict bar and tell it not to predict it again but that does nothing for single letters.

Is there any way to manually assign prediction priority so that "I" is always suggested before "u", no matter how precise my swiping may be?

 Hi, I like using Swiftkey because of the ability to create long text shortcut keys which I use in customer support and because it is the only keyboard to somewhat support spell checking and preemptive text when using Samsung DeX.

Won't you please include the bullet ( • ) and checkmark ( ✓ ) characters, so useful for lists of items and tasks? You could easily add them as alternate long-press symbols. It's the only thing preventing me from switching from GBoard to SwiftKey. I've asked for this for a couple of years now on Play Store, but maybe you don't read those comments…? Thanks!