Profiles
Profiles apply a coherent group of optional settings in one transaction.
Where to find it: Profiles. Where is each feature?
What to do
- Create a named profile, choose its template, keybox, privacy and patch settings, then assign apps and activate it.
- Inspect Effective State.
- Default also resets target files and removes remote servers.
Details and limits
Named profiles store app assignments, template and keybox references, privacy mode, independent System/Vendor/Boot patch rules and optional feature overrides. They do not embed private keys. Invalid changes leave the previous valid policy active; exact assignment conflicts are rejected.
| Setting | Result |
|---|---|
| Daily Compatibility / Default | Targeted optional identity setup; build and telephony off; automatic keybox checks on; DRM passthrough retained. |
| Maximum Compatibility | Global Mode, build identity, refresh and telephony on; DRM passthrough off. Use for focused testing. |
| Minimal | Optional identity and scheduled keybox checks off; genuine DRM passthrough retained. Core protection remains active. |
Default or Restore Defaults resets
target.txt,identity_target.txt,drm_packages.txt,boot_props_modeandpolicy_state_v2.json; it removes all Remote Servers and their cached keyboxes. Stored local keyboxes and encrypted backups are preserved. Back up first; reboot after early-boot identity changes.