PDA

View Full Version : Backspace does not work in Terminal (and other applications)



anonymous
06-08-2010, 8:32 PM
Installed today's beta release and backspace does not work in the terminal application. Works fine in other apps.

Phone Make/Model: T-Mobile MyTouch3g
Android OS (or ROM) version: Cyanogen 5.0.8-T3
Swype version: 7625
What behavior did you expect to see? Backspace working
What behavior did you actually see? Backspace doesn't do anything
Did you uninstall Swype and the SwypeInstaller first? Yes
Is the device rooted? Yes

Also verified this is not working on a friend's 5.0.8-T2 MT3G. Using action button followed by h (ostensibly CTRL-H) works fine.

xalimar
06-15-2010, 4:34 PM
Does not work for me either. Also does not work in connectbot (ssh client). I am on Nexus one

migr12336925
06-16-2010, 11:07 AM
Backspace (delete) key doesnt work for me in connectbot and I'm on a rooted HTC EVO with OTA update for stock ROM software version .06 and radio .05 with swype version 1.56.7625.t100.

migr12337639
06-16-2010, 11:49 AM
+1
backspace doesn't work in connectbot - rooted samsung moment on 2.1. works fine in other apps (handcent, gmail, etc) in both landscape and portrait.

migr12344289
06-16-2010, 7:46 PM
I have the same issue on a HTC Desire rooted 2.1
Backspace works everywhere else in connectbot just not while in a terminal.

migr12352957
06-17-2010, 12:46 PM
I have a similar problem with the backspace key not working to edit previously saved documents in Documents to Go. It works only with addition of new text and that sucks when I need to edit documents for school. When I switch to the default android keyboard I dont have this problem so I've definitely narrowed it down to Swype as being the culprit.

migr12352957
06-17-2010, 12:47 PM
I'm using a Nexus One and android 2.2 if that helps. Also I didnt have this problem with previous Swype versions.

migr12359597
06-17-2010, 10:22 PM
In the old "thick line" leaked HVGA copy it worked fine, now in the new "thin line" official beta it doesn't. Weird.

migr12352957
06-17-2010, 10:28 PM
I found another app where the Swype backspace key does not work while the android keyboard's does. It's called Arity Calculator in the app market. So this again narrows down that the problem isnt either of the apps themselves.

migr1564903
06-18-2010, 3:23 PM
I am the original poster for this issue (not sure why it shows me as anonymous). I have bugged this with CyanogenMod but the app is part of the AOSP distribution and they're not keen on accepting bugs related to beta products. That being said, the previous Swype beta did not exhibit this behavior.

migr12369343
06-18-2010, 5:19 PM
Nexus one, android 2.1-update 1. Not rooted. Backspace doesn't work in connectbot or the task manager program astrid.

catamountain
06-20-2010, 4:24 PM
When MobisleNotes, http://www.mobisleapps.com/blog/mobislenotes/, is set to checkbox view, I cannot delete a checkbox row with Swype's backspace. The backspace will only delete the text. The checkbox remains. The Android keyboard allows this.

But if I switch the same note to its Plain text layout, then Swype's backspace will delete the line.

catamountain
06-20-2010, 4:50 PM
I have N1, OS 2.1.

migr12400399
06-21-2010, 1:12 PM
I also have this problem. It doesnt happen all the time. Usually related to after having pressed return and manually moving up a line to delete a word or character - nothing happens.

This happens in numerous apps (DocumentsToGo, Handcent, K-9 mail, etc) so not related to the app i am using except Swype!

This is on an HTC Desire.

Shame as this is stopping me use this great app as I need to delete things!!

migr1564903
06-22-2010, 1:03 PM
Issue persists on Cyanogen 5.0.8 final.

migr12574865
07-03-2010, 2:15 PM
I also have this problem in my app under development. I had problems with the EditText's InputConnectionWrapper that it returns for onCreateInputConnection by default so I derived a subclass of BaseInputConnection and had a sublassed EditText return it for onCreateInputConnection. Bam. Swype stops backspacing.

brian.resnik
07-03-2010, 7:55 PM
Dan: I'm forwarding your info to our QA team.

migr12778503
07-09-2010, 3:37 PM
"I have a similar problem with the backspace key not working to edit previously saved documents in Documents to Go. It works only with addition of new text"

I have the exact same issue as well. I am on a N1 with 2.2 OTA update.

sadroid
07-20-2010, 9:05 AM
Any news regarding this one?

migr36166
07-21-2010, 2:06 PM
+1 Backspace not working in Connectbot on my Droid Incredible.

migr13179269
07-22-2010, 5:30 PM
Stock Samsung Vibrant, irssiconnectbot and connectbot will not let me backspace with the swype keyboard

migr13232525
07-25-2010, 4:28 AM
Any timeframe for a fix? Been over a month now...

migr13715431
08-02-2010, 10:25 PM
Same issue with Samsung Vibrant.

migr13775997
08-04-2010, 12:37 PM
Same on my Nexus One, not rooted Froyo
Kernel .6.32.9-27227-g3c98b0d, android-build@apa26 #1
Build FRF91

