Microsoft SwiftKey Android Support Forums

I opened my texting app to find the keyboard had suddenly shifted the arrows from the bottom horizontal position to a vertical position in the middle of the keyboard. I disabled the arrows and now there is a huge gap vertically in the middle of the keyboard. Does anyone have any idea how to get my keyboard back to normal?

vérifier et accepter car est enregistré dans le système tous les documents et certificats.
Avez-vous besoin de documents internationaux tels que; PASSEPORT, VISA, LICENCE DE CONDUCTEUR, RÉSIDENT

Demander des passeports rapides, SSN, ID, permis de conduire, visas

Les documents de citoyenneté offrent la plus haute qualité et assument l'entière responsabilité de ce que nous fabriquons. Des centaines d'utilisateurs, qui ont essayé nos services, nous ont classés n ° 1 sur la cote de confiance mondiale du site Web Fake ID. Nous sommes des créateurs et des vendeurs de qualité de disques authentiques et faux. [+ 380-9542-31375] Nous traitons et créons des archives que vous pouvez utiliser pour vous déplacer et travailler sur n'importe quelle partie du monde.

. [+ 380-9542-31375] Si vous voulez acheter de fausses cartes d'identité en ligne, y compris de vrais certificats de naissance, de faux permis de conduire en ligne, alors est le nom. Nous ne faisons aucun compromis sur la qualité. Les fausses cartes d'identité que nous fabriquons sont comme les vraies. Nous nous engageons à livrer les travaux à temps sans dépasser le délai mentionné aux clients. Nous fournissons une assistance complète à nos précieux clients et les aidons dans leurs problèmes.

Acheter Real Passport en ligne
Acheter la citoyenneté américaine
Acheter un permis de conduire en ligne
Demander un vrai permis de séjour
Acheter de faux billets
Demander un visa en ligne
SSN valide pour la vente en ligne
Demander un vrai passeport ......

Si vous souhaitez acheter de fausses cartes d'identité en ligne, y compris de vrais certificats de naissance, un faux permis de conduire en ligne, alors c'est le nom. Nous ne faisons aucun compromis sur la qualité. Les fausses cartes d'identité que nous fabriquons sont comme les vraies. Nous nous engageons à livrer les travaux à temps sans dépasser le délai mentionné aux clients. Nous fournissons une assistance complète à nos précieux clients et les aidons dans leurs problèmes.

Courriel - nchangca180@gmail.com
Whatsapp: + 380-9542-31375
www.qualitydocs4u.com

Trying to install an android app that my device r7ns a version of androidtha5 is  just nearly up to date

Please add ≤ (less than or equal to) and ≥ (greater than or equal to).

For example, they can be placed in a popup menu after a long touch on < and > symbols.

So I see in the latest update that incognito mode is automatically enabled when in an incognito chrome tab. This is great! I asked for this a long time ago, and the transition is very smooth. However, I have a couple big issues with how it's been implemented.

I can't turn it off. The toggle is just gone when in an incognito tab. Seems like defaulting to the mode is fine, but I want to be able to choose. Let people choose. Why? Next point...

The theme is fixed, and doesn't have secondary characters. I have to do a lot of work (access my work email) in an incognito tab. I'm used to the secondary characters for the rather technical writing I need to do. That's gone now, and is costing me time and sanity. Either allow the user to set the incognito theme, or add secondary characters.

I'm always a proponent for letting the user choose. Bury it in an advanced settings mode and hide it behind a warning if you want, but give us access to these toggles. Especially in the beta.

Cheers.

SwiftKey انا استخدم كيبورد 

علي موبيل اندرويد ولكن يوجد خط احمر يظهر تحت الكلام اريد ان ازيل هذا الخط

SwiftKey suddenly stopped displaying with my selected theme and reverted to some random black theme.  Go to Settings->Themes->Select either my earlier-used theme or a new theme, the message appears: "Sorry that your theme changed, something went wrong on our side.  You can change it back." -- BUT-- you cannot change it back. 

Hitting "More Info" displays "We have enhanced our themes under the hood to give you a better typing experience.  Something went wrong updating your theme.  Don't worry, you can still change it back to what you had."

Selecting [Change] and any other option provides exactly zero changes.

Several problems - 1) the better typing experience is now massively worse, nearly unusable with the bogus new themes forced into the UI.  2) we CAN NOT change it back, I've tried dozens of times, both old & new themes, downloading new ones, etc.

THIS IS BROKEN AND NEEDS TO BE FIXED OR ROLLED BACK IMMEDIATELY- HOW DO WE GET THE FIX?

Disgusting incompetence and lack of QA, and it isn't like Microsoft lacks resources.

I am trying Swiftkey. I am an old user of the defunct Swype keyboard. I can still use it, as it's installed on my phone, but there are no updates and some bugs will always exist. Still, it's more precise than Swifkey as far as i experience and the shortcuts makes your life much easier.

