FJ Software

I have been using MPE successfully for several years with a Samsung Charge connected over USB. I recently purchased a Samsung Galaxy 4s mini and can't get it to connect to MPE save my life. The computer sees that the phone is connected, but I get an error from MPE - "connection to phone could not be established: no device connected to USB". I've tried different USB ports and cables, etc, but no luck. I seem to see that others can connect. What am I doing wrong?

Forgot to mention USB debugging is activated. Here is the log file:

Logdatei MyPhoneExplorer
************************
Programmversion: 1.8.5
Datum: 3/6/2014

13:43:46.53 Setting Port: 999
13:43:46.53 Setting Baud: 115200
13:43:46.53 Avaiable Ports: COM1=\Device\Serial0;
13:43:46.53 Main Load frmSplash
13:43:46.56 Load frmSplash...
13:43:46.56 Show splash...
13:43:46.56 frmSplash geladen
13:43:47.18 Hauptfenster wird geladen
13:43:47.36 Sidebar fertig geladen
13:43:47.55 UC SMS wird geladen
13:43:47.58 UC Phonebook wird geladen
13:43:47.61 UC Phonebook fertig geladen
13:43:47.61 UC Calls wird geladen
13:43:47.66 UC Organizer wird geladen
13:43:47.74 Organizer initiated
13:43:47.77 Startpage=1
13:43:47.79 UC Filebrowser wird geladen
13:43:47.87 UC Filebrowser fertig geladen
13:43:47.87 UC AppBrowser wird geladen
13:43:47.87 UC Notes wird geladen
13:43:47.88 UC Calls wird geladen
13:43:47.93 Setting Lastuser:
13:43:47.96 Lade Userdatenbank:
13:43:47.99 Kontakte geladen
13:43:47.99 ParseDialedCalls needed 0ms
13:43:48.04 Anrufe geladen
13:43:48.04 Organizer LoadUser DefaultTimeColWidth=112
13:43:48.04 Organizer geladen
13:43:48.04 Notizen geladen
13:43:48.04 SMS geladen
13:43:48.36 Hauptfenster fertig geladen
13:43:48.62 Downloader: RC=6 BytesMax=5 URL=http://www.fjsoft.at/myphoneexplorer/version.txt
13:43:54.71 RunADBCommand: start-server
13:43:59.00 ADB CommandResponse: * daemon not running. starting it now on port 5037 *
* daemon started successfully *
13:43:59.00 RunADBCommand: devices
13:43:59.09 ADB CommandResponse: List of devices attached
13:43:59.09 Run DeviceTracker
13:43:59.11 Init Tracker
13:43:59.14 Device Tracker Message: OKAY0000
13:43:59.14 Connect to Android failed!
13:43:59.14 bOpened=False
13:43:59.14 No device attached to USB
13:43:59.14 Refresh ComDescriptions...
13:43:59.14 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
13:43:59.14 ErrMsg: Connection to phone could not be established:
No device attached to USB
13:44:07.87 Refresh ComDescriptions...
13:44:07.87 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
13:44:08.35 StickyNotesPath=C:\Windows\Sysnative\StikyNot.exe FileExists=True
13:44:08.35 StickyNotesTitle=Sticky Notes
13:45:33.41 OK pressed in settingswindow
13:45:33.43 Set first swap of settings
13:45:33.43 Apply new holidays
13:45:33.43 Holidays applied
13:45:33.44 Second swap of settings set
13:45:33.44 Everything is done
13:45:36.61 Try connecting to 10.70.127.114 (fixed IP)...
13:45:38.73 Connect to Android failed!
13:45:38.73 bOpened=False
13:45:38.73 Connection to 10.70.127.114 failed!
13:45:38.73 Refresh ComDescriptions...
13:45:38.73 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
13:45:38.73 ErrMsg: Connection to phone could not be established:
Connection to 10.70.127.114 failed!
13:45:47.94 Try connecting to 10.70.127.114 (fixed IP)...
13:45:50.06 Connect to Android failed!
13:45:50.06 bOpened=False
13:45:50.06 Connection to 10.70.127.114 failed!
13:45:50.06 Refresh ComDescriptions...
13:45:50.06 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
13:45:50.06 ErrMsg: Connection to phone could not be established:
Connection to 10.70.127.114 failed!
13:46:00.48 Refresh ComDescriptions...
13:46:00.48 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
13:46:17.56 OK pressed in settingswindow
13:46:17.58 Set first swap of settings
13:46:17.58 Apply new holidays
13:46:17.58 Holidays applied
13:46:17.60 Second swap of settings set
13:46:17.60 Everything is done
13:46:52.94 Broadcaster started
13:46:52.94 Sending broadcast
13:46:53.46 Sending broadcast
13:46:53.98 Sending broadcast
13:46:54.96 Connect to Android failed!
13:46:54.96 bOpened=False
13:46:54.96 Failed to obtain the IP-address of the phone
13:46:54.96 Refresh ComDescriptions...
13:46:54.96 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
13:46:54.96 ErrMsg: Connection to phone could not be established:
Failed to obtain the IP-address of the phone
13:47:02.21 Refresh ComDescriptions...
13:47:02.21 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
13:47:44.99 OK pressed in settingswindow
13:47:45.00 Set first swap of settings
13:47:45.00 Apply new holidays
13:47:45.00 Holidays applied
13:47:45.02 Second swap of settings set
13:47:45.02 Everything is done
13:48:20.30 Closing Broadcaster
13:48:20.30 RunADBCommand: start-server
13:48:20.43 ADB CommandResponse:
13:48:20.43 RunADBCommand: devices
13:48:20.51 ADB CommandResponse: List of devices attached
13:48:20.51 Connect to Android failed!
13:48:20.51 bOpened=False
13:48:20.51 No device attached to USB
13:48:20.51 Refresh ComDescriptions...
13:48:20.51 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
13:48:20.51 ErrMsg: Connection to phone could not be established:
No device attached to USB
13:48:26.90 RunADBCommand: start-server
13:48:26.97 ADB CommandResponse:
13:48:26.97 RunADBCommand: devices
13:48:27.04 ADB CommandResponse: List of devices attached
13:48:27.04 Connect to Android failed!
13:48:27.04 bOpened=False
13:48:27.04 No device attached to USB
13:48:27.04 Refresh ComDescriptions...
13:48:27.04 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
13:48:27.04 ErrMsg: Connection to phone could not be established:
No device attached to USB
13:48:30.80 Refresh ComDescriptions...
13:48:30.80 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1

see my response in http://www.fjsoft.at/forum/viewtopic.php?t=21894

I don't see why the S4 mini would be much different from the normal S4.

Install the ADB Drivers and follow the tips in the FAQ.