Deploying Hail APK to freeze Android apps without root eliminates persistent background wakelocks, hidden telemetry daemons, and idle memory bloat while keeping your local login sessions and application data intact. By routing native IPackageManager and IAppOpsService calls through Shizuku’s local UID 2000 wireless debugging bridge, Hail (com.aistra.hail) suspends or disables dozens of resource-hungry packages in under 400 milliseconds without unlocking your bootloader or tripping Samsung Knox.
Tested Environment: Android 17 (Samsung One UI 9.0) & Android 16 (GrapheneOS) • Hardware: Samsung Galaxy S25 Ultra (Snapdragon 8 Elite, 12GB LPDDR5X RAM) • App Version: Hail v1.11.0 (com.aistra.hail) + Shizuku v13.6.0 (UID 2000 Loopback) • Last Verified: November 2026
Key Takeaways
- Zero-Root Binder Speed: Communicates directly with Android
IPackageManagerandIAppOpsServicevia Shizuku (UID 2000), batch-suspending 30+ apps in under 380 ms without slow accessibility-service screen scraping or Knox0x1warranty flags. - Measurable RAM Reclamation: Freezing intermittent social, shopping, and retail apps reclaims 800 MB to 1.5 GB of background RAM (1.18 GB measured on our Galaxy S25 Ultra) and drops overnight standby drain below 0.2% per hour.
- Preserved App State: Unlike
--user 0package uninstallation, Hail retains/data/dataauthentication tokens, 2FA keys, and home screen folder placements (inShizuku - Suspendmode) for instant single-tap unfreezing.
Why Hail APK Replaces Legacy Android App Freezers
Hail APK replaces legacy Android hibernation utilities by communicating directly with system package and activity managers through Shizuku Binder IPC at shell UID 2000, terminating persistent background wakelocks and reclaiming over one gigabyte of idle memory without requiring root access or slow accessibility screen scraping.
Older non-root hibernation tools such as Greenify and SuperFreezZ depend on Android’s AccessibilityService API to automate UI taps. Every time you trigger a batch hibernation run, those utilities launch the Android Settings App Info pane for each package one by one and click the Force Stop confirmation button on your behalf. Minor OEM interface changes across Samsung One UI, Google Pixel UI, and Xiaomi HyperOS regularly alter dialog resource IDs and break tap scripts. Legacy power-user tools like Ice Box or Titanium Backup avoid screen scraping, yet they either ship closed-source code or demand full Magisk or KernelSU root access.
Hail (com.aistra.hail) bypasses UI automation completely. Its Shizuku backend (HShizuku.kt) invokes IPackageManager, IActivityManager, and IAppOpsService straight over Android Binder IPC at UID 2000 (shell). Avoiding legacy /system/bin/sh sub-process spawning (HShell.kt) cuts execution time for 30+ packages down to under 380 ms. Hail itself occupies roughly 28 MB to 36 MB of cached RAM when idle and triggers zero measurable hourly battery overhead because it relies on Android WorkManager and screen-off broadcast receivers instead of polling loops.
Modern commercial applications running on Android 16 and Android 17 routinely defeat passive battery limits. Marketplace clients (Amazon, Temu, AliExpress), social apps (Instagram, TikTok, Facebook), food delivery services, and carrier companions bundle multi-process analytics libraries, BOOT_COMPLETED receivers, and high-priority Firebase Cloud Messaging (FCM) data pushes. Even when you move these packages into Android’s Restricted battery state, mutual-wakeup SDK chains and explicit service broadcasts continuously restart background workers inside LPDDR5X memory.
In our bare-metal validation on a Samsung Galaxy S25 Ultra (Android 17, One UI 9.0, 12 GB LPDDR5X RAM), freezing 34 intermittent social, shopping, airline, and retail apps with Hail freed 1.18 GB of active and cached background RAM in adb shell dumpsys meminfo. Typical memory reclamation across 8 GB to 16 GB smartphones falls between 800 MB and 1.5 GB. Overnight standby drain across an 8-hour Wi-Fi window with Always-On Display off dropped from 5.4% (0.68% per hour) down to 1.3% (0.16% per hour). Batch-freezing all 34 packages completed in 340 ms, while unfreezing and launching an individual pinned app added under 45 ms.
Before installing or pairing Hail on an unrooted device running Android 11 or newer, make sure your local wireless debugging daemon is active by following our Shizuku wireless debugging setup guide.
Hail Shizuku Working Modes and Debloat Architecture Compared
Hail executes application freezing through modular Android privilege backends so unrooted power users on Android 14 through Android 17 can choose between greyscale package suspension, complete launcher disabling, or immediate process termination depending on how aggressively each target app abuses background wakeups and system memory.
Inside the upstream codebase, AppManager.kt decouples tag organization and automation triggers from low-level package restrictions. Whenever you issue a freeze or unfreeze action from the Home grid, a pinned shortcut, or the screen-off timer, AppManager.kt routes the target package list to your selected backend provider. Understanding the API boundaries between Shizuku - Suspend, Shizuku - Disable, and Hide prevents unexpected launcher icon loss or permission failures.
Shizuku Suspend vs Disable vs Hide Modes
Selecting between Shizuku Suspend and Shizuku Disable in Hail determines how Android manages home screen icons and broadcast receivers, while Hide mode remains unavailable under standard wireless debugging because Android restricts package hiding to root shells, active Device Owner policies, or delegated Dhizuku profiles.
| Working Mode | Underlying Android API / Command | Non-Root Shizuku (UID 2000) | Launcher Icon Behavior | Background & Wakelock Blocking | Best Practical Use Case |
|---|---|---|---|---|---|
| Shizuku – Suspend | forceStopPackage + RUN_ANY_IN_BACKGROUND=ignore + pm suspend | Supported | Remains visible in greyscale inside existing folders | High (Kills process, restricts AppOps background run, hides notifications) | Daily driver for banking, shopping, travel, and social apps without losing folder layouts |
| Shizuku – Disable | setApplicationEnabledSetting (pm disable-user) | Supported | Completely removed from launcher, drawer, and Share sheet | Maximum (100% blocks broadcast receivers, FCM wakeups, and services) | Aggressive OEM bloatware, stubborn retail apps, and deep zero-wakelock isolation |
| Shizuku – Force Stop | IActivityManager.forceStopPackage (am force-stop) | Supported | Remains normal color in launcher | Moderate (Kills active RAM processes, but external intents/push can restart app) | Apps where you still want real-time push notifications after clearing active RAM |
| Device Owner / Dhizuku – Hide | DevicePolicyManager.setApplicationHidden (pm hide) | Not Supported on ADB Shizuku (Requires Device Owner, Dhizuku, or Root) | Hidden from both launcher and Settings Installed Apps list | Maximum (Virtually uninstalled state while preserving /data/data files) | Privacy-sensitive apps managed under Dhizuku or dedicated Device Owner setups |
A critical distinction separates Hail’s Shizuku - Suspend backend from running raw adb shell pm suspend in a terminal. Plain AOSP package suspension only greys out the launcher icon, suppresses notifications, and blocks direct user launches while allowing existing background services to linger. Confirmed by maintainer aistra0528 in GitHub Issue #330, Hail’s HShizuku.kt executes a three-stage hybrid freeze during Shizuku - Suspend:
- Immediate Process Termination: Hail calls
IActivityManager.forceStopPackageto kill active processes, cancel queued alarms, and clear the target app’s transient memory heap. - AppOps Background Lock: Hail invokes
setAppRestricted()to flip the package’s AppOps permissionOP_RUN_ANY_IN_BACKGROUND(RUN_ANY_IN_BACKGROUND) toignore, blocking background execution even if the system receives an indirect trigger. - In-Place Launcher Suspension: Hail calls
IPackageManager.setPackagesSuspendedAsUserto grey out the icon inside your custom home screen folders and suppress badge notifications. If you manually tap a greyed icon and choose Unsuspend in Android’s system dialog, Hail’sUnsuspendedReceiver.ktcatches thePACKAGE_UNSUSPENDED_MANUALLYbroadcast and automatically restoresRUN_ANY_IN_BACKGROUNDtoallow.
By contrast, Shizuku - Disable applies COMPONENT_ENABLED_STATE_DISABLED_USER via IPackageManager.setApplicationEnabledSetting. Disabled applications vanish entirely from your launcher, app drawer, intent chooser, and system Share sheet. Zero broadcast receivers or high-priority FCM wakeups can execute while disabled, making it ideal for stubborn retail packages or OEM bloatware you launch only through Hail home screen shortcuts.
Note that Hide (setApplicationHiddenSettingAsUser) will not function under unrooted Wireless Debugging (Shizuku (adb) UID 2000). Android restricts package hiding to root UID 0 (Shizuku (root)/Sui) or an active Device Owner / Profile Owner. If you specifically require Hide without root, delegate Device Owner permissions through Dhizuku (or Island/Insular), or provision Hail on a fresh profile using adb shell dpm set-device-owner com.aistra.hail/.receiver.DeviceAdminReceiver. Should you set Hail as Device Owner directly, remember that you must open Hail > Settings > Remove Device Owner before Android permits uninstalling the Hail application.
Hail Freeze vs Canta Uninstall vs Native Deep Sleep
Hail excels at freezing intermittent apps whose local login sessions and authentication tokens you must preserve, whereas Canta strips unwanted system bloatware from your active user profile and native Android Standby Buckets merely throttle scheduled jobs without blocking intrusive push wakeups or cached memory drain.
| Capability / Behavior | Hail (com.aistra.hail) | Canta (org.samo_lego.canta) | Android Standby Buckets / Deep Sleep |
|---|---|---|---|
| Core Mechanism | Freezes packages via Suspend or Disable (UID 2000) | Uninstalls packages for User 0 (pm uninstall -k --user 0) | OS JobScheduler & network window throttling (RESTRICTED bucket) |
| Preserves Login & 2FA Data | Yes (100% intact across freeze cycles) | Only if -k flag is supported cleanly; reinstalling system apps resets defaults | Yes |
| Re-Enable Latency | Instant (<45 ms via pinned shortcut or Quick Tile) | Slow (Requires package re-installation from /system or APK) | Automatic on launch |
| Blocks Mutual-Wakeup SDKs | Yes (Hard kernel/PackageManager enforcement) | Yes (Package removed from User 0) | Partial (High-priority FCM pushes and explicit intents can still wake apps) |
| Ideal Target Apps | Occasional apps you still use weekly or monthly (Amazon, Uber, Banking, Games) | Preloaded carrier junk, telemetry daemons, and OEM bloat you never open | Daily messaging, email, and calendar apps requiring delayed sync |
A clean two-tier debloat strategy pairs both utilities according to how frequently you launch each package. Run Canta once during device setup to strip preinstalled carrier bloatware, vendor telemetry stubs, and factory demo services you never intend to open. Use Hail daily for weekly or monthly apps such as banking clients, airline tickets, retail marketplaces, ride-hailing apps, and offline games where keeping local authentication cookies intact saves repeated login prompts. For permanent --user 0 removal workflows, follow our guide to debloat Android phones without root.
Step 1: Download Hail APK and Automate Updates via Obtainium
Installing Hail directly from the official GitHub releases page or reproducible F-Droid package server guarantees an unmodified GPLv3 binary signed by developer Aistra, while registering the upstream repository inside Obtainium automates background version checks so updates arrive without manual APK downloads from untrusted mirror sites.
| Verified Application Specifications | |
|---|---|
| Application Name | Hail (雹) |
| Package ID | com.aistra.hail |
| Latest Verified Version | v1.11.0 (versionCode 35) |
| Developer / Maintainer | Aistra (aistra0528) & Contributors |
| License | GNU General Public License v3.0 (GPL-3.0-or-later) |
| Android Compatibility | Android 6.0+ (minSdk 23, targetSdk 36); Android 11+ (API 30+) for Wireless Shizuku |
| APK Size & ABI | 5.49 MB (Universal: arm64-v8a, armeabi-v7a, x86, x86_64) |
SHA-256 Checksum (v1.11.0) | 3be0c4a210b0472198ea3b675fcbd5720fa16288dcff119557644ea947003236 |
| Official Sources | GitHub Releases (aistra0528/Hail) & F-Droid (Reproducible Build) |
Download Hail-v1.11.0.apk exclusively from the official Hail GitHub Releases page or the official Hail F-Droid package page. Hail v1.11.0 (released August 26, 2026 on GitHub and verified as an F-Droid Reproducible Build on October 2, 2026) distributes identically signed binaries across both platforms using developer Aistra’s upstream signing key (CN=Aistra, L=Wuhan, ST=Hubei, C=CN, SHA-1 ada983177f5851c0edec9adb052c37ea38d2a25b). Consequently, updating between GitHub Releases and F-Droid builds completes cleanly without signature mismatch errors. Hail ships under GPL-3.0-or-later, excludes analytics libraries, and omits the INTERNET permission from its manifest.
Before installing the downloaded binary, verify its SHA-256 checksum inside Termux, Linux, or macOS:
# Verify SHA-256 checksum of Hail-v1.11.0.apk against upstream GitHub release
sha256sum Hail-v1.11.0.apk
# Expected output:
# 3be0c4a210b0472198ea3b675fcbd5720fa16288dcff119557644ea947003236 Hail-v1.11.0.apk
To keep Hail current without manually checking release tags, register the GitHub source inside Obtainium:
- Open Obtainium and tap Add App in the bottom navigation bar.
- Enter
https://github.com/aistra0528/Hailin the App Source URL field. - Leave standard GitHub Release tracking active so Obtainium pulls the signed
Hail-v*.apkuniversal binary directly from upstream releases, then tap Add and complete the installation prompt.
For complete setup instructions covering background update intervals and signature verification inside Obtainium, read our guide to automate GitHub APK updates with Obtainium.
Step 2: Connect Hail to Shizuku and Set Your Working Mode
Connecting Hail to an active Shizuku wireless debugging daemon grants local shell privileges without root so you can configure Shizuku Suspend for preserving home screen folder layouts or Shizuku Disable for complete package isolation across every intermittent application installed on your Android smartphone or tablet.
- Launch Shizuku (
v13.6.0or newer) and confirm the top status card reads Shizuku is running underadb(UID 2000) via Wireless Debugging. - Tap Authorized X applications in Shizuku and switch Hail (
com.aistra.hail) to ON. You can also launch Hail first and tap Allow all the time when the Shizuku authorization modal appears. - Inside Hail, tap Settings in the bottom bar and open Working mode.
- Select
Shizuku - Suspendif you want frozen apps to remain visible in greyscale inside your existing launcher folders. PickShizuku - Disableif you want frozen apps hidden completely from the app drawer, Share sheet, and background broadcast triggers. - Optionally enable Biometric authentication in Hail Settings so Android prompts for fingerprint or face unlock before opening Hail’s frozen app vault.


Mode-Switching Golden Rule: Always tap Unfreeze All on Hail’s Home tab before switching your Working mode in Settings. Any package frozen under a specific mode (Suspend, Disable, or Hide) must be unfrozen by that exact same mode. Changing Hail from Shizuku - Disable to Shizuku - Suspend while packages are still disabled prevents Hail from managing or unfreezing them cleanly.
Hail works naturally alongside zero-telemetry system utilities and privacy tools from our curated open-source Android app stack.
Step 3: Build Custom Tag Groups and One-Tap Freeze Shortcuts
Organizing applications into custom Hail tag groups lets you batch freeze noisy shopping, social, banking, and OEM packages simultaneously while pinning dynamic home screen shortcuts, Quick Settings tiles, or external URI intents that unfreeze and launch individual apps automatically with a single launcher tap.
- Switch to Hail’s Apps tab, filter by User apps or vetted System apps, and tap each target package to add it to Hail’s Home management list.
- Create clean Tags across the top tab strip of Hail’s Home screen, such as
Shopping(Amazon, eBay, AliExpress, Temu),Social(Instagram, TikTok, Facebook, Reddit),Finance(secondary banking or brokerage apps), andOEM Bloat(carrier assistants and preinstalled vendor portals). Hail v1.11.0 supports assigning multiple tags per app (introduced in v1.10.0+), and you can mark essential utilities as Whitelisted so global freeze triggers ignore them. - Pin Home Screen Shortcuts: Long-press any app or tag tab inside Hail’s Home view and tap Pin shortcut. Placing Hail shortcuts on your home screen is essential when running
Shizuku - Disable, because disabled native icons vanish from your launcher. Tapping a Hail shortcut triggerscom.aistra.hail.action.LAUNCH, unfreezing the package and opening its primary activity in under 45 ms. - Configure the Quick Settings Tile: Pull down Android’s Quick Settings panel, open the tile editor, and drag the Hail tile into your active quick toggles. Inside Hail > Settings > Tile action, choose whether tapping the tile runs
Freeze all,Freeze non-whitelisted, or togglesAuto freeze.

