Page MenuHomeSolus

Can't Open Android Device Via MTP (Solus Plasma - Dolphin)
Closed, ResolvedPublic

Description

I am unable to access/explore the filesystem of my Android device over USB and MTP. Upon either clicking the device in the left sidebar of Dolphin, or opening the device with the file manager from the device notifier, I am given an error, "Malformed URL". This otherwise works under Solus, Solus GNOME, and Solus MATE.

Event Timeline

Schyken created this task.Mar 28 2018, 10:40 PM

There seems to be a problem with the newer kernels and KDE's 'Solid' backend. There's a bug report here about it.

I don't even get the malformed URL error, instead I get an uri one. When I run mtp-detect in a terminal, the phone is there. When I run solid-hardware5 list it's not. Unless solid sees it, kio doesn't know what to do with it.

If you have wifi you can use kde-connect as a workaround. Hopefully upstream will get mtp sorted out soon.

Can someone validate that it does indeed work when booting the lts kernel? Or I'll do it when I get back.

Can someone validate that it does indeed work when booting the lts kernel? Or I'll do it when I get back.

I'll try it with the LTS kernel and see what happens. Will update in ~10 minutes.

I've gone ahead with the LTS kernel and it seems this doesn't happen with it. It still acts a little weird, like the connection itself is unstable, despite me checking cables and both devices thoroughly, but it is working.

Works with LTS kernel, but as @Schyken said, it's intermittent. That's also a problem that was reported upstream back in 2013, with reports being added to the bug ticket right up to December of last year.

Seems to be a timing issue between detection/seeing if the device is still connected and KIO. Definitely upstream though.

Someone want to try this with both kernels to verify it works?

https://bugs.kde.org/show_bug.cgi?id=387454#c25

Basically change line 4 in /usr/lib64/udev/rules.d/69-libmtp.rules

ACTION!="add", GOTO="libmtp_rules_end"

to

ACTION!="bind", ACTION!="add" GOTO="libmtp_rules_end"

dickie added a subscriber: dickie.Apr 29 2018, 11:41 AM

Someone want to try this with both kernels to verify it works?

That works fine with kernel 4.15.17-65.current

Someone want to try this with both kernels to verify it works?
https://bugs.kde.org/show_bug.cgi?id=387454#c25
Basically change line 4 in /usr/lib64/udev/rules.d/69-libmtp.rules
ACTION!="add", GOTO="libmtp_rules_end"
to
ACTION!="bind", ACTION!="add" GOTO="libmtp_rules_end"

Not sure what this did but it helped ?

Not sure what this did but it helped ?

Welcome to Linux ?

Someone want to try this with both kernels to verify it works?
https://bugs.kde.org/show_bug.cgi?id=387454#c25
Basically change line 4 in /usr/lib64/udev/rules.d/69-libmtp.rules
ACTION!="add", GOTO="libmtp_rules_end"
to
ACTION!="bind", ACTION!="add" GOTO="libmtp_rules_end"

Not sure what this did but it helped ?

Likely will be that the kernel from 4.14 now binds rather than adds devices...

ikey changed the task status from Open to In Progress.May 3 2018, 10:08 AM
ikey claimed this task.
ikey closed this task as Resolved.May 3 2018, 10:10 AM

Tada.