Hi,
My keyboard doesnt work properly after installing this rom: http://forum.xda-developers.com/showthread.php?t=2071694
when you push somewhere to type after typing the first letter, the keyboard disappears and you have to push the text field area again to get the keyboard back, this happens in every word, so as soon as you are done typing your first word and push space and start typing the first letter again this happens!
i am using the wifi tab 10.1 from samsung. running cwm 5.5
I changed back to android 4.1 and its working fine in that one.
anything i can do to fix this?
Any other keyboard from the market. I went with SwiftKey to fix it. Changing to a different gapps may fix it as well.
Sent from my SCH-I905 using xda premium
Related
i haven't had a chance to try it on my NC yet, but i think we might now be official.
http://stage3-beta.swype.com/android/supported/
I'm installing the update now i will tell you if it works.
ngrenn35 said:
I'm installing the update now i will tell you if it works.
Click to expand...
Click to collapse
Thanks! Don't forget to include what ROM you're running.
Honeycomb build 4 not working w swype
I installed todays swype and i can tap out words but not swype. I know i am using the right keyboard because it does trace but the words wont display.... Honeycomb build 4.
Works great for me on CM7 v14
It looks great but I can't actually use the swype function, like the poster before said.
Running CM7 and when I swype the border flashes blue but no word appears. Otherwise, it's nice to see some large screen support from Swype. I love it on my Vibrant
Doesn't work for me (NF 0.6.8.3). I can type but can't Swype.
It worked for a second then quit, cm7 v14 Keyboard is nice for fat fingers. Soo close.
I have phiremod v4.1 and the swype does as the others said; I can see the keyboard and the swpe gestures, but no words appear, I can tap them out as with the regular android keyboard, but swyping does nothing. It does make a noise after a swype gesture though.
Also when I put the NC in landscape view, the skype app takes up the entire screen.
still not able to try on my NC, but when swype does that behavior on my nexus one, if i switch to the android keyboard then back to swype through the input method selector, everything works great.
fzr-r4 said:
still not able to try on my NC, but when swype does that behavior on my nexus one, if i switch to the android keyboard then back to swype through the input method selector, everything works great.
Click to expand...
Click to collapse
You may well be my hero. I can't confirm that it worked for sure, as it threw a licensing fit since I used it on HC instead of CM7, so I'll revert back to HC and try this again. The licensing fit never occurred until I tried what you suggested.
Tried that method of switching to Android KB and back, still didnt work for me, same as everyone else.
I'm getting the same results on CM7 v17. I'm also getting a message that says swype is configured for another device and may not work correctly when I first switch over to it.
g
Boinky said:
I'm getting the same results on CM7 v17. I'm also getting a message that says swype is configured for another device and may not work correctly when I first switch over to it.
Click to expand...
Click to collapse
yeah, shoot, me, too. eMMC Honeycomb 2nd edition.
Sent from my Nexus One using XDA App
I have read in another thread that Nookie Froyo tends to spout random IMEI numbers when an app asks about the device it is installed again. Swype authenticates the beta by IMEI and you are limited as to how many IMEIs you can install it on. Thus the licensing problem - install Swype and it locks itself to the reported IMEI. Then run it again, and it thinks it's installed on another device.
Licensing errors
I'm also getting licensing errors but the keyboard does appear to load correctly on, CM7 #17,
damn. Was so excited too. Wont swype. Have been dying to put it on my NC, typing on this thing sucks.
Sometimes the betas get hacked (but no posting warez here!) so they are not IMEI locked anymore. Unless we can figure out a way to report a stable IMEI on the NC across all firmwares per device, that may be our best bet .
Will try when the WSVGA will be supported in french..
Yes I can confirm what is being said here about the IMEI... Definitely the root cause here as reported on the swype official forums.
The way I see it, this can be worked around without the need to hack the Swype package. My understanding is all we need to do is spoof the telephony stack a little better, so that the IMEI is consistent. I am at work so I cannot do too much to find out how hard that would be.
android API call for getting IMEI is
android.telephony.TelephonyManager.getDeviceId()
First step would probably be to override this function and just report to logcat to confirm the Swype Licensing process (Would have to check both "Swype installer" and "Swype" applications this way, full end to end install process) calls that function to retrieve the IMEI instead of using another method.
Then if that works, override the function to return a static number. Does anyone know if the IMEI can be used to reverse lookup manufacturers and devices models the same way MAC addresses can? If so, we may need to carefully pick the number returned so that if Swype does a reverse lookup it thinks we are using a valid device - Such as Galaxy tab, which I believe is functioning under the latest beta.
I am definitely not an expert android dev, I barely understand this stuff so far. Just hoping to get the conversation started because I'd really like to swype.
Might just be operator error here, but I installed Swype yesterday and it worked just fine. Didn't alter build.prop or anything. I get the pop up keyboard, but when I try to actually type by swiping nothing comes up. the line appears like it's trying to trace out the word but no letters ever show up on my screen. Am I doing something wrong?
PS-The keyboard works fine if I tap the keys, so it installed successfully, it just won't let me trace out the words(which rather defeats the purpose of having it installed)
That is because while swype works on our nook colors, our nook colors do not have an androidID or IMEI, which is a unique number given to any device with a cell radio. That number is required to give swype its "swype" functionality.
well that's depressing. Is there no workaround as of yet?
Swype works just fine, no build.prop edits needed. Refer to this thread
http://forum.xda-developers.com/showthread.php?t=973010&highlight=swype
You do have to be rooted, follow the instructions in post 29 (step 1 not needed if already rooted). I was rooted with AutoNooter, and used Root Explorer to put the apk in the posted location.
As my original post said, I am rooted(using CM7) and did get it installed fine. It's the swyping function that isn't working. Is that working for you?
has anyone got it working on honeycomb?
nicbennett said:
As my original post said, I am rooted(using CM7) and did get it installed fine. It's the swyping function that isn't working. Is that working for you?
Click to expand...
Click to collapse
Yes, the swyping function works fine for me. Sorry, though, can't help you as far as CM7, I am stock autonootered.
fwiw, I just downloaded the SlideIT trial and it is B-E-A-Utiful. swype is way too much hassle when you can pay $6.50 and have the same features for no work.
I have a problem with several keyboards on Android. After I install a new keyboard everything works OK. After a few days however the keyboard won't pop up when i select a textbox (for example in Messages). I can still switch keyboards and all other keyboards will still work (If they worked before). The only thing that helps is re-installing the keyboard.
This has happened with SwiftKey, Swype, and SlideIT.
Phone: HTC Desire
ROM: Android 2.3.5 Oxygen 2.2.2 (but has happened with every Oxygen I've had and with CM7)
Soo How do I stop the keyboards from not working?
Nobody has any idea to fix this problem?
Is original android keyboard working?
Accidentally sent from my Google Nexus S using XDA Premium
You could try a few other keyboards and see if you get better luck. I've not experienced the same thing as you on my Desire HD.
I currently use the MIUI Android rom.
Standard keyboard and Thumb Keyboard seem to be the only keyboards that consistently keeps working, everything else just stops after some time.
I looked around on Google but I could not find anything. I think this is a bug in Android, I'm going to try a different ROM and see if that helps.
i have tried most keyboards, I really have as its so important. I settled on SlideIT as this has swipe and a quick toggle between swype on and off, and all the right characters are where you need them. My keyboard had never failed me, so I wonder if you need to clear the data and/ or do a hard reset.
Sent using TCP/IP
I tried everything, I tried clearing data, clearing cache, re-installing ROM, and 3 different ROMs, but nothing works!!! My only hope is that Android 4.0 fixes this, but as you know the HTC Desire Custom ROM is still in early beta.
Hello,
This is mainly a question I would want to post in Android 4.1.1 - CyanogenMod 10 Preview thread, due to the fact that I’m a newbie on this forum, i can't.
I really hope that someone can help with my problems.
So, general description:
Galaxy tab 10.1 (p4wifi)
ROM - cm-10-20121109-EXPERIMENTAL-p4wifi.zip
ROM runs very smoothly, big thanks to all the developers and especially pershoot who is working hard to make this ROM tick.
So, I have a Bluetooth external keyboard and it works very well. But after installing it the native keyboard stopped working properly. Every time I wanted to use it: it would appear, I would type some characters and after 1 sec or so (very random) it would disappear, the keyboard selector in the bottom right corner would disappear with it. Then the keyboard/keyboard selector reappear after some time, without me doing anything (4-5 sec, also random), and when I would try to type more it would disappear again after a few characters.
In the beginning I though it's the external keyboard that's causing it. So I factory reset/ dalvik cache removed, but the problems remains even if the BT keyboard it’s not yet even connected with the tablet, on a clean install of the ROM.
Also it appears that the spell checker (red lines on the bottom of the words, PC style) doesn't work neither.
Tried Thumb keyboard and it works very well. But I would really want to know what happened, did I mess smth up.... Plus I’m writing a lot in French so the spell checker helped me a lot.
Thx for your help !!!
thx
Hello Arthur,
I am facing exactly the same issue as described by you. And I did not install any bluetooth keyboard.
Running CM10 nightly 20121117 on GT-P7510
hope someone knows how to fix this.
Thanks in advance
I think it was a known issue that the keyboard dock will no work properly with this ROM
Install hackers keyboard. Stable than the default keyboard.
Sent from my GT-P7500 using xda app-developers app
Ok so I'm having this problem no matter what keyboard I use that whenever I edit a word in a message or note, etc, Android duplicate the word every time I hit the spacebar and it's driving me insane because it ruins my message and I can't stop it. Does anyone know how to fix this? I'm using google keyboard at the moment but have the same issues on the stock keyboard, as well as swiftkey, which means its the OS. I'm rooted on Venom ROM, but had the same issues before I rooted. Any help would be appreciated. Thanks
Anyone?
Bump
Sent from my HTC One using xda app-developers app
I had the same issue using Perfect Keyboard from the Play Store, both on Stock Rom and on Viper Rom. Uninstalling and reinstalling didn't work, wipe data didn't work, even showed the issue right after a clean install (full wipe). Don't know the cause but I begrudgingly switched back to using HTC stock keyboard and no problems for over a month. I miss using the volume keys for moving the cursor, but I hated this issue even more...
Perhaps let the dev know and see if they can isolate the issue, otherwise use a different keyboard? Sorry can't help, but you're not the only one that's see the issue!
Good luck!
Sent from my Viper 2.0 HTC One
I had the issue even on the stock rom before root IIRC. I use google keyboard, but believe the issue was the same even using swiftkey. There has to be some bug in the OS that is causing this, but I've literally tried everything to no avail.