We have moved to a new Sailfish OS Forum. Please start new discussions there.
4

[solved][2.0.5.6] MTP stopped working [answered]

asked 2016-11-26 19:09:10 +0200

leszek gravatar image

updated 2016-11-28 10:39:27 +0200

chemist gravatar image

EDIT: Turns out my USB cable that I usually use to transfer files from phones/tablets to the pc broke half way and was able to charge devices but data transfer did not work anymore. Note for anyone and myself don't use cheapo chinese usb cables. The things underneath I just leave for reference. As the kernel error is one indicator of a broken usb cable.

MTP was working or at least the phone detected when plugged in my linux box on 2.0.4. With 2.0.5 and choosing pc connection nothing happens. The device is not detected at all. lsusb does not detect anything. The phone itself says it switched to pc connection mode.

libmtp is version 1.1.12 which should have the Jolla C device ids. Did the IDs changed maybe ? (Though strange that the device isn't detected at all)

Output of dmesg

[ 1011.486084] usb 2-1.1: device descriptor read/64, error -32
[ 1011.661086] usb 2-1.1: device descriptor read/64, error -32
[ 1011.835096] usb 2-1.1: new full-speed USB device number 10 using ehci-pci
[ 1011.909110] usb 2-1.1: device descriptor read/64, error -32
[ 1012.084083] usb 2-1.1: device descriptor read/64, error -32
[ 1012.258106] usb 2-1.1: new full-speed USB device number 11 using ehci-pci
[ 1012.660136] usb 2-1.1: device not accepting address 11, error -32
[ 1012.733130] usb 2-1.1: new full-speed USB device number 12 using ehci-pci
[ 1013.135145] usb 2-1.1: device not accepting address 12, error -32

Any ideas how to solve would be appreciated.

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by leszek
close date 2016-11-27 23:29:37.455748

Comments

@leszek Device IDs should not have been changed. But most of the testing was done on libmtp 1.1.10 (which used in ubuntu 16.04) so later versions might have different set of issues. Any logs you can get from the from phone side around cable connect time might be interesting to see.

spiiroin ( 2016-11-27 18:51:11 +0200 )edit

1 Answer

Sort by » oldest newest most voted
0

answered 2016-11-26 22:55:02 +0200

chemist gravatar image

It can take a very while to have the device show up as indexing everything for MTP is not done before you select it (duration varies depending on how much pictures and music you have). So for me that had an error under windows, the other day it just worked within seconds then. MTP is Mordor was Mordor and always will be Mordor!

edit flag offensive delete publish link more

Comments

4

I had it connected for several hours now as I had it charging through the laptop and nope it does not appear even after a longer time.

leszek ( 2016-11-26 23:00:08 +0200 )edit

As said, _the_other_day_ it started working, the day right after update I just got an error on the Windows side and no working MTP. This does not only sound stupid...

chemist ( 2016-11-27 12:30:46 +0200 )edit

@leszek If it is the biggest remaining known problem with mtp i.e. delay from indexing storages exported via mtp, then leaving the device connected for hours will not help. You should disconnect the cable after some time (depends, but something like 10 seconds to one minute) and connect again.

spiiroin ( 2016-11-27 18:35:40 +0200 )edit
1

Tried it again today a few times. Nothing changed.

leszek ( 2016-11-27 18:38:03 +0200 )edit

Question tools

Follow
1 follower

Stats

Asked: 2016-11-26 19:09:10 +0200

Seen: 593 times

Last updated: Nov 27 '16