

Otherwise, the other changes seem pretty minor, so keep checking back on our Android 13 page to stay up to date.Īnd stay tuned for Google I/O, which gets underway May 11. There's also signs of new audio abilities like spatial audio and Bluetooth LE. We're still digging into the beta on our Pixels, but it looks like Google has made it easier to control your smart home without unlocking your phone. For example, Google didn't talk much about the new Material You icons and the new Quick Settings API that helps you discover what apps have Quick Tile capabilities. That's not all that Android 13 Beta 1 has to offer, but we'll probably continue to find more things in the coming days. These errors help developers identify what's gone wrong and - more importantly - allow the apps to retry generating new keys. Cryptographic key generation fixesįor apps that use the KeyMint and Keystore systems - which generate and store cryptographic keys - Android 13 introduces a new error reporting system. This will make for seamless audio production, both user-facing and in the system itself. The API also allows Android to retrieve a list of devices it can use to play the audio. What does that mean? Basically, Android 13 will be able to tell apps what audio formats the OS can play and render on device. Now, Google has added a new anticipatory audio routing API into Beta 1, opening a lot of potential for musicians. In Android 13 Developer Preview 2, we got support for MIDI 2.0 peripheral devices. You will have ultimate choice over what apps can access your media files. Not any longer - Android 13 introduces three new granular permission types in the form of images, video, and audio.īasically, an app has to request access to each one of those categories separately. Before, when an app requested permission to access your media files, it got to see all of them stored on your phone.
