Stopping immediately after pressing the start button

[GoogleCodeExporter]

* Asus TF101G
* Android 3.2.1
* Kernel 2.6.36.3 (in case that matters)
* Device is not rooted
* DroidSSHdv06.apk (appears as 0.5 in control panel?!?)
* Press Start
* Returns immediately to stopped state
* A previous installation of 0.5 (from android market) did start. However, when 
logging in using a terminal window from Mac OS X Lion, an error message was 
printed since a logfile couldn't be created. After that, ssh worked fine. But 
this issue probably prevented both Cyberduck and MacFusion to connect to the 
device.
* I had no luck getting an error message using the command
  am start -a android.intent.action.MAIN -n br.com.bott.droidsshd/br.com.bott.droidsshd.DroidSSHd
* ssh connections work well using a Nokia N900

Was it possible to grab an error message in case something went wrong? Maybe a 
log file could be written to a user writable folder?

Thanks for sshd for Android BTW. I know from experience that open source coders 
usually only get user feedback in case something does not work :) .

Original issue reported on code.google.com by static.public.void on 21 Feb 2012 at 10:36

[GoogleCodeExporter]

I had the same problem with my device rooted and starting as root.
There have been some sidekicks as well: although listed in task list I couldn't 
get back to the active app by clicking it. I got another instance running which 
then would stop immediately after starting because of the used port.
I found out dropbear was still running even after force closing droidsshd and i 
had to kill the dropbear application so I could start it again using droidsshd.
Additionally using root any ssh connection fails because of child error.
I assume it's something about paths and permissions where pid files are saved 
and maybe the user management.

used:
* Samsung Galaxy S4 I9505
* Android 4.2.2
* rooted

Original comment by BAERn...@gmail.com on 8 Jul 2013 at 12:18