The previous window type FIRST_APPLICATION_WINDOW was incorrect and
could have caused the dialog to be dimmed and TalkBack to not be
focused. The current window type TYPE_APPLICATION fixes these issues by
correctly placing the dialog in the window hierarchy.
Bug: 404595933
Bug: 404439964
Bug: 353531691
Test: visual
Test: checked with TalkBack
Flag: EXEMPT bug fix
Change-Id: I520220c1527868b6fc928eaa35184ba9b0159e06
When a user clicks the biometric item in the Device unlock page and no
biometric is enrolled:
- Fingerint clicked: Launch fingerprint enroll then face enroll.
- Face clicked: Launch face enroll then fingerprint enroll.
Also fixed work profile not working issue:
- Use BiometricEnrollActivity.InternalActivity to provide correct userId
for work profile.
- Use the canAuthenticate() function that take userId as input.
Bug: 370940762
Test: atest FaceSafetySourceTest FingerprintSafetySourceTest
Flag: com.android.settings.flags.biometrics_onboarding_education
Change-Id: I0800c5bb71cc3813e0336ed65898d099857175ef
If there is no active esim and the active esim slot, then enabling esim
uses the active esim slot's port.
Bug: 394758842
Test: manual test
Flag: EXEMPT bugfix
Change-Id: Icd478a92662584d433e16b129da98204e9e2f5f3
- Use SatelliteManager#getSatelliteDataSupportMode() to check data
restricted or not.
Flag: EXEMPT bug fix
Bug: b/401043401
Test: atest pass
Test: Manual test
Change-Id: I6f3e25610717eca0f6e871a9e1158422659058ea
Test: local tested, haven't find good way to add unit test for reflection.
Flag: EXEMPT minor fix
Bug: 380801155
Change-Id: Ia0d05ef933b0ae24077f31e4ff46c9948b99628a
- Use controller base design instead of current
Flag: EXEMPT bug fix
Bug: b/401648126
Fix: b/402037025
Test: Manual test
Test: atest pass
Change-Id: Icb3fd6a1c5340e554593fc57cb238bf98d3ed0e3
This CL sets the full component for the Settings intent that opens
"Legal information->Third-party...".
Bug: 300111126
Test: make -j64 SettingsRoboTests
Test: create ika environment, manually open legal info.
Flag: EXEMPT bug fix
Change-Id: I3169620c0f2ff78a39b456597384a9738bc38a9f
This fixes a bug where the deep link initiated from a search result
would open the results page in a separate window. The root cause was the
inclusion of the FLAG_ACTIVITY_NEW_TASK intent flag.
Bug: 381127948
Test: atest SettingsSpaUnitTests:com.android.settings.activityembedding
Test: atest CtsSettingsTestCases:SettingsMultiPaneDeepLinkTest
Test: Manually verify UI
Flag: com.android.settings.flags.settings_search_result_deep_link_in_same_task
Change-Id: I91f9e5096ad02bd87e43bae03a2b3e69256be651
This guards against iterating over a null array. This scenario should
never happen on user devices, however we know it can happen if you
install a trunk-staging build of the settings app on top of a nextfood
device configuration. This happens because of a flag mismatch
(updateServiceIpcWrapper is enabled in the trunk-staging app but the
service is not implemented by a nextfood platform build).
This is a low risk change since we know users cannot usually get into
this state.
Fixed: 391725109
Test: N/A - this bug is not possible in any configuration we test
Flag: EXEMPT bugfix
Change-Id: I654e0be5ad94e769cd8325ce5d20d241a4a13c13
