Finish Osmo Nano implementation #50
erik-sutton95
started this conversation in
Ideas & Feature Requests
Replies: 1 comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Osmo Nano is a first-class hardware target (AVC live view), but the operator experience is still a Pocket shell with Nano exceptions. This thread is the remaining Nano work, not “discover Nano from scratch.”
D-Log M scope math has its own thread. Action 6 has its own thread.
Related: roadmap index
What already works (iOS)
0x0019, family.nano, Pocket↔Nano SSID/GATT conflict so the wrong body is refused0x09/0xa8receiver0x41(Pocket is0x08) plus Nano gate0x02/0x09Avc.swift, same decoder path as HEVC)Remaining chunks
Chrome and copy
Control
0x05(Pocket0x17is documented to ACK0xEEon Nano)00/3F/3Dwith a labeled Mimo capture (“swap3D/00if a labeled SET says otherwise”)Android
HevcDecoder.ktis HEVC-only today even though JNI can pack AVC CSD)Hardware close-out
Out of scope
Done when
A Nano operator can pair, monitor AVC live, set Nano color, take a still, and browse media without Pocket-only chrome (gimbal stick, AF, D-Log2) in the way. Android AVC is either done or explicitly listed as remaining under the Android parity thread.
Concrete threads: D-Log M mapping · Action 6 · Android parity
All reactions