Skip to content

fix(installer): rediscover Orbic ADB after tethering - #1166

Closed
Ununp3ntium115 wants to merge 1 commit into
EFForg:mainfrom
Ununp3ntium115:fix/orbic-adb-tethering-reconnect-523
Closed

Ununp3ntium115 wants to merge 1 commit into
EFForg:mainfrom
Ununp3ntium115:fix/orbic-adb-tethering-reconnect-523

Conversation

@Ununp3ntium115

Copy link
Copy Markdown

Summary

  • Fix Orbic USB installer rediscovery after tethering changes the USB composition.
  • Prefer the known Orbic ADB product ID, then fall back to adb_client interface-class autodetection.
  • Wait for any Orbic Qualcomm USB-mode reconnect instead of only the original product ID.
  • Add tests covering vendor matching across USB product modes.

Closes #523

Verification

  • npm ci
  • npm run build -w daemon/web
  • cargo fmt --all -- --check
  • cargo test -p installer orbic::tests --lib
  • cargo clippy -p installer --lib --all-targets -- -D warnings
  • cargo test --workspace --all-targets
  • git diff --check
  • codegraph sync .

All passed locally. Hardware validation after enabling/disabling tethering remains required.

@cooperq

cooperq commented Sep 25, 2026

Copy link
Copy Markdown
Collaborator

Please read our contribution guidelines and refrain from posting more AI-generated comments. Please fill out the checklist when you are submitting a pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Cant access Orbic via ADB after enabling tethering

2 participants