Definisi Kompatibilitas Android (Pratinjau)

1. Perkenalan

Dokumen ini menyebutkan persyaratan yang harus dipenuhi agar perangkat kompatibel dengan Android 13.

Penggunaan “HARUS”, “HARUS TIDAK”, “DIPERLUKAN”, “HARUS”, “HARUS TIDAK”, “HARUS”, “TIDAK HARUS”, “DIREKOMENDASIKAN”, “MUNGKIN”, dan “OPSIONAL” sesuai dengan IETF standar yang ditentukan dalam RFC2119 .

Seperti yang digunakan dalam dokumen ini, "pelaksana perangkat" atau "pelaksana" adalah orang atau organisasi yang mengembangkan solusi perangkat keras/perangkat lunak yang menjalankan Android 13. "Implementasi perangkat" atau "implementasi" adalah solusi perangkat keras/lunak yang dikembangkan demikian.

Agar dianggap kompatibel dengan Android 13, implementasi 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, merupakan tanggung jawab pelaksana perangkat untuk memastikan kompatibilitas dengan implementasi yang ada.

Untuk alasan ini, Proyek Sumber Terbuka Android adalah referensi dan implementasi yang disukai dari Android. Pelaksana perangkat SANGAT DIREKOMENDASIKAN untuk mendasarkan implementasi mereka semaksimal mungkin pada kode sumber “hulu” yang tersedia dari Proyek Sumber Terbuka Android. Sementara beberapa komponen secara hipotetis dapat diganti dengan implementasi alternatif, SANGAT DIREKOMENDASIKAN untuk tidak mengikuti praktik ini, karena lulus tes perangkat lunak akan menjadi jauh lebih sulit. Ini adalah tanggung jawab pelaksana untuk memastikan kompatibilitas perilaku penuh 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 ditautkan ke dalam dokumen ini berasal langsung atau tidak langsung dari Android SDK dan secara fungsional akan identik dengan informasi dalam dokumentasi SDK tersebut. Dalam kasus apa pun di mana Definisi Kompatibilitas atau Suite Uji Kompatibilitas ini tidak setuju dengan dokumentasi SDK, dokumentasi SDK dianggap otoritatif. Detail teknis apa pun yang disediakan dalam sumber tertaut di seluruh dokumen ini dianggap dengan penyertaan sebagai bagian dari Definisi Kompatibilitas ini.

1.1 Struktur Dokumen

1.1.1. Persyaratan menurut 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 untuk 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 diberikan hanya untuk persyaratan HARUS.
• Persyaratan SANGAT DIREKOMENDASIKAN ditandai sebagai [SR] tetapi ID tidak ditetapkan.
• ID terdiri dari : Device Type ID - Condition ID - Requirement ID (misalnya C-0-1).

Setiap ID didefinisikan sebagai berikut:

• ID Jenis Perangkat (lihat selengkapnya di 2. Jenis Perangkat )
  • C: Core (Persyaratan yang diterapkan ke semua implementasi perangkat Android)
  • H: Perangkat Genggam Android
  • T: Perangkat Televisi Android
  • J: Implementasi Android Automotive
  • W: Implementasi Android Watch
  • Tab: Implementasi Tablet Android
• ID Kondisi
  • Ketika persyaratan tidak bersyarat, ID ini ditetapkan sebagai 0.
  • Jika persyaratannya bersyarat, 1 ditetapkan untuk kondisi pertama dan angka 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 memiliki dua bagian. Yang pertama sesuai dengan ID bagian seperti yang dijelaskan di atas. Bagian kedua mengidentifikasi faktor bentuk dan persyaratan khusus faktor bentuk.

ID bagian yang diikuti oleh ID Persyaratan yang dijelaskan di atas.

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

2. Jenis Perangkat

Proyek Sumber Terbuka Android menyediakan tumpukan perangkat lunak yang dapat digunakan untuk berbagai jenis perangkat dan faktor bentuk. Untuk mendukung keamanan pada perangkat, tumpukan perangkat lunak, termasuk OS pengganti atau implementasi kernel alternatif, diharapkan dapat dijalankan di lingkungan yang aman seperti yang dijelaskan di bagian 9 dan di tempat lain dalam CDD ini. 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 sesuai dengan salah satu jenis perangkat yang dijelaskan HARUS tetap memenuhi semua persyaratan di bagian lain dari Definisi Kompatibilitas ini.

2.1 Konfigurasi Perangkat

Untuk perbedaan utama dalam konfigurasi perangkat keras menurut jenis perangkat, lihat persyaratan khusus perangkat yang mengikuti di bagian ini.

2.2. Persyaratan Genggam

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

Implementasi perangkat Android diklasifikasikan sebagai Perangkat Genggam jika memenuhi semua kriteria berikut:

• Memiliki sumber daya yang memberikan mobilitas, seperti baterai.
• Memiliki ukuran layar diagonal fisik dalam kisaran 3,3 inci (atau 2,5 inci untuk implementasi perangkat yang dikirimkan pada API level 29 atau lebih lama) 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 yang memenuhi semua persyaratan yang dijelaskan dalam dokumen ini.

• [ 7.1 .1.3/H-SR] SANGAT DIREKOMENDASIKAN untuk memberikan pengguna kemampuan untuk mengubah ukuran tampilan (kepadatan layar).

• [ 7.1 .1.1/H-0-2] HARUS mendukung komposisi GPU dari buffer grafis setidaknya sebesar resolusi tertinggi dari semua tampilan bawaan.

Jika implementasi perangkat Genggam mendukung rotasi layar perangkat lunak, mereka:

• [ 7.1 .1.1/H-1-1]* HARUS membuat layar logis yang tersedia untuk aplikasi pihak ketiga minimal 2 inci pada tepi pendek dan 2,7 inci pada tepi panjang. Perangkat yang dikirimkan pada Android API level 29 atau yang lebih lama MUNGKIN dikecualikan dari persyaratan ini.

Jika implementasi perangkat Genggam tidak mendukung rotasi layar perangkat lunak, mereka:

• [ 7.1 .1.1/H-2-1]* HARUS membuat layar logis yang tersedia untuk aplikasi pihak ketiga setidaknya berukuran 2,7 inci pada tepi pendek. Perangkat yang dikirimkan pada Android API level 29 atau yang lebih lama MUNGKIN dikecualikan dari persyaratan ini.

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

• [ 7.1 .4.5/H-1-1] HARUS mengiklankan dukungan untuk 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 extensions.

Implementasi perangkat genggam:

• [ 7.1 .4.6/H-0-1] HARUS melaporkan apakah perangkat mendukung kemampuan profil GPU melalui properti sistem graphics.gpu.profiler.support .

Jika implementasi perangkat Genggam mendeklarasikan dukungan melalui properti sistem graphics.gpu.profiler.support , mereka:

• [ 7.1 .4.6/H-1-1] HARUS melaporkan sebagai keluaran jejak protobuf yang sesuai dengan skema penghitung GPU dan rendering GPU yang ditentukan dalam dokumentasi Perfetto .
• [ 7.1 .4.6/H-1-2] HARUS melaporkan nilai yang sesuai untuk penghitung GPU perangkat mengikuti proto paket jejak penghitung GPU .
• [ 7.1 .4.6/H-1-3] HARUS melaporkan nilai yang sesuai untuk RenderStages GPU perangkat mengikuti proto paket jejak tahap render .
• [ 7.1 .4.6/H-1-4] HARUS melaporkan titik jejak Frekuensi GPU seperti yang ditentukan oleh format: power/gpu_frequency .

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 di mana mode kompatibilitas diaktifkan, dan TIDAK HARUS mengubah perilaku mode kompatibilitas itu sendiri.
• [ 7.2 .1/H-0-1] HARUS menyertakan dukungan untuk aplikasi Editor Metode Input (IME) pihak ketiga.
• [ 7.2 .3/H-0-2] HARUS mengirim acara tekan normal dan lama dari fungsi Kembali ( KEYCODE_BACK ) ke aplikasi latar depan. Peristiwa ini TIDAK HARUS dikonsumsi oleh sistem dan DAPAT dipicu oleh luar perangkat Android (misalnya keyboard perangkat keras eksternal yang terhubung ke perangkat Android).
• [ 7.2 .3/H-0-3] HARUS menyediakan fungsi Beranda di semua layar yang kompatibel dengan Android yang menyediakan layar beranda.
• [ 7.2 .3/H-0-4] HARUS menyediakan fungsi Kembali di semua layar yang kompatibel dengan Android dan fungsi Terbaru di setidaknya satu layar yang kompatibel dengan 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 acara-acara pers lama.
• [ 7.3 .1/H-SR] SANGAT DIREKOMENDASIKAN untuk menyertakan akselerometer 3-sumbu.

Jika implementasi perangkat Genggam menyertakan akselerometer 3-sumbu, mereka:

