Gutsy does not recognise Vodafone 715 phone (Huawei U120)

[Stephen Irons]

When I plug in a Vodafone 715 mobile phone...nothing visible happens. I believe this phone support USB storage at least.

Gutsy up-to-date 2008-02-28

Details of the phone:

It is a Vodafone 715 mobile phone. The OEM model is Huawei U120.

$ lsusb
Bus 003 Device 005: ID 12d1:1009

$ lsusb -v
Bus 003 Device 005: ID 12d1:1009
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x12d1
  idProduct 0x1009
  bcdDevice 0.00
  iManufacturer 1
  iProduct 2
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 62
    bNumInterfaces 2
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower 500mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 3
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 255 Vendor Specific Subclass
      bInterfaceProtocol 255 Vendor Specific Protocol
      iInterface 3
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0010 1x 16 bytes
        bInterval 128
      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 0x02 EP 2 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 1
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 255 Vendor Specific Subclass
      bInterfaceProtocol 255 Vendor Specific Protocol
      iInterface 3
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x85 EP 5 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 0x05 EP 5 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0

Please can you add support for this device. Thank you.

[Stephen Irons (stephen-irons)]

As an afterthought. Bluetooth works just fine with this phone: OBEX send and receive using Nautilus Send To > Bluetooth (gnome-obex-send) and gnome-obex-server. Also, synchronising with OpenSync works.

However, Bluetooth is slow when trying to send MP3s to the phone, so it would be nice to have a USB connection.

[Dale Jefferson (dalejefferson-deactivatedaccount-deactivatedaccount)]

Thanks for taking the time to post this bug, but we need a little more information.

Have you tried Ubuntu Hardy live cd?

Can you post the output of dmesg (after plugging in the phone) and uname -a

[Stephen Irons (stephen-irons)]

I have not tried Hardy.

$ uname -a
Linux xxxxxx 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 GNU/Linux

Before plugging in phone:
$ dmesg
[ 40.966310] NET: Registered protocol family 17
[ 55.190698] eth0: no IPv6 routers present

After plugging in phone:
$ dmesg
[ 40.966310] NET: Registered protocol family 17
[ 55.190698] eth0: no IPv6 routers present
[264586.497168] usb 5-1: new full speed USB device using uhci_hcd and address 3
[264586.658783] usb 5-1: configuration #1 chosen from 1 choice

If I run lsusb as root (as opposed to an ordinary user) I get strings for the iManufacturer, iProduct and iInterface fields:

  iManufacturer 1 HUAWEI Technologies
  iProduct 2 HUAWEI Mobile

      iInterface 3 Data Interface

but nothing else useful.

[Stephen Irons (stephen-irons)]

Debugging with the aid of Vodafone PC Assist software and a Windows machine:

1. The phone appears as a serial port using driver ...\system32\DRIVERS\hmvmdm.sys. This file is supplied with the PC Assist software.

2. Typing 'AT' into a terminal emulator gets the response 'OK'. But 'ATDT', 'ATH0' and 'ATH1' get an error message. There seems to be some protocol running over the serial connection.

3. To manage files on the the phone, you have to use the supplied PC Assist software. The phone does not appear as a drive that Windows explorer can see.

4. The supplied software also lets you:
   * view SMSs, calls and emails on the phone
   * synchronise addressbook and calendar with Outlook

5. Apparently, you can also connect to the internet via the phone, but I have not tried that; traffic charge is huge.

[Dale Jefferson (dalejefferson-deactivatedaccount-deactivatedaccount)]

I think this is more of a wishlist, but i'll mark it as complete now, thanks for the extra info

[Stephen Irons (stephen-irons)]

If you plug a micro SD card into the phone, then plug USB to the computer, the phone offers to become a USB mass storage device, and disable the phone function. After accepting this offer, the PC connects to the phone just like any other USB mass storage device.

You can close this bug completely. Implementing the other OEM protocols (see original details) is definitely wishlist.

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Michele Mangili (mangilimic)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!