Technical Documentation Index

Technical Documentation Index

中文

This page lists only canonical technical pages that have completed code verification, page disposition, and bilingual synchronization. Existing but unaudited documents do not appear here as if they were current facts. Their scope, order, and keep/merge/split/archive/delete status are tracked in Wiki Initialization and Update Checklist.

Framework and maintenance

• Developer Documentation: enter the wiki by task and understand documentation layers and authority rules.
• Wiki Initialization and Update Checklist: see the audit order and disposition status for every old page.
• Documentation Maintenance Conventions: naming, bilingual equivalence, deduplication, and acceptance rules.

Project overview and build

• Project Positioning and Capability Boundary: product goals, repository boundaries, user scenarios, technical shape, and core mental model.
• Build and Application Entry Points: current toolchain versions, included build, commands, Android entry points, and validation boundaries.
• scrcpy Server Integration and Upgrade: current server baseline, client protocol assumptions, upgrade workflow, and regression anchors.
• dadb Integration Boundary: included build, subproject ownership, app consumption boundary, transport identity, and upgrade verification.

Architecture and runtime

• Architecture Documentation: stable constraints and the reading path through architecture topics.
• Module Map and Boundaries: repository boundaries, code layers, ownership, dependency direction, and code-placement rules.
• Runtime Main Path: the end-to-end path from persisted configuration, ADB, and server startup through ordered sockets, metadata, media, and cleanup.
• Session State and Events: main state, process events, component snapshots, and issue classification.
• Session Configuration and Connection Lifecycle: unique ownership for configuration, capabilities, candidates, active connections, reconnection, and cleanup.

ADB, connection, and session configuration

• Subsystem Integration Guide: stable entry by ownership and change type.
• ADB, USB, and Wireless: transport identity, TCP/TLS, USB detach, mDNS, and troubleshooting split.
• ADB Connection Lifecycle: registry, primary/streaming lanes, foreground heartbeat, and the scrcpy health boundary.
• Device Pairing and Wireless Debugging: pairing/connect phases, mDNS state, and failure stages.
• Session Parameter Picker: current presets, game-mode normalization, custom values, and gesture/layout invariants.

scrcpy, media, and control

• Encoding and Decoding: format catalog, capability intersection, metadata, video/audio runtime, and fallback.
• Remote Interaction Performance and Floating Menu: multi-touch, control backpressure, Surface, metrics, and window-coordinate rules.
• Clipboard Synchronization: bidirectional control protocol, UTF-8 lengths, thread ordering, privacy, and test boundaries.

Management, logging, and troubleshooting

• Management Features: current seven management sections, connection ownership, performance, safety, and regression boundaries.
• Events, Monitoring, and Shell Integration: SessionEvent versus the global bus, sampled projections, and Shell APIs.
• Logging System and Maintenance: outputs, detail categories, tags, levels, privacy, and maintenance rules.
• Layered Troubleshooting Method: evidence order from configuration to UI, scenario routing, and fix acceptance.

UI, bilingual text, and engineering rules

• UI Design System: current tokens, shared components, form-layout rules, and visual acceptance baseline.
• Bilingual Text and Copy: TextPair, copy ownership, call-site rules, and bilingual wiki requirements.
• Remote UI Layout Analysis: secure uiautomator XML parsing, semantic nodes, filtering, deduplication, and overlay boundaries.
• Engineering and Verification Rules: connection invariants, code placement, abstractions, testing, performance, collaboration, and the pre-push documentation gate.

External research

• External Research and Trade-offs: reference scope, research method, and verified durable trade-offs; not a description of current behavior.

Inclusion rules

• The page is marked complete in the disposition checklist.
• The Chinese and English pages are complete counterparts with reciprocal links.
• The page has been checked against the code, tests, or build facts for its subject.
• It does not duplicate the same canonical details from another page.
• Research and handoff records identify their date and non-authoritative status.