am skip reason: Change-Id Ie1b01a97cf163d68e4a5529f1718a9a782d44bb0 with SHA-1 de616afce0 is in history
Change-Id: If7c8de95366319c47d6c5d4840c5d6d93021e221
1. Remove tag checker in HtmlTextPreference.
2. Set the max height for AnimatedImagePreference.
Bug: 149516547
Test: manaul test
Change-Id: I98f49d055db9427d91a3f1ca816e94a11d29cd3d
am skip reason: Change-Id I188badb43035172642cf235bb27e56d3a1dea169 with SHA-1 85a65e2dc6 is in history
Change-Id: I522ee7e1b07c0ab77f0cf230d1508e0bf9e479dc
ClearDefaultsPreference is a customized preference which contains a
TextView and a Button. In reality, the button is the only interaction
way to users. There are no more interaction when user click the whole
preference view.
Mark the ClearDefaultsPreference as unselectable can fix the talkback
issue for user clicking the preference view out of button.
In the meantime, the button of ClearDefaultsPreference is not yet to
apply the button style of Settings. Also fix it with ActionPrimaryButton
style of Settings.
Fixes: 146471192
Test: visual and robotests
Change-Id: Ife215d0901bd9fc3055495b0495ba175ed0dfa26
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
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
There were two CLs that conflicted causing
the functionality to break again. This CL switches
back to TestingSettingsBroadcastReceiver back to using
the secret code on TelephonyManager.
This is Ok because ag/10331474 moves AndroidManifest
to same flag.
Test: Brought up "Testing" activity using secret code
Test: Hit breakpoint in TestingSettingsBroadcastReceiver
within if block.
Bug: 149524255
Change-Id: I681d88d7f2f0f923850d33219a1ee56eedf87cad
