#1625 couldn't parse extension samsung.com/devicestatus:0

[Polywog]

I am getting the following error upon mtp-detect:
user@moz:~/Downloads> mtp-detect
libmtp version: 1.1.9

Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 9
Attempting to connect device(s)
LIBMTP ERROR: couldnt parse extension samsung.com/devicestatus:0

it doesn't connect at all to my device. Only thing that works is the Mac's "Android File Transfer" app from Google.

[Polywog]

Yes. Part of the problem though is that it keeps asking me over and over
again. Finally mtp fails with Try Resetting Device

sent from a rotary phone

On Oct 31, 2016 03:04, "Marcus Meissner" marcusmeissner@users.sf.net
wrote:

• assigned_to: Marcus Meissner
• Comment:

the error is likely unrelated.

the new android have a dialog that you need to acknowledging for acess,
did you select that?

weird :/

---

[bugs:#1625] couldn't parse extension samsung.com/devicestatus:0

Status: open
Group: 1.1.9
Created: Sun Oct 30, 2016 01:51 AM UTC by Polywog
Last Updated: Sun Oct 30, 2016 01:51 AM UTC
Owner: Marcus Meissner

I am getting the following error upon mtp-detect:
user@moz:~/Downloads> mtp-detect
libmtp version: 1.1.9

Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 9
Attempting to connect device(s)
LIBMTP ERROR: couldnt parse extension samsung.com/devicestatus:0

it doesn't connect at all to my device. Only thing that works is the Mac's
"Android File Transfer" app from Google.

---

Sent from sourceforge.net because you indicated interest in <
https://sourceforge.net/p/libmtp/bugs/1625/>

To unsubscribe from further messages, please visit <
https://sourceforge.net/auth/subscriptions/>

[Marcus Meissner]

the error is likely unrelated.

the new android have a dialog that you need to acknowledging for acess, did you select that?

weird :/

[Anonymous]

Hi Meissner,
Having the same problem as Polywog with mpt-connect, and I did click 'Allow' on my unlocked Samsung S5.

[Anonymous]

The same here with a Galaxy Tab S2

[Anonymous]

Problem is in the handling of Major and Minor version in libmtp.c, parse_extension_descriptior. The routine is expecting fromat of domain:Major.Minor. Samsung coded the option as domain:Major. Since there is no dot minor the route errors out and ignores that vendor extension and all subsequent extenstion information.

[Anonymous]

any solution? same error and YES I did click 'Allow' on pop up phone message (S7)

[Marcus Meissner]

the message will be gone in 1.1.13. the immediate resets might not yet

[Anonymous]

It's July 2020 and the message is still here.

[Anonymous]

Hello, I am curious if there has been a resolution to this problem? I see it as listed open still.

[Anonymous]

It's July of 2018 and I have the same problem.

This came up all of a sudden. I used to just plug the phone in to the USB connector to the computer and after answering "allow" the directory of the phone appeared on the screen.

[Marcus Meissner]

the question for the people that still have it is what version of libmtp they have in use?

[Anonymous]

I am getting this same error message... Debian 8.1, recently loaded MTP and JMTPFS, older Samsung phone.
My libmtp version (AMD64)
libmtp.so.9.2.0

[Anonymous]

I have same problem 12-27-20. Samsung S5 phone. LibMTP 9.2.0. Phone connected fine for a couple years, then I (stupidly) updated the phone software per provider request. Now no-workee. I've pushed all the right buttons (as I used to before) including the 'allow remote device to access phone files'.
-Croz

[Marcus Meissner]

i fixed this in libmtp 1.1.13 and newer versions (current libmtp.so.9.4.0)

please check that you have at least libmtp 1.1.13 or newer.