What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

the swype application thats installed was designed for another device?

i get this message or something similar everytime i reboot my phone and swype wont work until i unactivate it then reactivate it when i long press in a type field. any thoughts?
 
I have the same message. I also can not use SWYPE unless I change my input to android, then type something, then change it back to swype. this only happens after a restart. very annoying for a very cool app.
 
OK so I requested the beta from Swype and they sent me the email invitation, but my leaked version didn't time out until this morning, and by the time I went to install the official beta, they had closed it.

For anyone else who wants to use the beta but didn't get it before it was officially closed, please note: The APK linked here will allow you to install and run the app even though the Beta is officially closed. Or at least it worked for me as of a few minutes ago.
 
I am getting this same error.
Question: Is the version of Swype, linked above, the Android Beta version? Or the old Swype w/o auto-caps?
 
It's a known bug in the beta. If your phone reboots then you'll get this error. The only way to fix it is to delete swype from the phone and reinstall it. They're working on a fix.

I'm part of the official beta, so I can see these kinds of things in their support system.
 
Actually you can see the stuff on their web page:


https://beta.swype.com/android/welcome/detailed/


The relevant section is here


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 some functionality..."


A: On your phone, open the "Welcome to the Swype Beta" email and download the Swype-Installer again. Let it replace the existing installer and finish doing the installation again. There was an error in our previous installer version. NOTE!!! On some phones, including the Droid and the Nexus One, this upgrade only partially fixes the issue. You may still see one of the messages above after upgrading to the newest version. The workaround is - Each time you turn on your phone, before entering text, you need to switch between the Swype Keyboard and the Android Keyboard. After switching back to the Swype Keyboard it should work fine until you reboot again. Yes, it's annoying and we're working on it - It's a beta!
 
It's a known bug in the beta. If your phone reboots then you'll get this error. The only way to fix it is to delete swype from the phone and reinstall it. They're working on a fix.

I'm part of the official beta, so I can see these kinds of things in their support system.

NO! NO! NO!

Not only is that NOT the "only way to fix it," Swype specifically recommends that you NOT delete and reinstall. The beta program allows you to download and reinstall only a limited number of times so you're slitting your own throat if you do so.

As detailed in the other thread cited above, do the following after you power cycle your phone and get the "wrong device" message.

() Open an app that allows text entry like a notepad or compose an email.

() Long press on the text entry region.

() Choose "Input Method"

() Select an input method other than Swype such as the standard android keyboard.

() When the standard android keyboard appears, long press again.

() Choose "Input Method" and this time select Swype.

Everything will be OK.

The problem arises because Swype tries to initialize itself when the phone is booting before the Android O/S is through doing its "housekeeping." Once the O/S is up and running you can turn on the Swype keyboard without a problem.

P.S. This is simply the step-by-step version of the procedure in the post above this one.
 
Ok, you are correct, but it does also say on the page that this doesn't always work and a reinstall is sometimes needed, which is what was required in my case.
 
Back
Top