Swiftkey - Default keyboard reset on every restart or reboot

phil-k · 28 Feb 2013 at 19:22

Default keyboard re-setting on every restart or reboot over Swiftkey.
I have read that it is a know problem with 4.1.1, but has anyone found a fix for it on a un-rooted phone

mattyfez · 28 Feb 2013 at 20:01

I thing its a problem with any un-rooted phone, or it has been with my S3 since ICS. im currently on 4.1.2 via official firmware update.

I'm actually looking up at the mo how to root, I dont really want a custom ROM but I have a few apps that dont have full function unless I root. That swift key issue being one of them.

This whole rooting thing is confusing, dont know how to go about it, I dont want to void warranty, and im not sure if it's device specifice or Android version specific, and I certainly dont want to brick my phone!

Rusty! · 28 Feb 2013 at 21:33

What phone?

Check if it's been installed on the internal or external storage, if it's on the external, it will lose its default setting on reboot.

phil-k · 28 Feb 2013 at 21:57

Its on the internal storage,
The problem is mentioned here on the Swftkey support page
http://support.swiftkey.net/knowled...lt-keyboard-reset-on-every-restart-or-reboot-

Its a pity I didnt notice this happened before I purchased the full version

V4NT0M · 28 Feb 2013 at 22:27

I noticed this the other day too, not much of a problem though as my phone is rarely ever off.

Jake 657 · 28 Feb 2013 at 23:16

If you use Titanium Backup to Freeze the standard keyboard it will keep SwiftKey as the default keyboard after a reboot.

phil-k · 28 Feb 2013 at 23:50

Jake 657 said:
If you use Titanium Backup to Freeze the standard keyboard it will keep SwiftKey as the default keyboard after a reboot.

Doesn't your phone have to be rooted to use that though

Rusty! · 1 Mar 2013 at 10:12

Ahh, it's the JB encryption fail thing.

You can get round that by sideloading the app instead of installing it via Google Play

phil-k · 1 Mar 2013 at 10:18

Rusty! said:
Ahh, it's the JB encryption fail thing.

You can get round that by sideloading the app instead of installing it via Google Play

Thanks for that I will give it a try, does Google Play still recognise it as a paid app

Rusty! · 1 Mar 2013 at 10:20

Yeah it will, since it has the same fingerprint.

phil-k · 1 Mar 2013 at 10:38

Very Helpful, Thanks
I take it that if you install an app that you have not paid for this way it will not run or will prompt you to pay

Rusty! · 1 Mar 2013 at 10:48

Nope, it will work as if it was paid for.

phil-k · 1 Mar 2013 at 12:39

From what I read there is a problem with downloading .apk files as they could contain malware.
On a phone it could cost a lot of money with premium rate calls and texts being made.

GeX · 1 Mar 2013 at 12:47

This seems to be an issue with Samsung phones mainly.

I just tried this on my Nexus 4 (4.2.2), and it also worked fine on my (Samsung) Nexus S (4.1.2).

phil-k · 1 Mar 2013 at 13:30

There seem to be quite a lot of download sites, can you recommend any

Rusty! · 1 Mar 2013 at 13:53

GeX said:
This seems to be an issue with Samsung phones mainly.

I just tried this on my Nexus 4 (4.2.2), and it also worked fine on my (Samsung) Nexus S (4.1.2).

Both those have a new enough Android version for the bug to have been fixed, it was 4.1 and 4.1.1 that suffered it.

I don't think linking to paid app downloads is going to be within the boards rules, so you'll have to figure that out for yourself.

If you rooted the phone you could pick the .apk out of the secured area it currently resides in.

Bloomfield · 1 Mar 2013 at 14:35

GeX said:
This seems to be an issue with Samsung phones mainly.

I just tried this on my Nexus 4 (4.2.2), and it also worked fine on my (Samsung) Nexus S (4.1.2).

Did you just buy the app/already own it or did you just try the free version?

It's only an issue with the paid version due to Google deciding to encrypt paid apps and store them in /data/app-asec (and another part somewhere else that I can't remember off the top of my head) instead of /data/app, which Android isn't able to access on boot when it sets the keyboard.

Rusty, it hasn't been fixed in 4.1.2

.

Edit: http://support.swiftkey.net/knowled...lt-keyboard-reset-on-every-restart-or-reboot-

Apparently 4.1.2 fixes it, but even Swiftkey still say that it doesn't work for a lot of people

.

I've just installed this on my Note 2 so that if the SPen isn't out it will default to Swiftkey, even on boot

.

phil-k · 1 Mar 2013 at 14:54

I have the paid version on 4.1.1, hopefully they will sort it out sometime

mattyfez · 1 Mar 2013 at 17:00

Does not work on 4.1.2 on galaxy S3..

GeX · 5 Mar 2013 at 16:49

Rusty! said:
Both those have a new enough Android version for the bug to have been fixed, it was 4.1 and 4.1.1 that suffered it.

It's a problem on 4.1.2 still for Samsung devices. The Nexus S is technically a Samsung device, but they haven't fettled it.

Bloomfield said:
Did you just buy the app/already own it or did you just try the free version?

On the Nexus 4 it is the paid app. When I using the Nexus S though, I was using the public beta of the 'Flow' feature.. so that may account for it working still on 4.1.2 on that device.