Handsome Devil
New Member
Worked Great for me thanks... ive been without swype for bout a week now and it sucked, i got slide it for the meanwhile but its defenatly going to the trash once i got swype back
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!
Time to pay for Swype!
- Thread starter greyghost04
- Start date
This has been posted in several threads but it's easier to repeat it here than to find all the references that some people will ignore anyway.
If your beta version of Swype stops working after you turn your phone off and back on with a message about the software expiring or being the wrong version for your phone, don't uninstall and try to reinstall. Instead do the following.
() Open an app that requires keyboard input.
() Long press on the text field.
() From the picklist choose "Input Method."
() Select the standard Android Keyboard.
() When you get back to the text field, long press again and choose input method.
() Choose Swype.
Everything will be fine.
Note: The problem exists only in the approved beta version of the software and only happens when the power is cycled in your phone. If you are using an older version of the beta (5612) rather than the final version (5652), the bug does not occur.
If your beta version of Swype stops working after you turn your phone off and back on with a message about the software expiring or being the wrong version for your phone, don't uninstall and try to reinstall. Instead do the following.
() Open an app that requires keyboard input.
() Long press on the text field.
() From the picklist choose "Input Method."
() Select the standard Android Keyboard.
() When you get back to the text field, long press again and choose input method.
() Choose Swype.
Everything will be fine.
Note: The problem exists only in the approved beta version of the software and only happens when the power is cycled in your phone. If you are using an older version of the beta (5612) rather than the final version (5652), the bug does not occur.
I'm using the final version as the first one gave me problems too. Everytime my phone reboots I still have to go to settings/apps/manage apps/find swype and stop process....even though it isn't running. Then swiped words work again as opposed to only single keystrokes showing up in text boxes.
I'd pay for this app but they need to fix it so I don't have to tweak it every now and then. When I want to type I'm ready to type not ready to go jump through hoops. For me the leaked version worked way better only because I didn't have to revisit my settings every now and then.
I am running chevy's simply stunning and can't get swype to work either. I searched for "cornicakes" and found no user so i can try his instructions.
The instructions basically have you search your card and /system folders for "swype" and then delete those files. Some are in /system/apps and in /system/lib . You need to make those files read writable so you can delete them. Root Explorer does that or you can use Terminal Emulator commands. Get rid of the ones on your card too. I renamed mine to *.bak . At that point you will be able to install the new version. If it doesn't work right stop the process within app manager in the system area and/or do a long press on the text field and choose swype as the default keyboard input.
I'm naming my next kid after you.....I had Swype since early December. Today when I updated my ROM to BD 7.5 I got the same message about expiring and limited usage. I searched and found this thread, and all seems well again after your instructions. I just hope I don't have to do this every time I power cycle my Droid. Thanks for the help!
I think you might be looking for "Corinacakes." Not sure what role she has in all this but you might try looking again.
In one of the many Swype beta threads she typed up some directions to get folks going if they had install problems with the beta. It is interesting to see some STILL have not had expiration issues until they changed something. For me it was when I installed the beta version and my leaked version suddenly expired when I tried to go back to it when the beta didn't work at first.
Not sure what sort of data collection they are using for this beta. (time to see if there is feedback on their site
)edit: hmmph. no place for feedback, just a troubleshooting install guide. Funny beta where you can't give feedback.
Last edited:
I hope you don't really name your next kid "Jayessaichoneonetwozero." He'll have a rough time in school.
And I have some more bad news for you. You will have to do this each time you power cycle your droid until Swype has a fix for the problem.
The problem is fairly easy to understand though it's apparently a PITA to fix. It stems from the fact that Swype tries to initialize itself on boot up before the Android O/S has finished doing its housekeeping. This trips a setting that turns off Swype's functionality. By turning Swype off and back on it initializes correctly.
I suspect that the reason it's difficult to fix is because it's hard for Swype to determine if its services from the Android O/S are "ready" for it to initialize. If you have a bunch of apps on your phone ( like more than 100), you may notice that some apps don't start for awhile when you power cycle your phone.
Swype may have to put some sort of delay into the initialization routine to deal with the problem. Why they haven't done so already, I'm suspecting, is due to their architecture that ties Swype more closely to a phone's O/S than most other applications. This enables them to catch application incompatibility issues in most O/S environments but in the Android environment it seems to be a problem. (That's also the reason that Swype prefers to sell their app to phone manufacturers where their app is more tightly integrated with the device's O/S.)
Don't feel too bad. I've gotten pretty adept at the routine and no longer curse loudly enough to wake the family when it happens.
In one of the many Swype beta threads she typed up some directions to get folks going if they had install problems with the beta. It is interesting to see some STILL have not had expiration issues until they changed something. For me it was when I installed the beta version and my leaked version suddenly expired when I tried to go back to it when the beta didn't work at first.
Not sure what sort of data collection they are using for this beta. (time to see if there is feedback on their site
edit: hmmph. no place for feedback, just a troubleshooting install guide. Funny beta where you can't give feedback.
I think the instructions you're looking for are the same as I posted above.
Those who haven't encountered the problem are likely running version 5612 of the beta that they either received early in the beta program (and have not updated) or downloaded independently from several sources cited on other threads. I don't think anyone running the original leaked version has managed to avoid its "timing out." Anyone running version 5652 (which you can check on the Swype "options" page) will have the power recycle problem.
As for providing feedback on the Swype forum, all you have to do is search for a topic at the top of the page. If you don't find one that suits what you want to say, you can then enter a new thread rather than comment on an existing one.
This approach tends to reduce redundancy. Not a bad idea considering what often goes on here.
I'd think it would be easier to call swype the first time the keyboard was called up when pressing a text box. No reason to spin it up before then, no? But thanks for the background, Jayessaichoneonetwozero. I wasn't aware why it was breaking, only that it was
I'd think it would be easier to call swype the first time the keyboard was called up when pressing a text box. No reason to spin it up before then, no? But thanks for the background, Jayessaichoneonetwozero. I wasn't aware why it was breaking, only that it was
Well, keep in mind that is my speculation. I'm just guessing based on some general familiarity with software operations in a linux environment. And of course you're correct that Swype's own architecture is the source of the problem. SlideIt, Shapewriter, and other keyboard apps don't have the problem because (I'm guessing) they are not designed to act like a "native" O/S service like the Android keyboard (and like Swype).
So why does Swype do it that way? Well, "native" apps have a number of performance and functionality advantages in most O/S environments. And keep in mind that the Android market is not Swype's only target. Their first big sale, in fact, was for the Omnia II, a Windows phone.
In the Android environment Swype has to act like any other "non-native" application and it gets treated with no more respect by the O/S than other apps. If it's hogging memory the O/S can shut it down. The Swype process can "protest" before it's swapped out but ultimately the Android O/S decides what has to be available in memory and what can be shut down. If Swype were part of the O/S, that wouldn't be the case.
And finally, keep in mind that as a "non-native" app, Swype is not in a position to control other apps. It must just coexist with them. Since there's no telling what other apps are running on any particular device this means that Swype may be incompatible with another app and fail to work correctly for that particular application. That's the sort of problem the folks at Swype would like to avoid. Understandably.
So for those who don't understand why Swype doesn't simply toss their application into the Market and sell it like other apps, this explanation may help. It's not like other apps. It wants to have the same "status" as the standard Android Keyboard. And at the moment that's not possible.
Got it, I guess with the custom rom I had to select, menu, settings, language keyboard, and select swype that way. Long press wasn't working.
For the first time I didn't have to go to settings/apps/app manager, find swype, stop the process. The above instructions worked and it was much faster that way, thanks! Once again...I've learned something new