My Nexus 4 is unlocked when Ubuntu fails to mount Android MTP device.
Jim S.
On Saturday, May 30, 2015 9:10 AM, Garry Cairns <email address hidden> wrote:
Can I just check that all the people here reporting phone issues have
unlocked the phones? For example, if you need to enter a passcode or
draw a shape to use your phone, it also won't let a computer access it
until you enter the same code to unlock the phone. That's a feature of
the phone rather than a bug in Ubuntu (Ubuntu phones also do this). It
will also drop the connection as soon as your phone shuts its screen off
again after a period not being touched.
Bug description:
I have the same problem on 3 computers with 14.04:
So I tried,
mtp-detect
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10
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
inep: usb_get_endpoint_status(): Resource temporarily unavailable
outep: usb_get_endpoint_status(): Device or resource busy
ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
My Nexus 4 is unlocked when Ubuntu fails to mount Android MTP device.
Jim S.
On Saturday, May 30, 2015 9:10 AM, Garry Cairns <email address hidden> wrote:
Can I just check that all the people here reporting phone issues have
unlocked the phones? For example, if you need to enter a passcode or
draw a shape to use your phone, it also won't let a computer access it
until you enter the same code to unlock the phone. That's a feature of
the phone rather than a bug in Ubuntu (Ubuntu phones also do this). It
will also drop the connection as soon as your phone shuts its screen off
again after a period not being touched.
-- /bugs.launchpad .net/bugs/ 1314556
You received this bug notification because you are subscribed to the bug
report.
https:/
Title:
Unable to mount Android MTP device
Status in gvfs package in Ubuntu:
Confirmed
Bug description:
I have the same problem on 3 computers with 14.04:
So I tried,
mtp-detect
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6
Listing raw device(s) claim_interface () = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface endpoint_ status( ): Resource temporarily unavailable endpoint_ status( ): Device or resource busy claim_interface () = -6LIBMTP PANIC: failed to open session on second attempt
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10
Attempting to connect device(s)
ignoring libusb_
LIBMTP libusb: Attempt to reset device
inep: usb_get_
outep: usb_get_
ignoring libusb_
Unable to open raw device 0
OK.
ProblemType: Bug gnature: Ubuntu 3.13.0- 24.46-generic 3.13.9 Modules: nvidia gvfs/gvfs- mtp-volume- monitor edia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) DIR=<set>
DistroRelease: Ubuntu 14.04
Package: gvfs-backends 1.20.1-1ubuntu1
ProcVersionSi
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernel
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr 30 11:18:12 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-02-12 (441 days ago)
InstallationM
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
LANGUAGE=en_US
PATH=(custom, user)
LANG=en_US.UTF-8
SourcePackage: gvfs
UpgradeStatus: Upgraded to trusty on 2014-04-02 (27 days ago)
To manage notifications about this bug go to: /bugs.launchpad .net/ubuntu/ +source/ gvfs/+bug/ 1314556/ +subscriptions
https:/