The default was true before, which lead to quite a few bugs.
Moved done the introduced attrs to support it on AnimatedImageView
Change-Id: I68714c22ceefff6bac7cd9496c83edd69256ee1b
Fixes: 27745673
Per the platform team, we shouldn't enable debug logging automatically
in debug builds because it increases log-spam. Just disable the flag
and enable it manually when needed.
Add some ifs to make sure all our debug logging is properly removed.
BUG=27380154
Change-Id: I8338f226c07affdb65970c7cb14f1e6aae036934
When multi-user is disabled and user button on the notification panel
is tapped, the contact app is displayed behind the notification panel.
The notification panel should be closed
when the contact app is launched.
Bug: 27790403
Change-Id: I66ebcb66c898dfebe1d09b798f750f696c360da8
(cherry picked from commit 8cb009e45115dbd03c66de6d56ef1510777a4ead)
The overflow now comes in only after the other notifications have
fully transformed.
Bug: 24866646
Change-Id: Ia950205669916a637c44ea7d41bfc06e750ea987
If a group is expanded and a child is huned,
it is not isolated anymore as the user can
already see it.
Bug: 24866646
Change-Id: I671aad6556c2c1c7e1cee2b45f54834ef9e2e093
When dumpstate starts, it estimates its maximum duration and sends it
through an extra on BUGREPORT_STARTED; as it progress, it sets a system
property with its current progress and if the progress value overflows
the estimated max, it increases the max as well.
Shell uses the max/progress to display the progress % in the
system notification, and need to handle the scenario where the max
changes. The initial implementation would recalculate the progress, with
makes it swing back and forth as dumpstate increases the max.
This CL changes the Shell logic so the progress never go back, just
forward. The drawback of this approach is that if dumpstate
underestimate the maximum, the progress might get stuck in a high
value (99%) early on, but such issue will be addressed in the long
term by tuning the estimated max value.
BUG: 26354314
Change-Id: I3a5416acaffaaa43fd28d2f1f8ec8ea12aa0d91e
Root documents must be added by RootScanner.
Previously DocumentLoader unintentionally tries to load unmapped root
documents, which causes crash.
BUG=27731902
Change-Id: I8674473d80d6e7f758f6636d30148f5d2118bc25
Previously DocumentLoader#LoaderTask had a counter to count loaded
documents and completes adding documents to the database. However it
does not count documents where a MTP device returns an error for
getObjectInfo. The CL fixes the problem to ensure we complete documents
loading.
BUG=27729653
Change-Id: I696eac790a6535f1bd7a1855dc2d6f932e32eae5
More proper fix would be not showing Recents after an activity is PIPed,
but NPE shouldn't be happen so let me propose the CL as the first step.
Bug: 27634771
Change-Id: Ie98293b7dd2d206567ded08d54134164aa78ca9c
The group summary could still be visible even though
all children were heads upped. The notification
is now suppressed instead.
Change-Id: Ic489925d9881bd2f59170f9c0fe9a3dbb17e25aa
Bug: 27104166
Fixes: 27572569
