Platform Android 16 menyertakan perubahan perilaku yang dapat memengaruhi aplikasi Anda.
Perubahan perilaku berikut berlaku untuk semua aplikasi saat dijalankan di Android 16,
terlepas dari targetSdkVersion
. Sebaiknya uji aplikasi Anda, lalu ubah
sesuai kebutuhan untuk mendukung perubahan ini, jika memungkinkan.
Selain itu, pastikan Anda meninjau daftar perubahan perilaku yang hanya memengaruhi aplikasi yang menargetkan Android 16.
Fungsi inti
Android 16 (API level 36) menyertakan perubahan berikut yang mengubah atau memperluas berbagai kemampuan inti sistem Android.
Pengoptimalan kuota JobScheduler
Mulai Android 16, kami menyesuaikan kuota runtime eksekusi tugas reguler dan dipercepat berdasarkan faktor berikut:
- Bucket standby aplikasi yang digunakan aplikasi: di Android 16, bucket standby aktif akan mulai diterapkan oleh kuota runtime yang besar.
- Jika tugas memulai eksekusi saat aplikasi dalam status teratas: di Android 16, Tugas yang dimulai saat aplikasi terlihat oleh pengguna dan berlanjut setelah aplikasi menjadi tidak terlihat, akan mematuhi kuota runtime tugas.
- Jika tugas dieksekusi saat menjalankan Layanan Latar Depan: di Android 16, tugas yang dieksekusi secara serentak dengan layanan latar depan akan mematuhi kuota runtime tugas. Jika Anda memanfaatkan tugas untuk transfer data yang dimulai pengguna, sebaiknya gunakan tugas transfer data yang dimulai pengguna.
Perubahan ini memengaruhi tugas yang dijadwalkan menggunakan WorkManager, JobScheduler, dan
DownloadManager. Untuk men-debug alasan tugas dihentikan, sebaiknya catat alasan
tugas Anda dihentikan dengan memanggil WorkInfo.getStopReason()
(untuk
tugas JobScheduler, panggil JobParameters.getStopReason()
).
Untuk mengetahui informasi tentang pengaruh status aplikasi terhadap resource yang dapat digunakan, lihat Batas resource pengelolaan daya. Untuk informasi selengkapnya tentang praktik terbaik yang optimal untuk baterai, lihat panduan tentang mengoptimalkan penggunaan baterai untuk API penjadwalan tugas.
Sebaiknya manfaatkan juga
JobScheduler#getPendingJobReasonsHistory
API baru yang diperkenalkan di
Android 16 untuk memahami alasan tugas belum dieksekusi.
Pengujian
Untuk menguji perilaku aplikasi, Anda dapat mengaktifkan penggantian pengoptimalan kuota tugas tertentu selama aplikasi berjalan di perangkat Android 16.
Untuk menonaktifkan penerapan "status teratas akan mematuhi kuota runtime tugas", jalankan perintah adb
berikut:
adb shell am compat enable OVERRIDE_QUOTA_ENFORCEMENT_TO_TOP_STARTED_JOBS APP_PACKAGE_NAME
Untuk menonaktifkan penerapan "tugas yang dieksekusi secara serentak dengan
layanan latar depan akan mematuhi kuota runtime tugas", jalankan perintah
adb
berikut:
adb shell am compat enable OVERRIDE_QUOTA_ENFORCEMENT_TO_FGS_JOBS APP_PACKAGE_NAME
Untuk menguji perilaku bucket standby aplikasi tertentu, Anda dapat menetapkan bucket standby aplikasi
aplikasi menggunakan perintah adb
berikut:
adb shell am set-standby-bucket APP_PACKAGE_NAME active|working_set|frequent|rare|restricted
Untuk memahami bucket standby aplikasi yang berisi aplikasi Anda, Anda bisa mendapatkan bucket
standby aplikasi menggunakan perintah adb
berikut:
adb shell am get-standby-bucket APP_PACKAGE_NAME
Alasan penghentian tugas kosong yang ditinggalkan
An abandoned job occurs when the JobParameters
object associated with the job
has been garbage collected, but JobService#jobFinished(JobParameters,
boolean)
has not been called to signal job completion. This indicates that
the job may be running and being rescheduled without the app's awareness.
Apps that rely on JobScheduler, don't maintain a strong reference to the
JobParameters
object, and timeout will now be granted the new job stop reason
STOP_REASON_TIMEOUT_ABANDONED
, instead of STOP_REASON_TIMEOUT
.
If there are frequent occurrences of the new abandoned stop reason, the system will take mitigation steps to reduce job frequency.
Apps should use the new stop reason to detect and reduce abandoned jobs.
If you're using WorkManager, AsyncTask, or DownloadManager, you aren't impacted because these APIs manage the job lifecycle on your app's behalf.
Tidak lagi menggunakan JobInfo#setImportantWhileForeground sepenuhnya
The JobInfo.Builder#setImportantWhileForeground(boolean)
method indicates the importance of a job while the scheduling app is in the
foreground or when temporarily exempted from background restrictions.
This method has been deprecated since Android 12 (API level 31). Starting in Android 16, it no longer functions effectively and calling this method will be ignored.
This removal of functionality also applies to
JobInfo#isImportantWhileForeground()
. Starting in Android
16, if the method is called, the method returns false
.
Cakupan prioritas siaran yang diurutkan tidak lagi bersifat global
Android apps are allowed to define priorities on broadcast receivers to control
the order in which the receivers receive and process the broadcast. For
manifest-declared receivers, apps can use the
android:priority
attribute to define the priority and for
context-registered receivers, apps can use the
IntentFilter#setPriority()
API to define the priority. When
a broadcast is sent, the system delivers it to receivers in order of their
priority, from highest to lowest.
In Android 16, broadcast delivery order using the android:priority
attribute
or IntentFilter#setPriority()
across different processes will not be
guaranteed. Broadcast priorities will only be respected within the same
application process rather than across all processes.
Also, broadcast priorities will be automatically confined to the range
(SYSTEM_LOW_PRIORITY
+ 1,
SYSTEM_HIGH_PRIORITY
- 1). Only system components will be
allowed to set SYSTEM_LOW_PRIORITY
, SYSTEM_HIGH_PRIORITY
as broadcast
priority.
Your app might be impacted if it does either of the following:
- Your application has declared multiple processes with the same broadcast intent, and has expectations around receiving those intents in a certain order based on the priority.
- Your application process interacts with other processes and has expectations around receiving a broadcast intent in a certain order.
If the processes need to coordinate with each other, they should communicate using other coordination channels.
Perubahan internal ART
Android 16 includes the latest updates to the Android Runtime (ART) that improve the Android Runtime's (ART's) performance and provide support for additional Java features. Through Google Play System updates, these improvements are also available to over a billion devices running Android 12 (API level 31) and higher.
As these changes are released, libraries and app code that rely on internal structures of ART might not work correctly on devices running Android 16, along with earlier Android versions that update the ART module through Google Play system updates.
Relying on internal structures (such as non-SDK interfaces) can always lead to compatibility problems, but it's particularly important to avoid relying on code (or libraries containing code) that leverages internal ART structures, since ART changes aren't tied to the platform version the device is running on and they go out to over a billion devices through Google Play system updates.
All developers should check whether their app is impacted by testing their apps thoroughly on Android 16. In addition, check the known issues to see if your app depends on any libraries that we've identified that rely on internal ART structures. If you do have app code or library dependencies that are affected, seek public API alternatives whenever possible and request public APIs for new use cases by creating a feature request in our issue tracker.
Mode kompatibilitas ukuran halaman 16 KB
Android 15 introduced support for 16 KB memory pages to optimize performance of the platform. Android 16 adds a compatibility mode, allowing some apps built for 4 KB memory pages to run on a device configured for 16 KB memory pages.
When your app is running on a device with Android 16 or higher, if Android
detects that your app has 4 KB aligned memory pages, it automatically uses
compatibility mode and display a notification dialog to the user. Setting the
android:pageSizeCompat
property in the AndroidManifest.xml
to enable the
backwards compatibility mode will prevent the display of the dialog when your
app launches. To use the android:pageSizeCompat
property, compile your app
using the Android 16 SDK.
For best performance, reliability, and stability, your app should still be 16 KB aligned. Check out our recent blog post on updating your apps to support 16 KB memory pages for more details.

