Local shell fails on the Verizon Droid.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use a Droid, with Android 2.0
2. Open a Local Shell on ConnectBot

What is the expected output? What do you see instead?
I expect to see a local shell.  Instead, it says:
"Failure! Local shell is unavailable on this phone."

Original issue reported on code.google.com by sparkm...@gmail.com on 10 Nov 2009 at 8:12

[GoogleCodeExporter]

Given that it sounds like you don't have one to test on, if you need anyone to 
run
any tests on a Droid for you, just let me know. I would be happy to follow a
procedure and report the results to you. Connectbot is an awesome app, and I 
hope you
guys can get this issue resolved.

Original comment by jcall...@gmail.com on 13 Nov 2009 at 9:52

[GoogleCodeExporter]

I have the same problem/can make the same offer to help debug.
For what it's worth, the shell still seems to be /system/bin/sh,
as src/org/connectbot/transport/Local.java seems to expect.
More elaborate exception processing for the createSubprocess
call might reveal the specific error.

Original comment by charlech...@gmail.com on 16 Nov 2009 at 3:51

[GoogleCodeExporter]

The problem is that android.os.Exec was removed from 2.0 which is what we used 
to
create a PTY. It seems that others have started compiling their own JNI code.

Original comment by kenny@the-b.org on 17 Nov 2009 at 7:30

• Changed state: Accepted

[GoogleCodeExporter]

This should be fixed in r427

Original comment by kenny@the-b.org on 17 Nov 2009 at 8:01

• Changed state: Fixed