CarNavigationBar overrides getCurrentView() in phone NavigationBarView
but the dump() method in NavigationBarView uses mCurrentView directly,
which may be null in the auto case. Callign getCurrentView() returns
the correct overriden view.
This patch makes the change to dump() to use getCurrentView().
Bug: 27046536
Change-Id: I92e5655325247d27faac1e33d8622783652bdb10
- Rename to FrameMetrics to avoid collision with existing
android.view.FrameStats class
- Make FrameMetricsObserver implementation detail,
exposing FrameMetricsListener interface as public API
and wrapping in FrameStatsObserver to maintain state
- Remove dropped frame count call, in favor of passing as
parameter to callback method.
- Move away from raw timestamp access in favor of Metric IDs
which represent higher-level, more stable stages in a frame
lifecycle and match the categories exposed in the onscreen
bars.
- Support many-to-many Window<->FrameMetricsListener relationship
Change-Id: I00e741d664d4c868b1b6d0131a23f8316bd8c5c2
MtpDocumentsProvider remembers the mapping between SAF's ID and MTP's
ID. Sometimes we need to do heuristic to restore the mapping when MTP
device is reconnected.
Previously we do the mapping files that shares the same name more
strictly. For example,
1. Found file name "test.txt". Assign document ID "1".
2. MTP device is disconnected and the MTP ID of "1" is lost.
3. Found two files that have same name "test.txt" in the same directory.
Previously we don't reuse existing document ID "1" for neither of two
"test.txt" because it's not 1-to-1 mapping and we cannot determine which
one should be mapped with existing document ID. It means we need the
complete list of files in a directory to remap IDs. It takes long time
to fetch all file names in a directory when a directory has 100+
files. It's rare that a MTP device has the two files sharing the same
name in the same directory. Also the strict rule makes the mapping code
more complex.
The CL relax the rule of mapping, and it allows to reuse existing
document ID even if it is not 1-to-1 mapping. For the previous example,
it assigns "1" for either of "test.txt".
BUG=27053734
Change-Id: I19406fafc21f13ab94ba99411ce5e7f55ce7f658
(cherry picked from commit acdbc6e740ffbd465488b6eb0cf9388d43ae860a)
Fullscreen intents are always less distracting when heads upped
instead of launched fullscreen, so when snoozed or if the ranking
isn't high enough we now prefer HUN instead of simply launching
it.
Change-Id: Iae16d35c6a6d3f11f3d1f6db6e1dc067018a5172
Bug: 26874366
On Multiarch apps, it might be necessary to prioritize 32bit Abi ahead
of 64bit ones. The use32bitAbi flag enables this.
This CL also reverts the public api changes in I2c1fd1d036efe72b28b5fe996416df69a583959f and Ie3ecea6d84e2cb1522e736a21c3a3a24ac62eb27. Previously
the same functionality was provided using a raw abi string that
utilized cpuabioverride flag.
Change-Id: Idce3cbfedd11ef9079ce8a2901e69d30b1cf9ef4
- 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>
