time: 1600013674817 msg: Native crash: Segmentation fault stacktrace: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Revision: '0' ABI: 'arm64' Timestamp: 2020-09-13 19:14:34+0300 pid: 13673, tid: 13731, name: GLThread 1875 >>> com.touchtype.swiftkey.beta <<< uid: 10300 signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 Cause: null pointer dereference x0 0000007ab1397188 x1 0000000000000000 x2 0000000000000000 x3 6672755379726575 x4 0000000000000020 x5 0000000000000022 x6 6571745278716474 x7 7f7f7f7f7f7f7f7f x8 0000007ab10e8d50 x9 00000000000035a3 x10 00000000000001c7 x11 0000000000000000 x12 0000000000000015 x13 c3a5c85c97cb3127 x14 be41013c00000000 x15 615f4d435f317653 x16 0000007ba0ed3138 x17 0000007ba531d000 x18 0000007aa073a000 x19 0000007ab1397140 x20 0000000000000000 x21 0000000000000000 x22 0000007ab13e0d80 x23 0000007ab13e0db8 x24 0000007b060bca10 x25 0000000000003038 x26 0000007aa81228b0 x27 0000000000000005 x28 0000000000000003 x29 0000007ab10e7aa0 sp 0000007ab10e7a20 lr 0000007b05f3e7d4 pc 0000000000000000 backtrace: #00 pc 0000000000000000 <unknown> #01 pc 00000000002657d0 /vendor/lib64/egl/libGLESv2_adreno.so (!!!0000!ecc1182a9b77401cf79fde44965c23!54e0376!+928) (BuildId: f98b78dea04952d16bd150c01f9ddbd8) #02 pc 000000000025f4c8 /vendor/lib64/egl/libGLESv2_adreno.so (!!!0000!9fd1d7886c175ac1b2746eb9ebdcd4!54e0376!+144) (BuildId: f98b78dea04952d16bd150c01f9ddbd8) #03 pc 000000000001fbcc /system/lib64/libEGL.so (android::eglCreateContextImpl(void*, void*, void*, int const*)+216) (BuildId: 75a3a233f52b9f0ef9337005f4c7e3ac) #04 pc 00000000000c49a4 /system/lib64/libandroid_runtime.so (android::jni_eglCreateContext(_JNIEnv*, _jobject*, _jobject*, _jobject*, _jobject*, _jintArray*)+296) (BuildId: 58b41b29f92c69c33bf7b93b93d34c08) #05 pc 00000000002be63c /system/framework/arm64/boot-framework.oat (art_jni_trampoline+236) (BuildId: dcd2cfd91c1e70426c86a17b7a7aeea93c73eaec) #06 pc 0000000000b569e0 /system/framework/arm64/boot-framework.oat (com.google.android.gles_jni.EGLImpl.eglCreateContext+64) (BuildId: dcd2cfd91c1e70426c86a17b7a7aeea93c73eaec) #07 pc 0000000000136334 /apex/com.android.runtime/lib64/libart.so (art_quick_invoke_stub+548) (BuildId: 39c521eaaf443587c42421cd1671e849) #08 pc 0000000000145054 /apex/com.android.runtime/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+244) (BuildId: 39c521eaaf443587c42421cd1671e849) #09 pc 00000000002dc854 /apex/com.android.runtime/lib64/libart.so (art::interpreter::ArtInterpreterToCompiledCodeBridge(art::Thread*, art::ArtMethod*, art::ShadowFrame*, unsigned short, art::JValue*)+384) (BuildId: 39c521eaaf443587c42421cd1671e849) #10 pc 00000000002d7b34 /apex/com.android.runtime/lib64/libart.so (bool art::interpreter::DoCall<false, false>(art::ArtMethod*, art::Thread*, art::ShadowFrame&, art::Instruction const*, unsigned short, art::JValue*)+912) (BuildId: 39c521eaaf443587c42421cd1671e849) #11 pc 000000000058eb7c /apex/com.android.runtime/lib64/libart.so (MterpInvokeInterface+1052) (BuildId: 39c521eaaf443587c42421cd1671e849) #12 pc 0000000000130a14 /apex/com.android.runtime/lib64/libart.so (mterp_op_invoke_interface+20) (BuildId: 39c521eaaf443587c42421cd1671e849) #13 pc 00000000004d6598 /data/app/com.touchtype.swiftkey.beta-eb475koj9LntGZaT6IXXnw==/oat/arm64/base.vdex (pp4$b.createContext+16) #14 pc 000000000058ee2c /apex/com.android.runtime/lib64/libart.so (MterpInvokeInterface+1740) (BuildId: 39c521eaaf443587c42421cd1671e849) #15 pc 0000000000130a14 /apex/com.android.runtime/lib64/libart.so (mterp_op_invoke_interface+20) (BuildId: 39c521eaaf443587c42421cd1671e849) #16 pc 00000000002ca672 /system/framework/framework.jar (android.opengl.GLSurfaceView$EglHelper.start+154) #17 pc 000000000058d638 /apex/com.android.runtime/lib64/libart.so (MterpInvokeVirtual+1432) (BuildId: 39c521eaaf443587c42421cd1671e849) #18 pc 0000000000130814 /apex/com.android.runtime/lib64/libart.so (mterp_op_invoke_virtual+20) (BuildId: 39c521eaaf443587c42421cd1671e849) #19 pc 00000000002caae2 /system/framework/framework.jar (android.opengl.GLSurfaceView$GLThread.guardedRun+526) #20 pc 000000000058f9c8 /apex/com.android.runtime/lib64/libart.so (MterpInvokeDirect+1168) (BuildId: 39c521eaaf443587c42421cd1671e849) #21 pc 0000000000130914 /apex/com.android.runtime/lib64/libart.so (mterp_op_invoke_direct+20) (BuildId: 39c521eaaf443587c42421cd1671e849) #22 pc 00000000002cb2d8 /system/framework/framework.jar (android.opengl.GLSurfaceView$GLThread.run+48) #23 pc 00000000002ad6b0 /apex/com.android.runtime/lib64/libart.so (_ZN3art11interpreterL7ExecuteEPNS_6ThreadERKNS_20CodeItemDataAccessorERNS_11ShadowFrameENS_6JValueEbb.llvm.15111145639444711060+240) (BuildId: 39c521eaaf443587c42421cd1671e849) #24 pc 000000000057eb70 /apex/com.android.runtime/lib64/libart.so (artQuickToInterpreterBridge+1012) (BuildId: 39c521eaaf443587c42421cd1671e849) #25 pc 000000000013f468 /apex/com.android.runtime/lib64/libart.so (art_quick_to_interpreter_bridge+88) (BuildId: 39c521eaaf443587c42421cd1671e849) #26 pc 0000000000136334 /apex/com.android.runtime/lib64/libart.so (art_quick_invoke_stub+548) (BuildId: 39c521eaaf443587c42421cd1671e849) #27 pc 0000000000145054 /apex/com.android.runtime/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+244) (BuildId: 39c521eaaf443587c42421cd1671e849) #28 pc 00000000004a0540 /apex/com.android.runtime/lib64/libart.so (art::(anonymous namespace)::InvokeWithArgArray(art::ScopedObjectAccessAlreadyRunnable const&, art::ArtMethod*, art::(anonymous namespace)::ArgArray*, art::JValue*, char const*)+104) (BuildId: 39c521eaaf443587c42421cd1671e849) #29 pc 00000000004a15d4 /apex/com.android.runtime/lib64/libart.so (art::InvokeVirtualOrInterfaceWithJValues(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, _jmethodID*, jvalue const*)+416) (BuildId: 39c521eaaf443587c42421cd1671e849) #30 pc 00000000004e08c0 /apex/com.android.runtime/lib64/libart.so (art::Thread::CreateCallback(void*)+1332) (BuildId: 39c521eaaf443587c42421cd1671e849) #31 pc 00000000000e1e7c /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+36) (BuildId: dc5d39b686612dc48d78785006f75487) #32 pc 0000000000083678 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: dc5d39b686612dc48d78785006f75487)
Ask the community your SwiftKey for Android related questions
Theme not downloading0 votos 0 comentariosVirginia cavalier theme does not download says error each time I try to download it please fix this thanks
2020. Figured out number pad layout!0 votos 1 comentarioI feel like a poephol in Afrikaans language. I searched forever and eventually found the answer hidden here. Thank to it this is what I did thanks to the person that posted it. To change the number pad to a calculation type layout I did the following. I went to SwiftKey settings, click on number pad and layout and then you choose, (right number pad or left number pad and BINGO! It worked for me! I hope it works for you. SwiftKey developers! Please can you make this number pad setting easier to find? Just call it, number pad layout, etc or something like that.
how to add custom transliteration mapping0 votos 0 comentarios
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?
Screenshot how to get this number pad layout0 votos 0 comentariosAaaag, I can't upload a screenshot here. I thought I could.. I had to Reset my phone and I used to have the number pad layout, don't know if this is the right description. I want the number pad layout too look like the one before the reset, it look like a calculator. I googled it but can only find that you must tap or hold the number pad key bottom right. I tried it, no go. I also looked under themes and phone settings, no go. Lol, the frustration is that I eventually figured out how to do it before resetting my Huawei. I even posted it here but now I can't find my own bloody post,😁 I really liked my number pad layout back. Cab anyone help me out here please?
[Essential Features Request] Microsoft SwiftKey is Missing the QR-Code Scanner feature2 votos 2 comentarios
As a user, I would like to be able to use SwiftKey Keyboard to scan a barcode (QR-Code). By clicking a simple button that opens the camera and ready to scan a QR-code.
I think everyone wants to use this essential feature.
Please include your own system-wide spell-checker (red underline) with the app.0 votos 0 comentarios
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.
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.
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.
Here it has been suggested that the user should disable the spell checker:
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
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.
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?
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.
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.
My clipboard is lagging and it's not working when I wrote a lot of shortcuts/paragraphs0 votos 0 comentarioswhenever I open my clipboard it lags and few months ago my clipboard is not working it just crashed. i tried uninstalling and installing it again and it still doesnt work. i tried clearing cache it still doesnt work, i deleted all of high GBs/MBs vids and it still doesnt work. is there a solution to this issue/problem, i wanna fix the clipboard so badly.
Automatic dark mode and themes with no key borders2 votos 1 comentarioWith Android 10 and now 11, the we have had automatic dark mode switch off for apps. When do you plan to add auto dark mode for SwiftKey? The ideal would be to allow is to choose the light and dark theme and switch between them automatically. Please also add the option to get rid of key borders in the default theme.
SwiftKey Fails to show up Surface Duo0 votos 0 comentariosSwiftKey is in usable on the new surface duo. It fails to pop up all the time. I click in almost any text box multiple times and the keyboard fails to show. I have to force stop the application, restart SwiftKey, jump back to the other app, and there is still a 20% chance it doesn't open (reddit seems to hate it). Should I just swap keyboards on this new device? I have never experienced such a hard fail from SwiftKey on either Android or Windows phone previously. this new two screen phone seems to hate this keyboard. Super unreliable.
Keyboard Jumping0 votos 0 comentariosSince getting a new Note Ultra, my SwiftKey is experiencing two major problems. The first is that I will be typing and suddenly the cursor will jump back to the beginning lines randomly in the middle of a sentence and start typing there. The other issue is that suddenly the keyboard will switch to the symbol page, messing up my typing. Anyone else having this problem or have any advice? It really sucks.
Swiftkey problem with OnePlus 80 votos 0 comentariosSwiftkey is fenerally the best keyboard in android phones, but it is not working correctly, when using OnePlus 8 Pro. When typing, the cursor is jumping every now and then annoyingly. Stupid bug. Can You fix it? Thank You.
Keyboard disappears from Note 200 votos 0 comentarios
Segmentation fault when keyboard appears0 votos 0 comentariosThe bug appears on both stable and beta channels. Device: Poco F1, Android 10, Adreno GPU Driver version: 490
Can I have more accent markers?0 votos 0 comentariosHi I'm having a problem I want more accent markers but I can only have 5 languages at once. I don't want the prediction stuff since it's kinda annoying I just want more accent markers.
Long press for punctuation doesn't work on Android 110 votos 2 comentariosI recently got the Android 11 update on my Pixel 4a. The long press on the period button no longer works. I suspect it has something to do with the gesture navigation because the long press does work if I move the keyboard up by using "float" mode.
Cursor control bug1 voto 0 comentariosHello, I've found a bug with Cursor Control and Auto Capitalize. When you type a sentence that ends with punctuation, if you use the Cursor Control to go back in the sentence Swiftkey will correct and suggest any word with the first letter capitalised. If you then write a word in lower case and use the Cursor Control to go after the punctuation Swiftkey will not capitalise the first letter. Could you fix this bug?? Thanks for this feature 😁
how to remove the arrow to hide the keyboard in the lower right corner?1 voto 0 comentariosthis arrow spoils the look of the keyboard and when you create your own theme, it stands out against a dark blue background.
Any way to make German keys like ä/ö/ü appear before @/9/7?1 voto 0 comentariosAs I wrote in the Title, is there a way to make those appear before the letters? Because if you're trying to type smoothly and fast it's always a weird moment to just stop to go over to "ä" because at the first place there is "@" for some reason. Is there a simple option to change that? :)
BUG- Lost theme, stuck w/black, select mine or new one, error message, then reverts back HELP!0 votos 0 comentarios
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.
Enter key closes SwiftKey (Android)0 votos 0 comentariosWhen using the enter key in some apps, SwiftKey now closes. It's quite difficult to enter emails now, because this includes spark.app (email) most especially, but also at least one other app (I can't recall now). I uninstalled and reinstalled to the same effect.
Demander des passeports rapides, SSN, ID, permis de conduire, visas0 votos 0 comentarios
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.
MR Kevin Oneill0 votos 0 comentarios
Trying to install an android app that my device r7ns a version of androidtha5 is just nearly up to date
Add ≤ and ≥1 voto 0 comentarios
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.
Буфер обмена0 votos 1 comentario
В клавиатуре есть буфер обмена, можно отредактировать этот буфер обмена на компьютере? и каким образом
フルキーボード ひらがな入力できない0 votos 0 comentariosフルキーボード ひらがな入力できない
Why is there a SwiftKey service job running in the background and waking up my device?0 votos 0 comentarios
Why is there a SwiftKey job running in the background all the time and waking up my device? It's consuming quite a bit of battery. The job is the following:
*job*/com.touchtype.swiftkey/com.touchtype.scheduler.SwiftKeyJobServiceThis happened around an update available on 7/19/20. Can't tell you the exact version because I HAD to downgrade.
Change keyboard on external keyboard0 votos 0 comentarios
I'm using latest version of SwiftKey and Android on Samsung Galaxy S10.
If I use SwiftKey using external physical keyboard such as Logitech K850,
I know that Ctrl + Shift changes the language between English and another language such as Spanish.
If I want to switch to another keyboard app such as Samsung keyboard or Google GBoard using only physical keyboard, what should I do?
(I know touching the 'dots' on the lower-right corner does that, but I wonder if I can do this using only physical keyboard)
Clipboard memory0 votos 0 comentariosHow i can increase clipboard memory to save more copied text.
Configurable keys near space_key0 votos 0 comentarios
I think is a interesting idea, to put 1 or 2 configurable keys in bottom (like emoji key), doing little the space key. For example, I would config with ? and !