Problem bei USB-Verbindung zu Samsung Xcomer4

Eich
Beiträge: 1
Registriert: Di 16. Mai 2017, 14:00

Problem bei USB-Verbindung zu Samsung Xcomer4

Beitrag von Eich »

Servus,

bin langjähriger Benutzer von MyPhoneExplorer mit Samsung Geräten.

Da altes Gerät kaputt wurde, habe ich mir ein Samsung Xcover 4 zugelegt.
Und nun habe ich Probleme mit der USB Connection.

System: W7, MyPhoneExplorer 1.8.8, Debugg-Mode offen; Kies installiert um Treiber zu laden. USB-Mode am Handy: nur laden

Bitte um Hilfe.
Danke Kurt

Logdatei:
ogdatei MyPhoneExplorer
************************
Programmversion: 1.8.8
Datum: 16.05.2017

14:15:21.05 Windows Version=6.1
14:15:21.05 Setting Port: 999
14:15:21.05 Setting Baud: 115200
14:15:21.05 Avaiable Ports: COM3=\Device\ssudmdm0000;
14:15:21.05 Main Load frmSplash
14:15:21.06 Load frmSplash...
14:15:21.06 Show splash...
14:15:21.07 frmSplash geladen
14:15:23.18 Hauptfenster wird geladen
14:15:23.33 Sidebar fertig geladen
14:15:23.53 UC SMS wird geladen
14:15:23.56 UC Phonebook wird geladen
14:15:23.58 UC Phonebook fertig geladen
14:15:23.58 UC Calls wird geladen
14:15:23.60 UC Organizer wird geladen
14:15:23.65 Organizer initiated
14:15:23.67 Startpage=3
14:15:23.68 UC Filebrowser wird geladen
14:15:23.76 UC Filebrowser fertig geladen
14:15:23.76 UC AppBrowser wird geladen
14:15:23.77 UC Notes wird geladen
14:15:23.78 UC Calls wird geladen
14:15:23.81 Setting Lastuser: samsung GT-S7710 [356779055332901]
14:15:23.82 PasswordCheck OK, check Userfolder, G_AppData=C:\Users\Eich\AppData\Roaming\MyPhoneExplorer
14:15:23.82 CheckUserDirectory for: samsung GT-S7710 [356779055332901]
14:15:23.82 Userfolder=C:\Users\Eich\AppData\Roaming\MyPhoneExplorer\samsung GT-S7710 [356779055332901]
14:15:23.82 ParseModell
14:15:23.83 Lade Userdatenbank: samsung GT-S7710 [356779055332901]
14:15:24.03 LoadDatafile: pb_metadata.xml(2586 Bytes)
14:15:24.03 LoadDatafile: Phonebook.dat(184384 Bytes)
14:15:24.63 Kontakte geladen
14:15:24.63 LoadDatafile: Calls.dat(61796 Bytes)
14:15:24.76 ParseDialedCalls needed 31ms
14:15:25.21 Anrufe geladen
14:15:25.22 Organizer LoadUser DefaultTimeColWidth=113
14:15:25.23 LoadDatafile: Organizer.dat(215 Bytes)
14:15:25.23 LoadDatafile: cal_metadata.xml(673 Bytes)
14:15:25.23 Organizer geladen
14:15:25.23 LoadDatafile: Notes.dat(902 Bytes)
14:15:25.24 LoadDatafile: notes_metadata.xml(171 Bytes)
14:15:25.24 Notizen geladen
14:15:25.24 Load SMS Data...
14:15:25.24 LoadDatafile: SMS.dat(493156 Bytes)
14:15:25.25 SMS - Datenbank wird geladen...
14:15:25.70 SMS Laden - Readfile: 16 Split: 0 Parse: 437 HandleMultiSMS: 15 Nachrichten: 2606
14:15:25.70 LoadDatafile: SMSArchive.dat(1032758 Bytes)
14:15:25.79 SMS Archiv laden - Parse: 94
14:15:26.62 RefreshList (Archive): Addrows=374 Sort=78 MenuUpdate=16 Redraw=0
14:15:26.99 SMS Data Loaded...
14:15:26.99 SMS geladen
14:15:27.20 Hauptfenster fertig geladen
14:15:27.29 Init Android Connection for future connect via USB
14:15:27.29 RunADBCommand: start-server
14:15:31.94 Connect via USB
14:15:31.94 RunADBCommand: start-server
14:15:31.98 ADB CommandResponse:
14:15:31.98 RunADBCommand: devices
14:15:32.03 ADB CommandResponse: List of devices attached
42008d10a8ba34a3 device
14:15:32.03 Run DeviceTracker
14:15:32.05 Init Tracker
14:15:32.05 Device Tracker Message: OKAY001842008d10a8ba34a3 device

