You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Automatic settings restore: Kernel configurations (CPU, GPU, RAM, Storage) are automatically re-applied after every reboot when enabled.
10-second countdown notification: A foreground notification with a progress bar counts down before applying, giving users time to intervene.
Per-category toggles: Each section (CPU, GPU, RAM, Storage) has its own "Apply on Boot" toggle — enable only what you need.
BootApplyService: New foreground service started by BootReceiver on ACTION_BOOT_COMPLETED that applies all enabled settings via the existing shell layer.
Binder-based detection: MKM can now detect and use Shizuku even when it is hidden via AppHider, Shelter, or similar tools.
New "Hidden" status: Settings → Access Method card shows "Shizuku (Hidden) — tap to grant" in amber when the binder is alive but the package is invisible to PackageManager.
Dedicated permission screen state: A new "Shizuku is Hidden" screen guides users to grant permission with a working Grant Permission button.
🔧 Bug Fixes
BootToggleCard text overlap: Fixed the subtitle text running underneath the toggle switch on narrow screens. Long subtitles now wrap cleanly without overlapping the Switch.
Battery wattage stability: Guarded estimated-time calculation against bad early data; deduplicated wattage reads between notification and overlay.
Wattage fallback: Added a fallback path for devices where the primary power sysfs node is unavailable.
📦 Technical Changes
New BootApplyService and BootSettingsManager for per-category boot persistence.
ShizukuManager.isHidden() — returns true when isRunning() is true but isInstalled() is false.
isAvailable() simplified to isRunning() (live binder is sufficient).