Added contents to give an overview of VectorDrawables and
AnimatedVectorDrawables. For better understanding, added two graphic
files to explain the overall working of the XML file and the graphic
that is rendered as an output of the XML file.
Bug: 28072772
Change-Id: I9b6513c4b6e5aec59f45155963ff732fdd7b5784
Fixes a crash that would happen in all dreams
that did not have permission to acquire wake locks.
Instead moves the wake lock logic into the system
process. Also fixes a bug in DozeService where the
wake lock was not held until dozing was actually
properly initialized.
Fixes: 31612287
Bug: 31044352
Related-CL: I85955a2b7d6bad5171accbc336117a9660b1b198
Test: adb shell settings put secure screensaver_components com.android.dreams.basic/.Colors; adb shell service call dreams 1
Change-Id: Idb3f921ee71b6da6c2ab0c44c332ef91f93ddbc0
* changes:
Fixed a bug where the dimmed background could be invisible
Fixed an issue where the inline controls where not usable
Added Emergency affordance feature
A customer may switch off wifi in a retail environment, which will lead
to no internet connectivity in the following sessions, which is not
desirable. Fixing it by enabling wifi at the beginning of every new demo
session.
Bug: 31689469
Change-Id: Ie7eb17bfe8fbee185d5bfe6ac7a590ca5dabdc29
Forgot to add a redirect for this one when N released. Redirects
were staged to http://go/dods-stage
Change-Id: I333fbe9a51ae4d105e35ef4b86f36e576032f9fe
mActivePointerId should be initialized to INVALID_POINTER.
Otherwise, the click event to DismissView can be intercepted by
onInterceptTouchEventScroll() due to wrong calculated value of yDiff
when mActivePointerId is not intialized.
This issue can be reproduced at the first click to DismissView while
user have not touched any notification views ever after boot.
And that click event must contains some MOVE events.
Test: manual - Check whether user always can click DismissView
after boot.
Fixes: 31649735
Change-Id: If9baf6db1b891a58e17153806d52d395ddd661df
Sometimes, makeSingleLayout() can be invoked before layout direction is resolved.
When not resolved, it indents in LTR layout although it should be RTL.
So, to guarantee the exact indenting, we should re-build the text layout
when the layout direction is changed.
Test: manual - Test BigTextStyle notifications with LargeIcon under RTL configurations.
Fixes: 31633875
Change-Id: Idc6c5d7d41632cb9e1b70d9c67c13852e3f25023
This CL reflects the N MR1 behavior and
fixes some bugs.
Defining the compatibility behavior will be
done separately.
Bug: 31702571
Change-Id: I2a79871f47849f9f5a9c3377a3061208488e6ecb
Fix a bug where ResolverComparator's results were not consistent for
targets that cross profile boundaries.
Bug: 31640894
Change-Id: Ic6bf9512d2c2eb6f8fb7851e18eb9a347db29755