Pengalaman pengguna dan UI sistem
Android 16 (API level 36) menyertakan perubahan berikut yang dimaksudkan untuk menciptakan pengalaman pengguna yang lebih konsisten dan intuitif.
Penghentian pengumuman aksesibilitas yang mengganggu
Android 16 deprecates accessibility announcements, characterized by the use of
announceForAccessibility
or the dispatch of
TYPE_ANNOUNCEMENT
accessibility events. These can create
inconsistent user experiences for users of TalkBack and Android's screen reader,
and alternatives better serve a broader range of user needs across a variety of
Android's assistive technologies.
Examples of alternatives:
- For significant UI changes like window changes, use
Activity.setTitle(CharSequence)
andsetAccessibilityPaneTitle(java.lang.CharSequence)
. In Compose, useModifier.semantics { paneTitle = "paneTitle" }
- To inform the user of changes to critical UI, use
setAccessibilityLiveRegion(int)
. In Compose, useModifier.semantics { liveRegion = LiveRegionMode.[Polite|Assertive]}
. These should be used sparingly as they may generate announcements every time a View is updated. - To notify users about errors, send an
AccessibilityEvent
of typeAccessibilityEvent#CONTENT_CHANGE_TYPE_ERROR
and setAccessibilityNodeInfo#setError(CharSequence)
, or useTextView#setError(CharSequence)
.
The reference documentation for the deprecated
announceForAccessibility
API includes more details about
suggested alternatives.
Dukungan untuk navigasi 3 tombol
Android 16 brings predictive back support to the 3-button navigation for apps that have properly migrated to predictive back. Long-pressing the back button initiates a predictive back animation, giving you a preview of where the back swipe takes you.
This behavior applies across all areas of the system that support predictive back animations, including the system animations (back-to-home, cross-task, and cross-activity).
Faktor bentuk perangkat
Android 16 (API level 36) menyertakan perubahan berikut untuk aplikasi saat diproyeksikan ke layar oleh pemilik perangkat virtual.
Penggantian pemilik perangkat virtual
A virtual device owner is a trusted or privileged app that creates and manages a virtual device. Virtual device owners run apps on a virtual device and then project the apps to the display of a remote device, such as a personal computer, virtual reality device, or car infotainment system. The virtual device owner is on a local device, such as a mobile phone.

