Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[Solved] Unable to browse android phone using mtp

Need help with peripherals or devices?
Post Reply
Message
Author
milomak
Posts: 2168
Joined: 2009-06-09 22:20
Been thanked: 2 times

[Solved] Unable to browse android phone using mtp

#1 Post by milomak »

i am running debian sid on cinnamon. I am trying to browse my oneplus one using a file manager. the phone seems to be detected but does not actualy allow me to browse.

i am able to use adb on the device

Code: Select all

# adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached 
xxxxxxxx	device
dmesg output when device is plugged in

Code: Select all

[   27.287080] usb 1-4: new high-speed USB device number 8 using xhci_hcd
[   27.456287] usb 1-4: New USB device found, idVendor=05c6, idProduct=6765
[   27.456292] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   27.456295] usb 1-4: Product: A0001
[   27.456297] usb 1-4: Manufacturer: OnePlus
[   27.456299] usb 1-4: SerialNumber: 629a48f8
[   47.284968] usb 1-4: usbfs: process 1866 (mtp-detect) did not claim interface 0 before use
[   47.441273] usb 1-4: reset high-speed USB device number 8 using xhci_hcd
[   47.612407] usb 1-4: usbfs: process 1866 (mtp-detect) did not claim interface 0 before use
[   47.612596] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612607] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612615] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612623] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612629] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612636] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612643] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612650] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612656] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612664] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612681] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612689] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612696] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612710] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612717] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612723] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612731] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612738] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612745] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612752] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612759] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612807] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612820] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612831] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612848] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612857] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612864] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612872] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612879] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612886] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612894] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612901] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612909] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612917] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612924] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612932] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612939] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612950] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612958] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612967] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612979] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.612990] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613000] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613007] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613015] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613022] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613030] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613038] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613045] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613053] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613060] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613072] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613085] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613093] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613099] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613107] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613118] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613126] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613133] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613141] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613148] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613154] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613165] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613177] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613191] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613201] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613208] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613217] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613224] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613232] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613239] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613247] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613254] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613261] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613268] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613275] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613282] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613290] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613301] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.613309] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.769279] usb 1-4: reset high-speed USB device number 8 using xhci_hcd
[   47.940841] usb 1-4: usbfs: process 1768 (events) did not claim interface 0 before use
[   47.940930] usb 1-4: usbfs: process 1866 (mtp-detect) did not claim interface 0 before use
[  180.176779] usb 1-4: USB disconnect, device number 8
mtp-detect returns this

Code: Select all

$ mtp-detect 
libmtp version: 1.1.12

Listing raw device(s)
Device 0 (VID=05c6 and PID=6765) is a Qualcomm (for OnePlus) One (MTP+ADB).
   Found 1 device(s):
   Qualcomm (for OnePlus): One (MTP+ADB) (05c6:6765) @ bus 1, dev 9
Attempting to connect device(s)
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
this is what i see in nemo
Image

here are mtp related packages installed

Code: Select all

$ dpkg -l | grep mtp
ii  gmtp                                    1.3.10-1                             amd64        simple file transfer program for MTP based devices
ii  go-mtpfs                                0.0~git20150917.0.bc7c0f7-1          amd64        Mount MTP devices over FUSE
ii  jmtpfs                                  0.5-2+b1                             amd64        FUSE based filesystem for accessing MTP devices
ii  kio-mtp                                 0.75+git20140304-2                   amd64        access to MTP devices for applications using the KDE Platform
ii  libmtp-common                           1.1.12-1                             all          Media Transfer Protocol (MTP) common files
ii  libmtp-runtime                          1.1.12-1+b1                          amd64        Media Transfer Protocol (MTP) runtime tools
ii  libmtp9:amd64                           1.1.12-1+b1                          amd64        Media Transfer Protocol (MTP) library
ii  libnet-smtp-ssl-perl                    1.04-1                               all          Perl module providing SSL support to Net::SMTP
ii  mtp-tools                               1.1.12-1+b1                          amd64        Media Transfer Protocol (MTP) library tools
ii  mtpfs                                   1.1-5                                amd64        FUSE filesystem for Media Transfer Protocol devices
libusb related packages

Code: Select all

