1. When a user taps the notification body, it should function like clicking the "Open Settings" action button, taking them directly to the Settings page and the notification should disappear automatically.
2. To ensure the notification remains visible until the user interacts with it, we need to add the FLAG_NO_CLEAR flag. This will prevent the notification from being dismissed when the user uses the "Clear all" button in the notification shade.
Bug: 385794406
Flag: com.android.graphics.hwui.flags.high_contrast_text_small_text_rect
Test: manual
Change-Id: Ie2cd17e744363b9834021ddef48ec5a59f19ec64
These strings may be replaced again after our UX Writing team provides
new strings for the final public release.
Bug: 384791485
Test: observe new strings; see http://b/384791485#comment2
Flag: EXEMPT strings changes
Change-Id: I5359bc3d6faca84238fe00801a5d68e5ef8ffc2f
This logic is triggered by two scenarios:
(A) During first bootup after OTA update to Android 16, if the
user had HCT enabled.
- Trigger: ACTION_PRE_BOOT_COMPLETED.
- Migration: HCT is disabled and notification is shown.
(B) Restore backup from Android 15 (or earlier), if the backup
had HCT enabled and new device does not.
- Trigger: SettingsProvider's restore process.
- Migration: HCT is not restored and notification is shown.
We store whether the user has seen this notification in a new secure
setting ACCESSIBILITY_HCT_SHOW_PROMPT. This setting is also backed up.
Bug: 369906140
Flag: com.android.graphics.hwui.flags.high_contrast_text_small_text_rect
Test: atest SettingsRoboTests:com.android.settings.accessibility.HighContrastTextMigrationReceiverTest
Test: flash an incremental update on a build with HCT enabled;
observe HCT is disabled and a notification is sent.
Test: flash an incremental update on a build with HCT disabled;
observe no change to HCT and no notification.
Change-Id: I4d294ffc0b2eabc59ee7988a579d678975a16380
