-
Notifications
You must be signed in to change notification settings - Fork 3
Modernization
Sensitivity is the sole maintained product and repository. MiAssistantFork has been consolidated into it, not retained as a parallel implementation or compatibility layer.
The working direct-USB, validation, and sideload behavior remains authoritative. Both sensitivity and sensitivity-gui consume that one library implementation.
A new user can download one archive, connect a phone in Connect with Mi Assistant recovery mode, and use either a guided GUI or the scriptable CLI without installing Rust, Android platform tools, or Xiaomi desktop software.
Both interfaces must leave unrelated ADB processes alone unless explicitly requested otherwise, display destructive actions and require explicit confirmation, validate packages before sideloading, support cancellation without inventing an unverified resume protocol, and avoid exposing validation tokens or device serials in normal logs.
- The root
sensitivitylibrary owns USB discovery, ADB framing, Xiaomi commands, validation, download, and sideload. - The root CLI owns commands, prompts, diagnostics, JSON output, supervised progress and cancellation events, completions, and automation behavior.
-
apps/windows/Sensitivity.WinUIis the native Fluent Design 2 / WinUI 3 presentation layer and supervises the CLI backend without receiving validation tokens. -
crates/guiis the portable Linux/macOS presentation layer and calls the same library operations. - Release archives contain both front ends, documentation, and platform setup files.
See MAF consolidation for the disposition of MAF-specific features.
CI and offline tests prove compilation, parsing, framing, validation helpers, packaging, and front-end integration. Do not describe a release as hardware-validated until representative real devices have exercised detect/info, normal flash, server-required wipe, cancellation, failure reporting, and reboot. Record sanitized logs without serials or validation tokens.