If we start the forced resizable activity with an existing task,
avoid moving that task to the front. This can cause that a previous
task that was moved to the back gets moved to the front again just
because we started that activity. That's not good.
Bug: 28223489
Change-Id: If8acf31b8be98b82665de1015d5621331c37fb64
Previously, the disabled color was used for the contrast
calculations, which resulted in too dark RemoteInputView
backgrounds.
Change-Id: I99e8b2fa64a22a59fdc5d1be8a6aff5af3523a27
Fixes: 28429720
The transformed view could get updated during the transition
leading to a crash sometimes. We're now handling this better and
make sure the correct values are set.
Change-Id: I1a311cb7c108afeec0fc1c92eb3359c622db7b87
Fixes: 27922191
This plays nicer with SELinux and generally means we can be more robust
about file security policies.
Bug 28403975
Change-Id: I857ee7073c0090c7515421f41c9334025e25bc79
We now have a null object instead of null values and
there was a place where we returned null instead of
the correct null object.
bug:28423485
Change-Id: I2626768acdf8d19fc94aa5e978eb057818450fa5
Because nothing was drawing there with SRC one would simply see
the old buffer there.
Change-Id: Ie7a8989a4af92a05b1e9be2430fd9704c26a125d
Fixes: 27317122
Since we do this onLayout it's unnecessary to update the location here
plus it causes an NPE as the parent may not be laid out yet when
accessing collapsed height.
Bug: 28390732
Change-Id: I3e61eb7ce854002def3342856557d456249e5e26
Prevents swiping out a notification when started on
the RemoteInputView, as this can easily happen during
text manipulation otherwise.
Change-Id: I8f658eab88ca1daf8ffcb7a5d1fac4468f5f0845
Fixes: 28336831
- If a notification is updated, make sure that the focus
is kept even when the change cannot be applied inline.
- Make sure to update the pending intent to match one
of the new actions in case the old one is no longer
valid, and to prevent sending text to the wrong action
unintentionally.
- Keep focus when switching between heads-up and expanded.
- Prevent the action container from becoming transiently
gone during reapplying.
Fixes: 27357771
Change-Id: Ie9f49935827f6efb15b73f8d686f0c110448456a
With I5a40675dd226564c0ee190d0d6f7eb2a7e4673b0, isNull() is used for
null check but accidentally the condition is flipped.
Bug:28406262
Change-Id: I776a6c259765210a7b334a81876233b594fd25ed
We no longer have a null settings value - instead it is a
null object. This change adds a missing null check that is
not changed to check against the null object.
bug:28406262
Change-Id: I5a40675dd226564c0ee190d0d6f7eb2a7e4673b0
A recent change replaced the null state during a setting
lookup with a null object, however missed to update some
null checks to be null object ones.
bug:28405145
Change-Id: I80f0fb3ac6e64f4283b6c617283a009e97a40efe
- We were incorrectly setting the OnClickListener to null to try to do
this, which still causes the touch event to be consumed by the button
view, so instead we should just set the clickable state directly.
Bug: 27859552
Change-Id: Ida3b4a467c6f325ce8fe5a90b0b77c2bdda5a936
