When starting, the command is not displayed: 'am start -n

Question

Recently, when I try to run Android applications on my device, I have to run it several times from Eclipse before it starts.

I tried reinstalling the JRE, JDK, and IDE, and I tried switching workspaces. I also allowed Eclipse to use more RAM for the Java virtual machine.

Both IDE, JRE, JDK, ADT, and ADT modules are updated.

Any suggestions on this subject are greatly appreciated.

There is no command exit at startup: 'am start -n com.example.abstab / com.example.abstab.ActivityMain -a android.intent.action.MAIN -c android.intent.category.LAUNCHER' ​​on device HT15CV805781

Exception stack trace:

com.android.ddmlib.ShellCommandUnresponsiveException at com.android.ddmlib.AdbHelper.executeRemoteCommand(AdbHelper.java:408) at com.android.ddmlib.Device.executeShellCommand(Device.java:453) at com.android.ide.eclipse.adt.internal.launch.ActivityLaunchAction.doLaunchAction(ActivityLaunchAction.java:67) at com.android.ide.eclipse.adt.internal.launch.ActivityLaunchAction.doLaunchAction(ActivityLaunchAction.java:109) at com.android.ide.eclipse.adt.internal.launch.AndroidLaunchController.doLaunchAction(AndroidLaunchController.java:1277) at com.android.ide.eclipse.adt.internal.launch.AndroidLaunchController.doLaunchAction(AndroidLaunchController.java:1289) at com.android.ide.eclipse.adt.internal.launch.AndroidLaunchController.launchApp(AndroidLaunchController.java:1261) at com.android.ide.eclipse.adt.internal.launch.AndroidLaunchController.simpleLaunch(AndroidLaunchController.java:906) at com.android.ide.eclipse.adt.internal.launch.AndroidLaunchController.continueLaunch(AndroidLaunchController.java:748) at com.android.ide.eclipse.adt.internal.launch.AndroidLaunchController.launch(AndroidLaunchController.java:640) at com.android.ide.eclipse.adt.internal.launch.LaunchConfigDelegate.doLaunch(LaunchConfigDelegate.java:322) at com.android.ide.eclipse.adt.internal.launch.LaunchConfigDelegate.launch(LaunchConfigDelegate.java:238) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:855) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:704) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1047) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1251) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) 

Session Data:

 eclipse.buildId=M20120914-1800 java.version=1.7.0_15 java.vendor=Oracle Corporation BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US Framework arguments: -keyring /Users/myname/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws cocoa -arch x86_64 -keyring /Users/myname/.eclipse_keyring -showlocation 

Answer 1

I am facing the same majority of the time, and it works when I restart the ADB server. In most cases, ADB goes into a kind of suspended state (especially when emulators start again), and I had to restart it manually, for example:

 adb kill-server adb start 

After restarting ADB using the above commands, Eclipse Android is very stable.

Answer 2

'am start -n com.example.abstab / com.example.abstab.ActivityMain -a android.intent.action.MAIN -c android.intent.category.LAUNCHER' ​​on device HT15CV805781

HT15CV805781 a device problem may occur

in com.android.ddmlib.Device.executeShellCommand (Device.java:453)

this exception line indicates that your application has problems running on the device.

A reboot device can sometimes help or restart the adb bridge connection.

Answer 3

try this command:

 adb.exe kill-server adb.exe start-server adb.exe shell am start -n com.example.abstab/.ActivityMain