Published: -/Updated: -/3 minute/

Android 17 Notes

Summary

Android 17 introduces significant changes, including security enhancements, large screen adaptation, and performance improvements. Key features include blocking HTTP vulnerabilities, forced adaptive screens, and strict audio playback controls.

On February 13, 2026, Google officially released Android 17 Beta1 (API level 37).

If you are still immersed in the adaptation of Android 16, the rhythm of Android 17 may surprise you. This version not only marks a major change in the release process (from "Developer Preview" to "Canary Channel"), but also establishes the two core logics of Android's future: Secure-by-default and Adaptive-by-default


Core Summary

The "four major changes" that developers must pay attention to

Android 17 is no longer just a minor patch

  • Security defense tightening: fully block the vulnerabilities of text transmission (HTTP) and local loop (Localhost)

  • Large screen forced adaptive: On foldable screens and tablets, developers will no longer be able to "force vertical screens" through code

  • Multi-device collaboration enhancement: Introduce Handoff API to seamlessly continue tasks across devices

  • Audio control hardening: background audio playback will be subject to a strict lifecycle review

Security

The End of Cleartext Traffic

In Android 17, the usesCleartextTraffic property is on its way to being deprecated. If your app still relies on HTTP instead of HTTPS, you must migrate to Network Security Config and explicitly define the allowed domains.

Warning: If your minSdk is < 24, you must keep both the attribute and the configuration file. This marks Android's full shift to the philosophy of "default encryption."

Localhost needs Permission

This is a huge change. In the past, many apps liked to set up a local bridge at 127.0.0.1 for inter-process communication, but now you must declare the USE_LOOPBACK_INTERFACE permission. Security is more important than convenience, and this silent communication bridge will be cut off.

URI Authorization restrictions

In order to prevent future risks, Android 17 restricts implicit URI authorization. When sending ACTION_SEND or calling the camera, you can no longer rely on the system to automatically authorize, but must explicitly grant permissions, otherwise the application will completely crash in the Android 18 era.


Large screen adaptation

If you are still using screenOrientation="portrait" to avoid large screen adaptation, then Android 17 will make you unable to hide

On devices with a screen width of sw≥600dp:

  • Ignore the orientation attribute: the system will ignore the vertical or horizontal orientation requirements that you force.

  • Forced adjustable size: even if you set resizableActivity="false", the system will still force scaling


Performance and Media

Backstage Audio

Android 17 enforces constraints on the audio framework. If your app calls audio playback, gaining focus, or adjusting volume without a valid lifecycle state, these calls will be silently ignored. This solves the embarrassment of apps accidentally "vocalization" in the background for many years.

Evolution of ART virtual machine

Android 17 introduces Generational GC, which significantly reduces the CPU overhead of garbage collection and effectively reduces the phenomenon of frame loss during application operation

Dynamic Camera Session

The new "Dynamic Camera Session" function has been added. When switching between photo and video modes, you will no longer feel the black screen and lag, achieving a truly seamless switch

End