Perubahan perilaku: Aplikasi yang menargetkan Android 16 atau yang lebih tinggi

Tetap teratur dengan koleksi Simpan dan kategorikan konten berdasarkan preferensi Anda.

Seperti rilis sebelumnya, Android 16 menyertakan perubahan perilaku yang dapat memengaruhi aplikasi Anda. Perubahan perilaku berikut ini berlaku khusus bagi aplikasi yang menargetkan Android 16 atau yang lebih tinggi. Jika aplikasi menargetkan Android 16 atau yang lebih tinggi, Anda harus memodifikasi aplikasi untuk mendukung perilaku ini, jika berlaku.

Pastikan Anda meninjau daftar perubahan perilaku yang memengaruhi semua aplikasi yang berjalan di Android 16, terlepas dari targetSdkVersion aplikasi Anda.

Pengalaman pengguna dan UI sistem

Android 16 (API level 36) menyertakan perubahan berikut yang dimaksudkan untuk menciptakan pengalaman pengguna yang lebih konsisten dan intuitif.

Opsi tidak ikut layar penuh akan dihapus

Android 15 menerapkan tampilan penuh untuk aplikasi yang menargetkan Android 15 (level API 35), tetapi aplikasi Anda dapat memilih tidak ikut dengan menetapkan R.attr#windowOptOutEdgeToEdgeEnforcement ke true. Untuk aplikasi yang menargetkan Android 16 (API level 36), R.attr#windowOptOutEdgeToEdgeEnforcement tidak digunakan lagi dan dinonaktifkan, dan aplikasi Anda tidak dapat memilih untuk tidak menggunakan layar penuh.

• Jika aplikasi Anda menargetkan Android 16 (API level 36) dan berjalan di perangkat Android 15, R.attr#windowOptOutEdgeToEdgeEnforcement akan terus berfungsi.
• Jika aplikasi Anda menargetkan Android 16 (API level 36) dan berjalan di perangkat Android 16, R.attr#windowOptOutEdgeToEdgeEnforcement akan dinonaktifkan.

Untuk pengujian di Android 16 Beta 3, pastikan aplikasi Anda mendukung layar penuh dan hapus penggunaan R.attr#windowOptOutEdgeToEdgeEnforcement sehingga aplikasi Anda juga mendukung layar penuh di perangkat Android 15. Untuk mendukung tampilan dari tepi ke tepi, lihat panduan Compose dan View.

Migrasi atau pilihan tidak ikut diperlukan untuk kembali prediktif

For apps targeting Android 16 (API level 36) or higher and running on an Android 16 or higher device, the predictive back system animations (back-to-home, cross-task, and cross-activity) are enabled by default. Additionally, onBackPressed is not called and KeyEvent.KEYCODE_BACK is not dispatched anymore.

If your app intercepts the back event and you haven't migrated to predictive back yet, update your app to use supported back navigation APIs. or temporarily opt out by setting the android:enableOnBackInvokedCallback attribute to false in the <application> or <activity> tag of your app's AndroidManifest.xml file.

API font elegan tidak digunakan lagi dan dinonaktifkan

Apps targeting Android 15 (API level 35) have the elegantTextHeight TextView 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 attribute to false.

Android 16 deprecates the elegantTextHeight attribute, and the attribute will be ignored once your app targets Android 16. The "UI fonts" 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.

Fungsi inti

Android 16 (API level 36) menyertakan perubahan berikut yang mengubah atau memperluas berbagai kemampuan inti sistem Android.

Pengoptimalan penjadwalan pekerjaan dengan tarif tetap

Prior to targeting Android 16, when scheduleAtFixedRate missed a task execution due to being outside a valid process lifecycle, all missed executions immediately execute when the app returns to a valid lifecycle.

When targeting Android 16, at most one missed execution of scheduleAtFixedRate is immediately executed when the app returns to a valid lifecycle. This behavior change is expected to improve app performance. Test this behavior in your app to check if your app is impacted. You can also test by using the app compatibility framework and enabling the STPE_SKIP_MULTIPLE_MISSED_PERIODIC_TASKS compat flag.

Faktor bentuk perangkat

Android 16 (API level 36) menyertakan perubahan berikut untuk aplikasi saat ditampilkan di perangkat layar besar.

Tata letak adaptif

With Android apps now running on a variety of devices (such as phones, tablets, foldables, desktops, cars, and TVs) and windowing modes on large screens (such as split screen and desktop windowing), developers should build Android apps that adapt to any screen and window size, regardless of device orientation. Paradigms like restricting orientation and resizability are too restrictive in today's multidevice world.

Ignore orientation, resizability, and aspect ratio restrictions

For apps targeting Android 16 (API level 36), Android 16 includes changes to how the system manages orientation, resizability, and aspect ratio restrictions. On displays with smallest width >= 600dp, the restrictions no longer apply. Apps also fill the entire display window, regardless of aspect ratio or a user's preferred orientation, and pillarboxing isn't used.

This change introduces a new standard platform behavior. Android is moving toward a model where apps are expected to adapt to various orientations, display sizes, and aspect ratios. Restrictions like fixed orientation or limited resizability hinder app adaptability, so we recommend making your app adaptive to deliver the best possible user experience.

You can also test this behavior by using the app compatibility framework and enabling the UNIVERSAL_RESIZABLE_BY_DEFAULT compat flag.

Common breaking changes

Ignoring orientation, resizability, and aspect ratio restrictions might impact your app's UI on some devices, especially elements that were designed for small layouts locked in portrait orientation: for example, issues like stretched layouts and off-screen animations and components. Any assumptions about aspect ratio or orientation can cause visual issues with your app. Learn more about how to avoid them and improve your app's adaptive behaviour.

Allowing device rotation results in more activity re-creation, which can result in losing user state if not properly preserved. Learn how to correctly save UI state in Save UI states.

Implementation details

The following manifest attributes and runtime APIs are ignored across large screen devices in full-screen and multi-window modes:

• screenOrientation
• resizableActivity
• minAspectRatio
• maxAspectRatio
• setRequestedOrientation()
• getRequestedOrientation()

The following values for screenOrientation, setRequestedOrientation(), and getRequestedOrientation() are ignored:

• portrait
• reversePortrait
• sensorPortrait
• userPortrait
• landscape
• reverseLandscape
• sensorLandscape
• userLandscape

Regarding display resizability, android:resizeableActivity="false", android:minAspectRatio, and android:maxAspectRatio have no effect.

For apps targeting Android 16 (API level 36), app orientation, resizability, and aspect ratio constraints are ignored on large screens by default, but every app that isn't fully ready can temporarily override this behavior by opting out (which results in the previous behavior of being placed in compatibility mode).

Exceptions

The Android 16 orientation, resizability, and aspect ratio restrictions don't apply in the following situations:

• Games (based on the android:appCategory flag)
• Users explicitly opting in to the app's default behavior in aspect ratio settings of the device
• Screens that are smaller than sw600dp

Opt out temporarily

To opt out a specific activity, declare the PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY manifest property:

<activity ...>
  <property android:name="android.window.PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY" android:value="true" />
  ...
</activity>

If too many parts of your app aren't ready for Android 16, you can opt out completely by applying the same property at the application level:

<application ...>
  <property android:name="android.window.PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY" android:value="true" />
</application>

Kesehatan dan kebugaran

Android 16 (API level 36) menyertakan perubahan berikut yang terkait dengan data kesehatan dan kebugaran.

Izin kesehatan dan kebugaran

Untuk aplikasi yang menargetkan Android 16 (API level 36) atau yang lebih tinggi, izin BODY_SENSORS akan bertransisi ke izin terperinci di bagian android.permissions.health yang juga digunakan oleh Health Connect. Setiap API yang sebelumnya memerlukan BODY_SENSORS atau BODY_SENSORS_BACKGROUND kini memerlukan izin android.permissions.health yang sesuai. Hal ini memengaruhi jenis data, API, dan jenis layanan latar depan berikut:

