* In Android V, we can add qs as one of the accessibility shortcut option to be more discoverable.
Bug: 338327560
Flag: EXEMPT bugfix
Test: check shortcut option in hearing devices settings page
Change-Id: I60d4da2432605a5369eb87c1e594539d40c53ae8
Revert submission 27019285-ACTION_NETWORK_PROVIDER_SETTINGS
Reason for revert: b/338527563 CL seems to be introducing jank for systemui tests somehow, reverting to get out of the way
Reverted changes: /q/submissionid:27019285-ACTION_NETWORK_PROVIDER_SETTINGS
Change-Id: I48bc0f4efc22dbff9f983b4606442b3ebd6d584c
On Android V and newer, the PDB will no longer wipe itself on start,
even if OEM Unlocking is enabled, so trusted factory resets must
wipe it.
Bug: 336362291
Flag: EXEMPT bugfix
Test: atest & manual testing
Change-Id: I67cc0fc3e7470c5ddddd03d23942706345361f8f
Add unit tests for the updating of the Settings
Page for the Avalanche
visual and auditory Suppression.
Bug: 330606963
Test: PoliteNotificationGlobalPreferenceControllerTest, PoliteNotifWorkProfileToggleControllerTest
Flag: com.android.server.notification.polite_notifications
Change-Id: I8a84f688eb0b3981fbb0fdb699755b4601583702
Update the Settings Page for the Avalanche
visual and auditory Suppression.
Bug: 330606963
Test: PoliteNotificationPreferenceControllerTest
Flag: com.android.server.notification.polite_notifications
Change-Id: I60b64a0c00cafb22ac1db74285002862affb82d2
Currently we fire ALL_APP intent for System Launchers at the
end of PS setup flow, even when the system launcher (NexusLauncher)
was not the default Launcher.
In such cases, the user is moved to NexusLauncher, but they cannot
unlock PS (only default launcher can do it), leading to crashes.
To fix this, we do not fire the intent in case non system Launcher
has the HOME role.
Bug: 331722929
Test: Manual build and flash
Flag: NA
Change-Id: I77353474cc74028d72508c433c89b6116b4148bd
- Set SnapshotTimeMs initial value to unknown
- Reserve height for DataUsageSummaryPreference
Bug: 341234382
Test: manual - on Mobile Settings
Change-Id: I9145f666c5f8fd9595bcc047160fd6da17b3091d
Also fixed a handful of style issues / warnings along the way.
Fixes: 341950853
Fixes: 341910620
Test: atest com.android.settings.notification.modes
Flag: android.app.modes_ui
Change-Id: I65900941fcdf53824caf052fd0a24401c1bfb476
This reverts commit 25ef484675.
Reason for revert: I don't think the UI update will impact the codec test in b/342336993, which should be the false alarm. The codec test even not relative to the accessibility function.
Change-Id: I4c2e00667f229d8df8664e8cef5bee06f4468fdc
This reverts commit 1d134d6665.
Reason for revert: <Potential culprit for b/342336993 - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.>
Change-Id: Ifa208bbc77fc4f49b6465fd68d9a18e31d1d3254
As per GSMA specification TS37, below Primary IMEI requirements are mandatory to support
-TS37_2.2_REQ_5
-TS37_2.2_REQ_8 (Attached the document has description about this test cases)
Bug: 341006304
Test: atest MobileNetworkImeiPreferenceControllerTest
Change-Id: I839440de7d2680d21832dce6d0d56db992796fca
