When the user gets unlocked we schedule a handler-runnable to do cleanup work.
This runnable might be executed after the user is already locked again.
Fixes: 28512952
Change-Id: I6c05cbc8adab699e451565d74d56ad0f9b965954
ResolverActivity launches activities it resolves as the initial caller.
In the case of the home intent it can be sys-ui, but only the system
server is currently allow to launch things into the home stack, so the
resolved home activity is placed in non-home stack. This wasn’t a
visible problem in fullscreen mode as the user would notice since
everything is fullscreen, however it is very visible in multi-window mode.
We now allow home activities to be places in the home stack if it is coming
from the ResolverActivity.
Bug: 28487506
Change-Id: I68f81da68a207efab9ce911fa6661bd573f1e949
When an app updates to change their default tile icon, pick up on
the change. When listening this comes from the TileLifecycleManager
and when not listening this guts picked up next time listening starts.
Change-Id: Ib730f02ed54ca1c1ba72ce50adf7dcf91f01738f
Fixes: 27911877
am: 38d54f72e3
* commit '38d54f72e3795eb67eceacf5325b14a13492b25d':
Clarifies that filesystem permission 0700 is not enforced as an invariant
Change-Id: I12d68857f2fed0bb62b040df4193fc00cc97f500
am: d92fe240b9
* commit 'd92fe240b9811bd1b20af0b744f1aa727c80b97c':
Clarifies that filesystem permission 0700 is not enforced as an invariant
Change-Id: I7371da3bffa54b8904bd18d52b9803fb45afa31e
am: 73813c06cd
* commit '73813c06cd59a94fe53483b657fa58e954c97551':
Clarifies that filesystem permission 0700 is not enforced as an invariant
Change-Id: I92bcad43201a90273af9428a1a0a97e7e66b03bb
This causes foucs to move to the current activity in the stack which isn't
needed. Focus will be moved when the new activity is started in the stack.
Bug: 26381750
Change-Id: Ia76962dc5ba3ce336d2a4e074d14db06eebbe78c
During stopAllRecognitions(), the internal state of a sound model was
being cleared (which made it look like the model was being unloaded).
However, the model was still loaded, so subsequent calls to load a 'new'
model would break.
Bug:28432002
Change-Id: I7090bf52704c6e46e3bb6d495d8fe4b8a1d9e2ad
Do not enforce unlocked state when running on the background thread. User can
be in the stopping state or removed by the time the message is being processed.
Bug: 28471878
Change-Id: I1862849661d93b424a07ea94e80563bea7a94ce5
Previous assumption was ActivityInfo was completely initialized in
PackageParser, but that isn't the case with the ResolverActivity
whose ActivityInfo in populated in PackageManagerService.
This was causing the device to exist multi-window mode since
the default ActivityInfo.resizeMode was 0 (RESIZE_MODE_UNRESIZEABLE).
Bug: 28378995
Change-Id: I46e58d434f2a0274c461a8ff00b59ed3d2a1dd52
- The PrintActivity has to handle all config changes to not loose track
close the connection to the printing app
- In the case where onDestroy is called we need to make sure to
- not do any more UI operation
- on async calls after destroy is already called, handle failure to
unbind services.
Change-Id: If21335543fbfa16ecfe77d1965b2e8a13dfa14b8
Print throttling counters per each component and time remaining before
counters will be reset.
Also adjust estimate of space needed for events serialization.
Bug: 28204408
Change-Id: Ib57a24db554645e9f933126da00ef74c23097d1c
By declaring a <restrict-update> tag in its manifest, a system package
can restrict its update to be the singular package that has the same
given hash. An update's hash is the SHA-512 across all its APKs [i.e.
for splits, the SHA-512 is calculated over the concatenation of the
base plus all splits].
The restriction only applies to system packages.
Bug: 28398205
Change-Id: Iec493fc8ef27edee53f1d437cb0caaa78782f329
