VirtualBox

Opened 14 years ago

Closed 8 years ago

#8186 closed defect (obsolete)

Samsung Galaxy S Series phones can't connect via USB (Win64 host/Linux guest)

Reported by: Vladimir Vukicevic Owned by:
Component: USB Version: VirtualBox 3.2.12
Keywords: Cc:
Guest type: Linux Host type: Windows

Description (last modified by aeichner)

Samsung Galaxy S series phones/tablet seem to do something weird with USB; I have yet to successfully connect them to a Linux guest for use with the android tools (adb and the like).

A similar issue with VMWare seems to be fixed with adding some usb quirks, as described here: http://communities.vmware.com/message/1649362

VBox.log is attached; the VM has a filter for all 0x04e8 vendor devices (tried more specific ones as well; I believe the 0x681c product ID is the android adb interface).

Currently using 3.2.12, will upgrade to 4.0.2 shortly.

Attachments (5)

VBox.log (83.5 KB ) - added by Vladimir Vukicevic 14 years ago.
VBox.log
bad-galaxy-s-vbox.log (943 bytes ) - added by Greg Davis 14 years ago.
reset skipping in log file
FailureAll.txt (2.4 KB ) - added by Douwe Kiestra 13 years ago.
SuccessAll.txt (17.8 KB ) - added by Douwe Kiestra 13 years ago.
Ubuntu 11-2012-01-19-15-30-42.log (52.3 KB ) - added by Sergey Belov 13 years ago.
VBox.log

Download all attachments as: .zip

Change History (12)

by Vladimir Vukicevic, 14 years ago

Attachment: VBox.log added

VBox.log

comment:1 by Vladimir Vukicevic, 14 years ago

Similar issue with 4.0.2.

comment:2 by Greg Davis, 14 years ago

I have the same problem on all the 4.x releases, but with a Windows Vista 32-bit guest. The Galaxy S phone (Fascinate) is listed as "Unknown Device" in the Device Manager. The driver properties page lists the hardware ID as "USB\UNKNOWN" where this field is usually the PCI ID string for the device. The phone does disconnect from the host, and appear to connect to the guest.

by Greg Davis, 14 years ago

Attachment: bad-galaxy-s-vbox.log added

reset skipping in log file

comment:3 by Greg Davis, 14 years ago

That VMware link was really relevant. VMware's workaround was to add a usb "quirk" that skipped the device reset for a specific bus id. In my vbox.log (excerpt attached with a little context), it shows 2 lines for the device saying that a reset is being ignored as the device is already resetting. Same bus id as VMware thread mentions. Nothing else after that in the log though. Is there a synchronization issue going on here where the vbox USB stack needs to re-poll the phone after it finishes resetting in order to provide a hardware ID to windows so it can load a proper driver? Connecting the phone to the Windows Vista 64 bit host works fine, or else I wouldn't be sending this update!

comment:4 by Douwe Kiestra, 13 years ago

I managed to connect my Samsung Galaxy S (SGS for short) to the VB guest (both Linux and Windows XP). Host OS is Windows XP SP3. I installed the latest SAMSUNG USB Driver for Mobile Phones v1.4.2.2 on Windows XP (Host OS) and then I have to add two USB filters for the VB guest. One filter for any normal USB device and the second for my Samsung Galaxy S. The VB guest will only see the SGS when I first insert the normal USB device and only then connect the SGS phone. In Linux I can do "lsusb" and both devices do show up. You can then remove the normal USB device. SGS remains connected. However, if you disconnect the SGS you have to connect the normal USB device first or the VB guest will not see the SGS when you reconnect it. Now I can use Google App Inventor on a VB guest. VirtualBox version is 4.1.0.

by Douwe Kiestra, 13 years ago

Attachment: FailureAll.txt added

by Douwe Kiestra, 13 years ago

Attachment: SuccessAll.txt added

comment:5 by Douwe Kiestra, 13 years ago

Correction: I can use Google App Inventor on Linux (Debian and Ubuntu) guest, but not on Windows XP guest. On Windows XP guest I get a timeout. See log files. FailureAll.txt is Java console log on Windows XP guest. SuccessAll.txt is Java console log on Debian 6.0 guest.

comment:6 by Sergey Belov, 13 years ago

The problem still appears VirtualBox v.4.1.8

after device attach: lsusb Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet

by Sergey Belov, 13 years ago

VBox.log

comment:7 by aeichner, 8 years ago

Description: modified (diff)
Resolution: obsolete
Status: newclosed

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette