Livingstone utilities
Advanced Android tools with clear safety boundaries.
Explore the public utility layer for package inspection, activity discovery, workspace files, notifications, cleanup, and firmware context without hiding the risk lines.
Utility hub
Pick the tool that matches the job
Each utility page explains the user value, support evidence, policy boundary, and recovery-first workflow.
Inspect installed packages, understand app components, and prepare careful package actions with clear permission and root boundaries.
OpenActivity LauncherLivingstone utilityExplore exported activities and app entry points with intent-aware guidance, component context, and user-controlled launch actions.
OpenFile ManagerLivingstone utilityWork with boot animation sources, exported packages, previews, and support files while keeping scoped storage and sensitive paths clear.
OpenLive NotificationsLivingstone utilityKeep users informed about exports, long-running tasks, store review, support replies, releases, and maintenance without noisy or misleading alerts.
OpenAdvanced CleanerLivingstone utilityReview temporary CRYA files, failed exports, duplicate package artifacts, cache state, and cleanup candidates with a recovery-first posture.
OpenFirmware CheckLivingstone utilityCapture device, Android, One UI/build, resolution, boot media context, and root method notes to guide compatibility and support.
OpenSafety model
Use powerful tools in the right order
CRYA utilities should help users understand what is happening before they touch packages, files, activity launches, notification rules, cleanup actions, or firmware context.
Read package, file, device, or workspace context before making changes.
Show why a permission, root action, cleanup, or compatibility warning matters.
Keep recovery notes visible before destructive or system-adjacent actions.
Run only user-triggered actions with clear labels and feature gates.
Attach the right evidence when asking for help or submitting a pack.
Support evidence
Bring the details that shorten troubleshooting
The utility layer is also a support language: it helps users explain the device, package, file, and action state without posting private account data.
Package or app name, version, source, and the exact action you tried.
Device model, Android/One UI build, resolution, and root method if relevant.
Package Doctor notes, export report, screenshots, or preview state.
Whether the issue affects creation, install, Store submission, support, or notifications.
| App Manager | Package name, label, version, installer/source, component notes, and update state. |
|---|---|
| Activity Launcher | Target app, activity name, intent context, error message, and whether launch was user-triggered. |
| File Manager | Workspace path, file type, ZIP/frame structure, storage provider, and export destination. |
| Live Notifications | Android version, notification permission state, rule type, event source, and expected alert. |
| Advanced Cleaner | Cleanup category, selected files, backup status, and whether root/system paths were involved. |
| Firmware Check | Device/build context, Samsung/One UI notes, resolution, root method, and compatibility concern. |
Installed-app visibility, file access, notifications, and cleanup should be useful, explainable, and user-triggered.
System, package, and firmware-adjacent actions need backups, recovery notes, and admin-controlled feature gates.
Package names, activity names, device/build details, screenshots, reports, and app versions make support faster.
The website can explain tools, but remote gates, admin permissions, and risky-action switches stay in Mission Control.