14:15:32.05 RunADBCommand: -s "42008d10a8ba34a3" forward tcp:5210 tcp:5210
14:15:32.08 ADB CommandResponse:
14:15:32.08 Try connecting to 127.0.0.1...
14:15:32.09 Socket closed
14:15:32.09 RunADBCommand: -s "42008d10a8ba34a3" shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
14:15:33.36 ADB CommandResponse: Starting: Intent { cmp=com.fjsoft.myphoneexplorer.client/.MainActivity launchParam=MultiScreenLaunchParams { mDisplayId=0 mFlags=0 } (has extras) }
14:15:33.51 Try launch USB connection
14:15:33.52 Socket closed
14:15:33.82 Try launch USB connection
14:15:33.83 Socket closed
14:15:34.12 Try launch USB connection
14:15:34.12 Socket closed
14:15:34.42 Try launch USB connection
14:15:34.42 Socket closed
14:15:34.71 Try launch USB connection
14:15:34.72 Socket closed
14:15:35.02 Try launch USB connection
14:15:35.03 Socket closed
14:15:35.32 Try launch USB connection
14:15:35.33 Socket closed
14:15:35.62 Try launch USB connection
14:15:35.62 Socket closed
14:15:35.91 Try launch USB connection
14:15:35.92 Socket closed
14:15:36.23 Try launch USB connection
14:15:36.23 Socket closed
14:15:36.52 Try launch USB connection
14:15:36.53 Socket closed
14:15:36.82 Try launch USB connection
14:15:36.82 Socket closed
14:15:37.12 Try launch USB connection
14:15:37.12 Socket closed
14:15:37.41 Try launch USB connection
14:15:37.42 Socket closed
14:15:37.72 Try launch USB connection
14:15:37.73 Socket closed
14:15:38.02 Try launch USB connection
14:15:38.02 Socket closed
14:15:38.32 Try launch USB connection
14:15:38.32 Socket closed
14:15:38.61 Try launch USB connection
14:15:38.62 Socket closed
14:15:38.93 Try launch USB connection
14:15:38.93 Socket closed
14:15:39.22 Try launch USB connection
14:15:39.23 Socket closed
14:15:39.52 Connect to Android failed!
14:15:39.52 bOpened=False
14:15:39.52 Refresh ComDescriptions...
14:15:39.52 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\9&DB7353A&1&0001
14:15:39.52 ErrMsg: Verbindung zum Handy konnte nicht aufgebaut werden!
14:15:42.29 DoAdbCommand failed: ExecCmd: Timeout!
14:15:45.56 Device Tracker Message: 0000
14:15:46.41 DBT_DEVICEREMOVECOMPLETE: COM3
14:15:53.18 Connect via USB
14:15:53.18 RunADBCommand: start-server
14:15:53.23 ADB CommandResponse:
14:15:53.23 RunADBCommand: devices
14:15:53.26 ADB CommandResponse: List of devices attached
14:15:53.26 Connect to Android failed!
14:15:53.27 bOpened=False
14:15:53.27 Kein Gerät über USB angeschlossen
14:15:53.27 Refresh ComDescriptions...
14:15:53.27 ErrMsg: Verbindung zum Handy konnte nicht aufgebaut werden:
Kein Gerät über USB angeschlossen
14:36:11.31 DBT_DEVICEARRIVAL: COM3
14:36:11.85 Device Tracker Message: 001942008d10a8ba34a3 offline

14:36:11.87 Device Tracker Message: 001842008d10a8ba34a3 device

