ModuleInfo#isHidden is used for getting hidden module status from
ModuleMetadata package (Mainline). It was set to hide Mainline modules'
Apk to show in the Settings UI and this has caused the issue as it
disallowed the user to toggle permissions where it was needed. Thus, we
decided to deprecate the usage of ModuleInfo#isHidden (see
go/aml-hidden-modules-permissions).
Bug: 379056868
Test: unittest
Test: check behavior before/after enable flags
Flag: android.content.pm.remove_hidden_module_usage
Change-Id: I670c95350e3c21db9f74f37b675aba1b23c67a61
"Quickly open camera" screen was previously replaced by the "Double
Tap Power Button" screen and accessible only if the
feature flag
android.service.quickaccesswallet.launch_wallet_option_on_power_double_tap
was disabled.
This CL introduces the possibility to set, via a config resource, "Quickly open camera" as the double tap power
gesture screen.
Test: atest DoubleTapPowerSettingsTest
Test: atest DoubleTapPowerPreferenceControllerTest
Test: atest DoubleTapPowerSettingsUtilsTest
Test: manually modified config and verified screen and gesture behavior
change
Flag: android.service.quickaccesswallet.launch_wallet_option_on_power_double_tap
Bug: 384794943
Change-Id: I5ab4422da09fa90848c66a41829327494080b5a2
Change-Id: I8e04cac3999a7ed99a611ef084c54bc07a5505dc
If some other app or the system changes the topology, we detect it and
refresh the topology pane. If the listener reports a topology that we
just applied, do not actually refresh the pane.
Flag: com.android.settings.flags.display_topology_pane_in_display_list
Bug: b/352650922
Test: atest DisplayTopologyPreferenceTest.kt
Test: with added logs, verify that a detach and re-attach w/o new topology does not cause a full refresh
Change-Id: Iecf50d563b430755c93bee5a1ff54f3f3d6eb3da
Use Float rather than Int for View coordinates as mostly Floats are
required. Also stop requiring Point/PointF boxing of arguments, since
the Preference implementation ended up not using Point/PointF objects
very much.
Flag: com.android.settings.flags.display_topology_pane_in_display_list
Bug: b/352650922
Test: atest DisplayTopologyPreferenceTest.kt
Change-Id: Iecccb9d524014c3b6ad600f99b9e769418e57a4d
The API of the builder was changed a bit to clean up some things and
make others more explicit. Update tests in settingslib accordingly.
Bug: 382497909
Flag: TEST_ONLY
Test: this
Change-Id: Ib31991d61e7b232c8a2befda92537d7b388beb5b
After dropping, apply the new topology to the DisplayManager. We assume
the new topology is immediately written and read it back.
We don't yet respond to updates of the topology from other apps or
components; this will come in a follow-up patch soon.
Flag: com.android.settings.flags.display_topology_pane_in_display_list
Bug: b/352650922
Test: drag a display when there is only one in the topology
Test: drag a display when there are two in the topology
Test: close and re-open settings to verify a topology is persisted
Test: atest DisplayTopologyPreferenceTest.kt
Change-Id: I26aa7325570c5fd3e8b5fb60cb6e1196f8657b80
Bug: 320510464
Test: Presubmit
Test: Manual, i.e. verified system animations enabled on device
Flag: EXEMPT flag cleanup
Change-Id: Ie3b9ecd3355fcf86a1b4f597d45635b3fc794be9
The same flag is being (correctly) added in onCreate, so on top of being wrong this was also completely unnecessary.
Bug: 368579654
Test: atest NotificationAccessConfirmationActivityTest
Flag: EXEMPT bugfix
Change-Id: I539fca77a1d136bdd0e4892993020884430b8a4e
Update icons, strings and layouts for new UX design
Bug: 370940762
Test: manual:
Pre condition - no face enrolled
Go Settings>Security & privacy>Device unlock>Face unlock
Test: atest FaceEnrollTest
Flag: com.android.settings.flags.biometrics_onboarding_education
Change-Id: Ie469c47005afb941f5646a2f790736362c23c697
The metadata change listener will be added in later changes.
Test: atest: com.android.settings.bluetooth.ConnectedBluetoothDeviceUpdaterTest
Bug: 362859132
Flag: com.android.settingslib.flags.enable_temporary_bond_devices_ui
Change-Id: I3ba5a978ce66e748fc1a7666fa4f6e84144c2c54
Change "480 B" to "480 byte".
And no longer use FormattedDataUsage.
Bug: 321861088
Flag: EXEMPT bug fix
Test: manual - App data usage
Test: unit test
Change-Id: I9ed220e2d5b8fc512d7d28f6fa7faebb37beab83
* changes:
Notification on lockscreen settings: adapt text view for large font
Inverse toggles on the notifications on locks screen settings page
Update appearance of notifications on locks screen settings page
Remove description from notifications on locks screen settings page
This adds APP_NOTIFICATION_PROMOTION_SETTINGS to the set of intents that can go to AppNotificationSettings, and additionally adds the appropriate highlight key when the fragment is started with that intent action.
Flag: android.app.ui_rich_ongoing
Test: manual with flag on & off via sending intents over adb; AppNotificationSettingsTest
Bug: 369150427
Change-Id: I1c48fdae161979f1a221f7c57e83e94f6aadc306
These were never plumbed in, never mind launched, and are sometimes
causing confusion in design discussions when people have the feature
flag turned on. Let's remove them.
Bug: 245989146
Test: check System > Touchpad > Touchpad gestures option is removed even
when the flag's enabled
Flag: EXEMPT removing code controlled by a legacy sysprop-based flag
Change-Id: I22ca19faf6fed430bb3f0733867716a02514ac8d
Set initial value to null, so no animation when the actual value true
is emitted.
Bug: 329584989
Flag: EXEMPT bug fix
Test: manual - on SIMs
Test: unit test
Change-Id: I3eea55115f02e65dcdcc44ccf917f9083622b723
- Add a new PreferenceItem for check enrolled fingerprint
- Create a new DialogFragment for the check enrolled
fingerprint with functions:
- request an authentication to FingerprintManager
- highlight the item when a authentication successes
- show error text when authentication fails
- close the authentication
Bug: 370940762
Test: atest FingerprintSettingsFragmentTest
Flag: com.android.settings.flags.biometrics_onboarding_education
Change-Id: I90637e4ec20ea46e6f530ffd7ba79df9c31eda6b
