Settings and maintenance
About 1372 wordsAbout 5 min
Settings provides Feature controls, App Profile templates, SuperKey, UTS View, logs, and uninstall tools. The table below lists what each item changes and when it takes effect.
Configuration
| Entry | Purpose | Timing and requirements |
|---|---|---|
| App Profile templates | Sync online templates, create/edit local templates, and import from or export local templates to the clipboard | Affects a UID only after its profile selects the template |
| Feature controls | 13 Features: 0–4, 6, and 101–107, including su modes, Kasumi, and mount view cleanup | For each item's timing, see Feature controls |
| Do not store SuperKey | Deletes a saved key and prevents future automatic storage | Manager storage only; does not remove the verifier from an LKM |
| Authenticate SuperKey at boot | Makes one saved-key attempt after user unlock and BOOT_COMPLETED | Requires app autostart permission; no retry on failure |
| Clear SuperKey | Deletes manager-stored plaintext and disables automatic authentication | Does not rotate or revoke the LKM's SuperKey |
| Unmount modules by default | Default non-root unmount policy for apps without an explicit profile | Applies to later app starts and still requires Kernel Umount Feature |
| UTS View | Original/effective identity plus runtime, denylist, and early-boot templates | See UTS View |
| Built-in mounting | Uses the integrated Kagami engine to plan module mounting | Enabled by default; requires a full reboot; external mount owners take precedence, see Kasumi |
Online App Profile templates come from the KernelSU template service and are read-only in the page. Local templates can be edited and exported. Review UID, capabilities, SELinux rules, and namespace before applying either kind.
App settings
Update checks
- “Check for updates” controls stable-release checks when the app opens.
- “Check for CI updates” appears only while update checks are enabled. It is off by default and covers signed nightly Manager builds.
- An APK update does not flash the LKM or boot image. Sync device-side
ksudmanually, or enable automatic updates below.
Obtain stable builds from YukiSU Releases. See Update YukiSU for component update steps.
Automatic ksud update
This is off by default. When enabled, on a cold start, once the kernel recognizes the app as manager, it compares the actual APK-bundled libksud.so with /data/adb/ksud. On mismatch it atomically installs the bundled version through the manager's JNI/driver root channel and repairs tool links under /data/adb/ksu/bin.
With automatic sync off, tap the ksud daemon row on Home to inspect and sync manually.
Sync scope
This replaces device-side /data/adb/ksud and related links only. It does not flash the LKM or alter a boot image. Refresh Home afterward, confirm the daemon matches the APK, then test root and module functions.
WebUI engine
The choices are:
- automatic selection;
- force WebUI X; or
- force KSU WebUI.
Automatic mode selects WebUI X only when module configuration explicitly requests wx; an undeclared or unreadable preference uses KSU WebUI. Both engines run privileged content provided by modules. Open WebUIs only from trusted modules.
Auto jailbreak
This is configurable only while the current system is in late-load mode. After boot, when SELinux is detected as Permissive, the manager attempts an automatic Magica late-load bootstrap. App autostart permission is required.
It is not persistent installation and does not make SELinux Permissive. See Jailbreak mode for the actual prerequisites.
Soft restart instead of reboot
Disabled by default, this chooses soft reboot for completion buttons after module installation, update, enable, disable, or removal. Late-load mode prefers it when supported so the currently loaded LKM remains active.
v1.8.0 queries device-side daemon support, including Kasumi soft reboot when requirements are met. It waits for old Android services to exit, rebuilds mounts, restores hide rules, and starts Android. “Request accepted” means background work started. Return to Manager for the final completed, pending-rule, or failed state.
A new LKM, boot image, ImgPatch configuration, or early-boot UTS template still requires a full reboot. See Soft reboot for requirements, logs, and recovery. Android “Userspace reboot” in the power menu is a separate platform operation.
Tools
Logs and bugreport
“Send log” can save or share YukiSU_bugreport_*.tar.gz. When Superuser logging Feature is enabled, a usage-log viewer also appears with:
- current and historical log-file selection;
- search by UID, command, or details;
- event-type filters and exclusions for the manager/viewer refresh;
- raw records and paged loading; and
- clear-current-file or delete-history actions.
Clear and delete are irreversible. Preserve the original archive for a report instead of keeping only one filtered screenshot.
Unmount Path Management
This manages kernel module-unmount paths and flags (0 for normal unmount, 2 for MNT_DETACH). It can add, remove, clear custom paths, save, and apply the configuration to the running kernel.
Identify the mount to remove in the target app's mount namespace first. Entering a system mount that the app needs will remove its access to those files. Fully reboot after saving. “Apply configuration” updates the running kernel's list immediately, but existing apps still need to be fully stopped and restarted.
Uninstall YukiSU
Settings provides two flows:
- Permanent uninstall: enters the uninstall flashing flow.
- Restore stock image: attempts to restore the boot partition from a saved stock image.
Both modify the boot chain. Prepare stock images for the current firmware and target slot, and confirm that you can restore them through the bootloader or Recovery.
Maintenance from the Modules menu
The Modules menu also provides:
- Module compatibility settings: globally overrides the ksud version code, kernel version code, UAPI, and ksud version name exposed to module scripts. Disabled by default; blank or zero values use actual values and changes affect the next script execution. This cannot supply missing APIs.
- Module preinit: shows support, boot count, and module states. Repair the offending module before resetting the count; reset does not run preinit immediately.
- Mount filters and conflict checks: compares configured strategies, active Kasumi modules, and duplicate target paths.
These are distinct from dynamic-manager compatibility settings, which control version values returned to managers per APK signature. See App Profile, Boot configuration, and Kasumi.
More settings
Manager-display only
v1.8.0 consistently uses Material 3 Expressive and removes the Classic/Expressive selector. Language, light/dark theme, dynamic color, theme palette, app DPI, custom background, card opacity/dimming, and card visibility affect Manager presentation only.
Motion intensity offers Off, Soft, and Q Bouncy, with Q Bouncy as default. Page transitions offer Reveal and classic spring Slide, with Reveal as default. Changes apply to subsequent UI interactions without a device reboot.
More settings also offers predictive back gestures, disabled by default; this controls the return preview, not kernel behavior.
Simplicity and the corresponding hide options hide Working mode, Android version, Zygisk/MetaModule, or link cards from Home. Disable the relevant options before taking troubleshooting screenshots.
Advanced items that change live system state
- SELinux: directly runs
setenforce 1/0for the current boot; it is not persistent. Permissive materially weakens system isolation. - Allow any app as dynamic manager: only exposes “Set as dynamic manager” in every app profile. It does not trust every app automatically. Once granted, manager identity is more powerful than an ordinary root grant.
- WebView debugging / Eruda: shown only in debug APKs. Release builds remove these developer controls and the Eruda bundle.
See App Profile for dynamic-manager setup and permissions.
ksud integrity alerts
After boot, the ksud monitor watches the directory containing /data/adb/ksud. When the file is modified or atomically replaced, the manager rechecks it and reports differences from the APK-bundled version.
On an alert:
- record the bundled version, installed-side “Unknown/mismatch” state, and alert time; if
/data/adb/ksu/ksud-integrity.jsonis collected, retain its baseline/current SHA-256 and reason without executing the suspect daemon for a version; - review recently installed or updated root managers, scripts, and modules;
- sync the current APK's bundled daemon from Home details; and
- refresh daemon status and test root, modules, plugins, and YukiZygisk after syncing.
When using a custom-built ksud, install the APK from that same build. Files from different builds will trigger a mismatch alert.
Source references
Copyright
Copyright Ownership:Anatdx
License under:Attribution-NonCommercial-ShareAlike 4.0 International (CC-BY-NC-SA-4.0)