jumaris / connectbot

Automatically exported from code.google.com/p/connectbot
Apache License 2.0
1 stars 0 forks source link

Connect bot doesn't work properly with the onscreen keyboard of Android 1.5 (needed for HTC Magic) #142

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Use ConnectBot on a new HTC Magic, connect to some SSH host.
2. When the terminal window shows up, I need to open the keyboard manually 
through holding the menu key.
3. I can enter some letters, but the return key isn't recognized, so I'm 
unable to perform any commands.

What is the expected output? What do you see instead?
I'd expect that the onscreen keyboard shows up automatically and that 
connectbot's window is resized accordingly (perhaps not landscape would be 
cool). And that all keys from the onscreen keyboard are recognized.

What version of the product are you using (you can see this by using Menu -
> About in the Host List)?
1.3 r204 2009.02.18

What type of system are you trying to connect to?
Usual SSH systems.

If you are able to connect, what is the output of "echo $TERM", "uname -a", 
and any other relevant information on the host?
Hehehe, can't execute that command.

Please provide any additional information below.

Original issue reported on code.google.com by garbeam on 4 May 2009 at 6:40

GoogleCodeExporter commented 8 years ago
Try a revision after r217 to see if it works. Also, let me know if the back 
button
just closes the keyboard instead of going to the host list.

Original comment by kenny@the-b.org on 5 May 2009 at 10:05

GoogleCodeExporter commented 8 years ago
I was experiencing exactly the same problem with my new HTC Magic. I was also 
using 
the r204 revision.

Now I installed the r221 and the on-screen keyboard works fine.

Thanks.

Original comment by samuel.p...@gmail.com on 6 May 2009 at 9:37

GoogleCodeExporter commented 8 years ago
Hi, the onscreen keyboard works with r221, however it is not a great 
experience. I 
have to keep the menu pushed in order to pop it up, it would be better if 
connectbot 
could stay in portrait mode instead and display the keyboard non-overlapping 
automatically when the terminal shows up. If possible it would be desirable to 
expose 
the ctrl key as well (not sure if there's some option in the SDK API for that, 
need 
to check).

But many thanks anyways so far. I can at least do some basic stuff now ;)

Thanks.

Original comment by garbeam on 6 May 2009 at 10:31

GoogleCodeExporter commented 8 years ago
Hi garbeam, I also had problems with the keyboard overlapping with the terminal.

I played around with the configuration and finally my the terminal stays in 
portrait 
mode, the keyboard appears automatically and doesn't overlap.

My current settings are:
Emulation mode: screen
Rotation mode: automatic
Full screen: ON

Hope it works for you.

Original comment by samuel.p...@gmail.com on 6 May 2009 at 10:45

GoogleCodeExporter commented 8 years ago
Hi Samuel,

I followed your steps, but I got the impression that the keyboard is more 
likely to 
push the top of the terminal window offscreen to the top, so it's cropped for 
me 
until I press back and then press menu longer in order to make the keyboard 
reappear. 
When it reappears then in fullscreen portrait mode, it is overlapping and the 
terminal underneath is aligned correctly to the screen again. I really think 
connectbot must deal with this in a better fashion. I can live with it as it is 
for 
now though.

The biggest concern I have is the lack of the ctrl key on the virtual keyboard, 
so 
using screen(1) remotely is nearly impossible...

Kind regards,
Anselm

Original comment by garbeam on 7 May 2009 at 7:41

GoogleCodeExporter commented 8 years ago
I'm just going to track this in Issue 112.

Original comment by kenny@the-b.org on 7 May 2009 at 3:40

GoogleCodeExporter commented 8 years ago
Same issue, with new htc unit received at Google I/O conference.  There's no 
version
number for ConnectBot in the application settings... but it was downloaded 
today.
In addition to the issues the first poster mentioned, the onscreen keyboard 
does not
"bump up" the terminal, so you can't see what you are typing.

Original comment by digitalbitstream@gmail.com on 28 May 2009 at 4:58

GoogleCodeExporter commented 8 years ago
same issues w/ Google I/O conf version per digitalbitstream.

Original comment by jvale...@gmail.com on 30 May 2009 at 4:22

GoogleCodeExporter commented 8 years ago
Same problem with Google I/O conf phone - android 1.5

Original comment by karlh...@gmail.com on 31 May 2009 at 5:25

GoogleCodeExporter commented 8 years ago
Same sort of issues here to .. Im also am unable to use numbers in my path. eg 
cd
/volume1/ I am unable to enter the 1 it keeps appearing as a 'q'

Original comment by wmitch...@gmail.com on 14 Aug 2009 at 7:33

GoogleCodeExporter commented 8 years ago
Im using a HTC hero and I am unable to switch the keyboard to numbers also

Original comment by wmitch...@gmail.com on 14 Aug 2009 at 7:36

GoogleCodeExporter commented 8 years ago
effective use on portrait mode really requires an on screen keyboard with a 
working return key, and a terminal that sizes itself to fit the remaining space 
on the screen. is this possible currently?

Original comment by nickurak on 26 Apr 2010 at 12:17