14:36:15.33 Refresh ComDescriptions...
14:36:15.33 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\9&DB7353A&1&0001
14:36:30.45 Connect via USB
14:36:30.45 RunADBCommand: start-server
14:36:30.58 ADB CommandResponse:
14:36:30.58 RunADBCommand: devices
14:36:30.63 ADB CommandResponse: List of devices attached
42008d10a8ba34a3 device
14:36:30.63 RunADBCommand: -s "42008d10a8ba34a3" forward tcp:5210 tcp:5210
14:36:30.67 ADB CommandResponse:
14:36:30.67 Try connecting to 127.0.0.1...
14:36:30.68 Socket closed
14:36:30.68 RunADBCommand: -s "42008d10a8ba34a3" shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
14:36:31.96 ADB CommandResponse: Starting: Intent { cmp=com.fjsoft.myphoneexplorer.client/.MainActivity launchParam=MultiScreenLaunchParams { mDisplayId=0 mFlags=0 } (has extras) }
14:36:32.11 Try launch USB connection
14:36:32.12 Socket closed
14:36:32.43 Try launch USB connection
14:36:32.43 Socket closed
14:36:32.72 Try launch USB connection
14:36:32.73 Socket closed
14:36:33.02 Try launch USB connection
14:36:33.02 Socket closed
14:36:33.31 Try launch USB connection
14:36:33.32 Socket closed
14:36:33.63 Try launch USB connection
14:36:33.63 Socket closed
14:36:33.92 Try launch USB connection
14:36:33.93 Socket closed
14:36:34.22 Try launch USB connection
14:36:34.22 Socket closed
14:36:34.51 Try launch USB connection
14:36:34.52 Socket closed
14:36:34.83 Try launch USB connection
14:36:34.83 Socket closed
14:36:35.12 Try launch USB connection
14:36:35.12 Socket closed
14:36:35.42 Try launch USB connection
14:36:35.42 Socket closed
14:36:35.72 Try launch USB connection
14:36:35.72 Socket closed
14:36:36.01 Try launch USB connection
14:36:36.02 Socket closed
14:36:36.33 Try launch USB connection
14:36:36.33 Socket closed
14:36:36.62 Try launch USB connection
14:36:36.62 Socket closed
14:36:36.92 Try launch USB connection
14:36:36.92 Socket closed
14:36:37.21 Try launch USB connection
14:36:37.22 Socket closed
14:36:37.53 Try launch USB connection
14:36:37.53 Socket closed
14:36:37.82 Try launch USB connection
14:36:37.83 Socket closed
14:36:38.12 Connect to Android failed!
14:36:38.12 bOpened=False
14:36:38.12 Refresh ComDescriptions...
14:36:38.13 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\9&DB7353A&1&0001
14:36:38.13 ErrMsg: Verbindung zum Handy konnte nicht aufgebaut werden!
14:37:10.60 Device Tracker Message: 0000
14:37:11.34 DBT_DEVICEREMOVECOMPLETE: COM3
14:37:11.86 Device Tracker Message: 001942008d10a8ba34a3 offline

14:37:11.88 Device Tracker Message: 001842008d10a8ba34a3 device

14:37:20.12 Connect via USB
14:37:20.12 RunADBCommand: start-server
14:37:20.19 ADB CommandResponse:
14:37:20.19 RunADBCommand: devices
14:37:20.24 ADB CommandResponse: List of devices attached
42008d10a8ba34a3 device
14:37:20.24 RunADBCommand: -s "42008d10a8ba34a3" forward tcp:5210 tcp:5210
14:37:20.28 ADB CommandResponse:
14:37:20.28 Try connecting to 127.0.0.1...
14:37:20.28 Socket closed
14:37:20.28 RunADBCommand: -s "42008d10a8ba34a3" shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
14:37:21.53 ADB CommandResponse: Starting: Intent { cmp=com.fjsoft.myphoneexplorer.client/.MainActivity launchParam=MultiScreenLaunchParams { mDisplayId=0 mFlags=0 } (has extras) }
14:37:21.69 Try launch USB connection
14:37:21.69 Socket closed
14:37:22.00 Try launch USB connection
14:37:22.01 Socket closed
14:37:22.30 Try launch USB connection
14:37:22.30 Socket closed
14:37:22.59 Try launch USB connection
14:37:22.60 Socket closed
14:37:22.89 Try launch USB connection
14:37:22.90 Socket closed
14:37:23.20 Try launch USB connection
14:37:23.21 Socket closed
14:37:23.50 Try launch USB connection
14:37:23.50 Socket closed
14:37:23.80 Try launch USB connection
14:37:23.80 Socket closed
14:37:24.09 Try launch USB connection
14:37:24.10 Socket closed
14:37:24.40 Try launch USB connection
14:37:24.41 Socket closed
14:37:24.70 Try launch USB connection
14:37:24.71 Socket closed
14:37:25.00 Try launch USB connection
14:37:25.00 Socket closed
14:37:25.29 Try launch USB connection
14:37:25.30 Socket closed
14:37:25.59 Try launch USB connection
14:37:25.59 Socket closed
14:37:25.90 Try launch USB connection
14:37:25.91 Socket closed
14:37:26.20 Try launch USB connection
14:37:26.20 Socket closed
14:37:26.50 Try launch USB connection
14:37:26.50 Socket closed
14:37:26.79 Try launch USB connection
14:37:26.80 Socket closed
14:37:27.10 Try launch USB connection
14:37:27.11 Socket closed
14:37:27.40 Try launch USB connection
14:37:27.40 Socket closed
14:37:27.70 Connect to Android failed!
14:37:27.70 bOpened=False
14:37:27.70 Refresh ComDescriptions...
14:37:27.70 ErrMsg: Verbindung zum Handy konnte nicht aufgebaut werden!
14:37:46.44 Device Tracker Message: 0000
14:38:03.79 Connect via USB
14:38:03.80 RunADBCommand: start-server
14:38:03.92 ADB CommandResponse:
14:38:03.92 RunADBCommand: devices
14:38:04.01 ADB CommandResponse: List of devices attached
14:38:04.01 Connect to Android failed!
14:38:04.01 bOpened=False
14:38:04.01 Kein Gerät über USB angeschlossen
14:38:04.01 Refresh ComDescriptions...
14:38:04.01 ErrMsg: Verbindung zum Handy konnte nicht aufgebaut werden:
Kein Gerät über USB angeschlossen
14:38:21.32 Connect via USB
14:38:21.32 RunADBCommand: start-server
14:38:21.37 ADB CommandResponse:
14:38:21.37 RunADBCommand: devices
14:38:21.41 ADB CommandResponse: List of devices attached
14:38:21.41 Connect to Android failed!
14:38:21.42 bOpened=False
14:38:21.42 Kein Gerät über USB angeschlossen
14:38:21.42 Refresh ComDescriptions...
14:38:21.42 ErrMsg: Verbindung zum Handy konnte nicht aufgebaut werden:
Kein Gerät über USB angeschlossen
14:38:29.91 Connect via USB
14:38:29.91 RunADBCommand: start-server
14:38:29.98 ADB CommandResponse:
14:38:29.98 RunADBCommand: devices
14:38:30.03 ADB CommandResponse: List of devices attached
14:38:30.03 Connect to Android failed!
14:38:30.03 bOpened=False
14:38:30.04 Kein Gerät über USB angeschlossen
14:38:30.04 Refresh ComDescriptions...
14:38:30.04 ErrMsg: Verbindung zum Handy konnte nicht aufgebaut werden:
Kein Gerät über USB angeschlossen
14:38:39.98 Connect via USB
14:38:39.98 RunADBCommand: start-server
14:38:40.04 ADB CommandResponse:
14:38:40.04 RunADBCommand: devices
14:38:40.11 ADB CommandResponse: List of devices attached
14:38:40.11 Connect to Android failed!
14:38:40.11 bOpened=False
14:38:40.11 Kein Gerät über USB angeschlossen
14:38:40.11 Refresh ComDescriptions...
14:38:40.11 ErrMsg: Verbindung zum Handy konnte nicht aufgebaut werden:
Kein Gerät über USB angeschlossen
14:38:47.98 Device Tracker Message: 001942008d10a8ba34a3 offline

