Add disting of the following for the sdk:
- android-non-updatable.txt
- android-non-updatable-removed.txt
- removed.txt
Bug: 158544979
Test: m sdk dist && inspect out/dist/apistubs
Change-Id: I5f628f4fcfc13f67105ee3b2760274e900fc1e34
Stop tracking the ART APIs in the non-updatable current.txt, and
instead add in the txt/srcjar/jar files produced by the art module's
java_sdk_library.
Bug: 173606718
Test: manual last_released check of merged api txt (b/174847574 to
automate)
Change-Id: I446a381f2b364a114ce391b99a13742d6769f14d
This removes the i18n source from the non-updatable stubs which removes
them from the frameworks/base/core/api files too. The API is still
protected by both the build and Gerrit review as the API is specified
in the external/icu/android_icu4j/api/public/ directory.
The i18n stubs source is used instead of the implementation source for
generating the JavaDoc. That revealed a minor issue with metalava which
is fixed in this topic.
The i18n stubs library was statically included alongside the conscrypt
stubs library so it will still appear in the monolothic android.jar.
Bug: 174344410
Test: m offline-sdk-docs
- check that i18n classes are present
m android_stubs_current android_system_stubs_current android_test_stubs_current
- check that i18n classes are present in each jar
m droid
Change-Id: I744c8bac54a8a5518ca0eca2a7700abbfa0997f4
As general background, OWNERS files expedite code reviews by helping
code authors quickly find relevant reviewers, and they also ensure
that stakeholders are involved in code changes in their areas.
Some teams under frameworks/base/ have been using OWNERS files
successfully for many years, and we're ready to expand them to cover
more areas. Here's the historical coverage statistics for the last
two years of changes before these new OWNERS changes land:
-- 56% of changes are fully covered by OWNERS
-- 17% of changes are partially covered by OWNERS
-- 25% of changes have no OWNERS coverage
Working closely with team leads, we've now identified clear OWNERS on
a per-package basis, and we're using "include" directives whenever
possible to to simplify future maintenance. With this extensive
effort, we've now improved our coverage as follows:
-- 98% of changes are fully covered by OWNERS
-- 1% of changes are partially covered by OWNERS
-- 1% of changes have no OWNERS coverage
This specific change is automatically generated by a script that
identifies relevant "include" directives.
Bug: 174932174
Test: manual
Exempt-From-Owner-Approval: refactoring with team leads buy-in
Merged-In: I3480ddf2fe7ba3dfb922b459d4da01fa17a2c813
Change-Id: I3480ddf2fe7ba3dfb922b459d4da01fa17a2c813
Nothing depends on these anymore. The same data is available through
the build artifact framework-base-api-current.txt.
Bug: 171029603
Test: m checkbuild
Change-Id: I13d9373f7174e2ff2bc54122a1fcfae0b7f7293c
Merged-In: I13d9373f7174e2ff2bc54122a1fcfae0b7f7293c
(cherry picked from commit b5ec8a9a10)
This patch adds a shim around the Keystore 2.0 AIDL spec. The new shim
is modularized like the AIDL spec into the base Keystore module
Keystore2, the security level specific interface KeystoreSecurityLevel,
and the operation specific interface KeystoreOperation.
Other system maintenance specific interfaces have yet to be added.
Bug: 159476414
Bug: 171305684
Test: None
Change-Id: I070f73739e4b37ce10568939ac666e40b14a52a8
Nothing depends on these anymore. The same data is available through
the build artifact framework-base-api-system-current.txt.
Bug: 171029603
Test: m checkbuild
Change-Id: I8d5f0a132aa307d88fbc2bd7521cdd4bdd8c6cee
Merged-In: I8d5f0a132aa307d88fbc2bd7521cdd4bdd8c6cee
(cherry picked from commit d5cba3455f)
Provide API to retrive bandwidth per primary carrier
and secondary carrier
Bug: 162373679
Test: New CTS test, unit test, build
Merged-In: I3e8152d22fb9602c7d2ffdee681ac5d69c5dd3fd
Change-Id: I3e8152d22fb9602c7d2ffdee681ac5d69c5dd3fd
It retruns whether the caller has InCallService access for the companion
apps. A companion app is an app associated with a physical wearable
device via the {@link android.companion.CompanionDeviceManager} API.
Test: cts
Bug: 169595473
Change-Id: Id659bfae8556e965d3c31613848bde808f28a858
Merged-In: Id659bfae8556e965d3c31613848bde808f28a858
(cherry picked from commit 4d0652699a)
This patch adds set/getSecurityLevel to KeyInfo and KeyGenParameterSpec
and it deprecates the superseded function isInSecureHardware.
It also deprecates the system API set/getUid and replaces it with the
more generic set/getNamespace.
Test: None
Change-Id: Id2f54596510954862b5077a935f3daf07211f29c
The sources of the stubs are shipped as part of the public SDK.
Currently the SDK depends on the output of the monolithic metalava run,
but it can be assembled by merging the srcjars of the individual runs.
There is a diff -- module stub sources contain javadoc comments. I don't
think has any negative impact. Also package-info.html files are
included, which probably is fine.
Bug: 169034951
Test: diff new output with existing monolith
Test: TARGET_BUILD_APPS=foo m nothing
Change-Id: I851ff8e87476b8e22abdcfe1d75da5d82030f302
Merged-In: I851ff8e87476b8e22abdcfe1d75da5d82030f302
(cherry picked from commit 89c74dc41c)
This permission is intended to be used internally as a system App Ops permission, and let CompanionDeviceManager or RoleManager to grant with
users. If it is granted by user, the corresponding companion app has the ability to query the details of the ongoing calls, and also manage its life cycle.
Bug: 169595473
Test: atest ThirdPartyInCallServiceAppOpsPermissionTest
Change-Id: Ie0f790aab2edcd52cfdbded2630347b9f8dd4d49
Merged-In: Ie0f790aab2edcd52cfdbded2630347b9f8dd4d49
(cherry picked from commit 334ab546e4)
* changes:
Keystore 2.0 SPI: Adding the keystore AIDL interface to frameworks
Keystore 2.0: KeyProperties SignaturePadding is now public but hidden
Keystore SPI: Add SecurityLevelEnum to KeyProperties
This patch adds the SecurityLevelEnum to KeyProperties. This enum can be
used by the public API surface to express levels of enforcements of key
properties. And to select a designated residence for a newly generated
or imported key.
The values UNKNOWN and UNKNOWN_SECURE are used to convey to older target
APIs API levels that have not been defined when they where published.
Test: None
Change-Id: I88681f21b8a8ea9a383d32ba99f3ab7d7c8909c3
The sources of the stubs are shipped as part of the public SDK.
Currently the SDK depends on the output of the monolithic metalava run,
but it can be assembled by merging the srcjars of the individual runs.
There is a diff -- module stub sources contain javadoc comments. I don't
think has any negative impact. Also package-info.html files are
included, which probably is fine.
Bug: 169034951
Test: diff new output with existing monolith
Change-Id: Idfc94cdb3317d3bde0b29fd8da0a9ccef47377f9
Merged-In: Idfc94cdb3317d3bde0b29fd8da0a9ccef47377f9
(cherry picked from commit 5d0687a2ef)
The other non-updatable API files are in core/api/*. Also add
-non-updatable to the module to match the others.
Bug: 171029603
Test: m checkapi
Change-Id: I2bd1fa5bac6b35096b3059f93d68ef24b7a464e5
Merged-In: I2bd1fa5bac6b35096b3059f93d68ef24b7a464e5
(cherry picked from commit 3a1b1bd620454dd1d5b328c98634a567865cd55e)
Remove the dep on the monolithic current.txt so that it can be deleted.
Bug: 158465496
Test: m current-api-xml (same before and after)
Change-Id: I6d36801592a20cb9dc8f87c7d9d4babf0986c448
Add support for:
- reporting of incoming DTMF tones from IMS stack.
- incoming/outgoing RTP header extension data.
Test: Added unit tests where possible.
Test: Added test intents to inject test data into framework for platform
testing.
Bug: 163085177
Change-Id: If34faeba0461c677a1381c82ead4a79c607bcf13
Pipe these information for Dialer to determine HD+ icon
Bug: 169586285
Bug: 172304392
Test: build pass
Change-Id: If4149c3020230eff8da06a37a3cf4bf69c011a6d
Connectivity service module is using some AppOpsManager @hide
APIs but they are not able to call after CS become a
mainline module. Thus, expose them to System APIs.
Bug: 170593746
Test: make update-api
Change-Id: Idb8ee13394ccbd266061eef0cab08a5e28948a3e
1. Rename setDataEnabledWithReason to
setDataEnabledForReasn
2. Allow isDataConnectionAllowed to be accessed by
same apps as isDataEnabledForReason
3. Make these apis public
Bug: 156332911
Test: cts and build
Change-Id: I8672ab8861fdec1854427ee9ce5ad8eec8774608
Merged-In: I8672ab8861fdec1854427ee9ce5ad8eec8774608
Support api to control data by thermal service
Restructure data enablement API to have single API
with reason as an input to stop adding new apis
for new usecases.
Bug: 151342791
Test: added new CTS tests and verified
Change-Id: I763c422ba54907984977d19b2774c31337e5ffe5
Merged-In: I763c422ba54907984977d19b2774c31337e5ffe5
The modules that generated these api tracking files were removed in
the change Ib8ec547871045f77fb73aa82f192b5a7767d0c33.
Remove the now-stale files too.
Bug: 171029603
Test: presubmit
Change-Id: If6b849febcf0a89b6b67e7acd79b8bcd9985e6ca
Merged-In: If6b849febcf0a89b6b67e7acd79b8bcd9985e6ca
Test: cts builds
Test: the new cts tests run
Bug: 170981222
Reference: I39921ef80c62cc331bb2d72a8d614986d3166eb9
Change-Id: I82d9581c2892eff282de02ce5810cf819a35d1d4