flag: ENABLE_INPUT_CONSUMER_REASON_LOGGING
Fixes: 270390028
Test: ran launcher and printed gesture nav logs
Change-Id: I0fd0b82c1c812ddc43beba03bd456795f68ada55
Supporting the Launcher3 search box is low hanging fruit, so we might as
well do it.
Also renamed the feature flag to be for search in general.
Test: Launching, split screen, and popups work in search.
Bug: 216683257
Flag: ENABLE_ALL_APPS_SEARCH_IN_TASKBAR=false
Change-Id: I056b89be6f458d1d90100e34551baa34037574d1
This allows a targetting a collection of flags to a specific group
either using rollout or via opt-in
Flag: N/A
Bug: 274517185
Test: Verified that the team food flag controls dependent-flags
Change-Id: I7e02964d778e3fbf54eda0f34bab8ec5a1206e40
This patch creates a new Launcher flag for the upcoming App Pairs feature.
Flag: ENABLE_APP_PAIRS
Bug: 274189428
Test: Not needed
Change-Id: I84cfb3742a60bd5633d71bc68e7506ac0c67e55f
This reverts commit 17f7406a5e.
Reason for revert: To be submitted after the fix for b/273614966 is downstream merged into udc-dev (ag/22102493).
Change-Id: I3038b46776815069898829e46321885278b1caff
This reverts commit 5156b48f6c.
Reason for revert: Fixed test failures from flipping the flag on in ag/22066273 and ag/21992972
Change-Id: I0478869c22a8f23d81a688bfa07a40230521f638
This reverts commit 5d8489e71e.
Reason for revert: regression test failures b/273135788 b/272838823
Change-Id: I8b4747b8b714820648f7816f4b2ea962da5d332c
Will turn it off in all the U release branches (feature targeting U-QPR1)
Fixes: 271010401
Test: N/A
Change-Id: I25e8497cdc2828ddf5c2c660adfe64e1d5bea764
Made separate feature flag for on device search
Add unit test to test twoLine string
- Unit tests for testing newStringThatShouldSupportTwoLineText() in BubbleTextView.java. This class tests a couple of strings
and uses the getLineCount() to determine if the test passes. Verifying with getLineCount() is sufficient since BubbleTextView can only be in one line or two lines,
and this is enough to ensure whether the string should be specifically wrapped onto the second line and to ensure truncation.
bug: 201388851
test: presubmit, ran locally on big and small device, before: https://screenshot.googleplex.com/3Q6pwveFDZqxDXL (ORIGINAL TWO LINE TEXT)
after: https://screenshot.googleplex.com/7pkwUto6HGzMYoT
Change-Id: I93e6ed179e1081d5cdffc6db9c7ae34de8021c24
- Remove the Utilities.atLeast check since it's no longer relevant as there is no new haptics being played
in the original haptic..
When FeatureFlag is off, the haptic for all apps and qsb is played in one place. So when
FeatureFlag is on, we need to isolate where the haptic call gets played so we disable calling it from two places
and play the haptics at the respective areas.
flag: ENABLE_PREMIUM_HAPTICS_ALL_APPS=false
bug: 270634265
test: Manual
Change-Id: I7b92c427e880b196130270ed9709cf1ea0e19e0a
This change is only for dogfooding and will not be part of android release.
Guarded by feature flag.
Test: manual
Bug: 266177840
Change-Id: Iee416b43e0864b98f08149c46b7d011271ba8de6
The way WorkspaceBinder is currently setup, any calls to
bindWorkspace will result in the entire workspace being bound
all at the same time. These edits change that. Now callers
like LoaderTask can bind the first workspace pages before the
rest by splitting the WorkspaceBinding into 3 methods that
need to be called in order, but can happen at a staggered cadence.
Bug: 251502424
Test: Loaded and bound the workspace properly.
Change-Id: I28fa721ea95dae2df03e27f600653ba5bebe3ef1
> Only restart when the screen is off.
> This allows better propogation of flags similar to systemUI
> Adding support for integer flags
Bug: 266854800
Test: Verified on device using device_config shell command
Change-Id: I4ea9c564f2d973f11f9570b5a21365183afefab7