New SIII User & Swiftkey Question

shannonkish

Well-known member
Nov 21, 2010
102
4
0
Hey there!

I just got my SIII yesterday. I have been a fan of the Galaxy line for a long time. I had an SII prior and broke the internals when I dropped it. So, upgraded to the SIII.

Question--- Anyone have any issues with Swiftkey remaining the default keyboard? My phone keeps going back to the google keyboard and I have to switch it several times.

Thanks!
 
Yes, it's a Samsung thing (I guess). I think the Samsung software loads earlier in the boot process and makes itself the default keyboard. Not sure if there's a way around it. Nothing that I've found yet.

Sent from my Nexus 7 using Android Central Forums
 
Yup. I looked all over looking for a solution only to end up with the keyboard picker app.

Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
 
Yep me too .. ever since the update to JB, any restart causes the OS to default to the Samsung keyboard.. For me, I just do my best to not restart the phone..My $.02 anyway
 
Don't know anything about SwiftKey but I haven't experienced anything like this with the Kii keyboard.

Sent from my tin can with string attached
 
VZW S3, 4.1.1, Swiftkey, not experiencing this problem.

Blue 32gb Galaxy S3
 
Running the Swiftkey Beta solved the issue, but upgrading to the newest version (4) the issue as returned. Super annoying.
 
Same here, both my S3 and my wife's S3 are experiencing this issue since the Jelly Bean install.

Disappointing.....

________________________________________________________________________

Hey there!

I just got my SIII yesterday. I have been a fan of the Galaxy line for a long time. I had an SII prior and broke the internals when I dropped it. So, upgraded to the SIII.

Question--- Anyone have any issues with Swiftkey remaining the default keyboard? My phone keeps going back to the google keyboard and I have to switch it several times.

Thanks!
 
I would recommend Swype Beta

Sent from my SAMSUNG-SGH-I747 using Android Central Forums
 
Running the Swiftkey Beta solved the issue, but upgrading to the newest version (4) the issue as returned. Super annoying.

I find it curious since folks have said Swiftkey blames it on JB 4.1.1 (and can do nothing about it), yet SK beta didn't have that issue. I'm running SK 4.0.0.106 and it has the issue.
 
Have you gone into application management and cleared the cache memory on the Samsung keyboard I had the same problem and I believe this fixed it

Sent from my SGH-I747M using Android Central Forums
 

Forum statistics

Threads
952,721
Messages
6,957,315
Members
3,162,722
Latest member
rochell3