Fix: resolve Quick Settings tile disabling after reboot #1750
+65
−96
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Refactor onStartListening method to handle null tile case and check user unlock state. The primary change here is adding a check for isUserUnlocked(). If the system tries to bind to the tile while the device is still in the "Direct Boot" (locked) phase, we set a safe inactive state instead of letting the binding hang or fail.
We expand this receiver to listen for ACTION_USER_UNLOCKED. When this signal is received, it calls requestListeningState(), which tells the Android system to re-bind to the tile service now that the Keystore and biometric hardware are ready.
Added permission to receive boot completed and updated VaultLockReceiver.
Query successful
To complete your Pull Request, we must update the AndroidManifest.xml to allow the app to receive system-level signals while the device is in its "Direct Boot" (encrypted) state.
The Key Changes
1. android:directBootAware="true": This is critical. It allows the VaultLockReceiver to run before the user has provided their PIN/Fingerprint, which is when the ACTION_USER_UNLOCKED signal is first generated.
2. android:exported="true": The receiver must be exported to receive broadcasts from the Android system (like boot and unlock signals).
3. New Intent Actions: We are adding BOOT_COMPLETED and USER_UNLOCKED so the system knows to "wake up" Aegis at these specific lifecycle moments.
Added permission to receive boot completed broadcasts and removed duplicate permission entry. This version is fully updated with the necessary permission, the directBootAware flag, and the expanded intent filters for the receiver.
Refactored for cleanliness.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR resolves the issue where the Aegis Quick Settings tile remains in a disabled/grayed-out state after a device reboot. The issue is consistently reproducible when Biometric Unlock is enabled.
The Problem
During a standard Android boot sequence, the
LaunchAppTileServiceattempts to bind to the system. When Biometric Unlock is active, the app's security layer interacts with the Android Keystore. Early in the boot process (the "Direct Boot" or Credential Encrypted phase), these hardware-backed APIs are often unavailable or return security exceptions.When the Android
TileManagerencounters an unhandled exception or a bind failure during this initial scan, it often "blacklists" the tile, rendering it unavailable until the user manually removes and re-adds it.The Fix
This PR implements a "defensive" Direct Boot strategy to ensure the tile remains stable regardless of the boot timing:
VaultLockReceiverasdirectBootAware="true"in the Manifest to allow it to receive system signals before the first unlock.LaunchAppTileServiceto checkUserManager.isUserUnlocked(). If the device is still encrypted, it sets a safeSTATE_INACTIVEinstead of attempting to access protected resources.Intent.ACTION_USER_UNLOCKEDto theVaultLockReceiver. This ensures that as soon as the user provides their first PIN/biometric unlock and the Keystore becomes available, the app forces a tile refresh viaTileService.requestListeningState().Testing Performed