Currently in TelephonyProvider, it uses tm.getSimSpecificCarrierId() to
get the specific carrier id to retrieve the apns, update Settings to
match.
Fix: 360917123
Flag: EXEMPT bug fix
Test: manual - new apn
Test: atest ApnRepositoryTest
Change-Id: I982e0026acdf34ccec7508c41f83718894f7da57
The package name doesn't match the one used in
development_memtag_page.xml. This would result in the controller can't
be found when the DashboardFragment trying to instantiate the controller
defined in xml.
Bug: 245624194
Flag: EXEMPT low risk bugfix
Test: Examing the log and verify there is no "Cannot instantiate controller
from reflection" for DevelopmentMemtagFooterPreferenceController
Change-Id: I63ba96d587525c08cf1409883e2bd09bc85bfc41
**Root cause**
The PreferenceController can be constructed by the
SettingsSearchIndexablesProvider where the looper of the thread is not
prepared. This result in not able to construct the PreferenceController
that will be used as part of the SettingsSearch.
Currently, if the SettingsSearchIndexablesProvider is not able to
construct the PreferenceController defined in xml, it would just
silently failed.
Test: atest SettingsUnitTests
Test: atest SettingsRoboTests
Flag: EXEMPT low risk bugfix
Bug: 352622249
Change-Id: I72a4ce24ec6842b9efe067e3cb7d1c73cd98a566
Bug: 326057017
Change-Id: I83ab4461f28e7f40c676099213c840a1a7dc932a
Test: atest; open app info pages from both primary and secondary profile -> verify they open as expected
Flag: EXEMPT bug fix
Revert submission 28985385-bt_key_missing_dialog
Reason for revert: Likely culprit for b/362901443 - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.
Reverted changes: /q/submissionid:28985385-bt_key_missing_dialog
Change-Id: I2a3ab8f0dbd2c81eda49d11abc6d586f59f149e9
And also the flag.
Bug: 339884322
Flag: com.android.settings.flags.internet_preference_controller_v2
Test: manual - Network & internet
Change-Id: Icb3427f6624db0442c05f5e149dbe522d1497e83
Also support settings search for video calling.
Fix: 233327342
Flag: EXEMPT bug fix
Test: manual - on mobile settings
Test: manual - search video calling
Test: unit test
Change-Id: Ic4a25849f77f1759fa157931d428daa9e6854ff2
Which also avoid calling from main thread.
Bug: 356684993
Flag: EXEMPT bug fix
Test: manual - on SIMs
Test: atest EuiccRepositoryTest
Change-Id: I0b11b0bd1e8a4b5754781e888fd220fa3080a212
Also moves the modes entrypoints out of the sub-pages it was previously in (notifications and sound settings).
Bug: 353700470
Test: manual by opening the homepage
Flag: android.app.modes_ui
Change-Id: I53124bfed25c43fc2dabaf9c43ce0513bbfc7377
Flag: com.android.settings.flags.updated_suggestion_card_aosp
Bug: 323258154
Test: Enable flag and trigger suggestion cards to show
Change-Id: Iee47d05d8d75c10ba073ae3541f108bc37b4c09b
In settings, reduce calls to getInstance(), and pass it to preferences and their controllers instead.
Bug: 360399800
Test: atest ZenModesListItemPreferenceTest ZenModesListPreferenceControllerTest
Flag: android.app.modes_ui
Change-Id: I318320575e3bd32b5d13a385fa644f8032484e1c
From UX mocks, we need to show IME names in heading if there
are multiple IMEs. But in situation where we have multiple
IMEs but one of the IMEs doesn't have any valid subtype for PK,
it should work as if there is only a single IME.
Bug: 361528038
Test: manual
Flag: EXEMPT bugfix
Change-Id: Idd03a224b300df31b3265a5d58f79c0fc5d1535a