The terminal app in question is
http://code.google.com/p/androidterm/
and I have also had no backspace action in http://code.google.com/p/android-scripting/
on Swype version 1.56.30.7625.t100

I suspect this is to do with Swype being focused on dealing with text fields with words in them, whereas these programs are listening for keystrokes. For example none of the affected apps can receive swiped words from Swype.

Toby Murray
08-13-2010, 6:00 PM
+1 on Vibrant (galaxy s). Apparently it has something to do with TextView vs TerminalView

Dattas Moonchaser
08-14-2010, 11:43 AM
Still a problem on the Samsung Vibrant, what is the status of this? This is critical enough for me that I've dropped swype for the default keyboard. The App developer can't do anything about this issue because the problem exists with your keyboard, not their software.

Misuzu
08-15-2010, 5:02 PM
I can't use Swype until this is fixed. Not worth switching back and forth.

Brian
08-19-2010, 10:52 PM
I was using the beta on my older android phone and considering purchasing a new one that came with swype, but this is ridiculous. I think instead, I'm going to intentionally buy an android phone that doesn't have swype. 2 months? Do they just not care? 2 months is an eternity in the smart phone market.

migr13240059
08-20-2010, 6:33 AM
Please, some update on the current bugfixing status would be nice at least. I don't know whether the Swype team may see this issue as minor, but for people who need to log in to remote machines using ConnectBot and friends this is a complete showstopper!

indraf
08-25-2010, 2:01 AM
it was flawless untill i found this "backspace problem"

rickw
08-28-2010, 8:17 PM
Hmm - I thought the problem was with Documents to Go, until I tried turning Swype off on my Galaxy S, and with the basic samsung keyboard I can now delete again!

So I can edit documents at last on my Galaxy, but it's goodbye swype.
Sucks, because I was really liking it.

Unfortunately on the Galaxy S you set the default keyboard for the whole phone, so this means I can't swype for anything, (I could switch back and forth every time, but I doubt I'll bother.)

Wow - I've never loved anything so much and then turned it off so quickly! :-(

zaq111
08-31-2010, 3:24 PM
Preface: backspace doesn't work on rooted or stock nexus one.

I don't know if the mods are watching or if they care, but in connectbot you can do a trackball+d for delete or trackball+h for backspace. Not a true fix but at least it's a workaround.

brian.resnik
08-31-2010, 4:01 PM
Preface: backspace doesn't work on rooted or stock nexus one.

I don't know if the mods are watching or if they care, but in connectbot you can do a trackball+d for delete or trackball+h for backspace. Not a true fix but at least it's a workaround.

We're watching and we certainly care :) This issue is known and slated for fixing, but we haven't determined a cause yet. What we REALLY need is for the developers of the effected apps to analyze their apps to see why this is happening with their particular code. If we know the root cause, we're better equipped to adapt our software.

sadroid
09-01-2010, 8:26 AM
in connectbot you can do a trackball+d for delete or trackball+h for backspace. Not a true fix but at least it's a workaround.

Not for us Galaxy S i9000/Vibrant/Captivate etc. users who do not have a directional pad or trackball.

NinjaFish
09-03-2010, 12:36 PM
We're watching and we certainly care :) This issue is known and slated for fixing, but we haven't determined a cause yet. What we REALLY need is for the developers of the effected apps to analyze their apps to see why this is happening with their particular code. If we know the root cause, we're better equipped to adapt our software.

Phil Hassey, the developer of Galcon, has a post on his blog that references this issue specifically: http://www.philhassey.com/blog/2010/08/27/android-day-11-troubleshooting/

brian.resnik
09-03-2010, 8:07 PM
Thanks very much for the link. I'll pass this information along to our development team and hopefully they'll be able to implement a proper fix.

FOLLOWUP: We've tracked down the exact cause of this issue. I've submitted a bug to our internal bug tracker and this should be fixed soon. Thanks everyone so much for helping track this issue down!

NinjaFish
09-12-2010, 5:34 AM
Thanks very much for the link. I'll pass this information along to our development team and hopefully they'll be able to implement a proper fix.

FOLLOWUP: We've tracked down the exact cause of this issue. I've submitted a bug to our internal bug tracker and this should be fixed soon. Thanks everyone so much for helping track this issue down!

When can those of us who had Swype pre-installed on our phones expect this to get fixed?

Mr.anon
09-22-2010, 10:20 AM
When can those of us who had Swype pre-installed on our phones expect this to get fixed? ditto. eager to turn swype back on my droid x.

sndwv1
07-28-2011, 4:18 AM
I noticed this exact same problem on two apps (aDOSBox and AnDOSBox). The SWYPE keyboard backspace appears to not work (with other softkeyboards or default SAMSUNG keypad it does work), but I noticed that it requires five taps before registering as a backspace keypress onward. I contacted the developers of the apps about this, but the AnDOSBox devs pointed me here. Is this the same problem still not fixed for Galaxy S users or is this a new issue?