- Create new ClearAdbKeysPreferenceController
- Added ClearAdbKeysWarningDialog
- Create controller inside the DashboardFragment
- Port logic from DevelopmentSettings into the controller
Bug: 34203528
Test: make RunSettingsRoboTests -j40
Change-Id: Ia12bfee753f2c9222e6d833b1fb7e099f3602fdf
The old onSubmit was a no-op. It now correctly pipes onSubmit to
WifiManager#save() with the new WifiConfiguration. On successful save,
it displays the new network in the list, and on failure, it displays a
toast indicating that the save action failed. Adds a test for the
WifiDialog behaviors on this page.
Bug: 66177765
Test: make RunSettingsRoboTests, manual - tested with Wifi enabled and
disabled, and with networks that were visible and not.
Change-Id: I27446aa49bc9efaf1ea1d6c6158928b62ce01ba2
Merged-In: I27446aa49bc9efaf1ea1d6c6158928b62ce01ba2
- Create new ResizableActivityPreferenceController
- Create controller inside the DashboardFragment
- Port logic from DevelopmentSettings into the controller
Bug: 34203528
Test: make RunSettingsRoboTests -j40
Change-Id: I401db1fe3a051ee70ab9afe2bf8c377b3b0b4e2f
- Create new NotificationChannelWarningsPreferenceController
- Create controller inside the DashboardFragment
- Port logic from DevelopmentSettings into the controller
Bug: 34203528
Test: make RunSettingsRoboTests -j40
Change-Id: I232b24ee0505eae254bd1d43b7d91ab8860285e2
- Create new BugReportInPowerPreferenceControllerV2
- Deprecate BugReportInPowerPreferenceController
- Create controller inside the DashboardFragment
- Copy logic from BugReportInPowerPreferenceController with
slight modifications for dashboard fragment compatibility
Bug: 34203528
Test: make RunSettingsRoboTests -j40# Please enter the commit message for your changes. Lines starting
Change-Id: I8ec0c84fa9c4e59aca48586cc081822d78d8c0d5
Comparisons changed on the intent action. Sometimes an account
preference intent does not have an action specified.
Fixes: 67075850
Test: manual - go to Settings > Users & accounts and tap an account.
Change-Id: I54cebbc983b55aa1487a122d37ccd5c79bbf519d
- Create new VerifyAppsOverUsbPreferenceControllerV2
- Deprecate VerifyAppsOverUsbPreferenceController
- Create controller inside the DashboardFragment
- Copy logic from VerifyAppsOverUsbPreferenceController with
slight modifications for dashboard fragment compatibility
Bug: 34203528
Test: make RunSettingsRoboTests -j40
Change-Id: I37c01cd262c9e12307ec9cbe6effc5470496550f
- Create new AllowAppsOnExternalPreferenceController
- Create controller inside the DashboardFragment
- Port logic from DevelopmentSettings into the controller
Bug: 34203528
Test: make RunSettingsRoboTests -j40
Change-Id: Ia8f1be0509f87ad42cf3dc640fa711cdec07698d
- Create new AppsNotRespondingPreferenceController
- Create controller inside the DashboardFragment
- Port logic from DevelopmentSettings into the controller
Bug: 34203528
Test: make RunSettingsRoboTests -j40
Change-Id: I9cf9a19b59bf21d6aa0205377025f82ed21b7e51
- Create new UsbAudioRoutingPreferenceController
- Create controller inside the DashboardFragment
- Port logic from DevelopmentSettings into the controller
Bug: 34203528
Test: make RunSettingsRoboTests -j40
Change-Id: Ie806d509e3df4515cccbaf56c259ae55c3e2ab61
- Create new HardwareOverlaysPreferenceController
- Create controller inside the DashboardFragment
- Port logic from DevelopmentSettings into the controller
- Added ShadowParcel to help with testing
HardwareOverlaysPreferenceController and
ShowSurfaceUpdatesPreferenceController
Bug: 34203528
Test: make RunSettingsRoboTests -j40
Change-Id: Ib6b9679f2a2d2ec84f91da5ac0b68cb2b21eea72
- Create new GpuViewUpdatesPreferenceController
- Create controller inside the DashboardFragment
- Port logic from DevelopmentSettings into the controller
- Fix a typo in preference naming
Bug: 34203528
Test: make RunSettingsRoboTests -j40
Change-Id: Ieff20634238900137acc1524edb6fd0d4bfce894
- Create new ShowLayoutBoundsPreferenceController
- Create controller inside the DashboardFragment
- Port logic from DevelopmentSettings into the controller
Bug: 34203528
Test: make RunSettingsRoboTests -j40
Change-Id: Ie7bb26675f4dcedbff9607a2c4e4f5bee0343463
When a user explicitly clicks a button labeled "Enable" for an
application in settings, the underlying package state should reflect
this. Otherwise, it is impossible to distinguish between the default
state of an app and an app which the user has explicitly requested to
enable.
This behavior is consistent with the Play Store's.
This also fixes a metrics bug where enabling a DISABLED_UNTIL_USED app
would be erroneously treated as disabling the app.
Test: Flashed and verified enabling both DISABLED_UNTIL_USED and
DISABLED apps.
Fixes: 64223206
Change-Id: Ic18068e6047045d6f5333eaf10fcddd1e95a679d
- Create new StrictModePreferenceController
- Create controller inside the DashboardFragment
- Port logic from DevelopmentSettings into the controller
Bug: 34203528
Test: make RunSettingsRoboTests -j40
Change-Id: I28d70fd5c82de2427747625b5f06f79d3808a145
