am: f4810f5506
* commit 'f4810f5506203ac03439d1ed6e33e021540568f8':
Add api to WearableExtender for setting and getting the dismissal id. Bug:27696581
Change-Id: Id88f0a6b35750313554ee2e52347ac51c45e88c8
am: e0e6cf8e87
* commit 'e0e6cf8e877d9b748c5f2b10e5bccdc037e5afa7':
Clarifies that filesystem permission 0700 is not enforced as an invariant
Change-Id: I5220a77379927c680c995b3872dc34ee53d1f54e
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
The 0700 permission on apps' home directories is not
enforced as a invariant. This change to the behavior
changes documentation reflects this.
Change-Id: I2257796b804574f3c6c7d273957625f4458fe81b
(cherry picked from commit b25a17b3ea)
Drag handles are blocked from being shown if batch edit mode is active
when onPreDraw is called; however, IME can start and end batch edit
mode regardless of onPreDraw timing.
As a result, drag handles are sometimes not shown even if selection is
created and text action mode is started.
With this CL, drag handles are shown after finishing batch edit mode
if the handles were blocked from being shown in the above case.
Bug: 28366507
Change-Id: I7f099d0626bee70a63bb14bc75eefc2551a52d53
Currently AppFuse tries to terminate its message loop when it receives
FUSE_FORGET. But kernel continues to dispatch messages after FUSE_FORGET
and it should not terminate AppFuse meesage loop.
Change-Id: I070a71c35a8d80bcaaf7603305d219e65be97bc9
Fixes: 28508169
When entering split-screen mode by long pressing the recents button, the
top task in the fullscreen stack is moved to the docked stack and the new
top task is the fullscreen stack is considered visible for a short amount
of time until sys-ui launches the recents activity. This causes the new
top activity in the fullscreen stack to be relaunched due to configuration
change.
To fix this sys-ui now sends an hint to activity manager to move the home
stack forward so that it can be on-top of the fullscreen stack and makes
it invisible before recent is launched and animated in.
Bug: 28470261
Change-Id: Icfd85e932fe913dfb498752b5878cc7c690fd559
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
am: e7fefcb565
* commit 'e7fefcb5650afddff544c008bc06ce748f635727':
Set ActivityInfo.resizeMode to RESIZE_MODE_RESIZEABLE by default
Change-Id: I8755b8cae62fe4fb86a9015ffefd04d009b5eb58
Adds the diff command and various small fixes to issues
discovered when diffing old AAPT built APKs with new AAPT2
built APKS.
Bug:22775504
Change-Id: I682a7fe1cf4b3efa7cbd5d18b333cf2d1046fe1b
Transition is not set to ready until it's executed, which could happen
a bit later after the setAppVisibility where we set up the dummy.
It is rare, but an animation pass could still slip in between, and
since the transition is not ready, it modifies the scale and show a
bad wrong frame.
bug: 27742244
Change-Id: I97fb1955e810c7c4f01dc55a28d2e4ce4f47d5eb
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
...300mS in bindService
Make the "slow proc start" debugging more aggressive, so it will
catch cases where it is taking more than 50ms to start.
Change-Id: I6f6eb749cf205f9890946b3ec562b7653674c3d9
GmsCore will use different filenames to distinguish a security update
from a normal update. (update.zip for normal update and update_s.zip for
security update.) So, if framework observes the filename as
"update_s.zip", write command "--security" to BCB. This cmd ask the
recovery image to choose the right background string for update.
Bug: 27837319
Change-Id: I2ef12267a6be57d8a81f7f9f34c09aea54530c1f
am: 9a977b7d45
* commit '9a977b7d45df0d3d59c5eec7f9534c3bd5fcd91d':
Flag to mark foreground jobs, fix data saver.
Change-Id: I358ac7296a4409c2ee1ca3e53bfbdc0af57693bf
- 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
am: 0e9e5ea586
* commit '0e9e5ea58600a7b6aed1b307affdc400bfa9b33b':
Only platform defined permissions need a review.
Change-Id: I3a70903e01ab16e3ba3d2e56017570c91d4af4c3
