Added slot index information in the broadcast
so the receiver knows which slot to get information.
Test: Manual
Change-Id: Icd1bcc2fa905bae6b0f2220e9a27178711bac0c7
Fix: 150126754
am skip reason: Change-Id I3d162f6d2f1035b81b1b2eb915b488084e7ea36e with SHA-1 fcd9f1a870 is in history
Change-Id: Id69bc466f138dc5db47a853b01ed09507048e5b7
am skip reason: Change-Id I3d162f6d2f1035b81b1b2eb915b488084e7ea36e with SHA-1 fcd9f1a870 is in history
Change-Id: Id3bf8f851a257a95cbdb747dc7f7f93b71ae7d26
ClearDefaultsPreference is a customized preference which contains a
TextView and a Button. In reality, the button is the only thing that the user can interact with. It's a no-op when the user clicks on the whole preference view.
Mark the ClearDefaultsPreference as unselectable can fix the talkback
issue for the user clicking on the preference view outside of the button.
In the meantime, the button of ClearDefaultsPreference has not applied the button style of Settings yet. Also fixed it by using the ActionPrimaryButton style of Settings.
Fixes: 146471192
Test: visual and robotests
Change-Id: Ife215d0901bd9fc3055495b0495ba175ed0dfa26
Merged-In: Ife215d0901bd9fc3055495b0495ba175ed0dfa26
(cherry picked from commit b9bcbddc46)
Add a config for contextual dismissal. This config is used to
determine whether the existing dismissal timestamp should be
kept before an insertion.
The new dismissal behaviour design replaces the boolean
value(isDismissed) with a long value(dismissedTimestamp) to give
this behaviour more flexibility. Utilizing the timestamp allows
developers to define new criteria of card's display (e.g cards being
dismissed can be shown again after a period of time).
While newly inserted data from SettingsIntelligence or other clients
may not have dismissal timestamp recorded. Turning on the config gives
the capability to persist dismissal timestamp, and more customized
behaviour can be created.
Bug: 143055685
Test: robotests
Change-Id: I9d095955e9c51f2aa3332d49ee230d3ded9ae744
Merged-In: I9d095955e9c51f2aa3332d49ee230d3ded9ae744
(cherry picked from commit 377125bf96)
slider position is smaller than min value causes the exception.
Fixed by limit the position within min and max value.
Fixes: 148270968
Fixes: 149973990
Test: manual
Change-Id: I3d162f6d2f1035b81b1b2eb915b488084e7ea36e
(cherry picked from commit fcd9f1a870)
Merged-In: I3d162f6d2f1035b81b1b2eb915b488084e7ea36e
- remove "Pair new device" row
- change the on/off toggle to a plus button for pairing new device
- roll back the title "Bluetooth devices"
Bug: 149667096
Test: robotest
Change-Id: I47e9c47b2ab0adacdbdbde34522d7c0172adda75
Merged-In: I47e9c47b2ab0adacdbdbde34522d7c0172adda75
(cherry picked from commit 5e462a852b)
am skip reason: Change-Id Ie1b01a97cf163d68e4a5529f1718a9a782d44bb0 with SHA-1 de616afce0 is in history
Change-Id: If7c8de95366319c47d6c5d4840c5d6d93021e221
am skip reason: Change-Id I188badb43035172642cf235bb27e56d3a1dea169 with SHA-1 85a65e2dc6 is in history
Change-Id: I522ee7e1b07c0ab77f0cf230d1508e0bf9e479dc
am skip reason: Change-Id Ifa7045000ce578a611bb065cd821a87a54edd49c with SHA-1 5920f62784 is in history
Change-Id: I8b8701deacb8424499a40f0e67699d7e679bf6f7
Robotests cases in EnableVerboseVendorLoggingPreferenceControllerTest
show all pass but actually they are all bypassed due to the fact that
the test class can not grant sepolicy permission as what Settings
app does.
This version introduces mock DumpstateDevice HAL to really
perform the Robotests cases.
This CL also clear up code format issues.
Bug: 149886908
Test: make && make RunSettingsRoboTests
Change-Id: I64025ebea60e18d17338604519a6cae98ca7928b
To facilitate better development, add prerelease driver choice to graphics
driver preferences dashboard. This patch also makes sure that when game driver
or developer driver is not shipped, the choice doesn't show up.
Minor: Add tests.
Bug: b/148626177
Test: make RunSettingsRoboTests ROBOTEST_FILTER=GraphicsDriver
Change-Id: Iad398cd663300086d3f4802ffab34531e11dfb17
Currently, if a contextual card gets dismissed, it will be gone forever.
After this change, all cards being dismissed can be shown again after a
certain amount of time(e.g one day). In order to calculate the amount of
time, CARD_DISMISSED column is replaced with DISMISSED_TIMESTAMP. Once a
card gets dismissed, a timestamp will be recorded for a corresponding
card.
In this change, some methods are moved from CardDatabaseHelper to
ContextualCardFeatureProvider. So OEMs could replace the providers with
their own ones to get cards and have different dismissal behaviours.
Bug: 143055685
Test: rototests
Change-Id: I00ace98991cabcbfcae4fc47a44e9448683d680c
