Android

Android 15 Beta 3: New features, changes and bug fixes

Published

on

As scheduled, Android 15 reached Platform Stability with the release of Beta 3. Google recently rolled out the third Beta of Android 15 to Pixel phones. It’s a pretty exciting development, bringing us one step closer to the Stable release slated later this year.

With the Android 15 Beta 3, Google made some notable changes in the experience and functionalities. The new version is available for Pixel 6 and later devices. Android 15 Beta 4 might be released next month, followed by a Stable release expected by October.

What’s new in Android 15 Beta 3?

The third Beta update of Android 15 introduces a redesigned wallpaper editor, adaptive timeout, a more prominent Circle to Search off switch, Android Safe Browsing, the ability to show long app names, and a modernized Android 15 system icon.

Additional user-facing changes include: the volume menu can no longer be minimized, ‘Speakers and displays’ label removed, Device & app notifications turned Notification read, reply & control, a shortcut to Color contrast preferences in Settings > Display, and Home Controls screensaver for Pixel Tablet.

Resolved issues

Resolved developer-reported issues

  • Fixed an issue where disabling polling using the setDiscoveryTechnology method didn’t disable polling.
  • Fixed an issue that prevented the system sharesheet from loading in some cases.
  • Fixed an issue that caused the system Settings app to crash when accessing screen saver options.
  • Fixed an issue that sometimes caused the screen unlock icon to be displayed when notifications were on screen.
  • Fixed an issue that prevented mobile network security settings from being changed.

Other resolved issues

  • Fixed an issue with the Android Emulator that caused Simpleperf to crash when running a CPU profile.

Bluetooth resolved issues

  • Resolved an issue where Bluetooth LE scans could persist in the system after an app crash.
  • Fixed a bug in Bluetooth LE legacy advertising, where AdvertisingSet.setScanResponseData did not return ADVERTISE_FAILED_DATA_TOO_LARGE when scan response data exceeded the 31-byte limit.
  • Fixed a bug that caused LE connection failures on the GATT server by passing the address type from BluetoothGattServer.connect to native.

Leave a Reply

Your email address will not be published. Required fields are marked *

Trending

Exit mobile version