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.
Hi, do you mean restarting vmware and plugging mobile once more in windows virtual machine?
I mean, you'll have to connect the Samsung Galaxy S USB device to the VM while the VM is running again. There should be a pop-up box when you plug the device in while the VM is running or you can use the Fusion UI to find to connect it.
Hmm, I'm not sure what's going on here. The latest vmx log also shows no Samsung device was detected, so something more fundamental is going on if Fusion doesn't think the device is even there (it did detect it in your previous vmx logs). Here are some things you can try:
Make sure the phone is in a state where it can be connected to a PC (not locked, powered off).
Reboot the Mac host machine.
Try another USB cable.
Do you have any software running on the Mac host that uses the device? Maybe quitting that software or uninstalling it (if possible) would help...
There are a couple of issues. The first is that your VM doesn't have an EHCI controller for the high speed (USB 2.0) Samsung device. You should have gotten a pop-up:
Feb 15 02:29:03.366: vmx| The device "Samsung SHW-M110S" was unable to connect to its ideal host controller. An attempt will be made to connect this device to the best available host controller. This may result in an undefined behavior for this device.---------------------------------------
This can happen if you disabled USB 2.0 support or if you ejected the "Standard Enhanced PCI to USB Host Controller" from within the VM (this removes the device from the VMs config).
The second is that your Samsung device is using another PID:
Feb 15 02:29:00.881: vmx| USB: Found device [name:Samsung\ SHW-M110S vid:04e8 pid:685e path:6/2/2/6 speed:high family:vendor,other,comm,storage]
To resolve both issues, shutdown the VM and add the following to the vmx config file:
ehci.present = "TRUE"
usb.quirks.device4 = "0x4e8:0x685e skip-reset"
Let me know if the quirk works for your device and we'll make the quirk automatic for a future release.
Thank you very much for your help. I didn't get the first part but I put two lines and now it recognize my phone.
Now I don't have to go to Windows PC to upgrade my phone!!
Thank you!!!
Hi,
I have a UK Samsung Galaxy S phone and VMware Fusion 3.1.2 running XP SP3.
I have tried the tips on this thread to make my phone work, but when I connect it, it disconnects immediately.
It is driving me mad! Can anyone help please?
Thanks
I think we are actually dealing with a host OS problem here. On a mac, as soon as you plug in the device a number of things pop up on the host side, and they seem to disallow fusion from seeing it.
3/10/11 10:32:38 AM kernel USBF: 39629. 97 AppleUSBEHCI[0xba5a000]::Found a transaction which hasn't moved in 5 seconds on bus 0x24, timing out! (Addr: 0, EP: 0)
I have no idea how to get around this, but it repeats endlessly and none of the quirk settings earlier seem to have any effect.
It looks like you've got the quirks setup correctly and that it was set
Mar 10 13:14:15.385: vmx| DICT usb.quirks.device0 = 0x4e8:0x681d skip-reset
Mar 10 13:14:15.385: vmx| DICT usb.quirks.device1 = 0x4e8:0x68a9 skip-reset
Mar 10 13:14:15.385: vmx| DICT usb.quirks.device2 = 0x4e8:0x6877 skip-reset
Mar 10 13:16:54.167: vmx| USB: Found device [name:SAMSUNG_Android vid:04e8 pid:6877 path:6/2/2 speed:high family:comm]
Mar 10 13:17:27.287: vmx| USB: Found device [name:SAMSUNG_Android vid:04e8 pid:68a9 path:6/2/2 speed:high family:imaging]
Mar 10 13:17:28.269: vmx| USB: Found device [name:SAMSUNG_Android vid:04e8 pid:68a9 path:6/2/2 speed:high family:imaging]
Mar 10 13:18:19.261: vmx| USB: Found device [name:SAMSUNG_Android vid:04e8 pid:681d path:6/2/2 speed:high family:storage]
Mar 10 13:18:47.078: vmx| USB: Connecting device 0x262000004e8681d
Mar 10 13:18:48.270: vmx| USBG: CONNREQ: Dequeued head request after 1170 ms for [name:SAMSUNG_Android vid:04e8 pid:681d path:6/2/2 speed:high family:storage]
Mar 10 13:18:48.273: vmx| USBG: Quirks for device 04e8:681d (user-defined,skip-reset)
Mar 10 13:18:48.318: vmx| USB: Device [name:SAMSUNG_Android vid:04e8 pid:681d path:6/2/2 speed:high family:storage] should already be connected
Mar 10 13:18:48.318: vmx| USB: Found device [name:SAMSUNG_Android vid:04e8 pid:681d path:6/2/2 speed:high family:storage]
Mar 10 13:22:12.548: vmx| USB: Disconnecting device 0x262000004e8681d
I looks like the device was connected to the VM for four minutes in the storage mode, but wasn't connected to the VM in the comm or imaging modes. Was the device available in the guest during that four minute stretch? The disconnect looks like it was unplugged from the host.
Have you tried checking the "Remember" box when the Fusion UI asks you if you want the device to be used by the Windows VM or Mac host?
I think we are actually dealing with a host OS problem here. On a mac, as soon as you plug in the device a number of things pop up on the host side, and they seem to disallow fusion from seeing it.
3/10/11 10:32:38 AM kernel USBF: 39629. 97 AppleUSBEHCI[0xba5a000]::Found a transaction which hasn't moved in 5 seconds on bus 0x24, timing out! (Addr: 0, EP: 0)
I have no idea how to get around this, but it repeats endlessly and none of the quirk settings earlier seem to have any effect.
I wonder if this is related to why the device swtiches from comm to imaging to storage modes. Maybe the device automatically switching between them until it finds one that the host OS is able to use?
celica_tom, scotkight,
Could you try adding the following autoconnect lines to the vmx config file and see if there is any change in functionality?
usb.autoConnect.device0 = "vid:04e8 pid:681d"
usb.autoConnect.device1 = "vid:04e8 pid:68a9"
usb.autoConnect.device2 = "vid:04e8 pid:6877"
This should immediately connect any mode of the device to the VM automatically. Note that disconnecting the Samsung device via the UI may remove one or more of these lines, so just boot the VM after adding these and then physically connect the device to the Mac and see if it works.
No luck. There are no entries in the vmware log file being created when I plug in or unplug the samsung device in firmware load mode.
Still have a ton of the host messages though:
D'oh! If the host can't use/see the device in upgrade mode, then there's not much we can do...
Understood. Just wanted to give the rest of the details so as people pop in and try to duplicate what has already been done they understand why it seems to work for some and not others.
Gotta get someone at samsung to fix the on device drivers so it becomes a standard usb port in in upgrade mode. Once done, I bet it will all work just fine.
BTW, it hits on 6061 and not the other numbers mentioned I played with it quite a bit to see that sometimes it WILL connect to the macos for a second or two and be seen in the fusion menu/log, but then the OS kills it so it disappears from fusion after. If you try to connect immediately it will eventually fail saying it can't get a response.
Hey guys,
Well, randomly, it connected once to the guest! I had switched location from Ethernet to Airport, and plugged the Galaxy in and a little mobile phone icon appeared in the bottom of the VMware window.
Then I disconnected again and it wouldn't work again. I get these errors in the OS X console:
10/03/2011 20:20:26 kernel USBF: 3681. 80 [0x8552e00] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of Hub at 0x24000000)
10/03/2011 20:20:28 kernel USBF: 3682.910 [0x8552e00] The IOUSBFamily was not able to enumerate a device.
My Samsung Galaxy Tab does connect however...
I will try the Galaxy S in another Mac and see if I get the same errors in the OS X Console.
If VMware is not open and I connect the Galaxy S in upgrade mode, the Console says this:
10/03/2011 20:29:40 kernel 0 0 SamsungACMControl: start - Failed to find the CDC driver
10/03/2011 20:29:40 kernel USBF: 4234.721 CDC Abstract Control Model (ACM)[0xaf2e300]::joinPMtree - could not find the hub device
10/03/2011 20:29:42 kernel AppleUSBCDCACMData: Version number - 4.0.1, Input buffers 8, Output buffers 16
10/03/2011 20:29:43 kernel 0 0 SamsungACMControl: start - Failed to find the CDC driver
10/03/2011 20:29:43 kernel AppleUSBCDCACMData: Version number - 4.0.1, Input buffers 8, Output buffers 16
And now I've booted XP in VMware and it sees the phone.
So what I did was:
Close VMware
Connect the phone and select 'Kies' mode (i.e. upgrade mode)
Open VMware and start my VM
Click the phone icon in the bottom of the window to connect 'Samsung_ANDROID'
Open Kies and the phone connects
I'll try this process again and see if it still works.
Hmm.. it seems the phone connects to the guest OS, but I don't see much action in the Samsung software...
OSX console says:
11/03/2011 09:13:29 kernel USBF: 7430.269 AppleUSBEHCI[0x856a800]::Found a transaction which hasn't moved in 5 seconds on bus 0x24, timing out! (Addr: 3, EP: 0)
Repeatedly, while the phone is connected.
Dear all,
I need your help with my Samsung i9000.
I've added
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"
to my .vmx file, but VMWare doesn't find my I9000 in Kies-Mode.
My .log is attached.
Thank you!