Files

jasonwshsu e08c1a5f92 Flash Notifications color dialog crashs if configuration changes

Root Cause:
When configuration changes, it will recreate fragment then call no args constructor which lead to null pointer exception for error passing parameters in getInstance().

Solution:
* Use setArguments() to pass parameters.
* Move settings key update action into fragment.
* Obsever settings key changes to update summary accordingly.

Bug: 349049233
Test: atest ScreenFlashNotificationColorDialogFragmentTest ScreenFlashNotificationPreferenceControllerTest
Flag: EXEMPT bugfix
Change-Id: Ided0853cf9a989e2f288a85c1aa709f71f7e1cd6

2024-08-10 10:24:30 +08:00

assets

Merge Android 24Q1 Release (ab/11220357)

2024-01-30 09:24:25 -08:00

config

…

res

Improve lifecycle of ZenModeFragment & friends

2024-07-29 20:10:03 +02:00

resources/META-INF/services

…

src/com/android/settings

Flash Notifications color dialog crashs if configuration changes

2024-08-10 10:24:30 +08:00

testutils/com/android/settings/testutils

Remove package biometric2 from AOSP settings

2024-07-11 00:06:41 +00:00

Android.bp

Merge "Add strict_mode: false" into main

2024-06-18 03:07:47 +00:00

AndroidManifest.xml

…

new_tests_hook.sh

…

OWNERS

…

README.md

Update Setting's Robolectric tests' instructions

2024-05-11 02:29:57 +00:00

README.md

Running Settings Robolectric tests

The full suite

$ croot
$ atest SettingsRoboTests

Running a single test class

With a filter

$ croot
$ atest SettingsRoboTests:com.android.settings.display.AdaptiveSleepPreferenceControllerTest

You can also run any single test class with atest (it will try to find the correct path)

$ atest AdaptiveSleepPreferenceControllerTest