No command output when running: 'am start -n Error

Question

When I run my application in eclipse and click on a button to start a new Activity my application force closes and I get this error:

null
Error
Sat Apr 23 19:53:21 CDT 2011
No command output when running: 'am start -n com.example.lostalarmclock/com.example.lostalarmclock.LostAlarmClock -a android.intent.action.MAIN -c android.intent.category.LAUNCHER' on device emulator-5554

com.android.ddmlib.ShellCommandUnresponsiveException
at com.android.ddmlib.AdbHelper.executeRemoteCommand(AdbHelper.java:408)
at com.android.ddmlib.Device.executeShellCommand(Device.java:276)
at com.android.ide.eclipse.adt.internal.launch.ActivityLaunchAction.doLaunchAction(ActivityLaunchAction.java:74)
at com.android.ide.eclipse.adt.internal.launch.AndroidLaunchController.launchApp(AndroidLaunchController.java:1146)
at com.android.ide.eclipse.adt.internal.launch.AndroidLaunchController.clientChanged(AndroidLaunchController.java:1489)
at com.android.ddmlib.AndroidDebugBridge.clientChanged(AndroidDebugBridge.java:868)
at com.android.ddmlib.Device.update(Device.java:398)
at com.android.ddmlib.Client.update(Client.java:835)
at com.android.ddmlib.HandleAppName.handleAPNM(HandleAppName.java:90)
at com.android.ddmlib.HandleAppName.handleChunk(HandleAppName.java:64)
at com.android.ddmlib.MonitorThread.callHandler(MonitorThread.java:414)
at com.android.ddmlib.MonitorThread.processClientActivity(MonitorThread.java:322)
at com.android.ddmlib.MonitorThread.run(MonitorThread.java:263)

How can I fix this?

Answer 1

This error killed my many hours... Finally below steps helped.. Let me share so that some one can benefited...

In eclipse Increase the ADB connection timeout by following below steps

Window --> Preferences

Select Andriod -> DDMS from left panel

Increase value of "ADB connection time out (ms)"