Skip to content

K2GO-576 docs(adr): Clone adds a USB cable path over AOA - #790

Open
luisguzman-adfa wants to merge 2 commits into
mainfrom
docs/K2GO-576-clone-aoa-adr
Open

luisguzman-adfa wants to merge 2 commits into
mainfrom
docs/K2GO-576-clone-aoa-adr

Conversation

@luisguzman-adfa

Copy link
Copy Markdown
Collaborator

What changes

  • New ADR controller/docs/ADR-K2GO-576-clone-over-aoa.md (status: Proposed). Documentation only; no code change.
  • Decision: rsync stays the only engine. A local TCP relay carries a second rsync session over an Android Open Accessory (AOA) cable, in parallel with Wi-Fi. A work queue splits the library between the two paths.
  • Also decides: a small framed protocol on the AOA stream, USB roles detected (the sender should be the USB host), 5 GHz hotspot when there is no Wi-Fi network, and the sender learns the transfer result from rsync's own daemon hooks (post-xfer exec, transfer logging).

Why

  • K2GO-576: measured on three phones with the xfer-bench test APK, a 5 GHz hotspot plus an AOA cable gave 61-66 MB/s, about +50% over the hotspot alone, including two low-end phones.
  • The design must be agreed before implementation (3 phases in the ADR).

Steps to QA

  • Baseline: no design for a cable path in Clone.
  • Change: read the ADR; check that each decision matches the measurements in the linked wiki page.

Verifications

Notes

  • Reviewers: Luis, David (K2GO-576).

rsync over an AOA relay in parallel with Wi-Fi; decision, lifecycle and plan from the xfer-bench measurements.
…hooks

post-xfer exec and transfer logging instead of a wrapper around the binary.

This branch has not been deployed

No deployments
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.

1 participant