Boot Store
Compatibility Notes
Compatibility pages explain device context, resolution, QMG/Samsung limits, root method notes, preview behavior, and support evidence.
Public surface
Compatibility Notes
Compatibility should be honest and specific. Approved store visibility does not guarantee every device, firmware, root method, or QMG path will work.
Model family, Android/One UI build, resolution, density, and target path.
desc.txt, frame dimensions, fps, boot/shutdown folders, package report, and hash.
Magisk/KSU/system path notes, backups, uninstall route, and recovery plan.
Reports and ratings can improve labels when verified.
| Label wording | Use tested on, expected for, unknown, or not supported instead of universal claims. |
|---|---|
| Samsung/QMG | QMG behavior can vary by firmware and toolchain; link to QMG docs for limits. |
| Store review | Reviewers should reject or edit misleading compatibility claims. |
| Support | Compatibility failures should include device/build, package report, app version, and exact steps. |
Workflow
How this should work
A public page should explain the user path while protected state, permissions, and audit trails stay in CRYA Mission Control.
Check model, resolution, path, and known limits.
Use the app preview and Package Doctor before device-level steps.
Prepare recovery before root/system testing.
Send verified evidence to improve future labels.
Related surfaces
Continue the journey
Move between public discovery, creator guidance, store trust, and support evidence without exposing private admin systems.