I thought that since Swype keyboard is not anymore produced, Swiftkey had time to improve and implement the best features of Swype, at least make a choice in the options to use them. Swiftkey looks nice with so many themes, also some shortcuts are finally implemented. But it's extremely unreliable. I type "too" (or randomly any word) and it gives me "tyuol" or some other splited nonsense short words or even autocorrects the previous word in a wrong way, even if in option i unticked the autocorrect feature. It makes me spend more time correcting and deleting unasked words than actually text. I try to swype a simple word like "ich" in german..and it gives me again some weird words or letters..i'm asking myself why? almost every sentence you use that word and still it fails..i have a constant usecure feeling in my hand that the new word will be a fail..

Also, an unexplainable unchangeable backspace function in swiftkey, of not deleting the whole word after swyping a word but only bringing the cursor to the end of the word, makes texting so slow..because very often the word is wrong, but also on the prediction/correction bar i don't find the desired word, so pressing backspace should immediately delete the word and quickly retry. So i have to press backspace long and i might delete even the previous word or part of it. Weird. Weird that there's no option to customise the backspace action.

I like new and fresh updates. That's why i'd like to switch to swiftkey, but these issues make the app unusable. Was a cool first feeling, but it's not even been 24 hours and again I am convinced to delete it.

Another thing, I am texting much more than i call and i use 5 languages. Great, that now you're not limited to 3 languages like before, but maybe also that's why it's not reliable, because very possibly when i need a word, it gives me a word of another language. Why isn't it possible to choose the language manually or set which languages to work in a multilingual keyboard? On Swype keyboard i press long space and release it on the language that i prefer. Than to quickly switch back to the last language used, i swyped shortly from Swype button to space. However i had also the choice to use multilanguages.
This would be a basic option. If i'm not wrong, Huawei phones come from the box with Swiftkey installed and choosing the language is possible. Right or wrong? So why isn't it possible on the google market app?

Can someone give me some answers about my concerns? Am I doing something wrong? My phone is made in 2018, an S9+, no way that it's too slow for this app.
I'm here and wrote this post because i would like to use the app, but please someone tell me if you have a better experience. 
I can read for hours the complaints of the users on google play, but there are no answers, no solutions to the problems. That's why i described here my experience with Swiftkey.

Thank you!

the beta app has gone a little wonky on my phone.  out of nowhere the keys started popping up at double height (best way to explain it is when you're in Word and the paragraph settings have line separation at greater than 1pt.  hope that helps

then the app would crash and my phone crashes with it and i have to reinstall from scratch.

so i went back to the regular app for now

Just reinstalled app (7.6.3.4) on new device {Samsung S10e). My themes are listed but won't download (you're theme could not be downloaded. Please try again later). I have uninstalled and reinstalled and cleared cache. Still no success.

using the qwerty keyboard for phonetics sometimes does not bring the relevant word and requires switching to native keyboard to get the word right but then that word does not get save making it impossible to teach new words to the phonetic keyboard. For instance:

• The word "chappal" when typed does not provide a meaningful prediction in Hindi - ideally it should provide predeiction "चप्पल ".
• Typing "ch" only provides "छ" and no option for "च"

Now this would be reasonable so long as user had some way to map the phonetic predictions. Is it possible or is it on the roadmap as a feature?

First, I will clarify some things for those who may not know and for those who might assume that I am confusing spell-checker with keyboard input prediction.

Then I will:

Bring back a problem that has been called for attention many times and explain why it happens;

Explain why I think it matters and why previous suggested workarounds are sub-optimal;

Discuss Google’s (Gboard) chosen workaround;

Give my suggestion to fix the problem.

Definitions

Input prediction (IP) (Auto-complete and auto-correction) is a feature whose main purpose in software keyboards is to allow the user to type faster. The keyboard suggests words before you type them entirely and correct words where there are typos. By auto-correcting, the keyboard allows the user to type without painstaking care and precision, which allows for faster typing.

Spell-checking (SC) is (usually) a feature of word processors or system-wide input fields (MS Word, Android, and Google Chrome for desktop, each has its own spell-checker independent from software keyboards or any input method). Its main purpose is to alert and correct the user about the orthography of a given language.

The problem

People who use simultaneous multi-language input prediction – a feature present on SwiftKey (and Gboard also) – start seeing a red underling in all words of one of the languages.

The reason is that, while SwiftKey’s input prediction does have support for multiple languages simultaneously, the android’s system-wide spell-checker active in the user’s phone (usually AOSP’s or Google’s spell-checker) does not have.

Previous suggestions

Here it has been suggested that the user should disable the spell checker:

https://support.swiftkey.com/hc/en-us/community/posts/115002878149-Red-underline-Not-a-SK-problem-

Notably, this is also the approach used by Gboard (more on that latter), but I think this is far from the ideal because it forces the user to resort to input prediction (IP) as a form of spell-checking (SC). This is a problem because, as I said in the beginning, input-prediction is a feature focused on fast typing (as it should be) and not on orthography. To illustrate, imagine how a user uses IP as SC:

The user types the word and hopes that the keyboard will correct it automatically if it’s wrong. Except that, even when typing correctly, sometimes the first prediction (the middle one in SwiftKey) is not the desired one. And other times the prediction dictionary doesn’t have the desired word. For those reasons, the exact typed word is always shown as an option, typos and all (as it should be), and the keyboard memorizes anything the user decides to input (as it should be) either by typing space and accepting the middle prediction, or by selecting the desired word in the list.

