Add a comment for the LegacyGlobalActions broadcast receiver fix

The bug is already fixed in master branch by registering the broadcast
receiver with UserHandle.ALL, which is an uncommon way to register
a broadcast receiver. This CL adds a comment to explain it.

Bug: 182842046
Test: atest CtsAccessibilityServiceTestCases
Change-Id: I10405769ba6426c7bbcd31e09e1cd4c99585665b
This commit is contained in:
Yabin Huang
2021-06-03 19:12:28 -07:00
parent 23fd70f617
commit a6d73351fd

View File

@@ -135,6 +135,9 @@ class LegacyGlobalActions implements DialogInterface.OnDismissListener, DialogIn
filter.addAction(Intent.ACTION_CLOSE_SYSTEM_DIALOGS); filter.addAction(Intent.ACTION_CLOSE_SYSTEM_DIALOGS);
filter.addAction(Intent.ACTION_SCREEN_OFF); filter.addAction(Intent.ACTION_SCREEN_OFF);
filter.addAction(TelephonyManager.ACTION_EMERGENCY_CALLBACK_MODE_CHANGED); filter.addAction(TelephonyManager.ACTION_EMERGENCY_CALLBACK_MODE_CHANGED);
// By default CLOSE_SYSTEM_DIALOGS broadcast is sent only for current user, which is user
// 10 on devices with headless system user enabled.
// In order to receive the broadcast, register the broadcast receiver with UserHandle.ALL.
context.registerReceiverAsUser(mBroadcastReceiver, UserHandle.ALL, filter, null, null); context.registerReceiverAsUser(mBroadcastReceiver, UserHandle.ALL, filter, null, null);
mHasTelephony = mHasTelephony =