Several days ago, I noticed that SWYPE was not working correctly.
When I try to "swype" a word, I gent a "dink" noise and no word appears in the input field. I do see the Path trace on the keyboard as I try to swype the word.
If I pick out each letter one at a time, it works just fine.
I am running comm rom 2.0. I did a wipe and a re-load of comm rom (PB & J Kernal), but I still have the problem.
Any suggestions?
I believe you have to update it because I believe the trial period expired for the version that is in the comm rom....
http://forum.xda-developers.com/showthread.php?t=1128986
Thanks durakbane!
Worked like a charm.
Related
I have a Sprint Touch Pro 2 with stock WM6.5 ROM.
When I type in Opera Mini (say posting a forum message), after a while pressing a space bar (or a comma / period sign) starts erasing the previous word. This is very repeatable. Also once it starts happening, it affects any other keyboard, including the hardware one.
At first I thought it was related to FingerKeybd, so I yesterday uninstalled it and jumped through some hoops to get my English ROM device to type in two languages using HTC native keyboard. However, it appears the bug is still there, although in a modified version - now pressing space erases letter "I" only.
The problem is only with Opera Mini - I can type anywhere else with no issues. I also have a strong suspicion that it's somehow related to suggested words option being turned on, however I use this feature and don't want to give it up.
I did submit a bug to Opera team but it was immediately dismissed as something specific to my particular unit.
I am curious if anyone else had this problem... surely I can't be the only one !
I have the same problem. Thats horrible.
Same problem here. I have autocomplete turned off but it's still happening. It will also erase "ierd" if you type wierd but won't erase it if you type starting with another letter. The crazy thing is it cleared up for a while until I did a hard reset and erased the "fix".
I don't have this bug anymore. I think it may be related to TF3D (Sense). I stopped using Sense several months ago - got tired of lags and memory issues, tried Titanium and never looked back. This seems to have also fixed my Opera keyboard issue, somehow. I've been through many hard resets (trying different things, screwing up, hr to get back to basics) and so far no issues with keyboard. It may be not related as much to Sense as to CHT running on top of it; don't know - try switching to Titanium and see if that helps.
I used to use mini 4.2 and really liked it, but couldn't use the newer versions because the keyboard is just too buggy. I don't really remember what the keyboard did, I just remember that typing was nearly impossible. I use Resco for my sip.
I had the same thing, search Opera mini forum for "kuifje_opera". It turned out to be the autocorrect feature.
i dont face this problem.. perhaps try reinstalling it, + delete cache files? works fine for me! what about in you HW Keyboard, any problems there?
same
Same problem on rx3115 ROM 1.01.11a.
wm2003SE
any fix?
Try to use Opera mini 5 beta. From my experience with opera mini for about year I can say that the previous beta version i more stable and there are few problems on the rendering of sites and keyboard input in text fields compare to latest 5.1 version. The only thing I do not like in beta version is no so smoothly scrolling vs 5.1.
It is not a Opera problem. Here is what I did and get rid off it:
- Open Start Menu
- Go to: Settings>Personal>Input
- Now you are in Input Method, from the tabs above click Word Completition and uncheck everything there. Now go on the tab Options (on the right) and uncheck Capitalize first letter of the sentence and Scroll upon reaching the last line.
- Click OK (bottom right) and exit the Start Menu.
- Thats it!
This is what I did and solve the same problem, now everything is great when typing texts.
I am using Windows Mobile Pro 6.5.3, so I don't know if it's gonna work on 6.0, 6.1 or 6.5, but considering that this is an all WinMo option, I think it would work on any WinMo OS. Try it, you ain't gonna screw anything
Cheers.
So I think this is a problem. Sometime when I swype certain word, I don't get the word I want. It's almost like the swype program had its own idea of which word I was trying to spell. For example, it doesn't know the word funny. I had to add to the dictionary. It also keep giving me "knorr" when ever I tried to write know.
I can only think of a few possibilities. (1) the original swype dictionary database isn't an american version (maybe uk english). (2) my touch screen calibration is off.
I'm am using axura's build, version 2271. I wonder if anyone is experiencing similar problem. I have tried adjusting the accuracy/spewed meter to no avail. I have used swype before on my hd2 (wm6 + android version) and never had this problem even though the screen calibration on my hd2 android was off.
Any advice, guys? Much thx.
I think couple of older versions of swype had that problem. Upgrade to newest one and it is much better. Just sign up for beta at their website and install the new one.
azzzz said:
So I think this is a problem. Sometime when I swype certain word, I don't get the word I want. It's almost like the swype program had its own idea of which word I was trying to spell. For example, it doesn't know the word funny. I had to add to the dictionary. It also keep giving me "knorr" when ever I tried to write know.
I can only think of a few possibilities. (1) the original swype dictionary database isn't an american version (maybe uk english). (2) my touch screen calibration is off.
I'm am using axura's build, version 2271. I wonder if anyone is experiencing similar problem. I have tried adjusting the accuracy/spewed meter to no avail. I have used swype before on my hd2 (wm6 + android version) and never had this problem even though the screen calibration on my hd2 android was off.
Any advice, guys? Much thx.
Click to expand...
Click to collapse
I had the same problem with a couple of different roms. I just retrained it. It does make you wonder tho
Like the 2nd poster said, some versions of swype are missing words. If you go to the Bionix V discussion thread, there is a new version of Swype. Correct me if I'm wrong, but I'm pretty sure that would work fine with Axura. I would flash that if I were you. I had that problem and it pissed me off until I found out about it (in the SBG thread somewhere, I think).
download latest swype.apk
go into your files on phone, with w/e u use.
system/lib/
delete swypecore.so
go to system/app/
delete swypetips.apk and swype.apk
go back to system/lib/ make sure the swypecore.so is not there, if it is delete it.
reboot, you must reboot.
now put the new swype.apk in system/app/
now use swype installer from www.beta.swype.com
to update your language files, and BAM you got you a new language pack and new swype.
Much thanks for all the help, guys. One more question, do these beta expires? The last couple of them I have (on my HD2) kept on expiring which was really annoying (but not as annoying as dealing with the bad words my swype is outputting).
Thanks again.
Update: Alright. Got it all sorted out. Much thanks, guys. This was driving me nuts. The newest swype also look pretty nice too.
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.
Hi there!
I have just installed Team-B's CM7. First thing I do, install the market, and then install the Swiftkey tablet X Trial from the market.
The keyboard pops up as normal, but it doesn't make the predictions. I changed the input method to the one that comes with CM7 and it works with predictions just fine. When I select back the swift key to be my input method, the predictions are there and work fine.
This doesn't persist, i.e., when I go to another textbox I have to do this procedure again.
And it doesn't predict at all. I mean, when I write some rubbish and it won't correct me, so it's not that it's simply not showing the predictions bar.
(btw, didn't find anything on the wiftkey documentation or FAQ)
My question is why doesn't it predict at the first time I hit the text box? What do I have to do to solve this?
Any ideas?
Cheers
I've been running the beta version of Swiftkey 3 for a couple months which I loaded from the Swiftkey site. It has run OK, and yesterday Swiftkey released it on the market. Paid version is on sale for one week. I ran paid version all day yesterday and that runs ok also. Only problem I see with this version is predictions with apostrophes ('). It doesn't seem to learn them. It has same problem on my GNex too. I'd recommend a different apk.