If Swype beta stopped working...

[Peter123]

Some of you might have experienced this message:
"The Swype package you installed is configured for another device..."
and it does not work.

The way I could make it work again was:
(1) I deselected swype as the input method (went back to normal typing)
(2) Close the input selection window, then reopen it and select swype as the input method. Works for me.
Peter

PS. you may need to do this again if you reboot the phone.

 

[alprazolam]

Did you get a replacement device and now it says the ID doesn't match? That's my deal. I saw your method mentioned on the Swype website. Looks like you have to do what you did every time that you reboot your phone. I want my swipe back!

 

[Peter123]

Did you get a replacement device and now it says the ID doesn't match? That's my deal. I saw your method mentioned on the Swype website. Looks like you have to do what you did every time that you reboot your phone. I want my swipe back!

I did not get a replacement device, however, I have the OTA 2.1 update.
Peter

 

[scrubs]

Swype is really driving me crazy. I've had the above message of "configured for another device" come up randomly. I've tried all the tips on the swype beta faq, along with the one above, which works only some of the time...I am getting this error every time I turn the phone off/on, as well as at other times after it has been working fine for a few days...completely unacceptable. I fly frequently, meaning I have to turn off the device for takeoff/landing, and reinstalling swype each time is just not going to work for me.

Has anybody found a better solution?

 

[xx_bishop_xx]

Swype is really driving me crazy. I've had the above message of "configured for another device" come up randomly. I've tried all the tips on the swype beta faq, along with the one above, which works only some of the time...I am getting this error every time I turn the phone off/on, as well as at other times after it has been working fine for a few days...completely unacceptable. I fly frequently, meaning I have to turn off the device for takeoff/landing, and reinstalling swype each time is just not going to work for me.

Has anybody found a better solution?

How did you recieve your apk? The official installer?

 

[AdrianC14]

This also happened to me when I rooted my Eris. It kept saying it was not configured for my device and a blue box would show around the swype keyboard. I just got tired selecting it as the input method because the blue box would keep showing, so I uninstalled it. Now I use Swiftkey Beta, I like the look because it matches my notification bar on CELB 2.8 and it has really good word prediction.

 

[meatwad]

This also happened to me when I rooted my Eris. It kept saying it was not configured for my device and a blue box would show around the swype keyboard. I just got tired selecting it as the input method because the blue box would keep showing, so I uninstalled it. Now I use Swiftkey Beta, I like the look because it matches my notification bar on CELB 2.8 and it has really good word prediction.

Same thing happened to me when I rooted. I just downloaded the Swype Installer. Re-entered my password and downloaded from there. Haven't had any problems.

 

[AdrianC14]

Same thing happened to me when I rooted. I just downloaded the Swype Installer. Re-entered my password and downloaded from there. Haven't had any problems.

I did that 2 times, but the blue box still kept showing when I try to Swype, so I just gave up lol.

 

[Rossco_Pee]

There is an apk that will never expire located on the XDA forums. That is all I will say.

 

[scrubs]

How did you recieve your apk? The official installer?

Yes, it's the official installer I was e-mailed as a registered beta user.