LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
Reload this Page [SOLVED] Unable to browse android phone using mtp
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices


Reply
  Search this Thread
Old 02-26-2017, 03:04 AM   #1
milomak
Member
 
Registered: May 2009
Posts: 147

Rep: Reputation: 18
Unable to browse android phone using mtp

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:
# 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:
[   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:
$ 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
http://i65.tinypic.com/vsnvyv.jpg

here are mtp related packages installed
Code:
$ 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:
# 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:
# cat /etc/udev/rules.d/51-android.rules
# Qualcomm
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666", GROUP="plugdev"
mtp-rules
Code:
# 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"
Last edited by milomak; 02-26-2017 at 03:29 AM.
 
Old 02-26-2017, 05:01 AM   #2
ondoho
LQ Addict
 
Registered: Dec 2013
Posts: 19,872
Blog Entries: 12

Rep: Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053Reputation: 6053
it loks like you did some research for how to solve this, but it might have been a good idea to include that information.
mtp is notorious on linux and many threads with almost identical titles exist. top result.

i don't have a solution, but a workaround:
https://github.com/sole/aafm - a file manager based on adb.

ps:
i can't see the screenshot. too much javascript on tinypic.
 
Old 02-26-2017, 12:10 PM   #3
milomak
Member
 
Registered: May 2009
Posts: 147

Original Poster
Rep: Reputation: 18
the image is
http://imgur.com/a/bGBrZ

hope that works.

i'll try your recommendation
 
Old 02-26-2017, 09:27 PM   #4
rokytnji
LQ Veteran
 
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: antiX 23, MX 23
Posts: 7,095
Blog Entries: 21

Rep: Reputation: 3473Reputation: 3473Reputation: 3473Reputation: 3473Reputation: 3473Reputation: 3473Reputation: 3473Reputation: 3473Reputation: 3473Reputation: 3473Reputation: 3473
Just some threads you might not have seen yet

http://www.linuxquestions.org/questi...4/#post5655940

http://www.linuxquestions.org/questi...er-4175592209/

http://www.linuxquestions.org/questi...-a-4175590139/

http://www.linuxquestions.org/questi...4/#post5551539

My Samsung Edge S7 works OK with file sharing using Window Managers like Icewm <rox file manager> and , Desktop enviornments like XFCE <thunar>, on a Debian based distro <MX and AntiX linux>.

I am not telling you to install another distro, I am just guessing your phone settings are what keeping nemo from seeing anything and that this is more of a phone setting issue than a linux issue.

I also use a online file share, airdroid, as a backup for file sharing from any computer without using cables or bluetooth.
Last edited by rokytnji; 02-26-2017 at 09:29 PM.
 
Old 02-26-2017, 09:31 PM   #5
frankbell
LQ Guru
Contributing Member
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,307
Blog Entries: 28

Rep: Reputation: 6136Reputation: 6136Reputation: 6136Reputation: 6136Reputation: 6136Reputation: 6136Reputation: 6136Reputation: 6136Reputation: 6136Reputation: 6136Reputation: 6136
I use Airdroid.

It works very nicely. You don't have to sign up for any of their "cloud" services to use it between your phone and your local computer.

Just turn it off on your phone when you are done, or it will constantly ping wireless connections as you move through your day.
 
Old 03-25-2017, 07:11 AM   #6
milomak
Member
 
Registered: May 2009
Posts: 147

Original Poster
Rep: Reputation: 18
installed another rom on the phone and mtp worked with the above settings
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Problem syncing Android Phone (MTP) jim.thornton Linux - Newbie 5 10-11-2015 12:12 PM
Linux, Android, and MTP Webtm Linux - Mobile 20 09-06-2015 06:21 AM
phone displays in gui through mtp url fine but not in cli mode nitecrawler Slackware 5 01-01-2015 08:06 PM
[SOLVED] How to browse files on a Linux computer from an Android phone using Bluetooth elucches Linux - Networking 5 11-05-2013 05:24 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian

All times are GMT -5. The time now is 03:58 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration