Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,770,879 Members 43,799 Now Online
XDA Developers Android and Mobile Development Forum

[Q] VirtualBox hosted Ubuntu doesn't recognize Nexus S

Tip us?
 
Chinpokomon
Old
#1  
Senior Member - OP
Thanks Meter 14
Posts: 202
Join Date: Feb 2009
Question [Q] VirtualBox hosted Ubuntu doesn't recognize Nexus S

I've read this thread: http://forum.xda-developers.com/showthread.php?t=570452

Actually, I've been using the same setup since the G1, and most recently with my Nexus One. Using those devices, when I start up my VirtualBox session and connect them to the PC, USB debugging mode starts and I can use ADB to connect to the device. As a point of reference, ADB also works from the Windows 7 host environment. What I cannot seem to get working is ADB with my Ubuntu 10.10 guest OS. I'm seeing the following in the dmesg log:

Code:
[  453.061415] usb 1-1: new high speed USB device using ehci_hcd and address 2
[  454.132202] usb 1-1: device descriptor read/64, error -32
[  455.268177] usb 1-1: device descriptor read/64, error -32
[  456.397201] usb 1-1: new high speed USB device using ehci_hcd and address 3
[  457.440195] usb 1-1: device descriptor read/64, error -32
[  458.560189] usb 1-1: device descriptor read/64, error -32
[  459.684182] usb 1-1: new high speed USB device using ehci_hcd and address 4
[  459.730509] usb 1-1: device descriptor read/8, error -32
[  459.874823] usb 1-1: device descriptor read/8, error -32
[  460.977314] usb 1-1: new high speed USB device using ehci_hcd and address 5
[  461.042126] usb 1-1: device descriptor read/8, error -32
[  461.186504] usb 1-1: device descriptor read/8, error -32
[  461.288285] hub 1-0:1.0: unable to enumerate USB device on port 1
The VirtualBox USB driver looks like it is correctly installed on the host machine. Anyone have any idea?
 
slowz3r
Old
#2  
slowz3r's Avatar
Senior Member
Thanks Meter 100
Posts: 2,329
Join Date: Jun 2010
Location: Malmstrom AFB, MT
Quote:
Originally Posted by Chinpokomon View Post
I've read this thread: http://forum.xda-developers.com/showthread.php?t=570452

Actually, I've been using the same setup since the G1, and most recently with my Nexus One. Using those devices, when I start up my VirtualBox session and connect them to the PC, USB debugging mode starts and I can use ADB to connect to the device. As a point of reference, ADB also works from the Windows 7 host environment. What I cannot seem to get working is ADB with my Ubuntu 10.10 guest OS. I'm seeing the following in the dmesg log:

Code:
[  453.061415] usb 1-1: new high speed USB device using ehci_hcd and address 2
[  454.132202] usb 1-1: device descriptor read/64, error -32
[  455.268177] usb 1-1: device descriptor read/64, error -32
[  456.397201] usb 1-1: new high speed USB device using ehci_hcd and address 3
[  457.440195] usb 1-1: device descriptor read/64, error -32
[  458.560189] usb 1-1: device descriptor read/64, error -32
[  459.684182] usb 1-1: new high speed USB device using ehci_hcd and address 4
[  459.730509] usb 1-1: device descriptor read/8, error -32
[  459.874823] usb 1-1: device descriptor read/8, error -32
[  460.977314] usb 1-1: new high speed USB device using ehci_hcd and address 5
[  461.042126] usb 1-1: device descriptor read/8, error -32
[  461.186504] usb 1-1: device descriptor read/8, error -32
[  461.288285] hub 1-0:1.0: unable to enumerate USB device on port 1
The VirtualBox USB driver looks like it is correctly installed on the host machine. Anyone have any idea?
may have something to do with the udev adress G1 and N1 where made by HTC using the same UDEV
 
Chinpokomon
Old
#3  
Senior Member - OP
Thanks Meter 14
Posts: 202
Join Date: Feb 2009
Quote:
Originally Posted by slowz3r View Post
may have something to do with the udev adress G1 and N1 where made by HTC using the same UDEV
That was my initial thought as well, but it doesn't look like it's getting that far. I looked and the vendorID already matches what I had in my udev rules. To me, this seems like Virtual Box isn't modeling the Nexus S correctly for some reason.
 
slowz3r
Old
#4  
slowz3r's Avatar
Senior Member
Thanks Meter 100
Posts: 2,329
Join Date: Jun 2010
Location: Malmstrom AFB, MT
Quote:
Originally Posted by Chinpokomon View Post
That was my initial thought as well, but it doesn't look like it's getting that far. I looked and the vendorID already matches what I had in my udev rules. To me, this seems like Virtual Box isn't modeling the Nexus S correctly for some reason.
weird, works perfect using VMware :/
 
Chinpokomon
Old
#5  
Senior Member - OP
Thanks Meter 14
Posts: 202
Join Date: Feb 2009
I'm going to have do some serious shuffling. Android requires a 64-bit build environment now, but I use 32-bit Windows to work around driver signing issues. I think my best setup now will be a 64-bit Ubuntu host with a 32-bit Windows 7 guest... That's going to take some work. *sigh*
 
jaganlal
Old
#6  
Junior Member
Thanks Meter 0
Posts: 2
Join Date: Dec 2010
@Chinpokomon: did you get any solutions to fix this issue? Even i'm hving similar kind of issue. Past 2 days am trying to connect and list my Samsung Captivate Device in Ubuntu, but i failed everytime. Here is my environment

Launching Ubuntu 10.10 (guest OS) from Windows 7 (host OS) using Virtual Box 4.0

In the host OS (Windows 7), i have enabled USB Device Filter for Samsung_Android, and i could see that device in Ubuntu 10.10, but when i use 'lsusb', it doesn't list the samsung device. Any help would be greatly appreciated.
 
slowz3r
Old
#7  
slowz3r's Avatar
Senior Member
Thanks Meter 100
Posts: 2,329
Join Date: Jun 2010
Location: Malmstrom AFB, MT
I never have used VBox but if its anything like VMware dont you have to disconnect the device from windows /connect it to VBox
 
ToSa2
Old
#8  
Junior Member
Thanks Meter 0
Posts: 4
Join Date: Dec 2010
Same here except for the error: -110 instead of -32.
I have three USB filters defined in VBox (product ID 4e20 = fastboot, 4e21 = debug disabled, 4e22 = debug enabled) and corresponding rules defined in /etc/udev/rules.d/51-android.rules
In fastboot mode this works perfectly fine. "fastbood devices" lists the device but when the Nexus S is in normal operation (no matter if debug enabled or disabled), it does not work.
"lsusb" lists the device in fastboot mode but in normal operation it takes a loooooong time and then does not list the Samsung device...
I switched udev to debog logging (/etc/udev/udev.conf -> udev_log="debug") but didn't get any additional logging details in /var/log/udev...
 
ToSa2
Old
#9  
Junior Member
Thanks Meter 0
Posts: 4
Join Date: Dec 2010
I took the time and recreated the VM using VMware player instead of VirtualBox (after reading the post from slowz3r) and I can confirm exactly the same setup works fine in VMware... It's neither a host nor a Ubuntu setup problem but it seems to be the VirtualBox USB support causing the issue with the NS in debug mode...
 
jaganlal
Old
#10  
Junior Member
Thanks Meter 0
Posts: 2
Join Date: Dec 2010
Moved to VMWare - works like charm

Tags
adb, nexus s, usb, virtualbox
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes