• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

swype beta

Echh! I play a few games or visit far away lands & monuments using Google Earth every night before I fall asleep in bed. I got that sinking feeling that my Droid was gonna suck up some of my Suday morning when I saw Swype's "Piss-up-a-rope, loser!" expiration message.
Thanks to you folks on this forum, I'm back up & running with Swype before my first cup of coffee! (Cheers!)

I also have the issue with Swype not immediately recognizing my custom (Sholes 2.0.1) ROM.
Is this something that can be fixed by editing a stsyem file? (Please don't just tell me to install a different ROM.)
 
I am still standard, yet I can't get swype to work. I have changed the input type back and forth a couple times and have rebooted the phone a couple times, but it still wont recognize my swypes. Does not pick up the words at all.
 
gotwillk said:
yea also getting that error her too. not registered to this device yadda yadda. uninstalled swype, redownloaded the installer because a dev on their forums said to do so due to a bug in the previous installer, reinstalled, and still get that error after a reboot of the phone. no one else has this problem?
Click to expand...

I was also (stock Moto Droid/no root). I had to uninstall everything, the program and the installer, then delete everything.
After the re-install and reboot it still didn't work. then I did the following and it works:
Code: 
Currently working  from my droid, here's how.

[LIST]
[*]Settings, language and keyboard settings.
[*]Uncheck swype
[*] Check android keyboard
[*] Go to any text field and let the keyboard open.(If you don't do this  it won't work)
[*] Go back to language and keyboard settings
[*] Uncheck android keyboard
[*] Check swype
[*] Click ok
[*] Go to any text field and swype should work.
[/LIST]
   Again this will have to be done after every reboot  till they fix this major glitch. 
Which they will, because the product is too awesome and valuable for  them to let it slip. 
Plus older non released versions didn't have this problem.
This is from the Swype Forums
-J
 
followed exactly, it still did not work, unless I am a ****** as well as a noob


johnnybirdman said:
I was also (stock Moto Droid/no root). I had to uninstall everything, the program and the installer, then delete everything.
After the re-install and reboot it still didn't work. then I did the following and it works:
Code: 
Currently working  from my droid, here's how.

[LIST]
[*]Settings, language and keyboard settings.
[*]Uncheck swype
[*]Check android keyboard
[*]Go to any text field and let the keyboard open.(If you don't do this  it won't work)
[*]Go back to language and keyboard settings
[*]Uncheck android keyboard
[*]Check swype
[*]Click ok
[*]Go to any text field and swype should work.
[/LIST]  Again this will have to be done after every reboot  till they fix this major glitch. 
Which they will, because the product is too awesome and valuable for  them to let it slip. 
Plus older non released versions didn't have this problem.
This is from the Swype Forums
-J
Click to expand...
 
I just had the same issue. Fortunately, I have the old Swype beta (the one that I first received from Swype when I signed up for the Beta) backed up on my HD, so I am simply gonna push it back to the phone and not have to worry about these "The Swype package you installed is configured for another device and will operate with limited functionality..." issues.

I'll report back on how it goes.
 
Oops - I thought I did - apparently I just made a new backup and pulled the new one I just installed lol....
 
brio said:
FYI On the Swype Beta forum Michael helpfully posted this:

"I was having the same error saying it was "The Swype package you installed is configured for another device and will operate with limited functionality...". I am running a custom 2.1 ROM on a rooted Moto Droid. When you try and type, Swype will let you "hunt and peck" what you trying to type but not "swype". To fix this press and hold in an "Input" area and select the Android Keyboard, then press and hold in an "Input" area again and choose Swype, it will then start working as normal again until the next reboot."
Click to expand...

Not working for me - every time I do this as soon as I try swyping it gives me the same erorr message.
 
just found this instead:
Beta Users,

Thanks very much for installing (or trying to install....) our beta software. We've had a solid success rate but a few too many hiccups. As such we have REPOSTED a new installer.

If you've had ANY of the following problems please UN-INSTALL Swype and re-download the Installer.

Q: I get a bad link from the email you sent me....
A: Some phones are not processing the link correctly, we are adding code to catch those. Please try it again!

Q: I registered and downloaded a beta-version Swype but I get one of the following messages:
-----"The Swype package you installed is configured for another device"
-----"Your Swype version has expired."
-----"Download of the Package Failed"
A: On your phone, open the "Welcome to the Swype Beta" email and download the SwypeInstaller again. Let it replace the existing installer and finish doing the installation again. There was an error in our previous installer version.

Q: The download kept timing out and I eventually was told I'd reached my limit of attempts
A: Try again, we've reset the # of attempts we will allow. (The server was busier than expected)

Q: Do I need to keep the Swype Installer after installing Swype?
A: No. In fact, you should delete it because we update the Installer on the server when we find install bugs.

Again, thanks very much for downloading our product and please provide feedback on this forum. What do you like? What don't you like? What is confusing? etc.

Best Regards,

The Swype Team
Click to expand...

Gonna try this out if I can get my KB working again.
 
No go. I suppose that means that I cannot use Swype until they fix this stupid DRM issue....

I positively hate DRM. If they continue to keep it in there, I am boycotting Swype, no matter how nice it is. DRM sucks.
 
Ive had swype for like over a month already, I flipping love it. This beta version is even better, its alot more polished, and updated....cant text without swype now, im spoiled.
 
there's currently no permanent fix for this issue afaik. everytime you reboot the phone, you will get that message saying its configured for another device or whatever. only fix for this right now is to use the workaround and then to not reboot the phone. if you do have to reboot the phone then you'll have to do the workaround again.
 
gotwillk said:
there's currently no permanent fix for this issue afaik. everytime you reboot the phone, you will get that message saying its configured for another device or whatever. only fix for this right now is to use the workaround and then to not reboot the phone. if you do have to reboot the phone then you'll have to do the workaround again.
Click to expand...

It is not working for me even if I don't reboot - I get the error message ever time I try to use Swype, and even after I switch methods and then switch back.
 
messenger13 said:
I was using 0.35.3959 (the leaked version), but yesterday I updated to the new beta release, 1.25.16.5612. Both version have had the voice input option, so I'm a bit confused. When I'm in Handcent and I'm SWYPE'ing, I can press the Menu button and I get a "Speak" option. Maybe it's because I have the 2.1 keyboard installed. Or maybe it's because I have the TalkToMe Keyboard app installed ... I don't know. :confused:
Click to expand...

the speak option is part of handcent, not swype.
 
TBreezy said:
has anyone gotten the message that you are not using an Android phone so i couldnt download. (using a droid)
Click to expand...

I read in another forum that someone who was having that problem was able to get the Swype beta "get" site to recognize his Droid by changing the URL prefix from https to http. Have you tried that?

Also, see here: http://androidforums.com/android-ap...e-android-now-officially-beta.html#post413978

Apparently, when using the stock browser, this person's android phone wasn't recognized, but it was recognized as android when he used Dolphin.
 
You must log in or register to reply here.
Back
Top Bottom