Halaman ini diterjemahkan oleh Cloud Translation API.

Perubahan perilaku: semua aplikasi

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

Starting in Android 16, we're adjusting regular and expedited job execution runtime quota based on the following factors:

Which app standby bucket the application is in: in Android 16, active standby buckets will start being enforced by a generous runtime quota.
If the job starts execution while the app is in a top state: in Android 16, Jobs started while the app is visible to the user and continues after the app becomes invisible, will adhere to the job runtime quota.
If the job is executing while running a Foreground Service: in Android 16, jobs that are executing while concurrently with a foreground service will adhere to the job runtime quota. If you're leveraging jobs for user initiated data transfer, consider using user initiated data transfer jobs instead.

This change impacts tasks scheduled using WorkManager, JobScheduler, and DownloadManager. To debug why a job was stopped, we recommend logging why your job was stopped by calling WorkInfo.getStopReason() (for JobScheduler jobs, call JobParameters.getStopReason()).

For information about how your app's state affects the resources it can use, see Power management resource limits. For more information on battery-optimal best practices, refer to guidance on optimize battery use for task scheduling APIs.

We also recommend leveraging the new JobScheduler#getPendingJobReasonsHistory API introduced in Android 16 to understand why a job has not executed.

Testing

To test your app's behavior, you can enable override of certain job quota optimizations as long as the app is running on an Android 16 device.

To disable enforcement of "top state will adhere to job runtime quota", run the following adb command:

adb shell am compat enable OVERRIDE_QUOTA_ENFORCEMENT_TO_TOP_STARTED_JOBS APP_PACKAGE_NAME

To disable enforcement of "jobs that are executing while concurrently with a foreground service will adhere to the job runtime quota", run the following adb command:

adb shell am compat enable OVERRIDE_QUOTA_ENFORCEMENT_TO_FGS_JOBS APP_PACKAGE_NAME

To test certain app standby bucket behavior, you can set the app standby bucket of your app using the following adb command:

adb shell am set-standby-bucket APP_PACKAGE_NAME active|working_set|frequent|rare|restricted

To understand the app standby bucket your app is in, you can get the app standby bucket of your app using the following adb command:

adb shell am get-standby-bucket APP_PACKAGE_NAME

Alasan penghentian tugas kosong yang ditinggalkan

Tugas yang ditinggalkan terjadi saat objek JobParameters yang terkait dengan tugas telah dibersihkan sampah memorinya, tetapi JobService#jobFinished(JobParameters, boolean) belum dipanggil untuk menandakan penyelesaian tugas. Hal ini menunjukkan bahwa tugas mungkin sedang berjalan dan dijadwalkan ulang tanpa sepengetahuan aplikasi.

Aplikasi yang mengandalkan JobScheduler, tidak mempertahankan referensi yang kuat ke objek JobParameters, dan waktu tunggu kini akan diberi alasan penghentian tugas baru STOP_REASON_TIMEOUT_ABANDONED, bukan STOP_REASON_TIMEOUT.

Jika alasan perhentian yang ditinggalkan baru sering terjadi, sistem akan mengambil langkah mitigasi untuk mengurangi frekuensi tugas.

Aplikasi harus menggunakan alasan penghentian baru untuk mendeteksi dan mengurangi tugas yang ditinggalkan.

Jika menggunakan WorkManager, AsyncTask, atau DownloadManager, Anda tidak akan terpengaruh karena API ini mengelola siklus proses tugas atas nama aplikasi Anda.

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.

The compatibility mode dialog that displays when the system detects that a 4 KB-aligned app could run more optimally if 16 KB aligned.

Pengalaman pengguna dan UI sistem

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

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) and setAccessibilityPaneTitle(java.lang.CharSequence). In Compose, use Modifier.semantics { paneTitle = "paneTitle" }
To inform the user of changes to critical UI, use setAccessibilityLiveRegion(int). In Compose, use Modifier.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 type AccessibilityEvent#CONTENT_CHANGE_TYPE_ERROR and set AccessibilityNodeInfo#setError(CharSequence), or use TextView#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).

The predictive back animations in 3-button navigation mode.

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.

Virtual device owner on phone creates virtual device that projects app to remote display.

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

Companion app streaming

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 memperkenalkan perilaku baru selama alur penyambungan perangkat pendamping untuk melindungi privasi lokasi pengguna dari aplikasi berbahaya. Semua aplikasi pendamping yang berjalan di Android 16 tidak lagi diberi tahu secara langsung tentang waktu tunggu penemuan yang habis menggunakan RESULT_DISCOVERY_TIMEOUT. Sebagai gantinya, pengguna akan diberi tahu tentang peristiwa waktu tunggu habis dengan dialog visual. Saat pengguna menutup dialog, aplikasi akan diberi tahu tentang kegagalan pengaitan dengan RESULT_USER_REJECTED.

Durasi penelusuran juga telah diperpanjang dari 20 detik awal, dan penemuan perangkat dapat dihentikan oleh pengguna kapan saja selama penelusuran. Jika setidaknya satu perangkat ditemukan dalam 20 detik pertama sejak memulai penelusuran, CDM akan berhenti menelusuri perangkat tambahan.

Konektivitas

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

Peningkatan penanganan kerugian obligasi

Mulai Android 16, stack Bluetooth telah diupdate untuk meningkatkan keamanan dan pengalaman pengguna saat kehilangan ikatan jarak jauh terdeteksi. Sebelumnya, sistem akan otomatis menghapus ikatan dan memulai proses penyambungan baru, yang dapat menyebabkan penyambungan ulang yang tidak disengaja. Kami telah melihat dalam banyak kasus aplikasi tidak menangani peristiwa kehilangan ikatan secara konsisten.

Untuk menyatukan pengalaman, Android 16 meningkatkan penanganan kehilangan ikatan ke sistem. Jika perangkat Bluetooth yang sebelumnya tersambung tidak dapat diautentikasi setelah terhubung kembali, sistem akan memutuskan hubungan link, mempertahankan informasi ikatan lokal, dan menampilkan dialog sistem yang memberi tahu pengguna tentang hilangnya ikatan dan mengarahkan mereka untuk menyambungkan kembali.