# dpkg -l | grep libusb
ii  libgusb2:amd64                          0.2.9-1+b1                           amd64        GLib wrapper around libusb1
ii  libusb++-0.1-4c2:amd64                  2:0.1.12-25                          amd64        userspace C++ USB programming library
ii  libusb-0.1-4:amd64                      2:0.1.12-30                          amd64        userspace USB programming library
ii  libusb-1.0-0:amd64                      2:1.0.21-1                           amd64        userspace USB programming library
ii  libusb-1.0-0-dev:amd64                  2:1.0.21-1                           amd64        userspace USB programming library development files
ii  libusb-1.0-doc                          2:1.0.21-1                           all          documentation for userspace USB programming
ii  libusb-dev                              2:0.1.12-30                          amd64        userspace USB programming library development files
ii  libusbmuxd4:amd64                       1.0.10-3+b1                          amd64        USB multiplexor daemon for iPhone and iPod Touch devices - library
ii  libusbredirhost1:amd64                  0.7.1-1                              amd64        Implementing the usb-host (*) side of a usbredir connection (runtime)
ii  libusbredirparser1:amd64                0.7.1-1                              amd64        Parser for the usbredir protocol (runtime)
android-rules

Code: Select all

# cat /etc/udev/rules.d/51-android.rules
# Qualcomm
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666", GROUP="plugdev"
mtp-rules

Code: Select all

# cat /etc/udev/rules.d/69-mtp.rules
# OnePlus One (normal & ADB mode)
ATTR{idVendor}=="05c6", ATTR{idProduct}=="6764|6765", SYMLINK+="libmtp-%k", MODE="660", GROUP="plugdev", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
edit - installed another rom on the phone and mtp worked with the above settings
Last edited by milomak on 2017-03-25 11:19, edited 1 time in total.
Desktop: A320M-A PRO MAX, AMD Ryzen 5 3600, GALAX GeForce RTX™ 2060 Super EX (1-Click OC) - Sid, Win10, Arch Linux, Gentoo, Solus
Laptop: hp 250 G8 i3 11th Gen - Sid
Kodi: AMD Athlon 5150 APU w/Radeon HD 8400 - Sid

User avatar
phenest
Posts: 1702
Joined: 2010-03-09 09:38
Location: The Matrix

Re: Unable to browse android phone using mtp

#2 Post by phenest »

I have a Samsung Ace 3 which works in Stretch.

I have no android rules and my mtp rules are slightly different.

Code: Select all

# Qualcomm (for OnePlus) One (MTP)
ATTR{idVendor}=="05c6", ATTR{idProduct}=="6764", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
# Qualcomm (for OnePlus) One (MTP+ADB)
ATTR{idVendor}=="05c6", ATTR{idProduct}=="6765", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
You'll notice the GROUP is "audio" in mine, whereas yours says "plugdev".
ASRock H77 Pro4-M i7 3770K - 32GB RAM - Pioneer BDR-209D

milomak
Posts: 2168
Joined: 2009-06-09 22:20
Been thanked: 2 times

Re: Unable to browse android phone using mtp

#3 Post by milomak »

i tried it first with audio then with plugdev

the user trying to mount is a member of both groups so i don't suspect in the end that will be the fatal problem
Desktop: A320M-A PRO MAX, AMD Ryzen 5 3600, GALAX GeForce RTX™ 2060 Super EX (1-Click OC) - Sid, Win10, Arch Linux, Gentoo, Solus
Laptop: hp 250 G8 i3 11th Gen - Sid
Kodi: AMD Athlon 5150 APU w/Radeon HD 8400 - Sid

User avatar
phenest
Posts: 1702
Joined: 2010-03-09 09:38
Location: The Matrix

Re: Unable to browse android phone using mtp

#4 Post by phenest »

milomak wrote:ithe user trying to mount
Is there something you failed to mention in the first post? Do you have more than one user, and one of them works and one doesn't?
ASRock H77 Pro4-M i7 3770K - 32GB RAM - Pioneer BDR-209D

milomak
Posts: 2168
Joined: 2009-06-09 22:20
Been thanked: 2 times

Re: Unable to browse android phone using mtp

#5 Post by milomak »

nope. there's only one user.
Desktop: A320M-A PRO MAX, AMD Ryzen 5 3600, GALAX GeForce RTX™ 2060 Super EX (1-Click OC) - Sid, Win10, Arch Linux, Gentoo, Solus
Laptop: hp 250 G8 i3 11th Gen - Sid
Kodi: AMD Athlon 5150 APU w/Radeon HD 8400 - Sid

Post Reply