lsusb shows wrong name of the connected phone

Bug #1306747 reported by Sayantan Das on 2014-04-11
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
android-udev (Arch Linux)
New
Undecided
Unassigned
usbutils (Ubuntu)
Low
Unassigned

Bug Description

I am currently running Ubuntu 14.04 x64 version.
When I connect my Google Nexus 5 to the laptop using usb cable and type lsusb, the output shows Nexus 4

~$ lsusb
Bus 002 Device 004: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)
---

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1306747

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected trusty
description: updated
description: updated
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc1-trusty/

Changed in linux (Ubuntu):
importance: Undecided → Low
Sayantan Das (sayantan13) wrote :

Same issue. Reporting wrong name.

Vostro-3300:~$ lsusb
Bus 002 Device 003: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0c45:6481 Microdia
Bus 001 Device 003: ID 138a:0008 Validity Sensors, Inc. VFS300 Fingerprint Reader
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Vostro-3300:~$ uname -a
Linux Vostro-3300 3.15.0-031500rc1-generic #201404131835 SMP Sun Apr 13 22:36:23 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream

Sayantan Das, as per the lsusb man page, one may request a USB ID change via http://www.linux-usb.org/usb-ids.html .

Changed in linux (Ubuntu):
status: Confirmed → Triaged
affects: linux (Ubuntu) → usbutils (Ubuntu)
Robert Ancell (robert-ancell) wrote :

This was requested to be changed to "Nexus Device (debug)":
https://usb-ids.gowdy.us/read/UD/18d1/4ee2

Bartlomiej (bartoleo) wrote :

The problem still exist. When i attach Samsung Note 4 device in download mode, I'ts wrongly recognized as:
Bus 001 Device 102: ID 04e8:685d Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] (Download mode)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments