Related
Maybe it's since the JB upgrade, but my keyboard keeps resetting to the Default Samsung 3, from Swiftkey 3. Could also have been from installing the Swiftkey Flow beta.
Anyone else experience this, and what can I do to stop it.
dratsablive said:
Maybe it's since the JB upgrade, but my keyboard keeps resetting to the Default Samsung 3, from Swiftkey 3. Could also have been from installing the Swiftkey Flow beta.
Anyone else experience this, and what can I do to stop it.
Click to expand...
Click to collapse
I think if you go to the buglist at swiftkey.net you'll find you aren't alone. I'm using the Swiftkey Flow beta and this problem hasn't occurred...yet. You can turn of the Flow feature and it becomes a regular Swiftkey keyboard.
I use Smart Keyboard Pro off of the market and the same thing keeps happening to me. By that I mean I don't use swype and my settings keeps rolling back to the regular keyboard.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
dratsablive said:
Maybe it's since the JB upgrade, but my keyboard keeps resetting to the Default Samsung 3, from Swiftkey 3. Could also have been from installing the Swiftkey Flow beta.
Anyone else experience this, and what can I do to stop it.
Click to expand...
Click to collapse
I've found that these problems can sometimes can be fixed by uninstalling and reinstalling the keyboard.
I did a factory reset and it still happened.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
jeffdaman said:
I did a factory reset and it still happened.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Could you describe how this is happening? Does it switch keyboards after you use a certain app, or does it just switch at random times? One thing you could try is to disable all other keyboards under applications. This way, the phone has to keep using your keyboard.
Happens for me after a reboot. Always goes back to Samsung keyboard. Once I change to SwiftKey, it stays that way until the next reboot. As others have said, seems like a bug between JB and SwiftKey 3 (without Flow beta)
It happens every time I restart and then it would happen randomly while using the phone. I thing Task Manager by Rythm Soft was killing Smart Keyboard but I got it on the ignore list now; and so far it seems limited to the restart. It's not possible to disable Swype or the Samsung Keyboard. They are greyed out on the list.
To the O.P. you should check any task managers to be sure Swype isn't being killed.
MobileNick said:
Happens for me after a reboot. Always goes back to Samsung keyboard. Once I change to SwiftKey, it stays that way until the next reboot. As others have said, seems like a bug between JB and SwiftKey 3 (without Flow beta)
Click to expand...
Click to collapse
Same thing is happening to me. Always after a restart it falls back to the Samsung Keyboard.
If you guys are rooted make a back up of the Samsung keyboard then delete it. From system/app i know that worked on the early sprint JB leaks
Sent from my SGH-I747 using xda premium
brorex said:
If you guys are rooted make a back up of the Samsung keyboard then delete it. From system/app i know that worked on the early sprint JB leaks
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Anyone try this, and what does it default to if you do remove the Samsung Keyboard? I have several inputs, WiiMote, PS3, etc. If I have to keep changing the default back to Swiftkey, then this option would get annoying.
Known Bug with Work-Around
dratsablive said:
Maybe it's since the JB upgrade, but my keyboard keeps resetting to the Default Samsung 3, from Swiftkey 3. Could also have been from installing the Swiftkey Flow beta.
Anyone else experience this, and what can I do to stop it.
Click to expand...
Click to collapse
This is a known bug with JB 4.1.x.....
Swiftkey has it mentioned in a bug list as well as Google in a bug list...
It has something to do with apps getting installed differently and storing app data differently with JB. When a phone reboots the storage location for that app's data is not mounted or available right away so the app can't load and therefore the phone switches to the default keyboard.
Happens with a few other apps like AT&T Vooicemail Viewer.
The work-around is to root the phone, backup the app with Titanium Backup, uninstall the app, then restore it without data. Then set the keyboard as default and it should stay that way after re-boots.
Good luck!
Boomer6345 said:
This is a known bug with JB 4.1.x.....
Swiftkey has it mentioned in a bug list as well as Google in a bug list...
It has something to do with apps getting installed differently and storing app data differently with JB. When a phone reboots the storage location for that app's data is not mounted or available right away so the app can't load and therefore the phone switches to the default keyboard.
Happens with a few other apps like AT&T Vooicemail Viewer.
The work-around is to root the phone, backup the app with Titanium Backup, uninstall the app, then restore it without data. Then set the keyboard as default and it should stay that way after re-boots.
Good luck!
Click to expand...
Click to collapse
Might wait for Google or Swiftkey to fix the bug. If I restore without the data, then I lose all the words Swiftkey has learned.
This is really odd. A few weeks ago I downloaded the SwiftKey Flow Beta and this problem disappeared. That is, after a reboot my default keyboard would stay on SwiftKey Flow Beta. But yesterday SwiftKey released the official version 4 with Flow integrated. And now the problem is back - reboot makes Samsung Keyboard as default.
So what did the Beta do that was so special that it would stay after a reboot??
MobileNick said:
This is really odd. A few weeks ago I downloaded the SwiftKey Flow Beta and this problem disappeared. That is, after a reboot my default keyboard would stay on SwiftKey Flow Beta. But yesterday SwiftKey released the official version 4 with Flow integrated. And now the problem is back - reboot makes Samsung Keyboard as default.
So what did the Beta do that was so special that it would stay after a reboot??
Click to expand...
Click to collapse
Same. Reboot causes the problem. Not a huge issue, but odd.
cfn87 said:
Same. Reboot causes the problem. Not a huge issue, but odd.
Click to expand...
Click to collapse
It's a change in the way Jellybean handles how Google Play apps are loaded during boot process, since they happen after the keyboard gets loaded, it reverts to default.
Boomer6345 said:
This is a known bug with JB 4.1.x.....
Swiftkey has it mentioned in a bug list as well as Google in a bug list...
It has something to do with apps getting installed differently and storing app data differently with JB. When a phone reboots the storage location for that app's data is not mounted or available right away so the app can't load and therefore the phone switches to the default keyboard.
Happens with a few other apps like AT&T Vooicemail Viewer.
The work-around is to root the phone, backup the app with Titanium Backup, uninstall the app, then restore it without data. Then set the keyboard as default and it should stay that way after re-boots.
Good luck!
Click to expand...
Click to collapse
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
xBeerdroiDx said:
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
Where would this location be?
dratsablive said:
Where would this location be?
Click to expand...
Click to collapse
via a google search
MobileNick said:
This is really odd. A few weeks ago I downloaded the SwiftKey Flow Beta and this problem disappeared. That is, after a reboot my default keyboard would stay on SwiftKey Flow Beta. But yesterday SwiftKey released the official version 4 with Flow integrated. And now the problem is back - reboot makes Samsung Keyboard as default.
So what did the Beta do that was so special that it would stay after a reboot??
Click to expand...
Click to collapse
Sorry if this was already covered...but I read a post at the Swiftkey site that the issue is with Paid apps on JB. Not all paid apps of course...but some paid apps like Swiftkey install to this special storage location that is not available soon enough during the boot process.
The 4.x Swiftkey beta was not a paid app so it worked...now that the beta is released it is a paid app and the Swiftkey 4.x release in Google Play has the issue again on JB just like 3.x did.
Well 1st i did root my phone and i belive i might had unistalled a program. Anyways to bring it back to factory settings with all apps?
Used motochopper To root my phone.
Thank you in advance.
Edit: I have the SGH-M919
Murderah said:
Well 1st i did root my phone and i belive i might had unistalled a program. Anyways to bring it back to factory settings with all apps?
Used motochopper To root my phone.
Thank you in advance.
Edit: I have the SGH-M919
Click to expand...
Click to collapse
You don't have to bring the phone back to stock. In Settings, change the voice input to Google Voice/ Speech (don't remember what exactly it's called).
If you do decide to go back to stock, follow this:
http://forum.xda-developers.com/showthread.php?t=2258628
samsung text-to-speech stopped
To change it go to Settings / My device / Language and input / Text-to-Speech / and change Samsung to Google text-to-speech
sybor said:
To change it go to Settings / My device / Language and input / Text-to-Speech / and change Samsung to Google text-to-speech
Click to expand...
Click to collapse
Same problem here. Fix changing to google tex-to-speech works, but the S Voice does not respond to me after I ask any question, freezes and closes.
I do not know if the problems are related.
Any help?
Thanks!
If you delete chaton it breaks the svoice I think
Sent from my SGH-M919 using xda app-developers app
Is there any work around to solving this problem? I need help my s4 is having the same issues. I changed to Google speech still didn't work.
Sent from my GT-I9500 using xda premium
Go into svoice settings and check the use the home button option.
I had this problem, too, after deleting one too many apps. I fixed it by installing one of the ROMs in the development section, then used Titanium Backup to FREEZE the bloat, rather than delete it. That way, if it caused unexpected problems, I could defrost it and return to normal.
Thanks to ferganer!!
Had that fricken text-to-speech engine problem.Wanted to lighten up the ROM and prolly uninstalled something....
Now switched the engine to Google and everything works!! Don't need to restore the ROM!!
Thanks again.
Tester
Tester30 said:
Thanks to ferganer!!
Had that fricken text-to-speech engine problem.Wanted to lighten up the ROM and prolly uninstalled something....
Now switched the engine to Google and everything works!! Don't need to restore the ROM!!
Thanks again.
Tester
Click to expand...
Click to collapse
It's definitely related to the "Chat On" app/s. I enabled those back and haven't gotten that message since.
Matt
That's weird, I'm running Wicked ROM with no ChatOn app (or most Samsung bloatwares) both my Samsung TTS and Google TTS engine work just fine.
My screen won't turn off. when u turn it off it stays off for about 1-2 seconds and then turns back on. it must have been a particular system app I uninstalled. I was thinking It was because I unistalled the home system apps, which elsewhere are list as safe for removing as long as u replace it first. I was able to reinstall them, but not sure if they are reinstalled right. I did see another guy whom when he reinstalled certain system apps he had to rename them first. I can't find the post. So far that doesn't work.
1. does anybody know which system app I uninstalled or did to do this?
2. does anyone know the proper name to rename the home app apk for re-installation?
3. if this happens to anyone else I have found that using the "Redeye - Stay wake" app, Power on volume (button fix), and the "Desktop Visualizer (for creating customized shortcut) seemed to be a temporary fix until I find out what I did.
Anyone?
AC
Sent from my LG-E980 using Tapatalk
Attackcenter said:
My screen won't turn off. when u turn it off it stays off for about 1-2 seconds and then turns back on. it must have been a particular system app I uninstalled. I was thinking It was because I unistalled the home system apps, which elsewhere are list as safe for removing as long as u replace it first. I was able to reinstall them, but not sure if they are reinstalled right. I did see another guy whom when he reinstalled certain system apps he had to rename them first. I can't find the post. So far that doesn't work.
1. does anybody know which system app I uninstalled or did to do this?
2. does anyone know the proper name to rename the home app apk for re-installation?
3. if this happens to anyone else I have found that using the "Redeye - Stay wake" app, Power on volume (button fix), and the "Desktop Visualizer (for creating customized shortcut) seemed to be a temporary fix until I find out what I did.
Anyone?
AC
Sent from my LG-E980 using Tapatalk
Click to expand...
Click to collapse
If you deleted LG Home, that's your problem. That's the LG stock launcher. Your phone is technically booting, but it cannot get to the desktop without a launcher, basically. The thing is that you need both the app and the odex files to be properly installed for the LG Home launcher to function.
Do you have a backup? If not, you'll need to reflash the ROM. Do you have another launcher installed?
hey.
i had read that someone said that you can uninstall your native lg home apps as long as have an replacement launcher in place first. I already had nova prime launcher installed before I uninstalled the native lg home launcher apps? this wont work?
I did make an app backup of the native home launcher apps with "titanium backup" and "app master" (Uninstall master). is this sufficient?
AC
Sent from my LG-E980 using Tapatalk
I did find that I already had the APKs backed up from what I previously mentioned. I checked my root/system/apps directory and the odex files are there too. what do I do now? or do I need to do anything since I already previously had nova prime installed before I uninstalled the native lg home apps and that should have be fine?
AC
Sent from my LG-E980 using Tapatalk
Attackcenter said:
I did find that I already had the APKs backed up from what I previously mentioned. I checked my root/system/apps directory and the odex files are there too. what do I do now? or do I need to do anything since I already previously had nova prime installed before I uninstalled the native lg home apps and that should have be fine?
AC
Sent from my LG-E980 using Tapatalk
Click to expand...
Click to collapse
It won't use Nova unless it was set to use it, so it's not going to really matter.
It could be that the files were corrupted when you tried to reinstall them manually. I've had the same sort of issues with NFC and Bluetooth resources. I deleted then and then tried to reinstall them and produced the same sort of thing you described. I had no choice but to flash back to stock via the uber-crappy LG tools.
Let me try to understand. If you install Nova Prime while u still have a perfectly good working copy of LG home and then Uninstall LG home what is the problem? how would it not be set to use nova?
AC
Sent from my LG-E980 using Tapatalk
Attackcenter said:
Let me try to understand. If you install Nova Prime while u still have a perfectly good working copy of LG home and then Uninstall LG home what is the problem? how would it not be set to use nova?
AC
Sent from my LG-E980 using Tapatalk
Click to expand...
Click to collapse
There's a separate laucher/Home chooser component in the LG Home software that, unless it is set to use another launcher (which it can be in the settings) it will continue to look for LG Home and try to launch it. If it's been deleted, you'll have a mess.
Didn't you say that you tried to reinstall it also? I don't think it was perfect after reinstallation. It should be, but again, I used Titanium Backup to delete and reinstall some system components, and it did not work, even though the components seemed to be installed/restored correctly.
In reality, they weren't.
Fixed. Thanks donalgodon. That worked. my problem was that I had installed nova prime, but did not make it the default before Uninstalling the lg native home apps. So I found I had backups of lg home apk/data, lg selector apk/data, and of the lg optimus theme. the reason my previous restore did not work was because I was trying to restore the apk only with app master (master Uninstaller) which did not have the capability to restore data also for apps. I used titanium backup to restore my apk/data backup from last month of 1st the selector, then lg home, a d then the lg theme. it work perfectly. Then in made nova prime my default launcher. I tested the sleep awake functionality and it once again was working. I then uninstalled again the lg home selector, the lg home, and the Optimus theme. everything went perfectly.
AC
Sent from my LG-E980 using Tapatalk
Might wanna move Nova to /system/app and fix the permissions just as a precaution.. If you decide to do a factory reset, you'll be right back where you started lol.
Sent from my CM11 LG-E980
lol. thanks neroga. done. used the app system application manager by flaki.
AC
Sent from my LG-E980 using Tapatalk
Anyone read about this yet? I read about it in the guardian. It seems the chances are fairly slim if you watch what networks you connect to, but i would still prefer to have this issue fixed. Since i am running a custom rom without knox, i will not get any fix OTA. Any ideas for custom rom users?
For reference:
http://www.theguardian.com/technology/2015/jun/17/samsung-keyboard-bug-android-hack
http://arstechnica.com/security/201...ng-galaxy-phones-into-remote-bugging-devices/
I'm paranoid; I found /system/app/ SamsungIME and /system/lib/libswiftkeysdk-java.so and moved them permanently to ExtSdCard/downloads just for safekeeping. I looked for other files associated in /data/data and /data/dalvik-cache but found none. Rebooted with no issue; just don't try to select swiftkey as default in Settings/Language and input.
IDK how this swiftkey dictionary update works so I'm thinking there's still some or all security vulnerability. Anyone know? I searched pages of Google Search but currently filled with vulnerability issue and updates.
No Knox here either. I've long used Swype paid customized with top number row. Had no idea the swiftkey dictionary was updating in the background despite not being the default dictionary.
Sent from my SM-N910P using Tapatalk
Since most of us on xda have root, just wipe data and uninstall it with titanium backup. I'm maybe thinking user dictionary should be wiped and uninstalled. I'll back both up and check if everything is ok. It's no skin off my back, I've used Swype since it first appeared on android and that has its own dictionary it backs up.
I also could be wrong and uninstalling these may not prevent anything. But these are still parts of the rom that are not needed for me and hasn't hurt anything yet.
If any devs could chime in if they know that would be great.
Just decided to freeze the dictionary. Wasn't but 52 kB of data, 12kB cache there per application manager.
Sent from my SM-N910P using Tapatalk
I've got 2 issues, prediction keeps switching itself off all the time, and I just cannot get curve (swype) to work despite trying every combination of TouchPal settings, any ideas?
Sent from my HTC 10 using XDA-Developers mobile app
I couldnt stand touchpal. I use google keyboard and deleted touchpal and all its lanugage packs, skins etc (requires root). Much better now.
Just found solution to Swype, you have to update the language as htc only included basic language.
Sent from my LG-D855 using XDA-Developers mobile app
Holding off on root, but its killing me as no proper app backup solution, need to read up as htc is sooo different to sammy/lg
Sent from my LG-D855 using XDA-Developers mobile app
gsw5700 said:
Holding off on root, but its killing me as no proper app backup solution, need to read up as htc is sooo different to sammy/lg
Sent from my LG-D855 using XDA-Developers mobile app
Click to expand...
Click to collapse
You probably already know about this but to back up my app data I used helium from clockwork mod. It doesn't require root and all you need to do is enable USB debugging. That's what I used to back up my game data and other things when I switched from my one m9 to the 10.
For my call logs and text messages I used SMS backup and restore which worked flawlessly. The only thing left to do after that was to export my contacts to my SD card and I was set to go. It took me about 25 minutes to get everything up and going on the new phone not including system updates and application updates of course which you can't avoid
I hope that helps out some
Thanks, I am aware of helium but thought it may be a bit of a hassle. I'm used to titanium backup, LG has its own awesome backup utility.
Not too sure about flashing twrp/root yet as it stops OTA updates. So left with custom rom and wait for that rom to get OTA included. Looking forward to custom roms, custom kernel, heavy debloating, easy backup and restore. Still not sure how you flash HTC 10 back to stock!
Sent from my HTC 10 using XDA-Developers mobile app
gsw5700 said:
Thanks, I am aware of helium but thought it may be a bit of a hassle. I'm used to titanium backup, LG has its own awesome backup utility.
Not too sure about flashing twrp/root yet as it stops OTA updates. So left with custom rom and wait for that rom to get OTA included. Looking forward to custom roms, custom kernel, heavy debloating, easy backup and restore. Still not sure how you flash HTC 10 back to stock!
Sent from my HTC 10 using XDA-Developers mobile app
Click to expand...
Click to collapse
In my experience helium is not a hassle to use at all. If you've never used it before you basically turn on USB debugging install the app from the play store and install the application from the website on your computer. After you do that plug your phone into your computer and launch the application on your phone. It then comes up with a list of all the applications on your phone, you can either press select all or individually select the applications you would like to back up. Once you do that you push a button and a few moments later everything is done.
One thing to note is that it creates a folder named carbon on the root of the internal storage of the phone, just remember to move that folder over to your SD card before you start experimenting with anything that may require wiping the phone. I have used titanium backup in the past as well and while the helium method may not be just as easy it is the absolute best solution out there for people that don't already have a rooted device
dabbler77 said:
I couldn't stand touchpal. I use google keyboard and deleted touchpal and all its lanugage packs, skins etc (requires root). Much better now.
Click to expand...
Click to collapse
Just a heads up. Do not delete TouchPal like i did. My phone asked for the password for encrypted data at boot - it hadn't loaded the google keyboard, and as I deleted touchpal from system I had no keyboard! Only option was to restore. I've now left touchpal (minus all the language packs) in my rom, for some reason Google keyboard couldn't be moved to system. Oh well.
Hi I'm using Swiftkey but tried many keyboard. All are giving me a problem in the p button and keyboard being too sensitive. It types the same letter three times. Can anyone help
himesh82 said:
Hi I'm using Swiftkey but tried many keyboard. All are giving me a problem in the p button and keyboard being too sensitive. It types the same letter three times. Can anyone help
Click to expand...
Click to collapse
Hello,
I am an official moderator from SwiftKey, can you go to our community to post your issue?
Appreciate!
Alpert
---------- Post added at 09:52 AM ---------- Previous post was at 09:50 AM ----------
dabbler77 said:
Just a heads up. Do not delete TouchPal like i did. My phone asked for the password for encrypted data at boot - it hadn't loaded the google keyboard, and as I deleted touchpal from system I had no keyboard! Only option was to restore. I've now left touchpal (minus all the language packs) in my rom, for some reason Google keyboard couldn't be moved to system. Oh well.
Click to expand...
Click to collapse
Oh buddy, that's sad...
Just do not activate TouchPal in language&keyboard menu?
dabbler77 said:
Just a heads up. Do not delete TouchPal like i did. My phone asked for the password for encrypted data at boot - it hadn't loaded the google keyboard, and as I deleted touchpal from system I had no keyboard! Only option was to restore. I've now left touchpal (minus all the language packs) in my rom, for some reason Google keyboard couldn't be moved to system. Oh well.
Click to expand...
Click to collapse
Yeah. Disable touchpal doesn't stop force install on language packs. I'm disappointed there's no option to remove this on play store.
Sent from my HTC 10 using Tapatalk