am: 0751a83
* commit '0751a83a99dc4481533ed706a942b8bb9caf8834':
TIF: Be consistent with argument name for startRecording
Change-Id: I27de469a898051caa8e7e41ca170c79ac0e7e3d1
am: 7981e8f
* commit '7981e8ff6509769a590f15b440f989437d732be5':
Unbundle RemoteService on TV - part 3
Change-Id: Ib5eb6363e904a1f66000d12263f66a8e5bd1f663
- New service TVRemoteService triggered by SystemServer
- Provider service proxy and watcher for maintaining connections to unbundled
services which have the BIND_TV_REMOTE_SERVICE permission.
- Shared library to facilitate connections between unbundled service and
TVRemoteService.
- Unbundled service needs TV_VIRTUAL_REMOTE_CONTROLLER
permission to be fully functional.
b/23792608
Change-Id: Ief5c6995883d1f7268a73bdd0c920c4c3f42cddb
Replace usages where the Long is immediately unboxed or thrown
away with Long.parseLong().
In TaskRecord.java, I also fixed up similar uses of
{Boolean,Integer}.valueOf()
Tested: built frameworks/base successfully.
Bug: 28289401
(cherry picked from commit 4bd017d6a5)
Change-Id: Icfa4708946e774f4a1bacf185c3fd11a7087017e
am: b9c64cd2c0
* commit 'b9c64cd2c06933eda7ff1e691b80c53a74ff09d7':
Handle API review comments from the council.
Change-Id: I9f082a99d5c8cbce3aaa9708f5f0ea75cc5a9ed6
Test all A2DP type variants when checking if an A2DP device is connected
in isBluetoothA2dpOn().
Bug: 28286051
Change-Id: I756d632b12d584d8a27cc1890e758d8accff7120
am: 2faac0d
* commit '2faac0d74169ddc1f54f9cd356dc23b96a74c9eb':
MidiDevice: do not open ports on closed device
Change-Id: I6f98e504d682a5902dd29f5fa54023e7a8bc9814
Previously MtpDevice#readEvent does not have throws IOException at its
definition, though internal JNI functions throws it.
BUG=28254719
Change-Id: I4e6cf8003d168b7e732c4b4eb2eafe52a12442c2
am: bfa6d23
* commit 'bfa6d239b578fabd34781c11711a5413322efa6c':
MediaBrowserService: Provide a way to retrieve root hints
Change-Id: I632db5f48f65b189b0e21f858a7b091bb06ea102
* MtpEvent: Remove public constructor since properties cannot be set
directly.
* MtpEvent: Move event constants from MtpConstants to MtpEvent class.
* getPartialObject64: the byte[] must have indices of Integer.MAX_VALUE
at most. Document as such.
* sendObjectInfo: what happens if the transfer doesn’t succeed? How is
the app notified? If there is a reason for the failure communicated,
how does the app find this out? Add docs.
* Add isOperationSupported(int) and isEventSupported(int) helpers.
Change-Id: Ifd80016d2ddd3b66d5c45f6da76b6133f0c9a617
Fixes: 28146379
am: 865cef4
* commit '865cef475dd4b0ffcb4df0dd62cb86d4ce65ab08':
ExifInterface: keep the original metadata data instead of strings
Change-Id: Ie02b5ac90a8dde0389ace4bcae081f8bd4e064a0
This CL makes ExifInterface store the tag values as the original forms
and the format validiation is added that compares the given value and
the data format specificed in EXIF specification in order to keep the
valid tag values only.
Bug: 27583378, Bug: 27614052, Bug: 28075709
Change-Id: If60bbddefe74c4b87b4ce64b5fc79e467e36a5b9
am: 4a18235
* commit '4a182358c49c1f153177e9ca8f61ff12e4395806':
Player superclass for handling AppOps features
Change-Id: I56e418afaa0a081a1df52c32608582e86d64c823
am: 067f821
* commit '067f821ec84d3bcb556a8de77f3e3d3b8c042186':
Use a binder instead of a bundle in removeSubscriptionWithOptions
Change-Id: Ie6cd52b5169c9b29d437fc04fc1cd71881eede22
Add a new class to group media/audio player features under one
interface. Currently only used for audio-related AppsOps
restrictions. In the future can group routing, audio focus
handling by the framework...
MediaPlayer inherits from PlayerBase, and overrides the methods
that are needed to delegate the handling of the restrictions
in a separate class.
When AppOps restrictions change (as triggered through the
callback in PlayerBase), reset the volume to its value intended
by the application (when unmuting) or the framework (0 when
enforcing the restriction).
Bug 28069414
Change-Id: I2f38e4b9b3c029778836868cf78f4d15d7603247
am: abaa339
* commit 'abaa3395e94754563fb4b07d077e5e87d41f6a17':
TIF: Update documentation on time shifting start/current position
Change-Id: I1bffba2462cdd443860249830b4b8cf9b32df6b8
Now that we use the same set of API for both time shifting and
recording, the descriptions should be updated to support both use cases.
Bug: 28067038
Change-Id: I036446eca373ca27005f74b008a259f27b7c5f61
