Currently a native APEX can get and use a VINTF AIDL. However, this
can't be passed over JNI to be used by Java code.
This does not open VINTF AIDLs to any type of apps, where AIDL as an API
is completely disallowed. Also, no Java ServiceManager APIs are
available, and they couldn't be until b/139325468 is fixed.
Bug: 161501127
Test: atest binderVendorDoubleLoadTest
Change-Id: I1ab977248b1c39a7d08e0ca34389a7ba168c05b0
Add HapticGenertor, which is an audio effect that can generate haptic
data from audio data.
Bug: 136490803
Test: atest HapticGeneratorTest
Change-Id: Ib677f0ad82ae4a164546300c7a86760cdb6a52b4
This CL adds a system API to NotificationManager for checking whether
the NotificationListener for the current package name and user id is
enabled or not.
This replaces existing implementation which was using binder calls
directly to NotificationManagerService.
Bug: 160762852
Test: atest CtsMediaHostTestCases:\
android.media.session.cts.MediaSessionManagerHostTest\
#testGetActiveSessions_withSession2
-> MediaSessionManager#getActiveSessions verifies call by checking if
the notification listener is currently enabled.
Change-Id: Ic730b0abfe08c40171062421b2015be9cc05310a
This app op was introduced to support --no-isolated-storage
instrumentation flag in MediaProvider mainline module. Because it was
very late in the release cycle, app op wasn't exposed as @SystemApi in
rvc-dev, even though there CTS tests written around it, and
MediaProvider module depends on it.
To make things fair, expose it as @SystemApi.
Test: atest CtsScopedStorageHostTest
Bug: 159708202
Change-Id: Ifddf2cb920285eda5f859972937b0f9084fc32a3
SUBMIX type can be returned by routing query APIs such as
MediaPlayer.getRoutedDevice(), make it public.
Bug: 160819170
Test: atest AudioHostTest#testTwoChannelCapturingCheckSubmixDevice
Change-Id: Ie5854ad86464c40137d0a1b10420116bc5cc270e
Expose the MmTelCapabilities#isCapable() API to complete
a chain of APIs exposed for debuggability in Android RVC.
Without this API, there is no (public) way for a caller that
receives a capability callback to determine whether a particular
MMTel feature is enabled for a particular IMS Connection.
Bug: 156107100
Test: make update-api && make offline-sdk-docs && make
Test: cts - ImsServiceTest#testCapabilityStatusCallback()
Change-Id: I0a0d72897112460370e6981ae33cef4da6e3ce4b
Two APIs were added as @SystemApi and then @Deprecated within
the same API level (RVC). These methods were never exposed
publicly, and instead were replaced with more-appropriate
named methods that were added to the public API. As such they
were not fully deleted in RVC but were never exposed and expected
to be deleted following SDK finalization. This CL does precisely
that - removes all traces of these methods, as per the will of
the API Council.
-Remove #getDataConnectionLinkProperties()
-Remove #getDataConnectionNetworkType()
Bug: 152787887
Test: make update-api && make
Change-Id: I89463b0bd641e9316f90fe4f535d326f6e74a061
Since Android R, the FUSE prop is always on and FUSE-off is no longer
supported
Test: m
Bug: 160159282
Change-Id: Ia815c39d898b05bf8082ec5b7dfd903cc9e150bc
When config_remoteInsetsControllerControlsSystemBars is true,
DisplaySystemBarsController provides its own policy of how system
bars are displayed for specific packages. Currently limited to
only auto versions of Android.
Bug: 149585273
Test: Manual, atest BarControlPolicyTest, atest InsetsPolicyTest,
atest DisplaySystemBarsControllerTest
Change-Id: Ie6b1cc3e2760cbc9e48d62dfbd8bc3e23ffca20c
Merged-In: Ie6b1cc3e2760cbc9e48d62dfbd8bc3e23ffca20c
When config_remoteInsetsControllerControlsSystemBars is true,
DisplaySystemBarsController provides its own policy of how system
bars are displayed for specific packages. Currently limited to
only auto versions of Android.
Bug: 149585273
Test: Manual, atest BarControlPolicyTest, atest InsetsPolicyTest,
atest DisplaySystemBarsControllerTest
Change-Id: Ie6b1cc3e2760cbc9e48d62dfbd8bc3e23ffca20c
Bug: 159443507
Test: Built and flashed onto local adt-3 device
Test: Ran tests from ag/12034683
Test: Attempted to execute resetAppErrors via
adb shell service call activity 219
Change-Id: I3723d9aae18679b4292c6efb8549563063d64b98
Remove this method, which is undesirable, has unfortunate
side effects, and which is a worse way of getting the current
location than other methods such as TelephonyManager#getAllCellInfo()
(since KK) and TelephonyManager#requestCellInfoUpdate() (since QT/11).
Bug: 152648516
Test: make update-api && make (docstring-only change)
Change-Id: I3c7d345abcdd8c35cf539d33166ddf76ba987b1c
Several partners with devices that have small displays have run into
issues w/ CTS-on-GSI testing as these builds hardcode support for
split-screen. This prevents split-screen from being reported as
supported if the display isn't compatible according to the CDD.
Bug: 158310372
Test: android.server.wm.SplitScreenTests#testMinimumDeviceSize()
Change-Id: I0dfd6caca5116dccc115d64b755998171abe831f
The previous version of the file was generated from R
and was missing baseline entries for lint warnings
that were added to AOSP since March 2020.
Bug: 160405597
Test: built locally
Change-Id: If17fa952e9ca5b246eba9f4556b7ff13e5dc18d6
API guidelines recommend adding ability to set the executor
Bug: 156046799
Test: atest HdmiControlServiceTest
Change-Id: I1f6dde6efc498a112ac7da2c61c36fcc2afa6638
Broadcast intents on below control request
Log both the request and response for 51 control request (Get Protocol)
Log both the request and response for 52 control request (Identifying information)
Log both the request and response for 53 control request (Start accessory mode)
bug: 139264039
Test: Check the broadcast intent could be received
Change-Id: I7c8db41ee05398200e235cf10dde96ba89b306e8
Support API: get current supported channel list
Bug: 151189102
Test: atest frameworks/base/wifi/tests
Change-Id: I2decc0764243fb61e3b42b83eb04f83fab2270db
