Revision history [back]

Before the update I could connect my Jolla via USB (PC Connection) to my laptop (running Kubuntu 13.10) and I could access the contents via mtp:/ protocol.

Now however, the device is registered (system notification popup), but I cannot access it at all. Opening mtp:/ in Dolphin shows no devices (before: "Sailfish"). By default KDE tries to access it using camera:/ but nothing appears there either.

Before the update I could connect my Jolla via USB (PC Connection) to my laptop (running Kubuntu 13.10) and I could access the contents via mtp:/ protocol.

Now however, the device is registered (system notification popup), but I cannot access it at all. Opening mtp:/ in Dolphin shows no devices (before: "Sailfish"). By default KDE tries to access it using camera:/ but nothing appears there either.

Before the update I could connect my Jolla via USB (PC Connection) to my laptop (running Kubuntu 13.10) and I could access the contents via mtp:/ protocol.

Now however, the device is registered (system notification popup), but I cannot access it at all. Opening mtp:/ in Dolphin shows no devices (before: "Sailfish"). By default KDE tries to access it using camera:/ but nothing appears there either.

$ mtp-detect 
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6

Listing raw device(s)
Device 0 (VID=2931 and PID=0a05) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
   Found 1 device(s):
   2931:0a05 @ bus 2, dev 21
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
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.

$ mtp-files
libmtp version: 1.1.6

Device 0 (VID=2931 and PID=0a05) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device

Unable to open ~/.mtpz-data for reading, MTPZ disabled.mtp-files: Successfully connected
Listing File Information on Device with name: (NULL)
No files.
Error 2: PTP Layer error 02ff: get_all_metadata_fast(): could not get proplist of all objects.
Error 2: Error 02ff: PTP: I/O error
Error 2: PTP Layer error 02ff: get_handles_recursively(): could not get object handles.
Error 2: Error 02ff: PTP: I/O error
Error 2: PTP Layer error 02ff: Error getting friendlyname.
Error 2: Error 02ff: PTP: I/O error
Error 2: PTP Layer error 02ff: get_all_metadata_fast(): could not get proplist of all objects.
Error 2: Error 02ff: PTP: I/O error
Error 2: PTP Layer error 02ff: get_handles_recursively(): could not get object handles.
Error 2: Error 02ff: PTP: I/O error
ERROR: Could not close session!
OK.

$ mtp-filetree
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Attempting to connect device(s)
Device: Sailfish
Storage: Phone Memory
1 .chromono_scores
2 .config
…

Before the update I could connect my Jolla via USB (PC Connection) to my laptop (running Kubuntu 13.10) and I could access the contents via mtp:/ protocol.

Now however, the device is registered (system notification popup), but I cannot access it at all. Opening mtp:/ in Dolphin shows no devices (before: "Sailfish"). By default KDE tries to access it using camera:/ but nothing appears there either.

Update:

This is what i get when I try to connect using mtp-tools if it is of any help:

$ mtp-detect 
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6

Listing raw device(s)
Device 0 (VID=2931 and PID=0a05) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
   Found 1 device(s):
   2931:0a05 @ bus 2, dev 21
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
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
 

.

$ mtp-files
libmtp version: 1.1.6

Device 0 (VID=2931 and PID=0a05) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device

Unable to open ~/.mtpz-data for reading, MTPZ disabled.mtp-files: Successfully connected
Listing File Information on Device with name: (NULL)
No files.
Error 2: PTP Layer error 02ff: get_all_metadata_fast(): could not get proplist of all objects.
Error 2: Error 02ff: PTP: I/O error
Error 2: PTP Layer error 02ff: get_handles_recursively(): could not get object handles.
Error 2: Error 02ff: PTP: I/O error
Error 2: PTP Layer error 02ff: Error getting friendlyname.
Error 2: Error 02ff: PTP: I/O error
Error 2: PTP Layer error 02ff: get_all_metadata_fast(): could not get proplist of all objects.
Error 2: Error 02ff: PTP: I/O error
Error 2: PTP Layer error 02ff: get_handles_recursively(): could not get object handles.
Error 2: Error 02ff: PTP: I/O error
ERROR: Could not close session!
OK.

(the command above was running approx. 4 min and 20 sec)

With mtp-filetree I indeed get the file tree, though. Not fast, but this does:

$ mtp-filetree
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Attempting to connect device(s)
Device: Sailfish
Storage: Phone Memory
1 .chromono_scores
2 .config
…