Maybe it's since the JB upgrade, but my keyboard keeps resetting to the Default Samsung 3, from Swiftkey 3. Could also have been from installing the Swiftkey Flow beta.
Anyone else experience this, and what can I do to stop it.
dratsablive said:
Maybe it's since the JB upgrade, but my keyboard keeps resetting to the Default Samsung 3, from Swiftkey 3. Could also have been from installing the Swiftkey Flow beta.
Anyone else experience this, and what can I do to stop it.
Click to expand...
Click to collapse
I think if you go to the buglist at swiftkey.net you'll find you aren't alone. I'm using the Swiftkey Flow beta and this problem hasn't occurred...yet. You can turn of the Flow feature and it becomes a regular Swiftkey keyboard.
I use Smart Keyboard Pro off of the market and the same thing keeps happening to me. By that I mean I don't use swype and my settings keeps rolling back to the regular keyboard.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
dratsablive said:
Maybe it's since the JB upgrade, but my keyboard keeps resetting to the Default Samsung 3, from Swiftkey 3. Could also have been from installing the Swiftkey Flow beta.
Anyone else experience this, and what can I do to stop it.
Click to expand...
Click to collapse
I've found that these problems can sometimes can be fixed by uninstalling and reinstalling the keyboard.
I did a factory reset and it still happened.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
jeffdaman said:
I did a factory reset and it still happened.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Could you describe how this is happening? Does it switch keyboards after you use a certain app, or does it just switch at random times? One thing you could try is to disable all other keyboards under applications. This way, the phone has to keep using your keyboard.
Happens for me after a reboot. Always goes back to Samsung keyboard. Once I change to SwiftKey, it stays that way until the next reboot. As others have said, seems like a bug between JB and SwiftKey 3 (without Flow beta)
It happens every time I restart and then it would happen randomly while using the phone. I thing Task Manager by Rythm Soft was killing Smart Keyboard but I got it on the ignore list now; and so far it seems limited to the restart. It's not possible to disable Swype or the Samsung Keyboard. They are greyed out on the list.
To the O.P. you should check any task managers to be sure Swype isn't being killed.
MobileNick said:
Happens for me after a reboot. Always goes back to Samsung keyboard. Once I change to SwiftKey, it stays that way until the next reboot. As others have said, seems like a bug between JB and SwiftKey 3 (without Flow beta)
Click to expand...
Click to collapse
Same thing is happening to me. Always after a restart it falls back to the Samsung Keyboard.
If you guys are rooted make a back up of the Samsung keyboard then delete it. From system/app i know that worked on the early sprint JB leaks
Sent from my SGH-I747 using xda premium
brorex said:
If you guys are rooted make a back up of the Samsung keyboard then delete it. From system/app i know that worked on the early sprint JB leaks
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Anyone try this, and what does it default to if you do remove the Samsung Keyboard? I have several inputs, WiiMote, PS3, etc. If I have to keep changing the default back to Swiftkey, then this option would get annoying.
Known Bug with Work-Around
dratsablive said:
Maybe it's since the JB upgrade, but my keyboard keeps resetting to the Default Samsung 3, from Swiftkey 3. Could also have been from installing the Swiftkey Flow beta.
Anyone else experience this, and what can I do to stop it.
Click to expand...
Click to collapse
This is a known bug with JB 4.1.x.....
Swiftkey has it mentioned in a bug list as well as Google in a bug list...
It has something to do with apps getting installed differently and storing app data differently with JB. When a phone reboots the storage location for that app's data is not mounted or available right away so the app can't load and therefore the phone switches to the default keyboard.
Happens with a few other apps like AT&T Vooicemail Viewer.
The work-around is to root the phone, backup the app with Titanium Backup, uninstall the app, then restore it without data. Then set the keyboard as default and it should stay that way after re-boots.
Good luck!
Boomer6345 said:
This is a known bug with JB 4.1.x.....
Swiftkey has it mentioned in a bug list as well as Google in a bug list...
It has something to do with apps getting installed differently and storing app data differently with JB. When a phone reboots the storage location for that app's data is not mounted or available right away so the app can't load and therefore the phone switches to the default keyboard.
Happens with a few other apps like AT&T Vooicemail Viewer.
The work-around is to root the phone, backup the app with Titanium Backup, uninstall the app, then restore it without data. Then set the keyboard as default and it should stay that way after re-boots.
Good luck!
Click to expand...
Click to collapse
Might wait for Google or Swiftkey to fix the bug. If I restore without the data, then I lose all the words Swiftkey has learned.
This is really odd. A few weeks ago I downloaded the SwiftKey Flow Beta and this problem disappeared. That is, after a reboot my default keyboard would stay on SwiftKey Flow Beta. But yesterday SwiftKey released the official version 4 with Flow integrated. And now the problem is back - reboot makes Samsung Keyboard as default.
So what did the Beta do that was so special that it would stay after a reboot??
MobileNick said:
This is really odd. A few weeks ago I downloaded the SwiftKey Flow Beta and this problem disappeared. That is, after a reboot my default keyboard would stay on SwiftKey Flow Beta. But yesterday SwiftKey released the official version 4 with Flow integrated. And now the problem is back - reboot makes Samsung Keyboard as default.
So what did the Beta do that was so special that it would stay after a reboot??
Click to expand...
Click to collapse
Same. Reboot causes the problem. Not a huge issue, but odd.
cfn87 said:
Same. Reboot causes the problem. Not a huge issue, but odd.
Click to expand...
Click to collapse
It's a change in the way Jellybean handles how Google Play apps are loaded during boot process, since they happen after the keyboard gets loaded, it reverts to default.
Boomer6345 said:
This is a known bug with JB 4.1.x.....
Swiftkey has it mentioned in a bug list as well as Google in a bug list...
It has something to do with apps getting installed differently and storing app data differently with JB. When a phone reboots the storage location for that app's data is not mounted or available right away so the app can't load and therefore the phone switches to the default keyboard.
Happens with a few other apps like AT&T Vooicemail Viewer.
The work-around is to root the phone, backup the app with Titanium Backup, uninstall the app, then restore it without data. Then set the keyboard as default and it should stay that way after re-boots.
Good luck!
Click to expand...
Click to collapse
correct. since the play store installs apps in a location (on your JB device) that is not immediately scanned during the first part of boot up, thats why the stock keyboard is loaded. however, to fix this on my wife's unrooted/stock S3, i found the actual swiftkey apk then downloaded and installed it onto the phone. this placed the apps info in the correct storage location that is seen on boot up. i do not condone downloading apps you have not paid for however i did this for her as she and i have both paid for swiftkey on all our phones/tablets when it initially released on the play store. i dont have this swiftkey issue on my s3 as it is running a custom rom. cheers
xBeerdroiDx said:
correct. since the play store installs apps in a location (on your JB device) that is not immediately scanned during the first part of boot up, thats why the stock keyboard is loaded. however, to fix this on my wife's unrooted/stock S3, i found the actual swiftkey apk then downloaded and installed it onto the phone. this placed the apps info in the correct storage location that is seen on boot up. i do not condone downloading apps you have not paid for however i did this for her as she and i have both paid for swiftkey on all our phones/tablets when it initially released on the play store. i dont have this swiftkey issue on my s3 as it is running a custom rom. cheers
Click to expand...
Click to collapse
Where would this location be?
dratsablive said:
Where would this location be?
Click to expand...
Click to collapse
via a google search
MobileNick said:
This is really odd. A few weeks ago I downloaded the SwiftKey Flow Beta and this problem disappeared. That is, after a reboot my default keyboard would stay on SwiftKey Flow Beta. But yesterday SwiftKey released the official version 4 with Flow integrated. And now the problem is back - reboot makes Samsung Keyboard as default.
So what did the Beta do that was so special that it would stay after a reboot??
Click to expand...
Click to collapse
Sorry if this was already covered...but I read a post at the Swiftkey site that the issue is with Paid apps on JB. Not all paid apps of course...but some paid apps like Swiftkey install to this special storage location that is not available soon enough during the boot process.
The 4.x Swiftkey beta was not a paid app so it worked...now that the beta is released it is a paid app and the Swiftkey 4.x release in Google Play has the issue again on JB just like 3.x did.
Related
Hi there,
I removed the swype that came with our phones as I wanted to try downloading/installing the version from swype beta website (hoping it would not have the bug where it doesn't put a space after I, a etc).
It wouldn't work so now I cant get swype.
Can someone please help a brother out and send me (pm) the swype.apk from the Samsung Epic Touch 4g.
Much apprecaited!!!
-RR
Good luck . . . I got the swype beta to work for a bout a day and then it started giving me all sorts of errors, ended up switching to swiftkey X
h20wakebum said:
Hi there,
I removed the swype that came with our phones as I wanted to try downloading/installing the version from swype beta website (hoping it would not have the bug where it doesn't put a space after I, a etc).
It wouldn't work so now I cant get swype.
Can someone please help a brother out and send me (pm) the swype.apk from the Samsung Epic Touch 4g.
Much apprecaited!!!
Click to expand...
Click to collapse
I installed Swype beta and have been using it for a couple days with no problems whatsoever.
Did you actually use the Swype installer, or did you just try to copy in the Swype.apk?
After you delete the factory Swype.apk, I had to switch to the default keyboard, then go into task manager and kill the Swype process. THEN I ran the swype installer apk. I got a brief warning that said I was replacing a system app, but that was it.
Been enjoying properly spaced single words ever since.
Dalmus said:
I installed Swype beta and have been using it for a couple days with no problems whatsoever.
Did you actually use the Swype installer, or did you just try to copy in the Swype.apk?
After you delete the factory Swype.apk, I had to switch to the default keyboard, then go into task manager and kill the Swype process. THEN I ran the swype installer apk. I got a brief warning that said I was replacing a system app, but that was it.
Been enjoying properly spaced single words ever since.
Click to expand...
Click to collapse
I used to like the default Swype skin on the Epic, but once the Beta came out, I've been using that one since.
Dalmus said:
I installed Swype beta and have been using it for a couple days with no problems whatsoever.
Did you actually use the Swype installer, or did you just try to copy in the Swype.apk?
After you delete the factory Swype.apk, I had to switch to the default keyboard, then go into task manager and kill the Swype process. THEN I ran the swype installer apk. I got a brief warning that said I was replacing a system app, but that was it.
Been enjoying properly spaced single words ever since.
Click to expand...
Click to collapse
I first uninstalled swype.apk from applications.
Then I downloaded the installer, logged in and downloaded the swype application... At that point it just started force closing on me...
Any thoughts?
-robert
make sure you delete /system/app/Swype.apk AND system/lib/libswypecore.so or something like that, THEN use the Swype installer. Otherwise it will just say it's installed, but it really won't
Sent from my SPH-D710 using xda premium
I just extracted the ns4g beta and installed over the current swype.
Sent from my SPH-D710 using xda premium
Overstew said:
I just extracted the ns4g beta and installed over the current swype.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Nice gimme gimme lol pretty please
.: sent from my Samsung Galaxy S II Epic 4G Touch :.
just do a factory reset , that will put it back,, then after that STOP DELETING STUFF
I have the black nexus s Swype as well. it is awesome. No problems at all, been running it since root came out.
Sent from my Samsung Galaxy S2
boominz28 said:
just do a factory reset , that will put it back,, then after that STOP DELETING STUFF
Click to expand...
Click to collapse
A factory reset will not reinstall swype if the user deleted the app from /system. All factory reset does is wipe /data and /cache.
SwiftKey has released a statement on the issue of the keyboard reverting to stock on a reboot. It is a Google Play issue, strangely (but their beta worked, so...huh?) Anyway, the statement is here.
http://support.swiftkey.net/knowled...lt-keyboard-reset-on-every-restart-or-reboot-
Sharing is caring.
meatlocker said:
SwiftKey has released a statement on the issue of the keyboard reverting to stock on a reboot. It is a Google Play issue, strangely (but their beta worked, so...huh?) Anyway, the statement is here.
http://support.swiftkey.net/knowled...lt-keyboard-reset-on-every-restart-or-reboot-
Sharing is caring.
Click to expand...
Click to collapse
good looks bro. always good to know why things are happening
I fixed this issue by disabling the samsung keyboard in titanium backup. Now when I restart, I'm on SwiftKey!
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Here is what I did. Use TBU, long press on swift key, choose convert to system ap. Go to system app, grab the SwiftKey apk, place it on your card, click it to install properly. Then go back to system/app and delete the one in there
Or
Here is the apk
http://www.blownco.com/DAFOXS/com.touchtype.swiftkey-1.apk
Download it, click to install
~~~~~~~~~~~~~*~~~~~~~~~~~~
$$$$$$$$$$$PayPal$$$$$$$$$$$
dafoxs said:
Here is what I did. Use TBU, long press on swift key, choose convert to system ap. Go to system app, grab the SwiftKey apk, place it on your card, click it to install properly. Then go back to system/app and delete the one in there
Click to expand...
Click to collapse
That is an excellent solution, dafoxs (as usual). Thanks man.
i just cleared the cache, data and force closed the stock samsung keyboard. rebooted my phone, all worked fine
stretchwookie said:
i just cleared the cache, data and force closed the stock samsung keyboard. rebooted my phone, all worked fine
Click to expand...
Click to collapse
Does it show up after a reboot?
Dp you see the apk in data/app?
~~~~~~~~~~~~~*~~~~~~~~~~~~
$$$$$$$$$$$PayPal$$$$$$$$$$$
Had this problem with both Swiftkey and ADW Launcher. Froze the stock keyboard, Swype and the TouchWiz Home using Titanium, now it all works as it should.
I am having huge problems with keeping Swift Key as the default keyboard on my phone. It is frustrating enough that I'll drop SK unless I can fix it. It defaults back to the Samsung keyboard and re-enables Swype too. I tried deleting the cache and data from the app manager for the Sam keyboard but that had no effect. I tried deleting and reloading SK but that didn't work. How do I stop this?
Thanks,
Tim
Delete it, or disable it.. Do you really need the Samsung keyboard? I think this is more a problem with Swiftkey
Sent from my SGH-M919 using Tapatalk
By disabling the samsung kb what ever is going on will have no choice but to use SK kb.
Try disabling samsung kb.
Pp.
Sent from my Touchwiz device that never forgets apps.
I also had this problem...the ONLY thing that actually works on my phone (for any paid keyboard) is to make it a system app with titanium backup.
sdmark said:
I also had this problem...the ONLY thing that actually works on my phone (for any paid keyboard) is to make it a system app with titanium backup.
Click to expand...
Click to collapse
Good idea.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)
I don't get a disable option for the keyboard app. Can only stop it.
Froze it with Titanium Backup and it's finally freaking gone. Thanks!
Couldn't figure out how to make it a system app but freezing Samsung KB works.
Anyone read about this yet? I read about it in the guardian. It seems the chances are fairly slim if you watch what networks you connect to, but i would still prefer to have this issue fixed. Since i am running a custom rom without knox, i will not get any fix OTA. Any ideas for custom rom users?
For reference:
http://www.theguardian.com/technology/2015/jun/17/samsung-keyboard-bug-android-hack
http://arstechnica.com/security/201...ng-galaxy-phones-into-remote-bugging-devices/
I'm paranoid; I found /system/app/ SamsungIME and /system/lib/libswiftkeysdk-java.so and moved them permanently to ExtSdCard/downloads just for safekeeping. I looked for other files associated in /data/data and /data/dalvik-cache but found none. Rebooted with no issue; just don't try to select swiftkey as default in Settings/Language and input.
IDK how this swiftkey dictionary update works so I'm thinking there's still some or all security vulnerability. Anyone know? I searched pages of Google Search but currently filled with vulnerability issue and updates.
No Knox here either. I've long used Swype paid customized with top number row. Had no idea the swiftkey dictionary was updating in the background despite not being the default dictionary.
Sent from my SM-N910P using Tapatalk
Since most of us on xda have root, just wipe data and uninstall it with titanium backup. I'm maybe thinking user dictionary should be wiped and uninstalled. I'll back both up and check if everything is ok. It's no skin off my back, I've used Swype since it first appeared on android and that has its own dictionary it backs up.
I also could be wrong and uninstalling these may not prevent anything. But these are still parts of the rom that are not needed for me and hasn't hurt anything yet.
If any devs could chime in if they know that would be great.
Just decided to freeze the dictionary. Wasn't but 52 kB of data, 12kB cache there per application manager.
Sent from my SM-N910P using Tapatalk
I've got 2 issues, prediction keeps switching itself off all the time, and I just cannot get curve (swype) to work despite trying every combination of TouchPal settings, any ideas?
Sent from my HTC 10 using XDA-Developers mobile app
I couldnt stand touchpal. I use google keyboard and deleted touchpal and all its lanugage packs, skins etc (requires root). Much better now.
Just found solution to Swype, you have to update the language as htc only included basic language.
Sent from my LG-D855 using XDA-Developers mobile app
Holding off on root, but its killing me as no proper app backup solution, need to read up as htc is sooo different to sammy/lg
Sent from my LG-D855 using XDA-Developers mobile app
gsw5700 said:
Holding off on root, but its killing me as no proper app backup solution, need to read up as htc is sooo different to sammy/lg
Sent from my LG-D855 using XDA-Developers mobile app
Click to expand...
Click to collapse
You probably already know about this but to back up my app data I used helium from clockwork mod. It doesn't require root and all you need to do is enable USB debugging. That's what I used to back up my game data and other things when I switched from my one m9 to the 10.
For my call logs and text messages I used SMS backup and restore which worked flawlessly. The only thing left to do after that was to export my contacts to my SD card and I was set to go. It took me about 25 minutes to get everything up and going on the new phone not including system updates and application updates of course which you can't avoid
I hope that helps out some
Thanks, I am aware of helium but thought it may be a bit of a hassle. I'm used to titanium backup, LG has its own awesome backup utility.
Not too sure about flashing twrp/root yet as it stops OTA updates. So left with custom rom and wait for that rom to get OTA included. Looking forward to custom roms, custom kernel, heavy debloating, easy backup and restore. Still not sure how you flash HTC 10 back to stock!
Sent from my HTC 10 using XDA-Developers mobile app
gsw5700 said:
Thanks, I am aware of helium but thought it may be a bit of a hassle. I'm used to titanium backup, LG has its own awesome backup utility.
Not too sure about flashing twrp/root yet as it stops OTA updates. So left with custom rom and wait for that rom to get OTA included. Looking forward to custom roms, custom kernel, heavy debloating, easy backup and restore. Still not sure how you flash HTC 10 back to stock!
Sent from my HTC 10 using XDA-Developers mobile app
Click to expand...
Click to collapse
In my experience helium is not a hassle to use at all. If you've never used it before you basically turn on USB debugging install the app from the play store and install the application from the website on your computer. After you do that plug your phone into your computer and launch the application on your phone. It then comes up with a list of all the applications on your phone, you can either press select all or individually select the applications you would like to back up. Once you do that you push a button and a few moments later everything is done.
One thing to note is that it creates a folder named carbon on the root of the internal storage of the phone, just remember to move that folder over to your SD card before you start experimenting with anything that may require wiping the phone. I have used titanium backup in the past as well and while the helium method may not be just as easy it is the absolute best solution out there for people that don't already have a rooted device
dabbler77 said:
I couldn't stand touchpal. I use google keyboard and deleted touchpal and all its lanugage packs, skins etc (requires root). Much better now.
Click to expand...
Click to collapse
Just a heads up. Do not delete TouchPal like i did. My phone asked for the password for encrypted data at boot - it hadn't loaded the google keyboard, and as I deleted touchpal from system I had no keyboard! Only option was to restore. I've now left touchpal (minus all the language packs) in my rom, for some reason Google keyboard couldn't be moved to system. Oh well.
Hi I'm using Swiftkey but tried many keyboard. All are giving me a problem in the p button and keyboard being too sensitive. It types the same letter three times. Can anyone help
himesh82 said:
Hi I'm using Swiftkey but tried many keyboard. All are giving me a problem in the p button and keyboard being too sensitive. It types the same letter three times. Can anyone help
Click to expand...
Click to collapse
Hello,
I am an official moderator from SwiftKey, can you go to our community to post your issue?
Appreciate!
Alpert
---------- Post added at 09:52 AM ---------- Previous post was at 09:50 AM ----------
dabbler77 said:
Just a heads up. Do not delete TouchPal like i did. My phone asked for the password for encrypted data at boot - it hadn't loaded the google keyboard, and as I deleted touchpal from system I had no keyboard! Only option was to restore. I've now left touchpal (minus all the language packs) in my rom, for some reason Google keyboard couldn't be moved to system. Oh well.
Click to expand...
Click to collapse
Oh buddy, that's sad...
Just do not activate TouchPal in language&keyboard menu?
dabbler77 said:
Just a heads up. Do not delete TouchPal like i did. My phone asked for the password for encrypted data at boot - it hadn't loaded the google keyboard, and as I deleted touchpal from system I had no keyboard! Only option was to restore. I've now left touchpal (minus all the language packs) in my rom, for some reason Google keyboard couldn't be moved to system. Oh well.
Click to expand...
Click to collapse
Yeah. Disable touchpal doesn't stop force install on language packs. I'm disappointed there's no option to remove this on play store.
Sent from my HTC 10 using Tapatalk