• [ 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 ke aplikasi melalui tanda fitur android.hardware.location.gps , mereka:

• [ 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 rentang semu dan laju semu GNSS, yang, dalam kondisi langit terbuka setelah menentukan lokasi, saat diam atau bergerak dengan percepatan kurang dari 0,2 meter per detik kuadrat, sudah 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, mereka:

• [ 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, mereka:

• [ 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 , mereka:

• [ 7.5 .4/H-1-1] HARUS memiliki bidang pandang normal (FOV) secara default dan HARUS antara 50 dan 95 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 ada kurang dari 1GB memori yang tersedia untuk kernel dan ruang pengguna.

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

• [ 7.6 .1/H-1-1] Memori yang tersedia untuk kernel dan ruang pengguna HARUS setidaknya 416 MB 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 setidaknya 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 setidaknya 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 setidaknya 1344MB jika tampilan default menggunakan resolusi framebuffer hingga QHD (misalnya QWXGA).

Jika implementasi perangkat Genggam menyatakan dukungan ABI 32-bit dan 64-bit:

• [ 7.6 .1/H-5-1] Memori yang tersedia untuk kernel dan ruang pengguna HARUS setidaknya 816 MB 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 setidaknya 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 setidaknya 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 setidaknya 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 yang sudah didedikasikan untuk komponen perangkat keras seperti radio, video, dan sebagainya yang tidak berada di bawah kendali kernel pada implementasi perangkat.

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

• [ 7.6 .1/H-9-1] HARUS mendeklarasikan flag 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 menyertakan lebih dari 1GB memori yang tersedia untuk kernel dan ruang pengguna, mereka:

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

Jika implementasi perangkat Genggam mencakup lebih besar atau sama dengan 2GB dan kurang dari 4GB memori yang tersedia untuk kernel dan ruang pengguna, mereka: * [7.6.1/H-SR] SANGAT DIREKOMENDASIKAN untuk hanya mendukung ruang pengguna 32-bit (baik aplikasi dan kode sistem)

Jika implementasi perangkat Genggam menyertakan kurang dari 2GB memori yang tersedia untuk kernel dan ruang pengguna, mereka: * [7.6.1/H-1-1] HARUS hanya mendukung ABI 32-bit.

Implementasi perangkat genggam:

• [ 7.6 .2/H-0-1] TIDAK HARUS 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, mereka:

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

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

• [ 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, mereka:

• [ 7.9 .1/H-1-1] HARUS mendeklarasikan flag 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 beberapa 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 pemetaan perangkat lunak berikut dari kode HID:

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

Ketika terminal audio USB jenis 0x0302 terdeteksi, mereka:

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

Ketika terminal audio USB jenis 0x0402 terdeteksi, mereka:

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

Ketika API AudioManager.getDevices() dipanggil saat periferal USB terhubung, mereka:

• [ 7.8 .2.2/H-4-1] HARUS mencantumkan perangkat jenis 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 jenis 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 jenis 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 jenis 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 jenis 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 jenis 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 jenis AudioDeviceInfo.TYPE_USB_DEVICE dan peran isSource() jika bidang jenis terminal audio USB adalah 0x400.

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

Jika implementasi perangkat Genggam mendeklarasikan android.hardware.audio.output dan android.hardware.microphone , mereka:

• [ 5.6 /H-1-1] HARUS memiliki Latensi Pulang Pergi Berkelanjutan Rata-rata 500 800 milidetik atau kurang selama 5 pengukuran, dengan Deviasi Mutlak Rata-rata kurang dari 50 100 ms, melalui jalur data berikut: "speaker ke mikrofon", adaptor loopback 3,5 mm (jika didukung), loopback USB (jika didukung). setidaknya satu jalur yang didukung.

Jika implementasi perangkat Genggam menyertakan setidaknya satu aktuator haptic, mereka:

• [ 7.10 /H]* JANGAN menggunakan aktuator haptic (vibrator) eksentrik berputar massa (ERM).
• [ 7.10 /H]* HARUS memposisikan penempatan aktuator di dekat lokasi di mana perangkat biasanya dipegang atau disentuh oleh tangan.
• [ 7.10 /H]* HARUS menerapkan semua konstanta publik untuk menghapus haptics di android.view.HapticFeedbackConstants yaitu (CLOCK_TICK, CONTEXT_CLICK, KEYBOARD_PRESS, KEYBOARD_RELEASE, KEYBOARD_TAP, LONG_PRESS, TEXT_HANDLE_HANDLE_PRESS, VIRTUAL_REVIRTUAL_KEY, VIRTTURE_,END_FIRM, VIRTTURE_FIRTUAL_FIRM, KEYBOARD_FIRM, VIRTUAL_FIRM)
• [ 7.10 /H]* HARUS menerapkan semua konstanta publik untuk menghapus haptics di android.os.VibrationEffect yaitu (EFFECT_TICK, EFFECT_CLICK, EFFECT_HEAVY_CLICK dan EFFECT_DOUBLE_CLICK) dan semua konstanta PRIMITIVE_* publik yang layak untuk haptics kaya di android.os.Vibration (PRIMITIVE_CLICK dan PRIMITIVE_TICK) (KLIK, CENTANG, LOW_TICK, QUICK_FALL, QUICK_RISE, SLOW_RISE, SPIN, THUD). Beberapa dari primitif ini, seperti LOW_TICK dan SPIN hanya dapat dilakukan jika vibrator dapat mendukung frekuensi yang relatif rendah.

• [ 7.10 /H]* HARUS mengikuti penilaian kualitas untuk createOneShot() dan createWaveform() API.

Aktuator resonansi linier (LRA) adalah sistem pegas bermassa tunggal yang memiliki frekuensi resonansi dominan di mana massa diterjemahkan ke arah gerakan yang diinginkan.

Jika implementasi perangkat Genggam mencakup setidaknya satu aktuator resonansi linier, mereka:

• [ 7.10 /H]* HARUS memindahkan aktuator haptic di sumbu X (kiri-kanan) dari orientasi potret.

Jika implementasi perangkat Genggam memiliki aktuator haptic yang merupakan aktuator resonansi linier sumbu-X (LRA), mereka:

• [ 7.10 /H]* HARUS memiliki frekuensi resonansi LRA sumbu-X di bawah 200 Hz.

Jika implementasi perangkat genggam mengikuti pemetaan konstanta haptic, mereka:

• [ 7.10 /H]* HARUS memverifikasi status implementasi dengan menjalankan android.os.Vibrator.areAllEffectsSupported() dan android.os.Vibrator.arePrimitvesSupported() API.
• [ 7.10 /H]* HARUS melakukan penilaian kualitas untuk konstanta haptic.

2.2.2. Multimedia

Implementasi perangkat genggam HARUS mendukung format encoding dan decoding 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 MPEG-4 AAC (AAC LC)
• [ 5.1 /H-0-4] Profil MPEG-4 HE AAC (AAC+)
• [ 5.1 /H-0-5] AAC ELD (AAC penundaan rendah yang disempurnakan)

Implementasi perangkat genggam HARUS mendukung format penyandian 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 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.2.3.1 /H-0-2]* HARUS melakukan pramuat satu atau beberapa aplikasi atau komponen layanan dengan pengendali maksud, untuk semua pola filter maksud publik yang ditentukan oleh maksud aplikasi berikut yang tercantum di sini .
• [ 3.2.3.1 /H-SR] SANGAT DIREKOMENDASIKAN untuk memuat aplikasi email yang dapat menangani niat ACTION_SENDTO atau ACTION_SEND atau ACTION_SEND_MULTIPLE untuk mengirim email.
• [ 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 penjelajahan web pengguna umum.
• [ 3.8 .1/H-SR] SANGAT DIREKOMENDASIKAN untuk menerapkan peluncur default yang mendukung penyematan pintasan, widget, dan fitur widget dalam aplikasi .
• [ 3.8 .1/H-SR] SANGAT DIREKOMENDASIKAN untuk menerapkan peluncur default yang menyediakan akses cepat ke pintasan tambahan yang disediakan oleh aplikasi pihak ketiga melalui API ShortcutManager .
• [ 3.8 .1/H-SR] SANGAT DIREKOMENDASIKAN untuk menyertakan aplikasi peluncur default yang menunjukkan lencana untuk ikon aplikasi.
• [ 3.8 .2/H-SR] SANGAT DIREKOMENDASIKAN 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 Notification and NotificationManager API.
• [ 3.8 .3/H-0-2] HARUS mendukung notifikasi yang kaya.
• [ 3.8 .3/H-0-3] HARUS mendukung pemberitahuan pendahuluan.
• [ 3.8 .3/H-0-4] HARUS menyertakan bayangan pemberitahuan, memberikan pengguna kemampuan untuk secara langsung mengontrol (misalnya membalas, menunda, menutup, memblokir) pemberitahuan melalui kemampuan pengguna seperti tombol tindakan atau panel kontrol seperti yang 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 DIREKOMENDASIKAN untuk menampilkan pilihan pertama yang disediakan melalui RemoteInput.Builder setChoices() dalam bayangan pemberitahuan tanpa interaksi pengguna tambahan.
• [ 3.8 .3/H-SR] SANGAT DIREKOMENDASIKAN untuk menampilkan semua pilihan yang disediakan melalui RemoteInput.Builder setChoices() di bayangan notifikasi saat pengguna memperluas semua notifikasi di bayangan notifikasi.
• [ 3.8 .3.1/H-SR] SANGAT DIREKOMENDASIKAN untuk menampilkan tindakan yang Notification.Action.Builder.setContextual disetel sebagai true sesuai dengan balasan yang ditampilkan oleh Notification.Remoteinput.Builder.setChoices .
• [ 3.8 .4/H-SR] SANGAT DIREKOMENDASIKAN untuk menerapkan asisten pada perangkat untuk menangani tindakan Bantuan .

Jika implementasi perangkat Genggam mendukung tindakan Bantuan, mereka:

• [ 3.8 .4/H-SR] SANGAT DIREKOMENDASIKAN untuk menggunakan tekan lama pada 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 mendukung conversation notifications dan mengelompokkannya ke dalam bagian terpisah dari pemberitahuan dan pemberitahuan non-percakapan senyap, mereka:

• [ 3.8 .4/H-1-1]* HARUS menampilkan pemberitahuan percakapan sebelum pemberitahuan non-percakapan dengan pengecualian pemberitahuan layanan latar depan yang sedang berlangsung dan kepentingan: pemberitahuan tinggi .

Jika implementasi perangkat Android Handheld mendukung layar kunci, mereka:

• [ 3.8 .10/H-1-1] HARUS menampilkan Notifikasi layar Terkunci termasuk Template Notifikasi Media.

Jika implementasi perangkat Genggam mendukung layar kunci yang aman, mereka:

• [ 3.9 /H-1-1] HARUS menerapkan berbagai kebijakan administrasi perangkat yang ditentukan dalam dokumentasi Android SDK.

Jika implementasi perangkat Genggam menyertakan dukungan untuk ControlsProviderService dan Control API dan mengizinkan aplikasi pihak ketiga untuk memublikasikan device controls , maka implementasi tersebut:

• [ 3.8 .16/H-1-1] HARUS mendeklarasikan flag fitur android.software.controls dan menyetelnya ke true .
• [ 3.8 .16/H-1-2] HARUS memberikan kemampuan kepada pengguna untuk menambah, mengedit, memilih, dan mengoperasikan kontrol perangkat favorit pengguna dari kontrol yang didaftarkan oleh aplikasi pihak ketiga melalui ControlsProviderService dan Control API .
• [ 3.8 .16/H-1-3] HARUS menyediakan akses ke keterjangkauan pengguna ini dalam tiga interaksi dari Peluncur default.
• [ 3.8 .16/H-1-4] HARUS secara akurat merender di pengguna ini memberi nama dan ikon setiap aplikasi pihak ketiga yang menyediakan kontrol melalui API ControlsProviderService serta bidang tertentu yang disediakan oleh API Control .

Sebaliknya, Jika implementasi perangkat Genggam tidak menerapkan kontrol tersebut, mereka:

• [ 3.8 .16/H-2-1] HARUS melaporkan null untuk ControlsProviderService dan Control API.
• [ 3.8 .16/H-2-2] HARUS mendeklarasikan flag fitur android.software.controls dan menyetelnya ke false .

Jika implementasi perangkat genggam tidak berjalan dalam mode tugas kunci , ketika konten disalin ke clipboard mereka: * [3.8.17/H-1-1] HARUS menampilkan konfirmasi yang terlihat oleh pengguna (misalnya, thumbnail atau “Content copy. ”) dengan indikasi apakah data clipboard akan disinkronkan di seluruh perangkat

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 melebihi fungsionalitas Switch Access dan TalkBack (untuk bahasa yang didukung oleh mesin Text-to-speech yang telah diinstal sebelumnya) layanan aksesibilitas seperti yang disediakan dalam buka bicara balik proyek sumber .
• [ 3.11 /H-0-1] HARUS mendukung pemasangan mesin TTS pihak ketiga.
• [ 3.11 /H-SR] Are STRONGLY RECOMMENDED to include a TTS engine supporting the languages available on the device.
• [ 3.13 /H-SR] Are STRONGLY RECOMMENDED to include a Quick Settings UI component.

If Android handheld device implementations declare FEATURE_BLUETOOTH or FEATURE_WIFI support, they:

• [ 3.16 /H-1-1] MUST support the companion device pairing feature.

If the navigation function is provided as an on-screen, gesture-based action:

• [ 7.2 .3/H] The gesture recognition zone for the Home function SHOULD be no higher than 32 dp in height from the bottom of the screen.

If Handheld device implementations provide a navigation function as a gesture from anywhere on the left and right edges of the screen:

• [ 7.2 .3/H-0-1] The navigation function's gesture area MUST be less than 40 dp in width on each side. The gesture area SHOULD be 24 dp in width by default.

If Handheld device implementations support a secure lock screen and have greater than or equal to 2GB of memory available to the kernel and userspace, they:

• [3.9/H-1-2] MUST declare the support of managed profiles via the android.software.managed_users feature flag.

If Android handheld device implementations declare the support for camera via android.hardware.camera.any they:

• [ 7.5 .4/H-1-1] MUST honor the android.media.action.STILL_IMAGE_CAMERA and android.media.action.STILL_IMAGE_CAMERA_SECURE intent and launch the camera in still image mode as described in the SDK.
• [ 7.5 .4/H-1-2] MUST honor the android.media.action.VIDEO_CAMERA intent to launch the camera in video mode as described in the SDK.

2.2.4. Performance and Power

• [ 8.1 /H-0-1] Consistent frame latency . Inconsistent frame latency or a delay to render frames MUST NOT happen more often than 5 frames in a second, and SHOULD be below 1 frames in a second.
• [ 8.1 /H-0-2] User interface latency . Device implementations MUST ensure low latency user experience by scrolling a list of 10K list entries as defined by the Android Compatibility Test Suite (CTS) in less than 36 secs.
• [ 8.1 /H-0-3] Task switching . When multiple applications have been launched, re-launching an already-running application after it has been launched MUST take less than 1 second.

Handheld device implementations:

• [ 8.2 /H-0-1] MUST ensure a sequential write performance of at least 5 MB/s.
• [ 8.2 /H-0-2] MUST ensure a random write performance of at least 0.5 MB/s.
• [ 8.2 /H-0-3] MUST ensure a sequential read performance of at least 15 MB/s.
• [ 8.2 /H-0-4] MUST ensure a random read performance of at least 3.5 MB/s.

If Handheld device implementations include features to improve device power management that are included in AOSP or extend the features that are included in AOSP, they:

• [ 8.3 /H-1-1] MUST provide user affordance to enable and disable the battery saver feature.
• [ 8.3 /H-1-2] MUST provide user affordance to display all apps that are exempted from App Standby and Doze power-saving modes.

Handheld device implementations:

• [ 8.4 /H-0-1] MUST 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.
• [ 8.4 /H-0-2] MUST report all power consumption values in milliampere hours (mAh).
• [ 8.4 /H-0-3] MUST report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the uid_cputime kernel module implementation.
• [ 8.4 /H-0-4] MUST make this power usage available via the adb shell dumpsys batterystats shell command to the app developer.
• [ 8.4 /H] SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application.

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

• [ 8.4 /H-1-1] MUST honor the android.intent.action.POWER_USAGE_SUMMARY intent and display a settings menu that shows this power usage.

2.2.5. Security Model

Handheld device implementations:

• [ 9.1 /H-0-1] MUST allow third-party apps to access the usage statistics via the android.permission.PACKAGE_USAGE_STATS permission and provide a user-accessible mechanism to grant or revoke access to such apps in response to the android.settings.ACTION_USAGE_ACCESS_SETTINGS intent.

Handheld device implementations:

• [ 9.11 /H-0-2] MUST back up the keystore implementation with an isolated execution environment.
• [ 9.11 /H-0-3] 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. Secure isolation MUST block all potential mechanisms by which kernel or userspace code might access the internal state of the isolated environment, including DMA. The upstream Android Open Source Project (AOSP) meets this requirement by using the Trusty implementation, but another ARM TrustZone-based solution or a third-party reviewed secure implementation of a proper hypervisor-based isolation are alternative options.
• [ 9.11 /H-0-4] MUST perform the lock screen authentication in the isolated execution environment and only when successful, allow the authentication-bound keys to be used. Lock screen credentials MUST be stored in a way that allows only the isolated execution environment to perform lock screen authentication. The upstream Android Open Source Project provides the Gatekeeper Hardware Abstraction Layer (HAL) and Trusty, which can be used to satisfy this requirement.
• [ 9.11 /H-0-5] MUST support key attestation where the attestation signing key is protected by secure hardware and signing is performed in secure hardware. The attestation signing keys MUST be shared across large enough number of devices to prevent the keys from being used as device identifiers. One way of meeting this requirement is to share the same attestation key unless at least 100,000 units of a given SKU are produced. If more than 100,000 units of an SKU are produced, a different key MAY be used for each 100,000 units.
• [9/H-0-1] MUST declare the 'android.hardware.security.model.compatible' feature.

Note that if a device implementation is already launched on an earlier Android version, such a device is exempted from the requirement to have a keystore backed by an isolated execution environment and support the key attestation, unless it declares the android.hardware.fingerprint feature which requires a keystore backed by an isolated execution environment.

When Handheld device implementations support a secure lock screen, they:

• [ 9.11 /H-1-1] MUST allow the user to choose the shortest sleep timeout, that is a transition time from the unlocked to the locked state, as 15 seconds or less.
• [ 9.11 /H-1-2] MUST provide user affordance to hide notifications and disable all forms of authentication except for the primary authentication described in 9.11.1 Secure Lock Screen . The AOSP meets the requirement as lockdown mode.

If Handheld device implementations include multiple users and do not declare the android.hardware.telephony feature flag, they:

• [ 9.5 /H-2-1] MUST support restricted profiles, a feature that allows device owners to manage additional users and their capabilities on the device. With restricted profiles, device owners can quickly set up separate environments for additional users to work in, with the ability to manage finer-grained restrictions in the apps that are available in those environments.

If Handheld device implementations include multiple users and declare the android.hardware.telephony feature flag, they:

• [ 9.5 /H-3-1] MUST NOT support restricted profiles but MUST align with the AOSP implementation of controls to enable /disable other users from accessing the voice calls and SMS.

Android, through the System API VoiceInteractionService supports a mechanism for secure always-on hotword detection without mic access indication

If Handheld device implementations support the System API HotwordDetectionService or a another mechanism for hotword detection without mic access indication, they:

• [9.8/H-1-1] MUST make sure the hotword detection service can only transmit data to the System or ContentCaptureService
• [9.8/H-1-2] MUST make sure the hotword detection service can only transmit mic audio data or data derived from it to the system server through HotwordDetectionService API, or to ContentCaptureService through ContentCaptureManager API.
• [9.8/H-1-3] MUST NOT supply mic audio that is longer than 30 seconds for an individual hardware-triggered request to the hotword detection service.
• [9.8/H-1-4] MUST NOT supply buffered mic audio older than 8 seconds for an individual request to the hotword detection service.
• [9.8/H-1-5] MUST NOT supply buffered mic audio older than 30 seconds to the voice interaction service or similar entity.
• [9.8/H-1-6] MUST NOT allow more than 100 bytes of data to be transmitted out of the hotword detection service on each successful hotword result.
• [9.8/H-1-7] MUST NOT allow more than 5 bits of data to be transmitted out of the hotword detection service on each negative hotword result.
• [9.8/H-1-8] MUST only allow transmission of data out of the hotword detection service on a hotword validation request from the system server.
• [9.8/H-1-9] MUST NOT allow a user-installable application to provide the hotword detection service.
• [9.8/H-1-10] MUST NOT surface in the UI quantitative data about mic usage by the hotword detection service.
• [9.8/H-1-11] MUST log the number of bytes included in every transmission from the hotword detection service to allow inspectability for security researchers.
• [9.8/H-1-12] MUST support a debug mode that logs raw contents of every transmission from the hotword detection service to allow inspectability for security researchers.
• [9.8/H-1-13] MUST restart the process hosting the hotword detection service at least once every hour or every 30 hardware-trigger events, whichever comes first.
• [9.8/H-1-14] MUST display the microphone indicator, as required in [9.8/C-3-1], when a successful hotword result is transmitted to the voice interaction service or similar entity.
• [9.8/H-SR] Are STRONGLY RECOMMENDED to notify users before setting an application as the provider of the hotword detection service.
• [9.8/H-SR] Are STRONGLY RECOMMENDED to disallow the transmission of unstructured data out of the hotword detection service.

If device implementations include an application that uses the System API HotwordDetectionService , or similar mechanism for hotword detection without mic usage indication, the application: * [9.8/H-2-1] MUST provide explicit notice to the user for each hotword phrase supported. * [9.8/H-2-2] MUST NOT preserve raw audio data, or data derived from it, through the hotword detection service. * [9.8/H-2-3] MUST NOT transmit from the hotword detection service, audio data, data that can be used to reconstruct (wholly or partially) the audio, or audio contents unrelated to the hotword itself, except to the ContentCaptureService .

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

• [ 9.8.2 /H-4-1] MUST display the microphone indicator when an app is accessing audio data from the microphone, but not when the microphone is only accessed by HotwordDetectionService , SOURCE_HOTWORD , ContentCaptureService or apps holding the roles called out in section 9.1 with CDD identifier [C-4-X].
• [ 9.8.2 /H-4-2] MUST display the list of Recent and Active apps using microphone as returned from PermissionManager.getIndicatorAppOpUsageData() , along with any attribution messages associated with them.
• [ 9.8.2 /H-4-3] MUST not hide the microphone indicator for system apps that have visible user interfaces or direct user interaction.
• [ 9.8.2 /H-4-4] MUST display the list of Recent and Active apps using the microphone as returned from PermissionManager.getIndicatorAppOpUsageData() , along with any attribution messages associated with them.

If Handheld device implementations declare android.hardware.camera.any , they:

• [ 9.8.2 /H-5-1] MUST display the camera indicator when an app is accessing live camera data, but not when the camera is only being accessed by app(s) holding the roles called out in section 9.1 with CDD identifier [C-4-X].
• [ 9.8.2 /H-5-2] MUST display Recent and Active apps using camera as returned from PermissionManager.getIndicatorAppOpUsageData() , along with any attribution messages associated with them.
• [ 9.8.2 /H-5-3] MUST not hide the camera indicator for system apps that have visible user interfaces or direct user interaction.

2.2.6. Developer Tools and Options Compatibility

Handheld device implementations (* Not applicable for Tablet):

• [ 6.1 /H-0-1]* MUST support the shell command cmd testharness .

Handheld device implementations (* Not applicable for Tablet):

• Perfetto
  • [ 6.1 /H-0-2]* MUST expose a /system/bin/perfetto binary to the shell user which cmdline complies with the perfetto documentation .
  • [ 6.1 /H-0-3]* The perfetto binary MUST accept as input a protobuf config that complies with the schema defined in the perfetto documentation .
  • [ 6.1 /H-0-4]* The perfetto binary MUST write as output a protobuf trace that complies with the schema defined in the perfetto documentation .
  • [ 6.1 /H-0-5]* MUST provide, through the perfetto binary, at least the data sources described in the perfetto documentation .
  • [ 6.1 /H-0-6]* The perfetto traced daemon MUST be enabled by default (system property persist.traced.enable ).

2.2.7. Handheld Media Performance Class

See Section 7.11 for the definition of media performance class.

2.2.7.1. Media

If Handheld device implementations return android.os.Build.VERSION_CODES.S for android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS , then they:

• MUST meet the media requirements listed in android 12 CDD section 2.2.7.1 .

2.2.7.2. Camera

If Handheld device implementations return android.os.Build.VERSION_CODES.S for android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS , then they:

• MUST meet the camera requirements listed in android 12 CDD section 2.2.7.2 .

2.2.7.3. Hardware

If Handheld device implementations return android.os.Build.VERSION_CODES.S for android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS , then they:

• MUST meet the hardware requirements listed in android 12 CDD section 2.2.7.3 .

2.2.7.4. Performance

If Handheld device implementations return android.os.Build.VERSION_CODES.S for android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS , then they:

• MUST meet the performance requirements listed in android 12 CDD section 2.2.7.4 .

2.3. Television Requirements

An Android Television device refers to an Android device implementation that is an entertainment interface for consuming digital media, movies, games, apps, and/or live TV for users sitting about ten feet away (a “lean back” or “10-foot user interface”).

Android device implementations are classified as a Television if they meet all the following criteria:

• Have provided a mechanism to remotely control the rendered user interface on the display that might sit ten feet away from the user.
• Have an embedded screen display with the diagonal length larger than 24 inches OR include a video output port, such as VGA, HDMI, DisplayPort, or a wireless port for display.

The additional requirements in the rest of this section are specific to Android Television device implementations.

2.3.1. Hardware

Television device implementations:

• [ 7.2 .2/T-0-1] MUST support D-pad .
• [ 7.2 .3/T-0-1] MUST provide the Home and Back functions.
• [ 7.2 .3/T-0-2] MUST send both the normal and long press event of the Back function ( KEYCODE_BACK ) to the foreground application.
• [ 7.2 .6.1/T-0-1] MUST include support for game controllers and declare the android.hardware.gamepad feature flag.
• [ 7.2 .7/T] SHOULD provide a remote control from which users can access non-touch navigation and core navigation keys inputs.

If Television device implementations include a 3-axis gyroscope, they:

• [ 7.3 .4/T-1-1] MUST be able to report events up to a frequency of at least 100 Hz.
• [ 7.3 .4/T-1-2] MUST be capable of measuring orientation changes up to 1000 degrees per second.

Television device implementations:

• [ 7.4 .3/T-0-1] MUST support Bluetooth and Bluetooth LE.
• [ 7.6 .1/T-0-1] MUST have at least 4 GB of non-volatile storage available for application private data (aka "/data" partition).

If Television device implementations include a USB port that supports host mode, they:

• [ 7.5 .3/T-1-1] MUST include support for an external camera that connects through this USB port but is not necessarily always connected.

If TV device implementations are 32-bit:

• [ 7.6 .1/T-1-1] The memory available to the kernel and userspace MUST be at least 896MB if any of the following densities are used:

  • 400dpi or higher on small/normal screens
  • xhdpi or higher on large screens
  • tvdpi or higher on extra large screens

If TV device implementations are 64-bit:

• [ 7.6 .1/T-2-1] The memory available to the kernel and userspace MUST be at least 1280MB if any of the following densities are used:

  • 400dpi or higher on small/normal screens
  • xhdpi or higher on large screens
  • tvdpi or higher on extra large screens

Note that the "memory available to the kernel and userspace" above refers to the memory space provided in addition to any memory already dedicated to hardware components such as radio, video, and so on that are not under the kernel's control on device implementations.

Television device implementations:

• [ 7.8 .1/T] SHOULD include a microphone.
• [ 7.8 .2/T-0-1] MUST have an audio output and declare android.hardware.audio.output .

2.3.2. Multimedia

Television device implementations MUST support the following audio encoding and decoding formats and make them available to third-party applications:

• [ 5.1 /T-0-1] MPEG-4 AAC Profile (AAC LC)
• [ 5.1 /T-0-2] MPEG-4 HE AAC Profile (AAC+)
• [ 5.1 /T-0-3] AAC ELD (enhanced low delay AAC)

Television device implementations MUST support the following video encoding formats and make them available to third-party applications:

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

Television device implementations:

• [ 5.2 .2/T-SR] Are STRONGLY RECOMMENDED to support H.264 encoding of 720p and 1080p resolution videos at 30 frames per second.

Television device implementations MUST support the following video decoding formats and make them available to third-party applications:

• [ 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] VP9
• [ 5.3.1 /T-0-6] MPEG-2

Television device implementations MUST support MPEG-2 decoding, as detailed in Section 5.3.1, at standard video frame rates and resolutions up to and including:

• [ 5.3.1 /T-1-1] HD 1080p at 59.94 frames per second with Main Profile High Level.
• [ 5.3.1 /T-1-2] HD 1080i at 59.94 frames per second with Main Profile High Level. They MUST deinterlace interlaced MPEG-2 video and make it available to third-party applications.

Television device implementations MUST support H.264 decoding, as detailed in Section 5.3.4, at standard video frame rates and resolutions up to and including:

• [ 5.3.4 /T-1-1] HD 1080p at 60 frames per second with Baseline Profile
• [ 5.3.4 /T-1-2] HD 1080p at 60 frames per second with Main Profile
• [ 5.3.4 /T-1-3] HD 1080p at 60 frames per second with High Profile Level 4.2

Television device implementations with H.265 hardware decoders MUST support H.265 decoding, as detailed in Section 5.3.5, at standard video frame rates and resolutions up to and including:

• [ 5.3.5 /T-1-1] HD 1080p at 60 frames per second with Main Profile Level 4.1

If Television device implementations with H.265 hardware decoders support H.265 decoding and the UHD decoding profile, they:

• [ 5.3.5 /T-2-1] MUST support the UHD decoding profile at 60 frames per second with Main10 Level 5 Main Tier profile

Television device implementations MUST support VP8 decoding, as detailed in Section 5.3.6, at standard video frame rates and resolutions up to and including:

• [ 5.3.6 /T-1-1] HD 1080p at 60 frames per second decoding profile

Television device implementations with VP9 hardware decoders MUST support VP9 decoding, as detailed in Section 5.3.7, at standard video frame rates and resolutions up to and including:

• [ 5.3.7 /T-1-1] HD 1080p at 60 frames per second with profile 0 (8 bit color depth)

If Television device implementations with VP9 hardware decoders support VP9 decoding and the UHD decoding profile, they:

• [ 5.3.7 /T-2-1] MUST support the UHD decoding profile at 60 frames per second with profile 0 (8 bit color depth).
• [ 5.3.7 /T-2-1] Are STRONGLY RECOMMENDED to support the UHD decoding profile at 60 frames per second with profile 2 (10 bit color depth).

Television device implementations:

• [ 5.5 /T-0-1] MUST include support for system Master Volume and digital audio output volume attenuation on supported outputs, except for compressed audio passthrough output (where no audio decoding is done on the device).

If Television device implementations do not have a built in display, but instead support an external display connected via HDMI, they:

• [ 5.8 /T-0-1] MUST set the HDMI output mode to select the maximum resolution that can be supported with either a 50Hz or 60Hz refresh rate.
• [ 5.8 /T-SR] Are STRONGLY RECOMMENDED to provide a user configurable HDMI refresh rate selector.
• [ 5.8 ] SHOULD set the HDMI output mode refresh rate to either 50Hz or 60Hz, depending on the video refresh rate for the region the device is sold in.

If Television device implementations do not have a built in display, but instead support an external display connected via HDMI, they:

• [ 5.8 /T-1-1] MUST support HDCP 2.2.

If Television device implementations do not support UHD decoding, but instead support an external display connected via HDMI, they:

• [ 5.8 /T-2-1] MUST support HDCP 1.4

2.3.3. Software

Television device implementations:

• [ 3 /T-0-1] MUST declare the features android.software.leanback and android.hardware.type.television .
• [ 3.2.3.1 /T-0-1] MUST preload one or more applications or service components with an intent handler, for all the public intent filter patterns defined by the following application intents listed here .
• [ 3.4 .1/T-0-1] MUST provide a complete implementation of the android.webkit.Webview API.

If Android Television device implementations support a lock screen,they:

• [ 3.8 .10/T-1-1] MUST display the Lock screen Notifications including the Media Notification Template.

Television device implementations:

• [ 3.8 .14/T-SR] Are STRONGLY RECOMMENDED to support picture-in-picture (PIP) mode multi-window.
• [ 3.10 /T-0-1] MUST support third-party accessibility services.
• [ 3.10 /T-SR] Are STRONGLY RECOMMENDED to preload accessibility services on the device comparable with or exceeding functionality of the Switch Access and TalkBack (for languages supported by the preinstalled Text-to-speech engine) accessibility services as provided in the talkback open source project .

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

• [ 3.11 /T-SR] Are STRONGLY RECOMMENDED to include a TTS engine supporting the languages available on the device.
• [ 3.11 /T-1-1] MUST support installation of third-party TTS engines.

Television device implementations:

• [ 3.12 /T-0-1] MUST support TV Input Framework.

2.3.4. Performance and Power

• [ 8.1 /T-0-1] Consistent frame latency . Inconsistent frame latency or a delay to render frames MUST NOT happen more often than 5 frames in a second, and SHOULD be below 1 frames in a second.
• [ 8.2 /T-0-1] MUST ensure a sequential write performance of at least 5MB/s.
• [ 8.2 /T-0-2] MUST ensure a random write performance of at least 0.5MB/s.
• [ 8.2 /T-0-3] MUST ensure a sequential read performance of at least 15MB/s.
• [ 8.2 /T-0-4] MUST ensure a random read performance of at least 3.5MB/s.

If Television device implementations include features to improve device power management that are included in AOSP or extend the features that are included in AOSP, they:

• [ 8.3 /T-1-1] MUST provide user affordance to enable and disable the battery saver feature.

If Television device implementations do not have a battery they:

• [ 8.3 /T-1-2] MUST register the device as a batteryless device as described in Supporting Batteryless Devices .

If Television device implementations have a battery they:

• [ 8.3 /T-1-3] MUST provide user affordance to display all apps that are exempted from App Standby and Doze power-saving modes.

Television device implementations:

• [ 8.4 /T-0-1] MUST 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.
• [ 8.4 /T-0-2] MUST report all power consumption values in milliampere hours (mAh).
• [ 8.4 /T-0-3] MUST report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the uid_cputime kernel module implementation.
• [ 8.4 /T] SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application.
• [ 8.4 /T-0-4] MUST make this power usage available via the adb shell dumpsys batterystats shell command to the app developer.

2.3.5. Security Model

Television device implementations:

• [ 9.11 /T-0-1] MUST back up the keystore implementation with an isolated execution environment.
• [ 9.11 /T-0-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. Secure isolation MUST block all potential mechanisms by which kernel or userspace code might access the internal state of the isolated environment, including DMA. The upstream Android Open Source Project (AOSP) meets this requirement by using the Trusty implementation, but another ARM TrustZone-based solution or a third-party reviewed secure implementation of a proper hypervisor-based isolation are alternative options.
• [ 9.11 /T-0-3] MUST perform the lock screen authentication in the isolated execution environment and only when successful, allow the authentication-bound keys to be used. Lock screen credentials MUST be stored in a way that allows only the isolated execution environment to perform lock screen authentication. The upstream Android Open Source Project provides the Gatekeeper Hardware Abstraction Layer (HAL) and Trusty, which can be used to satisfy this requirement.
• [ 9.11 /T-0-4] MUST support key attestation where the attestation signing key is protected by secure hardware and signing is performed in secure hardware. The attestation signing keys MUST be shared across large enough number of devices to prevent the keys from being used as device identifiers. One way of meeting this requirement is to share the same attestation key unless at least 100,000 units of a given SKU are produced. If more than 100,000 units of an SKU are produced, a different key MAY be used for each 100,000 units.
• [9/T-0-1] MUST declare the 'android.hardware.security.model.compatible' feature.

Note that if a device implementation is already launched on an earlier Android version, such a device is exempted from the requirement to have a keystore backed by an isolated execution environment and support the key attestation, unless it declares the android.hardware.fingerprint feature which requires a keystore backed by an isolated execution environment.

If Television device implementations support a secure lock screen, they:

• [ 9.11 /T-1-1] 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 or less.

If Television device implementations include multiple users and do not declare the android.hardware.telephony feature flag, they:

• [ 9.5 /T-2-1] MUST support restricted profiles, a feature that allows device owners to manage additional users and their capabilities on the device. With restricted profiles, device owners can quickly set up separate environments for additional users to work in, with the ability to manage finer-grained restrictions in the apps that are available in those environments.

If Television device implementations include multiple users and declare the android.hardware.telephony feature flag, they:

• [ 9.5 /T-3-1] MUST NOT support restricted profiles but MUST align with the AOSP implementation of controls to enable /disable other users from accessing the voice calls and SMS.

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

• [ 9.8.2 /T-4-1] MUST display the microphone indicator when an app is accessing audio data from the microphone, but not when the microphone is only accessed by HotwordDetectionService, SOURCE_HOTWORD, ContentCaptureService, or apps holding the roles called out in Section 9.1 Permissions with CDD identifier C-3-X].
• [ 9.8.2 /T-4-2] MUST not hide the microphone indicator for system apps that have visible user interfaces or direct user interaction.

If Television device implementations declare android.hardware.camera.any , they:

• [ 9.8.2 /T-5-1] MUST display the camera indicator when an app is accessing live camera data, but not when the camera is only being accessed by app(s) holding the roles called out in Section 9.1 Permissions with CDD identifier [C-3-X].
• [ 9.8.2 /T-5-2] MUST not hide the camera indicator for system apps that have visible user interfaces or direct user interaction.

2.3.6. Developer Tools and Options Compatibility

Television device implementations:

• Perfetto
  • [ 6.1 /T-0-1] MUST expose a /system/bin/perfetto binary to the shell user which cmdline complies with the perfetto documentation .
  • [ 6.1 /T-0-2] The perfetto binary MUST accept as input a protobuf config that complies with the schema defined in the perfetto documentation .
  • [ 6.1 /T-0-3] The perfetto binary MUST write as output a protobuf trace that complies with the schema defined in the perfetto documentation .
  • [ 6.1 /T-0-4] MUST provide, through the perfetto binary, at least the data sources described in the perfetto documentation .

2.4. Watch Requirements

An Android Watch device refers to an Android device implementation intended to be worn on the body, perhaps on the wrist.

Android device implementations are classified as a Watch if they meet all the following criteria:

• Have a screen with the physical diagonal length in the range from 1.1 to 2.5 inches.
• Have a mechanism provided to be worn on the body.

The additional requirements in the rest of this section are specific to Android Watch device implementations.

2.4.1. Hardware

Watch device implementations:

• [ 7.1 .1.1/W-0-1] MUST have a screen with the physical diagonal size in the range from 1.1 to 2.5 inches.

• [ 7.2 .3/W-0-1] MUST have the Home function available to the user, and the Back function except for when it is in UI_MODE_TYPE_WATCH .

• [ 7.2 .4/W-0-1] MUST support touchscreen input.

• [ 7.3 .1/W-SR] Are STRONGLY RECOMMENDED to include a 3-axis accelerometer.

If Watch device implementations include a GPS/GNSS receiver and report the capability to applications through the android.hardware.location.gps feature flag, they:

• [ 7.3 .3/W-1-1] MUST report GNSS measurements, as soon as they are found, even if a location calculated from GPS/GNSS is not yet reported.
• [ 7.3 .3/W-1-2] MUST 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.

If Watch device implementations include a 3-axis gyroscope, they:

• [ 7.3 .4/W-2-1] MUST be capable of measuring orientation changes up to 1000 degrees per second.

Watch device implementations:

• [ 7.4 .3/W-0-1] MUST support Bluetooth.

• [ 7.6 .1/W-0-1] MUST have at least 1 GB of non-volatile storage available for application private data (aka "/data" partition).

• [ 7.6 .1/W-0-2] MUST have at least 416 MB memory available to the kernel and userspace.

• [ 7.8 .1/W-0-1] MUST include a microphone.

• [ 7.8 .2/W] MAY have audio output.

2.4.2. Multimedia

No additional requirements.

2.4.3. Software

Watch device implementations:

• [ 3 /W-0-1] MUST declare the feature android.hardware.type.watch .
• [ 3 /W-0-2] MUST support uiMode = UI_MODE_TYPE_WATCH .
• [ 3.2.3.1 /W-0-1] MUST preload one or more applications or service components with an intent handler, for all the public intent filter patterns defined by the following application intents listed here .

Watch device implementations:

• [ 3.8 .4/W-SR] Are STRONGLY RECOMMENDED to implement an assistant on the device to handle the Assist action .

Watch device implementations that declare the android.hardware.audio.output feature flag:

• [ 3.10 /W-1-1] MUST support third-party accessibility services.
• [ 3.10 /W-SR] Are STRONGLY RECOMMENDED to preload accessibility services on the device comparable with or exceeding functionality of the Switch Access and TalkBack (for languages supported by the preinstalled Text-to-speech engine) accessibility services as provided in the talkback open source project .

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

• [ 3.11 /W-SR] Are STRONGLY RECOMMENDED to include a TTS engine supporting the languages available on the device.

• [ 3.11 /W-0-1] MUST support installation of third-party TTS engines.

2.4.4. Performance and Power

If Watch device implementations include features to improve device power management that are included in AOSP or extend the features that are included in AOSP, they:

• [ 8.3 /W-SR] Are STRONGLY RECOMMENDED to provide user affordance to display all apps that are exempted from App Standby and Doze power-saving modes.
• [ 8.3 /W-SR] Are STRONGLY RECOMMENDED to provide user affordance to enable and disable the battery saver feature.

Watch device implementations:

• [ 8.4 /W-0-1] MUST 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.
• [ 8.4 /W-0-2] MUST report all power consumption values in milliampere hours (mAh).
• [ 8.4 /W-0-3] MUST report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the uid_cputime kernel module implementation.
• [ 8.4 /W-0-4] MUST make this power usage available via the adb shell dumpsys batterystats shell command to the app developer.
• [ 8.4 /W] SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application.

2.4.5. Security Model

Watch device implementations:

• [9/H-0-1] MUST declare the 'android.hardware.security.model.compatible' feature.

If Watch device implementations include multiple users and do not declare the android.hardware.telephony feature flag, they:

• [ 9.5 /W-1-1] MUST support restricted profiles, a feature that allows device owners to manage additional users and their capabilities on the device. With restricted profiles, device owners can quickly set up separate environments for additional users to work in, with the ability to manage finer-grained restrictions in the apps that are available in those environments.

If Watch device implementations include multiple users and declare the android.hardware.telephony feature flag, they:

• [ 9.5 /W-2-1] MUST NOT support restricted profiles but MUST align with the AOSP implementation of controls to enable /disable other users from accessing the voice calls and SMS.

2.5. Automotive Requirements

Android Automotive implementation refers to a vehicle head unit running Android as an operating system for part or all of the system and/or infotainment functionality.

Android device implementations are classified as an Automotive if they declare the feature android.hardware.type.automotive or meet all the following criteria.

• Are embedded as part of, or pluggable to, an automotive vehicle.
• Are using a screen in the driver's seat row as the primary display.

The additional requirements in the rest of this section are specific to Android Automotive device implementations.

2.5.1. Hardware

Automotive device implementations:

• [ 7.1 .1.1/A-0-1] MUST have a screen at least 6 inches in physical diagonal size.

• [ 7.1 .1.1/A-0-2] MUST have a screen size layout of at least 750 dp x 480 dp.

• [ 7.2 .3/A-0-1] MUST provide the Home function and MAY provide Back and Recent functions.

• [ 7.2 .3/A-0-2] MUST send both the normal and long press event of the Back function ( KEYCODE_BACK ) to the foreground application.

• [ 7.3 /A-0-1] MUST implement and report GEAR_SELECTION , NIGHT_MODE , PERF_VEHICLE_SPEED and PARKING_BRAKE_ON .

• [ 7.3 /A-0-2] The value of the NIGHT_MODE flag MUST be consistent with dashboard day/night mode and SHOULD be based on ambient light sensor input. The underlying ambient light sensor MAY be the same as Photometer .

• [ 7.3 /A-0-3] MUST provide sensor additional info field TYPE_SENSOR_PLACEMENT as part of SensorAdditionalInfo for every sensor provided.

• [ 7.3 /A-0-1] MAY dead reckon Location by fusing GPS/GNSS with additional sensors. If Location is dead reckoned, it is STRONGLY RECOMMENDED to implement and report the corresponding Sensor types and/or Vehicle Property IDs used.

• [ 7.3 /A-0-2] The Location requested via LocationManager#requestLocationUpdates() MUST NOT be map matched.

If Automotive device implementations support OpenGL ES 3.1, they:

• [ 7.1 .4.1/A-0-1] MUST declare OpenGL ES 3.1 or higher.
• [ 7.1 .4.1/A-0-2] MUST support Vulkan 1.1.
• [ 7.1 .4.1/A-0-3] MUST include Vulkan loader and export all symbols.

If Automotive device implementations include a 3-axis gyroscope, they:

If Automotive device implementations include a GPS/GNSS receiver, but do not include cellular network-based data connectivity, they:

• [ 7.3 .3/A-3-1] MUST determine location the very first time the GPS/GNSS receiver is turned on or after 4+ days within 60 seconds.
• [ 7.3 .3/A-3-2] MUST meet the time-to-first-fix criteria as described in 7.3.3/C-1-2 and 7.3.3/C-1-6 for all other location requests (ie requests which are not the first time ever or after 4+ days). The requirement 7.3.3/C-1-2 is typically met in vehicles without cellular network-based data connectivity, by using GNSS orbit predictions calculated on the receiver, or using the last known vehicle location along with the ability to dead reckon for at least 60 seconds with a position accuracy satisfying 7.3.3/C-1-3 , or a combination of both.

Automotive device implementations:

• [ 7.4 .3/A-0-1] MUST support Bluetooth and SHOULD support Bluetooth LE.
• [ 7.4 .3/A-0-2] Android Automotive implementations MUST support the following Bluetooth profiles:
  • Phone calling over Hands-Free Profile (HFP).
  • Media playback over Audio Distribution Profile (A2DP).
  • Media playback control over Remote Control Profile (AVRCP).
  • Contact sharing using the Phone Book Access Profile (PBAP).

• [ 7.4 .3/A-SR] Are STRONGLY RECOMMENDED to support Message Access Profile (MAP).

• [ 7.4 .5/A] SHOULD include support for cellular network-based data connectivity.

• [ 7.4 .5/A] MAY use the System API NetworkCapabilities#NET_CAPABILITY_OEM_PAID constant for networks that should be available to system apps.

An exterior view camera is a camera that images scenes outside of the device implementation, like the rearview camera a dashcam .

Automotive device implementations:

• SHOULD include one or more exterior view cameras.

If Automotive device implementations include an exterior view camera, for such a camera, they:

• [ 7.5 /A-1-1] MUST NOT have exterior view cameras accessible via the Android Camera APIs , unless they comply with camera core requirements .

• [ 7.5 /A-SR] Are STRONGLY RECOMMENDED not to rotate or horizontally mirror the camera preview.

• [ 7.5 .5/A-SR] Are STRONGLY RECOMMENDED to be oriented so that the long dimension of the camera aligns with the horizon.

• [ 7.5 /A-SR] Are STRONGLY RECOMMENDED to have a resolution of at least 1.3 megapixels.

• SHOULD have either fixed-focus or EDOF (extended depth of field) hardware.

• SHOULD support Android Synchronization Framework .

• MAY have either hardware auto-focus or software auto-focus implemented in the camera driver.

Automotive device implementations:

• [ 7.6 .1/A-0-1] MUST have at least 4 GB of non-volatile storage available for application private data (aka "/data" partition).

• [ 7.6 .1/A] SHOULD format the data partition to offer improved performance and longevity on flash storage, for example using f2fs file-system.

If Automotive device implementations provide shared external storage via a portion of the internal non-removable storage, they:

• [ 7.6 .1/A-SR] Are STRONGLY RECOMMENDED to reduce I/O overhead on operations performed on the external storage, for example by using SDCardFS .

If Automotive device implementations are 32-bit:

• [ 7.6 .1/A-1-1] The memory available to the kernel and userspace MUST be at least 512MB if any of the following densities are used:

  • 280dpi or lower on small/normal screens
  • ldpi or lower on extra large screens
  • mdpi or lower on large screens

• [ 7.6 .1/A-1-2] The memory available to the kernel and userspace MUST be at least 608MB if any of the following densities are used:

  • xhdpi or higher on small/normal screens
  • hdpi or higher on large screens
  • mdpi or higher on extra large screens

• [ 7.6 .1/A-1-3] The memory available to the kernel and userspace MUST be at least 896MB if any of the following densities are used:

  • 400dpi or higher on small/normal screens
  • xhdpi or higher on large screens
  • tvdpi or higher on extra large screens

• [ 7.6 .1/A-1-4] The memory available to the kernel and userspace MUST be at least 1344MB if any of the following densities are used:

  • 560dpi or higher on small/normal screens
  • 400dpi or higher on large screens
  • xhdpi or higher on extra large screens

If Automotive device implementations are 64-bit:

• [ 7.6 .1/A-2-1] The memory available to the kernel and userspace MUST be at least 816MB if any of the following densities are used:

  • 280dpi or lower on small/normal screens
  • ldpi or lower on extra large screens
  • mdpi or lower on large screens

• [ 7.6 .1/A-2-2] The memory available to the kernel and userspace MUST be at least 944MB if any of the following densities are used:

  • xhdpi or higher on small/normal screens
  • hdpi or higher on large screens
  • mdpi or higher on extra large screens

• [ 7.6 .1/A-2-3] The memory available to the kernel and userspace MUST be at least 1280MB if any of the following densities are used:

  • 400dpi or higher on small/normal screens
  • xhdpi or higher on large screens
  • tvdpi or higher on extra large screens

• [ 7.6 .1/A-2-4] The memory available to the kernel and userspace MUST be at least 1824MB if any of the following densities are used:

  • 560dpi or higher on small/normal screens
  • 400dpi or higher on large screens
  • xhdpi or higher on extra large screens

Note that the "memory available to the kernel and userspace" above refers to the memory space provided in addition to any memory already dedicated to hardware components such as radio, video, and so on that are not under the kernel's control on device implementations.

Automotive device implementations:

• [ 7.7 .1/A] SHOULD include a USB port supporting peripheral mode.

Automotive device implementations:

• [ 7.8 .1/A-0-1] MUST include a microphone.

Automotive device implementations:

• [ 7.8 .2/A-0-1] MUST have an audio output and declare android.hardware.audio.output .

2.5.2. Multimedia

Automotive device implementations MUST support the following audio encoding and decoding formats and make them available to third-party applications:

• [ 5.1 /A-0-1] MPEG-4 AAC Profile (AAC LC)
• [ 5.1 /A-0-2] MPEG-4 HE AAC Profile (AAC+)
• [ 5.1 /A-0-3] AAC ELD (enhanced low delay AAC)

Automotive device implementations MUST support the following video encoding formats and make them available to third-party applications:

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

Automotive device implementations MUST support the following video decoding formats and make them available to third-party applications:

• [ 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] VP9

Automotive device implementations are STRONGLY RECOMMENDED to support the following video decoding:

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

2.5.3. Software

Automotive device implementations:

• [ 3 /A-0-1] MUST declare the feature android.hardware.type.automotive .

• [ 3 /A-0-2] MUST support uiMode = UI_MODE_TYPE_CAR .

• [ 3 /A-0-3] MUST support all public APIs in the android.car.* namespace.

If Automotive device implementations provide a proprietary API using android.car.CarPropertyManager with android.car.VehiclePropertyIds , they:

• [ 3 /A-1-1] MUST NOT attach special privileges to system application's use of these properties, or prevent third-party applications from using these properties.
• [ 3 /A-1-2] MUST NOT replicate a vehicle property that already exists in the SDK .

Automotive device implementations:

• [ 3.2 .1/A-0-1] MUST support and enforce all permissions constants as documented by the Automotive Permission reference page .

• [ 3.2.3.1 /A-0-1] MUST preload one or more applications or service components with an intent handler, for all the public intent filter patterns defined by the following application intents listed here .

• [ 3.4 .1/A-0-1] MUST provide a complete implementation of the android.webkit.Webview API.

• [ 3.8 .3/A-0-1] MUST display notifications that use the Notification.CarExtender API when requested by third-party applications.

• [ 3.8 .4/A-SR] Are Strongly Recommended to implement an assistant on the device to handle the Assist action .

If Automotive device implementations include a push-to-talk button, they:

• [ 3.8 .4/A-1-1] MUST use a short press of the push-to-talk button as the designated interaction to launch the user-selected assist app, in other words the app that implements VoiceInteractionService .

Automotive device implementations:

• [ 3.8.3.1 /A-0-1] MUST correctly render resources as described in the Notifications on Automotive OS SDK documentation.
• [ 3.8.3.1 /A-0-2] MUST display PLAY and MUTE for notification actions in the place of those provided through Notification.Builder.addAction()
• [ 3.8.3.1 /A] SHOULD restrict the use of rich management tasks such as per-notification-channel controls. MAY use UI affordance per application to reduce controls.

If Automotive device implementations support User HAL properties, they:

• [ 3.9.3 /A-1-1] MUST implement all of the User lifecycle properties
  • INITIAL_USER_INFO , SWITCH_USER , CREATE_USER , REMOVE_USER .

Automotive device implementations:

• [ 3.14 /A-0-1] MUST include a UI framework to support third-party apps using the media APIs as described in section 3.14 .
• [ 3.14 /A-0-2] MUST allow the user to safely interact with Media Applications while driving.
• [ 3.14 /A-0-3] MUST support the CAR_INTENT_ACTION_MEDIA_TEMPLATE implicit Intent action with the CAR_EXTRA_MEDIA_PACKAGE extra.
• [ 3.14 /A-0-4] MUST provide an affordance to navigate into a Media Application's preference activity , but MUST only enable it when Car UX Restrictions are not in effect.
• [ 3.14 /A-0-5] MUST display error messages set by Media Applications, and MUST support the optional extras ERROR_RESOLUTION_ACTION_LABEL and ERROR_RESOLUTION_ACTION_INTENT .
• [ 3.14 /A-0-6] MUST support an in-app search affordance for apps that support searching.
• [ 3.14 /A-0-7] MUST respect CONTENT_STYLE_BROWSABLE_HINT and CONTENT_STYLE_PLAYABLE_HINT definitions when displaying the MediaBrowser hierarchy.

If Automotive device implementations include a default launcher app, they:

• [ 3.14 /A-1-1] MUST include media services and open them with the CAR_INTENT_ACTION_MEDIA_TEMPLATE intent.

Automotive device implementations:

• [ 3.8 /A] MAY restrict the application requests to enter a full screen mode as described in immersive documentation .
• [ 3.8 /A] MAY keep the status bar and the navigation bar visible at all times.
• [ 3.8 /A] MAY restrict the application requests to change the colors behind the system UI elements, to ensure those elements are clearly visible at all times.

2.5.4. Performance and Power

Automotive device implementations:

• [ 8.2 /A-0-1] MUST report the number of bytes read and written to non-volatile storage per each process's UID so the stats are available to developers through System API android.car.storagemonitoring.CarStorageMonitoringManager . The Android Open Source Project meets the requirement through the uid_sys_stats kernel module.
• [ 8.3 /A-1-3] MUST support Garage Mode .
• [ 8.3 /A] SHOULD be in Garage Mode for at least 15 minutes after every drive unless:
  • The battery is drained.
  • No idle jobs are scheduled.
  • The driver exits Garage Mode.
• [ 8.4 /A-0-1] MUST 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.
• [ 8.4 /A-0-2] MUST report all power consumption values in milliampere hours (mAh).
• [ 8.4 /A-0-3] MUST report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the uid_cputime kernel module implementation.
• [ 8.4 /A] SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application.
• [ 8.4 /A-0-4] MUST make this power usage available via the adb shell dumpsys batterystats shell command to the app developer.

2.5.5. Security Model

If Automotive device implementations support multiple users, they:

• [ 9.5 /A-1-1] MUST NOT allow users to interact with nor switch into the Headless System User , except for device provisioning .
• [ 9.5 /A-1-2] MUST switch into a Secondary User before BOOT_COMPLETED .
• [ 9.5 /A-1-3] MUST support the ability to create a Guest User even when the maximum number of Users on a device has been reached.

Automotive device implementations:

• [ 9.11 /A-0-1] MUST back up the keystore implementation with an isolated execution environment.
• [ 9.11 /A-0-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. Secure isolation MUST block all potential mechanisms by which kernel or userspace code might access the internal state of the isolated environment, including DMA. The upstream Android Open Source Project (AOSP) meets this requirement by using the Trusty implementation, but another ARM TrustZone-based solution or a third-party reviewed secure implementation of a proper hypervisor-based isolation are alternative options.
• [ 9.11 /A-0-3] MUST perform the lock screen authentication in the isolated execution environment and only when successful, allow the authentication-bound keys to be used. Lock screen credentials MUST be stored in a way that allows only the isolated execution environment to perform lock screen authentication. The upstream Android Open Source Project provides the Gatekeeper Hardware Abstraction Layer (HAL) and Trusty, which can be used to satisfy this requirement.
• [ 9.11 /A-0-4] MUST support key attestation where the attestation signing key is protected by secure hardware and signing is performed in secure hardware. The attestation signing keys MUST be shared across large enough number of devices to prevent the keys from being used as device identifiers. One way of meeting this requirement is to share the same attestation key unless at least 100,000 units of a given SKU are produced. If more than 100,000 units of an SKU are produced, a different key MAY be used for each 100,000 units.
• [9/A-0-1] MUST declare the 'android.hardware.security.model.compatible' feature.

Note that if a device implementation is already launched on an earlier Android version, such a device is exempted from the requirement to have a keystore backed by an isolated execution environment and support the key attestation, unless it declares the android.hardware.fingerprint feature which requires a keystore backed by an isolated execution environment.

Automotive device implementations:

• [ 9.14 /A-0-1] MUST gatekeep messages from Android framework vehicle subsystems, eg, whitelisting permitted message types and message sources.
• [ 9.14 /A-0-2] MUST watchdog against denial of service attacks from the Android framework or third-party apps. This guards against malicious software flooding the vehicle network with traffic, which may lead to malfunctioning vehicle subsystems.

2.5.6. Developer Tools and Options Compatibility

Automotive device implementations:

• Perfetto
  • [ 6.1 /A-0-1] MUST expose a /system/bin/perfetto binary to the shell user which cmdline complies with the perfetto documentation .
  • [ 6.1 /A-0-2] The perfetto binary MUST accept as input a protobuf config that complies with the schema defined in the perfetto documentation .
  • [ 6.1 /A-0-3] The perfetto binary MUST write as output a protobuf trace that complies with the schema defined in the perfetto documentation .
  • [ 6.1 /A-0-4] MUST provide, through the perfetto binary, at least the data sources described in the perfetto documentation .

2.6. Tablet Requirements

An Android Tablet device refers to an Android device implementation that typically meets all the following criteria:

• Used by holding in both hands.
• Does not have a clamshell or convertible configuration.
• Physical keyboard implementations used with the device connect by means of a standard connection (eg USB, Bluetooth).
• Has a power source that provides mobility, such as a battery.

Tablet device implementations have similar requirements to handheld device implementations. The exceptions are indicated by an * in that section and noted for reference in this section.

2.6.1. Hardware

Gyroscope

If Tablet device implementations include a 3-axis gyroscope, they:

• [ 7.3 .4/Tab-1-1] MUST be capable of measuring orientation changes up to 1000 degrees per second.

Minimum Memory and Storage (Section 7.6.1)

The screen densities listed for small/normal screens in the handheld requirements are not applicable to tablets.

USB peripheral mode (Section 7.7.1)

If tablet device implementations include a USB port supporting peripheral mode, they:

• [ 7.7.1 /Tab] MAY implement the Android Open Accessory (AOA) API.

Virtual Reality Mode (Section 7.9.1)

Virtual Reality High Performance (Section 7.9.2)

Virtual reality requirements are not applicable to tablets.

2.6.2. Security Model

Keys and Credentials (Section 9.11)

Refer to Section [ 9.11 ].

If Tablet device implementations include multiple users and do not declare the android.hardware.telephony feature flag, they:

• [ 9.5 /T-1-1] MUST support restricted profiles, a feature that allows device owners to manage additional users and their capabilities on the device. With restricted profiles, device owners can quickly set up separate environments for additional users to work in, with the ability to manage finer-grained restrictions in the apps that are available in those environments.

If Tablet device implementations include multiple users and declare the android.hardware.telephony feature flag, they:

• [ 9.5 /T-2-1] MUST NOT support restricted profiles but MUST align with the AOSP implementation of controls to enable /disable other users from accessing the voice calls and SMS.

2.6.2. Software

• [ 3.2.3.1 /Tab-0-1] MUST preload one or more applications or service components with an intent handler, for all the public intent filter patterns defined by the following application intents listed here .

3. Software

3.1. Managed API Compatibility

The managed Dalvik bytecode execution environment is the primary vehicle for Android applications. The Android application programming interface (API) is the set of Android platform interfaces exposed to applications running in the managed runtime environment.

Device implementations:

• [C-0-1] MUST provide complete implementations, including all documented behaviors, of any documented API exposed by the Android SDK or any API decorated with the “@SystemApi” marker in the upstream Android source code.

• [C-0-2] MUST support/preserve all classes, methods, and associated elements marked by the TestApi annotation (@TestApi).

• [C-0-3] MUST NOT omit any managed APIs, alter API interfaces or signatures, deviate from the documented behavior, or include no-ops, except where specifically allowed by this Compatibility Definition.

• [C-0-4] MUST still keep the APIs present and behave in a reasonable way, even when some hardware features for which Android includes APIs are omitted. See section 7 for specific requirements for this scenario.

• [C-0-5] MUST NOT allow third-party apps to use non-SDK interfaces, which are defined as methods and fields in the Java language packages that are in the boot classpath in AOSP, and that do not form part of the public SDK. This includes APIs decorated with the @hide annotation but not with a @SystemAPI , as described in the SDK documents and private and package-private class members.

• [C-0-6] MUST ship with each and every non-SDK interface on the same restricted lists as provided via the greylist , greylist-max-o , greylist-max-p , and blacklist flags in prebuilts/runtime/appcompat/hiddenapi-flags.csv path for the appropriate API level branch in the AOSP.

• [C-0-7] MUST support the signed config dynamic update mechanism to remove non-SDK interfaces from a restricted list by embedding signed configuration in any APK, using the existing public keys present in AOSP.

  However they:

  • MAY, if a hidden API is absent or implemented differently on the device implementation, move the hidden API into the blacklist or omit it from all restricted lists (ie light-grey, dark-grey, black).
  • MAY, if a hidden API does not already exist in the AOSP, add the hidden API to any of the restricted lists (ie light-grey, dark-grey, black).

3.1.1. Android Extensions

Android supports extending the managed API surface of a particular API level by updating the extension version for that API level. The android.os.ext.SdkExtensions.getExtensionVersion(int apiLevel) API returns the extension version of the provided apiLevel , if there are extensions for that API level.

Android device implementations:

• [C-0-1] MUST preload the AOSP implementation of both the shared library ExtShared and services ExtServices with versions greater than or equal to the minimum versions allowed per each API level. For example, Android 7.0 device implementations, running API level 24 MUST include at least version 1.

• [C-0-2] MUST only return valid extension version number that have been defined by the AOSP.

• [C-0-3] MUST support all the APIs defined by the extension versions returned by android.os.ext.SdkExtensions.getExtensionVersion(int apiLevel) in the same manner as other managed APIs are supported, following the requirements in section 3.1 .

3.1.2. Android Library

Due to Apache HTTP client deprecation , device implementations:

• [C-0-1] MUST NOT place the org.apache.http.legacy library in the bootclasspath.
• [C-0-2] MUST add the org.apache.http.legacy library to the application classpath only when the app satisfies one of the following conditions:
  • Targets API level 28 or lower.
  • Declares in its manifest that it needs the library by setting the android:name attribute of <uses-library> to org.apache.http.legacy .

The AOSP implementation meets these requirements.

3.2. Soft API Compatibility

In addition to the managed APIs from section 3.1 , Android also includes a significant runtime-only “soft” API, in the form of such things as intents, permissions, and similar aspects of Android applications that cannot be enforced at application compile time.

3.2.1. Permissions

• [C-0-1] Device implementers MUST support and enforce all permission constants as documented by the Permission reference page . Note that section 9 lists additional requirements related to the Android security model.

3.2.2. Build Parameters

The Android APIs include a number of constants on the android.os.Build class that are intended to describe the current device.

• [C-0-1] To provide consistent, meaningful values across device implementations, the table below includes additional restrictions on the formats of these values to which device implementations MUST conform.

3.2.3. Intent Compatibility

3.2.3.1. Common Application Intents

Android intents allow application components to request functionality from other Android components. The Android upstream project includes a list of applications which implement several intent patterns to perform common actions.

Device implementations:

• [C-SR] Are STRONGLY RECOMMENDED to preload one or more applications or service components with an intent handler, for all the public intent filter patterns defined by the following application intents listed here and provide fulfillment ie meet with the developer expectation for these common application intents as described in the SDK.

Please refer to Section 2 for mandatory application intents for each device type.

3.2.3.2. Intent Resolution

• [C-0-1] As Android is an extensible platform, device implementations MUST allow each intent pattern referenced in section 3.2.3.1 , except for Settings, to be overridden by third-party applications. The upstream Android open source implementation allows this by default.

• [C-0-2] Device implementers MUST NOT attach special privileges to system applications' use of these intent patterns, or prevent third-party applications from binding to and assuming control of these patterns. This prohibition specifically includes but is not limited to disabling the “Chooser” user interface that allows the user to select between multiple applications that all handle the same intent pattern.

• [C-0-3] Device implementations MUST provide a user interface for users to modify the default activity for intents.

• However, device implementations MAY provide default activities for specific URI patterns (eg http://play.google.com) when the default activity provides a more specific attribute for the data URI. For example, an intent filter pattern specifying the data URI “http://www.android.com” is more specific than the browser's core intent pattern for “http://”.

Android also includes a mechanism for third-party apps to declare an authoritative default app linking behavior for certain types of web URI intents. When such authoritative declarations are defined in an app's intent filter patterns, device implementations:

• [C-0-4] MUST attempt to validate any intent filters by performing the validation steps defined in the Digital Asset Links specification as implemented by the Package Manager in the upstream Android Open Source Project.
• [C-0-5] MUST attempt validation of the intent filters during the installation of the application and set all successfully validated URI intent filters as default app handlers for their URIs.
• MAY set specific URI intent filters as default app handlers for their URIs, if they are successfully verified but other candidate URI filters fail verification. If a device implementation does this, it MUST provide the user appropriate per-URI pattern overrides in the settings menu.
• MUST provide the user with per-app App Links controls in Settings as follows:
  • [C-0-6] The user MUST be able to override holistically the default app links behavior for an app to be: always open, always ask, or never open, which must apply to all candidate URI intent filters equally.
  • [C-0-7] The user MUST be able to see a list of the candidate URI intent filters.
  • The device implementation MAY provide the user with the ability to override specific candidate URI intent filters that were successfully verified, on a per-intent filter basis.
  • [C-0-8] The device implementation MUST provide users with the ability to view and override specific candidate URI intent filters if the device implementation lets some candidate URI intent filters succeed verification while some others can fail.

3.2.3.3. Intent Namespaces

• [C-0-1] Device implementations MUST NOT include any Android component that honors any new intent or broadcast intent patterns using an ACTION, CATEGORY, or other key string in the android.* or com.android.* namespace.
• [C-0-2] Device implementers MUST NOT include any Android components that honor any new intent or broadcast intent patterns using an ACTION, CATEGORY, or other key string in a package space belonging to another organization.
• [C-0-3] Device implementers MUST NOT alter or extend any of the intent patterns listed in section 3.2.3.1 .
• Device implementations MAY include intent patterns using namespaces clearly and obviously associated with their own organization. This prohibition is analogous to that specified for Java language classes in section 3.6 .

3.2.3.4. Broadcast Intents

Third-party applications rely on the platform to broadcast certain intents to notify them of changes in the hardware or software environment.

Device implementations:

• [C-0-1] MUST broadcast the public broadcast intents listed here in response to appropriate system events as described in the SDK documentation. Note that this requirement is not conflicting with section 3.5 as the limitation for background applications are also described in the SDK documentation. Also certain broadcast intents are conditional upon hardware support, if the device supports the necessary hardware they MUST broadcast the intents and provide the behavior inline with SDK documentation.

3.2.3.5. Conditional Application Intents

Android includes settings that provide users an easy way to select their default applications, for example for Home screen or SMS.

Where it makes sense, device implementations MUST provide a similar settings menu and be compatible with the intent filter pattern and API methods described in the SDK documentation as below.

If device implementations report android.software.home_screen , they:

• [C-1-1] MUST honor the android.settings.HOME_SETTINGS intent to show a default app settings menu for Home Screen.

If device implementations report android.hardware.telephony , they:

• [C-2-1] MUST provide a settings menu that will call the android.provider.Telephony.ACTION_CHANGE_DEFAULT intent to show a dialog to change the default SMS application.

• [C-2-2] MUST honor the android.telecom.action.CHANGE_DEFAULT_DIALER intent to show a dialog to allow the user to change the default Phone application.

  • MUST use the user-selected default Phone app's UI for incoming and outgoing calls except for emergency calls, which would use the preinstalled Phone app.

• [C-2-3] MUST honor the android.telecom.action.CHANGE_PHONE_ACCOUNTS intent to provide user affordance to configure the ConnectionServices associated with the PhoneAccounts , as well as a default PhoneAccount that the telecommunications service provider will use to place outgoing calls. The AOSP implementation meets this requirement by including a "Calling Accounts option" menu within the "Calls" settings menu.

• [C-2-4] MUST allow android.telecom.CallRedirectionService for an app that holds the android.app.role.CALL_REDIRECTION role.

• [C-2-5] MUST provide the user affordance to choose an app that holds the android.app.role.CALL_REDIRECTION role.

• [C-2-6] MUST honor the android.intent.action.SENDTO and android.intent.action.VIEW intents and provide an activity to send/display SMS messages.

• [C-SR] Are Strongly Recommended to honor android.intent.action.ANSWER , android.intent.action.CALL , android.intent.action.CALL_BUTTON , android.intent.action.VIEW & android.intent.action.DIAL intents with a preloaded dialer application which can handle these intents and provide fulfillment as described in the SDK.

If device implementations report android.hardware.nfc.hce , they:

• [C-3-1] MUST honor the android.settings.NFC_PAYMENT_SETTINGS intent to show a default app settings menu for Contactless payment.
• [C-3-2] MUST honor android.nfc.cardemulation.action.ACTION_CHANGE_DEFAULT intent to show an activity which opens a dialog to ask the user to change the default card emulation service for a certain category as described in the SDK.

If device implementations report android.hardware.nfc , they:

• [C-4-1] MUST honor these intents android.nfc.action.NDEF_DISCOVERED , android.nfc.action.TAG_DISCOVERED & android.nfc.action.TECH_DISCOVERED , to show an activity which fulfils developer expectations for these intents as described in the SDK.

If device implementations support the VoiceInteractionService and have more than one application using this API installed at a time, they:

• [C-4-1] MUST honor the android.settings.ACTION_VOICE_INPUT_SETTINGS intent to show a default app settings menu for voice input and assist.

If device implementations report android.hardware.bluetooth , they:

• [C-5-1] MUST honor the 'android.bluetooth.adapter.action.REQUEST_ENABLE' intent and show a system activity to allow the user to turn on Bluetooth.
• [C-5-2] MUST honor the 'android.bluetooth.adapter.action.REQUEST_DISCOVERABLE' intent and show a system activity that requests discoverable mode.

If device implementations support the DND feature, they:

• [C-6-1] MUST implement an activity that would respond to the intent ACTION_NOTIFICATION_POLICY_ACCESS_SETTINGS , which for implementations with UI_MODE_TYPE_NORMAL it MUST be an activity where the user can grant or deny the app access to DND policy configurations.

If device implementations allow users to use third-party input methods on the device, they:

• [C-7-1] MUST provide a user-accessible mechanism to add and configure third-party input methods in response to the android.settings.INPUT_METHOD_SETTINGS intent.

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

• [C-8-1] 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 preloaded accessibility services.

If device implementations include support for Wi-Fi Easy Connect and expose the functionality to third-party apps, they:

• [C-9-1] MUST implement the Settings#ACTION_PROCESS_WIFI_EASY_CONNECT_URI Intent APIs as described in the SDK documentation.

If device implementations provide the data saver mode, they: * [C-10-1] 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 allow list.

If device implementations do not provide the data saver mode, they:

• [C-11-1] MUST have an activity that handles the Settings.ACTION_IGNORE_BACKGROUND_DATA_RESTRICTIONS_SETTINGS intent but MAY implement it as a no-op.

If device implementations declare support for the camera via android.hardware.camera.any , they:

• [C-12-3] MUST handle and MUST only allow preinstalled Android applications to handle the following intents MediaStore.ACTION_IMAGE_CAPTURE , MediaStore.ACTION_IMAGE_CAPTURE_SECURE , and MediaStore.ACTION_VIDEO_CAPTURE as described in the SDK document .

If device implementations report android.software.device_admin , they:

• [C-13-1] MUST honor the intent android.app.action.ADD_DEVICE_ADMIN to invoke a UI to bring the user through adding the device administrator to the system (or allowing them to reject it).

• [C-13-2] MUST honor the intents android.app.action.PROVISION_MANAGED_PROFILE , android.app.action.SET_NEW_PARENT_PROFILE_PASSWORD , android.app.action.SET_NEW_PASSWORD & android.app.action.START_ENCRYPTION and have an activity to provide fulfillment for these intents as described in SDK here .

If device implementations declare the android.software.autofill feature flag, they:

• [C-14-1] MUST fully implement the AutofillService and AutofillManager APIs and honor the android.settings.REQUEST_SET_AUTOFILL_SERVICE intent to show a default app settings menu to enable and disable autofill and change the default autofill service for the user.

If device implementations include a pre-installed app or wish to allow third-party apps to access the usage statistics, they:

• [C-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-15-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.

If device implementations surface links to the activities specified by AutofillService_passwordsActivity in Settings or links to user passwords through a similar mechanism, they:

• [C-16-1] MUST surface such links for all installed autofill services.

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

• [C-SR] Are Strongly Recommended to honor android.intent.action.TTS_SERVICE, android.speech.tts.engine.INSTALL_TTS_DATA & android.speech.tts.engine.GET_SAMPLE_TEXT intents have an activity to provide fulfillment for these intents as described in SDK here .

Android includes support for interactive screensavers, previously referred to as Dreams. Screen Savers allow users to interact with applications when a device connected to a power source is idle or docked in a desk dock. Device Implementations:

• SHOULD include support for screen savers and provide a settings option for users to configure screen savers in response to the android.settings.DREAM_SETTINGS intent.

3.2.4. Activities on secondary/multiple displays

If device implementations allow launching normal Android Activities on more than one display, they:

• [C-1-1] MUST set the android.software.activities_on_secondary_displays feature flag.
• [C-1-2] MUST guarantee API compatibility similar to an activity running on the primary display.
• [C-1-3] MUST land the new activity on the same display as the activity that launched it, when the new activity is launched without specifying a target display via the ActivityOptions.setLaunchDisplayId() API.
• [C-1-4] MUST destroy all activities, when a display with the Display.FLAG_PRIVATE flag is removed.
• [C-1-5] MUST securely hide content on all screens when the device is locked with a secure lock screen, unless the app opts in to show on top of lock screen using Activity#setShowWhenLocked() API.
• SHOULD have android.content.res.Configuration which corresponds to that display in order to be displayed, operate correctly, and maintain compatibility if an activity is launched on secondary display.

If device implementations allow launching normal Android Activities on secondary displays and a secondary display has the android.view.Display.FLAG_PRIVATE flag:

• [C-3-1] Only the owner of that display, system, and activities that are already on that display MUST be able to launch to it. Everyone can launch to a display that has android.view.Display.FLAG_PUBLIC flag.

3.3. Native API Compatibility

Native code compatibility is challenging. For this reason, device implementers are:

• [SR] STRONGLY RECOMMENDED to use the implementations of the libraries listed below from the upstream Android Open Source Project.

3.3.1. Application Binary Interfaces

Managed Dalvik bytecode can call into native code provided in the application .apk file as an ELF .so file compiled for the appropriate device hardware architecture. As native code is highly dependent on the underlying processor technology, Android defines a number of Application Binary Interfaces (ABIs) in the Android NDK.

Device implementations:

• [C-0-1] MUST be compatible with one or more defined Android NDK ABIs .
• [C-0-2] MUST include support for code running in the managed environment to call into native code, using the standard Java Native Interface (JNI) semantics.
• [C-0-3] MUST be source-compatible (ie header-compatible) and binary-compatible (for the ABI) with each required library in the list below.
• [C-0-5] MUST accurately report the native Application Binary Interface (ABI) supported by the device, via the android.os.Build.SUPPORTED_ABIS , android.os.Build.SUPPORTED_32_BIT_ABIS , and android.os.Build.SUPPORTED_64_BIT_ABIS parameters, each a comma separated list of ABIs ordered from the most to the least preferred one.

• [C-0-6] MUST report, via the above parameters, a subset of the following list of ABIs and MUST NOT report any ABI not on the list.

  • armeabi (no longer supported as a target by the NDK)
  • armeabi-v7a
  • arm64-v8a
  • x86
  • x86-64

• [C-0-7] MUST make all the following libraries, providing native APIs, available to apps that include native code:

  • libaaudio.so (AAudio native audio support)
  • libamidi.so (native MIDI support, if feature android.software.midi is claimed as described in Section 5.9)
  • libandroid.so (native Android activity support)
  • libc (C library)
  • libcamera2ndk.so
  • libdl (dynamic linker)
  • libEGL.so (native OpenGL surface management)
  • libGLESv1_CM.so (OpenGL ES 1.x)
  • libGLESv2.so (OpenGL ES 2.0)
  • libGLESv3.so (OpenGL ES 3.x)
  • libicui18n.so
  • libicuuc.so
  • libjnigraphics.so
  • liblog (Android logging)
  • libmediandk.so (native media APIs support)
  • libm (math library)
  • libneuralnetworks.so (Neural Networks API)
  • libOpenMAXAL.so (OpenMAX AL 1.0.1 support)
  • libOpenSLES.so (OpenSL ES 1.0.1 audio support)
  • libRS.so
  • libstdc++ (Minimal support for C++)
  • libvulkan.so (Vulkan)
  • libz (Zlib compression)
  • JNI interface

• [C-0-8] MUST NOT add or remove the public functions for the native libraries listed above.

• [C-0-9] MUST list additional non-AOSP libraries exposed directly to third-party apps in /vendor/etc/public.libraries.txt .

• [C-0-10] MUST NOT expose any other native libraries, implemented and provided in AOSP as system libraries, to third-party apps targeting API level 24 or higher as they are reserved.

• [C-0-11] MUST export all the OpenGL ES 3.1 and Android Extension Pack function symbols, as defined in the NDK, through the libGLESv3.so library. Note that while all the symbols MUST be present, section 7.1.4.1 describes in more detail the requirements for when the full implementation of each corresponding functions are expected.

• [C-0-12] MUST export function symbols for the core Vulkan 1.0 function symbols, as well as the VK_KHR_surface , VK_KHR_android_surface , VK_KHR_swapchain , VK_KHR_maintenance1 , and VK_KHR_get_physical_device_properties2 extensions through the libvulkan.so library. Note that while all the symbols MUST be present, section 7.1.4.2 describes in more detail the requirements for when the full implementation of each corresponding functions are expected.

• SHOULD be built using the source code and header files available in the upstream Android Open Source Project

Note that future releases of Android may introduce support for additional ABIs.

3.3.2. 32-bit ARM Native Code Compatibility

If device implementations report the support of the armeabi ABI, they:

• [C-3-1] MUST also support armeabi-v7a and report its support, as armeabi is only for backwards compatibility with older apps.

If device implementations report the support of the armeabi-v7a ABI, for apps using this ABI, they:

• [C-2-1] MUST include the following lines in /proc/cpuinfo , and SHOULD NOT alter the values on the same device, even when they are read by other ABIs.

  • Features: , followed by a list of any optional ARMv7 CPU features supported by the device.
  • CPU architecture: , followed by an integer describing the device's highest supported ARM architecture (eg, "8" for ARMv8 devices).

• [C-2-2] MUST always keep the following operations available, even in the case where the ABI is implemented on an ARMv8 architecture, either through native CPU support or through software emulation:

  • SWP and SWPB instructions.
  • CP15ISB, CP15DSB, and CP15DMB barrier operations.

• [C-2-3] MUST include support for the Advanced SIMD (aka NEON) extension.

3.4. Web Compatibility

3.4.1. WebView Compatibility

If device implementations provide a complete implementation of the android.webkit.Webview API, they:

• [C-1-1] MUST report android.software.webview .
• [C-1-2] MUST use the Chromium Project build from the upstream Android Open Source Project on the Android 13 branch for the implementation of the android.webkit.WebView API.

• [C-1-3] The user agent string reported by the WebView MUST be in this format:

  Mozilla/5.0 (Linux; Android $(VERSION); [$(MODEL)] [Build/$(BUILD)]; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 $(CHROMIUM_VER) Mobile Safari/537.36

  • The value of the $(VERSION) string MUST be the same as the value for android.os.Build.VERSION.RELEASE.
  • The $(MODEL) string MAY be empty, but if it is not empty it MUST have the same value as android.os.Build.MODEL.
  • "Build/$(BUILD)" MAY be omitted, but if it is present the $(BUILD) string MUST be the same as the value for android.os.Build.ID.
  • The value of the $(CHROMIUM_VER) string MUST be the version of Chromium in the upstream Android Open Source Project.
  • Device implementations MAY omit Mobile in the user agent string.

• The WebView component SHOULD include support for as many HTML5 features as possible and if it supports the feature SHOULD conform to the HTML5 specification .

• [C-1-3] MUST render the provided content or remote URL content in a process that is distinct from the application that instantiates the WebView. Specifically the separate renderer process MUST hold lower privilege, run as a separate user ID, have no access to the app's data directory, have no direct network access, and only have access to the minimum-required system services over Binder. The AOSP implementation of WebView meets this requirement.

Note that if device implementations are 32-bit or declare the feature flag android.hardware.ram.low , they are exempted from C-1-3.

3.4.2. Browser Compatibility

If device implementations include a standalone Browser application for general web browsing, they:

• [C-1-1] MUST support each of these APIs associated with HTML5:
  • application cache/offline operation
  • <video> tag
  • geolocation
• [C-1-2] MUST support the HTML5/W3C webstorage API and SHOULD support the HTML5/W3C IndexedDB API . Note that as the web development standards bodies are transitioning to favor IndexedDB over webstorage, IndexedDB is expected to become a required component in a future version of Android.
• MAY ship a custom user agent string in the standalone Browser application.
• SHOULD implement support for as much of HTML5 as possible on the standalone Browser application (whether based on the upstream WebKit Browser application or a third-party replacement).

However, If device implementations do not include a standalone Browser application, they:

• [C-2-1] MUST still support the public intent patterns as described in section 3.2.3.1 .

3.5. API Behavioral Compatibility

Device implementations:

• [C-0-9] MUST ensure that API behavioral compatibility is applied for all installed apps unless they are restricted as described in Section 3.5.1 .
• [C-0-10] MUST NOT implement the whitelisting approach that ensures API behavioral compatibility only for apps that are selected by device implementers.

The behaviors of each of the API types (managed, soft, native, and web) must be consistent with the preferred implementation of the upstream Android Open Source Project . Some specific areas of compatibility are:

• [C-0-1] Devices MUST NOT change the behavior or semantics of a standard intent.
• [C-0-2] Devices MUST NOT alter the lifecycle or lifecycle semantics of a particular type of system component (such as Service, Activity, ContentProvider, etc.).
• [C-0-3] Devices MUST NOT change the semantics of a standard permission.
• Devices MUST NOT alter the limitations enforced on background applications. More specifically, for background apps:
  • [C-0-4] they MUST stop executing callbacks that are registered by the app to receive outputs from the GnssMeasurement and GnssNavigationMessage .
  • [C-0-5] they MUST rate-limit the frequency of updates that are provided to the app through the LocationManager API class or the WifiManager.startScan() method.
  • [C-0-6] if the app is targeting API level 25 or higher, they MUST NOT allow to register broadcast receivers for the implicit broadcasts of standard Android intents in the app's manifest, unless the broadcast intent requires a "signature" or "signatureOrSystem" protectionLevel permission or are on the exemption list .
  • [C-0-7] if the app is targeting API level 25 or higher, they MUST stop the app's background services, just as if the app had called the services' stopSelf() method, unless the app is placed on a temporary whitelist to handle a task that's visible to the user.
  • [C-0-8] if the app is targeting API level 25 or higher, they MUST release the wakelocks the app holds.
• [C-0-9] Devices MUST return the following security providers as the first seven array values from the Security.getProviders() method, in the given order and with the given names (as returned by Provider.getName() ) and classes, unless the app has modified the list via insertProviderAt() or removeProvider() . Devices MAY return additional providers after the specified list of providers below.
  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

The above list is not comprehensive. The Compatibility Test Suite (CTS) tests significant portions of the platform for behavioral compatibility, but not all. It is the responsibility of the implementer to ensure behavioral compatibility with the Android Open Source Project. For this reason, device implementers SHOULD use the source code available via the Android Open Source Project where possible, rather than re-implement significant parts of the system.

3.5.1. Application Restriction

If device implementations implement a proprietary mechanism to restrict apps (eg changing or restricting API behaviors that are described in the SDK) and that mechanism is more restrictive than the Restricted App Standby Bucket , they:

If device implementations extend the app restrictions that are implemented in AOSP, they:

• [C-2-1]MUST follow the implementation described in this document .

3.5.2. Application Hibernation

If device implementations include App Hibernation that is included in AOSP or extends the feature that is included in AOSP, then they:

• [C-1-1] MUST meet all the requirements in section 3.5.1 except for [C-1-6] and [C-1-3].
• [C-1-2] MUST only apply the restriction on the app for a user when there is evidence that the user has not used the app for some period of time. This duration is STRONGLY RECOMMENDED to be one month or longer. Usage MUST be defined by either explicit user interaction via the [UsageStats#getLastTimeVisible()]( https://developer.android.com/reference/android/app/usage/UsageStats#getLastTimeVisible()) API or anything that would cause an app to leave the force-stopped state, including service bindings, content provider bindings, explicit broadcasts, etc., which will be tracked by a new API UsageStats#getLastTimeAnyComponentUsed().
• [C-1-3] MUST only apply restrictions affecting all device users when there is evidence that the package has not been used by ANY user for some period of time. This duration is STRONGLY RECOMMENDED to be one month or longer.
• [C-1-4] MUST NOT render the app unable to respond to activity intents, service bindings, content provider requests, or explicit broadcasts.

App Hibernation in AOSP meets the above requirements.

3.6. API Namespaces

Android follows the package and class namespace conventions defined by the Java programming language. To ensure compatibility with third-party applications, device implementers MUST NOT make any prohibited modifications (see below) to these package namespaces:

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

That is, they:

• [C-0-1] MUST NOT modify the publicly exposed APIs on the Android platform by changing any method or class signatures, or by removing classes or class fields.
• [C-0-2] MUST NOT add any publicly exposed elements (such as classes or interfaces, or fields or methods to existing classes or interfaces) or Test or System APIs to the APIs in the above namespaces. A “publicly exposed element” is any construct that is not decorated with the “@hide” marker as used in the upstream Android source code.

Device implementers MAY modify the underlying implementation of the APIs, but such modifications:

• [C-0-3] MUST NOT impact the stated behavior and Java-language signature of any publicly exposed APIs.
• [C-0-4] MUST NOT be advertised or otherwise exposed to developers.

However, device implementers MAY add custom APIs outside the standard Android namespace, but the custom APIs:

• [C-0-5] MUST NOT be in a namespace owned by or referring to another organization. For instance, device implementers MUST NOT add APIs to the com.google.* or similar namespace: only Google may do so. Similarly, Google MUST NOT add APIs to other companies' namespaces.
• [C-0-6] MUST be packaged in an Android shared library so that only apps that explicitly use them (via the <uses-library> mechanism) are affected by the increased memory usage of such APIs.

Device implementers MAY add custom APIs in native languages, outside of the NDK APIs, but the custom APIs:

• [C-1-1] MUST NOT be in a NDK library or a library owned by another organization as described here .

If a device implementer proposes to improve one of the package namespaces above (such as by adding useful new functionality to an existing API, or adding a new API), the implementer SHOULD visit source.android.com and begin the process for contributing changes and code, according to the information on that site.

Note that the restrictions above correspond to standard conventions for naming APIs in the Java programming language; this section simply aims to reinforce those conventions and make them binding through inclusion in this Compatibility Definition.

3.7. Runtime Compatibility

Device implementations:

• [C-0-1] MUST support the full Dalvik Executable (DEX) format and Dalvik bytecode specification and semantics .

• [C-0-2] MUST configure Dalvik runtimes to allocate memory in accordance with the upstream Android platform, and as specified by the following table. (See section 7.1.1 for screen size and screen density definitions.)

• SHOULD use Android RunTime (ART), the reference upstream implementation of the Dalvik Executable Format, and the reference implementation's package management system.

• SHOULD run fuzz tests under various modes of execution and target architectures to assure the stability of the runtime. Refer to JFuzz and DexFuzz in the Android Open Source Project website.

Note that memory values specified below are considered minimum values and device implementations MAY allocate more memory per application.

3.8. User Interface Compatibility

3.8.1. Launcher (Home Screen)

Android includes a launcher application (home screen) and support for third-party applications to replace the device launcher (home screen).

If device implementations allow third-party applications to replace the device home screen, they:

• [C-1-1] MUST declare the platform feature android.software.home_screen .
• [C-1-2] MUST return the AdaptiveIconDrawable object when the third-party application use <adaptive-icon> tag to provide their icon, and the PackageManager methods to retrieve icons are called.

If device implementations include a default launcher that supports in-app pinning of shortcuts, they:

• [C-2-1] MUST report true for ShortcutManager.isRequestPinShortcutSupported() .
• [C-2-2] MUST have user affordance asking the user before adding a shortcut requested by apps via the ShortcutManager.requestPinShortcut() API method.
• [C-2-3] MUST support pinned shortcuts and dynamic and static shortcuts as documented on the App Shortcuts page .

Conversely, if device implementations do not support in-app pinning of shortcuts, they:

• [C-3-1] MUST report false for ShortcutManager.isRequestPinShortcutSupported() .

If device implementations implement a default launcher that provides quick access to the additional shortcuts provided by third-party apps through the ShortcutManager API, they:

• [C-4-1] MUST support all documented shortcut features (eg static and dynamic shortcuts, pinning shortcuts) and fully implement the APIs of the ShortcutManager API class.

If device implementations include a default launcher app that shows badges for the app icons, they:

• [C-5-1] MUST respect the NotificationChannel.setShowBadge() API method. In other words, show a visual affordance associated with the app icon if the value is set as true , and do not show any app icon badging scheme when all of the app's notification channels have set the value as false .
• MAY override the app icon badges with their proprietary badging scheme when third-party applications indicate support of the proprietary badging scheme through the use of proprietary APIs, but SHOULD use the resources and values provided through the notification badges APIs described in the SDK , such as the Notification.Builder.setNumber() and the Notification.Builder.setBadgeIconType() API.

3.8.2. Widgets

Android supports third-party app widgets by defining a component type and corresponding API and lifecycle that allows applications to expose an “AppWidget” to the end user.

If device implementations support third-party app widgets, they:

• [C-1-1] MUST declare support for platform feature android.software.app_widgets .
• [C-1-2] MUST include built-in support for AppWidgets and expose user interface affordances to add, configure, view, and remove AppWidgets directly within the Launcher.
• [C-1-3] MUST be capable of rendering widgets that are 4 x 4 in the standard grid size. See the App Widget DesignGuidelines in the Android SDK documentation for details.
• MAY support application widgets on the lock screen.

If device implementations support third-party app widgets and in-app pinning of shortcuts, they:

• [C-2-1] MUST report true for AppWidgetManager.html.isRequestPinAppWidgetSupported() .
• [C-2-2] MUST have user affordance asking the user before adding a shortcut requested by apps via the AppWidgetManager.requestPinAppWidget() API method.

3.8.3. Notifications

Android includes Notification and NotificationManager APIs that allow third-party app developers to notify users of notable events and attract users' attention using the hardware components (eg sound, vibration and light) and software features (eg notification shade, system bar) of the device.

3.8.3.1. Presentation of Notifications

If device implementations allow third-party apps to notify users of notable events , they:

• [C-1-1] MUST support notifications that use hardware features, as described in the SDK documentation, and to the extent possible with the device implementation hardware. For instance, if a device implementation includes a vibrator, it MUST correctly implement the vibration APIs. If a device implementation lacks hardware, the corresponding APIs MUST be implemented as no-ops. This behavior is further detailed in section 7 .
• [C-1-2] MUST correctly render all resources (icons, animation files, etc.) provided for in the APIs, or in the Status/System Bar icon style guide , although they MAY provide an alternative user experience for notifications than that provided by the reference Android Open Source implementation.
• [C-1-3] MUST honor and implement properly the behaviors described for the APIs to update, remove and group notifications.
• [C-1-4] MUST provide the full behavior of the NotificationChannel API documented in the SDK.
• [C-1-5] MUST provide a user affordance to block and modify a certain third-party app's notification per each channel and app package level.
• [C-1-6] MUST also provide a user affordance to display deleted notification channels.
• [C-1-7] MUST correctly render all resources (images, stickers, icons, etc.) provided through Notification.MessagingStyle alongside the notification text without additional user interaction. For example, MUST show all resources including icons provided through android.app.Person in a group conversation that is set through setGroupConversation .
• [C-SR] Are STRONGLY RECOMMENDED to provide an affordance for the user to control the notifications that are exposed to apps that have been granted the Notification Listener permission. The granularity MUST be so that the user can control for each such notification listener what notification types are bridged to this listener. The types MUST include "conversations", "alerting", "silent", and "important ongoing" notifications.
• [C-SR] Are STRONGLY RECOMMENDED provide an affordance for users to specify apps to exclude from notifying any specific notification listener.
• [C-SR] Are STRONGLY RECOMMENDED to automatically surface a user affordance to block a certain third-party app's notification per each channel and app package level after the user dismisses that notification multiple times.
• SHOULD support rich notifications.
• SHOULD present some higher priority notifications as heads-up notifications.
• SHOULD have a user affordance to snooze notifications.
• MAY only manage the visibility and timing of when third-party apps can notify users of notable events to mitigate safety issues such as driver distraction.

Android 11 introduces support for conversation notifications, which are notifications that use MessagingStyle and provides a published People Shortcut ID.

Device implementations:

• [C-SR] Are STRONGLY RECOMMENDED to group and display conversation notifications ahead of non conversation notifications with the exception of ongoing foreground service notifications and importance:high notifications.

If device implementations support conversation notifications and the app provides the required data for bubbles , they:

• [C-SR] Are STRONGLY RECOMMENDED to display this conversation as a bubble. The AOSP implementation meets these requirements with the default System UI, Settings, and Launcher.

If device implementations support rich notifications, they:

• [C-2-1] MUST use the exact resources as provided through the Notification.Style API class and its subclasses for the presented resource elements.
• SHOULD present each and every resource element (eg icon, title and summary text) defined in the Notification.Style API class and its subclasses.

Heads up notifications are notifications that are presented to the user as they come in independently of the surface the user is on. If device implementations support heads-up notifications, then they:

• [C-3-1] MUST use the heads-up notification view and resources as described in the Notification.Builder API class when heads-up notifications are presented.
• [C-3-2] MUST display the actions provided through Notification.Builder.addAction() together with the notification content without additional user interaction as described in the SDK .

3.8.3.2. Notification Listener Service

Android includes the NotificationListenerService APIs that allow apps (once explicitly enabled by the user) to receive a copy of all notifications as they are posted or updated.

Device implementations:

• [C-0-1] MUST correctly and promptly update notifications in their entirety to all such installed and user-enabled listener services, including any and all metadata attached to the Notification object.
• [C-0-2] MUST respect the snoozeNotification() API call, and dismiss the notification and make a callback after the snooze duration that is set in the API call.

If device implementations have a user affordance to snooze notifications, they:

• [C-1-1] MUST reflect the snoozed notification status properly through the standard APIs such as NotificationListenerService.getSnoozedNotifications() .
• [C-1-2] MUST make this user affordance available to snooze notifications from each installed third-party app's, unless they are from persistent/foreground services.

3.8.3.3. DND (Do not Disturb) / Priority Mode

If device implementations support the DND feature (also called Priority Mode), they:

• [C-1-1] MUST, for when the device implementation has provided a means for the user to grant or deny third-party apps to access the DND policy configuration, display Automatic DND rules created by applications alongside the user-created and pre-defined rules.
• [C-1-3] MUST honor the suppressedVisualEffects values passed along the NotificationManager.Policy and if an app has set any of the SUPPRESSED_EFFECT_SCREEN_OFF or SUPPRESSED_EFFECT_SCREEN_ON flags, it SHOULD indicate to the user that the visual effects are suppressed in the DND settings menu.

3.8.4. Assist API's

Android includes the Assist APIs to allow applications to elect how much information of the current context is shared with the assistant on the device.

If device implementations support the Assist action, they:

• [C-2-1] MUST indicate clearly to the end user when the context is shared, by either:
  • Each time the assist app accesses the context, displaying a white light around the edges of the screen that meet or exceed the duration and brightness of the Android Open Source Project implementation.
  • For the preinstalled assist app, providing a user affordance less than two navigations away from the default voice input and assistant app settings menu , and only sharing the context when the assist app is explicitly invoked by the user through a hotword or assist navigation key input.
• [C-2-2] The designated interaction to launch the assist app as described in section 7.2.3 MUST launch the user-selected assist app, in other words the app that implements VoiceInteractionService , or an activity handling the ACTION_ASSIST intent.

3.8.5. Alerts and Toasts

Applications can use the Toast API to display short non-modal strings to the end user that disappear after a brief period of time, and use the TYPE_APPLICATION_OVERLAY window type API to display alert windows as an overlay over other apps.

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

• [C-1-1] MUST provide a user affordance to block an app from displaying alert windows that use the TYPE_APPLICATION_OVERLAY . The AOSP implementation meets this requirement by having controls in the notification shade.

• [C-1-2] MUST honor the Toast API and display Toasts from applications to end users in some highly visible manner.

3.8.6. Themes

Android provides “themes” as a mechanism for applications to apply styles across an entire Activity or application.

Android includes a “Holo” and "Material" theme family as a set of defined styles for application developers to use if they want to match the Holo theme look and feel as defined by the Android SDK.

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

• [C-1-1] MUST NOT alter any of the Holo theme attributes exposed to applications.
• [C-1-2] MUST support the “Material” theme family and MUST NOT alter any of the Material theme attributes or their assets exposed to applications.
• [C-1-3] MUST either set the "sans-serif" font family to Roboto version 2.x for the languages that Roboto supports, or provide a user affordance to change the font used for the "sans-serif" font family to Roboto version 2.x for the languages that Roboto supports.

Android also includes a “Device Default” theme family as a set of defined styles for application developers to use if they want to match the look and feel of the device theme as defined by the device implementer.

• Device implementations MAY modify the Device Default theme attributes exposed to applications.

Android supports a variant theme with translucent system bars, which allows application developers to fill the area behind the status and navigation bar with their app content. To enable a consistent developer experience in this configuration, it is important the status bar icon style is maintained across different device implementations.

If device implementations include a system status bar, they:

• [C-2-1] MUST use white for system status icons (such as signal strength and battery level) and notifications issued by the system, unless the icon is indicating a problematic status or an app requests a light status bar using the WindowInsetsController#APPEARANCE_LIGHT_STATUS_BARS flag.
• [C-2-2] Android device implementations MUST change the color of the system status icons to black (for details, refer to R.style ) when an app requests a light status bar.

3.8.7. Live Wallpapers

Android defines a component type and corresponding API and lifecycle that allows applications to expose one or more “Live Wallpapers” to the end user. Live wallpapers are animations, patterns, or similar images with limited input capabilities that display as a wallpaper, behind other applications.

Hardware is considered capable of reliably running live wallpapers if it can run all live wallpapers, with no limitations on functionality, at a reasonable frame rate with no adverse effects on other applications. If limitations in the hardware cause wallpapers and/or applications to crash, malfunction, consume excessive CPU or battery power, or run at unacceptably low frame rates, the hardware is considered incapable of running live wallpaper. As an example, some live wallpapers may use an OpenGL 2.0 or 3.x context to render their content. Live wallpaper will not run reliably on hardware that does not support multiple OpenGL contexts because the live wallpaper use of an OpenGL context may conflict with other applications that also use an OpenGL context.

• Device implementations capable of running live wallpapers reliably as described above SHOULD implement live wallpapers.

If device implementations implement live wallpapers, they:

• [C-1-1] MUST report the platform feature flag android.software.live_wallpaper.

3.8.8. Activity Switching

The upstream Android source code includes the overview screen , a system-level user interface for task switching and displaying recently accessed activities and tasks using a thumbnail image of the application's graphical state at the moment the user last left the application.

Device implementations including the recents function navigation key as detailed in section 7.2.3 MAY alter the interface.

If device implementations including the recents function navigation key as detailed in section 7.2.3 alter the interface, they:

• [C-1-1] MUST support at least up to 7 displayed activities.
• SHOULD at least display the title of 4 activities at a time.
• [C-1-2] MUST implement the screen pinning behavior and provide the user with a settings menu to toggle the feature.
• SHOULD display highlight color, icon, screen title in recents.
• SHOULD display a closing affordance ("x") but MAY delay this until user interacts with screens.
• SHOULD implement a shortcut to switch easily to the previous activity.
• SHOULD trigger the fast-switch action between the two most recently used apps, when the recents function key is tapped twice.
• SHOULD trigger the split-screen multiwindow-mode, if supported, when the recents functions key is long pressed.
• MAY display affiliated recents as a group that moves together.
• [SR] Are STRONGLY RECOMMENDED to use the upstream Android user interface (or a similar thumbnail-based interface) for the overview screen.

3.8.9. Input Management

Android includes support for Input Management and support for third-party input method editors.

If device implementations allow users to use third-party input methods on the device, they:

• [C-1-1] MUST declare the platform feature android.software.input_methods and support IME APIs as defined in the Android SDK documentation.

3.8.10. Lock Screen Media Control

The Remote Control Client API is deprecated from Android 5.0 in favor of the Media Notification Template that allows media applications to integrate with playback controls that are displayed on the lock screen.

3.8.11. Screen savers (previously Dreams)

See section 3.2.3.5 for settings intent to congfigure screen savers.

3.8.12. Location

If device implementations include a hardware sensor (eg GPS) that is capable of providing the location coordinates, they

• [C-1-2] MUST display the current status of location in the Location menu within Settings.
• [C-1-3] MUST NOT display location modes in the Location menu within Settings.

3.8.13. Unicode and Font

Android includes support for the emoji characters defined in Unicode 10.0 .

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

• [C-1-1] MUST be capable of rendering these emoji characters in color glyph.
• [C-1-2] MUST include support for:
  • Roboto 2 font with different weights—sans-serif-thin, sans-serif-light, sans-serif-medium, sans-serif-black, sans-serif-condensed, sans-serif-condensed-light for the languages available on the device.
  • Full Unicode 7.0 coverage of Latin, Greek, and Cyrillic, including the Latin Extended A, B, C, and D ranges, and all glyphs in the currency symbols block of Unicode 7.0.
• [C-1-3] MUST NOT remove or modify NotoColorEmoji.tff in the system image. (It is acceptable to add a new emoji font to override emoji in NotoColorEmoji.tff)
• SHOULD support the skin tone and diverse family emojis as specified in the Unicode Technical Report #51 .

If device implementations include an IME, they:

• SHOULD provide an input method to the user for these emoji characters.

Android includes support to render Myanmar fonts. Myanmar has several non-Unicode compliant fonts, commonly known as “Zawgyi,” for rendering Myanmar languages.

If device implementations include support for Burmese, they:

• [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 is specified (eg 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

If device implementations have the capability to display multiple activities at the same time, they:

• [C-1-1] MUST implement such multi-window mode(s) in accordance with the application behaviors and APIs described in the Android SDK multi-window mode support documentation and meet the following requirements:
• [C-1-2] MUST honor android:resizeableActivity that is set by an app in the AndroidManifest.xml file as described in this SDK .
• [C-1-3] MUST NOT offer split-screen or freeform mode if the screen height is less than 440 dp and the screen width is less than 440 dp.
• [C-1-4] An activity MUST NOT be resized to a size smaller than 220dp in multi-window modes other than Picture-in-Picture.
• Device implementations with screen size xlarge SHOULD support freeform mode.

If device implementations support multi-window mode(s), and the split screen mode, they:

• [C-2-2] MUST crop the docked activity of a split-screen multi-window but SHOULD show some content of it, if the Launcher app is the focused window.
• [C-2-3] MUST honor the declared AndroidManifestLayout_minWidth and AndroidManifestLayout_minHeight values of the third-party launcher application and not override these values in the course of showing some content of the docked activity.

If device implementations support multi-window mode(s) and Picture-in-Picture multi-window mode, they:

• [C-3-1] MUST launch activities in picture-in-picture multi-window mode when the app is: * Targeting API level 26 or higher and declares android:supportsPictureInPicture * Targeting API level 25 or lower and declares both android:resizeableActivity and android:supportsPictureInPicture .
• [C-3-2] MUST expose the actions in their SystemUI as specified by the current PIP activity through the setActions() API.
• [C-3-3] MUST support aspect ratios greater than or equal to 1:2.39 and less than or equal to 2.39:1, as specified by the PIP activity through the setAspectRatio() API.
• [C-3-4] MUST use KeyEvent.KEYCODE_WINDOW to control the PIP window; if PIP mode is not implemented, the key MUST be available to the foreground activity.
• [C-3-5] MUST provide a user affordance to block an app from displaying in PIP mode; the AOSP implementation meets this requirement by having controls in the notification shade.

• [C-3-6] MUST allocate the following minimum width and height for the PIP window when an application does not declare any value for AndroidManifestLayout_minWidth and AndroidManifestLayout_minHeight :

  • Devices with the Configuration.uiMode that is set other than UI_MODE_TYPE_TELEVISION MUST allocate a minimum width and height of 108 dp.
  • Devices with the Configuration.uiMode that is set to UI_MODE_TYPE_TELEVISION MUST allocate a minimum width of 240 dp and a minimum height of 135 dp.

3.8.15. Display Cutout

Android supports a Display Cutout as described in the SDK document. The DisplayCutout API defines an area on the edge of the display that may not be functional for an application due to a display cutout or curved display on the edge(s).

If device implementations include display cutout(s), they:

• [C-1-5] MUST NOT have cutout(s) if the device's aspect ratio is 1.0(1:1).
• [C-1-2] MUST NOT have more than one cutout per edge.
• [C-1-3] MUST honor the display cutout flags set by the app through the WindowManager.LayoutParams API as described in the SDK.
• [C-1-4] MUST report correct values for all cutout metrics defined in the DisplayCutout API.

3.8.16. Device Controls

Android includes ControlsProviderService and Control APIs to allow third-party applications to publish device controls for quick status and action for users.

See Section 2_2_3 for device-specific requirements.

3.9. Device Administration

Android includes features that allow security-aware applications to perform device administration functions at the system level, such as enforcing password policies or performing remote wipe, through the Android Device Administration API .

If device implementations implement the full range of device administration policies defined in the Android SDK documentation, they:

• [C-1-1] MUST declare android.software.device_admin .
• [C-1-2] MUST support device owner provisioning as described in section 3.9.1 and section 3.9.1.1 .

3.9.1 Device Provisioning

3.9.1.1 Device owner provisioning

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

• [C-1-1] MUST support enrolling a Device Policy Client (DPC) as a Device Owner app as described below:
  • When the device implementation has neither users nor user data configured, it:
    • [C-1-5] MUST enroll the DPC application as the Device Owner app or enable the DPC app to choose whether to become a Device Owner or a Profile Owner, if the device declares Near-Field Communications (NFC) support via the feature flag android.hardware.nfc and receives an NFC message containing a record with MIME type MIME_TYPE_PROVISIONING_NFC .
    • [C-1-8] MUST send the ACTION_GET_PROVISIONING_MODE intent after device owner provisioning is triggered so that the DPC app can choose whether to become a Device Owner or a Profile Owner, depending on the values of android.app.extra.PROVISIONING_ALLOWED_PROVISIONING_MODES , unless it can be determined from context that there is only one valid option. (such as for NFC based provisioning where Profile Owner provisioning is not supported).
    • [C-1-9] MUST send the ACTION_ADMIN_POLICY_COMPLIANCE intent to the Device Owner app if a Device Owner is established during provisioning regardless of the provisioning method used. The user must not be able to proceed in the Setup Wizard until the Device Owner app finishes.
  • When the device implementation has users or user data, it:
    • [C-1-7] MUST not enroll any DPC application as the Device Owner App any more.
• [C-1-2] MUST show an appropriate disclosure notice (such as referenced in AOSP ) and obtain affirmative consent from the end user prior to an app being set as Device Owner, unless the device is programmatically configured for Retail Demo Mode prior to on-screen, end-user interaction. require some affirmative action before or during the provisioning process to consent to an app being set as Device Owner. Consent can be via user action or by some programmatic means but appropriate disclosure notice (as referenced in AOSP) MUST be shown before device owner provisioning is initiated. Also, the programmatic device owner consent mechanism used (by enterprises) for device owner provisioning MUST NOT interfere with the Out-Of-Box Experience for non-enterprise use.
• [C-1-3] MUST NOT hard code the consent or prevent the use of other device owner apps.

If device implementations declare android.software.device_admin , but also include a proprietary Device Owner device 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 has been 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".
• [C-2-3] MUST NOT hard code the consent or prevent the use of other device owner apps.
• 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 the DPC using the android.app.action.PROVISION_MANAGED_PROFILE ) or by the platform), consent screen and user 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.

• [C-1-4] MUST launch the handler for ACTION_PROVISIONING_SUCCESSFUL intent in the work profile if a Profile Owner is established when provisioning is initiated by the android.app.action.PROVISION_MANAGED_PROFILE intent and the DPC has implemented the handler.

• [C-1-5] MUST send ACTION_PROFILE_PROVISIONING_COMPLETE broadcast to the work profile DPC when provisioning is initiated by the android.app.action.PROVISION_MANAGED_PROFILE intent.

• [C-1-6] MUST send the ACTION_GET_PROVISIONING_MODE intent after profile owner provisioning is triggered so that the DPC app can choose whether to become a Device Owner or a Profile Owner except when provisioning is triggered by the intent android.app.action.PROVISION_MANAGED_PROFILE .

• [C-1-7] MUST send the ACTION_ADMIN_POLICY_COMPLIANCE intent to the work profile when a Profile Owner is established during provisioning regardless of which provisioning method is used except when provisioning is triggered by the intent android.app.action.PROVISION_MANAGED_PROFILE . The user must not be able proceed in the Setup Wizard until the Profile Owner app finishes.

• [C-1-8] MUST send ACTION_MANAGED_PROFILE_PROVISIONED broadcast to the personal profile DPC when a Profile Owner is established, regardless of the provisioning method used.

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 Controller.
• [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.

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

• [C-2-1] MUST support the ability to specify a separate lock screen meeting the following requirements to grant access to apps running in a managed profile only.
  • 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.

If device implementations declare android.software.device_admin and provide an on-device user affordance to add additional secondary Users , they:

• [C-SR] Are STRONGLY RECOMMENDED show the same AOSP Device Owner consent disclosures that were shown in the flow initiated by android.app.action.PROVISION_MANAGED_DEVICE , prior to allowing accounts to be added in the new secondary User, so users understand that the device is managed.

3.10. Accessibility

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-4] MUST provide a user affordance to control accessibility services that declare the AccessibilityServiceInfo.FLAG_REQUEST_ACCESSIBILITY_BUTTON . Note that for device implementations with a system navigation bar, they SHOULD allow the user to have the option for a button in the system's navigation bar to control these 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. Text-to-Speech

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. Quick Settings

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 and support third-party Quick Settings, 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. Instant Apps

If device implementations support Instant Apps, they MUST satisfy the following requirements:

• [C-1-1] Instant Apps MUST only be granted permissions that have the android:protectionLevel set to "instant" .
• [C-1-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-1-3] Instant Apps MUST NOT interact explicitly with installed apps unless the component is exposed via android:visibleToInstantApps.
• [C-1-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. Device implementations:

  • [C-1-5] MUST provide a user affordance to view and delete Instant Apps locally cached for each individual app package.
  • [C-1-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-1-7] MUST allow running Instant Apps to be accessed from the Recents function if the Recents function is available on the device.

• [C-1-8] MUST preload one or more applications or service components with an intent handler for the intents listed in the SDK here and make the intents visible for Instant Apps.

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.

3.18. Contacts

Android includes Contacts Provider APIs to allow applications to manage contact information stored on the device. Contact data that is entered directly into the device is typically synchronized with a web service, but the data MAY also only reside locally on the device. Contacts that are only stored on the device are referred to as local contacts.

RawContacts are "associated with" or "stored in" an Account when the ACCOUNT_NAME , and ACCOUNT_TYPE , columns for the raw contacts match the corresponding Account.name and Account.type fields of the account.

Default local account : an account for raw contacts that are only stored on the device and not associated with an Account in the AccountManager , which are created with null values for the ACCOUNT_NAME , and ACCOUNT_TYPE , columns.

Custom local account : an account for raw contacts that are only stored on the device and not associated with an Account in the AccountManager, which are created with at least one non-null value for the ACCOUNT_NAME , and ACCOUNT_TYPE , columns.

Device implementations:

• [C-SR] Are STRONGLY RECOMMENDED to not create custom local accounts .

If device implementations use a custom local account :

• [C-1-1] The ACCOUNT_NAME , of the custom local account MUST be returned by ContactsContract.RawContacts.getLocalAccountName
• [C-1-2] The ACCOUNT_TYPE , of the custom local account MUST be returned by ContactsContract.RawContacts.getLocalAccountType
• [C-1-3] Raw contacts that are inserted by third party applications with the default local account (ie by setting null values for ACCOUNT_NAME and ACCOUNT_TYPE ) MUST be inserted to the custom local account .
• [C-1-4] Raw contacts inserted into the custom local account MUST not be removed when accounts are added or removed.
• [C-1-5] Delete operations performed against the custom local account MUST result in raw contacts being purged immediately (as if the CALLER_IS_SYNCADAPTER param was set to true), even if the CALLER\_IS\_SYNCADAPTER param was set to false or not specified.

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.

• [C-0-2] MUST support verifying “.apk” files using the APK Signature Scheme v3.1 , 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 harmful.

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

• [C-0-8] MUST implement support for Incremental File System as documented here .

• [C-0-9] MUST support verifying .apk files using the APK Signature Scheme v4 and APK Signature Scheme v4.1 .

5. Multimedia Compatibility

Device implementations:

• [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 .

Device implementations:

• 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. Media Codecs

5.1.1. Audio Encoding

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

If device implementations support HEVC video decoding, they: * [C-1-1] MUST support HEIF (HEIC) image decoding.

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

• [C-2-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. Video Codecs

• 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.

In particular:

• [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. Video Encoding

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.

If device implementations provide HDR encoding, they:

• [C-SR] are STRONGLY RECOMMENDED to provide a plugin for the seamless transcoding API to convert from HDR format to SDR format.

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. VP8

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. VP9

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. Video Decoding

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 through the Media APIs:

• [C-3-1] Device implementations MUST accept the required HDR metadata from the application, as well as support extracting and outputting the required HDR metadata from the bitstream and/or container.
• [C-3-2] Device implementations MUST properly display HDR content on the device screen or on a standard video output port (eg, HDMI).

5.3.6. VP8

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. VP9

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 ( KEY_HDR_STATIC_INFO for all HDR profiles, as well as 'KEY_HDR10_PLUS_INFO' for HDR10Plus profiles) from the application. They also MUST support extracting and outputting the required HDR metadata from the bitstream and/or container.
• [C-4-2] Device implementations MUST properly display HDR content on the device screen or on a standard video output port (eg, HDMI).

5.3.8. Dolby Vision

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. Audio Recording

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 for any AudioRecord or AAudio INPUT stream that is opened successfully. At a minimum, the following characteristics MUST be supported :

  • Format: Linear PCM, 16-bit
  • Sampling rates: 8000, 11025, 16000, 44100, 48000 Hz
  • Channels: Mono
  • Audio Sources: DEFAULT , MIC , CAMCORDER , VOICE_RECOGNITION , VOICE_COMMUNICATION , UNPROCESSED , or VOICE_PERFORMANCE . This also applies to the equivalent Input Presets in AAudio , for example, AAUDIO_INPUT_PRESET_CAMCORDER .

• 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, for active AudioRecord using MediaRecorder.AudioSources DEFAULT , MIC , CAMCORDER , VOICE_RECOGNITION , VOICE_COMMUNICATION , UNPROCESSED , or VOICE_PERFORMANCE . 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 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 . Specifically:

• [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.5. Audio Playback

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, 24000, 32000, 44100, 48000 at the channel configurations listed above
    • 96000 in mono and stereo

5.5.2. Audio Effects

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

Automotive device implementations:

• 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.5.4. Audio Offload

If device implementations support audio offload playback , they:

• [C-SR] Are STRONGLY RECOMMENDED to trim the played gapless audio content between two clips with the same format when specified by the AudioTrack gapless API and the media container for MediaPlayer.

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 the environment at an on-device transducer or the signal leaves the device via a port and can be observed externally.
• cold output latency . The time between starting an output stream and the presentation time of the first frame based on timestamps, 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 time between starting the stream and when the first valid frame is received, 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.

• 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 .
• glitch . 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.
• mean absolute deviation . The average of the absolute value of the deviations from the mean for a set of values.
• tap-to-tone latency . The time between when the screen is tapped and when a tone generated as a result of that tap is heard on the speaker.

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 over the speaker data path. Existing and new devices that run this version of Android are VERY STRONGLY RECOMMENDED to meet these requirements now. In a future platform release, we will require Cold output latency of 200 ms or less as a MUST.
• [C-SR] Tap-to-tone latency of 80 milliseconds or less.

• [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 the AAudio native audio API, 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 the AAudio native audio API, 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 over the microphone data path. Existing and new devices that run this version of Android are VERY STRONGLY RECOMMENDED to meet these requirements now. In a future platform release we will require Cold input latency of 200 ms or less as a MUST.

• [C-SR] Limit the error in input timestamps, as returned by AudioRecord.getTimestamp or AAudioStream_getTimestamp , to +/- 1 ms.

If device implementations declare android.hardware.audio.output and android.hardware.microphone , they: * [C-SR] Are STRONGLY RECOMMENDED to have a Mean Continuous Round-Trip Latency of 50 milliseconds or less over 5 measurements, with a Mean Absolute Deviation less than 10 msec, over at least one supported path.

5.7. Network Protocols

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

For each codec and container format that a device implementation is required to support, the device implementation:

• [C-1-1] MUST support that codec or container over HTTP and HTTPS.

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

• [C-1-3] MUST support the corresponding RTSP payload formats as shown in the RTSP table below. For exceptions please see the table footnotes in section 5.1 .

Media Segment Formats

RTSP (RTP, SDP)

5.8. Secure Media

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. Musical Instrument Digital Interface (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
  • 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)

• SHOULD support MIDI over USB peripheral mode, section 7.7

5.10. Professional Audio

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 the continuous round-trip audio latency, as defined in section 5.6 Audio Latency of 25 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 the AAudio native audio API and AAUDIO_PERFORMANCE_MODE_LOW_LATENCY .
• [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.

• [C-SR] Are STRONGLY RECOMMENDED to meet latencies as defined in section 5.6 Audio Latency , of 20 milliseconds or less, over 5 measurements with a Mean Absolute Deviation less than 5 milliseconds over the speaker to microphone path.
• [C-SR] Are STRONGLY RECOMMENDED to meet the Pro Audio requirements for continuous round-trip audio latency, cold input latency and cold output latency and USB audio requirements using the AAudio native audio API over the MMAP path.

• [C-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 SynthMark . SynthMark uses a software synthesizer running on a simulated audio framework that measures system performance. See the SynthMark documentation for an explanation of the benchmarks. 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

• 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).

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 a mean Continuous Round-trip Audio Latency, as defined in section 5.6 Audio Latency , of 20 milliseconds or less, over 5 measurements with a Mean Absolute Deviation less than 5 milliseconds over the audio jack path using an Audio Loopback Dongle .
• [SR] STRONGLY RECOMMENDED to comply with section Mobile device (jack) specifications of the Wired Audio Headset Specification (v1.1) .

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 mean Continuous Round-trip Audio Latency of 25 milliseconds or less, over 5 measurements with a Mean Absolute Deviation less than 5 milliseconds over the USB host mode port using USB audio class. (This can be measured using a USB-3.5mm adapter and an Audio Loopback Dongle, or using a USB audio interface with patch cables connecting the inputs to outputs).
• [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.
• [C-SR] Are STRONGLY RECOMMENDED to meet this group of requirements using the AAudio native audio API over the MMAP path.

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. In other words:

• [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. Developer Tools

Device implementations:

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

• Android Debug Bridge (adb)

  • [C-0-2] MUST support adb as documented in the Android SDK and the shell commands provided in the AOSP, which can be used by app developers, including dumpsys cmd stats
  • [C-0-11] MUST support the shell command cmd testharness . Upgrading device implementations from an earlier Android version without a persistent data block MAY be exempted from C-0-11.
  • [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. Specifically:

  If device implementations without a USB port support peripheral mode, they:

  • [C-3-1] MUST implement adb via local-area network (such as Ethernet or Wi-Fi).
  • [C-3-2] MUST provide drivers for Windows 7, 8 and 10, allowing developers to connect to the device using the adb protocol.

  If device implementations support adb connections to a host machine via Wi-Fi or Ethernet , they:

  • [C-4-1] MUST have the AdbManager#isAdbWifiSupported() method return true .

  If device implementations support adb connections to a host machine via Wi-Fi or Ethernet , and includes at least one camera, they:

  • [C-5-1] MUST have the AdbManager#isAdbWifiQrSupported() method return true .

• 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.

• Monkey

  • [C-0-8] MUST include the Monkey framework and make it available for applications to use.

• SysTrace

  • [C-0-9] MUST support the systrace tool as documented in the Android SDK. Systrace must be inactive by default and there MUST be a user-accessible mechanism to turn on Systrace.

• Perfetto

  • [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 .

• Low Memory Killer

  • [C-0-10] MUST write a LMK_KILL_OCCURRED_FIELD_NUMBER Atom to the statsd log when an app is terminated by the Low Memory Killer .

• Test Harness Mode 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 Test 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. Developer Options

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. Display and Graphics

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. Screen Configuration

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 .

Device implementations:

• [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 Android-compatible display(s) with rounded corners, they:

• [C-1-1] MUST ensure that at least one of the following requirements is met:

  • The radius of the rounded corners is less than or equal to 38 dp.
  • When a 15 dp by 15 dp box is anchored at each corner of the logical display, at least one pixel of each box is visible on the screen.

• SHOULD include user affordance to switch to the display mode with the rectangular corners.

If device implementations include an Android-compatible display(s) that is foldable, or includes a folding hinge between multiple display panels and makes such display(s) available to render third-party apps, they:

• [C-2-1] MUST implement the latest available stable version of the extensions API or the stable version of sidecar API to be used by Window Manager Jetpack library.

If device implementations include an Android-compatible display(s) that is foldable, or includes a folding hinge between multiple display panels and if the hinge or fold crosses a fullscreen application window, they:

• [C-3-1] MUST report the position, bounds and state of hinge or fold through extensions or sidecar APIs to the application.

For details on correctly implementing the sidecar or extension APIs refer to the public documentation of Window Manager Jetpack .

7.1.1.2. Screen Aspect Ratio

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-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. Screen Density

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. Screen Orientation

Device implementations:

• [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

Device implementations:

• [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.

The OpenGL ES dEQP tests are partitioned into a number of test lists, each with an associated date/version number. These are in the Android source tree at external/deqp/android/cts/master/glesXX-master-YYYY-MM-DD.txt . A device that supports OpenGL ES at a self-reported level indicates that it can pass the dEQP tests in all test lists from this level and earlier.

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-2-3] MUST report the maximum version of the OpenGL ES dEQP tests supported via the android.software.opengles.deqp.level feature flag.
• [C-2-4] MUST at least support version 132383489 (from Mar 1st, 2020) as reported in the android.software.opengles.deqp.level feature flag.
• [C-2-5] MUST pass all OpenGL ES dEQP Tests in the test lists between version 132383489 and the version specified in the android.software.opengles.deqp.level feature flag, for each supported OpenGL ES version.
• [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:

The Vulkan dEQP tests are partitioned into a number of test lists, each with an associated date/version. These are in the Android source tree at external/deqp/android/cts/master/vk-master-YYYY-MM-DD.txt . A device that supports Vulkan at a self-reported level indicates that it can pass the dEQP tests in all test lists from this level and earlier.

If device implementations include support for Vulkan 1.0 or higher, 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-1-8] MUST report the maximum version of the Vulkan dEQP Tests supported via the android.software.vulkan.deqp.level feature flag.
• [C-1-9] MUST at least support version 132317953 (from Mar 1st, 2019) as reported in the android.software.vulkan.deqp.level feature flag.
• [C-1-10] MUST pass all Vulkan dEQP Tests in the test lists between version 132317953 and the version specified in the android.software.vulkan.deqp.level feature flag.
• [C-1-11] MUST NOT enumerate support for the VK_KHR_video_queue, VK_KHR_video_decode_queue, or VK_KHR_video_encode_queue 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.

Device implementations:

• [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.

Device implementations:

• [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. Screen Technology

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. Input Devices

Device implementations:

• [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. Keyboard

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.

Device implementations:

• [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. Navigation Keys

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 indication.

Device implementations:

• [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 function.

If device implementations do not provide the Menu function, for backwards compatibility, they: * [C-3-1] MUST make the Menu function available to applications when targetSdkVersion is less than 10, either by a physical button, a software key, or gestures. 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.

If the navigation function is provided as an on-screen, gesture-based action:

• [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, View.SYSTEM_UI_FLAG_IMMERSIVE_STICKY, WindowInsetsController.BEHAVIOR_DEFAULT, or WindowInsetsController.BEHAVIOR_SHOW_TRANSIENT_BARS_BY_SWIPE 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, View.SYSTEM_UI_FLAG_IMMERSIVE_STICKY, WindowInsetsController.BEHAVIOR_DEFAULT, or WindowInsetsController.BEHAVIOR_SHOW_TRANSIENT_BARS_BY_SWIPE flags set, custom swipeable system panels MUST be hidden until the user brings in or un-dims 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.

Device implementations:

• 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) on a primary Android-compatible display, 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 on a primary Android-compatible display, 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 device.

If device implementations rely on an external input device such as mouse or trackball (ie not directly touching the screen) for input on a primary Android-compatible display 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 .
• [C-3-2] MUST report only android.hardware.faketouch .
• [C-3-3] MUST report TOUCHSCREEN_NOTOUCH for the Configuration.touchscreen API field.

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.

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. Game Controller Support

7.2.6.1. Button Mappings

Device implementations:

• [C-1-1] MUST be capable to map HID events to the corresponding InputEvent constants as listed in the below tables. The upstream Android implementation satisfies this requirement.

If device implementations 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, they:

• [C-2-1] MUST declare the feature flag android.hardware.gamepad

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. Remote Control

See Section 2.3.1 for device-specific requirements.

7.3. Sensors

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 .

Device implementations:

• [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.
• [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.
• [C-1-6] MUST 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.
• [C-SR] Are STRONGLY RECOMMENDED to have timestamp synchronization error below 100 milliseconds, and SHOULD have timestamp synchronization error below 1 millisecond.
• 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.

If device implementations include a particular sensor type that has a corresponding API for third-party developers, they:

• [C-1-6] MUST set a non-zero resolution for all sensors, and report the value via the Sensor.getResolution() API method.

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.)

Device implementations:

• 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 .

If device implementations include a particular sensor type that has a corresponding API for third-party developers and the sensor only reports one value, then device implementations:

• [C-3-1] MUST set the resolution to 1 for the sensor and report the value via the Sensor.getResolution() API method.

If device implementations include a particular sensor type which supports SensorAdditionalInfo#TYPE_VEC3_CALIBRATION and the sensor is exposed to third-party developers, they:

• [C-4-1] MUST NOT include any fixed, factory-determined calibration parameters in the data provided.

If device implementations include a combination of 3-axis accelerometer, a 3-axis gyroscope sensor, or a magnetometer sensor, they are:

• [C-SR] STRONGLY RECOMMENDED to ensure the accelerometer, gyroscope and magnetometer have a fixed relative position, such that if the device is transformable (eg foldable), the sensor axes remain aligned and consistent with the sensor coordinate system throughout all possible device transformation states.

7.3.1. Accelerometer

Device implementations:

• [C-SR] Are STRONGLY RECOMMENDED to include a 3-axis accelerometer.

If device implementations include an accelerometer, 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-4-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-5-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-6-1] MUST implement a TYPE_ROTATION_VECTOR composite sensor.

7.3.2. Magnetometer

Device implementations:

• [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.
• [C-1-10] MUST 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

Device implementations:

• [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 API's 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. Gyroscope

Device implementations:

• [C-SR] Are STRONGLY RECOMMENDED to include a gyroscope sensor.

If device implementations include a 3-axis gyroscope, they:

• [C-2-1] MUST implement the TYPE_GYROSCOPE sensor.
• [C-SR] Are Strongly Recommended to implement TYPE_GYROSCOPE_UNCALIBRATED sensor.

If device implementations include a 3-axis gyroscope, an accelerometer sensor and a magnetometer sensor, they:

• [C-4-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-5-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

Device implementations:

• [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. Thermometer

If device implementations include an ambient thermometer (temperature sensor), they:

• [C-1-1] MUST define SENSOR_TYPE_AMBIENT_TEMPERATURE for the ambient temperature sensor and the sensor MUST measure the ambient (room/vehicle cabin) temperature from where the user is interacting with the device in degrees Celsius.

If device implementations include a thermometer sensor that measures a temperature other than ambient temperature, such as CPU temperature, they:

• [C-2-1] MUST NOT define SENSOR_TYPE_AMBIENT_TEMPERATURE for the temperature sensor.

If device implementations include a sensor for monitoring skin temperature, then they:

• [C-SR] Are STRONGLY RECOMMENDED to support the [PowerManager.getThermalHeadroom]( https://developer.android.com/reference/android/os/PowerManager#getThermalHeadroom(int)) API.

7.3.7. Photometer

• Device implementations MAY include a photometer (ambient light sensor).

7.3.8. Proximity Sensor

• Device implementations MAY include a proximity sensor.

If device implementations include a proximity sensor and they report only a binary “near” or “far” reading, 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.
• [C-1-3] MUST use 0 centimeters as the near reading and 5 centimeters as the far reading.
• [C-1-4] MUST report a maximum range and resolution of 5.

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, and is STRONGLY RECOMMENDED to 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. Biometric Sensors

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 Class 3 (formerly Strong ), Class 2 (formerly Weak ), or Class 1 (formerly 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 need to meet additional requirements as detailed below if they wish to be classified as either Class 1 , Class 2 or Class 3 . Sensors are classified as Class 1 by default, and need to meet additional requirements as detailed below if they wish to be classified as either Class 2 or Class 3 . Both Class 2 and Class 3 biometrics get additional capabilities as detailed below.

If device implementations make a biometric sensor available to third-party applications via android.hardware.biometrics.BiometricManager , android.hardware.biometrics.BiometricPrompt , and android.provider.Settings.ACTION_BIOMETRIC_ENROLL , they:

• [C-4-1] MUST meet the requirements for Class 3 or Class 2 biometric as defined in this document.
• [C-4-2] MUST recognize and honor each parameter name defined as a constant in the Authenticators class and any combinations thereof. Conversely, MUST NOT honor or recognize integer constants passed to the canAuthenticate(int) and setAllowedAuthenticators(int) methods other than those documented as public constants in Authenticators and any combinations thereof.
• [C-4-3] MUST implement the ACTION_BIOMETRIC_ENROLL action on devices that have either Class 3 or Class 2 biometrics. This action MUST only present the enrollment entry points for Class 3 or Class 2 biometrics.

If device implementations support passive biometrics, they:

• [C-5-1] MUST by default require an additional confirmation step (eg a button press).
• [C-SR] Are STRONGLY RECOMMENDED to have a setting to allow users to override application preference and always require accompanying confirmation step.
• [C-SR] Are STRONGLY RECOMMENDED to have the confirm action 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 press.
• [C-5-2] MUST additionally implement an implicit authentication flow (without confirmation step) corresponding to setConfirmationRequired(boolean) , which applications can set to utilize for sign-in flows.

If device implementations have multiple biometric sensors, they:

• [C-SR] Are STRONGLY RECOMMENDED to require only one biometric be confirmed per authentication (eg if both fingerprint and face sensors are available on the device, onAuthenticationSucceeded should be sent after any one of them is confirmed).

In order for device implementations to allow access to keystore keys to third-party applications, they:

• [C-6-1] MUST meet the requirements for Class 3 as defined in this section below.
• [C-6-2] MUST present only Class 3 biometrics when the authentication requires BIOMETRIC_STRONG , or the authentication is invoked with a CryptoObject .

If device implementations wish to treat a biometric sensor as Class 1 (formerly 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% as measured by the Android Biometrics Test Protocols .
• [C-1-9] MUST challenge the user for the recommended primary authentication (eg PIN, pattern, password) after no more than twenty false trials and no less than ninety-second backoff time 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-SR] Are STRONGLY RECOMMENDED to lower the total number of false trials for biometric verification specified in [C-1-9] if the spoof and imposter acceptance rates are higher than 7% as measure by the Android Biometrics Test Protocols.
• [C-1-3] MUST rate limit attempts 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-SR] Are STRONGLY RECOMMENDED to rate limit attempts for at least 30 seconds after five false trials for biometric verification for the maximum number of false trials per [C-1-9] - where a false trial is one with an adequate capture quality (BIOMETRIC_ACQUIRED_GOOD) that does not match an enrolled biometric.
• [C-SR] Are STRONGLY RECOMMENDED to have all rate limiting logic in TEE.
• [C-1-10] MUST disable biometrics once primary authentication backoff has first triggered as described in [C-0-2] of section 9.11.

• [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. Note: Upgrading devices launched on Android version 9 or earlier MUST challenge the user for the recommended primary authentication (eg PIN, pattern, password) once every 72 hours or less.
• [C-1-8] MUST challenge the user for the recommended primary authentication (eg: PIN, pattern, password) or Class 3 (STRONG) biometric 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. Note: Upgrading devices launched on Android version 9 or earlier MAY be exempted from C-1-8.
• [C-SR] Are STRONGLY RECOMMENDED to use the logic in the framework provided by the Android Open Source Project to enforce constraints specified in [C-1-7] and [C-1-8] for new devices.
• [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 Class 2 (formerly Weak ), they:

• [C-2-1] MUST meet all requirements for Class 1 above.

• [C-2-2] MUST have a spoof and imposter acceptance rate not higher than 20%, with (1) a spoof and imposter acceptance rate for Level A presentation attack instrument (PAI) species not higher than 20%, and (2) a spoof and imposter acceptance rate of Level B PAI species not higher than 30%, as measured by the Android Biometrics Test Protocols .

• [C-2-3] MUST 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. Upgrading devices launched on Android version 9 or earlier are not exempted from C-2-7.

• [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. Note: If device implementations are already launched on Android version 9 or earlier and cannot meet the requirement C-2-8 through a system software update, they MAY be exempted from the requirement.

• [C-SR] Are STRONGLY RECOMMENDED to include liveness detection for all biometric modalities and attention detection for Face biometrics.

• [C-2-9] MUST make the biometric sensor available to third-party applications.

If device implementations wish to treat a biometric sensor as Class 3 (formerly Strong ), they:

• [C-3-1] MUST meet all the requirements of Class 2 above, except for [C-1-7] and [C-1-8].
• [C-3-2] MUST have a hardware-backed keystore implementation.

• [C-3-3] MUST have a spoof and imposter acceptance rate not higher than 7%, with (1) a spoof and imposter acceptance rate for Level A presentation attack instrument (PAI) species not higher than 7%, and (2) a spoof and imposter acceptance rate of Level B PAI species not higher than 20%, as measured by the Android Biometrics Test Protocols .

• [C-3-4] MUST challenge the user for the recommended primary authentication (eg PIN, pattern, password) once every 72 hours or less.

• [C-3-5] MUST re-generate Authenticator ID for all Class 3 biometrics supported on device if any of them is re-enrolled.

• [C-3-6] Must enable biometric-backed keystore keys to third-party applications.

If device implementations contain an under-display fingerprint sensor (UDFPS), they:

• [C-SR] Are STRONGLY RECOMMENDED to prevent the touchable area of the UDFPS from interfering with 3-button navigation( which some users might require for accessibility purposes).

7.3.11. Pose Sensor

Device implementations:

• 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.3.12. Hinge Angle Sensor

If device implementations support a hinge angle sensor, they:

• [C-1-1] MUST implement and report TYPE_HINGLE_ANGLE .
• [C-1-2] MUST support at least two readings between 0 and 360 degrees (inclusive ie including 0 and 360 degrees).
• [C-1-3] MUST return a wakeup sensor for getDefaultSensor(SENSOR_TYPE_HINGE_ANGLE) .

7.4. Data Connectivity

7.4.1. Telephony

“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.
• SHOULD allow all available cellular service types (2G, 3G, 4G, 5G, etc.) during emergency calls (regardless of the network types set by SetAllowedNetworkTypeBitmap() ).

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 declare the android.hardware.telephony.euicc feature flag. provide a complete implementation of the EuiccManager API .

If device implementations don't set the system property ro.telephony.iwlan\_operation\_mode to 'legacy', then they:

• [C-4-1] MUST NOT report ' NETWORK_TYPE_IWLAN ' via NetworkRegistrationInfo#getAccessNetworkTechnology() when NetworkRegistrationInfo#getTransportType() is reported as ' TRANSPORT_TYPE_WWAN ' for the same NetworkRegistrationInfo instance.

If device implementations support a single IP Multimedia Subsystem (IMS) registration for both multimedia telephony service (MMTEL) and rich communication service (RCS) features and are expected to comply with cellular carrier requirements regarding using a single IMS registration for all IMS signalling traffic, they:

• [C-5-1] MUST declare the android.hardware.telephony.ims feature flag and provide a complete implementation of the ImsService API for both MMTEL and RCS User Capability Exchange API .
• [C-5-2] MUST declare the android.hardware.telephony.ims.singlereg feature flag and provide a complete implementation of the SipTransport API , the GbaService API , dedicated bearer indications using the IRadio 1.6 HAL, and provisioning via Auto Configuration Server (ACS) or other proprietary provisioning mechanism using the IMS Configuration 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-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

If device implementations report android.hardware.telephony , they:

• [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)

Device implementations:

• 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-1-7] MUST randomize the source MAC address and sequence number of probe request frames, once at the beginning of each scan, while STA is disconnected.
• [C-1-8] MUST use one consistent MAC address (SHOULD NOT randomize MAC address halfway through a scan).
• [C-1-9] MUST iterate probe request sequence number as normal (sequentially) between the probe requests in a scan.
• [C-1-10] MUST randomize Probe request sequence number between the last probe request of a scan and the first probe request of the next scan.
• [C-SR] Are STRONGLY RECOMMENDED to randomize the source MAC address used for all STA communication to an Access Point (AP) while associating and associated.
  • The device MUST use a different randomized MAC address for each SSID (FQDN for Passpoint) it communicates with.
  • The device MUST provide the user with an option to control the randomization per SSID (FQDN for Passpoint) with non randomized and randomized options, and MUST set the default mode for new Wi-Fi configurations to be randomized.
• [C-SR] Are STRONGLY RECOMMENDED to use a random BSSID for any AP that they create.
  • The MAC address MUST be randomized and persisted per SSID used by the AP.
  • The DEVICE MAY provide the user with an option to disable this feature. If such an option is provided, randomization MUST be enabled by default.

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 Direct

Device implementations:

• 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.
• [C-SR] Are STRONGLY RECOMMENDED to randomize the source MAC address for all newly formed Wi-Fi Direct connections.

7.4.2.2. Wi-Fi Tunneled Direct Link Setup

Device implementations:

• 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. Wi-Fi Aware

Device implementations:

• 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 unless an Aware ranging operation is ongoing or an Aware data-path is active (randomization is not expected for as long as the data-path is active).

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. Wi-Fi Passpoint

If device implementations include support for 802.11 (Wi-Fi) they:

• [C-1-1] MUST include support for Wi-Fi Passpoint .
• [C-1-2] MUST implement the Passpoint related WifiManager APIs as described in the SDK documentation .
• [C-1-3] 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).
• [C-1-4] MUST declare android.hardware.wifi.passpoint feature flag.
• [C-1-5] MUST follow the AOSP implementation to discover, match and associate to Passpoint networks.
• [C-1-6] MUST support at least the following subset of device provisioning protocols as defined in the Wi-Fi Alliance Passpoint R2: EAP-TTLS authentication and SOAP-XML.
• [C-1-7] MUST process the AAA server certificate as described in Hotspot 2.0 R3 specification.
• [C-1-8] MUST support user control of provisioning through the Wi-Fi picker.
• [C-1-9] MUST keep Passpoint configurations persistent across reboots.
• [C-SR] Are Strongly recommended to support the terms and conditions acceptance feature.
• [C-SR] Are Strongly recommended to support the Venue information feature.

If a global Passpoint disable user control switch is provided, implementations:

• [C-3-1] MUST enable Passpoint by default.

7.4.2.5. Wi-Fi Location (Wi-Fi Round Trip Time - RTT)

Device implementations:

• 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 NAT-T Keepalive Offload

7.4.2.7. Wi-Fi Easy Connect (Device Provisioning Protocol)

Device implementations:

• 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 have the WifiManager#isEasyConnectSupported() method return true .

7.4.2.8. Enterprise Wi-Fi Server Certificate Validation

If the Wi-Fi server certificate is not validated or the Wi-Fi server domain name is not set, device implementations:

• [C-SR] Are STRONGLY RECOMMENDED not to provide the user an option to manually add Enterprise Wi-Fi network in the Settings app.

7.4.3. Bluetooth

If device implementations support Bluetooth Audio profile, they:

• SHOULD support Advanced Audio Codecs and Bluetooth Audio Codecs (eg LDAC) with A2DP.

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.
• [C-3-5] MUST implement a Resolvable Private Address (RPA) timeout no longer than 15 minutes and rotate the address at timeout to protect user privacy. To prevent timing attacks, timeout intervals MUST also be randomized between 5 and 15 minutes.
• 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.

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) .

If device implementations include support for Bluetooth or Bluetooth Low Energy, they:

• [C-6-1] MUST restrict access to any Bluetooth metadata (such as scan results) which could be used to derive the location of the device, unless the requesting app successfully passes an android.permission.ACCESS_FINE_LOCATION permission check based on its current foreground/background state.

If device implementations include support for Bluetooth or Bluetooth Low Energy and the app manifest does not include a declaration from the developer stating that they are not deriving location from Bluetooth, then, they:

• [C-6-2] MUST gate Bluetooth access behind the android.permission.ACCESS_FINE_LOCATION .

7.4.4. Near-Field Communications

Device implementations:

• 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.