New Kindle 10 HD

Question

New Kindle 10 HD

JoshuaFern opened this issue 2 years ago · 13 comments

Hi, I ordered a Kindle around December and it has a different product id, could you add it to the list?

  ~ ❯ adb devices -l
List of devices attached
G8S1KT061474031B       device usb:3-4 product:trona model:KFTRWI device:trona transport_id:2

  ~ ❯ lsusb         
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 009: ID 1949:05e8 Lab126, Inc. Fire
Bus 003 Device 003: ID 0810:0001 Personal Communication Systems, Inc. Dual PSX Adaptor
Bus 003 Device 002: ID 1209:2303 Generic Atreus
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 003: ID 046d:c24a Logitech, Inc. G600 Gaming Mouse
Bus 001 Device 002: ID b58e:9e84 Blue Microphones Yeti Stereo Microphone
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ATTRS{idVendor}=="1949", ATTRS{idProduct}=="05e8"

Answer 1 · 2023-04-25T05:37:09.000Z

Hi @JoshuaFern,
Can you please try kindle10 patch.

I think earlier versions of Kindle simply ran in debug mode, but searching around, I see various numbers when I look for Kindle10.
I am guessing that default mode with MTP access is 05e1 based on seeing this requested patch #1913 Amazon Kindle fire 10 plus problem, and the value you have 05e8 is for adb access?

Please test the patched 51-android-rules and verify it works.
Please try the various Kindle modes and let us know which numbers you see for the different modes (example, default, adb-debug, etc....).

This might help, even if it is for a different kindle - see pdf listed below:
https://stackoverflow.com/questions/8257201/how-can-usb-debugging-for-kindle-fire-can-be-enabled-on-a-linux-ubuntu
http://g-ecx.images-amazon.com/images/G/01/sdk/Connecting_your_Kindle_Fire_to_ADB.pdf

Answer 2 · 2023-05-02T18:49:44.000Z

Hi @JoshuaFern can you give feedback on testing this PR?
#257
Thanks

Answer 3 · 2023-05-02T18:56:05.000Z

Hi,
I haven't tested the PR yet as I've been busy, but I had manually added the udev rules with this product ID and vendor ID and it works.

Please try the various Kindle modes and let us know which numbers you see for the different modes (example, default, adb-debug, etc....).

Could you give me specific instructions for how to enter each mode you'd like me to test? It's not clear how many modes there are or how to get into each of them.

Answer 4 · 2023-05-02T19:03:17.000Z

Generally speaking you have to iterate between different modes and catch the vendor id /product id of an lsusb output.
reboot in fastboot mode and catch
reboot in Android and catch
All these captured values need a line like @JoesCat has done, with the specific udev ENV for that mode.you can look around the .rules file for other examples of ENV usage. Have a look alsa at the gh wiki hereby

Answer 5 · 2023-05-04T19:30:23.000Z

I'm not sure if these are all the modes but I went through and got the IDs for this device.

Fastboot: Bus 001 Device 006: ID 1949:05e0 Lab126, Inc. Android
MTP: Bus 001 Device 011: ID 1949:05e1 Lab126, Inc. Fire
MIDI: Bus 001 Device 012: ID 1949:2046 Lab126, Inc. Fire
PTP: Bus 001 Device 013: ID 1949:05e3 Lab126, Inc. Fire
ADB: Bus 003 Device 009: ID 1949:05e8 Lab126, Inc. Fire

Answer 6 · 2023-05-04T19:50:15.000Z

I had some extra time so I got some IDs for another Android device, the Anbernic RG353P.

Fastboot: Bus 001 Device 024: ID 18d1:d00d Google Inc. Xiaomi Mi/Redmi 2 (fastboot)
MTP: Bus 001 Device 018: ID 2207:0017 Fuzhou Rockchip Electronics Company RG353P
USB Tethering: Bus 001 Device 019: ID 2207:0013 Fuzhou Rockchip Electronics Company RG353P
PTP: Bus 001 Device 020: ID 2207:0018 Fuzhou Rockchip Electronics Company RG353P
ADB: Bus 001 Device 021: ID 2207:0006 Fuzhou Rockchip Electronics Company RG353P

I also have some other devices I could grab the IDs from if you want.

