- Clean up our LayoutManager code. We actually only need a single
layout manager, since a GridLayoutManager is a LinearLayoutManager,
and list layout is simply grid layout with one column. Make it so.
- Use the layout manager to compute item offsets for one page's worth of
items. Use that to implement page up/page down.
BUG=25195770
Change-Id: I23ddd5fd38532682e7f099b44e188d8c3fec02be
(cherry picked from commit 4d4bf9a21a16bae3497f94dbb558a2ede9d989ee)
Setting android:animateLayoutChanges=true was causing flickering and problems
with sliding the cabinet while a fragment transition was already in progress.
Bug: 27060052
Bug: 26952361
Change-Id: I17e5f8b57d63cd9a586fc70ae43e030c4f232e8d
(cherry picked from commit ed82fd784301c645cb665517edc3006888d6f237)
The tests should fail, as the features are broken.
Change-Id: Ib760ba5469164b8ca0d08c57f24273268ae2436f
(cherry picked from commit 94eca73fec7aa1857f5847df355877d523d0c8a6)
This is another preparation for Bug 26279466. Whether an input method
is marked to be encryption-aware or not would become the thing here and
there in the Framework code. Having a utility method and debug info
in dumpsys should make our lives easier.
Bug: 26279466
Change-Id: Icf921fe3661eccf4a589b08b616d05decc561356
This has nothing to do with Bug 26279466 but might be something nice to
fix just as a preparation.
Bug: 26279466
Change-Id: Ie1a8ee2248081a70728c29e52c657b3a0ed919b1
Nothing is changed in the test expectations.
Major changes in this CL are:
1. To obtain a custom context with the given locale,
Context#createConfigurationContext() is the way to go.
Modifying any internal state of the resource that is owned by the
context is not supported at all.
2. As a preparation to test cases where multiple locales are specified
in the system settings, unit tests need to switch to
Confituration#setLocales(LocaleList).
Bug: 27076327
Change-Id: I6caa76627677c7625a1c42d76a275f67ae65a9b2
This utility class automates the process of binding to the best
matching service, including rebinding as packages change over time.
This design means it's easy to become encryption-aware: we use the
default PackageManager behavior that filters components based on
their encryption-aware status, and we just kick off another
evaluation pass once the user is unlocked.
This change cleans up some of the internal logic so we only rebind
when the implementation switches, and it fixes several bugs along
the way. For example, we would never trigger a rebind if a service
was refactored to a different ComponentName. Another subtle bug was
that we'd never fallback to an older implementation if a higher
version was uninstalled/disabled. And finally, if all implementations
were uninstalled/disabled, we'd leave the last connection bound.
Bug: 26280056
Change-Id: I259af78e6564d61353a772ac03cf5799a398d535
ActivityInstrumentationTestCase2 takes care of starting and closing
the activity, which prevents flakyness.
Change-Id: I2d3908f6605a67a3c2d11e18a9c4799443828df9
(cherry picked from commit e366886c7d91b62fe1478a057fc4c0a104d12b02)
- To handle the specific animation spec, we just animate the views
manually instead of animating the stack scroll (like how we do when
swiping to dismiss)
- Fixing a regression in settings the initial focused index when
alt-tabbing
- Minor tweak to make the front most task smaller when in the initial
non-paging mode
Change-Id: Ic5fd54500fd8ce8284c7aaeddb102b2291bcecac
Signed-off-by: Winson <winsonc@google.com>
This drawable is used for cascading menus. It was 25dp on one dimension
before, for some reason. I verified it looks fine at 24x24.
Change-Id: Iff5d4f00655d77830d9492190b1a74ef6f408f47
(cherry picked from commit c007e91cc0519adeb4ff35e9e8c436231c2be822)
This makes the animation when exiting docked mode a bit nicer
when you fling the divider towards to the navigation bar. However,
since the divider ends at the navigation bar, we need to immediately
dismiss it instead of fading out when the divider is fully occluded
by the navigation bar.
Change-Id: Ic5432fd118cb71be36485667b2c537caf5065ce5
Closing two small holes in the implementation:
1. The gesture was dispatched before the callback was registered. It
was possible for gestures that failed quickly to fail to report any
status.
2. Gestures could be dispatched before the input filter was
installed. Adding a wait to give the filter a chance to install
before reporting a failure.
Also removing an unused method on the input filter.
Change-Id: I77cd80dcd2cec6c72b3761169aba5eaecf62250b
(cherry picked from commit 03465fb874ccf35ead2228b66ec03afc31d7694e)
673cbd2b6932b39d6804cda2969b7f059c1ce748 introduced logic to make
non-top activities in the home stack invisible under certain
conditions. However, this caused problems with the set-up wizard which
uses the home stack to launch all its activties. Changed the logic to
determine if the next task in the home stack should be visible behind
vs. the next activity in the same task. So, activities in the same task
in the home stack can be visible at the same time, but not activities
in different tasks.
Bug: 26922407
Bug: 26571156
Change-Id: Ied20d45cd27a1adcc105703d8ca21861d1856700
Fix two bugs: one where Instrumentation did not properly
handle destroyed UiAutomations, another where UiAutomation
did not properly disable running accessibility services.
Change-Id: I1773dbd373f4d5b0e7c9917ff18d8d9b1a0e07c7
(cherry picked from commit 846522cea043d3113b3b96daa8f3a1b70e3beb5e)
- Initially select the name of the file without extension
- Trigger renaming action when software keyboard Done button pressed
- Trigger creating new directory when software kayboard Done button pressed
Bug: 26954407
Change-Id: I700d5beacdb98eb0699bbdd4f4bbcafcc1a67e83
(cherry picked from commit 953498df13ff05f189a6de750093e322250a6659)
This change introduces the ability to have multiple packages per
APK. The feature is currently restricted to privileged apps and
updates to such apps.
In essence the manifest can have multiple child package declarations.
A child package can declare everything an Android package can except
some tags or attributes that are not applicable and instead inherited
from the parent when needed. For example, the target SDK of the parent
applies to all children.
A child package can be updated only through the parent package.
A package with multiple child packages is installed, uninstalled
atomically - no partial installs where some child packages are not
installed.
The remaining work is to ensure broadcasts are also sent for child
packages. This will come in a subsequent change.
Sample app:ag/848432
Design doc: https://docs.google.com/document/d/18nFWtJuZchLxrHf5SBbJW03-Ky9Rh_G0-OVB14b6u78
Change-Id: I6fd021d981bf5786290e0c53502724a14c97358c
