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

Document ADB in the car: TCP over the NCM link, one SSH hop via 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 13:20:29 +09:00
parent d965031a56
commit 5d5653acec
3 changed files with 104 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/impl/plans/INITIAL.md
+5 -16
View File
@@ -109,23 +109,12 @@ The app binds the process to the USB Ethernet network only when the gateway
address is on `192.168.55.0/24`, so a desk build pointed at halogen over WiFi is
not routed into a dead USB link.
### ADB in the car, without a hub
### ADB in the car
The tablet's only USB port is the Orin link, and in it the tablet is the host —
USB debugging is unavailable there. ADB over TCP is not, and it travels over the
same NCM link:
```bash
adb tcpip 5555 # at the desk, over USB, once per tablet boot
# in the car, from halogen, through the Orin over the tailnet:
ssh -N -L 5555:192.168.55.100:5555 mikkeli-orin-nano &
adb connect localhost:5555
flutter run -d localhost:5555
```
The tablet keeps the RSA authorisation from the USB pairing. `adb usb` turns TCP
mode off again; a reboot does too. Android's *Wireless debugging* (pairing) is
WiFi-only and does not help here. Untested in the car so far.
USB debugging is unavailable there: on the Orin link the tablet is the USB host.
ADB runs over TCP on the NCM link instead, reached from halogen through one SSH
forward via the Orin. Mechanism, steps and troubleshooting:
[ADB in the car](../../ADB-IN-CAR.md).
### CI