Last Updated: Jun 11,2010
Just got an email from Swype with a download link. Just installed, report to follow.
I made the switch back to a regular keyboard already so I guess I'll wait and see if there are big improvements.
Just installed and tried using it ... and so far it's a fail. I might need to reboot.
I have no issues with the last version though.
Update: It's working flawlessly after the third install.
Yea I didn't have problems with the first one either, just kind of got tired of it.
Mine didn't work either, says it's not for my device.
Curious as to the issues you're seeing - so far here (stock 2.1) it's fine. Any chance it's a Froyo issue?
Just installed mine on stock 2.1 too and it works fine, don't have to change between the stock keyboard and swype upon unlock anymore
It must be because of froyo then. Well I guess I'll go back to the one I was using before.
Nope, it's not a Froyo issue. I'm still on rooted 2.1 (Bugless Beast V1.1) and the message said that's it's not compatible with my phone -- was completely unusable, even switching input methods didn't work. I've reverted back to the trusty version .5612, which hasn't ever given me a single problem.
Swype was great - until I finally figured out that WAS the culprit for seriously slowing the Droid down. I uninstalled it, and there was a noticeable immediate speed improvement. I did miss having voice input though when using Swype.
Another user somewhere reported that the input method broke, but uninstalling and reinstalling worked.
I emailed the good folks at Swype. It's almost like they sent us the wrong d/l link or something.
They sent me the wrong link when I first got the beta so I wouldn't doubt it happening.
I found the biggest annoyance with swype was writing words with apostrophes and any mix of letters/numbers/symbols (such as dates/times/passwords)
Plus no voice-to-text button.
When they fix all that I'll give em another shot.
I missed the .6969 notification, never got it actually. I have to find out why I did not get the notification, but it might be because I reverted to the 5612 build b/c of all the issues with 5652 (and then, a black-themed 5612 build at that).
Of course, I don't have that account back on the phone since I have been playing with FroYo - so that may, in effect, also be a reason - but I check that account nightly at home and have not seen a Swype notification.
If they jerked me from the beta test b.c I had to keep reinstalling 5652 b/c I was changing OSs, and they upped my limit for installs (which I never used again) I am gonna be pissed....)
I was able to do apostrophed / contracted words without an issue.
My biggest issue was that when I tried to do a Capital I I invariably get jimi instead....
I'm still running bone stock, I followed the instructions in the email, removed current version, and the loader, dl'd the apk, installed, and it's working perfect.
Do u have a link to that? I have been using the HTC themed swype which I really like, but it is a .thm file so I am using the older MetaMorph cause I have yet to see .xml version. But now on froyo my MetaMorph doesn't work says I don't have root, yet all my other apps that require root work.
I probably shouldn't do this....but I already have it in my Media Fire account....
Well, I think I have it but I cannot be sure - will have to go home to verify it is the right file - I have 2 of them in my account but neither looks like the right one.
New version runs fine on my unrooted, stock 2.1 Droid, too.
any chance of uploading it to a link?
EDIT: whoops sorry, guess you're not allowed to.
Swype has a voice-to-text button. Although you have to press the menu button to get to it.
If only they'd open the beta back up again.
In the words of good ole Maxwell Smart...
Missed it by -----> <------ that much
Stock 2.1 Moto Droid here and installed Swype beta, reboot... not working.
Uninstalled the original Beta a long time ago and was using the version from this link http://androidforums.com/motorola-droid/87037-no-swype-moto-droid.html#post824733
Too bad this "new" beta doesn't work at all, at least the last one worked even if it was annoying to have to switch the keyboard after a power cycle.
I was too fast.
After the install you have to let it go back to the "downloading/installing" screen and let it crank somemore, then you get the "ENABLE" prompt.
After that, all is working.
Too much, too soon. (name that movie?)
EDIT: and it only took me 3 tries to figure this out... doh!
Separate names with a comma.