This project has moved. For the latest updates, please go here.
2
Vote

App stuck on run during 'Attempting to launch ADB as Root' with Samsung Devices

description

Windows 7 (x64)
Droid Explorer 0.9.0.4 Beta


Rooted Devices:
Galaxys S4 (4.4) - Droid Explorer crashes
Galaxys 2 (4.1) - Droid Explorer stuck
Galaxy Note (4.1) - Droid Explorer stuck

file attachments

comments

TranzioR wrote Sep 15, 2015 at 3:31 PM

Small notes: Running Droid Explorer from device shortcut in windows explorer is successful

camalot wrote Sep 15, 2015 at 4:01 PM

Try setting HKEY_LOCAL_MACHINE\SOFTWARE\DroidExplorer\CloudStatistics = 0 in the registry:
  • press WIN+R
  • type regedit
  • navigate to HKEY_LOCAL_MACHINE\SOFTWARE\DroidExplorer
  • double click on CloudStatistics
  • change the value to 0
  • press OK
  • try launching droid explorer again.
It looks like there was an issue while trying to send that statistics information

wrote Sep 15, 2015 at 4:02 PM

TranzioR wrote Sep 15, 2015 at 4:43 PM

The same result: App stuck on run during 'Attempting to launch ADB as Root'

camalot wrote Sep 16, 2015 at 5:30 PM

I have a Note 2. I will see if I can reproduce. although it is not running samsung's version of android (TouchWiz).

I am also going to see if there is more logging information that I can add during the initialization that may indicate what the problem is.

wrote Sep 16, 2015 at 6:28 PM

Associated with changeset 111720:
  • Added link to WiFi ADB app on the remote connect dialog. This will help people enable wifi adb. [workitem:17533]
  • Added method to IPlugin interface to initialize the plugin. This can be used to set up files on the device before the plugin executes.
  • Removed androidscreencast, switched to using android screen monitor fork (https://github.com/camalot/android-screen-monitor). The fork allows the device ID to be passed as an argument. This way the user does not have to select the device again.
  • Changed the call to launch the jar for screen monitor to call "java.exe", before it was just "java" and that was causing issues. [workitem:17531]
  • Added more logging during initialization to help with debugging start up issues. [workitem:17527]
  • Set the toolstrip renderer on screenshot plugin to be the same that is used elsewhere.

wrote Sep 17, 2015 at 5:30 PM

TranzioR wrote Sep 17, 2015 at 5:30 PM

New logs

wrote Sep 18, 2015 at 12:22 PM

Jorrit wrote Sep 19, 2016 at 6:28 PM

I have this issue. My logs read:

2016-09-19 19:26:35,368 [1 ][ DEBUG] [DroidExplorer.Core.Logger] Loading Droid Explorer Settings
2016-09-19 19:26:35,432 [1 ][ DEBUG] [DroidExplorer.Core.Logger] Settings Loaded from file 'C:\Users\xxxxx\AppData\Roaming\DroidExplorer\Data\DroidExplorer.config'
2016-09-19 19:26:35,433 [1 ][ DEBUG] [DroidExplorer.Core.Logger] Locating SDK Path
2016-09-19 19:26:35,435 [1 ][ DEBUG] [DroidExplorer.Core.Logger] SDK Path Set to C:\Users\xxxxx\AppData\Local\Android\android-sdk
2016-09-19 19:26:35,435 [1 ][ DEBUG] [DroidExplorer.Core.Logger] Verifying SDK Tools
2016-09-19 19:26:35,443 [1 ][ DEBUG] [DroidExplorer.Core.Logger] adb.exe version
2016-09-19 19:26:35,493 [1 ][ DEBUG] [DroidExplorer.Core.Logger] Starting ADB Server
2016-09-19 19:26:35,513 [1 ][ DEBUG] [DroidExplorer.Core.Logger] adb.exe start-server
2016-09-19 19:26:35,789 [1 ][ DEBUG] [DroidExplorer.Core.Logger]
2016-09-19 19:26:35,790 [1 ][ DEBUG] [DroidExplorer.Core.Logger] Getting connected devices
2016-09-19 19:26:35,860 [10 ][ DEBUG] [DroidExplorer.Core.Logger] Registering anonymous statistics for device types
2016-09-19 19:26:35,862 [1 ][ DEBUG] [DroidExplorer.Core.Logger] Attempting to launch ADB as Root.