VirtualBox

Opened 13 years ago

Closed 8 years ago

#9822 closed defect (obsolete)

Can't mount Google Nexus S on Linux guest

Reported by: Per Ostgard Owned by:
Component: USB Version: VirtualBox 4.1.4
Keywords: nexus s, usb failure Cc:
Guest type: Linux Host type: other

Description (last modified by Klaus Espenlaub)

Guest: XUbuntu 11.04 64-bit Host: Windows 7 64-bit

When trying to mount a Google Nexus S phone i see the following messages in the dmesg log:

[ 70.470167] usb 1-1: new high speed USB device using ehci_hcd and address 2 [ 71.530155] usb 1-1: device descriptor read/64, error -32 [ 72.691073] usb 1-1: device descriptor read/64, error -32 [ 73.820244] usb 1-1: new high speed USB device using ehci_hcd and address 3 [ 74.861218] usb 1-1: device descriptor read/64, error -32 [ 76.020277] usb 1-1: device descriptor read/64, error -32 [ 77.130214] usb 1-1: new high speed USB device using ehci_hcd and address 4 [ 77.212407] usb 1-1: device descriptor read/8, error -32 [ 77.356577] usb 1-1: device descriptor read/8, error -32 [ 78.470206] usb 1-1: new high speed USB device using ehci_hcd and address 5 [ 78.525166] usb 1-1: device descriptor read/8, error -32 [ 78.669208] usb 1-1: device descriptor read/8, error -32 [ 78.770405] hub 1-0:1.0: unable to enumerate USB device on port 1

The phone does not show up when running a lsusb

Bus 002 Device 002: ID 80ee:0021 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

"Bus 002 Device 002: ID 80ee:0021" is not the phone since it is also there when the phone is physically disconnected from the host.

Attachments (3)

VBox.log (54.3 KB ) - added by Per Ostgard 13 years ago.
Virtualbox log file
dmesg.log (29.7 KB ) - added by Per Ostgard 13 years ago.
dmesg log file
WindowsDisconn.png (210.8 KB ) - added by Gian-Carlo Pascutto 13 years ago.
Windows errors arfter failed client attach

Download all attachments as: .zip

Change History (9)

by Per Ostgard, 13 years ago

Attachment: VBox.log added

Virtualbox log file

by Per Ostgard, 13 years ago

Attachment: dmesg.log added

dmesg log file

by Gian-Carlo Pascutto, 13 years ago

Attachment: WindowsDisconn.png added

Windows errors arfter failed client attach

comment:1 by Gian-Carlo Pascutto, 13 years ago

I'm hit by this too. Windows Vista x64, Ubuntu 11.04 x64 client. The same setup works perfectly with a Galaxy S2 and a Galaxy Tab.

It's only the Nexus S that fails. More people hitting this problem:

http://forum.xda-developers.com/showthread.php?t=882708 https://forums.virtualbox.org/viewtopic.php?f=1&t=42605

I'm guessing this happens a lot to people doing Android development.

After I try to "adb attach" in the (Linux) client, the Windows side errors out. I've attached a screenshot.

It seems VMware had similar problems and has a setting that allows to work around this: https://plus.google.com/115676199813038165917/posts/WbbZhmDRzDH Any VirtualBox devs wants to take a look if something similar can be done?

comment:2 by komoxo, 13 years ago

Confirm, same problem.

In my case, I used both VB 4.1.6 and 4.1.8 with host WinXP 32/64, guest Ubuntu 10.10 64.

Still no solution yet.

Nexus S is one of the official supported device by Google, I think there could be many users with the same issue.

comment:3 by komoxo, 13 years ago

More information.

Under the same setup/config, for Nexus S, although the ADP interface (18d1:4e22) not work, the fastboot interface (18d1:4e20) does work. So we can flash image to Nexus S, but not debugging program.

See Android docs on Nexus S USB interface:

http://source.android.com/source/initializing.html http://source.android.com/source/building-devices.html

comment:4 by GeorgeGW, 12 years ago

identical problem here. trying to debug Google Nexus S on my ubuntu vbox guest on win7 64 bit host.

I seem this post mention that vmware works fine. If it is the only solution available, might have to switch to vmware even though I don't like to.

Version 0, edited 12 years ago by GeorgeGW (next)

comment:5 by Klaus Espenlaub, 12 years ago

Description: modified (diff)

The only way to get it fixed is providing us with such a device...

VMware tricks don't apply to VirtualBox.

comment:6 by aeichner, 8 years ago

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