Answer 7 · 2023-05-04T22:11:28.000Z

Sounds like you are on a roll.
Go for it!

:-)

Answer 8 · 2023-05-05T00:57:18.000Z

PinePhone v1.2 running Glodroid
Fastboot: Bus 001 Device 048: ID 18d1:4ee0 Google Inc. Nexus/Pixel Device (fastboot)
MTP: Bus 001 Device 040: ID 18d1:4ee2 Google Inc. Nexus/Pixel Device (MTP + debug)
USB Tethering: Bus 001 Device 041: ID 18d1:4ee4 Google Inc. Nexus/Pixel Device (tether+ debug)
PTP: Bus 001 Device 042: ID 18d1:4ee6 Google Inc. Nexus/Pixel Device (PTP + debug)
ADB: Bus 001 Device 036: ID 18d1:4ee7 Google Inc. Nexus/Pixel Device (charging + debug)

It just occurred to me that I might have my terminology wrong, when I list an output as "adb" I mean charging + debug like above, which makes me wonder. Is there another device ID for MTP without debugging? Should I gather those as well?

Amazon Fire HD 8 2016 (giza)
Fastboot: Bus 001 Device 061: ID 0bb4:0c01 HTC (High Tech Computer Corp.) Dream / ADP1 / G1 / Magic / Tattoo / FP1
MTP: Bus 001 Device 051: ID 1949:0232 Lab126, Inc. Fire
PTP: Bus 001 Device 052: ID 1949:0234 Lab126, Inc. Fire

This version of FireOS has only MTP and PTP as selectable options in the USB screen.

Answer 9 · 2023-05-05T07:35:22.000Z

Yes, when debug is turned-off there is also MTP, PTP,midi,charging......
A large percentage of users are not developers, so the debug-off mode is useful for adding to other rules like 69-mtp, libmtp and other libraries.
If you can clarify which are with debug enabled, or disabled, that is useful info.
If you look at some of the comments in 51-android-rules, you'll notice some have detailed info, like the Fairphone, while other phones lack a lot of info.
The info you have for the PinePhone looks great (mtp+debug....etc)
I guess the FireOS MTP,PTP are with debug off? on? both?

Answer 10 · 2023-05-05T08:30:40.000Z

Thanks for clarifying, I'm starting to understand the nuances. Let me do this all again just to make sure everything is complete and correct. Codenames and ROM versions where appropriate, because I noticed after switching the ROM on the Anbernic the output changed a bit.

Amazon Kindle 10 2021 (trona) - 7.3.2.8

Fastboot: Fastboot: Bus 001 Device 006: ID 1949:05e0 Lab126, Inc. Android
Debug+MTP: Bus 001 Device 056: ID 1949:05e2 Lab126, Inc. Fire
Debug+MIDI: Bus 001 Device 057: ID 1949:2048 Lab126, Inc. Fire
Debug+PTP: Bus 001 Device 058: ID 1949:05e4 Lab126, Inc. Fire
Debug+No data transfer: Bus 001 Device 059: ID 1949:05e8 Lab126, Inc. Fire
MTP: Bus 001 Device 049: ID 1949:05e1 Lab126, Inc. Fire
MIDI: Bus 001 Device 050: ID 1949:2046 Lab126, Inc. Fire
PTP: Bus 001 Device 051: ID 1949:05e3 Lab126, Inc. Fire
No data transfer: Bus 001 Device 052: ID 1949:05e1 Lab126, Inc. Fire

Amazon Kindle 8 2016 (giza) - 5.7.0.0

Fastboot: Bus 001 Device 061: ID 0bb4:0c01 HTC (High Tech Computer Corp.) Dream / ADP1 / G1 / Magic / Tattoo / FP1
Debug+MTP: Bus 001 Device 051: ID 1949:0232 Lab126, Inc. Fire
Debug+PTP: Bus 001 Device 052: ID 1949:0234 Lab126, Inc. Fire
MTP: Bus 001 Device 034: ID 1949:0231 Lab126, Inc. Fire
PTP: Bus 001 Device 031: ID 1949:0233 Lab126, Inc. Fire

Anbernic RG353P - AOSP12 Beta #1

Fastboot: Bus 001 Device 024: ID 18d1:d00d Google Inc. Xiaomi Mi/Redmi 2 (fastboot)
Debug+MTP: Bus 001 Device 006: ID 2207:0017 Fuzhou Rockchip Electronics Company Pixel 6
Debug+Tethering: Bus 001 Device 009: ID 2207:0013 Fuzhou Rockchip Electronics Company Pixel 6
Debug+PTP: Bus 001 Device 010: ID 2207:0018 Fuzhou Rockchip Electronics Company Pixel 6
Debug+No data transfer: Bus 001 Device 011: ID 2207:0006 Fuzhou Rockchip Electronics Company Pixel 6
MTP: Bus 001 Device 015: ID 2207:0007 Fuzhou Rockchip Electronics Company Pixel 6
USB tethering: Bus 001 Device 014: ID 2207:0003 Fuzhou Rockchip Electronics Company Pixel 6
PTP: Bus 001 Device 013: ID 2207:0008 Fuzhou Rockchip Electronics Company Pixel 6
No data transfer: Bus 001 Device 012: ID 2207:0007 Fuzhou Rockchip Electronics Company Pixel 6

PinePhone (v1.2) - 2023w12

Fastboot: Bus 001 Device 048: ID 18d1:4ee0 Google Inc. Nexus/Pixel Device (fastboot)
Debug+MTP: Bus 001 Device 040: ID 18d1:4ee2 Google Inc. Nexus/Pixel Device (MTP + debug)
Debug+Tethering: Bus 001 Device 041: ID 18d1:4ee4 Google Inc. Nexus/Pixel Device (tether+ debug)
Debug+PTP: Bus 001 Device 042: ID 18d1:4ee6 Google Inc. Nexus/Pixel Device (PTP + debug)
Debug+No data transfer: Bus 001 Device 036: ID 18d1:4ee7 Google Inc. Nexus/Pixel Device (charging + debug)
MTP: Bus 001 Device 026: ID 18d1:4ee1 Google Inc. Nexus/Pixel Device (MTP)
Tethering: Bus 001 Device 025: ID 18d1:4ee3 Google Inc. Nexus/Pixel Device (tether)
PTP: Bus 001 Device 024: ID 18d1:4ee5 Google Inc. Nexus/Pixel Device (PTP)
No data transfer: Bus 001 Device 023: ID 18d1:4ee1 Google Inc. Nexus/Pixel Device (MTP)

Answer 11 · 2023-05-05T19:51:05.000Z

Looks good, but I see some conflicting info:

may be a copy-n-paste error == 05e1
Amazon Kindle 10 2021 (trona) - 7.3.2.8
MTP: Bus 001 Device 049: ID 1949:05e1 Lab126, Inc. Fire
No data transfer: Bus 001 Device 052: ID 1949:05e1 Lab126, Inc. Fire (charging)

Anbernic RG353P
MTP: Bus 001 Device 015: ID 2207:0007 Fuzhou Rockchip Electronics Company Pixel 6
No data transfer: Bus 001 Device 012: ID 2207:0007 Fuzhou Rockchip Electronics Company Pixel 6

...and this conflicts with the HTC MTP, and there are many users vs developers, so this could be a comment, but not activated (this avoids causing problems for the majority of users).
Amazon Kindle 8 2016 (giza) - 5.7.0.0
Fastboot: Bus 001 Device 061: ID 0bb4:0c01 HTC (High Tech Computer Corp.)

Answer 12 · 2023-05-05T19:56:50.000Z

It's not a copy paste error, the IDs are the same in both modes - not sure why.

Answer 13 · 2023-05-06T07:01:00.000Z

Maybe it could be (smart) charging, since it is connected to a USB socket.
Without details, it would charge at USB 1.0 rates, not fast charge.

I've added something to try-out, based on looking at other codes, particularly the Samsung mtp.
Give a try for:
adbmtp - might end up being some variant of something like this https://support.garmin.com/en-US/?faq=ycfanFPMus028WBG13MEOA
adbptp - no special extras added
adbmidi - you should see /dev/midi and /dev/midi0? devices - might need more.

I did not add plain mtp, or ptp, since this might be something to add to rules 69
plain midi, don't think is served by anything yet, maybe needs to be retained with 51-rules. ....just thinking out loud.....