sapcmc
Contributor
Contributor

Samsung Galaxy S connection problems

Greetings,

I am trying to connect my Samsung Galaxy S in my Windows virtual machine but however VMachine doesn't even detect the USB and therefore Samsung Kies can not detect mobile.

Is anyone able to use the Samsung Galaxy S in a fusion virtual machine running Windows?

Vmware should get this issue sorted out.

All help appreciated.

0 Kudos
56 Replies
bersa
Contributor
Contributor

I have the same problem. Have tested Win7, Ubuntu 10.4 and SLES 11 SP1 under VMWare Fusion 3.1.1.

Under Linux (SLES I get:

hub 1-0:1.0: unable to enumerate USB device on port 1

/Per

0 Kudos
Neben
VMware Employee
VMware Employee

Could you try adding the following to the VM's vmx config file?

usb.quirks.device0 = "0x4e8:0x681d skip-reset" # Mass Storage

usb.quirks.device1 = "0x4e8:0x68a9 skip-reset" # Media

usb.quirks.device2 = "0x4e8:0x6877 skip-reset" # Kies

0 Kudos
sapcmc
Contributor
Contributor

Can you tell me how can I edit the vmx config file? I am not much of an expert.

Thanks

0 Kudos
Neben
VMware Employee
VMware Employee

Sure, here are the useful links that do it better than I could in a single post. 🐵

Message was edited by: Neben - Added another useful link

0 Kudos
bersa
Contributor
Contributor

Did not make any difference Smiley Sad

Nov 18 18:18:30.908: vmx| USB: Found device

Nov 18 18:18:34.807: vmx| USBGM: UsbgDeviceArbitratedNotificationCallback connecting:SAMSUNG_Android

Nov 18 18:18:34.808: vmx| USB: Adding autoconnect pattern in slot 0

Nov 18 18:18:34.811: vmx| USB: Device should already be connected

Nov 18 18:18:34.811: vmx| VMXVmdbLoadUsbDevices: New set of 5 USB devices

Nov 18 18:18:34.811: vmx| USB: Found device

Nov 18 18:18:34.811: vmx| USB: Found device

Nov 18 18:18:34.811: vmx| USB: Found device

Nov 18 18:18:34.811: vmx| USB: Found device

Nov 18 18:18:34.811: vmx| USB: Found device

Nov 18 18:18:35.315: vmx| USB: Removing autoconnect pattern from slot 0

Nov 18 18:18:35.316: vmx| USBGM: Device SAMSUNG_Android disconnected; clearing vmx autoconnect.

Nov 18 18:18:35.316: vmx| USB: Disconnecting device 0xfa1400004e8681c

Nov 18 18:18:35.317: vmx| VMXVmdbLoadUsbDevices: New set of 4 USB devices

Nov 18 18:18:35.318: vmx| USB: Found device

Nov 18 18:18:35.318: vmx| USB: Found device

Nov 18 18:18:35.318: vmx| USB: Found device

Nov 18 18:18:35.318: vmx| USB: Found device

0 Kudos
Neben
VMware Employee
VMware Employee

Could you attach the full vmware.log?

0 Kudos
bersa
Contributor
Contributor

Please find it attached.

/Per

0 Kudos
Neben
VMware Employee
VMware Employee

Looks like you need this one too:

usb.quirks.device0 = "0x4e8:0x681c skip-reset"

0 Kudos
bersa
Contributor
Contributor

Works like a charm !!!

Two follow up questions:

i) What is the 0x681c (as 0x681d is mass storage).

ii) I had to remove the previous usb.quirks.device0 line to let Fusion accept the config.

Are the other lines needed or should I make it usb.quirks.device3 ?

/Per

0 Kudos
Neben
VMware Employee
VMware Employee

i) I'm not sure. I don't have one of these in front of me to know what this PID does.