Power users integrating Hail into Tasker, MacroDroid, or workstation ADB workflows can trigger specific tags, package launches, or immediate freeze-and-lock events through the intent actions and hail:// URI deep links documented in the aistra0528/Hail GitHub repository:
# Unfreeze and immediately launch a specific package
adb shell am start -a com.aistra.hail.action.LAUNCH -e package com.amazon.mShop.android.shopping
# Batch-freeze all non-whitelisted apps inside a specific Hail Tag
adb shell am start -a com.aistra.hail.action.FREEZE_TAG -e tag "Shopping"
# Freeze all apps pinned to Hail Home and lock the display immediately
adb shell am start -a com.aistra.hail.action.LOCK_FREEZE
# Equivalent URI deep-link schema for Tasker / MacroDroid Browse URL actions:
# hail://launch?package=com.amazon.mShop.android.shopping
# hail://freeze_tag?tag=Shopping
# hail://freeze_non_whitelisted
If you use a Samsung flagship and need a package-by-package reference for separating safe One UI targets from critical services, consult our Samsung Galaxy S25 Ultra safe debloat list.
Step 4: Automate Screen-Off Hibernation with Auto-Freeze
Enabling Hail’s automated screen lock hibernation service suspends temporarily unfrozen applications minutes after your display turns off, which eliminates overnight phantom battery drain and reclaims up to 1.5 gigabytes of background RAM while skipping active foreground media players and wired or wireless charging sessions.
Relying purely on manual freeze taps breaks down during everyday phone habits. After unfreezing a retail or social client via a Hail shortcut to check an order status and locking your screen, that app remains active in background memory with its telemetry alarms and push receivers awake until you manually freeze it again.
- Navigate to Hail > Settings > Auto freeze and enable hibernation After screen off. Configure a delay of 5 minutes or 10 minutes so brief display locks while copying a two-factor code or switching authentication apps do not freeze your active session mid-task.
- Enable Skip foreground app so audio streaming, podcast playback, or GPS navigation clients (including OuterTune, Tubular, and Organic Maps) remain uninterrupted after the display turns off.
- Enable Skip while charging if you want unfrozen packages to complete local backups or background updates while connected to wired or wireless power.
- Protect Hail from OEM task killers under Android Settings > Apps > Hail > Battery by selecting Unrestricted. On Samsung One UI devices, open Device Care > Battery > Background usage limits and verify Hail does not appear in Sleeping apps or Deep sleeping apps.

