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

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

Agar dianggap kompatibel dengan Android 6.0, implementasi perangkat HARUS memenuhi persyaratan yang disajikan dalam Definisi Kompatibilitas ini, termasuk dokumen apa pun yang dimasukkan melalui referensi.

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

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

Banyak sumber daya yang tercantum di bagian 14 berasal langsung atau tidak langsung dari Android SDK, dan fungsinya akan sama dengan informasi dalam dokumentasi SDK tersebut. Jika Definisi Kompatibilitas atau Rangkaian Uji Kompatibilitas ini tidak sesuai dengan dokumentasi SDK, dokumentasi SDK dianggap resmi. Detail teknis apa pun yang diberikan dalam referensi yang disertakan dalam bagian 14 dianggap sebagai bagian dari Definisi Kompatibilitas ini.

2. Jenis Perangkat

Meskipun Proyek Sumber Terbuka Android telah digunakan dalam implementasi berbagai jenis perangkat dan faktor bentuk, banyak aspek arsitektur dan persyaratan kompatibilitas yang dioptimalkan untuk perangkat genggam. Mulai dari Android 5.0, Proyek Sumber Terbuka Android bertujuan untuk mencakup lebih banyak variasi jenis perangkat seperti yang dijelaskan di bagian ini.

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

HARUS memiliki layar sentuh yang tertanam di perangkat.
HARUS memiliki sumber listrik yang memberikan mobilitas, seperti baterai.

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

HARUS memiliki layar tertanam ATAU menyertakan port output video, seperti VGA, HDMI, atau port nirkabel untuk tampilan.
HARUS mendeklarasikan fitur android.software.leanback dan android.hardware.type.television [ Sumberdaya, 3 ].

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

HARUS memiliki layar dengan panjang diagonal fisik berkisar antara 1,1 hingga 2,5 inci.
HARUS mendeklarasikan fitur android.hardware.type.watch.
HARUS mendukung uiMode = UI_MODE_TYPE_WATCH [ Sumber Daya, 4 ].

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

HARUS mendeklarasikan fitur android.hardware.type.automotive.
HARUS mendukung uiMode = UI_MODE_TYPE_CAR [ Sumber Daya, 5 ].

Semua implementasi perangkat Android yang tidak sesuai dengan salah satu jenis perangkat di atas tetap HARUS memenuhi semua persyaratan dalam dokumen ini agar kompatibel dengan Android 6.0, kecuali persyaratan tersebut dijelaskan secara eksplisit untuk hanya berlaku pada jenis perangkat Android tertentu di atas.

2.1 Konfigurasi Perangkat

Ini adalah ringkasan perbedaan utama dalam konfigurasi perangkat keras berdasarkan jenis perangkat. (Sel kosong menunjukkan “MEI”). Tidak semua konfigurasi tercakup dalam tabel ini; lihat bagian perangkat keras yang relevan untuk detail lebih lanjut.

Kategori	Fitur	Bagian	Genggam	Televisi	Jam tangan	Otomotif	Lainnya
Memasukkan	D-pad	7.2.2. Navigasi non-sentuh		HARUS
	Layar sentuh	7.2.4. Masukan layar sentuh	HARUS		HARUS		SEBAIKNYA
	Mikropon	7.8.1. Mikropon	HARUS	SEBAIKNYA	HARUS	HARUS	SEBAIKNYA
Sensor	Akselerometer	7.3.1 Akselerometer	SEBAIKNYA		SEBAIKNYA		SEBAIKNYA
Sensor	GPS	7.3.3. GPS	SEBAIKNYA			SEBAIKNYA
Konektivitas	Wifi	7.4.2. IEEE 802.11	SEBAIKNYA	HARUS		SEBAIKNYA	SEBAIKNYA
	Wi-Fi Langsung	7.4.2.1. Wi-Fi Langsung	SEBAIKNYA	SEBAIKNYA			SEBAIKNYA
	Bluetooth	7.4.3. Bluetooth	SEBAIKNYA	HARUS	HARUS	HARUS	SEBAIKNYA
	Bluetooth Hemat Energi	7.4.3. Bluetooth	SEBAIKNYA	HARUS	SEBAIKNYA	SEBAIKNYA	SEBAIKNYA
	Mode periferal/host USB	7.7. USB	SEBAIKNYA			SEBAIKNYA	SEBAIKNYA
Keluaran	Port speaker dan/atau output Audio	7.8.2. Keluaran Audio	HARUS	HARUS		HARUS	HARUS

3. Perangkat Lunak

3.1. Kompatibilitas API Terkelola

Lingkungan eksekusi bytecode Dalvik yang dikelola adalah sarana utama untuk aplikasi Android. Antarmuka pemrograman aplikasi (API) Android adalah kumpulan antarmuka platform Android yang diekspos ke aplikasi yang berjalan di lingkungan runtime terkelola. Implementasi perangkat HARUS menyediakan implementasi lengkap, termasuk semua perilaku yang terdokumentasi, dari setiap API terdokumentasi yang diekspos oleh Android SDK [ Sumber Daya, 6 ] atau API apa pun yang diberi penanda “@SystemApi” di kode sumber Android upstream.

Implementasi perangkat TIDAK BOLEH menghilangkan API terkelola apa pun, mengubah antarmuka atau tanda tangan API, menyimpang dari perilaku yang terdokumentasi, atau menyertakan larangan pengoperasian, kecuali jika diizinkan secara khusus oleh Definisi Kompatibilitas ini.

Definisi Kompatibilitas ini mengizinkan beberapa jenis perangkat keras yang Android menyertakan API untuk dihilangkan oleh implementasi perangkat. Dalam kasus seperti ini, API HARUS tetap ada dan berperilaku wajar. Lihat bagian 7 untuk persyaratan khusus untuk skenario ini.

3.2. Kompatibilitas API Lunak

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

3.2.1. Izin

Pelaksana perangkat HARUS mendukung dan menegakkan semua konstanta izin seperti yang didokumentasikan oleh halaman referensi Izin [ Sumber Daya, 7 ]. Perhatikan bahwa bagian 9 mencantumkan persyaratan tambahan terkait model keamanan Android.

3.2.2. Parameter Bangun

Android API menyertakan sejumlah konstanta pada kelas android.os.Build [ Resources, 8 ] yang dimaksudkan untuk mendeskripsikan perangkat saat ini. Untuk memberikan nilai yang konsisten dan bermakna di seluruh penerapan perangkat, tabel di bawah menyertakan batasan tambahan pada format nilai yang HARUS dipatuhi oleh penerapan perangkat.

Parameter	Detail
VERSI. RELEASE	Versi sistem Android yang sedang dijalankan, dalam format yang dapat dibaca manusia. Bidang ini HARUS memiliki salah satu nilai string yang ditentukan di [ Sumber Daya, 9 ].
VERSI.SDK	Versi sistem Android yang sedang dijalankan, dalam format yang dapat diakses oleh kode aplikasi pihak ketiga. Untuk Android 6.0, kolom ini HARUS memiliki nilai integer 23.
VERSI.SDK_INT	Versi sistem Android yang sedang dijalankan, dalam format yang dapat diakses oleh kode aplikasi pihak ketiga. Untuk Android 6.0, kolom ini HARUS memiliki nilai integer 23.
VERSI.INKREMENTAL	Nilai yang dipilih oleh pelaksana perangkat yang menunjuk build spesifik sistem Android yang sedang dijalankan, dalam format yang dapat dibaca manusia. Nilai ini TIDAK BOLEH digunakan kembali untuk build berbeda yang tersedia untuk pengguna akhir. Penggunaan umum bidang ini adalah untuk menunjukkan nomor build atau pengidentifikasi perubahan kontrol sumber mana yang digunakan untuk menghasilkan build. Tidak ada persyaratan mengenai format spesifik bidang ini, kecuali TIDAK HARUS berupa null atau string kosong ("").
PAPAN	Nilai yang dipilih oleh pelaksana perangkat yang mengidentifikasi perangkat keras internal spesifik yang digunakan oleh perangkat, dalam format yang dapat dibaca manusia. Kemungkinan penggunaan bidang ini adalah untuk menunjukkan revisi spesifik pada papan yang memberi daya pada perangkat. Nilai bidang ini HARUS dapat dikodekan sebagai ASCII 7-bit dan cocok dengan ekspresi reguler “^[a-zA-Z0-9_-]+$”.
MEREK	Nilai yang mencerminkan nama merek yang terkait dengan perangkat yang diketahui oleh pengguna akhir. HARUS dalam format yang dapat dibaca manusia dan HARUS mewakili produsen perangkat atau merek perusahaan tempat perangkat tersebut dipasarkan. Nilai bidang ini HARUS dapat dikodekan sebagai ASCII 7-bit dan cocok dengan ekspresi reguler “^[a-zA-Z0-9_-]+$”.
DIDUKUNG_ABIS	Nama set instruksi (tipe CPU + konvensi ABI) dari kode asli. Lihat bagian 3.3. Kompatibilitas API Asli .
DIDUKUNG_32_BIT_ABIS	Nama set instruksi (tipe CPU + konvensi ABI) dari kode asli. Lihat bagian 3.3. Kompatibilitas API Asli .
DIDUKUNG_64_BIT_ABIS	Nama set instruksi kedua (tipe CPU + konvensi ABI) dari kode asli. Lihat bagian 3.3. Kompatibilitas API Asli .
CPU_ABI	Nama set instruksi (tipe CPU + konvensi ABI) dari kode asli. Lihat bagian 3.3. Kompatibilitas API Asli .
CPU_ABI2	Nama set instruksi kedua (tipe CPU + konvensi ABI) dari kode asli. Lihat bagian 3.3. Kompatibilitas API Asli .
PERANGKAT	Nilai yang dipilih oleh pelaksana perangkat yang berisi nama pengembangan atau nama kode yang mengidentifikasi konfigurasi fitur perangkat keras dan desain industri perangkat. Nilai bidang ini HARUS dapat dikodekan sebagai ASCII 7-bit dan cocok dengan ekspresi reguler “^[a-zA-Z0-9_-]+$”.
SIDIK JARI	Sebuah string yang secara unik mengidentifikasi bangunan ini. Itu HARUS dapat dibaca manusia secara wajar. Itu HARUS mengikuti templat ini: $(MEREK)/$(PRODUK)/ $(PERANGKAT):$(VERSION.RELEASE)/$(ID)/$(VERSION.INCREMENTAL):$(TYPE)/$(TAGS) Misalnya: puncak/produk saya/ perangkat saya:6.0/LMYXX/3359:userdebug/test-keys Sidik jari TIDAK HARUS menyertakan karakter spasi. Jika kolom lain yang disertakan dalam template di atas memiliki karakter spasi, maka kolom tersebut HARUS diganti di sidik jari build dengan karakter lain, misalnya karakter garis bawah ("_"). Nilai bidang ini HARUS dapat dikodekan sebagai ASCII 7-bit.
PERANGKAT KERAS	Nama perangkat keras (dari baris perintah kernel atau /proc). Itu HARUS dapat dibaca manusia secara wajar. Nilai bidang ini HARUS dapat dikodekan sebagai ASCII 7-bit dan cocok dengan ekspresi reguler “^[a-zA-Z0-9_-]+$”.
TUAN RUMAH	Sebuah string yang secara unik mengidentifikasi host tempat build dibangun, dalam format yang dapat dibaca manusia. Tidak ada persyaratan mengenai format spesifik bidang ini, kecuali TIDAK HARUS berupa null atau string kosong ("").
PENGENAL	Pengidentifikasi yang dipilih oleh pelaksana perangkat untuk merujuk pada rilis tertentu, dalam format yang dapat dibaca manusia. Kolom ini bisa sama dengan android.os.Build.VERSION.INCREMENTAL, namun HARUS berupa nilai yang cukup bermakna bagi pengguna akhir untuk membedakan build perangkat lunak. Nilai bidang ini HARUS dapat dikodekan sebagai ASCII 7-bit dan cocok dengan ekspresi reguler “^[a-zA-Z0-9._-]+$”.
PABRIKAN	Nama dagang Produsen Peralatan Asli (OEM) produk. Tidak ada persyaratan mengenai format spesifik bidang ini, kecuali TIDAK HARUS berupa null atau string kosong ("").
MODEL	Nilai yang dipilih oleh pelaksana perangkat yang berisi nama perangkat yang diketahui oleh pengguna akhir. Nama ini HARUS sama dengan nama perangkat yang dipasarkan dan dijual kepada pengguna akhir. Tidak ada persyaratan mengenai format spesifik bidang ini, kecuali TIDAK HARUS berupa null atau string kosong ("").
PRODUK	Nilai yang dipilih oleh pelaksana perangkat yang berisi nama pengembangan atau nama kode produk tertentu (SKU) yang HARUS unik dalam merek yang sama. HARUS dapat dibaca manusia, namun tidak dimaksudkan untuk dilihat oleh pengguna akhir. Nilai bidang ini HARUS dapat dikodekan sebagai ASCII 7-bit dan cocok dengan ekspresi reguler “^[a-zA-Z0-9_-]+$”.
SERIAL	Nomor seri perangkat keras, yang HARUS tersedia dan unik di seluruh perangkat dengan MODEL dan PRODUSEN yang sama. Nilai bidang ini HARUS dapat dikodekan sebagai ASCII 7-bit dan cocok dengan ekspresi reguler “^([a-zA-Z0-9]{6,20})$”.
TAG	Daftar tag yang dipisahkan koma yang dipilih oleh pelaksana perangkat yang selanjutnya membedakan build. Bidang ini HARUS memiliki salah satu nilai yang sesuai dengan tiga konfigurasi penandatanganan platform Android pada umumnya: kunci rilis, kunci pengembang, kunci uji.
WAKTU	Nilai yang mewakili stempel waktu saat pembangunan terjadi.
JENIS	Nilai yang dipilih oleh pelaksana perangkat yang menentukan konfigurasi runtime build. Bidang ini HARUS memiliki salah satu nilai yang sesuai dengan tiga konfigurasi waktu proses Android pada umumnya: pengguna, userdebug, atau eng.
PENGGUNA	Nama atau ID pengguna dari pengguna (atau pengguna otomatis) yang menghasilkan build. Tidak ada persyaratan mengenai format spesifik bidang ini, kecuali TIDAK HARUS berupa null atau string kosong ("").
KEAMANAN_PATCH	Nilai yang menunjukkan tingkat patch keamanan suatu build. Ini HARUS menandakan bahwa build tersebut mencakup semua patch keamanan yang dikeluarkan melalui Buletin Keamanan Publik Android yang ditunjuk. Formatnya HARUS, [YYYY-MM-DD], cocok dengan salah satu string Tingkat Patch Keamanan Android dari Buletin Keamanan Publik , misalnya "01-11-2015".
DASAR_OS	Nilai yang mewakili parameter FINGERPRINT build yang identik dengan build ini kecuali untuk patch yang disediakan di Buletin Keamanan Publik Android. Itu HARUS melaporkan nilai yang benar dan jika build tersebut tidak ada, laporkan string kosong ("").

3.2.3. Kompatibilitas Maksud

Implementasi perangkat HARUS mengikuti sistem loose-coupling Android, seperti yang dijelaskan pada bagian di bawah ini. Yang dimaksud dengan “terhormat” adalah bahwa pelaksana perangkat HARUS menyediakan Aktivitas atau Layanan Android yang menentukan filter maksud yang cocok yang mengikat dan mengimplementasikan perilaku yang benar untuk setiap pola maksud yang ditentukan.

3.2.3.1. Maksud Aplikasi Inti

Maksud Android memungkinkan komponen aplikasi meminta fungsionalitas dari komponen Android lainnya. Proyek upstream Android mencakup daftar aplikasi yang dianggap sebagai aplikasi inti Android, yang mengimplementasikan beberapa pola maksud untuk melakukan tindakan umum. Aplikasi inti Android adalah:

Jam Meja
Peramban
Kalender
Kontak
Galeri
Pencarian Global
Peluncur
Musik
Pengaturan

Implementasi perangkat HARUS menyertakan aplikasi inti Android sebagaimana mestinya, namun HARUS menyertakan komponen yang menerapkan pola maksud yang sama yang ditentukan oleh semua komponen Aktivitas atau Layanan “publik” dari aplikasi inti Android ini. Perhatikan bahwa komponen Aktivitas atau Layanan dianggap “publik” jika atribut android:exported tidak ada atau bernilai true.

3.2.3.2. Resolusi Niat

Karena Android adalah platform yang dapat diperluas, implementasi perangkat HARUS mengizinkan setiap pola maksud yang dirujuk di bagian 3.2.3.1 diganti oleh aplikasi pihak ketiga. Implementasi open source Android upstream mengizinkan hal ini secara default; pelaksana perangkat TIDAK BOLEH memberikan hak istimewa khusus pada penggunaan pola maksud ini oleh aplikasi sistem, atau mencegah aplikasi pihak ketiga mengikat dan mengambil kendali atas pola ini. Larangan ini secara khusus mencakup namun tidak terbatas pada menonaktifkan antarmuka pengguna “Pemilih” yang memungkinkan pengguna memilih di antara beberapa aplikasi yang semuanya menangani pola maksud yang sama.

Implementasi perangkat HARUS menyediakan antarmuka pengguna bagi pengguna untuk mengubah aktivitas default untuk maksud.

Namun, penerapan perangkat MUNGKIN menyediakan aktivitas default untuk pola URI tertentu (mis. http://play.google.com) bila aktivitas default menyediakan atribut yang lebih spesifik untuk URI data. Misalnya, pola filter maksud yang menentukan URI data “http://www.android.com” lebih spesifik dibandingkan pola maksud inti browser untuk “http://”.

Android juga menyertakan mekanisme bagi aplikasi pihak ketiga untuk mendeklarasikan perilaku penautan aplikasi default yang otoritatif untuk jenis maksud URI web tertentu [ Sumberdaya, 140 ]. Jika deklarasi otoritatif tersebut ditentukan dalam pola filter maksud aplikasi, implementasi perangkat:

HARUS mencoba memvalidasi filter maksud apa pun dengan melakukan langkah-langkah validasi yang ditentukan dalam spesifikasi Digital Asset Links [ Sumber Daya, 141 ] seperti yang diterapkan oleh Manajer Paket di Proyek Sumber Terbuka Android hulu.
HARUS mencoba validasi filter maksud selama instalasi aplikasi dan menetapkan semua filter maksud UIR yang berhasil divalidasi sebagai pengendali aplikasi default untuk UIRnya.
MUNGKIN menetapkan filter maksud URI tertentu sebagai pengendali aplikasi default untuk URI-nya, jika filter tersebut berhasil diverifikasi tetapi kandidat filter URI lainnya gagal dalam verifikasi. Jika implementasi perangkat melakukan hal ini, implementasi tersebut HARUS memberikan penggantian pola per-URI yang sesuai kepada pengguna di menu pengaturan.
HARUS memberi pengguna kontrol Tautan Aplikasi per aplikasi di Pengaturan sebagai berikut:
- Pengguna HARUS dapat mengganti secara holistik perilaku tautan aplikasi default untuk suatu aplikasi: selalu terbuka, selalu bertanya, atau tidak pernah terbuka, yang harus diterapkan secara merata ke semua kandidat filter maksud URI.
- Pengguna HARUS dapat melihat daftar calon filter maksud URI.
- Implementasi perangkat MUNGKIN memberi pengguna kemampuan untuk mengganti kandidat filter maksud URI tertentu yang berhasil diverifikasi, berdasarkan filter per maksud.
- Penerapan perangkat HARUS memberi pengguna kemampuan untuk melihat dan mengganti filter maksud URI kandidat tertentu jika penerapan perangkat memungkinkan beberapa calon filter maksud URI berhasil dalam verifikasi sementara beberapa lainnya mungkin gagal.

3.2.3.3. Ruang Nama Maksud

Implementasi perangkat TIDAK BOLEH menyertakan komponen Android apa pun yang mengikuti pola maksud baru atau maksud siaran apa pun menggunakan ACTION, CATEGORY, atau string kunci lainnya di namespace android.* atau com.android.*. Implementer perangkat TIDAK BOLEH menyertakan komponen Android apa pun yang mengikuti pola maksud baru atau maksud siaran apa pun menggunakan TINDAKAN, KATEGORI, atau string kunci lainnya dalam ruang paket milik organisasi lain. Pelaksana perangkat TIDAK BOLEH mengubah atau memperluas pola maksud apa pun yang digunakan oleh aplikasi inti yang tercantum di bagian 3.2.3.1 . Implementasi perangkat MUNGKIN mencakup pola maksud menggunakan namespace yang jelas dan jelas terkait dengan organisasinya sendiri. Larangan ini serupa dengan yang ditentukan untuk kelas bahasa Java di bagian 3.6 .

3.2.3.4. Maksud Siaran

Aplikasi pihak ketiga mengandalkan platform untuk menyiarkan maksud tertentu guna memberi tahu mereka tentang perubahan dalam lingkungan perangkat keras atau perangkat lunak. Perangkat yang kompatibel dengan Android HARUS menyiarkan maksud siaran publik sebagai respons terhadap kejadian sistem yang sesuai. Maksud siaran dijelaskan dalam dokumentasi SDK.

3.2.3.5. Pengaturan Aplikasi Default

Android menyertakan pengaturan yang memberi pengguna cara mudah untuk memilih aplikasi default mereka, misalnya untuk Layar Beranda atau SMS. Jika masuk akal, penerapan perangkat HARUS menyediakan menu pengaturan serupa dan kompatibel dengan pola filter maksud dan metode API yang dijelaskan dalam dokumentasi SDK di bawah.

Implementasi perangkat:

HARUS menghormati maksud android.settings.HOME_SETTINGS untuk menampilkan menu pengaturan aplikasi default untuk Layar Beranda, jika implementasi perangkat melaporkan android.software.home_screen [ Sumber Daya, 10 ]
HARUS menyediakan menu pengaturan yang akan memanggil maksud android.provider.Telephony.ACTION_CHANGE_DEFAULT untuk menampilkan dialog untuk mengubah aplikasi SMS default, jika implementasi perangkat melaporkan android.hardware.telephony [ Sumber Daya, 11 ]
HARUS menghormati maksud android.settings.NFC_PAYMENT_SETTINGS untuk menampilkan menu pengaturan aplikasi default untuk Ketuk dan Bayar, jika implementasi perangkat melaporkan android.hardware.nfc.hce [ Sumber Daya, 10 ]

3.3. Kompatibilitas API Asli

3.3.1. Antarmuka Biner Aplikasi

Bytecode Dalvik yang dikelola dapat memanggil kode asli yang disediakan dalam file .apk aplikasi sebagai file ELF .so yang dikompilasi untuk arsitektur perangkat keras perangkat yang sesuai. Karena kode asli sangat bergantung pada teknologi prosesor yang mendasarinya, Android mendefinisikan sejumlah Antarmuka Biner Aplikasi (ABI) di Android NDK. Implementasi perangkat HARUS kompatibel dengan satu atau beberapa ABI yang ditentukan, dan HARUS mengimplementasikan kompatibilitas dengan Android NDK, seperti di bawah ini.

Jika implementasi perangkat menyertakan dukungan untuk Android ABI, maka:

HARUS menyertakan dukungan untuk kode yang berjalan di lingkungan terkelola untuk memanggil kode asli, menggunakan semantik Java Native Interface (JNI) standar
HARUS kompatibel dengan sumber (yaitu kompatibel dengan header) dan kompatibel dengan biner (untuk ABI) dengan setiap pustaka yang diperlukan dalam daftar di bawah
HARUS mendukung ABI 32-bit yang setara jika ada ABI 64-bit yang didukung
HARUS melaporkan secara akurat Antarmuka Biner Aplikasi (ABI) asli yang didukung oleh perangkat, melalui parameter android.os.Build.SUPPORTED_ABIS, android.os.Build.SUPPORTED_32_BIT_ABIS, dan android.os.Build.SUPPORTED_64_BIT_ABIS, masing-masing dalam daftar yang dipisahkan koma ABI diurutkan dari yang paling disukai hingga yang paling tidak disukai
HARUS melaporkan, melalui parameter di atas, hanya ABI yang didokumentasikan dan dijelaskan dalam versi terbaru dokumentasi Manajemen ABI Android NDK [ Sumber Daya, 12 ], dan HARUS menyertakan dukungan untuk ekstensi SIMD Tingkat Lanjut (alias NEON) [ Sumber Daya, 13 ]
HARUS dibuat menggunakan kode sumber dan file header yang tersedia di Proyek Sumber Terbuka Android upstream

API kode asli berikut HARUS tersedia untuk aplikasi yang menyertakan kode asli:

libc (perpustakaan C)
libm (perpustakaan matematika)
Dukungan minimal untuk C++
antarmuka JNI
liblog (pencatatan Android)
libz (kompresi Zlib)
libdl (penghubung dinamis)
libGLESv1_CM.so (OpenGL ES 1.x)
libGLESv2.so (OpenGL ES 2.0)
libGLESv3.so (OpenGL ES 3.x)
libEGL.so (manajemen permukaan OpenGL asli)
libjnigraphics.so
libOpenSLES.so (dukungan audio OpenSL ES 1.0.1)
libOpenMAXAL.so (dukungan OpenMAX AL 1.0.1)
libandroid.so (dukungan aktivitas Android asli)
libmediandk.so (dukungan API media asli)
Dukungan untuk OpenGL, seperti dijelaskan di bawah

Perlu diperhatikan bahwa rilis Android NDK di masa mendatang mungkin memperkenalkan dukungan untuk ABI tambahan. Jika implementasi perangkat tidak kompatibel dengan ABI yang telah ditentukan sebelumnya, maka implementasi tersebut TIDAK BOLEH melaporkan dukungan untuk ABI apa pun sama sekali.

Perhatikan bahwa implementasi perangkat HARUS menyertakan libGLESv3.so dan HARUS menghubungkan simbol (tautan simbolis) ke libGLESv2.so. pada gilirannya, HARUS mengekspor semua simbol fungsi OpenGL ES 3.1 dan Android Extension Pack [ Resources, 14 ] seperti yang didefinisikan dalam rilis NDK android-21. Meskipun semua simbol harus ada, hanya fungsi terkait untuk versi OpenGL ES dan ekstensi yang benar-benar didukung oleh perangkat yang harus diterapkan sepenuhnya.

Implementasi perangkat, jika menyertakan perpustakaan asli dengan nama libvulkan.so, HARUS mengekspor simbol fungsi dan menyediakan implementasi API Vulkan 1.0 dan ekstensi VK_KHR_surface, VK_KHR_swapchain, dan VK_KHR_android_surface seperti yang ditentukan oleh Grup Khronos dan lulus uji kesesuaian Khronos.

Kompatibilitas kode asli merupakan suatu tantangan. Oleh karena itu, pelaksana perangkat SANGAT DIREKOMENDASIKAN untuk menggunakan implementasi pustaka yang tercantum di atas dari Proyek Sumber Terbuka Android hulu.

3.3.2. Kompatibilitas Kode Asli ARM 32-bit

Arsitektur ARMv8 tidak lagi menggunakan beberapa operasi CPU, termasuk beberapa operasi yang digunakan dalam kode asli yang sudah ada. Pada perangkat ARM 64-bit, operasi yang tidak berlaku lagi berikut ini HARUS tetap tersedia untuk kode ARM asli 32-bit, baik melalui dukungan CPU asli atau melalui emulasi perangkat lunak:

Instruksi SWP dan SWPB
instruksi SETEND
Operasi penghalang CP15ISB, CP15DSB, dan CP15DMB

Versi lama Android NDK menggunakan /proc/cpuinfo untuk menemukan fitur CPU dari kode asli ARM 32-bit. Agar kompatibel dengan aplikasi yang dibuat menggunakan NDK ini, perangkat HARUS menyertakan baris berikut di /proc/cpuinfo saat dibaca oleh aplikasi ARM 32-bit:

"Fitur:", diikuti dengan daftar fitur CPU ARMv7 opsional yang didukung oleh perangkat
"Arsitektur CPU:", diikuti dengan bilangan bulat yang menjelaskan arsitektur ARM tertinggi yang didukung perangkat (misalnya, "8" untuk perangkat ARMv8)

Persyaratan ini hanya berlaku ketika /proc/cpuinfo dibaca oleh aplikasi ARM 32-bit. Perangkat TIDAK BOLEH mengubah /proc/cpuinfo saat dibaca oleh aplikasi ARM atau non-ARM 64-bit.

3.4. Kompatibilitas Web

3.4.1. Kompatibilitas Tampilan Web

Perangkat Android Watch MUNGKIN, namun semua implementasi perangkat lainnya HARUS menyediakan implementasi lengkap dari android.webkit.Webview API.

Fitur platform android.software.webview HARUS dilaporkan pada perangkat apa pun yang menyediakan implementasi lengkap API android.webkit.WebView, dan TIDAK HARUS dilaporkan pada perangkat tanpa implementasi API yang lengkap. Implementasi Android Open Source menggunakan kode dari Proyek Chromium untuk mengimplementasikan android.webkit.WebView [ Resources, 15 ]. Karena tidak layak untuk mengembangkan rangkaian pengujian komprehensif untuk sistem rendering web, pelaksana perangkat HARUS menggunakan versi hulu Chromium yang spesifik dalam implementasi WebView. Secara khusus:

Implementasi perangkat android.webkit.WebView HARUS didasarkan pada build Chromium dari Proyek Sumber Terbuka Android upstream untuk Android 6.0. Versi ini mencakup serangkaian fungsionalitas dan perbaikan keamanan khusus untuk WebView [ Sumber Daya, 16 ].
String agen pengguna yang dilaporkan oleh WebView HARUS dalam format ini:
Mozilla/5.0 (Linux; Android $(VERSION); $(MODEL) Build/$(BUILD); wv) AppleWebKit/537.36 (KHTML, seperti Gecko) Version/4.0 $(CHROMIUM_VER) Mobile Safari/537.36
- Nilai string $(VERSION) HARUS sama dengan nilai untuk android.os.Build.VERSION.RELEASE.
- Nilai string $(MODEL) HARUS sama dengan nilai untuk android.os.Build.MODEL.
- Nilai string $(BUILD) HARUS sama dengan nilai untuk android.os.Build.ID.
- Nilai string $(CHROMIUM_VER) HARUS versi Chromium di Proyek Sumber Terbuka Android upstream.
- Implementasi perangkat MUNGKIN menghilangkan Seluler dalam string agen pengguna.

Komponen WebView HARUS menyertakan dukungan untuk sebanyak mungkin fitur HTML5 dan jika mendukung fitur tersebut HARUS sesuai dengan spesifikasi HTML5 [ Sumberdaya, 17 ].

3.4.2. Kompatibilitas Peramban

Implementasi Android Television, Watch, dan Android Automotive MUNGKIN menghilangkan aplikasi browser, namun HARUS mendukung pola niat publik seperti yang dijelaskan di bagian 3.2.3.1 . Semua jenis implementasi perangkat lainnya HARUS menyertakan aplikasi Browser mandiri untuk penelusuran web pengguna umum.

Browser mandiri MUNGKIN didasarkan pada teknologi browser selain WebKit. Namun, meskipun aplikasi Browser alternatif digunakan, komponen android.webkit.WebView yang disediakan untuk aplikasi pihak ketiga HARUS berbasis WebKit, seperti dijelaskan di bagian 3.4.1 .

Implementasi MUNGKIN mengirimkan string agen pengguna khusus dalam aplikasi Browser mandiri.

Aplikasi Browser mandiri (baik berdasarkan aplikasi Browser WebKit upstream atau pengganti pihak ketiga) HARUS menyertakan dukungan untuk HTML5 sebanyak mungkin [ Sumber Daya, 17 ] . Minimal, implementasi perangkat HARUS mendukung setiap API yang terkait dengan HTML5 berikut:

cache aplikasi/operasi offline [ Sumber Daya, 18 ]
tag <video> [ Sumber Daya, 19 ]
geolokasi [ Sumber Daya, 20 ]

Selain itu, implementasi perangkat HARUS mendukung API penyimpanan web HTML5/W3C [ Sumber Daya, 21 ], dan HARUS mendukung API IndexedDB HTML5/W3C [ Sumber Daya, 22 ]. Perlu diperhatikan bahwa seiring dengan transisi badan standar pengembangan web yang lebih mengutamakan IndexedDB dibandingkan penyimpanan web, IndexedDB diperkirakan akan menjadi komponen wajib dalam versi Android mendatang.

3.5. Kompatibilitas Perilaku API

Perilaku masing-masing jenis API (terkelola, lunak, asli, dan web) harus konsisten dengan implementasi pilihan Proyek Sumber Terbuka Android upstream [ Sumber Daya, 2 ]. Beberapa area kompatibilitas tertentu adalah:

Perangkat TIDAK BOLEH mengubah perilaku atau semantik maksud standar.
Perangkat TIDAK BOLEH mengubah semantik siklus hidup atau siklus hidup jenis komponen sistem tertentu (seperti Layanan, Aktivitas, ContentProvider, dll.).
Perangkat TIDAK HARUS mengubah semantik izin standar.

Daftar di atas tidak lengkap. Compatibility Test Suite (CTS) menguji sebagian besar platform untuk kompatibilitas perilaku, namun tidak semuanya. Implementer bertanggung jawab memastikan kompatibilitas perilaku dengan Proyek Sumber Terbuka Android. Oleh karena itu, pelaksana perangkat HARUS menggunakan kode sumber yang tersedia melalui Proyek Sumber Terbuka Android jika memungkinkan, daripada mengimplementasikan ulang bagian penting dari sistem.

3.6. Ruang Nama API

Android mengikuti konvensi namespace paket dan kelas yang ditentukan oleh bahasa pemrograman Java. Untuk memastikan kompatibilitas dengan aplikasi pihak ketiga, pelaksana perangkat TIDAK BOLEH melakukan modifikasi apa pun yang dilarang (lihat di bawah) pada namespace paket ini:

Jawa.*
javax.*
matahari.*
android.*
com.android.*

Modifikasi yang dilarang antara lain :

Implementasi perangkat TIDAK BOLEH mengubah API yang diekspos secara publik di platform Android dengan mengubah metode atau tanda tangan kelas apa pun, atau dengan menghapus kelas atau kolom kelas.
Pelaksana perangkat MUNGKIN memodifikasi implementasi dasar API, namun modifikasi tersebut TIDAK BOLEH berdampak pada perilaku yang dinyatakan dan tanda tangan bahasa Java dari API apa pun yang diekspos secara publik.
Pelaksana perangkat TIDAK BOLEH menambahkan elemen apa pun yang diekspos secara publik (seperti kelas atau antarmuka, atau bidang atau metode ke kelas atau antarmuka yang ada) ke API di atas.

“Elemen yang diekspos secara publik” adalah konstruksi apa pun yang tidak dihiasi dengan penanda “@hide” seperti yang digunakan dalam kode sumber Android upstream. Dengan kata lain, pelaksana perangkat TIDAK BOLEH mengekspos API baru atau mengubah API yang sudah ada di namespace yang disebutkan di atas. Pelaksana perangkat MUNGKIN melakukan modifikasi internal saja, namun modifikasi tersebut TIDAK BOLEH diiklankan atau diekspos ke pengembang.

Pelaksana perangkat MUNGKIN menambahkan API khusus, namun API tersebut TIDAK BOLEH berada dalam namespace yang dimiliki atau mengacu pada organisasi lain. Misalnya, pelaksana perangkat TIDAK BOLEH menambahkan API ke com.google.* atau namespace serupa: hanya Google yang boleh melakukannya. Demikian pula, Google TIDAK BOLEH menambahkan API ke namespace perusahaan lain. Selain itu, jika implementasi perangkat menyertakan API khusus di luar namespace Android standar, API tersebut HARUS dikemas dalam pustaka bersama Android sehingga hanya aplikasi yang menggunakannya secara eksplisit (melalui mekanisme lt;uses-librarygt;) yang terpengaruh oleh peningkatan memori penggunaan API tersebut.

Jika pelaksana perangkat mengusulkan untuk meningkatkan salah satu namespace paket di atas (misalnya dengan menambahkan fungsi baru yang berguna ke API yang sudah ada, atau menambahkan API baru), pelaksana HARUS mengunjungi source.android.com dan memulai proses untuk memberikan kontribusi perubahan dan kode, menurut informasi di situs itu.

Perhatikan bahwa batasan di atas sesuai dengan konvensi standar untuk penamaan API dalam bahasa pemrograman Java; bagian ini hanya bertujuan untuk memperkuat konvensi tersebut dan menjadikannya mengikat melalui penyertaan dalam Definisi Kompatibilitas ini.

3.7. Kompatibilitas Waktu Proses

Implementasi perangkat HARUS mendukung format penuh Dalvik Executable (DEX) serta spesifikasi bytecode dan semantik Dalvik [ Sumber Daya, 23 ]. Pelaksana perangkat HARUS menggunakan ART, implementasi hulu referensi dari Dalvik Executable Format, dan sistem manajemen paket implementasi referensi.

Implementasi perangkat harus mengkonfigurasi Dalvik RunTimes untuk mengalokasikan memori sesuai dengan platform Android hulu, dan sebagaimana ditentukan oleh tabel berikut. (Lihat bagian 7.1.1 untuk mengetahui ukuran layar dan definisi kepadatan layar.)

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

Tata Letak Layar	Kepadatan Layar	Memori Aplikasi Minimum
Arloji android	120 dpi (LDPI)	32MB
	160 dpi (mdpi)
	213 DPI (TVDPI)
	240dpi (hdpi)	36MB
	280 dpi (280dpi)	36MB
	320dpi (xhdpi)	48MB
	360 DPI (360DPI)	48MB
	400 dpi (400dpi)	56MB
	420dpi (420dpi)	64MB
	480 dpi (xxhdpi)	88MB
	560 DPI (560DPI)	112MB
	640 dpi (xxxhdpi)	154MB
kecil/biasa	120 dpi (LDPI)	32MB
	160 dpi (mdpi)	32MB
	213 DPI (TVDPI)	48MB
	240dpi (hdpi)
	280 dpi (280dpi)
	320dpi (xhdpi)	80MB
	360 DPI (360DPI)	80MB
	400 dpi (400dpi)	96MB
	420dpi (420dpi)	112MB
	480 dpi (xxhdpi)	128MB
	560 DPI (560DPI)	192MB
	640 dpi (xxxhdpi)	256MB
besar	120 dpi (LDPI)	32MB
	160 dpi (mdpi)	48MB
	213 DPI (TVDPI)	80MB
	240dpi (hdpi)	80MB
	280 dpi (280dpi)	96MB
	320dpi (xhdpi)	128MB
	360 DPI (360DPI)	160MB
	400 dpi (400dpi)	192MB
	420dpi (420dpi)	228MB
	480 dpi (xxhdpi)	256MB
	560 DPI (560DPI)	384MB
	640 dpi (xxxhdpi)	512MB
xbesar	120 dpi (LDPI)	48MB
	160 dpi (mdpi)	80MB
	213 DPI (TVDPI)	96MB
	240dpi (hdpi)	96MB
	280 dpi (280dpi)	144MB
	320dpi (xhdpi)	192MB
	360 DPI (360DPI)	240MB
	400 dpi (400dpi)	288MB
	420dpi (420dpi)	336MB
	480 dpi (xxhdpi)	384MB
	560 DPI (560DPI)	576MB
	640 dpi (xxxhdpi)	768MB

3.8. Kompatibilitas Antarmuka Pengguna

3.8.1. Peluncur (Layar Beranda)

Android menyertakan aplikasi peluncur (layar beranda) dan dukungan aplikasi pihak ketiga untuk menggantikan peluncur perangkat (layar beranda). Implementasi perangkat yang memungkinkan aplikasi pihak ketiga untuk mengganti layar beranda perangkat harus mendeklarasikan fitur platform android.software.home_screen.

3.8.2. Widget

Widget adalah opsional untuk semua implementasi perangkat Android, tetapi harus didukung pada perangkat genggam Android.

Android mendefinisikan jenis komponen dan API dan siklus hidup yang sesuai yang memungkinkan aplikasi untuk mengekspos "appwidget" ke pengguna akhir [ sumber daya, 24 ] fitur yang sangat disarankan untuk didukung pada implementasi perangkat genggam. Implementasi perangkat yang mendukung penyembatan widget di layar beranda harus memenuhi persyaratan berikut dan mendeklarasikan dukungan untuk fitur platform android.software.app_widgets.

Peluncur perangkat harus menyertakan dukungan bawaan untuk AppWidgets, dan mengekspos keterjangkauan antarmuka pengguna untuk menambah, mengkonfigurasi, melihat, dan menghapus APPWIDGET secara langsung di dalam peluncur.
Implementasi perangkat harus mampu rendering widget yang 4 x 4 dalam ukuran grid standar. Lihat Pedoman Desain Widget Aplikasi dalam dokumentasi Android SDK [ Sumber Daya, 24 ] untuk detailnya.
Implementasi perangkat yang mencakup dukungan untuk layar kunci dapat mendukung widget aplikasi pada layar kunci.

3.8.3. Pemberitahuan

Android termasuk API yang memungkinkan pengembang untuk memberi tahu pengguna tentang acara terkenal [ Sumber Daya, 25 ], menggunakan fitur perangkat keras dan perangkat lunak perangkat.

Beberapa API memungkinkan aplikasi untuk melakukan pemberitahuan atau menarik perhatian menggunakan perangkat keras - khususnya suara, getaran, dan cahaya. Implementasi perangkat harus mendukung pemberitahuan yang menggunakan fitur perangkat keras, seperti yang dijelaskan dalam dokumentasi SDK, dan sejauh mungkin dengan perangkat keras implementasi perangkat. Misalnya, jika implementasi perangkat menyertakan vibrator, maka perangkat tersebut HARUS mengimplementasikan API getaran dengan benar. Jika implementasi perangkat tidak memiliki perangkat keras, API terkait HARUS diimplementasikan sebagai tanpa operasi. Perilaku ini dirinci lebih lanjut di bagian 7 .

Selain itu, implementasi harus dengan benar membuat semua sumber daya (ikon, file animasi, dll.) Disediakan dalam API [ Sumber Daya, 26 ], atau dalam Panduan Gaya Ikon Status/Sistem [ Sumber Daya, 27 ], yang dalam kasus sebuah Perangkat televisi Android mencakup kemungkinan untuk tidak menampilkan pemberitahuan. Pelaksana perangkat dapat memberikan pengalaman pengguna alternatif untuk pemberitahuan daripada yang disediakan oleh referensi implementasi sumber terbuka Android; Namun, sistem pemberitahuan alternatif tersebut harus mendukung sumber daya pemberitahuan yang ada, seperti di atas.

Android termasuk dukungan untuk berbagai pemberitahuan, seperti:

Pemberitahuan yang kaya . Tampilan interaktif untuk pemberitahuan yang sedang berlangsung.
Pemberitahuan Kepala . Tampilan interaktif yang dapat ditindaklanjuti oleh pengguna atau menepis tanpa meninggalkan aplikasi saat ini.
Pemberitahuan LockScreen . Pemberitahuan yang ditampilkan di atas layar kunci dengan kontrol granular pada visibilitas.

Implementasi perangkat Android, ketika pemberitahuan tersebut dibuat terlihat, harus dengan benar mengeksekusi pemberitahuan yang kaya dan head-up dan memasukkan judul/nama, ikon, teks seperti yang didokumentasikan dalam API Android [ Sumber Daya, 28 ].

Android termasuk API layanan pendengar pemberitahuan yang memungkinkan aplikasi (setelah diaktifkan secara eksplisit oleh pengguna) untuk menerima salinan semua pemberitahuan saat diposting atau diperbarui. Implementasi perangkat harus segera dan segera mengirim pemberitahuan secara keseluruhan ke semua layanan pendengar yang diinstal dan pengguna tersebut, termasuk setiap dan semua metadata yang dilampirkan pada objek pemberitahuan.

3.8.4. Mencari

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

Implementasi perangkat Android harus mencakup pencarian global, antarmuka pengguna pencarian satu, bersama, yang mampu melakukan saran real-time sebagai tanggapan terhadap input pengguna. Implementasi perangkat harus mengimplementasikan API yang memungkinkan pengembang untuk menggunakan kembali antarmuka pengguna ini untuk memberikan pencarian dalam aplikasi mereka sendiri. Implementasi perangkat yang mengimplementasikan antarmuka pencarian global harus mengimplementasikan API yang memungkinkan aplikasi pihak ketiga untuk menambahkan saran ke kotak pencarian saat dijalankan dalam mode pencarian global. Jika tidak ada aplikasi pihak ketiga yang diinstal yang memanfaatkan fungsi ini, perilaku default harus menampilkan hasil dan saran mesin pencari web.

Implementasi perangkat Android harus mengimplementasikan asisten pada perangkat untuk menangani tindakan bantuan [ sumber daya, 30 ].

Android juga mencakup API Assist untuk memungkinkan aplikasi untuk memilih berapa banyak informasi dari konteks saat ini dibagikan dengan asisten pada perangkat [ Sumber Daya, 31 ]. Implementasi perangkat yang mendukung tindakan bantuan harus menunjukkan dengan jelas kepada pengguna akhir ketika konteks dibagikan dengan menampilkan lampu putih di sekitar tepi layar. Untuk memastikan visibilitas yang jelas kepada pengguna akhir, indikasi harus memenuhi atau melampaui durasi dan kecerahan implementasi proyek sumber terbuka Android.

3.8.5. Bersulang

Aplikasi dapat menggunakan API "Toast" untuk menampilkan string non-modal pendek kepada pengguna akhir, yang menghilang setelah periode waktu yang singkat [ Sumber Daya, 32 ]. Implementasi perangkat harus menampilkan roti panggang dari aplikasi ke pengguna akhir dengan cara visibilitas tinggi.

3.8.6. Tema

Android menyediakan “tema” sebagai mekanisme bagi aplikasi untuk menerapkan gaya di seluruh Aktivitas atau aplikasi.

Android termasuk keluarga tema "holo" sebagai satu set gaya yang ditentukan untuk digunakan pengembang aplikasi jika mereka ingin mencocokkan tampilan dan nuansa tema holo sebagaimana didefinisikan oleh Android SDK [ Sumber Daya, 33 ]. Implementasi perangkat tidak boleh mengubah atribut tema holo yang terpapar pada aplikasi [ Sumber Daya, 34 ].

Android mencakup keluarga tema "materi" sebagai satu set gaya yang ditentukan untuk digunakan pengembang aplikasi jika mereka ingin mencocokkan tampilan dan nuansa tema desain di berbagai jenis perangkat Android yang berbeda. Implementasi perangkat harus mendukung keluarga tema "materi" dan tidak boleh mengubah atribut tema material atau asetnya yang terpapar pada aplikasi [ sumber daya, 35 ].

Android juga mencakup keluarga tema "Deveult Default" sebagai satu set gaya yang ditentukan untuk digunakan pengembang aplikasi jika mereka ingin mencocokkan tampilan dan nuansa tema perangkat sebagaimana didefinisikan oleh pelaksana perangkat. Implementasi perangkat dapat memodifikasi atribut tema default perangkat yang terpapar pada aplikasi [ sumber daya, 34 ].

Android mendukung tema varian dengan bilah sistem tembus cahaya, yang memungkinkan pengembang aplikasi untuk mengisi area di belakang status dan bilah navigasi dengan konten aplikasi mereka. Untuk mengaktifkan pengalaman pengembang yang konsisten dalam konfigurasi ini, penting gaya ikon bilah status dipertahankan di berbagai implementasi perangkat. Oleh karena itu, implementasi perangkat Android harus menggunakan White untuk ikon status sistem (seperti kekuatan sinyal dan tingkat baterai) dan pemberitahuan yang dikeluarkan oleh sistem, kecuali ikon tersebut menunjukkan status bermasalah atau aplikasi meminta bilah status lampu menggunakan bendera System_UI_FLAG_LIGN_STOTUS_BAR. Ketika sebuah aplikasi meminta bilah status cahaya, implementasi perangkat Android harus mengubah warna ikon status sistem menjadi hitam [ sumber daya, 34 ].

3.8.7. Wallpaper Hidup

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

Perangkat keras dianggap mampu menjalankan wallpaper hidup dengan andal jika dapat menjalankan semua wallpaper hidup, tanpa batasan fungsionalitas, pada kecepatan bingkai yang wajar tanpa efek buruk pada aplikasi lain. Jika keterbatasan pada perangkat keras menyebabkan wallpaper dan/atau aplikasi mogok, tidak berfungsi, menghabiskan daya CPU atau baterai secara berlebihan, atau berjalan pada kecepatan bingkai yang sangat rendah, perangkat keras tersebut dianggap tidak mampu menjalankan wallpaper hidup. Sebagai contoh, beberapa wallpaper animasi mungkin menggunakan konteks OpenGL 2.0 atau 3.x untuk merender kontennya. Wallpaper hidup tidak akan berjalan dengan andal pada perangkat keras yang tidak mendukung beberapa konteks OpenGL karena penggunaan wallpaper hidup dalam konteks OpenGL mungkin bertentangan dengan aplikasi lain yang juga menggunakan konteks OpenGL.

Implementasi perangkat yang mampu menjalankan wallpaper langsung dengan andal seperti yang dijelaskan di atas harus mengimplementasikan wallpaper hidup, dan ketika diimplementasikan harus melaporkan fitur platform bendera android.software.live_wallpaper.

3.8.8. Peralihan Aktivitas

Karena kunci navigasi fungsi terbaru adalah opsional, persyaratan untuk mengimplementasikan layar ikhtisar adalah opsional untuk perangkat televisi Android dan perangkat Android Watch.

Kode sumber Android hulu mencakup layar ikhtisar [ Sumber Daya, 37 ], antarmuka pengguna tingkat sistem untuk pengalihan tugas dan menampilkan aktivitas dan tugas yang baru diakses menggunakan gambar thumbnail dari keadaan grafik aplikasi pada saat pengguna terakhir kali meninggalkan aplikasi. Implementasi Perangkat Termasuk Kunci Navigasi Fungsi REST sebagaimana dirinci dalam Bagian 7.2.3 , dapat mengubah antarmuka tetapi harus memenuhi persyaratan berikut:

Harus menampilkan resent yang berafiliasi sebagai kelompok yang bergerak bersama.
Harus mendukung setidaknya hingga 6 kegiatan yang ditampilkan.
Setidaknya HARUS menampilkan judul 4 aktivitas sekaligus.
Harus menampilkan warna sorotan, ikon, judul layar dalam resents.
Harus mengimplementasikan perilaku pinning layar [ sumber daya, 38 ] dan memberi pengguna menu pengaturan untuk beralih fitur.
HARUS menampilkan keterjangkauan penutup ("x") tetapi MUNGKIN menundanya hingga pengguna berinteraksi dengan layar.

Implementasi perangkat sangat disarankan untuk menggunakan antarmuka pengguna Android hulu (atau antarmuka berbasis thumbnail serupa) untuk layar ikhtisar.

3.8.9. Manajemen Masukan

Android termasuk dukungan untuk manajemen input dan dukungan untuk editor metode input pihak ketiga [ Sumber Daya, 39 ]. Implementasi perangkat yang memungkinkan pengguna untuk menggunakan metode input pihak ketiga pada perangkat harus mendeklarasikan fitur platform android.software.input_methods dan mendukung IME API sebagaimana didefinisikan dalam dokumentasi Android SDK.

Implementasi perangkat yang mendeklarasikan fitur android.software.input_methods harus memberikan mekanisme yang dapat diakses pengguna untuk menambah dan mengonfigurasi metode input pihak ketiga. Implementasi Perangkat harus menampilkan antarmuka Pengaturan sebagai respons terhadap intent android.settings.input_method_settings.

3.8.10. Kontrol Media Layar Kunci

API Klien Kontrol Jarak Jauh sudah usang dari Android 5.0 yang mendukung templat pemberitahuan media yang memungkinkan aplikasi media untuk berintegrasi dengan kontrol pemutaran yang ditampilkan pada layar kunci [ sumber daya, 40 ] sebagai pemberitahuan layar kunci. Implementasi perangkat harus membuat templat pemberitahuan media dengan benar sebagai bagian dari pemberitahuan layar kunci yang dijelaskan dalam Bagian 3.8.3.

3.8.11. Mimpi

Android termasuk dukungan untuk screensavers interaktif yang disebut Dreams [ Resources, 41 ]. Mimpi memungkinkan pengguna untuk berinteraksi dengan aplikasi ketika perangkat yang terhubung ke sumber daya menganggur atau merapat di dermaga meja. Perangkat Android Watch dapat menerapkan mimpi, tetapi jenis implementasi perangkat lainnya harus mencakup dukungan untuk mimpi dan menyediakan opsi pengaturan bagi pengguna untuk mengonfigurasi mimpi sebagai tanggapan terhadap intent android.settings.dream_settings.

3.8.12. Lokasi

Ketika perangkat memiliki sensor perangkat keras (misalnya GPS) yang mampu memberikan koordinat lokasi, mode lokasi harus ditampilkan di menu lokasi dalam pengaturan [ Sumber Daya, 42 ].

3.8.13. Unicode dan Font

Android termasuk dukungan untuk karakter emoji warna. Ketika implementasi perangkat Android menyertakan IME, perangkat harus memberikan metode input kepada pengguna untuk karakter emoji yang ditentukan dalam Unicode 6.1 [ Sumber Daya, 43 ]. Semua perangkat harus mampu membuat karakter emoji ini dalam mesin terbang warna.

Android termasuk dukungan untuk roboto 2 font dengan bobot yang berbeda-SANS-serif-thin, sans-serif-light, sans-serif-medium, sans-serif-black, sans-serif-condensed, sans-serif-condensed-light-yang- Semua harus disertakan untuk bahasa yang tersedia di perangkat dan cakupan Latin, Yunani, dan Cyrillic yang lengkap, termasuk rentang Latin yang diperluas A, B, C, dan D, dan semua mesin terbang di blok simbol mata uang Unicode 7.0.

3.9. Administrasi Perangkat

Android mencakup fitur yang memungkinkan aplikasi yang sadar keamanan untuk melakukan fungsi administrasi perangkat di tingkat sistem, seperti menegakkan kebijakan kata sandi atau melakukan penghapusan jarak jauh, melalui API Administrasi Perangkat Android [ Sumber Daya, 44 ]. Implementasi perangkat harus memberikan implementasi kelas DevicePolicyManager [ Sumber Daya, 45 ]. Implementasi perangkat yang mencakup dukungan untuk layar kunci berbasis PIN (numerik) atau kata sandi (alfanumerik) harus mendukung berbagai kebijakan administrasi perangkat yang ditentukan dalam dokumentasi Android SDK [ Sumber Daya, 44 ] dan melaporkan fitur platform android.software.device_admin.

3.9.1 Penyediaan Perangkat

3.9.1.1 Penyediaan Pemilik Perangkat

Jika implementasi perangkat mendeklarasikan fitur android.software.device_admin, aliran pengaturan di luar kotak harus memungkinkan untuk mendaftarkan aplikasi pengontrol kebijakan perangkat (DPC) sebagai aplikasi pemilik perangkat [ sumber daya, 46 ]. Implementasi perangkat dapat memiliki fungsi aplikasi yang telah diinstal sebelumnya, tetapi aplikasi ini tidak boleh ditetapkan sebagai aplikasi pemilik perangkat tanpa persetujuan atau tindakan eksplisit dari pengguna atau administrator perangkat.

Proses penyediaan pemilik perangkat (aliran yang diprakarsai oleh android.app.action.provision_managed_device [ sumber daya, 47 ]) pengalaman pengguna harus selaras dengan implementasi AOSP

Jika implementasi perangkat melaporkan android.hardware.nfc, ia harus mengaktifkan NFC, bahkan selama aliran pengaturan out-of-box, untuk memungkinkan penyediaan NFC dari pemilik perangkat [ sumber daya, 48 ].

3.9.1.2 Penyediaan profil yang dikelola

Jika implementasi perangkat mendeklarasikan Android.software.Managed_Users, harus dimungkinkan untuk mendaftarkan aplikasi Pengontrol Kebijakan Perangkat (DPC) sebagai pemilik profil terkelola baru [ sumber daya, 49 ]

Proses penyediaan profil yang dikelola (aliran yang diprakarsai oleh android.app.action.provision_managed_profile [ sumber daya, 50 ]) pengalaman pengguna harus selaras dengan implementasi AOSP

3.9.2 Dukungan profil yang dikelola

Profil yang Dikelola Perangkat Mampu adalah perangkat yang:

Deklarasikan android.software.device_admin (lihat Bagian 3.9 Administrasi Perangkat)
Bukan perangkat RAM rendah (lihat Bagian 7.6.1
Alokasikan penyimpanan internal (tidak dapat dilepas) sebagai penyimpanan bersama (lihat Bagian 7.6.2 )

Profil yang Dikelola Perangkat Mampu harus:

Deklarasikan fitur platform flag android.software.managed_users.
Dukungan Profil Terkelola melalui Android.App.Admin.DevicePolicyManager API
Izinkan satu dan hanya satu profil yang dikelola untuk dibuat [ sumber daya, 50 ]
Gunakan Lencana Ikon (Mirip dengan Lencana Pekerjaan Hulu AOSP) untuk mewakili aplikasi dan widget yang dikelola dan elemen UI lencana lainnya seperti RESEN & NOTIFIKASI
Tampilkan Ikon Pemberitahuan (Mirip dengan Lencana Pekerjaan Hulu AOSP) untuk menunjukkan kapan pengguna berada dalam aplikasi profil yang dikelola
Tampilkan roti panggang yang menunjukkan bahwa pengguna berada di profil yang dikelola jika dan ketika perangkat bangun (action_user_present) dan aplikasi latar depan berada dalam profil yang dikelola
Di mana ada profil yang dikelola, tunjukkan keterjangkauan visual dalam niat 'pemilih' untuk memungkinkan pengguna meneruskan niat dari profil yang dikelola ke pengguna utama atau sebaliknya, jika diaktifkan oleh pengontrol kebijakan perangkat
Di mana ada profil yang dikelola, paparkan keterjangkauan pengguna berikut untuk pengguna utama dan profil yang dikelola:
- Akuntansi terpisah untuk baterai, lokasi, data seluler, dan penggunaan penyimpanan untuk pengguna utama dan profil yang dikelola.
- Manajemen Independen Aplikasi VPN yang diinstal dalam pengguna utama atau profil yang dikelola.
- Manajemen aplikasi independen yang diinstal dalam pengguna pengguna utama atau profil yang dikelola.
- Manajemen akun independen dalam pengguna utama atau profil yang dikelola.
Pastikan dialer default dapat mencari informasi penelepon dari profil yang dikelola (jika ada) di samping yang dari profil utama, jika pengontrol kebijakan perangkat mengizinkannya.
Harus memastikan bahwa itu memenuhi semua persyaratan keamanan yang berlaku untuk perangkat dengan beberapa pengguna diaktifkan (lihat Bagian 9.5 ), meskipun profil yang dikelola tidak dihitung sebagai pengguna lain selain pengguna utama.

3.10. Aksesibilitas

Android menyediakan lapisan aksesibilitas yang membantu pengguna penyandang cacat untuk menavigasi perangkat mereka dengan lebih mudah. Selain itu, Android menyediakan API platform yang memungkinkan implementasi layanan aksesibilitas untuk menerima panggilan balik untuk acara pengguna dan sistem dan menghasilkan mekanisme umpan balik alternatif, seperti teks-ke-ucapan, umpan balik haptic, dan navigasi trackball/d-pad [ Sumber Daya, 51 ].

Implementasi perangkat termasuk persyaratan berikut:

Implementasi otomotif Android harus memberikan implementasi kerangka aksesibilitas Android yang konsisten dengan implementasi Android default.
Implementasi Perangkat (Android Automotive dikecualikan) harus memberikan implementasi kerangka kerja aksesibilitas android yang konsisten dengan implementasi Android default.
Implementasi Perangkat (Android Automotive Excluded) harus mendukung implementasi layanan aksesibilitas pihak ketiga melalui Android.AccessibilityService API [ Sumber Daya, 52 ]
Implementasi Perangkat (Android Automotive dikecualikan) harus menghasilkan aksesibilitas dan memberikan acara ini ke semua implementasi layanan aksesibilitas terdaftar dengan cara yang konsisten dengan implementasi Android default
Implementasi Perangkat (Android Automotive dan Android Watch Devices tanpa output audio dikecualikan), harus memberikan mekanisme yang dapat diakses pengguna untuk mengaktifkan dan menonaktifkan layanan aksesibilitas, dan harus menampilkan antarmuka ini sebagai respons terhadap niat Android.provider.settings.action_accessibility_settings.

Selain itu, implementasi perangkat harus memberikan implementasi layanan aksesibilitas pada perangkat, dan harus menyediakan mekanisme bagi pengguna untuk mengaktifkan layanan aksesibilitas selama pengaturan perangkat. Implementasi open source dari layanan aksesibilitas tersedia dari proyek bebas mata [ Sumber Daya, 53 ].

3.11. Teks pidato

Android mencakup API yang memungkinkan aplikasi untuk menggunakan layanan teks-ke-speech (TTS) dan memungkinkan penyedia layanan untuk menyediakan implementasi layanan TTS [ sumber daya, 54 ]. Implementasi perangkat yang melaporkan fitur android.hardware.audio.output harus memenuhi persyaratan ini terkait dengan kerangka kerja TTS Android.

Implementasi Otomotif Android:

Harus mendukung API kerangka kerja Android TTS.
Dapat mendukung pemasangan mesin TTS pihak ketiga. Jika didukung, mitra harus menyediakan antarmuka yang dapat diakses pengguna yang memungkinkan pengguna untuk memilih mesin TTS untuk digunakan di tingkat sistem.

Semua implementasi perangkat lainnya:

Harus mendukung API kerangka kerja Android TTS dan harus menyertakan mesin TTS yang mendukung bahasa yang tersedia di perangkat. Perhatikan bahwa perangkat lunak open source Android hulu mencakup implementasi mesin TTS berfitur lengkap.
Harus mendukung pemasangan mesin TTS pihak ketiga
Harus menyediakan antarmuka yang dapat diakses pengguna yang memungkinkan pengguna memilih mesin TTS untuk digunakan di level sistem

3.12. Kerangka Input TV

Android Television Input Framework (TIF) menyederhanakan pengiriman konten langsung ke perangkat televisi Android. TIF menyediakan API standar untuk membuat modul input yang mengontrol perangkat televisi Android. Implementasi perangkat televisi Android harus mendukung kerangka input TV [ Sumber Daya, 55 ].

Implementasi perangkat yang mendukung TIF harus mendeklarasikan fitur platform android.software.live_tv.

3.12.1. Aplikasi TV

Setiap implementasi perangkat yang menyatakan dukungan untuk TV langsung harus memiliki aplikasi TV yang diinstal (aplikasi TV). Proyek Open Source Android menyediakan implementasi aplikasi TV.

Aplikasi TV default harus menyediakan akses ke saluran dari input yang diinstal dan input pihak ketiga. Perhatikan bahwa input yang diinstal mencakup semua input yang disediakan secara default, apakah mereka berbasis TIF atau tidak.

Aplikasi TV harus menyediakan fasilitas untuk menginstal dan menggunakan saluran TV [ sumber daya, 56 ] dan memenuhi persyaratan berikut:

Implementasi perangkat harus memungkinkan input berbasis TIF pihak ketiga (input pihak ketiga) [ Sumber Daya, 57 ] diinstal dan dikelola.
Implementasi perangkat dapat memberikan pemisahan visual antara input berbasis TIF yang telah diinstal sebelumnya (input yang diinstal) [ Sumber Daya, 58 ] dan input pihak ketiga.
Implementasi perangkat tidak boleh menampilkan input pihak ketiga lebih dari satu tindakan navigasi tunggal dari aplikasi TV (yaitu memperluas daftar input pihak ketiga dari aplikasi TV).

3.12.1.1. Panduan Program Elektronik

Implementasi perangkat televisi Android harus menunjukkan overlay informasi dan interaktif, yang harus mencakup panduan program elektronik (EPG) yang dihasilkan dari nilai -nilai di bidang TVContract.Program [ Sumber Daya, 59 ]. EPG harus memenuhi persyaratan berikut:

EPG harus menampilkan informasi dari semua input yang diinstal dan input pihak ketiga.
EPG dapat memberikan pemisahan visual antara input yang diinstal dan input pihak ketiga.
EPG sangat disarankan untuk menampilkan input yang terpasang dan input pihak ketiga dengan keunggulan yang sama. EPG tidak boleh menampilkan input pihak ketiga lebih dari satu tindakan navigasi tunggal dari input yang diinstal pada EPG.
Pada perubahan saluran, implementasi perangkat harus menampilkan data EPG untuk program yang saat ini bermain.

3.12.1.2. Navigasi

Perangkat Input Perangkat Televisi Android (yaitu remote control, aplikasi remote control, atau pengontrol game) harus memungkinkan navigasi ke semua bagian layar yang dapat ditindaklanjuti melalui D-PAD. D-Pad Up dan Down HARUS digunakan untuk mengubah saluran TV langsung ketika tidak ada bagian yang dapat ditindaklanjuti di layar.

Aplikasi TV harus lulus acara utama ke input HDMI melalui CEC.

3.12.1.3. Linking aplikasi input TV

Implementasi perangkat televisi Android harus mendukung tautan aplikasi input TV, yang memungkinkan semua input untuk menyediakan tautan aktivitas dari aktivitas saat ini ke aktivitas lain (yaitu tautan dari pemrograman langsung ke konten terkait) [ Sumber Daya, 60 ]. Aplikasi TV harus menampilkan aplikasi input TV yang menautkan saat disediakan.

4. Kompatibilitas Kemasan Aplikasi

Implementasi perangkat harus menginstal dan menjalankan file android ".apk" seperti yang dihasilkan oleh alat "AAPT" yang termasuk dalam Android SDK resmi [ Sumber Daya, 61 ].

Implementasi perangkat tidak boleh memperluas .apk [ sumber daya, 62 ], manifes android [ sumber daya, 49 ], dalvik bytecode [ sumber daya, 23 ], atau renderscript bytecode format sedemikian perangkat lain yang kompatibel.

5. Kompatibilitas Multimedia

5.1. Codec media

Implementasi perangkat harus mendukung format media inti yang ditentukan dalam dokumentasi Android SDK [ Sumber Daya, 64 ] kecuali jika diizinkan secara eksplisit dalam dokumen ini. Secara khusus, implementasi perangkat harus mendukung format media, encoder, decoder, jenis file, dan format kontainer yang ditentukan dalam tabel di bawah ini dan dilaporkan melalui MediaCodeclist [ Sumber Daya, 65 ]. Implementasi perangkat juga harus dapat memecahkan kode semua profil yang dilaporkan dalam CamCorderProfile [ Sumber Daya, 66 ] dan harus dapat memecahkan kode semua format yang dapat dikodekannya. Semua codec ini disediakan sebagai implementasi perangkat lunak dalam implementasi Android yang disukai dari proyek open source Android.

Harap dicatat bahwa baik Google maupun aliansi handset terbuka tidak membuat representasi bahwa codec ini bebas dari paten pihak ketiga. Mereka yang bermaksud menggunakan kode sumber ini dalam produk perangkat keras atau perangkat lunak disarankan agar implementasi kode ini, termasuk dalam perangkat lunak open source atau shareware, mungkin memerlukan lisensi paten dari pemegang paten yang relevan.

5.1.1. Codec Audio

Format/Kodek	Pembuat enkode	Dekoder	Detail	Jenis file/format kontainer yang didukung
Profil AAC MPEG-4 (AAC LC)	Diperlukan ¹	DIPERLUKAN	Dukungan untuk konten mono/stereo/5.0/5.1 ² dengan laju pengambilan sampel standar dari 8 hingga 48 kHz.	3GPP (.3GP) MPEG-4 (.mp4, .m4a) ADTS RAW AAC (.AAC, Decode di Android 3.1+, Encode di Android 4.0+, Adif Tidak Didukung) MPEG-TS (.ts, tidak dicari, Android 3.0+)
MPEG-4 He AAC Profile (AAC+)	Diperlukan ¹ (Android 4.1+)	DIPERLUKAN	Dukungan untuk konten mono/stereo/5.0/5.1 ² dengan laju pengambilan sampel standar dari 16 hingga 48 kHz.
MPEG-4 He AACV2 Profil (ditingkatkan AAC+)		DIPERLUKAN	Dukungan untuk konten mono/stereo/5.0/5.1 ² dengan laju pengambilan sampel standar dari 16 hingga 48 kHz.
AAC ELD (peningkatan penundaan rendah AAC)	Diperlukan ¹ (Android 4.1+)	DIPERLUKAN (Android 4.1+)	Dukungan untuk konten mono/stereo dengan tingkat pengambilan sampel standar dari 16 hingga 48 kHz.
AMR-NB	Diperlukan ³	Diperlukan ³	4,75 hingga 12,2 kbps sampel @ 8 kHz	3GPP (.3GP)
AMR-WB	Diperlukan ³	Diperlukan ³	9 tarif dari 6,60 kbit/s hingga 23,85 kbit/s sampel @ 16 kHz
FLAC		DIPERLUKAN (Android 3.1+)	Mono/stereo (tidak ada multichannel). Tingkat sampel hingga 48 kHz (tetapi hingga 44,1 kHz direkomendasikan pada perangkat dengan output 44,1 kHz, karena Downsampler 48 hingga 44,1 kHz tidak termasuk filter low-pass). 16-bit direkomendasikan; Tidak ada yang diterapkan untuk 24-bit.	Flac (.flac) saja
MP3		DIPERLUKAN	Mono/Stereo 8-320kbps Constant (CBR) atau Variabel Bitrate (VBR)	MP3 (.mp3)
MIDI		DIPERLUKAN	MIDI Tipe 0 dan 1. DLS Versi 1 dan 2. XMF dan Mobile XMF. Dukungan untuk Format Nada Dering RTTTL/RTX, OTA, dan IMELODY	Tipe 0 dan 1 (.mid, .xmf, .mxmf) Rtttl/rtx (.rtttl, .rtx) OTA (.ota) Imelody (.imy)
Vorbis		DIPERLUKAN		Ogg (.ogg) Matroska (.mkv, Android 4.0+)
PCM/WAVE	Diperlukan ⁴ (Android 4.1+)	DIPERLUKAN	PCM linier 16-bit (tarif hingga batas perangkat keras). Perangkat harus mendukung laju pengambilan sampel untuk perekaman PCM mentah pada frekuensi 8000, 11025, 16000, dan 44100 Hz.	GELOMBANG (.wav)
Karya		DIPERLUKAN (Android 5.0+)		Matroska (.mkv)

1 Diperlukan untuk implementasi perangkat yang mendefinisikan android.hardware.microphone tetapi opsional untuk implementasi perangkat Android Watch.

2 hanya downmix dari konten 5.0/5.1 yang diperlukan; Merekam atau merender lebih dari 2 saluran adalah opsional.

3 Diperlukan untuk implementasi perangkat genggam Android.

4 Diperlukan untuk implementasi perangkat yang mendefinisikan android.hardware.microphone, termasuk implementasi perangkat Android Watch.

5.1.2. Codec gambar

Format/Kodek	Pembuat enkode	Dekoder	Detail	Jenis file/format kontainer yang didukung
jpeg	DIPERLUKAN	DIPERLUKAN	Basis+progresif	JPEG (.jpg)
GIF		DIPERLUKAN		GIF (.gif)
PNG	DIPERLUKAN	DIPERLUKAN		PNG (.png)
BMP		DIPERLUKAN		BMP (.bmp)
WebP	DIPERLUKAN	DIPERLUKAN		Webp (.webp)

5.1.3. Codec Video

Format/Kodek	Pembuat enkode	Dekoder	Detail	Jenis file yang didukung/ Format Kontainer
H.263	Diperlukan ¹	Diperlukan ²		3GPP (.3GP) MPEG-4 (.mp4)
H.264 AVC	Diperlukan ²	Diperlukan ²	Lihat Bagian 5.2 dan 5.3 untuk detailnya	3GPP (.3GP) MPEG-4 (.mp4) MPEG-2 TS (.ts, AAC Audio saja, tidak dicari, Android 3.0+)
H.265 HEVC		Diperlukan ⁵	Lihat Bagian 5.3 untuk detailnya	MPEG-4 (.mp4)
MPEG-2		Sangat direkomendasikan ⁶	Profil Utama	MPEG2-TS
MPEG-4SP		Diperlukan ²		3GPP (.3GP)
VP8 ³	Diperlukan ² (Android 4.3+)	Diperlukan ² (Android 2.3.3+)	Lihat Bagian 5.2 dan 5.3 untuk detailnya	Webm (.webm) [ Sumber Daya, 67 Matroska (.mkv, Android 4.0+) ⁴
Wakil Presiden9		Diperlukan ² (Android 4.4+)	Lihat Bagian 5.3 untuk detailnya	Webm (.webm) [ Sumber Daya, 67 ] Matroska (.mkv, Android 4.0+) ⁴

1 Diperlukan untuk implementasi perangkat yang mencakup perangkat keras kamera dan mendefinisikan android.hardware.camera atau android.hardware.camera.front.

2 Diperlukan untuk implementasi perangkat kecuali perangkat Android Watch.

3 Untuk kualitas streaming video web dan layanan konferensi video yang dapat diterima, implementasi perangkat harus menggunakan codec VP8 perangkat keras yang memenuhi persyaratan dalam [ sumber daya, 68 ].

4 Implementasi Perangkat harus mendukung file Webm Matroska yang menulis.

5 Sangat disarankan untuk Android Automotive, opsional untuk Android Watch, dan diperlukan untuk semua jenis perangkat lainnya.

6 hanya berlaku untuk implementasi perangkat televisi Android.

5.2. Pengkodean Video

Codec video adalah opsional untuk implementasi perangkat Android Watch.

Implementasi perangkat Android dengan encoder H.263, harus mendukung level profil dasar 45.

Implementasi perangkat Android dengan dukungan CODEC H.264, harus mendukung profil profil dasar 3 dan profil pengkodean video SD (Definisi Standar) berikut dan harus mendukung profil profil utama 4 dan profil pengkodean video HD (definisi tinggi) berikut. Perangkat televisi Android sangat disarankan untuk menyandikan video HD 1080p pada 30 fps.

	SD (kualitas rendah)	SD (kualitas tinggi)	HD 720p ¹	HD 1080p ¹
Resolusi video	320x240 piksel	720x480 piksel	1280x720 piksel	1920x1080 piksel
Kecepatan bingkai video	20fps	30fps	30fps	30fps
Kecepatan bit video	384 Kbps	2Mbps	4Mbps	10Mbps

1 Ketika didukung oleh perangkat keras, tetapi sangat disarankan untuk perangkat televisi Android.

Implementasi perangkat Android dengan Dukungan Codec VP8 harus mendukung profil pengkodean video SD dan harus mendukung profil pengkodean video HD (definisi tinggi) berikut.

	SD (kualitas rendah)	SD (kualitas tinggi)	HD 720p ¹	HD 1080p ¹
Resolusi video	320 x 180 px	640x360 piksel	1280x720 piksel	1920x1080 piksel
Kecepatan bingkai video	30fps	30fps	30fps	30fps
Kecepatan bit video	800 Kbps	2Mbps	4Mbps	10Mbps

1 Saat didukung oleh perangkat keras.

5.3. Penguraian Video

Codec video adalah opsional untuk implementasi perangkat Android Watch.

Implementasi perangkat harus mendukung resolusi video dinamis dan switching frame rate melalui API Android standar dalam aliran yang sama untuk semua codec VP8, VP9, H.264, dan H.265 secara real time dan hingga resolusi maksimum yang didukung oleh setiap codec pada pada perangkat.

Implementasi perangkat Android dengan decoder H.263, harus mendukung level profil dasar 30.

Implementasi perangkat Android dengan decoder MPEG-4, harus mendukung profil sederhana level 3.

Implementasi perangkat Android dengan decoder H.264, harus mendukung profil utama Tingkat 3.1 dan profil decoding video SD berikut dan harus mendukung profil decoding HD. Perangkat televisi Android harus mendukung profil tinggi level 4.2 dan profil decoding HD 1080p.

	SD (kualitas rendah)	SD (kualitas tinggi)	HD 720p ¹	HD 1080p ¹
Resolusi video	320x240 piksel	720x480 piksel	1280x720 piksel	1920x1080 piksel
Kecepatan bingkai video	30fps	30fps	60fps	30 fps / 60 fps ²
Kecepatan bit video	800 Kbps	2Mbps	8Mbps	20Mbps

1 Diperlukan untuk ketika ketinggian seperti yang dilaporkan oleh display.getSupportedModes () metode sama atau lebih besar dari resolusi video.

2 Diperlukan untuk implementasi perangkat televisi Android.

Implementasi Perangkat Android Saat mendukung Codec VP8 seperti yang dijelaskan dalam Bagian 5.1.3 , harus mendukung profil decoding SD berikut dan harus mendukung profil decoding HD. Perangkat televisi Android harus mendukung profil decoding HD 1080p.

	SD (kualitas rendah)	SD (kualitas tinggi)	HD 720p ¹	HD 1080p ¹
Resolusi video	320 x 180 px	640x360 piksel	1280x720 piksel	1920x1080 piksel
Kecepatan bingkai video	30fps	30fps	30 fps / 60 fps ²	30 /60 fps ²
Kecepatan bit video	800 Kbps	2Mbps	8Mbps	20Mbps

1 Diperlukan untuk ketika ketinggian seperti yang dilaporkan oleh display.getSupportedModes () metode sama atau lebih besar dari resolusi video.

2 Diperlukan untuk implementasi perangkat televisi Android.

Implementasi perangkat Android, saat mendukung VP9 Codec seperti yang dijelaskan dalam Bagian 5.1.3 , harus mendukung profil decoding video SD berikut dan harus mendukung profil decoding HD. Perangkat televisi Android sangat disarankan untuk mendukung profil decoding HD 1080p dan harus mendukung profil decoding UHD. Ketika profil decoding video UHD didukung, itu harus mendukung kedalaman warna 8-bit dan harus mendukung Profil VP9 2 (10-bit).

	SD (kualitas rendah)	SD (kualitas tinggi)	HD 720p ¹	HD 1080p ²	Uhd ²
Resolusi video	320 x 180 px	640x360 piksel	1280x720 piksel	1920x1080 piksel	3840x2160 piksel
Kecepatan bingkai video	30fps	30fps	30fps	60fps	60fps
Kecepatan bit video	600 Kbps	1,6Mbps	4Mbps	5Mbps	20Mbps

1 Diperlukan untuk implementasi perangkat televisi Android, tetapi untuk jenis perangkat lainnya hanya jika didukung oleh perangkat keras.

2 Sangat disarankan untuk implementasi perangkat televisi Android yang ada saat didukung oleh perangkat keras.

Implementasi perangkat Android, ketika mendukung H.265 codec seperti yang dijelaskan dalam Bagian 5.1.3 , harus mendukung tingkat utama profil 3 tingkat utama dan profil decoding video SD berikut dan harus mendukung profil decoding HD. Perangkat televisi Android sangat disarankan untuk mendukung profil decoding UHD dan profil decoding HD 1080p. Jika profil decoding HD 1080p didukung, itu harus mendukung profil utama level 4.1 tingkat utama. Jika decoding UHD didukung, maka itu harus mendukung profil tingkat utama Main10 Level 5.

	SD (kualitas rendah)	SD (kualitas tinggi)	HD 720p ¹	HD 1080p ²	Uhd ²
Resolusi video	352 x 288 px	640x360 piksel	1280x720 piksel	1920x1080 piksel	3840x2160 piksel
Kecepatan bingkai video	30fps	30fps	30fps	60 fps ²	60fps
Kecepatan bit video	600 Kbps	1,6Mbps	4Mbps	10Mbps	20Mbps

1 Diperlukan untuk implementasi perangkat televisi Android, tetapi untuk jenis perangkat lainnya hanya jika didukung oleh perangkat keras.

2 Sangat disarankan untuk implementasi perangkat televisi Android yang ada saat didukung oleh perangkat keras.

5.4. Rekaman audio

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

5.4.1. Raw Audio Capture

Device implementations that declare android.hardware.microphone MUST allow capture of raw audio content with the following characteristics:

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

The capture for the above sample rates MUST be done without up-sampling, and any down-sampling MUST include an appropriate anti-aliasing filter.

Device implementations that declare android.hardware.microphone SHOULD allow capture of raw audio content with the following characteristics:

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

If capture for the above sample rates is supported, then the capture MUST be done without up-sampling at any ratio higher than 16000:22050 or 44100:48000. Any up-sampling or down-sampling MUST include an appropriate anti-aliasing filter.

5.4.2. Capture for Voice Recognition

In addition to the above recording specifications, when an application has started recording an audio stream using the android.media.MediaRecorder.AudioSource.VOICE_RECOGNITION audio source:

The device SHOULD exhibit approximately flat amplitude versus frequency characteristics: specifically, ±3 dB, from 100 Hz to 4000 Hz.
Audio input sensitivity SHOULD be set such that a 90 dB sound power level (SPL) source at 1000 Hz yields RMS of 2500 for 16-bit samples.
PCM amplitude levels SHOULD 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.
Total harmonic distortion SHOULD be less than 1% for 1 kHz at 90 dB SPL input level at the microphone.
Noise reduction processing, if present, MUST be disabled.
Automatic gain control, if present, MUST be disabled

If the platform supports noise suppression technologies tuned for speech recognition, the effect MUST be controllable from the android.media.audiofx.NoiseSuppressor API. Moreover, the UUID field for the noise suppressor's effect descriptor MUST uniquely identify each implementation of the noise suppression technology.

5.4.3. Capture for Rerouting of Playback

The android.media.MediaRecorder.AudioSource class includes the REMOTE_SUBMIX audio source. Devices that declare android.hardware.audio.output 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 can capture a mix of all audio streams except for the following :

STREAM_RING
STREAM_ALARM
STREAM_NOTIFICATION

5.5. Pemutaran Audio

Device implementations that declare android.hardware.audio.output MUST conform to the requirements in this section.

5.5.1. Raw Audio Playback

The device MUST allow playback of raw audio content with the following characteristics:

Format : Linear PCM, 16-bit
Sampling rates : 8000, 11025, 16000, 22050, 32000, 44100
Channels : Mono, Stereo

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

Sampling rates : 24000, 48000

5.5.2. Efek Audio

Android provides an API for audio effects for device implementations [ Resources, 69 ]. Device implementations that declare the feature android.hardware.audio.output:

MUST support the EFFECT_TYPE_EQUALIZER and EFFECT_TYPE_LOUDNESS_ENHANCER implementations controllable through the AudioEffect subclasses Equalizer, LoudnessEnhancer.
MUST support the visualizer API implementation, controllable through the Visualizer class.
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.

5.5.3. Volume Keluaran Audio

Android Television device implementations 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).

5.6. Latensi Audio

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 can be heard by an external listener or observed by a transducer.
cold output latency . The output latency for the first frame, when the audio output system has been idle and powered down prior to the request.
continuous output latency . The output latency for subsequent frames, after the device is playing audio.
input latency . The interval between when an external sound is presented to the device and when an application reads the corresponding frame of PCM-coded data.
cold input latency . The sum of lost input time and the input latency for the first frame, when the audio input system has been idle and powered down prior to the request.
continuous input latency . The input latency for subsequent frames, while the device is capturing audio.
cold output jitter . The variance among separate measurements of cold output latency values.
cold input jitter . The variance among separate measurements of cold input latency values.
continuous round-trip latency . The sum of continuous input latency plus continuous output latency plus one buffer period. The buffer period term allows processing time for the app and 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; see NDK_root/docs/opensles/index.html.

Device implementations that declare android.hardware.audio.output are STRONGLY RECOMMENDED to meet or exceed these audio output requirements:

cold output latency of 100 milliseconds or less
continuous output latency of 45 milliseconds or less
minimize the cold output jitter

If a device implementation meets the requirements of this section after any initial calibration when using the OpenSL ES PCM buffer queue API, for continuous output latency and cold output latency over at least one supported audio output device, it is STRONGLY RECOMMENDED to report support for low-latency audio, by reporting the feature android.hardware.audio.low_latency via the android.content.pm.PackageManager class [ Resources, 70 ]. Conversely, if the device implementation does not meet these requirements it MUST NOT report support for low-latency audio.

Device implementations that include android.hardware.microphone are STRONGLY RECOMMENDED to meet these input audio requirements:

cold input latency of 100 milliseconds or less
continuous input latency of 30 milliseconds or less
continuous round-trip latency of 50 milliseconds or less
minimize the cold input jitter

5.7. Protokol Jaringan

Devices MUST support the media network protocols for audio and video playback as specified in the Android SDK documentation [ Resources, 64 ]. Specifically, devices MUST support the following media network protocols:

RTSP (RTP, SDP)
HTTP(S) progressive streaming
HTTP(S) Live Streaming draft protocol, Version 3 [ Resources, 71 ]

5.8. Media Aman

Device implementations that support secure video output and are capable of supporting secure surfaces MUST declare support for Display.FLAG_SECURE. Device implementations that declare support for Display.FLAG_SECURE, if they support a wireless display protocol, MUST secure the link with a cryptographically strong mechanism such as HDCP 2.x or higher for Miracast wireless displays. Similarly if they support a wired external display, the device implementations MUST support HDCP 1.2 or higher. Android Television device implementations MUST support HDCP 2.2 for devices supporting 4K resolution and HDCP 1.4 or above for lower resolutions. The upstream Android open source implementation includes support for wireless (Miracast) and wired (HDMI) displays that satisfies this requirement.

5.9. Antarmuka Digital Alat Musik (MIDI)

If a device implementation supports the inter-app MIDI software transport (virtual MIDI devices), and it supports MIDI over all of the following MIDI-capable hardware transports for which it provides generic non-MIDI connectivity, it is STRONGLY RECOMMENDED to report support for feature android.software.midi via the android.content.pm.PackageManager class [ Resources, 70 ].

The MIDI-capable hardware transports are:

USB host mode (section 7.7 USB)
USB peripheral mode (section 7.7 USB)

Conversely, if the device implementation provides generic non-MIDI connectivity over a particular MIDI-capable hardware transport listed above, but does not support MIDI over that hardware transport, it MUST NOT report support for feature android.software.midi.

MIDI over Bluetooth LE acting in central role (section 7.4.3 Bluetooth) is in trial use status. A device implementation that reports feature android.software.midi, and which provides generic non-MIDI connectivity over Bluetooth LE, SHOULD support MIDI over Bluetooth LE.

5.10. Audio Profesional

If a device implementation meets all of the following requirements, it is STRONGLY RECOMMENDED to report support for feature android.hardware.audio.pro via the android.content.pm.PackageManager class [ Resources, 70 ].

The device implementation MUST report support for feature android.hardware.audio.low_latency.
The continuous round-trip audio latency, as defined in section 5.6 Audio Latency, MUST be 20 milliseconds or less and SHOULD be 10 milliseconds or less over at least one supported path.
If the device includes a 4 conductor 3.5mm audio jack, the continuous round-trip audio latency MUST be 20 milliseconds or less over the audio jack path, and SHOULD be 10 milliseconds or less over the audio jack path.
The device implementation MUST include a USB port(s) supporting USB host mode and USB peripheral mode.
The USB host mode MUST implement the USB audio class.
If the device includes an HDMI port, the device implementation MUST support output in stereo and eight channels at 20-bit or 24-bit depth and 192 kHz without bit-depth loss or resampling.
The device implementation MUST report support for feature android.software.midi.
If the device includes a 4 conductor 3.5mm audio jack, the device implementation is STRONGLY RECOMMENDED to comply with section Mobile device (jack) specifications of the Wired Audio Headset Specification (v1.1) .

6. Developer Tools and Options Compatibility

6.1. Alat pengembang

Device implementations MUST support the Android Developer Tools provided in the Android SDK. Android compatible devices MUST be compatible with:

Android Debug Bridge (adb) [ Resources, 72 ]

Device implementations MUST support all adb functions as documented in the Android SDK including dumpsys [ Resources, 73 ]. The device-side adb daemon MUST be inactive by default and there MUST be a user-accessible mechanism to turn on the Android Debug Bridge. If a device implementation omits USB peripheral mode, it MUST implement the Android Debug Bridge via local-area network (such as Ethernet or 802.11).

Android includes support for secure adb. Secure adb enables adb on known authenticated hosts. Device implementations MUST support secure adb.

Dalvik Debug Monitor Service (ddms) [ Resources, 74 ]

Device implementations 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 [ Resources, 75 ]

Device implementations MUST include the Monkey framework, and make it available for applications to use.

SysTrace [ Resources, 76 ]

Device implementations MUST support 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.

Most Linux-based systems and Apple Macintosh systems recognize Android devices using the standard Android SDK tools, without additional support; however Microsoft Windows systems typically require a driver for new Android devices. (For instance, new vendor IDs and sometimes new device IDs require custom USB drivers for Windows systems.) If a device implementation is unrecognized by the adb tool as provided in the standard Android SDK, device implementers MUST provide Windows drivers allowing developers to connect to the device using the adb protocol. These drivers MUST be provided for Windows XP, Windows Vista, Windows 7, Windows 8 and Windows 10 in both 32-bit and 64-bit versions.

6.2. Opsi Pengembang

Android includes support for developers to configure application development-related settings. Device implementations MUST honor the android.settings.APPLICATION_DEVELOPMENT_SETTINGS intent to show application development-related settings [ Resources, 77 ]. 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. Device implementations MUST provide a consistent experience for Developer Options. Specifically, device implementations MUST hide Developer Options by default and MUST provide a mechanism to enable Developer Options that is consistent with the upstream Android implementation.

7. Hardware Compatibility

If a device includes a particular hardware component that has a corresponding API for third-party developers, 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:

Complete class definitions (as documented by the SDK) for the component APIs MUST still be presented.
The API's behaviors MUST be implemented as no-ops in some reasonable fashion.
API methods MUST return null values where permitted by the SDK documentation.
API methods MUST return no-op implementations of classes where null values are not permitted by the SDK documentation.
API methods MUST NOT throw exceptions not documented by the SDK documentation.

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.

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. [ Resources, 70 ]

7.1. Tampilan dan Grafik

Android includes facilities that automatically adjust application assets and UI layouts appropriately for the device, to ensure that third-party applications run well on a variety of hardware configurations [ Resources, 78 ]. Devices 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.
rasio aspek . The ratio of the pixels of the longer dimension to the shorter dimension of the screen. For example, a display of 480x854 pixels would be 854/480 = 1.779, or roughly “16:9”.
density-independent pixel (dp) The virtual pixel unit normalized to a 160 dpi screen, calculated as: pixels = dps * (density/160).

7.1.1. Konfigurasi Layar

7.1.1.1. Ukuran layar

Android Watch devices (detailed in section 2 ) MAY have smaller screen sizes as described in this section.

The Android UI framework supports a variety of different screen sizes, and allows applications to query the device screen size (aka “screen layout") via android.content.res.Configuration.screenLayout with the SCREENLAYOUT_SIZE_MASK. Device implementations MUST report the correct screen size as defined in the Android SDK documentation [ Resources, 78 ] and determined by the upstream Android platform. Specifically, device implementations MUST report the correct screen size according to the following logical density-independent pixel (dp) screen dimensions.

Devices MUST have screen sizes of at least 426 dp x 320 dp ('small'), unless it is an Android Watch device.
Devices that report screen size 'normal' MUST have screen sizes of at least 480 dp x 320 dp.
Devices that report screen size 'large' MUST have screen sizes of at least 640 dp x 480 dp.
Devices that report screen size 'xlarge' MUST have screen sizes of at least 960 dp x 720 dp.

Selain itu,

Android Watch devices MUST have a screen with the physical diagonal size in the range from 1.1 to 2.5 inches.
Other types of Android device implementations, with a physically integrated screen, MUST have a screen at least 2.5 inches in physical diagonal size.

Devices MUST NOT change their reported screen size at any time.

Applications optionally indicate which screen sizes they support via the <supports-screens> attribute in the AndroidManifest.xml file. Device implementations MUST correctly honor applications' stated support for small, normal, large, and xlarge screens, as described in the Android SDK documentation.

7.1.1.2. Rasio Aspek Layar

Android Watch devices MAY have an aspect ratio of 1.0 (1:1).

The screen aspect ratio MUST be a value from 1.3333 (4:3) to 1.86 (roughly 16:9), but Android Watch devices MAY have an aspect ratio of 1.0 (1:1) because such a device implementation will use a UI_MODE_TYPE_WATCH as the android.content.res.Configuration.uiMode.

7.1.1.3. Kepadatan Layar

The Android UI framework defines a set of standard logical densities to help application developers target application resources. Device implementations MUST report only one of the following logical Android framework densities through the android.util.DisplayMetrics APIs, and MUST execute applications at this standard density and MUST NOT change the value at at any time for the default display.

120 dpi (ldpi)
160 dpi (mdpi)
213 dpi (tvdpi)
240dpi (hdpi)
280 dpi (280dpi)
320dpi (xhdpi)
360 dpi (360dpi)
400 dpi (400dpi)
420dpi (420dpi)
480 dpi (xxhdpi)
560 dpi (560dpi)
640 dpi (xxxhdpi)

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.

7.1.2. Metrik Tampilan

Device implementations MUST report correct values for all display metrics defined in android.util.DisplayMetrics [ Resources, 79 ] and MUST report the same values regardless of whether the embedded or external screen is used as the default display.

7.1.3. Orientasi layar

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

Devices that report both screen orientations 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. Device implementations MAY select either portrait or landscape orientation as the default.

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

Devices MUST NOT change the reported screen size or density when changing orientation.

7.1.4. 2D and 3D Graphics Acceleration

Device implementations MUST support both OpenGL ES 1.0 and 2.0, as embodied and detailed in the Android SDK documentations. Device implementations SHOULD support OpenGL ES 3.0 or 3.1 on devices capable of supporting it. Device implementations MUST also support Android RenderScript, as detailed in the Android SDK documentation [ Resources, 80 ].

Device implementations MUST also correctly identify themselves as supporting OpenGL ES 1.0, OpenGL ES 2.0, OpenGL ES 3.0 or OpenGL 3.1. Itu adalah:

The managed APIs (such as via the GLES10.getString() method) MUST report support for OpenGL ES 1.0 and OpenGL ES 2.0.
The native C/C++ OpenGL APIs (APIs available to apps via libGLES_v1CM.so, libGLES_v2.so, or libEGL.so) MUST report support for OpenGL ES 1.0 and OpenGL ES 2.0.
Device implementations that declare support for OpenGL ES 3.0 or 3.1 MUST support the corresponding managed APIs and include support for native C/C++ APIs. On device implementations that declare support for OpenGL ES 3.0 or 3.1, libGLESv2.so MUST export the corresponding function symbols in addition to the OpenGL ES 2.0 function symbols.

In addition to OpenGL ES 3.1, Android provides an extension pack with Java interfaces [ Resources, 81 ] and native support for advanced graphics functionality such as tessellation and the ASTC texture compression format. Android device implementations MAY support this extension pack, and—only if fully implemented—MUST identify the support through the android.hardware.opengles.aep feature flag.

Also, device implementations MAY implement any desired OpenGL ES extensions. However, device implementations MUST report via the OpenGL ES managed and native APIs all extension strings that they do support, and conversely MUST NOT report extension strings that they do not support.

Note that Android includes support for applications to optionally specify that they require specific OpenGL texture compression formats. These formats are typically vendor-specific. Device implementations are not required by Android to implement any specific texture compression format. However, they SHOULD accurately report any texture compression formats that they do support, via the getString() method in the OpenGL API.

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 [ Resources, 82 ].

Device implementations 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.

In addition, device implementations MUST exhibit behavior consistent with the Android SDK documentation on hardware acceleration [ Resources, 82 ].

Android includes a TextureView object that lets developers directly integrate hardware-accelerated OpenGL ES textures as rendering targets in a UI hierarchy. Device implementations MUST support the TextureView API, and MUST exhibit consistent behavior with the upstream Android implementation.

Android includes support for EGL_ANDROID_RECORDABLE, an EGLConfig attribute that indicates whether the EGLConfig supports rendering to an ANativeWindow that records images to a video. Device implementations MUST support EGL_ANDROID_RECORDABLE extension [ Resources, 83 ].

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.

Android Automotive does not support legacy compatibility mode.
All other device implementations MUST include support for legacy application compatibility mode as implemented by the upstream Android open source code. That is, device implementations MUST NOT alter the triggers or thresholds at which compatibility mode is activated, and MUST NOT alter the behavior of the compatibility mode itself.

7.1.6. Teknologi Layar

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

Devices MUST support displays capable of rendering 16-bit color graphics and SHOULD support displays capable of 24-bit color graphics.
Devices MUST support displays capable of rendering animations.
The display technology used 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 display to enable media sharing capabilities and developer APIs for accessing external displays. If a device supports an external display either via a wired, wireless, or an embedded additional display connection then the device implementation MUST implement the display manager API as described in the Android SDK documentation [ Resources, 84 ].

7.2. Perangkat masukan

Devices MUST support a touchscreen or meet the requirements listed in 7.2.2 for non-touch navigation.

7.2.1. Papan ketik

Android Watch and Android Automotive implementations MAY implement a soft keyboard. All other device implementations MUST implement a soft keyboard and:

Implementasi perangkat:

MUST include support for the Input Management Framework (which allows third-party developers to create Input Method Editors—ie soft keyboard) as detailed at http://developer.android.com .
MUST provide at least one soft keyboard implementation (regardless of whether a hard keyboard is present) except for Android Watch devices where the screen size makes it less reasonable to have a soft keyboard.
MAY include additional soft keyboard implementations.
MAY include a hardware keyboard.
MUST NOT include a hardware keyboard that does not match one of the formats specified in android.content.res.Configuration.keyboard [ Resources, 85 ] (QWERTY or 12-key).

7.2.2. Non-touch Navigation

Android Television devices MUST support D-pad.

Implementasi perangkat:

MAY omit a non-touch navigation option (trackball, d-pad, or wheel) if the device implementation is not an Android Television device.
MUST report the correct value for android.content.res.Configuration.navigation [ Resources, 85 ].
MUST provide a reasonable alternative user interface mechanism for the selection and editing of text, compatible with Input Management Engines. The upstream Android open source implementation includes a selection mechanism suitable for use with devices that lack non-touch navigation inputs.

7.2.3. Tombol Navigasi

The availability and visibility requirement of the Home, Recents, and Back functions differ between device types as described in this section.

The Home, Recents, and Back functions (mapped to the key events KEYCODE_HOME, KEYCODE_APP_SWITCH, KEYCODE_BACK, respectively) are essential to the Android navigation paradigm and therefore:

Android Handheld device implementations MUST provide the Home, Recents, and Back functions.
Android Television device implementations MUST provide the Home and Back functions.
Android Watch device implementations MUST have the Home function available to the user, and the Back function except for when it is in UI_MODE_TYPE_WATCH.
Android Automotive implementations MUST provide the Home function and MAY provide Back and Recent functions.
All other types of device implementations MUST provide the Home and Back functions.

These functions MAY be implemented via dedicated physical buttons (such as mechanical or capacitive touch buttons), or MAY be implemented using dedicated software keys on a distinct portion of the screen, gestures, touch panel, etc. Android supports both implementations. All of these functions MUST be accessible with a single action (eg tap, double-click or gesture) when visible.

Recents function, if provided, MUST have a visible button or icon unless hidden together with other navigation functions in full-screen mode. This does not apply to devices upgrading from earlier Android versions that have physical buttons for navigation and no recents key.

The Home and Back functions, if provided, MUST each have a visible button or icon unless hidden together with other navigation functions in full-screen mode or when the uiMode UI_MODE_TYPE_MASK is set to UI_MODE_TYPE_WATCH.

The Menu function is deprecated in favor of action bar since Android 4.0. Therefore the new device implementations shipping with Android 6.0 and later MUST NOT implement a dedicated physical button for the Menu function. Older device implementations SHOULD NOT implement a dedicated physical button for the Menu function, but if the physical Menu button is implemented and the device is running applications with targetSdkVersion > 10, the device implementation:

MUST display the action overflow button on the action bar when it is visible and the resulting action overflow menu popup is not empty. For a device implementation launched before Android 4.4 but upgrading to Android 6.0, this is RECOMMENDED.
MUST NOT modify the position of the action overflow popup displayed by selecting the overflow button in the action bar.
MAY render the action overflow popup at a modified position on the screen when it is displayed by selecting the physical menu button.

For backwards compatibility, device implementations 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 presented unless hidden together with other navigation functions.

Android device implementations with the support of the Assist action [ Resources, 30 ] MUST make this accessible with a single action (eg tap, double-click, or gesture) when other navigation keys are visible, and are STRONGLY RECOMMENDED to use the long-press on the Home button or software key as the single action.

Device implementations MAY use a distinct portion of the screen to display the navigation keys, but if so, MUST meet these requirements:

Device implementation 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.
Device implementations MUST make available a portion of the display to applications that meets the requirements defined in section 7.1.1 .
Device implementations MUST display the navigation keys when applications do not specify a system UI mode, or specify SYSTEM_UI_FLAG_VISIBLE.
Device implementations MUST present the navigation keys in an unobtrusive “low profile” (eg. dimmed) mode when applications specify SYSTEM_UI_FLAG_LOW_PROFILE.
Device implementations MUST hide the navigation keys when applications specify SYSTEM_UI_FLAG_HIDE_NAVIGATION.

7.2.4. Touchscreen Input

Android Handhelds and Watch Devices MUST support touchscreen input.

Device implementations SHOULD have a pointer input system of some kind (either mouse-like or touch). However, if a device implementation does not support a pointer input system, it MUST NOT report the android.hardware.touchscreen or android.hardware.faketouch feature constant. Device implementations that do include a pointer input system:

SHOULD support fully independently tracked pointers, if the device input system supports multiple pointers.
MUST report the value of android.content.res.Configuration.touchscreen [ Resources, 85 ] corresponding to the type of the specific touchscreen on the device.

Android includes support for a variety of touchscreens, touch pads, and fake touch input devices. Touchscreen based device implementations are associated with a display [ Resources, 86 ] 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. In contrast, a 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. Device implementations that declare the fake touch feature MUST meet the fake touch requirements in section 7.2.5 .

Device implementations MUST report the correct feature corresponding to the type of input used. Device implementations that include a touchscreen (single-touch or better) MUST report the platform feature constant android.hardware.touchscreen. Device implementations that report the platform feature constant android.hardware.touchscreen MUST also report the platform feature constant android.hardware.faketouch. Device implementations that do not include a touchscreen (and rely on a pointer device only) MUST NOT report any touchscreen feature, and MUST report only android.hardware.faketouch if they meet the fake touch requirements in section 7.2.5 .

7.2.5. Fake Touch Input

Device implementations that declare support for android.hardware.faketouch:

MUST report the absolute X and Y screen positions of the pointer location and display a visual pointer on the screen [ Resources, 87 ].
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 [ Resources, 87 ].
MUST support pointer down and up on an object on the screen, which allows users to emulate tap on an object on the screen.
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 [ Resources, 87 ].
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.
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.

Devices that declare support for android.hardware.faketouch.multitouch.distinct MUST meet the requirements for faketouch above, and MUST also support distinct tracking of two or more independent pointer inputs.

7.2.6. Game Controller Support

Android Television device implementations MUST support button mappings for game controllers as listed below. The upstream Android implementation includes implementation for game controllers that satisfies this requirement.

7.2.6.1. Button Mappings

Android Television device implementations MUST support the following key mappings:

Tombol	HID Usage ²	Tombol Android
Sebuah ¹	0x09 0x0001	KEYCODE_BUTTON_A (96)
B1 ^_	0x09 0x0002	KEYCODE_BUTTON_B (97)
X ¹	0x09 0x0004	KEYCODE_BUTTON_X (99)
kamu ¹	0x09 0x0005	KEYCODE_BUTTON_Y (100)
D-pad up ¹ D-pad down ¹	0x01 0x0039 ³	AXIS_HAT_Y ⁴
D-pad left 1 D-pad right ¹	0x01 0x0039 ³	AXIS_HAT_X ⁴
Left shoulder button ¹	0x09 0x0007	KEYCODE_BUTTON_L1 (102)
Right shoulder button ¹	0x09 0x0008	KEYCODE_BUTTON_R1 (103)
Left stick click ¹	0x09 0x000E	KEYCODE_BUTTON_THUMBL (106)
Right stick click ¹	0x09 0x000F	KEYCODE_BUTTON_THUMBR (107)
Rumah ¹	0x0c 0x0223	KEYCODE_HOME (3)
Kembali ¹	0x0c 0x0224	KEYCODE_BACK (4)

1 [ Resources, 88 ]

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 [ Resources, 87 ]

Analog Controls ¹	HID Usage	Tombol Android
Pemicu Kiri	0x02 0x00C5	AXIS_LTRIGGER
Pemicu Kanan	0x02 0x00C4	AXIS_RTRIGGER
Joystick Kiri	0x01 0x0030 0x01 0x0031	AXIS_X AXIS_Y
Joystick Kanan	0x01 0x0032 0x01 0x0035	AXIS_Z AXIS_RZ

1 [ Resources, 87 ]

7.2.7. Kendali Jarak Jauh

Android Television device implementations SHOULD provide a remote control to allow users to access the TV interface. The remote control MAY be a physical remote or can be a software-based remote that is accessible from a mobile phone or tablet. The remote control MUST meet the requirements defined below.

Search affordance . Device implementations MUST fire KEYCODE_SEARCH (or KEYCODE_ASSIST if the device supports an assistant) when the user invokes voice search on either the physical or software-based remote.
Navigasi . All Android Television remotes MUST include Back, Home, and Select buttons and support for D-pad events [ Resources, 88 ].

7.3. Sensor

Android includes APIs for accessing a variety of sensor types. Devices implementations generally MAY omit these sensors, as provided for in the following subsections. If a device includes 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 [ Resources, 89 ]. For example, device implementations:

MUST accurately report the presence or absence of sensors per the android.content.pm.PackageManager class [ Resources, 70] .
MUST return an accurate list of supported sensors via the SensorManager.getSensorList() and similar methods.
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.).
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 [ Resources, 90 ].
SHOULD report the event time in nanoseconds as defined in the Android SDK documentation, representing the time the event happened and synchronized with the SystemClock.elapsedRealtimeNano() clock. Existing and new Android devices are STRONGLY RECOMMENDED to meet these requirement so they will be able to upgrade to the future platform releases where this might become a REQUIRED component. The synchronization error SHOULD be below 100 milliseconds [ Resources, 91 ].
MUST report sensor data with a maximum latency of 100 milliseconds + 2 * sample_time for the case of a sensor streamed with a minimum required latency of 5 ms + 2 * sample_time when the application processor is active. This delay does not include any filtering delays.
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.

The list above is not comprehensive; the documented behavior of the Android SDK and the Android Open Source Documentations on Sensors [ Resources, 89 ] is to be considered authoritative.

Some sensor types are composite, meaning they can be derived from data provided by one or more other sensors. (Examples include the orientation sensor, and the linear acceleration sensor.) Device implementations SHOULD implement these sensor types, when they include the prerequisite physical sensors as described in [ Resources, 92 ]. If a device implementation includes a composite sensor it MUST implement the sensor as described in the Android Open Source documentation on composite sensors [ Resources, 92 ].

Some Android sensors support a “continuous” trigger mode, which returns data continuously [ Resources, 93 ]. 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 acara.

Note that the device implementations 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.

Finally, when several sensors are activated, the power consumption SHOULD NOT exceed the sum of the individual sensor's reported power consumption.

7.3.1. Akselerometer

Device implementations SHOULD include a 3-axis accelerometer. Android Handheld devices and Android Watch devices are STRONGLY RECOMMENDED to include this sensor. If a device implementation does include a 3-axis accelerometer, it:

MUST implement and report TYPE_ACCELEROMETER sensor [ Resources, 94 ].
MUST be able to report events up to a frequency of at least 50 Hz for Android Watch devices as such devices have a stricter power constraint and 100 Hz for all other device types.
SHOULD report events up to at least 200 Hz.
MUST comply with the Android sensor coordinate system as detailed in the Android APIs [ Resources, 90 ].
MUST be capable of measuring from freefall up to four times the gravity (4g) or more on any axis.
MUST have a resolution of at least 12-bits and 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.
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.
SHOULD implement the TYPE_SIGNIFICANT_MOTION, TYPE_TILT_DETECTOR, TYPE_STEP_DETECTOR, TYPE_STEP_COUNTER composite sensors as described in the Android SDK document. Existing and new Android devices are STRONGLY RECOMMENDED to implement the TYPE_SIGNIFICANT_MOTION composite sensor. If any of these sensors are implemented, the sum of their power consumption MUST always be less than 4 mW and SHOULD each be below 2 mW and 0.5 mW for when the device is in a dynamic or static condition.
If a gyroscope sensor is included, MUST implement the TYPE_GRAVITY and TYPE_LINEAR_ACCELERATION composite sensors and SHOULD implement the TYPE_GAME_ROTATION_VECTOR composite sensor. Existing and new Android devices are STRONGLY RECOMMENDED to implement the TYPE_GAME_ROTATION_VECTOR sensor.
MUST implement a TYPE_ROTATION_VECTOR composite sensor, if a gyroscope sensor and a magnetometer sensor is also included.

7.3.2. magnetometer

Device implementations SHOULD include a 3-axis magnetometer (compass). If a device does include a 3-axis magnetometer, it:

MUST implement the TYPE_MAGNETIC_FIELD sensor and SHOULD also implement TYPE_MAGNETIC_FIELD_UNCALIBRATED sensor. Existing and new Android devices are STRONGLY RECOMMENDED to implement the TYPE_MAGNETIC_FIELD_UNCALIBRATED sensor.
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.
MUST comply with the Android sensor coordinate system as detailed in the Android APIs [ Resources, 90 ].
MUST be capable of measuring between -900 µT and +900 µT on each axis before saturating.
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.
MUST have a resolution equal or denser than 0.6 µT and SHOULD have a resolution equal or denser than 0.2 µ.
SHOULD be temperature compensated.
MUST support online calibration and compensation of the hard iron bias, and preserve the compensation parameters between device reboots.
MUST have the soft iron compensation applied—the calibration can be done either while in use or during the production of the device.
SHOULD 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 0.5 µT.
MUST implement a TYPE_ROTATION_VECTOR composite sensor, if an accelerometer sensor and a gyroscope sensor is also included.
MAY implement the TYPE_GEOMAGNETIC_ROTATION_VECTOR sensor if an accelerometer sensor is also implemented. However if implemented, it MUST consume less than 10 mW and SHOULD consume less than 3 mW when the sensor is registered for batch mode at 10 Hz.

7.3.3. GPS

Device implementations SHOULD include a GPS receiver. If a device implementation does include a GPS receiver, it SHOULD include some form of“assisted GPS” technique to minimize GPS lock-on time.

7.3.4. Giroskop

Device implementations SHOULD include a gyroscope (angular change sensor). Devices SHOULD NOT include a gyroscope sensor unless a 3-axis accelerometer is also included. If a device implementation includes a gyroscope, it:

MUST implement the TYPE_GYROSCOPE sensor and SHOULD also implement TYPE_GYROSCOPE_UNCALIBRATED sensor. Existing and new Android devices are STRONGLY RECOMMENDED to implement the SENSOR_TYPE_GYROSCOPE_UNCALIBRATED sensor.
MUST be capable of measuring orientation changes up to 1,000 degrees per second.
MUST be able to report events up to a frequency of at least 50 Hz for Android Watch devices as such devices have a stricter power constraint and 100 Hz for all other device types.
SHOULD report events up to at least 200 Hz.
MUST have a resolution of 12-bits or more and SHOULD have a resolution of 16-bits or more.
MUST be temperature compensated.
MUST be calibrated and compensated while in use, and preserve the compensation parameters between device reboots.
MUST have a variance no greater than 1e-7 rad^2 / s^2 per Hz (variance per Hz, or rad^2 / s). The variance is allowed to vary with the sampling rate, but must be constrained by this value. In other words, if you measure the variance of the gyro at 1 Hz sampling rate it should be no greater than 1e-7 rad^2/s^2.
MUST implement a TYPE_ROTATION_VECTOR composite sensor, if an accelerometer sensor and a magnetometer sensor is also included.
If an accelerometer sensor is included, MUST implement the TYPE_GRAVITY and TYPE_LINEAR_ACCELERATION composite sensors and SHOULD implement the TYPE_GAME_ROTATION_VECTOR composite sensor. Existing and new Android devices are STRONGLY RECOMMENDED to implement the TYPE_GAME_ROTATION_VECTOR sensor.

7.3.5. Barometer

Device implementations SHOULD include a barometer (ambient air pressure sensor). If a device implementation includes a barometer, it:

MUST implement and report TYPE_PRESSURE sensor.
MUST be able to deliver events at 5 Hz or greater.
MUST have adequate precision to enable estimating altitude.
MUST be temperature compensated.

7.3.6. Termometer

Device implementations MAY include an ambient thermometer (temperature sensor). If present, it MUST be defined as SENSOR_TYPE_AMBIENT_TEMPERATURE and it MUST measure the ambient (room) temperature in degrees Celsius.

Device implementations MAY but SHOULD NOT include a CPU temperature sensor. If present, it MUST be defined as SENSOR_TYPE_TEMPERATURE, it MUST measure the temperature of the device CPU, and it MUST NOT measure any other temperature. Note the SENSOR_TYPE_TEMPERATURE sensor type was deprecated in Android 4.0.

7.3.7. Fotometer

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

7.3.8. Sensor jarak

Device implementations MAY include a proximity sensor. Devices that can make a voice call and indicate any value other than PHONE_TYPE_NONE in getPhoneType SHOULD include a proximity sensor. If a device implementation does include a proximity sensor, it:

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 a device implementation includes a proximity sensor with any other orientation, it MUST NOT be accessible through this API.
MUST have 1-bit of accuracy or more.

7.3.9. High Fidelity Sensors

Device implementations supporting a set of higher quality sensors that can meet all the requirements listed in this section MUST identify the support through the android.hardware.sensor.hifi_sensors feature flag.

A device declaring android.hardware.sensor.hifi_sensors MUST support all of the following sensor types meeting the quality requirements as below:

SENSOR_TYPE_ACCELEROMETER
- MUST have a measurement range between at least -8g and +8g
- MUST have a measurement resolution of at least 1024 LSB/G
- MUST have a minimum measurement frequency of 12.5 Hz or lower
- MUST have a maxmium measurement frequency of 200 Hz or higher
- MUST have a measurement noise not above 400uG/√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
SENSOR_TYPE_GYROSCOPE
- 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 maxmium measurement frequency of 200 Hz or higher
- MUST have a measurement noise not above 0.014°/s/√Hz
SENSOR_TYPE_GYROSCOPE_UNCALIBRATED with the same quality requirements as SENSOR_TYPE_GYROSCOPE
SENSOR_TYPE_GEOMAGNETIC_FIELD
- MUST have a measurement range between at least -900 and +900 uT
- 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 maxmium measurement frequency of 50 Hz or higher
- MUST have a measurement noise not above 0.5 uT
SENSOR_TYPE_MAGNETIC_FIELD_UNCALIBRATED with the same quality requirements as SENSOR_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
SENSOR_TYPE_PRESSURE
- 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
TYPE_GAME_ROTATION_VECTOR
- 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 4 mW.
SENSOR_TYPE_SIGNIFICANT_MOTION
- MUST have a power consumption not worse than 0.5 mW when device is static and 1.5 mW when device is moving
SENSOR_TYPE_STEP_DETECTOR
- 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
SENSOR_TYPE_STEP_COUNTER
- MUST have a power consumption not worse than 0.5 mW when device is static and 1.5 mW when device is moving
SENSOR_TILT_DETECTOR
- MUST have a power consumption not worse than 0.5 mW when device is static and 1.5 mW when device is moving

Also such a device MUST meet the following sensor subsystem requirements:

The event timestamp of the same physical event reported by the Accelerometer, Gyroscope sensor and Magnetometer MUST be within 2.5 milliseconds of each other.
The Gyroscope sensor event timestamps MUST be on the same time base as the camera subsystem and within 1 millisconds of error.
The latency of delivery of samples to the HAL SHOULD be below 5 milliseconds from the instant the data is available on the physical sensor hardware.
The power consumption MUST not be 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

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.

The following sensor types MAY also be supported on a device implementation declaring android.hardware.sensor.hifi_sensors, but if these sensor types are present they MUST meet the following minimum buffering capability requirement:

SENSOR_TYPE_PROXIMITY: 100 sensor events

7.3.10. Sensor Sidik Jari

Device implementations with a secure lock screen SHOULD include a fingerprint sensor. If a device implementation includes a fingerprint sensor and has a corresponding API for third-party developers, it:

MUST declare support for the android.hardware.fingerprint feature.
MUST fully implement the corresponding API as described in the Android SDK documentation [ Resources, 95 ].
MUST have a false acceptance rate not higher than 0.002%.
Is STRONGLY RECOMMENDED to have a false rejection rate of less than 10%, as measured on the device
Is STRONGLY RECOMMENDED to have a latency below 1 second, measured from when the fingerprint sensor is touched until the screen is unlocked, for one enrolled finger.
MUST rate limit attempts for at least 30 seconds after five false trials for fingerprint verification.
HARUS memiliki implementasi keystore yang didukung perangkat keras, dan melakukan pencocokan sidik jari di Trusted Execution Environment (TEE) atau pada chip dengan saluran aman ke TEE.
MUST have all identifiable fingerprint data encrypted and cryptographically authenticated such that they cannot be acquired, read or altered outside of the Trusted Execution Environment (TEE) as documented in the implementation guidelines on the Android Open Source Project site [ Resources, 96 ].
MUST prevent adding a fingerprint 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.
MUST NOT enable 3rd-party applications to distinguish between individual fingerprints.
MUST honor the DevicePolicyManager.KEYGUARD_DISABLE_FINGERPRINT flag.
MUST, when upgraded from a version earlier than Android 6.0, have the fingerprint data securely migrated to meet the above requirements or removed.
SHOULD use the Android Fingerprint icon provided in the Android Open Source Project.

7.4. Konektivitas Data

7.4.1. Telepon

“Telephony” as used by the Android APIs and this document refers specifically to hardware related to placing voice calls and sending SMS messages via a GSM or CDMA network. While these voice calls may or may not be packet-switched, they are for the purposes of Android considered independent of any data connectivity that may be implemented using the same network. In other words, the Android “telephony” functionality and APIs refer specifically to voice calls and SMS. For instance, device implementations that cannot place calls or send/receive SMS messages MUST NOT report the android.hardware.telephony feature or any subfeatures, 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. However, if a device implementation does include GSM or CDMA telephony, it MUST implement full support for the API for that technology. Device implementations that do not include telephony hardware MUST implement the full APIs as no-ops.

7.4.2. IEEE 802.11 (Wi-Fi)

Android Television device implementations MUST include Wi-Fi support.

Android Television device implementations MUST include support for one or more forms of 802.11 (b/g/a/n, etc.) and other types of Android device implementation SHOULD include support for one or more forms of 802.11. If a device implementation does include support for 802.11 and exposes the functionality to a third-party application, it MUST implement the corresponding Android API and:

MUST report the hardware feature flag android.hardware.wifi.
MUST implement the multicast API as described in the SDK documentation [ Resources, 97 ].
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.

7.4.2.1. Wi-Fi Langsung

Device implementations SHOULD include support for Wi-Fi Direct (Wi-Fi peer-to-peer). If a device implementation does include support for Wi-Fi Direct, it MUST implement the corresponding Android API as described in the SDK documentation [ Resources, 98 ]. If a device implementation includes support for Wi-Fi Direct, then it:

MUST report the hardware feature android.hardware.wifi.direct.
MUST support regular Wi-Fi operation.
SHOULD support concurrent Wi-Fi and Wi-Fi Direct operation.

7.4.2.2. Wi-Fi Tunneled Direct Link Setup

Android Television device implementations MUST include support for Wi-Fi Tunneled Direct Link Setup (TDLS).

Android Television device implementations MUST include support for Wi-Fi Tunneled Direct Link Setup (TDLS) and other types of Android device implementations SHOULD include support for Wi-Fi TDLS as described in the Android SDK Documentation [ Resources, 99 ]. If a device implementation does include support for TDLS and TDLS is enabled by the WiFiManager API, the device:

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.3. Bluetooth

Android Watch and Automotive implementations MUST support Bluetooth. Android Television implementations MUST support Bluetooth and Bluetooth LE.

Android includes support for Bluetooth and Bluetooth Low Energy [ Resources, 100 ]. Device implementations that include support for Bluetooth and Bluetooth Low Energy MUST declare the relevant platform features (android.hardware.bluetooth and android.hardware.bluetooth_le respectively) and implement the platform APIs. Device implementations SHOULD implement relevant Bluetooth profiles such as A2DP, AVCP, OBEX, etc. as appropriate for the device. Android Television device implementations MUST support Bluetooth and Bluetooth LE.

Device implementations including support for Bluetooth Low Energy:

MUST declare the hardware feature android.hardware.bluetooth_le.
MUST enable the GATT (generic attribute profile) based Bluetooth APIs as described in the SDK documentation and [ Resources, 100 ].
are STRONGLY RECOMMENDED to implement a Resolvable Private Address (RPA) timeout no longer than 15 minutes and rotate the address at timeout to protect user privacy.
SHOULD support offloading of the filtering logic to the bluetooth chipset when implementing the ScanFilter API [ Resources, 101 ], and MUST report the correct value of where the filtering logic is implemented whenever queried via the android.bluetooth.BluetoothAdapter.isOffloadedFilteringSupported() method.
SHOULD support offloading of the batched scanning to the bluetooth chipset, but if not supported, MUST report 'false' whenever queried via the android.bluetooth.BluetoothAdapater.isOffloadedScanBatchingSupported() method.
SHOULD support multi advertisement with at least 4 slots, but if not supported, MUST report 'false' whenever queried via the android.bluetooth.BluetoothAdapter.isMultipleAdvertisementSupported() method.

7.4.4. Near-Field Communications

Device implementations SHOULD include a transceiver and related hardware for Near-Field Communications (NFC). If a device implementation does include NFC hardware and plans to make it available to third-party apps, then it:

MUST report the android.hardware.nfc feature from the android.content.pm.PackageManager.hasSystemFeature() method [ Resources, 70 ].
MUST be capable of reading and writing NDEF messages via the following NFC standards:
- 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 (defined by the NFC Forum)
- 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 below 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.
  - NfcV (ISO 15693)
- SHOULD be capable of reading the barcode and URL (if encoded) of Thinfilm NFC Barcode [ Resources, 102 ] products.
- MUST be capable of transmitting and receiving data via the following peer-to-peer standards and protocols:
  - ISO 18092
  - LLCP 1.2 (defined by the NFC Forum)
  - SDP 1.0 (defined by the NFC Forum)
  - NDEF Push Protocol [ Resources, 103 ]
  - SNEP 1.0 (defined by the NFC Forum)
- MUST include support for Android Beam [ Resources, 104 ]:
  - MUST implement the SNEP default server. Valid NDEF messages received by the default SNEP server MUST be dispatched to applications using the android.nfc.ACTION_NDEF_DISCOVERED intent. Disabling Android Beam in settings MUST NOT disable dispatch of incoming NDEF message.
  - MUST honor the android.settings.NFCSHARING_SETTINGS intent to show NFC sharing settings [ Resources, 105 ].
  - MUST implement the NPP server. Messages received by the NPP server MUST be processed the same way as the SNEP default server.
  - MUST implement a SNEP client and attempt to send outbound P2P NDEF to the default SNEP server when Android Beam is enabled. If no default SNEP server is found then the client MUST attempt to send to an NPP server.
  - MUST allow foreground activities to set the outbound P2P NDEF message using android.nfc.NfcAdapter.setNdefPushMessage, and android.nfc.NfcAdapter.setNdefPushMessageCallback, and android.nfc.NfcAdapter.enableForegroundNdefPush.
  - SHOULD use a gesture or on-screen confirmation, such as 'Touch to Beam', before sending outbound P2P NDEF messages.
  - SHOULD enable Android Beam by default and MUST be able to send and receive using Android Beam, even when another proprietary NFC P2p mode is turned on.
  - MUST support NFC Connection handover to Bluetooth when the device supports Bluetooth Object Push Profile. Device implementations MUST support connection handover to Bluetooth when using android.nfc.NfcAdapter.setBeamPushUris, by implementing the “Connection Handover version 1.2” [ Resources, 106 ] and “Bluetooth Secure Simple Pairing Using NFC version 1.0” [ Resources, 107 ] specs from the NFC Forum. Such an implementation MUST implement the handover LLCP service with service name “urn:nfc:sn:handover” for exchanging the handover request/select records over NFC, and it MUST use the Bluetooth Object Push Profile for the actual Bluetooth data transfer. For legacy reasons (to remain compatible with Android 4.1 devices), the implementation SHOULD still accept SNEP GET requests for exchanging the handover request/select records over NFC. However an implementation itself SHOULD NOT send SNEP GET requests for performing connection handover.
- 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.

(Note that publicly available links are not available for the JIS, ISO, and NFC Forum specifications cited above.)

Android includes support for NFC Host Card Emulation (HCE) mode. If a device implementation does include an NFC controller chipset capable of HCE and Application ID (AID) routing, then it:

MUST report the android.hardware.nfc.hce feature constant.
MUST support NFC HCE APIs as defined in the Android SDK [ Resources, 108 ].

Additionally, device implementations MAY include reader/writer support for the following MIFARE technologies.

MIFARE Klasik
MIFARE Ultra ringan
NDEF on MIFARE Classic

Note that Android includes APIs for these MIFARE types. If a device implementation supports MIFARE in the reader/writer role, it:

MUST implement the corresponding Android APIs as documented by the Android SDK.
MUST report the feature com.nxp.mifare from the android.content.pm.PackageManager.hasSystemFeature() method [ Resources, 70 ]. Note that this is not a standard Android feature and as such does not appear as a constant in the android.content.pm.PackageManager class.
MUST NOT implement the corresponding Android APIs nor report the com.nxp.mifare feature unless it also implements general NFC support as described in this section.

If a device implementation does not include NFC hardware, it MUST NOT declare the android.hardware.nfc feature from the android.content.pm.PackageManager.hasSystemFeature() method [ Resources, 70 ], and MUST implement the Android NFC API as a no-op.

As the classes android.nfc.NdefMessage and android.nfc.NdefRecord represent a protocol-independent data representation format, device implementations MUST implement these APIs even if they do not include support for NFC or declare the android.hardware.nfc feature.

7.4.5. Minimum Network Capability

Device implementations MUST include support for one or more forms of data networking. Specifically, device implementations MUST include support for at least one data standard capable of 200Kbit/sec or greater. Examples of technologies that satisfy this requirement include EDGE, HSPA, EV-DO, 802.11g, Ethernet, Bluetooth PAN, etc.

Device implementations where a physical networking standard (such as Ethernet) is the primary data connection SHOULD also include support for at least one common wireless data standard, such as 802.11 (Wi-Fi).

Devices MAY implement more than one form of data connectivity.

Devices MUST include an IPv6 networking stack and support IPv6 communication using the managed APIs, such as java.net.Socket and java.net.URLConnection , as well as the native APIs, such as AF_INET6 sockets. The required level of IPv6 support depends on the network type, as follows:

Devices that support Wi-Fi networks MUST support dual-stack and IPv6-only operation on Wi-Fi.
Devices that support Ethernet networks MUST support dual-stack operation on Ethernet.
Devices that support cellular data SHOULD support IPv6 operation (IPv6-only and possibly dual-stack) on cellular data.
When a device is simultaneously connected to more than one network (eg, Wi-Fi and cellular data), it MUST simultaneously meet these requirements on each network to which it is connected.

IPv6 MUST be enabled by default.

In order to ensure that IPv6 communication is as reliable as IPv4, unicast IPv6 packets sent to the device MUST NOT be dropped, even when the screen is not in an active state. Redundant multicast IPv6 packets, such as repeated identical Router Advertisements, MAY be rate-limited in hardware or firmware if doing so is necessary to save power. In such cases, rate-limiting MUST NOT cause the device to lose IPv6 connectivity on any IPv6-compliant network that uses RA lifetimes of at least 180 seconds.

IPv6 connectivity MUST be maintained in doze mode.

7.4.6. Pengaturan Sinkronisasi

Device implementations MUST have the master auto-sync setting on by default so that the method getMasterSyncAutomatically() returns “true” [ Resources, 109 ].

7.5. Kamera

Device implementations SHOULD include a rear-facing camera and MAY include a front-facing camera. A rear-facing camera is a camera located on the side of the device opposite the display; that is, it images scenes on the far side of the device, like a traditional camera. A front-facing camera is a camera located on the same side of the device as the display; that is, a camera typically used to image the user, such as for video conferencing and similar applications.

If a device implementation includes at least one camera, it SHOULD be possible for an application to simultaneously allocate 3 bitmaps equal to the size of the images produced by the largest-resolution camera sensor on the device.

7.5.1. Kamera Menghadap ke Belakang

Device implementations SHOULD include a rear-facing camera. If a device implementation includes at least one rear-facing camera, it:

MUST report the feature flag android.hardware.camera and android.hardware.camera.any.
MUST have a resolution of at least 2 megapixels.
SHOULD have either hardware auto-focus or software auto-focus implemented in the camera driver (transparent to application software).
MAY have fixed-focus or EDOF (extended depth of field) hardware.
MAY include a flash. If the Camera includes a flash, the flash lamp MUST NOT be lit while an android.hardware.Camera.PreviewCallback instance has been registered on a Camera preview surface, unless the application has explicitly enabled the flash by enabling the FLASH_MODE_AUTO or FLASH_MODE_ON attributes of a Camera.Parameters object. Note that this constraint does not apply to the device's built-in system camera application, but only to third-party applications using Camera.PreviewCallback.

7.5.2. Kamera Menghadap Depan

Device implementations MAY include a front-facing camera. If a device implementation includes at least one front-facing camera, it:

MUST report the feature flag android.hardware.camera.any and android.hardware.camera.front.
MUST have a resolution of at least VGA (640x480 pixels).
MUST NOT use a front-facing camera as the default for the Camera API. The camera API in Android has specific support for front-facing cameras and device implementations MUST NOT configure the API to to treat a front-facing camera as the default rear-facing camera, even if it is the only camera on the device.
MAY include features (such as auto-focus, flash, etc.) available to rear-facing cameras as described in section 7.5.1 .
MUST horizontally reflect (ie mirror) the stream displayed by an app in a CameraPreview, as follows:
- If the device implementation is capable of being rotated by user (such as automatically via an accelerometer or manually via user input), the camera preview MUST be mirrored horizontally relative to the device's current orientation.
- If the current application has explicitly requested that the Camera display be rotated via a call to the android.hardware.Camera.setDisplayOrientation()[ Resources, 110 ] method, the camera preview MUST be mirrored horizontally relative to the orientation specified by the application.
- Otherwise, the preview MUST be mirrored along the device's default horizontal axis.
MUST mirror the image displayed by the postview in the same manner as the camera preview image stream. If the device implementation does not support postview, this requirement obviously does not apply.
MUST NOT mirror the final captured still image or video streams returned to application callbacks or committed to media storage.

7.5.3. Kamera Eksternal

Device implementations with USB host mode MAY include support for an external camera that connects to the USB port. If a device includes support for an external camera, it:

MUST declare the platform feature android.hardware.camera.external and android.hardware camera.any.
MUST support USB Video Class (UVC 1.0 or higher).
MAY support multiple cameras.

Video compression (such as MJPEG) support is RECOMMENDED to enable transfer of high-quality unencoded streams (ie raw or independently compressed picture streams). Camera-based video encoding MAY be supported. If so, a simultaneous unencoded/ MJPEG stream (QVGA or greater resolution) MUST be accessible to the device implementation.

7.5.4. Camera API Behavior

Android includes two API packages to access the camera, the newer android.hardware.camera2 API expose lower-level camera control to the app, including efficient zero-copy burst/streaming flows and per-frame controls of exposure, gain, white balance gains, color conversion, denoising, sharpening, and more.

The older API package, android.hardware.Camera, is marked as deprecated in Android 5.0 but as it should still be available for apps to use Android device implementations MUST ensure the continued support of the API as described in this section and in the Android SDK .

Device implementations MUST implement the following behaviors for the camera-related APIs, for all available cameras:

If an application has never called android.hardware.Camera.Parameters.setPreviewFormat(int), then the device MUST use android.hardware.PixelFormat.YCbCr_420_SP for preview data provided to application callbacks.
If an application registers an android.hardware.Camera.PreviewCallback instance and the system calls the onPreviewFrame() method when the preview format is YCbCr_420_SP, the data in the byte[] passed into onPreviewFrame() must further be in the NV21 encoding format. That is, NV21 MUST be the default.
For android.hardware.Camera, device implementations MUST support the YV12 format (as denoted by the android.graphics.ImageFormat.YV12 constant) for camera previews for both front- and rear-facing cameras. (The hardware video encoder and camera may use any native pixel format, but the device implementation MUST support conversion to YV12.)
For android.hardware.camera2, device implementations must support the android.hardware.ImageFormat.YUV_420_888 and android.hardware.ImageFormat.JPEG formats as outputs through the android.media.ImageReader API.

Device implementations MUST still implement the full Camera API included in the Android SDK documentation [ Resources, 111 ], regardless of whether the device includes hardware autofocus or other capabilities. For instance, cameras that lack autofocus MUST still call any registered android.hardware.Camera.AutoFocusCallback instances (even though this has no relevance to a non-autofocus camera.) Note that this does apply to front-facing cameras; for instance, even though most front-facing cameras do not support autofocus, the API callbacks must still be “faked” as described.

Device implementations MUST recognize and honor each parameter name defined as a constant on the android.hardware.Camera.Parameters class, if the underlying hardware supports the feature. If the device hardware does not support a feature, the API must behave as documented. Conversely, device implementations MUST NOT honor or recognize string constants passed to the android.hardware.Camera.setParameters() method other than those documented as constants on the android.hardware.Camera.Parameters. That is, device implementations MUST support all standard Camera parameters if the hardware allows, and MUST NOT support custom Camera parameter types. For instance, device implementations that support image capture using high dynamic range (HDR) imaging techniques MUST support camera parameter Camera.SCENE_MODE_HDR [ Resources, 112 ].

Because not all device implementations can fully support all the features of the android.hardware.camera2 API, device implementations MUST report the proper level of support with the android.info.supportedHardwareLevel property as described in the Android SDK [ Resources, 113 ] and report the appropriate framework feature flags [ Resources, 114 ].

Device implementations MUST also declare its Individual camera capabilities of android.hardware.camera2 via the android.request.availableCapabilities property and declare the appropriate feature flags [ Resources, 114 ]; a device must define the feature flag if any of its attached camera devices supports the feature.

Device implementations MUST broadcast the Camera.ACTION_NEW_PICTURE intent whenever a new picture is taken by the camera and the entry of the picture has been added to the media store.

Device implementations MUST broadcast the Camera.ACTION_NEW_VIDEO intent whenever a new video is recorded by the camera and the entry of the picture has been added to the media store.

7.5.5. Orientasi Kamera

Both front- and rear-facing cameras, if present, MUST be oriented so that the long dimension of the camera aligns with the screen's long dimension. That is, when the device is held in the landscape orientation, cameras MUST capture images in the landscape orientation. This applies regardless of the device's natural orientation; that is, it applies to landscape-primary devices as well as portrait-primary devices.

7.6. Memori dan Penyimpanan

7.6.1. Minimum Memory and Storage

Android Television devices MUST have at least 5GB of non-volatile storage available for application private data.

The memory available to the kernel and userspace on device implementations MUST be at least equal or larger than the minimum values specified by the following table. (See section 7.1.1 for screen size and density definitions.)

Density and screen size	32-bit device	perangkat 64-bit
Android Watch devices (due to smaller screens)	416MB	Tak dapat diterapkan
280dpi or lower on small/normal screens mdpi or lower on large screens ldpi or lower on extra large screens	424MB	704MB
xhdpi or higher on small/normal screens hdpi or higher on large screens mdpi or higher on extra large screens	512MB	832MB
400dpi or higher on small/normal screens xhdpi or higher on large screens tvdpi or higher on extra large screens	896MB	1280MB
560dpi or higher on small/normal screens 400dpi or higher on large screens xhdpi or higher on extra large screens	1344MB	1824MB

The minimum memory values MUST be in addition to any memory space already dedicated to hardware components such as radio, video, and so on that is not under the kernel's control.

Device implementations with less than 512MB of memory available to the kernel and userspace, unless an Android Watch, MUST return the value "true" for ActivityManager.isLowRamDevice().

Android Television devices MUST have at least 5GB and other device implementations MUST have at least 1.5GB of non-volatile storage available for application private data. That is, the /data partition MUST be at least 5GB for Android Television devices and at least 1.5GB for other device implementations. Device implementations that run Android are STRONGLY RECOMMENDED to have at least 3GB of non-volatile storage for application private data so they will be able to upgrade to the future platform releases.

The Android APIs include a Download Manager that applications MAY use to download data files [ Resources, 115 ]. The device implementation of the Download Manager MUST be capable of downloading individual files of at least 100MB in size to the default “cache" location.

7.6.2. Application Shared Storage

Device implementations MUST offer shared storage for applications also often referred as “shared external storage”.

Device implementations MUST be configured with shared storage mounted by default, “out of the box”. If the shared storage is not mounted on the Linux path /sdcard, then the device MUST include a Linux symbolic link from /sdcard to the actual mount point.

Device implementations MAY have hardware for user-accessible removable storage, such as a Secure Digital (SD) card slot. If this slot is used to satisfy the shared storage requirement, the device implementation:

MUST implement a toast or pop-up user interface warning the user when there is no SD card.
MUST include a FAT-formatted SD card 1GB in size or larger OR show on the box and other material available at time of purchase that the SD card has to be separately purchased.
MUST mount the SD card by default.

Alternatively, device implementations MAY allocate internal (non-removable) storage as shared storage for apps as included in the upstream Android Open Source Project; device implementations SHOULD use this configuration and software implementation. If a device implementation uses internal (non-removable) storage to satisfy the shared storage requirement, while that storage MAY share space with the application private data, it MUST be at least 1GB in size and mounted on /sdcard (or /sdcard MUST be a symbolic link to the physical location if it is mounted elsewhere).

Device implementations MUST enforce as documented the android.permission.WRITE_EXTERNAL_STORAGE permission on this shared storage. Shared storage MUST otherwise be writable by any application that obtains that permission.

Device implementations that include multiple shared storage paths (such as both an SD card slot and shared internal storage) MUST allow only pre-installed & privileged Android applications with the WRITE_EXTERNAL_STORAGE permission to write to the secondary external storage, except when writing to their package-specific directories or within the URI returned by firing the ACTION_OPEN_DOCUMENT_TREE intent.

However, device implementations SHOULD expose content from both storage paths transparently through Android's media scanner service and android.provider.MediaStore.

Regardless of the form of shared storage used, if the device implementation has a USB port with USB peripheral mode support, it MUST provide some mechanism to access the contents of shared storage from a host computer. Device implementations MAY use USB mass storage, but SHOULD use Media Transfer Protocol to satisfy this requirement. If the device implementation supports Media Transfer Protocol, it:

SHOULD be compatible with the reference Android MTP host, Android File Transfer [ Resources, 116 ].
SHOULD report a USB device class of 0x00.
SHOULD report a USB interface name of 'MTP'.

7.6.3. Penyimpanan yang Dapat Diadopsi

Device implementations are STRONGLY RECOMMENDED to implement adoptable storage if the removable storage device port is in a long-term stable location, such as within the battery compartment or other protective cover [ Resources, 117 ].

Device implementations such as a television, MAY enable adoption through USB ports as the device is expected to be static and not mobile. But for other device implementations that are mobile in nature, it is STRONGLY RECOMMENDED to implement the adoptable storage in a long-term stable location, since accidentally disconnecting them can cause data loss/corruption.

7.7. USB

Device implementations SHOULD support USB peripheral mode and SHOULD support USB host mode.

If a device implementation includes a USB port supporting peripheral mode:

The port MUST be connectable to a USB host that has a standard type-A or type -C USB port.
The port SHOULD use micro-B, micro-AB or Type-C USB form factor. Existing and new Android devices are STRONGLY RECOMMENDED to meet these requirements so they will be able to upgrade to future platform releases.
The port SHOULD either be located on the bottom of the device (according to natural orientation) or enable software screen rotation for all apps (including home screen), so that the display draws correctly when the device is oriented with the port at bottom. Existing and new Android devices are STRONGLY RECOMMENDED to meet these requirements so they will be able to upgrade to future platform releases.
It SHOULD implement the Android Open Accessory (AOA) API and specification as documented in the Android SDK documentation, and if it is an Android Handheld device it MUST implement the AOA API. Device implementations implementing the AOA specification:
- MUST declare support for the hardware feature android.hardware.usb.accessory [ Resources, 118 ].
- MUST support establishing an AOA protocol based communication on first time connection with a USB host machine that acts as an accessory, without the need for the user to change the default USB mode.
- MUST implement the USB audio class as documented in the Android SDK documentation [ Resources, 119 ].
- And also the USB mass storage class, MUST include the string "android" at the end of the interface description iInterface string of the USB mass storage
It SHOULD implement support to draw 1.5 A current during HS chirp and traffic as specified in the USB Battery Charging Specification, Revision 1.2 [ Resources, 120 ]. Existing and new Android devices are STRONGLY RECOMMENDED to meet these requirements so they will be able to upgrade to the future platform releases.
The value of iSerialNumber in USB standard device descriptor MUST be equal to the value of android.os.Build.SERIAL.

If a device implementation includes a USB port supporting host mode, it:

SHOULD use a type-C USB port, if the device implementation supports USB 3.1.
MAY use a non-standard port form factor, but if so MUST ship with a cable or cables adapting the port to a standard type-A or type-C USB port.
MAY use a micro-AB USB port, but if so SHOULD ship with a cable or cables adapting the port to a standard type-A or type-C USB port.
is STRONGLY RECOMMENDED to implement the USB audio class as documented in the Android SDK documentation [ Resources, 119 ].
MUST implement the Android USB host API as documented in the Android SDK, and MUST declare support for the hardware feature android.hardware.usb.host [ Resources, 121 ].
SHOULD support device charging while in host mode; advertising a source current of at least 1.5A as specified in the Termination Parameters section of the USB Type-C Cable and Connector Specification, Revision 1.2 [ ] for USB Type-C connectors or using Charging Downstream Port(CDP) output current range as specified in the USB Battery Charging Specification, Revision 1.2 [ Resources, 120 ] for Micro-AB connectors.

7.8. Audio

7.8.1. Mikropon

Android Handheld, Watch, and Automotive implementations MUST include a microphone.

Device implementations MAY omit a microphone. However, if a device implementation omits a microphone, it MUST NOT report the android.hardware.microphone feature constant, and MUST implement the audio recording API at least as no-ops, per section 7 . Conversely, device implementations that do possess a microphone:

MUST report the android.hardware.microphone feature constant
MUST meet the audio recording requirements in section 5.4
MUST meet the audio latency requirements in section 5.6
STRONGLY RECOMMENDED to support near-ultrasound recording as described in section 7.8.3

7.8.2. Keluaran Audio

Android Watch devices MAY include an audio output.

Device implementations including a speaker or with an audio/multimedia output port for an audio output peripheral as a headset or an external speaker:

MUST report the android.hardware.audio.output feature constant.
MUST meet the audio playback requirements in section 5.5 .
MUST meet the audio latency requirements in section 5.6 .
STRONGLY RECOMMENDED to support near-ultrasound playback as described in section 7.8.3

Conversely, if a device implementation does not include a speaker or audio output port, it MUST NOT report the android.hardware.audio output feature, and MUST implement the Audio Output related APIs as no-ops at least.

Android Watch device implementation MAY but SHOULD NOT have audio output, but other types of Android device implementations MUST have an audio output and declare android.hardware.audio.output.

7.8.2.1. Analog Audio Ports

In order to be compatible with the headsets and other audio accessories using the 3.5mm audio plug across the Android ecosystem [ Resources, 122 ], if a device implementation includes one or more analog audio ports, at least one of the audio port(s) SHOULD be a 4 conductor 3.5mm audio jack. If a device implementation has a 4 conductor 3.5mm audio jack, it:

MUST support audio playback to stereo headphones and stereo headsets with a microphone, and SHOULD support audio recording from stereo headsets with a microphone.
MUST support TRRS audio plugs with the CTIA pin-out order, and SHOULD support audio plugs with the OMTP pin-out order.
MUST support the detection of microphone on the plugged in audio accessory, if the device implementation supports a microphone, and broadcast the android.intent.action.HEADSET_PLUG with the extra value microphone set as 1.
SHOULD support the detection and mapping to the keycodes for the following 3 ranges of equivalent impedance between the microphone and ground conductors on the audio plug:
- 70 ohm or less : KEYCODE_HEADSETHOOK
- 210-290 Ohm : KEYCODE_VOLUME_UP
- 360-680 Ohm : KEYCODE_VOLUME_DOWN
SHOULD support the detection and mapping to the keycode for the following range of equivalent impedance between the microphone and ground conductors on the audio plug:
- 110-180 Ohm: KEYCODE_VOICE_ASSIST
MUST trigger ACTION_HEADSET_PLUG upon a plug insert, but only after all contacts on plug are touching their relevant segments on the jack.
MUST be capable of driving at least 150mV ± 10% of output voltage on a 32 Ohm speaker impedance.
MUST have a microphone bias voltage between 1.8V ~ 2.9V.

7.8.3. Near-Ultrasound

Near-Ultrasound audio is the 18.5 kHz to 20 kHz band. Device implementations MUST correctly report the support of near-ultrasound audio capability via the AudioManager.getProperty API as follows:

If PROPERTY_SUPPORT_MIC_NEAR_ULTRASOUND is "true", then
- The microphone's mean power response in the 18.5 kHz to 20 kHz band MUST be no more than 15 dB below the response at 2 kHz.
- The microphone's unweighted signal-to-noise ratio (SNR) over 18.5 kHz to 20 kHz for a 19 kHz tone at -26 dBFS MUST be no lower than 50 dB.
If PROPERTY_SUPPORT_SPEAKER_NEAR_ULTRASOUND is "true", then the speaker's mean response in 18.5 kHz - 20 kHz MUST be no lower than 40 dB below the response at 2 kHz.

8. Performance and Power

Some minimum performance and power criteria are critical to the user experience and impact the baseline assumptions developers would have when developing an app. Android Watch devices SHOULD and other type of device implementations MUST meet the following criteria:

8.1. User Experience Consistency

Device implementations MUST provide a smooth user interface by ensuring a consistent frame rate and response times for applications and games. Device implementations MUST meet the following requirements:

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.
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.
Peralihan tugas . When multiple applications have been launched, re-launching an already-running application after it has been launched MUST take less than 1 second.

8.2. File I/O Access Performance

Device implementations MUST ensure internal storage file access performance consistency for read and write operations.

Sequential write . Device implementations MUST ensure a sequential write performance of at least 5MB/s for a 256MB file using 10MB write buffer.
Random write . Device implementations MUST ensure a random write performance of at least 0.5MB/s for a 256MB file using 4KB write buffer.
Sequential read . Device implementations MUST ensure a sequential read performance of at least 15MB/s for a 256MB file using 10MB write buffer.
Random read . Device implementations MUST ensure a random read performance of at least 3.5MB/s for a 256MB file using 4KB write buffer.

8.3. Mode Hemat Daya

All apps exempted from App Standby and/or Doze mode MUST be made visible to the end user. Further, the triggering, maintenance, wakeup algorithms and the use of Global system settings of these power-saving modes MUST not deviate from the Android Open Source Project.

8.4. Power Consumption Accounting

A more accurate accounting and reporting of the power consumption provides the app developer both the incentives and the tools to optimize the power usage pattern of the application. Therefore, device implementations:

MUST be able to track hardware component power usage and attribute that power usage to specific applications. Specifically, implementations:
- 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 [ Resources, 123 ].
- MUST report all power consumption values in milliampere hours (mAh)
- SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application.
- 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.
MUST make this power usage available via the adb shell dumpsys batterystats shell command to the app developer [ Resources, 124 ].
MUST honor the android.intent.action.POWER_USAGE_SUMMARY intent and display a settings menu that shows this power usage [ Resources, 125 ].

9. Security Model Compatibility

Device implementations MUST implement a security model consistent with the Android platform security model as defined in Security and Permissions reference document in the APIs [ Resources, 126 ] in the Android developer documentation. Device implementations MUST support installation of self-signed applications without requiring any additional permissions/certificates from any third parties/authorities. Specifically, compatible devices MUST support the security mechanisms described in the follow subsections.

9.1. Izin

Device implementations MUST support the Android permissions model as defined in the Android developer documentation [ Resources, 126 ]. Specifically, implementations MUST enforce each permission defined as described in the SDK documentation; no permissions may be omitted, altered, or ignored. Implementations MAY add additional permissions, provided the new permission ID strings are not in the android.* namespace.

Permissions with a protection level of dangerous are runtime permissions. Applications with targetSdkVersion > 22 request them at runtime. Implementasi perangkat:

MUST show a dedicated interface for the user to decide whether to grant the requested runtime permissions and also provide an interface for the user to manage runtime permissions.
MUST have one and only one implementation of both user interfaces.
MUST NOT grant any runtime permissions to preinstalled apps unless:
- the user's consent can be obtained before the application uses it
- the runtime permissions are associated with an intent pattern for which the preinstalled application is set as the default handler

9.2. UID and Process Isolation

Device implementations MUST support the Android application sandbox model, in which each application runs as a unique Unixstyle UID and in a separate process. Device implementations MUST support running multiple applications as the same Linux user ID, provided that the applications are properly signed and constructed, as defined in the Security and Permissions reference [ Resources, 126 ].

9.3. Izin Sistem File

Device implementations MUST support the Android file access permissions model as defined in the Security and Permissions reference [ Resources, 126 ].

9.4. Alternate Execution Environments

Device implementations MAY include runtime environments that execute applications using some other software or technology than the Dalvik Executable Format or native code. However, such alternate execution environments MUST NOT compromise the Android security model or the security of installed Android applications, as described in this section.

Alternate runtimes MUST themselves be Android applications, and abide by the standard Android security model, as described elsewhere in section 9 .

Alternate runtimes MUST NOT be granted access to resources protected by permissions not requested in the runtime's AndroidManifest.xml file via the <uses-permission> mechanism.

Alternate runtimes MUST NOT permit applications to make use of features protected by Android permissions restricted to system applications.

Alternate runtimes MUST abide by the Android sandbox model. Specifically, alternate runtimes:

SHOULD install apps via the PackageManager into separate Android sandboxes ( Linux user IDs, etc.).
MAY provide a single Android sandbox shared by all applications using the alternate runtime.
and installed applications using an alternate runtime, MUST NOT reuse the sandbox of any other app installed on the device, except through the standard Android mechanisms of shared user ID and signing certificate.
MUST NOT launch with, grant, or be granted access to the sandboxes corresponding to other Android applications.
MUST NOT be launched with, be granted, or grant to other applications any privileges of the superuser (root), or of any other user ID.

The .apk files of alternate runtimes MAY be included in the system image of a device implementation, but MUST be signed with a key distinct from the key used to sign other applications included with the device implementation.

When installing applications, alternate runtimes MUST obtain user consent for the Android permissions used by the application. If an application needs to make use of a device resource for which there is a corresponding Android permission (such as Camera, GPS, etc.), the alternate runtime MUST inform the user that the application will be able to access that resource. If the runtime environment does not record application capabilities in this manner, the runtime environment MUST list all permissions held by the runtime itself when installing any application using that runtime.

9.5. Dukungan Multi-Pengguna

This feature is optional for all device types.

Android includes support for multiple users and provides support for full user isolation [ Resources, 127 ]. Device implementations MAY enable multiple users, but when enabled MUST meet the following requirements related to multi-user support [ Resources, 128 ]:

Device implementations that do not declare the android.hardware.telephony feature flag 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.
Conversely device implementations that declare the android.hardware.telephony feature flag 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.
Device implementations MUST, for each user, implement a security model consistent with the Android platform security model as defined in Security and Permissions reference document in the APIs [ Resources, 126 ].
Each user instance on an Android device MUST have separate and isolated external storage directories. Device implementations MAY store multiple users' data on the same volume or filesystem. However, the device implementation MUST ensure that applications owned by and running on behalf a given user cannot list, read, or write to data owned by any other user. Note that removable media, such as SD card slots, can allow one user to access another's data by means of a host PC. For this reason, device implementations that use removable media for the primary external storage APIs MUST encrypt the contents of the SD card if multiuser is enabled using a key stored only on non-removable media accessible only to the system. As this will make the media unreadable by a host PC, device implementations will be required to switch to MTP or a similar system to provide host PCs with access to the current user's data. Accordingly, device implementations MAY but SHOULD NOT enable multi-user if they use removable media [ Resources, 129 ] for primary external storage.

9.6. Premium SMS Warning

Android includes support for warning users of any outgoing premium SMS message [ Resources, 130 ]. Premium SMS messages are text messages sent to a service registered with a carrier that may incur a charge to the user. Device implementations that declare support for android.hardware.telephony MUST warn users before sending a SMS message to numbers identified by regular expressions defined in /data/misc/sms/codes.xml file in the device. The upstream Android Open Source Project provides an implementation that satisfies this requirement.

9.7. Kernel Security Features

The Android Sandbox includes features that use the Security-Enhanced Linux (SELinux) mandatory access control (MAC) system and other security features in the Linux kernel. SELinux or any other security features implemented below the Android framework:

MUST maintain compatibility with existing applications.
MUST NOT have a visible user interface when a security violation is detected and successfully blocked, but MAY have a visible user interface when an unblocked security violation occurs resulting in a successful exploit.
SHOULD NOT be user or developer configurable.

If any API for configuration of policy is exposed to an application that can affect another application (such as a Device Administration API), the API MUST NOT allow configurations that break compatibility.

Devices MUST implement SELinux or, if using a kernel other than Linux, an equivalent mandatory access control system. Devices MUST also meet the following requirements, which are satisfied by the reference implementation in the upstream Android Open Source Project.

Implementasi perangkat:

MUST set SELinux to global enforcing mode.
MUST configure all domains in enforcing mode. No permissive mode domains are allowed, including domains specific to a device/vendor.
MUST NOT modify, omit, or replace the neverallow rules present within the external/sepolicy folder provided in the upstream Android Open Source Project (AOSP) and the policy MUST compile with all neverallow rules present, for both AOSP SELinux domains as well as device/vendor specific domains.

Device implementations SHOULD retain the default SELinux policy provided in the external/sepolicy folder of the upstream Android Open Source Project and only further add to this policy for their own device-specific configuration. Device implementations MUST be compatible with the upstream Android Open Source Project.

9.8. Pribadi

If the device implements functionality in the system that captures the contents displayed on the screen and/or records the audio stream played on the device, it MUST continuously notify the user whenever this functionality is enabled and actively capturing/recording.

If a device implementation has a mechanism that routes network data traffic through a proxy server or VPN gateway by default (for example, preloading a VPN service with android.permission.CONTROL_VPN granted), the device implementation MUST ask for the user's consent before enabling that mekanisme.

If a device implementation has a USB port with USB peripheral mode support, it MUST present a user interface asking for the user's consent before allowing access to the contents of the shared storage over the USB port.

9.9. Enkripsi Disk Penuh

Optional for Android device implementations without a lock screen.

If the device implementation supports a secure lock screen reporting " true " for KeyguardManager.isDeviceSecure() [ Resources, 131 ], and is not a device with restricted memory as reported through the ActivityManager.isLowRamDevice() method, then the device MUST support full-disk encryption [ Resources, 132 ] of the application private data (/data partition), as well as the application shared storage partition (/sdcard partition) if it is a permanent, non-removable part of the device.

For device implementations supporting full-disk encryption and with Advanced Encryption Standard (AES) crypto performance above 50MiB/sec, the full-disk encryption MUST be enabled by default at the time the user has completed the out-of-box setup experience. If a device implementation is already launched on an earlier Android version with full-disk encryption disabled by default, such a device cannot meet the requirement through a system software update and thus MAY be exempted.

Encryption MUST use AES with a key of 128-bits (or greater) and a mode designed for storage (for example, AES-XTS, AES-CBC-ESSIV). The encryption key MUST NOT be written to storage at any time without being encrypted. Other than when in active use, the encryption key SHOULD be AES encrypted with the lockscreen passcode stretched using a slow stretching algorithm (eg PBKDF2 or scrypt). If the user has not specified a lockscreen passcode or has disabled use of the passcode for encryption, the system SHOULD use a default passcode to wrap the encryption key. If the device provides a hardware-backed keystore, the password stretching algorithm MUST be cryptographically bound to that keystore. The encryption key MUST NOT be sent off the device (even when wrapped with the user passcode and/or hardware bound key). The upstream Android Open Source project provides a preferred implementation of this feature based on the Linux kernel feature dm-crypt.

9.10. Boot Terverifikasi

Verified boot is a feature that guarantees the integrity of the device software. If a device implementation supports the feature, it MUST:

Declare the platform feature flag android.software.verified_boot
Perform verification on every boot sequence
Start verification from an immutable hardware key that is the root of trust, and go all the way up to the system partition
Implement each stage of verification to check the integrity and authenticity of all the bytes in the next stage before executing the code in the next stage
Use verification algorithms as strong as current recommendations from NIST for hashing algorithms (SHA-256) and public key sizes (RSA-2048)

The upstream Android Open Source Project provides a preferred implementation of this feature based on the Linux kernel feature dm-verity.

Starting from Android 6.0, device implementations with Advanced Encryption Standard (AES) crypto performance above 50MiB/seconds MUST support verified boot for device integrity. If a device implementation is already launched without supporting verified boot on an earlier version of Android, such a device can not add support for this feature with a system software update and thus are exempted from the requirement.

9.11. Keys and Credentials

The Android Keystore System [ Resources, 133 ] allows app developers to store cryptographic keys in a container and use them in cryptographic operations through the KeyChain API [ Resources, 134 ] or the Keystore API [ Resources, 135 ].

All Android device implementations MUST meet the following requirements:

SHOULD not limit the number of keys that can be generated, and MUST at least allow more than 8,192 keys to be imported.
The lock screen authentication MUST rate limit attempts and SHOULD have an exponential backoff algorithm as implemented in the Android Open Source Project.
When the device implementation supports a secure lock screen and has a secure hardware such as a Secure Element (SE) where a Trusted Execution Environment (TEE) can be implemented, then it:
- Is STRONGLY RECOMMENDED to back up the keystore implementation with the secure hardware. The upstream Android Open Source Project provides the Keymaster Hardware Abstraction Layer (HAL) implementation that can be used to satisfy this requirement.
- MUST perform the lock screen authentication in the secure hardware if the device has a hardware-backed keystore implementation and only when successful allow the authentication-bound keys to be used. The upstream Android Open Source Project provides the Gatekeeper Hardware Abstraction Layer (HAL) that can be used to satisfy this requirement [ Resources, 136 ].

Note that while the above TEE-related requirements are stated as STRONGLY RECOMMENDED, the Compatibility Definition for the next API version is planned to changed these to REQUIRED. If a device implementation is already launched on an earlier Android version and has not implemented a trusted operating system on the secure hardware, such a device might not be able to meet the requirements through a system software update and thus is STRONGLY RECOMMENDED to implement a TEE .

9.12. Penghapusan Data

Devices MUST provide users with a mechanism to perform a "Factory Data Reset" that allows logical and physical deletion of all data except for the system image and data in other partitions that can be regarded as part of the system image. This MUST satisfy relevant industry standards for data deletion such as NIST SP800-88. This MUST be used for the implementation of the wipeData() API (part of the Android Device Administration API) described in section 3.9 Device Administration .

Devices MAY provide a fast data wipe that conducts a logical data erase.

10. Software Compatibility Testing

Device implementations MUST pass all tests described in this section.

However, note that no software test package is fully comprehensive. For this reason, device implementers are STRONGLY RECOMMENDED to make the minimum number of changes as possible to the reference and preferred implementation of Android available from the Android Open Source Project. This will minimize the risk of introducing bugs that create incompatibilities requiring rework and potential device updates.

10.1. Rangkaian Uji Kompatibilitas

Device implementations MUST pass the Android Compatibility Test Suite (CTS) [ Resources, 137 ] available from the Android Open Source Project, using the final shipping software on the device. Additionally, device implementers SHOULD use the reference implementation in the Android Open Source tree as much as possible, and MUST ensure compatibility in cases of ambiguity in CTS and for any reimplementations of parts of the reference source code.

The CTS is designed to be run on an actual device. Like any software, the CTS may itself contain bugs. The CTS will be versioned independently of this Compatibility Definition, and multiple revisions of the CTS may be released for Android 6.0. Device implementations MUST pass the latest CTS version available at the time the device software is completed.

10.2. CTS Verifier

Device implementations MUST correctly execute all applicable cases in the CTS Verifier. The CTS Verifier is included with the Compatibility Test Suite, and is intended to be run by a human operator to test functionality that cannot be tested by an automated system, such as correct functioning of a camera and sensors.

The CTS Verifier has tests for many kinds of hardware, including some hardware that is optional. Device implementations MUST pass all tests for hardware that they possess; for instance, if a device possesses an accelerometer, it MUST correctly execute the Accelerometer test case in the CTS Verifier. Test cases for features noted as optional by this Compatibility Definition Document MAY be skipped or omitted.

Every device and every build MUST correctly run the CTS Verifier, as noted above. However, since many builds are very similar, device implementers are not expected to explicitly run the CTS Verifier on builds that differ only in trivial ways. Specifically, device implementations that differ from an implementation that has passed the CTS Verifier only by the set of included locales, branding, etc. MAY omit the CTS Verifier test.

11. Updatable Software

Device implementations MUST include a mechanism to replace the entirety of the system software. The mechanism need not perform “live” upgrades—that is, a device restart MAY be required.

Any method can be used, provided that it can replace the entirety of the software preinstalled on the device. For instance, any of the following approaches will satisfy this requirement:

“Over-the-air (OTA)” downloads with offline update via reboot
“Tethered” updates over USB from a host PC
“Offline” updates via a reboot and update from a file on removable storage

However, if the device implementation includes support for an unmetered data connection such as 802.11 or Bluetooth PAN (Personal Area Network) profile:

Android Automotive implementations SHOULD support OTA downloads with offline update via reboot.
All other device implementations MUST support OTA downloads with offline update via reboot.

The update mechanism used MUST support updates without wiping user data. That is, the update mechanism MUST preserve application private data and application shared data. Note that the upstream Android software includes an update mechanism that satisfies this requirement.

For device implementations that are launching with Android 6.0 and later, the update mechanism SHOULD support verifying that the system image is binary identical to expected result following an OTA. The block-based OTA implementation in the upstream Android Open Source Project, added since Android 5.1, satisfies this requirement.

If an error is found in a device implementation after it has been released but within its reasonable product lifetime that is determined in consultation with the Android Compatibility Team to affect the compatibility of third-party applications, the device implementer MUST correct the error via a software update available that can be applied per the mechanism just described.

Android includes features that allow the Device Owner app (if present) to control the installation of system updates. To facilitate this, the system update subsystem for devices that report android.software.device_admin MUST implement the behavior described in the SystemUpdatePolicy class [ Resources, 138 ].

12. Document Changelog

The following table contains a summary of the changes to the Compatibility Definition in this release.

Bagian	Ringkasan perubahan
Bermacam-macam	Replaced instances of the "encouraged" term with "RECOMMENDED"
2. Device Types	Update for Android Automotive implementations
3.2.2. Parameter Bangun	Additions for the hardware serial number and for the security patch level of a build
3.2.3.2. Resolusi Niat	Section renamed from "Intent Overrides" to "Intent Resolution," with new requirements related to authoritative default app linking
3.3.1. Application Binary Interfaces	Additions for Android ABI support; change related to Vulkan library name
3.4.1. WebView Compatibility	Change for the user agent string reported by the WebView
3.7. Kompatibilitas Waktu Proses	Updates to memory allocation table
3.8.4. Mencari	Updates regarding Assistant requirements
3.8.6. Tema	Added requirement to support black system icons when requested by the SYSTEM_UI_FLAG_LIGHT_STATUS_BAR flag
3.8.8. Peralihan Aktivitas	Relaxed Overview title count requirement.
3.8.10. Kontrol Media Layar Kunci	Lock Screen Media Control to refer to 3.8.3 in detail.
3.9.1. Penyediaan Perangkat	Contains new sections for device owner provisioning and managed profile provisioning
3.9.2. Managed Profile Support	New section with requirements for device support of managed profile functionality
3.12.1. Aplikasi TV	Added section to clarify TV App requirements for Android Television devices
3.12.1.1. Panduan Program Elektronik	Added section to clarify EPG requirements for Android Television devices
3.12.1.2. Navigasi	Added section to clarify TV App navigation requirements for Android Television devices
3.12.1.3. TV input app linking	Added section to clarify TV input app linking support requirements for Android Television devices
5.1. Media Codecs	Updates regarding support for core media formats and decoding.
5.1.3. Codec Video	Changes and additions related to Android Televisions
5.2. Pengkodean Video	Changes for encoders
5.3. Penguraian Video	Changes for decoders, including regarding support for dynamic video resolution, frame rate switching, and more
5.4. Rekaman audio	Additions related to audio capture
5.6. Latensi Audio	Update regarding reporting of support for low-latency audio
5.10. Audio Profesional	General updates for professional audio support; updates for mobile device (jack) specifications, USB audio host mode, and other updates
5.9. Antarmuka Digital Alat Musik (MIDI)	Added new section on optional Musical Instrument Digital Interface (MIDI) support
6.1. Alat pengembang	Update for drivers supporting Windows 10
7.1.1.3. Kepadatan Layar	Updates for screen density, for example related to an Android watch
7.2.3. Tombol Navigasi	Updated requirements for device implementations that include the Assist action
7.3. Sensors (and subsections)	New requirements for some sensor types
7.3.9. High Fidelity Sensors	New section with requirements for devices supporting high fidelity sensors
7.3.10. Sensor Sidik Jari	New section on requirements related to fingerprint sensors
7.4.2. IEEE 802.11 (Wi-Fi)	Updates regarding support for multicast DNS (mDNS)
7.4.3. Bluetooth	Addition related to Resolvable Private Address (RPA) for Bluetooth Low Energy (BLE)
7.4.4. Near-Field Communications	Additions to requirements for Near-Field Communications (NFC)
7.4.5. Minimum Network Capability	Added requirements for IPv6 support
7.6.3. Penyimpanan yang Dapat Diadopsi	New section for implementation of adoptable storage
7.7. USB	Requirement related to implementing the AOA specification
7.8.3. Near-Ultrasound	Additions related to near-ultrasound recording, playback, and audio	Relax Near-ultrasound microphone SNR requirement.
8.3. Mode Hemat Daya	New section with requirements regarding the App Standby and Doze modes
8.4. Power Consumption Accounting	New section with requirements for tracking hardware component power usage and attributing that power usage to specific applications
9.1. Izin	Addition to Permissions requirements
9.7. Kernel Security Features	SE Linux updates
9.8. Pribadi	Addition regarding user's consent for access to shared storage over a USB port
9.9. Enkripsi Disk Penuh	Requirements related to full disk encryption
9.10. Boot Terverifikasi	Additional requirement for verified boot
9.11. Keys and Credentials	New section of requirements related to keys and credentials
9.12. Penghapusan Data	New section for "Factory Data Reset"
11. Updatable Software	Requirement related to the system update policy set by the device owner

13. Hubungi Kami

You can join the android-compatibility forum [Resources, 139 ] and ask for clarifications or bring up any issues that you think the document does not cover.

14. Sumber Daya

1. IETF RFC2119 Requirement Levels: http://www.ietf.org/rfc/rfc2119.txt

2. Android Open Source Project: http://source.android.com/

3. Android Television features: http://developer.android.com/reference/android/content/pm/PackageManager.html#FEATURE_LEANBACK

4. Android Watch feature: http://developer.android.com/reference/android/content/res/Configuration.html#UI_MODE_TYPE_WATCH

5. Android UI_MODE_TYPE_CAR API: http://developer.android.com/reference/android/content/res/Configuration.html#UI_MODE_TYPE_CAR

6. API definitions and documentation: http://developer.android.com/reference/packages.html

7. Android Permissions reference: http://developer.android.com/reference/android/Manifest.permission.html

8. android.os.Build reference: http://developer.android.com/reference/android/os/Build.html

9. Android 6.0 allowed version strings: http://source.android.com/docs/compatibility/6.0/versions.html

10. Android Developer Settings: http://developer.android.com/reference/android/provider/Settings.html

11. Telephony Provider: http://developer.android.com/reference/android/provider/Telephony.html

12. Android NDK ABI Management: https://developer.android.com/ndk/guides/abis.html

13. Advanced SIMD architecture: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0388f/Beijfcja.html

14. Android Extension Pack: http://developer.android.com/guide/topics/graphics/opengl.html#aep

15. android.webkit.WebView class: http://developer.android.com/reference/android/webkit/WebView.html

16. WebView compatibility: http://www.chromium.org/

17. HTML5: http://html.spec.whatwg.org/multipage/

18. HTML5 offline capabilities: http://dev.w3.org/html5/spec/Overview.html#offline

19. HTML5 video tag: http://dev.w3.org/html5/spec/Overview.html#video

20. HTML5/W3C geolocation API: http://www.w3.org/TR/geolocation-API/

21. HTML5/W3C webstorage API: http://www.w3.org/TR/webstorage/

22. HTML5/W3C IndexedDB API: http://www.w3.org/TR/IndexedDB/

23. Dalvik Executable Format and bytecode specification: available in the Android source code, at dalvik/docs

24. AppWidgets: http://developer.android.com/guide/practices/ui_guidelines/widget_design.html

25. Notifications: http://developer.android.com/guide/topics/ui/notifiers/notifications.html

26. Application Resources: https://developer.android.com/guide/topics/resources/available-resources.html

27. Status Bar icon style guide: http://developer.android.com/design/style/iconography.html

28. Notifications Resources: https://developer.android.com/design/patterns/notifications.html

29. Search Manager: http://developer.android.com/reference/android/app/SearchManager.html

30. Action Assist: http://developer.android.com/reference/android/content/Intent.html#ACTION_ASSIST

31. Android Assist APIs: https://developer.android.com/reference/android/app/assist/package-summary.html

32. Toasts: http://developer.android.com/reference/android/widget/Toast.html

33. Themes: http://developer.android.com/guide/topics/ui/themes.html

34. R.style class: http://developer.android.com/reference/android/R.style.html

35. Material design: http://developer.android.com/reference/android/R.style.html#Theme_Material

36. Live Wallpapers: http://developer.android.com/reference/android/service/wallpaper/WallpaperService.html

37. Overview screen resources: http://developer.android.com/guide/components/recents.html

38. Screen pinning: https://developer.android.com/about/versions/android-5.0.html#ScreenPinning

39. Input methods: http://developer.android.com/guide/topics/text/creating-input-method.html

40. Media Notification: https://developer.android.com/reference/android/app/Notification.MediaStyle.html

41. Dreams: http://developer.android.com/reference/android/service/dreams/DreamService.html

42. Settings.Secure LOCATION_MODE: http://developer.android.com/reference/android/provider/Settings.Secure.html#LOCATION_MODE

43. Unicode 6.1.0: http://www.unicode.org/versions/Unicode6.1.0/

44. Android Device Administration: http://developer.android.com/guide/topics/admin/device-admin.html

45. DevicePolicyManager reference: http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html

46. Device Owner App: http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#isDeviceOwnerApp(java.lang.String)

47. Android Device Owner Provisioning Flow: http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#ACTION_PROVISION_MANAGED_DEVICE

48. Device Owner Provisioning via NFC: /devices/tech/admin/provision.html#device_owner_provisioning_via_nfc

49. Android Profile Owner App: http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#isProfileOwnerApp(java.lang.String)

50. Android Managed Profile Provisioning flow: http://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#ACTION_PROVISION_MANAGED_PROFILE

51. Android Accessibility Service APIs: http://developer.android.com/reference/android/accessibilityservice/AccessibilityService.html

52. Android Accessibility APIs: http://developer.android.com/reference/android/view/accessibility/package-summary.html

53. Eyes Free project: http://code.google.com/p/eyes-free

54. Text-To-Speech APIs: http://developer.android.com/reference/android/speech/tts/package-summary.html

55. Television Input Framework: /devices/tv/index.html

56. TV App channels: http://developer.android.com/reference/android/media/tv/TvContract.Channels.html

57. Third-party TV inputs: /devices/tv/index.html#third-party_input_example

58. TV inputs: /devices/tv/index.html#tv_inputs

59. TV channel EPG fields: https://developer.android.com/reference/android/media/tv/TvContract.Programs.html

60. TV input app linking: http://developer.android.com/reference/android/media/tv/TvContract.Channels.html#COLUMN_APP_LINK_INTENT_URI

61. Reference tool documentation (for adb, aapt, ddms, systrace): http://developer.android.com/tools/help/index.html

62. Android apk file description: http://developer.android.com/guide/components/fundamentals.html

63. Manifest files: http://developer.android.com/guide/topics/manifest/manifest-intro.html

64. Android Media Formats: http://developer.android.com/guide/appendix/media-formats.html

65. Android MediaCodecList API: http://developer.android.com/reference/android/media/MediaCodecList.html

66. Android CamcorderProfile API: http://developer.android.com/reference/android/media/CamcorderProfile.html

67. WebM project: http://www.webmproject.org/

68. RTC Hardware Coding Requirements: http://www.webmproject.org/hardware/rtc-coding-requirements/

69. AudioEffect API: http://developer.android.com/reference/android/media/audiofx/AudioEffect.html

70. Android android.content.pm.PackageManager class and Hardware Features List: http://developer.android.com/reference/android/content/pm/PackageManager.html

71. HTTP Live Streaming Draft Protocol: http://tools.ietf.org/html/draft-pantos-http-live-streaming-03

72. ADB: http://developer.android.com/tools/help/adb.html

73. Dumpsys: /devices/input/diagnostics.html

74. DDMS: http://developer.android.com/tools/debugging/ddms.html

75. Monkey testing tool: http://developer.android.com/tools/help/monkey.html

76. SysyTrace tool: http://developer.android.com/tools/help/systrace.html

77. Android Application Development-Related Settings: http://developer.android.com/reference/android/provider/Settings.html#ACTION_APPLICATION_DEVELOPMENT_SETTINGS

78. Supporting Multiple Screens: http://developer.android.com/guide/practices/screens_support.html

79. android.util.DisplayMetrics: http://developer.android.com/reference/android/util/DisplayMetrics.html

80. RenderScript: http://developer.android.com/guide/topics/renderscript/

81. Android extension pack for OpenGL ES: https://developer.android.com/reference/android/opengl/GLES31Ext.html

82. Hardware Acceleration: http://developer.android.com/guide/topics/graphics/hardware-accel.html

83. EGL Extension-EGL_ANDROID_RECORDABLE: http://www.khronos.org/registry/egl/extensions/ANDROID/EGL_ANDROID_recordable.txt

84. Display Manager: http://developer.android.com/reference/android/hardware/display/DisplayManager.html

85. android.content.res.Configuration: http://developer.android.com/reference/android/content/res/Configuration.html

86. Touch Input Configuration: http://source.android.com/docs/core/interaction/input/touch-devices

87. Motion Event API: http://developer.android.com/reference/android/view/MotionEvent.html

88. Key Event API: http://developer.android.com/reference/android/view/KeyEvent.html

89. Android Open Source sensors: http://source.android.com/docs/core/interaction/sensors

90. android.hardware.SensorEvent: http://developer.android.com/reference/android/hardware/SensorEvent.html

91. Timestamp sensor event: http://developer.android.com/reference/android/hardware/SensorEvent.html#timestamp

92. Android Open Source composite sensors: /docs/core/interaction/sensors/sensor-types#composite_sensor_type_summary

93. Continuous trigger mode: http://developer.android.com/reference/android/hardware/Sensor.html#TYPE_ACCELEROMETER

95. Android Fingerprint API: https://developer.android.com/reference/android/hardware/fingerprint/package-summary.html

96. Android Fingerprint HAL: /devices/tech/security/authentication/fingerprint-hal.html

97. Wi-Fi Multicast API: http://developer.android.com/reference/android/net/wifi/WifiManager.MulticastLock.html

98. Wi-Fi Direct (Wi-Fi P2P): http://developer.android.com/reference/android/net/wifi/p2p/WifiP2pManager.html

99. WifiManager API: http://developer.android.com/reference/android/net/wifi/WifiManager.html

100. Bluetooth API: http://developer.android.com/reference/android/bluetooth/package-summary.html

101. Bluetooth ScanFilter API: https://developer.android.com/reference/android/bluetooth/le/ScanFilter.html

102. NFC Barcode: http://developer.android.com/reference/android/nfc/tech/NfcBarcode.html

103. NDEF Push Protocol: http://source.android.com/docs/compatibility/ndef-push-protocol.pdf

104. Android Beam: http://developer.android.com/guide/topics/connectivity/nfc/nfc.html

105. Android NFC Sharing Settings: http://developer.android.com/reference/android/provider/Settings.html#ACTION_NFCSHARING_SETTINGS

106. NFC Connection Handover: http://members.nfc-forum.org/specs/spec_list/#conn_handover

107. Bluetooth Secure Simple Pairing Using NFC: http://members.nfc-forum.org/apps/group_public/download.php/18688/NFCForum-AD-BTSSP_1_1.pdf

108. Host-based Card Emulation: http://developer.android.com/guide/topics/connectivity/nfc/hce.html

109. Content Resolver: http://developer.android.com/reference/android/content/ContentResolver.html

110. Camera orientation API: http://developer.android.com/reference/android/hardware/Camera.html#setDisplayOrientation(int)

111. Camera: http://developer.android.com/reference/android/hardware/Camera.html

112. Camera: http://developer.android.com/reference/android/hardware/Camera.Parameters.html

113. Camera hardware level: https://developer.android.com/reference/android/hardware/camera2/CameraCharacteristics.html#INFO_SUPPORTED_HARDWARE_LEVEL

114. Camera version support: http://source.android.com/docs/core/camera/versioning

115. Android DownloadManager: http://developer.android.com/reference/android/app/DownloadManager.html

116. Android File Transfer: http://www.android.com/filetransfer

117. Adoptable storage: http://source.android.com/docs/core/storage/adoptable

118. Android Open Accessories: http://developer.android.com/guide/topics/connectivity/usb/accessory.html

119. Android USB Audio: http://developer.android.com/reference/android/hardware/usb/UsbConstants.html#USB_CLASS_AUDIO

120. USB Battery Charging Specification, Revision 1.2: http://www.usb.org/developers/docs/devclass_docs/BCv1.2_070312.zip

121. USB Host API: http://developer.android.com/guide/topics/connectivity/usb/host.html

122. Wired audio headset: http://source.android.com/docs/core/interaction/accessories/headset/plug-headset-spec

123. Power profile components: http://source.android.com/docs/core/power/values

124. Batterystats: https://developer.android.com/tools/dumpsys#battery

125. Power usage summary: http://developer.android.com/reference/android/content/Intent.html#ACTION_POWER_USAGE_SUMMARY

126. Android Security and Permissions reference: http://developer.android.com/guide/topics/security/permissions.html

127. UserManager reference: http://developer.android.com/reference/android/os/UserManager.html

128. External Storage reference: http://source.android.com/docs/core/storage/traditional

129. External Storage APIs: http://developer.android.com/reference/android/os/Environment.html

130. SMS Short Code: http://en.wikipedia.org/wiki/Short_code

131. Secure lock screen reporting: http://developer.android.com/reference/android/app/KeyguardManager.html#isDeviceSecure()

132. Android Open Source Encryption: http://source.android.com/docs/security/features/encryption

133. Android Keystore System: https://developer.android.com/training/articles/keystore.html

134. KeyChain API: https://developer.android.com/reference/android/security/KeyChain.html

135. Keystore API: https://developer.android.com/reference/java/security/KeyStore.html

136. Gatekeeper HAL: http://source.android.com/docs/security/features/authentication/gatekeeper

137. Android Compatibility Program Overview: http://source.android.com/docs/compatibility

138. SystemUpdatePolicy class: http://developer.android.com/reference/android/app/admin/SystemUpdatePolicy.html

139. Android Compatibility forum: https://groups.google.com/forum/#!forum/android-compatibility

140. Handling app links: https://developer.android.com/training/app-links/index.html

141. Google Digital Asset Links: https://developers.google.com/digital-asset-links

Many of these resources are derived directly or indirectly from the Android SDK, and will be functionally identical to the information in that SDK's documentation. In any cases where this Compatibility Definition or the Compatibility Test Suite disagrees with the SDK documentation, the SDK documentation is considered authoritative. Any technical details provided in the references included above are considered by inclusion to be part of this Compatibility Definition.