It would really help me out if the ‘text input’ box had a ‘command history’. Thus that above whatever the terminal provides. Especially on simple devices (cellphones) without a full qwerty keyboard that could save a lot of time. It would only have to remember them during a session.

If I had the time I’d look into it myself, but I’ve got so many things going on now (I guess that sounds familiar for you).

1. In the menus you select before connecting, you can’t merely click the pearl (or blackberry wheel-click on the older 87xx series), or press enter, you always have to press the “make a dropdown menu appear” button and select the first option in the dropdown menu. This makes the interface clunky and awkward, and should be changed to have a default action for “click” or “enter”.

2. When in “type” mode, pressing the “SYM” (Symbol) button should bring up the typical symbol prompt so the user doesn’t have to enter “input” mode to type something like this: “export TERM=foo” because of the ‘=’ character.

I recently exchanged my Samsung Instinct for a Blackberry Pearl, just to be able to run midpssh. I love the program and it works wonderfully. I was wondering though, would it be possible to allow multitap from the command line? Right now when I press a key, only the first letter on the key is typed. All the commands I enter I have to type from the Input test box, and that’s a pain because most of the time it capitalizes the first char of every “sentence”.

Thanks for this awesome program!

Rene

I’ve stumbled on two problems -

1) In some cases, when switching between Text and AMF view, I get an exception - Failed to parse data. (java.io.EOFException)

2) It seems impossible to add new AMF entries when editing an AMF request. I can tamper with existing values, but I cannot add my own key/value pairs.

-OS

I love this program but unfortunately I’m unable to get it to work on the new Sprint Instinct (SPH-M800). Are there any plans to support this phone in the future? It does load fine, but I’m unable to input any text most likely because of its “virtual onscreen keyboard”.

Thanks!

But..

The input method is counterproductive on the TYTN II as it has a nearly full keyboard already. It, however, does not have seperate keys for the numbers 0 to 9, including * and #. To enter a line of text:

Fn-U (enter Type mode, 2 keypresses)
some text
Left-button (exit Type mode, 2 keypresses)
Fn-K (2 keypresses, to simulate the Enter button. The “Return” key is ignored)

MidpSSH could offer a more advanced input mode, allowing direct input from the keyboard of the device. The TYTN II lacks many special keys, even on the on-screen keyboard, making the keys in MidpSSH menus very nice to have.

I am using 1.7.3 on a Blackberry 8830 on Verizon, no BES.

About half the time connecting will fail some place between ‘OK’ and getting the prompt on the remote system.

The times that it does connect I generally get disconnected within 3-4 minutes, and quite often within the first 1-2 minutes.

In all cases, I get “Session Error Reader: Connection Closed”

Any ideas?