14:38:48.01 Device Tracker Message: 001842008d10a8ba34a3 device

14:38:48.95 Connect via USB
14:38:48.96 RunADBCommand: start-server
14:38:49.02 ADB CommandResponse:
14:38:49.02 RunADBCommand: devices
14:38:49.08 ADB CommandResponse: List of devices attached
42008d10a8ba34a3 device
14:38:49.08 RunADBCommand: -s "42008d10a8ba34a3" forward tcp:5210 tcp:5210
14:38:49.14 ADB CommandResponse:
14:38:49.14 Try connecting to 127.0.0.1...
14:38:49.14 Socket closed
14:38:49.14 RunADBCommand: -s "42008d10a8ba34a3" shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
14:38:50.39 ADB CommandResponse: Starting: Intent { cmp=com.fjsoft.myphoneexplorer.client/.MainActivity launchParam=MultiScreenLaunchParams { mDisplayId=0 mFlags=0 } (has extras) }
14:38:50.53 Try launch USB connection
14:38:50.54 Socket closed
14:38:50.84 Try launch USB connection
14:38:50.85 Socket closed
14:38:51.14 Try launch USB connection
14:38:51.14 Socket closed
14:38:51.44 Try launch USB connection
14:38:51.44 Socket closed
14:38:51.73 Try launch USB connection
14:38:51.74 Socket closed
14:38:52.05 Try launch USB connection
14:38:52.05 Socket closed
14:38:52.34 Try launch USB connection
14:38:52.35 Socket closed
14:38:52.64 Try launch USB connection
14:38:52.64 Socket closed
14:38:52.94 Try launch USB connection
14:38:52.94 Socket closed
14:38:53.25 Try launch USB connection
14:38:53.25 Socket closed
14:38:53.54 Try launch USB connection
14:38:53.55 Socket closed
14:38:53.84 Try launch USB connection
14:38:53.84 Socket closed
14:38:54.14 Try launch USB connection
14:38:54.14 Socket closed
14:38:54.43 Try launch USB connection
14:38:54.44 Socket closed
14:38:54.74 Try launch USB connection
14:38:54.75 Socket closed
14:38:55.04 Try launch USB connection
14:38:55.06 Socket closed
14:38:55.34 Try launch USB connection
14:38:55.34 Socket closed
14:38:55.63 Try launch USB connection
14:38:55.64 Socket closed
14:38:55.95 Try launch USB connection
14:38:55.98 Socket closed
14:38:56.24 Try launch USB connection
14:38:56.25 Socket closed
14:38:56.54 Connect to Android failed!
14:38:56.54 bOpened=False
14:38:56.54 Refresh ComDescriptions...
14:38:56.54 ErrMsg: Verbindung zum Handy konnte nicht aufgebaut werden!
14:39:18.19 Device Tracker Message: 0000
14:39:18.76 DBT_DEVICEARRIVAL: COM3
14:39:19.08 Device Tracker Message: 001942008d10a8ba34a3 offline

14:39:19.12 Device Tracker Message: 001842008d10a8ba34a3 device

