Comment # 3 on bug 1095822 from Mischa Salle

(In reply to Axel Braun from comment #2)
> Created attachment 772943 [details]
> journalctl on current Tumbleweed 20180530
> 
> under current Tumbleweed, using libmtp-1.1.15 it is broken as well. I attach
> a journalctl output as well.
> If you let me know what debugging output from mtp-tools you are looking at
> I'm happy to provide

actually very straight forward just the error returned (if any) by e.g.
mtp-detect and / or simple-mtpfs.

For mtp-detect, in my case (with amarok already opening the mtp), the error is
 "error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to
initialize device"
Googling the combination of libusb_claim_interface() and -6 lead me to
https://stackoverflow.com/questions/6365314/libusb-interface-already-claimed
and then it was easy.

simple-mtpfs only gives the more cryptic
"LIBMTP PANIC: Trying to dump the error stack of a NULL device!"
which is too generic.

I had tried patching libmtp with the different suggested patches from the
stackoverflow page above and those in
https://github.com/phatina/simple-mtpfs/issues/37 but none worked. Now it's
simply making sure amarok doesn't run (which is mildly annoying but
acceptable).

I don't know whether your issue is at all related, it seems more like the
actual android doesn't let you access the device.