Open GoogleCodeExporter opened 8 years ago
Thanks for the feedback! I've also been trying it properly over the past
couple of
days and have seen the same issues you describe with completion appearing. It
does
go away when the keyboard's relaunched from the icon, so I've been trying to
work
out how to configure the input type on connect.
ReeeYeees - do you use a private/public key for login? Wwhen you do this, it
won't
hide the keyboard as it doesn't go through the password prompt code path.
Either way, both issues are related to the same problem - how to configure the
keyboard properly after connection. I've tried the restartInput in the same
place,
but it doesn't fix it. Any other thoughts on how to disable the completion?
Original comment by dominic.cleal@gmail.com
on 29 Aug 2009 at 6:36
I'm also having keyboard issues including the duplicate key one. Is this patch
going
to be folded in?
Another issue I'm having is that when the keyboard goes away (like if I
accidentally
tell it to), there seems to be no way to get it back unless I go back to the
menu and
re-open the session.
I have the hero.
Original comment by penelope...@gmail.com
on 1 Sep 2009 at 6:06
Penelope: On my hero the following helps: after closing the keyboard, hit the
terminal background. Keyboard item appears in the top right corner, tap it ->
keyboard is up again.
Original comment by martin.u...@gmail.com
on 2 Sep 2009 at 6:41
I just tested ConnectBot on a CDMA Hero and it doesn't have the
"12#"-button-doesn't-work bug.
you have to close the keyboard and reopen it to get the long-press on a key to
work
like you'd expect. Actually sending the key press event while holding down a
key when
TYPE_NULL is set is probably not good, though. I don't see any reason for it to
behave that way.
Original comment by kenny@the-b.org
on 3 Sep 2009 at 9:29
martin.und.katja / dominic.cleal
your close/open virtual keyboard is a great work around for me for symbol
typing, thanks.
12# button works fine for me (r409) without work around
Original comment by darksk...@gmail.com
on 11 Sep 2009 at 4:22
Could you give an indication of what it shows under Settings -> About Phone ->
Build/Firmware version?
Original comment by kenny@the-b.org
on 11 Sep 2009 at 4:26
I Have the same problem, not able to write <> symbols
under the 12# button.
Original comment by spsi...@gmail.com
on 14 Sep 2009 at 7:04
I Have the same problem, not able to write <> symbols
under the 12# button.
Original comment by spsi...@gmail.com
on 14 Sep 2009 at 7:05
I have the same problem in two applications with my HTC Hero, ConnectBot and
remoteVNC. When I get the keyboard it isn't possible to write symbols. The 12#
seems
not doing what it should. And two chars are sent when long pressing a key.
Original comment by fio...@gmail.com
on 21 Sep 2009 at 8:52
Just added the new firmware to my hero and the 12# button now works. Long
holding the
buttons also now works (if you close and reopen the keyboard!)
Original comment by dr.i.a.n...@gmail.com
on 21 Sep 2009 at 3:15
Same as commenc 60 for me. Newest firmware.
Bug appears on application startup.
Close and reopen of keyboard makes the bug go away.
Original comment by vidar.wa...@gmail.com
on 21 Sep 2009 at 5:29
Issue 223 has been merged into this issue.
Original comment by kenny@the-b.org
on 28 Nov 2009 at 4:32
I have the HTC Hero (Sprint, US). I'm having difficulty using the pipe
character ('|').
I can insert a broken vertical bar ('¦'), but this seems to be interpreted
differently
from a plain vertical bar. For example, "echo hi ¦ grep hi" (without quotes)
produces
"hi ¦ grep hi" instead of just "hi". Also, "ps ¦ more" produces "Error:
Garbage
option." followed by a bunch more text. Either I'm doing something dumb and
can't
figure out how to use the pipe properly, or there isn't a way to insert one on
the HTC
Hero's virtual keyboard. I've heard that Sprint is going to update to Android
2.1
sometime in the near future (from 1.6 i believe), so maybe that will fix things.
Original comment by gshs1...@gmail.com
on 4 Jan 2010 at 2:03
Need this, im from finland and this is one of the biggest issues for me with
connectbot
Original comment by jonne.ba...@gmail.com
on 11 Jan 2010 at 3:15
I'm seeing the double key issue on the HTC Droid Eris (Verizon); also the lack
of a
pipe is a major issue. I've tried both 466 & 472 and am still seeing the
issues.
Original comment by SDNick...@gmail.com
on 8 Feb 2010 at 8:14
Looks like the HTC is probably sending the right character:
http://www.fileformat.info/info/unicode/char/00a6/index.htm
But everyone is used to this character being sent as the following from most
physical
keyboards even though the symbol is the broken bar:
http://www.fileformat.info/info/unicode/char/007c/index.htm
And this site seems to explain the confusion between to two characters:
http://en.wikipedia.org/wiki/Vertical_bar
Guess the HTC keyboard needs to adopt the confusion.
Original comment by hit...@gmail.com
on 10 Feb 2010 at 8:47
Issue 282 has been merged into this issue.
Original comment by kenny@the-b.org
on 13 Mar 2010 at 8:49
Hi,
I also have this problem with german htc hero.maybe you can use the input-field
(password for
connection) also for every text-input.
Using r496
Original comment by frank.wunderlich@gmail.com
on 24 Mar 2010 at 6:56
Hi,
HTC Hero (rus). For two weeks I having an issue with "backspace" button on
virtual
keyboard - its just not pressing. I`m trying to press another button, and keep
moving
my finger to "backspace" - I`m getting animation of pressing it, but nothing in
my
text getting removed.
I thinking about something in dictionary, that broke my virtual keyboard (dunno
what
else can explaing some "changes" in keyboard programm). Using HTC Hero for 6
month.
Original comment by multprik...@gmail.com
on 30 Mar 2010 at 9:15
FWIW, there's a modified HTC_IME here
(http://forum.xda-developers.com/showthread.php?
t=624416) that adds a real ASCII pipe character, though it doesn't fix the
double-
characters-on-first-open problem.
Original comment by aripol...@gmail.com
on 6 Apr 2010 at 4:26
Having the same issue on an European HTC Desire running 2.1 and the stock
HTC_IME.
Will test the close/open OSK workaround tonight.
Having no issues opening the 12# section of the OSK.
Original comment by stokesge...@gmail.com
on 14 May 2010 at 7:47
I am using ConnectBot r480 (2010.02.12) as downloaded from the Android Market
on an
HTC Incredible (Verizon) in the US, language is English, and I'm connecting to a
Debian Linux box. I appear to be having the same basic issue as the original
poster.
Pressing and holding most buttons on the software keyboard to access secondary
symbols (like pressing and holding 'x' to get a quote symbol) results in the
basic
character being immediately echoed to the terminal when the key is pressed,
then the
secondary symbol is sent after a moment. So, instead of ", I have x".
TWO KEYS on the software keyboard are EXEMPT from this problem; the ,/; and ./:
keys
work as desired. I can press and hold the period key and the period is not
immediately sent, and the colon is sent after a moment. Apparently, these keys
are
somehow different from the others.
It is possible to reach all of the symbols through the 12# button (that is
working
fine) but it would be certainly welcome if the press and hold shortcuts worked
on the
rest of the keyboard.
Original comment by TGTMar...@gmail.com
on 20 May 2010 at 5:50
I have experienced the same issue on an HTC Desire.
Original comment by stedmeis...@gmail.com
on 25 May 2010 at 12:42
Same issue with HTC_IME mod v25 (derived from HTC_IME) on Nexus One.
I think ConnectBot might workaround the bug by adding a "don't auto-open
keyboard"
option in its settings, so it behaves like Better Terminal Emulator Pro, which
does
*not* have this issue with HTC keyboard.
Original comment by joel.bou...@gmail.com
on 25 May 2010 at 12:50
I have this issue as well, as explained by TGTMarten, and I have an easy
work-around. The "auto-open keyboard" mentioned by joel.bourguard appears to be
the issue. If I close the keyboard and then open it manually, it begins to
function properly again and I no longer get the unwanted characters.
Original comment by wireless...@gmail.com
on 6 Jul 2010 at 2:41
excellent, joel.bourguard: that deals with the problem on the evo as well
Original comment by rluse...@gmail.com
on 7 Jul 2010 at 3:58
Hi,
i'm using ConnectBot on SSH,
sometimes the "long 'n' press" works (strangely but works)
and sometimes not.
I don't understand why it's so hard to get software inputs ?
it's not possible to get pluged on the soft-keyboard output ? (and let's him
deal with long-press and other things )
it's maybe because of shortcuts ?
isn't possible to use 2 modes : one for shortcut, one for classic inputs ?
Original comment by aurelien...@gmail.com
on 21 Jul 2010 at 12:04
A workaround for the missing pipe character in bash is to use construct the
commands as strings and run the with eval. This works in bash, anyway.
$ export p='|'
$ eval "echo 'issue' | xargs -I_ echo schm_"
Original comment by thomas.h...@gmail.com
on 25 Jul 2010 at 3:47
Issue 319 has been merged into this issue.
Original comment by kenny@the-b.org
on 4 Aug 2010 at 4:43
Issue 313 has been merged into this issue.
Original comment by kenny@the-b.org
on 4 Aug 2010 at 4:58
Is there a way to type a pipe "|" character with the soft keyboard? HTC
Incredible here. My issue was merged to this one, but I don't see a solution.
Original comment by gavinburris@gmail.com
on 4 Aug 2010 at 5:50
I too need a hash | for my droid incredible.
Original comment by jpv...@gmail.com
on 10 Aug 2010 at 2:54
The shift key does not work when using SwiftKey (HTC Hero).
Original comment by Christop...@gmail.com
on 10 Sep 2010 at 3:55
Same problem here: shift key does not work on Connectbot with SwiftKey, very
annoying bug. This bug did not exist with the native Froyo keyboard, so I am
guessing swiftkey is to blame, though not sure.
This problem occurs once the connection is established to a ssh server and
using swiftkey as a terminal keyboard, not when setting up connections
Nexus One, Froyo 2.2 (stock)
Original comment by yann...@gmail.com
on 13 Sep 2010 at 12:29
Connectboot dont work, sucks on andorid 2.1
Original comment by do83...@gmail.com
on 15 Sep 2010 at 4:11
Issue still exists on HTC Desire, not rooted, no custom ROM, no custom
keyboard, latest updates from HTC. Makes ssh almost unusable.
Original comment by kong...@gmail.com
on 25 Sep 2010 at 7:13
As a workaround, try to install and use "Full Keyboard"
http://www.appbrain.com/app/com.hmw.android.fullkeyboard
Original comment by michael....@gmail.com
on 25 Sep 2010 at 5:27
Is it just me, or is this problem suddenly resolved? (HTC_IME Mod on Android
2.2, Nexus One)
Original comment by joel.bou...@gmail.com
on 12 Oct 2010 at 10:18
Works great here now as well! Thanks!
Original comment by frankgroeneveld
on 8 Jan 2011 at 9:30
I cannot believe this issue has been around for over a year and it is still not
fixed.
How hard can this be? Not being able to type a correct pipe char makes this
terrible for using with Linux systems. My failure is on HTC Incredible,
totally vanilla US version.
Original comment by drbob...@gmail.com
on 12 Mar 2011 at 12:39
I've yet to see any need for the ¦ character (U+00A6) in the context of
ConnectBot. Yet we all here are screaming (politely) for the | character
(U+007C). Can ConnectBot not just provide a transparent mapping of the
"useless" character to the "necessary" one?
At the moment I have to use Hacker's Keyboard, which although it's nice, is
actually less convenient on my relatively small HTC Wildfire (UK version).
Thanks!
Original comment by cdroa...@gmail.com
on 28 Oct 2012 at 5:05
Original issue reported on code.google.com by
thelinxswe
on 15 Jul 2009 at 1:21