BlackBerry USB Composite Device not visible to BlackBerry Device Manager

[Sateesh]

USB Composite Device does not seem to work completely. Mass Storage works, but not control. Because of this BlackBerry Device Manager does not see the device connected. Mass Storage works, though.

The same works with VMware Player -- but only after usb.generic.skipSetConfig modifications.

Host: Ubuntu 7.10 with work-arounds for /proc/bus/usb applied Guest: Windows XP Professional

VBox.log has following entries

UUID {4f190ed5-a63c-4228-d394-5862ba9e9c3f}} aPreserve=false

4772:22:13.183 ERROR [COM]: aRC=0x80070057 aIID={e31f3248-90dd-4ca2-95f0-6b36042d96a2} aComponent={OUSBDeviceCollection} aText={Could not find a USB device with UUID {3e72b3bc-4045-4355-7ab5-d255a1e18ebc}} aPreserve=false

Output of VBoxManager list usbhost: UUID: 3e72b3bc-4045-4355-7ab5-d255a1e18ebc VendorId: 0x0fca (0FCA) ProductId: 0x0004 (0004) Revision: 1.6 (0106) Manufacturer: Research In Motion Product: RIM Composite Device SerialNumber: 49D61147982AF514363F448623D99AB0E04EEF38 Address: /proc/bus/usb/002/004 Current State: Captured

[Sateesh]

VBox.log

[Matt Rusiniak]

I can confirm this issue on 1.5.6 on Fedora 8.

[Stefano Marinelli]

Same on 1.5.6 on Ubuntu 8.04 Beta, amd64. In Windows 2000 guest it behaves a little differently: it detects the BlackBerry device but can't connect to it.

[Sander van Leeuwen]

What about 1.6.0 and also try to enable the ECHI controller.

[Stefano Marinelli]

No difference with 1.6.0 and Win2k guest.

[xvalentinex]

I can confirm this as well.

[ingenium]

I can also confirm on 1.6.0 and XP guest.

[Gergely Kis]

I can also confirm it with 1.6.2 and XP SP2 Professional guest.

I tested with both the new USB controller and the old controller. Host configuration: Ubuntu 8.04 Hardy 32bit (On an Acer Travelmate 5720) Guest configuration: 1024MB RAM, 1 HDD 20GB, VT off, PAE off, ACPI on, USB EHCI on/off.

Vmware Workstation 6.0 works without any hacks / workarounds.

[technofiend]

Replying to sateeshpnv:

USB Composite Device does not seem to work completely. Mass Storage works, but not control. Because of this BlackBerry Device Manager does not see the device connected. Mass Storage works, though.

Confirmed as still broken on 1.6.4 using Windows XP host and Windows XP guest.

Workaround (not confirmed): use a bluetooth dongle to connect to the blackberry.

[Gergely Kis]

Replying to technofiend:

Workaround (not confirmed): use a bluetooth dongle to connect to the blackberry.

Using Bluetooth is _not_ a real workaround, because you can't install software using bluetooth.

[Sateesh]

Replying to technofiend:

Workaround (not confirmed): use a bluetooth dongle to connect to the blackberry.

Blackberry Desktop Manager works with Windows bluetooth stack only. So, the bluetooth dongle should be one supported by Windows bluetooth stack. I tried with Widcomm and Blackberry Desktop Manager does not recognize it.

[Gregory Rojas]

Hi,

I tried the bluetooth workaround and didn't work and confirm the problem in Ubuntu Hardy heron.

[William]

I have a fresh install ubuntu hardy heron with virtualbox version 1.6.4-33808 amd64.

I cannot use my blackberry with a windows xp install 32 bit. The device shows up under device manager as a correct working device but i cannot connect to it with the blackberry desktop manager.

The device shows up as 0fca 0001

With kind regards

William van de Velde

[Kai Ponte]

I see the same issue.

​http://www.perfectreign.com/stuff/2008/20081019_virtualbox_usb_blackberry.png

I can see the blackberry in Windows' Device Manager screen, but the desktop manager doesn't appear to register it.

Ideas?

[Kai Ponte]

Oops! I must have had a brain freeze -