14:39:22.54 Connect via USB
14:39:22.54 RunADBCommand: start-server
14:39:22.57 ADB CommandResponse:
14:39:22.57 RunADBCommand: devices
14:39:22.62 ADB CommandResponse: List of devices attached
42008d10a8ba34a3 device
14:39:22.62 RunADBCommand: -s "42008d10a8ba34a3" forward tcp:5210 tcp:5210
14:39:22.65 ADB CommandResponse:
14:39:22.65 Try connecting to 127.0.0.1...
14:39:22.66 Socket closed
14:39:22.66 RunADBCommand: -s "42008d10a8ba34a3" shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
14:39:22.77 Refresh ComDescriptions...
14:39:22.77 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\9&DB7353A&1&0001
14:39:23.89 ADB CommandResponse: Starting: Intent { cmp=com.fjsoft.myphoneexplorer.client/.MainActivity launchParam=MultiScreenLaunchParams { mDisplayId=0 mFlags=0 } (has extras) }
14:39:24.04 Try launch USB connection
14:39:24.05 Socket closed
14:39:24.35 Try launch USB connection
14:39:24.36 Socket closed
14:39:24.65 Try launch USB connection
14:39:24.65 Socket closed
14:39:24.95 Try launch USB connection
14:39:24.95 Socket closed
14:39:25.24 Try launch USB connection
14:39:25.25 Socket closed
14:39:25.55 Try launch USB connection
14:39:25.56 Socket closed
14:39:25.85 Try launch USB connection
14:39:25.86 Socket closed
14:39:26.15 Try launch USB connection
14:39:26.15 Socket closed
14:39:26.44 Try launch USB connection
14:39:26.45 Socket closed
14:39:26.76 Try launch USB connection
14:39:26.76 Socket closed
14:39:27.05 Try launch USB connection
14:39:27.06 Socket closed
14:39:27.35 Try launch USB connection
14:39:27.35 Socket closed
14:39:27.65 Try launch USB connection
14:39:27.65 Socket closed
14:39:27.94 Try launch USB connection
14:39:27.94 Socket closed
14:39:28.25 Try launch USB connection
14:39:28.26 Socket closed
14:39:28.55 Try launch USB connection
14:39:28.55 Socket closed
14:39:28.85 Try launch USB connection
14:39:28.85 Socket closed
14:39:29.14 Try launch USB connection
14:39:29.15 Socket closed
14:39:29.45 Try launch USB connection
14:39:29.46 Socket closed
14:39:29.75 Try launch USB connection
14:39:29.76 Socket closed
14:39:30.05 Connect to Android failed!
14:39:30.05 bOpened=False
14:39:30.05 Refresh ComDescriptions...
14:39:30.05 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\9&DB7353A&1&0001
14:39:30.05 ErrMsg: Verbindung zum Handy konnte nicht aufgebaut werden!
14:42:49.22 Refresh ComDescriptions...
14:42:49.22 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\9&DB7353A&1&0001
14:42:53.36 OK pressed in settingswindow
14:42:53.38 Set first swap of settings
14:42:53.38 Apply new holidays
14:42:53.38 Holidays applied
14:42:53.38 Second swap of settings set
14:42:53.39 Everything is done
14:42:55.41 Connect via USB
14:42:55.41 RunADBCommand: start-server
14:42:55.47 ADB CommandResponse:
14:42:55.47 RunADBCommand: devices
14:42:55.51 ADB CommandResponse: List of devices attached
42008d10a8ba34a3 device
14:42:55.51 RunADBCommand: -s "42008d10a8ba34a3" forward tcp:5210 tcp:5210
14:42:55.55 ADB CommandResponse:
14:42:55.55 Try connecting to 127.0.0.1...
14:42:55.55 Socket closed
14:42:55.55 RunADBCommand: -s "42008d10a8ba34a3" shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
14:42:56.81 ADB CommandResponse: Starting: Intent { cmp=com.fjsoft.myphoneexplorer.client/.MainActivity launchParam=MultiScreenLaunchParams { mDisplayId=0 mFlags=0 } (has extras) }
14:42:56.97 Try launch USB connection
14:42:56.97 Socket closed
14:42:57.28 Try launch USB connection
14:42:57.28 Socket closed
14:42:57.58 Try launch USB connection
14:42:57.58 Socket closed
14:42:57.87 Try launch USB connection
14:42:57.88 Socket closed
14:42:58.17 Try launch USB connection
14:42:58.17 Socket closed
14:42:58.48 Try launch USB connection
14:42:58.49 Socket closed
14:42:58.78 Try launch USB connection
14:42:58.78 Socket closed
14:42:59.07 Try launch USB connection
14:42:59.08 Socket closed
14:42:59.37 Try launch USB connection
14:42:59.37 Socket closed
14:42:59.68 Try launch USB connection
14:42:59.69 Socket closed
14:42:59.98 Try launch USB connection
14:42:59.98 Socket closed
14:43:00.27 Try launch USB connection
14:43:00.28 Socket closed
14:43:00.57 Try launch USB connection
14:43:00.58 Socket closed
14:43:00.87 Try launch USB connection
14:43:00.87 Socket closed
14:43:01.18 Try launch USB connection
14:43:01.18 Socket closed
14:43:01.48 Try launch USB connection
14:43:01.48 Socket closed
14:43:01.77 Try launch USB connection
14:43:01.78 Socket closed
14:43:02.07 Try launch USB connection
14:43:02.07 Socket closed
14:43:02.38 Try launch USB connection
14:43:02.38 Socket closed
14:43:02.68 Try launch USB connection
14:43:02.68 Socket closed
14:43:02.97 Connect via FixedIP:
14:43:02.97 Connect via WiFi
14:43:02.97 Broadcaster started
14:43:02.98 Start UPnP Discovery
14:43:02.98 Sending broadcast
14:43:03.11 UPnP Device: MediaAccess TG588v (1509CZE27)
14:43:03.39 UPnP Device: MediaAccess TG588v (1509CZE27)
14:43:03.49 Sending broadcast
14:43:03.53 UPnP Device: MediaAccess TG588v (1509CZE27)
14:43:04.00 Sending broadcast
14:43:05.62 UPnP Device: EICH-LT: Eich:
14:43:06.50 UPnP Device: A1 WLAN Box
14:43:07.98 Connect via Bluetooth
14:43:07.98 Connect Bluetooth...
14:43:08.11 Found Microsoft Bluetooth Stack
14:43:08.16 Refresh ComDescriptions...
14:43:08.16 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\9&DB7353A&1&0001
14:43:39.06 Connect to Android failed!
14:43:39.07 bOpened=False
14:43:39.07 WLAN: Die IP-Adresse des Handys konnte nicht ermittelt werden
Bluetooth:
14:43:39.07 Refresh ComDescriptions...
14:43:39.08 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\9&DB7353A&1&0001
14:43:39.08 ErrMsg: Verbindung zum Handy konnte nicht aufgebaut werden:
WLAN: Die IP-Adresse des Handys konnte nicht ermittelt werden
Bluetooth:
14:43:44.32 Refresh ComDescriptions...
14:43:44.33 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\9&DB7353A&1&0001
14:43:49.12 OK pressed in settingswindow
14:43:49.13 Set first swap of settings
14:43:49.13 Apply new holidays
14:43:49.13 Holidays applied
14:43:49.13 Second swap of settings set
14:43:49.14 Everything is done
14:43:51.40 Connect via USB
14:43:51.40 Closing Broadcaster
14:43:51.41 RunADBCommand: start-server
14:43:51.45 ADB CommandResponse:
14:43:51.45 RunADBCommand: devices
14:43:51.48 ADB CommandResponse: List of devices attached
42008d10a8ba34a3 device
14:43:51.48 RunADBCommand: -s "42008d10a8ba34a3" forward tcp:5210 tcp:5210
14:43:51.54 ADB CommandResponse:
14:43:51.54 Try connecting to 127.0.0.1...
14:43:51.55 Socket closed
14:43:51.55 RunADBCommand: -s "42008d10a8ba34a3" shell am start -n com.fjsoft.myphoneexplorer.client/.MainActivity --ez adb true
14:43:52.81 ADB CommandResponse: Starting: Intent { cmp=com.fjsoft.myphoneexplorer.client/.MainActivity launchParam=MultiScreenLaunchParams { mDisplayId=0 mFlags=0 } (has extras) }
14:43:52.96 Try launch USB connection
14:43:52.96 Socket closed
14:43:53.27 Try launch USB connection
14:43:53.27 Socket closed
14:43:53.56 Try launch USB connection
14:43:53.57 Socket closed
14:43:53.86 Try launch USB connection
14:43:53.87 Socket closed
14:43:54.16 Try launch USB connection
14:43:54.16 Socket closed
14:43:54.47 Try launch USB connection
14:43:54.47 Socket closed
14:43:54.76 Try launch USB connection
14:43:54.77 Socket closed
14:43:55.06 Try launch USB connection
14:43:55.07 Socket closed
14:43:55.36 Try launch USB connection
14:43:55.36 Socket closed
14:43:55.67 Try launch USB connection
14:43:55.67 Socket closed
14:43:55.97 Try launch USB connection
14:43:55.97 Socket closed
14:43:56.26 Try launch USB connection
14:43:56.27 Socket closed
14:43:56.56 Try launch USB connection
14:43:56.56 Socket closed
14:43:56.86 Try launch USB connection
14:43:56.86 Socket closed
14:43:57.17 Try launch USB connection
14:43:57.17 Socket closed
14:43:57.46 Try launch USB connection
14:43:57.47 Socket closed
14:43:57.76 Try launch USB connection
14:43:57.77 Socket closed
14:43:58.06 Try launch USB connection
14:43:58.06 Socket closed
14:43:58.37 Try launch USB connection
14:43:58.37 Socket closed
14:43:58.66 Try launch USB connection
14:43:58.67 Socket closed
14:43:58.96 Connect to Android failed!
14:43:58.96 bOpened=False
14:43:58.96 Refresh ComDescriptions...
14:43:58.97 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\9&DB7353A&1&0001
14:43:58.97 ErrMsg: Verbindung zum Handy konnte nicht aufgebaut werden!
14:44:09.03 Refresh ComDescriptions...
14:44:09.03 MODEM: COM3 Enumerator=USB Displayed=SAMSUNG Mobile USB Modem FriendlyName=SAMSUNG Mobile USB Modem InstanceID=USB\VID_04E8&PID_6860&MODEM\9&DB7353A&1&0001
14:44:10.76 Device driver info:
14:44:10.76 Devices with ADB Interface: SAMSUNG Android ADB Interface
14:44:10.80 ADB Devices: SAMSUNG Android ADB Interface
14:44:10.80 Portable devices: SM-G390F
14:44:10.80 Unknown devices:
icke1954
Moderator
Beiträge: 18155
Registriert: Sa 19. Apr 2014, 10:35

Beitrag von icke1954 »

Hallo und willkommen in unserem Forum!
Ich weiß momentan auch nicht so recht, weshalb MPE keinen Zugriff über USB bekommt?
Hast Du mal versucht über Wlan eine Verbindung zu realisieren?

- Handy USB-Mode MTP statt Nur Laden bitte aktivieren
- In jedem Fall solltest Du die Rechte des MPE-Clients überprüfen, e.v.t. wurden die eingeschränkt.
- Handy neu booten

Sonst kann ich Dir leider nicht helfen, das muß sich FJ ansehen.

  1. MPE => F2 => Verbindung => Logdatei mitschreiben muß aktiviert sein
  2. Beende MyPhoneExplorer am PC
  3. Handy => MPE-Client => Einstellungen => Client automatisch starten deaktivieren
  4. Beende den MyPhoneExplorer-Client am Handy
  5. Stelle die Verbindung zum Handy via USB-Kabelher
  6. Starte MyPhoneExplorer am PC im Debugmodus
    (Windows) Start => Ausführen => myphoneexplorer debug => OK
  7. Falls die USB-Verbindung nicht automatisch hergestellt wird, drücke <F1> für Verbinden
  8. Reproduziere die Fehlermeldung
  9. Öffne das Datenverzeichnis von myPhoneExplorer am PC
    (Windows) Start => Ausführen => %appdata%\MyPhoneExplorer => OK
  10. Dort befinden sich u.a. zwei Dateien: Debug.txt und AndroidDebug.txt

Sende FJ eine Mail (fj.wechselberger@gmx.at) mit einem Hinweis auf diesen Thread und diesen beiden Dateien

Gruß icke
Zuletzt geändert von icke1954 am Mi 9. Aug 2017, 09:40, insgesamt 1-mal geändert.
halbeshirn
Beiträge: 11
Registriert: Mi 6. Mai 2015, 21:29

Beitrag von halbeshirn »

also bei mir war das problem, dass ich vergessen hatte, den mpe-client auf dem xcover4 zu installieren. seitdem ich den gestern installiert habe, funzt alles prächtig mit der desktop-anbindung und dem nutzen des mpe auf win vista system...
Antworten