• HEART_RATE_BPM dari Fitur Kesehatan Wear
• Sensor.TYPE_HEART_RATE dari Android Sensor Manager
• heartRateAccuracy dan heartRateBpm dari Wear ProtoLayout
• FOREGROUND_SERVICE_TYPE_HEALTH jika izin android.permission.health masing-masing diperlukan sebagai pengganti BODY_SENSORS

Jika aplikasi Anda menggunakan API ini, aplikasi tersebut kini harus meminta izin terperinci masing-masing:

• Untuk pemantauan Detak Jantung, SpO2, atau Suhu Kulit saat digunakan: minta izin terperinci di bagian android.permissions.health, seperti READ_HEART_RATE, bukan BODY_SENSORS.
• Untuk akses sensor latar belakang: minta READ_HEALTH_DATA_IN_BACKGROUND, bukan BODY_SENSORS_BACKGROUND.

Izin ini sama dengan izin yang menjaga akses untuk membaca data dari Health Connect, datastore Android untuk data kesehatan, kebugaran, dan kesehatan.

Aplikasi seluler

Aplikasi seluler yang bermigrasi untuk menggunakan READ_HEART_RATE dan izin terperinci lainnya juga harus mendeklarasikan aktivitas untuk menampilkan kebijakan privasi aplikasi. Persyaratan ini sama dengan Health Connect.

Konektivitas

Android 16 (level API 36) menyertakan perubahan berikut dalam stack Bluetooth untuk meningkatkan konektivitas dengan perangkat periferal.

Intent baru untuk menangani perubahan enkripsi dan hilangnya obligasi

Sebagai bagian dari Peningkatan penanganan kehilangan ikatan, Android 16 juga memperkenalkan 2 intent baru untuk memberi aplikasi kesadaran yang lebih besar tentang kehilangan ikatan dan perubahan enkripsi.

Aplikasi yang menargetkan Android 16 kini dapat:

• Menerima intent ACTION_KEY_MISSING saat hilangnya ikatan jarak jauh terdeteksi, sehingga memungkinkannya memberikan masukan pengguna yang lebih informatif dan mengambil tindakan yang sesuai.
• Menerima intent ACTION_ENCRYPTION_CHANGE setiap kali status enkripsi link berubah. Hal ini mencakup perubahan status enkripsi, perubahan algoritma enkripsi, dan perubahan ukuran kunci enkripsi. Aplikasi harus mempertimbangkan pengikatan yang dipulihkan jika link berhasil dienkripsi setelah menerima intent ACTION_ENCRYPTION_CHANGE nanti.

Jika aplikasi Anda saat ini menggunakan mekanisme kustom untuk penanganan kehilangan ikatan, bermigrasilah ke intent baru ACTION_KEY_MISSING untuk mendeteksi dan mengelola peristiwa kehilangan ikatan. Sebaiknya aplikasi Anda memandu pengguna untuk mengonfirmasi bahwa perangkat jarak jauh berada dalam jangkauan sebelum memulai penghapusan perangkat dan penyambungan ulang.

Selain itu, jika perangkat terputus setelah intent ACTION_KEY_MISSING diterima, aplikasi Anda harus berhati-hati saat terhubung kembali ke perangkat karena perangkat tersebut mungkin tidak lagi terikat dengan sistem.

Keamanan

Android 16 (API level 36) menyertakan perubahan keamanan berikut.

Penguncian versi MediaStore

Untuk aplikasi yang menargetkan Android 16 atau yang lebih tinggi, MediaStore#getVersion() kini akan unik untuk setiap aplikasi. Hal ini menghilangkan properti identifikasi dari string versi untuk mencegah penyalahgunaan dan penggunaan untuk teknik sidik jari. Aplikasi tidak boleh membuat asumsi apa pun terkait format versi ini. Aplikasi seharusnya sudah menangani perubahan versi saat menggunakan API ini dan dalam sebagian besar kasus tidak perlu mengubah perilakunya saat ini, kecuali jika developer telah mencoba menyimpulkan informasi tambahan yang berada di luar cakupan API ini yang dimaksudkan.

