Connect to Android 4.4.2 (KitKat)

Anmeldedatum: 16.09.2014 Beiträge: 3

I have just bought Jiayu G4S and upgraded it to Android 4.4.2
Now when try to connect to the smartphone using MyPhoneExplorer 1.8.6 via USB I see just message "Connection to phone could not be established: No device attached to USB"
USB DebugMode enabled.
Not sure is it related Android version or vendor.
My PC OS is Win7 64-bit
So, how to fix the issue?

Here is debug.txt (GIGABYTE GSmart G1345- is my previous phone)

Code:

14:07:45.38 Setting Port: 999
14:07:45.38 Setting Baud: 115200
14:07:45.38 Avaiable Ports: COM1=\Device\Serial1; COM3=\Device\Serial0;
14:07:45.38 Main Load frmSplash
14:07:45.39 Load frmSplash...
14:07:45.40 Show splash...
14:07:45.40 frmSplash geladen
14:07:45.88 Hauptfenster wird geladen
14:07:45.99 Sidebar fertig geladen
14:07:46.13 UC SMS wird geladen
14:07:46.16 UC Phonebook wird geladen
14:07:46.18 UC Phonebook fertig geladen
14:07:46.18 UC Calls wird geladen
14:07:46.21 UC Organizer wird geladen
14:07:46.26 Organizer initiated
14:07:46.28 Startpage=1
14:07:46.29 UC Filebrowser wird geladen
14:07:46.33 UC Filebrowser fertig geladen
14:07:46.33 UC AppBrowser wird geladen
14:07:46.34 UC Notes wird geladen
14:07:46.34 UC Calls wird geladen
14:07:46.37 Setting Lastuser: GIGABYTE GSmart G1345 [356049019546586]
14:07:46.38 Lade Userdatenbank: GIGABYTE GSmart G1345 [356049019546586]
14:07:46.51 LoadDatafile: pb_metadata.xml(2305 Bytes)
14:07:46.51 LoadDatafile: Phonebook.dat(52469 Bytes)
14:07:46.81 Kontakte geladen
14:07:46.82 LoadDatafile: Calls.dat(19820 Bytes)
14:07:46.85 ParseDialedCalls needed 0ms
14:07:47.01 Anrufe geladen
14:07:47.01 Organizer LoadUser DefaultTimeColWidth=118
14:07:47.02 LoadDatafile: Organizer.dat(45 Bytes)
14:07:47.03 LoadDatafile: cal_metadata.xml(359 Bytes)
14:07:47.03 Organizer geladen
14:07:47.03 Notizen geladen
14:07:47.03 Load SMS Data...
14:07:47.03 LoadDatafile: SMS.dat(16098 Bytes)
14:07:47.03 SMS - Datenbank wird geladen...
14:07:47.05 SMS Laden - Readfile: 0 Split: 0 Parse: 15 HandleMultiSMS: 0 Nachrichten: 67
14:07:47.07 RefreshList (Archive): Addrows=0 Sort=0 MenuUpdate=0 Redraw=0
14:07:47.10 SMS Data Loaded...
14:07:47.10 SMS geladen
14:07:47.36 Hauptfenster fertig geladen
14:07:47.47 Init Android Connection for future connect via USB
14:07:47.47 RunADBCommand: start-server
14:07:48.35 RunADBCommand: start-server
14:07:48.93 ADB CommandResponse:
14:07:48.93 RunADBCommand: devices
14:07:49.03 ADB CommandResponse: List of devices attached
14:07:49.03 Run DeviceTracker
14:07:49.03 Init Tracker
14:07:49.04 Device Tracker Message: OKAY0000
14:07:49.04 Connect to Android failed!
14:07:49.04 bOpened=False
14:07:49.04 No device attached to USB
14:07:49.04 Refresh ComDescriptions...
14:07:49.04 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
14:07:49.04 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_1C3D&SUBSYS_1495103C&REV_04\3&11583659&0&B3
14:07:49.04 ErrMsg: Connection to phone could not be established:
No device attached to USB
14:07:51.66 ADB CommandResponse: * daemon not running. starting it now on port 5037 *
* daemon started successfully *
14:08:25.57 RunADBCommand: start-server
14:08:25.66 ADB CommandResponse:
14:08:25.66 RunADBCommand: devices
14:08:25.75 ADB CommandResponse: List of devices attached
14:08:25.75 Connect to Android failed!
14:08:25.75 bOpened=False
14:08:25.75 No device attached to USB
14:08:25.75 Refresh ComDescriptions...
14:08:25.75 PORT: COM1 Enumerator=ACPI Displayed=Communications Port InstanceID=ACPI\PNP0501\1
14:08:25.75 PORT: COM3 Enumerator=PCI Displayed=Intel(R) Active Management Technology - SOL InstanceID=PCI\VEN_8086&DEV_1C3D&SUBSYS_1495103C&REV_04\3&11583659&0&B3
14:08:25.75 ErrMsg: Connection to phone could not be established:
No device attached to USB

Verfasst am: Di Sep 16, 2014 15:20

Did you start the MPE client on the phone before trying to connect the phone with the MPE Software on the computer?

Anmeldedatum: 16.09.2014 Beiträge: 3

No, I didn't
As far as i Remember the MPE install it itself while first connection.
I'll try to install it on my phone and the connect once again.
But i'm 99% sure it won't help.
I just tried another smartphone with android 4.2.2 without pre-installed client and it works.
So as far as i understand pre-installed MPE client on the phone is not a "must be " requirement

Verfasst am: Mi Sep 17, 2014 00:33

And it would be unacceptable to just install the client on the phone?

Anmeldedatum: 16.09.2014 Beiträge: 3

Just downgraded Android to version 4.2.2 and it connected to MPE without any additional things.
So, i suppose the problem was with driver for Android 4.4.2.
By the way, does MPE support Android 4.4 ?

Verfasst am: Mi Sep 17, 2014 13:41

stepan_mk hat Folgendes geschrieben:

... By the way, does MPE support Android 4.4 ?

Yep. I tried a 4.4 ROM and MPE worked fine, though I'm back to 4.2.2 now (not because of any driver issues as I use wifi to connect). But look for Kitkat issues with sms apps and use of the sdcard though.

Verfasst am: Mi Sep 17, 2014 13:48

stepan_mk hat Folgendes geschrieben:

and it connected to MPE without any additional things

You´re not going to tell us, you´re able to connect the MPE on your computer without the MPE client on your phone.

Anmeldedatum: 12.08.2012 Beiträge: 6

Remember to set the USB in DEBUG mode and try also to connect when the phone is in MTP option, cause charge only seems to not work properly with MTK phones ... Exclamation

And install also the ADB drivers ( PDAnet ADB Auto-Driver For Windows * Jiayu G4s USB drivers ) !!

Bye.

Site Admin Anmeldedatum: 15.02.2006 Beiträge: 31478 Wohnort: Tirol

If you update your phone from 4.2.2 to 4.4 then you will have to update also the ADB-Drivers. This is the real issue for your problem. MyPhoneExplorer - or better the connection of MyPhoneExplorer - is the same as in earlier versions. MPE is fully compatible with Android KitKat

Informationen zum Datenschutz auf dieser Website