am: 1669d42808
* commit '1669d42808251eebddfe5e176eb8d322b84df636':
Never set resized while not drag resizing for pinned stack.
Change-Id: I5da72476c63c5f368e7ff8c1269308d206761ffd
It's not necessary in the pinned stack and interferes with the
animation. It's not enough to just check getBoundsAnimating, as
we turn that off prior to the final resize so that we unmute
notifications to the client.
Bug: 28559097
Change-Id: Iae180c8a8ca0585184efcf24e7677557a33678eb
am: b5b03bc450
* commit 'b5b03bc450235ffa85ac636da460b61f1e99bff1':
Mapping up/down of legacy Gps vs. Gnss Status
Change-Id: I2ff6c7714ecca01cb75176452cdbd2ec969fc937
am: 090bf55130
* commit '090bf551308e68b1b2a996c959b608cabd025c5c':
While turning OFF do not honor ON requests.
Change-Id: I528c640a9bc482fbbec3b11eef6569c93a632b76
Native stack does not handle being put from OFF -> ON state without
doing a complete cleanup. Hence instead of going from start -> ON -> OFF
-> cleanup it goes start -> ON -> OFF ->ON -> ... usually leads to race
conditions down the road in native.
This patch is a workaround so that we can throw away the requests if we
are in currently "turning off" phase. The side-effect would be that user
will need to turn it ON again. The race happens when the turn OFF time
is longer but usually it is found to be close to order of seconds hence
the wait should be bounded.
Bug: b/28318203
Change-Id: I14f6633f31311e5b561e1dcbc8a9d6d2a5dd6fdc
- Maps incoming (from HAL) GpsSvStatus for Glonass, Beidou, SBAS, and QZSS
from defacto (NMEA-like) numbers to internal platform with detected constellation.
- Maps outgoing (to Java API) GpsStatus getSatellite info back into the de-facto
overloaded (beyond 32) "GPS" ID numbers.
- Simplifies Glonass ID definition for N (comments only.)
- This enables GPS/GNSS Test apps a non-degrading upgrade path.
Bug: 28623392
Change-Id: I9a19db1f11267032c6927daed767df5afa51c770
am: a75bd7d4e0
* commit 'a75bd7d4e01985c8ad8aa57960337cc3507f374a':
Fixed a bug where autobundling could lead to bugs
Change-Id: I41033eaf326565f73cd2cbb2eb0d2a16be0e430f
am: d171df660e
* commit 'd171df660e19bdba4d188beeb8b6023874712413':
Lock down networking when waiting for always-on
Change-Id: I34fffb119eecef0052be673f307ef63c94fc58ee
Notifications could appear twice if a notification with an app
group became bundled and one could not be swiped away anymore.
This is because we were unconditionally copying over the override
key even if the notification just became a group.
This also fixes a nullpointer that could happen with a racecondition
when a notification was cancelled and it tried to be used for autobundling.
This also fixes an issue that the autobundling wasn't working correctly
when a notification didn't have a group set but was set to be a
group summary.
Change-Id: Icd971f16ae0804ce162fd3171fcdd99bd04f3885
Fixes: 28706404
Fixes: 28628237
am: 56a9395aeb
* commit '56a9395aeb198e0a7db5e9666cc81ba7ce5f8e0d':
Two phases to set the password for disk encryption
Change-Id: I76b3b1351ea85d8a5e42da523f57a291b3a1b0d9
am: 32b54f2e42
* commit '32b54f2e42c4ff793c418c29c0ce9ef0be2a4a16':
Mark occluded home stack as invisible.
Change-Id: Iaa68bb7c93ffd8bcfc9af3e66fd7fced7787a671
During the PiP animation, we have two basic requirements:
1. We need to scale windows to the pinned stack bounds.
2. We need to halt resize and movement notifications to the client.
As we end the animation, we need to disable these states at differing
times. First we need to deliver a final resize and movement notification
to the client for it's new position. However, Surfaces may not
immediately resize (in particular in the case of child windows,
it may be some time!), furthermore Surfaces may resize at different
times so we need to persist scaling on a Surface by Surface
basis after reenabling resize notifications.
Bug: 28559097
Change-Id: I6d52a3e213e08a34f4c0eea892b2a84cd4c20e18
We want to calculate the scaling factor we need to have
the content area of the surface (not including insets) to reach
our desired size, otherwise we will seem to scale the insets
up or down over time.
Bug: 28559097
Change-Id: I86dbd5fc902b5d380d33dba626c6694b3c57ff25
am: ab0744344d
* commit 'ab0744344db3e626f1a249f285289b66653cf6bb':
Fix a deadlock in system server
Change-Id: Ib223cf25d4ac53225e9e8791bdae497956dc8471
am: 96b2fe6a4e
* commit '96b2fe6a4eec82635f39c025ee9c57e99207a3df':
Fix a few issues with ime adjust/minimized dock stack
Change-Id: I29e2d748e77f7773d7fc45440c1f807b25389ac5
am: 3bed1c0ef8
* commit '3bed1c0ef8a66c4ce064b1c6ee443681070c5fcb':
Explicitly close pipe end when we cease operations...
Change-Id: Iefb271ac59812bee8e271bbfe6fc73fcd60c4581
- Do not override minimized state in SysUI when IME adjust change
comes in.
- Do not animate IME adjust if we are already animating for minimized.
This lead to problems that we animated the minimized state with the IME
adjust values.
- Make sure to update state after checking whether the IME adjust is
animating. This is to fix an issue where sometimes the IME adjust
animation didn't run because the old target was wrong.
Change-Id: Ie35e2f943a4cda99ffdc6f14663d892863759e46
Fixes: 28819201
...because the other in-VM reference to that FD means that it won't
get GC'd after we release our local reference to the containing object,
and we wind up with the feeder end blocking on write to a still-fully-
open pipe rather than being made aware that the read end has needed
to shut down.
Bug 28756668
Change-Id: I90b6aaeaabe7d912d96d7ef57c24f68d87d9d0ab