Privasi

Android 16 (API level 36) menyertakan perubahan privasi berikut.

Izin Jaringan Lokal

Devices on the LAN can be accessed by any app that has the INTERNET permission. This makes it easy for apps to connect to local devices but it also has privacy implications such as forming a fingerprint of the user, and being a proxy for location.

The Local Network Protections project aims to protect the user's privacy by gating access to the local network behind a new runtime permission.

Release plan

This change will be deployed between two releases, 25Q2 and TBD respectively. It is imperative that developers follow this guidance for 25Q2 and share feedback because these protections will be enforced at a later Android release. Moreover, they will need to update scenarios which depend on implicit local network access by using the following guidance and prepare for user rejection and revocation of the new permission.

Impact

At the current stage, LNP is an opt-in feature which means only the apps that opt in will be affected. The goal of the opt-in phase is for app developers to understand which parts of their app depend on implicit local network access such that they can prepare to permission guard them for the next release.

Apps will be affected if they access the user's local network using:

• Direct or library use of raw sockets on local network addresses (e.g. mDNS or SSDP service discovery protocol)
• Use of framework level classes that access the local network (e.g. NsdManager)

Traffic to and from a local network address requires local network access permission. The following table lists some common cases:

These restrictions are implemented deep in the networking stack, and thus they apply to all networking APIs. This includes sockets created in native or managed code, networking libraries like Cronet and OkHttp, and any APIs implemented on top of those. Trying to resolve services on the local network (i.e. those with a .local suffix) will require local network permission.

Exceptions to the rules above:

• If a device's DNS server is on a local network, traffic to or from it (at port 53) doesn't require local network access permission.
• Applications using Output Switcher as their in-app picker won't need local network permissions (more guidance to come in 2025Q4).

Developer Guidance (Opt-in)

To opt into local network restrictions, do the following:

1. Flash the device to a build with 25Q2 Beta 3 or later.
2. Install the app to be tested.

3. Toggle the Appcompat flag in adb:

   adb shell am compat enable RESTRICT_LOCAL_NETWORK <package_name>
   

4. Reboot The device

Now your app's access to the local network is restricted and any attempt to access the local network will lead to socket errors. If you are using APIs that perform local network operations outside of your app process (ex: NsdManager), they won't be impacted during the opt-in phase.

To restore access, you must grant your app permission to NEARBY_WIFI_DEVICES.

1. Ensure the app declares the NEARBY_WIFI_DEVICES permission in its manifest.
2. Go to Settings > Apps > [Application Name] > Permissions > Nearby devices > Allow.

Now your app's access to the local network should be restored and all your scenarios should work as they did prior to opting the app in.

Once enforcement for local network protection begins, here is how the app network traffic will be impacted.

Use the following command to toggle-off the App-Compat flag

adb shell am compat disable RESTRICT_LOCAL_NETWORK <package_name>

Errors

Errors arising from these restrictions will be returned to the calling socket whenever it invokes send or a send variant to a local network address.

Example errors:

sendto failed: EPERM (Operation not permitted)

sendto failed: ECONNABORTED (Operation not permitted)

Local Network Definition

A local network in this project refers to an IP network that utilizes a broadcast-capable network interface, such as Wi-Fi or Ethernet, but excludes cellular (WWAN) or VPN connections.

The following are considered local networks:

IPv4:

• 169.254.0.0/16 // Link Local
• 100.64.0.0/10 // CGNAT
• 10.0.0.0/8 // RFC1918
• 172.16.0.0/12 // RFC1918
• 192.168.0.0/16 // RFC1918

IPv6:

• Link-local
• Directly-connected routes
• Stub networks like Thread
• Multiple-subnets (TBD)

Additionally, both multicast addresses (224.0.0.0/4, ff00::/8) and the IPv4 broadcast address (255.255.255.255) are classified as local network addresses.