Per-app overrides
On devices running Android 16 (API level 36), virtual device owners can override app settings on select virtual devices that the virtual device owners manage. For example, to improve app layout, a virtual device owner can ignore orientation, aspect ratio, and resizability restrictions when projecting apps onto an external display.
Common breaking changes
The Android 16 behavior might impact your app's UI on large screen form factors such as car displays or Chromebooks, especially layouts that were designed for small displays in portrait orientation. To learn how to make your app adaptive for all device form factors, see About adaptive layouts.
References
Keamanan
Android 16 (API level 36) menyertakan perubahan yang meningkatkan keamanan sistem untuk membantu melindungi aplikasi dan pengguna dari aplikasi berbahaya.
Peningkatan keamanan terhadap serangan pengalihan Intent
Android 16 memberikan keamanan default terhadap serangan pengalihan
Intent
umum, dengan kompatibilitas minimum dan perubahan developer yang diperlukan.
Kami memperkenalkan solusi hardening keamanan secara default untuk eksploitasi pengalihan
Intent
. Pada umumnya, aplikasi yang menggunakan intent biasanya tidak akan
mengalami masalah kompatibilitas; kami telah mengumpulkan metrik selama
proses pengembangan untuk memantau aplikasi mana yang mungkin mengalami kerusakan.
Pengalihan intent di Android terjadi saat penyerang dapat mengontrol sebagian atau seluruh konten intent yang digunakan untuk meluncurkan komponen baru dalam konteks aplikasi yang rentan, sementara aplikasi korban meluncurkan intent sub-level yang tidak tepercaya di kolom tambahan Intent ("tingkat teratas"). Hal ini dapat menyebabkan aplikasi penyerang meluncurkan komponen pribadi dalam konteks aplikasi korban, memicu tindakan dengan hak istimewa, atau mendapatkan akses URI ke data sensitif, yang berpotensi menyebabkan pencurian data dan eksekusi kode arbitrer.
Memilih tidak ikut penanganan pengalihan Intent
Android 16 memperkenalkan API baru yang memungkinkan aplikasi memilih tidak ikut perlindungan keamanan peluncuran. Hal ini mungkin diperlukan dalam kasus tertentu saat perilaku keamanan default mengganggu kasus penggunaan aplikasi yang sah.
Untuk aplikasi yang dikompilasi dengan SDK Android 16 (API level 36) atau yang lebih tinggi
Anda dapat langsung menggunakan metode removeLaunchSecurityProtection()
pada objek Intent.
val i = intent
val iSublevel: Intent? = i.getParcelableExtra("sub_intent")
iSublevel?.removeLaunchSecurityProtection() // Opt out from hardening
iSublevel?.let { startActivity(it) }
Untuk aplikasi yang dikompilasi dengan Android 15 (API level 35) atau yang lebih lama
Meskipun tidak direkomendasikan, Anda dapat menggunakan refleksi untuk mengakses
metode removeLaunchSecurityProtection()
.
val i = intent
val iSublevel: Intent? = i.getParcelableExtra("sub_intent", Intent::class.java)
try {
val removeLaunchSecurityProtection = Intent::class.java.getDeclaredMethod("removeLaunchSecurityProtection")
removeLaunchSecurityProtection.invoke(iSublevel)
} catch (e: Exception) {
// Handle the exception, e.g., log it
} // Opt-out from the security hardening using reflection
iSublevel?.let { startActivity(it) }
Aplikasi pendamping tidak lagi diberi tahu tentang waktu tunggu penemuan yang habis
Android 16 introduces a new behavior during
companion device pairing flow to protect the user's location
privacy from malicious apps. All companion apps running on Android 16 are no
longer directly notified of discovery timeout using
RESULT_DISCOVERY_TIMEOUT
. Instead, the user is
notified of timeout events with a visual dialog. When the user dismisses
the dialog, the app is alerted of the association failure with
RESULT_USER_REJECTED
.
The search duration has also been extended from the original 20 seconds, and the device discovery can be stopped by the user at any point during the search. If at least one device was discovered within the first 20 seconds of starting the search, the CDM stops searching for additional devices.
Konektivitas
Android 16 (level API 36) menyertakan perubahan berikut dalam stack Bluetooth untuk meningkatkan konektivitas dengan perangkat periferal.
Peningkatan penanganan kerugian obligasi
Starting in Android 16, the Bluetooth stack has been updated to improve security and user experience when a remote bond loss is detected. Previously, the system would automatically remove the bond and initiate a new pairing process, which could lead to unintentional re-pairing. We have seen in many instances apps not taking care of the bond loss event in a consistent way.
To unify the experience, Android 16 improved the bond loss handling to the system. If a previously bonded Bluetooth device could not be authenticated upon reconnection, the system will disconnect the link, retain local bond information, and display a system dialog informing users of the bond loss and directing them to re-pair.