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

Help Swype & Thunderbolt - a bug?

Left Coast DJ

Left Coast DJ

Android Enthusiast
Does Swype tracing stop working after you reboot your Thunderbolt? The key presses still work. But tracing gets locked.

Swype can be re-enabled if you select another keyboard and then Swype again.
 
Autospacing issue lies with the way I think the HTC SMS app is set-up, and not Swype (according to the Swype forum). It works fine with Handcent.

Garnto, does your Swype lock-up after a reboot? You then have to manually re-enable it?
 
Left Coast DJ said:
Autospacing issue lies with the way I think the HTC SMS app is set-up, and not Swype (according to the Swype forum). It works fine with Handcent.

Garnto, does your Swype lock-up after a reboot? You then have to manually re-enable it?
Click to expand...
I am using hand centand yes it does lock up after r boot. Jut put on regular input them back on swype and it's good to go
 
I'm having a separate issue with Swype. I've been signed up for the beta for a while and used it with no issues on my eris for months. I downloaded the installer and when I try to open it I get the message: "There is a problem parsing the package." Has anyone seen this error and know how to fix it? Thanks in advance.
 
Left Coast DJ said:
Does Swype tracing stop working after you reboot your Thunderbolt? The key presses still work. But tracing gets locked.

Swype can be re-enabled if you select another keyboard and then Swype again.
Click to expand...

No, this is an outstanding bug that swype has across multiple devices. I had this with my Incredible and still have it with the Thunderbolt. Actually, with the TB, it happens less often. sometimes it actually activate swype correctly after a reboot. with the inc, it happened maybe a couple times over the course of a year.
 
The problem I'm having with Swype is that when you double tap a word to correct it, the Sense copy/paste/ text selector will cover up a lot of the Swype word selector. Any workarounds?
 
Sigh... I've been having the same problem.

It also makes adding words to the swype dictionary impossible.
 
I only saw this problem on my D1 when the Swype beta periods expired and we had to go get new licenses. On my TB, the lock ups got to the point that I had to drop Swype. Swype wants to sell their keyboard directly to device OEMs and limit the devices they formally support. They seem to have no interest in ever open marketing the product. So every few months, they time bomb and we have to interrupt what we're doing to re-license. We also get this unsupported device reboot square dance. For me, Swype has lost its value and I'm not going to choose a device over another because it has licensed Swype support.

I'm on trials of SlideIT and Swiftkey. No conclusions yet.
 
I love Swype, but it is getting a bit annoying to use on the T-bolt. I'd pay 3-4 bucks for a version that worked well. Why don't they do that? I guess the money is better when you sell directly to the OEM?

Blah, may have to try swiftkey.
 
Swype is acting funny for me too on the tbolt. I will swype a word out, and it will beep an not put the word into my message. Is there some setting that is messed up? Im not too familier with swype, so i have no idea what this error means.
 
You must log in or register to reply here.
Back
Top Bottom