Subsystem Integration Guide

Subsystem Integration Guide

中文

This is the stable entry point for adding or changing a subsystem. It does not duplicate implementation details from subject pages. Determine capability ownership first, then follow the canonical topic.

Read by task

• Connection transports, USB, or wireless: ADB, USB, and Wireless and ADB Connection Lifecycle.
• Pairing, mDNS, and Wireless Debugging: Device Pairing and Wireless Debugging.
• Session configuration, candidates, and runtime resources: Session Configuration and Connection Lifecycle.
• Server, sockets, metadata, and cleanup: Runtime Main Path.
• Events, state, and diagnostics: Session State and Events.
• Codec selection and fallback: Encoding and Decoding.
• Shell and common events: Event System and Shell Integration (Chinese; bilingual audit pending).
• Logs and sampling: Logging System and Maintenance and Events, Monitoring, and Shell Integration.

Pages not yet listed in the Technical Documentation Index are still under audit and must be verified against code before use.

Definition of done

• Ownership is clear: user scenarios live in feature, technical capabilities in infrastructure, and stable shared models and rules in core.
• Success, failure, cancellation, and closure all have complete paths, with resource creation and reclamation under the same lifecycle boundary.
• Changes to session facts use the formal event, state, and component snapshot instead of a new global boolean.
• User configuration, detected capabilities, connection candidates, and current-run results do not overwrite one another.
• Logs include correlatable session, device or transport, phase, and structured failure category without exposing pairing codes or private material.
• Automated tests cover key protocol and policy constraints. Device-dependent behavior has a separate manual acceptance matrix.
• Canonical Chinese and English wiki pages are updated together; unstable concrete values are not copied into this entry page.