ii) Yep, making it usb.quirks.device3 will work, my bad for marking it "0". Each device quirk needs to have a different N in usb.quirks.deviceN. You'll probably want to keep the others if your device switches to one of the other PIDs or you may have to add additional ones if it uses an different PID (and doesn't work without the quirk). Let us know if there are other PIDs that also need the quirk for your device as we can make them automatic (you and others won't have to add them to the vmx) in a future Fusion release.

Here's the new set for copy/paste convenience.

usb.quirks.device0 = "0x4e8:0x681d skip-reset" # Mass Storage

usb.quirks.device1 = "0x4e8:0x68a9 skip-reset" # Media

usb.quirks.device2 = "0x4e8:0x6877 skip-reset" # Kies

usb.quirks.device3 = "0x4e8:0x681c skip-reset" # ?

0 Kudos
sapcmc
Contributor
Contributor

Problem is now solved, thanks for all the help . Would be great if VMware does include this on an update as I guess many VMware customers start to have Samsung Mobiles together with their Mac + VMware Fusion .

I can now sync my contacts without a problem and have access to all the updates.

Big thumbs up.

0 Kudos
sapcmc
Contributor
Contributor

I have a problem with this fix. Now with a Samsung Galaxy S I 9000 the Mass Storage Function works well but the Kies mode connection does not work.

Can someone give a hand?

Are you experiencing similar issues?

0 Kudos
sapcmc
Contributor
Contributor

Please find logs:

Feb 10 11:14:58.380: vmx| VMXVmdbLoadUsbDevices: New set of 4 USB devices
Feb 10 11:14:58.380: vmx| USB: Found device [name:Apple\ Built-in\ iSight vid:05ac pid:8501 path:13/15/4 speed:high family:vendor,video]
Feb 10 11:14:58.380: vmx| USB: Found device [name:Apple\ Bluetooth\ USB\ Host\ Controller vid:05ac pid:8205 path:10/1/1 speed:full family:other,wireless,bluetooth]
Feb 10 11:14:58.395: vmx| USB: Found device [name:Apple\ IR\ Receiver vid:05ac pid:8242 path:13/5/1 speed:low family:hid]
Feb 10 11:14:58.395: vmx| USB: Found device [name:SAMSUNG_Android vid:04e8 pid:681d path:13/15/1 speed:high family:storage]
Feb 10 11:15:05.573: vmx| USBGM: UsbgDeviceArbitratedNotificationCallback connecting:SAMSUNG_Android
Feb 10 11:15:05.591: vmx| USBG: Quirks for device 04e8:681d (user-defined,skip-reset)
Feb 10 11:15:05.591: vmx| USB: Adding autoconnect pattern [path:13/15/1 autoclean:1] in slot 0
Feb 10 11:15:05.701: vmx| USB: Device [name:SAMSUNG_Android vid:04e8 pid:681d path:13/15/1 speed:high family:storage] should already be connected
Feb 10 11:15:05.701: vmx| VMXVmdbLoadUsbDevices: New set of 4 USB devices
Feb 10 11:15:05.701: vmx| USB: Found device [name:Apple\ Built-in\ iSight vid:05ac pid:8501 path:13/15/4 speed:high family:vendor,video]
Feb 10 11:15:05.701: vmx| USB: Found device [name:Apple\ Bluetooth\ USB\ Host\ Controller vid:05ac pid:8205 path:10/1/1 speed:full family:other,wireless,bluetooth]
Feb 10 11:15:05.701: vmx| USB: Found device [name:Apple\ IR\ Receiver vid:05ac pid:8242 path:13/5/1 speed:low family:hid]
Feb 10 11:15:05.701: vmx| USB: Found device [name:SAMSUNG_Android vid:04e8 pid:681d path:13/15/1 speed:high family:storage]
Feb 10 11:15:07.358: vmx| USBIO: Detect usb-storage class
Feb 10 11:16:06.717: vcpu-0| USBGM: Disable port called. (status=0)
Feb 10 11:16:24.615: vmx| USB: Disconnecting device 0xfd1000004e8681d
Feb 10 11:16:24.616: vmx| VMXVmdbLoadUsbDevices: New set of 3 USB devices
Feb 10 11:16:24.616: vmx| USB: Found device [name:Apple\ Built-in\ iSight vid:05ac pid:8501 path:13/15/4 speed:high family:vendor,video]
Feb 10 11:16:24.616: vmx| USB: Found device [name:Apple\ Bluetooth\ USB\ Host\ Controller vid:05ac pid:8205 path:10/1/1 speed:full family:other,wireless,bluetooth]
Feb 10 11:16:24.616: vmx| USB: Found device [name:Apple\ IR\ Receiver vid:05ac pid:8242 path:13/5/1 speed:low family:hid]
Feb 10 11:16:36.296: vmx| USBGM: UsbgMacosGetDeviceHandle failed
Feb 10 11:16:36.296: vmx| USBGM: Connect failed for fd1000004e86877
Feb 10 11:16:36.296: vmx| USBGM: Rejecting claimed device [name:SAMSUNG_Android vid:04e8 pid:6877 path:13/15/1 speed:high family:comm]
Feb 10 11:16:36.297: vmx| USB: Autoconnecting device "SAMSUNG_Android" matching pattern [path:13/15/1 autoclean:1]
Feb 10 11:16:36.297: vmx| USB: Connecting device 0xfd1000004e86877
Feb 10 11:16:36.299: vmx| VMXVmdbLoadUsbDevices: New set of 4 USB devices
Feb 10 11:16:36.299: vmx| USB: Found device [name:Apple\ Built-in\ iSight vid:05ac pid:8501 path:13/15/4 speed:high family:vendor,video]
Feb 10 11:16:36.299: vmx| USB: Found device [name:Apple\ Bluetooth\ USB\ Host\ Controller vid:05ac pid:8205 path:10/1/1 speed:full family:other,wireless,bluetooth]
Feb 10 11:16:36.299: vmx| USB: Found device [name:Apple\ IR\ Receiver vid:05ac pid:8242 path:13/5/1 speed:low family:hid]
Feb 10 11:16:36.299: vmx| USB: Found device [name:SAMSUNG_Android vid:04e8 pid:6877 path:13/15/1 speed:high family:comm]
Feb 10 11:16:36.313: vmx| VMXVmdbLoadUsbDevices: New set of 3 USB devices
Feb 10 11:16:36.314: vmx| USB: Found device [name:Apple\ Built-in\ iSight vid:05ac pid:8501 path:13/15/4 speed:high family:vendor,video]
Feb 10 11:16:36.314: vmx| USB: Found device [name:Apple\ Bluetooth\ USB\ Host\ Controller vid:05ac pid:8205 path:10/1/1 speed:full family:other,wireless,bluetooth]
Feb 10 11:16:36.314: vmx| USB: Found device [name:Apple\ IR\ Receiver vid:05ac pid:8242 path:13/5/1 speed:low family:hid]
Feb 10 11:19:52.566: vmx| USBG: CONNREQ: Dequeued head request after 196265 ms for [name:SAMSUNG_Android vid:04e8 pid:6877 path:13/15/1 speed:high family:comm]
Feb 10 11:19:52.609: vmx| USBGM: UsbgMacosGetDeviceHandle failed
Feb 10 11:19:52.609: vmx| USBGM: Connect failed for fd1000004e86877
Feb 10 11:19:52.633: vmx| USBGM: Rejecting claimed device [name:SAMSUNG_Android vid:04e8 pid:6877 path:13/15/1 speed:high family:comm]
Feb 10 11:20:43.573: vmx| USB: Autoconnecting device "SAMSUNG_Android" matching pattern [path:13/15/1 autoclean:1]
Feb 10 11:20:43.573: vmx| USB: Connecting device 0xfd1000004e8681c
Feb 10 11:20:43.575: vmx| VMXVmdbLoadUsbDevices: New set of 4 USB devices
Feb 10 11:20:43.575: vmx| USB: Found device [name:Apple\ Built-in\ iSight vid:05ac pid:8501 path:13/15/4 speed:high family:vendor,video]
Feb 10 11:20:43.575: vmx| USB: Found device [name:Apple\ Bluetooth\ USB\ Host\ Controller vid:05ac pid:8205 path:10/1/1 speed:full family:other,wireless,bluetooth]
Feb 10 11:20:43.575: vmx| USB: Found device [name:Apple\ IR\ Receiver vid:05ac pid:8242 path:13/5/1 speed:low family:hid]
Feb 10 11:20:43.575: vmx| USB: Found device [name:SAMSUNG_Android vid:04e8 pid:681c path:13/15/1 speed:high family:vendor,comm,storage]
Feb 10 11:20:48.180: vmx| USBGM: UsbgDeviceArbitratedNotificationCallback connecting:SAMSUNG_Android
Feb 10 11:20:48.180: vmx| USBGM: Stale autoconnect lockout on port fd100000 expired 51546 ms ago
Feb 10 11:21:01.876: vmx| USB: Connecting device 0xfd1000004e8681c
Feb 10 11:21:10.637: vmx| USB: Connecting device 0xfd1000004e8681c
Feb 10 11:22:11.377: vmx| USB: Connecting device 0xfd1000004e8681c
Feb 10 11:22:11.377: vmx| USBG: CONNREQ: Removing stale request after 87802 ms for [name:SAMSUNG_Android vid:04e8 pid:681c path:13/15/1 speed:high family:vendor,comm,storage]
Feb 10 11:22:11.399: vmx| VMXVmdbLoadUsbDevices: New set of 3 USB devices
Feb 10 11:22:11.399: vmx| USB: Found device [name:Apple\ Built-in\ iSight vid:05ac pid:8501 path:13/15/4 speed:high family:vendor,video]
Feb 10 11:22:11.399: vmx| USB: Found device [name:Apple\ Bluetooth\ USB\ Host\ Controller vid:05ac pid:8205 path:10/1/1 speed:full family:other,wireless,bluetooth]
Feb 10 11:22:11.399: vmx| USB: Found device [name:Apple\ IR\ Receiver vid:05ac pid:8242 path:13/5/1 speed:low family:hid]
Feb 10 11:23:28.835: vmx| USBG: CONNREQ: Dequeued head request after 77456 ms for [name:SAMSUNG_Android vid:04e8 pid:681c path:13/15/1 speed:high family:vendor,comm,storage]
Feb 10 11:23:28.910: vmx| USBGM: UsbgMacosGetDeviceHandle failed
Feb 10 11:23:28.910: vmx| USBGM: Connect failed for fd1000004e86877
Feb 10 11:23:28.910: vmx| USBGM: Rejecting claimed device [name:SAMSUNG_Android vid:04e8 pid:6877 path:13/15/1 speed:high family:comm]

0 Kudos
Neben
VMware Employee
VMware Employee

Do you have all of the following lines set in the vmx config file?

usb.quirks.device0 = "0x4e8:0x681d skip-reset"

usb.quirks.device1 = "0x4e8:0x68a9 skip-reset"

usb.quirks.device2 = "0x4e8:0x6877 skip-reset"

usb.quirks.device3 = "0x4e8:0x681c skip-reset"

Please also attach the full vmx log file.

0 Kudos
sapcmc
Contributor
Contributor

Please find attached both .log file and .vmx configuration used.

Thanks for the help.

0 Kudos
Neben
VMware Employee
VMware Employee

Thanks!

It looks like the quirks are setup correctly, but there's something that's causing UHCI to continually reset (shouldn't affect the Galaxy since it's high speed/connects to EHCI).  Could you delete these lines and try powering on/booting the VM again?

ehci:1.present = "TRUE"
ehci:1.deviceType = "mouse"
usb:0.present = "FALSE"
usb:1.present = "FALSE"

The virtual mouse should be connected to usb:N (UHCI) instead of EHCI and the default settings should be readded automatically on when the VM is powered on.  Also, could you check to see if there is a "USB Univeral Host Controller" device present in the VM's device manager?  Maybe there's some driver isssue in the guest that's resetting UHCI.

0 Kudos
sapcmc
Contributor
Contributor

Hi,

Just deleted those lines, rebooted VM and still mobile not visible when connecting via Kies ....

Also attached screenshot of computer management. There seems to be no issue at USB controllers.

0 Kudos
sapcmc
Contributor
Contributor

Also current log

0 Kudos
Neben
VMware Employee
VMware Employee

Thanks, no more UHCI resets, so that seems to be resolved.  From this log, it doesn't looks like the Galaxy S was ever connected to the VM.  Since it wasn't plugged in during VM bootup, the sticky-autoconnect was removed:

Feb 10 20:34:01.464: vmx| USB: Removing stale autoconnect pattern [path:13/15/1 autoclean:1]
Feb 10 20:34:01.464: vmx| USB: Removing autoconnect pattern from slot 0

It looks like you'll need to connect it to the VM via the Fusion UI again.

0 Kudos