MS Activesync cannot recognize a device

[Dmitry Yakimov]

I'm using Ubuntu gutsy as host and WinXP SP2 as quest and MS Activesync 4.5. I have enabled usbfs that is disabled by default in gutsy, that is how I did it:

1. added "none /proc/bus/usb usbfs devgid=1001,devmode=664 0 0" in /etc/fstab
2. removed comments as suggested in ​http://www.virtualbox.org/ticket/747

Then I have enabled USB and USB high speed in VM settings. Then while using WinXP I connect a device and select in VM's USB devices "HP generic RNDIS". Windows starts recognising a device and it fails - the device is not recognized.

When I go to Windows\Device Manager\USB I can see that "unknown" device is connected but its properties do not contain anything related to smartphone or HP.

May I hope that this important thing for many users that moved from Win to Lin will be fixed? Thanks!

[Thomas Käfer]

I can confirm above problem.

Ubuntu 7.10 detects the smartphone with following details

Bus 005 Device 009: ID 045e:0301 Microsoft Corp. 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          239 Miscellaneous Device
  bDeviceSubClass         1 ?
  bDeviceProtocol         1 Microsoft ActiveSync
  bMaxPacketSize0         8
  idVendor           0x045e Microsoft Corp.
  idProduct          0x0301 
  bcdDevice            0.00
  iManufacturer           1 MSFT
  iProduct                2 PocketPC USB Sync
  iSerial                 3 7abf5000-4967-0801-0000-0d9200088fd4
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           62
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xc0
      Self Powered
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass       239 Miscellaneous Device
      bInterfaceSubClass      1 ?
      bInterfaceProtocol      1 Microsoft ActiveSync
      iInterface              0 
      Class specific interface descriptor for class 239 is unsupported
      Class specific interface descriptor for class 239 is unsupported
      Class specific interface descriptor for class 239 is unsupported
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval               1
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0001
  Self Powered

[Hugo Ideler]

Dit you try to disable the USB 2.0 / EHCI controller? And disable the advanced networking functions on your phone? That worked for me.

[Sander van Leeuwen]

If you can reproduce this behaviour with 1.6.x, then please reopen. Try the suggestion posted above as well.