[solved] mtpfs crashes with my Nexus 7

Started by orinoco, 2013/07/01, 17:37:05

Previous topic - Next topic

DeKa

Nexus4 and thunar is working fine with kernel 3.10

GoinEasy9

I'm not having any luck in KDE.  Notification is still showing only 2 choices, Gwenview and Digicam.  I'm still playing with it.
Linux Counter number 348347

michaaa62

Did you try some other desktop session to avoid possible KDE services quirks to mtp.
May be from live media to avoid a 'scrambled' /home/$USER.

GoinEasy9

I think the problem is 2 fold:
1) The absence of kio-mtp
2) My Galaxy Nexus isn't rooted.

With distros like Fedora and openSUSE, where kio-mtp is available, I get 4 choices.  The bottom 2 choices are both Dolphin, one reading mtp:/ and one reading camera:/.  The phone is set to mtp.  Funny though, I can see file choices under camera (PTP) but not mtp.  I am getting the "Phone must not be rooted" error using openSUSE and Fedora when trying to access the Dolphin mtp choice.

mtp-detect shows me:
goineasy9@siduction64kdeFX:~$ 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=685c) is a Samsung Galaxy models (MTP+ADB).
  Found 1 device(s):
  Samsung: Galaxy models (MTP+ADB) (04e8:685c) @ bus 2, dev 3
Attempting to connect device(s)
Android device detected, assigning default bug flags
Error 1: Get Storage information failed.
Error 2: PTP Layer error 02fe: get_handles_recursively(): could not get object handles.
Error 2: Error 02fe: PTP: Protocol error, data expected

along with a long printout of the Galaxy Nexus' abilities.

Right now I'm going to follow DeepDayze's advice and try my rooted GTablet, that is, as soon as I find the special mini usb cable that came with it.
Linux Counter number 348347

orinoco

Today I installed kio-mtp. Now the Nexus 7 is recognized as a "Tragbarer Medienspieler" aka mobile mediaplyer. But mounting is not possible.

/var/log/syslog says:

Jul 25 20:09:59 jake kernel: [45894.909333] usb 2-2.1: USB disconnect, device number 3
Jul 25 20:10:11 jake kernel: [45906.778884] usb 2-2.1: new high-speed USB device number 4 using xhci_hcd
Jul 25 20:10:11 jake kernel: [45906.806037] usb 2-2.1: New USB device found, idVendor=18d1, idProduct=4e41
Jul 25 20:10:11 jake kernel: [45906.806050] usb 2-2.1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Jul 25 20:10:11 jake kernel: [45906.806058] usb 2-2.1: Product: Nexus 7
Jul 25 20:10:11 jake kernel: [45906.806065] usb 2-2.1: Manufacturer: asus
Jul 25 20:10:11 jake kernel: [45906.806071] usb 2-2.1: SerialNumber: x
Jul 25 20:10:19 jake kernel: [45914.862645] usb 2-2.1: usbfs: process 3601 (kio_mtp) did not claim interface 0 before use
Jul 25 20:10:19 jake kernel: [45914.925317] usb 2-2.1: reset high-speed USB device number 4 using xhci_hcd
Jul 25 20:10:19 jake kernel: [45914.944851] xhci_hcd 0000:02:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880419e8e3c0
Jul 25 20:10:19 jake kernel: [45914.944864] xhci_hcd 0000:02:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880419e8e400
Jul 25 20:10:19 jake kernel: [45914.944873] xhci_hcd 0000:02:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880419e8e440
Jul 25 20:10:19 jake kernel: [45914.946375] usb 2-2.1: usbfs: process 3601 (kio_mtp) did not claim interface 0 before use
Jul 25 20:10:19 jake kernel: [45914.946734] usb 2-2.1: usbfs: process 5379 (ThreadWeaver::T) did not claim interface 0 before use
Jul 25 20:10:19 jake kernel: [45914.954033] usb 2-2.1: usbfs: process 3601 (kio_mtp) did not claim interface 0 before use

orinoco

For no reason libmtp-runtime wasn't installed on my system. Now it works.

tuxracer

I don't know if I need it, but I have installed libmtp-runtime, libmitp9, libmtp-common, mtpfs on my system and I still have issues when trying to access my HTC One X smartphone.  

Dolphin (file manager) shows up twice when the phone supposedly mounts.  If I'm lucky, I'll see 'mtp:  > HTC One X > Internal storage.   So, I click DCIM. > 100MEDIA.

For e.g., I click an image and Gwenview loads with the final result, a dark grey screen and the circular dots going.   But, no picture ever loads.   I also cannot play videos that are on the phone -at all.

I guess my system is messed up.   This isn't on siduction but I am bringing this up because my Debian Testing distro outputs similar stuff.  Both are KDE, though.

I plan to try a siduction install on another HDD with LXDE or XFCE but not sure on the DE yet.   I guess I can install an additional one if need be.   I was just wondering if the DE has anything to do with how the device mounts or accesses the device.