Mobile Development

Android 17 QPR 3 Beta 4 Released: Fixes for system_server Memory Leak, Conscrypt TLS Error and Bluetooth Battery Drain

Google released Android 17 QPR 3 Beta 4 on 12 November 2026 with stability and battery fixes. App development teams are advised to test their apps.

By Oemah Solution Editorial 3 min read

This article was prepared with AI assistance from the official sources listed below, and checked automatically before publication.

Google, through Android Developers, released Beta 4 of Android 17 QPR 3 on 12 November 2026. This release brings a number of fixes related to system stability and battery consumption. According to Google, QPR betas contain no API changes that affect apps, but images are still provided so that developers can test their apps.

Beta 4 Release Details

Based on the Android Developers release notes, here are the technical details of Beta 4:

  • Release date: 12 November 2026
  • Build: DP11.261030.003
  • Security patch level: 2026-10-05
  • Google Play services: 26.41.31
  • Emulator support: x86 (64-bit) and ARM (v8-A)

This beta follows three earlier betas: Beta 1 on 2 October, Beta 2 on 20 October and Beta 3 on 29 October 2026. QPR (Quarterly Platform Release) updates are delivered to AOSP and Pixel devices through Feature Drops on a quarterly cadence.

Highlighted Fixes

Several issues fixed in Beta 4:

  • A memory leak in system_server that caused a very slow UI, Pixel Launcher crashes and unexpected device restarts.
  • Conscrypt threw an unclear IllegalArgumentException message when TLSv1 or TLSv1.1 connections were rejected in apps targeting API level 36.
  • Excessive Bluetooth background activity that drained the battery.
  • The on-screen keyboard being cut off.

Why It Matters for Organisations in Indonesia

Even though there are no API changes that affect apps, a release like this is still relevant for organisations that operate Android apps, such as banking apps, e-government services or field-officer apps. System-level issues such as memory leaks or Bluetooth behaviour can affect the user experience without any fault in the app's own code. Early regression testing helps teams identify behavioural differences before the QPR update reaches users' Pixel devices.

The note about Conscrypt deserves particular attention. Apps that still connect to legacy back-ends using TLS 1.0 or 1.1 will fail when targeting API 36. The fix in Beta 4 only concerns the clarity of the error message, but those connections are still rejected. For that reason, legacy systems should be upgraded to TLS 1.2 or later.

Practical Steps

  • Download the Beta 4 image or use the x86/ARM emulator to run regression tests on the app's main flows.
  • Review the inventory of back-end services and make sure none depend on TLS 1.0 or 1.1.
  • Monitor UI performance, stability and battery consumption, especially for features that use Bluetooth.
  • Test the on-screen keyboard display on important input forms.
  • Report findings to Google if you find platform-related issues.

With a quarterly release cadence, testing against QPR betas should be a routine part of the app quality cycle, not a one-off task shortly before release.

#android#android-17#mobile-development#tls#regression-testing

Sources & references

This article is a summary and interpretation by the Oemah Solution team of the sources below. Refer to the original sources for full details and context.

  1. Release notes  |  Android Developers Android Developers · developer.android.com