The result is that the IP learns a lot of slangs, acronyms and jargon (as is should be), but also learns misspelled words. And the user has no way of knowing if the thing he/her has typed didn’t appear as the first (middle) prediction because it was wrong or because the neural network crystal ball simply got it wrong or because the word doesn’t exist in the IP dictionary. Also, sometimes the misspelling is so different from the intended word that the latter doesn’t appear in the prediction list, and sometimes the misspelling is even presented as the first (middle) prediction.

The clear solution to that in my opinion is to have a separate mechanism for checking orthography, the spell-checker, which has to support simultaneously multi-language input as well (chrome desktop browser has that). This is a second independent layer that runs after input prediction, and is not affected by the IP dictionary. And when the user decides to tap a word and include it in the SC dictionary it is a conscious deliberate decision.

How does Gboard deal with that

https://support.swiftkey.com/hc/en-us/community/posts/115002630445-Changing-the-language-doesn-t-change-the-system-spell-checker

Here it has been said that SwiftKey cannot control the spellchecker, and that Gboard doesn’t break in the same way because it has “advanced system privileges that SwiftKey cannot access”. I’m not an android programmer, but from the tests I have done, it seems to me that Gboard has the exact same level of system access that SwiftKey has with respect to spell-checking:

If my selected system-wide spell-checker is the AOSP one, it behaves in the exact same way with Gboard as it does with SwiftKey. The thing that Gboard does different is that, along with the keyboard, the app installs a spell-checking service as well. I’m using LineageOS, which doesn’t come with Gboard or Google’s spell-checker, only the AOSP ones. And when I install Gboard, Google’s SC appears as an option.

Now, Google’s solution is far from the best in my opinion. For what I tested, the ‘Google spell-checker’ (installed by Gboard) simply disables itself if it detects that Gboard is being used and uses only the system’s language when it detects other 3rd party keyboards (exactly like the AOSP one). And I already explained my problems with both solutions.

My suggestion

Simply put together a simple spell-checker with simultaneous multi-language support and ship it within the SwiftKey app. I think this would be simple to do, just copy the default dictionaries of the SwiftKey IP as a starting point, but it would not have to deal with predictions and other complex features that a software keyboard has to deal with. Again, copy the dictionaries, any word learned by the IP should not be automatically learned by the SC.

The simplest implementation would be to have one hash table for each language. If the user decides to use two languages simultaneously, a new empty language-agnostic hash table is created. That way, when the user includes a new word to de dictionary, it is included in the language-agnostic one to avoid guessing the language of the word. Then, spell-checking a word is simply to query the word on 3 hash tables.

Why am I suggesting this to you?

https://support.swiftkey.com/hc/en-us/community/posts/360038666231-How-to-Active-Spell-Checker-in-SwiftKey

Here it has been said that SC “was never a feature of SwiftKey itself”, and that it’s an Android problem.

Indeed, if only AOSP’s SC did support multiple languages simultaneously, this problem would be solved. But I use and prefer SwiftKey; AOSP’s keyboard still doesn’t have support for simultaneous multi-language input, suggesting that this support is also not in the horizon for AOSP spell-checker; and it’s more probable that Google’s engineers will fix this only in Google’s SC, in a way that works exclusively with Gboard (as it’s the case with the ‘auto-disable SC’ workaround).

And ultimately this is a problem that (to me at least) seems extremely simple to solve and is hurting your product.

Here are some treads complaining of SC-related problems that, while not necessarily being all related to multi-language support, could benefit from a simple Spell Checker shipped inside the SwiftKey app.

https://support.swiftkey.com/hc/en-us/community/posts/115002905745-Multilingual-keyboard-underlines-all-English-as-incorrect-Spell-Checker-

https://support.swiftkey.com/hc/en-us/community/posts/360057381832-Red-underline

https://support.swiftkey.com/hc/en-us/community/posts/360041911952-Swiftkey-red-underline-is-gone-

https://support.swiftkey.com/hc/en-us/community/posts/360054924171-Red-line-under-text

https://support.swiftkey.com/hc/en-us/community/posts/115004508429--Duplicate-Android-Showing-red-underlines-for-all-words-in-second-language

https://support.swiftkey.com/hc/en-us/community/posts/360071921211-Swiftkey-underline-not-showing

https://support.swiftkey.com/hc/en-us/community/posts/115000617369-Reduced-English-suggestions-for-incorrect-spellings

https://support.swiftkey.com/hc/en-us/community/posts/360043539472-Red-line-under-spelling-errors-with-SwiftKey-

https://support.swiftkey.com/hc/en-us/community/posts/115000528649-Spell-Check-with-SwiftKey-has-Red-underlined-text

P.S.:

I’m conscious that I might be wrong about a number of things: There could be another workaround that solves the problem in a satisfactory way; There could be a barrier to install system-wide spell-checkers on android; Maybe spell-checking is harder than I think, even without grammar-checking or prediction; etc.

In that case it would be nice if someone could explain the situation in a more in-depth way.