Reverts to default keyboard at reboot / restart
After I updated my device to Jelly Bean, Swiftkey keeps returning to android default keyboard after restart or shutdown. I uninstalled the keyboard and re-installed it but nothing happened. Everytime the phone loads the OS i go to setting and configure again Swiftkey
I set SwiftKey as default keyboard; it changes back to the default Android keyboard upon a reboot of the phone.
This has been ongoing from some time now. Any chance of it getting fixed?
Be able to select swift key as a default keyboard. So when you turn your phone on it is already selected
I set my default keyboard to SwiftKey but it won't stay when I reboot or shutdown, it revert to samsung keyboard
Keyboard resets to default android keyboard every time I reboot my Samsung Galaxy S3. Using latest AT&T update, I was using Beta version of SwiftKey and uninstalled prior to upgrading SwiftKey.
This is really annoying because every time I turn off the phone and turn it back on my SwiftKey is not appearing it wasn't a problem before but now is a constant.
Every time I turn on my phone after jellybeans update, the phone reverts back to stock keyboard instead of SwiftKey on galaxy S3
After updating to JB, SwiftKey lost the ability to remain the default keyboard upon system restart.
Give us a default option.
Whenever my phone gets turned off it automatically resets back to a different keyboard options.
Is there a way to make SwiftKey my default keyboard?
Hi
My keyboard changes to default android everytime I swych my Phone of and on. Can U Guys fix IT.
Each time restart the phone or turn on, the keyboard back to the deafult of samsung in my Galaxy S3. I'm using Android 4.1.1 official (Brazil), whitout any modification.
Already been done factory reset in the phone and reinstalled swiftkey but the problem continues.
I have Galaxy Note 2. Because auto correction does not work I use the SwiftKey keyboard that I've purchased, however with every reboot keyboard switches back to stock!
Every time I reboot my s3 running jb 4.1.1 the keyboard reverts to the stock Samsung keyboard. Why does it not keep SwiftKey?
Every time I reboot my SGS3 running JB, the phone defaults to the stock keyboard meaning I have to manually select it in the settings.
Getting a little tedious now.
Every time my phone is powered off my keyboard setting are switched back to default instead of swiftkey, Which causes me to go back to my phone settings and switch it back to how it was before my phone powered off
Keeps going to default when rebooted on jellybean
After setting Swiftkey 3 as the default keyboard, it should persist even after restarting the device.
After reboot my nexus I have to reset the keyboard and enter SwiftKey as the default. My OS is jelly been
After Jelly Bean update, Swiftkey keeps returning to android default keyboard after restart or shutdown
After i updated my Samsung galaxy s3 to Jelly Bean, Swiftkey keeps returning to android default keyboard after restart or shutdown. I uninstalled the keyboard and re-installed it but nothing happened. Everytime the phone loads the OS i go to setting and configure again Swiftkey olso force close app and restart mysql phone
I'm using a nexus s with 4.1.1
On Nexus S with stock jellybean 4.1.1 /SWiftkey 3.0.0.302
After each reboot swiftkey is disabled. even after some time of inactivity, the stock google keyboard takes over. After reenabling Swiftkey everything is fine. Until the next reboot
when I go to use it it constantly is changing itself back to android keyboard
Update:
We have contacted Samsung regarding this problem – they acknowledged the issue and have checked that it does not occur in their latest update. They intend to roll out Android 4.2.2 to Galaxy S3 users in the near future (unfortunately we don’t have an exact date), at which point the problem should be fixed.
Explanation of the issue:
We are aware of the issue where your phone reverts to the stock keyboard on reboot and we appreciate that it is very annoying.
We are currently in contact with Google Play to see if there is anything that they can do to fix this.
The issue is that Google Play installs paid apps in a particular location on your phone and that in some versions of Android (particularly 4.1 on Samsung devices) this location is not available at the point in the boot process where keyboards are being switched on. So your phone does not know that you have SwiftKey, and it defaults back to the phone’s keyboard.
We are unable to control where Google Play installs the app, and also unable to do anything about the way in which your phone boots up, so we are essentially powerless.
You can read more about the issue here http://code.google.com/p/android/issues/detail?id=34880 – the issue is listed as “released”, which means that it has been fixed in the code and the fixed version has been released, but we know that it can take months for a new version of Android to reach customers’ phones, which is why we are trying to see if Google Play can do something about it in the shorter term.
Free apps will not be affected, and of course with most apps you just tap them to turn them on once your phone is already fully booted, so it is only with paid apps that offer services like keyboards or widgets that this problem is visible.
If you have not yet used SwiftKey Trial you can download it here https://play.google.com/store/apps/details?id=com.touchtype.swiftkey.phone.trial – it will work for a month, and hopefully by the time that month is over the issue will be resolved. (you can only use SwiftKey Trial one time on each phone – if your phone has tried SwiftKey Trial before then the trial will show up as “expired” immediately and will not work – sorry).
Again, we appreciate that this is not ideal, but we are doing the best that we can to get SwiftKey working for you.
Best,
Sarah
Small update:
We contacted Android Developer Support and they could not help us to get around this problem. Their response was “The issue is fixed in Android 4.1.2, not 4.1.1. Your customers will need to upgrade, unfortunately.”
We have informed them that a number of you are still experiencing the issue on 4.1.2 and they have said that they will look into it.
Explanation of the issue:
We are aware of the issue where your phone reverts to the stock keyboard on reboot and we appreciate that it is very annoying.
We are currently in contact with Google Play to see if there is anything that they can do to fix this.
The issue is that Google Play installs paid apps in a particular location on your phone and that in some versions of Android (particularly 4.1 on Samsung devices) this location is not available at the point in the boot process where keyboards are being switched on. So your phone does not know that you have SwiftKey, and it defaults back to the phone’s keyboard.
We are unable to control where Google Play installs the app, and also unable to do anything about the way in which your phone boots up, so we are essentially powerless.
You can read more about the issue here http://code.google.com/p/android/issues/detail?id=34880 – the issue is listed as “released”, which means that it has been fixed in the code and the fixed version has been released, but we know that it can take months for a new version of Android to reach customers’ phones, which is why we are trying to see if Google Play can do something about it in the shorter term.
Free apps will not be affected, and of course with most apps you just tap them to turn them on once your phone is already fully booted, so it is only with paid apps that offer services like keyboards or widgets that this problem is visible.
If you have not yet used SwiftKey Trial you can download it here https://play.google.com/store/apps/details?id=com.touchtype.swiftkey.phone.trial – it will work for a month, and hopefully by the time that month is over the issue will be resolved. (you can only use SwiftKey Trial one time on each phone – if your phone has tried SwiftKey Trial before then the trial will show up as “expired” immediately and will not work – sorry).
Again, we appreciate that this is not ideal, but we are doing the best that we can to get SwiftKey working for you.
Best,
Sarah
Small update:
We contacted Android Developer Support and they could not help us to get around this problem. Their response was “The issue is fixed in Android 4.1.2, not 4.1.1. Your customers will need to upgrade, unfortunately.”
Previous message:
We are aware of the issue where your phone reverts to the stock keyboard on reboot and we appreciate that it is very annoying.
We are currently in contact with Google Play to see if there is anything that they can do to fix this.
The issue is that Google Play installs paid apps in a particular location on your phone and that in some versions of Android (particularly 4.1 on Samsung devices) this location is not available at the point in the boot process where keyboards are being switched on. So your phone does not know that you have SwiftKey, and it defaults back to the phone’s keyboard.
We are unable to control where Google Play installs the app, and also unable to do anything about the way in which your phone boots up, so we are essentially powerless.
You can read more about the issue here http://code.google.com/p/android/issues/detail?id=34880 – the issue is listed as “released”, which means that it has been fixed in the code and the fixed version has been released, but we know that it can take months for a new version of Android to reach customers’ phones, which is why we are trying to see if Google Play can do something about it in the shorter term.
Free apps will not be affected, and of course with most apps you just tap them to turn them on once your phone is already fully booted, so it is only with paid apps that offer services like keyboards or widgets that this problem is visible.
If you have not yet used SwiftKey Trial you can download it here https://play.google.com/store/apps/details?id=com.touchtype.swiftkey.phone.trial – it will work for a month, and hopefully by the time that month is over the issue will be resolved. (you can only use SwiftKey Trial one time on each phone – if your phone has tried SwiftKey Trial before then the trial will show up as “expired” immediately and will not work – sorry).
Again, we appreciate that this is not ideal, but we are doing the best that we can to get SwiftKey working for you.
Best,
Sarah
Hi everyone,
We are aware of the issue where your phone reverts to the stock keyboard on reboot and we appreciate that it is very annoying.
We are currently in contact with Google Play to see if there is anything that they can do to fix this.
The issue is that Google Play installs paid apps in a particular location on your phone and that in some versions of Android (particularly 4.1 on Samsung devices) this location is not available at the point in the boot process where keyboards are being switched on. So your phone does not know that you have SwiftKey, and it defaults back to the phone’s keyboard.
We are unable to control where Google Play installs the app, and also unable to do anything about the way in which your phone boots up, so we are essentially powerless.
You can read more about the issue here http://code.google.com/p/android/issues/detail?id=34880 – the issue is listed as “released”, which means that it has been fixed in the code and the fixed version has been released, but we know that it can take months for a new version of Android to reach customers’ phones, which is why we are trying to see if Google Play can do something about it in the shorter term.
Free apps will not be affected, and of course with most apps you just tap them to turn them on once your phone is already fully booted, so it is only with paid apps that offer services like keyboards or widgets that this problem is visible.
If you have not yet used SwiftKey Trial you can download it here https://play.google.com/store/apps/details?id=com.touchtype.swiftkey.phone.trial – it will work for a month, and hopefully by the time that month is over the issue will be resolved. (you can only use SwiftKey Trial one time on each phone – if your phone has tried SwiftKey Trial before then the trial will show up as “expired” immediately and will not work – sorry).
Again, we appreciate that this is not ideal, but we are doing the best that we can to get SwiftKey working for you.
Best,
Sarah
This issue isn’t restricted to SwiftKey, it is a bug in Android 4.1.1 and relates to the location on your phone where Google Play installs paid apps.
We appreciate that it is very annoying and we are investigating whether there is anything at all that we can do, but it may be that this is out of our hands.
You can read more here: http://code.google.com/p/android/issues/detail?id=34880.
This issue isn’t restricted to SwiftKey. You can read more here: http://code.google.com/p/android/issues/detail?id=34880.
The 4.1.2 update has resolved this for the majority of users. If you had 4.1.1 pushed to your device, it’s only a matter of time until you receive the 4.1.2 bugfix update as well.
This issue was not restricted to SwiftKey. You can read more here: http://code.google.com/p/android/issues/detail?id=34880.
Hi all,
This issue does not appear to only be restricted to SwiftKey. You can read more here: http://code.google.com/p/android/issues/detail?id=34880. Our team is looking into what we can do on our end to get things sorted out for you.
If you have any extra details that you think might help us to pin it down please do add them as a comment – thanks.
HI everyone, we are aware of this and are looking into it.
If you have any extra details that you think might help us to pin it down please do add them as a comment – thanks.
753 comments
-
Shaf
commented
·
·
Flag as inappropriate
·
Delete
How could I trust Google Play's application & their reviews. I've read almost all of your reviews not a one review I find complaining about the "reverts to default keyboard after reboot ", so wwhat's telling me most of your reviews are fake with 5 stars. It's a shame for the cover up. You should refund our money.
-
Ruslan
commented
·
·
Flag as inappropriate
·
Delete
Actually i found a solution that worked for me, i downloaded latest apk version from Internet for now its 4.1.0.142 version and reinstalled it. I think it's not a big deal as i bought keyboard and have apk downloaded.And it's set by default after reboot
-
Anonymous
commented
·
·
Flag as inappropriate
·
Delete
Same problem on AT&T Galaxy Note. Very annoying.
-
roberthp
commented
·
·
Flag as inappropriate
·
Delete
Change your keyboard to use a license file and you wont have this problem with your keyboard package. It's already been widely reported that the update doesn't work for most, and also doesn't address the fact that most of us will never see the update get issued by our carriers.
-
Corey
commented
·
·
Flag as inappropriate
·
Delete
I have a Samsung Galaxy S2, which was just updated to Jelly Bean 4.1.
SwiftKey was laggy after the Jelly Bean update, but only started to reset to default keyboard after the latest SwiftKey update. -
Josh Cleaver
commented
·
·
Flag as inappropriate
·
Delete
I also am experiencing this problem. Asus Nexus 7 - 4.2.2
Very frustrating.
-
Anonymous
commented
·
·
Flag as inappropriate
·
Delete
When looking at Sarah Reynolds post, I can see a post date of 4/8/13, but I have no idea if that is the date for the full body of the post or for the "update" that she edited in afterwards. I am interested to know when that update section was added, as we all just received an update 4.1.2 without the fix and who knows when we will receive 4.2.
Recommendation: when updating a post, please add the revision date to the body of the post.
-
Michael Dunton
commented
·
·
Flag as inappropriate
·
Delete
I too have the GS3 and experience this issue. I just recently got a software update. Android Version 4.1.2, baseband version t999uvdmd5, kernel version 3.0.31-1128078, build number jz054k.t999uvdmd5
-
Ian Womack
commented
·
·
Flag as inappropriate
·
Delete
This is ridiculous. There are multiple online threads about this since 2012 and there should be a fix by now...
-
Chad Bordes
commented
·
·
Flag as inappropriate
·
Delete
Its funny because this doesn't happen on the verizon GS3 running 4.1.2? Why is that?
-
Anonymous
commented
·
·
Flag as inappropriate
·
Delete
This keeps happening to my S3 and I do have the latest updates. Using A.I Keyboard paid version. Good keyboard but frustrating when you keeps reverting back to stock..aaarggg
-
Robert Strauch
commented
·
·
Flag as inappropriate
·
Delete
I have the same problem on my HTC Desire with Cyanogenmod 7. Will be asking for a refund if there is no fix available :-(
-
Angus Hunter
commented
·
·
Flag as inappropriate
·
Delete
Eventually problem solved but not by Swiftkey.!!!! Tried to get a Software update for my Samsung Galaxy s3 mini with Samsung. It was possible from Samsung but It needed 3gb of space to complete the update. Had to wait for my provider to give me an automatic soft update. This was completed last week and part of that update was the Android Version going from 4.1.1 to 4.1.2. Now I have no problem with Swiftkey. So guys check your Android Version and see if you can move to 4.1.2. Good luck!
-
Mischa
commented
·
·
Flag as inappropriate
·
Delete
Have the same problem with HTC One X. I suggest you also post a solution to ppl with rooted phones. It's a bummer to go through 700+ comments to find it.
-
Gabriel Vazquez
commented
·
·
Flag as inappropriate
·
Delete
*every time
-
Anonymous
commented
·
·
Flag as inappropriate
·
Delete
Make a free version available in the Play Store for users with this problem. Like the app itself is free, but we have to confirm that we've already paid before we are allowed full access.
-
Bom Bastinator
commented
·
·
Flag as inappropriate
·
Delete
there's another thread that says it's a samsung specific issue which they won't fix till they feel like updating. I advise against breath holding.
one more reason non standard android sucks. i may have to root and cyanogen after all.
-
Bom Bastinator
commented
·
·
Flag as inappropriate
·
Delete
"dave" seems to be trying a phishing scam. not thdot after goo
-
RB
commented
·
·
Flag as inappropriate
·
Delete
Anon,
There IS something swiftkey can do about it. They choose not to. -
Anonymous
commented
·
·
Flag as inappropriate
·
Delete
Happens on my HTC One S as well. So annoying. But appreciate that there isn't much swiftkey can do about it