I'm using openSUSE 10.3 32-bit on the host, and the guest is Vista SP1 running under Sun xVM VirtualBox 2.0.2

[Jason]

This problem has been affecting me for several months, but it seems to be working now in VirtualBox 2.0.6 on Ubuntu 8.10 with a Windows XP SP3 guest.

[MuffinFlavored]

This problem is still affecting me.

Host: Arch Linux 32-bit Guest: Windows XP 32-bit Service Pack 3 VirutalBox: PUEL 2.0.6 Device: BlackBerry Pearl 8100

The device is enabled in "Devices". The device appears in "Windows Device Manager". The device does not appear in "BlackBerry Desktop Manager" or "BlackBerry Device Manager".

[Sateesh]

This problem is still present. Verified it on Ubuntu 8.10 host running VirtualBox 2.0.6, Windows XP SP2 guest with BlackBerry Curve 8300 device.

Same symptom -- Windows detects the device, but BlackBerry Device Manager does not. I am running BlackBerry Desktop Manager version 4.7.

jeebus, did you follow any special sequence of actions?

[Jason]

I got a new phone. I just tested, and that apparently is why it's working.

Curve 8310 (OS 4.5) does not work. Bold 9000 (OS 4.6) works fine.

I'm also using Desktop Manager 4.7.

[Kai Ponte]

Just tried under VB 2.0.6, Windows Vista SP1, blackberry 8700c - does not show up as supported under USB.

[Dejan]

I can also confirm that this is not working (VB 2.0.6, XP SP3, Blackberry 8310).

[Wil]

Hello Everyone .. Great News.

I'm running Ubuntu 8.04.1 and the Latest version of VBox. 2.1.0.

I have a Blackberry Storm, and I am running the Desktop Software V 4.7 --

I can confirm this is working .. I'll attach a screen shot.

[Wil]

arg -- no screen shot, and too lazy to upload to a free image host ..

But it does work. W.

[turbo]

This remains an issue

Kubuntu 8.10, vbox 2.1.0, Desktop Manager 4.7, Blackberry 8330 v. 4.3.0.127

9812713 > Storm may not have the same issue because it is a new device with different OS than most versions in the field

[Kai Ponte]

Just tried with VirtualBox 2.1.4, on openSUSE with Vista Ultimate guest OS. (Blackberry 8700c)

Still not being seen through USB. External USB drive and usb key are seen and property assigned drive letters.

[Brad Edmondson]

I confirm the same issue on guest XP Pro SP3+updates, host Ubuntu 9.04, VirtualBox 2.2.4r47978 with a Blackberry 8830 running BBOS 4.2.2.196. The mass storage mode works correctly and I can install the BB USB driver and modify the contents of the media card in Windows, but Blackberry Desktop Manager 4.7 cannot detect the phone. Standalone application loader also does not detect the phone.

[Ian MacDonald]

As noted in #3509, VirtualBox 3.0 now prompts me for a PIN on my 8800. My only issue is the device connection sleeping, and not reconnecting during any 10 second period of inactivity. I can unplug and replug to begin the sync process only to have it get an Intellisync error on the transition where it goes to read my email client contacts. I have seen similar issues on the barry mailing lists related to devices sleeping, so I am going to play with disabling linux autosuspend and see if there is any impact.

[Ian MacDonald]

Even after passing usbcore.autosuspend=0 to my Ubuntu Jaunty 9.04 kernel, I am still experiencing this strange timeout problem with my 8800 on XP SP3 guest with desktop manager 4.7, VBox 3.0, r49315 with the guest additions installed. The USB storage connects without issue.

[Ian MacDonald]

Up to jaunty VBox v3.0.2r49928, still seeing USB timeouts on my 8300 (not 8800 as incorrectly stated above). I experience the same symptoms on Ubuntu 9.10 (kernel 2.6.30) with Vista 64 Pro.

[George R. Young]

On a Debian Lenny 64 bit linux host and a Windows XP client, blackberry synchronization started to work in VirtualBox 3.02, but stopped in 3.04, 3.06 and 3.08. In 3.08, connecting the Blackberry yields 4 entries in the USB device list.

So I've reverted to 3.02.

[Frank Mehnert]

Hopefully fixed in VBox 3.2.10. Duplicate of #6465.