yukart/app-flutter
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Link test report: RNDIS unusable on the Redmi; Torque 5G does not enumerate the Orin

Browse Source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DDwfd6Ki8UfG4hK6W5YpJz
This commit is contained in:
Mikkeli Matlock
2026-10-11 17:14:03 +09:00
parent 7f967340b6
commit 657ff90c54
1 changed files with 15 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/impl/reports/LINK-TEST-2026-10-11.md
+15 -2
View File
@@ -140,5 +140,18 @@ when it flows. Labels `pace5-bi`, `pace5-dl`:
socket; for a camera relay, its stream socket. Senders that cannot be changed socket; for a camera relay, its stream socket. Senders that cannot be changed
(sshd for the adb tunnel) stay affected. (sshd for the adb tunnel) stay affected.
Open: whether RNDIS instead of NCM avoids the holding in the first place (not ## No second data point
tested: changing the live gadget configuration needs a root action on the Orin).
- **RNDIS:** with NCM removed from the gadget (RNDIS + ACM only), the Redmi
creates no network interface at all: its kernel has no RNDIS host driver, or
does not bind it. NCM is the only option for this tablet.
- **Kyocera Torque 5G (KYG01, Qualcomm lito, Android 13, kernel 4.19):** has
`cdc_ncm` but no RNDIS driver either. Neither through the PD hub nor on a
direct C-to-C cable did it enumerate the Orin: on the direct cable it reports
itself as host with a device attached, yet nothing appears on its bus and the
Orin's UDC stays `suspended`. Through the hub it charges and is not host at all.
Even enumerated, its Android 13 Ethernet service only accepts `eth\d+`, while
the NCM link would be named `usb0` (the Redmi's Android 16 accepts `usb\d+`).
So whether the holds come from the Orin's NCM gadget or the Redmi's host side is
still open; the ~5.6 MB/s downstream ceiling is likewise unattributed.