Related
Anyone been able to get SWYPE working? I've cleared cache, wiped data from the SWYPE app, reinstalled it, tried different versions - nothing but FCs...
My reply isnt very helpful, but I have it working on my Aria. Im running Liberated FR006, but I dont think there should be any difference between Swype working on FR006 and FR007
I just got the invite from Swype beta, and the keyboard's working perfectly fine. So I don't know why it isn't working for you?
It's working for me without a hitch on FR007. The only problems I can think of are either that some app is causing interference with Swype or the ROM itself. Maybe you should wipe and install FR007 again, install Swype first to see if it works and then slowly install everything else one-by-one.
I'm running fr007 also, no hitches for me either
Sent from my HTC Liberty using XDA App
Just reinstalled it on mine, FR007. I did have an issue a few days ago with it telling me I was using a version for a different device, but I deleted both the program and the installer and it worked. I'm in the beta if that helps
Think having other keyboards installed, but not "checked" would cause problems?
(NM - Wiped my other keyboards - still have the problem)
uninstall the app, and then uninstall the installer. and then reinstall.
if that doesnt work - do a clean FR007 image, cause I dont see others having the same issue?
I'm on fr007, Swype beta seems to be working fine. I got the email an hour ago for the download and am having no problems.
Sent from my HTC Liberty using XDA App
Mine is working fine on both FR007 and FR008. That is, until I re-boot the phone. Then when I go to the Swype keyboard (in any app that uses it), the keyboard appears fine, but the "swyping" aspect doesn't work at all. I can still "hunt and peck", but not swype the words. I then have to uninstall swype, and reinstall (starting from the user login, download, and all). It works fine until the next re-boot.
I still haven't figured out why it does this. I'm wondering if wiping all data associated with Swype would work. I assumed that a re-install would overwrite it, but could be wrong.
For those who have gotten it to work on FR008 (my preferred ROM), did you wipe all Swype associated data first?
Thanks
Dave
I know it seems stupid, but try running the Swype Tutorial. For some reason that is what has gotten Swype to "stick" as my default keyboard the last two times I've installed it. (Once on my Aria running CM 6.1 RC2 and the other time on my friend's Aria with a fresh FR008 install.)
SPD387 said:
Mine is working fine on both FR007 and FR008. That is, until I re-boot the phone. Then when I go to the Swype keyboard (in any app that uses it), the keyboard appears fine, but the "swyping" aspect doesn't work at all. I can still "hunt and peck", but not swype the words. I then have to uninstall swype, and reinstall (starting from the user login, download, and all). It works fine until the next re-boot.
I still haven't figured out why it does this. I'm wondering if wiping all data associated with Swype would work. I assumed that a re-install would overwrite it, but could be wrong.
For those who have gotten it to work on FR008 (my preferred ROM), did you wipe all Swype associated data first?
Thanks
Dave
Click to expand...
Click to collapse
does that to me now and then. install titanium backup, make sure swype is working normally, and do a backup. then when it stops working again just restore data with titanium. Stupid, but it works.
My phone is unrooted, unlocked and on Vodafone
Just installed OTA gingerbread and now I can't use the keyboard for messages/emails, when I tap into an input text box, nothing happens. Long press brings up a little bar (used to have icons for selecting text etc but now its empty)
Android version 2.3.3, HTC Sense 2.1, baseband 12.54.60.25U_26.09.04.11_M2, kernel 2.6.35.10-g0956377, build 2.36.405.8 CL47853, software 2.36.405.8
Any body else had this? Any ideas?
OK now - uninstalled swype and adw launcher and after 4th reboot keyboard came back
both reinstalled and keyboard is still OK
In fact I had the same problem, and you don't need to uninstall swype in the end, just click 'Generate Lisense' and follow the steps there.
I couldn't get my stock keyboard to work when I got to the step where I had to type in my username and password, then I realised the installer has actually frozen, so I force closed it and reopen it to type things in. Done.
I've had a similar issue before. Just download the gingerbread keyboard.apk and reinstall it.
I think this is likely an issue with swype considering your license to be duplicated after the update, and blocking the use of it (the identifier for your license is probably tied to the software version you are on).
I have approximately same issue with my HTC Desire S after I updated it to 2.3.5
The phone is new, not rooted (untouched)
please help me to fix it :-(
aref_tmu said:
I have approximately same issue with my HTC Desire S after I updated it to 2.3.5
The phone is new, not rooted (untouched)
please help me to fix it :-(
Click to expand...
Click to collapse
I assume you've tried all the above suggestions, including installing gb keyboard from market and they've failed?
Sent from my HTC Desire HD using Tapatalk
Using the latest (r8) Modaco CM. I don't know what happened, but all of a sudden gesture typing on aosp keyboard doesn't work. It shows the gesture trail but the word suggestion box is blank. Cleared all data/cache for keyboard already.
I tried removing AOSP keyboard with Titanium and installing manually but still the same result. Even tried dirty flashing my rom over.
In desperation, I fully wiped and switched to PA, and the same result.
I suspect there's a setting somewhere I'm missing or have to clear something first.
I've been so used to using this and Swype that I can't deal with that primitive thumb typing anymore lol.
Thanks in advance.
Did you flash an unmodified build of Gapps? It seems more of a software error.
so i tried to install a themed keyboard on my nexus 6p. i had to uninstall the stock one first, i did that, the themed one didnt work so i just reinstalled the stock one. everything seemed to be working until i rebooted and it asked me to enter pin. theres no keyboard there now. any ideas?
I'm not sure what happened, but my Google Keyboard seems to have disappeared. Google Keyboard is not showing as an option under "Keyboard & input methods". I have Flesky and Swiftkey, so I'm getting by, but I don't know how to get it working. Gboard shows under Apps, and I've tried clearing cache, clearing data, force stop, and uninstall/reinstall, but it still doesn't appear as an option to use as a keyboard. How can I rectify this? Thanks in advance to anyone who has a solution.
sbs8331 said:
I'm not sure what happened, but my Google Keyboard seems to have disappeared. Google Keyboard is not showing as an option under "Keyboard & input methods". I have Flesky and Swiftkey, so I'm getting by, but I don't know how to get it working. Gboard shows under Apps, and I've tried clearing cache, clearing data, force stop, and uninstall/reinstall, but it still doesn't appear as an option to use as a keyboard. How can I rectify this? Thanks in advance to anyone who has a solution.
Click to expand...
Click to collapse
Google keyboard is replaced by Gboard but I think you already knew that. Also if you are on a custom ROM flash Gapps again. Gboard will appear on input options. If not maybe you have factory reset or wait for the app to be updated again .
PS did you reboot after clearing cache?
guessingagain said:
Google keyboard is replaced by Gboard but I think you already knew that. Also if you are on a custom ROM flash Gapps again. Gboard will appear on input options. If not maybe you have factory reset or wait for the app to be updated again .
PS did you reboot after clearing cache?
Click to expand...
Click to collapse
Thanks for the reply. I'm not rooted and therefore don't have a custom ROM, just the one that came with the device, so therefore I can't really flash anything. I went into recovery mode and did a cache wipe there, which, of course, requires reboot, to no avail. I'll wait to see if an update comes out soon and will live with 3rd party keyboards in the meantime. For what it's worth, I've included screen shots showing that Gboard is showing as an app but is not showing as an available keyboard. When I click "Current Keyboard", my only options are Flesky and Swiftkey.
The reply is appreciated.
sbs8331 said:
Thanks for the reply. I'm not rooted and therefore don't have a custom ROM, just the one that came with the device, so therefore I can't really flash anything. I went into recovery mode and did a cache wipe there, which, of course, requires reboot, to no avail. I'll wait to see if an update comes out soon and will live with 3rd party keyboards in the meantime. For what it's worth, I've included screen shots showing that Gboard is showing as an app but is not showing as an available keyboard. When I click "Current Keyboard", my only options are Flesky and Swiftkey.
The reply is appreciated.
Click to expand...
Click to collapse
Sorry to hear. If you do manage to get it fixed please reply to this thread. Thanks. I am on 7.0 and Gboard is running fine.
guessingagain said:
Sorry to hear. If you do manage to get it fixed please reply to this thread. Thanks. I am on 7.0 and Gboard is running fine.
Click to expand...
Click to collapse
Update: I finally got Gboard back. I tried a number of things, including a manual download and install of the apk. I decided to try Slash keyboard, and, when I installed it, I was taken to the screen to enable it, and, voila', Gboard shows up with an enable option. I don't know what happened, but it's working now.
sbs8331 said:
Update: I finally got Gboard back. I tried a number of things, including a manual download and install of the apk. I decided to try Slash keyboard, and, when I installed it, I was taken to the screen to enable it, and, voila', Gboard shows up with an enable option. I don't know what happened, but it's working now.
Click to expand...
Click to collapse
Actually, in your second screenshot, if you tap on "Current Keyboard" there will be a button to choose keyboard. If you press that, it will bring you to the screen where you can enable/disable keyboards. That's probably why Gboard was hidden.
doomed151 said:
Actually, in your second screenshot, if you tap on "Current Keyboard" there will be a button to choose keyboard. If you press that, it will bring you to the screen where you can enable/disable keyboards. That's probably why Gboard was hidden.
Click to expand...
Click to collapse
Yep. Not intuitive to me, but you're correct. I thought "Current Keyboard" was just a prompt to select one from the pop-up window. Often the answers are simple if you know where to look. Thanks! :good:
sbs8331 said:
Yep. Not intuitive to me, but you're correct. I thought "Current Keyboard" was just a prompt to select one from the pop-up window. Often the answers are simple if you know where to look. Thanks! :good:
Click to expand...
Click to collapse
No worries! They changed the menu structure in Nougat so it's more intuitive now.
Probably off topic but does anyone else not like the update they did to the keyboard? No way to remove that search menu row? I have never used the suggestions and wished I could remove it.
daverobinson88 said:
Probably off topic but does anyone else not like the update they did to the keyboard? No way to remove that search menu row? I have never used the suggestions and wished I could remove it.
Click to expand...
Click to collapse
Go to input > virtual > Gboard > settings > search and disable it.
It removes the search G but still keeps the row there. See attachment.
daverobinson88 said:
It removes the search G but still keeps the row there. See attachment.
Click to expand...
Click to collapse
Yeah that's true. I can't find an option to disable that. Maybe it's not possible in this update.
I am sort of in the same boat
Hey everyone.
Lastnight I installed, an android 7.0 custom rom to my tab pro 10.1. I used TWRP to flash install the ROM when it installed it automatically rebooted my device before I could go on to Gapps and install them with the the ROM. So when the ROM loaded up I connected to my hub (using the keyboards) then had a look at the new OS and the wife had a look out of interest with me and everything was working well in fact it was quicker than it was when we got it brand new.
Then playtime over rebooted back into TWRP and flashed Gapps. Then it rebooted again. When it finally loaded back in I was met with a loading screen saying Android is Starting which wouldn't go away but it asked me to sign back on to the Hub so went to do this on problem was.....no Keyboard.....so I managed to get into my setting through quick menu settings and find input settings and there is no keyboard installed to the device...it asked me to add one but I can't because I can't type and even if I could the android is starting message is still going.
Please help I am new to this and I want to learn all this type of thing but I am completely puzzled on what to do. I tried clear chase and data and even tried factory reset.....tried installing gapps on twice (before the factory reset) and nothing was working.
I am tough to use odin to flash it back to standard rom and start again but I could do with some pointers with what i have done wrong.
Thanks people
Owenboy89 said:
Hey everyone.
Lastnight I installed, an android 7.0 custom rom to my tab pro 10.1. I used TWRP to flash install the ROM when it installed it automatically rebooted my device before I could go on to Gapps and install them with the the ROM. So when the ROM loaded up I connected to my hub (using the keyboards) then had a look at the new OS and the wife had a look out of interest with me and everything was working well in fact it was quicker than it was when we got it brand new.
Then playtime over rebooted back into TWRP and flashed Gapps. Then it rebooted again. When it finally loaded back in I was met with a loading screen saying Android is Starting which wouldn't go away but it asked me to sign back on to the Hub so went to do this on problem was.....no Keyboard.....so I managed to get into my setting through quick menu settings and find input settings and there is no keyboard installed to the device...it asked me to add one but I can't because I can't type and even if I could the android is starting message is still going.
Please help I am new to this and I want to learn all this type of thing but I am completely puzzled on what to do. I tried clear chase and data and even tried factory reset.....tried installing gapps on twice (before the factory reset) and nothing was working.
I am tough to use odin to flash it back to standard rom and start again but I could do with some pointers with what i have done wrong.
Thanks people
Click to expand...
Click to collapse
You may wish to ask over in the Galaxy Tab Pro forums at https://forum.xda-developers.com/galaxy-tab-pro-12-10-8 - you've somehow wandered into the Moto G4 forums
But as a very general suggestion - sounds like your GApps isn't happy with your custom ROM. You may have to clean flash your custom ROM again and verify that the GApps you're flashing is suitable for your device/custom ROM.
I agree with you I have just download the same rom and a stock gapps and I had the same message and again with no keyboard.....agian. Difference this time I haven't rushed to do a factory reset and gone back and reflashed the android 7.0 rom and I am back working again with keyboard but no google apps.
Is there a way of installing them a different way, only 2 google apps I use is play store and gmail. I have tried installing a google play store and play services apk but doesn't work. It goes to load and then just stops.....feels like I need a list of apps to get them going.
Hope someone can help
I worked out my problem with Gapps, "android is starting messages" and no keyboard.
1. I needed to wipe my cache, data and davarlik (whatever it says....looks like darlik to me...lol) before and after.
2. Like fella before said my ROM didn't like the Gapps package I had downloaded, so everytime I had the android message I went back on to TWRP and restored back to the orginal point where the lineage ROM worked, then went back on to the net and installed the next Gapps package and repeated till I found a package that worked......that package was the "Micro" package.
Any google apps I was missing I simply just downloaded them via the playstore after.
I realise this is a moto G forum but I find that sometimes you need to go other places to find answers and I had originally looked in the samsung Tab Pro 10.1 forum section and couldn't find anything similar to my problem this fella at the beginning of the thread was the closest to my problem I could fine.
Hope this helps