Android Q Beta 2 gives programs more control over sound capture via a fresh MicrophoneDirection API. You can use the API to define a preferred direction of the microphone when taking an audio recording. For example, when the user is shooting a”selfie” video, you can request the front-facing mic for sound recording (in case it is ) by calling setMicrophoneDirection(MIC_DIRECTION_FRONT).
On the platform side, we have made a variety of improvements in onResume and onPause to encourage multi-resume and inform your program when it’s focus. We have also changed the way the resizeableActivity manifest attribute functions, so you can manage the way your app is displayed on foldable and large screens. You may read more in the programmer guide.
We’re only getting started with bubbles, but please give them a try and let’s know what you think. It’s possible to discover a sample execution here.
Foldables emulator
To build using Android Q, download the Android Q Beta SDK and programs into Android Studio 3.3 or higher, and follow these instructions to configure your own surroundings. If you’d like the newest fixes for Android Q associated changes, we advise that you use Android Studio 3.5 or higher.
We are still in Beta using edges are so expected by Android Q! Before you set up, have a look at the Known Problems . As developers get their program updates prepared Specifically, expect the transitional issues with apps that we see during Betas. As an example, you might observe issues with apps that get photographs, videos, networking, or other documents stored on your device, such as when sharing or browsing in social media apps.
We’re releasing an SDK for programmers along with Android Q Beta 2. It includes the latest bug fixes, optimizations, and API upgrades for Android Q, together with the April 2019 security patches. You’ll also notice remote storage becoming more prominent as we look for your broader testing and comments to help us refine that feature.
Update your program’s targetSdkVersion to’Q’ as soon as you can. This permits you to test your app with all of the privacy and security features in Android Q, in addition to some other behaviour changes for programs targeting Q.
When you’re ready, dive into Android Q and learn about the brand new features and APIs it is possible to use in your programs. Here’s a movie highlighting lots of the modifications for developers in Beta 1 and Beta 2. Take a look at the API diff report for an overview of what’s changed in Beta 2, and watch that the Android Q Beta API benchmark for details. Visit the Android Q Beta programmer site for more funds, including release notes and how to report problems .
In each configuration, the emulator provides you controls to trigger actions that are quick, change orientation, and fold/unfold.
To prepare a runtime environment on your program, you can now configure a foldable emulator as a digital device (AVD) from Android Studio. The foldable AVD is a reference apparatus that lets you test with hardware configurations, behaviours, and states, as will be employed by our device maker partners. Models and the AVD meets CTS/GTS requirements CDD compliance to ensure compatibility. It supports runtime configuration change, multi-resume as well as the newest resizeableActivity behaviors.
What is new in Beta 2?
Improved sharesheet
As the ecosystem moves quickly toward apparatus that are foldable , fresh use-cases are opening to take advantage of those new screens. With Beta 2, you can build for handheld devices through Android Q improved platform support, combined with a new handheld apparatus emulator, available as an Android Virtual apparatus in Android Studio 3.5 available from the canary release station.
The application of early, open previews of android is driven by our philosophy of openness, and collaboration with our community. Your comments since Beta 1 proves the openness’ value – it’s been clear loud, and exceptionally valuable. You have sent us thousands of bug reports, giving us insights and directional feedback, changing our plans in a way that make the platform better for consumers and programmers. We are taking your feedback so please stay tuned. We are lucky to have such a fervent community helping to guide Android Q toward the product.
We’ve built bubbles in addition to Android’s telling system to provide a familiar and easy to use API for developers. To ship a bubble by means of a telling you need to add a BubbleMetadata by calling setBubbleMetadata. Within the metadata you can offer the Task to exhibit as content inside the bubble, along with an icon (handicapped in beta 2) and associated person.
In Android Q we are continuing our long-term effort to move programs toward just using public APIs. We introduced the majority of the restrictions in Beta 1, and we are making a few minor updates to all those lists in Beta 2 to minimize impact on programs. Our goal is to provide public choice APIs for valid use-cases before restricting access, so if an interface which you use in Android 9 Pie is now limited, you should ask for a new public API for that port .
Get started with Android Q Beta
We recommend getting started with Scoped Storage soon — the developer guide has details on how to take care of key use-cases. For testing, be sure that you enable Scoped Storage to your app using the adb command. If you discover that your app has a use-case that’s not supported by Scoped Storage, please let us know by using this short survey. As we move forward with the development of this attribute, we love the excellent feedback you have given us , it is a big help.
Bubbles will let users multitask because they move between activities.
As always, your input is crucial, therefore please let’s know what you believe . You can use our hotlists for submitting platform problems (like privacy and behavior adjustments ), program compatibility issues, and third party SDK problems . You’ve shared opinions with us so far and we are working to incorporate as much of it as possible within the next Beta release.
For attributes such as Scoped Storage, we’re sharing our plans as early as possible to provide you with more time to check and give us your input. To create broader opinions, we enabled Scoped Storage for app installs that were new so you can easily see what is affected.
After the first Sharing Shortcuts APIs in Beta 1, Now You Can offer a preview of the content being shared by supplying an EXTRA_TITLE additional from the Intent for your name, or by placing the Intent’s ClipData for a thumbnail picture. See the updated sample application for the implementation details.
First, make your program compatible and give your customers a seamless transition into Android Q, including your customers. The program should operate and look great, and manage the Android Q behaviour changes for many programs properly. If you find issues, we recommend without changing your level fixing them in the current program. See the migration guide for steps and a timeline that is recommended.
A few weeks ago we Introduced Android Q Beta, a first glance at the next version of Android. Together with new privacy features for users, Android Q adds new capabilities for programmers – such as enhancements for foldables, new APIs for connectivity, fresh media codecs and camera capabilities, NNAPI extensions, Vulkan 1.1 images, and much more.
With important privacy features which are likely to affect your programs, we recommend getting started with testing straight away. See the privacy checklist as a beginning point.
Today’s update includes Beta two system graphics for all of Pixel devices as well as the Android Emulator, as well upgraded SDK and tools for developers. These give you whatever that you need to begin analyzing your apps and assemble with the APIs.
With Scoped Storage, programs can use their private sandbox without permission, but they need new permissions to access shared collections for photos, videos and audio. Programs using files in shared groups — for pickers and instance, video and photo galleries, media browsing, and record storage — can behave differently under Scoped Storage.
As we discussed at Beta 1, we’re making substantial privacy investments in Android Q as well as the work we have done in prior releases. Our goals are improving giving users more control, and securing private data across apps and platform. We know that to achieve those goals, we will need to partner with you, our app developers. We realize that encouraging such attributes is an investment for you too, so we’ll do whatever we can to minimize the influence.
Programs have built similar connections from the ground up, and we are excited to deliver the best from those while helping reduce development time, protect user privacy, make interactions constant, and drive innovation.
Bubbles assist users do it inside another app and prioritize information, while keeping their context. They let users carry an app’s performance around together as they transfer between activities in their apparatus.
Bubbles: a fresh Approach to multitask
Bubbles are fantastic because they allow users maintain conversations that are important within easy reach, for messaging. They offer a perspective over tasks and upgrades, like telephone calls or arrival times. They can offer quick access to UI and can be reminders of tasks.
It’s easy – it is possible to register here to acquire Android Q Beta updates over-the-air, on almost any Pixel device (and this season we’re supporting all three generations of Pixel — Pixel 3, Pixel 2, as well as the original Pixel!) . You’ll receive the upgrade shortly if you’re already enrolled, no action is necessary on your part. Downloadable system images are also available. You can use the Android Emulator — just download the emulator system images via the SDK Manager in Android Studio if you don’t have a Pixel apparatus.