• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Samsung keyboard keeps overriding Swift..

J

jlm86

Well-Known Member
How does I get Swift keyboard to remain default keyboard?
Samsung keyboard keeps coming back...
 
Swiftkey had something on their website about there being an issue with Samsung phones that reset the default keyboard from keyboards purchased in the market to the samsung keyboard on reboots. This is because of permissions issues I believe. Is that what you're having problems with?

Or is it resetting the default keyboard even without rebooting?
 
ardyer said:
Swiftkey had something on their website about there being an issue with Samsung phones that reset the default keyboard from keyboards purchased in the market to the samsung keyboard on reboots. This is because of permissions issues I believe. Is that what you're having problems with?

Or is it resetting the default keyboard even without rebooting?
Click to expand...

The purchased apps go into the /sbin/ folder and the os can't access it really enough in the boot process to make SwiftKey active, freezing the Samsung keyboard works because with it frozen there is no other alternative but SwiftKey, eventually, once the os can access /sbin, after a few seconds from reaching the homescreen.
Or something like that anyway.
 
So you have to either freeze the stock keyboard or move the downloaded one to system so the only solution is rooting? How about Tasker, could that be used to change keyboard as soon as the phone boots?
I dont remember having this problem with ICS :confused:
 
funkylogik said:
So you have to either freeze the stock keyboard or move the downloaded one to system so the only solution is rooting? How about Tasker, could that be used to change keyboard as soon as the phone boots?
I dont remember having this problem with ICS :confused:
Click to expand...

It's only with the paid version. If they stepped the paid for code or of SwiftKey and used a separate app to unlock the features, like many do, (power amp, aqua mail etc) then the main Swiftkey app wouldn't be in /sbin and default prefs would stick on reboot. ;)
 
On the Tasker note, this would work I expect.

New profile: KB

+System/event/device boot (as context/trigger)

Task: KB

+Task/wait (set to 5-10 seconds and experiment)
+Input/select input method

Job done ;) all you need after that is to tap on Swiftkey to select :D
 
Cured mine today using the Titanium Backup. I froze the Samsung keyboard and rebooted the phone and my Swiftkey is my permanent keyboard. Took only a few minutes. Gotta love it!

Running S3 MOAR (mother of all roms) v6.1, 7000mah extended battery, and loving it because stock sucks!!
 
I experience the same thing on my S3 and just created a shortcut that I touch once the phone boots... An aside, I also have a 2014 10.1 Note and there is no problem with TouchWiz remembering that Swiftkey is the default... so, I guess it isn't a universal TouchWiz thing...
 
I read on a different forum that the 4.3 update being pushed to AT&T S3's fixes this problem. Being as my HTC that was running 4.1.2 didn't have this problem and after hearing about the issue being fixed I'm going to blame Samsung.
 
Hi, I use the paid for version of SwiftKey, this problem was supposed to be fixed in the last SwiftKey update, it was on mine. Phil
 
I can confirm that Swiftkey works as it should with the 4.3 update. There was also a beta version of Swiftkey that cured the problem but it seemed to be just a trial version so I couldn't figure out how to make it permanent even though I had a paid version also.
 
I don't understand the fuss: I am not rooted and have been using Swiftkey since I got this phone w/o any problems. Tried Google but preferred Swiftkey.

JM
 
mydian said:
I read on a different forum that the 4.3 update being pushed to AT&T S3's fixes this problem. Being as my HTC that was running 4.1.2 didn't have this problem and after hearing about the issue being fixed I'm going to blame Samsung.
Click to expand...

Bingo! I had this problem ever since the 4.1 update and now 4.3 has fixed it (I'm on AT&T).
 
javamann said:
I don't understand the fuss: I am not rooted and have been using Swiftkey since I got this phone w/o any problems. Tried Google but preferred Swiftkey.

JM
Click to expand...

The problem I and many others were having was that if you rebooted the phone it defaulted back to the Samsung keyboard. I didn't have the patience to keep switching it back so I just stopped using swiftkey. After the 4.3 update I have started using it again.
 
i9300 said:
The problem I and many others were having was that if you rebooted the phone it defaulted back to the Samsung keyboard. I didn't have the patience to keep switching it back so I just stopped using swiftkey. After the 4.3 update I have started using it again.
Click to expand...


I had this exact problem since updating to 4.1 I believe and the upgrade to 4.3 fixed it...yeehah.

Luckily have only had one minor issue with 4.3 so far (knocking on wood) but on the flip side exactly what is the benefit? I am having a hard time recognizing any!
 
Erm10 said:
I had this exact problem since updating to 4.1 I believe and the upgrade to 4.3 fixed it...yeehah.

Luckily have only had one minor issue with 4.3 so far (knocking on wood) but on the flip side exactly what is the benefit? I am having a hard time recognizing any!
Click to expand...

I have had issues mainly from waking the device up. A couple of times I have had to pull the battery which I don't recall ever having to do before. Nothing I can't live with for a while though. On the plus side, the phone seems snappier to me. Apart from the wake up issue it seems to be really fast whereas before it sometimes lagged a bit. I haven't found anything else of benefit so far.
 
You must log in or register to reply here.
Back
Top Bottom