Hi all...
Hope Im in the right section...
I have Swiftkey (paid) installed as I prefer it to the default keyboard...about every 2 days out of nowhere the keyboard resets back to the default android keyboard..I'm not rooted, modded etc. (not exactly bored with the UI yet, be modding soon )
I'm completely stock out of the box.
Happened to anyone else? thanks
cadorette said:
Hi all...
Hope Im in the right section...
I have Swiftkey (paid) installed as I prefer it to the default keyboard...about every 2 days out of nowhere the keyboard resets back to the default android keyboard..I'm not rooted, modded etc. (not exactly bored with the UI yet, be modding soon )
I'm completely stock out of the box.
Happened to anyone else? thanks
Click to expand...
Click to collapse
there's been some folks dealing with this same issue. i've attached the most recent thread. i posted a fix that works for me
http://forum.xda-developers.com/showthread.php?t=2064541
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
Related
Hey guys, I wound up digging around wanting to add Google's Car Home app when I flashed a couple different ROMs and lost the similar app that came from Samsung. It wound up being pretty simple to do and it's been working great on my S3.
I wound up writing it up on my blog, you can find it here:
Manually Installing Google's Car Home App
The steps I wrote aren't necessarily specific to the S3. I had success with a few other Android devices too.
I haven't tried your version yet, but with previous versions on my VZW SGS3 Google Car Home loads and runs fine, but as soon as I customize it (add / remove apps), it no longer loads and FQs.
Have you noticed anything like this with your setup? Thanks!
bradys said:
I haven't tried your version yet, but with previous versions on my VZW SGS3 Google Car Home loads and runs fine, but as soon as I customize it (add / remove apps), it no longer loads and FQs.
Have you noticed anything like this with your setup? Thanks!
Click to expand...
Click to collapse
No, I haven't noticed anything like this at all. That seems weird to me (although, I imagine there's a reason that Google doesn't list many devices as compatible in the Market).
I would recomend trying the version I've got out there and then also maybe installing it as a System App to see if that fixes your FQs?
Neckhole said:
No, I haven't noticed anything like this at all. That seems weird to me (although, I imagine there's a reason that Google doesn't list many devices as compatible in the Market).
I would recomend trying the version I've got out there and then also maybe installing it as a System App to see if that fixes your FQs?
Click to expand...
Click to collapse
I used TB to pull com.google.android.carhome.apk (v2.2.1) and com.google.android.cardock.apk (v2.2) off my Thunderbolt running 4.0.3 (I can't even remember what rom it's running now). After installing both to my GS3 (4.1.1 stock), Car Home seems to be working fine. Good thing, too, because all the alternatives in the play store suck.
mobilejohn said:
I used TB to pull com.google.android.carhome.apk (v2.2.1) and com.google.android.cardock.apk (v2.2) off my Thunderbolt running 4.0.3 (I can't even remember what rom it's running now). After installing both to my GS3 (4.1.1 stock), Car Home seems to be working fine. Good thing, too, because all the alternatives in the play store suck.
Click to expand...
Click to collapse
Any way you could post those APKs?
Well I purchased a couple of i927r's from newegg, got them updated to ICS, rooted. Decided to go with JB rootbox as it seemed to be what I wanted, simple, effective. Just got both phones activated on ST recently, so far been liking them. But a couple issues I am having with them are primarily related to the digital keyboard. I don't really plan on using the physical keyboard much...the phone was at the right price so I guess it's there if I need to use it. But whenever I try to use the digital keyboard for mms, email, searching I hit one letter and it closes. If you keep tapping the word, the keyboard will come back up, but eventually closing again, usually a few keystrokes later.
Both phones do this, both have the most recent rootbox update via goomanager and teamwin. I would post this in the dev thread, but alas I do not have enough posts to. I am searching, but I can't seem to find an answer. I do like the stock digital keyboard, maybe I should try a different one? Anyone else have this issue? The physical keyboard is okay, but I prefer the digital one even on the smaller screen. Thanks for your time.
Have you tried different keyboards.just saying you can try Swype? Or another from the market and see if it still does it.
******************************
Installed:
CWMR5x_i927_recovery.tar.md5
ICS 4.0.4 LiteRom 0.9.0
LiteKernel
Kursah said:
Well I purchased a couple of i927r's from newegg, got them updated to ICS, rooted. Decided to go with JB rootbox as it seemed to be what I wanted, simple, effective. Just got both phones activated on ST recently, so far been liking them. But a couple issues I am having with them are primarily related to the digital keyboard. I don't really plan on using the physical keyboard much...the phone was at the right price so I guess it's there if I need to use it. But whenever I try to use the digital keyboard for mms, email, searching I hit one letter and it closes. If you keep tapping the word, the keyboard will come back up, but eventually closing again, usually a few keystrokes later.
Both phones do this, both have the most recent rootbox update via goomanager and teamwin. I would post this in the dev thread, but alas I do not have enough posts to. I am searching, but I can't seem to find an answer. I do like the stock digital keyboard, maybe I should try a different one? Anyone else have this issue? The physical keyboard is okay, but I prefer the digital one even on the smaller screen. Thanks for your time.
Click to expand...
Click to collapse
This is a known issue and is still being worked on. in the meantime, run rootbox 4.1 ..
yohan4ws said:
This is a known issue and is still being worked on. in the meantime, run rootbox 4.1 ..
Click to expand...
Click to collapse
The default keyboard crashes when used. It is recommended that a third party keyboard is used until the bug is resolved. There's a fair number available on the play store. Avoid any that are directly based on the jelly bean keyboard
I'm using Swifkey 4 (BTW, if you aren't using this, you're missing out) and randomly the keyboard started to revert back to the default after I reboot. Very annoying.
Any suggestions?
seanvree said:
I'm using Swifkey 4 (BTW, if you aren't using this, you're missing out) and randomly the keyboard started to revert back to the default after I reboot. Very annoying.
Any suggestions?
Click to expand...
Click to collapse
It's an issue with SwiftKey. It's not sticking with reboots. Hopefully they fix it in the next release.
Towle said:
It's an issue with SwiftKey. It's not sticking with reboots. Hopefully they fix it in the next release.
Click to expand...
Click to collapse
In the meanwhile (I don't think it's Swiftkey's problem) All you need to do is freeze the stock keyboard and it'll stay on whichever keyboard you assign. You are not the only one having the default keyboard always muscle in after a reboot!
Good Luck!
Aloha.....
Yeah I'm having the same issue, was working fine on SwiftKey Flow Beta. I just uninstalled the android and swyoe keyboard that came with wicked.
Sent from Flip's S3
bobolinko said:
In the meanwhile (I don't think it's Swiftkey's problem) All you need to do is freeze the stock keyboard and it'll stay on whichever keyboard you assign. You are not the only one having the default keyboard always muscle in after a reboot!
Good Luck!
Aloha.....
Click to expand...
Click to collapse
If it's not a SwiftKey problem, my phone just coincidentally started doing this the second I installed SwiftKey 4.. And coincidentally stops doing it whenever I set a different keyboard as default.
bobolinko said:
In the meanwhile (I don't think it's Swiftkey's problem) All you need to do is freeze the stock keyboard and it'll stay on whichever keyboard you assign. You are not the only one having the default keyboard always muscle in after a reboot!
Good Luck!
Aloha.....
Click to expand...
Click to collapse
How do you "freeze the stock" Keyboard?
seanvree said:
How do you "freeze the stock" Keyboard?
Click to expand...
Click to collapse
Either uae titanium backup and look for the keyboard, click on it and you have an option to freeze. Or go to settings>application manager> swipe all the way to the right and look for the keyboard, click on it and it gives you the option of disabling it.
Also I did a fresh install of my rom and now it's sticking after reboots
Sent from Flip's S3
Towle said:
If it's not a SwiftKey problem, my phone just coincidentally started doing this the second I installed SwiftKey 4.. And coincidentally stops doing it whenever I set a different keyboard as default.
Click to expand...
Click to collapse
It is a Google problem that primarily affects people using Android 4.1.1. The play store encrypts paid apps to mnt/asec. The problem is that when android 4.1.1 boots up, it establishes services like keyboards before asec is mounted. This means that SwiftKey isn't seen until after the default keyboard is established. It is supposed to be fixed in 4.1.2.
I cannot speak for the previously mentioned workaround (either for our against) , but I have one that has worked for me. Backup your SwiftKey installation with TiBu, uninstall it, reboot, then restore SwiftKey with TiBu. I hope one of these solutions work for you.
driftinganomaly said:
It is a Google problem that primarily affects people using Android 4.1.1. The play store encrypts paid apps to mnt/asec. The problem is that when android 4.1.1 boots up, it establishes services like keyboards before asec is mounted. This means that SwiftKey isn't seen until after the default keyboard is established. It is supposed to be fixed in 4.1.2.
I cannot speak for the previously mentioned workaround (either for our against) , but I have one that has worked for me. Backup your SwiftKey installation with TiBu, uninstall it, reboot, then restore SwiftKey with TiBu. I hope one of these solutions work for you.
Click to expand...
Click to collapse
I've the same problem with android 4.1.2 MA2 and galaxy s3.
Probably it depends on Swiftkey and not Android itself....
umberto.sulla said:
I've the same problem with android 4.1.2 MA2 and galaxy s3.
Probably it depends on Swiftkey and not Android itself....
Click to expand...
Click to collapse
Did you try the workaround that I mentioned?
FYI: I had he same issue with SlideIt keyboard on 4.1.1. Froze it with TiBu as suggested and it is gone now. Thanks for the suggestion!
at&t I747 w.Swype (from play store)
driftinganomaly said:
It is a Google problem that primarily affects people using Android 4.1.1. The play store encrypts paid apps to mnt/asec. The problem is that when android 4.1.1 boots up, it establishes services like keyboards before asec is mounted. This means that SwiftKey isn't seen until after the default keyboard is established. It is supposed to be fixed in 4.1.2.
Click to expand...
Click to collapse
I just noticed this was the T-Mobile galaxy s3 forum, but I found this through Google, but on my stock at&t I747 when I reboot not only is Swype no longer default, but most of my defaults are reset, so I asked someone @ the at&t store, and they nonchalantly replied, "yeah that's normal". So, reading this response that it's a 4.1.1 issue on xda puts my mind at ease.
I can now just chock it up to another one of those wonderful phenomena (bugs) on this device.
Please excuse any typos, as I wrote this using my gs3 using chrome
If you are rooted, the problem is quite trivial to resolve.
Thank God the guy you spoke to was intelligent enough to give you the right answer. Hes right. Swiftkey Team said any OS under 4.1.2 was affected by that bug.
Sent from my SGH-T999 using Tapatalk 4 Beta
I use ADW paid launcher and when I reboot, I have to choose the default launcher each time. I have Swype and I have the same problem. I've reset the device to full factory a few times and the problem still comes back. I thought that it was only me.
Glad to know I'm not alone.
I reinstalled the rom and didn't choose samsung keyboard but the other one listed, nothing else selected and reboot the phone. Installed SwiftKey and don't have problems anymore with swift not sticking after reboot.
Sent from my SGH-T999
Hey All,
Jelly Beer's 4.2.2 update worked great on my Samsung S3. However, I went out and purchased a new Note 2 GT-N7100 T-Mobile T889. I love the phone. The only problem is that I got used to the keyboard that the guys included in with Jelly Beer 4.2.2 update. In the Input settings, the keyboard is listed as Android keyboard (AOSP). That's the keyboard that I want.
The one that came with the Note 2 is Samsung's own and it's awful. Yes, yes, yes, I've installed just about every other keyboard out there. I've purchased the paid versions and all. Still, nothing does the job as well as the keyboard AOSP. I was literally going to toss the phone because I can't type on it. Then I started to use the gesture part of it, and I'm getting used to that. However, I still want the AOSP one. I've looked all over in the Play store and nothing.
Does anyone have the direct link or the actual .apk that I can download?
Would really appreciate it.
Google keyboard from the play store https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin
Sent from my SGH-T889 using Tapatalk 4
cre8nkhaos said:
Hey All,
Jelly Beer's 4.2.2 update worked great on my Samsung S3. However, I went out and purchased a new Note 2 GT-N7100 T-Mobile T889. I love the phone. The only problem is that I got used to the keyboard that the guys included in with Jelly Beer 4.2.2 update. In the Input settings, the keyboard is listed as Android keyboard (AOSP). That's the keyboard that I want.
The one that came with the Note 2 is Samsung's own and it's awful. Yes, yes, yes, I've installed just about every other keyboard out there. I've purchased the paid versions and all. Still, nothing does the job as well as the keyboard AOSP. I was literally going to toss the phone because I can't type on it. Then I started to use the gesture part of it, and I'm getting used to that. However, I still want the AOSP one. I've looked all over in the Play store and nothing.
Does anyone have the direct link or the actual .apk that I can download?
Would really appreciate it.
Click to expand...
Click to collapse
I am wanting the same thing.
yes, there is a google keyboard in the app store. but its not the same as AOSP, AOSP has the symbols as long hold on the letter keys. and you can long press the "." and slide to choose ?! and others.
I tried pulling out the aosp keyboard from carbon rom, if I just install it, it works, but no sliding to type (like swype) and if I move it to system/app and set permissions, then reset, it just force closes... so... it kind of works... but I would really like to be able to slide type.
Here is a quick tutorial:
I get an error trying to install this over the stock google keyboard.
Try this.
This is the one which was available in Google Play Store, but was removed...
You don't need to uninstall stock keyboard, just install it as another app...
The guy who posted it on the google play store who got it removed because it was the actual stock android L keyboard and thats not allowed, posted it on amazon's app store. This one can be alongside the google keyboard with no problem.
http://www.amazon.com/Shen-Ye-Andro...e=UTF8&qid=1405724912&sr=8-4&keywords=Shen+ye
Misterowl said:
The guy who posted it on the google play store who got it removed because it was the actual stock android L keyboard and thats not allowed, posted it on amazon's app store. This one can be alongside the google keyboard with no problem.
http://www.amazon.com/Shen-Ye-Andro...e=UTF8&qid=1405724912&sr=8-4&keywords=Shen+ye
Click to expand...
Click to collapse
I've been facing some problems using that keyboard since 3 days ago (before that it worked flawlessly.) Every time I press on a text field the Google Voice Input screen appears. I had to uninstall it so I could use the normal keyboard.
Morrissex said:
I've been facing some problems using that keyboard since 3 days ago (before that it worked flawlessly.) Every time I press on a text field the Google Voice Input screen appears. I had to uninstall it so I could use the normal keyboard.
Click to expand...
Click to collapse
That maybe an issue with your rom... then again I don't really know. I have never had issues so I can't really tell you.
Misterowl said:
That maybe an issue with your rom... then again I don't really know. I have never had issues so I can't really tell you.
Click to expand...
Click to collapse
I'm using Stock 4.4.2