Definisi Kompatibilitas Android 10

1. Perkenalan

Dokumen ini merinci persyaratan yang harus dipenuhi agar perangkat kompatibel dengan Android 10.

Penggunaan “HARUS”, “TIDAK HARUS”, “WAJIB”, “HARUS”, “TIDAK BOLEH”, “HARUS”, “TIDAK BOLEH”, “DIANJURKAN”, “BOLEH”, dan “OPSIONAL” sesuai dengan IETF standar yang ditentukan dalam RFC2119 .

Seperti yang digunakan dalam dokumen ini, “implementer perangkat” atau “implementer” adalah orang atau organisasi yang mengembangkan solusi perangkat keras/perangkat lunak yang menjalankan Android 10. “implementasi perangkat” atau “implementasi" adalah solusi perangkat keras/perangkat lunak yang dikembangkan.

Agar dianggap kompatibel dengan Android 10, penerapan perangkat HARUS memenuhi persyaratan yang disajikan dalam Definisi Kompatibilitas ini, termasuk dokumen apa pun yang digabungkan melalui referensi.

Jika definisi ini atau pengujian perangkat lunak yang dijelaskan di bagian 10 tidak jelas, ambigu, atau tidak lengkap, maka pelaksana perangkat bertanggung jawab untuk memastikan kompatibilitas dengan implementasi yang ada.

Karena alasan ini, Proyek Sumber Terbuka Android merupakan referensi dan implementasi Android yang disukai. Pelaksana perangkat SANGAT DIREKOMENDASIKAN untuk mendasarkan penerapannya semaksimal mungkin pada kode sumber “upstream” yang tersedia dari Proyek Sumber Terbuka Android. Meskipun beberapa komponen secara hipotetis dapat diganti dengan implementasi alternatif, SANGAT DISARANKAN untuk tidak mengikuti praktik ini, karena lulus pengujian perangkat lunak akan menjadi jauh lebih sulit. Implementer bertanggung jawab untuk memastikan kompatibilitas penuh perilaku dengan implementasi Android standar, termasuk dan di luar Compatibility Test Suite. Terakhir, perhatikan bahwa penggantian dan modifikasi komponen tertentu secara eksplisit dilarang oleh dokumen ini.

Banyak sumber daya yang tertaut dalam dokumen ini berasal langsung atau tidak langsung dari Android SDK dan secara fungsional akan identik dengan informasi dalam dokumentasi SDK tersebut. Jika Definisi Kompatibilitas atau Rangkaian Uji Kompatibilitas ini tidak sesuai dengan dokumentasi SDK, dokumentasi SDK dianggap resmi. Detail teknis apa pun yang disediakan dalam sumber daya tertaut di seluruh dokumen ini dianggap sebagai bagian dari Definisi Kompatibilitas ini.

1.1 Struktur Dokumen

1.1.1. Persyaratan berdasarkan Jenis Perangkat

Bagian 2 berisi semua persyaratan yang berlaku untuk jenis perangkat tertentu. Setiap subbagian dari Bagian 2 didedikasikan untuk jenis perangkat tertentu.

Semua persyaratan lainnya, yang berlaku secara universal pada implementasi perangkat Android apa pun, tercantum di bagian setelah Bagian 2 . Persyaratan ini dirujuk sebagai "Persyaratan Inti" dalam dokumen ini.

1.1.2. ID Persyaratan

ID Persyaratan ditetapkan untuk persyaratan HARUS.

• ID ditetapkan hanya untuk persyaratan HARUS.
• Persyaratan SANGAT DIANJURKAN ditandai sebagai [SR] tetapi ID tidak ditetapkan.
• ID tersebut terdiri dari : ID Tipe Perangkat - ID Kondisi - ID Persyaratan (misalnya C-0-1).

Setiap ID didefinisikan sebagai berikut:

• ID Jenis Perangkat (lihat lebih lanjut di 2. Jenis Perangkat )
  • C: Core (Persyaratan yang diterapkan pada implementasi perangkat Android apa pun)
  • H: Perangkat Genggam Android
  • T: Perangkat Televisi Android
  • J: Implementasi Android Automotive
  • W: Implementasi Android Watch
  • Tab: Implementasi Tablet Android
• ID kondisi
  • Jika persyaratannya tidak bersyarat, ID ini ditetapkan sebagai 0.
  • Jika persyaratannya bersyarat, 1 ditetapkan untuk kondisi pertama dan jumlahnya bertambah 1 dalam bagian yang sama dan jenis perangkat yang sama.
• ID Persyaratan
  • ID ini dimulai dari 1 dan bertambah 1 dalam bagian yang sama dan kondisi yang sama.

1.1.3. ID Persyaratan di Bagian 2

ID Persyaratan di Bagian 2 dimulai dengan ID bagian terkait yang diikuti dengan ID Persyaratan yang dijelaskan di atas.

• ID pada Bagian 2 terdiri dari : ID Bagian / ID Jenis Perangkat - ID Kondisi - ID Persyaratan (misalnya 7.4.3/A-0-1).

2. Jenis Perangkat

Meskipun Proyek Sumber Terbuka Android menyediakan tumpukan perangkat lunak yang dapat digunakan untuk berbagai jenis perangkat dan faktor bentuk, ada beberapa jenis perangkat yang memiliki ekosistem distribusi aplikasi yang relatif lebih baik.

Bagian ini menjelaskan jenis perangkat tersebut, serta persyaratan dan rekomendasi tambahan yang berlaku untuk setiap jenis perangkat.

Semua implementasi perangkat Android yang tidak cocok dengan jenis perangkat apa pun yang dijelaskan HARUS tetap memenuhi semua persyaratan di bagian lain Definisi Kompatibilitas ini.

2.1 Konfigurasi Perangkat

Untuk mengetahui perbedaan utama dalam konfigurasi perangkat keras berdasarkan jenis perangkat, lihat persyaratan khusus perangkat di bagian ini.

2.2. Persyaratan Genggam

Perangkat Genggam Android mengacu pada implementasi perangkat Android yang biasanya digunakan dengan memegangnya di tangan, seperti pemutar mp3, ponsel, atau tablet.

Implementasi perangkat Android diklasifikasikan sebagai Genggam jika memenuhi seluruh kriteria berikut:

• Miliki sumber listrik yang memberikan mobilitas, seperti baterai.
• Memiliki ukuran diagonal layar fisik pada kisaran 2,5 hingga 8 inci.

Persyaratan tambahan di sisa bagian ini khusus untuk implementasi perangkat Genggam Android.

2.2.1. Perangkat keras

Implementasi perangkat genggam:

• [ 7.1 .1.1/H-0-1] HARUS memiliki setidaknya satu layar yang kompatibel dengan Android dengan ukuran diagonal fisik minimal 2,5 inci dan setiap layar yang kompatibel dengan Android HARUS memenuhi semua persyaratan yang dijelaskan dalam dokumen ini.
• [ 7.1 .1.3/H-SR] SANGAT DIREKOMENDASIKAN untuk memberikan kemampuan kepada pengguna untuk mengubah ukuran tampilan (kepadatan layar).

Jika penerapan perangkat Genggam mengklaim dukungan untuk tampilan rentang dinamis tinggi melalui Configuration.isScreenHdr() , penerapan tersebut:

• [ 7.1 .4.5/H-1-1] HARUS mengiklankan dukungan untuk ekstensi EGL_EXT_gl_colorspace_bt2020_pq , EGL_EXT_surface_SMPTE2086_metadata , EGL_EXT_surface_CTA861_3_metadata , VK_EXT_swapchain_colorspace , dan VK_EXT_hdr_metadata .

Implementasi perangkat genggam:

• [ 7.1 .5/H-0-1] HARUS menyertakan dukungan untuk mode kompatibilitas aplikasi lama seperti yang diterapkan oleh kode sumber terbuka Android upstream. Artinya, implementasi perangkat TIDAK HARUS mengubah pemicu atau ambang batas saat mode kompatibilitas diaktifkan, dan TIDAK HARUS mengubah perilaku mode kompatibilitas itu sendiri.
• [ 7.2 .1/H-0-1] HARUS menyertakan dukungan untuk aplikasi Input Method Editor (IME) pihak ketiga.
• [ 7.2 .3/H-0-3] HARUS menyediakan fungsi Beranda di semua tampilan kompatibel Android yang menyediakan layar beranda.
• [ 7.2 .3/H-0-4] HARUS menyediakan fungsi Kembali di semua tampilan yang kompatibel dengan Android dan fungsi Terbaru di setidaknya salah satu tampilan yang kompatibel dengan Android.
• [ 7.2 .3/H-0-2] HARUS mengirimkan peristiwa tekan normal dan lama dari fungsi Kembali ( KEYCODE_BACK ) ke aplikasi latar depan. Peristiwa ini TIDAK BOLEH dikonsumsi oleh sistem dan BISA dipicu oleh bagian luar perangkat Android (misalnya keyboard perangkat keras eksternal yang terhubung ke perangkat Android).
• [ 7.2 .4/H-0-1] HARUS mendukung input layar sentuh.
• [ 7.2 .4/H-SR] SANGAT DIREKOMENDASIKAN untuk meluncurkan aplikasi bantuan yang dipilih pengguna, dengan kata lain aplikasi yang mengimplementasikan VoiceInteractionService, atau aktivitas yang menangani ACTION_ASSIST dengan menekan lama KEYCODE_MEDIA_PLAY_PAUSE atau KEYCODE_HEADSETHOOK jika aktivitas latar depan tidak menangani peristiwa-peristiwa yang sudah lama terjadi itu.
• [ 7.3 .1/H-SR] SANGAT DIANJURKAN untuk menyertakan akselerometer 3 sumbu.

Jika implementasi perangkat Genggam menyertakan akselerometer 3 sumbu, maka:

• [ 7.3 .1/H-1-1] HARUS dapat melaporkan kejadian hingga frekuensi minimal 100 Hz.

Jika implementasi perangkat Genggam menyertakan penerima GPS/GNSS dan melaporkan kemampuan tersebut ke aplikasi melalui tanda fitur android.hardware.location.gps , implementasi tersebut:

• [ 7.3 .3/H-2-1] HARUS melaporkan pengukuran GNSS segera setelah ditemukan, meskipun lokasi yang dihitung dari GPS/GNSS belum dilaporkan.
• [ 7.3 .3/H-2-2] HARUS melaporkan kecepatan pseudorange dan pseudorange GNSS, yang, dalam kondisi langit terbuka setelah menentukan lokasi, saat diam atau bergerak dengan percepatan kurang dari 0,2 meter per detik kuadrat, cukup untuk menghitung posisi dalam jarak 20 meter, dan kecepatan dalam 0,2 meter per detik, setidaknya 95% dari waktu.

Jika implementasi perangkat Genggam menyertakan giroskop 3 sumbu, maka:

• [ 7.3 .4/H-3-1] HARUS dapat melaporkan kejadian hingga frekuensi minimal 100 Hz.
• [ 7.3 .4/H-3-2] HARUS mampu mengukur perubahan orientasi hingga 1000 derajat per detik.

Implementasi perangkat genggam yang dapat melakukan panggilan suara dan menunjukkan nilai apa pun selain PHONE_TYPE_NONE di getPhoneType :

• [ 7.3 .8/H] HARUS menyertakan sensor jarak.

Implementasi perangkat genggam:

• [ 7.3 .11/H-SR] DIREKOMENDASIKAN untuk mendukung sensor pose dengan 6 derajat kebebasan.
• [ 7.4 .3/H] HARUS menyertakan dukungan untuk Bluetooth dan Bluetooth LE.

Jika implementasi perangkat Genggam menyertakan koneksi terukur, maka:

• [ 7.4 .7/H-1-1] HARUS menyediakan mode penghemat data.

Jika implementasi perangkat Genggam menyertakan perangkat kamera logis yang mencantumkan kemampuan menggunakan CameraMetadata.REQUEST_AVAILABLE_CAPABILITIES_LOGICAL_MULTI_CAMERA , implementasi tersebut:

• [ 7.5 .4/H-1-1] HARUS memiliki bidang pandang normal (FOV) secara default dan HARUS antara 50 dan 90 derajat.

Implementasi perangkat genggam:

• [ 7.6 .1/H-0-1] HARUS memiliki setidaknya 4 GB penyimpanan non-volatil yang tersedia untuk data pribadi aplikasi (alias partisi "/data").
• [ 7.6 .1/H-0-2] HARUS mengembalikan "true" untuk ActivityManager.isLowRamDevice() ketika memori yang tersedia untuk kernel dan ruang pengguna kurang dari 1GB.

Jika implementasi perangkat Genggam menyatakan dukungan hanya untuk ABI 32-bit:

• [ 7.6 .1/H-1-1] Memori yang tersedia untuk kernel dan ruang pengguna HARUS minimal 416MB jika tampilan default menggunakan resolusi framebuffer hingga qHD (misalnya FWVGA).

• [ 7.6 .1/H-2-1] Memori yang tersedia untuk kernel dan ruang pengguna HARUS minimal 592MB jika tampilan default menggunakan resolusi framebuffer hingga HD+ (misalnya HD, WSVGA).

• [ 7.6 .1/H-3-1] Memori yang tersedia untuk kernel dan ruang pengguna HARUS minimal 896MB jika tampilan default menggunakan resolusi framebuffer hingga FHD (misalnya WSXGA+).

• [ 7.6 .1/H-4-1] Memori yang tersedia untuk kernel dan ruang pengguna HARUS minimal 1344MB jika tampilan default menggunakan resolusi framebuffer hingga QHD (misalnya QWXGA).

Jika implementasi perangkat Genggam menyatakan dukungan terhadap ABI 64-bit (dengan atau tanpa ABI 32-bit):

• [ 7.6 .1/H-5-1] Memori yang tersedia untuk kernel dan ruang pengguna HARUS minimal 816MB jika tampilan default menggunakan resolusi framebuffer hingga qHD (misalnya FWVGA).

• [ 7.6 .1/H-6-1] Memori yang tersedia untuk kernel dan ruang pengguna HARUS minimal 944MB jika tampilan default menggunakan resolusi framebuffer hingga HD+ (misalnya HD, WSVGA).

• [ 7.6 .1/H-7-1] Memori yang tersedia untuk kernel dan ruang pengguna HARUS minimal 1280MB jika tampilan default menggunakan resolusi framebuffer hingga FHD (misalnya WSXGA+).

• [ 7.6 .1/H-8-1] Memori yang tersedia untuk kernel dan ruang pengguna HARUS minimal 1824MB jika tampilan default menggunakan resolusi framebuffer hingga QHD (misalnya QWXGA).

Perhatikan bahwa "memori yang tersedia untuk kernel dan ruang pengguna" di atas mengacu pada ruang memori yang disediakan selain memori apa pun yang telah didedikasikan untuk komponen perangkat keras seperti radio, video, dan sebagainya yang tidak berada di bawah kendali kernel pada implementasi perangkat.

Jika implementasi perangkat Genggam mencakup kurang dari atau sama dengan 1 GB memori yang tersedia untuk kernel dan ruang pengguna, maka implementasi tersebut:

• [ 7.6 .1/H-9-1] HARUS mendeklarasikan tanda fitur android.hardware.ram.low .
• [ 7.6 .1/H-9-2] HARUS memiliki setidaknya 1,1 GB penyimpanan non-volatil untuk data pribadi aplikasi (alias partisi "/data").

Jika implementasi perangkat Genggam mencakup lebih dari 1 GB memori yang tersedia untuk kernel dan ruang pengguna, maka implementasi tersebut:

• [ 7.6 .1/H-10-1] HARUS memiliki setidaknya 4GB penyimpanan non-volatil yang tersedia untuk data pribadi aplikasi (alias partisi "/data").
• HARUS mendeklarasikan tanda fitur android.hardware.ram.normal .

Implementasi perangkat genggam:

• [ 7.6 .2/H-0-1] TIDAK BOLEH menyediakan penyimpanan bersama aplikasi yang lebih kecil dari 1 GiB.
• [ 7.7 .1/H] HARUS menyertakan port USB yang mendukung mode periferal.

Jika implementasi perangkat genggam menyertakan port USB yang mendukung mode periferal, maka:

• [ 7.7 .1/H-1-1] HARUS mengimplementasikan API Android Open Accessories (AOA).

Jika implementasi perangkat Genggam menyertakan port USB yang mendukung mode host, maka:

• [ 7.7 .2/H-1-1] HARUS mengimplementasikan kelas audio USB seperti yang didokumentasikan dalam dokumentasi Android SDK.

Implementasi perangkat genggam:

• [ 7.8 .1/H-0-1] HARUS menyertakan mikrofon.
• [ 7.8 .2/H-0-1] HARUS memiliki output audio dan mendeklarasikan android.hardware.audio.output .

Jika implementasi perangkat Genggam mampu memenuhi semua persyaratan kinerja untuk mendukung mode VR dan menyertakan dukungan untuk itu, maka implementasi tersebut:

• [ 7.9 .1/H-1-1] HARUS mendeklarasikan tanda fitur android.hardware.vr.high_performance .
• [ 7.9 .1/H-1-2] HARUS menyertakan aplikasi yang mengimplementasikan android.service.vr.VrListenerService yang dapat diaktifkan oleh aplikasi VR melalui android.app.Activity#setVrModeEnabled .

Jika implementasi perangkat Genggam menyertakan satu atau lebih port USB-C dalam mode host dan implementasi (kelas audio USB), selain persyaratan di bagian 7.7.2 , implementasi tersebut:

• [ 7.8 .2.2/H-1-1] HARUS menyediakan perangkat lunak pemetaan kode HID berikut:

• [ 7.8 .2.2/H-1-2] HARUS memicu ACTION_HEADSET_PLUG pada sisipan steker, tetapi hanya setelah antarmuka audio USB dan titik akhir dihitung dengan benar untuk mengidentifikasi jenis terminal yang terhubung.

Ketika terminal audio USB tipe 0x0302 terdeteksi, terminal tersebut:

• [ 7.8 .2.2/H-2-1] HARUS menyiarkan Intent ACTION_HEADSET_PLUG dengan tambahan "mikrofon" yang disetel ke 0.

Ketika terminal audio USB tipe 0x0402 terdeteksi, terminal tersebut:

• [ 7.8 .2.2/H-3-1] HARUS menyiarkan Intent ACTION_HEADSET_PLUG dengan set ekstra "mikrofon" ke 1.

Ketika API AudioManager.getDevices() dipanggil saat perangkat USB tersambung, mereka:

• [ 7.8 .2.2/H-4-1] HARUS mencantumkan perangkat bertipe AudioDeviceInfo.TYPE_USB_HEADSET dan peran isSink() jika bidang jenis terminal audio USB adalah 0x0302.

• [ 7.8 .2.2/H-4-2] HARUS mencantumkan perangkat bertipe AudioDeviceInfo.TYPE_USB_HEADSET dan peran isSink() jika bidang jenis terminal audio USB adalah 0x0402.

• [ 7.8 .2.2/H-4-3] HARUS mencantumkan perangkat bertipe AudioDeviceInfo.TYPE_USB_HEADSET dan peran isSource() jika bidang jenis terminal audio USB adalah 0x0402.

• [ 7.8 .2.2/H-4-4] HARUS mencantumkan perangkat bertipe AudioDeviceInfo.TYPE_USB_DEVICE dan peran isSink() jika bidang jenis terminal audio USB adalah 0x603.

• [ 7.8 .2.2/H-4-5] HARUS mencantumkan perangkat bertipe AudioDeviceInfo.TYPE_USB_DEVICE dan peran isSource() jika bidang jenis terminal audio USB adalah 0x604.

• [ 7.8 .2.2/H-4-6] HARUS mencantumkan perangkat bertipe AudioDeviceInfo.TYPE_USB_DEVICE dan peran isSink() jika bidang jenis terminal audio USB adalah 0x400.

• [ 7.8 .2.2/H-4-7] HARUS mencantumkan perangkat bertipe AudioDeviceInfo.TYPE_USB_DEVICE dan peran isSource() jika bidang jenis terminal audio USB adalah 0x400.

• [ 7.8 .2.2/H-SR] SANGAT DIREKOMENDASIKAN saat menyambungkan periferal audio USB-C, untuk melakukan enumerasi deskriptor USB, mengidentifikasi jenis terminal, dan menyiarkan Intent ACTION_HEADSET_PLUG dalam waktu kurang dari 1000 milidetik.

2.2.2. Multimedia

Implementasi perangkat genggam HARUS mendukung format pengkodean dan penguraian audio berikut dan membuatnya tersedia untuk aplikasi pihak ketiga:

• [ 5.1 /H-0-1] AMR-NB
• [ 5.1 /H-0-2] AMR-WB
• [ 5.1 /H-0-3] Profil AAC MPEG-4 (AAC LC)
• [ 5.1 /H-0-4] Profil AAC MPEG-4 HE (AAC+)
• [ 5.1 /H-0-5] AAC ELD (AAC penundaan rendah yang ditingkatkan)

Implementasi perangkat genggam HARUS mendukung format pengkodean video berikut dan membuatnya tersedia untuk aplikasi pihak ketiga:

• [ 5.2 /H-0-1] H.264 AVC
• [ 5.2 /H-0-2] VP8

Implementasi perangkat genggam HARUS mendukung format decoding video berikut dan membuatnya tersedia untuk aplikasi pihak ketiga:

• [ 5.3 /H-0-1] H.264 AVC
• [ 5.3 /H-0-2] H.265 HEVC
• [ 5.3 /H-0-3] MPEG-4 SP
• [ 5.3 /H-0-4] VP8
• [ 5.3 /H-0-5] VP9

2.2.3. Perangkat lunak

Implementasi perangkat genggam:

• [ 3.2.3.1 /H-0-1] HARUS memiliki aplikasi yang menangani maksud ACTION_GET_CONTENT , ACTION_OPEN_DOCUMENT , ACTION_OPEN_DOCUMENT_TREE , dan ACTION_CREATE_DOCUMENT seperti yang dijelaskan dalam dokumen SDK, dan memberikan kemampuan pengguna untuk mengakses data penyedia dokumen dengan menggunakan DocumentsProvider API.
• [ 3.4 .1/H-0-1] HARUS menyediakan implementasi lengkap dari android.webkit.Webview API.
• [ 3.4 .2/H-0-1] HARUS menyertakan aplikasi Browser mandiri untuk penelusuran web pengguna umum.
• [ 3.8 .1/H-SR] SANGAT DIREKOMENDASIKAN untuk mengimplementasikan peluncur default yang mendukung penyematan pintasan, widget, dan widgetFeatures dalam aplikasi.
• [ 3.8 .1/H-SR] SANGAT DIREKOMENDASIKAN untuk mengimplementasikan peluncur default yang menyediakan akses cepat ke pintasan tambahan yang disediakan oleh aplikasi pihak ketiga melalui ShortcutManager API.
• [ 3.8 .1/H-SR] SANGAT DIREKOMENDASIKAN untuk menyertakan aplikasi peluncur default yang menampilkan lencana untuk ikon aplikasi.
• [ 3.8 .2/H-SR] SANGAT DIANJURKAN untuk mendukung widget aplikasi pihak ketiga.
• [ 3.8 .3/H-0-1] HARUS mengizinkan aplikasi pihak ketiga untuk memberi tahu pengguna tentang peristiwa penting melalui kelas API Notification dan NotificationManager .
• [ 3.8 .3/H-0-2] HARUS mendukung notifikasi yang kaya.
• [ 3.8 .3/H-0-3] HARUS mendukung notifikasi pendahuluan.
• [ 3.8 .3/H-0-4] HARUS menyertakan bayangan notifikasi, memberikan pengguna kemampuan untuk mengontrol secara langsung (misalnya membalas, menunda, menutup, memblokir) notifikasi melalui kemampuan pengguna seperti tombol tindakan atau panel kontrol sebagaimana diterapkan di AOSP.
• [ 3.8 .3/H-0-5] HARUS menampilkan pilihan yang disediakan melalui RemoteInput.Builder setChoices() di bayangan notifikasi.
• [ 3.8 .3/H-SR] SANGAT DIANJURKAN untuk menampilkan pilihan pertama yang disediakan melalui RemoteInput.Builder setChoices() dalam bayangan notifikasi tanpa interaksi pengguna tambahan.
• [ 3.8 .3/H-SR] SANGAT DIREKOMENDASIKAN untuk menampilkan semua pilihan yang disediakan melalui RemoteInput.Builder setChoices() di bayangan notifikasi ketika pengguna memperluas semua notifikasi di bayangan notifikasi.
• [ 3.8 .3.1/H-SR] SANGAT DIREKOMENDASIKAN untuk menampilkan tindakan yang Notification.Action.Builder.setContextual ditetapkan sebagai true sejalan dengan balasan yang ditampilkan oleh Notification.Remoteinput.Builder.setChoices .
• [ 3.8 .4/H-SR] SANGAT DIREKOMENDASIKAN untuk mengimplementasikan asisten pada perangkat untuk menangani tindakan Assist .

Jika implementasi perangkat Genggam mendukung tindakan Assist, maka implementasi tersebut:

• [ 3.8 .4/H-SR] SANGAT DISARANKAN untuk menggunakan tekan lama tombol HOME sebagai interaksi yang ditentukan untuk meluncurkan aplikasi bantuan seperti yang dijelaskan di bagian 7.2.3 . HARUS meluncurkan aplikasi bantuan yang dipilih pengguna, dengan kata lain aplikasi yang mengimplementasikan VoiceInteractionService , atau aktivitas yang menangani maksud ACTION_ASSIST .

Jika implementasi perangkat Genggam Android mendukung layar kunci, maka:

• [ 3.8 .10/H-1-1] HARUS menampilkan Notifikasi Layar Kunci termasuk Templat Notifikasi Media.

Jika penerapan perangkat Genggam mendukung layar kunci yang aman, penerapannya:

• [ 3.9 /H-1-1] HARUS menerapkan seluruh kebijakan administrasi perangkat yang ditentukan dalam dokumentasi Android SDK.
• [ 3.9 /H-1-2] HARUS mendeklarasikan dukungan profil terkelola melalui tanda fitur android.software.managed_users , kecuali jika perangkat dikonfigurasi sehingga akan melaporkan dirinya sebagai perangkat dengan RAM rendah atau mengalokasikan internal ( penyimpanan yang tidak dapat dilepas) sebagai penyimpanan bersama.

Implementasi perangkat genggam:

• [ 3.10 /H-0-1] HARUS mendukung layanan aksesibilitas pihak ketiga.
• [ 3.10 /H-SR] SANGAT DIREKOMENDASIKAN untuk melakukan pramuat layanan aksesibilitas pada perangkat yang sebanding dengan atau melampaui fungsi layanan aksesibilitas Tombol Akses dan TalkBack (untuk bahasa yang didukung oleh mesin Text-to-speech yang sudah diinstal sebelumnya) sebagaimana disediakan dalam talkback terbuka proyek sumber .
• [ 3.11 /H-0-1] HARUS mendukung pemasangan mesin TTS pihak ketiga.
• [ 3.11 /H-SR] SANGAT DIANJURKAN untuk menyertakan mesin TTS yang mendukung bahasa yang tersedia di perangkat.
• [ 3.13 /H-SR] SANGAT DIREKOMENDASIKAN untuk menyertakan komponen UI Pengaturan Cepat.

Jika penerapan perangkat genggam Android menyatakan dukungan FEATURE_BLUETOOTH atau FEATURE_WIFI , maka:

• [ 3.16 /H-1-1] HARUS mendukung fitur pemasangan perangkat pendamping.

Jika fungsi navigasi disediakan sebagai tindakan berbasis gerakan di layar:

• [ 7.2 .3/H] Zona pengenalan gerakan untuk fungsi Beranda HARUS tingginya tidak lebih dari 32 dp dari bagian bawah layar.

Jika implementasi perangkat Genggam menyediakan fungsi navigasi sebagai isyarat dari mana saja di tepi kiri dan kanan layar:

• [ 7.2 .3/H-0-1] Area gerakan fungsi navigasi HARUS lebarnya kurang dari 40 dp di setiap sisi. Area isyarat HARUS memiliki lebar 24 dp secara default.

2.2.4. Kinerja dan Kekuatan

• [ 8.1 /H-0-1] Latensi bingkai yang konsisten . Latensi frame yang tidak konsisten atau penundaan dalam merender frame TIDAK BOLEH terjadi lebih dari 5 frame dalam satu detik, dan HARUS di bawah 1 frame dalam satu detik.
• [ 8.1 /H-0-2] Latensi antarmuka pengguna . Implementasi perangkat HARUS memastikan pengalaman pengguna berlatensi rendah dengan men-scroll daftar 10 ribu entri seperti yang ditentukan oleh Android Compatibility Test Suite (CTS) dalam waktu kurang dari 36 detik.
• [ 8.1 /H-0-3] Peralihan tugas . Ketika beberapa aplikasi telah diluncurkan, meluncurkan kembali aplikasi yang sudah berjalan setelah diluncurkan HARUS memakan waktu kurang dari 1 detik.

Implementasi perangkat genggam:

• [ 8.2 /H-0-1] HARUS memastikan kinerja penulisan berurutan minimal 5 MB/s.
• [ 8.2 /H-0-2] HARUS memastikan kinerja penulisan acak minimal 0,5 MB/s.
• [ 8.2 /H-0-3] HARUS memastikan kinerja pembacaan berurutan minimal 15 MB/s.
• [ 8.2 /H-0-4] HARUS memastikan kinerja pembacaan acak minimal 3,5 MB/s.

Jika implementasi perangkat Genggam menyertakan fitur untuk meningkatkan manajemen daya perangkat yang disertakan dalam AOSP atau memperluas fitur yang disertakan dalam AOSP, maka implementasi tersebut:

• [ 8.3 /H-1-1] HARUS memberikan kemampuan pengguna untuk mengaktifkan dan menonaktifkan fitur penghemat baterai.
• [ 8.3 /H-1-2] HARUS memberikan kemampuan pengguna untuk menampilkan semua aplikasi yang dikecualikan dari mode hemat daya Aplikasi Siaga dan Istirahatkan.

Implementasi perangkat genggam:

• [ 8.4 /H-0-1] HARUS menyediakan profil daya per komponen yang menentukan nilai konsumsi saat ini untuk setiap komponen perangkat keras dan perkiraan pengurasan baterai yang disebabkan oleh komponen dari waktu ke waktu seperti yang didokumentasikan di situs Proyek Sumber Terbuka Android.
• [ 8.4 /H-0-2] HARUS melaporkan semua nilai konsumsi daya dalam miliampere jam (mAh).
• [ 8.4 /H-0-3] HARUS melaporkan konsumsi daya CPU per UID setiap proses. Proyek Sumber Terbuka Android memenuhi persyaratan melalui implementasi modul kernel uid_cputime .
• [ 8.4 /H-0-4] HARUS membuat penggunaan daya ini tersedia melalui perintah adb shell dumpsys batterystats shell kepada pengembang aplikasi.
• [ 8.4 /H] HARUS dikaitkan dengan komponen perangkat keras itu sendiri jika tidak dapat mengaitkan penggunaan daya komponen perangkat keras ke suatu aplikasi.

Jika implementasi perangkat Genggam menyertakan output layar atau video, maka:

• [ 8.4 /H-1-1] HARUS menghormati maksud android.intent.action.POWER_USAGE_SUMMARY dan menampilkan menu pengaturan yang menunjukkan penggunaan daya ini.

2.2.5. Model Keamanan

Implementasi perangkat genggam:

• [ 9.1 /H-0-1] HARUS mengizinkan aplikasi pihak ketiga mengakses statistik penggunaan melalui izin android.permission.PACKAGE_USAGE_STATS dan menyediakan mekanisme yang dapat diakses pengguna untuk memberikan atau mencabut akses ke aplikasi tersebut sebagai respons terhadap android.settings.ACTION_USAGE_ACCESS_SETTINGS maksud android.settings.ACTION_USAGE_ACCESS_SETTINGS .

Implementasi perangkat genggam (* Tidak berlaku untuk Tablet):

• [ 9.11 /H-0-2]* HARUS mencadangkan implementasi keystore dengan lingkungan eksekusi yang terisolasi.
• [ 9.11 /H-0-3]* HARUS memiliki implementasi algoritme kriptografi RSA, AES, ECDSA, dan HMAC serta fungsi hash keluarga MD5, SHA1, dan SHA-2 untuk mendukung algoritme yang didukung sistem Android Keystore dengan benar di area yang diisolasi dengan aman dari kode yang berjalan pada kernel dan di atasnya. Isolasi aman HARUS memblokir semua mekanisme potensial yang memungkinkan kode kernel atau ruang pengguna mengakses keadaan internal lingkungan yang terisolasi, termasuk DMA. Proyek Sumber Terbuka Android (AOSP) upstream memenuhi persyaratan ini dengan menggunakan implementasi Trusty , namun solusi berbasis ARM TrustZone lainnya atau implementasi aman yang ditinjau oleh pihak ketiga dari isolasi berbasis hypervisor yang tepat adalah opsi alternatif.
• [ 9.11 /H-0-4]* HARUS melakukan otentikasi layar kunci di lingkungan eksekusi yang terisolasi dan hanya jika berhasil, izinkan penggunaan kunci terikat otentikasi. Kredensial layar kunci HARUS disimpan sedemikian rupa sehingga hanya lingkungan eksekusi terisolasi yang dapat melakukan otentikasi layar kunci. Proyek Sumber Terbuka Android hulu menyediakan Lapisan Abstraksi Perangkat Keras Gatekeeper (HAL) dan Trusty, yang dapat digunakan untuk memenuhi persyaratan ini.
• [ 9.11 /H-0-5]* HARUS mendukung pengesahan kunci di mana kunci penandatanganan pengesahan dilindungi oleh perangkat keras yang aman dan penandatanganan dilakukan di perangkat keras yang aman. Kunci penandatanganan pengesahan HARUS dibagikan ke sejumlah perangkat yang cukup besar untuk mencegah kunci digunakan sebagai pengidentifikasi perangkat. Salah satu cara untuk memenuhi persyaratan ini adalah dengan berbagi kunci pengesahan yang sama kecuali setidaknya 100.000 unit SKU tertentu diproduksi. Jika lebih dari 100.000 unit SKU diproduksi, kunci yang berbeda MUNGKIN digunakan untuk setiap 100.000 unit.

Perhatikan bahwa jika implementasi perangkat telah diluncurkan pada versi Android yang lebih lama, perangkat tersebut dikecualikan dari persyaratan untuk memiliki keystore yang didukung oleh lingkungan eksekusi terisolasi dan mendukung pengesahan kunci, kecuali perangkat tersebut mendeklarasikan fitur android.hardware.fingerprint yang mana memerlukan keystore yang didukung oleh lingkungan eksekusi yang terisolasi.

Ketika penerapan perangkat Genggam mendukung layar kunci yang aman, penerapannya:

• [ 9.11 /H-1-1] HARUS mengizinkan pengguna untuk memilih waktu tunggu tidur terpendek, yaitu waktu transisi dari keadaan tidak terkunci ke keadaan terkunci, yaitu 15 detik atau kurang.
• [ 9.11 /H-1-2] HARUS memberikan kemampuan kepada pengguna untuk menyembunyikan pemberitahuan dan menonaktifkan semua bentuk otentikasi kecuali untuk otentikasi utama yang dijelaskan dalam 9.11.1 Layar Kunci Aman . AOSP memenuhi persyaratan sebagai mode lockdown.

Jika implementasi perangkat Genggam mencakup beberapa pengguna dan tidak mendeklarasikan tanda fitur android.hardware.telephony , mereka:

• [ 9.5 /H-2-1] HARUS mendukung profil terbatas, sebuah fitur yang memungkinkan pemilik perangkat mengelola pengguna tambahan dan kemampuan mereka di perangkat. Dengan profil yang dibatasi, pemilik perangkat dapat dengan cepat mengatur lingkungan terpisah agar pengguna tambahan dapat bekerja, dengan kemampuan untuk mengelola pembatasan yang lebih terperinci pada aplikasi yang tersedia di lingkungan tersebut.

Jika penerapan perangkat Genggam menyertakan beberapa pengguna dan mendeklarasikan tanda fitur android.hardware.telephony , mereka:

• [ 9.5 /H-3-1] TIDAK HARUS mendukung profil yang dibatasi tetapi HARUS selaras dengan penerapan kontrol AOSP untuk mengaktifkan/menonaktifkan pengguna lain mengakses panggilan suara dan SMS.

2.2.6. Kompatibilitas Alat dan Opsi Pengembang

Implementasi perangkat genggam (* Tidak berlaku untuk Tablet):

• [ 6.1 /H-0-1]* HARUS mendukung perintah shell cmd testharness .

Implementasi perangkat genggam (* Tidak berlaku untuk Tablet):

• Sempurna
  • [ 6.1 /H-0-2]* HARUS mengekspos biner /system/bin/perfetto ke pengguna shell yang cmdlinenya sesuai dengan dokumentasi perfetto .
  • [ 6.1 /H-0-3]* Biner perfetto HARUS menerima konfigurasi protobuf sebagai masukan yang sesuai dengan skema yang ditentukan dalam dokumentasi perfetto .
  • [ 6.1 /H-0-4]* Biner perfetto HARUS menulis jejak protobuf sebagai keluaran yang sesuai dengan skema yang ditentukan dalam dokumentasi perfetto .
  • [ 6.1 /H-0-5]* HARUS menyediakan, melalui biner perfetto, setidaknya sumber data yang dijelaskan dalam dokumentasi perfetto .

2.3. Persyaratan Televisi

Perangkat Android Television mengacu pada implementasi perangkat Android yang merupakan antarmuka hiburan untuk menikmati media digital, film, game, aplikasi, dan/atau siaran langsung TV bagi pengguna yang duduk sekitar sepuluh kaki jauhnya (“pengguna bersandar” atau “pengguna setinggi 10 kaki antarmuka”).

Implementasi perangkat Android diklasifikasikan sebagai Televisi jika memenuhi seluruh kriteria berikut:

• Telah menyediakan mekanisme untuk mengontrol antarmuka pengguna yang dirender dari jarak jauh pada layar yang mungkin berjarak sepuluh kaki dari pengguna.
• Memiliki tampilan layar tertanam dengan panjang diagonal lebih besar dari 24 inci ATAU menyertakan port output video, seperti VGA, HDMI, DisplayPort, atau port nirkabel untuk tampilan.

Persyaratan tambahan di sisa bagian ini khusus untuk implementasi perangkat Android Television.

2.3.1. Perangkat keras

Implementasi perangkat televisi:

• [ 7.2 .2/T-0-1] HARUS mendukung D-pad .
• [ 7.2 .3/T-0-1] HARUS menyediakan fungsi Home dan Back.
• [ 7.2 .3/T-0-2] HARUS mengirimkan peristiwa normal dan tekan lama dari fungsi Kembali ( KEYCODE_BACK ) ke aplikasi latar depan.
• [ 7.2 .6.1/T-0-1] HARUS menyertakan dukungan untuk pengontrol game dan mendeklarasikan tanda fitur android.hardware.gamepad .
• [ 7.2 .7/T] HARUS menyediakan kendali jarak jauh tempat pengguna dapat mengakses navigasi non-sentuh dan input tombol navigasi inti .

Jika implementasi perangkat televisi menyertakan giroskop 3 sumbu, maka:

• [ 7.3 .4/T-1-1] HARUS dapat melaporkan kejadian hingga frekuensi minimal 100 Hz.
• [ 7.3 .4/T-1-2] HARUS mampu mengukur perubahan orientasi hingga 1000 derajat per detik.

Implementasi perangkat televisi:

• [ 7.4 .3/T-0-1] HARUS mendukung Bluetooth dan Bluetooth LE.
• [ 7.6 .1/T-0-1] HARUS memiliki setidaknya 4 GB penyimpanan non-volatil yang tersedia untuk data pribadi aplikasi (alias partisi "/data").

Jika implementasi perangkat televisi menyertakan port USB yang mendukung mode host, maka:

• [ 7.5 .3/T-1-1] HARUS menyertakan dukungan untuk kamera eksternal yang terhubung melalui port USB ini tetapi tidak selalu terhubung.

Jika implementasi perangkat TV 32-bit:

• [ 7.6 .1/T-1-1] Memori yang tersedia untuk kernel dan ruang pengguna HARUS minimal 896MB jika salah satu dari kepadatan berikut digunakan:

  • 400dpi atau lebih tinggi pada layar kecil/normal
  • xhdpi atau lebih tinggi pada layar besar
  • tvdpi atau lebih tinggi pada layar ekstra besar

Jika implementasi perangkat TV 64-bit:

• [ 7.6 .1/T-2-1] Memori yang tersedia untuk kernel dan ruang pengguna HARUS minimal 1280MB jika salah satu dari kepadatan berikut digunakan:

  • 400dpi atau lebih tinggi pada layar kecil/normal
  • xhdpi atau lebih tinggi pada layar besar
  • tvdpi atau lebih tinggi pada layar ekstra besar

Perhatikan bahwa "memori yang tersedia untuk kernel dan ruang pengguna" di atas mengacu pada ruang memori yang disediakan selain memori apa pun yang telah didedikasikan untuk komponen perangkat keras seperti radio, video, dan sebagainya yang tidak berada di bawah kendali kernel pada implementasi perangkat.

Implementasi perangkat televisi:

• [ 7.8 .1/T] HARUS menyertakan mikrofon.
• [ 7.8 .2/T-0-1] HARUS memiliki output audio dan mendeklarasikan android.hardware.audio.output .

2.3.2. Multimedia

Implementasi perangkat televisi HARUS mendukung format pengkodean dan penguraian audio berikut dan membuatnya tersedia untuk aplikasi pihak ketiga:

• [ 5.1 /T-0-1] Profil AAC MPEG-4 (AAC LC)
• [ 5.1 /T-0-2] Profil AAC MPEG-4 HE (AAC+)
• [ 5.1 /T-0-3] AAC ELD (AAC penundaan rendah yang ditingkatkan)

Implementasi perangkat televisi HARUS mendukung format pengkodean video berikut dan membuatnya tersedia untuk aplikasi pihak ketiga:

• [ 5.2 /T-0-1] H.264
• [ 5.2 /T-0-2] VP8

Implementasi perangkat televisi:

• [ 5.2 .2/T-SR] SANGAT DIREKOMENDASIKAN untuk mendukung pengkodean H.264 pada video resolusi 720p dan 1080p pada 30 frame per detik.

Implementasi perangkat televisi HARUS mendukung format decoding video berikut dan membuatnya tersedia untuk aplikasi pihak ketiga:

• [ 5.3.3 /T-0-1] MPEG-4 SP
• [ 5.3.4 /T-0-2] H.264 AVC
• [ 5.3.5 /T-0-3] H.265 HEVC
• [ 5.3.6 /T-0-4] VP8
• [ 5.3.7 /T-0-5] Wakil Presiden9
• [ 5.3.1 /T-0-6] MPEG-2

Implementasi perangkat televisi HARUS mendukung decoding MPEG-2, sebagaimana dijelaskan secara rinci dalam Bagian 5.3.1, pada frame rate dan resolusi video standar hingga dan termasuk:

• [ 5.3.1 /T-1-1] HD 1080p pada 29,97 frame per detik dengan Profil Utama Tingkat Tinggi.
• [ 5.3.1 /T-1-2] HD 1080i pada 59,94 frame per detik dengan Profil Utama Tingkat Tinggi. Mereka HARUS memisahkan video MPEG-2 yang saling bertautan dan membuatnya tersedia untuk aplikasi pihak ketiga.

Implementasi perangkat televisi HARUS mendukung decoding H.264, sebagaimana dirinci dalam Bagian 5.3.4, pada frame rate dan resolusi video standar hingga dan termasuk:

• [ 5.3.4 /T-1-1] HD 1080p pada 60 frame per detik dengan Profil Dasar
• [ 5.3.4 /T-1-2] HD 1080p pada 60 frame per detik dengan Profil Utama
• [ 5.3.4 /T-1-3] HD 1080p pada 60 frame per detik dengan Profil Tinggi Level 4.2

Implementasi perangkat televisi dengan decoder perangkat keras H.265 HARUS mendukung decoding H.265, sebagaimana dirinci dalam Bagian 5.3.5, pada kecepatan dan resolusi frame video standar hingga dan termasuk:

• [ 5.3.5 /T-1-1] HD 1080p pada 60 frame per detik dengan Profil Utama Level 4.1

Jika implementasi perangkat televisi dengan decoder perangkat keras H.265 mendukung decoding H.265 dan profil decoding UHD, maka:

• [ 5.3.5 /T-2-1] HARUS mendukung profil decoding UHD pada 60 frame per detik dengan profil Tingkat Utama Main10 Level 5.

Implementasi perangkat televisi HARUS mendukung decoding VP8, sebagaimana dirinci dalam Bagian 5.3.6, pada frame rate dan resolusi video standar hingga dan termasuk:

• [ 5.3.6 /T-1-1] HD 1080p pada profil decoding 60 frame per detik

Implementasi perangkat televisi dengan decoder perangkat keras VP9 HARUS mendukung decoding VP9, ​​sebagaimana dirinci dalam Bagian 5.3.7, pada kecepatan dan resolusi frame video standar hingga dan termasuk:

• [ 5.3.7 /T-1-1] HD 1080p pada 60 frame per detik dengan profil 0 (kedalaman warna 8 bit)

Jika implementasi perangkat Televisi dengan decoder perangkat keras VP9 mendukung decoding VP9 dan profil decoding UHD, maka:

• [ 5.3.7 /T-2-1] HARUS mendukung profil decoding UHD pada 60 frame per detik dengan profil 0 (kedalaman warna 8 bit).
• [ 5.3.7 /T-2-1] SANGAT DIANJURKAN untuk mendukung profil decoding UHD pada 60 frame per detik dengan profil 2 (kedalaman warna 10 bit).

Implementasi perangkat televisi:

• [ 5.5 /T-0-1] HARUS menyertakan dukungan untuk Volume Master sistem dan redaman volume output audio digital pada output yang didukung, kecuali untuk output passthrough audio terkompresi (di mana tidak ada decoding audio yang dilakukan pada perangkat).

Jika implementasi perangkat Televisi tidak memiliki layar internal, namun mendukung layar eksternal yang tersambung melalui HDMI, perangkat tersebut:

• [ 5.8 /T-0-1] HARUS mengatur mode output HDMI untuk memilih resolusi maksimum yang dapat didukung dengan kecepatan refresh 50Hz atau 60Hz.
• [ 5.8 /T-SR] SANGAT DIREKOMENDASIKAN untuk menyediakan pemilih kecepatan refresh HDMI yang dapat dikonfigurasi pengguna.
• [ 5.8 ] HARUS mengatur kecepatan refresh mode output HDMI ke 50Hz atau 60Hz, tergantung pada kecepatan refresh video untuk wilayah tempat perangkat dijual.

Jika implementasi perangkat Televisi tidak memiliki layar internal, namun mendukung layar eksternal yang tersambung melalui HDMI, perangkat tersebut:

• [ 5.8 /T-1-1] HARUS mendukung HDCP 2.2.

Jika implementasi perangkat Televisi tidak mendukung decoding UHD, namun mendukung layar eksternal yang terhubung melalui HDMI, maka:

• [ 5.8 /T-2-1] HARUS mendukung HDCP 1.4

2.3.3. Perangkat lunak

Implementasi perangkat televisi:

• [ 3 /T-0-1] HARUS mendeklarasikan fitur android.software.leanback dan android.hardware.type.television .
• [ 3.4 .1/T-0-1] HARUS menyediakan implementasi lengkap dari android.webkit.Webview API.

Jika penerapan perangkat Android Television mendukung layar kunci, mereka:

• [ 3.8 .10/T-1-1] HARUS menampilkan Notifikasi Layar Kunci termasuk Templat Notifikasi Media.

Implementasi perangkat televisi:

• [ 3.8 .14/T-SR] SANGAT DIANJURKAN untuk mendukung mode gambar-dalam-gambar (PIP) multi-jendela.
• [ 3.10 /T-0-1] HARUS mendukung layanan aksesibilitas pihak ketiga.
• [ 3.10 /T-SR] SANGAT DIREKOMENDASIKAN untuk melakukan pramuat layanan aksesibilitas pada perangkat yang sebanding dengan atau melampaui fungsi layanan aksesibilitas Tombol Akses dan TalkBack (untuk bahasa yang didukung oleh mesin Text-to-speech yang sudah diinstal sebelumnya) sebagaimana disediakan dalam talkback terbuka proyek sumber .

Jika implementasi perangkat Televisi melaporkan fitur android.hardware.audio.output , mereka:

• [ 3.11 /T-SR] SANGAT DIREKOMENDASIKAN untuk menyertakan mesin TTS yang mendukung bahasa yang tersedia di perangkat.
• [ 3.11 /T-1-1] HARUS mendukung pemasangan mesin TTS pihak ketiga.

Implementasi perangkat televisi:

• [ 3.12 /T-0-1] HARUS mendukung Kerangka Input TV.

2.3.4. Kinerja dan Kekuatan

• [ 8.1 /T-0-1] Latensi bingkai yang konsisten . Latensi frame yang tidak konsisten atau penundaan dalam merender frame TIDAK BOLEH terjadi lebih dari 5 frame dalam satu detik, dan HARUS di bawah 1 frame dalam satu detik.
• [ 8.2 /T-0-1] HARUS memastikan kinerja penulisan berurutan minimal 5MB/s.
• [ 8.2 /T-0-2] HARUS memastikan kinerja penulisan acak minimal 0,5MB/s.
• [ 8.2 /T-0-3] HARUS memastikan kinerja pembacaan berurutan minimal 15MB/s.
• [ 8.2 /T-0-4] HARUS memastikan kinerja pembacaan acak minimal 3,5MB/s.

Jika implementasi perangkat Televisi menyertakan fitur untuk meningkatkan manajemen daya perangkat yang disertakan dalam AOSP atau memperluas fitur yang disertakan dalam AOSP, maka implementasi tersebut:

• [ 8.3 /T-1-1] HARUS memberikan kemampuan pengguna untuk mengaktifkan dan menonaktifkan fitur penghemat baterai.

Jika implementasi perangkat televisi tidak memiliki baterai, maka:

• [ 8.3 /T-1-2] HARUS mendaftarkan perangkat sebagai perangkat tanpa baterai seperti yang dijelaskan dalam Mendukung Perangkat Tanpa Baterai .

Jika implementasi perangkat televisi memiliki baterai, maka:

• [ 8.3 /T-1-3] HARUS memberikan keterjangkauan pengguna untuk menampilkan semua aplikasi yang dikecualikan dari mode hemat daya Aplikasi Siaga dan Istirahatkan.

Implementasi perangkat televisi:

• [ 8.4 /T-0-1] HARUS menyediakan profil daya per komponen yang menentukan nilai konsumsi saat ini untuk setiap komponen perangkat keras dan perkiraan pengurasan baterai yang disebabkan oleh komponen dari waktu ke waktu seperti yang didokumentasikan di situs Proyek Sumber Terbuka Android.
• [ 8.4 /T-0-2] HARUS melaporkan semua nilai konsumsi daya dalam miliampere jam (mAh).
• [ 8.4 /T-0-3] HARUS melaporkan konsumsi daya CPU per UID setiap proses. Proyek Sumber Terbuka Android memenuhi persyaratan melalui implementasi modul kernel uid_cputime .
• [ 8.4 /T] HARUS dikaitkan dengan komponen perangkat keras itu sendiri jika tidak dapat mengaitkan penggunaan daya komponen perangkat keras ke suatu aplikasi.
• [ 8.4 /T-0-4] HARUS membuat penggunaan daya ini tersedia melalui perintah adb shell dumpsys batterystats shell kepada pengembang aplikasi.

2.3.5. Model Keamanan

Implementasi perangkat televisi:

• [ 9.11 /T-0-1] HARUS mencadangkan implementasi keystore dengan lingkungan eksekusi yang terisolasi.
• [ 9.11 /T-0-2] HARUS memiliki implementasi algoritme kriptografi RSA, AES, ECDSA, dan HMAC serta fungsi hash keluarga MD5, SHA1, dan SHA-2 untuk mendukung algoritme yang didukung sistem Android Keystore dengan benar di area yang terisolasi dengan aman dari kode yang berjalan di kernel ke atas. Isolasi aman HARUS memblokir semua mekanisme potensial yang memungkinkan kode kernel atau ruang pengguna mengakses keadaan internal lingkungan yang terisolasi, termasuk DMA. Proyek Sumber Terbuka Android (AOSP) upstream memenuhi persyaratan ini dengan menggunakan implementasi Trusty , namun solusi berbasis ARM TrustZone lainnya atau implementasi aman yang ditinjau oleh pihak ketiga dari isolasi berbasis hypervisor yang tepat adalah opsi alternatif.
• [ 9.11 /T-0-3] HARUS melakukan otentikasi layar kunci di lingkungan eksekusi yang terisolasi dan hanya jika berhasil, izinkan penggunaan kunci terikat otentikasi. Kredensial layar kunci HARUS disimpan sedemikian rupa sehingga hanya lingkungan eksekusi terisolasi yang dapat melakukan otentikasi layar kunci. Proyek Sumber Terbuka Android hulu menyediakan Lapisan Abstraksi Perangkat Keras Gatekeeper (HAL) dan Trusty, yang dapat digunakan untuk memenuhi persyaratan ini.
• [ 9.11 /T-0-4] HARUS mendukung pengesahan kunci di mana kunci penandatanganan pengesahan dilindungi oleh perangkat keras yang aman dan penandatanganan dilakukan di perangkat keras yang aman. Kunci penandatanganan pengesahan HARUS dibagikan ke sejumlah perangkat yang cukup besar untuk mencegah kunci digunakan sebagai pengidentifikasi perangkat. Salah satu cara untuk memenuhi persyaratan ini adalah dengan berbagi kunci pengesahan yang sama kecuali setidaknya 100.000 unit SKU tertentu diproduksi. Jika lebih dari 100.000 unit SKU diproduksi, kunci yang berbeda MUNGKIN digunakan untuk setiap 100.000 unit.

Perhatikan bahwa jika implementasi perangkat telah diluncurkan pada versi Android yang lebih lama, perangkat tersebut dikecualikan dari persyaratan untuk memiliki keystore yang didukung oleh lingkungan eksekusi terisolasi dan mendukung pengesahan kunci, kecuali perangkat tersebut mendeklarasikan fitur android.hardware.fingerprint yang mana memerlukan keystore yang didukung oleh lingkungan eksekusi yang terisolasi.

Jika penerapan perangkat televisi mendukung layar kunci yang aman, penerapan tersebut:

• [ 9.11 /T-1-1] HARUS mengizinkan pengguna memilih batas waktu Tidur untuk transisi dari keadaan tidak terkunci ke keadaan terkunci, dengan batas waktu minimum yang diperbolehkan hingga 15 detik atau kurang.

Jika penerapan perangkat Televisi menyertakan banyak pengguna dan tidak mendeklarasikan tanda fitur android.hardware.telephony , mereka:

• [ 9.5 /T-2-1] HARUS mendukung profil terbatas, sebuah fitur yang memungkinkan pemilik perangkat mengelola pengguna tambahan dan kemampuan mereka di perangkat. Dengan profil yang dibatasi, pemilik perangkat dapat dengan cepat mengatur lingkungan terpisah agar pengguna tambahan dapat bekerja, dengan kemampuan untuk mengelola pembatasan yang lebih terperinci pada aplikasi yang tersedia di lingkungan tersebut.

Jika penerapan perangkat Televisi menyertakan beberapa pengguna dan mendeklarasikan tanda fitur android.hardware.telephony , mereka:

• [ 9.5 /T-3-1] TIDAK HARUS mendukung profil yang dibatasi tetapi HARUS selaras dengan penerapan kontrol AOSP untuk mengaktifkan/menonaktifkan pengguna lain mengakses panggilan suara dan SMS.

2.3.6. Kompatibilitas Alat dan Opsi Pengembang

Implementasi perangkat televisi:

• Sempurna
  • [ 6.1 /T-0-1] HARUS mengekspos biner /system/bin/perfetto ke pengguna shell yang cmdlinenya sesuai dengan dokumentasi perfetto .
  • [ 6.1 /T-0-2] Biner perfetto HARUS menerima konfigurasi protobuf sebagai masukan yang sesuai dengan skema yang ditentukan dalam dokumentasi perfetto .
  • [ 6.1 /T-0-3] Biner perfetto HARUS menulis sebagai keluaran jejak protobuf yang sesuai dengan skema yang ditentukan dalam dokumentasi perfetto .
  • [ 6.1 /T-0-4] HARUS menyediakan, melalui biner perfetto, setidaknya sumber data yang dijelaskan dalam dokumentasi perfetto .

2.4. Persyaratan Tontonan

Perangkat Android Watch mengacu pada implementasi perangkat Android yang dimaksudkan untuk dikenakan di tubuh, mungkin di pergelangan tangan.

Implementasi perangkat Android diklasifikasikan sebagai Jam tangan jika memenuhi seluruh kriteria berikut:

• Memiliki layar dengan panjang diagonal fisik berkisar antara 1,1 hingga 2,5 inci.
• Memiliki mekanisme yang disediakan untuk dikenakan pada tubuh.

Persyaratan tambahan di sisa bagian ini khusus untuk penerapan perangkat Android Watch.

2.4.1. Perangkat keras

Tonton implementasi perangkat:

• [ 7.1 .1.1/W-0-1] HARUS memiliki layar dengan ukuran diagonal fisik dalam kisaran 1,1 hingga 2,5 inci.

• [ 7.2 .3/W-0-1] HARUS memiliki fungsi Beranda yang tersedia untuk pengguna, dan fungsi Kembali kecuali jika berada di UI_MODE_TYPE_WATCH .

• [ 7.2 .4/W-0-1] HARUS mendukung input layar sentuh.

• [ 7.3 .1/W-SR] SANGAT DIREKOMENDASIKAN untuk menyertakan akselerometer 3 sumbu.

Jika implementasi perangkat Watch menyertakan penerima GPS/GNSS dan melaporkan kemampuan tersebut ke aplikasi melalui tanda fitur android.hardware.location.gps , maka implementasi tersebut:

• [ 7.3 .3/W-1-1] HARUS melaporkan pengukuran GNSS, segera setelah ditemukan, meskipun lokasi yang dihitung dari GPS/GNSS belum dilaporkan.
• [ 7.3 .3/W-1-2] HARUS melaporkan kecepatan pseudorange dan pseudorange GNSS, yang, dalam kondisi langit terbuka setelah menentukan lokasi, saat diam atau bergerak dengan percepatan kurang dari 0,2 meter per detik kuadrat, cukup untuk menghitung posisi dalam jarak 20 meter, dan kecepatan dalam 0,2 meter per detik, setidaknya 95% dari waktu.

Jika implementasi perangkat Watch menyertakan giroskop 3 sumbu, maka:

• [ 7.3 .4/W-2-1] HARUS mampu mengukur perubahan orientasi hingga 1000 derajat per detik.

Tonton implementasi perangkat:

• [ 7.4 .3/W-0-1] HARUS mendukung Bluetooth.

• [ 7.6 .1/W-0-1] HARUS memiliki setidaknya 1 GB penyimpanan non-volatil yang tersedia untuk data pribadi aplikasi (alias partisi "/data").

• [ 7.6 .1/W-0-2] HARUS memiliki setidaknya 416 MB memori yang tersedia untuk kernel dan ruang pengguna.

• [ 7.8 .1/W-0-1] HARUS menyertakan mikrofon.

• [ 7.8 .2/W] MUNGKIN tetapi TIDAK HARUS memiliki output audio.

2.4.2. Multimedia

Tidak ada persyaratan tambahan.

2.4.3. Perangkat lunak

Tonton implementasi perangkat:

• [ 3 /W-0-1] HARUS mendeklarasikan fitur android.hardware.type.watch .
• [ 3 /W-0-2] HARUS mendukung uiMode = UI_MODE_TYPE_WATCH .

Tonton implementasi perangkat:

• [ 3.8 .4/W-SR] SANGAT DIREKOMENDASIKAN untuk mengimplementasikan asisten pada perangkat untuk menangani tindakan Assist .

Perhatikan implementasi perangkat yang mendeklarasikan flag fitur android.hardware.audio.output :

• [ 3.10 /W-1-1] HARUS mendukung layanan aksesibilitas pihak ketiga.

• [ 3.10 /W-SR] SANGAT DIREKOMENDASIKAN untuk melakukan pramuat layanan aksesibilitas pada perangkat yang sebanding dengan atau melebihi fungsi layanan aksesibilitas Tombol Akses dan TalkBack (untuk bahasa yang didukung oleh mesin Text-to-speech yang sudah diinstal sebelumnya) sebagaimana disediakan dalam talkback terbuka proyek sumber .

• [ 3.11 /W-SR] SANGAT DIANJURKAN untuk menyertakan mesin TTS yang mendukung bahasa yang tersedia di perangkat.

• [ 3.11 /W-0-1] HARUS mendukung pemasangan mesin TTS pihak ketiga.

2.4.4. Kinerja dan Kekuatan

Jika implementasi perangkat Watch menyertakan fitur untuk meningkatkan manajemen daya perangkat yang disertakan dalam AOSP atau memperluas fitur yang disertakan dalam AOSP, maka implementasi tersebut:

• [ 8.3 /W-SR] SANGAT DIREKOMENDASIKAN untuk memberikan keterjangkauan bagi pengguna untuk menampilkan semua aplikasi yang dikecualikan dari mode hemat daya Aplikasi Siaga dan Istirahatkan.
• [ 8.3 /W-SR] SANGAT DIREKOMENDASIKAN untuk memberikan keterjangkauan pengguna untuk mengaktifkan dan menonaktifkan fitur penghemat baterai.

Tonton implementasi perangkat:

• [ 8.4 /W-0-1] HARUS menyediakan profil daya per komponen yang menentukan nilai konsumsi saat ini untuk setiap komponen perangkat keras dan perkiraan pengurasan baterai yang disebabkan oleh komponen dari waktu ke waktu seperti yang didokumentasikan di situs Proyek Sumber Terbuka Android.
• [ 8.4 /W-0-2] HARUS melaporkan semua nilai konsumsi daya dalam miliampere jam (mAh).
• [ 8.4 /W-0-3] HARUS melaporkan konsumsi daya CPU per UID setiap proses. Proyek Sumber Terbuka Android memenuhi persyaratan melalui implementasi modul kernel uid_cputime .
• [ 8.4 /W-0-4] HARUS membuat penggunaan daya ini tersedia melalui perintah adb shell dumpsys batterystats shell kepada pengembang aplikasi.
• [ 8.4 /W] HARUS dikaitkan dengan komponen perangkat keras itu sendiri jika tidak dapat mengaitkan penggunaan daya komponen perangkat keras ke suatu aplikasi.

2.4.5. Model Keamanan

Jika implementasi perangkat Watch menyertakan beberapa pengguna dan tidak mendeklarasikan tanda fitur android.hardware.telephony , mereka:

• [ 9.5 /W-1-1] HARUS mendukung profil terbatas, sebuah fitur yang memungkinkan pemilik perangkat mengelola pengguna tambahan dan kemampuan mereka di perangkat. Dengan profil yang dibatasi, pemilik perangkat dapat dengan cepat mengatur lingkungan terpisah agar pengguna tambahan dapat bekerja, dengan kemampuan untuk mengelola pembatasan yang lebih terperinci pada aplikasi yang tersedia di lingkungan tersebut.

Jika implementasi perangkat Watch menyertakan beberapa pengguna dan mendeklarasikan tanda fitur android.hardware.telephony , mereka:

• [ 9.5 /W-2-1] TIDAK HARUS mendukung profil yang dibatasi tetapi HARUS selaras dengan penerapan kontrol AOSP untuk mengaktifkan/menonaktifkan pengguna lain mengakses panggilan suara dan SMS.

2.5. Persyaratan Otomotif

Implementasi Android Automotive mengacu pada head unit kendaraan yang menjalankan Android sebagai sistem operasi untuk sebagian atau seluruh fungsi sistem dan/atau infotainment.

Implementasi perangkat Android diklasifikasikan sebagai Otomotif jika mendeklarasikan fitur android.hardware.type.automotive atau memenuhi semua kriteria berikut.

• Tertanam sebagai bagian dari, atau dapat dipasang ke, kendaraan otomotif.
• Sedang menggunakan layar di baris kursi pengemudi sebagai tampilan utama.

Persyaratan tambahan di sisa bagian ini khusus untuk implementasi perangkat Android Automotive.

2.5.1. Perangkat keras

Implementasi perangkat otomotif:

• [ 7.1 .1.1/A-0-1] HARUS memiliki layar minimal 6 inci dalam ukuran diagonal fisik.

• [ 7.1 .1.1/A-0-2] HARUS memiliki tata letak ukuran layar minimal 750 dp x 480 dp.

• [ 7.2 .3/A-0-1] HARUS menyediakan fungsi Beranda dan MUNGKIN menyediakan fungsi Kembali dan Terbaru.

• [ 7.2 .3/A-0-2] HARUS mengirimkan peristiwa normal dan tekan lama dari fungsi Kembali ( KEYCODE_BACK ) ke aplikasi latar depan.
• [ 7.3 /A-0-1] HARUS menerapkan dan melaporkan GEAR_SELECTION , NIGHT_MODE , PERF_VEHICLE_SPEED dan PARKING_BRAKE_ON .
• [ 7.3 /A-0-2] Nilai tanda NIGHT_MODE HARUS konsisten dengan mode siang/malam dasbor dan HARUS didasarkan pada input sensor cahaya sekitar. Sensor cahaya sekitar yang mendasarinya MUNGKIN sama dengan Fotometer .
• [ 7.3 /A-0-3] HARUS menyediakan bidang info tambahan sensor TYPE_SENSOR_PLACEMENT sebagai bagian dari SensorAdditionalInfo untuk setiap sensor yang disediakan.
• [ 7.3 /A-0-1] MUNGKIN memperhitungkan Lokasi dengan menggabungkan GPS/GNSS dengan sensor tambahan. Jika Lokasi dianggap mati, SANGAT DISARANKAN untuk menerapkan dan melaporkan jenis Sensor dan/atau ID Properti Kendaraan yang digunakan.
• [ 7.3 /A-0-2] Lokasi yang diminta melalui LocationManager#requestLocationUpdates() TIDAK HARUS cocok dengan peta.

Jika implementasi perangkat Otomotif menyertakan akselerometer 3 sumbu, maka:

• [ 7.3 .1/A-1-1] HARUS dapat melaporkan kejadian hingga frekuensi minimal 100 Hz.
• [ 7.3 .1/A-1-2] HARUS mematuhi sistem koordinat sensor mobil Android.

Jika implementasi perangkat Otomotif menyertakan giroskop 3 sumbu, maka:

• [ 7.3 .4/A-2-1] HARUS dapat melaporkan kejadian hingga frekuensi minimal 100 Hz.
• [ 7.3 .4/A-2-2] HARUS juga mengimplementasikan sensor TYPE_GYROSCOPE_UNCALIBRATED .
• [ 7.3 .4/A-2-3] HARUS mampu mengukur perubahan orientasi hingga 250 derajat per detik.
• [ 7.3 .4/A-SR] SANGAT DIREKOMENDASIKAN untuk mengonfigurasi rentang pengukuran giroskop ke +/-250dps untuk memaksimalkan resolusi yang mungkin

Implementasi perangkat otomotif:

• [ 7.4 .3/A-0-1] HARUS mendukung Bluetooth dan HARUS mendukung Bluetooth LE.

• [ 7.4 .3/A-0-2] Implementasi Android Automotive HARUS mendukung profil Bluetooth berikut:

  • Panggilan telepon melalui Profil Bebas Genggam (HFP).
  • Pemutaran media melalui Profil Distribusi Audio (A2DP).
  • Kontrol pemutaran media melalui Profil Remote Control (AVRCP).
  • Berbagi kontak menggunakan Profil Akses Buku Telepon (PBAP).

• [ 7.4 .3/A-SR] SANGAT DIANJURKAN untuk mendukung Profil Akses Pesan (MAP).

• [ 7.4 .5/A] HARUS menyertakan dukungan untuk konektivitas data berbasis jaringan seluler.

• [ 7.4 .5/A] MUNGKIN menggunakan konstanta System API NetworkCapabilities#NET_CAPABILITY_OEM_PAID untuk jaringan yang tersedia untuk aplikasi sistem.

Kamera tampilan eksterior adalah kamera yang memotret pemandangan di luar implementasi perangkat, seperti kamera dasbor.

Implementasi perangkat otomotif:

• HARUS menyertakan satu atau lebih kamera tampak luar.

Jika implementasi perangkat Otomotif menyertakan kamera tampilan eksterior, untuk kamera tersebut, mereka:

• [ 7.5 /A-1-1] TIDAK HARUS memiliki kamera tampak luar yang dapat diakses melalui API Kamera Android , kecuali kamera tersebut mematuhi persyaratan inti kamera.
• [ 7.5 /A-SR] SANGAT DIREKOMENDASIKAN untuk tidak memutar atau mencerminkan pratinjau kamera secara horizontal.
• [ 7.5 .5/A-SR] SANGAT DIREKOMENDASIKAN untuk diorientasikan sehingga dimensi panjang kamera sejajar dengan cakrawala.
• [ 7.5 /A-SR] SANGAT DIANJURKAN untuk memiliki resolusi minimal 1,3 megapiksel.
• HARUS memiliki perangkat keras fokus tetap atau EDOF (kedalaman bidang yang diperluas).
• MUNGKIN memiliki fokus otomatis perangkat keras atau fokus otomatis perangkat lunak yang diterapkan pada driver kamera.

Implementasi perangkat otomotif:

• [ 7.6 .1/A-0-1] HARUS memiliki setidaknya 4 GB penyimpanan non-volatil yang tersedia untuk data pribadi aplikasi (alias partisi "/data").

• [ 7.6 .1/A] HARUS memformat partisi data untuk menawarkan peningkatan kinerja dan umur panjang pada penyimpanan flash, misalnya menggunakan sistem file f2fs .

Jika implementasi perangkat Otomotif menyediakan penyimpanan eksternal bersama melalui sebagian penyimpanan internal yang tidak dapat dilepas, maka implementasi tersebut:

• [ 7.6 .1/A-SR] SANGAT DIREKOMENDASIKAN untuk mengurangi overhead I/O pada operasi yang dilakukan pada penyimpanan eksternal, misalnya dengan menggunakan SDCardFS .

Jika implementasi perangkat Otomotif adalah 32-bit:

• [ 7.6 .1/A-1-1] Memori yang tersedia untuk kernel dan ruang pengguna HARUS minimal 512MB jika salah satu dari kepadatan berikut digunakan:

  • 280dpi atau lebih rendah pada layar kecil/normal
  • ldpi atau lebih rendah pada layar ekstra besar
  • mdpi atau lebih rendah pada layar besar

• [ 7.6 .1/A-1-2] Memori yang tersedia untuk kernel dan ruang pengguna HARUS minimal 608MB jika salah satu dari kepadatan berikut digunakan:

  • xhdpi atau lebih tinggi pada layar kecil/normal
  • hdpi atau lebih tinggi pada layar besar
  • mdpi atau lebih tinggi pada layar ekstra besar

• [ 7.6 .1/A-1-3] Memori yang tersedia untuk kernel dan ruang pengguna HARUS minimal 896MB jika salah satu dari kepadatan berikut digunakan:

  • 400dpi atau lebih tinggi pada layar kecil/normal
  • xhdpi atau lebih tinggi pada layar besar
  • tvdpi atau lebih tinggi pada layar ekstra besar

• [ 7.6 .1/A-1-4] Memori yang tersedia untuk kernel dan ruang pengguna HARUS minimal 1344MB jika salah satu dari kepadatan berikut digunakan:

  • 560dpi atau lebih tinggi pada layar kecil/normal
  • 400dpi atau lebih tinggi pada layar besar
  • xhdpi atau lebih tinggi pada layar ekstra besar

Jika implementasi perangkat Otomotif adalah 64-bit:

• [ 7.6 .1/A-2-1] Memori yang tersedia untuk kernel dan ruang pengguna HARUS minimal 816MB jika salah satu dari kepadatan berikut digunakan:

  • 280dpi atau lebih rendah pada layar kecil/normal
  • ldpi atau lebih rendah pada layar ekstra besar
  • mdpi atau lebih rendah pada layar besar

• [ 7.6 .1/A-2-2] Memori yang tersedia untuk kernel dan ruang pengguna HARUS minimal 944MB jika salah satu dari kepadatan berikut digunakan:

  • xhdpi atau lebih tinggi pada layar kecil/normal
  • hdpi atau lebih tinggi pada layar besar
  • mdpi atau lebih tinggi pada layar ekstra besar

• [ 7.6 .1/A-2-3] Memori yang tersedia untuk kernel dan ruang pengguna HARUS minimal 1280MB jika salah satu dari kepadatan berikut digunakan:

  • 400dpi atau lebih tinggi pada layar kecil/normal
  • xhdpi atau lebih tinggi pada layar besar
  • tvdpi atau lebih tinggi pada layar ekstra besar

• [ 7.6 .1/A-2-4] Memori yang tersedia untuk kernel dan ruang pengguna HARUS minimal 1824MB jika salah satu dari kepadatan berikut digunakan:

  • 560dpi atau lebih tinggi pada layar kecil/normal
  • 400dpi atau lebih tinggi pada layar besar
  • xhdpi atau lebih tinggi pada layar ekstra besar

Perhatikan bahwa "memori yang tersedia untuk kernel dan ruang pengguna" di atas mengacu pada ruang memori yang disediakan selain memori apa pun yang telah didedikasikan untuk komponen perangkat keras seperti radio, video, dan sebagainya yang tidak berada di bawah kendali kernel pada implementasi perangkat.

Implementasi perangkat otomotif:

• [ 7.7 .1/A] HARUS menyertakan port USB yang mendukung mode periferal.

Implementasi perangkat otomotif:

• [ 7.8 .1/A-0-1] HARUS menyertakan mikrofon.

Implementasi perangkat otomotif:

• [ 7.8 .2/A-0-1] HARUS memiliki output audio dan mendeklarasikan android.hardware.audio.output .

2.5.2. Multimedia

Implementasi perangkat otomotif HARUS mendukung format pengkodean dan penguraian audio berikut dan membuatnya tersedia untuk aplikasi pihak ketiga:

• [ 5.1 /A-0-1] Profil AAC MPEG-4 (AAC LC)
• [ 5.1 /A-0-2] Profil AAC MPEG-4 HE (AAC+)
• [ 5.1 /A-0-3] AAC ELD (AAC penundaan rendah yang ditingkatkan)

Implementasi perangkat otomotif HARUS mendukung format pengkodean video berikut dan membuatnya tersedia untuk aplikasi pihak ketiga:

• [ 5.2 /A-0-1] H.264 AVC
• [ 5.2 /A-0-2] VP8

Implementasi perangkat otomotif HARUS mendukung format decoding video berikut dan membuatnya tersedia untuk aplikasi pihak ketiga:

• [ 5.3 /A-0-1] H.264 AVC
• [ 5.3 /A-0-2] MPEG-4 SP
• [ 5.3 /A-0-3] VP8
• [ 5.3 /A-0-4] Wakil Presiden9

Implementasi perangkat otomotif SANGAT DIANJURKAN untuk mendukung decoding video berikut:

• [ 5.3 /A-SR] H.265 HEVC

2.5.3. Perangkat lunak

Implementasi perangkat otomotif:

• [ 3 /A-0-1] HARUS mendeklarasikan fitur android.hardware.type.automotive .

• [ 3 /A-0-2] HARUS mendukung uiMode = UI_MODE_TYPE_CAR .

• [ 3 /A-0-3] HARUS mendukung semua API publik di namespace android.car.* .

• [ 3.2 .1/A-0-1] HARUS mendukung dan menegakkan semua konstanta izin sebagaimana didokumentasikan oleh halaman referensi Izin Otomotif .

• [ 3.4 .1/A-0-1] HARUS menyediakan implementasi lengkap dari android.webkit.Webview API.

• [ 3.8 .3/A-0-1] HARUS menampilkan notifikasi yang menggunakan API Notification.CarExtender ketika diminta oleh aplikasi pihak ketiga.

• [ 3.8 .4/A-SR] SANGAT DIREKOMENDASIKAN untuk mengimplementasikan asisten pada perangkat untuk menangani tindakan Assist .

Jika implementasi perangkat Otomotif menyertakan tombol push-to-talk, maka:

• [ 3.8 .4/A-1-1] HARUS menekan sebentar tombol push-to-talk sebagai interaksi yang ditentukan untuk meluncurkan aplikasi bantuan yang dipilih pengguna, dengan kata lain aplikasi yang mengimplementasikan VoiceInteractionService .

Implementasi perangkat otomotif:

• [ 3.8.3.1 /A-0-1] HARUS merender sumber daya dengan benar seperti yang dijelaskan dalam dokumentasi Notifications on Automotive OS .
• [ 3.8.3.1 /A-0-2] HARUS menampilkan PLAY dan MUTE untuk tindakan notifikasi menggantikan yang disediakan melalui Notification.Builder.addAction()
• [ 3.8.3.1 /A] HARUS membatasi penggunaan tugas manajemen kaya seperti kontrol per saluran notifikasi. MUNGKIN menggunakan keterjangkauan UI per aplikasi untuk mengurangi kontrol.

Implementasi perangkat otomotif:

• [ 3.14 /A-0-1] HARUS menyertakan kerangka UI untuk mendukung aplikasi pihak ketiga menggunakan API media seperti yang dijelaskan di bagian 3.14 .
• [ 3.14 /A-0-2] HARUS memungkinkan pengguna berinteraksi dengan Aplikasi Media dengan aman saat mengemudi.
• [ 3.14 /A-0-3] HARUS mendukung tindakan Intent implisit CAR_INTENT_ACTION_MEDIA_TEMPLATE dengan tambahan CAR_EXTRA_MEDIA_PACKAGE .
• [ 3.14 /A-0-4] HARUS memberikan kemampuan untuk menavigasi ke aktivitas preferensi Aplikasi Media, tetapi HARUS hanya mengaktifkannya ketika Pembatasan UX Mobil tidak berlaku.
• [ 3.14 /A-0-5] HARUS menampilkan pesan kesalahan yang disetel oleh Aplikasi Media, dan HARUS mendukung tambahan opsional ERROR_RESOLUTION_ACTION_LABEL dan ERROR_RESOLUTION_ACTION_INTENT .
• [ 3.14 /A-0-6] HARUS mendukung keterjangkauan pencarian dalam aplikasi untuk aplikasi yang mendukung pencarian.
• [ 3.14 /A-0-7] HARUS menghormati definisi CONTENT_STYLE_BROWSABLE_HINT dan CONTENT_STYLE_PLAYABLE_HINT saat menampilkan hierarki MediaBrowser .

Jika penerapan perangkat Otomotif menyertakan aplikasi peluncur default, penerapan tersebut:

• [ 3.14 /A-1-1] HARUS menyertakan layanan media dan membukanya dengan maksud CAR_INTENT_ACTION_MEDIA_TEMPLATE .

Implementasi perangkat otomotif:

• [ 3.8 /A] MUNGKIN membatasi permintaan aplikasi untuk membatasi kemampuan memasuki mode layar penuh seperti yang dijelaskan dalam immersive documentation .
• [ 3.8 /A] MUNGKIN membuat bilah status dan bilah navigasi tetap terlihat setiap saat.
• [ 3.8 /A] MUNGKIN membatasi permintaan aplikasi untuk membatasi kemampuan mengubah warna di balik elemen UI sistem, untuk memastikan elemen tersebut terlihat jelas setiap saat, seperti yang dijelaskan dalam WindowManager.LayoutParams#FLAG_TRANSLUCENT_STATUS dan WindowManager.LayoutParams#FLAG_TRANSLUCENT_NAVIGATION .

2.5.4. Kinerja dan Kekuatan

Implementasi perangkat otomotif:

• [ 8.2 /A-0-1] HARUS melaporkan jumlah byte yang dibaca dan ditulis ke penyimpanan non-volatile per UID setiap proses sehingga statistik tersedia untuk pengembang melalui System API android.car.storagemonitoring.CarStorageMonitoringManager . Proyek Sumber Terbuka Android memenuhi persyaratan melalui modul kernel uid_sys_stats .
• [ 8.3 /A-1-3] HARUS masuk ke Mode Garasi minimal satu kali sebelum mobil dimatikan.
• [ 8.3 /A-1-4] HARUS berada dalam Mode Garasi minimal 15 menit kecuali:
  • Baterai terkuras.
  • Tidak ada pekerjaan menganggur yang dijadwalkan.
  • Pengemudi keluar dari Mode Garasi.
• [ 8.4 /A-0-1] HARUS menyediakan profil daya per komponen yang menentukan nilai konsumsi saat ini untuk setiap komponen perangkat keras dan perkiraan pengurasan baterai yang disebabkan oleh komponen seiring waktu seperti yang didokumentasikan di situs Proyek Sumber Terbuka Android.
• [ 8.4 /A-0-2] HARUS melaporkan semua nilai konsumsi daya dalam miliampere jam (mAh).
• [ 8.4 /A-0-3] HARUS melaporkan konsumsi daya CPU per UID setiap proses. Proyek Sumber Terbuka Android memenuhi persyaratan melalui implementasi modul kernel uid_cputime .
• [ 8.4 /A] HARUS dikaitkan dengan komponen perangkat keras itu sendiri jika tidak dapat mengaitkan penggunaan daya komponen perangkat keras ke suatu aplikasi.
• [ 8.4 /A-0-4] HARUS membuat penggunaan daya ini tersedia melalui perintah adb shell dumpsys batterystats shell kepada pengembang aplikasi.

2.5.5. Model Keamanan

Jika penerapan perangkat Otomotif mendukung banyak pengguna, mereka:

• [ 9.5 /A-1-1] TIDAK BOLEH mengizinkan pengguna untuk berinteraksi atau beralih ke Pengguna Sistem Tanpa Kepala , kecuali untuk penyediaan perangkat .
• [ 9.5 /A-1-2] HARUS beralih menjadi Pengguna Sekunder sebelum BOOT_COMPLETED .
• [ 9.5 /A-1-3] HARUS mendukung kemampuan untuk membuat Pengguna Tamu meskipun jumlah maksimum Pengguna pada suatu perangkat telah tercapai.

Implementasi perangkat otomotif:

• [ 9.11 /A-0-1] HARUS mencadangkan implementasi keystore dengan lingkungan eksekusi yang terisolasi.
• [ 9.11 /A-0-2] HARUS memiliki implementasi algoritme kriptografi RSA, AES, ECDSA, dan HMAC serta fungsi hash keluarga MD5, SHA1, dan SHA-2 untuk mendukung algoritme yang didukung sistem Android Keystore dengan benar di area yang terisolasi dengan aman dari kode yang berjalan di kernel ke atas. Isolasi aman HARUS memblokir semua mekanisme potensial yang memungkinkan kode kernel atau ruang pengguna mengakses keadaan internal lingkungan yang terisolasi, termasuk DMA. Proyek Sumber Terbuka Android (AOSP) upstream memenuhi persyaratan ini dengan menggunakan implementasi Trusty , namun solusi berbasis ARM TrustZone lainnya atau implementasi aman yang ditinjau oleh pihak ketiga dari isolasi berbasis hypervisor yang tepat adalah opsi alternatif.
• [ 9.11 /A-0-3] HARUS melakukan otentikasi layar kunci di lingkungan eksekusi yang terisolasi dan hanya jika berhasil, izinkan penggunaan kunci terikat otentikasi. Kredensial layar kunci HARUS disimpan sedemikian rupa sehingga hanya lingkungan eksekusi terisolasi yang dapat melakukan otentikasi layar kunci. Proyek Sumber Terbuka Android hulu menyediakan Lapisan Abstraksi Perangkat Keras Gatekeeper (HAL) dan Trusty, yang dapat digunakan untuk memenuhi persyaratan ini.
• [ 9.11 /A-0-4] HARUS mendukung pengesahan kunci di mana kunci penandatanganan pengesahan dilindungi oleh perangkat keras yang aman dan penandatanganan dilakukan di perangkat keras yang aman. Kunci penandatanganan pengesahan HARUS dibagikan ke sejumlah perangkat yang cukup besar untuk mencegah kunci digunakan sebagai pengidentifikasi perangkat. Salah satu cara untuk memenuhi persyaratan ini adalah dengan berbagi kunci pengesahan yang sama kecuali setidaknya 100.000 unit SKU tertentu diproduksi. Jika lebih dari 100.000 unit SKU diproduksi, kunci yang berbeda MUNGKIN digunakan untuk setiap 100.000 unit.

Perhatikan bahwa jika implementasi perangkat telah diluncurkan pada versi Android yang lebih lama, perangkat tersebut dikecualikan dari persyaratan untuk memiliki keystore yang didukung oleh lingkungan eksekusi terisolasi dan mendukung pengesahan kunci, kecuali perangkat tersebut mendeklarasikan fitur android.hardware.fingerprint yang mana memerlukan keystore yang didukung oleh lingkungan eksekusi yang terisolasi.

Jika penerapan perangkat Otomotif mendukung layar kunci yang aman, penerapan tersebut:

• [ 9.11 /A-1-1] HARUS mengizinkan pengguna memilih batas waktu Tidur untuk transisi dari keadaan tidak terkunci ke keadaan terkunci, dengan batas waktu minimum yang diperbolehkan hingga 15 detik atau kurang.

Implementasi perangkat otomotif:

• [ 9.14 /A-0-1] HARUS menjaga gerbang pesan dari subsistem kendaraan framework Android, misalnya, memasukkan jenis pesan dan sumber pesan yang diizinkan ke dalam daftar yang diizinkan.
• [ 9.14 /A-0-2] HARUS menjadi pengawas terhadap serangan penolakan layanan dari kerangka Android atau aplikasi pihak ketiga. Hal ini melindungi terhadap perangkat lunak berbahaya yang membanjiri jaringan kendaraan dengan lalu lintas, yang dapat menyebabkan tidak berfungsinya subsistem kendaraan.

2.5.6. Kompatibilitas Alat dan Opsi Pengembang

Implementasi perangkat otomotif:

• Sempurna
  • [ 6.1 /A-0-1] HARUS mengekspos biner /system/bin/perfetto ke pengguna shell yang cmdlinenya sesuai dengan dokumentasi perfetto .
  • [ 6.1 /A-0-2] Biner perfetto HARUS menerima konfigurasi protobuf sebagai masukan yang sesuai dengan skema yang ditentukan dalam dokumentasi perfetto .
  • [ 6.1 /A-0-3] Biner perfetto HARUS menulis sebagai keluaran jejak protobuf yang sesuai dengan skema yang ditentukan dalam dokumentasi perfetto .
  • [ 6.1 /A-0-4] HARUS menyediakan, melalui biner perfetto, setidaknya sumber data yang dijelaskan dalam dokumentasi perfetto .

2.6. Persyaratan Tablet

Perangkat Tablet Android mengacu pada implementasi perangkat Android yang memenuhi seluruh kriteria berikut:

• Biasanya digunakan dengan cara dipegang dengan kedua tangan.
• Tidak memiliki konfigurasi clamshell atau convertible.
• Implementasi keyboard fisik apa pun yang digunakan dengan perangkat HARUS terhubung melalui koneksi standar.
• Memiliki sumber tenaga yang memberikan mobilitas, seperti baterai.
• Memiliki ukuran diagonal layar fisik pada kisaran 7 hingga 18 inci.

Implementasi perangkat tablet memiliki persyaratan serupa dengan implementasi perangkat genggam. Pengecualian ditunjukkan dengan tanda * di bagian itu dan dicatat untuk referensi di bagian ini.

2.6.1. Perangkat keras

Ukuran layar

• [ 7.1 .1.1/Tab-0-1] HARUS memiliki layar dalam kisaran 7 hingga 18 inci.

Giroskop

Jika implementasi perangkat Tablet menyertakan giroskop 3 sumbu, maka:

• [ 7.3 .4/Tab-1-1] HARUS mampu mengukur perubahan orientasi hingga 1000 derajat per detik.

Memori dan Penyimpanan Minimum (Bagian 7.6.1)

Kepadatan layar yang tercantum untuk layar kecil/normal dalam persyaratan perangkat genggam tidak berlaku untuk tablet.

Mode periferal USB (Bagian 7.7.1)

Jika implementasi perangkat tablet menyertakan port USB yang mendukung mode periferal, maka:

• [ 7.7.1 /Tab] MUNGKIN mengimplementasikan API Android Open Accessories (AOA).

Mode Realitas Virtual (Bagian 7.9.1)

Realitas Virtual Kinerja Tinggi (Bagian 7.9.2)

Persyaratan realitas virtual tidak berlaku untuk tablet.

2.6.2. Model Keamanan

Kunci dan Kredensial (Bagian 9.11)

Lihat Bagian [ 9.11 ].

Jika penerapan perangkat Tablet menyertakan beberapa pengguna dan tidak mendeklarasikan tanda fitur android.hardware.telephony , mereka:

• [ 9.5 /T-1-1] HARUS mendukung profil terbatas, sebuah fitur yang memungkinkan pemilik perangkat mengelola pengguna tambahan dan kemampuan mereka di perangkat. Dengan profil yang dibatasi, pemilik perangkat dapat dengan cepat mengatur lingkungan terpisah agar pengguna tambahan dapat bekerja, dengan kemampuan untuk mengelola pembatasan yang lebih terperinci pada aplikasi yang tersedia di lingkungan tersebut.

Jika penerapan perangkat Tablet menyertakan beberapa pengguna dan mendeklarasikan tanda fitur android.hardware.telephony , mereka:

• [ 9.5 /T-2-1] TIDAK HARUS mendukung profil yang dibatasi tetapi HARUS selaras dengan penerapan kontrol AOSP untuk mengaktifkan/menonaktifkan pengguna lain mengakses panggilan suara dan SMS.

3. Perangkat Lunak

3.1. Kompatibilitas API Terkelola

Lingkungan eksekusi bytecode Dalvik yang dikelola adalah sarana utama untuk aplikasi Android. Antarmuka pemrograman aplikasi (API) Android adalah kumpulan antarmuka platform Android yang diekspos ke aplikasi yang berjalan di lingkungan runtime terkelola.

Implementasi perangkat:

• [C-0-1] HARUS menyediakan implementasi lengkap, termasuk semua perilaku yang terdokumentasi, dari setiap API terdokumentasi yang diekspos oleh Android SDK atau API apa pun yang diberi penanda “@SystemApi” di kode sumber Android upstream.

• [C-0-2] HARUS mendukung/mempertahankan semua kelas, metode, dan elemen terkait yang ditandai dengan anotasi TestApi (@TestApi).

• [C-0-3] TIDAK BOLEH menghilangkan API yang dikelola, mengubah antarmuka atau tanda tangan API, menyimpang dari perilaku yang terdokumentasi, atau menyertakan larangan pengoperasian, kecuali jika diizinkan secara khusus oleh Definisi Kompatibilitas ini.

• [C-0-4] HARUS tetap menjaga API tetap ada dan berperilaku wajar, meskipun beberapa fitur perangkat keras yang menyertakan API di Android dihilangkan. Lihat bagian 7 untuk persyaratan khusus untuk skenario ini.

• [C-0-5] TIDAK HARUS mengizinkan aplikasi pihak ketiga untuk menggunakan antarmuka non-SDK, yang didefinisikan sebagai metode dan bidang dalam paket bahasa Java yang ada di jalur kelas boot di AOSP, dan yang bukan merupakan bagian dari SDK publik. Ini termasuk API yang dihiasi dengan anotasi @hide tetapi tidak dengan @SystemAPI , seperti yang dijelaskan dalam dokumen SDK dan anggota kelas privat dan paket-pribadi.

• [C-0-6] HARUS dikirimkan dengan setiap antarmuka non-SDK pada daftar terbatas yang sama seperti yang disediakan melalui daftar sementara dan tanda daftar penolakan di jalur prebuilts/runtime/appcompat/hiddenapi-flags.csv untuk cabang level API yang sesuai di AOSP.

  Namun mereka:

  • MUNGKIN, jika API tersembunyi tidak ada atau diterapkan secara berbeda pada implementasi perangkat, pindahkan API tersembunyi ke dalam daftar yang ditolak atau hilangkan dari semua daftar yang dibatasi.
  • MUNGKIN, jika API tersembunyi belum ada di AOSP, tambahkan API tersembunyi ke salah satu daftar terbatas.

• [C-0-7] HARUS mendukung mekanisme pembaruan dinamis konfigurasi yang ditandatangani untuk menghapus antarmuka non-SDK dari daftar terbatas dengan menyematkan konfigurasi yang ditandatangani di APK apa pun, menggunakan kunci publik yang ada di AOSP.

3.1.1. Ekstensi Android

Android menyertakan dukungan untuk memperluas API terkelola sambil mempertahankan versi level API yang sama.

• [C-0-1] Implementasi perangkat Android HARUS memuat implementasi AOSP dari perpustakaan bersama ExtShared dan layanan ExtServices dengan versi yang lebih tinggi atau sama dengan versi minimum yang diizinkan per setiap level API. Misalnya, implementasi perangkat Android 7.0, yang menjalankan API level 24 HARUS menyertakan setidaknya versi 1.

3.1.2. Perpustakaan Android

Karena penghentian klien HTTP Apache , implementasi perangkat:

• [C-0-1] TIDAK HARUS menempatkan perpustakaan org.apache.http.legacy di jalur bootclass.
• [C-0-2] HARUS menambahkan perpustakaan org.apache.http.legacy ke classpath aplikasi hanya jika aplikasi memenuhi salah satu kondisi berikut:
  • Menargetkan API level 28 atau lebih rendah.
  • Mendeklarasikan dalam manifesnya bahwa ia memerlukan perpustakaan dengan menyetel atribut android:name dari <uses-library> ke org.apache.http.legacy .

Implementasi AOSP memenuhi persyaratan ini.

3.2. Kompatibilitas API Lunak

Selain API terkelola dari bagian 3.1 , Android juga menyertakan API “lunak” khusus waktu proses yang signifikan, dalam bentuk hal-hal seperti maksud, izin, dan aspek serupa dari aplikasi Android yang tidak dapat diterapkan pada waktu kompilasi aplikasi.

3.2.1. Izin

• [C-0-1] Pelaksana perangkat HARUS mendukung dan menegakkan semua konstanta izin seperti yang didokumentasikan oleh halaman referensi Izin . Perhatikan bahwa bagian 9 mencantumkan persyaratan tambahan terkait model keamanan Android.

3.2.2. Parameter Bangun

Android API menyertakan sejumlah konstanta pada kelas android.os.Build yang dimaksudkan untuk mendeskripsikan perangkat saat ini.

• [C-0-1] Untuk memberikan nilai yang konsisten dan bermakna di seluruh implementasi perangkat, tabel di bawah menyertakan batasan tambahan pada format nilai-nilai ini yang HARUS dipatuhi oleh implementasi perangkat.

3.2.3. Kompatibilitas Inten

3.2.3.1. Maksud aplikasi inti

Intents Android memungkinkan komponen aplikasi untuk meminta fungsionalitas dari komponen Android lainnya. Proyek hulu Android mencakup daftar aplikasi yang dianggap sebagai aplikasi Android inti, yang mengimplementasikan beberapa pola niat untuk melakukan tindakan umum.

• [C-0-1] Implementasi perangkat harus memuat satu atau lebih aplikasi atau komponen layanan dengan penangan niat, untuk semua pola filter niat publik yang ditentukan oleh aplikasi Android inti berikut di AOSP:

  • Jam meja
  • Peramban
  • Kalender
  • Kontak
  • Galeri
  • Pencarian Global
  • Peluncur
  • Musik
  • Pengaturan

3.2.3.2. Resolusi Inten

• [C-0-1] Karena Android adalah platform yang dapat diperluas, implementasi perangkat harus memungkinkan setiap pola niat yang dirujuk dalam Bagian 3.2.3.1 , kecuali untuk pengaturan, untuk ditimpa oleh aplikasi pihak ketiga. Implementasi sumber terbuka Android hulu memungkinkan ini secara default.

• [C-0-2] Pelaksana perangkat tidak boleh melampirkan hak istimewa khusus untuk penggunaan aplikasi sistem dari pola-pola niat ini, atau mencegah aplikasi pihak ketiga dari mengikat dan dengan asumsi kontrol pola-pola ini. Larangan ini secara khusus mencakup tetapi tidak terbatas untuk menonaktifkan antarmuka pengguna "pemilih" yang memungkinkan pengguna untuk memilih antara beberapa aplikasi yang semuanya menangani pola niat yang sama.

• [C-0-3] Implementasi perangkat harus menyediakan antarmuka pengguna bagi pengguna untuk memodifikasi aktivitas default untuk maksud.

• Namun, implementasi perangkat dapat memberikan aktivitas default untuk pola URI tertentu (misalnya http://play.google.com) ketika aktivitas default memberikan atribut yang lebih spesifik untuk URI data. Misalnya, pola filter niat yang menentukan data URI “http://www.android.com” lebih spesifik daripada pola inti inti browser untuk “http: //”.

Android juga mencakup mekanisme untuk aplikasi pihak ketiga untuk mendeklarasikan perilaku menghubungkan aplikasi default otoritatif untuk jenis-jenis niat URI web tertentu. Ketika deklarasi otoritatif tersebut didefinisikan dalam pola filter niat aplikasi, implementasi perangkat:

• [C-0-4] harus berupaya memvalidasi filter niat apa pun dengan melakukan langkah-langkah validasi yang ditentukan dalam spesifikasi tautan aset digital seperti yang diimplementasikan oleh manajer paket dalam proyek sumber terbuka Android hulu.
• [C-0-5] Harus mencoba validasi filter niat selama pemasangan aplikasi dan mengatur semua filter niat URI yang berhasil divalidasi sebagai penangan aplikasi default untuk URI mereka.
• Dapat mengatur filter niat URI spesifik sebagai penangan aplikasi default untuk URI mereka, jika mereka berhasil diverifikasi tetapi kandidat lain filter URI gagal verifikasi. Jika implementasi perangkat melakukan ini, ia harus memberikan pengguna yang sesuai dengan pola per-URI yang sesuai di menu Pengaturan.
• Harus memberi pengguna kontrol tautan aplikasi per-aplikasi dalam pengaturan sebagai berikut:
  • [C-0-6] Pengguna harus dapat mengganti secara holistik perilaku aplikasi default untuk suatu aplikasi: selalu terbuka, selalu bertanya, atau tidak pernah terbuka, yang harus berlaku untuk semua kandidat filter niat URI secara setara.
  • [C-0-7] Pengguna harus dapat melihat daftar filter niat kandidat URI.
  • Implementasi perangkat dapat memberi pengguna kemampuan untuk mengganti filter niat kandidat URI tertentu yang berhasil diverifikasi, berdasarkan per-basis filter per-intent.
  • [C-0-8] Implementasi perangkat harus memberi pengguna kemampuan untuk melihat dan mengganti filter niat kandidat spesifik URI jika implementasi perangkat memungkinkan beberapa kandidat filter niat URI berhasil verifikasi sementara beberapa yang lain dapat gagal.

3.2.3.3. Names names

• [C-0-1] Implementasi perangkat tidak boleh menyertakan komponen android apa pun yang menghormati pola niat atau siaran baru apa pun menggunakan tindakan, kategori, atau string kunci lainnya di Android. atau com.android. ruang nama.
• [C-0-2] Implementer Perangkat tidak boleh memasukkan komponen Android yang menghormati pola niat atau siaran baru apa pun menggunakan tindakan, kategori, atau string kunci lainnya dalam ruang paket milik organisasi lain.
• [C-0-3] Implementer perangkat tidak boleh mengubah atau memperluas salah satu pola niat yang digunakan oleh aplikasi inti yang tercantum dalam Bagian 3.2.3.1 .
• Implementasi perangkat dapat mencakup pola niat menggunakan ruang nama dengan jelas dan jelas terkait dengan organisasi mereka sendiri. Larangan ini analog dengan yang ditentukan untuk kelas bahasa Java di Bagian 3.6 .

3.2.3.4. Maksud siaran

Aplikasi pihak ketiga bergantung pada platform untuk menyiarkan maksud tertentu untuk memberi tahu mereka tentang perubahan dalam lingkungan perangkat keras atau perangkat lunak.

Implementasi perangkat:

• [C-0-1] Harus menyiarkan niat siaran publik sebagai respons terhadap peristiwa sistem yang sesuai seperti yang dijelaskan dalam dokumentasi SDK. Perhatikan bahwa persyaratan ini tidak bertentangan dengan Bagian 3.5 karena batasan untuk aplikasi latar belakang juga dijelaskan dalam dokumentasi SDK.

3.2.3.5. Pengaturan Aplikasi Default

Android termasuk pengaturan yang memberikan pengguna cara mudah untuk memilih aplikasi default mereka, misalnya untuk layar beranda atau SMS.

Di mana masuk akal, implementasi perangkat harus memberikan menu pengaturan yang serupa dan kompatibel dengan pola filter niat dan metode API yang dijelaskan dalam dokumentasi SDK seperti di bawah ini.

Jika implementasi perangkat melaporkan android.software.home_screen , mereka:

• [C-1-1] Harus menghormati android.settings.HOME_SETTINGS niat untuk menampilkan menu pengaturan aplikasi default untuk layar beranda.

Jika implementasi perangkat melaporkan android.hardware.telephony , mereka:

• [C-2-1] harus menyediakan menu pengaturan yang akan menghubungi RoleManager.createRequestRoleIntent(String) niat dengan RoleManager.ROLE_SMS untuk menampilkan dialog untuk mengubah aplikasi SMS default.

• [C-2-2] Harus menghormati android.telecom.action.CHANGE_DEFAULT_DIALER Intent untuk menampilkan dialog agar pengguna mengubah aplikasi telepon default.

  • Harus menggunakan UI aplikasi telepon default yang dipilih pengguna untuk panggilan masuk dan keluar kecuali untuk panggilan darurat, yang akan menggunakan aplikasi telepon yang diinstal sebelumnya.

• [C-2-3] Harus menghormati Android.telecom.action.change_phone_accounts niat untuk memberikan keterjangkauan pengguna untuk mengkonfigurasi ConnectionServices yang terkait dengan PhoneAccounts , serta phoneaccount default yang akan digunakan oleh penyedia layanan telekomunikasi untuk melakukan panggilan keluar. Implementasi AOSP memenuhi persyaratan ini dengan memasukkan menu "Opsi Akun Panggilan" dalam menu Pengaturan "Panggilan".

• [C-2-4] Harus mengizinkan android.telecom.CallRedirectionService untuk aplikasi yang memegang peran android.app.role.CALL_REDIRECTION .

• [C-2-5] harus memberikan keterjangkauan pengguna untuk memilih aplikasi yang memegang peran android.app.role.CALL_REDIRECTION .

Jika implementasi perangkat melaporkan android.hardware.nfc.hce , mereka:

• [C-3-1] Harus menghormati android.settings.nfc_payment_settings bermaksud menampilkan menu pengaturan aplikasi default untuk tap dan bayar.

Jika implementasi perangkat mendukung VoiceInteractionService dan memiliki lebih dari satu aplikasi menggunakan API ini yang diinstal pada satu waktu, mereka:

• [C-4-1] Harus menghormati android.settings.ACTION_VOICE_INPUT_SETTINGS bermaksud menampilkan menu pengaturan aplikasi default untuk input suara dan membantu.

3.2.4. Aktivitas pada tampilan sekunder/ganda

Jika implementasi perangkat memungkinkan meluncurkan aktivitas Android normal pada lebih dari satu tampilan, mereka:

• [C-1-1] Harus mengatur android.software.activities_on_secondary_displays fitur bendera.
• [C-1-2] Harus menjamin kompatibilitas API yang mirip dengan aktivitas yang berjalan pada tampilan primer.
• [C-1-3] harus mendaratkan aktivitas baru pada tampilan yang sama dengan aktivitas yang meluncurkannya, ketika aktivitas baru diluncurkan tanpa menentukan tampilan target melalui ActivityOptions.setLaunchDisplayId() API.
• [C-1-4] Harus menghancurkan semua kegiatan, saat tampilan dengan Display.FLAG_PRIVATE Flag dihapus.
• [C-1-5] Harus menyembunyikan konten dengan aman di semua layar ketika perangkat dikunci dengan layar kunci yang aman, kecuali jika aplikasi memilih untuk menampilkan di atas layar kunci menggunakan Activity#setShowWhenLocked() API.
• Harus memiliki android.content.res.Configuration yang sesuai dengan tampilan tersebut untuk ditampilkan, beroperasi dengan benar, dan mempertahankan kompatibilitas jika suatu aktivitas diluncurkan pada tampilan sekunder.

Jika implementasi perangkat memungkinkan meluncurkan aktivitas Android normal pada tampilan sekunder dan tampilan sekunder memiliki android.view.display.flag_private Flag:

• [C-3-1] Hanya pemilik tampilan, sistem, dan aktivitas yang sudah ada di layar itu harus dapat meluncurkannya. Semua orang dapat meluncurkan ke layar yang memiliki android.view.display.flag_public Flag.

3.3. Kompatibilitas API Asli

Kompatibilitas kode asli menantang. Untuk alasan ini, pelaksana perangkat adalah:

• [SR] Sangat disarankan untuk menggunakan implementasi perpustakaan yang tercantum di bawah ini dari proyek open source Android hulu.

3.3.1. Antarmuka Biner Aplikasi

Dalvik Bytecode yang dikelola dapat memanggil kode asli yang disediakan dalam file aplikasi .apk sebagai file elf .so yang dikumpulkan untuk arsitektur perangkat keras perangkat yang sesuai. Karena kode asli sangat tergantung pada teknologi prosesor yang mendasarinya, Android mendefinisikan sejumlah antarmuka biner aplikasi (ABIS) di NDK Android.

Implementasi perangkat:

• [C-0-1] harus kompatibel dengan satu atau lebih ABIS yang ditentukan dan mengimplementasikan kompatibilitas dengan NDK Android.
• [C-0-2] harus menyertakan dukungan untuk kode yang berjalan di lingkungan yang dikelola untuk memanggil kode asli, menggunakan semantik standar Java Aslif Afterface (JNI).
• [C-0-3] harus kompatibel dengan sumber (yaitu compatible header) dan kompatibel biner (untuk ABI) dengan masing-masing perpustakaan yang diperlukan dalam daftar di bawah ini.
• [C-0-5] Harus secara akurat melaporkan antarmuka biner aplikasi asli (ABI) yang didukung oleh perangkat, melalui android.os.Build.SUPPORTED_ABIS , android.os.Build.SUPPORTED_32_BIT_ABIS , dan android.os.build.supported_64_bit_abis Paramer Paramer, dan android.os.Build.SUPPORTED_64_BIT_ABIS Paramers.osabis , masing -masing koma yang terpisah dari ABIS yang dipesan dari yang paling disukai.

• [C-0-6] Harus melaporkan, melalui parameter di atas, subset dari daftar ABIS berikut dan tidak boleh melaporkan ABI apa pun yang tidak ada dalam daftar.

  • armeabi
  • armeabi-v7a
  • arm64-v8a
  • x86
  • x86-64

  • [C-0-7] Harus membuat semua perpustakaan berikut, menyediakan API asli, tersedia untuk aplikasi yang menyertakan kode asli:

  • libaaudio.so (dukungan audio asli AAudio)

  • libamidi.so (dukungan MIDI asli, jika fitur android.software.midi diklaim seperti dijelaskan di Bagian 5.9)
  • libandroid.so (dukungan aktivitas Android asli)
  • libc (perpustakaan C)
  • libcamera2ndk.so
  • libdl (penghubung dinamis)
  • libEGL.so (manajemen permukaan OpenGL asli)
  • libGLESv1_CM.so (OpenGL ES 1.x)
  • libGLESv2.so (OpenGL ES 2.0)
  • libGLESv3.so (OpenGL ES 3.x)
  • lilicui18n.so
  • libicuuc.so
  • libjnigraphics.so
  • liblog (pencatatan Android)
  • libmediandk.so (dukungan API media asli)
  • libm (perpustakaan matematika)
  • libneuralnetworks.so (API Jaringan Syaraf Tiruan)
  • libOpenMAXAL.so (dukungan OpenMAX AL 1.0.1)
  • libOpenSLES.so (dukungan audio OpenSL ES 1.0.1)
  • libRS.jadi
  • libstdc++ (Dukungan minimal untuk C++)
  • libvulkan.so (Vulkan)
  • libz (kompresi Zlib)
  • antarmuka JNI

• [C-0-8] tidak boleh menambah atau menghapus fungsi publik untuk perpustakaan asli yang tercantum di atas.

• [C-0-9] Harus mencantumkan perpustakaan non-AOSP tambahan yang diekspos langsung ke aplikasi pihak ketiga di /vendor/etc/public.libraries.txt .
• [C-0-10] Tidak boleh mengekspos perpustakaan asli lainnya, diimplementasikan dan disediakan dalam AOSP sebagai perpustakaan sistem, untuk aplikasi pihak ketiga yang menargetkan API level 24 atau lebih tinggi saat mereka dicadangkan.
• [C-0-11] Harus mengekspor semua simbol fungsi OpenGL ES 3.1 dan Android Extension Pack , sebagaimana didefinisikan dalam NDK, melalui perpustakaan libGLESv3.so . Perhatikan bahwa sementara semua simbol harus ada, Bagian 7.1.4.1 menjelaskan secara lebih rinci persyaratan ketika implementasi penuh dari setiap fungsi yang sesuai diharapkan.
• [C-0-12] Harus mengekspor simbol fungsi untuk simbol fungsi Core Vulkan 1.0, serta VK_KHR_surface , VK_KHR_android_surface VK_KHR_get_physical_device_properties2 VK_KHR_swapchain libvulkan.so VK_KHR_maintenance1 . Perhatikan bahwa sementara semua simbol harus ada, Bagian 7.1.4.2 menjelaskan secara lebih rinci persyaratan ketika implementasi penuh dari setiap fungsi yang sesuai diharapkan.
• Harus dibangun menggunakan kode sumber dan file header yang tersedia di proyek open source android hulu

Perhatikan bahwa rilis Android di masa depan dapat memperkenalkan dukungan untuk ABIS tambahan.

3.3.2. Kompatibilitas kode asli lengan 32-bit

Jika implementasi perangkat melaporkan dukungan dari ABI armeabi , mereka:

• [C-3-1] juga harus mendukung armeabi-v7a dan melaporkan dukungannya, karena armeabi hanya untuk kompatibilitas ke belakang dengan aplikasi yang lebih lama.

Jika implementasi perangkat melaporkan dukungan dari ABI armeabi-v7a , untuk aplikasi menggunakan ABI ini, mereka:

• [C-2-1] harus menyertakan baris berikut di /proc/cpuinfo , dan tidak boleh mengubah nilai pada perangkat yang sama, bahkan ketika mereka dibaca oleh ABIS lainnya.

  • Features: diikuti oleh daftar fitur CPU ARMV7 opsional yang didukung oleh perangkat.
  • CPU architecture: diikuti oleh bilangan bulat yang menggambarkan arsitektur lengan tertinggi yang didukung perangkat (misalnya, "8" untuk perangkat ARMV8).

• [C-2-2] harus selalu menjaga operasi berikut tersedia, bahkan dalam kasus di mana ABI diimplementasikan pada arsitektur ARMV8, baik melalui dukungan CPU asli atau melalui emulasi perangkat lunak:

  • Instruksi SWP dan SWPB.
  • Setend instruksi.
  • Operasi penghalang CP15ISB, CP15DSB, dan CP15DMB.

• [C-2-3] harus mencakup dukungan untuk ekstensi SIMD lanjutan (alias neon).

3.4. Kompatibilitas Web

3.4.1. Kompatibilitas Webview

Jika implementasi perangkat memberikan implementasi lengkap dari android.webkit.Webview API, mereka:

• [C-1-1] Harus melaporkan android.software.webview .
• [C-1-2] Harus menggunakan Proyek Chromium Build dari proyek open source Android hulu di cabang Android 10 untuk implementasi android.webkit.WebView API.

• [C-1-3] String agen pengguna yang dilaporkan oleh WebView harus dalam format ini:

  Mozilla/5.0 (linux; android $ (versi); [$ (model)] [build/$ (build)]; wv) applewebkit/537.36 (khtml, seperti tokek) versi/4.0 $ (chromium_ver) safari seluler/537.36

  • Nilai string $ (versi) harus sama dengan nilai untuk android.os.build.version.release.
  • String $ (model) mungkin kosong, tetapi jika tidak kosong, ia harus memiliki nilai yang sama dengan android.os.build.model.
  • "Build/$ (build)" dapat dihilangkan, tetapi jika ada string $ (build) harus sama dengan nilai untuk android.os.build.id.
  • Nilai string $ (chromium_ver) harus menjadi versi kromium dalam proyek open source android hulu.
  • Implementasi perangkat dapat menghilangkan seluler di string agen pengguna.

• Komponen WebView harus menyertakan dukungan untuk sebanyak mungkin fitur HTML5 dan jika mendukung fitur tersebut harus sesuai dengan spesifikasi HTML5 .

• [C-1-4] harus membuat konten yang disediakan atau konten URL jarak jauh dalam proses yang berbeda dari aplikasi yang membuat instantiate webview. Secara khusus proses renderer yang terpisah harus memiliki hak istimewa yang lebih rendah, dijalankan sebagai ID pengguna yang terpisah, tidak memiliki akses ke direktori data aplikasi, tidak memiliki akses jaringan langsung, dan hanya memiliki akses ke layanan sistem yang diminta minimum di atas Binder. Implementasi WebView AOSP memenuhi persyaratan ini.

Perhatikan bahwa jika implementasi perangkat 32-bit atau mendeklarasikan fitur fitur android.hardware.ram.low , mereka dibebaskan dari C-1-3.

3.4.2. Kompatibilitas Peramban

Jika implementasi perangkat mencakup aplikasi browser mandiri untuk penelusuran web umum, mereka:

• [C-1-1] harus mendukung masing-masing API ini yang terkait dengan HTML5:
  • Operasi Cache/Offline Aplikasi
  • Tag <video>
  • geolokasi
• [C-1-2] Harus mendukung WebStorage API HTML5/W3C dan harus mendukung API IndexedDB HTML5/W3C. Perhatikan bahwa karena Standar Pengembangan Web, badan beralih untuk mendukung IndexedDB daripada WebStorage, IndexEdDB diharapkan menjadi komponen yang diperlukan dalam versi Android yang akan datang.
• Dapat mengirimkan string agen pengguna khusus di aplikasi browser mandiri.
• Harus menerapkan dukungan untuk sebanyak mungkin HTML5 pada aplikasi browser mandiri (baik berdasarkan aplikasi browser webkit hulu atau penggantian pihak ketiga).

Namun, jika implementasi perangkat tidak termasuk aplikasi browser mandiri, mereka:

• [C-2-1] masih harus mendukung pola niat publik seperti yang dijelaskan dalam Bagian 3.2.3.1 .

3.5. Kompatibilitas perilaku API

Implementasi perangkat:

• [C-0-9] harus memastikan bahwa kompatibilitas perilaku API diterapkan untuk semua aplikasi yang diinstal kecuali mereka dibatasi seperti yang dijelaskan dalam Bagian 3.5.1 .
• [C-0-10] tidak boleh mengimplementasikan pendekatan daftar yang diizinkan yang memastikan kompatibilitas perilaku API hanya untuk aplikasi yang dipilih oleh pelaksana perangkat.

Perilaku masing -masing jenis API (dikelola, lunak, asli, dan web) harus konsisten dengan implementasi yang disukai dari proyek open source Android hulu. Beberapa bidang kompatibilitas spesifik adalah:

• Perangkat [C-0-1] tidak boleh mengubah perilaku atau semantik dari niat standar.
• Perangkat [C-0-2] tidak boleh mengubah siklus hidup atau siklus hidup dari jenis komponen sistem tertentu (seperti layanan, aktivitas, contentProvider, dll.).
• Perangkat [C-0-3] tidak boleh mengubah semantik izin standar.
• Perangkat tidak boleh mengubah batasan yang ditegakkan pada aplikasi latar belakang. Lebih khusus lagi, untuk aplikasi latar belakang:
  • [C-0-4] Mereka harus berhenti mengeksekusi panggilan balik yang terdaftar oleh aplikasi untuk menerima output dari GnssMeasurement dan GnssNavigationMessage .
  • [C-0-5] Mereka harus membatasi tingkat frekuensi pembaruan yang disediakan untuk aplikasi melalui kelas API LocationManager atau metode WifiManager.startScan() .
  • [C-0-6] Jika aplikasi menargetkan API level 25 atau lebih tinggi, mereka tidak boleh mengizinkan untuk mendaftarkan penerima siaran untuk siaran implisit dari intents android standar dalam manifes aplikasi, kecuali niat siaran memerlukan "signature" atau "signatureOrSystem" Izin protectionLevel atau ada dalam daftar pengecualian .
  • [C-0-7] Jika aplikasi menargetkan API level 25 atau lebih tinggi, mereka harus menghentikan layanan latar belakang aplikasi, seperti halnya aplikasi telah memanggil metode layanan ' stopSelf() , kecuali jika aplikasi ditempatkan pada daftar izin sementara Untuk menangani tugas yang terlihat oleh pengguna.
  • [C-0-8] Jika aplikasi menargetkan API level 25 atau lebih tinggi, mereka harus melepaskan Wakelocks yang dimiliki aplikasi.
• Perangkat [C-0-9] harus mengembalikan penyedia keamanan berikut sebagai tujuh nilai array pertama dari metode Security.getProviders() , dalam urutan yang diberikan dan dengan nama yang diberikan (seperti yang dikembalikan oleh Provider.getName() dan kelas dan kelas , Kecuali jika aplikasi telah memodifikasi daftar melalui insertProviderAt() atau removeProvider() . Perangkat dapat mengembalikan penyedia tambahan setelah daftar penyedia yang ditentukan di bawah ini.
  1. AndroidNSSP - android.security.net.config.NetworkSecurityConfigProvider
  2. Androidopenssl - com.android.org.conscrypt.OpenSSLProvider
  3. CertPathProvider - sun.security.provider.CertPathProvider
  4. AndroidKeyStorEBCWorkaround - android.security.keystore.AndroidKeyStoreBCWorkaroundProvider
  5. BC - com.android.org.bouncycastle.jce.provider.BouncyCastleProvider
  6. Harmonyjsse - com.android.org.conscrypt.JSSEProvider
  7. AndroidKeyStore - android.security.keystore.AndroidKeyStoreProvider

Daftar di atas tidak lengkap. Compatibility Test Suite (CTS) menguji bagian -bagian signifikan dari platform untuk kompatibilitas perilaku, tetapi tidak semua. Merupakan tanggung jawab pelaksana untuk memastikan kompatibilitas perilaku dengan proyek open source Android. Untuk alasan ini, pelaksana perangkat harus menggunakan kode sumber yang tersedia melalui proyek open source Android jika memungkinkan, daripada mengimplementasikan kembali bagian-bagian signifikan dari sistem.

3.5.1. Pembatasan latar belakang

Jika implementasi perangkat mengimplementasikan pembatasan aplikasi yang termasuk dalam AOSP atau memperluas pembatasan aplikasi, mereka:

• [C-1-1] harus memberikan keterjangkauan pengguna di mana pengguna dapat melihat daftar aplikasi terbatas.
• [C-1-2] harus memberikan keterjangkauan pengguna untuk menghidupkan / mematikan pembatasan pada setiap aplikasi.
• [C-1-3] tidak boleh secara otomatis menerapkan pembatasan tanpa bukti perilaku kesehatan sistem yang buruk, tetapi dapat menerapkan pembatasan aplikasi setelah mendeteksi perilaku kesehatan sistem yang buruk seperti macet Wakelocks, layanan jangka panjang, dan kriteria lainnya. Kriteria dapat ditentukan oleh pelaksana perangkat tetapi harus terkait dengan dampak aplikasi pada kesehatan sistem. Kriteria lain yang tidak murni terkait dengan kesehatan sistem, seperti kurangnya popularitas aplikasi di pasar, tidak boleh digunakan sebagai kriteria.
• [C-1-4] tidak boleh secara otomatis menerapkan pembatasan aplikasi untuk aplikasi ketika pengguna telah mematikan pembatasan aplikasi secara manual, dan dapat menyarankan pengguna untuk menerapkan pembatasan aplikasi.
• [C-1-5] Harus memberi tahu pengguna jika pembatasan aplikasi diterapkan pada aplikasi secara otomatis.
• [C-1-6] Harus kembali true untuk ActivityManager.isBackgroundRestricted() ketika aplikasi terbatas memanggil API ini.
• [C-1-7] tidak boleh membatasi aplikasi latar depan teratas yang secara eksplisit digunakan oleh pengguna.
• [C-1-8] Harus menangguhkan pembatasan pada aplikasi yang menjadi aplikasi latar depan teratas ketika pengguna secara eksplisit mulai menggunakan aplikasi yang dulu dibatasi.

3.6. API Namespaces

Android mengikuti konvensi paket dan namespace kelas yang ditentukan oleh bahasa pemrograman Java. Untuk memastikan kompatibilitas dengan aplikasi pihak ketiga, pelaksana perangkat tidak boleh melakukan modifikasi yang dilarang (lihat di bawah) ke paket nama ini:

• java.*
• javax.*
• sun.*
• android.*
• androidx.*
• com.android.*

Yaitu, mereka:

• [C-0-1] tidak boleh memodifikasi API yang diekspos publik pada platform Android dengan mengubah metode atau tanda tangan kelas apa pun, atau dengan menghapus kelas atau bidang kelas.
• [C-0-2] tidak boleh menambahkan elemen yang terpapar publik (seperti kelas atau antarmuka, atau bidang atau metode ke kelas atau antarmuka yang ada) atau menguji atau sistem API ke API di ruang nama di atas. "Elemen yang diekspos secara publik" adalah konstruksi apa pun yang tidak dihiasi dengan penanda "@Hide" seperti yang digunakan dalam kode sumber Android hulu.

Pelaksana perangkat dapat memodifikasi implementasi API yang mendasari, tetapi modifikasi tersebut:

• [C-0-3] Tidak boleh berdampak pada perilaku yang dinyatakan dan tanda tangan berbahasa Java dari API yang terpapar publik.
• [C-0-4] tidak boleh diiklankan atau terpapar dengan pengembang.

Namun, pelaksana perangkat dapat menambahkan API khusus di luar standar Namespace Android, tetapi API khusus:

• [C-0-5] tidak boleh berada di namespace yang dimiliki oleh atau merujuk pada organisasi lain. Misalnya, pelaksana perangkat tidak boleh menambahkan API ke com.google.* Atau namespace serupa: Hanya Google yang dapat melakukannya. Demikian pula, Google tidak boleh menambahkan API ke ruang nama perusahaan lain.
• [C-0-6] harus dikemas dalam perpustakaan bersama Android sehingga hanya aplikasi yang secara eksplisit menggunakannya (melalui mekanisme <go-library>) yang dipengaruhi oleh peningkatan penggunaan memori API tersebut.

Jika pelaksana perangkat mengusulkan untuk meningkatkan salah satu paket nama di atas (seperti dengan menambahkan fungsionalitas baru yang berguna ke API yang ada, atau menambahkan API baru), pelaksana harus mengunjungi sumber.android.com dan memulai proses untuk menyumbangkan perubahan dan kode, sesuai dengan informasi di situs itu.

Perhatikan bahwa pembatasan di atas sesuai dengan konvensi standar untuk penamaan API dalam bahasa pemrograman Java; Bagian ini hanya bertujuan untuk memperkuat konvensi tersebut dan membuatnya mengikat melalui inklusi dalam definisi kompatibilitas ini.

3.7. Kompatibilitas runtime

Implementasi perangkat:

• [C-0-1] Harus mendukung format Dalvik Executable (DEX) lengkap dan spesifikasi bytecode Dalvik dan semantik .

• [C-0-2] Harus mengkonfigurasi Dalvik RunTimes untuk mengalokasikan memori sesuai dengan platform Android hulu, dan sebagaimana ditentukan oleh tabel berikut. (Lihat Bagian 7.1.1 untuk ukuran layar dan definisi kepadatan layar.)

• Harus menggunakan Android Runtime (ART), implementasi hulu referensi dari format yang dapat dieksekusi Dalvik, dan sistem manajemen paket implementasi referensi.

• Harus menjalankan tes fuzz di bawah berbagai mode eksekusi dan arsitektur target untuk memastikan stabilitas runtime. Lihat JFUZZ dan DEXFUZZ di situs web Proyek Open Source Android.

Perhatikan bahwa nilai memori yang ditentukan di bawah ini dianggap sebagai nilai minimum dan implementasi perangkat dapat mengalokasikan lebih banyak memori per aplikasi.

3.8. Kompatibilitas Antarmuka Pengguna

3.8.1. Peluncur (Layar Beranda)

Android termasuk aplikasi peluncur (layar beranda) dan dukungan untuk aplikasi pihak ketiga untuk menggantikan peluncur perangkat (layar beranda).

Jika implementasi perangkat memungkinkan aplikasi pihak ketiga untuk mengganti layar beranda perangkat, mereka:

• [C-1-1] harus mendeklarasikan fitur platform android.software.home_screen .
• [C-1-2] harus mengembalikan objek AdaptiveIconDrawable ketika aplikasi aplikasi pihak ketiga menggunakan tag <adaptive-icon> untuk memberikan ikon mereka, dan metode PackageManager untuk mengambil ikon yang dipanggil.

Jika implementasi perangkat mencakup peluncur default yang mendukung pinning dalam aplikasi, mereka:

• [C-2-1] Harus melaporkan true untuk ShortcutManager.isRequestPinShortcutSupported() .
• [C-2-2] Harus memiliki keterjangkauan pengguna yang menanyakan pengguna sebelum menambahkan pintasan yang diminta oleh aplikasi melalui metode API ShortcutManager.requestPinShortcut() .
• [C-2-3] Harus mendukung pintasan yang disematkan dan pintasan dinamis dan statis seperti yang didokumentasikan pada halaman pintasan aplikasi .

Sebaliknya, jika implementasi perangkat tidak mendukung pinning dalam aplikasi, mereka:

• [C-3-1] Harus melaporkan false untuk ShortcutManager.isRequestPinShortcutSupported() .

Jika implementasi perangkat mengimplementasikan peluncur default yang menyediakan akses cepat ke pintasan tambahan yang disediakan oleh aplikasi pihak ketiga melalui shortcutManager API, mereka:

• [C-4-1] Harus mendukung semua fitur pintasan yang didokumentasikan (misalnya pintasan statis dan dinamis, menyematkan jalan pintas) dan sepenuhnya mengimplementasikan API kelas API ShortcutManager .

Jika implementasi perangkat menyertakan aplikasi peluncur default yang menunjukkan lencana untuk ikon aplikasi, mereka:

• [C-5-1] harus menghormati metode API NotificationChannel.setShowBadge() . Dengan kata lain, tunjukkan keterjangkauan visual yang terkait dengan ikon aplikasi jika nilainya ditetapkan sebagai true , dan tidak menunjukkan skema lencana ikon aplikasi apa pun ketika semua saluran pemberitahuan aplikasi telah menetapkan nilainya sebagai false .
• Dapat mengesampingkan lencana ikon APP dengan skema lencana eksklusif mereka ketika aplikasi pihak ketiga menunjukkan dukungan dari skema lencana eksklusif melalui penggunaan API berpemilik, tetapi harus menggunakan sumber daya dan nilai yang disediakan melalui pemberitahuan lencana API yang dijelaskan dalam SDK , seperti Notification.Builder.setNumber() dan Notification.Builder.setBadgeIconType() API.

3.8.2. Widget

Android mendukung widget aplikasi pihak ketiga dengan mendefinisikan jenis komponen dan API dan siklus hidup yang sesuai yang memungkinkan aplikasi untuk mengekspos "appwidget" kepada pengguna akhir.

Jika implementasi perangkat mendukung widget aplikasi pihak ketiga, mereka:

• [C-1-1] harus mendeklarasikan dukungan untuk fitur platform android.software.app_widgets .
• [C-1-2] harus menyertakan dukungan bawaan untuk AppWidgets dan mengekspos keterjangkauan antarmuka pengguna untuk menambah, mengkonfigurasi, melihat, dan menghapus AppWidgets secara langsung di dalam peluncur.
• [C-1-3] harus mampu rendering widget yang 4 x 4 dalam ukuran grid standar. Lihat Aplikasi Widget DesignGuidelines dalam dokumentasi Android SDK untuk detailnya.
• Dapat mendukung widget aplikasi di layar kunci.

Jika implementasi perangkat mendukung widget aplikasi pihak ketiga dan pinning pintasan dalam aplikasi, mereka:

• [C-2-1] Harus melaporkan true untuk AppWidgetManager.html.isRequestPinAppWidgetSupported() .
• [C-2-2] Harus memiliki keterjangkauan pengguna yang menanyakan pengguna sebelum menambahkan pintasan yang diminta oleh aplikasi melalui metode API AppWidgetManager.requestPinAppWidget() .

3.8.3. Pemberitahuan

Android termasuk Notification dan NotificationManager API yang memungkinkan pengembang aplikasi pihak ketiga untuk memberi tahu pengguna tentang acara terkenal dan menarik perhatian pengguna menggunakan komponen perangkat keras (misalnya suara, getaran dan cahaya) dan fitur perangkat lunak (misalnya notifikasi notifikasi, bilah sistem) dari perangkat tersebut .

3.8.3.1. Presentasi pemberitahuan

Jika implementasi perangkat memungkinkan aplikasi pihak ketiga untuk memberi tahu pengguna tentang acara terkenal , mereka:

• [C-1-1] harus mendukung pemberitahuan yang menggunakan fitur perangkat keras, seperti yang dijelaskan dalam dokumentasi SDK, dan sejauh mungkin dengan perangkat keras implementasi perangkat. Misalnya, jika implementasi perangkat mencakup vibrator, ia harus mengimplementasikan API getaran dengan benar. Jika implementasi perangkat tidak memiliki perangkat keras, API yang sesuai harus diimplementasikan sebagai no-ops. Perilaku ini lebih rinci dalam Bagian 7 .
• [C-1-2] Harus dengan benar membuat semua sumber daya (ikon, file animasi, dll.) Disediakan untuk di API, atau di Panduan Gaya Ikon Bilah Status/Sistem, meskipun mereka dapat memberikan pengalaman pengguna alternatif untuk pemberitahuan dari itu Disediakan oleh Referensi Implementasi Sumber Terbuka Android.
• [C-1-3] harus menghormati dan menerapkan dengan benar perilaku yang dijelaskan untuk API untuk memperbarui, menghapus dan pemberitahuan kelompok.
• [C-1-4] harus memberikan perilaku penuh dari API NotificationChannel yang didokumentasikan dalam SDK.
• [C-1-5] harus memberikan keterjangkauan pengguna untuk memblokir dan memodifikasi pemberitahuan aplikasi pihak ketiga tertentu per setiap saluran dan level paket aplikasi.
• [C-1-6] juga harus memberikan keterjangkauan pengguna untuk menampilkan saluran pemberitahuan yang dihapus.
• [C-1-7] harus dengan benar membuat semua sumber daya (gambar, stiker, ikon, dll.) Disediakan melalui pemberitahuan. Misalnya, harus menampilkan semua sumber daya termasuk ikon yang disediakan melalui android.app.person dalam percakapan grup yang diatur melalui setGroupConversation .
• [C-SR] sangat disarankan untuk secara otomatis memunculkan keterjangkauan pengguna untuk memblokir pemberitahuan aplikasi pihak ketiga tertentu per setiap saluran dan level paket aplikasi setelah pengguna menolak pemberitahuan itu beberapa kali.
• Harus mendukung pemberitahuan yang kaya.
• Harus menyajikan beberapa pemberitahuan prioritas yang lebih tinggi sebagai pemberitahuan head-up.
• Harus memiliki keterjangkauan pengguna untuk menunda pemberitahuan.
• Hanya dapat mengelola visibilitas dan waktu ketika aplikasi pihak ketiga dapat memberi tahu pengguna tentang acara terkenal untuk mengurangi masalah keselamatan seperti gangguan pengemudi.

Jika implementasi perangkat mendukung pemberitahuan yang kaya, mereka:

• [C-2-1] harus menggunakan sumber daya yang tepat seperti yang disediakan melalui Notification.Style API Class dan subclass-nya untuk elemen sumber daya yang disajikan.
• Harus menyajikan masing -masing dan setiap elemen sumber daya (misalnya ikon, judul dan teks ringkasan) yang didefinisikan dalam kelas API Notification.Style dan subkelasnya.

Jika implementasi perangkat mendukung pemberitahuan head-up: Mereka:

• [C-3-1] harus menggunakan tampilan pemberitahuan dan sumber daya head-up seperti yang dijelaskan dalam Notification.Builder .
• [C-3-2] harus menampilkan tindakan yang disediakan melalui Notification.Builder.addAction() bersama-sama dengan konten pemberitahuan tanpa interaksi pengguna tambahan seperti yang dijelaskan dalam SDK .

3.8.3.2. Layanan pendengar pemberitahuan

Android mencakup API NotificationListenerService yang memungkinkan aplikasi (setelah diaktifkan secara eksplisit oleh pengguna) untuk menerima salinan semua pemberitahuan seperti yang diposting atau diperbarui.

Jika implementasi perangkat melaporkan fitur fitur android.hardware.ram.normal , mereka:

• [C-1-1] harus segera dan segera memperbarui pemberitahuan secara keseluruhan untuk semua layanan pendengar yang diinstal dan pengguna tersebut, termasuk setiap dan semua metadata yang dilampirkan pada objek pemberitahuan.
• [C-1-2] Harus menghormati panggilan API snoozeNotification() , dan mengabaikan pemberitahuan dan melakukan panggilan balik setelah durasi tunda yang ditetapkan dalam panggilan API.

Jika implementasi perangkat memiliki keterjangkauan pengguna untuk menunda pemberitahuan, mereka:

• [C-2-1] harus mencerminkan status pemberitahuan yang tertidur dengan benar melalui API standar seperti NotificationListenerService.getSnoozedNotifications() .
• [C-2-2] harus membuat keterjangkauan pengguna ini tersedia untuk menunda pemberitahuan dari setiap aplikasi pihak ketiga yang diinstal, kecuali mereka berasal dari layanan persisten/latar depan.

3.8.3.3. DND (jangan ganggu)

Jika implementasi perangkat mendukung fitur DND, mereka:

• [C-1-1] harus menerapkan aktivitas yang akan menanggapi intent Action_notification_policy_access_settings , yang untuk implementasi dengan UI_MODE_TYPE_NORMAL itu harus menjadi aktivitas di mana pengguna dapat memberikan atau menolak akses aplikasi ke konfigurasi kebijakan DND.
• [C-1-2] Harus, untuk ketika implementasi perangkat telah menyediakan sarana bagi pengguna untuk memberikan atau menolak aplikasi pihak ketiga untuk mengakses konfigurasi kebijakan DND, menampilkan aturan DND otomatis yang dibuat oleh aplikasi di samping yang dibuat pengguna dan pre aturan -yang ditentukan.
• [C-1-3] Harus menghormati nilai-nilai suppressedVisualEffects yang ditekan di sepanjang NotificationManager.Policy dan jika suatu aplikasi telah menetapkan salah satu dari Suppressed_Effect_Screen_off atau Suppressed_effect_screen_on Flags, itu harus menunjukkan kepada pengguna bahwa efek visual ditekan dalam menu pengaturan DND.

3.8.4. Mencari

Android termasuk API yang memungkinkan pengembang untuk memasukkan pencarian ke dalam aplikasi mereka dan mengekspos data aplikasi mereka ke dalam pencarian sistem global. Secara umum, fungsionalitas ini terdiri dari antarmuka pengguna tunggal, seluruh sistem yang memungkinkan pengguna untuk memasukkan kueri, menampilkan saran sebagai pengguna mengetik, dan menampilkan hasil. API Android memungkinkan pengembang untuk menggunakan kembali antarmuka ini untuk menyediakan pencarian di dalam aplikasi mereka sendiri dan memungkinkan pengembang untuk memasok hasil ke antarmuka pengguna pencarian global umum.

• Implementasi perangkat Android harus mencakup pencarian global, antarmuka pengguna pencarian satu, bersama, yang mampu melakukan saran real-time sebagai tanggapan terhadap input pengguna.

Jika implementasi perangkat mengimplementasikan antarmuka pencarian global, mereka:

• [C-1-1] harus mengimplementasikan API yang memungkinkan aplikasi pihak ketiga untuk menambahkan saran ke kotak pencarian saat dijalankan dalam mode pencarian global.

Jika tidak ada aplikasi pihak ketiga yang diinstal yang memanfaatkan pencarian global:

• Perilaku default harus menampilkan hasil dan saran mesin pencari web.

Android juga mencakup API Assist untuk memungkinkan aplikasi untuk memilih berapa banyak informasi dari konteks saat ini dibagikan dengan asisten pada perangkat.

Jika implementasi perangkat mendukung tindakan bantuan, mereka:

• [C-2-1] harus menunjukkan dengan jelas kepada pengguna akhir ketika konteks dibagikan, baik oleh:
  • Setiap kali aplikasi Assist mengakses konteks, menampilkan lampu putih di sekitar tepi layar yang memenuhi atau melampaui durasi dan kecerahan implementasi proyek open source Android.
  • Untuk aplikasi assist yang diinstal sebelumnya, memberikan keterjangkauan pengguna yang kurang dari dua navigasi dari input suara default dan menu Pengaturan Aplikasi Asisten , dan hanya berbagi konteks ketika aplikasi Assist secara eksplisit dipanggil oleh pengguna melalui HotWord atau Insput Kunci Navigasi Bantuan.
• [C-2-2] Interaksi yang ditunjuk untuk meluncurkan aplikasi Assist seperti yang dijelaskan dalam Bagian 7.2.3 harus meluncurkan aplikasi Assist yang dipilih pengguna, dengan kata lain aplikasi yang mengimplementasikan VoiceInteractionService , atau aktivitas yang menangani niat ACTION_ASSIST .

3.8.5. Peringatan dan bersulang

Aplikasi dapat menggunakan Toast API untuk menampilkan string non-modal pendek kepada pengguna akhir yang menghilang setelah periode waktu yang singkat, dan menggunakan API Type Window TYPE_APPLICATION_OVERLAY untuk menampilkan windows windows sebagai overlay melalui aplikasi lain.

Jika implementasi perangkat menyertakan output layar atau video, mereka:

• [C-1-1] harus memberikan keterjangkauan pengguna untuk memblokir aplikasi dari menampilkan jendela peringatan yang menggunakan TYPE_APPLICATION_OVERLAY . Implementasi AOSP memenuhi persyaratan ini dengan memiliki kontrol dalam naungan pemberitahuan.

• [C-1-2] Harus menghormati API Toast dan menampilkan bersulang dari aplikasi ke pengguna akhir dengan cara yang sangat terlihat.

3.8.6. Tema

Android menyediakan "tema" sebagai mekanisme bagi aplikasi untuk menerapkan gaya di seluruh aktivitas atau aplikasi.

Android termasuk keluarga tema "holo" dan "materi" sebagai satu set gaya yang ditentukan untuk digunakan pengembang aplikasi jika mereka ingin mencocokkan tampilan tema holo dan rasakan seperti yang ditentukan oleh Android SDK.

Jika implementasi perangkat menyertakan output layar atau video, mereka:

• [C-1-1] tidak boleh mengubah atribut tema holo yang terpapar aplikasi.
• [C-1-2] harus mendukung keluarga tema "materi" dan tidak boleh mengubah atribut tema material atau asetnya yang terpapar pada aplikasi.

Android juga mencakup keluarga tema "Deveult Default" sebagai satu set gaya yang ditentukan untuk digunakan pengembang aplikasi jika mereka ingin mencocokkan tampilan dan nuansa tema perangkat sebagaimana didefinisikan oleh pelaksana perangkat.

• Implementasi perangkat dapat memodifikasi atribut tema default perangkat yang terpapar pada aplikasi.

Android mendukung tema varian dengan bilah sistem tembus cahaya, yang memungkinkan pengembang aplikasi untuk mengisi area di belakang status dan bilah navigasi dengan konten aplikasi mereka. Untuk mengaktifkan pengalaman pengembang yang konsisten dalam konfigurasi ini, penting gaya ikon bilah status dipertahankan di berbagai implementasi perangkat.

Jika implementasi perangkat mencakup bilah status sistem, mereka:

• [C-2-1] Harus menggunakan putih untuk ikon status sistem (seperti kekuatan sinyal dan tingkat baterai) dan pemberitahuan yang dikeluarkan oleh sistem, kecuali ikon tersebut menunjukkan status bermasalah atau aplikasi meminta bilah status lampu menggunakan bendera System_UI_FLAG_LIGN_STOTUS_BAR .
• [C-2-2] Implementasi perangkat Android harus mengubah warna ikon status sistem menjadi hitam (untuk detail, lihat R.Style ) ketika aplikasi meminta bilah status lampu.

3.8.7. Wallpaper Hidup

Android mendefinisikan jenis komponen dan API dan siklus hidup yang sesuai yang memungkinkan aplikasi untuk mengekspos satu atau lebih "wallpaper hidup" kepada pengguna akhir. Wallpaper hidup adalah animasi, pola, atau gambar serupa dengan kemampuan input terbatas yang ditampilkan sebagai wallpaper, di belakang aplikasi lain.

Perangkat keras dianggap mampu menjalankan wallpaper langsung jika dapat menjalankan semua wallpaper hidup, tanpa batasan fungsionalitas, pada frame rate yang masuk akal tanpa efek samping pada aplikasi lain. Jika keterbatasan dalam perangkat keras menyebabkan wallpaper dan/atau aplikasi untuk macet, tidak berfungsi, mengonsumsi CPU yang berlebihan atau daya baterai, atau dijalankan dengan laju bingkai rendah yang tidak dapat diterima, perangkat keras dianggap tidak mampu menjalankan wallpaper hidup. Sebagai contoh, beberapa wallpaper hidup dapat menggunakan konteks OpenGL 2.0 atau 3.x untuk membuat konten mereka. Wallpaper langsung tidak akan berjalan dengan andal pada perangkat keras yang tidak mendukung beberapa konteks OpenGL karena penggunaan wallpaper langsung dari konteks OpenGL dapat bertentangan dengan aplikasi lain yang juga menggunakan konteks OpenGL.

• Implementasi perangkat yang mampu menjalankan wallpaper langsung dengan andal seperti yang dijelaskan di atas harus menerapkan wallpaper hidup.

Jika implementasi perangkat mengimplementasikan wallpaper hidup, mereka:

• [C-1-1] Harus melaporkan fitur platform fitur android.software.live_wallpaper.

3.8.8. Switching aktivitas

Kode sumber Android hulu mencakup layar ikhtisar , antarmuka pengguna tingkat sistem untuk pengalihan tugas dan menampilkan aktivitas dan tugas yang baru diakses menggunakan gambar thumbnail dari keadaan grafik aplikasi pada saat pengguna terakhir meninggalkan aplikasi.

Implementasi perangkat termasuk kunci navigasi fungsi RESTS sebagaimana dirinci dalam Bagian 7.2.3 dapat mengubah antarmuka.

Jika implementasi perangkat termasuk tombol navigasi fungsi terkini seperti yang dirinci di bagian 7.2.3 mengubah antarmuka, maka:

• [C-1-1] harus mendukung setidaknya hingga 7 kegiatan yang ditampilkan.
• Setidaknya harus menampilkan judul 4 kegiatan sekaligus.
• [C-1-2] harus mengimplementasikan perilaku pinning layar dan memberi pengguna menu Pengaturan untuk beralih fitur.
• Harus menampilkan warna sorotan, ikon, judul layar dalam resents.
• Harus menampilkan keterjangkauan penutup ("x") tetapi dapat menunda ini sampai pengguna berinteraksi dengan layar.
• Harus menerapkan jalan pintas untuk beralih dengan mudah ke aktivitas sebelumnya.
• Harus memicu aksi switch cepat antara dua aplikasi yang paling baru digunakan, ketika kunci fungsi RESEN disadap dua kali.
• Harus memicu mode multiwindow layar split, jika didukung, ketika tombol fungsi resents sudah lama ditekan.
• Dapat menampilkan resent yang berafiliasi sebagai kelompok yang bergerak bersama.
• [SR] sangat disarankan untuk menggunakan antarmuka pengguna Android hulu (atau antarmuka berbasis thumbnail serupa) untuk layar ikhtisar.

3.8.9. Manajemen Masukan

Android termasuk dukungan untuk manajemen input dan dukungan untuk editor metode input pihak ketiga.

Jika implementasi perangkat memungkinkan pengguna untuk menggunakan metode input pihak ketiga pada perangkat, mereka:

• [C-1-1] harus mendeklarasikan fitur platform android.software.input_methods dan mendukung API IME sebagaimana didefinisikan dalam dokumentasi Android SDK.
• [C-1-2] harus memberikan mekanisme yang dapat diakses pengguna untuk menambah dan mengkonfigurasi metode input pihak ketiga sebagai respons terhadap intent android.settings.input_method_settings.

Jika implementasi perangkat mendeklarasikan bendera fitur android.software.autofill , mereka:

• [C-2-1] harus sepenuhnya mengimplementasikan AutofillService dan AutofillManager API dan menghormati android.settings.REQUEST_SET_AUTOFILL_SERVICE Niat untuk menampilkan menu Pengaturan Aplikasi Default untuk mengaktifkan dan menonaktifkan Autofill dan mengubah layanan Autofill default untuk pengguna.

3.8.10. Kontrol Media Layar Kunci

API Klien Kontrol Jarak Jauh Diusir dari Android 5.0 yang mendukung templat pemberitahuan media yang memungkinkan aplikasi media untuk berintegrasi dengan kontrol pemutaran yang ditampilkan pada layar kunci.

3.8.11. Screen savers (sebelumnya mimpi)

Android mencakup dukungan untuk penyelamat layar interaktif , yang sebelumnya disebut sebagai mimpi. Screen Savers memungkinkan pengguna untuk berinteraksi dengan aplikasi ketika perangkat yang terhubung ke sumber daya menganggur atau merapat di dermaga meja. Perangkat Android Watch dapat menerapkan screen saver, tetapi jenis implementasi perangkat lainnya harus mencakup dukungan untuk penyelamat layar dan menyediakan opsi pengaturan bagi pengguna untuk mengonfigurasi screen saver sebagai respons terhadap intent android.settings.DREAM_SETTINGS .

3.8.12. Lokasi

Jika implementasi perangkat termasuk sensor perangkat keras (misalnya GPS) yang mampu menyediakan koordinat lokasi, mereka

• [C-1-2] Harus menampilkan status lokasi saat ini di menu lokasi dalam pengaturan.
• [C-1-3] Tidak boleh menampilkan mode lokasi di menu lokasi dalam pengaturan.

3.8.13. Unicode dan Font

Android termasuk dukungan untuk karakter emoji yang ditentukan dalam Unicode 10.0 .

Jika implementasi perangkat menyertakan output layar atau video, mereka:

• [C-1-1] harus mampu membuat karakter emoji ini dalam mesin terbang warna.
• [C-1-2] harus menyertakan dukungan untuk:
  • Font Roboto 2 dengan bobot yang berbeda-SANS-SERIF-THIN, SANS-SERIF-LIGHT, SANS-SERIF-MEDIUM, SANS-SERIF-Black, SANS-SERIF-CONDENSED, SANS-SERIF-CONDENSED-LIGHT untuk bahasa yang tersedia di perangkat.
  • Cakupan Latin, Yunani, dan Cyrillic Latin, termasuk Latin yang diperluas Latin, B, C, dan D rentang, dan semua mesin terbang dalam blok simbol mata uang dari Unicode 7.0.
• Harus mendukung warna kulit dan beragam emoji keluarga sebagaimana ditentukan dalam Laporan Teknis Unicode #51 .

Jika implementasi perangkat menyertakan IME, mereka:

• Harus memberikan metode input kepada pengguna untuk karakter emoji ini.

Android termasuk dukungan untuk membuat font Myanmar. Myanmar memiliki beberapa font yang tidak sesuai non-unicode, umumnya dikenal sebagai "Zawgyi," untuk memberikan bahasa Myanmar.

Jika implementasi perangkat termasuk dukungan untuk Burma, mereka:

* [C-2-1] MUST render text with Unicode compliant font as default;
  non-Unicode compliant font MUST NOT be set as default font unless the user
  chooses it in the language picker.
* [C-2-2] MUST support a Unicode font and a non-Unicode compliant font if a
  non-Unicode compliant font is supported on the device.  Non-Unicode
  compliant font MUST NOT remove or overwrite the Unicode font.
* [C-2-3] MUST render text with non-Unicode compliant font ONLY IF a
  language code with [script code Qaag](
  http://unicode.org/reports/tr35/#unicode_script_subtag_validity) is
  specified (e.g. my-Qaag). No other ISO language or region codes (whether
  assigned, unassigned, or reserved) can be used to refer to non-Unicode
  compliant font for Myanmar. App developers and web page authors can
  specify my-Qaag as the designated language code as they would for any
  other language.

3.8.14. Multi-windows

Jika implementasi perangkat memiliki kemampuan untuk menampilkan banyak kegiatan secara bersamaan, mereka:

• [C-1-1] harus mengimplementasikan mode multi-window tersebut sesuai dengan perilaku aplikasi dan API yang dijelaskan dalam Dokumentasi Dukungan Mode Multi-Window Android SDK dan memenuhi persyaratan berikut:
• [C-1-2] Harus menghormati android:resizeableActivity yang ditetapkan oleh aplikasi dalam file AndroidManifest.xml seperti yang dijelaskan dalam SDK ini .
• [C-1-3] tidak boleh menawarkan mode split-screen atau bentuk bebas jika ketinggian layar kurang dari 440 dp dan lebar layar kurang dari 440 dp.
• [C-1-4] Suatu aktivitas tidak boleh diubah ukurannya ke ukuran yang lebih kecil dari 220dp dalam mode multi-window selain gambar-in-picture.
• Implementasi perangkat dengan ukuran layar xlarge harus mendukung mode bentuk bebas.

Jika implementasi perangkat mendukung mode multi-window, dan mode layar split, mereka:

• [C-2-1] Harus memulai peluncur yang dapat diatur ulang sebagai default.
• [C-2-2] Harus memotong aktivitas merapat dari multi-jendela layar terpisah tetapi harus menunjukkan beberapa kontennya, jika aplikasi peluncur adalah jendela yang terfokus.
• [C-2-3] Harus menghormati AndroidManifestLayout_minWidth dan AndroidManifestLayout_minHeight nilai dari aplikasi peluncur pihak ketiga dan tidak mengesampingkan nilai-nilai ini dalam proses menunjukkan beberapa konten dari aktivitas yang berlabuh.

Jika implementasi perangkat mendukung mode multi-window dan mode multi-window gambar-in-picture, mereka:

• [C-3-1] Harus meluncurkan kegiatan dalam mode multi-window gambar-in-picture ketika aplikasi adalah: * menargetkan API level 26 atau lebih tinggi dan menyatakan android:supportsPictureInPicture * Menargetkan API Level 25 atau lebih rendah dan mendeklarasikan kedua android:resizeableActivity dan android:supportsPictureInPicture .
• [C-3-2] harus mengekspos tindakan dalam systemui mereka sebagaimana ditentukan oleh aktivitas PIP saat ini melalui setActions() API.
• [C-3-3] harus mendukung rasio aspek yang lebih besar dari atau sama dengan 1: 2.39 dan kurang dari atau sama dengan 2,39: 1, sebagaimana ditentukan oleh aktivitas PIP melalui API setAspectRatio() .
• [C-3-4] Harus menggunakan KeyEvent.KEYCODE_WINDOW untuk mengontrol jendela PIP; Jika mode PIP tidak diimplementasikan, kunci harus tersedia untuk aktivitas latar depan.
• [C-3-5] harus memberikan keterjangkauan pengguna untuk memblokir aplikasi dari menampilkan dalam mode PIP; Implementasi AOSP memenuhi persyaratan ini dengan memiliki kontrol dalam naungan pemberitahuan.
• [C-3-6] Harus mengalokasikan lebar minimum dan tinggi 108 dp untuk jendela PIP dan lebar minimum 240 dp dan tinggi 135 dp untuk jendela PIP saat Configuration.uiMode dikonfigurasi sebagai UI_MODE_TYPE_TELEVISION .

3.8.15. Potongan Tampilan

Android mendukung potongan tampilan seperti yang dijelaskan dalam dokumen SDK. API DisplayCutout mendefinisikan area di tepi tampilan yang tidak berfungsi untuk menampilkan konten.

Jika implementasi perangkat mencakup potongan tampilan, mereka:

• [C-1-1] hanya harus memiliki potongan pada tepi pendek perangkat. Sebaliknya, jika rasio aspek perangkat adalah 1.0 (1: 1), mereka tidak boleh memiliki potongan.
• [C-1-2] tidak boleh memiliki lebih dari satu potongan per tepi.
• [C-1-3] Harus menghormati bendera potongan tampilan yang ditetapkan oleh aplikasi melalui WindowManager.LayoutParams API seperti yang dijelaskan dalam SDK.
• [C-1-4] Harus melaporkan nilai yang benar untuk semua metrik potongan yang ditentukan dalam API DisplayCutout .

3.9. Administrasi Perangkat

Android mencakup fitur yang memungkinkan aplikasi yang sadar keamanan untuk melakukan fungsi administrasi perangkat di tingkat sistem, seperti menegakkan kebijakan kata sandi atau melakukan penghapusan jarak jauh, melalui API Administrasi Perangkat Android .

Jika implementasi perangkat mengimplementasikan berbagai kebijakan administrasi perangkat yang ditentukan dalam dokumentasi Android SDK, mereka:

• [C-1-1] Harus mendeklarasikan android.software.device_admin .
• [C-1-2] Harus mendukung penyediaan pemilik perangkat seperti yang dijelaskan dalam Bagian 3.9.1 dan Bagian 3.9.1.1 .

3.9.1 Penyediaan Perangkat

3.9.1.1 Penyediaan Pemilik Perangkat

Jika implementasi perangkat mendeklarasikan android.software.device_admin , mereka:

• [C-1-1] Harus mendukung mendaftarkan klien kebijakan perangkat (DPC) sebagai aplikasi pemilik perangkat seperti yang dijelaskan di bawah ini:
  • Ketika implementasi perangkat belum dikonfigurasi, itu: itu:
    • [C-1-3] Harus melaporkan true untuk DevicePolicyManager.isProvisioningAllowed(ACTION_PROVISION_MANAGED_DEVICE) .
    • [C-1-4] Harus mendaftarkan aplikasi DPC sebagai aplikasi pemilik perangkat sebagai respons terhadap tindakan intent android.app.action.PROVISION_MANAGED_DEVICE .
    • [C-1-5] Harus mendaftarkan aplikasi DPC sebagai aplikasi pemilik perangkat jika perangkat mendeklarasikan dukungan Komunikasi dekat-Field (NFC) melalui fitur bendera android.hardware.nfc dan menerima pesan NFC yang berisi catatan dengan tipe MIME_TYPE_PROVISIONING_NFC .
  • Ketika implementasi perangkat memiliki data pengguna, itu:
    • [C-1-6] HARUS melaporkan false untuk DevicePolicyManager.isProvisioningAllowed(ACTION_PROVISION_MANAGED_DEVICE) .
    • [C-1-7] tidak boleh mendaftarkan aplikasi DPC sebagai aplikasi pemilik perangkat lagi.
• [C-1-2] harus memerlukan beberapa tindakan afirmatif selama proses penyediaan untuk menyetujui aplikasi yang ditetapkan sebagai pemilik perangkat. Consent can be via user action or by some programmatic means during provisioning but it MUST NOT be hard coded or prevent the use of other Device Owner apps.

If device implementations declare android.software.device_admin , but also include a proprietary Device Owner management solution and provide a mechanism to promote an application configured in their solution as a "Device Owner equivalent" to the standard "Device Owner" as recognized by the standard Android DevicePolicyManager APIs, they:

• [C-2-1] MUST have a process in place to verify that the specific app being promoted belongs to a legitimate enterprise device management solution and it has been already configured in the proprietary solution to have the rights equivalent as a "Device Owner" .
• [C-2-2] MUST show the same AOSP Device Owner consent disclosure as the flow initiated by android.app.action.PROVISION_MANAGED_DEVICE prior to enrolling the DPC application as "Device Owner".
• MAY have user data on the device prior to enrolling the DPC application as "Device Owner".

3.9.1.2 Managed profile provisioning

If device implementations declare android.software.managed_users , they:

• [C-1-1] MUST implement the APIs allowing a Device Policy Controller (DPC) application to become the owner of a new Managed Profile .

• [C-1-2] The managed profile provisioning process (the flow initiated by android.app.action.PROVISION_MANAGED_PROFILE ) users experience MUST align with the AOSP implementation.

• [C-1-3] MUST provide the following user affordances within the Settings to indicate to the user when a particular system function has been disabled by the Device Policy Controller (DPC):

  • A consistent icon or other user affordance (for example the upstream AOSP info icon) to represent when a particular setting is restricted by a Device Admin.
  • A short explanation message, as provided by the Device Admin via the setShortSupportMessage .
  • The DPC application's icon.

3.9.2 Managed Profile Support

If device implementations declare android.software.managed_users , they:

• [C-1-1] MUST support managed profiles via the android.app.admin.DevicePolicyManager APIs.
• [C-1-2] MUST allow one and only one managed profile to be created .
• [C-1-3] MUST use an icon badge (similar to the AOSP upstream work badge) to represent the managed applications and widgets and other badged UI elements like Recents & Notifications.
• [C-1-4] MUST display a notification icon (similar to the AOSP upstream work badge) to indicate when user is within a managed profile application.
• [C-1-5] MUST display a toast indicating that the user is in the managed profile if and when the device wakes up (ACTION_USER_PRESENT) and the foreground application is within the managed profile.
• [C-1-6] Where a managed profile exists, MUST show a visual affordance in the Intent 'Chooser' to allow the user to forward the intent from the managed profile to the primary user or vice versa, if enabled by the Device Policy Pengendali.
• [C-1-7] Where a managed profile exists, MUST expose the following user affordances for both the primary user and the managed profile:
  • Separate accounting for battery, location, mobile data and storage usage for the primary user and managed profile.
  • Independent management of VPN Applications installed within the primary user or managed profile.
  • Independent management of applications installed within the primary user or managed profile.
  • Independent management of accounts within the primary user or managed profile.
• [C-1-8] MUST ensure the preinstalled dialer, contacts and messaging applications can search for and look up caller information from the managed profile (if one exists) alongside those from the primary profile, if the Device Policy Controller permits it.
• [C-1-9] MUST ensure that it satisfies all the security requirements applicable for a device with multiple users enabled (see section 9.5 ), even though the managed profile is not counted as another user in addition to the primary user.
• [C-1-10] MUST support the ability to specify a separate lock screen meeting the following requirements to grant access to apps running in a managed profile.
  • Device implementations MUST honor the DevicePolicyManager.ACTION_SET_NEW_PASSWORD intent and show an interface to configure a separate lock screen credential for the managed profile.
  • The lock screen credentials of the managed profile MUST use the same credential storage and management mechanisms as the parent profile, as documented on the Android Open Source Project Site .
  • The DPC password policies MUST apply to only the managed profile's lock screen credentials unless called upon the DevicePolicyManager instance returned by getParentProfileInstance .
• When contacts from the managed profile are displayed in the preinstalled call log, in-call UI, in-progress and missed-call notifications, contacts and messaging apps they SHOULD be badged with the same badge used to indicate managed profile applications.

3.9.3 Managed User Support

If device implementations declare android.software.managed_users , they:

• [C-1-1] MUST provide a user affordance to logout from the current user and switch back to the primary user in multiple-user session when isLogoutEnabled returns true . The user affordance MUST be accessible from the lockscreen without unlocking the device.

3.10. Aksesibilitas

Android provides an accessibility layer that helps users with disabilities to navigate their devices more easily. In addition, Android provides platform APIs that enable accessibility service implementations to receive callbacks for user and system events and generate alternate feedback mechanisms, such as text-to-speech, haptic feedback, and trackball/d-pad navigation.

If device implementations support third-party accessibility services, they:

• [C-1-1] MUST provide an implementation of the Android accessibility framework as described in the accessibility APIs SDK documentation.
• [C-1-2] MUST generate accessibility events and deliver the appropriate AccessibilityEvent to all registered AccessibilityService implementations as documented in the SDK.
• [C-1-3] MUST honor the android.settings.ACCESSIBILITY_SETTINGS intent to provide a user-accessible mechanism to enable and disable the third-party accessibility services alongside the preinstalled accessibility services.
• [C-1-4] MUST add a button in the system's navigation bar allowing the user to control the accessibility service when the enabled accessibility services declare the AccessibilityServiceInfo.FLAG_REQUEST_ACCESSIBILITY_BUTTON . Note that for device implementations with no system navigation bar, this requirement is not applicable, but device implementations SHOULD provide a user affordance to control these accessibility services.

If device implementations include preinstalled accessibility services, they:

• [C-2-1] MUST implement these preinstalled accessibility services as Direct Boot Aware apps when the data storage is encrypted with File Based Encryption (FBE).
• SHOULD provide a mechanism in the out-of-box setup flow for users to enable relevant accessibility services, as well as options to adjust the font size, display size and magnification gestures.

3.11. Teks pidato

Android includes APIs that allow applications to make use of text-to-speech (TTS) services and allows service providers to provide implementations of TTS services.

If device implementations reporting the feature android.hardware.audio.output, they:

• [C-1-1] MUST support the Android TTS framework APIs.

If device implementations support installation of third-party TTS engines, they:

• [C-2-1] MUST provide user affordance to allow the user to select a TTS engine for use at system level.

3.12. TV Input Framework

The Android Television Input Framework (TIF) simplifies the delivery of live content to Android Television devices. TIF provides a standard API to create input modules that control Android Television devices.

If device implementations support TIF, they:

• [C-1-1] MUST declare the platform feature android.software.live_tv .
• [C-1-2] MUST support all TIF APIs such that an application which uses these APIs and the third-party TIF-based inputs service can be installed and used on the device.

3.13. Pengaturan Cepat

Android provides a Quick Settings UI component that allows quick access to frequently used or urgently needed actions.

If device implementations include a Quick Settings UI component, they:

• [C-1-1] MUST allow the user to add or remove the tiles provided through the quicksettings APIs from a third-party app.
• [C-1-2] MUST NOT automatically add a tile from a third-party app directly to the Quick Settings.
• [C-1-3] MUST display all the user-added tiles from third-party apps alongside the system-provided quick setting tiles.

3.14. Media UI

If device implementations include non-voice-activated applications (the Apps) that interact with third-party applications through MediaBrowser or MediaSession , the Apps:

• [C-1-2] MUST clearly display icons obtained via getIconBitmap() or getIconUri() and titles obtained via getTitle() as described in MediaDescription . May shorten titles to comply with safety regulations (eg driver distraction).

• [C-1-3] MUST show the third-party application icon whenever displaying content provided by this third-party application.

• [C-1-4] MUST allow the user to interact with the entire MediaBrowser hierarchy. MAY restrict the access to part of the hierarchy to comply with safety regulations (eg driver distraction), but MUST NOT give preferential treatment based on content or content provider.

• [C-1-5] MUST consider double tap of KEYCODE_HEADSETHOOK or KEYCODE_MEDIA_PLAY_PAUSE as KEYCODE_MEDIA_NEXT for MediaSession.Callback#onMediaButtonEvent .

3.15. Aplikasi Instan

Device implementations MUST satisfy the following requirements:

• [C-0-1] Instant Apps MUST only be granted permissions that have the android:protectionLevel set to "instant" .
• [C-0-2] Instant Apps MUST NOT interact with installed apps via implicit intents unless one of the following is true:
  • The component's intent pattern filter is exposed and has CATEGORY_BROWSABLE
  • The action is one of ACTION_SEND, ACTION_SENDTO, ACTION_SEND_MULTIPLE
  • The target is explicitly exposed with android:visibleToInstantApps
• [C-0-3] Instant Apps MUST NOT interact explicitly with installed apps unless the component is exposed via android:visibleToInstantApps.
• [C-0-4] Installed Apps MUST NOT see details about Instant Apps on the device unless the Instant App explicitly connects to the installed application.
• Device implementations MUST provide the following user affordances for interacting with Instant Apps. The AOSP meets the requirements with the default System UI, Settings, and Launcher. Implementasi perangkat:
  • [C-0-5] MUST provide a user affordance to view and delete Instant Apps locally cached for each individual app package.
  • [C-0-6] MUST provide a persistent user notification that can be collapsed while an Instant App is running in the foreground. This user notification MUST include that Instant Apps do not require installation and provide a user affordance that directs the user to the application info screen in Settings. For Instant Apps launched via web intents, as defined by using an intent with action set to Intent.ACTION_VIEW and with a scheme of "http" or "https", an additional user affordance SHOULD allow the user not to launch the Instant App and launch the associated link with the configured web browser, if a browser is available on the device.
  • [C-0-7] MUST allow running Instant Apps to be accessed from the Recents function if the Recents function is available on the device.

3.16. Companion Device Pairing

Android includes support for companion device pairing to more effectively manage association with companion devices and provides the CompanionDeviceManager API for apps to access this feature.

If device implementations support the companion device pairing feature, they:

• [C-1-1] MUST declare the feature flag FEATURE_COMPANION_DEVICE_SETUP .
• [C-1-2] MUST ensure the APIs in the android.companion package is fully implemented.
• [C-1-3] MUST provide user affordances for the user to select/confirm a companion device is present and operational.

3.17. Heavyweight Apps

If device implementations declare the feature FEATURE_CANT_SAVE_STATE , then they:

• [C-1-1] MUST have only one installed app that specifies cantSaveState running in the system at a time. If the user leaves such an app without explicitly exiting it (for example by pressing home while leaving an active activity the system, instead of pressing back with no remaining active activities in the system), then device implementations MUST prioritize that app in RAM as they do for other things that are expected to remain running, such as foreground services. While such an app is in the background, the system can still apply power management features to it, such as limiting CPU and network access.
• [C-1-2] MUST provide a UI affordance to chose the app that won't participate in the normal state save/restore mechanism once the user launches a second app declared with cantSaveState attribute.
• [C-1-3] MUST NOT apply other changes in policy to apps that specify cantSaveState , such as changing CPU performance or changing scheduling prioritization.

If device implementations don't declare the feature FEATURE_CANT_SAVE_STATE , then they:

• [C-1-1] MUST ignore the cantSaveState attribute set by apps and MUST NOT change the app behavior based on that attribute.

4. Application Packaging Compatibility

Devices implementations:

• [C-0-1] MUST be capable of installing and running Android “.apk” files as generated by the “aapt” tool included in the official Android SDK .
• As the above requirement may be challenging, device implementations are RECOMMENDED to use the AOSP reference implementation's package management system.

Implementasi perangkat:

• [C-0-2] MUST support verifying “.apk” files using the APK Signature Scheme v3 , APK Signature Scheme v2 and JAR signing .
• [C-0-3] MUST NOT extend either the .apk , Android Manifest , Dalvik bytecode , or RenderScript bytecode formats in such a way that would prevent those files from installing and running correctly on other compatible devices.

• [C-0-4] MUST NOT allow apps other than the current "installer of record" for the package to silently uninstall the app without any user confirmation, as documented in the SDK for the DELETE_PACKAGE permission. The only exceptions are the system package verifier app handling PACKAGE_NEEDS_VERIFICATION intent and the storage manager app handling ACTION_MANAGE_STORAGE intent.

• [C-0-5] MUST have an activity that handles the android.settings.MANAGE_UNKNOWN_APP_SOURCES intent.

• [C-0-6] MUST NOT install application packages from unknown sources, unless the app that requests the installation meets all the following requirements:

  • It MUST declare the REQUEST_INSTALL_PACKAGES permission or have the android:targetSdkVersion set at 24 or lower.
  • It MUST have been granted permission by the user to install apps from unknown sources.

• SHOULD provide a user affordance to grant/revoke the permission to install apps from unknown sources per application, but MAY choose to implement this as a no-op and return RESULT_CANCELED for startActivityForResult() , if the device implementation does not want to allow users to have this choice. However, even in such cases, they SHOULD indicate to the user why there is no such choice presented.

• [C-0-7] MUST display a warning dialog with the warning string that is provided through the system API PackageManager.setHarmfulAppWarning to the user before launching an activity in an application that has been marked by the same system API PackageManager.setHarmfulAppWarning as potentially berbahaya.

• SHOULD provide a user affordance to choose to uninstall or launch an application on the warning dialog.

5. Multimedia Compatibility

Implementasi perangkat:

• [C-0-1] MUST support the media formats, encoders, decoders, file types, and container formats defined in section 5.1 for each and every codec declared by MediaCodecList .
• [C-0-2] MUST declare and report support of the encoders, decoders available to third-party applications via MediaCodecList .
• [C-0-3] MUST be able to properly decode and make available to third-party apps all the formats it can encode. This includes all bitstreams that its encoders generate and the profiles reported in its CamcorderProfile .

Implementasi perangkat:

• SHOULD aim for minimum codec latency, in others words, they
  • SHOULD NOT consume and store input buffers and return input buffers only once processed.
  • SHOULD NOT hold onto decoded buffers for longer than as specified by the standard (eg SPS).
  • SHOULD NOT hold onto encoded buffers longer than required by the GOP structure.

All of the codecs listed in the section below are provided as software implementations in the preferred Android implementation from the Android Open Source Project.

Please note that neither Google nor the Open Handset Alliance make any representation that these codecs are free from third-party patents. Those intending to use this source code in hardware or software products are advised that implementations of this code, including in open source software or shareware, may require patent licenses from the relevant patent holders.

5.1. Codec Media

5.1.1. Pengkodean Audio

See more details in 5.1.3. Audio Codecs Details .

If device implementations declare android.hardware.microphone , they MUST support encoding the following audio formats and make them available to third-party apps:

• [C-1-1] PCM/WAVE
• [C-1-2] FLAC
• [C-1-3] Opus

All audio encoders MUST support:

• [C-3-1] PCM 16-bit native byte order audio frames via the android.media.MediaCodec API.

5.1.2. Audio Decoding

See more details in 5.1.3. Audio Codecs Details .

If device implementations declare support for the android.hardware.audio.output feature, they MUST support decoding the following audio formats:

• [C-1-1] MPEG-4 AAC Profile (AAC LC)
• [C-1-2] MPEG-4 HE AAC Profile (AAC+)
• [C-1-3] MPEG-4 HE AACv2 Profile (enhanced AAC+)
• [C-1-4] AAC ELD (enhanced low delay AAC)
• [C-1-11] xHE-AAC (ISO/IEC 23003-3 Extended HE AAC Profile, which includes the USAC Baseline Profile, and ISO/IEC 23003-4 Dynamic Range Control Profile)
• [C-1-5] FLAC
• [C-1-6] MP3
• [C-1-7] MIDI
• [C-1-8] Vorbis
• [C-1-9] PCM/WAVE including high-resolution audio formats up to 24 bits, 192 kHz sample rate, and 8 channels. Note that this requirement is for decoding only, and that a device is permitted to downsample and downmix during the playback phase.
• [C-1-10] Opus

If device implementations support the decoding of AAC input buffers of multichannel streams (ie more than two channels) to PCM through the default AAC audio decoder in the android.media.MediaCodec API, the following MUST be supported:

• [C-2-1] Decoding MUST be performed without downmixing (eg a 5.0 AAC stream MUST be decoded to five channels of PCM, a 5.1 AAC stream MUST be decoded to six channels of PCM).
• [C-2-2] Dynamic range metadata MUST be as defined in "Dynamic Range Control (DRC)" in ISO/IEC 14496-3, and the android.media.MediaFormat DRC keys to configure the dynamic range-related behaviors of the audio decoder. The AAC DRC keys were introduced in API 21, and are: KEY_AAC_DRC_ATTENUATION_FACTOR , KEY_AAC_DRC_BOOST_FACTOR , KEY_AAC_DRC_HEAVY_COMPRESSION , KEY_AAC_DRC_TARGET_REFERENCE_LEVEL and KEY_AAC_ENCODED_TARGET_LEVEL .
• [SR] It is STRONGLY RECOMMENDED that requirements C-2-1 and C-2-2 above are satisfied by all AAC audio decoders.

When decoding USAC audio, MPEG-D (ISO/IEC 23003-4):

• [C-3-1] Loudness and DRC metadata MUST be interpreted and applied according to MPEG-D DRC Dynamic Range Control Profile Level 1.
• [C-3-2] The decoder MUST behave according to the configuration set with the following android.media.MediaFormat keys: KEY_AAC_DRC_TARGET_REFERENCE_LEVEL and KEY_AAC_DRC_EFFECT_TYPE .

MPEG-4 AAC, HE AAC, and HE AACv2 profile decoders:

• MAY support loudness and dynamic range control using ISO/IEC 23003-4 Dynamic Range Control Profile.

If ISO/IEC 23003-4 is supported and if both ISO/IEC 23003-4 and ISO/IEC 14496-3 metadata are present in a decoded bitstream, then:

• ISO/IEC 23003-4 metadata SHALL take precedence.

All audio decoders MUST support outputting:

• [C-6-1] PCM 16-bit native byte order audio frames via the android.media.MediaCodec API.

5.1.3. Audio Codecs Details

5.1.4. Image Encoding

See more details in 5.1.6. Image Codecs Details .

Device implementations MUST support encoding the following image encoding:

• [C-0-1] JPEG
• [C-0-2] PNG
• [C-0-3] WebP

If device implementations support HEIC encoding via android.media.MediaCodec for media type MIMETYPE_IMAGE_ANDROID_HEIC , they:

• [C-1-1] MUST provide a hardware-accelerated HEVC encoder codec that supports BITRATE_MODE_CQ bitrate control mode, HEVCProfileMainStill profile and 512 x 512 px frame size.

5.1.5. Image Decoding

See more details in 5.1.6. Image Codecs Details .

Device implementations MUST support decoding the following image encoding:

• [C-0-1] JPEG
• [C-0-2] GIF
• [C-0-3] PNG
• [C-0-4] BMP
• [C-0-5] WebP
• [C-0-6] Raw
• [C-0-7] HEIF (HEIC)

Image decoders that support a high bit-depth format (9+ bits per channel)

• [C-1-1] MUST support outputting an 8-bit equivalent format if requested by the application, for example, via the ARGB_8888 config of android.graphics.Bitmap .

5.1.6. Image Codecs Details

Image encoder and decoders exposed through the MediaCodec API

• [C-1-1] MUST support YUV420 8:8:8 flexible color format ( COLOR_FormatYUV420Flexible ) through CodecCapabilities .

• [SR] STRONGLY RECOMMENDED to support RGB888 color format for input Surface mode.

• [C-1-3] MUST support at least one of a planar or semiplanar YUV420 8:8:8 color format: COLOR_FormatYUV420PackedPlanar (equivalent to COLOR_FormatYUV420Planar ) or COLOR_FormatYUV420PackedSemiPlanar (equivalent to COLOR_FormatYUV420SemiPlanar ). They are STRONGLY RECOMMENDED to support both.

5.1.7. Codec Video

• For acceptable quality of web video streaming and video-conference services, device implementations SHOULD use a hardware VP8 codec that meets the requirements .

If device implementations include a video decoder or encoder:

• [C-1-1] Video codecs MUST support output and input bytebuffer sizes that accommodate the largest feasible compressed and uncompressed frame as dictated by the standard and configuration but also not overallocate.

• [C-1-2] Video encoders and decoders MUST support YUV420 8:8:8 flexible color formats ( COLOR_FormatYUV420Flexible ) through CodecCapabilities .

• [C-1-3] Video encoders and decoders MUST support at least one of a planar or semiplanar YUV420 8:8:8 color format: COLOR_FormatYUV420PackedPlanar (equivalent to COLOR_FormatYUV420Planar ) or COLOR_FormatYUV420PackedSemiPlanar (equivalent to COLOR_FormatYUV420SemiPlanar ). They are STRONGLY RECOMMENDED to support both.

• [SR] Video encoders and decoders are STRONGLY RECOMMENDED to support at least one of a hardware optimized planar or semiplanar YUV420 8:8:8 color format (YV12, NV12, NV21 or equivalent vendor optimized format.)

• [C-1-5] Video decoders that support a high bit-depth format (9+ bits per channel) MUST support outputting an 8-bit equivalent format if requested by the application. This MUST be reflected by supporting an YUV420 8:8:8 color format via android.media.MediaCodecInfo .

If device implementations advertise HDR profile support through Display.HdrCapabilities , they:

• [C-2-1] MUST support HDR static metadata parsing and handling.

If device implementations advertise intra refresh support through FEATURE_IntraRefresh in the MediaCodecInfo.CodecCapabilities class, they:

• [C-3-1] MUST support the refresh periods in the range of 10 - 60 frames and accurately operate within 20% of configured refresh period.

Unless the application specifies otherwise using the KEY_COLOR_FORMAT format key, video decoder implementations:

• [C-4-1] MUST default to the color format optimized for hardware display if configured using Surface output.
• [C-4-2] MUST default to a YUV420 8:8:8 color format optimized for CPU reading if configured to not use Surface output.

5.1.8. Video Codecs List

5.1.9. Media Codec Security

Device implementations MUST ensure compliance with media codec security features as described below.

Android includes support for OMX, a cross-platform multimedia acceleration API, as well as Codec 2.0, a low-overhead multimedia acceleration API.

If device implementations support multimedia, they:

• [C-1-1] MUST provide support for media codecs either via OMX or Codec 2.0 APIs (or both) as in the Android Open Source Project and not disable or circumvent the security protections. This specifically does not mean that every codec MUST use either the OMX or Codec 2.0 API, only that support for at least one of these APIs MUST be available, and support for the available APIs MUST include the security protections present.
• [C-SR] Are STRONGLY RECOMMENDED to include support for Codec 2.0 API.

If device implementations do not support the Codec 2.0 API, they:

• [C-2-1] MUST include the corresponding OMX software codec from the Android Open Source Project (if it is available) for each media format and type (encoder or decoder) supported by the device.
• [C-2-2] Codecs that have names starting with "OMX.google." MUST be based on their Android Open Source Project source code.
• [C-SR] Are STRONGLY RECOMMENDED that the OMX software codecs run in a codec process that does not have access to hardware drivers other than memory mappers.

If device implementations support Codec 2.0 API, they:

• [C-3-1] MUST include the corresponding Codec 2.0 software codec from the Android Open Source Project (if it is available) for each media format and type (encoder or decoder) supported by the device.
• [C-3-2] MUST house the Codec 2.0 software codecs in the software codec process as provided in the Android Open Source Project to make it possible to more narrowly grant access to software codecs.
• [C-3-3] Codecs that have names starting with "c2.android." MUST be based on their Android Open Source Project source code.

5.1.10. Media Codec Characterization

If device implementations support media codecs, they:

• [C-1-1] MUST return correct values of media codec characterization via the MediaCodecInfo API.

Secara khusus:

• [C-1-2] Codecs with names starting with "OMX." MUST use the OMX APIs and have names that conform to OMX IL naming guidelines.
• [C-1-3] Codecs with names starting with "c2." MUST use the Codec 2.0 API and have names that conform to Codec 2.0 naming guidelines for Android.
• [C-1-4] Codecs with names starting with "OMX.google." or "c2.android." MUST NOT be characterized as vendor or as hardware-accelerated.
• [C-1-5] Codecs that run in a codec process (vendor or system) that have access to hardware drivers other than memory allocators and mappers MUST NOT be characterized as software-only.
• [C-1-6] Codecs not present in the Android Open Source Project or not based on the source code in that project MUST be characterized as vendor.
• [C-1-7] Codecs that utilize hardware acceleration MUST be characterized as hardware accelerated.
• [C-1-8] Codec names MUST NOT be misleading. For example, codecs named "decoders" MUST support decoding, and those named "encoders" MUST support encoding. Codecs with names containing media formats MUST support those formats.

If device implementations support video codecs:

• [C-2-1] All video codecs MUST publish achievable frame rate data for the following sizes if supported by the codec:

• [C-2-2] Video codecs that are characterized as hardware accelerated MUST publish performance points information. They MUST each list all supported standard performance points (listed in PerformancePoint API), unless they are covered by another supported standard performance point.
• Additionally they SHOULD publish extended performance points if they support sustained video performance other than one of the standard ones listed.

5.2. Pengkodean Video

If device implementations support any video encoder and make it available to third-party apps, they:

• SHOULD NOT be, over two sliding windows, more than 15% over the bitrate between intraframe (I-frame) intervals.
• SHOULD NOT be more than 100% over the bitrate over a sliding window of 1 second.

If device implementations include an embedded screen display with the diagonal length of at least 2.5 inches or include a video output port or declare the support of a camera via the android.hardware.camera.any feature flag, they:

• [C-1-1] MUST include the support of at least one of the VP8 or H.264 video encoders, and make it available for third-party applications.
• SHOULD support both VP8 and H.264 video encoders, and make it available for third-party applications.

If device implementations support any of the H.264, VP8, VP9 or HEVC video encoders and make it available to third-party applications, they:

• [C-2-1] MUST support dynamically configurable bitrates.
• SHOULD support variable frame rates, where video encoder SHOULD determine instantaneous frame duration based on the timestamps of input buffers, and allocate its bit bucket based on that frame duration.

If device implementations support the MPEG-4 SP video encoder and make it available to third-party apps, they:

• SHOULD support dynamically configurable bitrates for the supported encoder.

If device implementations provide hardware accelerated video or image encoders, and support one or more attached or pluggable hardware camera(s) exposed through the android.camera APIs:

• [C-4-1] all hardware accelerated video and image encoders MUST support encoding frames from the hardware camera(s).
• SHOULD support encoding frames from the hardware camera(s) through all video or image encoders.

5.2.1. H.263

If device implementations support H.263 encoders and make it available to third-party apps, they:

• [C-1-1] MUST support Baseline Profile Level 45.
• SHOULD support dynamically configurable bitrates for the supported encoder.

5.2.2. H.264

If device implementations support H.264 codec, they:

• [C-1-1] MUST support Baseline Profile Level 3. However, support for ASO (Arbitrary Slice Ordering), FMO (Flexible Macroblock Ordering) and RS (Redundant Slices) is OPTIONAL. Moreover, to maintain compatibility with other Android devices, it is RECOMMENDED that ASO, FMO and RS are not used for Baseline Profile by encoders.
• [C-1-2] MUST support the SD (Standard Definition) video encoding profiles in the following table.
• SHOULD support Main Profile Level 4.
• SHOULD support the HD (High Definition) video encoding profiles as indicated in the following table.

If device implementations report support of H.264 encoding for 720p or 1080p resolution videos through the media APIs, they:

• [C-2-1] MUST support the encoding profiles in the following table.

5.2.3. Wakil Presiden8

If device implementations support VP8 codec, they:

• [C-1-1] MUST support the SD video encoding profiles.
• SHOULD support the following HD (High Definition) video encoding profiles.
• [C-1-2] MUST support writing Matroska WebM files.
• SHOULD provide a hardware VP8 codec that meets the WebM project RTC hardware coding requirements , to ensure acceptable quality of web video streaming and video-conference services.

If device implementations report support of VP8 encoding for 720p or 1080p resolution videos through the media APIs, they:

• [C-2-1] MUST support the encoding profiles in the following table.

5.2.4. Wakil Presiden9

If device implementations support VP9 codec, they:

• [C-1-2] MUST support Profile 0 Level 3.
• [C-1-1] MUST support writing Matroska WebM files.
• [C-1-3] MUST generate CodecPrivate data.
• SHOULD support the HD decoding profiles as indicated in the following table.
• [SR] are STRONGLY RECOMMENDED to support the HD decoding profiles as indicated in the following table if there is a hardware encoder.

If device implementations claim to support Profile 2 or Profile 3 through the Media APIs:

• Support for 12-bit format is OPTIONAL.

5.2.5. H.265

If device implementations support H.265 codec, they:

• [C-1-1] MUST support Main Profile Level 3.
• SHOULD support the HD encoding profiles as indicated in the following table.
• [SR] are STRONGLY RECOMMENDED to support the HD encoding profiles as indicated in the following table if there is a hardware encoder.

5.3. Penguraian Video

If device implementations support VP8, VP9, H.264, or H.265 codecs, they:

• [C-1-1] MUST support dynamic video resolution and frame rate switching through the standard Android APIs within the same stream for all VP8, VP9, H.264, and H.265 codecs in real time and up to the maximum resolution supported by each codec on the device.

5.3.1. MPEG-2

If device implementations support MPEG-2 decoders, they:

• [C-1-1] MUST support the Main Profile High Level.

5.3.2. H.263

If device implementations support H.263 decoders, they:

• [C-1-1] MUST support Baseline Profile Level 30 and Level 45.

5.3.3. MPEG-4

If device implementations with MPEG-4 decoders, they:

• [C-1-1] MUST support Simple Profile Level 3.

5.3.4. H.264

If device implementations support H.264 decoders, they:

• [C-1-1] MUST support Main Profile Level 3.1 and Baseline Profile. Support for ASO (Arbitrary Slice Ordering), FMO (Flexible Macroblock Ordering) and RS (Redundant Slices) is OPTIONAL.
• [C-1-2] MUST be capable of decoding videos with the SD (Standard Definition) profiles listed in the following table and encoded with the Baseline Profile and Main Profile Level 3.1 (including 720p30).
• SHOULD be capable of decoding videos with the HD (High Definition) profiles as indicated in the following table.

If the height that is reported by the Display.getSupportedModes() method is equal or greater than the video resolution, device implementations:

• [C-2-1] MUST support the HD 720p video decoding profiles in the following table.
• [C-2-2] MUST support the HD 1080p video decoding profiles in the following table.

5.3.5. H.265 (HEVC)

If device implementations support H.265 codec, they:

• [C-1-1] MUST support the Main Profile Level 3 Main tier and the SD video decoding profiles as indicated in the following table.
• SHOULD support the HD decoding profiles as indicated in the following table.
• [C-1-2] MUST support the HD decoding profiles as indicated in the following table if there is a hardware decoder.

If the height that is reported by the Display.getSupportedModes() method is equal to or greater than the video resolution, then:

• [C-2-1] Device implementations MUST support at least one of H.265 or VP9 decoding of 720, 1080 and UHD profiles.

If device implementations claim to support an HDR Profile ( HEVCProfileMain10HDR10 , HEVCProfileMain10HDR10Plus ) through the Media APIs:

• [C-3-1] Device implementations MUST accept the required HDR metadata ( MediaFormat#KEY_HDR_STATIC_INFO for all HDR profiles) from the application using MediaCodec API, as well as support extracting the required HDR metadata ( MediaFormat#KEY_HDR_STATIC_INFO for all HDR profiles, as well as MediaFormat#KEY_HDR10_PLUS_INFO for HDR10Plus profiles) from the bitstream and/or container as defined by the relevant specifications. They MUST also support outputting the required HDR metadata ( MediaFormat#KEY_HDR_STATIC_INFO for all HDR profiles) from the bitstream and/or container as defined by the relevant specifications.

• [C-SR] The device implementations are STRONGLY RECOMMENDED to support outputting the metadata MediaFormat#KEY_HDR10_PLUS_INFO for HDR10Plus profiles via MediaCodec#getOutputFormat(int) .

• [C-3-2] Device implementations MUST properly display HDR content for HEVCProfileMain10HDR10 profile on the device screen or on a standard video output port (eg, HDMI).

• [C-SR] Device implementations are STRONGLY RECOMMENDED to properly display HDR content for HEVCProfileMain10HDR10Plus profile on the device screen or on a standard video output port (eg, HDMI).

5.3.6. Wakil Presiden8

If device implementations support VP8 codec, they:

• [C-1-1] MUST support the SD decoding profiles in the following table.
• SHOULD use a hardware VP8 codec that meets the requirements .
• SHOULD support the HD decoding profiles in the following table.

If the height as reported by the Display.getSupportedModes() method is equal or greater than the video resolution, then:

• [C-2-1] Device implementations MUST support 720p profiles in the following table.
• [C-2-2] Device implementations MUST support 1080p profiles in the following table.

5.3.7. Wakil Presiden9

If device implementations support VP9 codec, they:

• [C-1-1] MUST support the SD video decoding profiles as indicated in the following table.
• SHOULD support the HD decoding profiles as indicated in the following table.

If device implementations support VP9 codec and a hardware decoder:

• [C-2-1] MUST support the HD decoding profiles as indicated in the following table.

If the height that is reported by the Display.getSupportedModes() method is equal to or greater than the video resolution, then:

• [C-3-1] Device implementations MUST support at least one of VP9 or H.265 decoding of the 720, 1080 and UHD profiles.

If device implementations claim to support VP9Profile2 or VP9Profile3 through the 'CodecProfileLevel' media APIs:

• Support for 12-bit format is OPTIONAL.

If device implementations claim to support an HDR Profile ( VP9Profile2HDR , VP9Profile2HDR10Plus , VP9Profile3HDR , VP9Profile3HDR10Plus ) through the media APIs:

• [C-4-1] Device implementations MUST accept the required HDR metadata ( MediaFormat#KEY_HDR_STATIC_INFO for all HDR profiles, as well as parameter MediaCodec#PARAMETER_KEY_HDR10_PLUS_INFO for HDR10Plus profiles) from the application using MediaCodec API, as well as support extracting the required HDR metadata ( MediaFormat#KEY_HDR_STATIC_INFO for all HDR profiles, as well as MediaFormat#KEY_HDR10_PLUS_INFO for HDR10Plus profiles) from the bitstream and/or container as defined by the relevant specifications. They MUST also support outputting the required HDR metadata ( MediaFormat#KEY_HDR_STATIC_INFO for all HDR profiles) from the bitstream and/or container as defined by the relevant specifications.

• [C-4-2] Device implementations MUST properly display HDR content for VP9Profile2HDR and VP9Profile3HDR profiles on the device screen or on a standard video output port (eg, HDMI).

• [C-SR] The device implementations are STRONGLY RECOMMENDED to support outputting the metadata MediaFormat#KEY_HDR10_PLUS_INFO for HDR10Plus profiles via MediaCodec#getOutputFormat(int) .

• [C-SR] Device implementations are STRONGLY RECOMMENDED to properly display HDR content for VP9Profile2HDR10Plus and VP9Profile3HDR10Plus profiles on the device screen or on a standard video output port (eg, HDMI).

5.3.8. Visi Dolby

If device implementations declare support for the Dolby Vision decoder through HDR_TYPE_DOLBY_VISION , they:

• [C-1-1] MUST provide a Dolby Vision-capable extractor.
• [C-1-2] MUST properly display Dolby Vision content on the device screen or on a standard video output port (eg, HDMI).
• [C-1-3] MUST set the track index of backward-compatible base-layer(s) (if present) to be the same as the combined Dolby Vision layer's track index.

5.3.9. AV1

If device implementations support AV1 codec, they:

• [C-1-1] MUST support Profile 0 including 10-bit content.

5.4. Rekaman audio

While some of the requirements outlined in this section are listed as SHOULD since Android 4.3, the Compatibility Definition for future versions are planned to change these to MUST. Existing and new Android devices are STRONGLY RECOMMENDED to meet these requirements that are listed as SHOULD, or they will not be able to attain Android compatibility when upgraded to the future version.

5.4.1. Raw Audio Capture and Microphone Information

If device implementations declare android.hardware.microphone , they:

• [C-1-1] MUST allow capture of raw audio content with the following characteristics:

  • Format : Linear PCM, 16-bit
  • Sampling rates : 8000, 11025, 16000, 44100, 48000 Hz
  • Channels : Mono

• SHOULD allow capture of raw audio content with the following characteristics:

  • Format : Linear PCM, 16-bit and 24-bit
  • Sampling rates : 8000, 11025, 16000, 22050, 24000, 32000, 44100, 48000 Hz
  • Channels : As many channels as the number of microphones on the device

• [C-1-2] MUST capture at above sample rates without up-sampling.

• [C-1-3] MUST include an appropriate anti-aliasing filter when the sample rates given above are captured with down-sampling.

• SHOULD allow AM radio and DVD quality capture of raw audio content, which means the following characteristics:

  • Format : Linear PCM, 16-bit
  • Sampling rates : 22050, 48000 Hz
  • Channels : Stereo

• [C-1-4] MUST honor the MicrophoneInfo API and properly fill in information for the available microphones on device accessible to the third-party applications via the AudioManager.getMicrophones() API, and the currently active microphones which are accessible to the third party applications via the AudioRecord.getActiveMicrophones() and MediaRecorder.getActiveMicrophones() APIs. If device implementations allow AM radio and DVD quality capture of raw audio content, they:

• [C-2-1] MUST capture without up-sampling at any ratio higher than 16000:22050 or 44100:48000.

• [C-2-2] MUST include an appropriate anti-aliasing filter for any up-sampling or down-sampling.

5.4.2. Capture for Voice Recognition

If device implementations declare android.hardware.microphone , they:

• [C-1-1] MUST capture android.media.MediaRecorder.AudioSource.VOICE_RECOGNITION audio source at one of the sampling rates, 44100 and 48000.
• [C-1-2] MUST, by default, disable any noise reduction audio processing when recording an audio stream from the AudioSource.VOICE_RECOGNITION audio source.
• [C-1-3] MUST, by default, disable any automatic gain control when recording an audio stream from the AudioSource.VOICE_RECOGNITION audio source.
• SHOULD record the voice recognition audio stream with approximately flat amplitude versus frequency characteristics: specifically, ±3 dB, from 100 Hz to 4000 Hz.
• SHOULD record the voice recognition audio stream with input sensitivity set such that a 90 dB sound power level (SPL) source at 1000 Hz yields RMS of 2500 for 16-bit samples.
• SHOULD record the voice recognition audio stream so that the PCM amplitude levels linearly track input SPL changes over at least a 30 dB range from -18 dB to +12 dB re 90 dB SPL at the microphone.
• SHOULD record the voice recognition audio stream with total harmonic distortion (THD) less than 1% for 1 kHz at 90 dB SPL input level at the microphone.

If device implementations declare android.hardware.microphone and noise suppression (reduction) technologies tuned for speech recognition, they:

• [C-2-1] MUST allow this audio effect to be controllable with the android.media.audiofx.NoiseSuppressor API.
• [C-2-2] MUST uniquely identify each noise suppression technology implementation via the AudioEffect.Descriptor.uuid field.

5.4.3. Capture for Rerouting of Playback

The android.media.MediaRecorder.AudioSource class includes the REMOTE_SUBMIX audio source.

If device implementations declare both android.hardware.audio.output and android.hardware.microphone , they:

• [C-1-1] MUST properly implement the REMOTE_SUBMIX audio source so that when an application uses the android.media.AudioRecord API to record from this audio source, it captures a mix of all audio streams except for the following:

  • AudioManager.STREAM_RING
  • AudioManager.STREAM_ALARM
  • AudioManager.STREAM_NOTIFICATION

5.4.4. Acoustic Echo Canceler

If device implementations declare android.hardware.microphone , they:

• SHOULD implement an Acoustic Echo Canceler (AEC) technology tuned for voice communication and applied to the capture path when capturing using AudioSource.VOICE_COMMUNICATION

If device implementations provides an Acoustic Echo Canceler which is inserted in the capture audio path when AudioSource.VOICE_COMMUNICATION is selected, they:

• [C-SR] are STRONGLY_RECOMMENDED to declare this via AcousticEchoCanceler API method AcousticEchoCanceler.isAvailable()
• [C-SR] are STRONGLY_RECOMMENDED to allow this audio effect to be controllable with the AcousticEchoCanceler API.
• [C-SR] are STRONGLY_RECOMMENDED to uniquely identify each AEC technology implementation via the AudioEffect.Descriptor.uuid field.

5.4.5. Concurrent Capture

If device implementations declare android.hardware.microphone ,they MUST implement concurrent capture as described in this document . Secara khusus:

• [C-1-1] MUST allow concurrent access to microphone by an accessibility service capturing with AudioSource.VOICE_RECOGNITION and at least one application capturing with any AudioSource .
• [C-1-2] MUST allow concurrent access to microphone by a pre-installed application that holds an Assistant role and at least one application capturing with any AudioSource except for AudioSource.VOICE_COMMUNICATION or AudioSource.CAMCORDER .
• [C-1-3] MUST silence the audio capture for any other application, except for an accessibility service, while an application is capturing with AudioSource.VOICE_COMMUNICATION or AudioSource.CAMCORDER . However, when an app is capturing via AudioSource.VOICE_COMMUNICATION then another app can capture the voice call if it is a privileged (pre-installed) app with permission CAPTURE_AUDIO_OUTPUT .
• [C-1-4] If two or more applications are capturing concurrently and if neither app has an UI on top, the one that started capture the most recently receives audio.

5.4.6. Microphone Gain Levels

If device implementations declare android.hardware.microphone , they:

• SHOULD exhibit approximately flat amplitude-versus-frequency characteristics in the mid-frequency range: specifically ±3dB from 100 Hz to 4000 Hz for each and every microphone used to record the voice recognition audio source.
• SHOULD set audio input sensitivity such that a 1000 Hz sinusoidal tone source played at 90 dB Sound Pressure Level (SPL) yields a response with RMS of 2500 for 16 bit-samples (or -22.35 dB Full Scale for floating point/double precision samples) for each and every microphone used to record the voice recognition audio source.
• [C-SR] are STRONGLY RECOMMENDED to exhibit amplitude levels in the low frequency range: specifically from ±20 dB from 5 Hz to 100 Hz compared to the mid-frequency range for each and every microphone used to record the voice recognition audio source.
• [C-SR] are STRONGLY RECOMMENDED to exhibit amplitude levels in the high frequency range: specifically from ±30 dB from 4000 Hz to 22 KHz compared to the mid-frequency range for each and every microphone used to record the voice recognition audio source.

5.5. Pemutaran Audio

Android includes the support to allow apps to playback audio through the audio output peripheral as defined in section 7.8.2.

5.5.1. Raw Audio Playback

If device implementations declare android.hardware.audio.output , they:

• [C-1-1] MUST allow playback of raw audio content with the following characteristics:

  • Source formats : Linear PCM, 16-bit, 8-bit, float
  • Channels : Mono, Stereo, valid multichannel configurations with up to 8 channels
  • Sampling rates (in Hz) :
    • 8000, 11025, 16000, 22050, 32000, 44100, 48000 at the channel configurations listed above
    • 96000 in mono and stereo

• SHOULD allow playback of raw audio content with the following characteristics:

  • Sampling rates : 24000

5.5.2. Efek Audio

Android provides an API for audio effects for device implementations.

If device implementations declare the feature android.hardware.audio.output , they:

• [C-1-1] MUST support the EFFECT_TYPE_EQUALIZER and EFFECT_TYPE_LOUDNESS_ENHANCER implementations controllable through the AudioEffect subclasses Equalizer and LoudnessEnhancer .
• [C-1-2] MUST support the visualizer API implementation, controllable through the Visualizer class.
• [C-1-3] MUST support the EFFECT_TYPE_DYNAMICS_PROCESSING implementation controllable through the AudioEffect subclass DynamicsProcessing .
• SHOULD support the EFFECT_TYPE_BASS_BOOST , EFFECT_TYPE_ENV_REVERB , EFFECT_TYPE_PRESET_REVERB , and EFFECT_TYPE_VIRTUALIZER implementations controllable through the AudioEffect sub-classes BassBoost , EnvironmentalReverb , PresetReverb , and Virtualizer .
• [C-SR] Are STRONGLY RECOMMENDED to support effects in floating-point and multichannel.

5.5.3. Audio Output Volume

Implementasi perangkat otomotif:

• SHOULD allow adjusting audio volume separately per each audio stream using the content type or usage as defined by AudioAttributes and car audio usage as publicly defined in android.car.CarAudioManager .

5.6. Audio Latency

Audio latency is the time delay as an audio signal passes through a system. Many classes of applications rely on short latencies, to achieve real-time sound effects.

For the purposes of this section, use the following definitions:

• output latency . The interval between when an application writes a frame of PCM-coded data and when the corresponding sound is presented to environment at an on-device transducer or signal leaves the device via a port and can be observed externally.
• cold output latency . The output latency for the first frame, when the audio output system has been idle and powered down prior to the request.
• continuous output latency . The output latency for subsequent frames, after the device is playing audio.
• input latency . The interval between when a sound is presented by environment to device at an on-device transducer or signal enters the device via a port and when an application reads the corresponding frame of PCM-coded data.
• lost input . The initial portion of an input signal that is unusable or unavailable.
• cold input latency . The sum of lost input time and the input latency for the first frame, when the audio input system has been idle and powered down prior to the request.
• continuous input latency . The input latency for subsequent frames, while the device is capturing audio.
• cold output jitter . The variability among separate measurements of cold output latency values.
• cold input jitter . The variability among separate measurements of cold input latency values.
• continuous round-trip latency . The sum of continuous input latency plus continuous output latency plus one buffer period. The buffer period allows time for the app to process the signal and time for the app to mitigate phase difference between input and output streams.
• OpenSL ES PCM buffer queue API . The set of PCM-related OpenSL ES APIs within Android NDK .
• AAudio native audio API . The set of AAudio APIs within Android NDK .
• timestamp . A pair consisting of a relative frame position within a stream and the estimated time when that frame enters or leaves the audio processing pipeline on the associated endpoint. See also AudioTimestamp .
• kesalahan . A temporary interruption or incorrect sample value in the audio signal, typically caused by a buffer underrun for output, buffer overrun for input, or any other source of digital or analog noise.

If device implementations declare android.hardware.audio.output , they MUST meet or exceed the following requirements:

• [C-1-1] The output timestamp returned by AudioTrack.getTimestamp and AAudioStream_getTimestamp is accurate to +/- 2 ms.
• [C-1-2] Cold output latency of 500 milliseconds or less.

If device implementations declare android.hardware.audio.output they are STRONGLY RECOMMENDED to meet or exceed the following requirements:

• [C-SR] Cold output latency of 100 milliseconds or less. Existing and new devices that run this version of Android are VERY STRONGLY RECOMMENDED to meet these requirements now. In a future platform release in 2021, we will require Cold output latency of 200 ms or less as a MUST.
• [C-SR] Continuous output latency of 45 milliseconds or less.
• [C-SR] Minimize the cold output jitter.
• [C-SR] The output timestamp returned by AudioTrack.getTimestamp and AAudioStream_getTimestamp is accurate to +/- 1 ms.

If device implementations meet the above requirements, after any initial calibration, when using both the OpenSL ES PCM buffer queue and AAudio native audio APIs, for continuous output latency and cold output latency over at least one supported audio output device, they are:

• [C-SR] STRONGLY RECOMMENDED to report low-latency audio by declaring android.hardware.audio.low_latency feature flag.
• [C-SR] STRONGLY RECOMMENDED to meet the requirements for low-latency audio via the AAudio API.
• [C-SR] STRONGLY RECOMMENDED to ensure that for streams that return AAUDIO_PERFORMANCE_MODE_LOW_LATENCY from AAudioStream_getPerformanceMode() , the value returned by AAudioStream_getFramesPerBurst() is less than or equal to the value returned by android.media.AudioManager.getProperty(String) for property key AudioManager.PROPERTY_OUTPUT_FRAMES_PER_BUFFER .

If device implementations do not meet the requirements for low-latency audio via both the OpenSL ES PCM buffer queue and AAudio native audio APIs, they:

• [C-2-1] MUST NOT report support for low-latency audio.

If device implementations include android.hardware.microphone , they MUST meet these input audio requirements:

• [C-3-1] Limit the error in input timestamps, as returned by AudioRecord.getTimestamp or AAudioStream_getTimestamp , to +/- 2 ms. "Error" here means the deviation from the correct value.
• [C-3-2] Cold input latency of 500 milliseconds or less.

If device implementations include android.hardware.microphone , they are STRONGLY RECOMMENDED to meet these input audio requirements:

• [C-SR] Cold input latency of 100 milliseconds or less. Existing and new devices that run this version of Android are VERY STRONGLY RECOMMENDED to meet these requirements now. In a future platform release in 2021 we will require Cold input latency of 200 ms or less as a MUST.
• [C-SR] Continuous input latency of 30 milliseconds or less.
• [C-SR] Continuous round-trip latency of 50 milliseconds or less.
• [C-SR] Minimize the cold input jitter.
• [C-SR] Limit the error in input timestamps, as returned by AudioRecord.getTimestamp or AAudioStream_getTimestamp , to +/- 1 ms.

5.7. Protokol Jaringan

Device implementations MUST support the media network protocols for audio and video playback as specified in the Android SDK documentation.

If device implementations include an audio or a video decoder, they:

• [C-1-1] MUST support all required codecs and container formats in section 5.1 over HTTP(S).

• [C-1-2] MUST support the media segment formats shown in the Media Segment Formats table below over HTTP Live Streaming draft protocol, Version 7 .

• [C-1-3] MUST support the following RTP audio video profile and related codecs in the RTSP table below. For exceptions please see the table footnotes in section 5.1 .

Media Segment Formats

RTSP (RTP, SDP)

5.8. Media Aman

If device implementations support secure video output and are capable of supporting secure surfaces, they:

• [C-1-1] MUST declare support for Display.FLAG_SECURE .

If device implementations declare support for Display.FLAG_SECURE and support wireless display protocol, they:

• [C-2-1] MUST secure the link with a cryptographically strong mechanism such as HDCP 2.x or higher for the displays connected through wireless protocols such as Miracast.

If device implementations declare support for Display.FLAG_SECURE and support wired external display, they:

• [C-3-1] MUST support HDCP 1.2 or higher for all external displays connected via a user-accessible wired port.

5.9. Antarmuka Digital Alat Musik (MIDI)

If device implementations report support for feature android.software.midi via the android.content.pm.PackageManager class, they:

• [C-1-1] MUST support MIDI over all MIDI-capable hardware transports for which they provide generic non-MIDI connectivity, where such transports are:

  • USB host mode, section 7.7
  • USB peripheral mode, section 7.7
  • MIDI over Bluetooth LE acting in central role, section 7.4.3

• [C-1-2] MUST support the inter-app MIDI software transport (virtual MIDI devices)

• [C-1-3] MUST include libamidi.so (native MIDI support)

5.10. Audio Profesional

If device implementations report support for feature android.hardware.audio.pro via the android.content.pm.PackageManager class, they:

• [C-1-1] MUST report support for feature android.hardware.audio.low_latency .
• [C-1-2] MUST have a continuous round-trip audio latency, as defined in section 5.6 Audio Latency , of 20 milliseconds or less and SHOULD be 10 milliseconds or less over at least one supported path.
• [C-1-3] MUST include a USB port(s) supporting USB host mode and USB peripheral mode.
• [C-1-4] MUST report support for feature android.software.midi .
• [C-1-5] MUST meet latencies and USB audio requirements using both the OpenSL ES PCM buffer queue API and at least one path of the AAudio native audio API.
• [SR] Are STRONGLY RECOMMENDED to meet latencies and USB audio requirements using the AAudio native audio API over the MMAP path .
• [C-1-6] MUST have Cold output latency of 200 milliseconds or less.
• [C-1-7] MUST have Cold input latency of 200 milliseconds or less.
• [SR] Are STRONGLY RECOMMENDED to provide a consistent level of CPU performance while audio is active and CPU load is varying. This SHOULD be tested using the Android app version of SynthMark commit id 09b13c6f49ea089f8c31e5d035f912cc405b7ab8 . SynthMark uses a software synthesizer running on a simulated audio framework that measures system performance. The SynthMark app needs to be run using the “Automated Test” option and achieve the following results:
  • voicemark.90 >= 32 voices
  • latencymark.fixed.little <= 15 msec
  • latencymark.dynamic.little <= 50 msec

See the SynthMark documentation for an explanation of the benchmarks.

• SHOULD minimize audio clock inaccuracy and drift relative to standard time.
• SHOULD minimize audio clock drift relative to the CPU CLOCK_MONOTONIC when both are active.
• SHOULD minimize audio latency over on-device transducers.
• SHOULD minimize audio latency over USB digital audio.
• SHOULD document audio latency measurements over all paths.
• SHOULD minimize jitter in audio buffer completion callback entry times, as this affects usable percentage of full CPU bandwidth by the callback.
• SHOULD provide zero audio glitches under normal use at reported latency.
• SHOULD provide zero inter-channel latency difference.
• SHOULD minimize MIDI mean latency over all transports.
• SHOULD minimize MIDI latency variability under load (jitter) over all transports.
• SHOULD provide accurate MIDI timestamps over all transports.
• SHOULD minimize audio signal noise over on-device transducers, including the period immediately after cold start.
• SHOULD provide zero audio clock difference between the input and output sides of corresponding end-points, when both are active. Examples of corresponding end-points include the on-device microphone and speaker, or the audio jack input and output.
• SHOULD handle audio buffer completion callbacks for the input and output sides of corresponding end-points on the same thread when both are active, and enter the output callback immediately after the return from the input callback. Or if it is not feasible to handle the callbacks on the same thread, then enter the output callback shortly after entering the input callback to permit the application to have a consistent timing of the input and output sides.
• SHOULD minimize the phase difference between HAL audio buffering for the input and output sides of corresponding end-points.
• SHOULD minimize touch latency.
• SHOULD minimize touch latency variability under load (jitter).
• SHOULD have a latency from touch input to audio output of less than or equal to 40 ms.

If device implementations meet all of the above requirements, they:

• [SR] STRONGLY RECOMMENDED to report support for feature android.hardware.audio.pro via the android.content.pm.PackageManager class.

If device implementations include a 4 conductor 3.5mm audio jack, they:

• [C-2-1] MUST have the continuous round-trip audio latency to be 20 milliseconds or less over the audio jack path.
• [SR] STRONGLY RECOMMENDED to comply with section Mobile device (jack) specifications of the Wired Audio Headset Specification (v1.1) .
• The continuous round-trip audio latency SHOULD be 10 milliseconds or less over the audio jack path.

If device implementations omit a 4 conductor 3.5mm audio jack and include a USB port(s) supporting USB host mode, they:

• [C-3-1] MUST implement the USB audio class.
• [C-3-2] MUST have a continuous round-trip audio latency of 20 milliseconds or less over the USB host mode port using USB audio class.
• The continuous round-trip audio latency SHOULD be 10 milliseconds or less over the USB host mode port using USB audio class.
• [C-SR] Are STRONGLY RECOMMENDED to support simultaneous I/O up to 8 channels each direction, 96 kHz sample rate, and 24-bit or 32-bit depth, when used with USB audio peripherals that also support these requirements.

If device implementations include an HDMI port, they:

• SHOULD support output in stereo and eight channels at 20-bit or 24-bit depth and 192 kHz without bit-depth loss or resampling, in at least one configuration.

5.11. Capture for Unprocessed

Android includes support for recording of unprocessed audio via the android.media.MediaRecorder.AudioSource.UNPROCESSED audio source. In OpenSL ES, it can be accessed with the record preset SL_ANDROID_RECORDING_PRESET_UNPROCESSED .

If device implementations intent to support unprocessed audio source and make it available to third-party apps, they:

• [C-1-1] MUST report the support through the android.media.AudioManager property PROPERTY_SUPPORT_AUDIO_SOURCE_UNPROCESSED .

• [C-1-2] MUST exhibit approximately flat amplitude-versus-frequency characteristics in the mid-frequency range: specifically ±10dB from 100 Hz to 7000 Hz for each and every microphone used to record the unprocessed audio source.

• [C-1-3] MUST exhibit amplitude levels in the low frequency range: specifically from ±20 dB from 5 Hz to 100 Hz compared to the mid-frequency range for each and every microphone used to record the unprocessed audio source.

• [C-1-4] MUST exhibit amplitude levels in the high frequency range: specifically from ±30 dB from 7000 Hz to 22 KHz compared to the mid-frequency range for each and every microphone used to record the unprocessed audio source.

• [C-1-5] MUST set audio input sensitivity such that a 1000 Hz sinusoidal tone source played at 94 dB Sound Pressure Level (SPL) yields a response with RMS of 520 for 16 bit-samples (or -36 dB Full Scale for floating point/double precision samples) for each and every microphone used to record the unprocessed audio source.

• [C-1-6] MUST have a signal-to-noise ratio (SNR) at 60 dB or higher for each and every microphone used to record the unprocessed audio source. (whereas the SNR is measured as the difference between 94 dB SPL and equivalent SPL of self noise, A-weighted).

• [C-1-7] MUST have a total harmonic distortion (THD) less than be less than 1% for 1 kHZ at 90 dB SPL input level at each and every microphone used to record the unprocessed audio source.

• MUST not have any other signal processing (eg Automatic Gain Control, High Pass Filter, or Echo cancellation) in the path other than a level multiplier to bring the level to desired range. Dengan kata lain:

• [C-1-8] If any signal processing is present in the architecture for any reason, it MUST be disabled and effectively introduce zero delay or extra latency to the signal path.
• [C-1-9] The level multiplier, while allowed to be on the path, MUST NOT introduce delay or latency to the signal path.

All SPL measurements are made directly next to the microphone under test. For multiple microphone configurations, these requirements apply to each microphone.

If device implementations declare android.hardware.microphone but do not support unprocessed audio source, they:

• [C-2-1] MUST return null for the AudioManager.getProperty(PROPERTY_SUPPORT_AUDIO_SOURCE_UNPROCESSED) API method, to properly indicate the lack of support.
• [SR] are still STRONGLY RECOMMENDED to satisfy as many of the requirements for the signal path for the unprocessed recording source.

6. Developer Tools and Options Compatibility

6.1. Alat pengembang

Implementasi perangkat:

• [C-0-1] MUST support the Android Developer Tools provided in the Android SDK.

• Jembatan Debug Android (adb)

  • [C-0-2] HARUS mendukung adb seperti yang didokumentasikan dalam Android SDK dan perintah shell yang disediakan di AOSP, yang dapat digunakan oleh pengembang aplikasi, termasuk cmd stats dumpsys
  • [C-SR] Are STRONGLY RECOMMENDED to support the shell command cmd testharness .
  • [C-0-3] MUST NOT alter the format or the contents of device system events (batterystats , diskstats, fingerprint, graphicsstats, netstats, notification, procstats) logged via the dumpsys command.
  • [C-0-10] MUST record, without omission, and make the following events accessible and available to the cmd stats shell command and the StatsManager System API class.
    • ActivityForegroundStateChanged
    • AnomalyDetected
    • AppBreadcrumbReported
    • AppCrashOccurred
    • AppStartOccurred
    • BatteryLevelChanged
    • BatterySaverModeStateChanged
    • BleScanResultReceived
    • BleScanStateChanged
    • ChargingStateChanged
    • DeviceIdleModeStateChanged
    • ForegroundServiceStateChanged
    • GpsScanStateChanged
    • JobStateChanged
    • PluggedStateChanged
    • ScheduledJobStateChanged
    • ScreenStateChanged
    • SyncStateChanged
    • SystemElapsedRealtime
    • UidProcessStateChanged
    • WakelockStateChanged
    • WakeupAlarmOccurred
    • WifiLockStateChanged
    • WifiMulticastLockStateChanged
    • WifiScanStateChanged
  • [C-0-4] MUST have the device-side adb daemon be inactive by default and there MUST be a user-accessible mechanism to turn on the Android Debug Bridge.
  • [C-0-5] MUST support secure adb. Android includes support for secure adb. Secure adb enables adb on known authenticated hosts.

  • [C-0-6] MUST provide a mechanism allowing adb to be connected from a host machine. Misalnya:

    • Device implementations without a USB port supporting peripheral mode MUST implement adb via local-area network (such as Ethernet or Wi-Fi).
    • MUST provide drivers for Windows 7, 9 and 10, allowing developers to connect to the device using the adb protocol.

• Dalvik Debug Monitor Service (ddms)

  • [C-0-7] MUST support all ddms features as documented in the Android SDK. As ddms uses adb, support for ddms SHOULD be inactive by default, but MUST be supported whenever the user has activated the Android Debug Bridge, as above.
• Monyet
  • [C-0-8] MUST include the Monkey framework and make it available for applications to use.
• SysTrace
  • [C-0-9] HARUS mendukung alat systrace seperti yang didokumentasikan dalam Android SDK. Systrace MUST be inactive by default and there MUST be a user-accessible mechanism to turn on Systrace.

• Sempurna

  • [C-SR] Are STRONGLY RECOMMENDED to expose a /system/bin/perfetto binary to the shell user which cmdline complies with the perfetto documentation .
  • [C-SR] The perfetto binary is STRONGLY RECOMMENDED to accept as input a protobuf config that complies with the schema defined in the perfetto documentation .
  • [C-SR] The perfetto binary is STRONGLY RECOMMENDED to write as output a protobuf trace that complies with the schema defined in the perfetto documentation .
  • [C-SR] Are STRONGLY RECOMMENDED to provide, through the perfetto binary, at least the data sources described in the perfetto documentation .

• Mode Uji Harness

  If device implementations support the shell command cmd testharness and run cmd testharness enable , they:

  • [C-2-1] MUST return true for ActivityManager.isRunningInUserTestHarness()
  • [C-2-2] MUST implement Test Harness Mode as described in harness mode documentation .

If device implementations report the support of Vulkan 1.0 or higher via the android.hardware.vulkan.version feature flags, they:

• [C-1-1] MUST provide an affordance for the app developer to enable/disable GPU debug layers.
• [C-1-2] MUST, when the GPU debug layers are enabled, enumerate layers in libraries provided by external tools (ie not part of the platform or application package) found in debuggable applications' base directory to support vkEnumerateInstanceLayerProperties() and vkCreateInstance() API methods.

6.2. Opsi Pengembang

Android includes support for developers to configure application development-related settings.

Device implementations MUST provide a consistent experience for Developer Options, they:

• [C-0-1] MUST honor the android.settings.APPLICATION_DEVELOPMENT_SETTINGS intent to show application development-related settings. The upstream Android implementation hides the Developer Options menu by default and enables users to launch Developer Options after pressing seven (7) times on the Settings > About Device > Build Number menu item.
• [C-0-2] MUST hide Developer Options by default.
• [C-0-3] MUST provide a clear mechanism that does not give preferential treatment to one third-party app as opposed to another to enable Developer Options. MUST provide a public visible document or website that describes how to enable Developer Options. This document or website MUST be linkable from the Android SDK documents.
• SHOULD have an ongoing visual notification to the user when Developer Options is enabled and the safety of the user is of concern.
• MAY temporarily limit access to the Developer Options menu, by visually hiding or disabling the menu, to prevent distraction for scenarios where the safety of the user is of concern.

7. Hardware Compatibility

If a device includes a particular hardware component that has a corresponding API for third-party developers:

• [C-0-1] The device implementation MUST implement that API as described in the Android SDK documentation.

If an API in the SDK interacts with a hardware component that is stated to be optional and the device implementation does not possess that component:

• [C-0-2] Complete class definitions (as documented by the SDK) for the component APIs MUST still be presented.
• [C-0-3] The API's behaviors MUST be implemented as no-ops in some reasonable fashion.
• [C-0-4] API methods MUST return null values where permitted by the SDK documentation.
• [C-0-5] API methods MUST return no-op implementations of classes where null values are not permitted by the SDK documentation.
• [C-0-6] API methods MUST NOT throw exceptions not documented by the SDK documentation.
• [C-0-7] Device implementations MUST consistently report accurate hardware configuration information via the getSystemAvailableFeatures() and hasSystemFeature(String) methods on the android.content.pm.PackageManager class for the same build fingerprint.

A typical example of a scenario where these requirements apply is the telephony API: Even on non-phone devices, these APIs MUST be implemented as reasonable no-ops.

7.1. Tampilan dan Grafik

Android includes facilities that automatically adjust application assets and UI layouts appropriately for the device to ensure that third-party applications run well on a variety of hardware configurations . On the Android-compatible display(s) where all third-party Android-compatible applications can run, device implementations MUST properly implement these APIs and behaviors, as detailed in this section.

The units referenced by the requirements in this section are defined as follows:

• physical diagonal size . The distance in inches between two opposing corners of the illuminated portion of the display.
• dots per inch (dpi) . The number of pixels encompassed by a linear horizontal or vertical span of 1”. Where dpi values are listed, both horizontal and vertical dpi MUST fall within the range.
• aspect ratio . The ratio of the pixels of the longer dimension to the shorter dimension of the screen. For example, a display of 480x854 pixels would be 854/480 = 1.779, or roughly “16:9”.
• density-independent pixel (dp) . The virtual pixel unit normalized to a 160 dpi screen, calculated as: pixels = dps * (density/160).

7.1.1. Konfigurasi Layar

7.1.1.1. Screen Size and Shape

The Android UI framework supports a variety of different logical screen layout sizes, and allows applications to query the current configuration's screen layout size via Configuration.screenLayout with the SCREENLAYOUT_SIZE_MASK and Configuration.smallestScreenWidthDp .

Implementasi perangkat:

• [C-0-1] MUST report the correct layout size for the Configuration.screenLayout as defined in the Android SDK documentation. Specifically, device implementations MUST report the correct logical density-independent pixel (dp) screen dimensions as below:

  • Devices with the Configuration.uiMode set as any value other than UI_MODE_TYPE_WATCH, and reporting a small size for the Configuration.screenLayout , MUST have at least 426 dp x 320 dp.
  • Devices reporting a normal size for the Configuration.screenLayout , MUST have at least 480 dp x 320 dp.
  • Devices reporting a large size for the Configuration.screenLayout , MUST have at least 640 dp x 480 dp.
  • Devices reporting a xlarge size for the Configuration.screenLayout , MUST have at least 960 dp x 720 dp.

• [C-0-2] MUST correctly honor applications' stated support for screen sizes through the < supports-screens > attribute in the AndroidManifest.xml, as described in the Android SDK documentation.

• MAY have the Android-compatible display(s) with rounded corners.

If device implementations support UI_MODE_TYPE_NORMAL and include the Android-compatible display(s) with rounded corners, they:

• [C-1-1] MUST ensure that the radius of the rounded corners is less than or equal to 38 dp.
• SHOULD include user affordance to switch to the display mode with the rectangular corners.

7.1.1.2. Rasio Aspek Layar

While there is no restriction to the aspect ratio of the physical display for the Android-compatible display(s), the aspect ratio of the logical display where third-party apps are rendered, which can be derived from the height and width values reported through the view.Display APIs and Configuration APIs, MUST meet the following requirements:

• [C-0-1] Device implementations with Configuration.uiMode set to UI_MODE_TYPE_NORMAL MUST have an aspect ratio value less than or equal to 1.86 (roughly 16:9), unless the app meets one of the following conditions:

  • The app has declared that it supports a larger screen aspect ratio through the android.max_aspect metadata value.
  • The app declares it is resizeable via the android:resizeableActivity attribute.
  • The app targets API level 24 or higher and does not declare an android:maxAspectRatio that would restrict the allowed aspect ratio.

• [C-0-2] Device implementations with Configuration.uiMode set to UI_MODE_TYPE_NORMAL MUST have an aspect ratio value equal to or greater than 1.3333 (4:3), unless the app can be stretched wider by meeting one of the following conditions:

  • The app declares it is resizeable via the android:resizeableActivity attribute.
  • The app declares an android:minAspectRatio that would restrict the allowed aspect ratio.

• [C-0-3] Device implementations with the Configuration.uiMode set as UI_MODE_TYPE_WATCH MUST have an aspect ratio value set as 1.0 (1:1).

7.1.1.3. Kepadatan Layar

The Android UI framework defines a set of standard logical densities to help application developers target application resources.

• [C-0-1] By default, device implementations MUST report only one of the Android framework densities that are listed on DisplayMetrics through the DENSITY_DEVICE_STABLE API and this value MUST NOT change at any time; however, the device MAY report a different arbitrary density according to the display configuration changes made by the user (for example, display size) set after initial boot.

• Device implementations SHOULD define the standard Android framework density that is numerically closest to the physical density of the screen, unless that logical density pushes the reported screen size below the minimum supported. If the standard Android framework density that is numerically closest to the physical density results in a screen size that is smaller than the smallest supported compatible screen size (320 dp width), device implementations SHOULD report the next lowest standard Android framework density.

If there is an affordance to change the display size of the device:

• [C-1-1] The display size MUST NOT be scaled any larger than 1.5 times the native density or produce an effective minimum screen dimension smaller than 320dp (equivalent to resource qualifier sw320dp), whichever comes first.
• [C-1-2] Display size MUST NOT be scaled any smaller than 0.85 times the native density.
• To ensure good usability and consistent font sizes, it is RECOMMENDED that the following scaling of Native Display options be provided (while complying with the limits specified above)
• Small: 0.85x
• Default: 1x (Native display scale)
• Large: 1.15x
• Larger: 1.3x
• Largest 1.45x

7.1.2. Display Metrics

If device implementations include the Android-compatible display(s) or video output to the Android-compatible display screen(s), they:

• [C-1-1] MUST report correct values for all Android-compatible display metrics defined in the android.util.DisplayMetrics API.

If device implementations does not include an embedded screen or video output, they:

• [C-2-1] MUST report correct values of the Android-compatible display as defined in the android.util.DisplayMetrics API for the emulated default view.Display .

7.1.3. Orientasi layar

Implementasi perangkat:

• [C-0-1] MUST report which screen orientations they support ( android.hardware.screen.portrait and/or android.hardware.screen.landscape ) and MUST report at least one supported orientation. For example, a device with a fixed orientation landscape screen, such as a television or laptop, SHOULD only report android.hardware.screen.landscape .
• [C-0-2] MUST report the correct value for the device's current orientation, whenever queried via the android.content.res.Configuration.orientation , android.view.Display.getOrientation() , or other APIs.

If device implementations support both screen orientations, they:

• [C-1-1] MUST support dynamic orientation by applications to either portrait or landscape screen orientation. That is, the device MUST respect the application's request for a specific screen orientation.
• [C-1-2] MUST NOT change the reported screen size or density when changing orientation.
• MAY select either portrait or landscape orientation as the default.

7.1.4. 2D and 3D Graphics Acceleration

7.1.4.1 OpenGL ES

Implementasi perangkat:

• [C-0-1] MUST correctly identify the supported OpenGL ES versions (1.1, 2.0, 3.0, 3.1, 3.2) through the managed APIs (such as via the GLES10.getString() method) and the native APIs.
• [C-0-2] MUST include the support for all the corresponding managed APIs and native APIs for every OpenGL ES versions they identified to support.

If device implementations include a screen or video output, they:

• [C-1-1] MUST support both OpenGL ES 1.1 and 2.0, as embodied and detailed in the Android SDK documentation .
• [C-SR] Are STRONGLY RECOMMENDED to support OpenGL ES 3.1.
• SHOULD support OpenGL ES 3.2.

If device implementations support any of the OpenGL ES versions, they:

• [C-2-1] MUST report via the OpenGL ES managed APIs and native APIs any other OpenGL ES extensions they have implemented, and conversely MUST NOT report extension strings that they do not support.
• [C-2-2] MUST support the EGL_KHR_image , EGL_KHR_image_base , EGL_ANDROID_image_native_buffer , EGL_ANDROID_get_native_client_buffer , EGL_KHR_wait_sync , EGL_KHR_get_all_proc_addresses , EGL_ANDROID_presentation_time , EGL_KHR_swap_buffers_with_damage , EGL_ANDROID_recordable , and EGL_ANDROID_GLES_layers extensions.
• [C-SR] Are STRONGLY RECOMMENDED to support the EGL_KHR_partial_update and OES_EGL_image_external extensions.
• SHOULD accurately report via the getString() method, any texture compression format that they support, which is typically vendor-specific.

If device implementations declare support for OpenGL ES 3.0, 3.1, or 3.2, they:

• [C-3-1] MUST export the corresponding function symbols for these version in addition to the OpenGL ES 2.0 function symbols in the libGLESv2.so library.
• [SR] Are STRONGLY RECOMMENDED to support the OES_EGL_image_external_essl3 extension.

If device implementations support OpenGL ES 3.2, they:

• [C-4-1] MUST support the OpenGL ES Android Extension Pack in its entirety.

If device implementations support the OpenGL ES Android Extension Pack in its entirety, they:

• [C-5-1] MUST identify the support through the android.hardware.opengles.aep feature flag.

If device implementations expose support for the EGL_KHR_mutable_render_buffer extension, they:

• [C-6-1] MUST also support the EGL_ANDROID_front_buffer_auto_refresh extension.

7.1.4.2 Vulkan

Android includes support for Vulkan , a low-overhead, cross-platform API for high-performance 3D graphics.

If device implementations support OpenGL ES 3.1, they:

• [SR] Are STRONGLY RECOMMENDED to include support for Vulkan 1.1.

If device implementations include a screen or video output, they:

• SHOULD include support for Vulkan 1.1.

If device implementations include support for Vulkan 1.0, they:

• [C-1-1] MUST report the correct integer value with the android.hardware.vulkan.level and android.hardware.vulkan.version feature flags.
• [C-1-2] MUST enumerate, at least one VkPhysicalDevice for the Vulkan native API vkEnumeratePhysicalDevices() .
• [C-1-3] MUST fully implement the Vulkan 1.0 APIs for each enumerated VkPhysicalDevice .
• [C-1-4] MUST enumerate layers, contained in native libraries named as libVkLayer*.so in the application package's native library directory, through the Vulkan native APIs vkEnumerateInstanceLayerProperties() and vkEnumerateDeviceLayerProperties() .
• [C-1-5] MUST NOT enumerate layers provided by libraries outside of the application package, or provide other ways of tracing or intercepting the Vulkan API, unless the application has the android:debuggable attribute set as true .
• [C-1-6] MUST report all extension strings that they do support via the Vulkan native APIs , and conversely MUST NOT report extension strings that they do not correctly support.
• [C-1-7] MUST support the VK_KHR_surface, VK_KHR_android_surface, VK_KHR_swapchain, and VK_KHR_incremental_present extensions.
• [C-SR] Are STRONGLY RECOMMENDED to support the VK_KHR_driver_properties and VK_GOOGLE_display_timing extensions.

If device implementations do not include support for Vulkan 1.0, they:

• [C-2-1] MUST NOT declare any of the Vulkan feature flags (eg android.hardware.vulkan.level , android.hardware.vulkan.version ).
• [C-2-2] MUST NOT enumerate any VkPhysicalDevice for the Vulkan native API vkEnumeratePhysicalDevices() .

If device implementations include support for Vulkan 1.1 and declare any of the Vulkan feature flags, they:

• [C-3-1] MUST expose support for the SYNC_FD external semaphore and handle types and the VK_ANDROID_external_memory_android_hardware_buffer extension.

7.1.4.3 RenderScript

• [C-0-1] Device implementations MUST support Android RenderScript , as detailed in the Android SDK documentation.

7.1.4.4 2D Graphics Acceleration

Android includes a mechanism for applications to declare that they want to enable hardware acceleration for 2D graphics at the Application, Activity, Window, or View level through the use of a manifest tag android:hardwareAccelerated or direct API calls.

Implementasi perangkat:

• [C-0-1] MUST enable hardware acceleration by default, and MUST disable hardware acceleration if the developer so requests by setting android:hardwareAccelerated="false” or disabling hardware acceleration directly through the Android View APIs.
• [C-0-2] MUST exhibit behavior consistent with the Android SDK documentation on hardware acceleration .

Android includes a TextureView object that lets developers directly integrate hardware-accelerated OpenGL ES textures as rendering targets in a UI hierarchy.

Implementasi perangkat:

• [C-0-3] MUST support the TextureView API, and MUST exhibit consistent behavior with the upstream Android implementation.

7.1.4.5 Wide-gamut Displays

If device implementations claim support for wide-gamut displays through Configuration.isScreenWideColorGamut() , they:

• [C-1-1] MUST have a color-calibrated display.
• [C-1-2] MUST have a display whose gamut covers the sRGB color gamut entirely in CIE 1931 xyY space.
• [C-1-3] MUST have a display whose gamut has an area of at least 90% of DCI-P3 in CIE 1931 xyY space.
• [C-1-4] MUST support OpenGL ES 3.1 or 3.2 and report it properly.
• [C-1-5] MUST advertise support for the EGL_KHR_no_config_context , EGL_EXT_pixel_format_float , EGL_KHR_gl_colorspace , EGL_EXT_gl_colorspace_scrgb , EGL_EXT_gl_colorspace_scrgb_linear , EGL_EXT_gl_colorspace_display_p3 , EGL_EXT_gl_colorspace_display_p3_linear , and EGL_EXT_gl_colorspace_display_p3_passthrough extensions.
• [C-SR] Are STRONGLY RECOMMENDED to support GL_EXT_sRGB .

Conversely, if device implementations do not support wide-gamut displays, they:

• [C-2-1] SHOULD cover 100% or more of sRGB in CIE 1931 xyY space, although the screen color gamut is undefined.

7.1.5. Legacy Application Compatibility Mode

Android specifies a “compatibility mode” in which the framework operates in a 'normal' screen size equivalent (320dp width) mode for the benefit of legacy applications not developed for old versions of Android that pre-date screen-size independence.

7.1.6. Teknologi Layar

The Android platform includes APIs that allow applications to render rich graphics to an Android-compatible display. Devices MUST support all of these APIs as defined by the Android SDK unless specifically allowed in this document.

All of a device implementation's Android-compatible displays:

• [C-0-1] MUST be capable of rendering 16-bit color graphics.
• SHOULD support displays capable of 24-bit color graphics.
• [C-0-2] MUST be capable of rendering animations.
• [C-0-3] MUST have a pixel aspect ratio (PAR) between 0.9 and 1.15. That is, the pixel aspect ratio MUST be near square (1.0) with a 10 ~ 15% tolerance.

7.1.7. Secondary Displays

Android includes support for secondary Android-compatible displays to enable media sharing capabilities and developer APIs for accessing external displays.

If device implementations support an external display either via a wired, wireless, or an embedded additional display connection, they:

• [C-1-1] MUST implement the DisplayManager system service and API as described in the Android SDK documentation.

7.2. Perangkat masukan

Implementasi perangkat:

• [C-0-1] MUST include an input mechanism, such as a touchscreen or non-touch navigation , to navigate between the UI elements.

7.2.1. Papan ketik

If device implementations include support for third-party Input Method Editor (IME) applications, they:

• [C-1-1] MUST declare the android.software.input_methods feature flag.
• [C-1-2] MUST implement fully Input Management Framework
• [C-1-3] MUST have a preinstalled software keyboard.

Device implementations: * [C-0-1] MUST NOT include a hardware keyboard that does not match one of the formats specified in android.content.res.Configuration.keyboard (QWERTY or 12-key). * SHOULD include additional soft keyboard implementations. * MAY include a hardware keyboard.

7.2.2. Non-touch Navigation

Android includes support for d-pad, trackball, and wheel as mechanisms for non-touch navigation.

Implementasi perangkat:

• [C-0-1] MUST report the correct value for android.content.res.Configuration.navigation .

If device implementations lack non-touch navigations, they:

• [C-1-1] MUST provide a reasonable alternative user interface mechanism for the selection and editing of text, compatible with Input Management Engines. The upstream Android open source implementation includes a selection mechanism suitable for use with devices that lack non-touch navigation inputs.

7.2.3. Tombol Navigasi

The Home , Recents , and Back functions typically provided via an interaction with a dedicated physical button or a distinct portion of the touch screen, are essential to the Android navigation paradigm and therefore, device implementations:

• [C-0-1] MUST provide a user affordance to launch installed applications that have an activity with the <intent-filter> set with ACTION=MAIN and CATEGORY=LAUNCHER or CATEGORY=LEANBACK_LAUNCHER for Television device implementations. The Home function SHOULD be the mechanism for this user affordance.
• SHOULD provide buttons for the Recents and Back function.

If the Home, Recents, or Back functions are provided, they:

• [C-1-1] MUST be accessible with a single action (eg tap, double-click or gesture) when any of them are accessible.
• [C-1-2] MUST provide a clear indication of which single action would trigger each function. Having a visible icon imprinted on the button, showing a software icon on the navigation bar portion of the screen, or walking the user through a guided step-by-step demo flow during the out-of-box setup experience are examples of such an indikasi.

Implementasi perangkat:

• [SR] are STRONGLY RECOMMENDED to not provide the input mechanism for the Menu function as it is deprecated in favor of action bar since Android 4.0.

If device implementations provide the Menu function, they:

• [C-2-1] MUST display the action overflow button whenever the action overflow menu popup is not empty and the action bar is visible.
• [C-2-2] MUST NOT modify the position of the action overflow popup displayed by selecting the overflow button in the action bar, but MAY render the action overflow popup at a modified position on the screen when it is displayed by selecting the Menu fungsi.

If device implementations do not provide the Menu function, for backwards compatibility, they: * [C-SR] Are STRONGLY RECOMMENDED make the Menu function available to applications when targetSdkVersion is less than 10, either by a physical button, a software key, or isyarat. This Menu function SHOULD be accessible unless hidden together with other navigation functions.

If device implementations provide the Assist function , they:

• [C-4-1] MUST make the Assist function accessible with a single action (eg tap, double-click or gesture) when other navigation keys are accessible.
• [SR] STRONGLY RECOMMENDED to use long press on HOME function as this designated interaction.

If device implementations use a distinct portion of the screen to display the navigation keys, they:

• [C-5-1] Navigation keys MUST use a distinct portion of the screen, not available to applications, and MUST NOT obscure or otherwise interfere with the portion of the screen available to applications.
• [C-5-2] MUST make available a portion of the display to applications that meets the requirements defined in section 7.1.1 .
• [C-5-3] MUST honor the flags set by the app through the View.setSystemUiVisibility() API method, so that this distinct portion of the screen (aka the navigation bar) is properly hidden away as documented in the SDK.

Jika fungsi navigasi disediakan sebagai tindakan berbasis di layar, berbasis gesture:

• [C-6-1] WindowInsets#getMandatorySystemGestureInsets() MUST only be used to report the Home gesture recognition area.
• [C-6-2] Gestures that start within an exclusion rect as provided by the foreground application via View#setSystemGestureExclusionRects() , but outside of WindowInsets#getMandatorySystemGestureInsets() , MUST NOT be intercepted for the navigation function as long as the exclusion rect is allowed within the max exclusion limit as specified in the documentation for View#setSystemGestureExclusionRects() .
• [C-6-3] MUST send the foreground app a MotionEvent.ACTION_CANCEL event once touches start being intercepted for a system gesture, if the foreground app was previously sent an MotionEvent.ACTION_DOWN event.
• [C-6-4] MUST provide a user affordance to switch to an on-screen, button-based navigation (for example, in Settings).
• SHOULD provide Home function as a swipe up from the bottom edge of the current orientation of the screen.
• SHOULD provide Recents function as a swipe up and hold before release, from the same area as the Home gesture.
• Gestures that start within WindowInsets#getMandatorySystemGestureInsets() SHOULD NOT be affected by exclusion rects provided by the foreground application via View#setSystemGestureExclusionRects() .

If a navigation function is provided from anywhere on the left and right edges of the current orientation of the screen:

• [C-7-1] The navigation function MUST be Back and provided as a swipe from both left and right edges of the current orientation of the screen.
• [C-7-2] If custom swipeable system panels are provided on the left or right edges, they MUST be placed within the top 1/3rd of the screen with a clear, persistent visual indication that dragging in would invoke the aforementioned panels, and hence not Back. A system panel MAY be configured by a user such that it lands below the top 1/3rd of the screen edge(s) but the system panel MUST NOT use longer than 1/3rd of the edge(s).
• [C-7-3] When the foreground app has either the View.SYSTEM_UI_FLAG_IMMERSIVE or View.SYSTEM_UI_FLAG_IMMERSIVE_STICKY flags set, swiping from the edges MUST behave as implemented in AOSP, which is documented in the SDK .
• [C-7-4] When the foreground app has either the View.SYSTEM_UI_FLAG_IMMERSIVE or View.SYSTEM_UI_FLAG_IMMERSIVE_STICKY flags set, custom swipeable system panels MUST be hidden until the user brings in the system bars (aka navigation and status bar) as implemented in AOSP .

7.2.4. Touchscreen Input

Android includes support for a variety of pointer input systems, such as touchscreens, touch pads, and fake touch input devices. Touchscreen-based device implementations are associated with a display such that the user has the impression of directly manipulating items on screen. Since the user is directly touching the screen, the system does not require any additional affordances to indicate the objects being manipulated.

Implementasi perangkat:

• SHOULD have a pointer input system of some kind (either mouse-like or touch).
• SHOULD support fully independently tracked pointers.

If device implementations include a touchscreen (single-touch or better), they:

• [C-1-1] MUST report TOUCHSCREEN_FINGER for the Configuration.touchscreen API field.
• [C-1-2] MUST report the android.hardware.touchscreen and android.hardware.faketouch feature flags.

If device implementations include a touchscreen that can track more than a single touch, they:

• [C-2-1] MUST report the appropriate feature flags android.hardware.touchscreen.multitouch , android.hardware.touchscreen.multitouch.distinct , android.hardware.touchscreen.multitouch.jazzhand corresponding to the type of the specific touchscreen on the perangkat.

If device implementations do not include a touchscreen (and rely on a pointer device only) and meet the fake touch requirements in section 7.2.5 , they:

• [C-3-1] MUST NOT report any feature flag starting with android.hardware.touchscreen and MUST report only android.hardware.faketouch .

7.2.5. Fake Touch Input

Fake touch interface provides a user input system that approximates a subset of touchscreen capabilities. For example, a mouse or remote control that drives an on-screen cursor approximates touch, but requires the user to first point or focus then click. Numerous input devices like the mouse, trackpad, gyro-based air mouse, gyro-pointer, joystick, and multi-touch trackpad can support fake touch interactions. Android includes the feature constant android.hardware.faketouch, which corresponds to a high-fidelity non-touch (pointer-based) input device such as a mouse or trackpad that can adequately emulate touch-based input (including basic gesture support), and indicates that the device supports an emulated subset of touchscreen functionality.

If device implementations do not include a touchscreen but include another pointer input system which they want to make available, they:

• SHOULD declare support for the android.hardware.faketouch feature flag.

If device implementations declare support for android.hardware.faketouch , they:

• [C-1-1] MUST report the absolute X and Y screen positions of the pointer location and display a visual pointer on the screen.
• [C-1-2] MUST report touch event with the action code that specifies the state change that occurs on the pointer going down or up on the screen .
• [C-1-3] MUST support pointer down and up on an object on the screen, which allows users to emulate tap on an object on the screen.
• [C-1-4] MUST support pointer down, pointer up, pointer down then pointer up in the same place on an object on the screen within a time threshold, which allows users to emulate double tap on an object on the screen.
• [C-1-5] MUST support pointer down on an arbitrary point on the screen, pointer move to any other arbitrary point on the screen, followed by a pointer up, which allows users to emulate a touch drag.
• [C-1-6] MUST support pointer down then allow users to quickly move the object to a different position on the screen and then pointer up on the screen, which allows users to fling an object on the screen.
• [C-1-7] MUST report TOUCHSCREEN_NOTOUCH for the Configuration.touchscreen API field.

If device implementations declare support for android.hardware.faketouch.multitouch.distinct , they:

• [C-2-1] MUST declare support for android.hardware.faketouch .
• [C-2-2] MUST support distinct tracking of two or more independent pointer inputs.

If device implementations declare support for android.hardware.faketouch.multitouch.jazzhand , they:

• [C-3-1] MUST declare support for android.hardware.faketouch .
• [C-3-2] MUST support distinct tracking of 5 (tracking a hand of fingers) or more pointer inputs fully independently.

7.2.6. Dukungan Pengontrol Game

7.2.6.1. Button Mappings

If device implementations declare the android.hardware.gamepad feature flag, they:

• [C-1-1] MUST have embed a controller or ship with a separate controller in the box, that would provide means to input all the events listed in the below tables.
• [C-1-2] MUST be capable to map HID events to its associated Android view.InputEvent constants as listed in the below tables. The upstream Android implementation includes implementation for game controllers that satisfies this requirement.

1 KeyEvent

2 The above HID usages MUST be declared within a Game pad CA (0x01 0x0005).

3 This usage MUST have a Logical Minimum of 0, a Logical Maximum of 7, a Physical Minimum of 0, a Physical Maximum of 315, Units in Degrees, and a Report Size of 4. The logical value is defined to be the clockwise rotation away from the vertical axis; for example, a logical value of 0 represents no rotation and the up button being pressed, while a logical value of 1 represents a rotation of 45 degrees and both the up and left keys being pressed.

4 MotionEvent

1 MotionEvent

7.2.7. Kendali Jarak Jauh

See Section 2.3.1 for device-specific requirements.

7.3. Sensor

If device implementations include a particular sensor type that has a corresponding API for third-party developers, the device implementation MUST implement that API as described in the Android SDK documentation and the Android Open Source documentation on sensors .

Implementasi perangkat:

• [C-0-1] MUST accurately report the presence or absence of sensors per the android.content.pm.PackageManager class.
• [C-0-2] MUST return an accurate list of supported sensors via the SensorManager.getSensorList() and similar methods.
• [C-0-3] MUST behave reasonably for all other sensor APIs (for example, by returning true or false as appropriate when applications attempt to register listeners, not calling sensor listeners when the corresponding sensors are not present; etc.).

If device implementations include a particular sensor type that has a corresponding API for third-party developers, they:

• [C-1-1] MUST report all sensor measurements using the relevant International System of Units (metric) values for each sensor type as defined in the Android SDK documentation.
• [C-1-2] MUST report sensor data with a maximum latency of 100 milliseconds + 2 * sample_time for the case of a sensor stream with a maximum requested latency of 0 ms when the application processor is active. This delay does not include any filtering delays.
• [C-1-3] MUST report the first sensor sample within 400 milliseconds + 2 * sample_time of the sensor being activated. It is acceptable for this sample to have an accuracy of 0.

• [SR] SHOULD report the event time in nanoseconds as defined in the Android SDK documentation, representing the time the event happened and synchronized with the SystemClock.elapsedRealtimeNano() clock. Existing and new Android devices are STRONGLY RECOMMENDED to meet these requirements so they will be able to upgrade to the future platform releases where this might become a REQUIRED component. The synchronization error SHOULD be below 100 milliseconds.

• [C-1-4] For any API indicated by the Android SDK documentation to be a continuous sensor , device implementations MUST continuously provide periodic data samples that SHOULD have a jitter below 3%, where jitter is defined as the standard deviation of the difference of the reported timestamp values between consecutive events.

• [C-1-5] MUST ensure that the sensor event stream MUST NOT prevent the device CPU from entering a suspend state or waking up from a suspend state.

• When several sensors are activated, the power consumption SHOULD NOT exceed the sum of the individual sensor's reported power consumption.

The list above is not comprehensive; the documented behavior of the Android SDK and the Android Open Source Documentations on sensors is to be considered authoritative.

Some sensor types are composite, meaning they can be derived from data provided by one or more other sensors. (Examples include the orientation sensor and the linear acceleration sensor.)

Implementasi perangkat:

• SHOULD implement these sensor types, when they include the prerequisite physical sensors as described in sensor types .

If device implementations include a composite sensor, they:

• [C-2-1] MUST implement the sensor as described in the Android Open Source documentation on composite sensors .

7.3.1. Akselerometer

Implementasi perangkat:

• [C-SR] Are STRONGLY RECOMMENDED to include a 3-axis accelerometer.

If device implementations include a 3-axis accelerometer, they:

• [C-1-1] MUST be able to report events up to a frequency of at least 50 Hz.
• [C-1-2] MUST implement and report TYPE_ACCELEROMETER sensor.
• [C-1-3] MUST comply with the Android sensor coordinate system as detailed in the Android APIs.
• [C-1-4] MUST be capable of measuring from freefall up to four times the gravity(4g) or more on any axis.
• [C-1-5] MUST have a resolution of at least 12-bits.
• [C-1-6] MUST have a standard deviation no greater than 0.05 m/s^, where the standard deviation SHOULD be calculated on a per axis basis on samples collected over a period of at least 3 seconds at the fastest sampling rate.
• [SR] are STRONGLY RECOMMENDED to implement the TYPE_SIGNIFICANT_MOTION composite sensor.
• [SR] are STRONGLY RECOMMENDED to implement and report TYPE_ACCELEROMETER_UNCALIBRATED sensor. Android devices are STRONGLY RECOMMENDED to meet this requirement so they will be able to upgrade to the future platform release where this might become REQUIRED.
• SHOULD implement the TYPE_SIGNIFICANT_MOTION , TYPE_TILT_DETECTOR , TYPE_STEP_DETECTOR , TYPE_STEP_COUNTER composite sensors as described in the Android SDK document.
• SHOULD report events up to at least 200 Hz.
• SHOULD have a resolution of at least 16-bits.
• SHOULD be calibrated while in use if the characteristics changes over the life cycle and compensated, and preserve the compensation parameters between device reboots.
• SHOULD be temperature compensated.

If device implementations include a 3-axis accelerometer and any of the TYPE_SIGNIFICANT_MOTION , TYPE_TILT_DETECTOR , TYPE_STEP_DETECTOR , TYPE_STEP_COUNTER composite sensors are implemented:

• [C-2-1] The sum of their power consumption MUST always be less than 4 mW.
• SHOULD each be below 2 mW and 0.5 mW for when the device is in a dynamic or static condition.

If device implementations include a 3-axis accelerometer and a 3-axis gyroscope sensor, they:

• [C-3-1] MUST implement the TYPE_GRAVITY and TYPE_LINEAR_ACCELERATION composite sensors.
• [C-SR] Are STRONGLY RECOMMENDED to implement the TYPE_GAME_ROTATION_VECTOR composite sensor.

If device implementations include a 3-axis accelerometer, a 3-axis gyroscope sensor, and a magnetometer sensor, they:

• [C-4-1] MUST implement a TYPE_ROTATION_VECTOR composite sensor.

7.3.2. magnetometer

Implementasi perangkat:

• [C-SR] Are STRONGLY RECOMMENDED to include a 3-axis magnetometer (compass).

If device implementations include a 3-axis magnetometer, they:

• [C-1-1] MUST implement the TYPE_MAGNETIC_FIELD sensor.
• [C-1-2] MUST be able to report events up to a frequency of at least 10 Hz and SHOULD report events up to at least 50 Hz.
• [C-1-3] MUST comply with the Android sensor coordinate system as detailed in the Android APIs.
• [C-1-4] MUST be capable of measuring between -900 µT and +900 µT on each axis before saturating.
• [C-1-5] MUST have a hard iron offset value less than 700 µT and SHOULD have a value below 200 µT, by placing the magnetometer far from dynamic (current-induced) and static (magnet-induced) magnetic fields.
• [C-1-6] MUST have a resolution equal or denser than 0.6 µT.
• [C-1-7] MUST support online calibration and compensation of the hard iron bias, and preserve the compensation parameters between device reboots.
• [C-1-8] MUST have the soft iron compensation applied—the calibration can be done either while in use or during the production of the device.
• [C-1-9] MUST have a standard deviation, calculated on a per axis basis on samples collected over a period of at least 3 seconds at the fastest sampling rate, no greater than 1.5 µT; SHOULD have a standard deviation no greater than 0.5 µT.
• SHOULD implement TYPE_MAGNETIC_FIELD_UNCALIBRATED sensor.
• [SR] Existing and new Android devices are STRONGLY RECOMMENDED to implement the TYPE_MAGNETIC_FIELD_UNCALIBRATED sensor.

If device implementations include a 3-axis magnetometer, an accelerometer sensor, and a 3-axis gyroscope sensor, they:

• [C-2-1] MUST implement a TYPE_ROTATION_VECTOR composite sensor.

If device implementations include a 3-axis magnetometer, an accelerometer, they:

• MAY implement the TYPE_GEOMAGNETIC_ROTATION_VECTOR sensor.

If device implementations include a 3-axis magnetometer, an accelerometer and TYPE_GEOMAGNETIC_ROTATION_VECTOR sensor, they:

• [C-3-1] MUST consume less than 10 mW.
• SHOULD consume less than 3 mW when the sensor is registered for batch mode at 10 Hz.

7.3.3. GPS

Implementasi perangkat:

• [C-SR] Are STRONGLY RECOMMENDED to include a GPS/GNSS receiver.

If device implementations include a GPS/GNSS receiver and report the capability to applications through the android.hardware.location.gps feature flag, they:

• [C-1-1] MUST support location outputs at a rate of at least 1 Hz when requested via LocationManager#requestLocationUpdate .
• [C-1-2] MUST be able to determine the location in open-sky conditions (strong signals, negligible multipath, HDOP < 2) within 10 seconds (fast time to first fix), when connected to a 0.5 Mbps or faster data speed internet connection. This requirement is typically met by the use of some form of Assisted or Predicted GPS/GNSS technique to minimize GPS/GNSS lock-on time (Assistance data includes Reference Time, Reference Location and Satellite Ephemeris/Clock).
  • [C-1-6] After making such a location calculation, device implementations MUST determine its location, in open sky, within 5 seconds, when location requests are restarted, up to an hour after the initial location calculation, even when the subsequent request is made without a data connection, and/or after a power cycle.

• In open sky conditions after determining the location, while stationary or moving with less than 1 meter per second squared of acceleration:

  • [C-1-3] MUST be able to determine location within 20 meters, and speed within 0.5 meters per second, at least 95% of the time.
  • [C-1-4] MUST simultaneously track and report via GnssStatus.Callback at least 8 satellites from one constellation.
  • SHOULD be able to simultaneously track at least 24 satellites, from multiple constellations (eg GPS + at least one of Glonass, Beidou, Galileo).
  • [C-SR] Are STRONGLY RECOMMENDED to continue to deliver normal GPS/GNSS location outputs through GNSS Location Provider APIs during an emergency phone call.
  • [C-SR] Are STRONGLY RECOMMENDED to report GNSS measurements from all constellations tracked (as reported in GnssStatus messages), with the exception of SBAS.
  • [C-SR] Are STRONGLY RECOMMENDED to report AGC, and Frequency of GNSS measurement.
  • [C-SR] Are STRONGLY RECOMMENDED to report all accuracy estimates (including Bearing, Speed, and Vertical) as part of each GPS/GNSS location.
  • [C-SR] Are STRONGLY RECOMMENDED to report GNSS measurements, as soon as they are found, even if a location calculated from GPS/GNSS is not yet reported.
  • [C-SR] Are STRONGLY RECOMMENDED to report GNSS pseudoranges and pseudorange rates, that, in open-sky conditions after determining the location, while stationary or moving with less than 0.2 meter per second squared of acceleration, are sufficient to calculate position within 20 meters, and speed within 0.2 meters per second, at least 95% of the time.

7.3.4. Giroskop

Implementasi perangkat:

• [C-SR] Are STRONGLY RECOMMENDED to include a gyroscope sensor unless a 3-axis accelerometer is also included.

If device implementations include a 3-axis gyroscope, they:

• [C-1-1] MUST be able to report events up to a frequency of at least 50 Hz.
• [C-1-2] MUST implement the TYPE_GYROSCOPE sensor and are STRONGLY RECOMMENDED to also implement the TYPE_GYROSCOPE_UNCALIBRATED sensor.
• [C-1-4] MUST have a resolution of 12-bits or more and SHOULD have a resolution of 16-bits or more.
• [C-1-5] MUST be temperature compensated.
• [C-1-6] MUST be calibrated and compensated while in use, and preserve the compensation parameters between device reboots.
• [C-1-7] MUST have a variance no greater than 1e-7 rad^2 / s^2 per Hz (variance per Hz, or rad^2 / s). The variance is allowed to vary with the sampling rate, but MUST be constrained by this value. In other words, if you measure the variance of the gyro at 1 Hz sampling rate it SHOULD be no greater than 1e-7 rad^2/s^2.
• [SR] Calibration error is STRONGLY RECOMMENDED to be less than 0.01 rad/s when device is stationary at room temperature.
• SHOULD report events up to at least 200 Hz.

If device implementations include a 3-axis gyroscope, an accelerometer sensor and a magnetometer sensor, they:

• [C-2-1] MUST implement a TYPE_ROTATION_VECTOR composite sensor.

If device implementations include a 3-axis accelerometer and a 3-axis gyroscope sensor, they:

• [C-3-1] MUST implement the TYPE_GRAVITY and TYPE_LINEAR_ACCELERATION composite sensors.
• [C-SR] Are STRONGLY RECOMMENDED to implement the TYPE_GAME_ROTATION_VECTOR composite sensor.

7.3.5. Barometer

Implementasi perangkat:

• [C-SR] Are STRONGLY RECOMMENDED to include a barometer (ambient air pressure sensor).

If device implementations include a barometer, they:

• [C-1-1] MUST implement and report TYPE_PRESSURE sensor.
• [C-1-2] MUST be able to deliver events at 5 Hz or greater.
• [C-1-3] MUST be temperature compensated.
• [SR] STRONGLY RECOMMENDED to be able to report pressure measurements in the range 300hPa to 1100hPa.
• SHOULD have an absolute accuracy of 1hPa.
• SHOULD have a relative accuracy of 0.12hPa over 20hPa range (equivalent to ~1m accuracy over ~200m change at sea level).

7.3.6. Termometer

Implementasi perangkat:

• MAY include an ambient thermometer (temperature sensor).
• MAY but SHOULD NOT include a CPU temperature sensor.

If device implementations include an ambient thermometer (temperature sensor), they:

• [C-1-1] MUST be defined as SENSOR_TYPE_AMBIENT_TEMPERATURE and MUST measure the ambient (room/vehicle cabin) temperature from where the user is interacting with the device in degrees Celsius.
• [C-1-2] MUST be defined as SENSOR_TYPE_TEMPERATURE .
• [C-1-3] MUST measure the temperature of the device CPU.
• [C-1-4] MUST NOT measure any other temperature.

Note the SENSOR_TYPE_TEMPERATURE sensor type was deprecated in Android 4.0.

7.3.7. Fotometer

• Device implementations MAY include a photometer (ambient light sensor).

7.3.8. Sensor jarak

• Device implementations MAY include a proximity sensor.

If device implementations include a proximity sensor, they:

• [C-1-1] MUST measure the proximity of an object in the same direction as the screen. That is, the proximity sensor MUST be oriented to detect objects close to the screen, as the primary intent of this sensor type is to detect a phone in use by the user. If device implementations include a proximity sensor with any other orientation, it MUST NOT be accessible through this API.
• [C-1-2] MUST have 1-bit of accuracy or more.

7.3.9. High Fidelity Sensors

If device implementations include a set of higher quality sensors as defined in this section, and make available them to third-party apps, they:

• [C-1-1] MUST identify the capability through the android.hardware.sensor.hifi_sensors feature flag.

If device implementations declare android.hardware.sensor.hifi_sensors , they:

• [C-2-1] MUST have a TYPE_ACCELEROMETER sensor which:

  • MUST have a measurement range between at least -8g and +8g, SHOULD have a measurement range between at least -16g and +16g.
  • MUST have a measurement resolution of at least 2048 LSB/g.
  • MUST have a minimum measurement frequency of 12.5 Hz or lower.
  • MUST have a maximum measurement frequency of 400 Hz or higher; SHOULD support the SensorDirectChannel RATE_VERY_FAST .
  • MUST have a measurement noise not above 400 μg/√Hz.
  • MUST implement a non-wake-up form of this sensor with a buffering capability of at least 3000 sensor events.
  • MUST have a batching power consumption not worse than 3 mW.
  • [C-SR] Is STRONGLY RECOMMENDED to have 3dB measurement bandwidth of at least 80% of Nyquist frequency, and white noise spectrum within this bandwidth.
  • SHOULD have an acceleration random walk less than 30 μg √Hz tested at room temperature.
  • SHOULD have a bias change vs. temperature of ≤ +/- 1 mg/°C.
  • SHOULD have a best-fit line non-linearity of ≤ 0.5%, and sensitivity change vs. temperature of ≤ 0.03%/C°.
  • SHOULD have cross-axis sensitivity of < 2.5 % and variation of cross-axis sensitivity < 0.2% in device operation temperature range.

• [C-2-2] MUST have a TYPE_ACCELEROMETER_UNCALIBRATED with the same quality requirements as TYPE_ACCELEROMETER .

• [C-2-3] MUST have a TYPE_GYROSCOPE sensor which:

  • MUST have a measurement range between at least -1000 and +1000 dps.
  • MUST have a measurement resolution of at least 16 LSB/dps.
  • MUST have a minimum measurement frequency of 12.5 Hz or lower.
  • MUST have a maximum measurement frequency of 400 Hz or higher; SHOULD support the SensorDirectChannel RATE_VERY_FAST .
  • MUST have a measurement noise not above 0.014°/s/√Hz.
  • [C-SR] Is STRONGLY RECOMMENDED to have 3dB measurement bandwidth of at least 80% of Nyquist frequency, and white noise spectrum within this bandwidth.
  • SHOULD have a rate random walk less than 0.001 °/s √Hz tested at room temperature.
  • SHOULD have a bias change vs. temperature of ≤ +/- 0.05 °/ s / °C.
  • SHOULD have a sensitivity change vs. temperature of ≤ 0.02% / °C.
  • SHOULD have a best-fit line non-linearity of ≤ 0.2%.
  • SHOULD have a noise density of ≤ 0.007 °/s/√Hz.
  • SHOULD have calibration error less than 0.002 rad/s in temperature range 10 ~ 40 ℃ when device is stationary.
  • SHOULD have g-sensitivity less than 0.1°/s/g.
  • SHOULD have cross-axis sensitivity of < 4.0 % and cross-axis sensitivity variation < 0.3% in device operation temperature range.

• [C-2-4] MUST have a TYPE_GYROSCOPE_UNCALIBRATED with the same quality requirements as TYPE_GYROSCOPE .

• [C-2-5] MUST have a TYPE_GEOMAGNETIC_FIELD sensor which:

  • MUST have a measurement range between at least -900 and +900 μT.
  • MUST have a measurement resolution of at least 5 LSB/uT.
  • MUST have a minimum measurement frequency of 5 Hz or lower.
  • MUST have a maximum measurement frequency of 50 Hz or higher.
  • MUST have a measurement noise not above 0.5 uT.

• [C-2-6] MUST have a TYPE_MAGNETIC_FIELD_UNCALIBRATED with the same quality requirements as TYPE_GEOMAGNETIC_FIELD and in addition:

  • MUST implement a non-wake-up form of this sensor with a buffering capability of at least 600 sensor events.
  • [C-SR] Is STRONGLY RECOMMENDED to have white noise spectrum from 1 Hz to at least 10 Hz when the report rate is 50 Hz or higher.

• [C-2-7] MUST have a TYPE_PRESSURE sensor which:

  • MUST have a measurement range between at least 300 and 1100 hPa.
  • MUST have a measurement resolution of at least 80 LSB/hPa.
  • MUST have a minimum measurement frequency of 1 Hz or lower.
  • MUST have a maximum measurement frequency of 10 Hz or higher.
  • MUST have a measurement noise not above 2 Pa/√Hz.
  • MUST implement a non-wake-up form of this sensor with a buffering capability of at least 300 sensor events.
  • MUST have a batching power consumption not worse than 2 mW.
• [C-2-8] MUST have a TYPE_GAME_ROTATION_VECTOR sensor.
• [C-2-9] MUST have a TYPE_SIGNIFICANT_MOTION sensor which:
  • MUST have a power consumption not worse than 0.5 mW when device is static and 1.5 mW when device is moving.
• [C-2-10] MUST have a TYPE_STEP_DETECTOR sensor which:
  • MUST implement a non-wake-up form of this sensor with a buffering capability of at least 100 sensor events.
  • MUST have a power consumption not worse than 0.5 mW when device is static and 1.5 mW when device is moving.
  • MUST have a batching power consumption not worse than 4 mW.
• [C-2-11] MUST have a TYPE_STEP_COUNTER sensor which:
  • MUST have a power consumption not worse than 0.5 mW when device is static and 1.5 mW when device is moving.
• [C-2-12] MUST have a TILT_DETECTOR sensor which:
  • MUST have a power consumption not worse than 0.5 mW when device is static and 1.5 mW when device is moving.
• [C-2-13] The event timestamp of the same physical event reported by the Accelerometer, Gyroscope, and Magnetometer MUST be within 2.5 milliseconds of each other. The event timestamp of the same physical event reported by the Accelerometer and Gyroscope SHOULD be within 0.25 milliseconds of each other.
• [C-2-14] MUST have Gyroscope sensor event timestamps on the same time base as the camera subsystem and within 1 milliseconds of error.
• [C-2-15] MUST deliver samples to applications within 5 milliseconds from the time when the data is available on any of the above physical sensors to the application.
• [C-2-16] MUST NOT have a power consumption higher than 0.5 mW when device is static and 2.0 mW when device is moving when any combination of the following sensors are enabled:
  • SENSOR_TYPE_SIGNIFICANT_MOTION
  • SENSOR_TYPE_STEP_DETECTOR
  • SENSOR_TYPE_STEP_COUNTER
  • SENSOR_TILT_DETECTORS
• [C-2-17] MAY have a TYPE_PROXIMITY sensor, but if present MUST have a minimum buffer capability of 100 sensor events.

Note that all power consumption requirements in this section do not include the power consumption of the Application Processor. It is inclusive of the power drawn by the entire sensor chain—the sensor, any supporting circuitry, any dedicated sensor processing system, etc.

If device implementations include direct sensor support, they:

• [C-3-1] MUST correctly declare support of direct channel types and direct report rates level through the isDirectChannelTypeSupported and getHighestDirectReportRateLevel API.
• [C-3-2] MUST support at least one of the two sensor direct channel types for all sensors that declare support for sensor direct channel.
  • TYPE_HARDWARE_BUFFER
  • TYPE_MEMORY_FILE
• SHOULD support event reporting through sensor direct channel for primary sensor (non-wakeup variant) of the following types:
  • TYPE_ACCELEROMETER
  • TYPE_ACCELEROMETER_UNCALIBRATED
  • TYPE_GYROSCOPE
  • TYPE_GYROSCOPE_UNCALIBRATED
  • TYPE_MAGNETIC_FIELD
  • TYPE_MAGNETIC_FIELD_UNCALIBRATED

7.3.10. Sensor Biometrik

For additional background on Measuring Biometric Unlock Security, please see Measuring Biometric Security documentation .

If device implementations include a secure lock screen, they:

• SHOULD include a biometric sensor

Biometric sensors can be classified as Strong , Weak , or Convenience based on their spoof and imposter acceptance rates, and on the security of the biometric pipeline. This classification determines the capabilities the biometric sensor has to interface with the platform and with third-party applications. Sensors are classified as Convenience by default, and need to meet additional requirements as detailed below if they wish to be classified as either Weak or Strong . Both Weak and Strong biometrics get additional capabilities as detailed below.

To make a biometric sensor available to third-party applications, device implementations:

• [C-0-1] MUST meet the requirements for Strong or Weak biometric as defined in this document.

To allow access to keystore keys to third-party applications, device implementations:

• [C-0-2] MUST meet the requirements for Strong as defined in this document.

Selain itu:

• [C-0-3] MUST be paired with an explicit confirm action (eg a button press) if that Strong biometric is passive (eg face or iris where no explicit signal of the user's intent exists).
  • [C-SR] The confirm action for passive biometrics is STRONGLY RECOMMENDED to be secured such that an operating system or kernel compromise cannot spoof it. For example, this means that the confirm action based on a physical button is routed through an input-only general-purpose input/output (GPIO) pin of a secure element (SE) that cannot be driven by any other means than a physical button tekan.

If device implementations wish to treat a biometric sensor as Convenience , they:

• [C-1-1] MUST have a false acceptance rate less than 0.002%.
• [C-1-2] MUST disclose that this mode may be less secure than a strong PIN, pattern, or password and clearly enumerate the risks of enabling it, if the spoof and imposter acceptance rates are higher than 7%.
• [C-1-3] MUST rate limit attempts for at least 30 seconds after five false trials for biometric verification - where a false trial is one with an adequate capture quality ( BIOMETRIC_ACQUIRED_GOOD ) that does not match an enrolled biometric.
• [C-1-4] MUST prevent adding new biometrics without first establishing a chain of trust by having the user confirm existing or add a new device credential (PIN/pattern/password) that's secured by TEE; the Android Open Source Project implementation provides the mechanism in the framework to do so.
• [C-1-5] MUST completely remove all identifiable biometric data for a user when the user's account is removed (including via a factory reset).
• [C-1-6] MUST honor the individual flag for that biometric (ie DevicePolicyManager.KEYGUARD_DISABLE_FINGERPRINT , DevicePolicymanager.KEYGUARD_DISABLE_FACE , or DevicePolicymanager.KEYGUARD_DISABLE_IRIS ).
• [C-1-7] MUST challenge the user for the recommended primary authentication (eg PIN, pattern, password) once every 24 hours or less for new devices launching with Android version 10, once every 72 hours or less for devices upgrading from earlier versi Android.

• [C-1-8] MUST challenge the user for the recommended primary authentication (eg: PIN, pattern, password) after one of the following:

  • A 4-hour idle timeout period, OR
  • 3 failed biometric authentication attempts.
  • The idle timeout period and the failed authentication count is reset after any successful confirmation of the device credentials.

  Upgrading devices from an earlier Android version can be exempted from C-1-8.

• [C-SR] Are STRONGLY RECOMMENDED to have a false rejection rate of less than 10%, as measured on the device.

• [C-SR] Are STRONGLY RECOMMENDED to have a latency below 1 second, measured from when the biometric is detected, until the screen is unlocked, for each enrolled biometric.

If device implementations wish to treat a biometric sensor as Weak , they:

• [C-2-1] MUST meet all requirements for Convenience above, except for [C-1-2].
• [C-2-2] MUST have a spoof and imposter acceptance rate not higher than 20%.
• [C-2-3] MUST have a hardware-backed keystore implementation, and perform the biometric matching in an isolated execution environment outside Android user or kernel space, such as the Trusted Execution Environment (TEE), or on a chip with a secure channel to the isolated execution environment.
• [C-2-4] MUST have all identifiable data encrypted and cryptographically authenticated such that they cannot be acquired, read or altered outside of the isolated execution environment or a chip with a secure channel to the isolated execution environment as documented in the implementation guidelines on the Android Open Source Project site.
• [C-2-5] For camera based biometrics, while biometric based authentication or enrollment is happening:
  • MUST operate the camera in a mode that prevents camera frames from being read or altered outside the isolated execution environment or a chip with a secure channel to the isolated execution environment.
  • For RGB single-camera solutions, the camera frames CAN be readable outside the isolated execution environment to support operations such as preview for enrollment, but MUST still NOT be alterable.
• [C-2-6] MUST NOT enable third-party applications to distinguish between individual biometric enrollments.
• [C-2-7] MUST NOT allow unencrypted access to identifiable biometric data or any data derived from it (such as embeddings) to the Application Processor outside the context of the TEE.

• [C-2-8] MUST have a secure processing pipeline such that an operating system or kernel compromise cannot allow data to be directly injected to falsely authenticate as the user.

  If device implementations are already launched on an earlier Android version and cannot meet the requirement C-2-8 through a system software update, they MAY be exempted from the requirement.

If device implementations wish to treat a biometric sensor as Strong , they:

• [C-3-1] MUST meet all the requirements of Weak above. Upgrading devices from an earlier Android version is not exempted from C-2-7.
• [C-3-2] MUST have a spoof and imposter acceptance rate not higher than 7%.
• [C-3-3] MUST challenge the user for the recommended primary authentication (eg PIN, pattern, password) once every 72 hours or less.

7.3.12. Pose Sensor

Implementasi perangkat:

• MAY support pose sensor with 6 degrees of freedom.

If device implementations support pose sensor with 6 degrees of freedom, they:

• [C-1-1] MUST implement and report TYPE_POSE_6DOF sensor.
• [C-1-2] MUST be more accurate than the rotation vector alone.

7.4. Konektivitas Data

7.4.1. Telepon

“Telephony” as used by the Android APIs and this document refers specifically to hardware related to placing voice calls and sending SMS messages via a GSM or CDMA network. While these voice calls may or may not be packet-switched, they are for the purposes of Android considered independent of any data connectivity that may be implemented using the same network. In other words, the Android “telephony” functionality and APIs refer specifically to voice calls and SMS. For instance, device implementations that cannot place calls or send/receive SMS messages are not considered a telephony device, regardless of whether they use a cellular network for data connectivity.

• Android MAY be used on devices that do not include telephony hardware. That is, Android is compatible with devices that are not phones.

If device implementations include GSM or CDMA telephony, they:

• [C-1-1] MUST declare the android.hardware.telephony feature flag and other sub-feature flags according to the technology.
• [C-1-2] MUST implement full support for the API for that technology.

If device implementations do not include telephony hardware, they:

• [C-2-1] MUST implement the full APIs as no-ops.

If device implementations support eUICCs or eSIMs/embedded SIMs and include a proprietary mechanism to make eSIM functionality available for third-party developers, they:

• [C-3-1] MUST provide a complete implementation of the EuiccManager API .

7.4.1.1. Number Blocking Compatibility

If device implementations report the android.hardware.telephony feature , they:

• [C-1-1] MUST include number blocking support
• [C-1-2] MUST fully implement BlockedNumberContract and the corresponding API as described in the SDK documentation.
• [C-1-3] MUST block all calls and messages from a phone number in 'BlockedNumberProvider' without any interaction with apps. The only exception is when number blocking is temporarily lifted as described in the SDK documentation.
• [C-1-4] MUST NOT write to the platform call log provider for a blocked call.
• [C-1-5] MUST NOT write to the Telephony provider for a blocked message.
• [C-1-6] MUST implement a blocked numbers management UI, which is opened with the intent returned by TelecomManager.createManageBlockedNumbersIntent() method.
• [C-1-7] MUST NOT allow secondary users to view or edit the blocked numbers on the device as the Android platform assumes the primary user to have full control of the telephony services, a single instance, on the device. All blocking related UI MUST be hidden for secondary users and the blocked list MUST still be respected.
• SHOULD migrate the blocked numbers into the provider when a device updates to Android 7.0.

7.4.1.2. Telecom API

Jika implementasi perangkat melaporkan android.hardware.telephony , mereka:

• [C-1-1] MUST support the ConnectionService APIs described in the SDK .
• [C-1-2] MUST display a new incoming call and provide user affordance to accept or reject the incoming call when the user is on an ongoing call that is made by a third-party app that does not support the hold feature specified via CAPABILITY_SUPPORT_HOLD .
• [C-1-3] MUST have an application that implements InCallService .

• [C-SR] Are STRONGLY RECOMMENDED to notify the user that answering an incoming call will drop an ongoing call.

  The AOSP implementation meets these requirements by a heads-up notification which indicates to the user that answering an incoming call will cause the other call to be dropped.

• [C-SR] Are STRONGLY RECOMMENDED to preload the default dialer app that shows a call log entry and the name of a third-party app in its call log when the third-party app sets the EXTRA_LOG_SELF_MANAGED_CALLS extras key on its PhoneAccount to true .

• [C-SR] Are STRONGLY RECOMMENDED to handle the audio headset's KEYCODE_MEDIA_PLAY_PAUSE and KEYCODE_HEADSETHOOK events for the android.telecom APIs as below:
  • Call Connection.onDisconnect() when a short press of the key event is detected during an ongoing call.
  • Call Connection.onAnswer() when a short press of the key event is detected during an incoming call.
  • Call Connection.onReject() when a long press of the key event is detected during an incoming call.
  • Toggle the mute status of the CallAudioState .

7.4.2. IEEE 802.11 (Wi-Fi)

Implementasi perangkat:

• SHOULD include support for one or more forms of 802.11.

If device implementations include support for 802.11 and expose the functionality to a third-party application, they:

• [C-1-1] MUST implement the corresponding Android API.
• [C-1-2] MUST report the hardware feature flag android.hardware.wifi .
• [C-1-3] MUST implement the multicast API as described in the SDK documentation.
• [C-1-4] MUST support multicast DNS (mDNS) and MUST NOT filter mDNS packets (224.0.0.251) at any time of operation including:
  • Even when the screen is not in an active state.
  • For Android Television device implementations, even when in standby power states.
• [C-1-5] MUST NOT treat the WifiManager.enableNetwork() API method call as a sufficient indication to switch the currently active Network that is used by default for application traffic and is returned by ConnectivityManager API methods such as getActiveNetwork and registerDefaultNetworkCallback . In other words, they MAY only disable the Internet access provided by any other network provider (eg mobile data) if they successfully validate that the Wi-Fi network is providing Internet access.
• [C-1-6] Are STRONGLY RECOMMENDED to, when the ConnectivityManager.reportNetworkConnectivity() API method is called, re-evaluate the Internet access on the Network and, once the evaluation determines that the current Network no longer provides Internet access, switch to any other available network (eg mobile data) that provides Internet access.
• [C-SR] Are STRONGLY RECOMMENDED to randomize the source MAC address and sequence number of probe request frames, once at the beginning of each scan, while STA is disconnected.
  • Each group of probe request frames comprising one scan SHOULD use one consistent MAC address (SHOULD NOT randomize MAC address halfway through a scan).
  • Probe request sequence number SHOULD iterate as normal (sequentially) between the probe requests in a scan.
  • Probe request sequence number SHOULD randomize between the last probe request of a scan and the first probe request of the next scan.
• [C-SR] Are STRONGLY RECOMMENDED, while STA is disconnected, to allow only the following elements in probe request frames:
  • SSID Parameter Set (0)
  • DS Parameter Set (3)

If device implementations include support for Wi-Fi power save mode as defined in IEEE 802.11 standard, they:

• [C-3-1] MUST turn off Wi-Fi power save mode whenever an app acquires WIFI_MODE_FULL_HIGH_PERF lock or WIFI_MODE_FULL_LOW_LATENCY lock via WifiManager.createWifiLock() and WifiManager.WifiLock.acquire() APIs and the lock is active.
• [C-3-2] The average round trip latency between the device and an access point while the device is in a Wi-Fi Low Latency Lock ( WIFI_MODE_FULL_LOW_LATENCY ) mode MUST be smaller than the latency during a Wi-Fi High Perf Lock ( WIFI_MODE_FULL_HIGH_PERF ) mode.
• [C-SR] Are STRONGLY RECOMMENDED to minimize Wi-Fi round trip latency whenever a Low Latency Lock ( WIFI_MODE_FULL_LOW_LATENCY ) is acquired and takes effect.

If device implementations support Wi-Fi and use Wi-Fi for location scanning, they:

• [C-2-1] MUST provide a user affordance to enable/disable the value read through the WifiManager.isScanAlwaysAvailable API method.

7.4.2.1. Wi-Fi Langsung

Implementasi perangkat:

• SHOULD include support for Wi-Fi Direct (Wi-Fi peer-to-peer).

If device implementations include support for Wi-Fi Direct, they:

• [C-1-1] MUST implement the corresponding Android API as described in the SDK documentation.
• [C-1-2] MUST report the hardware feature android.hardware.wifi.direct .
• [C-1-3] MUST support regular Wi-Fi operation.
• [C-1-4] MUST support Wi-Fi and Wi-Fi Direct operations concurrently.

7.4.2.2. Wi-Fi Tunneled Direct Link Setup

Implementasi perangkat:

• SHOULD include support for Wi-Fi Tunneled Direct Link Setup (TDLS) as described in the Android SDK Documentation.

If device implementations include support for TDLS and TDLS is enabled by the WiFiManager API, they:

• [C-1-1] MUST declare support for TDLS through WifiManager.isTdlsSupported .
• SHOULD use TDLS only when it is possible AND beneficial.
• SHOULD have some heuristic and NOT use TDLS when its performance might be worse than going through the Wi-Fi access point.

7.4.2.3. Sadar Wi-Fi

Implementasi perangkat:

• SHOULD include support for Wi-Fi Aware .

If device implementations include support for Wi-Fi Aware and expose the functionality to third-party apps, then they:

• [C-1-1] MUST implement the WifiAwareManager APIs as described in the SDK documentation .
• [C-1-2] MUST declare the android.hardware.wifi.aware feature flag.
• [C-1-3] MUST support Wi-Fi and Wi-Fi Aware operations concurrently.
• [C-1-4] MUST randomize the Wi-Fi Aware management interface address at intervals no longer than 30 minutes and whenever Wi-Fi Aware is enabled.

If device implementations include support for Wi-Fi Aware and Wi-Fi Location as described in Section 7.4.2.5 and exposes these functionalities to third-party apps, then they:

• [C-2-1] MUST implement the location-aware discovery APIs: setRangingEnabled , setMinDistanceMm , setMaxDistanceMm , and onServiceDiscoveredWithinRange .

7.4.2.4. Titik Akses Wi-Fi

Implementasi perangkat:

• SHOULD include support for Wi-Fi Passpoint .

If device implementations include support for Wi-Fi Passpoint, they:

• [C-1-1] MUST implement the Passpoint related WifiManager APIs as described in the SDK documentation .
• [C-1-2] MUST support IEEE 802.11u standard, specifically related to Network Discovery and Selection, such as Generic Advertisement Service (GAS) and Access Network Query Protocol (ANQP).

Conversely if device implementations do not include support for Wi-Fi Passpoint:

• [C-2-1] The implementation of the Passpoint related WifiManager APIs MUST throw an UnsupportedOperationException .

7.4.2.5. Wi-Fi Location (Wi-Fi Round Trip Time - RTT)

Implementasi perangkat:

• SHOULD include support for Wi-Fi Location .

If device implementations include support for Wi-Fi Location and expose the functionality to third-party apps, then they:

• [C-1-1] MUST implement the WifiRttManager APIs as described in the SDK documentation .
• [C-1-2] MUST declare the android.hardware.wifi.rtt feature flag.
• [C-1-3] MUST randomize the source MAC address for each RTT burst which is executed while the Wi-Fi interface on which the RTT is being executed is not associated to an Access Point.

7.4.2.6. Wi-Fi Keepalive Offload

Implementasi perangkat:

• SHOULD include support for Wi-Fi keepalive offload.

If device implementations include support for Wi-Fi keepalive offload and expose the functionality to third-party apps, they:

• [C-1-1] MUST support the SocketKeepAlive API.

• [C-1-2] MUST support at least three concurrent keepalive slots over Wi-Fi and at least one keepalive slot over cellular.

If device implementations do not include support for Wi-Fi keepalive offload, they:

• [C-2-1] MUST return ERROR_UNSUPPORTED .

7.4.2.7. Wi-Fi Easy Connect (Device Provisioning Protocol)

Implementasi perangkat:

• SHOULD include support for Wi-Fi Easy Connect (DPP) .

If device implementations include support for Wi-Fi Easy Connect and expose the functionality to third-party apps, they:

• [C-1-1] MUST implement the Settings#ACTION_PROCESS_WIFI_EASY_CONNECT_URI Intent APIs as described in the SDK documentation.
• [C-1-2] MUST have the WifiManager#isEasyConnectSupported() method return true .

7.4.3. Bluetooth

If device implementations support Bluetooth Audio profile, they:

• SHOULD support Advanced Audio Codecs and Bluetooth Audio Codecs (eg LDAC).

If device implementations support HFP, A2DP and AVRCP, they:

• SHOULD support at least 5 total connected devices.

If device implementations declare android.hardware.vr.high_performance feature, they:

• [C-1-1] MUST support Bluetooth 4.2 and Bluetooth LE Data Length Extension.

Android includes support for Bluetooth and Bluetooth Low Energy .

If device implementations include support for Bluetooth and Bluetooth Low Energy, they:

• [C-2-1] MUST declare the relevant platform features ( android.hardware.bluetooth and android.hardware.bluetooth_le respectively) and implement the platform APIs.
• SHOULD implement relevant Bluetooth profiles such as A2DP, AVRCP, OBEX, HFP, etc. as appropriate for the device.

If device implementations include support for Bluetooth Low Energy, they:

• [C-3-1] MUST declare the hardware feature android.hardware.bluetooth_le .
• [C-3-2] MUST enable the GATT (generic attribute profile) based Bluetooth APIs as described in the SDK documentation and android.bluetooth .
• [C-3-3] MUST report the correct value for BluetoothAdapter.isOffloadedFilteringSupported() to indicate whether the filtering logic for the ScanFilter API classes is implemented.
• [C-3-4] MUST report the correct value for BluetoothAdapter.isMultipleAdvertisementSupported() to indicate whether Low Energy Advertising is supported.
• SHOULD support offloading of the filtering logic to the bluetooth chipset when implementing the ScanFilter API .
• SHOULD support offloading of the batched scanning to the bluetooth chipset.

• SHOULD support multi advertisement with at least 4 slots.

• [SR] STRONGLY RECOMMENDED to implement a Resolvable Private Address (RPA) timeout no longer than 15 minutes and rotate the address at timeout to protect user privacy.

If device implementations support Bluetooth LE and use Bluetooth LE for location scanning, they:

• [C-4-1] MUST provide a user affordance to enable/disable the value read through the System API BluetoothAdapter.isBleScanAlwaysAvailable() .

If device implementations include support for Bluetooth LE and Hearing Aids Profile, as described in Hearing Aid Audio Support Using Bluetooth LE , they:

• [C-5-1] MUST return true for BluetoothAdapter.getProfileProxy(context, listener, BluetoothProfile.HEARING_AID) .

7.4.4. Near-Field Communications

Implementasi perangkat:

• SHOULD include a transceiver and related hardware for Near-Field Communications (NFC).
• [C-0-1] MUST implement android.nfc.NdefMessage and android.nfc.NdefRecord APIs even if they do not include support for NFC or declare the android.hardware.nfc feature as the classes represent a protocol-independent data representation format .

If device implementations include NFC hardware and plan to make it available to third-party apps, they:

• [C-1-1] MUST report the android.hardware.nfc feature from the android.content.pm.PackageManager.hasSystemFeature() method .
• MUST be capable of reading and writing NDEF messages via the following NFC standards as below:
• [C-1-2] MUST be capable of acting as an NFC Forum reader/writer (as defined by the NFC Forum technical specification NFCForum-TS-DigitalProtocol-1.0) via the following NFC standards:
  • NfcA (ISO14443-3A)
  • NfcB (ISO14443-3B)
  • NfcF (JIS X 6319-4)
  • IsoDep (ISO 14443-4)
  • NFC Forum Tag Types 1, 2, 3, 4, 5 (defined by the NFC Forum)

• [SR] STRONGLY RECOMMENDED to be capable of reading and writing NDEF messages as well as raw data via the following NFC standards. Note that while the NFC standards are stated as STRONGLY RECOMMENDED, the Compatibility Definition for a future version is planned to change these to MUST. These standards are optional in this version but will be required in future versions. Existing and new devices that run this version of Android are VERY STRONGLY ENCOURAGED to meet these requirements now so they will be able to upgrade to the future platform releases.

• [C-1-13] MUST poll for all supported technologies while in NFC discovery mode.

• SHOULD be in NFC discovery mode while the device is awake with the screen active and the lock-screen unlocked.
• SHOULD be capable of reading the barcode and URL (if encoded) of Thinfilm NFC Barcode products.

Note that publicly available links are not available for the JIS, ISO, and NFC Forum specifications cited above.

Android includes support for NFC Host Card Emulation (HCE) mode.

If device implementations include an NFC controller chipset capable of HCE (for NfcA and/or NfcB) and support Application ID (AID) routing, they:

• [C-2-1] MUST report the android.hardware.nfc.hce feature constant.
• [C-2-2] MUST support NFC HCE APIs as defined in the Android SDK.

If device implementations include an NFC controller chipset capable of HCE for NfcF, and implement the feature for third-party applications, they:

• [C-3-1] MUST report the android.hardware.nfc.hcef feature constant.
• [C-3-2] MUST implement the NfcF Card Emulation APIs as defined in the Android SDK.

If device implementations include general NFC support as described in this section and support MIFARE technologies (MIFARE Classic, MIFARE Ultralight, NDEF on MIFARE Classic) in the reader/writer role, they:

• [C-4-1] MUST implement the corresponding Android APIs as documented by the Android SDK.
• [C-4-2] MUST report the feature com.nxp.mifare from the android.content.pm.PackageManager.hasSystemFeature () method. Note that this is not a standard Android feature and as such does not appear as a constant in the android.content.pm.PackageManager class.

7.4.5. Minimum Network Capability

Implementasi perangkat:

• [C-0-1] MUST include support for one or more forms of data networking. Specifically, device implementations MUST include support for at least one data standard capable of 200 Kbit/sec or greater. Examples of technologies that satisfy this requirement include EDGE, HSPA, EV-DO, 802.11g, Ethernet and Bluetooth PAN.
• SHOULD also include support for at least one common wireless data standard, such as 802.11 (Wi-Fi), when a physical networking standard (such as Ethernet) is the primary data connection.
• MAY implement more than one form of data connectivity.
• [C-0-2] MUST include an IPv6 networking stack and support IPv6 communication using the managed APIs, such as java.net.Socket and java.net.URLConnection , as well as the native APIs, such as AF_INET6 sockets.
• [C-0-3] MUST enable IPv6 by default.
• MUST ensure that IPv6 communication is as reliable as IPv4, for example:
  • [C-0-4] MUST maintain IPv6 connectivity in doze mode.
  • [C-0-5] Rate-limiting MUST NOT cause the device to lose IPv6 connectivity on any IPv6-compliant network that uses RA lifetimes of at least 180 seconds.
• [C-0-6] MUST provide third-party applications with direct IPv6 connectivity to the network when connected to an IPv6 network, without any form of address or port translation happening locally on the device. Both managed APIs such as Socket#getLocalAddress or Socket#getLocalPort ) and NDK APIs such as getsockname() or IPV6_PKTINFO MUST return the IP address and port that is actually used to send and receive packets on the network.

The required level of IPv6 support depends on the network type, as shown in the following requirements.

If device implementations support Wi-Fi, they:

• [C-1-1] MUST support dual-stack and IPv6-only operation on Wi-Fi.

If device implementations support Ethernet, they:

• [C-2-1] MUST support dual-stack operation on Ethernet.

If device implementations support Cellular data, they:

• SHOULD support IPv6 operation (IPv6-only and possibly dual-stack) on cellular.

If device implementations support more than one network type (eg, Wi-Fi and cellular data), they:

• [C-3-1] MUST simultaneously meet the above requirements on each network when the device is simultaneously connected to more than one network type.

7.4.6. Pengaturan Sinkronisasi

Implementasi perangkat:

• [C-0-1] MUST have the master auto-sync setting on by default so that the method getMasterSyncAutomatically() returns “true”.

7.4.7. Penghemat Kuota

If device implementations include a metered connection, they are:

• [SR] STRONGLY RECOMMENDED to provide the data saver mode.

If device implementations provide the data saver mode, they:

• [C-1-1] MUST support all the APIs in the ConnectivityManager class as described in the SDK documentation
• [C-1-2] MUST provide a user interface in the settings, that handles the Settings.ACTION_IGNORE_BACKGROUND_DATA_RESTRICTIONS_SETTINGS intent, allowing users to add applications to or remove applications from the allowlist.

If device implementations do not provide the data saver mode, they:

• [C-2-1] MUST return the value RESTRICT_BACKGROUND_STATUS_DISABLED for ConnectivityManager.getRestrictBackgroundStatus()
• [C-2-2] MUST NOT broadcast ConnectivityManager.ACTION_RESTRICT_BACKGROUND_CHANGED .
• [C-2-3] MUST have an activity that handles the Settings.ACTION_IGNORE_BACKGROUND_DATA_RESTRICTIONS_SETTINGS intent but MAY implement it as a no-op.

7.4.8. Secure Elements

If device implementations support Open Mobile API capable secure elements and make them available to 3rd-party apps, they:

• [C-1-1] MUST enumerate the available Secure Elements readers when android.se.omapi.SEService.getReaders() method is called.

7.5. Kamera

If device implementations include at least one camera, they:

• [C-1-1] MUST declare the android.hardware.camera.any feature flag.
• [C-1-2] MUST be possible for an application to simultaneously allocate 3 RGBA_8888 bitmaps equal to the size of the images produced by the largest-resolution camera sensor on the device, while camera is open for the purpose of basic preview and still menangkap.
• [C-1-3] MUST ensure that the preinstalled default camera application handling intents MediaStore.ACTION_IMAGE_CAPTURE , MediaStore.ACTION_IMAGE_CAPTURE_SECURE , or MediaStore.ACTION_VIDEO_CAPTURE , is responsible for removing the user location in the image metadata before sending it to the receiving application when the receiving application does not have ACCESS_FINE_LOCATION .

7.5.1. Kamera Menghadap ke Belakang

A rear-facing camera is a camera located on the side of the device opposite the display; that is, it images scenes on the far side of the device, like a traditional camera.

Implementasi perangkat:

• SHOULD include a rear-facing camera.

If device implementations include at least one rear-facing camera, they:

• [C-1-1] MUST report the feature flag android.hardware.camera and android.hardware.camera.any .
• [C-1-2] MUST have a resolution of at least 2 megapixels.
• SHOULD have either hardware auto-focus or software auto-focus implemented in the camera driver (transparent to application software).
• MAY have fixed-focus or EDOF (extended depth of field) hardware.
• MAY include a flash.

If the camera includes a flash:

• [C-2-1] the flash lamp MUST NOT be lit while an android.hardware.Camera.PreviewCallback instance has been registered on a Camera preview surface, unless the application has explicitly enabled the flash by enabling the FLASH_MODE_AUTO or FLASH_MODE_ON attributes of a Camera.Parameters object. Note that this constraint does not apply to the device's built-in system camera application, but only to third-party applications using Camera.PreviewCallback .

7.5.2. Kamera Menghadap Depan

A front-facing camera is a camera located on the same side of the device as the display; that is, a camera typically used to image the user, such as for video conferencing and similar applications.

Implementasi perangkat:

• MAY include a front-facing camera.

If device implementations include at least one front-facing camera, they:

• [C-1-1] MUST report the feature flag android.hardware.camera.any and android.hardware.camera.front .
• [C-1-2] MUST have a resolution of at least VGA (640x480 pixels).
• [C-1-3] MUST NOT use a front-facing camera as the default for the Camera API and MUST NOT configure the API to treat a front-facing camera as the default rear-facing camera, even if it is the only camera pada perangkat.
• [C-1-4] The camera preview MUST be mirrored horizontally relative to the orientation specified by the application when the current application has explicitly requested that the Camera display be rotated via a call to the android.hardware.Camera.setDisplayOrientation() method . Conversely, the preview MUST be mirrored along the device's default horizontal axis when the current application does not explicitly request that the Camera display be rotated via a call to the android.hardware.Camera.setDisplayOrientation() method.
• [C-1-5] MUST NOT mirror the final captured still image or video streams returned to application callbacks or committed to media storage.
• [C-1-6] MUST mirror the image displayed by the postview in the same manner as the camera preview image stream.
• MAY include features (such as auto-focus, flash, etc.) available to rear-facing cameras as described in section 7.5.1 .

If device implementations are capable of being rotated by user (such as automatically via an accelerometer or manually via user input):

• [C-2-1] The camera preview MUST be mirrored horizontally relative to the device's current orientation.

7.5.3. Kamera Eksternal

Implementasi perangkat:

• MAY include support for an external camera that is not necessarily always connected.

If device implementations include support for an external camera, they:

• [C-1-1] MUST declare the platform feature flag android.hardware.camera.external and android.hardware camera.any .
• [C-1-2] MUST support USB Video Class (UVC 1.0 or higher) if the external camera connects through the USB host port.
• [C-1-3] MUST pass camera CTS tests with a physical external camera device connected. Details of camera CTS testing are available at source.android.com .
• SHOULD support video compressions such as MJPEG to enable transfer of high-quality unencoded streams (ie raw or independently compressed picture streams).
• MAY support multiple cameras.
• MAY support camera-based video encoding.

If camera-based video encoding is supported:

• [C-2-1] A simultaneous unencoded / MJPEG stream (QVGA or greater resolution) MUST be accessible to the device implementation.

7.5.4. Camera API Behavior

Android includes two API packages to access the camera, the newer android.hardware.camera2 API expose lower-level camera control to the app, including efficient zero-copy burst/streaming flows and per-frame controls of exposure, gain, white balance gains, color conversion, denoising, sharpening, and more.

The older API package, android.hardware.Camera , is marked as deprecated in Android 5.0 but as it SHOULD still be available for apps to use. Android device implementations MUST ensure the continued support of the API as described in this section and in the Android SDK.

All features that are common between the deprecated android.hardware.Camera class and the newer android.hardware.camera2 package MUST have equivalent performance and quality in both APIs. For example, with equivalent settings, autofocus speed and accuracy MUST be identical, and the quality of captured images MUST be the same. Features that depend on the different semantics of the two APIs are not required to have matching speed or quality, but SHOULD match as closely as possible.

Device implementations MUST implement the following behaviors for the camera-related APIs, for all available cameras. Implementasi perangkat:

• [C-0-1] MUST use android.hardware.PixelFormat.YCbCr_420_SP for preview data provided to application callbacks when an application has never called android.hardware.Camera.Parameters.setPreviewFormat(int) .
• [C-0-2] MUST further be in the NV21 encoding format when an application registers an android.hardware.Camera.PreviewCallback instance and the system calls the onPreviewFrame() method and the preview format is YCbCr_420_SP, the data in the byte[] passed into onPreviewFrame() . That is, NV21 MUST be the default.
• [C-0-3] MUST support the YV12 format (as denoted by the android.graphics.ImageFormat.YV12 constant) for camera previews for both front- and rear-facing cameras for android.hardware.Camera . (The hardware video encoder and camera may use any native pixel format, but the device implementation MUST support conversion to YV12.)
• [C-0-4] MUST support the android.hardware.ImageFormat.YUV_420_888 and android.hardware.ImageFormat.JPEG formats as outputs through the android.media.ImageReader API for android.hardware.camera2 devices that advertise REQUEST_AVAILABLE_CAPABILITIES_BACKWARD_COMPATIBLE capability in android.request.availableCapabilities .
• [C-0-5] MUST still implement the full Camera API included in the Android SDK documentation, regardless of whether the device includes hardware autofocus or other capabilities. For instance, cameras that lack autofocus MUST still call any registered android.hardware.Camera.AutoFocusCallback instances (even though this has no relevance to a non-autofocus camera.) Note that this does apply to front-facing cameras; for instance, even though most front-facing cameras do not support autofocus, the API callbacks MUST still be “faked” as described.
• [C-0-6] MUST recognize and honor each parameter name defined as a constant in the android.hardware.Camera.Parameters class and the android.hardware.camera2.CaptureRequest class. Conversely, device implementations MUST NOT honor or recognize string constants passed to the android.hardware.Camera.setParameters() method other than those documented as constants on the android.hardware.Camera.Parameters . That is, device implementations MUST support all standard Camera parameters if the hardware allows, and MUST NOT support custom Camera parameter types. For instance, device implementations that support image capture using high dynamic range (HDR) imaging techniques MUST support camera parameter Camera.SCENE_MODE_HDR .
• [C-0-7] MUST report the proper level of support with the android.info.supportedHardwareLevel property as described in the Android SDK and report the appropriate framework feature flags .
• [C-0-8] MUST also declare its individual camera capabilities of android.hardware.camera2 via the android.request.availableCapabilities property and declare the appropriate feature flags ; MUST define the feature flag if any of its attached camera devices supports the feature.
• [C-0-9] MUST broadcast the Camera.ACTION_NEW_PICTURE intent whenever a new picture is taken by the camera and the entry of the picture has been added to the media store.
• [C-0-10] MUST broadcast the Camera.ACTION_NEW_VIDEO intent whenever a new video is recorded by the camera and the entry of the picture has been added to the media store.
• [C-0-11] MUST have all cameras accessible via the deprecated android.hardware.Camera API also accessible via the android.hardware.camera2 API.
• [C-SR] For devices with multiple RGB cameras facing in the same direction, are STRONGLY RECOMMENDED to support a logical camera device that lists capability CameraMetadata.REQUEST_AVAILABLE_CAPABILITIES_LOGICAL_MULTI_CAMERA , consisting of all of the RGB cameras facing that direction as physical sub-devices.

If device implementations provide a proprietary camera API to 3rd-party apps, they:

• [C-1-1] MUST implement such a camera API using android.hardware.camera2 API.
• MAY provide vendor tags and/or extensions to android.hardware.camera2 API.

7.5.5. Orientasi Kamera

If device implementations have a front- or a rear-facing camera, such camera(s):

• [C-1-1] MUST be oriented so that the long dimension of the camera aligns with the screen's long dimension. That is, when the device is held in the landscape orientation, cameras MUST capture images in the landscape orientation. This applies regardless of the device's natural orientation; that is, it applies to landscape-primary devices as well as portrait-primary devices.

7.6. Memori dan Penyimpanan

7.6.1. Minimum Memory and Storage

Implementasi perangkat:

• [C-0-1] MUST include a Download Manager that applications MAY use to download data files and they MUST be capable of downloading individual files of at least 100MB in size to the default “cache” location.

7.6.2. Application Shared Storage

Implementasi perangkat:

• [C-0-1] MUST offer storage to be shared by applications, also often referred as “shared external storage”, "application shared storage" or by the Linux path "/sdcard" it is mounted on.
• [C-0-2] MUST be configured with shared storage mounted by default, in other words “out of the box”, regardless of whether the storage is implemented on an internal storage component or a removable storage medium (eg Secure Digital card slot ).
• [C-0-3] MUST mount the application shared storage directly on the Linux path sdcard or include a Linux symbolic link from sdcard to the actual mount point.
• [C-0-4] MUST enforce the android.permission.WRITE_EXTERNAL_STORAGE permission on this shared storage as documented in the SDK.
• [C-0-5] MUST enable scoped storage by default for all apps targeting API level 29 or above, except in the following situations:
  • when the app was installed before the device upgraded to API level 29, regardless of the target API of the app.
  • when the app has requested android:requestLegacyExternalStorage="true" in their manifest.
  • when the app is granted the android.permission.WRITE_MEDIA_STORAGE permission.
• [C-0-6] MUST enforce that apps with scoped storage enabled have no direct filesystem access to files outside of their application-specific directories, as returned by Context API methods such as Context.getExternalFilesDirs() , Context.getExternalCacheDirs() , Context.getExternalMediaDirs() , and Context.getObbDirs() methods.
• [C-0-7] MUST redact location metadata, such as GPS Exif tags, stored in media files when those files are accessed through MediaStore , except when the calling app holds the ACCESS_MEDIA_LOCATION permission.

Device implementations MAY meet the above requirements using either of the following:

• User-accessible removable storage, such as a Secure Digital (SD) card slot.
• A portion of the internal (non-removable) storage as implemented in the Android Open Source Project (AOSP).

If device implementations use removable storage to satisfy the above requirements, they:

• [C-1-1] MUST implement a toast or pop-up user interface warning the user when there is no storage medium inserted in the slot.
• [C-1-2] MUST include a FAT-formatted storage medium (eg SD card) or show on the box and other material available at time of purchase that the storage medium has to be purchased separately.

If device implementations use a portion of the non-removable storage to satisfy the above requirements, they:

• SHOULD use the AOSP implementation of the internal application shared storage.
• MAY share the storage space with the application private data.

If device implementations include multiple shared storage paths (such as both an SD card slot and shared internal storage), they:

• [C-2-1] MUST allow only pre-installed and privileged Android applications with the WRITE_MEDIA_STORAGE permission to write to the secondary external storage, except when writing to their package-specific directories or within the URI returned by firing the ACTION_OPEN_DOCUMENT_TREE intent.
• [C-2-2] MUST require that the direct access associated with the android.permission.WRITE_MEDIA_STORAGE permission is only given to user-visible apps when the android.permission.WRITE_EXTERNAL_STORAGE permission is also granted.
• [SR] STRONGLY RECOMMENDED that pre-installed and privileged Android applications use public APIs such as MediaStore to interact with storage devices, instead of relying on the direct access granted by android.permission.WRITE_MEDIA_STORAGE .

Jika implementasi perangkat memiliki port USB dengan dukungan mode periferal USB, implementasi tersebut:

• [C-3-1] MUST provide a mechanism to access the data on the application shared storage from a host computer.
• SHOULD expose content from both storage paths transparently through Android's media scanner service and android.provider.MediaStore .
• MAY use USB mass storage, but SHOULD use Media Transfer Protocol to satisfy this requirement.

If device implementations have a USB port with USB peripheral mode and support Media Transfer Protocol, they:

• SHOULD be compatible with the reference Android MTP host, Android File Transfer .
• SHOULD report a USB device class of 0x00.
• SHOULD report a USB interface name of 'MTP'.

7.6.3. Penyimpanan yang Dapat Diadopsi

If the device is expected to be mobile in nature unlike Television, device implementations are:

• [SR] STRONGLY RECOMMENDED to implement the adoptable storage in a long-term stable location, since accidentally disconnecting them can cause data loss/corruption.

If the removable storage device port is in a long-term stable location, such as within the battery compartment or other protective cover, device implementations are:

• [SR] STRONGLY RECOMMENDED to implement adoptable storage .

7.7. USB

If device implementations have a USB port, they:

• SHOULD support USB peripheral mode and SHOULD support USB host mode.

7.7.1. USB peripheral mode

If device implementations include a USB port supporting peripheral mode:

• [C-1-1] The port MUST be connectable to a USB host that has a standard type-A or type-C USB port.
• [C-1-2] MUST report the correct value of iSerialNumber in USB standard device descriptor through android.os.Build.SERIAL .
• [C-1-3] MUST detect 1.5A and 3.0A chargers per the Type-C resistor standard and MUST detect changes in the advertisement if they support Type-C USB.
• [SR] The port SHOULD use micro-B, micro-AB or Type-C USB form factor. Existing and new Android devices are STRONGLY RECOMMENDED to meet these requirements so they will be able to upgrade to the future platform releases.
• [SR] The port SHOULD be located on the bottom of the device (according to natural orientation) or enable software screen rotation for all apps (including home screen), so that the display draws correctly when the device is oriented with the port at bottom . Existing and new Android devices are STRONGLY RECOMMENDED to meet these requirements so they will be able to upgrade to future platform releases.
• [SR] SHOULD implement support to draw 1.5 A current during HS chirp and traffic as specified in the USB Battery Charging specification, revision 1.2 . Existing and new Android devices are STRONGLY RECOMMENDED to meet these requirements so they will be able to upgrade to the future platform releases.
• [SR] STRONGLY RECOMMENDED to not support proprietary charging methods that modify Vbus voltage beyond default levels, or alter sink/source roles as such may result in interoperability issues with the chargers or devices that support the standard USB Power Delivery methods. While this is called out as "STRONGLY RECOMMENDED", in future Android versions we might REQUIRE all type-C devices to support full interoperability with standard type-C chargers.
• [SR] STRONGLY RECOMMENDED to support Power Delivery for data and power role swapping when they support Type-C USB and USB host mode.
• SHOULD support Power Delivery for high-voltage charging and support for Alternate Modes such as display out.
• SHOULD implement the Android Open Accessory (AOA) API and specification as documented in the Android SDK documentation.

If device implementations include a USB port and implement the AOA specification, they:

• [C-2-1] MUST declare support for the hardware feature android.hardware.usb.accessory .
• [C-2-2] The USB mass storage class MUST include the string "android" at the end of the interface description iInterface string of the USB mass storage
• SHOULD NOT implement AOAv2 audio documented in the Android Open Accessory Protocol 2.0 documentation. AOAv2 audio is deprecated as of Android version 8.0 (API level 26).

7.7.2. USB host mode

If device implementations include a USB port supporting host mode, they:

• [C-1-1] MUST implement the Android USB host API as documented in the Android SDK and MUST declare support for the hardware feature android.hardware.usb.host .
• [C-1-2] MUST implement support to connect standard USB peripherals, in other words, they MUST either:
  • Have an on-device type C port or ship with cable(s) adapting an on-device proprietary port to a standard USB type-C port (USB Type-C device).
  • Have an on-device type A or ship with cable(s) adapting an on-device proprietary port to a standard USB type-A port.
  • Have an on-device micro-AB port, which SHOULD ship with a cable adapting to a standard type-A port.
• [C-1-3] MUST NOT ship with an adapter converting from USB type A or micro-AB ports to a type-C port (receptacle).
• [C-SR] Are STRONGLY RECOMMENDED to implement the USB audio class as documented in the Android SDK documentation.
• SHOULD support charging the connected USB peripheral device while in host mode; advertising a source current of at least 1.5A as specified in the Termination Parameters section of the USB Type-C Cable and Connector Specification Revision 1.2 for USB Type-C connectors or using Charging Downstream Port(CDP) output current range as specified in the USB Battery Charging specifications, revision 1.2 for Micro-AB connectors.
• SHOULD implement and support USB Type-C standards.

If device implementations include a USB port supporting host mode and the USB audio class, they:

• [C-2-1] MUST support the USB HID class .
• [C-2-2] MUST support the detection and mapping of the following HID data fields specified in the USB HID Usage Tables and the Voice Command Usage Request to the KeyEvent constants as below:
  • Usage Page (0xC) Usage ID (0x0CD): KEYCODE_MEDIA_PLAY_PAUSE
  • Usage Page (0xC) Usage ID (0x0E9): KEYCODE_VOLUME_UP
  • Usage Page (0xC) Usage ID (0x0EA): KEYCODE_VOLUME_DOWN
  • Usage Page (0xC) Usage ID (0x0CF): KEYCODE_VOICE_ASSIST

If device implementations include a USB port supporting host mode and the Storage Access Framework (SAF), they:

• [C-3-1] MUST recognize any remotely connected MTP (Media Transfer Protocol) devices and make their contents accessible through the ACTION_GET_CONTENT , ACTION_OPEN_DOCUMENT , and ACTION_CREATE_DOCUMENT intents.

If device implementations include a USB port supporting host mode and USB Type-C, they:

• [C-4-1] MUST implement Dual Role Port functionality as defined by the USB Type-C specification (section 4.5.1.3.3).
• [SR] STRONGLY RECOMMENDED to support DisplayPort, SHOULD support USB SuperSpeed Data Rates, and are STRONGLY RECOMMENDED to support Power Delivery for data and power role swapping.
• [SR] STRONGLY RECOMMENDED to NOT support Audio Adapter Accessory Mode as described in the Appendix A of the USB Type-C Cable and Connector Specification Revision 1.2 .
• SHOULD implement the Try.* model that is most appropriate for the device form factor. For example a handheld device SHOULD implement the Try.SNK model.

7.8. Audio

7.8.1. Mikropon

If device implementations include a microphone, they:

• [C-1-1] MUST report the android.hardware.microphone feature constant.
• [C-1-2] MUST meet the audio recording requirements in section 5.4 .
• [C-1-3] MUST meet the audio latency requirements in section 5.6 .
• [SR] Are STRONGLY RECOMMENDED to support near-ultrasound recording as described in section 7.8.3 .

If device implementations omit a microphone, they:

• [C-2-1] MUST NOT report the android.hardware.microphone feature constant.
• [C-2-2] MUST implement the audio recording API at least as no-ops, per section 7 .

7.8.2. Keluaran Audio

If device implementations include a speaker or an audio/multimedia output port for an audio output peripheral such as a 4 conductor 3.5mm audio jack or USB host mode port using USB audio class , they:

• [C-1-1] MUST report the android.hardware.audio.output feature constant.
• [C-1-2] MUST meet the audio playback requirements in section 5.5 .
• [C-1-3] MUST meet the audio latency requirements in section 5.6 .
• [SR] STRONGLY RECOMMENDED to support near-ultrasound playback as described in section 7.8.3 .

If device implementations do not include a speaker or audio output port, they:

• [C-2-1] MUST NOT report the android.hardware.audio.output feature.
• [C-2-2] MUST implement the Audio Output related APIs as no-ops at least.

For the purposes of this section, an "output port" is a physical interface such as a 3.5mm audio jack, HDMI, or USB host mode port with USB audio class. Support for audio output over radio-based protocols such as Bluetooth, WiFi, or cellular network does not qualify as including an "output port".

7.8.2.1. Analog Audio Ports

In order to be compatible with the headsets and other audio accessories using the 3.5mm audio plug across the Android ecosystem, if device implementations include one or more analog audio ports, they:

• [C-SR] Are STRONGLY RECOMMENDED to include at least one of the audio port(s) to be a 4 conductor 3.5mm audio jack.

If device implementations have a 4 conductor 3.5mm audio jack, they:

• [C-1-1] MUST support audio playback to stereo headphones and stereo headsets with a microphone.
• [C-1-2] MUST support TRRS audio plugs with the CTIA pin-out order.
• [C-1-3] MUST support the detection and mapping to the keycodes for the following 3 ranges of equivalent impedance between the microphone and ground conductors on the audio plug:
  • 70 ohm or less : KEYCODE_HEADSETHOOK
  • 210-290 ohm : KEYCODE_VOLUME_UP
  • 360-680 ohm : KEYCODE_VOLUME_DOWN
• [C-1-4] MUST trigger ACTION_HEADSET_PLUG upon a plug insert, but only after all contacts on plug are touching their relevant segments on the jack.
• [C-1-5] MUST be capable of driving at least 150mV ± 10% of output voltage on a 32 ohm speaker impedance.
• [C-1-6] MUST have a microphone bias voltage between 1.8V ~ 2.9V.
• [C-1-7] MUST detect and map to the keycode for the following range of equivalent impedance between the microphone and ground conductors on the audio plug:
  • 110-180 ohm: KEYCODE_VOICE_ASSIST
• [C-SR] Are STRONGLY RECOMMENDED to support audio plugs with the OMTP pin-out order.
• [C-SR] Are STRONGLY RECOMMENDED to support audio recording from stereo headsets with a microphone.

If device implementations have a 4 conductor 3.5mm audio jack and support a microphone, and broadcast the android.intent.action.HEADSET_PLUG with the extra value microphone set as 1, they:

• [C-2-1] MUST support the detection of microphone on the plugged in audio accessory.

7.8.2.2. Digital Audio Ports

In order to be compatible with the headsets and other audio accessories using USB-C connectors and implementing (USB audio class) across the Android ecosystem as defined in Android USB headset specification .

See Section 2.2.1 for device-specific requirements.

7.8.3. Near-Ultrasound

Near-Ultrasound audio is the 18.5 kHz to 20 kHz band.

Implementasi perangkat:

• MUST correctly report the support of near-ultrasound audio capability via the AudioManager.getProperty API as follows:

If PROPERTY_SUPPORT_MIC_NEAR_ULTRASOUND is "true", the following requirements MUST be met by the VOICE_RECOGNITION and UNPROCESSED audio sources:

• [C-1-1] The microphone's mean power response in the 18.5 kHz to 20 kHz band MUST be no more than 15 dB below the response at 2 kHz.
• [C-1-2] The microphone's unweighted signal to noise ratio over 18.5 kHz to 20 kHz for a 19 kHz tone at -26 dBFS MUST be no lower than 50 dB.

If PROPERTY_SUPPORT_SPEAKER_NEAR_ULTRASOUND is "true":

• [C-2-1] The speaker's mean response in 18.5 kHz - 20 kHz MUST be no lower than 40 dB below the response at 2 kHz.

7.8.4. Integritas Sinyal

Implementasi perangkat:

• SHOULD provide a glitch-free audio signal path for both input and output streams on handheld devices, as defined by zero glitches measured during a test of one minute per path. Test using [OboeTester] (https://github.com/google/oboe/tree/master/apps/OboeTester) “Automated Glitch Test”.

The test requires an audio loopback dongle , used directly in a 3.5mm jack, and/or in combination with a USB-C to 3.5mm adapter. All audio output ports SHOULD be tested.

OboeTester currently supports AAudio paths, so the following combinations SHOULD be tested for glitches using AAudio:

A reliable stream SHOULD meet the following criteria for Signal to Noise Ratio (SNR) and Total Harmonic Distortion (THD) for 2000 Hz sine.

7.9. Realitas maya

Android includes APIs and facilities to build "Virtual Reality" (VR) applications including high quality mobile VR experiences. Device implementations MUST properly implement these APIs and behaviors, as detailed in this section.

7.9.1. Virtual Reality Mode

Android includes support for VR Mode , a feature which handles stereoscopic rendering of notifications and disables monocular system UI components while a VR application has user focus.

7.9.2. Virtual Reality Mode - High Performance

If device implementations support VR mode, they:

• [C-1-1] MUST have at least 2 physical cores.
• [C-1-2] MUST declare the android.hardware.vr.high_performance feature.
• [C-1-3] MUST support sustained performance mode.
• [C-1-4] MUST support OpenGL ES 3.2.
• [C-1-5] MUST support android.hardware.vulkan.level 0.
• SHOULD support android.hardware.vulkan.level 1 or higher.
• [C-1-6] MUST implement EGL_KHR_mutable_render_buffer , EGL_ANDROID_front_buffer_auto_refresh , EGL_ANDROID_get_native_client_buffer , EGL_KHR_fence_sync , EGL_KHR_wait_sync , EGL_IMG_context_priority , EGL_EXT_protected_content , EGL_EXT_image_gl_colorspace , and expose the extensions in the list of available EGL extensions.
• [C-1-8] MUST implement GL_EXT_multisampled_render_to_texture2 , GL_OVR_multiview , GL_OVR_multiview2 , GL_OVR_multiview_multisampled_render_to_texture , GL_EXT_protected_textures , and expose the extensions in the list of available GL extensions.
• [C-SR] Are STRONGLY RECOMMENDED to implement GL_EXT_external_buffer , GL_EXT_EGL_image_array , and expose the extensions in the list of available GL extensions.
• [C-SR] Are STRONGLY RECOMMENDED to support Vulkan 1.1.
• [C-SR] Are STRONGLY RECOMMENDED to implement VK_ANDROID_external_memory_android_hardware_buffer , VK_GOOGLE_display_timing , VK_KHR_shared_presentable_image , and expose it in the list of available Vulkan extensions.
• [C-SR] Are STRONGLY RECOMMENDED to expose at least one Vulkan queue family where flags contain both VK_QUEUE_GRAPHICS_BIT and VK_QUEUE_COMPUTE_BIT , and queueCount is at least 2.
• [C-1-7] The GPU and display MUST be able to synchronize access to the shared front buffer such that alternating-eye rendering of VR content at 60fps with two render contexts will be displayed with no visible tearing artifacts.
• [C-1-9] MUST implement support for AHardwareBuffer flags AHARDWAREBUFFER_USAGE_GPU_DATA_BUFFER , AHARDWAREBUFFER_USAGE_SENSOR_DIRECT_DATA and AHARDWAREBUFFER_USAGE_PROTECTED_CONTENT as described in the NDK.
• [C-1-10] MUST implement support for AHardwareBuffer s with any combination of the usage flags AHARDWAREBUFFER_USAGE_GPU_COLOR_OUTPUT , AHARDWAREBUFFER_USAGE_GPU_SAMPLED_IMAGE , AHARDWAREBUFFER_USAGE_PROTECTED_CONTENT for at least the following formats: AHARDWAREBUFFER_FORMAT_R5G6B5_UNORM , AHARDWAREBUFFER_FORMAT_R8G8B8A8_UNORM , AHARDWAREBUFFER_FORMAT_R10G10B10A2_UNORM , AHARDWAREBUFFER_FORMAT_R16G16B16A16_FLOAT .
• [C-SR] Are STRONGLY RECOMMENDED to support the allocation of AHardwareBuffer s with more than one layer and flags and formats specified in C-1-10.
• [C-1-11] MUST support H.264 decoding at least 3840 x 2160 at 30fps, compressed to an average of 40Mbps (equivalent to 4 instances of 1920 x1080 at 30 fps-10 Mbps or 2 instances of 1920 x 1080 at 60 fps-20 Mbps).
• [C-1-12] MUST support HEVC and VP9, MUST be capable of decoding at least 1920 x 1080 at 30 fps compressed to an average of 10 Mbps and SHOULD be capable of decoding 3840 x 2160 at 30 fps-20 Mbps (equivalent to 4 instances of 1920 x 1080 at 30 fps-5 Mbps).
• [C-1-13] MUST support HardwarePropertiesManager.getDeviceTemperatures API and return accurate values for skin temperature.
• [C-1-14] MUST have an embedded screen, and its resolution MUST be at least 1920 x 1080.
• [C-SR] Are STRONGLY RECOMMENDED to have a display resolution of at least 2560 x 1440.
• [C-1-15] The display MUST update at least 60 Hz while in VR Mode.
• [C-1-17] The display MUST support a low-persistence mode with ≤ 5 milliseconds persistence, persistence being defined as the amount of time for which a pixel is emitting light.
• [C-1-18] MUST support Bluetooth 4.2 and Bluetooth LE Data Length Extension section 7.4.3 .
• [C-1-19] MUST support and properly report Direct Channel Type for all of the following default sensor types:
  • TYPE_ACCELEROMETER
  • TYPE_ACCELEROMETER_UNCALIBRATED
  • TYPE_GYROSCOPE
  • TYPE_GYROSCOPE_UNCALIBRATED
  • TYPE_MAGNETIC_FIELD
  • TYPE_MAGNETIC_FIELD_UNCALIBRATED
• [C-SR] Are STRONGLY RECOMMENDED to support the TYPE_HARDWARE_BUFFER direct channel type for all Direct Channel Types listed above.
• [C-1-21] MUST meet the gyroscope, accelerometer, and magnetometer related requirements for android.hardware.hifi_sensors , as specified in section 7.3.9 .
• [C-SR] Are STRONGLY RECOMMENDED to support the android.hardware.sensor.hifi_sensors feature.
• [C-1-22] MUST have end-to-end motion to photon latency not higher than 28 milliseconds.
• [C-SR] Are STRONGLY RECOMMENDED to have end-to-end motion to photon latency not higher than 20 milliseconds.
• [C-1-23] MUST have first-frame ratio, which is the ratio between the brightness of pixels on the first frame after a transition from black to white and the brightness of white pixels in steady state, of at least 85%.
• [C-SR] Are STRONGLY RECOMMENDED to have first-frame ratio of at least 90%.
• MAY provide an exclusive core to the foreground application and MAY support the Process.getExclusiveCores API to return the numbers of the cpu cores that are exclusive to the top foreground application.

If exclusive core is supported, then the core:

• [C-2-1] MUST not allow any other userspace processes to run on it (except device drivers used by the application), but MAY allow some kernel processes to run as necessary.

8. Performance and Power

Some minimum performance and power criteria are critical to the user experience and impact the baseline assumptions developers would have when developing an app.

8.1. Konsistensi Pengalaman Pengguna

A smooth user interface can be provided to the end user if there are certain minimum requirements to ensure a consistent frame rate and response times for applications and games. Device implementations, depending on the device type, MAY have measurable requirements for the user interface latency and task switching as described in section 2 .

8.2. File I/O Access Performance

Providing a common baseline for a consistent file access performance on the application private data storage ( /data partition) allows app developers to set a proper expectation that would help their software design. Device implementations, depending on the device type, MAY have certain requirements described in section 2 for the following read and write operations:

• Sequential write performance . Measured by writing a 256MB file using 10MB write buffer.
• Random write performance . Measured by writing a 256MB file using 4KB write buffer.
• Sequential read performance . Measured by reading a 256MB file using 10MB write buffer.
• Random read performance . Measured by reading a 256MB file using 4KB write buffer.

8.3. Power-Saving Modes

If device implementations include features to improve device power management that are included in AOSP or extend the features that are included in AOSP, they:

• [C-1-1] MUST NOT deviate from the AOSP implementation for the triggering, maintenance, wakeup algorithms and the use of global system settings of App Standby and Doze power-saving modes.
• [C-1-2] MUST NOT deviate from the AOSP implementation for the use of global settings to manage the throttling of jobs, alarm and network for apps in each bucket for App standby.
• [C-1-3] MUST NOT deviate from the AOSP implementation for the number of the App Standby Buckets used for App Standby.
• [C-1-4] MUST implement App Standby Buckets and Doze as described in Power Management .
• [C-1-5] MUST return true for PowerManager.isPowerSaveMode() when the device is on power save mode.
• [C-SR] Are STRONGLY RECOMMENDED to provide user affordance to enable and disable the battery saver feature.
• [C-SR] Are STRONGLY RECOMMENDED to provide user affordance to display all Apps that are exempted from App Standby and Doze power-saving modes.

In addition to the power-saving modes, Android device implementations MAY implement any or all of the 4 sleeping power states as defined by the Advanced Configuration and Power Interface (ACPI).

If device implementations implement S4 power states as defined by the ACPI, they:

• [C-1-1] MUST enter this state only after the user has taken an explicit action to put the device in an inactive state (eg by closing a lid that is physically part of the device or turning off a vehicle or television) and before the user re-activates the device (eg by opening the lid or turning the vehicle or television back on).

If device implementations implement S3 power states as defined by the ACPI, they:

• [C-2-1] MUST meet C-1-1 above, or, MUST enter S3 state only when third-party applications do not need the system resources (eg the screen, CPU).

  Conversely, MUST exit from S3 state when third-party applications need the system resources, as described on this SDK.

  For example, while the third-party applications request to keep the screen on through FLAG_KEEP_SCREEN_ON or keep CPU running through PARTIAL_WAKE_LOCK , the device MUST NOT enter S3 state unless, as described in C-1-1, the user has taken explicit action to put the device in an inactive state. Conversely, at a time when a task that third-party apps implement through JobScheduler is triggered or Firebase Cloud Messaging is delivered to third-party apps, the device MUST exit the S3 state unless the user has put the device in an inactive state. These are not comprehensive examples and AOSP implements extensive wake-up signals that trigger a wakeup from this state.

8.4. Power Consumption Accounting

A more accurate accounting and reporting of the power consumption provides the app developer both the incentives and the tools to optimize the power usage pattern of the application.

Implementasi perangkat:

• [SR] STRONGLY RECOMMENDED to provide a per-component power profile that defines the current consumption value for each hardware component and the approximate battery drain caused by the components over time as documented in the Android Open Source Project site.
• [SR] STRONGLY RECOMMENDED to report all power consumption values in milliampere hours (mAh).
• [SR] STRONGLY RECOMMENDED to report CPU power consumption per each process's UID. Proyek Sumber Terbuka Android memenuhi persyaratan melalui implementasi modul kernel uid_cputime .
• [SR] STRONGLY RECOMMENDED to make this power usage available via the adb shell dumpsys batterystats shell command to the app developer.
• SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application.

8.5. Kinerja yang Konsisten

Performance can fluctuate dramatically for high-performance long-running apps, either because of the other apps running in the background or the CPU throttling due to temperature limits. Android includes programmatic interfaces so that when the device is capable, the top foreground application can request that the system optimize the allocation of the resources to address such fluctuations.

Implementasi perangkat:

• [C-0-1] MUST report the support of Sustained Performance Mode accurately through the PowerManager.isSustainedPerformanceModeSupported() API method.

• SHOULD support Sustained Performance Mode.

If device implementations report support of Sustained Performance Mode, they:

• [C-1-1] MUST provide the top foreground application a consistent level of performance for at least 30 minutes, when the app requests it.
• [C-1-2] MUST honor the Window.setSustainedPerformanceMode() API and other related APIs.

If device implementations include two or more CPU cores, they:

• SHOULD provide at least one exclusive core that can be reserved by the top foreground application.

If device implementations support reserving one exclusive core for the top foreground application, they:

• [C-2-1] MUST report through the Process.getExclusiveCores() API method the ID numbers of the exclusive cores that can be reserved by the top foreground application.
• [C-2-2] MUST not allow any user space processes except the device drivers used by the application to run on the exclusive cores, but MAY allow some kernel processes to run as necessary.

If device implementations do not support an exclusive core, they:

• [C-3-1] MUST return an empty list through the Process.getExclusiveCores() API method.

9. Security Model Compatibility

Implementasi perangkat:

• [C-0-1] MUST implement a security model consistent with the Android platform security model as defined in Security and Permissions reference document in the APIs in the Android developer documentation.

• [C-0-2] MUST support installation of self-signed applications without requiring any additional permissions/certificates from any third parties/authorities. Specifically, compatible devices MUST support the security mechanisms described in the following subsections.

9.1. Izin

Implementasi perangkat:

• [C-0-1] MUST support the Android permissions model as defined in the Android developer documentation. Specifically, they MUST enforce each permission defined as described in the SDK documentation; no permissions may be omitted, altered, or ignored.

• MAY add additional permissions, provided the new permission ID strings are not in the android.\* namespace.

• [C-0-2] Permissions with a protectionLevel of PROTECTION_FLAG_PRIVILEGED MUST only be granted to apps preinstalled in the privileged path(s) of the system image and within the subset of the explicitly allowlisted permissions for each app. The AOSP implementation meets this requirement by reading and honoring the allowlisted permissions for each app from the files in the etc/permissions/ path and using the system/priv-app path as the privileged path.

Permissions with a protection level of dangerous are runtime permissions. Applications with targetSdkVersion > 22 request them at runtime.

Implementasi perangkat:

• [C-0-3] MUST show a dedicated interface for the user to decide whether to grant the requested runtime permissions and also provide an interface for the user to manage runtime permissions.
• [C-0-4] MUST have one and only one implementation of both user interfaces.
• [C-0-5] MUST NOT grant any runtime permissions to preinstalled apps unless:
  • The user's consent can be obtained before the application uses it.
  • The runtime permissions are associated with an intent pattern for which the preinstalled application is set as the default handler.
• [C-0-6] MUST grant the android.permission.RECOVER_KEYSTORE permission only to system apps that register a properly secured Recovery Agent. A properly secured Recovery Agent is defined as an on-device software agent that synchronizes with an off-device remote storage, that is equipped with secure hardware with protection equivalent or stronger than what is described in Google Cloud Key Vault Service to prevent brute-force attacks on the lockscreen knowledge factor.

Implementasi perangkat:

• [C-0-7] MUST adhere to Android location permission properties when an app requests the location or physical activity data through standard Android API or proprietary mechanism. Such data includes but not limited to:

  • Device's location (eg latitude and longitude).
  • Information that can be used to determine or estimate the device's location (eg SSID, BSSID, Cell ID, Bluetooth scans, or location of the network that the device is connected to).
  • User's physical activity or classification of the physical activity.

More specifically, device implementations:

• [C-0-8] MUST obtain user consent to allow an app to access the location or physical activity data.
• [C-0-9] MUST grant a runtime permission ONLY to the app that holds sufficient permission as described on SDK. For example, TelephonyManager#getServiceState requires android.permission.ACCESS_FINE_LOCATION ).

Permissions can be marked as restricted altering their behavior.

• [C-0-10] Permissions marked with the flag hardRestricted MUST NOT be granted to an app unless:

  • An app APK file is in the system partition.
  • The user assigns a role that is associated with the hardRestricted permissions to an app.
  • The installer grants the hardRestricted to an app.
  • An app is granted the hardRestricted on an earlier Android version.

• [C-0-11] Apps holding a softRestricted permission MUST get only limited access and MUST NOT gain full access until added to an allowlist as described in the SDK, where full and limited access is defined for each softRestricted permission (for example, WRITE_EXTERNAL_STORAGE and READ_EXTERNAL_STORAGE ).

If device implementations include a pre-installed app or wish to allow third-party apps to access the usage statistics, they:

• [SR] are STRONGLY RECOMMENDED provide user-accessible mechanism to grant or revoke access to the usage stats in response to the android.settings.ACTION_USAGE_ACCESS_SETTINGS intent for apps that declare the android.permission.PACKAGE_USAGE_STATS permission.

If device implementations intend to disallow any apps, including pre-installed apps, from accessing the usage statistics, they:

• [C-1-1] MUST still have an activity that handles the android.settings.ACTION_USAGE_ACCESS_SETTINGS intent pattern but MUST implement it as a no-op, that is to have an equivalent behavior as when the user is declined for access.

9.2. UID and Process Isolation

Implementasi perangkat:

• [C-0-1] HARUS mendukung model sandbox aplikasi Android, di mana setiap aplikasi berjalan sebagai UID Unixstyle unik dan dalam proses terpisah.
• [C-0-2] MUST support running multiple applications as the same Linux user ID, provided that the applications are properly signed and constructed, as defined in the Security and Permissions reference .

9.3. Izin Sistem File

Implementasi perangkat:

• [C-0-1] MUST support the Android file access permissions model as defined in the Security and Permissions reference .

9.4. Alternate Execution Environments

Device implementations MUST keep consistency of the Android security and permission model, even if they include runtime environments that execute applications using some other software or technology than the Dalvik Executable Format or native code. Dengan kata lain:

• [C-0-1] Alternate runtimes MUST themselves be Android applications, and abide by the standard Android security model, as described elsewhere in section 9 .

• [C-0-2] Alternate runtimes MUST NOT be granted access to resources protected by permissions not requested in the runtime's AndroidManifest.xml file via the < uses-permission > mechanism.

• [C-0-3] Alternate runtimes MUST NOT permit applications to make use of features protected by Android permissions restricted to system applications.

• [C-0-4] Alternate runtimes MUST abide by the Android sandbox model and installed applications using an alternate runtime MUST NOT reuse the sandbox of any other app installed on the device, except through the standard Android mechanisms of shared user ID and signing certificate .

• [C-0-5] Alternate runtimes MUST NOT launch with, grant, or be granted access to the sandboxes corresponding to other Android applications.

• [C-0-6] Alternate runtimes MUST NOT be launched with, be granted, or grant to other applications any privileges of the superuser (root), or of any other user ID.

• [C-0-7] When the .apk files of alternate runtimes are included in the system image of device implementations, it MUST be signed with a key distinct from the key used to sign other applications included with the device implementations.

• [C-0-8] When installing applications, alternate runtimes MUST obtain user consent for the Android permissions used by the application.

• [C-0-9] When an application needs to make use of a device resource for which there is a corresponding Android permission (such as Camera, GPS, etc.), the alternate runtime MUST inform the user that the application will be able to access that resource.

• [C-0-10] When the runtime environment does not record application capabilities in this manner, the runtime environment MUST list all permissions held by the runtime itself when installing any application using that runtime.

• Alternate runtimes SHOULD install apps via the PackageManager into separate Android sandboxes (Linux user IDs, etc.).

• Alternate runtimes MAY provide a single Android sandbox shared by all applications using the alternate runtime.

9.5. Dukungan Multi-Pengguna

Android includes support for multiple users and provides support for full user isolation.

• Device implementations MAY but SHOULD NOT enable multi-user if they use removable media for primary external storage.

If device implementations include multiple users, they:

• [C-1-1] MUST meet the following requirements related to multi-user support .
• [C-1-2] MUST, for each user, implement a security model consistent with the Android platform security model as defined in Security and Permissions reference document in the APIs.
• [C-1-3] MUST have separate and isolated shared application storage (aka /sdcard ) directories for each user instance.
• [C-1-4] MUST ensure that applications owned by and running on behalf a given user cannot list, read, or write to the files owned by any other user, even if the data of both users are stored on the same volume or berkas sistem.
• [C-1-5] MUST encrypt the contents of the SD card when multiuser is enabled using a key stored only on non-removable media accessible only to the system if device implementations use removable media for the external storage APIs. As this will make the media unreadable by a host PC, device implementations will be required to switch to MTP or a similar system to provide host PCs with access to the current user's data.

9.6. Premium SMS Warning

Android includes support for warning users of any outgoing premium SMS message . Premium SMS messages are text messages sent to a service registered with a carrier that may incur a charge to the user.

Jika implementasi perangkat mendeklarasikan dukungan untuk android.hardware.telephony , mereka:

• [C-1-1] MUST warn users before sending a SMS message to numbers identified by regular expressions defined in /data/misc/sms/codes.xml file in the device. The upstream Android Open Source Project provides an implementation that satisfies this requirement.

9.7. Fitur keamanan

Device implementations MUST ensure compliance with security features in both the kernel and platform as described below.

The Android Sandbox includes features that use the Security-Enhanced Linux (SELinux) mandatory access control (MAC) system, seccomp sandboxing, and other security features in the Linux kernel. Implementasi perangkat:

• [C-0-1] MUST maintain compatibility with existing applications, even when SELinux or any other security features are implemented below the Android framework.
• [C-0-2] MUST NOT have a visible user interface when a security violation is detected and successfully blocked by the security feature implemented below the Android framework, but MAY have a visible user interface when an unblocked security violation occurs resulting in a successful mengeksploitasi.
• [C-0-3] MUST NOT make SELinux or any other security features implemented below the Android framework configurable to the user or app developer.
• [C-0-4] MUST NOT allow an application that can affect another application through an API (such as a Device Administration API) to configure a policy that breaks compatibility.
• [C-0-5] MUST split the media framework into multiple processes so that it is possible to more narrowly grant access for each process as described in the Android Open Source Project site.
• [C-0-6] MUST implement a kernel application sandboxing mechanism which allows filtering of system calls using a configurable policy from multithreaded programs. The upstream Android Open Source Project meets this requirement through enabling the seccomp-BPF with threadgroup synchronization (TSYNC) as described in the Kernel Configuration section of source.android.com .

Kernel integrity and self-protection features are integral to Android security. Implementasi perangkat:

• [C-0-7] MUST implement kernel stack buffer overflow protection mechanisms. Examples of such mechanisms are CC_STACKPROTECTOR_REGULAR and CONFIG_CC_STACKPROTECTOR_STRONG .
• [C-0-8] MUST implement strict kernel memory protections where executable code is read-only, read-only data is non-executable and non-writable, and writable data is non-executable (eg CONFIG_DEBUG_RODATA or CONFIG_STRICT_KERNEL_RWX ).
• [C-0-9] MUST implement static and dynamic object size bounds checking of copies between user-space and kernel-space (eg CONFIG_HARDENED_USERCOPY ) on devices originally shipping with API level 28 or higher.
• [C-0-10] MUST NOT execute user-space memory when executing in the kernel mode (eg hardware PXN, or emulated via CONFIG_CPU_SW_DOMAIN_PAN or CONFIG_ARM64_SW_TTBR0_PAN ) on devices originally shipping with API level 28 or higher.
• [C-0-11] MUST NOT read or write user-space memory in the kernel outside of normal usercopy access APIs (eg hardware PAN, or emulated via CONFIG_CPU_SW_DOMAIN_PAN or CONFIG_ARM64_SW_TTBR0_PAN ) on devices originally shipping with API level 28 or higher.
• [C-0-12] MUST implement kernel page table isolation if the hardware is vulnerable to CVE-2017-5754 on all devices originally shipping with API level 28 or higher (eg CONFIG_PAGE_TABLE_ISOLATION or CONFIG_UNMAP_KERNEL_AT_EL0 ).
• [C-0-13] MUST implement branch prediction hardening if the hardware is vulnerable to CVE-2017-5715 on all devices originally shipping with API level 28 or higher (eg CONFIG_HARDEN_BRANCH_PREDICTOR ).
• [SR] STRONGLY RECOMMENDED to keep kernel data which is written only during initialization marked read-only after initialization (eg __ro_after_init ).

• [C-SR] Are STRONGLY RECOMMENDED to randomize the layout of the kernel code and memory, and to avoid exposures that would compromise the randomization (eg CONFIG_RANDOMIZE_BASE with bootloader entropy via the /chosen/kaslr-seed Device Tree node or EFI_RNG_PROTOCOL ).

• [C-SR] Are STRONGLY RECOMMENDED to enable control flow integrity (CFI) in the kernel to provide additional protection against code-reuse attacks (eg CONFIG_CFI_CLANG and CONFIG_SHADOW_CALL_STACK ).

• [C-SR] Are STRONGLY RECOMMENDED not to disable Control-Flow Integrity (CFI), Shadow Call Stack (SCS) or Integer Overflow Sanitization (IntSan) on components that have it enabled.
• [C-SR] Are STRONGLY RECOMMENDED to enable CFI, SCS, and IntSan for any additional security-sensitive userspace components as explained in CFI and IntSan .

If device implementations use a Linux kernel, they:

• [C-1-1] MUST implement SELinux.
• [C-1-2] MUST set SELinux to global enforcing mode.
• [C-1-3] MUST configure all domains in enforcing mode. No permissive mode domains are allowed, including domains specific to a device/vendor.
• [C-1-4] MUST NOT modify, omit, or replace the neverallow rules present within the system/sepolicy folder provided in the upstream Android Open Source Project (AOSP) and the policy MUST compile with all neverallow rules present, for both AOSP SELinux domains as well as device/vendor specific domains.
• [C-1-5] MUST run third-party applications targeting API level 28 or higher in per-application SELinux sandboxes with per-app SELinux restrictions on each application's private data directory.
• SHOULD retain the default SELinux policy provided in the system/sepolicy folder of the upstream Android Open Source Project and only further add to this policy for their own device-specific configuration.

If device implementations are already launched on an earlier Android version and cannot meet the requirements [C-1-1] and [C-1-5] through a system software update, they MAY be exempted from these requirements.

If device implementations use kernel other than Linux, they:

• [C-2-1] MUST use a mandatory access control system that is equivalent to SELinux.

Android contains multiple defense-in-depth features that are integral to device security.

9.8. Pribadi

9.8.1. Riwayat Penggunaan

Android stores the history of the user's choices and manages such history by UsageStatsManager .

Implementasi perangkat:

• [C-0-1] MUST keep a reasonable retention period of such user history.
• [SR] Are STRONGLY RECOMMENDED to keep the 14 days retention period as configured by default in the AOSP implementation.

Android stores the system events using the StatsLog identifiers, and manages such history via the StatsManager and the IncidentManager System API.

Implementasi perangkat:

• [C-0-2] MUST only include the fields marked with DEST_AUTOMATIC in the incident report created by the System API class IncidentManager .
• [C-0-3] MUST not use the system event identifiers to log any other event than what is described in the StatsLog SDK documents. If additional system events are logged, they MAY use a different atom identifier in the range between 100,000 and 200,000.

9.8.2. Rekaman

Implementasi perangkat:

• [C-0-1] MUST NOT preload or distribute software components out-of-box that send the user's private information (eg keystrokes, text displayed on the screen, bugreport) off the device without the user's consent or clear ongoing notifications.

• [C-0-2] MUST display and obtain explicit user consent that includes substantially the same message as AOSP whenever screen casting or screen recording is enabled via MediaProjection or proprietary APIs. MUST NOT provide users an affordance to disable future display of the user consent.

• [C-0-3] MUST have an ongoing notification to the user while screen casting or screen recording is enabled. AOSP meets this requirement by showing an ongoing notification icon in the status bar.

If device implementations include functionality in the system that either captures the contents displayed on the screen and/or records the audio stream played on the device other than via the System API ContentCaptureService , or other proprietary means described in Section 9.8.6 Content Capture , they :

• [C-1-1] MUST have an ongoing notification to the user whenever this functionality is enabled and actively capturing/recording.

If device implementations include a component enabled out-of-box, capable of recording ambient audio and/or record the audio played on the device to infer useful information about user's context, they:

• [C-2-1] MUST NOT store in persistent on-device storage or transmit off the device the recorded raw audio or any format that can be converted back into the original audio or a near facsimile, except with explicit user consent.

9.8.3. Konektivitas

Jika implementasi perangkat memiliki port USB dengan dukungan mode periferal USB, implementasi tersebut:

• [C-1-1] MUST present a user interface asking for the user's consent before allowing access to the contents of the shared storage over the USB port.

9.8.4. Lalu Lintas Jaringan

Implementasi perangkat:

• [C-0-1] MUST preinstall the same root certificates for the system-trusted Certificate Authority (CA) store as provided in the upstream Android Open Source Project.
• [C-0-2] MUST ship with an empty user root CA store.
• [C-0-3] MUST display a warning to the user indicating the network traffic may be monitored, when a user root CA is added.

If device traffic is routed through a VPN, device implementations:

• [C-1-1] MUST display a warning to the user indicating either:
  • That network traffic may be monitored.
  • That network traffic is being routed through the specific VPN application providing the VPN.

If device implementations have a mechanism, enabled out-of-box by default, that routes network data traffic through a proxy server or VPN gateway (for example, preloading a VPN service with android.permission.CONTROL_VPN granted), they:

• [C-2-1] MUST ask for the user's consent before enabling that mechanism, unless that VPN is enabled by the Device Policy Controller via the DevicePolicyManager.setAlwaysOnVpnPackage() , in which case the user does not need to provide a separate consent, but MUST only be notified.

If device implementations implement a user affordance to toggle on the "always-on VPN" function of a 3rd-party VPN app, they:

• [C-3-1] MUST disable this user affordance for apps that do not support always-on VPN service in the AndroidManifest.xml file via setting the SERVICE_META_DATA_SUPPORTS_ALWAYS_ON attribute to false .

9.8.5. Device Identifiers

Implementasi perangkat:

• [C-0-1] MUST prevent access to the device serial number and, where applicable, IMEI/MEID, SIM serial number, and International Mobile Subscriber Identity (IMSI) from an app, unless it meets one of the following requirements:
  • is a signed carrier app that is verified by device manufacturers.
  • has been granted the READ_PRIVILEGED_PHONE_STATE permission.
  • has carrier privileges as defined in UICC Carrier Privileges .
  • is a device owner or profile owner that has been granted the READ_PHONE_STATE permission.
  • (For SIM serial number/ICCID only) has the local regulations requirement that the app detect changes in the subscriber's identity.

9.8.6. Content Capture

Android, through the System API ContentCaptureService , or by other proprietary means, supports a mechanism for device implementations to capture the following interactions between the applications and the user.

• Text and graphics rendered on-screen, including but not limited to, notifications and assist data via AssistStructure API.
• Media data, such as audio or video, recorded or played by the device.
• Input events (eg key, mouse, gesture, voice, video, and accessibility).
• Any other events that an application provides to the system via the Content Capture API or a similarly capable, proprietary API.

If device implementations capture the data above, they:

• [C-0-1] MUST encrypt all such data when stored in the device. This encryption MAY be carried out using Android File Based Encryption, or any of the ciphers listed as API version 26+ described in Cipher SDK .
• [C-0-2] MUST NOT back up either raw or encrypted data using Android backup methods or any other back up methods.
• [C-0-3] MUST only send all such data and the log of the device using a privacy-preserving mechanism. The privacy-preserving mechanism is defined as “those which allow only analysis in aggregate and prevent matching of logged events or derived outcomes to individual users”, to prevent any per-user data being introspectable (eg, implemented using a differential privacy technology such as RAPPOR ).
• [C-0-4] MUST NOT associate such data with any user identity (such as Account ) on the device, except with explicit user consent each time the data is associated.
• [C-0-5] MUST NOT share such data with other apps, except with explicit user consent every time it is shared.
• [C-0-6] MUST provide user affordance to erase such data that the ContentCaptureService or the proprietary means collects if the data is stored in any form on the device.

If device implementations include a service that implements the System API ContentCaptureService , or any proprietary service that captures the data as described as above, they:

• [C-1-1] MUST NOT allow users to replace the content capture service with a user-installable application or service and MUST only allow the preinstalled service to capture such data.
• [C-1-2] MUST NOT allow any apps other than the preinstalled content capture service mechanism to be able to capture such data.
• [C-1-3] MUST provide user affordance to disable the content capture service.
• [C-1-4] MUST NOT omit user affordance to manage Android permissions that are held by the content capture service and follow Android permissions model as described in Section 9.1. Izin .

• [C-SR] Are STRONGLY RECOMMENDED to keep the content capturing service components separate, for example, not binding the service or sharing process IDs, from other system components except for the following:

  • Telephony, Contacts, System UI, and Media

9.8.7. Clipboard Access

Implementasi perangkat:

• [C-0-1] MUST NOT return a clipped data on the clipboard (eg via the ClipboardManager API) unless the app is the default IME or is the app that currently has focus.

9.8.8. Lokasi

Implementasi perangkat:

• [C-0-1] MUST NOT turn on/off device location setting and Wi-Fi/Bluetooth scanning settings without explicit user consent or user initiation.
• [C-0-2] MUST provide the user affordance to access location related information including recent location requests, app level permissions and usage of Wi-Fi/Bluetooth scanning for determining location.
• [C-0-3] MUST ensure that the application using Emergency Location Bypass API [LocationRequest.setLocationSettingsIgnored()] is a user initiated emergency session (eg dial 911 or text to 911).
• [C-0-4] MUST preserve the Emergency Location Bypass API's ability to bypass device location settings without changing the settings.
• [C-0-5] MUST schedule a notification that reminds the user after an app in the background has accessed their location using the [ ACCESS_BACKGROUND_LOCATION ] permission.

9.9. Enkripsi Penyimpanan Data

All devices MUST meet the requirements of section 9.9.1. Devices which launched on an API level earlier than that of this document are exempted from the requirements of sections 9.9.2 and 9.9.3; instead they MUST meet the requirements in section 9.9 of the Android Compatibility Definition document corresponding to the API level on which the device launched.

9.9.1. Direct Boot

Implementasi perangkat:

• [C-0-1] MUST implement the Direct Boot mode APIs even if they do not support Storage Encryption.

• [C-0-2] The ACTION_LOCKED_BOOT_COMPLETED and ACTION_USER_UNLOCKED Intents MUST still be broadcast to signal Direct Boot aware applications that Device Encrypted (DE) and Credential Encrypted (CE) storage locations are available for user.

9.9.2. Encryption requirements

Implementasi perangkat:

• [C-0-1] MUST encrypt the application private data ( /data partition), as well as the application shared storage partition ( /sdcard partition) if it is a permanent, non-removable part of the device.
• [C-0-2] MUST enable the data storage encryption by default at the time the user has completed the out-of-box setup experience.
• [C-0-3] MUST meet the above data storage encryption requirement via implementing File Based Encryption (FBE).

9.9.3. Enkripsi Berbasis File

Encrypted devices:

• [C-1-1] MUST boot up without challenging the user for credentials and allow Direct Boot aware apps to access to the Device Encrypted (DE) storage after the ACTION_LOCKED_BOOT_COMPLETED message is broadcasted.
• [C-1-2] MUST only allow access to Credential Encrypted (CE) storage after the user has unlocked the device by supplying their credentials (eg. passcode, pin, pattern or fingerprint) and the ACTION_USER_UNLOCKED message is broadcasted.
• [C-1-3] MUST NOT offer any method to unlock the CE protected storage without either the user-supplied credentials or a registered escrow key.
• [C-1-4] MUST use Verified Boot and ensure that DE keys are cryptographically bound to the device's hardware root of trust.
• [C-1-5] MUST encrypt file contents using AES-256-XTS or Adiantum. AES-256-XTS refers to the Advanced Encryption Standard with a 256-bit cipher key length, operated in XTS mode; the full length of the key is 512 bits. Adiantum refers to Adiantum-XChaCha12-AES, as specified at https://github.com/google/adiantum.
• [C-1-6] MUST encrypt file names using AES-256-CBC-CTS or Adiantum.

• [C-1-12] MUST use AES-256-XTS for file contents and AES-256-CBC-CTS for file names (instead of Adiantum) if the device has Advanced Encryption Standard (AES) instructions. AES instructions are ARMv8 Cryptography Extensions on ARM-based devices, or AES-NI on x86-based devices. If the device does not have AES instructions, the device MAY use Adiantum.

• The keys protecting CE and DE storage areas:

• [C-1-7] MUST be cryptographically bound to a hardware-backed Keystore.

• [C-1-8] CE keys MUST be bound to a user's lock screen credentials.
• [C-1-9] CE keys MUST be bound to a default passcode when the user has not specified lock screen credentials.
• [C-1-10] MUST be unique and distinct, in other words no user's CE or DE key matches any other user's CE or DE keys.
• [C-1-11] MUST use the mandatorily supported ciphers, key lengths and modes.

• [C-SR] Are STRONGLY RECOMMENDED to encrypt file system metadata, such as file sizes, ownership, modes, and Extended attributes (xattrs), with a key cryptographically bound to the device's hardware root of trust.

• SHOULD make preinstalled essential apps (eg Alarm, Phone, Messenger) Direct Boot aware.

The upstream Android Open Source project provides a preferred implementation of this feature based on the Linux kernel "fscrypt" encryption feature.

9.10. Integritas Perangkat

The following requirements ensure there is transparency to the status of the device integrity. Implementasi perangkat:

• [C-0-1] MUST correctly report through the System API method PersistentDataBlockManager.getFlashLockState() whether their bootloader state permits flashing of the system image. The FLASH_LOCK_UNKNOWN state is reserved for device implementations upgrading from an earlier version of Android where this new system API method did not exist.

• [C-0-2] MUST support Verified Boot for device integrity.

If device implementations are already launched without supporting Verified Boot on an earlier version of Android and can not add support for this feature with a system software update, they MAY be exempted from the requirement.

Verified Boot adalah fitur yang menjamin integritas perangkat lunak perangkat. Jika implementasi perangkat mendukung fitur, mereka:

• [C-1-1] MUST declare the platform feature flag android.software.verified_boot .
• [C-1-2] MUST perform verification on every boot sequence.
• [C-1-3] MUST start verification from an immutable hardware key that is the root of trust and go all the way up to the system partition.
• [C-1-4] MUST implement each stage of verification to check the integrity and authenticity of all the bytes in the next stage before executing the code in the next stage.
• [C-1-5] MUST use verification algorithms as strong as current recommendations from NIST for hashing algorithms (SHA-256) and public key sizes (RSA-2048).
• [C-1-6] MUST NOT allow boot to complete when system verification fails, unless the user consents to attempt booting anyway, in which case the data from any non-verified storage blocks MUST not be used.
• [C-1-7] MUST NOT allow verified partitions on the device to be modified unless the user has explicitly unlocked the bootloader.
• [C-SR] If there are multiple discrete chips in the device (eg radio, specialized image processor), the boot process of each of those chips is STRONGLY RECOMMENDED to verify every stage upon booting.
• [C-1-8] MUST use tamper-evident storage: for storing whether the bootloader is unlocked. Tamper-evident storage means that the bootloader can detect if the storage has been tampered with from inside Android.
• [C-1-9] MUST prompt the user, while using the device, and require physical confirmation before allowing a transition from bootloader locked mode to bootloader unlocked mode.
• [C-1-10] MUST implement rollback protection for partitions used by Android (eg boot, system partitions) and use tamper-evident storage for storing the metadata used for determining the minimum allowable OS version.
• [C-SR] Are STRONGLY RECOMMENDED to verify all privileged app APK files with a chain of trust rooted in partitions protected by Verified Boot.
• [C-SR] Are STRONGLY RECOMMENDED to verify any executable artifacts loaded by a privileged app from outside its APK file (such as dynamically loaded code or compiled code) before executing them or STRONGLY RECOMMENDED not to execute them at all.
• SHOULD implement rollback protection for any component with persistent firmware (eg modem, camera) and SHOULD use tamper-evident storage for storing the metadata used for determining the minimum allowable version.

If device implementations are already launched without supporting C-1-8 through C-1-10 on an earlier version of Android and can not add support for these requirements with a system software update, they MAY be exempted from the requirements.

The upstream Android Open Source Project provides a preferred implementation of this feature in the external/avb/ repository, which can be integrated into the bootloader used for loading Android.

Implementasi perangkat:

• [CR] Are RECOMMENDED to support the Android Protected Confirmation API .

If device implementations support the Android Protected Confirmation API they:

• [C-3-1] MUST report true for the ConfirmationPrompt.isSupported() API.

• [C-3-2] MUST ensure that code running in the Android OS including its kernel, malicious or otherwise, cannot generate a positive response without user interaction.

• [C-3-3] MUST ensure that the user has been able to review and approve the prompted message even in the event that the Android OS, including its kernel, is compromised.

9.11. Keys and Credentials

The Android Keystore System allows app developers to store cryptographic keys in a container and use them in cryptographic operations through the KeyChain API or the Keystore API . Implementasi perangkat:

• [C-0-1] MUST allow at least 8,192 keys to be imported or generated.
• [C-0-2] The lock screen authentication MUST rate-limit attempts and MUST have an exponential backoff algorithm. Beyond 150 failed attempts, the delay MUST be at least 24 hours per attempt.
• SHOULD not limit the number of keys that can be generated

When the device implementation supports a secure lock screen, it:

• [C-1-1] MUST back up the keystore implementation with an isolated execution environment.
• [C-1-2] MUST have implementations of RSA, AES, ECDSA and HMAC cryptographic algorithms and MD5, SHA1, and SHA-2 family hash functions to properly support the Android Keystore system's supported algorithms in an area that is securely isolated from the code running on the kernel and above. Isolasi yang aman harus memblokir semua mekanisme potensial yang dengannya kernel atau kode ruang pengguna dapat mengakses keadaan internal lingkungan yang terisolasi, termasuk DMA. Proyek Open Source Android Hulu (AOSP) memenuhi persyaratan ini dengan menggunakan implementasi yang dapat dipercaya , tetapi solusi berbasis ARM Trustzone lainnya atau implementasi aman pihak ketiga yang ditinjau dari isolasi berbasis hypervisor yang tepat adalah opsi alternatif.
• [C-1-3] MUST perform the lock screen authentication in the isolated execution environment and only when successful, allow the authentication-bound keys to be used. Kredensial layar kunci harus disimpan dengan cara yang hanya memungkinkan lingkungan eksekusi yang terisolasi untuk melakukan otentikasi layar kunci. Proyek Open Source Android hulu menyediakan lapisan abstraksi perangkat keras Gatekeeper (HAL) dan terpercaya, yang dapat digunakan untuk memenuhi persyaratan ini.
• [C-1-4] MUST support key attestation where the attestation signing key is protected by secure hardware and signing is performed in secure hardware. Kunci penandatanganan pengesahan harus dibagikan di jumlah perangkat yang cukup besar untuk mencegah kunci digunakan sebagai pengidentifikasi perangkat. Salah satu cara untuk memenuhi persyaratan ini adalah dengan berbagi kunci pengesahan yang sama kecuali setidaknya 100.000 unit SKU yang diberikan diproduksi. Jika lebih dari 100.000 unit SKU diproduksi, kunci yang berbeda dapat digunakan untuk setiap 100.000 unit.

Perhatikan bahwa jika implementasi perangkat sudah diluncurkan pada versi Android sebelumnya, perangkat seperti itu dibebaskan dari persyaratan untuk memiliki keystore yang didukung oleh lingkungan eksekusi yang terisolasi dan mendukung pengesahan utama, kecuali jika ia menyatakan fitur android.hardware.fingerprint mana membutuhkan keystore yang didukung oleh lingkungan eksekusi yang terisolasi.

• [C-1-5] MUST allow the user to choose the Sleep timeout for transition from the unlocked to the locked state, with a minimum allowable timeout up to 15 seconds.

9.11.1. Secure Lock Screen and Authentication

The AOSP implementation follows a tiered authentication model where a knowledge-factory based primary authentication can be backed by either a secondary strong biometric, or by weaker tertiary modalities.

Implementasi perangkat:

• [C-SR] Are STRONGLY RECOMMENDED to set only one of the following as the primary authentication method:
  • A numeric PIN
  • An alphanumeric password
  • A swipe pattern on a grid of exactly 3x3 dots

Note that the above authentication methods are referred as the recommended primary authentication methods in this document.

If device implementations add or modify the recommended primary authentication methods and use a new authentication method as a secure way to lock the screen, the new authentication method:

• [C-2-1] MUST be the user authentication method as described in Requiring User Authentication For Key Use .
• [C-2-2] MUST unlock all keys for a third-party developer app to use when the user unlocks the secure lock screen. For example, all keys MUST be available for a third-party developer app through relevant APIs, such as createConfirmDeviceCredentialIntent and setUserAuthenticationRequired .

If device implementations add or modify the authentication methods to unlock the lock screen if based on a known secret and use a new authentication method to be treated as a secure way to lock the screen:

• [C-3-1] The entropy of the shortest allowed length of inputs MUST be greater than 10 bits.
• [C-3-2] The maximum entropy of all possible inputs MUST be greater than 18 bits.
• [C-3-3] The new authentication method MUST NOT replace any of the recommended primary authentication methods (ie PIN, pattern, password) implemented and provided in AOSP.
• [C-3-4] The new authentication method MUST be disabled when the Device Policy Controller (DPC) application has set the password quality policy via the DevicePolicyManager.setPasswordQuality() method with a more restrictive quality constant than PASSWORD_QUALITY_SOMETHING .
• [C-3-5] New authentication methods MUST either fall back to the recommended primary authentication methods (ie PIN, pattern, password) once every 72 hours or less OR clearly disclose to the user that some data will not be backed up in order to preserve the privacy of their data.

If device implementations add or modify the recommended primary authentication methods to unlock the lock screen and use a new authentication method that is based on biometrics to be treated as a secure way to lock the screen, the new method:

• [C-4-1] MUST meet all requirements described in section 7.3.10 for Convenience .
• [C-4-2] MUST have a fall-back mechanism to use one of the recommended primary authentication methods which is based on a known secret.
• [C-4-3] MUST be disabled and only allow the recommended primary authentication to unlock the screen when the Device Policy Controller (DPC) application has set the keyguard feature policy by calling the method DevicePolicyManager.setKeyguardDisabledFeatures() , with any of the associated biometric flags (ie KEYGUARD_DISABLE_BIOMETRICS , KEYGUARD_DISABLE_FINGERPRINT , KEYGUARD_DISABLE_FACE , or KEYGUARD_DISABLE_IRIS ).

If the biometric authentication methods do not meet the requirements for Strong as described in section 7.3.10 :

• [C-5-1] The methods MUST be disabled if the Device Policy Controller (DPC) application has set the password quality policy via the DevicePolicyManager.setPasswordQuality() method with a more restrictive quality constant than PASSWORD_QUALITY_BIOMETRIC_WEAK .
• [C-5-2] The user MUST be challenged for the recommended primary authentication (eg: PIN, pattern, password) after any 4-hour idle timeout period. The idle timeout period is reset after any successful confirmation of the device credentials.
• [C-5-3] The methods MUST NOT be treated as a secure lock screen, and MUST meet the requirements that start with C-8 in this section below.

If device implementations add or modify the authentication methods to unlock the lock screen and a new authentication method is based on a physical token or the location:

• [C-6-1] They MUST have a fall-back mechanism to use one of the recommended primary authentication methods which is based on a known secret and meet the requirements to be treated as a secure lock screen.
• [C-6-2] The new method MUST be disabled and only allow one of the recommended primary authentication methods to unlock the screen when the Device Policy Controller (DPC) application has set the policy with either the DevicePolicyManager.setKeyguardDisabledFeatures(KEYGUARD_DISABLE_TRUST_AGENTS) method or the DevicePolicyManager.setPasswordQuality() method with a more restrictive quality constant than PASSWORD_QUALITY_UNSPECIFIED .
• [C-6-3] The user MUST be challenged for one of the recommended primary authentication methods (egPIN, pattern, password) at least once every 4 hours or less.
• [C-6-4] The new method MUST NOT be treated as a secure lock screen and MUST follow the constraints listed in C-8 below.

Jika implementasi perangkat memiliki layar kunci yang aman dan menyertakan satu atau lebih agen kepercayaan, yang mengimplementasikan API sistem TrustAgentService , mereka:

• [C-7-1] MUST have clear indication in the settings menu and on the lock screen when device lock is deferred or can be kept unlocked by trust agent(s). For example, AOSP meets this requirement by showing a text description for the "Automatically lock setting" and "Power button instantly locks" in the settings menu and a distinguishable icon on the lock screen.
• [C-7-2] MUST respect and fully implement all trust agent APIs in the DevicePolicyManager class, such as the KEYGUARD_DISABLE_TRUST_AGENTS constant.
• [C-7-3] MUST NOT fully implement the TrustAgentService.addEscrowToken() function on a device that is used as a primary personal device (eg handheld) but MAY fully implement the function on device implementations that are typically shared (eg Android Television or Automotive device).
• [C-7-4] MUST encrypt all stored tokens added by TrustAgentService.addEscrowToken() .
• [C-7-5] MUST NOT store the encryption key or escrow token on the same device where the key is used. For example, it is allowed for a key stored on a phone to unlock a user account on a TV.
• [C-7-6] MUST inform the user about the security implications before enabling the escrow token to decrypt the data storage.
• [C-7-7] MUST have a fall-back mechanism to use one of the recommended primary authentication methods.
• [C-7-8] The user MUST be challenged for one of the recommended primary authentication (eg: PIN, pattern, password) methods at least once every 72 hours or less unless the safety of the user (eg driver distraction) is of kekhawatiran.
• [C-7-9] The user MUST be challenged for one of the recommended primary authentication (eg: PIN, pattern, password) methods after any 4-hour idle timeout period unless the safety of the user (eg driver distraction) is of concern.. The idle timeout period is reset after any successful confirmation of the device credentials.
• [C-7-10] MUST NOT be treated as a secure lock screen and MUST follow the constraints listed in C-8 below.
• [C-7-11] MUST NOT allow TrustAgents on primary personal devices (eg: handheld) to unlock the device, and can only use them to keep an already unlocked device in the unlocked state for up to a maximum of 4 hours. The default implementation of TrustManagerService in AOSP meets this requirement.
• [C-7-12] MUST use a cryptographically secure (eg UKEY2) communication channel to pass the escrow token from the storage device to the target device.

If device implementations add or modify the authentication methods to unlock the lock screen that is not a secure lock screen as described above, and use a new authentication method to unlock the keyguard:

• [C-8-1] The new method MUST be disabled when the Device Policy Controller (DPC) application has set the password quality policy via the DevicePolicyManager.setPasswordQuality() method with a more restrictive quality constant than PASSWORD_QUALITY_UNSPECIFIED .
• [C-8-2] They MUST NOT reset the password expiration timers set by DevicePolicyManager.setPasswordExpirationTimeout() .
• [C-8-3] They MUST NOT expose an API for use by third-party apps to determine the lock state.

9.11.2. Peti besi

The Android Keystore System allows app developers to store cryptographic keys in a dedicated secure processor as well as the isolated execution environment described above. Such a dedicated secure processor is called "StrongBox". Requirements C-1-3 through C-1-11 below define the requirements a device MUST meet to qualify as a StrongBox.

Device implementations that have a dedicated secure processor:

• [C-SR] Are STRONGLY RECOMMENDED to support StrongBox. StrongBox will likely become a requirement in a future release.

If device implementations support StrongBox, they:

• [C-1-1] MUST declare FEATURE_STRONGBOX_KEYSTORE .

• [C-1-2] MUST provide dedicated secure hardware that is used to back keystore and secure user authentication. The dedicated secure hardware may be used for other purposes as well.

• [C-1-3] MUST have a discrete CPU that shares no cache, DRAM, coprocessors or other core resources with the application processor (AP).

• [C-1-4] MUST ensure that any peripherals shared with the AP cannot alter StrongBox processing in any way, or obtain any information from the StrongBox. The AP MAY disable or block access to StrongBox.

• [C-1-5] MUST have an internal clock with reasonable accuracy (+-10%) that is immune to manipulation by the AP.

• [C-1-6] MUST have a true random number generator that produces uniformly-distributed and unpredictable output.

• [C-1-7] MUST have tamper resistance, including resistance against physical penetration, and glitching.

• [C-1-8] MUST have side-channel resistance, including resistance against leaking information via power, timing, electromagnetic radiation, and thermal radiation side channels.

• [C-1-9] MUST have secure storage which ensures confidentiality, integrity, authenticity, consistency, and freshness of the contents. The storage MUST NOT be able to be read or altered, except as permitted by the StrongBox APIs.

• To validate compliance with [C-1-3] through [C-1-9], device implementations:

  • [C-1-10] MUST include the hardware that is certified against the Secure IC Protection Profile BSI-CC-PP-0084-2014 or evaluated by a nationally accredited testing laboratory incorporating High attack potential vulnerability assessment according to the Common Criteria Application of Attack Potential to Smartcards .
  • [C-1-11] MUST include the firmware that is evaluated by a nationally accredited testing laboratory incorporating High attack potential vulnerability assessment according to the Common Criteria Application of Attack Potential to Smartcards .
  • [C-SR] Are STRONGLY RECOMMENDED to include the hardware that is evaluated using a Security Target, Evaluation Assurance Level (EAL) 5, augmented by AVA_VAN.5. EAL 5 certification will likely become a requirement in a future release.

• [C-SR] are STRONGLY RECOMMENDED to provide insider attack resistance (IAR), which means that an insider with access to firmware signing keys cannot produce firmware that causes the StrongBox to leak secrets, to bypass functional security requirements or otherwise enable access to sensitive data pengguna. The recommended way to implement IAR is to allow firmware updates only when the primary user password is provided via the IAuthSecret HAL.

9.12. Penghapusan Data

All device implementations:

• [C-0-1] MUST provide users a mechanism to perform a "Factory Data Reset".
• [C-0-2] MUST delete all data on the userdata filesystem.
• [C-0-3] MUST delete the data in such a way that will satisfy relevant industry standards such as NIST SP800-88.
• [C-0-4] MUST trigger the above "Factory Data Reset" process when the DevicePolicyManager.wipeData() API is called by the primary user's Device Policy Controller app.
• MAY provide a fast data wipe option that conducts only a logical data erase.

9.13. Safe Boot Mode

Android provides Safe Boot Mode, which allows users to boot up into a mode where only preinstalled system apps are allowed to run and all third-party apps are disabled. This mode, known as "Safe Boot Mode", provides the user the capability to uninstall potentially harmful third-party apps.

Device implementations are:

• [SR] STRONGLY RECOMMENDED to implement Safe Boot Mode.

If device implementations implement Safe Boot Mode, they:

• [C-1-1] MUST provide the user an option to enter Safe Boot Mode in such a way that is uninterruptible from third-party apps installed on the device, except when the third-party app is a Device Policy Controller and has set the UserManager.DISALLOW_SAFE_BOOT flag as true.

• [C-1-2] MUST provide the user the capability to uninstall any third-party apps within Safe Mode.

• SHOULD provide the user an option to enter Safe Boot Mode from the boot menu using a workflow that is different from that of a normal boot.

9.14. Automotive Vehicle System Isolation

Android Automotive devices are expected to exchange data with critical vehicle subsystems by using the vehicle HAL to send and receive messages over vehicle networks such as CAN bus.

The data exchange can be secured by implementing security features below the Android framework layers to prevent malicious or unintentional interaction with these subsystems.

9.15. Paket Berlangganan

"Subscription plans" refer to the billing relationship plan details provided by a mobile carrier through SubscriptionManager.setSubscriptionPlans() .

All device implementations:

• [C-0-1] MUST return subscription plans only to the mobile carrier app that has originally provided them.
• [C-0-2] MUST NOT remotely back up or upload subscription plans.
• [C-0-3] MUST only allow overrides, such as SubscriptionManager.setSubscriptionOverrideCongested() , from the mobile carrier app currently providing valid subscription plans.

10. Software Compatibility Testing

Device implementations MUST pass all tests described in this section. However, note that no software test package is fully comprehensive. For this reason, device implementers are STRONGLY RECOMMENDED to make the minimum number of changes as possible to the reference and preferred implementation of Android available from the Android Open Source Project. This will minimize the risk of introducing bugs that create incompatibilities requiring rework and potential device updates.

10.1. Compatibility Test Suite

Implementasi perangkat:

• [C-0-1] MUST pass the Android Compatibility Test Suite (CTS) available from the Android Open Source Project, using the final shipping software on the device.

• [C-0-2] MUST ensure compatibility in cases of ambiguity in CTS and for any reimplementations of parts of the reference source code.

The CTS is designed to be run on an actual device. Like any software, the CTS may itself contain bugs. The CTS will be versioned independently of this Compatibility Definition, and multiple revisions of the CTS may be released for Android 10.

Implementasi perangkat:

• [C-0-3] MUST pass the latest CTS version available at the time the device software is completed.

• SHOULD use the reference implementation in the Android Open Source tree as much as possible.

10.2. CTS Verifier

The CTS Verifier is included with the Compatibility Test Suite, and is intended to be run by a human operator to test functionality that cannot be tested by an automated system, such as correct functioning of a camera and sensors.

Implementasi perangkat:

• [C-0-1] MUST correctly execute all applicable cases in the CTS verifier.

The CTS Verifier has tests for many kinds of hardware, including some hardware that is optional.

Implementasi perangkat:

• [C-0-2] MUST pass all tests for hardware that they possess; for instance, if a device possesses an accelerometer, it MUST correctly execute the Accelerometer test case in the CTS Verifier.

Test cases for features noted as optional by this Compatibility Definition Document MAY be skipped or omitted.

• [C-0-2] Every device and every build MUST correctly run the CTS Verifier, as noted above. However, since many builds are very similar, device implementers are not expected to explicitly run the CTS Verifier on builds that differ only in trivial ways. Specifically, device implementations that differ from an implementation that has passed the CTS Verifier only by the set of included locales, branding, etc. MAY omit the CTS Verifier test.

11. Updatable Software

• [C-0-1] Device implementations MUST include a mechanism to replace the entirety of the system software. The mechanism need not perform “live” upgrades—that is, a device restart MAY be required. Any method can be used, provided that it can replace the entirety of the software preinstalled on the device. For instance, any of the following approaches will satisfy this requirement:

  • “Over-the-air (OTA)” downloads with offline update via reboot.
  • “Tethered” updates over USB from a host PC.
  • “Offline” updates via a reboot and update from a file on removable storage.

• [C-0-2] The update mechanism used MUST support updates without wiping user data. That is, the update mechanism MUST preserve application private data and application shared data. Note that the upstream Android software includes an update mechanism that satisfies this requirement.

• [C-0-3] The entire update MUST be signed and the on-device update mechanism MUST verify the update and signature against a public key stored on device.

• [C-SR] The signing mechanism is STRONGLY RECOMMENDED to hash the update with SHA-256 and validate the hash against the public key using ECDSA NIST P-256.

If the device implementations includes support for an unmetered data connection such as 802.11 or Bluetooth PAN (Personal Area Network) profile, then, they:

• [C-1-1] MUST support OTA downloads with offline update via reboot.

For device implementations that are launching with Android 6.0 and later, the update mechanism SHOULD support verifying that the system image is binary identical to expected result following an OTA. The block-based OTA implementation in the upstream Android Open Source Project, added since Android 5.1, satisfies this requirement.

Also, device implementations SHOULD support A/B system updates . The AOSP implements this feature using the boot control HAL.

If an error is found in a device implementation after it has been released but within its reasonable product lifetime that is determined in consultation with the Android Compatibility Team to affect the compatibility of third-party applications, then:

• [C-2-1] The device implementer MUST correct the error via a software update available that can be applied per the mechanism just described.

Android includes features that allow the Device Owner app (if present) to control the installation of system updates. If the system update subsystem for devices report android.software.device_admin then, they:

• [C-3-1] MUST implement the behavior described in the SystemUpdatePolicy class.

12. Document Changelog

For a summary of changes to the Compatibility Definition in this release:

• Document changelog

For a summary of changes to individuals sections:

1. Perkenalan
2. Jenis Perangkat
3. Perangkat lunak
4. Kemasan Aplikasi
5. Multimedia
6. Developer Tools and Options
7. Kompatibilitas Perangkat Keras
8. Kinerja dan Kekuatan
9. Model Keamanan
10. Software Compatibility Testing
11. Updatable Software
12. Log Perubahan Dokumen
13. Hubungi kami

12.1. Changelog Viewing Tips

Changes are marked as follows:

• CDD
  Substantive changes to the compatibility requirements.

• dokumen
  Cosmetic or build related changes.

For best viewing, append the pretty=full and no-merges URL parameters to your changelog URLs.

13. Hubungi Kami

You can join the android-compatibility forum and ask for clarifications or bring up any issues that you think the document does not cover.