I had the same problem and it was leftover bits and pieces of swype from the leaked version. You can connect your droid to computer and mount the sd card and do a search on the card for swype and delete all of swype files. Then you can install swype again and voila. That's it in a nutshell, but you can go to previous posts that provide more detail.
Ok, I'm going to give this a try and will post my results.
I tried all the steps as outlined by Bastosero to no avail. Still getting the Parse Error. Very frustrating. This was working well with the leaked beta and now I'm stuck without the standard keyboard. I've gotten used to the Swype keyboard and can't see myself without it anymore
Ok, finally got it to install after having my friend email me the .apk file and then i copied it through the USB. However, now I'm getting an error that says "The Swype package you installed is configured for another device". Anyone see that?
Ok, finally got it to install after having my friend email me the .apk file and then i copied it through the USB. However, now I'm getting an error that says "The Swype package you installed is configured for another device". Anyone see that?
Are you getting this message after you restart your device? If so, try changing your touch keyboard input method to Android then switch back to Swype and it should work....it's a bug
Ok, finally got it to install after having my friend email me the .apk file and then i copied it through the USB. However, now I'm getting an error that says "The Swype package you installed is configured for another device". Anyone see that?
Are you getting this message after you restart your device? If so, try changing your touch keyboard input method to Android then switch back to Swype and it should work....it's a bug
Tried that but still getting that error. Any other ideas?
Ok, finally got it to install after having my friend email me the .apk file and then i copied it through the USB. However, now I'm getting an error that says "The Swype package you installed is configured for another device". Anyone see that?
Are you getting this message after you restart your device? If so, try changing your touch keyboard input method to Android then switch back to Swype and it should work....it's a bug
Tried that but still getting that error. Any other ideas?
Are you getting this message after you restart your device? If so, try changing your touch keyboard input method to Android then switch back to Swype and it should work....it's a bug
Tried that but still getting that error. Any other ideas?
You will still get the error after a restart, but switching the input ethod then switching back to swype should still make swype work until your next restart.....
Or is it just flat out not working at all?
Hate to burst the bubble of those who think Swype is about to be available for purchase in the Market after a short "beta" period; that's very unlikely. Swype has not changed their strategy of marketing to OEM manufacturers. They've simply made a version of their keyboard available to a select group of users on the Android platform to test its functionality and performance.
As the folks at Swype have said repeatedly, they are not staffed to provide support to thousands (much less millions) of individual users. Furthermore, they want to be sure their product works identically in every device. With the Android platform proliferating to a wide variety of devices, that is a daunting challenge. Finally, if you were a software firm and had a choice of receiving $2 on every one of 100,000 devices sold or $5 for 20% of 100,000 devices which would you choose?
If you don't know the answer to the last question, you shoulda paid more attention in the fifth grade.
Nobody said that the official price for it when it becomes available in the market would be $5. If they chose to sell it for $10 then that 20% of 100,000 would equal the $2 on every one of that 100,000. Now, what if they chose to sell it for more than $10? Then that would be greater than the example you gave. Besides, I don't see why they won't do both anyways. If they get their app to more people and have it accessible to more people, the greater profit they get.
<sigh> I'm reminded of an old I Love Lucy episode in which Lucy and Ethyl buy a dress shop. And though they lose $10 on every dress they sell, Lucy is convinced they can make it up in volume.
Suffice to say that I doubt you've ever worked in the software industry, at least not on the accounting side. Customer support is a cost of business. If a firm can avoid it, the cost drops to the bottom line (i.e. profit.) Otherwise, it gobbles up profit. And the more you sell the more customer support you have to provide.
Swype may eventually go into the retail software business. But the folks running the company are bright enough to realize that if they can sell their product to manufacturers of the devices that run their software they can be compensated for every unit sold with no cost of advertising, sales, or support.
To get an idea of the level of support they would have to provide to those running android devices, look at the last 28 pages of this thread.
Hate to burst the bubble of those who think Swype is about to be available for purchase in the Market after a short "beta" period; that's very unlikely. Swype has not changed their strategy of marketing to OEM manufacturers. They've simply made a version of their keyboard available to a select group of users on the Android platform to test its functionality and performance.
As the folks at Swype have said repeatedly, they are not staffed to provide support to thousands (much less millions) of individual users. Furthermore, they want to be sure their product works identically in every device. With the Android platform proliferating to a wide variety of devices, that is a daunting challenge. Finally, if you were a software firm and had a choice of receiving $2 on every one of 100,000 devices sold or $5 for 20% of 100,000 devices which would you choose?
If you don't know the answer to the last question, you shoulda paid more attention in the fifth grade.
Nobody said that the official price for it when it becomes available in the market would be $5. If they chose to sell it for $10 then that 20% of 100,000 would equal the $2 on every one of that 100,000. Now, what if they chose to sell it for more than $10? Then that would be greater than the example you gave. Besides, I don't see why they won't do both anyways. If they get their app to more people and have it accessible to more people, the greater profit they get.
<sigh> I'm reminded of an old I Love Lucy episode in which Lucy and Ethyl buy a dress shop. And though they lose $10 on every dress they sell, Lucy is convinced they can make it up in volume.
Suffice to say that I doubt you've ever worked in the software industry, at least not on the accounting side. Customer support is a cost of business. If a firm can avoid it, the cost drops to the bottom line (i.e. profit.) Otherwise, it gobbles up profit. And the more you sell the more customer support you have to provide.
Swype may eventually go into the retail software business. But the folks running the company are bright enough to realize that if they can sell their product to manufacturers of the devices that run their software they can be compensated for every unit sold with no cost of advertising, sales, or support.
To get an idea of the level of support they would have to provide to those running android devices, look at the last 28 pages of this thread.
'is this actually better than the one i installed a few months ago?
I completely disagree.
Just like every app on the marketplace it will get updated as they improve it and get the bugs out.
If they did a deal and had it as OEM they would have exactly the same cost of customer service.
It would be absolutely stupid not to offer it for $5 to Droid and Nexus One users considering there is no way they are going to get money from those devices any other way.
I'm amazed at the lack of business sense here.
'is this actually better than the one i installed a few months ago?
good question mets, is it?