Avila tablet is not recognised by libmtp

Bug #1535689 reported by Chunsang Jeong
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
Critical
Pat McGowan
The Avila project
Fix Released
Critical
Alfonso Sanchez-Beato
libmtp (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

The Avila tablet (product name is Frieza) is not recognised when in MTP file mode by Ubuntu.

 idVendor=2a47, idProduct=200D

Tested on a trusty/precise/wily laptop and found the device is not listed in the desktop interface.

The line below will make it work normally just for testing.
ATTR{idVendor}=="2a47", ATTR{idProduct}=="200d", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
# Avila Frieza (MTP+ADB)

Reproduction Proceedure:

 - Plug a tarblet into the Ubuntu desktop via a USB cable
 - Expect to see a natuilus window pop up, with the option to browse and copy files to the phone's file system

 - Actual result: no response from the Ubuntu host.

Related OEM bug #1531494

Changed in avila:
milestone: none → ww06-2016
Changed in canonical-devices-system-image:
milestone: none → ww08-2016
Changed in avila:
milestone: ww06-2016 → none
description: updated
Changed in canonical-devices-system-image:
status: New → Confirmed
importance: Undecided → Critical
assignee: nobody → Pat McGowan (pat-mcgowan)
Changed in avila:
status: New → Invalid
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

This is working on my Wily laptop !?

My rules contain

My /lib/udev/rules.d/69-libmtp.rules:

ATTR{idVendor}=="2a47", ATTR{idProduct}=="2008", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
ATTR{idVendor}=="2a47", ATTR{idProduct}=="0c02", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
ATTR{idVendor}=="2a47", ATTR{idProduct}=="2008", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
ATTR{idVendor}=="2a47", ATTR{idProduct}=="0c02", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
ATTR{idVendor}=="2a47", ATTR{idProduct}=="7f10", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"

lsusb shows

Bus 001 Device 075: ID 2a47:200d

Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

I am running the eng-15 version of the build

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

I added the rule to the udev rules of an up to date xenial host and the device is still not recognized. I'm using user build 17

Changed in avila:
importance: Undecided → Critical
Changed in avila:
status: Invalid → Triaged
assignee: nobody → Yuan-Chen Cheng (ycheng-twn)
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Last update was MTP works if developer mode is not enabled and a fix is in progress

Changed in canonical-devices-system-image:
status: Confirmed → In Progress
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Working with final adb support

Changed in canonical-devices-system-image:
status: In Progress → Fix Committed
Changed in avila:
assignee: Yuan-Chen Cheng (ycheng-twn) → Alfonso Sanchez-Beato (alfonsosanchezbeato)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libmtp (Ubuntu):
status: New → Confirmed
Changed in canonical-devices-system-image:
status: Fix Committed → Fix Released
Changed in avila:
status: Triaged → Fix Released
Revision history for this message
Dylan Aïssi (daissi) wrote :

Should be fixed since libmtp 1.1.12 [1] already in Yakkety.

[1] https://sourceforge.net/p/libmtp/code/ci/777203683b5

Changed in libmtp (Ubuntu):
status: Confirmed → Fix Committed
Dylan Aïssi (daissi)
Changed in libmtp (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.