commit | 426cb73fb7647852bf7a5fcf9ec6d9b3d8e7fafe | [log] [tgz] |
---|---|---|
author | Pranav Madapurmath <pmadapurmath@google.com> | Wed Aug 30 17:18:40 2023 +0000 |
committer | Pranav Madapurmath <pmadapurmath@google.com> | Fri Sep 01 23:25:20 2023 +0000 |
tree | fc5af24a549f9ada89b5a938cddf4a4853ed0c03 | |
parent | baadc51c1eeecc9a4e388010908937bced01dfce [diff] |
Resolve call extension type in Jetpack ICS With supporting the new VOIP app actions being added, the Jetpack layer needs to be able to resolve the extension type for the call before initiating capability exchange. If the v2 APIs are being used (U/V) or the backwards compat library is being leveraged (on pre-U devices), we need to ensure that CAPABILITY_EXCHANGE is the resolved extension type. For apps that are using the v1.5 Connection Service (AUTO), we need to resolve the extension type as EXTRAS when the call extras contains EXTRA_VOIP_API_VERSION. If none of these conditions apply, the phone account will be checked to see if it supports transactional ops. If the caller does not have the required permissions, the extension type is resolved as UNKOWN (no capability exchange). If the phone account doesn't have the required capability, we can simply resolve the extension as not supporting capability exchange (NONE). Fixes: 297438037 Test: atest InCallServiceCompat (on pre-U, U, V devices) Change-Id: I55aa958e75c28029747a52cc5a8537761a0de430
Jetpack is a suite of libraries, tools, and guidance to help developers write high-quality apps easier. These components help you follow best practices, free you from writing boilerplate code, and simplify complex tasks, so you can focus on the code you care about.
Jetpack comprises the androidx.*
package libraries, unbundled from the platform APIs. This means that it offers backward compatibility and is updated more frequently than the Android platform, making sure you always have access to the latest and greatest versions of the Jetpack components.
Our official AARs and JARs binaries are distributed through Google Maven.
You can learn more about using it from Android Jetpack landing page.
For contributions via GitHub, see the GitHub Contribution Guide.
Note: The contributions workflow via GitHub is currently experimental - only contributions to the following projects are being accepted at this time:
When contributing to Jetpack, follow the code review etiquette.
We are not currently accepting new modules.
Head over to the onboarding docs to learn more about getting set up and the development workflow!
Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.
Before uploading your first contribution, you will need setup a password and agree to the contribution agreement:
Generate a HTTPS password: https://android-review.googlesource.com/new-password
Agree to the Google Contributor Licenses Agreement: https://android-review.googlesource.com/settings/new-agreement
AndroidX uses git to store all the binary Gradle dependencies. They are stored in prebuilts/androidx/internal
and prebuilts/androidx/external
directories in your checkout. All the dependencies in these directories are also available from google()
, or mavenCentral()
. We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.