CleveresTricky

Custom properties

Custom Properties applies user-defined system properties after templates and build values, so a single problematic property can be overridden without changing the whole template.

Where to find it: Identity. Where is each feature?

What to do

  1. Enable the required identity control on Dashboard, then configure its values in Identity.
  2. Save the change and follow any reboot indicator.
  3. Keep unrelated controls off.

Details and limits

It is off by default, has its own toggle, is device-wide, and is never part of app profiles.

File format

The custom_props file holds one KEY=VALUE entry per line. Blank lines and # comments are ignored. Property names use 1-127 characters from A-Z a-z 0-9 . _ : @ - with no leading or trailing dot, and never target ctl.* control properties. Values use 1-91 printable characters.

The file accepts at most 256 entries within 64 KiB. A file with an invalid line applies nothing.

Scope

Entries override template and build values. Values set through the property service live in memory only and return after a reboot unless re-applied at boot. Enabled Custom properties are applied device-wide during early boot. Reboot after changing them.

Limits

Editing custom_props never changes module verification: the live file lives in the configuration directory, outside the verified module tree. Custom properties cannot relax hardware attestation, Verified Boot, or Keystore trust roots.

Zygisk is optional for the module. While Identity is enabled on Dashboard, Global Identity stays enabled and cannot be turned off separately. Enabled Build, Region and Custom properties apply device-wide; disabling Identity disables these changes. Zygisk is recommended for app-specific Identity profile overrides. Security Patch remains independent.

Back to all guides

The same ZIP installs the optional CleveresTricky Identity (Optional Zygisk) companion as a separate module. The core module never requires Zygisk. Without an active provider, the companion starts disabled; enable Zygisk and then enable the companion in your root manager for app-specific overrides. Companion disable choices survive updates. Removing the core removes its companion, and a disabled, removed or mismatched core prevents companion hooks.