am: a74a6e5ba9
* commit 'a74a6e5ba92d049710de31c5bcf75e3bda4aadcc':
Sync jd_extras/jd_collections with jd_extras_en. make a few minor updates.
Change-Id: I681173818b4f7f4fa8e1d1182b7b30a91fefd834
- Change back the throttling quota to 10 calls / day
- Foreground apps are no longer throttled, and when an app comes to
foreground the call counter will be reset.
- When the system locale changes, reset throttling for all packages
for all users.
See LocalService.onSystemLocaleChangedNoLock() for how it's performed.
Because the reset must happen before any other apps have a chance to
publish shortcuts, the logic is not straightforward.
- Added an internal API to reset the throttling upon inline-reply
from a notification.
- Stop supporting icons from "content:" URIs
- Improved javadoc on several APIs.
Also internal refactor needed to this:
- ShortcutUser.getAllPackages()/getAllLaunchers() are no longer
accessible to outer code to prevent accidentally adding/removing the
content. Outer code should use forAllPackages() / forAllLaunchers().
Bug 27923857
Change-Id: I002511193d1d33718163bb1dabe77610bde58198
Using null will take the pinned stack to fullscreen. We need to use
the existing bounds when pinning an activity if pinned stack already exist.
Bug: 28517964
Change-Id: I9a15a2e4477a2ee0e2f09cf052627034f9ff6023
We need to read the settings when UiAutomation closes in order to
configure other accessibility features from settings.
Bug: 28461805
Bug: 28460671
Change-Id: I030761922ec4acfa2d916e171c39e9dc2deb85a2
There are a number of different conditions that could cause
ActivityManager to fail to fork() a process. One of the most common
ones is a package being "frozen" during a PackageManager operation.
When this happens, use the common forceStopPackageLocked() method
to cleanup any internal bookkeeping structures. (It's slightly
misnamed, since it doesn't actually "force stop" the app.) It's
also the same method that we called moments earlier when the package
was first frozen through KILL_APPLICATION_MSG.
Bug: 28395549
Change-Id: I7b1623c5f66fc1de24cad5360c977ea764d09244
Previously, we only looked at whether home task is going away or
getting visible. This doesn't work anymore, as we also need to
un-minimize docked stack if another task is visible with translucency
over the home task.
Change-Id: I993f58a25d99d2ef9f562f7d1587c2dec0d05142
Fixes: 28434466
Fixes: 27906038
Pinned activities are normally in the paused state so when finishing
they can finish immediately as there might not be additional transition
in the system to finish them.
Bug: 28434641
Bug: 28350881
Change-Id: I5f1eaf0969a7eb08292cb9cc123bf8c0fddc9ea8
We migrate the existing (shared) system wallpaper to be the lock-only
wallpaper when setting a new system-only wallpaper. The end result
is that if you say "set the system wallpaper only" the lock wallpaper
won't change.
(The migration is via a rename of the underlying imagery files, not
via copying, because copying all that data would be silly.)
Bug 27599080
Change-Id: I03ecf23c943fe88af58d5ac26f05587a15e2d0a9
The record might already be removed and the records array set to null
when the binder dies, hence handle the scenario.
Bug: 28512952
Change-Id: Id21b03b6d14d1dc8cb792ee4ec0519287a289a33
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
Adding missing items about MIME type and account type to the
"integration with the Contacts Provider" section.
Bug 28295510
Change-Id: I890458e62a714519be70e930fd53315c141ba354
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
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
