Connection problems

Anmeldedatum: 27.11.2010 Beiträge: 9

I use two android phones - OnePlus3 and HTC One M - both of which are set as separate users on MFE, which worked without problems connecting through USB.

My old PC, ThinkPad X1 on Windows 10 64bit, has been recently replaced with ThinkPad X1-Yoga also Windows 10 64bit.

While replacing the PC I had to hard reset my OnePlus3.

I installed MFE on my new PC along with all drivers. HTC One M - works fine on my new PC - which seems to indicate that MFE and drivers are set up properly on this PC. Unfortunately, OnePlus3 (the one I had to reset) cannot connect to MFE through either USB or WiFi, although it connects nicely through Bluetooth.

Both phones still connect to the old PC's MFE without any problems - which seems to indicate that there are no installation/settings problems with phones as well.

Here is the log of my attempts to connect OnePlus3 through USB:

Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.7
Datum: 24-Oct-16

23:02:54.27 Windows Version=10.0
23:02:54.27 Setting Port: 999
23:02:54.27 Setting Baud: 115200
23:02:54.27 Avaiable Ports: COM0=;
23:02:54.27 Main Load frmSplash
23:02:54.27 Load frmSplash...
23:02:54.27 Show splash...
23:02:54.28 frmSplash geladen
23:02:54.86 Hauptfenster wird geladen
23:02:54.97 Sidebar fertig geladen
23:02:55.05 UC SMS wird geladen
23:02:55.08 UC Phonebook wird geladen
23:02:55.11 UC Phonebook fertig geladen
23:02:55.11 UC Calls wird geladen
23:02:55.14 UC Organizer wird geladen
23:02:55.22 Organizer initiated
23:02:55.24 Startpage=3
23:02:55.25 UC Filebrowser wird geladen
23:02:55.32 UC Filebrowser fertig geladen
23:02:55.32 UC AppBrowser wird geladen
23:02:55.33 UC Notes wird geladen
23:02:55.35 UC Calls wird geladen
23:02:55.38 Setting Lastuser:
23:02:55.39 Lade Userdatenbank:
23:02:55.42 Kontakte geladen
23:02:55.42 ParseDialedCalls needed 0ms
23:02:55.47 Anrufe geladen
23:02:55.47 Organizer LoadUser DefaultTimeColWidth=118
23:02:55.47 Organizer geladen
23:02:55.47 Notizen geladen
23:02:55.47 SMS geladen
23:02:55.80 Hauptfenster fertig geladen
23:03:06.03 RunADBCommand: start-server
23:03:10.17 ADB CommandResponse: * daemon not running. starting it now on port 5037 *
* daemon started successfully *
23:03:10.17 RunADBCommand: devices
23:03:10.23 ADB CommandResponse: List of devices attached
23:03:10.23 Run DeviceTracker
23:03:10.25 Init Tracker
23:03:10.28 Device Tracker Message: OKAY0000
23:03:10.28 Connect to Android failed!
23:03:10.28 bOpened=False
23:03:10.28 No device attached to USB
23:03:10.28 Refresh ComDescriptions...
23:03:10.28 ErrMsg: Connection to phone could not be established:
No device attached to USB
23:03:44.72 RunADBCommand: start-server
23:03:44.77 ADB CommandResponse:
23:03:44.77 RunADBCommand: devices
23:03:44.82 ADB CommandResponse: List of devices attached
23:03:44.82 Connect to Android failed!
23:03:44.82 bOpened=False
23:03:44.82 No device attached to USB
23:03:44.82 Refresh ComDescriptions...
23:03:44.82 ErrMsg: Connection to phone could not be established:
No device attached to USB
23:16:02.47 RunADBCommand: start-server
23:16:02.52 ADB CommandResponse:
23:16:02.52 RunADBCommand: devices
23:16:02.58 ADB CommandResponse: List of devices attached
23:16:02.58 Connect to Android failed!
23:16:02.58 bOpened=False
23:16:02.58 No device attached to USB
23:16:02.58 Refresh ComDescriptions...
23:16:02.58 ErrMsg: Connection to phone could not be established:
No device attached to USB
23:22:06.49 Refresh ComDescriptions...
23:22:11.78 Device driver info:
23:22:11.78 Devices with ADB Interface: ADB Device
23:22:11.78 ADB Devices:
23:22:11.78 Portable devices: ONEPLUS A3003
23:22:11.78 Unknown devices: <unknown device>

Informationen zum Datenschutz auf dieser Website