English · 简体中文
Previously FCM Guard. Package identity, signing certificate and upgrade data are retained.
Version 3 refocuses this HyperOS tool on the apps whose notifications matter to you. The dashboard, system-list reader, component scan, app settings links and Quick Settings entry work without Shizuku authorization. No whitelist writes, persistent notification, foreground service, background periodic polling, wake lock, or scheduled wakeup is used.
- View the recent automatically read GMS connection state. Open Google Play services’ FCM diagnostics using the fixed home-screen button when needed; returning resumes automatic checks without a recording or confirmation dialog.
- Choose your notification apps from launchable apps, including those without detected FCM/GCM declarations. Components establish capability, not a working token, actual message route or guaranteed delivery.
- Inspect Autostart, read-only
MILLET_NO_RESTRICT_APPmembership, Android notification permission, stopped flag and AOSP Doze exemption. Unknown is distinct from enabled. Notification master switches/channels, in-app mute settings and recents locking require review where a supported query is unavailable. System-list membership and the HyperOS UI's complete battery policy are not treated as interchangeable. - Open the exact selected app’s notification, battery or app-details settings. Unsupported checks retain explanatory text and settings links without checkboxes or result recording.
- Add the Quick Settings tile. Visibility starts checks; tapping attempts a rate-limited heartbeat request and opens GMS diagnostics. A network probe or broadcast does not certify reconnection. With app diagnostic access (granted once through Shizuku or ADB), or optional running Shizuku, the tile reports current GMS service state: lit/Connected, grey disconnected icon/Disconnected, or a question mark/Unknown. Unknown stays clickable for diagnostics and never means off.
The daily settings show independent diagnostic access and its one-time Shizuku grant action. Manual ADB instructions and fallback Shizuku controls live under collapsed Advanced options. Once independent access is ready, the old enhancement mode is disabled and hidden; the app releases its own helper and does not reconnect it for normal checks. Temporary setup is released on cancellation, completion, expiry or leaving a destroyed activity; interrupted setup is cleared on the next process start. Existing diagnostic grants and selected apps are retained.
Start Shizuku through wireless debugging, connect and authorize it in the app, then tap Grant once through Shizuku and confirm the diagnostic permission explanation. The helper grants DUMP, PACKAGE_USAGE_STATS and the usage AppOp only to this package in the verified Binder caller profile. The app verifies its own access before showing success. It can then read current GMS state without a running Shizuku; no computer is needed for this setup path. Manual ADB instructions remain available.
Optional one-time ADB grants let the app read current GMS service state using its own UID, even after wireless debugging and Shizuku stop. The dashboard distinguishes this source from the independent Shizuku status. Permission/AppOp loss clears evidence; unsupported reads remain Unknown. No persistent notification, foreground service or hidden polling was added. See grant/revoke instructions and validation limits.
The signed APK is 1.55 MiB, 72.8% smaller than 3.1.3, using R8 and resource shrinking with verified Shizuku helper entry points. RecyclerView recycles visible app rows and applies diffs; disabled apps retain their priority, red text and counts. Component metadata is cached on demand, while mutable policy/permissions are reread when returning to the app. List mode, advanced expansion and position survive recreation.
All 105 Traditional Chinese application strings are complete. App data is explicitly excluded from cloud backup and device transfer. Application/test dependencies are locked and CI actions use immutable commits. Validation includes 35 device tests on each Android 17 image, actual minified-helper queries and real Shizuku authorization/64-bit binding. Use the HyperOS 4 phone checklist for OEM settings and locked-screen delivery.
Long-press the FCM Guard launcher icon and choose FCM diagnostics to open Google diagnostics directly. This is a native Android app shortcut, with menu styling supplied by the launcher and no Shizuku/extra permission requirement. Cold launches and existing activities use the same diagnostic routing without a recording prompt on return.
Fixed stale callbacks/results, helper lifecycle and recovery-request handling; bounded duplicate refresh work; reduced per-app scan overhead; removed obsolete socket/repair resources and strengthened release verification. Full audit and follow-up decisions.
Remove diagnostic recording, the confirmation dialog on return, historical user-reported connection state and per-app confirmation checklists. Upgrades clear old records and pending-dialog flags while retaining selected apps, Shizuku preferences, themes and request rate limits. Connection status comes only from automatic reads; unreadable state stays unknown.
Only a successful read of the correct profile and current GMS connection fields supplies Connected/Disconnected. Historical events, reachability, sockets and authorization cannot light the tile. The dashboard and tile share the same snapshot.
Reads refresh every five seconds only while the dashboard or quick-settings panel is visible. Hidden surfaces stop their refresh callbacks. Verdicts expire after 15 monotonic seconds and invalidate immediately on network, authorization or helper changes. Hiding the panel clears its lit state so SystemUI cannot cache a stale connection claim. Tapping still checks, attempts a heartbeat and opens diagnostics; it does not turn off GMS push.
The private GMS dump format can change. Denied, unavailable, unsupported or timed-out reads remain Unknown. Permission-free mode retains the diagnostic shortcut; automatic connection indication needs optional diagnostic access through ADB or Shizuku.
Off by default, even after upgrading an older authorized installation. Enabling it explicitly allows fixed, read-only helper operations: read the system projection and current GMS push-service state for the correct user. Connection indication no longer depends on restricted socket UID enumeration. A separate, explicit consent action may grant this application its diagnostic permissions once. That operation verifies the Binder caller UID and exact package; callers cannot supply a target package, permission, command or profile. Other helper operations remain read-only, with no system-list or battery-policy writes.
While Android lets the app process run, system-list and network callbacks refresh checks. Process freezing/reclamation can interrupt them until the tile or app is opened. There is no claim of continuous offline detection, permanent Connected state, or guaranteed delivery for Twitter/X, Telegram, Slack or other apps. Network/VPN conditions, Google services, platform delivery, notification channels and app-specific policies all matter. Telegram variants can use their own connection.
AGP 9.5.1, SHA-256-verified Gradle 9.9.1, JDK 21 / Java 17, compile SDK 37.2, target API 37, minSdk 24. Official Material Components 1.14.0 and Material 3 Views; language follows the system. ABI-neutral DEX supports 64-bit devices without dummy native libraries. Only Android 17 images are used for device CI. See BUILDING.
Releases attach one signed FCMGuard-HyperOS.apk; previews/test reports stay in CI and checksums are included in release notes. The signing key is unchanged from v2.x.
Based on ReedGAOOO/FCMGuard-HyperOS. System-policy research: dingwen07/hyperos-fcm-fix. MIT, see LICENSE.