From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 209411] When retrieving string descriptor from mobile device returns eproto error
Date: Wed, 30 Sep 2020 14:47:58 +0000 [thread overview]
Message-ID: <bug-209411-208809-fnXB08JlRB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209411-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209411
--- Comment #11 from Alan Stern (stern@rowland.harvard.edu) ---
The traces aren't really complete, because you didn't start them until after
the USB cable was plugged in. Also, the traces start out with the computer
reading string descriptors 1, 2, 3, 4, and 6 (in the non-working trace), and
the values of the descriptors are different in the two traces. In the working
trace, the values are:
1: "Xiaomi"
2: "MI MAX"
3: "d553b4b6"
4: "ADB Interface"
In the non-working trace:
1: "Xiaomi"
2: "Redmi K30 5G"
3: "c2a85d7"
4: "ptp_adb"
6: "ADB Interface"
It looks like you used two different phones for the tests, or one phone with
two different ROMs installed. Is that what you did?
Are you asking why one phone works and the other phone doesn't?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-09-30 14:47 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 17:51 [Bug 209411] New: When retrieving string descriptor from mobile device returns eproto error bugzilla-daemon
2020-09-28 17:49 ` [Bug 209411] " bugzilla-daemon
2020-09-28 17:49 ` [Bug 209411] New: " Greg KH
2020-09-29 14:35 ` [Bug 209411] " bugzilla-daemon
2020-09-29 14:38 ` bugzilla-daemon
2020-09-29 16:04 ` bugzilla-daemon
2020-09-29 16:23 ` bugzilla-daemon
2020-09-29 16:24 ` bugzilla-daemon
2020-09-29 16:40 ` bugzilla-daemon
2020-09-30 11:05 ` bugzilla-daemon
2020-09-30 11:06 ` bugzilla-daemon
2020-09-30 11:06 ` bugzilla-daemon
2020-09-30 14:47 ` bugzilla-daemon [this message]
2020-09-30 14:52 ` bugzilla-daemon
2020-09-30 14:53 ` bugzilla-daemon
2020-09-30 15:04 ` bugzilla-daemon
2020-09-30 15:15 ` bugzilla-daemon
2020-09-30 15:37 ` bugzilla-daemon
2020-09-30 15:41 ` bugzilla-daemon
2020-09-30 15:43 ` bugzilla-daemon
2020-09-30 15:44 ` bugzilla-daemon
2020-09-30 19:25 ` bugzilla-daemon
2020-10-02 16:02 ` bugzilla-daemon
2020-10-02 16:04 ` bugzilla-daemon
2020-10-02 16:46 ` bugzilla-daemon
2020-10-05 13:53 ` bugzilla-daemon
2020-10-05 14:38 ` bugzilla-daemon
2020-10-05 14:48 ` bugzilla-daemon
2020-10-07 4:54 ` bugzilla-daemon
2020-10-10 18:02 ` bugzilla-daemon
2020-10-11 1:15 ` bugzilla-daemon
2020-10-11 4:27 ` bugzilla-daemon
2020-10-11 8:13 ` bugzilla-daemon
2020-10-11 14:13 ` bugzilla-daemon
2020-10-12 12:49 ` bugzilla-daemon
2020-10-12 12:50 ` bugzilla-daemon
2020-10-12 14:47 ` bugzilla-daemon
2020-10-12 16:25 ` bugzilla-daemon
2020-10-12 16:49 ` bugzilla-daemon
2020-10-12 18:30 ` bugzilla-daemon
2020-10-12 18:50 ` bugzilla-daemon
2020-10-13 0:24 ` bugzilla-daemon
2020-10-13 4:09 ` bugzilla-daemon
2020-10-13 5:10 ` bugzilla-daemon
2020-10-13 6:02 ` bugzilla-daemon
2020-10-13 6:21 ` bugzilla-daemon
2020-10-13 6:25 ` bugzilla-daemon
2020-10-13 6:37 ` bugzilla-daemon
2020-10-13 17:51 ` bugzilla-daemon
2020-10-13 17:55 ` bugzilla-daemon
2020-10-13 17:56 ` bugzilla-daemon
2020-10-13 17:58 ` bugzilla-daemon
2020-10-14 3:56 ` bugzilla-daemon
2020-10-14 13:24 ` bugzilla-daemon
2020-10-14 18:43 ` bugzilla-daemon
2020-10-14 18:49 ` bugzilla-daemon
2020-10-14 18:56 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-209411-208809-fnXB08JlRB@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).