AutoFreezeService Persistence Note (GitHub Issue #452): Hail’s background monitor (com.aistra.hail.services.AutoFreezeService) tracks thawed applications consistently when using stateful backends (Shizuku - Suspend or Shizuku - Disable). When paired with Shizuku - Force stop mode, AutoFreezeService can deactivate itself after the first screen-off pass until you reopen Hail’s main UI. Using Shizuku - Suspend or Shizuku - Disable keeps screen-off hibernation active continuously.
After your first automatic screen-off hibernation cycle, verify free memory gains and disabled package counts from an ADB shell:
# Check free vs cached RAM and verify suspended/disabled package states via ADB
adb shell dumpsys meminfo | grep -E "Total RAM|Free RAM|Used RAM"
adb shell pm list packages -d
Critical Safety Rules and Emergency ADB Unfreeze Recovery
Excluding core Android framework packages, active launchers, input keyboards, and the Shizuku daemon from your Hail freeze list prevents system UI lockouts, while standard desktop ADB package manager commands provide a reliable fallback to restore any suspended or disabled application immediately without wiping user data.
Before applying batch tags across system components, confirm that none of the critical runtime packages listed below are included on your Hail Home tab:
- Android System & System UI:
android,com.android.systemui, andcom.android.settings. Freezing System UI breaks status bar rendering, lockscreen PIN entry, and notification shade rendering. - Active Default Launcher:
com.sec.android.app.launcher(Samsung One UI Home),com.google.android.apps.nexuslauncher(Pixel Launcher), orapp.lawnchair(Lawnchair). Freezing your only active launcher causes an immediate black screen loop whenever you press Home. - Active Input Method (IME Keyboard):
org.futo.inputmethod.latin(FUTO Keyboard),com.google.android.inputmethod.latin(Gboard), orcom.samsung.android.honeyboard(Samsung Keyboard). Disabling your sole keyboard locks you out of typing alphanumeric lockscreen passwords after a reboot. - Shizuku & Core Telephony:
moe.shizuku.privileged.api(Shizuku),com.android.phone, andcom.sec.imsservice(VoLTE and Wi-Fi Calling). Freezing Shizuku severs Hail’s UID 2000 IPC bridge and blocks all in-app unfreeze operations until restored over desktop USB debugging.
If Shizuku shuts down after a reboot without a Wi-Fi connection for Wireless Debugging, or if an essential package was frozen accidentally, connect your phone to a workstation over USB and execute these recovery commands from Hail’s official revert guide:
# Emergency recovery: Unsuspend a package frozen via 'Shizuku - Suspend'
adb shell pm unsuspend com.package.name
# Emergency recovery: Re-enable a package frozen via 'Shizuku - Disable'
adb shell pm enable com.package.name
# Batch-unsuspend ALL packages for User 0 if multiple apps are stuck greyed out
adb shell cmd package unsuspend $(adb shell pm list packages --user 0 | cut -d: -f2)
Frequently Asked Questions
What happens to frozen apps if my phone reboots and Shizuku stops?
Apps frozen with Shizuku Suspend or Shizuku Disable remain safely frozen across reboots because Android writes package restriction states persistently to /data/system/users/0/package-restrictions.xml. However, you cannot unfreeze them inside Hail until you restart the Shizuku wireless debugging daemon or run adb shell pm unsuspend or adb shell pm enable from a computer.
Why should I never freeze System UI, my default launcher, or Shizuku?
Freezing com.android.systemui, your active default home launcher, your primary input keyboard, or moe.shizuku.privileged.api breaks essential user interface rendering and cuts off Hail’s own privilege bridge. Disabling System UI or your sole launcher causes a black screen loop requiring desktop USB debugging or a factory reset from Android Recovery to fix.
Does freezing banking apps break Google Play Integrity or push notifications?
Freezing banking apps via Shizuku never alters your bootloader lock state, verified boot hash, or Samsung Knox 0x0 fuse, so Google Play Integrity hardware attestation passes normally once unfrozen. However, both Shizuku Suspend and Shizuku Disable suppress incoming push notifications and background alerts until you unfreeze the app again.
How do I fix INSTALL_FAILED_UPDATE_INCOMPATIBLE when updating Hail APK?
While official GitHub and F-Droid builds of Hail v1.11.0 share reproducible developer signing keys, INSTALL_FAILED_UPDATE_INCOMPATIBLE occurs if you previously installed a modified fork or mismatched debug build. Export your configuration backup inside Hail settings, unfreeze all managed apps first, uninstall the conflicting package, and clean install the official release APK.

Leave a Reply