Feature shape
Activity Launcher
Activity Launcher should feel like an inspection and troubleshooting tool, not a promise that every hidden screen is safe or supported. Public pages should explain exported activities, intent context, and app ownership limits.
Discover activity names, exported state, labels, package ownership, and launchable entry points.
Start visible/exported surfaces when Android permits it and explain when the system blocks access.
Useful user-facing entries can become app-local shortcuts where supported.
Private activities, protected permissions, and vendor-only screens may fail or behave unexpectedly.
| Best use | Find app settings screens, testing surfaces, exported activities, and component names for support. |
|---|---|
| Compatibility | Android version, manufacturer changes, exported flags, and permissions affect whether launches work. |
| Safety | Do not encourage users to force private components or bypass app protections. |
| Evidence | Package name, activity name, Android version, and exact error help support explain failures. |
| Admin boundary | Remote gates can hide or pause advanced launch features when policy or device risk changes. |
User workflow
How this utility should feel in the app
A CRYA utility should be useful, explicit about risk, and connected to support evidence when something fails.
Open the package entry from App Manager or search.
Check label, component name, exported state, and permission notes.
Use Android-permitted entries and expect blocked private screens.
Create a local shortcut where supported.
Copy the component details when asking for help.
Related CRYA surfaces
Continue safely
Utility pages connect users to Toolkit workflows, docs, policies, and support without exposing protected admin controls.