AWARE_TAP_PAUSE_GESTURE_COUNT is the number of times the user
has used the Motion Sense tap gesture to pause media. This number
is used to determine whether to show the "Tap to pause media"
contextual tooltip.
AWARE_TAP_PAUSE_TOUCH_COUNT is the number of times the user has
touched the device to pause media instead of using the Motion Sense
tap gesture (Motion Sense and tap gesture must be active for this value
to increment). This number is also used to determine whether to show the
"Tap to pause media" contextual tip.
We back up these counts so that users moving to new devices with Motion
Sense will not be given these contextual tips again if they already know
how to use the feature.
Test: manual
Bug: 138296598
Change-Id: I702719fb7cec8b6be9dff91d212a00fb26129957
Merged-In: I702719fb7cec8b6be9dff91d212a00fb26129957
(cherry picked from commit a6e468831a)
Test: Verified that the flag could be modified with
adb shell settings put secure...
Bug: 141380252
Change-Id: Ifa24b688a487482e5b02689c1046d85423f73280
* changes:
DO NOT MERGE Move device config key high_refresh_rate_blacklist to display_manager
DO NOT MERGE Allow DeviceConfig to change display settings
DO NOT MERGE DeviceConfig: Add Name space and keys for Display Manager
Notices about obsolete fields and methods now mention the publish
location (Google Play Store) or Android version (Q and higher).
Test: make ds-docs
Bug: 122482744
Change-Id: Idb60fef711401d43af8eb71343f157590c311571
Deprecates the Secure setting so it's clear we're not using it anymore.
Since this work is for a QPR we need to listen for both the new Global
setting as well as the old Secure setting so that CTS may pass without
code changes:
* When the secure setting is changed (only CTS uses it now), the global
setting will also be updated.
* When the global setting is changed (i.e. switching developer toggle), the
global setting is updated and so is the secure setting.
Test: atest NotificationManagerTest
Bug: 137876221
Change-Id: Ib4623689aa4ec1fc79e2ec130702fdf9785834d8
Follow up to http://ag/8222583, which enables bubbles globally instead
of at the per-user level
- Remove user-specific tracking
- Remove Secure.NOTIFICATION_BUBBLES from backup
- Replace references to Secure.NOTIFICATION_BUBBLES with
Global.NOTIFICATION_BUBBLES
- Update tests
Fixes: 136034310
Bug: 129158983
Test: m RunSettingsRoboTests
Test: atest SystemUITests
Test: manual - work profile bubbles show up
Change-Id: I931f8f2640ac01fdf4c30ef9f9474fde7ca2d262
Follow up to http://ag/8222583
- Remove Secure.NOTIFICATION_BUBBLES from backup.
- Replace references to Secure.NOTIFICATION_BUBBLES with
Global.NOTIFICATION_BUBBLES
- Update tests
Fixes: 136034310
Bug: 129158983
Test: atest SystemUITests
Test: manual - work profile bubbles show up
Change-Id: I0c1956272e9d18bcd2e13c6658ca8925cedfcef5
When available, we should read the high refresh rate blacklist from
DeviceConfig, and use the device's configured list as a default /
fallback. This lets us change the blacklist in the field in case we find
additional compatibility issues, or one of the developers fixes their
app and asks us to remove them from the blacklist.
Fixes: 132338514
Test: atest WmTests:HighRefreshRateBlacklistTest
Exempt-From-Owner-Approval: TBR
Merged-In: I984dab60eeafff01758ac38c3db6056b33f662a6
Change-Id: I984dab60eeafff01758ac38c3db6056b33f662a6
Background: Bubble settings have the following levels
- Global (developer options flag)
- App-level
- Channel-level
Issue: Global settings do not propagate to the work profile user because we are
storing NOTIFICATION_BUBBLES in the Secure Settings table instead of the
Global Settings table. Settings are global XOR per-user.
This change
- Sets default value for NOTIFICATION_BUBBLES in global settings table.
- Adds Global.NOTIFICATIONS_BUBBLES to frameworks/base/api/test-current.txt
- Keeps old upgrade steps as no-op to keep db versioning stable.
Bug: 136034310
Test: RunSettingsRoboTests ROBOTEST_FILTER="Bubble"
Change-Id: I21d3dae75e2a4ab0fac10f3d7ea7eed16e0f5d6c
Users where missing the music controls so
we are showing a headsup for them on the
lockscreen.
Fixes: 134543453
Change-Id: I089fa8ff35b918f485f79e09393173f05971a73e
Add limits for system gesture exclusion on the left and right edges.
This prevents non-immersive-sticky apps from totally disabling the
back gesture.
Bug: 135522625
Test: atest SystemGestureExclusionRectsTest
Merged-In: Ib26161663a6aababe803d3c70044f4017bdbe675
Change-Id: Ib26161663a6aababe803d3c70044f4017bdbe675
Settings.Secure string for clock face may be JSON so that it can contain
the timestamp that it was set for logging purposes.
Bug: 134687399
Test: Added SettingsWrapperTest
Change-Id: I50afba479c30029428819c6616ca754db681a2b4
Also decoupling the settings, so they can be configured
separately.
Fixes: 135023656
Test: manual
Test: adb shell settings put secure doze_wake_lock_screen_gesture 0
Test: adb shell settings put secure doze_wake_lock_screen_gesture 1
Change-Id: I2138d5d06919b9c23428663e49381fc1b694e301
