am: 2486cb2c89
* commit '2486cb2c8978003d2b5cfa7e8169019421582cb0':
Fixed a bug where the chronometer was invisible
Change-Id: Ib495f096b5b2bc758ce7224fae33ba1a44c027a2
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
We were requiring the time to show in order to show the chronomer
which didn't make any sense.
Change-Id: Ia6d00d0932d272a6c5e20e8b41e3acfb53b7987a
Fixes: 28848113
am: 32b54f2e42
* commit '32b54f2e42c4ff793c418c29c0ce9ef0be2a4a16':
Mark occluded home stack as invisible.
Change-Id: Iaa68bb7c93ffd8bcfc9af3e66fd7fced7787a671
am: 96b2fe6a4e
* commit '96b2fe6a4eec82635f39c025ee9c57e99207a3df':
Fix a few issues with ime adjust/minimized dock stack
Change-Id: I29e2d748e77f7773d7fc45440c1f807b25389ac5
- 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
am: 5201a6246d
* commit '5201a6246d12830d0bb766d59e22b0320f2f99dc':
Handle PhoneStatusBarPolicy user switch callbacks on main thread
Change-Id: I561be9cf58d0a43abd43d98cf1ee717241f10ef1
am: bbd26bc023
* commit 'bbd26bc023992ee7bc6a0e682d4a343dfe3dc848':
Refactor how StatusBarPolicy knows if keyguard is visible.
Change-Id: I782d354549ba3185d4779a2e8b3ac6d0724e22ec
- The home stack is still visible when a translucent activity (like
dialer) is on top, which caused us to use the logic path that just
tries to launch the next task. However, that path does not reload
the stack state (since the activity stack generally doesn’t change
while Recents is visible) so it was always launching the already top
activity. The new check ensures that we start the activity anew
as if it was coming from an occluding app.
Bug: 28767764
Change-Id: Iec0fdc0957e5070cec532c5de5cba3454c906a3b
Since LocaleList needs to depend on android.os.Parcelable, we cannot let
that class belong to "android.util" package, which causes layering
violation.
Bug: 28819696
Change-Id: Ia8de2ee9df3dd0a42b1fe84574439519b680fe18
am: a35d9b3ee0
* commit 'a35d9b3ee055d591249a30c58285fe2be5a45c43':
Fixed a bug with auto cancelling
Change-Id: I46be6f420c4ad89ffc7cd88f621aed173ba130d1
- Declare a printers availability when changing the removed state.
- Set printJob.printerId to current printer when returning from
SelectPrinter
Change-Id: Ie4680be04fa614a4088f2f32a527e80928c957cc
Fixes: 27643305
