Android app · Utility

FrozenDroid

Android utility focused on app/device control and cleaner performance routines.

Get it on Google Play ↗ Source on GitHub ↗

FrozenDroid is a no-root Android utility for reviewing, freezing, and restoring installed packages that waste battery or run unwanted background services. It is built for Android power users who want Shizuku-assisted package control, offline safety guidance, reusable freeze profiles, and CPU wake telemetry without sending app data to a backend.

No hosted demo is configured. The repository includes generated Google Play assets for reviewing the current app experience.

Project Overview

FrozenDroid helps users make safer package-management decisions on Android devices with OEM, carrier, or social-app bloatware. The app combines a local package inventory, an offline safety directory, protected-package rules, profile workflows, and telemetry views so users can disable noise while avoiding core system components.

This folder contains the Android app. In the parent workspace, the Netlify-ready privacy-policy site lives in ../FrozenDroid-pv/.

Key Features

• 🧊 Freeze and unfreeze packages through Shizuku-backed pm disable-user and pm enable commands.
• 🛡️ Block dangerous system packages with a hard-coded safety policy before command execution.
• 📚 Load an offline bloatware catalog from bloatware_db.json with safety levels, reasons, and affected features.
• 🔎 Refresh installed-package inventory, including disabled packages, into a local Room database.
• 👤 Save user safety overrides and profile state with Room and DataStore.
• 📊 Parse CPU wake telemetry to help identify packages that keep waking the device.
• 🧭 Provide built-in Shizuku privilege-state handling and setup guidance when access is degraded.
• 🏪 Generate Google Play screenshots, an app icon, and a feature graphic with Roborazzi-backed tests.

Architecture Overview

Components

Request And Data Flow

1. Compose screens call ViewModel actions for package refresh, freeze, unfreeze, profile, or telemetry operations.
2. ViewModels delegate to domain use cases such as FreezeAppUseCase, UnfreezeAppUseCase, and MonitorCpuWakeUseCase.
3. Use cases validate safety through FreezeSafetyPolicy before a package-changing command runs.
4. Repositories combine local Room rows, user overrides, and the static bloatware catalog into app-facing models.
5. CommandExecutorImpl prefers a live Shizuku binder and falls back to the configured ADB mode when selected.
6. WorkManager workers run background freeze, profile-switch, and CPU-monitoring work.

Design Patterns

• Clean Architecture-style layering separates UI, domain logic, data access, and Android framework integrations.
• Repository interfaces keep ViewModels and use cases independent from Room, assets, and shell execution details.
• Hilt provides application, database, executor, and repository dependencies.
• StateFlow/DataStore streams keep UI state reactive and local-first.

Tech Stack & Libraries

Configuration

Runtime user preferences are stored in DataStore under frozendroid_settings. Package inventory, profiles, telemetry events, and safety overrides are stored in the Room database.

Usage / Quick Start

Build And Install The Android App

./gradlew assembleDebug
./gradlew installDebug

After installing, start Shizuku on the target device and open FrozenDroid. The app listens for Shizuku binder availability and records the privilege mode as SHIZUKU, ADB, or DEGRADED.

Freeze And Restore A Package

val blocked = FreezeSafetyPolicy.blockReason("com.android.systemui")
check(blocked != null)

val result = commandExecutor.freeze("com.samsung.android.bixby.agent")

The app validates package names and protected-package rules before it calls pm disable-user --user 0 <package> through Shizuku or the selected ADB flow.

Generate Play Store Assets

./gradlew generatePlayStoreAssets

API Reference

Not applicable. This repository does not expose an HTTP API, public SDK, or CLI. Package operations are internal Android app flows backed by Shizuku, ADB-mode shell commands, Room, DataStore, and WorkManager.

Internal Command Surface

Testing

Run commands from this Android app directory:

./gradlew testDebugUnitTest
./gradlew connectedDebugAndroidTest
./gradlew generatePlayStoreAssets

| Coverage | Not configured | No JaCoCo/Kover setup is present. | | End-to-end tests | Not configured | No dedicated e2e suite is present. |

Current naming convention uses descriptive Kotlin test classes such as FreezeSafetyPolicyTest, ShizukuPrivilegeModeTest, and BatterystatsWakeParserTest.

Deployment

Android Debug Builds

./gradlew assembleDebug

Debug APK output is produced under app/build/outputs/apk/debug/.

Android Release Builds

KEYSTORE_PATH="$HOME/keystores/frozendroid-upload.jks" \
STORE_PASSWORD="$FROZENDROID_STORE_PASSWORD" \
KEY_PASSWORD="$FROZENDROID_KEY_PASSWORD" \
./gradlew assembleRelease

Release signing expects an alias named upload unless KEY_ALIAS or key.properties overrides it. Minification is currently disabled for the release build type.

Google Play Assets

./gradlew generatePlayStoreAssets

Docker And Health Checks

Not applicable. The repository does not include Docker or docker-compose files. The Android app has no server health check.