When properties weren't changing, animators were not cancelled.
In addition did we still apply the delay even though animators
were running before.
Change-Id: I05fdd15d770900ac901eb95b616bed4cf311cd23
Fixes: 29540362
In messaging style we sometimes transform an individual
message and sometimes we don't. This causes the ViewTransformationHelper
to sometimes add the container and sometimes the individual messages,
which prevented the right view from getting reset.
To fix this, we now reset all views that were once managed by
ViewTransformationHelper but no longer are.
Change-Id: I1512434fde5b4444657db1c69f9a7bd1ba96fe5f
Fixes: 29509682
Fixes a bug where trust agents weren't able to run during
provisioning, because user presence is only acknowledged after
provisioning completed.
Change-Id: Ib9ed235e8372555fdc40eefd0fc6b1192613abda
Fixes: 29231515
* changes:
Fixed a stackoverflow in notifications
Fixed a bug where a notification was incorrectly marked as removed
Fixed a potential issue where a notification could be empty
Fixed a bug where the expanded layout would flash
When unauto-bundled, it could lead to serious bugs on the lockscreen
and the header not being restored.
Change-Id: I2d6310a2bcb2f3a60402db5f1e522954f8bd0389
Fixes: 29463339
Fixes a race in BluetoothControllerImpl that could lead
to a ConcurrentModificationException, by moving the manipulation
of the callbacks array to the handler.
Change-Id: I7c3be74d239d4706f55357f54e539b7b6439e76d
Fixes: 29390132
When the heads up disappeared from the shade, it's layout would
switch to the expanded state. We're now delaying this until
the animation is done.
Change-Id: I6c5c970f6b471fb10b197922dfea520b07c84abc
Fixes: 29318819
It was possible for the state to be updated in the background
but before the callback was actually registered and never propagate
to the UI. Call the callback directly after it is added (from the
QS thread) to ensure that the current state gets sent out on tiles
being added.
Change-Id: Idd76dce5cbc9dc9c99f9b3dc13998751fd170582
Fixes: 29419435
We depend on a layout listener for when we ask for focus, but layout
sometimes doesn't happen. Make it always happen.
Change-Id: I7c805470c6ce9863bf7eac627f59d49191ce8946
Fixes: 29126464
- The signal cluster dedupes multiple calls with the same value, but
since the first calls come before the rotation relayout, the dark
tint is calculated incorrectly and subsequent calls get deduped.
Ensure that if the layout changes, we also update the tint of all
icons again.
Bug: 29390902
Change-Id: I79c3796cba2f9a94d44f9fd59cf1702a64b62cd9
- Catch the exception when removing a view that is not yet attached.
This is not an issue because we are in the process of attaching it for
the first time anyways.
- Ensure that we post the calls from the secondary user in the main
thread for the system user. Especially since this calls through to
add the view for the new screen pinning window.
Bug: 29341417
Change-Id: If0e29a77ddb67426115f1d5d9f1adb580a1f07df
The backgrounds weren't being updated before the collapse animation when
going to the keyguard so it would look very bad when they collapsed.
This moves updating the background into setChildrenExpanded which will
cover updating the background for both the tapping to expand case as
well as the animating to the keyguard case.
Change-Id: Icba2fa895498d307a38bd9f65be06265afd21a1a
Fixes: 29240532
We reinflated the brightness mirror, but not the QS panel,
which meant we were controlling the wrong view. Now we
reapply the mirror controller on configuration changes.
Change-Id: I69e5f1962e9ec0cfda85b19b1d5d5bbdf3d5779b
Fixes: 29339630
Previously, scrolled notifications would collapse into a stack (the top
stack). With the new design, that's no longer the case, so tall
notifications can now be scrolled out so much that their translation
becomes negative.
Unfortunatly, getBoundsOnScreen then clips the bounds to the parent,
which interferes with our adjustment to the bounds, so we first undo
the clipping.
Fixes: 29368064
Change-Id: I71da054ed1eb6d06868d56e18d0320f764ed86b3
