- Icons are now persisted. (under /data/system_ce, as PNGs)
- the "load icon" APIs in LauncherApps are supported.
- Implement updateShortcuts()
- Addressed all the comments on the previous CL
- @hide the newly added constructor for PersistableBundle
- Enhance incoming shortcut validation
- A lot of internal clean-up.
Bug 27548047
Change-Id: I8e3c1ccd3e0a997a6d271c84d81170f0c022b60e
...Blocked in monitor com.android.s
There was a change awhile ago to make the IInstrumentationWatcher
callbacks synchronous, to avoid issues with them spamming non-responsive
watches and filling the binder transfer buffer. However, you can't
just do this, because the activity manager calls these with its
lock held.
To allow them to stay synchronous with the activity manager getting
blocked on the watcher, introduce a new thread for dispatching calls
to the watcher. This thread is created as needed, and dispatches
a queue of callback commands to make to instrumentation watchers.
The callback is still synchronous, so it won't dispatch a new one
until the previous completes.
Change-Id: I8384bd475a1a004c567a4ae20ea64385244f45c5
Seems like mCurrentPackage name can get stale and the optimization
to cache is isn't all that needed so remove it in the name of app
launch reliability.
Bug: 27505472
Change-Id: I641284c1392f8ff1f392f8dbf2c31177a64b4326
During development one needs to be able to test changes conveniently,
and when the jobs would normally have hard-to-simulate constraints
like idle-time or long minimum latencies, testing becomes difficult.
This CL introduces the ability to run a specific job immediately
from the adb shell.
Without the "-f"/"--force" flag, the job still won't run if it has
unmet "functional" requirements such as being connected via an
unmetered network. With that flag, the job will be run immediately
regardless of its declared constraints (so it may not work properly
due to lack of network connectivity or similar).
Bug 27501783
Change-Id: Icc046f53f8846690c8234e60066e85c283d325ce
When draging down the y positions were animating even though
they didn't need to as they were not scaling anymore.
Bug: 24866646
Change-Id: Ied6c39a32522756b5f4d8eab7203c87d1958c278
This ports my previous CL for InputMethodManagerService [1] to
TextServicesSettings (TSMS).
With File-Based Encryption (FBE), now we have yet another runteime event
to reset TSMS state in order to keep the list of available spell
checkers updated.
See my previous commit message [1] for details about the idea.
Rebuild spell checker list when the system becomes ready.
[1]: Ifa2225070bf8223f8964cf063c86889e312c5e9a
0e367d08aab2c1cb2d0fb9cbf1e8a6d09d1ac523
Bug: 27456430
Change-Id: I2b5a6989a99fd18b3bf109f5cda6270ccadaaf6d
static VectorDrawable should be returning Transparent while root alpha is 0.
AnimatedVectorDrawable running on RenderThread now, and the opacity should
be conservatively set as Translucent.
http://b/27554766
Change-Id: I9a78696cab94f10ba40a733cc9c00f1c2d7ebb7f
This ports my previous CL for InputMethodManagerService [1] to
TextServicesSettings (TSMS).
This is a preparation for File-Based Encryption (FBE) support in TSMS.
With this CL, we start switching TextServicesSettings from copy-on-write
mode to real mode and start rebuilding the list of available spell
checkers when the system becomes ready. Anything else should be the
same. See the previous commit message [1] for details.
[1]: I9c6f9bb3d51174198e5f73588637f87ea0d90e11
68645a638ad1bfb734b2b0f56b17fe206bb891c5
Bug: 27456430
Change-Id: Ie3d61458648df469abe149b7aaad8087c531a675
The orientation field is not expected to be present in subIFDs.
With this, the new DNG validation CTS checks pass.
Bug: 23727371
Change-Id: I959fd84bc196adbbba1de2c4369e25f568411168
This is a preparation CL to make TextServicesManagerService (TSMS)
encryption-aware.
This CL changes nothing except for the output of TSMS#dump().
To diagnose File-Based Encryption (FBE) related issues, it would be
useful if we can see if each spell checker service is encryption-aware
or not. To do that this CL updates TSMS#dump() so that it can include
the result of ResolveInfo#dump() as we have done in
InputMethodManagerService.
This CL also updates TSMS#dump() so that its output can be more
consistent with IMMS#dump().
Bug: 27456430
Change-Id: Ie2321278f1d52533a3cd74d98f1f84c950a8f6d0
Frequently, trust agents are not running because
a successful unlock is required for them to start.
Unfortunately, that means they were not able to receive the
successful unlock. To fix this, we'll now override
StrongAuth requirements and start agents early if we
detect a successful unlock.
Bug: 23021202
Change-Id: Ie85f78d9ce2823dd5c9b6215a52db069fb796d91
