Jeremy Goldman 09a185dbca Store whether the Dialog was previously dismissed ...

The dialog can be dismissed by either the framework automatically (i.e.
when the screen is rotated) or when the subscriptions change.

If both of these things happen while the class is not deleted, then
dismiss() will be called twice and there will be a crash

Bug: 184899699
Test: atest -c SettingsUnitTests
Change-Id: Ibaef59696feb566664a424f65f806396f02497e8

2021-05-13 14:42:26 +08:00

..

receivers

Merge "Post SUW Slot Change Receiver Migration" into sc-dev

2021-02-05 18:13:58 +00:00

smartForwarding

[Smart forwarding] Enable/Disable Smart Forwarding flow

2021-01-25 10:08:33 +08:00

CallsSimListDialogFragment.java

[Settings] Code refactor - remove unused import lines

2021-03-16 10:24:24 +00:00

ChooseSimActivity.java

Slot Change Receiver Migration

2021-01-28 14:15:53 -08:00

DsdsDialogActivity.java

Change DSDS dialog confirm text from "Continue" to "Yes"

2021-04-14 13:43:26 -07:00

OWNERS

Add OWNERS

2021-02-19 02:33:26 +00:00

PreferredSimDialogFragment.java

Store whether the Dialog was previously dismissed

2021-05-13 14:42:26 +08:00

SimActivationNotifier.java

Fix the notification issue after pSIM is auto enabled

2021-02-17 20:42:52 +00:00

SimDialogActivity.java

Automatically dismiss SIM combination warnings and selection dialogs.

2020-12-15 16:45:27 -08:00

SimDialogFragment.java

Store whether the Dialog was previously dismissed

2021-05-13 14:42:26 +08:00

SimListDialogFragment.java

Store whether the Dialog was previously dismissed

2021-05-13 14:42:26 +08:00

SimNotificationService.java

Post SUW Slot Change Receiver Migration

2021-02-02 17:57:40 -08:00

SimSelectNotification.java

Revert "[Settings] Support getSystemService(Class<T>)"

2021-03-30 00:51:15 +00:00

SwitchToEsimConfirmDialogActivity.java

Slot Change Receiver Migration

2021-01-28 14:15:53 -08:00