\n
![](\"https:\/\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEjTbEtmcMRsVnZNjDLfHHmaHRbWrOxiuKlPvOEKOdTQv5zdrBXiwR2seAo7nH7WHr5OBn-40Cokd-O8A39uNI8YPwNPS0KyNKmR5KfMdKWylTB2urSRAtJKSybArxjCTCi5dJghCUPgA49ZVOn3_4TLqppzii0bc5PDKdbeHzGfG0DrNeAyjbt5VSoOVYI\/s1600\/image1.gif\")
<\/p>\n Posted by Today we’re releasing the second beta of Android 16, continuing our work to build a platform that enables creative expression. You can enroll any supported Pixel device<\/a> to get this and future Android Beta updates over-the-air.<\/p>\n This build adds new support for professional camera experiences, graphical effects, extends our performance framework, and continues the evolution of features related to privacy, security, and background tasks. We\u2019re looking forward to hearing what you think<\/a>, and thank you in advance for your continued help in making Android a platform that works for everyone.<\/p>\n Android 16 enhances support for professional camera users, allowing for hybrid auto exposure along with precise color temperature and tint adjustments. It’s easier than ever to capture motion photos with new Intent actions, and we’re continuing to improve UltraHDR images, with support for HEIC encoding and new parameters from the ISO 21496-1 draft standard.<\/p>\n Android 16 adds new hybrid auto-exposure modes to Camera2<\/a>, allowing you to manually control specific aspects of exposure while letting the auto-exposure (AE) algorithm handle the rest. You can control ISO + AE<\/a>, and exposure time + AE<\/a>, providing greater flexibility compared to the current approach where you either have full manual control or rely entirely on auto-exposure.<\/p>\n <\/p>\n Android 16 adds camera support for fine color temperature and tint adjustments to better support professional video recording applications. White balance settings are currently controlled through CONTROL_AWB_MODE<\/span><\/a>, which contains options limited to a preset list, such as Incandescent<\/a>, Cloudy<\/a>, and Twilight<\/a>. The COLOR_CORRECTION_MODE_CCT<\/a><\/span> enables the use of COLOR_CORRECTION_COLOR_TEMPERATURE<\/a><\/span> and COLOR_CORRECTION_COLOR_TINT<\/a><\/span> for precise adjustments of white balance based on the correlated color temperature.<\/p>\n <\/p>\n <\/image><\/p>\n Android 16 adds standard Intent actions \u2014 ACTION_MOTION_PHOTO_CAPTURE<\/a><\/span>, and ACTION_MOTION_PHOTO_CAPTURE_SECURE<\/a><\/span> \u2014 which request that the camera application capture a motion photo and return it.<\/p>\n <\/image><\/p>\n You must either pass an extra EXTRA_OUTPUT<\/a><\/span> to control where the image will be written, or a Uri<\/a><\/span> through Intent<\/a><\/span> setClipData<\/a><\/span>. If you don’t set a ClipData<\/a><\/span>, it will be copied there for you when calling Context.startActivity<\/a><\/span>.<\/p>\n <\/image><\/p>\n Android 16 continues our work to deliver dazzling image quality with UltraHDR<\/a> images. It adds support for UltraHDR images in the HEIC file format. These images will get ImageFormat<\/span> type HEIC_ULTRAHDR<\/a><\/span> and will contain an embedded gainmap similar to the existing UltraHDR JPEG format. We’re working on AVIF support for UltraHDR as well, so stay tuned.<\/p>\n In addition, Android 16 implements additional parameters in UltraHDR from the ISO 21496-1 draft standard<\/a>, including the ability to get and set the colorspace that gainmap math should be applied in, as well as support for HDR encoded base images with SDR gainmaps.<\/p>\n Android 16 adds RuntimeColorFilter<\/a><\/span> and RuntimeXfermode<\/a><\/span>, allowing you to author complex effects like Threshold, Sepia, and Hue Saturation and apply them to draw calls. Since Android 13, you’ve been able to use AGSL<\/a> to create custom RuntimeShaders<\/a><\/span> that extend Shaders<\/a><\/span>. The new API mirrors this, adding an AGSL-powered RuntimeColorFilter<\/a><\/span> that extends ColorFilters<\/a><\/span>, and a Xfermode<\/a><\/span> effect that allows you to implement AGSL-based custom compositing and blending between source and destination pixels.<\/p>\n <\/p>\n With every Android release, we seek to make the platform more efficient, privacy conscious, internationalization friendly, and robust, balancing the needs of apps against hardware support, system performance, user privacy, and battery life. This can result in behavior changes that impact compatibility.<\/p>\n Android 15 enforced edge-to-edge<\/a> for apps targeting Android 15 (SDK 35), but your app could opt-out by setting R.attr#windowOptOutEdgeToEdgeEnforcement<\/a><\/span> to true<\/span>. Once your app targets Android 16 (Baklava), R.attr#windowOptOutEdgeToEdgeEnforcement<\/span> is deprecated and disabled and your app cannot opt-out of going edge-to-edge. To be compatible with Android 16 Beta 2, ensure your app supports edge-to-edge and remove any use of R.attr#windowOptOutEdgeToEdgeEnforcement<\/span>. To support edge-to-edge, see the Compose<\/a> and Views<\/a> guidance. Please let us know about concerns in our tracker on the feedback page<\/a>.<\/p>\n For apps targeting Android 16 or higher, BODY_SENSORS<\/a><\/span> permissions are transitioning to the granular permissions under android.permissions.health<\/span> also used by Health Connect<\/a>. Any API previously requiring BODY_SENSORS<\/span> or BODY_SENSORS_BACKGROUND<\/span> will now require the corresponding android.permissions.health permission<\/span>. This affects the following data types, APIs, and foreground service types:<\/p>\n If your app uses these APIs, it should now request the respective granular permissions:<\/p>\n These permissions are the same as those that guard access to reading data from Health Connect, the Android datastore for health, fitness, and wellness data.<\/p>\n An abandoned job occurs when the JobParameters<\/a><\/span> object associated with the job has been garbage collected, but jobFinished<\/a><\/span> has not been called to signal job completion. This indicates that the job may be running and being rescheduled without the application’s awareness.<\/p>\n Applications in Android 16 that rely on JobScheduler<\/a><\/span> without maintaining a strong reference to the JobParameters<\/a><\/span> object will now be granted the new job stop reason STOP_REASON_TIMEOUT_ABANDONED<\/a><\/span> on timeout, instead of STOP_REASON_TIMEOUT<\/a><\/span>.<\/p>\n If there are frequent occurrences of the new abandoned stop reason, the system will take mitigation steps to reduce job frequency. Please use the new stop reason to detect and reduce abandoned jobs.<\/p>\n Note:<\/b> If you’re using WorkManager<\/a><\/span>, you’re not expected to be impacted by this change \u2014 one nice side effect of using Android Jetpack to schedule your work.<\/p><\/blockquote>\n Android 16 introduces default security hardening against Intent redirection attacks regardless of your app’s targetSDK version. The removeLaunchSecurityProtection<\/a><\/span> API allows you to opt-out of this protection if your testing reveals issues.<\/p>\n Note:<\/b> Opting out of security protections should be done with caution and only when absolutely necessary, as it can increase the risk of security vulnerabilities.<\/p><\/blockquote>\n <\/p>\n Apps targeting Android 15 (API level 35) have the elegantTextHeight<\/a><\/span> TextView<\/a><\/span> attribute set to true by default, replacing the compact font with one that is much more readable. You could override this by setting the elegantTextHeight<\/span> attribute to false.<\/p>\n Android 16 deprecates the elegantTextHeight<\/a><\/span> attribute, and the attribute will be ignored once your app targets Android 16. The \u201cUI fonts\u201d controlled by these APIs are being discontinued, so you should adapt any layouts to ensure consistent and future proof text rendering in Arabic, Lao, Myanmar, Tamil, Gujarati, Kannada, Malayalam, Odia, Telugu or Thai.<\/p>\n Android 15 introduced support for 16KB memory pages to optimize performance<\/a> of the platform. Android 16 adds a compatibility mode<\/a>, allowing some apps built for 4K memory pages to run on a device configured for 16KB memory pages.<\/p>\n If Android detects that your app has 4KB aligned memory pages, it will automatically use compatibility mode and display a notification dialog to the user. Setting the android:pageSizeCompat<\/span> property in the AndroidManifest.xml<\/span> to enable the backwards compatibility mode will prevent the display of the dialog when your app launches. For best performance, reliability, and stability, your app should still be 16KB aligned. Read our recent blog post about updating your apps to support 16KB memory pages<\/a> for more details.<\/p>\n <\/image><\/p>\n Users can now customize their measurement system in regional preferences within Settings. The user preference is included as part of the locale code, so you can register a BroadcastReceiver<\/a><\/span> on ACTION_LOCALE_CHANGED<\/a><\/span> to handle locale configuration changes when regional preferences change.<\/p>\n Using formatters<\/a> can help match the local experience. For example, “0.5 in” in English (United States), is “12,7 mm” for a user who has set their phone to English (Denmark) or who uses their phone in English (United States) with the metric system as the measurement system preference.<\/p>\n To find these settings in Android 16 Beta 2, open the Settings app and navigate to System > Languages & region.<\/p>\n In Android 16, the live wallpaper framework is gaining a new content API to address the challenges of dynamic, user-driven wallpapers. Currently, live wallpapers incorporating user-provided content require complex, service-specific implementations. Android 16 introduces WallpaperDescription<\/a><\/span> and WallpaperInstance<\/a><\/span>. WallpaperDescription<\/span> allows you to identify distinct instances of a live wallpaper from the same service. For example, a wallpaper that has instances on both the home screen and on the lock screen may have unique content in both places. The wallpaper picker and WallpaperManager<\/a><\/span> use this metadata to better present wallpapers to users, streamlining the process for you to create diverse and personalized live wallpaper experiences.<\/p>\n The SystemHealthManager<\/a><\/span> introduces the getCpuHeadroom<\/a><\/span> and getGpuHeadroom<\/span> APIs, designed to provide games and resource-intensive apps with estimates of available CPU and GPU resources. These methods offer a way for you to gauge how your app or game can best improve system health, particularly when used in conjunction with other Android Dynamic Performance Framework<\/a> (ADPF) APIs that detect thermal throttling<\/a>. By using CpuHeadroomParams<\/a><\/span> and GpuHeadroomParams<\/a><\/span> on supported devices, you will be able to customize the time window used to compute the headroom and select between average or minimum resource availability. This can help you reduce your CPU or GPU resource usage accordingly, leading to better user experiences and improved battery life.<\/p>\n Android 16 adds APIs that support sharing access to Android Keystore<\/a> keys with other apps. The new KeyStoreManager<\/a><\/span> class supports granting<\/a> and revoking<\/a> access to keys by app uid<\/a>, and includes an API for apps to access shared keys.<\/p>\n The new <\/a><\/div>\nMedia and camera updates<\/span><\/h2>\n
Hybrid auto-exposure<\/span><\/h3>\n
fun<\/span> setISOPriority<\/span>() {\n \/\/ ...<\/span>\n\n val<\/span> availablePriorityModes = mStaticInfo.characteristics.get<\/span>(\n CameraCharacteristics.CONTROL_AE_AVAILABLE_PRIORITY_MODES\n )\n \/\/ ...<\/span>\n \n \/\/ Turn on AE mode to set priority mode<\/span>\n reqBuilder[CaptureRequest.CONTROL_AE_MODE] = CameraMetadata.CONTROL_AE_MODE_ON\n reqBuilder[CaptureRequest.CONTROL_AE_PRIORITY_MODE] = CameraMetadata.CONTROL_AE_PRIORITY_MODE_SENSOR_SENSITIVITY_PRIORITY\n reqBuilder[CaptureRequest.SENSOR_SENSITIVITY] = TEST_SENSITIVITY_VALUE\n val<\/span> request: CaptureRequest = reqBuilder.build()\n\n \/\/ ...<\/span>\n\n}\n<\/pre>\n<\/div>\nPrecise color temperature and tint adjustments<\/span><\/h3>\n
fun<\/span> setCCT<\/span>() {\n \/\/ ... (Your existing code before this point) ...<\/span>\n\n val<\/span> colorTemperatureRange: Range<\/div>\nMotion photo capture intent actions<\/span><\/h3>\n
<\/div>\nUltraHDR image enhancements<\/span><\/h3>\n
<\/a><\/div>\nCustom graphical effects with AGSL<\/span><\/h2>\n
private<\/span> val<\/span> thresholdEffectString = \"\"\"<\/span>\n uniform half threshold;\n half4 main<\/span>(half4 c) {\n half luminosity = dot(c.rgb, half3(0.2126<\/span>, 0.7152<\/span>, 0.0722<\/span>));\n half bw = step(threshold, luminosity);\n return<\/span> bw.xxx1 * c.a;\n }\"\"\"<\/span>\n\nfun<\/span> setCustomColorFilter<\/span>(paint: Paint) {\n val<\/span> filter = RuntimeColorFilter(thresholdEffectString)\n filter.setFloatUniform(0.5<\/span>)\n paint.colorFilter = filter\n}\n<\/pre>\n<\/div>\nBehavior changes<\/span><\/h2>\n
Edge to edge opt-out going away<\/span><\/h3>\n
Health and fitness permissions<\/span><\/h3>\n
Abandoned empty jobs stop reason<\/span><\/h3>\n
Intent redirect changes<\/span><\/h3>\n
val<\/span> iSublevel = intent.getParcelableExtra(\"sub_intent\"<\/span>, Intent::class.java)\niSublevel?.let {\n it.removeLaunchSecurityProtection()\n startActivity(it)\n}\n<\/pre>\n<\/div>\nElegant font APIs deprecated and disabled<\/span><\/h3>\n
<\/div>\n<\/div>\n16 KB page size compatibility mode<\/span><\/h3>\n
<\/div>\nMeasurement system customization<\/span><\/h3>\n
Content handling for live wallpapers<\/span><\/h2>\n
Headroom APIs in ADPF<\/span><\/h2>\n
Key sharing API<\/span><\/h2>\n
Standardized picture and audio quality framework for TVs<\/span><\/h2>\n