Definição de compatibilidade do Android 15

1. Introdução

Este documento enumera os requisitos que devem ser atendidos para que os dispositivos sejam compatíveis com Android 15.

O uso de "DEVE", "NÃO DEVE", "REQUERIDO", "DEVE", "NÃO DEVE", "DEVE", "NÃO DEVE", "RECOMENDADO", "PODE" e "OPCIONAL" é de acordo com a IETF padrão definido em RFC2119 .

Conforme usado neste documento, um "implementador de dispositivo" ou "implementador" é uma pessoa ou organização que desenvolve uma solução de hardware/software executando o Android 15. Uma "implementação de dispositivo" ou "implementação" é a solução de hardware/software assim desenvolvida.

Para serem consideradas compatíveis com o Android 15, as implementações de dispositivos DEVEM atender aos requisitos apresentados nesta definição de compatibilidade, incluindo quaisquer documentos incorporados por referência.

Quando esta definição ou os testes de software descritos na seção 10 forem silenciosos, ambíguos ou incompletos, é responsabilidade do implementador do dispositivo garantir a compatibilidade com as implementações existentes.

Por esse motivo, o Android Open Source Project é ao mesmo tempo a referência e a implementação preferida do Android. É FORTEMENTE RECOMENDADO que os implementadores de dispositivos baseiem suas implementações, tanto quanto possível, no código-fonte "upstream" disponível no Android Open Source Project. Embora alguns componentes possam hipoteticamente ser substituídos por implementações alternativas, é FORTEMENTE RECOMENDADO não seguir esta prática, pois passar nos testes de software se tornará substancialmente mais difícil. É responsabilidade do implementador garantir total compatibilidade comportamental com a implementação padrão do Android, incluindo e além do Conjunto de testes de compatibilidade. Finalmente, observe que certas substituições e modificações de componentes são explicitamente proibidas por este documento.

Muitos dos recursos vinculados neste documento são derivados direta ou indiretamente do Android SDK e serão funcionalmente idênticos às informações contidas na documentação desse SDK. Em qualquer caso em que esta Definição de Compatibilidade ou o Conjunto de Testes de Compatibilidade discordem da documentação do SDK, a documentação do SDK será considerada oficial. Quaisquer detalhes técnicos fornecidos nos recursos vinculados ao longo deste documento são considerados, por inclusão, como parte desta Definição de Compatibilidade.

1.1 Estrutura do Documento

1.1.1. Requisitos por tipo de dispositivo

A seção 2 contém todos os requisitos aplicáveis ​​a um tipo específico de dispositivo. Cada subseção da Seção 2 é dedicada a um tipo específico de dispositivo.

Todos os outros requisitos, que se aplicam universalmente a qualquer implementação de dispositivo Android, estão listados nas seções após a Seção 2 . Esses requisitos são referenciados como “Requisitos Básicos” neste documento.

1.1.2. ID do requisito

O ID do requisito é atribuído para requisitos MUST.

• O ID é atribuído apenas para requisitos MUST.
• Os requisitos FORTEMENTE RECOMENDADOS são marcados como [SR], mas o ID não é atribuído.
• O ID consiste em: ID do tipo de dispositivo - ID da condição - ID do requisito (por exemplo, C-0-1).

Cada ID é definido conforme abaixo:

• ID do tipo de dispositivo (veja mais em 2. Tipos de dispositivos )
  • C: Core (requisitos aplicados a todas as implementações de dispositivos Android)
  • H: Dispositivo portátil Android
  • T: dispositivo de televisão Android
  • R: Implementação do Android Automotive
  • W: Implementação do Android Watch
  • Guia: Implementação do Android Tablet
• ID da condição
  • Quando o requisito é incondicional, esse ID é definido como 0.
  • Quando o requisito é condicional, 1 é atribuído para a 1ª condição e o número é incrementado em 1 dentro da mesma seção e do mesmo tipo de dispositivo.
• ID do requisito
  • Esse ID começa em 1 e aumenta em 1 na mesma seção e na mesma condição.

1.1.3. ID do requisito na Seção 2

Os IDs de requisitos na Seção 2 têm duas partes. O primeiro corresponde a um ID de seção conforme descrito acima. A segunda parte identifica o fator de forma e o requisito específico do fator de forma.

ID da seção que é seguido pelo ID do Requisito descrito acima.

• O ID na Seção 2 consiste em: ID da Seção / ID do Tipo de Dispositivo - ID da Condição - ID do Requisito (por exemplo, 7.4.3/A-0-1).

2. Tipos de dispositivos

O Android Open Source Project fornece uma pilha de software que pode ser usada para vários tipos de dispositivos e formatos. Para oferecer suporte à segurança dos dispositivos, espera-se que a pilha de software, incluindo qualquer sistema operacional substituto ou uma implementação de kernel alternativa, seja executada em um ambiente seguro, conforme descrito na seção 9 e em outras partes deste CDD. Existem alguns tipos de dispositivos que possuem um ecossistema de distribuição de aplicativos relativamente melhor estabelecido.

Esta seção descreve esses tipos de dispositivos e requisitos e recomendações adicionais aplicáveis ​​a cada tipo de dispositivo.

Todas as implementações de dispositivos Android que não se enquadram em nenhum dos tipos de dispositivos descritos DEVEM atender a todos os requisitos nas outras seções desta Definição de Compatibilidade.

2.1 Configurações do dispositivo

Para conhecer as principais diferenças na configuração de hardware por tipo de dispositivo, consulte os requisitos específicos do dispositivo a seguir nesta seção.

2.2. Requisitos portáteis

Um dispositivo portátil Android refere-se a uma implementação de dispositivo Android que normalmente é usada segurando-o na mão, como um mp3 player, telefone ou tablet.

As implementações de dispositivos Android são classificadas como portáteis se atenderem a todos os critérios a seguir:

• Tenha uma fonte de energia que proporcione mobilidade, como uma bateria.
• Tenha um tamanho de tela diagonal físico na faixa de 4 a 8 polegadas.
• Possui uma interface de entrada touchscreen.

Os requisitos adicionais no restante desta seção são específicos para implementações de dispositivos portáteis Android.

Nota: Os requisitos que não se aplicam a dispositivos Android Tablet estão marcados com um *.

2.2.1. Hardware

Implementações de dispositivos portáteis:

• [ 7.1 .1.1/H-0-1] DEVE ter pelo menos um monitor compatível com Android que meça pelo menos 2,2" na borda curta e 3,4" na borda longa.

• [ 7.1 .1.3/H-SR-1] São FORTEMENTE RECOMENDADOS para fornecer aos usuários a possibilidade de alterar o tamanho da tela (densidade da tela).

• [ 7.1.1.1/H-0-2 ] DEVE suportar a composição de GPU de buffers gráficos pelo menos tão grande quanto a resolução mais alta de qualquer monitor integrado.

• [ 7.1 .1.1/H-0-3]* DEVE mapear cada display UI_MODE_NORMAL disponibilizado para aplicativos de terceiros em uma área de exibição física desobstruída que tenha pelo menos 2,2" polegadas na borda curta e 3,4" polegadas na borda longa.

• [ 7.1 .1.3/H-0-1]* DEVE definir o valor de DENSITY_DEVICE_STABLE como 92% ou maior que a densidade física real do display correspondente.

Se as implementações de dispositivos portáteis reivindicarem suporte para exibições de alta faixa dinâmica por meio de Configuration.isScreenHdr() , elas:

• [ 7.1 .4.5/H-1-1] DEVE anunciar suporte para as extensões EGL_EXT_gl_colorspace_bt2020_pq , EGL_EXT_surface_SMPTE2086_metadata , EGL_EXT_surface_CTA861_3_metadata , VK_EXT_swapchain_colorspace e VK_EXT_hdr_metadata .

Implementações de dispositivos portáteis:

• [ 7.1 .4.6/H-0-1] DEVE informar se o dispositivo oferece suporte ao recurso de criação de perfil de GPU por meio de uma propriedade do sistema graphics.gpu.profiler.support .

Se as implementações de dispositivos portáteis declararem suporte por meio de uma propriedade de sistema graphics.gpu.profiler.support , elas:

• [ 7.1.4.6/H-1-1 ] DEVE relatar como saída um rastreamento protobuf que esteja em conformidade com o esquema para contadores de GPU e estágios de renderização de GPU definidos na documentação do Perfetto .
• [ 7.1 .4.6/H-1-2] DEVE relatar valores compatíveis para os contadores de GPU do dispositivo seguindo o proto do pacote de rastreamento do contador de GPU .
• [ 7.1 .4.6/H-1-3] DEVE relatar valores compatíveis para os RenderStages da GPU do dispositivo seguindo o proto do pacote de rastreamento do estágio de renderização .
• [ 7.1 .4.6/H-1-4] DEVE relatar um tracepoint de frequência da GPU conforme especificado pelo formato: power/gpu_frequency .

Implementações de dispositivos portáteis:

• [ 7.1.5 /H-0-1] DEVE incluir suporte para modo de compatibilidade de aplicativos legados conforme implementado pelo código-fonte aberto Android upstream. Ou seja, as implementações de dispositivos NÃO DEVEM alterar os gatilhos ou limites nos quais o modo de compatibilidade é ativado e NÃO DEVEM alterar o comportamento do próprio modo de compatibilidade.
• [ 7.2.1 /H-0-1] DEVE incluir suporte para aplicativos Input Method Editor (IME) de terceiros.
• [ 7.2 .3/H-0-2] DEVE enviar o evento de pressionamento normal e longo da função Voltar ( KEYCODE_BACK ) para o aplicativo em primeiro plano. Esses eventos NÃO DEVEM ser consumidos pelo sistema e PODEM ser acionados fora do dispositivo Android (por exemplo, teclado de hardware externo conectado ao dispositivo Android).
• [ 7.2 .3/H-0-3] DEVE fornecer a função Home em todos os monitores compatíveis com Android que fornecem a tela inicial.
• [ 7.2 .3/H-0-4] DEVE fornecer a função Voltar em todos os monitores compatíveis com Android e a função Recentes em pelo menos um dos monitores compatíveis com Android.
• [ 7.2.4 /H-0-1] DEVE suportar entrada de tela sensível ao toque.
• [ 7.2 .4/H-SR-1] É FORTEMENTE RECOMENDADO iniciar o aplicativo de assistência selecionado pelo usuário, em outras palavras, o aplicativo que implementa VoiceInteractionService ou uma atividade que manipula ACTION_ASSIST ao pressionar longamente KEYCODE_MEDIA_PLAY_PAUSE ou KEYCODE_HEADSETHOOK se a atividade em primeiro plano não lida com esses eventos de pressão longa.
• [ 7.3 .1/H-SR-1] É FORTEMENTE RECOMENDADO incluir um acelerômetro de 3 eixos.

Se as implementações de dispositivos portáteis incluírem um acelerômetro de 3 eixos, elas:

• [ 7.3.1 /H-1-1] DEVE ser capaz de relatar eventos até uma frequência de pelo menos 100 Hz.

Se as implementações de dispositivos portáteis incluírem um receptor GPS/GNSS e reportarem a capacidade aos aplicativos por meio do sinalizador de recurso android.hardware.location.gps , elas:

• [ 7.3 .3/H-2-1] DEVE reportar medições GNSS, assim que forem encontradas, mesmo que uma localização calculada a partir de GPS/GNSS ainda não tenha sido reportada.
• [ 7.3.3 /H-2-2] DEVE relatar pseudodistâncias GNSS e taxas de pseudodistância que, em condições de céu aberto após a determinação da localização, enquanto estacionário ou em movimento com menos de 0,2 metro por segundo quadrado de aceleração, sejam suficientes para calcular posição dentro de 20 metros e velocidade dentro de 0,2 metros por segundo, pelo menos 95% do tempo.

Se as implementações de dispositivos portáteis incluírem um giroscópio de 3 eixos, elas:

• [ 7.3.4 /H-3-1] DEVE ser capaz de relatar eventos até uma frequência de pelo menos 100 Hz.
• [ 7.3.4 /H-3-2] DEVE ser capaz de medir mudanças de orientação de até 1000 graus por segundo.

Implementações de dispositivos portáteis que podem fazer uma chamada de voz e indicar qualquer valor diferente de PHONE_TYPE_NONE em getPhoneType :

• [ 7.3 .8/H] DEVE incluir um sensor de proximidade.

Implementações de dispositivos portáteis:

• [ 7.3 .11/H-SR-1] São FORTEMENTE RECOMENDADOS para suportar sensor de pose com 6 graus de liberdade.

Iniciar novos requisitos para 15 (AOSP experimental)

[7.4.3] (visualização de 8 de abril de 2024)

• [ 7.4.3 /H] DEVE incluir suporte para Bluetooth e Bluetooth LE.
• [ 7.4.3 /H-0-1] DEVE incluir suporte para Bluetooth e Bluetooth LE.

Implementações de dispositivos portáteis que incluem suporte para Bluetooth LE:

• [ 7.4 .3/H-SR-1] São FORTEMENTE RECOMENDADOS para suportar extensão de comprimento de pacote de dados Bluetooth LE.

  Nota: Este requisito [7.4.3/H-SR-1] se tornará OBRIGATÓRIO em uma versão futura do Android.

Acabar com novos requisitos

[7.4.3] (visualização de 26 de fevereiro de 2024)

• [ 7.4.3 /H-0-1] DEVE incluir suporte para Bluetooth e Bluetooth LE.
• [ 7.4.3 /H-0-2] DEVE suportar Bluetooth 4.2.
• [ 7.4 .3/H-SR-1] São FORTEMENTE RECOMENDADOS para suportar extensão de comprimento de pacote de dados Bluetooth LE.

Nota: O requisito fortemente recomendado [7.4.3/H-SR-1] se tornará OBRIGATÓRIO em uma versão futura do Android.

Acabar com novos requisitos

[7.4.3] (visualização de 11 de dezembro de 2023)

• [ 7.4.3 /H-0-1] DEVE incluir suporte para Bluetooth e Bluetooth LE.
• [ 7.4 .3/H-0-2] DEVE suportar Bluetooth 4.2 e extensão de comprimento de dados Bluetooth LE.
• [ 7.4.3 /H-0-3] DEVE suportar GATT ATT_MTU de no mínimo 247 bytes.
• [ 7.4.3 /H-0-4] DEVE suportar Serviço BTP com 3 características C1, C2 e C3, conforme definido na Especificação Principal da Matéria 1.0 .

Acabar com novos requisitos

Se os dispositivos suportarem o protocolo WiFi Neighbor Awareness Network (NAN) declarando PackageManager.FEATURE_WIFI_AWARE e a localização Wi-Fi (Wi-Fi Round Trip Time — RTT) declarando PackageManager.FEATURE_WIFI_RTT , então eles:

• [ 7.4 .2.5/H-1-1] DEVE relatar o alcance com precisão de +/- 1 metro na largura de banda de 160 MHz no 68º percentil (conforme calculado com a função de distribuição cumulativa), +/- 2 metros na largura de banda de 80 MHz no percentil 68, +/- 4 metros com largura de banda de 40 MHz no percentil 68 e +/- 8 metros com largura de banda de 20 MHz no percentil 68 em distâncias de 10 cm, 1 m, 3 m e 5 m, como observado por meio da API Android WifiRttManager#startRanging .

• [ 7.4 .2.5/H-SR-1] É FORTEMENTE RECOMENDADO relatar o alcance com precisão de +/- 1 metro na largura de banda de 160 MHz no 90º percentil (conforme calculado com a função de distribuição cumulativa), +/- 2 metros em Largura de banda de 80 MHz no percentil 90, +/- 4 metros na largura de banda de 40 MHz no percentil 90 e +/- 8 metros na largura de banda de 20 MHz no percentil 90 em distâncias de 10 cm, conforme observado por meio do WifiRttManager#startRanging Android API .

É FORTEMENTE RECOMENDADO seguir as etapas de configuração de medição especificadas em Calibração de presença .

Se as implementações de dispositivos portáteis declararem FEATURE_BLUETOOTH_LE , elas:

• [ 7.4 .3/H-1-3] DEVE medir e compensar o deslocamento Rx para garantir que a mediana do BLE RSSI seja -50dBm +/- 15 dB a 1 m de distância de um dispositivo de referência transmitindo em ADVERTISE_TX_POWER_HIGH .
• [ 7.4 .3/H-1-4] DEVE medir e compensar o deslocamento de Tx para garantir que a mediana do BLE RSSI seja -50dBm +/- 15 dB ao digitalizar a partir de um dispositivo de referência posicionado a 1 m de distância e transmitindo em ADVERTISE_TX_POWER_HIGH .

Se as implementações de dispositivos portáteis incluírem uma conexão medida, elas:

• [ 7.4 .7/H-1-1] DEVE fornecer o modo de economia de dados.

Se as implementações de dispositivos portáteis incluírem um dispositivo de câmera lógica que lista recursos usando CameraMetadata.REQUEST_AVAILABLE_CAPABILITIES_LOGICAL_MULTI_CAMERA , elas:

• [ 7.5.4 /H-1-1] DEVE ter campo de visão normal (FOV) por padrão e DEVE estar entre 50 e graus.

Implementações de dispositivos portáteis:

• [ 7.6 .1/H-0-1] DEVE ter pelo menos 4 GB de armazenamento não volátil disponível para dados privados do aplicativo (também conhecido como partição "/data").
• [ 7.6 .1/H-0-2] DEVE retornar "true" para ActivityManager.isLowRamDevice() quando houver menos de 1 GB de memória disponível para o kernel e espaço do usuário.

Se as implementações de dispositivos portáteis declararem suporte apenas para uma ABI de 32 bits:

• [ 7.6.1 /H-1-1] A memória disponível para o kernel e o espaço do usuário DEVE ser de pelo menos 416 MB se a exibição padrão usar resoluções de framebuffer de até qHD (por exemplo, FWVGA).

• [ 7.6.1 /H-2-1] A memória disponível para o kernel e o espaço do usuário DEVE ser de pelo menos 592 MB se a exibição padrão usar resoluções de framebuffer até HD+ (por exemplo, HD, WSVGA).

• [ 7.6.1 /H-3-1] A memória disponível para o kernel e espaço do usuário DEVE ser de pelo menos 896 MB se a exibição padrão usar resoluções de framebuffer de até FHD (por exemplo, WSXGA +).

• [ 7.6.1 /H-4-1] A memória disponível para o kernel e o espaço do usuário DEVE ser de pelo menos 1344 MB se a exibição padrão usar resoluções de framebuffer até QHD (por exemplo, QWXGA).

Se as implementações de dispositivos portáteis declararem suporte a qualquer ABI de 64 bits (com ou sem qualquer ABI de 32 bits):

• [ 7.6.1 /H-5-1] A memória disponível para o kernel e o espaço do usuário DEVE ser de pelo menos 816 MB se a exibição padrão usar resoluções de framebuffer de até qHD (por exemplo, FWVGA).

• [ 7.6.1 /H-6-1] A memória disponível para o kernel e o espaço do usuário DEVE ser de pelo menos 944 MB se a exibição padrão usar resoluções de framebuffer até HD+ (por exemplo, HD, WSVGA).

• [ 7.6.1 /H-7-1] A memória disponível para o kernel e espaço do usuário DEVE ser de pelo menos 1280 MB se a exibição padrão usar resoluções de framebuffer de até FHD (por exemplo, WSXGA +).

• [ 7.6 .1/H-8-1] A memória disponível para o kernel e espaço do usuário DEVE ser de pelo menos 1824 MB se a exibição padrão usar resoluções de framebuffer até QHD (por exemplo, QWXGA).

Observe que a "memória disponível para o kernel e espaço do usuário" acima se refere ao espaço de memória fornecido além de qualquer memória já dedicada a componentes de hardware, como rádio, vídeo e assim por diante, que não estão sob o controle do kernel nas implementações de dispositivos.

Se as implementações de dispositivos portáteis incluírem menos ou igual a 1 GB de memória disponível para o kernel e espaço do usuário, elas:

• [ 7.6 .1/H-9-1] DEVE declarar o sinalizador de recurso android.hardware.ram.low .
• [ 7.6 .1/H-9-2] DEVE ter pelo menos 1,1 GB de armazenamento não volátil para dados privados do aplicativo (também conhecida como partição "/data").

Se as implementações de dispositivos portáteis incluírem mais de 1 GB de memória disponível para o kernel e espaço do usuário, elas:

• [ 7.6 .1/H-10-1] DEVE ter pelo menos 4 GB de armazenamento não volátil disponível para dados privados do aplicativo (também conhecido como partição "/data").
• DEVE declarar o sinalizador de recurso android.hardware.ram.normal .

Se as implementações de dispositivos portáteis incluírem mais ou igual a 2 GB e menos de 4 GB de memória disponível para o kernel e espaço do usuário, elas:

• [7.6.1/H-SR-1] São FORTEMENTE RECOMENDADOS para oferecer suporte apenas ao espaço do usuário de 32 bits (aplicativos e código do sistema)

Se as implementações de dispositivos portáteis incluírem menos de 2 GB de memória disponível para o kernel e espaço do usuário, elas:

• [7.6.1/H-1-1] DEVE suportar apenas ABIs de 32 bits.

Implementações de dispositivos portáteis:

• [ 7.6.2 /H-0-1] NÃO DEVE fornecer um armazenamento compartilhado de aplicativo menor que 1 GiB.
• [ 7.7.1 /H] DEVE incluir uma porta USB com suporte para modo periférico.

Iniciar novos requisitos para 15 (AOSP experimental)

[7.7.1/H-1-1] (visualização de 11 de dezembro de 2023)

Se as implementações de dispositivos portáteis incluírem uma porta USB compatível com um controlador operando em modo periférico, elas:

• [ 7.7.1 /H-1-1] DEVE implementar a API Android Open Accessory (AOA).

Acabar com novos requisitos

Se as implementações de dispositivos portáteis incluírem uma porta USB compatível com o modo host, elas:

• [ 7.7.2 /H-1-1] DEVE implementar a classe de áudio USB conforme documentado na documentação do Android SDK.

Implementações de dispositivos portáteis:

• [ 7.8.1 /H-0-1] DEVE incluir um microfone.
• [ 7.8 .2/H-0-1] DEVE ter uma saída de áudio e declarar android.hardware.audio.output .

Se as implementações de dispositivos portáteis forem capazes de atender a todos os requisitos de desempenho para suportar o modo VR e incluir suporte para ele, elas:

• [ 7.9 .1/H-1-1] DEVE declarar o sinalizador de recurso android.hardware.vr.high_performance .
• [ 7.9 .1/H-1-2] DEVE incluir um aplicativo que implemente android.service.vr.VrListenerService que possa ser habilitado por aplicativos VR via android.app.Activity#setVrModeEnabled .

Se as implementações de dispositivos portáteis incluírem uma ou mais portas USB-C no modo host e implementarem (classe de áudio USB), além dos requisitos na seção 7.7.2 , elas:

• [ 7.8.2.2/H-1-1 ] DEVE fornecer o seguinte mapeamento de software de códigos HID:

Função	Mapeamentos	Contexto	Comportamento
A	Página de uso HID : 0x0C Uso HID : 0x0CD Chave do kernel : KEY_PLAYPAUSE Chave Android : KEYCODE_MEDIA_PLAY_PAUSE	Reprodução de mídia	Entrada : toque curto Saída : Reproduzir ou pausar
			Entrada : Pressão longa Saída : iniciar comando de voz Envia : android.speech.action.VOICE_SEARCH_HANDS_FREE se o dispositivo estiver bloqueado ou a tela desligada. Envia android.speech.RecognizerIntent.ACTION_WEB_SEARCH caso contrário
		Chamada recebida	Entrada : toque curto Saída : Aceitar chamada
			Entrada : Pressão longa Saída : Rejeitar chamada
		Chamada em andamento	Entrada : toque curto Saída : Encerrar chamada
			Entrada : Pressão longa Saída : ativar ou desativar o microfone
B	Página de uso HID : 0x0C Uso de HID : 0x0E9 Chave do kernel : KEY_VOLUMEUP Chave do Android : VOLUME_UP	Reprodução de mídia, chamada em andamento	Entrada : toque curto ou longo Saída : Aumenta o volume do sistema ou do fone de ouvido
C	Página de uso HID : 0x0C Uso de HID : 0x0EA Chave do kernel : KEY_VOLUMEDOWN Chave do Android : VOLUME_DOWN	Reprodução de mídia, chamada em andamento	Entrada : toque curto ou longo Saída : Diminui o volume do sistema ou do fone de ouvido
D	Página de uso HID : 0x0C Uso de HID : 0x0CF Chave do kernel : KEY_VOICECOMMAND Chave Android : KEYCODE_VOICE_ASSIST	Todos. Pode ser acionado em qualquer instância.	Entrada : toque curto ou longo Saída : iniciar comando de voz

• [ 7.8 .2.2/H-1-2] DEVE acionar ACTION_HEADSET_PLUG após a inserção de um plugue, mas somente após as interfaces de áudio USB e terminais terem sido devidamente enumerados para identificar o tipo de terminal conectado.

Quando o terminal de áudio USB tipo 0x0302 é detectado, eles:

• [ 7.8 .2.2/H-2-1] DEVE transmitir a intenção ACTION_HEADSET_PLUG com o extra "microfone" definido como 0.

Quando o terminal de áudio USB tipo 0x0402 é detectado, eles:

• [ 7.8 .2.2/H-3-1] DEVE transmitir a intenção ACTION_HEADSET_PLUG com "microfone" extra definido como 1.

Quando a API AudioManager.getDevices() é chamada enquanto o periférico USB está conectado, eles:

• [ 7.8 .2.2/H-4-1] DEVE listar um dispositivo do tipo AudioDeviceInfo.TYPE_USB_HEADSET e função isSink() se o campo do tipo de terminal de áudio USB for 0x0302.

• [ 7.8 .2.2/H-4-2] DEVE listar um dispositivo do tipo AudioDeviceInfo.TYPE_USB_HEADSET e função isSink() se o campo do tipo de terminal de áudio USB for 0x0402.

• [ 7.8 .2.2/H-4-3] DEVE listar um dispositivo do tipo AudioDeviceInfo.TYPE_USB_HEADSET e função isSource() se o campo do tipo de terminal de áudio USB for 0x0402.

• [ 7.8 .2.2/H-4-4] DEVE listar um dispositivo do tipo AudioDeviceInfo.TYPE_USB_DEVICE e função isSink() se o campo do tipo de terminal de áudio USB for 0x603.

• [ 7.8 .2.2/H-4-5] DEVE listar um dispositivo do tipo AudioDeviceInfo.TYPE_USB_DEVICE e função isSource() se o campo do tipo de terminal de áudio USB for 0x604.

• [ 7.8 .2.2/H-4-6] DEVE listar um dispositivo do tipo AudioDeviceInfo.TYPE_USB_DEVICE e função isSink() se o campo do tipo de terminal de áudio USB for 0x400.

• [ 7.8 .2.2/H-4-7] DEVE listar um dispositivo do tipo AudioDeviceInfo.TYPE_USB_DEVICE e função isSource() se o campo do tipo de terminal de áudio USB for 0x400.

• [ 7.8 .2.2/H-SR-1] São FORTEMENTE RECOMENDADOS na conexão de um periférico de áudio USB-C, para realizar enumeração de descritores USB, identificar tipos de terminais e transmitir Intent ACTION_HEADSET_PLUG em menos de 1000 milissegundos.

Iniciar novos requisitos para 15 (AOSP experimental)

[5.6/H-1-1 e 5.6/H-1-2] (visualização de 5 de fevereiro de 2024)

Se for para implementações de dispositivos portáteis que declaram android.hardware.audio.output e android.hardware.microphone , eles: consulte os requisitos RTL e TTL na seção 5.6 .

• [ 5.6 /H-1-1] DEVE ter uma latência média contínua de ida e volta de 300 milissegundos ou menos em 5 medições, com um desvio médio absoluto inferior a 30 ms, nos seguintes caminhos de dados: "alto-falante para microfone", 3,5 mm adaptador de loopback (se compatível), loopback USB (se compatível).

• [ 5.6 /H-1-2] DEVE ter uma latência média Tap-to-tone de 300 milissegundos ou menos em pelo menos 5 medições no caminho de dados do alto-falante para o microfone.

Acabar com novos requisitos

Um atuador ressonante linear (LRA) é um sistema de mola de massa única que possui uma frequência ressonante dominante onde a massa se traduz na direção do movimento desejado.

Se as implementações de dispositivos portáteis incluírem pelo menos um atuador ressonante linear 7.10 de uso geral, elas:

• [ 7.10 /H] DEVE posicionar o atuador próximo ao local onde o dispositivo normalmente é segurado ou tocado pelas mãos.

• [ 7.10 /H] DEVE mover o atuador háptico no eixo X (esquerda-direita) da orientação natural do dispositivo.

Se as implementações de dispositivos portáteis tiverem um atuador háptico de uso geral que seja um atuador ressonante linear do eixo X (LRA), elas:

• [ 7.10 /H] DEVE ter a frequência de ressonância do LRA do eixo X abaixo de 200 Hz.

Se as implementações de dispositivos portáteis seguirem o mapeamento de constantes táteis, elas:

• [ 7.10 /H]* DEVE verificar o status da implementação executando as APIs android.os.Vibrator.areAllEffectsSupported() e android.os.Vibrator.arePrimitivesSupported() .

• [ 7.10 /H]* DEVE realizar uma avaliação de qualidade para constantes táteis.

• [ 7.10 /H]* DEVE verificar e atualizar, se necessário, a configuração de fallback para primitivas não suportadas, conforme descrito nas orientações de implementação para constantes.

2.2.2. Multimídia

As implementações de dispositivos portáteis DEVEM suportar os seguintes formatos de codificação e decodificação de áudio e disponibilizá-los para aplicativos de terceiros:

• [ 5.1 /H-0-1] AMR-NB
• [ 5.1 /H-0-2] AMR-WB
• [ 5.1 /H-0-3] Perfil MPEG-4 AAC (AAC LC)
• [ 5.1 /H-0-4] Perfil MPEG-4 HE AAC (AAC+)
• [ 5.1 /H-0-5] AAC ELD (AAC de baixo atraso aprimorado)

As implementações de dispositivos portáteis DEVEM suportar os seguintes formatos de codificação de vídeo e disponibilizá-los para aplicativos de terceiros:

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

As implementações de dispositivos portáteis DEVEM suportar os seguintes formatos de decodificação de vídeo e disponibilizá-los para aplicativos de terceiros:

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

2.2.3. Programas

Implementações de dispositivos portáteis:

• [ 3.2.3.1 /H-0-1] DEVE ter um aplicativo que lide com as intenções ACTION_GET_CONTENT , ACTION_OPEN_DOCUMENT , ACTION_OPEN_DOCUMENT_TREE e ACTION_CREATE_DOCUMENT conforme descrito nos documentos do SDK e forneça ao usuário recursos para acessar os dados do provedor de documentos usando a API DocumentsProvider .
• [ 3.2.3.1 /H-0-2]* DEVE pré-carregar um ou mais aplicativos ou componentes de serviço com um manipulador de intenções, para todos os padrões de filtro de intenções públicas definidos pelas seguintes intenções de aplicativos listadas aqui .
• [ 3.2.3.1 /H-SR-1] É FORTEMENTE RECOMENDADO pré-carregar um aplicativo de e-mail que possa lidar com intenções ACTION_SENDTO ou ACTION_SEND ou ACTION_SEND_MULTIPLE para enviar um e-mail.
• [ 3.4.1 /H-0-1] DEVE fornecer uma implementação completa da API android.webkit.Webview .
• [ 3.4.2 /H-0-1] DEVE incluir um aplicativo de navegador independente para navegação geral do usuário na web.
• [ 3.8.1 /H-SR-1] É FORTEMENTE RECOMENDADO implementar um iniciador padrão que suporte fixação de atalhos, widgets e widgetFeatures no aplicativo.
• [ 3.8.1 /H-SR-2] É FORTEMENTE RECOMENDADO implementar um inicializador padrão que forneça acesso rápido aos atalhos adicionais fornecidos por aplicativos de terceiros por meio da API ShortcutManager .
• [ 3.8 .1/H-SR-3] É FORTEMENTE RECOMENDADO incluir um aplicativo inicializador padrão que mostre emblemas para os ícones do aplicativo.
• [ 3.8.2 /H-SR-1] São FORTEMENTE RECOMENDADOS para oferecer suporte a widgets de aplicativos de terceiros.
• [ 3.8.3 /H-0-1] DEVE permitir que aplicativos de terceiros notifiquem os usuários sobre eventos notáveis ​​por meio das classes de API Notification e NotificationManager .
• [ 3.8.3 /H-0-2] DEVE oferecer suporte a notificações avançadas.
• [ 3.8.3 /H-0-3] DEVE suportar notificações de alerta.
• [ 3.8.3 /H-0-4] DEVE incluir uma aba de notificação, fornecendo ao usuário a capacidade de controlar diretamente (por exemplo, responder, suspender, dispensar, bloquear) as notificações por meio de recursos do usuário, como botões de ação ou o painel de controle, conforme implementado na AOSP.
• [ 3.8.3 /H-0-5] DEVE exibir as opções fornecidas por meio de RemoteInput.Builder setChoices() na aba de notificação.
• [ 3.8.3 /H-SR-1] É FORTEMENTE RECOMENDADO exibir a primeira opção fornecida por meio de RemoteInput.Builder setChoices() na aba de notificação sem interação adicional do usuário.
• [ 3.8.3 /H-SR-2] É FORTEMENTE RECOMENDADO exibir todas as opções fornecidas por meio de RemoteInput.Builder setChoices() na aba de notificações quando o usuário expande todas as notificações na aba de notificações.
• [ 3.8 .3.1/H-SR-1] São FORTEMENTE RECOMENDADOS para exibir ações para as quais Notification.Action.Builder.setContextual é definido como true em linha com as respostas exibidas por Notification.Remoteinput.Builder.setChoices .
• [ 3.8.4 /H-SR-1] É FORTEMENTE RECOMENDADO implementar um assistente no dispositivo para lidar com a ação Assist .

Se as implementações de dispositivos portáteis suportarem notificações MediaStyle , elas:

• [ 3.8 .3.1/H-SR-2] São FORTEMENTE RECOMENDADOS para fornecer uma capacidade de usuário (por exemplo, comutador de saída) acessada a partir da interface do sistema que permite aos usuários alternar entre rotas de mídia disponíveis apropriadas (por exemplo, dispositivos Bluetooth e rotas fornecidas para MediaRouter2Manager ) quando um aplicativo publica uma notificação MediaStyle com um token MediaSession .

Se as implementações do dispositivo, incluindo a tecla de navegação da função recente, conforme detalhado na seção 7.2.3, alterarem a interface, elas:

• [ 3.8.3 /H-1-1] DEVE implementar o comportamento de fixação de tela e fornecer ao usuário um menu de configurações para alternar o recurso.

Se as implementações de dispositivos portáteis suportarem a ação Assist, elas:

• [ 3.8.4 /H-SR-2] É FORTEMENTE RECOMENDADO usar um toque longo na tecla HOME como a interação designada para iniciar o aplicativo de assistência, conforme descrito na seção 7.2.3 . DEVE iniciar o aplicativo de assistência selecionado pelo usuário, em outras palavras, o aplicativo que implementa VoiceInteractionService ou uma atividade que manipula a intenção ACTION_ASSIST .

Se as implementações de dispositivos portáteis suportarem conversation notifications e agrupá-las em uma seção separada das notificações de alerta e silenciosas sem conversa, elas:

• [ 3.8.4 /H-1-1]* DEVE exibir notificações de conversa antes das notificações que não são de conversa, com exceção de notificações de serviço em primeiro plano em andamento e notificações de importância: alta .

Se as implementações de dispositivos portáteis Android suportarem uma tela de bloqueio, elas:

• [ 3.8.10 /H-1-1] DEVE exibir as notificações da tela de bloqueio, incluindo o modelo de notificação de mídia.

Se as implementações de dispositivos portáteis suportarem uma tela de bloqueio segura, elas:

• [ 3.9 /H-1-1] DEVE implementar toda a gama de políticas de administração de dispositivos definidas na documentação do Android SDK.

Se as implementações de dispositivos portáteis incluírem suporte para APIs ControlsProviderService e Control e permitirem que aplicativos de terceiros publiquem controles de dispositivos , então elas:

• [ 3.8.16 /H-1-1] DEVE declarar o sinalizador de recurso android.software.controls e defini-lo como true .
• [ 3.8.16 /H-1-2] DEVE fornecer ao usuário a capacidade de adicionar, editar, selecionar e operar os controles de dispositivo favoritos do usuário a partir dos controles registrados pelos aplicativos de terceiros por meio do ControlsProviderService e das APIs Control .
• [ 3.8.16 /H-1-3] DEVE fornecer acesso a esta capacidade de usuário dentro de três interações a partir de um inicializador padrão.

• [ 3.8.16 /H-1-4] DEVE renderizar com precisão neste recurso do usuário o nome e o ícone de cada aplicativo de terceiros que fornece controles por meio da API ControlsProviderService , bem como quaisquer campos especificados fornecidos pelas APIs Control .

• [ 3.8.16 /H-1-5] DEVE fornecer ao usuário a possibilidade de cancelar os controles de dispositivos triviais de autenticação designados pelo aplicativo dos controles registrados pelos aplicativos de terceiros por meio do ControlsProviderService e da API Control Control.isAuthRequired .

• [ 3.8.16 /H-1-6] As implementações de dispositivos DEVEM renderizar com precisão a capacidade do usuário da seguinte forma:

  • Se o dispositivo tiver definido config_supportsMultiWindow=true e o aplicativo declarar os metadados META_DATA_PANEL_ACTIVITY na declaração ControlsProviderService , incluindo o ComponentName de uma atividade válida (conforme definido pela API), o aplicativo DEVE incorporar essa atividade nesta capacidade do usuário.
  • Se o aplicativo não declarar metadados META_DATA_PANEL_ACTIVITY , ele DEVE renderizar os campos especificados conforme fornecidos pela API ControlsProviderService , bem como quaisquer campos especificados fornecidos pelas APIs de controle .

• [ 3.8.16 /H-1-7] Se o aplicativo declarar os metadados META_DATA_PANEL_ACTIVITY , ele DEVE passar o valor da configuração definida em [3.8.16/H-1-5] usando EXTRA_LOCKSCREEN_ALLOW_TRIVIAL_CONTROLS ao iniciar a atividade incorporada.

Por outro lado, se as implementações de dispositivos portáteis não implementarem tais controles, elas:

• [ 3.8.16 /H-2-1] DEVE reportar null para ControlsProviderService e APIs Control .
• [ 3.8 .16/H-2-2] DEVE declarar o sinalizador de recurso android.software.controls e defini-lo como false .

Se as implementações de dispositivos portáteis não estiverem sendo executadas no modo de tarefa de bloqueio , quando o conteúdo for copiado para a área de transferência, elas:

• [3.8.17/H-1-1] DEVE apresentar ao usuário uma confirmação de que os dados foram copiados para a área de transferência (por exemplo, uma miniatura ou alerta de "Conteúdo copiado"). Além disso, inclua aqui uma indicação se os dados da área de transferência serão sincronizados entre dispositivos.

Implementações de dispositivos portáteis:

• [ 3.10 /H-0-1] DEVE oferecer suporte a serviços de acessibilidade de terceiros.
• [ 3.10 /H-SR-1] É FORTEMENTE RECOMENDADO pré-carregar serviços de acessibilidade no dispositivo comparáveis ​​ou superiores à funcionalidade dos serviços de acessibilidade Switch Access e TalkBack (para idiomas suportados pelo mecanismo de conversão de texto em fala pré-instalado), conforme fornecido no projeto de código aberto talkback .
• [ 3.11 /H-0-1] DEVE suportar a instalação de mecanismos TTS de terceiros.
• [ 3.11 /H-SR-1] É FORTEMENTE RECOMENDADO incluir um mecanismo TTS que suporte os idiomas disponíveis no dispositivo.
• [ 3.13 /H-SR-1] É FORTEMENTE RECOMENDADO incluir um componente de UI de configurações rápidas.

Se as implementações de dispositivos portáteis Android declararem suporte para FEATURE_BLUETOOTH ou FEATURE_WIFI , elas:

• [ 3.16 /H-1-1] DEVE oferecer suporte ao recurso de emparelhamento de dispositivo complementar.

Se a função de navegação for fornecida como uma ação baseada em gestos na tela:

• [ 7.2 .3/H] A zona de reconhecimento de gestos para a função Home NÃO DEVE ter mais de 32 dp de altura a partir da parte inferior da tela.

Se as implementações de dispositivos portáteis fornecerem uma função de navegação como um gesto de qualquer lugar nas bordas esquerda e direita da tela:

• [ 7.2 .3/H-0-1] A área de gestos da função de navegação DEVE ter menos de 40 dp de largura em cada lado. A área de gesto DEVE ter 24 dp de largura por padrão.

Se as implementações de dispositivos portáteis suportarem uma tela de bloqueio segura e tiverem mais ou igual a 2 GB de memória disponível para o kernel e espaço do usuário, elas:

• [3.9/H-1-2] DEVE declarar o suporte de perfis gerenciados por meio do sinalizador de recurso android.software.managed_users .

Se as implementações de dispositivos portáteis Android declararem suporte para câmera via android.hardware.camera.any , elas:

• [ 7.5 .4/H-1-1] DEVE respeitar a intenção android.media.action.STILL_IMAGE_CAMERA e android.media.action.STILL_IMAGE_CAMERA_SECURE e iniciar a câmera no modo de imagem estática, conforme descrito no SDK.
• [ 7.5 .4/H-1-2] DEVE respeitar a intenção android.media.action.VIDEO_CAMERA de iniciar a câmera no modo de vídeo conforme descrito no SDK.

Se o aplicativo de configurações da implementação do dispositivo implementar uma funcionalidade dividida , usando incorporação de atividades, então eles:

• [3.2.3.1/H-1-1] DEVE ter uma atividade que lide com a intenção Settings#ACTION_SETTINGS_EMBED_DEEP_LINK_ACTIVITY quando a funcionalidade de divisão estiver ativada. A atividade DEVE ser protegida por android.permission.LAUNCH_MULTI_PANE_SETTINGS_DEEP_LINK e DEVE iniciar a atividade da Intent analisada em Settings#EXTRA_SETTINGS_EMBEDDED_DEEP_LINK_INTENT_URI .

Se as implementações de dispositivos permitirem que os usuários façam chamadas de qualquer tipo, elas

• [ 7.4.1.2 /H-0-1] DEVE declarar o sinalizador de recurso android.software.telecom .
• [ 7.4.1.2 /H-0-2] DEVE implementar a estrutura de telecomunicações .

2.2.4. Desempenho e potência

• [ 8.1 /H-0-1] Latência de quadro consistente . A latência de quadro inconsistente ou um atraso na renderização de quadros NÃO DEVE acontecer com mais frequência do que 5 quadros por segundo e DEVE estar abaixo de 1 quadro por segundo.
• [ 8.1 /H-0-2] Latência da interface do usuário . As implementações de dispositivos DEVEM garantir uma experiência de usuário de baixa latência, rolando uma lista de 10 mil entradas de lista conforme definido pelo Android Compatibility Test Suite (CTS) em menos de 36 segundos.
• [ 8.1 /H-0-3] Troca de tarefas . Quando vários aplicativos forem iniciados, reiniciar um aplicativo já em execução após ele ter sido iniciado DEVE levar menos de 1 segundo.

Implementações de dispositivos portáteis:

• [ 8.2 /H-0-1] DEVE garantir um desempenho de gravação sequencial de pelo menos 5 MB/s.
• [ 8.2 /H-0-2] DEVE garantir um desempenho de gravação aleatória de pelo menos 0,5 MB/s.
• [ 8.2 /H-0-3] DEVE garantir um desempenho de leitura sequencial de pelo menos 15 MB/s.
• [ 8.2 /H-0-4] DEVE garantir um desempenho de leitura aleatória de pelo menos 3,5 MB/s.

Se as implementações de dispositivos portáteis incluírem recursos para melhorar o gerenciamento de energia do dispositivo incluídos no AOSP ou estender os recursos incluídos no AOSP, elas:

• [ 8.3 /H-1-1] DEVE fornecer ao usuário recursos para ativar e desativar o recurso de economia de bateria.
• [ 8.3 /H-1-2] DEVE fornecer ao usuário recursos para exibir todos os aplicativos que estão isentos dos modos de economia de energia App Standby e Doze.

Implementações de dispositivos portáteis:

• [ 8.4 /H-0-1] DEVE fornecer um perfil de energia por componente que defina o valor de consumo atual para cada componente de hardware e o consumo aproximado de bateria causado pelos componentes ao longo do tempo, conforme documentado no site do Android Open Source Project.
• [ 8.4 /H-0-2] DEVE informar todos os valores de consumo de energia em miliamperes-hora (mAh).
• [ 8.4 /H-0-3] DEVE relatar o consumo de energia da CPU por UID de cada processo. O Android Open Source Project atende ao requisito por meio da implementação do módulo do kernel uid_cputime .
• [ 8.4 /H-0-4] DEVE disponibilizar esse uso de energia por meio do comando shell adb shell dumpsys batterystats para o desenvolvedor do aplicativo.
• [ 8.4 /H] DEVE ser atribuído ao próprio componente de hardware se não for possível atribuir o uso de energia do componente de hardware a um aplicativo.

Se as implementações de dispositivos portáteis incluírem uma tela ou saída de vídeo, elas:

• [ 8.4 /H-1-1] DEVE respeitar a intenção android.intent.action.POWER_USAGE_SUMMARY e exibir um menu de configurações que mostre esse uso de energia.

Implementações de dispositivos portáteis:

• [ 8.5 /H-0-1] DEVE fornecer ao usuário a possibilidade de ver todos os aplicativos com serviços ativos em primeiro plano ou trabalhos iniciados pelo usuário, incluindo a duração de cada um desses serviços desde que foi iniciado, conforme descrito no documento do SDK .

• [ 8.5 /H-0-2]DEVE fornecer ao usuário uma oportunidade para interromper um aplicativo que esteja executando um serviço em primeiro plano ou um trabalho iniciado pelo usuário.

2.2.5. Modelo de segurança

Implementações de dispositivos portáteis:

• [9/H-0-1] DEVE declarar o recurso android.hardware.security.model.compatible .
• [ 9.1 /H-0-1] DEVE permitir que aplicativos de terceiros acessem as estatísticas de uso por meio da permissão android.permission.PACKAGE_USAGE_STATS e fornecer um mecanismo acessível ao usuário para conceder ou revogar o acesso a tais aplicativos em resposta ao android.settings.ACTION_USAGE_ACCESS_SETTINGS intenção.

Se as implementações de dispositivos declararem suporte para android.hardware.telephony , elas:

• [ 9.5 /H-1-1] NÃO DEVE definir UserManager.isHeadlessSystemUserMode como true .

Implementações de dispositivos portáteis:

• [ 9.11 /H-0-2] DEVE fazer backup da implementação do keystore com um ambiente de execução isolado.
• [ 9.11 /H-0-3] DEVE ter implementações de algoritmos criptográficos RSA, AES, ECDSA e HMAC e funções hash da família MD5, SHA1 e SHA-2 para oferecer suporte adequado aos algoritmos suportados pelo sistema Android Keystore em uma área que seja segura isolado do código em execução no kernel e acima. O isolamento seguro DEVE bloquear todos os mecanismos potenciais pelos quais o código do kernel ou do espaço do usuário possa acessar o estado interno do ambiente isolado, incluindo DMA. O Android Open Source Project (AOSP) upstream atende a esse requisito usando a implementação Trusty , mas outra solução baseada em ARM TrustZone ou uma implementação segura revisada por terceiros de um isolamento adequado baseado em hipervisor são opções alternativas.
• [ 9.11 /H-0-4] DEVE realizar a autenticação da tela de bloqueio no ambiente de execução isolado e somente quando bem-sucedido, permitir que as chaves vinculadas à autenticação sejam usadas. As credenciais da tela de bloqueio DEVEM ser armazenadas de forma que permita que apenas o ambiente de execução isolado execute a autenticação da tela de bloqueio. O Android Open Source Project upstream fornece o Gatekeeper Hardware Abstraction Layer (HAL) e o Trusty, que podem ser usados ​​para satisfazer esse requisito.
• [ 9.11 /H-0-5] DEVE suportar atestado de chave onde a chave de assinatura do atestado é protegida por hardware seguro e a assinatura é executada em hardware seguro. As chaves de assinatura de atestado DEVEM ser compartilhadas entre um número grande o suficiente de dispositivos para evitar que as chaves sejam usadas como identificadores de dispositivos. Uma forma de atender a esse requisito é compartilhar a mesma chave de atestado, a menos que sejam produzidas pelo menos 100.000 unidades de um determinado SKU. Se forem produzidas mais de 100.000 unidades de um SKU, uma chave diferente PODE ser usada para cada 100.000 unidades.

Observe que se uma implementação de dispositivo já tiver sido lançada em uma versão anterior do Android, tal dispositivo estará isento do requisito de ter um armazenamento de chaves apoiado por um ambiente de execução isolado e suportar o atestado de chave, a menos que declare o android.hardware.fingerprint que requer um keystore apoiado por um ambiente de execução isolado.

Quando as implementações de dispositivos portáteis suportam uma tela de bloqueio segura, elas:

• [ 9.11 /H-1-1] DEVE permitir que o usuário escolha o tempo limite de suspensão mais curto, que é um tempo de transição do estado desbloqueado para o bloqueado, de 15 segundos ou menos.
• [ 9.11 /H-1-2] DEVE fornecer ao usuário recursos para ocultar notificações e desabilitar todas as formas de autenticação, exceto a autenticação primária descrita em 9.11.1 Tela de bloqueio seguro . O AOSP atende ao requisito como modo de bloqueio.

Se as implementações de dispositivos tiverem uma tela de bloqueio segura e incluírem um ou mais agentes confiáveis, que implementam a API do sistema TrustAgentService , elas:

• [ 9.11.1 /H-1-1] DEVE desafiar o usuário para um dos métodos de autenticação primários recomendados (por exemplo: PIN, padrão, senha) com mais frequência do que uma vez a cada 72 horas.

Se as implementações de dispositivos portáteis incluírem vários usuários e não declararem o sinalizador de recurso android.hardware.telephony , elas:

• [ 9.5 /H-2-1] DEVE oferecer suporte a perfis restritos, um recurso que permite aos proprietários de dispositivos gerenciar usuários adicionais e seus recursos no dispositivo. Com perfis restritos, os proprietários de dispositivos podem configurar rapidamente ambientes separados para usuários adicionais trabalharem, com a capacidade de gerenciar restrições mais detalhadas nos aplicativos disponíveis nesses ambientes.

Se as implementações de dispositivos portáteis incluírem vários usuários e declararem o sinalizador de recurso android.hardware.telephony , elas:

• [ 9.5 /H-3-1] NÃO DEVE suportar perfis restritos, mas DEVE se alinhar com a implementação de controles do AOSP para permitir/desabilitar o acesso de outros usuários às chamadas de voz e SMS.

Se as implementações de dispositivos portáteis definirem UserManager.isHeadlessSystemUserMode como true , elas

• [ 9.5 /H-4-1] NÃO DEVE incluir suporte para eUICCs, nem para eSIMs com capacidade de chamada.
• [ 9.5 /H-4-2] NÃO DEVE declarar suporte para android.hardware.telephony .

O Android, por meio da API do sistema VoiceInteractionService, oferece suporte a um mecanismo para detecção segura de hotword sempre ativa sem indicação de acesso ao microfone e detecção de consulta sempre ativa, sem indicação de acesso ao microfone ou câmera.

Se as implementações de dispositivos portáteis suportarem a API do sistema HotwordDetectionService ou outro mecanismo para detecção de hotword sem indicação de acesso ao microfone, elas:

• [9.8/H-1-1] DEVE garantir que o serviço de detecção de hotword só possa transmitir dados para o sistema, ContentCaptureService ou serviço de reconhecimento de fala no dispositivo criado por SpeechRecognizer#createOnDeviceSpeechRecognizer() .
• [9.8/H-1-2] DEVE garantir que o serviço de detecção de hotword só possa transmitir dados de áudio do microfone ou dados derivados dele para o servidor do sistema por meio da API HotwordDetectionService ou para ContentCaptureService por meio da API ContentCaptureManager .
• [9.8/H-1-3] NÃO DEVE fornecer áudio de microfone com duração superior a 30 segundos para uma solicitação individual acionada por hardware ao serviço de detecção de hotword.
• [9.8/H-1-4] NÃO DEVE fornecer áudio de microfone em buffer com mais de 8 segundos para uma solicitação individual ao serviço de detecção de hotword.
• [9.8/H-1-5] NÃO DEVE fornecer áudio de microfone em buffer com mais de 30 segundos ao serviço de interação de voz ou entidade semelhante.
• [9.8/H-1-6] NÃO DEVE permitir que mais de 100 bytes de dados (excluindo fluxos de áudio) sejam transmitidos para fora do serviço de detecção de hotword em cada resultado de hotword bem-sucedido.
• [9.8/H-1-7] NÃO DEVE permitir que mais de 5 bits de dados sejam transmitidos para fora do serviço de detecção de hotword em cada resultado negativo de hotword.
• [9.8/H-1-8] DEVE permitir apenas a transmissão de dados fora do serviço de detecção de hotword em uma solicitação de validação de hotword do servidor do sistema.
• [9.8/H-1-9] NÃO DEVE permitir que um aplicativo instalável pelo usuário forneça o serviço de detecção de hotword.
• [9.8/H-1-10] NÃO DEVE aparecer na IU dados quantitativos sobre o uso do microfone pelo serviço de detecção de hotword.
• [9.8/H-1-11] DEVE registrar o número de bytes incluídos em cada transmissão do serviço de detecção de hotword para permitir a inspeção por pesquisadores de segurança.
• [9.8/H-1-12] DEVE suportar um modo de depuração que registre o conteúdo bruto de cada transmissão do serviço de detecção de hotword para permitir a inspeção para pesquisadores de segurança.

• [9.8/H-1-14] DEVE exibir o indicador do microfone, conforme descrito na seção 9.8.2 , quando um resultado de hotword bem-sucedido é transmitido ao serviço de interação de voz ou entidade similar.

• [9.8/H-1-15] DEVE garantir que os fluxos de áudio fornecidos em resultados de hotword bem-sucedidos sejam transmitidos unidirecionalmente do serviço de detecção de hotword para o serviço de interação de voz.

• [9.8/H-SR-1] É FORTEMENTE RECOMENDADO notificar os usuários antes de definir um aplicativo como provedor do serviço de detecção de hotword.

• [9.8/H-SR-2] São FORTEMENTE RECOMENDADOS para proibir a transmissão de dados não estruturados fora do serviço de detecção de hotword.

• [9.8/H-SR-3] É FORTEMENTE RECOMENDADO reiniciar o processo que hospeda o serviço de detecção de hotword pelo menos uma vez a cada hora ou a cada 30 eventos acionados por hardware, o que ocorrer primeiro.

Se as implementações do dispositivo incluírem um aplicativo que usa a API do sistema HotwordDetectionService ou um mecanismo semelhante para detecção de hotword sem indicação de uso do microfone, o aplicativo:

• [9.8/H-2-1] DEVE fornecer aviso explícito ao usuário para cada frase de hotword suportada.
• [9.8/H-2-2] NÃO DEVE preservar dados de áudio brutos, ou dados derivados deles, por meio do serviço de detecção de hotword.
• [9.8/H-2-3] NÃO DEVE transmitir do serviço de detecção de hotword dados de áudio, dados que possam ser usados ​​para reconstruir (total ou parcialmente) o áudio ou conteúdos de áudio não relacionados à hotword em si, exceto para o ContentCaptureService ou serviço de reconhecimento de fala no dispositivo.

Se as implementações de dispositivos portáteis suportarem a API do sistema VisualQueryDetectionService ou outro mecanismo para detecção de consulta sem indicação de acesso de microfone e/ou câmera, elas:

• [9.8/H-3-1] DEVE garantir que o serviço de detecção de consulta só possa transmitir dados para o Sistema, ou ContentCaptureService , ou serviço de reconhecimento de fala no dispositivo (criado por SpeechRecognizer#createOnDeviceSpeechRecognizer() ).
• [9.8/H-3-2] NÃO DEVE permitir que nenhuma informação de áudio ou vídeo seja transmitida para fora do VisualQueryDetectionService , exceto para ContentCaptureService ou serviço de reconhecimento de fala no dispositivo.
• [9.8/H-3-3] DEVE exibir um aviso ao usuário na UI do sistema quando o dispositivo detecta a intenção do usuário de interagir com o aplicativo Digital Assistant (por exemplo, detectando a presença do usuário por meio da câmera).
• [9.8/H-3-4] DEVE exibir um indicador de microfone e exibir a consulta do usuário detectada na UI logo após a consulta do usuário ser detectada.
• [9.8/H-3-5] NÃO DEVE permitir que um aplicativo instalável pelo usuário forneça o serviço de detecção de consulta visual.

Se as implementações de dispositivos portáteis declararem android.hardware.microphone , elas:

• [ 9.8.2 /H-4-1] DEVE exibir o indicador do microfone quando um aplicativo estiver acessando dados de áudio do microfone, mas não quando o microfone for acessado apenas por HotwordDetectionService , SOURCE_HOTWORD , ContentCaptureService ou aplicativos que detêm as funções indicadas na seção 9.1 com identificador CDD [C-4-X].
• [ 9.8.2 /H-4-2] DEVE exibir a lista de aplicativos recentes e ativos usando microfone conforme retornado de PermissionManager.getIndicatorAppOpUsageData() , junto com quaisquer mensagens de atribuição associadas a eles.
• [ 9.8.2 /H-4-3] NÃO DEVE ocultar o indicador do microfone para aplicativos do sistema que tenham interfaces de usuário visíveis ou interação direta do usuário.
• [ 9.8.2 /H-4-4] DEVE exibir a lista de aplicativos recentes e ativos usando o microfone conforme retornado de PermissionManager.getIndicatorAppOpUsageData() , junto com quaisquer mensagens de atribuição associadas a eles.

Se as implementações de dispositivos portáteis declararem android.hardware.camera.any , elas:

• [ 9.8.2 /H-5-1] DEVE exibir o indicador da câmera quando um aplicativo estiver acessando dados da câmera ao vivo, mas não quando a câmera estiver sendo acessada apenas por aplicativos que detêm as funções descritas na seção 9.1 com identificador CDD [C-4-X].
• [ 9.8.2 /H-5-2] DEVE exibir aplicativos recentes e ativos usando câmera conforme retornado de PermissionManager.getIndicatorAppOpUsageData() , juntamente com quaisquer mensagens de atribuição associadas a eles.
• [ 9.8.2 /H-5-3] NÃO DEVE ocultar o indicador da câmera para aplicativos do sistema que tenham interfaces de usuário visíveis ou interação direta do usuário.

Iniciar novos requisitos para 15 (AOSP experimental)

[9.10/H–1–1] (visualização de 26 de fevereiro de 2024)

Inicialização verificada é um recurso que garante a integridade do software do dispositivo. Se as implementações de dispositivos suportarem o recurso, elas:

• [ 9.10 /H–1–1] DEVE verificar todas as partições somente leitura carregadas durante a sequência de inicialização do Android.

Observação: se as implementações de dispositivos já tiverem sido lançadas sem suporte a 9.10/C-1-8 até C-1-12 em uma versão anterior do Android e não puderem adicionar suporte a esses requisitos com uma atualização de software do sistema, elas PODEM ficar isentas dos requisitos .

Acabar com novos requisitos

2.2.6. Compatibilidade com ferramentas e opções do desenvolvedor

Implementações de dispositivos portáteis (* Não aplicável para Tablet):

• [ 6.1 /H-0-1]* DEVE suportar o comando shell cmd testharness .

Implementações de dispositivos portáteis (* Não aplicável para Tablet):

• Perfeito
  • [ 6.1 /H-0-2]* DEVE expor um binário /system/bin/perfetto ao usuário shell cujo cmdline esteja em conformidade com a documentação do perfetto .
  • [ 6.1 /H-0-3]* O binário perfetto DEVE aceitar como entrada uma configuração do protobuf que esteja em conformidade com o esquema definido na documentação do perfetto .
  • [ 6.1 /H-0-4]* O binário perfetto DEVE escrever como saída um rastreamento protobuf que esteja em conformidade com o esquema definido na documentação do perfetto .
  • [ 6.1 /H-0-5]* DEVE fornecer, por meio do binário perfetto, pelo menos as fontes de dados descritas na documentação do perfetto .
  • [ 6.1 /H-0-6]* O daemon rastreado perfetto DEVE ser habilitado por padrão (propriedade do sistema persist.traced.enable ).

2.2.7. Classe de desempenho de mídia portátil

Consulte a Seção 7.11 para a definição de classe de desempenho de mídia.

2.2.7.1. meios de comunicação

Se as implementações de dispositivos portáteis retornarem android.os.Build.VERSION_CODES.U para android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS , elas:

• DEVE atender aos requisitos de mídia listados na seção 2.2.7.1 do CDD do Android 14 .

Iniciar novos requisitos para 15 (AOSP experimental)

Atualizações de classe de desempenho de mídia para Android 15 (experimental AOSP) (visualização de 5 de fevereiro de 2024)

Se as implementações de dispositivos portáteis retornarem android.os.Build.VERSION_CODES.V para android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS , elas:

Acabar com novos requisitos

• [5.1/H-1-1] DEVE anunciar o número máximo de sessões de decodificador de vídeo de hardware que podem ser executadas simultaneamente em qualquer combinação de codec por meio dos métodos CodecCapabilities.getMaxSupportedInstances() e VideoCapabilities.getSupportedPerformancePoints() .

Iniciar novos requisitos para 15 (AOSP experimental)

5.1/H-1-2 (visualização de 5 de fevereiro de 2024)

• [5.1/H-1-2] DEVE suportar 6 instâncias de sessões de decodificador de vídeo de hardware de 8 bits (SDR) (AVC, HEVC, VP9, ​​AV1 ou posterior) em qualquer combinação de codec em execução simultaneamente com 3 sessões com resolução de 1080p@30 fps e 3 sessões com resolução 4k a 30fps, a menos que AV1. Para todas as sessões, NÃO DEVE haver mais de 1 quadro perdido por segundo. Os codecs AV1 são necessários apenas para oferecer suporte à resolução de 1080p, mas ainda são necessários para oferecer suporte a 6 instâncias a 1080p30fps.

Acabar com novos requisitos

• [5.1/H-1-3] DEVE anunciar o número máximo de sessões de codificador de vídeo de hardware que podem ser executadas simultaneamente em qualquer combinação de codec por meio dos métodos CodecCapabilities.getMaxSupportedInstances() e VideoCapabilities.getSupportedPerformancePoints() .

Iniciar novos requisitos para 15 (AOSP experimental)

5.1/H-1-4 (visualização de 5 de fevereiro de 2024)

• [5.1/H-1-4] DEVE suportar 6 instâncias de sessões de codificador de vídeo de hardware de 8 bits (SDR) (AVC, HEVC, VP9, ​​AV1 ou posterior) em qualquer combinação de codec em execução simultaneamente com 4 sessões com resolução de 1080p@30 fps e 2 sessões com resolução 4k a 30fps, a menos que AV1. Para todas as sessões, NÃO DEVE haver mais de 1 quadro perdido por segundo. Os codecs AV1 são necessários apenas para oferecer suporte à resolução de 1080p, mas ainda são necessários para oferecer suporte a 6 instâncias a 1080p30fps.

Acabar com novos requisitos

• [5.1/H-1-5] DEVE anunciar o número máximo de sessões de codificador e decodificador de vídeo de hardware que podem ser executadas simultaneamente em qualquer combinação de codec por meio dos métodos CodecCapabilities.getMaxSupportedInstances() e VideoCapabilities.getSupportedPerformancePoints() .

Iniciar novos requisitos para 15 (AOSP experimental)

5.1/H-1-6 (visualização de 5 de fevereiro de 2024)

• [5.1/H-1-6] DEVE suportar 6 instâncias de decodificador de vídeo de hardware de 8 bits (SDR) e sessões de codificador de vídeo de hardware (AVC, HEVC, VP9, ​​AV1 ou posterior) em qualquer combinação de codec executada simultaneamente com 3 sessões em Resolução 4K a 30fps (exceto AV1), das quais no máximo 2 são sessões de codificador e 3 sessões com resolução de 1080p. Para todas as sessões, NÃO DEVE haver mais de 1 quadro perdido por segundo. Os codecs AV1 são necessários apenas para oferecer suporte à resolução de 1080p, mas ainda são necessários para oferecer suporte a 6 instâncias a 1080p30fps.

Acabar com novos requisitos

Iniciar novos requisitos para 15 (AOSP experimental)

5.1/H-1-19 (visualização de 5 de fevereiro de 2024)

• [5.1/H-1-19] DEVE suportar 3 instâncias de decodificador de vídeo de hardware de 10 bits (HDR) e sessões de codificador de vídeo de hardware (AVC, HEVC, VP9, ​​AV1 ou posterior) em qualquer combinação de codec executando simultaneamente a 4K@30fps resolução (a menos que AV1), da qual no máximo 1 é uma sessão do codificador, que pode ser configurada no formato de entrada RGBA_1010102 por meio de uma superfície GL. Para todas as sessões, NÃO DEVE haver mais de 1 quadro perdido por segundo. A geração de metadados HDR pelo codificador não é necessária se a codificação for da superfície GL. As sessões do codec AV1 só são necessárias para oferecer suporte à resolução 1080p, mesmo quando esse requisito exige 4K.

Acabar com novos requisitos

• [5.1/H-1-7] DEVE ter uma latência de inicialização do codec de 40 ms ou menos para uma sessão de codificação de vídeo de 1080p ou menor para todos os codificadores de vídeo de hardware quando sob carga. O carregamento aqui é definido como uma sessão simultânea de transcodificação somente de vídeo de 1080p a 720p usando codecs de vídeo de hardware junto com a inicialização da gravação de áudio e vídeo de 1080p. Para o codec Dolby Vision, a latência de inicialização do codec DEVE ser de 50 ms ou menos.
• [5.1/H-1-8] DEVE ter uma latência de inicialização do codec de 30 ms ou menos para uma sessão de codificação de áudio com taxa de bits de 128 kbps ou inferior para todos os codificadores de áudio quando sob carga. O carregamento aqui é definido como uma sessão simultânea de transcodificação somente de vídeo de 1080p a 720p usando codecs de vídeo de hardware junto com a inicialização da gravação de áudio e vídeo de 1080p.

Iniciar novos requisitos para 15 (AOSP experimental)

5.1/H-1-9 (visualização de 5 de fevereiro de 2024)

• [5.1/H-1-9] DEVE suportar 2 instâncias de sessões seguras de decodificador de vídeo de hardware (AVC, HEVC, VP9, ​​AV1 ou posterior) em qualquer combinação de codecs executadas simultaneamente com resolução de 4k a 30 fps (a menos que AV1) para ambos 8 -bit (SDR) e conteúdo HDR de 10 bits. Para todas as sessões, NÃO DEVE haver mais de 1 quadro perdido por segundo. As sessões do codec AV1 só são necessárias para oferecer suporte à resolução 1080p, mesmo quando esse requisito exige 4K.

Acabar com novos requisitos

Iniciar novos requisitos para 15 (AOSP experimental)

5.1/H-1-10 (visualização de 5 de fevereiro de 2024)

• [5.1/H-1-10] DEVE suportar 3 instâncias de sessões de decodificador de vídeo de hardware não seguras junto com 1 instância de sessão de decodificador de vídeo de hardware segura (4 instâncias no total) (AVC, HEVC, VP9, ​​AV1 ou posterior) em qualquer combinação de codecs executada simultaneamente com 3 sessões com resolução 4K a 30fps (a menos que AV1), que inclui uma sessão de decodificador seguro e 1 sessão nn-segura com resolução de 1080p a 30fps, onde no máximo 2 sessões podem ser em HDR de 10 bits. Para todas as sessões, NÃO DEVE haver mais de 1 quadro perdido por segundo. As sessões do codec AV1 só são necessárias para oferecer suporte à resolução 1080p, mesmo quando esse requisito exige 4K.

Acabar com novos requisitos

• [5.1/H-1-11] DEVE oferecer suporte a um decodificador seguro para cada decodificador de hardware AVC, HEVC, VP9 ou AV1 no dispositivo.
• [5.1/H-1-12] DEVE ter uma latência de inicialização do codec de 40 ms ou menos para uma sessão de decodificação de vídeo de 1080p ou menor para todos os decodificadores de vídeo de hardware quando sob carga. O carregamento aqui é definido como uma sessão simultânea de transcodificação somente de vídeo de 1080p a 720p usando codecs de vídeo de hardware junto com a inicialização da reprodução de áudio e vídeo de 1080p. Para o codec Dolby Vision, a latência de inicialização do codec DEVE ser de 50 ms ou menos.
• [5.1/H-1-13] DEVE ter uma latência de inicialização do codec de 30 ms ou menos para uma sessão de decodificação de áudio com taxa de bits de 128 kbps ou inferior para todos os decodificadores de áudio quando sob carga. O carregamento aqui é definido como uma sessão simultânea de transcodificação somente de vídeo de 1080p a 720p usando codecs de vídeo de hardware junto com a inicialização da reprodução de áudio e vídeo de 1080p.

Iniciar novos requisitos para 15 (AOSP experimental)

[5.1/H-1-14] (visualização de 5 de fevereiro de 2024)

• [5.1/H-1-14] DEVE suportar o decodificador de hardware AV1 Main 10, Nível 4.1 e granulação de filme com efeito de granulação de filme sobre a composição da GPU .

Acabar com novos requisitos

• [5.1/H-1-15] DEVE ter pelo menos 1 decodificador de vídeo de hardware compatível com 4K60.
• [5.1/H-1-16] DEVE ter pelo menos 1 codificador de vídeo de hardware compatível com 4K60.

Iniciar novos requisitos para 15 (AOSP experimental)

[5.1/H-1-21] (visualização de 5 de fevereiro de 2024)

• [5.1/H-1-21] DEVE suportar FEATURE_DynamicColorAspect para todos os decodificadores de vídeo de hardware (AVC, HEVC, VP9, ​​AV1 ou posterior). Nota: Isso significa que os aplicativos podem atualizar os aspectos de cores do conteúdo de vídeo durante a sessão de decodificação. Os decodificadores que suportam conteúdo de 10 e 8 bits DEVEM oferecer suporte à alternância dinâmica entre conteúdo de 8 e 10 bits no modo Surface. Os decodificadores que suportam a função de transferência HDR DEVEM suportar a alternância dinâmica entre conteúdo SDR e HDR.

Acabar com novos requisitos

Iniciar novos requisitos para 15 (AOSP experimental)

[5.1/H-1-22] (visualização de 5 de fevereiro de 2024)

• [5.1/H-1-22] DEVE suportar codificação, decodificação, edição de GPU e exibição de conteúdo de vídeo na proporção de retrato, independentemente dos metadados de rotação para a maior resolução suportada pela câmera ou 4K, o que for menor. Observação: isso inclui perfis HDR se o codec suportar HDR. Os codecs AV1 são necessários apenas para oferecer suporte à resolução 1080p. Este requisito é apenas para codecs de hardware, GPU e DPU.

Acabar com novos requisitos

• [5.3/H-1-1] NÃO DEVE perder mais de 1 quadro em 10 segundos (ou seja, menos de 0,167% de queda de quadro) para uma sessão de vídeo 4K a 60 fps sob carga.
• [5.3/H-1-2] NÃO DEVE perder mais de 1 quadro em 10 segundos durante uma alteração na resolução de vídeo em uma sessão de vídeo de 60 fps sob carga para uma sessão de 4K.
• [5.6/H-1-1] DEVE ter uma latência tap-to-tone de 80 milissegundos ou menos usando o teste tap-to-tone do CTS Verifier.
• [5.6/H-1-2] DEVE ter uma latência de áudio de ida e volta de 80 milissegundos ou menos em pelo menos um caminho de dados suportado.
• [5.6/H-1-3] DEVE suportar >= áudio de 24 bits para saída estéreo em conectores de áudio de 3,5 mm, se houver, e áudio USB, se for compatível com todo o caminho de dados para configurações de baixa latência e streaming. Para a configuração de baixa latência, o AAudio deve ser usado pelo aplicativo no modo de retorno de chamada de baixa latência. Para a configuração do streaming, um Java AudioTrack deve ser utilizado pelo aplicativo. Nas configurações de baixa latência e streaming, o coletor de saída HAL deve aceitar AUDIO_FORMAT_PCM_24_BIT , AUDIO_FORMAT_PCM_24_BIT_PACKED , AUDIO_FORMAT_PCM_32_BIT ou AUDIO_FORMAT_PCM_FLOAT para seu formato de saída de destino.

Iniciar novos requisitos para 15 (AOSP experimental)

[5.6/H-1-4] (visualização de 5 de fevereiro de 2024)

• [5.6/H-1-4] DEVE suportar >= dispositivos de áudio USB de 4 canais. (Isso é usado pelos controladores de DJ para pré-visualizar músicas.)

Acabar com novos requisitos

• [5.6/H-1-5] DEVE suportar dispositivos MIDI compatíveis com a classe e declarar o sinalizador de recurso MIDI.
• [5.6/H-1-9] DEVE suportar mixagem de pelo menos 12 canais. Isto implica a capacidade de abrir uma AudioTrack com máscara de canal 7.1.4 e espacializar ou mixar adequadamente todos os canais para estéreo.
• [5.6/H-SR] São FORTEMENTE RECOMENDADOS para suportar mixagem de 24 canais com pelo menos suporte para máscaras de canais 9.1.6 e 22.2.
• [5.7/H-1-2] DEVE oferecer suporte MediaDrm.SECURITY_LEVEL_HW_SECURE_ALL com os recursos de descriptografia de conteúdo abaixo.

Tamanho mínimo da amostra	4 MiB
Número Mínimo de Subamostras - H264 ou HEVC	32
Número Mínimo de Subamostras - VP9	9
Número Mínimo de Subamostras - AV1	288
Tamanho mínimo do buffer de subamostra	1 MiB
Tamanho mínimo do buffer de criptografia genérico	500 KiB
Número mínimo de sessões simultâneas	30
Número mínimo de chaves por sessão	20
Número total mínimo de chaves (todas as sessões)	80
Número total mínimo de chaves DRM (todas as sessões)	6
Tamanho da mensagem	16 KiB
Quadros descriptografados por segundo	60fps

• [5.1/H-1-17] DEVE ter pelo menos 1 decodificador de imagem de hardware compatível com AVIF Baseline Profile.
• [5.1/H-1-18] DEVE suportar o codificador AV1, que pode codificar resolução de até 480p a 30fps e 1Mbps.

Iniciar novos requisitos para 15 (AOSP experimental)

[5.1/H-1-20] (visualização de 5 de fevereiro de 2024)

• [5.1/H-1-20] DEVE oferecer suporte ao recurso Feature_HdrEditing para todos os codificadores AV1 e HEVC de hardware presentes no dispositivo com resolução 4K ou a maior resolução suportada pela câmera, o que for menor.

Acabar com novos requisitos

• [5.12/H-SR] São fortemente recomendados para oferecer suporte ao recurso Feature_HdrEditing para todos os codificadores AV1 e HEVC de hardware presentes no dispositivo.
• [5.12/H-1-2] DEVE suportar o formato de cores RGBA_1010102 para todos os codificadores AV1 e HEVC de hardware presentes no dispositivo.
• [5.12/H-1-3] DEVE anunciar suporte para a extensão EXT_YUV_target para amostrar texturas YUV em 8 e 10 bits.
• [7.1.4/H-1-1] DEVE ter pelo menos 6 sobreposições de hardware na unidade de processamento de dados (DPU) Hardware Composer (HWC), com pelo menos 2 delas capazes de exibir conteúdo de vídeo de 10 bits.

Iniciar novos requisitos para 15 (AOSP experimental)

Atualizações de classe de desempenho de mídia para Android 15 (experimental AOSP) (visualização de 5 de fevereiro de 2024)

Se as implementações de dispositivos portáteis retornarem android.os.Build.VERSION_CODES.V para android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS e incluírem suporte para um codificador AVC ou HEVC de hardware, elas:

Acabar com novos requisitos

• [5.2/H-2-1] DEVE atender à meta de qualidade mínima definida pelas curvas de distorção de taxa do codificador de vídeo para codecs AVC e HEVC de hardware, conforme definido nos testes de qualidade de codificação de vídeo (VEQ) Run Performance Class 14 (PC14) .

Iniciar novos requisitos para 15 (AOSP experimental)

[5.2/H-2-2] [Retirado] (visualização de 8 de abril de 2024)

• [5.2/H-2-2]
  Este requisito foi retirado do Android 15 (AOSP experimental).

Acabar com novos requisitos

[5.2/H-2-2] (visualização de 5 de fevereiro de 2024)

• [5.2/H-2-2] DEVE renderizar o vídeo de amostra usando o decodificador AV1 do software dav1d em 1080p a >= 60 FPS.

Acabar com novos requisitos

2.2.7.2. Câmera

Se as implementações de dispositivos portáteis retornarem android.os.Build.VERSION_CODES.U para android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS , elas:

• DEVE atender aos requisitos de mídia listados na seção 2.2.7.2 do CDD do Android 14 .

Iniciar novos requisitos para 15 (AOSP experimental)

Atualizações de classe de desempenho de mídia para Android 15 (experimental AOSP) (visualização de 5 de fevereiro de 2024)

Se as implementações de dispositivos portáteis retornarem android.os.Build.VERSION_CODES.V para android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS , elas:

Acabar com novos requisitos

Iniciar novos requisitos para 15 (AOSP experimental)

[7.5/H-1-1] (visualização de 26 de fevereiro de 2024)

• [ 7.5 /H-1-1] DEVE ter uma câmera traseira primária com resolução de pelo menos 12 megapixels com suporte para captura de vídeo em 4k a 30fps , 1080p a 60fps e 720p a 60fps . A câmera traseira principal é a câmera traseira com o ID de câmera mais baixo.

Acabar com novos requisitos

[7.5/H-1-1] (visualização de 5 de fevereiro de 2024)

• [ 7.5 /H-1-1] DEVE ter uma câmera traseira primária com resolução de pelo menos 12 megapixels com suporte para captura de vídeo em 4k a 30fps , 1080p a 60fps e 720p a 60fps. A taxa de queda de quadros para essas taxas de captura não DEVE ser superior a X% (X será definido até o primeiro trimestre de 2024). A câmera traseira principal é a câmera traseira com o ID de câmera mais baixo.

Acabar com novos requisitos

• [ 7.5 /H-1-2] DEVE ter uma câmera frontal primária com resolução de pelo menos 6 megapixels e suporte para captura de vídeo em 1080p a 30fps. A câmera frontal principal é a câmera frontal com o ID de câmera mais baixo.
• [ 7.5 /H-1-3] DEVE oferecer suporte à propriedade android.info.supportedHardwareLevel como FULL ou melhor para câmera primária traseira e LIMITED ou melhor para câmera primária frontal.
• [ 7.5 /H-1-4] DEVE oferecer suporte CameraMetadata.SENSOR_INFO_TIMESTAMP_SOURCE_REALTIME para ambas as câmeras primárias.
• [ 7.5 /H-1-5] DEVE ter latência de captura JPEG da câmera2 < 1000 ms para resolução de 1080p, conforme medido pelo Teste de desempenho da câmera CTS sob condições de iluminação ITS (3000K) para ambas as câmeras primárias.
• [ 7.5 /H-1-6] DEVE ter latência de inicialização da câmera2 (câmera aberta para o primeiro quadro de visualização) <500 ms conforme medido pelo Teste de desempenho da câmera CTS sob condições de iluminação ITS (3000K) para ambas as câmeras primárias.
• [ 7.5 /H-1-8] DEVE oferecer suporte CameraMetadata.REQUEST_AVAILABLE_CAPABILITIES_RAW e android.graphics.ImageFormat.RAW_SENSOR para a câmera traseira principal.
• [ 7.5 /H-1-9] DEVE ter uma câmera primária voltada para trás com suporte a 720p ou 1080p a 240fps.
• [ 7.5 /H-1-10] DEVE ter mínimo ZOOM_RATIO <1.0 para as câmeras primárias se houver uma câmera RGB ultralarga voltada para a mesma direção.
• [ 7.5 /H-1-11] DEVE implementar streaming frontal-traseiro simultâneo em câmeras primárias.
• [ 7.5 /H-1-12] DEVE oferecer suporte CONTROL_VIDEO_STABILIZATION_MODE_PREVIEW_STABILIZATION para câmera frontal primária e traseira primária.
• [ 7.5 /H-1-13] DEVE suportar o recurso LOGICAL_MULTI_CAMERA para a câmera traseira principal se houver mais de 1 câmera traseira RGB.
• [ 7.5 /H-1-14] DEVE oferecer suporte ao recurso STREAM_USE_CASE para câmera frontal primária e traseira primária.
• [ 7.5 /H-1-15] DEVE oferecer suporte a extensões de modo noturno por meio de extensões CameraX e Camera2 para câmeras primárias.
• [ 7.5 /H-1-16] DEVE oferecer suporte ao recurso DYNAMIC_RANGE_TEN_BIT para as câmeras primárias.
• [ 7.5 /H-1-17] DEVE suportar CONTROL_SCENE_MODE_FACE_PRIORITY e detecção de rosto ( STATISTICS_FACE_DETECT_MODE_SIMPLE ou STATISTICS_FACE_DETECT_MODE_FULL ) para as câmeras primárias.

Iniciar novos requisitos para 15 (AOSP experimental)

[7.5/H-1-18] (visualização de 5 de fevereiro de 2024)

• [ 7.5 /H-1-18] DEVE suportar JPEG_R para as câmeras traseira e frontal primárias.

Acabar com novos requisitos

Iniciar novos requisitos para 15 (AOSP experimental)

[7.5/H-1-19] (visualização de 8 de abril de 2024)

• [ 7.5 /H-1-19] DEVE suportar CONTROL_VIDEO_STABILIZATION_MODE_PREVIEW_STABILIZATION para visualização HLG10 de 1080p com tamanho máximo JPEG de proporção de aspecto 16:9 e para visualização HLG10 de 720p com combinações de fluxo JPEG de tamanho máximo de proporção de aspecto 16:9 para a câmera traseira principal.

Acabar com novos requisitos

[7.5/H-1-19] (visualização de 26 de fevereiro de 2024)

• [ 7.5 /H-1-19] DEVE suportar CONTROL_VIDEO_STABILIZATION_MODE_PREVIEW_STABILIZATION para visualização HLG10 de 1080p com JPEG de tamanho máximo e para visualização HLG10 de 720p com combinações de fluxo JPEG de tamanho máximo para a câmera traseira principal.

Acabar com novos requisitos

Iniciar novos requisitos para 15 (AOSP experimental)

[7.5/H-1-20] (visualização de 8 de abril de 2024)

• [ 7.5 /H-1-20] DEVE, por padrão, gerar JPEG_R para as câmeras traseira e frontal primária no aplicativo de câmera nativo.

Acabar com novos requisitos

2.2.7.3. Hardware

Se as implementações de dispositivos portáteis retornarem android.os.Build.VERSION_CODES.U para android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS , elas:

• DEVE atender aos requisitos de mídia listados na seção 2.2.7.3 do CDD do Android 14 .

Iniciar novos requisitos para 15 (AOSP experimental)

Atualizações de classe de desempenho de mídia para Android 15 (experimental AOSP) (visualização de 5 de fevereiro de 2024)

Se as implementações de dispositivos portáteis retornarem android.os.Build.VERSION_CODES.V para android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS , elas:

Acabar com novos requisitos

• [7.1.1.1/H-2-1] DEVE ter resolução de tela de pelo menos 1080p.

Iniciar novos requisitos para 15 (AOSP experimental)

[7.1.1.3/H-2-1] (visualização de 5 de fevereiro de 2024)

• [7.1.1.3/H-2-1] DEVE ter densidade de tela de pelo menos 400 dpi se a largura da tela do dispositivo for < 600 dp .

Acabar com novos requisitos

• [7.1.1.3/H-3-1] DEVE ter uma tela HDR que suporte pelo menos 1000 nits em média.

Iniciar novos requisitos para 15 (AOSP experimental)

[7.6.1/H-2-1] (visualização de 8 de abril de 2024)

• [7.6.1/H-2-1] DEVE ter pelo menos 8 GB de memória física , com pelo menos 6,64 GB disponíveis para o kernel conforme relatado por android.app.ActivityManager.MemoryInfo .

Acabar com novos requisitos

2.2.7.4. Desempenho

Se as implementações de dispositivos portáteis retornarem android.os.Build.VERSION_CODES.U para android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS , elas:

• DEVE atender aos requisitos de desempenho listados na seção 2.2.7.4 do CDD do Android 14 .

Iniciar novos requisitos para 15 (AOSP experimental)

Atualizações de classe de desempenho de mídia para Android 15 (experimental AOSP) (visualização de 5 de fevereiro de 2024)

Se as implementações de dispositivos portáteis retornarem android.os.Build.VERSION_CODES.V para android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS , elas:

Acabar com novos requisitos

• [8.2/H-1-1] DEVE garantir um desempenho de gravação sequencial de pelo menos 150 MB/s.
• [8.2/H-1-2] DEVE garantir um desempenho de gravação aleatória de pelo menos 10 MB/s.
• [8.2/H-1-3] DEVE garantir um desempenho de leitura sequencial de pelo menos 250 MB/s.
• [8.2/H-1-4] DEVE garantir um desempenho de leitura aleatória de pelo menos 100 MB/s.
• [8.2/H-1-5] DEVE garantir um desempenho de leitura e gravação sequencial paralela com desempenho de leitura 2x e gravação 1x de pelo menos 50 MB/s.

Iniciar novos requisitos para 15 (AOSP experimental)

2.2.7.5. Gráficos

[2.2.7.5 Gráficos] (visualização de 8 de abril de 2024)

Se as implementações de dispositivos portáteis retornarem android.os.Build.VERSION_CODES.V para android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS , elas:

• [ 7.1.4.1/H-1-1 ]
  Este requisito foi retirado do Android 15 (AOSP experimental).
• [ 7.1.4.1 /H-1-2] DEVE suportar as extensões EGL_IMG_context_priority e EGL_EXT_protected_content .
• [ 7.1.4.1 /H-1-3] DEVE oferecer suporte VkPhysicalDeviceProtectedMemoryFeatures.protectedMemory e VK_KHR_global_priority .

Acabar com novos requisitos

[2.2.7.5 Gráficos] (visualização de 5 de fevereiro de 2024)

Se as implementações de dispositivos portáteis retornarem android.os.Build.VERSION_CODES.V para android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS , elas:

• [ 7.1.4.1 /H-1-1] DEVE atender aos testes de desempenho de renderização OpenGL em resolução de 1080p com pelo menos 30 FPS.
• [ 7.1.4.1 /H-1-2] DEVE suportar as extensões EGL_IMG_context_priority e EGL_EXT_protected_content .
• [ 7.1.4.1 /H-1-3] DEVE oferecer suporte VkPhysicalDeviceProtectedMemoryFeatures.protectedMemory e VK_EXT_global_priority .

Acabar com novos requisitos

2.3. Requisitos de televisão

Um dispositivo Android Television refere-se a uma implementação de dispositivo Android que é uma interface de entretenimento para consumir mídia digital, filmes, jogos, aplicativos e/ou TV ao vivo para usuários sentados a cerca de três metros de distância (um usuário "reclinado" ou "usuário de 3 metros". interface").

As implementações de dispositivos Android são classificadas como Televisão se atenderem a todos os critérios a seguir:

• Forneceram um mecanismo para controlar remotamente a interface do usuário renderizada na tela que pode ficar a três metros de distância do usuário.
• Tenha uma tela incorporada com comprimento diagonal maior que 24 polegadas OU inclua uma porta de saída de vídeo, como VGA, HDMI, DisplayPort ou uma porta sem fio para exibição.

Os requisitos adicionais no restante desta seção são específicos para implementações de dispositivos Android Television.

2.3.1. Hardware

Implementações de dispositivos de televisão:

• [ 7.2.2 /T-0-1] DEVE suportar D-pad .
• [ 7.2 .3/T-0-1] DEVE fornecer as funções Home e Back.
• [ 7.2 .3/T-0-2] DEVE enviar o evento de pressionamento normal e longo da função Back ( KEYCODE_BACK ) para o aplicativo em primeiro plano.
• [ 7.2 .6.1/T-0-1] DEVE incluir suporte para controladores de jogo e declarar o sinalizador de recurso android.hardware.gamepad .
• [ 7.2.7 /T] DEVE fornecer um controle remoto a partir do qual os usuários possam acessar a navegação sem toque e as entradas das teclas de navegação principais .

Se as implementações de dispositivos de televisão incluírem um giroscópio de 3 eixos, elas:

• [ 7.3.4 /T-1-1] DEVE ser capaz de relatar eventos até uma frequência de pelo menos 100 Hz.
• [ 7.3.4 /T-1-2] DEVE ser capaz de medir mudanças de orientação de até 1000 graus por segundo.

Implementações de dispositivos de televisão:

• [ 7.4 .3/T-0-1] DEVE suportar Bluetooth e Bluetooth LE.
• [ 7.6 .1/T-0-1] DEVE ter pelo menos 4 GB de armazenamento não volátil disponível para dados privados do aplicativo (também conhecida como partição "/data").

Se as implementações de dispositivos de televisão incluírem uma porta USB compatível com o modo host, elas:

• [ 7.5 .3/T-1-1] DEVE incluir suporte para uma câmera externa que se conecta através desta porta USB, mas não está necessariamente sempre conectada.

Se as implementações de dispositivos de TV forem de 32 bits:

• [ 7.6 .1/T-1-1] A memória disponível para o kernel e espaço do usuário DEVE ser de pelo menos 896 MB se qualquer uma das seguintes densidades for usada:

  • 400 dpi ou superior em telas pequenas/normais
  • xhdpi ou superior em telas grandes
  • tvdpi ou superior em telas extragrandes

Se as implementações de dispositivos de TV forem de 64 bits:

• [ 7.6 .1/T-2-1] A memória disponível para o kernel e espaço do usuário DEVE ser de pelo menos 1280 MB se qualquer uma das seguintes densidades for usada:

  • 400 dpi ou superior em telas pequenas/normais
  • xhdpi ou superior em telas grandes
  • tvdpi ou superior em telas extragrandes

Observe que a "memória disponível para o kernel e espaço do usuário" acima se refere ao espaço de memória fornecido além de qualquer memória já dedicada a componentes de hardware, como rádio, vídeo e assim por diante, que não estão sob o controle do kernel nas implementações de dispositivos.

Implementações de dispositivos de televisão:

• [ 7.8 .1/T] DEVE incluir um microfone.
• [ 7.8 .2/T-0-1] DEVE ter uma saída de áudio e declarar android.hardware.audio.output .

2.3.2. Multimídia

As implementações de dispositivos de televisão DEVEM suportar os seguintes formatos de codificação e decodificação de áudio e disponibilizá-los para aplicativos de terceiros:

• [ 5.1 /T-0-1] Perfil MPEG-4 AAC (AAC LC)
• [ 5.1 /T-0-2] Perfil MPEG-4 HE AAC (AAC+)
• [ 5.1 /T-0-3] AAC ELD (AAC de baixo atraso aprimorado)

As implementações de dispositivos de televisão DEVEM suportar os seguintes formatos de codificação de vídeo e disponibilizá-los para aplicativos de terceiros:

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

Implementações de dispositivos de televisão:

• [ 5.2 .2/T-SR-1] São FORTEMENTE RECOMENDADOS para suportar codificação H.264 de vídeos com resolução de 720p e 1080p a 30 quadros por segundo.

As implementações de dispositivos de televisão DEVEM suportar os seguintes formatos de decodificação de vídeo e disponibilizá-los para aplicativos de terceiros:

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

As implementações de dispositivos de televisão DEVEM suportar a decodificação MPEG-2, conforme detalhado na Seção 5.3.1, em taxas de quadros de vídeo padrão e resoluções até e incluindo:

• [ 5.3.1 /T-1-1] HD 1080p a 29,97 quadros por segundo com perfil principal de alto nível.
• [ 5.3.1 /T-1-2] HD 1080i a 59,94 quadros por segundo com perfil principal de alto nível. Eles DEVEM desentrelaçar vídeo MPEG-2 entrelaçado e disponibilizá-lo para aplicativos de terceiros.

As implementações de dispositivos de televisão DEVEM suportar a decodificação H.264, conforme detalhado na Seção 5.3.4, em taxas de quadros de vídeo padrão e resoluções até e incluindo:

• [ 5.3.4 /T-1-1] HD 1080p a 60 quadros por segundo com perfil de linha de base
• [ 5.3.4 /T-1-2] HD 1080p a 60 quadros por segundo com perfil principal
• [ 5.3.4 /T-1-3] HD 1080p a 60 quadros por segundo com High Profile Level 4.2

As implementações de dispositivos de televisão com decodificadores de hardware H.265 DEVEM suportar a decodificação H.265, conforme detalhado na Seção 5.3.5, em taxas de quadros de vídeo padrão e resoluções até e incluindo:

• [ 5.3.5 /T-1-1] HD 1080p a 60 quadros por segundo com nível de perfil principal 4.1

Se as implementações de dispositivos de televisão com decodificadores de hardware H.265 suportarem a decodificação H.265 e o perfil de decodificação UHD, elas:

• [ 5.3.5 /T-2-1] DEVE suportar o perfil de decodificação UHD a 60 quadros por segundo com perfil Main10 Level 5 Main Tier

As implementações de dispositivos de televisão DEVEM suportar a decodificação VP8, conforme detalhado na Seção 5.3.6, em taxas de quadros de vídeo padrão e resoluções até e incluindo:

• [ 5.3.6 /T-1-1] Perfil de decodificação HD 1080p a 60 quadros por segundo

As implementações de dispositivos de televisão com decodificadores de hardware VP9 DEVEM suportar a decodificação VP9, ​​conforme detalhado na Seção 5.3.7, em taxas de quadros de vídeo padrão e resoluções até e incluindo:

• [ 5.3.7 /T-1-1] HD 1080p a 60 quadros por segundo com perfil 0 (profundidade de cor de 8 bits)

Se as implementações de dispositivos de televisão com decodificadores de hardware VP9 suportarem a decodificação VP9 e o perfil de decodificação UHD, elas:

• [ 5.3.7 /T-2-1] DEVE suportar o perfil de decodificação UHD a 60 quadros por segundo com perfil 0 (profundidade de cor de 8 bits).
• [ 5.3.7 /T-SR1] São FORTEMENTE RECOMENDADOS para suportar o perfil de decodificação UHD a 60 quadros por segundo com perfil 2 (profundidade de cor de 10 bits).

Implementações de dispositivos de televisão:

• [ 5.5 /T-0-1] DEVE incluir suporte para volume mestre do sistema e atenuação do volume de saída de áudio digital nas saídas suportadas, exceto para saída de passagem de áudio compactado (onde nenhuma decodificação de áudio é feita no dispositivo).

Se as implementações de dispositivos de televisão não tiverem um monitor integrado, mas suportarem um monitor externo conectado via HDMI, elas:

• [ 5.8 /T-0-1] DEVE definir o modo de saída HDMI para a resolução mais alta para o formato de pixel escolhido que funcione com taxa de atualização de 50 Hz ou 60 Hz para o monitor externo, dependendo da taxa de atualização de vídeo para a região em que o dispositivo é vendido em.
• [ 5.8 /T-SR-1] São FORTEMENTE RECOMENDADOS para fornecer um seletor de taxa de atualização HDMI configurável pelo usuário.
• [ 5.8 ] DEVE definir a taxa de atualização do modo de saída HDMI para 50 Hz ou 60 Hz, dependendo da taxa de atualização de vídeo para a região em que o dispositivo é vendido.

Se as implementações de dispositivos de televisão não tiverem um monitor integrado, mas suportarem um monitor externo conectado via HDMI, elas:

• [ 5.8 /T-1-1] DEVE suportar HDCP 2.2.

Se as implementações de dispositivos de televisão não suportarem a decodificação UHD, mas, em vez disso, suportarem um monitor externo conectado via HDMI, elas:

• [ 5.8 /T-2-1] DEVE suportar HDCP 1.4

2.3.3. Programas

Implementações de dispositivos de televisão:

• [ 3 /T-0-1] DEVE declarar os recursos android.software.leanback e android.hardware.type.television .
• [ 3.2.3.1 /T-0-1] DEVE pré-carregar um ou mais aplicativos ou componentes de serviço com um manipulador de intenções, para todos os padrões de filtro de intenções públicas definidos pelas seguintes intenções de aplicativos listadas aqui .
• [ 3.4.1 /T-0-1] DEVE fornecer uma implementação completa da API android.webkit.Webview .

Se as implementações de dispositivos Android Television suportarem uma tela de bloqueio, elas:

• [ 3.8.10 /T-1-1] DEVE exibir as notificações da tela de bloqueio, incluindo o modelo de notificação de mídia.

Implementações de dispositivos de televisão:

• [ 3.8 .14/T-SR-1] São FORTEMENTE RECOMENDADOS para suportar múltiplas janelas no modo picture-in-picture (PIP).
• [ 3.10 /T-0-1] DEVE oferecer suporte a serviços de acessibilidade de terceiros.
• [ 3.10 /T-SR-1] É FORTEMENTE RECOMENDADO pré-carregar serviços de acessibilidade no dispositivo comparáveis ​​ou superiores à funcionalidade dos serviços de acessibilidade Switch Access e TalkBack (para idiomas suportados pelo mecanismo de conversão de texto em fala pré-instalado), conforme fornecido no projeto de código aberto talkback .

Se as implementações de dispositivos de televisão reportarem o recurso android.hardware.audio.output , elas:

• [ 3.11 /T-SR-1] É FORTEMENTE RECOMENDADO incluir um mecanismo TTS que suporte os idiomas disponíveis no dispositivo.
• [ 3.11 /T-1-1] DEVE suportar a instalação de mecanismos TTS de terceiros.

Iniciar novos requisitos para 15 (AOSP experimental)

[3.12/T-0-1] (visualização de 26 de fevereiro de 2024)

Implementações de dispositivos de televisão:

• [ 3.12 /T-0-1] DEVE suportar TV Input Framework.

Acabar com novos requisitos

Iniciar novos requisitos para 15 (AOSP experimental)

[3/T-0-2, 3/T-0-3. 3/T-1-1] (visualização de 26 de fevereiro de 2024)

O Android Television Input Framework (TIF) simplifica a entrega de conteúdo ao vivo para dispositivos Android Television. TIF fornece uma API padrão para criar módulos de entrada que controlam dispositivos Android Television.

Implementações de dispositivos de televisão:

• [ 3 /T-0-2] DEVE declarar o recurso da plataforma android.software.live_tv .
• [ 3 /T-0-3] DEVE oferecer suporte a todas as APIs TIF, de modo que um aplicativo que use essas APIs e o serviço de entradas baseado em TIF de terceiros possa ser instalado e usado no dispositivo.

O Android Television Tuner Framework (TF) [LINK TBD até o terceiro trimestre de 2024] unifica o manuseio de conteúdo ao vivo do Tuner com streaming de conteúdo de IP em dispositivos Android Television. O Turner Framework fornece uma API padrão para criar serviços de entrada que usam o Android Television Tuner.

Se as implementações de dispositivos suportarem o Tuner, elas:

• [ 3 /T-1-1] DEVE oferecer suporte a todas as APIs do Tuner Framework, de modo que um aplicativo que use essas APIs possa ser instalado e usado no dispositivo.

Acabar com novos requisitos

2.3.4. Desempenho e potência

• [ 8.1 /T-0-1] Latência de quadro consistente . A latência de quadro inconsistente ou um atraso na renderização de quadros NÃO DEVE acontecer com mais frequência do que 5 quadros por segundo e DEVE estar abaixo de 1 quadro por segundo.
• [ 8.2 /T-0-1] DEVE garantir um desempenho de gravação sequencial de pelo menos 5 MB/s.
• [ 8.2 /T-0-2] DEVE garantir um desempenho de gravação aleatória de pelo menos 0,5 MB/s.
• [ 8.2 /T-0-3] DEVE garantir um desempenho de leitura sequencial de pelo menos 15MB/s.
• [ 8.2 /T-0-4] DEVE garantir um desempenho de leitura aleatória de pelo menos 3,5 MB/s.

Se as implementações de dispositivos de televisão incluírem recursos para melhorar o gerenciamento de energia do dispositivo incluídos no AOSP ou estender os recursos incluídos no AOSP, elas:

• [ 8.3 /T-1-1] DEVE fornecer ao usuário recursos para ativar e desativar o recurso de economia de bateria.

Se as implementações de dispositivos de televisão não tiverem bateria, elas:

• [ 8.3 /T-1-2] DEVE registrar o dispositivo como um dispositivo sem bateria, conforme descrito em Suporte a dispositivos sem bateria .

Se as implementações de dispositivos de televisão tiverem bateria, elas:

• [ 8.3 /T-1-3] DEVE fornecer ao usuário recursos para exibir todos os aplicativos que estão isentos dos modos de economia de energia App Standby e Doze.

Implementações de dispositivos de televisão:

• [ 8.4 /T-0-1] DEVE fornecer um perfil de energia por componente que defina o valor de consumo atual para cada componente de hardware e o consumo aproximado de bateria causado pelos componentes ao longo do tempo, conforme documentado no site do Android Open Source Project.
• [ 8.4 /T-0-2] DEVE informar todos os valores de consumo de energia em miliamperes-hora (mAh).
• [ 8.4 /T-0-3] DEVE relatar o consumo de energia da CPU por UID de cada processo. O Android Open Source Project atende ao requisito por meio da implementação do módulo do kernel uid_cputime .
• [ 8.4 /T] DEVE ser atribuído ao próprio componente de hardware se não for possível atribuir o uso de energia do componente de hardware a um aplicativo.
• [ 8.4 /T-0-4] DEVE disponibilizar esse uso de energia por meio do comando shell adb shell dumpsys batterystats para o desenvolvedor do aplicativo.

2.3.5. Modelo de segurança

Implementações de dispositivos de televisão:

• [9/T-0-1] DEVE declarar o recurso android.hardware.security.model.compatible .
• [ 9.11 /T-0-1] DEVE fazer backup da implementação do keystore com um ambiente de execução isolado.
• [ 9.11 /T-0-2] DEVE ter implementações de algoritmos criptográficos RSA, AES, ECDSA e HMAC e funções hash da família MD5, SHA1 e SHA-2 para oferecer suporte adequado aos algoritmos suportados pelo sistema Android Keystore em uma área isolada com segurança do código em execução no kernel e acima. O isolamento seguro DEVE bloquear todos os mecanismos potenciais pelos quais o código do kernel ou do espaço do usuário possa acessar o estado interno do ambiente isolado, incluindo DMA. O Android Open Source Project (AOSP) upstream atende a esse requisito usando a implementação Trusty , mas outra solução baseada em ARM TrustZone ou uma implementação segura revisada por terceiros de um isolamento adequado baseado em hipervisor são opções alternativas.
• [ 9.11 /T-0-3] DEVE realizar a autenticação da tela de bloqueio no ambiente de execução isolado e somente quando bem sucedido, permitir que as chaves vinculadas à autenticação sejam usadas. As credenciais da tela de bloqueio DEVEM ser armazenadas de forma que permita que apenas o ambiente de execução isolado execute a autenticação da tela de bloqueio. O Android Open Source Project upstream fornece o Gatekeeper Hardware Abstraction Layer (HAL) e o Trusty, que podem ser usados ​​para satisfazer esse requisito.
• [ 9.11 /T-0-4] DEVE oferecer suporte ao atestado de chave onde a chave de assinatura do atestado é protegida por hardware seguro e a assinatura é executada em hardware seguro. As chaves de assinatura de atestado DEVEM ser compartilhadas entre um número grande o suficiente de dispositivos para evitar que as chaves sejam usadas como identificadores de dispositivos. Uma forma de atender a esse requisito é compartilhar a mesma chave de atestado, a menos que sejam produzidas pelo menos 100.000 unidades de um determinado SKU. Se forem produzidas mais de 100.000 unidades de um SKU, uma chave diferente PODE ser usada para cada 100.000 unidades.

Observe que se uma implementação de dispositivo já tiver sido lançada em uma versão anterior do Android, tal dispositivo estará isento do requisito de ter um armazenamento de chaves apoiado por um ambiente de execução isolado e suportar o atestado de chave, a menos que declare o android.hardware.fingerprint que requer um keystore apoiado por um ambiente de execução isolado.

Se as implementações de dispositivos de televisão suportarem uma tela de bloqueio segura, elas:

• [ 9.11 /T-1-1] DEVE permitir que o usuário escolha o tempo limite de suspensão para transição do estado desbloqueado para bloqueado, com um tempo limite mínimo permitido de até 15 segundos ou menos.

Se as implementações de dispositivos de televisão incluírem vários usuários e não declararem o sinalizador de recurso android.hardware.telephony , elas:

• [ 9.5 /T-2-1] DEVE oferecer suporte a perfis restritos, um recurso que permite aos proprietários de dispositivos gerenciar usuários adicionais e seus recursos no dispositivo. Com perfis restritos, os proprietários de dispositivos podem configurar rapidamente ambientes separados para usuários adicionais trabalharem, com a capacidade de gerenciar restrições mais detalhadas nos aplicativos disponíveis nesses ambientes.

Se as implementações de dispositivos de televisão incluírem vários usuários e declararem o sinalizador de recurso android.hardware.telephony , elas:

• [ 9.5 /T-3-1] NÃO DEVE suportar perfis restritos, mas DEVE se alinhar com a implementação de controles do AOSP para permitir/desabilitar o acesso de outros usuários às chamadas de voz e SMS.

Se as implementações de dispositivos de televisão declararem android.hardware.microphone , elas:

• [ 9.8.2 /T-4-1] DEVE exibir o indicador do microfone quando um aplicativo está acessando dados de áudio do microfone, mas não quando o microfone é acessado apenas por HotwordDetectionService, SOURCE_HOTWORD, ContentCaptureService ou aplicativos que possuem as funções indicadas em Seção 9.1 Permissões com identificador CDD C-3-X].
• [ 9.8.2 /T-4-2] NÃO DEVE ocultar o indicador do microfone para aplicativos do sistema que tenham interfaces de usuário visíveis ou interação direta do usuário.

Se as implementações de dispositivos de televisão declararem android.hardware.camera.any , elas:

• [ 9.8.2 /T-5-1] DEVE exibir o indicador da câmera quando um aplicativo estiver acessando dados da câmera ao vivo, mas não quando a câmera estiver sendo acessada apenas por aplicativos que detêm as funções descritas na Seção 9.1 Permissões com CDD identificador [C-3-X].
• [ 9.8.2 /T-5-2] NÃO DEVE ocultar o indicador da câmera para aplicativos do sistema que tenham interfaces de usuário visíveis ou interação direta do usuário.

2.3.6. Compatibilidade com ferramentas e opções do desenvolvedor

Implementações de dispositivos de televisão:

• Perfeito
  • [ 6.1 /T-0-1] DEVE expor um binário /system/bin/perfetto ao usuário shell cujo cmdline esteja em conformidade com a documentação do perfetto .
  • [ 6.1 /T-0-2] O binário perfetto DEVE aceitar como entrada uma configuração do protobuf que esteja em conformidade com o esquema definido na documentação do perfetto .
  • [ 6.1 /T-0-3] O binário perfetto DEVE escrever como saída um rastreamento protobuf que esteja em conformidade com o esquema definido na documentação do perfetto .
  • [ 6.1 /T-0-4] DEVE fornecer, através do binário perfetto, pelo menos as fontes de dados descritas na documentação do perfetto .

2.4. Requisitos de observação

Um dispositivo Android Watch refere-se a uma implementação de dispositivo Android destinada a ser usada no corpo, talvez no pulso.

As implementações de dispositivos Android são classificadas como Watch se atenderem a todos os seguintes critérios:

• Tenha uma tela com comprimento diagonal físico na faixa de 1,1 a 2,5 polegadas.
• Possui um mecanismo fornecido para ser usado no corpo.

Os requisitos adicionais no restante desta seção são específicos para implementações de dispositivos Android Watch.

2.4.1. Hardware

Assista às implementações de dispositivos:

• [ 7.1 .1.1/W-0-1] DEVE ter uma tela com tamanho diagonal físico na faixa de 1,1 a 2,5 polegadas.

• [ 7.2 .3/W-0-1] DEVE ter a função Home disponível para o usuário e a função Back exceto quando estiver em UI_MODE_TYPE_WATCH .

• [ 7.2 .4/W-0-1] DEVE suportar entrada de tela sensível ao toque.

• [ 7.3 .1/W-SR-1] É FORTEMENTE RECOMENDADO incluir um acelerômetro de 3 eixos.

Se as implementações do dispositivo Watch incluírem um receptor GPS/GNSS e reportarem a capacidade aos aplicativos por meio do sinalizador de recurso android.hardware.location.gps , eles:

• [ 7.3 .3/W-1-1] DEVE reportar medições GNSS, assim que forem encontradas, mesmo que uma localização calculada a partir de GPS/GNSS ainda não tenha sido reportada.
• [ 7.3.3 /W-1-2] DEVE relatar pseudodistâncias GNSS e taxas de pseudodistância que, em condições de céu aberto após a determinação da localização, enquanto estacionário ou em movimento com menos de 0,2 metro por segundo quadrado de aceleração, sejam suficientes para calcular posição dentro de 20 metros e velocidade dentro de 0,2 metros por segundo, pelo menos 95% do tempo.

Se as implementações do dispositivo Watch incluírem um giroscópio de 3 eixos, elas:

• [ 7.3.4 /W-2-1] DEVE ser capaz de medir mudanças de orientação de até 1000 graus por segundo.

Assista às implementações de dispositivos:

• [ 7.4 .3/W-0-1] DEVE suportar Bluetooth.

• [ 7.6 .1/W-0-1] DEVE ter pelo menos 1 GB de armazenamento não volátil disponível para dados privados do aplicativo (também conhecido como partição "/data").

• [ 7.6 .1/W-0-2] DEVE ter pelo menos 416 MB de memória disponível para o kernel e espaço do usuário.

• [ 7.8 .1/W-0-1] DEVE incluir um microfone.

• [ 7.8.2 /W] PODE ter saída de áudio.

2.4.2. Multimídia

Sem requisitos adicionais.

2.4.3. Programas

Assista às implementações de dispositivos:

• [ 3 /W-0-1] DEVE declarar o recurso android.hardware.type.watch .
• [ 3 /W-0-2] DEVE suportar uiMode = UI_MODE_TYPE_WATCH .
• [ 3.2.3.1 /W-0-1] DEVE pré-carregar um ou mais aplicativos ou componentes de serviço com um manipulador de intenções, para todos os padrões de filtro de intenções públicas definidos pelas seguintes intenções de aplicativos listadas aqui .

Assista às implementações de dispositivos:

• [ 3.8.4 /W-SR-1] É FORTEMENTE RECOMENDADO implementar um assistente no dispositivo para lidar com a ação Assist .

Observe as implementações de dispositivos que declaram o sinalizador de recurso android.hardware.audio.output :

• [ 3.10 /W-1-1] DEVE oferecer suporte a serviços de acessibilidade de terceiros.
• [ 3.10 /W-SR-1] É FORTEMENTE RECOMENDADO pré-carregar serviços de acessibilidade no dispositivo comparáveis ​​ou superiores à funcionalidade dos serviços de acessibilidade Switch Access e TalkBack (para idiomas suportados pelo mecanismo de conversão de texto em fala pré-instalado), conforme fornecido no projeto de código aberto talkback .

Se as implementações do dispositivo Watch reportarem o recurso android.hardware.audio.output, elas:

• [ 3.11 /W-SR-1] É FORTEMENTE RECOMENDADO incluir um mecanismo TTS que suporte os idiomas disponíveis no dispositivo.

• [ 3.11 /W-0-1] DEVE suportar a instalação de mecanismos TTS de terceiros.

2.4.4. Desempenho e potência

Se as implementações do dispositivo Watch incluírem recursos para melhorar o gerenciamento de energia do dispositivo incluídos no AOSP ou estender os recursos incluídos no AOSP, elas:

• [ 8.3 /W-SR-1] São FORTEMENTE RECOMENDADOS para fornecer ao usuário recursos para exibir todos os aplicativos que estão isentos dos modos de economia de energia App Standby e Doze.
• [ 8.3 /W-SR-2] São FORTEMENTE RECOMENDADOS para fornecer ao usuário recursos para ativar e desativar o recurso de economia de bateria.

Assista às implementações de dispositivos:

• [ 8.4 /W-0-1] DEVE fornecer um perfil de energia por componente que defina o valor de consumo atual para cada componente de hardware e o consumo aproximado de bateria causado pelos componentes ao longo do tempo, conforme documentado no site do Android Open Source Project.
• [ 8.4 /W-0-2] DEVE informar todos os valores de consumo de energia em miliamperes-hora (mAh).
• [ 8.4 /W-0-3] DEVE relatar o consumo de energia da CPU por UID de cada processo. O Android Open Source Project atende ao requisito por meio da implementação do módulo do kernel uid_cputime .
• [ 8.4 /W-0-4] DEVE disponibilizar esse uso de energia por meio do comando shell adb shell dumpsys batterystats para o desenvolvedor do aplicativo.
• [ 8.4 /W] DEVE ser atribuído ao próprio componente de hardware se não for possível atribuir o uso de energia do componente de hardware a um aplicativo.

2.4.5. Modelo de segurança

Assista às implementações de dispositivos:

• [9/W-0-1] DEVE declarar o recurso android.hardware.security.model.compatible .

Se as implementações do dispositivo Watch incluírem vários usuários e não declararem o sinalizador de recurso android.hardware.telephony , elas:

• [ 9.5 /W-1-1] DEVE oferecer suporte a perfis restritos, um recurso que permite aos proprietários de dispositivos gerenciar usuários adicionais e seus recursos no dispositivo. Com perfis restritos, os proprietários de dispositivos podem configurar rapidamente ambientes separados para usuários adicionais trabalharem, com a capacidade de gerenciar restrições mais detalhadas nos aplicativos disponíveis nesses ambientes.

Se as implementações do dispositivo Watch incluírem vários usuários e declararem o sinalizador de recurso android.hardware.telephony , elas:

• [ 9.5 /W-2-1] NÃO DEVE suportar perfis restritos, mas DEVE se alinhar com a implementação de controles do AOSP para permitir/desabilitar o acesso de outros usuários às chamadas de voz e SMS.

Se as implementações de dispositivos tiverem uma tela de bloqueio segura e incluírem um ou mais agentes confiáveis, que implementam a API do sistema TrustAgentService , elas:

• [ 9.11.1 /W-1-1] DEVE desafiar o usuário para um dos métodos de autenticação primários recomendados (por exemplo: PIN, padrão, senha) com mais frequência do que uma vez a cada 72 horas.

2.5. Requisitos Automotivos

A implementação do Android Automotive refere-se a uma unidade principal do veículo executando o Android como sistema operacional para parte ou todo o sistema e/ou funcionalidade de infoentretenimento.

As implementações de dispositivos Android são classificadas como automotivas se declararem o recurso android.hardware.type.automotive ou atenderem a todos os critérios a seguir.

• São incorporados como parte ou conectáveis ​​a um veículo automotivo.
• Estão usando uma tela na fileira do banco do motorista como exibição principal.

Os requisitos adicionais no restante desta seção são específicos para implementações de dispositivos Android Automotive.

2.5.1. Hardware

Implementações de dispositivos automotivos:

• [ 7.1 .1.1/A-0-1] DEVE ter uma tela de pelo menos 6 polegadas de tamanho diagonal físico.
• [ 7.1 .1.1/A-0-2] DEVE ter um layout de tamanho de tela de pelo menos 750 dp x 480 dp.
• [ 7.2 .3/A-0-1] DEVE fornecer a função Home e PODE fornecer as funções Voltar e Recente.
• [ 7.2 .3/A-0-2] DEVE enviar o evento de pressionamento normal e longo da função Back ( KEYCODE_BACK ) para o aplicativo em primeiro plano.
• [ 7.3 /A-0-1] DEVE implementar e relatar GEAR_SELECTION , NIGHT_MODE , PERF_VEHICLE_SPEED e PARKING_BRAKE_ON .
• [ 7.3 /A-0-2] O valor do sinalizador NIGHT_MODE DEVE ser consistente com o modo dia/noite do painel e DEVE ser baseado na entrada do sensor de luz ambiente. O sensor de luz ambiente subjacente PODE ser o mesmo do Fotômetro .
• [ 7.3 /A-0-3] DEVE fornecer o campo de informações adicionais do sensor TYPE_SENSOR_PLACEMENT como parte do SensorAdditionalInfo para cada sensor fornecido.
• [ 7.3 /A-SR1] PODE calcular a localização fundindo GPS/GNSS com sensores adicionais. Se a Localização for calculada, é FORTEMENTE RECOMENDADO implementar e relatar os tipos de sensores correspondentes e/ou IDs de propriedade do veículo usados.

• [ 7.3 /A-0-4] O local solicitado por meio de LocationManager#requestLocationUpdates() NÃO DEVE corresponder ao mapa.

• [ 7.3.1 /A-0-4] DEVE estar em conformidade com o sistema de coordenadas do sensor do carro Android.

• [ 7.3 /A-SR-1] É FORTEMENTE_RECOMENDADO incluir um acelerômetro de 3 eixos e um giroscópio de 3 eixos.

• [ 7.3 /A-SR-2] São STRONGLY_RECOMMENDED implementar e reportar sensor TYPE_HEADING .

Se as implementações de dispositivos automotivos suportarem OpenGL ES 3.1, elas:

• [ 7.1.4.1/A-0-1 ] DEVE declarar OpenGL ES 3.1 ou superior.
• [ 7.1 .4.1/A-0-2] DEVE suportar Vulkan 1.1.
• [ 7.1 .4.1/A-0-3] DEVE incluir o carregador Vulkan e exportar todos os símbolos.

Se as implementações de dispositivos automotivos incluírem um acelerômetro, elas:

• [ 7.3 .1/A-1-1] DEVE ser capaz de relatar eventos até uma frequência de pelo menos 100 Hz.

Se as implementações do dispositivo incluírem um acelerômetro de 3 eixos, elas:

• [ 7.3 .1/A-SR-1] São FORTEMENTE RECOMENDADOS para implementar o sensor composto para acelerômetro de eixos limitados.

Se as implementações de dispositivos automotivos incluírem um acelerômetro com menos de 3 eixos, elas:

• [ 7.3 .1/A-1-3] DEVE implementar e reportar o sensor TYPE_ACCELEROMETER_LIMITED_AXES .
• [ 7.3 .1/A-1-4] DEVE implementar e reportar o sensor TYPE_ACCELEROMETER_LIMITED_AXES_UNCALIBRATED .

Se as implementações de dispositivos automotivos incluírem um giroscópio, elas:

• [ 7.3 .4/A-2-1] DEVE ser capaz de relatar eventos até uma frequência de pelo menos 100 Hz.
• [ 7.3 .4/A-2-3] DEVE ser capaz de medir mudanças de orientação de até 250 graus por segundo.
• [ 7.3 .4/A-SR-1] É FORTEMENTE RECOMENDADO configurar a faixa de medição do giroscópio para +/-250dps para maximizar a resolução possível.

Se as implementações de dispositivos automotivos incluírem um giroscópio de 3 eixos, elas:

• [ 7.3 .4/A-SR-2] São FORTEMENTE RECOMENDADOS para implementar o sensor composto para giroscópio de eixos limitados.

Se as implementações de dispositivos automotivos incluírem um giroscópio com menos de 3 eixos, elas:

• [ 7.3 .4/A-4-1] DEVE implementar e reportar o sensor TYPE_GYROSCOPE_LIMITED_AXES .
• [ 7.3 .4/A-4-2] DEVE implementar e reportar o sensor TYPE_GYROSCOPE_LIMITED_AXES_UNCALIBRATED .

Se as implementações de dispositivos automotivos incluírem um receptor GPS/GNSS, mas não incluírem conectividade de dados baseada em rede celular, elas:

• [ 7.3 .3/A-3-1] DEVE determinar a localização na primeira vez que o receptor GPS/GNSS for ligado ou após mais de 4 dias em 60 segundos.
• [ 7.3 .3/A-3-2] DEVE atender aos critérios de tempo para a primeira correção, conforme descrito em 7.3.3/C-1-2 e 7.3.3/C-1-6 para todas as outras solicitações de localização ( ou seja, solicitações que não são a primeira vez ou após mais de 4 dias). O requisito 7.3.3/C-1-2 é normalmente atendido em veículos sem conectividade de dados baseada em rede celular, usando previsões de órbita GNSS calculadas no receptor ou usando a última localização conhecida do veículo junto com a capacidade de calcular pelo menos pelo menos 60 segundos com uma precisão de posição satisfatória 7.3.3/C-1-3 , ou uma combinação de ambos.

Se as implementações de dispositivos automotivos incluírem um sensor TYPE_HEADING , elas:

• [ 7.3 .4/A-4-3] DEVE ser capaz de relatar eventos até uma frequência de pelo menos 1 Hz.
• [ 7.3 .4/A-SR-3] STRONGLY_RECOMMENDED relatar eventos até uma frequência de pelo menos 10 Hz.
• DEVE ser uma referência ao norte verdadeiro.
• DEVE estar disponível mesmo quando o veículo estiver parado.
• DEVE ter uma resolução de pelo menos 1 grau.

Implementações de dispositivos automotivos:

• [ 7.4.3 /A-0-1] DEVE suportar Bluetooth e DEVE suportar Bluetooth LE.
• [ 7.4 .3/A-0-2] As implementações do Android Automotive DEVEM oferecer suporte aos seguintes perfis Bluetooth:
  • Chamadas telefônicas através do perfil viva-voz (HFP).
  • Reprodução de mídia através do perfil de distribuição de áudio (A2DP).
  • Controle de reprodução de mídia através do perfil de controle remoto (AVRCP).
  • Compartilhamento de contatos usando o perfil de acesso à lista telefônica (PBAP).

• [ 7.4 .3/A-SR-1] São FORTEMENTE RECOMENDADOS para suportar Perfil de Acesso a Mensagens (MAP).

• [ 7.4.5 /A] DEVE incluir suporte para conectividade de dados baseada em rede celular.

• [ 7.4 .5/A] PODE usar a constante API do sistema NetworkCapabilities#NET_CAPABILITY_OEM_PAID para redes que devem estar disponíveis para aplicativos do sistema.

Se as implementações do dispositivo incluírem suporte para transmissão de rádio AM/FM e exporem a funcionalidade a qualquer aplicativo, elas:

• [ 7.4 /A-0-1] DEVE declarar suporte para FEATURE_BROADCAST_RADIO .

Uma câmara traseira significa uma câmara voltada para o mundo que pode estar localizada em qualquer lugar do veículo e está voltada para o exterior da cabina do veículo; isto é, ele captura cenas do outro lado da carroceria do veículo, como a câmera retrovisora.

Uma câmara frontal significa uma câmara voltada para o utilizador que pode estar localizada em qualquer lugar do veículo e está voltada para o interior da cabina do veículo; isto é, imagens do usuário, como para videoconferência e aplicativos semelhantes.

Implementações de dispositivos automotivos:

• [7.5/A-SR-1] É FORTEMENTE RECOMENDADO incluir uma ou mais câmeras voltadas para o mundo.
• PODE incluir uma ou mais câmeras voltadas para o usuário.
• [7.5/A-SR-2] São FORTEMENTE RECOMENDADOS para suportar streaming simultâneo de múltiplas câmeras.

Se as implementações de dispositivos automotivos incluírem pelo menos uma câmera voltada para o mundo, então, para tal câmera, elas:

• [7.5/A-1-1] DEVE ser orientado de forma que a dimensão longa da câmera se alinhe com o plano XY dos eixos do sensor automotivo Android.
• [7.5/A-SR-3] É FORTEMENTE RECOMENDADO ter hardware de foco fixo ou EDOF (Profundidade de Campo Estendida).
• [7.5/A-1-2] DEVE ter a câmera primária voltada para o mundo como a câmera voltada para o mundo com o ID de câmera mais baixo.

Se as implementações de dispositivos automotivos incluírem pelo menos uma câmera voltada para o usuário, para tal câmera:

• [7.5/A-2-1] A câmera primária voltada para o usuário DEVE ser a câmera voltada para o usuário com o ID de câmera mais baixo.
• PODE ser orientado de forma que a dimensão longa da câmera se alinhe com o plano XY dos eixos do sensor automotivo Android.

Se as implementações de dispositivos automotivos incluírem uma câmera acessível por meio da API android.hardware.Camera ou android.hardware.camera2 , elas:

• [7.5/A-3-1] DEVE cumprir os requisitos principais da câmera na seção 7.5.

Se as implementações de dispositivos automotivos incluírem uma câmera que não é acessível por meio da API android.hardware.Camera ou android.hardware.camera2 , elas:

• [7.5/A-4-1] DEVE ser acessível através do serviço Extended View System.

Se as implementações de dispositivos automotivos incluírem uma ou mais câmeras acessíveis por meio do Extended View System Service, para tal câmera, elas:

• [7.5/A-5-1] NÃO DEVE girar ou espelhar horizontalmente a visualização da câmera.
• [7.5/A-SR-4] É FORTEMENTE RECOMENDADO ter uma resolução de pelo menos 1,3 megapixels.

Se as implementações de dispositivos automotivos incluírem uma ou mais câmeras acessíveis por meio do Extended View System Service e da API android.hardware.Camera ou android.hardware.Camera2 , então, para tal câmera, elas:

• [7.5/A-6-1] DEVE informar o mesmo ID da câmera.

Se as implementações de dispositivos automotivos fornecerem uma API de câmera proprietária, elas:

• [7.5/A-7-1] DEVE implementar tal API de câmera usando android.hardware.camera2 API ou Extended View System API.

Implementações de dispositivos automotivos:

• [ 7.6 .1/A-0-1] DEVE ter pelo menos 4 GB de armazenamento não volátil disponível para dados privados do aplicativo (também conhecida como partição "/data").

• [ 7.6 .1/A] DEVE formatar a partição de dados para oferecer melhor desempenho e longevidade no armazenamento flash, por exemplo, usando o sistema de arquivos f2fs .

Se as implementações de dispositivos automotivos fornecerem armazenamento externo compartilhado por meio de uma parte do armazenamento interno não removível, elas:

• [ 7.6 .1/A-SR-1] São FORTEMENTE RECOMENDADOS para reduzir a sobrecarga de E/S em operações realizadas no armazenamento externo, por exemplo, usando SDCardFS .

Se as implementações de dispositivos automotivos forem de 64 bits:

• [ 7.6 .1/A-2-1] A memória disponível para o kernel e espaço do usuário DEVE ser de pelo menos 816 MB se qualquer uma das seguintes densidades for usada:

  • 280 dpi ou menos em telas pequenas/normais
  • ldpi ou inferior em telas extragrandes
  • mdpi ou inferior em telas grandes

• [ 7.6 .1/A-2-2] A memória disponível para o kernel e espaço do usuário DEVE ser de pelo menos 944 MB se qualquer uma das seguintes densidades for usada:

  • xhdpi ou superior em telas pequenas/normais
  • hdpi ou superior em telas grandes
  • mdpi ou superior em telas extragrandes

• [ 7.6 .1/A-2-3] A memória disponível para o kernel e espaço do usuário DEVE ser de pelo menos 1280 MB se qualquer uma das seguintes densidades for usada:

  • 400 dpi ou superior em telas pequenas/normais
  • xhdpi ou superior em telas grandes
  • tvdpi ou superior em telas extragrandes

• [ 7.6 .1/A-2-4] A memória disponível para o kernel e espaço do usuário DEVE ser de pelo menos 1824 MB se qualquer uma das seguintes densidades for usada:

  • 560 dpi ou superior em telas pequenas/normais
  • 400 dpi ou superior em telas grandes
  • xhdpi ou superior em telas extragrandes

Observe que a "memória disponível para o kernel e espaço do usuário" acima se refere ao espaço de memória fornecido além de qualquer memória já dedicada a componentes de hardware, como rádio, vídeo e assim por diante, que não estão sob o controle do kernel nas implementações de dispositivos.

Implementações de dispositivos automotivos:

• [ 7.7 .1/A] DEVE incluir uma porta USB com suporte para modo periférico.

Implementações de dispositivos automotivos:

• [ 7.8 .1/A-0-1] DEVE incluir um microfone.

Implementações de dispositivos automotivos:

• [ 7.8 .2/A-0-1] DEVE ter uma saída de áudio e declarar android.hardware.audio.output .

2.5.2. Multimídia

As implementações de dispositivos automotivos DEVEM suportar os seguintes formatos de codificação e decodificação de áudio e disponibilizá-los para aplicativos de terceiros:

• [ 5.1 /A-0-1] Perfil MPEG-4 AAC (AAC LC)
• [ 5.1 /A-0-2] Perfil MPEG-4 HE AAC (AAC+)
• [ 5.1 /A-0-3] AAC ELD (AAC de baixo atraso aprimorado)

As implementações de dispositivos automotivos DEVEM suportar os seguintes formatos de codificação de vídeo e disponibilizá-los para aplicativos de terceiros:

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

As implementações de dispositivos automotivos DEVEM suportar os seguintes formatos de decodificação de vídeo e disponibilizá-los para aplicativos de terceiros:

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

Implementações de dispositivos automotivos são FORTEMENTE RECOMENDADAS para suportar a seguinte decodificação de vídeo:

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

2.5.3. Programas

Implementações de dispositivos automotivos:

• [ 3 /A-0-1] DEVE declarar o recurso android.hardware.type.automotive .

• [ 3 /A-0-2] DEVE suportar uiMode = UI_MODE_TYPE_CAR .

• [ 3 /A-0-3] DEVE oferecer suporte a todas as APIs públicas no namespace android.car.* .

Iniciar novos requisitos para 15 (AOSP experimental)

[3/A-0-4] [Retirado] (visualização de 8 de abril de 2024)

Este requisito foi retirado do Android 15 (AOSP experimental).

Acabar com novos requisitos

[3/A-0-4] (visualização de 11 de dezembro de 2023)

• [ 3 /A-0-4] DEVE oferecer suporte ao aplicativo Adapt para telas de carros.

Acabar com novos requisitos

Se as implementações de dispositivos automotivos fornecerem uma API proprietária usando android.car.CarPropertyManager com android.car.VehiclePropertyIds , elas:

• [ 3 /A-1-1] NÃO DEVE atribuir privilégios especiais ao uso dessas propriedades por aplicativos do sistema ou impedir que aplicativos de terceiros usem essas propriedades.
• [ 3 /A-1-2] NÃO DEVE replicar uma propriedade de veículo que já exista no SDK .

Implementações de dispositivos automotivos:

• [ 3.2.1 /A-0-1] DEVE apoiar e aplicar todas as constantes de permissões, conforme documentado na página de referência de Permissão Automotiva .

• [ 3.2.3.1 /A-0-1] DEVE pré-carregar um ou mais aplicativos ou componentes de serviço com um manipulador de intenções, para todos os padrões de filtro de intenções públicas definidos pelas seguintes intenções de aplicativos listadas aqui .

• [ 3.4.1 /A-0-1] DEVE fornecer uma implementação completa da API android.webkit.Webview .

• [ 3.8 /A-0-1] NÃO DEVE permitir que usuários secundários completos que não sejam o usuário em primeiro plano atual iniciem atividades e tenham acesso à IU em quaisquer monitores.

• [ 3.8.3 /A-0-1] DEVE exibir notificações que usam a API Notification.CarExtender quando solicitadas por aplicativos de terceiros.

• [ 3.8.4 /A-SR-1] É altamente recomendável implementar um assistente no dispositivo para lidar com a ação Assist .

Se as implementações de dispositivos automotivos incluírem um botão push-to-talk, elas:

• [ 3.8 .4/A-1-1] DEVE usar um toque curto no botão push-to-talk como a interação designada para iniciar o aplicativo de assistência selecionado pelo usuário, em outras palavras, o aplicativo que implementa VoiceInteractionService .

Implementações de dispositivos automotivos:

• [ 3.8.3.1 /A-0-1] DEVE renderizar corretamente os recursos conforme descrito na documentação do SDK Notifications on Automotive OS .
• [ 3.8.3.1 /A-0-2] DEVE exibir PLAY e MUTE para ações de notificação no lugar daquelas fornecidas por meio de Notification.Builder.addAction()
• [ 3.8.3.1 /A] DEVE restringir o uso de tarefas de gerenciamento avançadas, como controles por canal de notificação. PODE usar recursos de UI por aplicativo para reduzir os controles.

Se as implementações de dispositivos automotivos suportarem propriedades HAL do usuário, elas:

• [ 3.9.3 /A-1-1] DEVE implementar todas as propriedades do ciclo de vida do usuário
  • INITIAL_USER_INFO , SWITCH_USER , CREATE_USER , REMOVE_USER .

Implementações de dispositivos automotivos:

• [ 3.14 /A-0-1] DEVE incluir uma estrutura de UI para oferecer suporte a aplicativos de terceiros usando APIs de mídia conforme descrito na seção 3.14 .
• [ 3.14 /A-0-2] DEVE permitir que o usuário interaja com segurança com aplicativos de mídia enquanto dirige.
• [ 3.14 /A-0-3] DEVE suportar a ação de intenção implícita CAR_INTENT_ACTION_MEDIA_TEMPLATE com o extra CAR_EXTRA_MEDIA_PACKAGE .
• [ 3.14 /A-0-4] DEVE fornecer uma capacidade para navegar na atividade de preferência de um aplicativo de mídia, mas DEVE ativá-la apenas quando as restrições de UX do carro não estiverem em vigor.
• [ 3.14 /A-0-5] DEVE exibir mensagens de erro definidas por aplicativos de mídia e DEVE suportar os extras opcionais ERROR_RESOLUTION_ACTION_LABEL e ERROR_RESOLUTION_ACTION_INTENT .
• [ 3.14 /A-0-6] DEVE oferecer suporte a recursos de pesquisa no aplicativo para aplicativos que suportam pesquisa.
• [ 3.14 /A-0-7] DEVE respeitar as definições CONTENT_STYLE_BROWSABLE_HINT e CONTENT_STYLE_PLAYABLE_HINT ao exibir a hierarquia do MediaBrowser .

Se as implementações de dispositivos automotivos incluirem um aplicativo de lançador padrão, eles:

• [ 3.14 /a-1-1] deve incluir serviços de mídia e abri-los com a intenção CAR_INTENT_ACTION_MEDIA_TEMPLATE .

Implementações de dispositivos automotivos:

Inicie novos requisitos para 15 (AOSP Experimental)

[3.14/a-0-8] (8 de abril de 2024 pré-visualização)

• [ 3.14 /a-0-8] devem fornecer acesso aos controles de mídia na ActivityBlockingActivity e na tela inicial para aplicativos otimizados para não distração .

Acabar com novos requisitos

• [ 3.8 /a] podem restringir as solicitações de aplicativos para inserir um modo de tela inteira, conforme descrito na immersive documentation .
• [ 3.8 /a] pode manter a barra de status e a barra de navegação visível o tempo todo.
• [ 3.8 /a] podem restringir as solicitações de aplicativos para alterar as cores por trás dos elementos da interface do usuário do sistema, para garantir que esses elementos sejam claramente visíveis o tempo todo.

2.5.4. Desempenho e potência

Implementações de dispositivos automotivos:

• [ 8.2 /a-0-1] devem relatar o número de bytes lidos e gravados em armazenamento não volátil de acordo com o UID de cada processo, para que as estatísticas estejam disponíveis para os desenvolvedores através do sistema API android.car.storagemonitoring.CarStorageMonitoringManager . O projeto de código aberto Android atende ao requisito através do módulo uid_sys_stats KERNEL.
• [ 8.3 /a-1-3] deve suportar o modo de garagem .
• [ 8.3 /a] deve estar no modo de garagem por pelo menos 15 minutos após cada unidade, a menos que:
  • A bateria é drenada.
  • Nenhum trabalho ocioso está agendado.
  • O motorista sai do modo de garagem.
• [ 8.4 /a-0-1] devem fornecer um perfil de potência por componente que define o valor atual do consumo para cada componente de hardware e o dreno aproximado da bateria causado pelos componentes ao longo do tempo, conforme documentado no site do projeto de código aberto Android.
• [ 8.4 /A-0-2] devem relatar todos os valores de consumo de energia em Horas Milliampere (MAH).
• [ 8.4 /a-0-3] devem relatar o consumo de energia da CPU de acordo com o UID de cada processo. O Android Open Source Project atende ao requisito por meio da implementação do módulo do kernel uid_cputime .
• [ 8.4 /a] devem ser atribuídos ao próprio componente de hardware, se não conseguir atribuir o uso de energia do componente de hardware a um aplicativo.
• [ 8.4 /a-0-4] deve disponibilizar esse uso de energia através do comando adb shell dumpsys batterystats para o desenvolvedor de aplicativos.

2.5.5. Modelo de segurança

Se as implementações de dispositivos automotivos suportarem vários usuários, eles:

• [ 9.5 /a-1-1] não deve permitir que os usuários interajam nem mude para o usuário do sistema sem cabeça , exceto para o provisionamento do dispositivo .
• [ 9.5 /a-1-2] deve alternar para um usuário secundário antes BOOT_COMPLETED .
• [ 9.5 /a-1-3] deve suportar a capacidade de criar um usuário convidado, mesmo quando o número máximo de usuários em um dispositivo foi atingido.

Se implementações de dispositivos automotivos declararem android.hardware.microphone , eles:

• [ 9.8.2 /a-1-1] deve exibir o indicador de microfone quando um aplicativo está acessando dados de áudio do microfone, mas não quando o microfone é acessado apenas por HotwordDetectionService , SOURCE_HOTWORD , ContentCaptureService ou aplicativos que mantêm os papéis chamados na seção 9.1 com identificador CDD [C-4-X].
• [ 9.8.2 /a-1-2] Não deve ocultar o indicador de microfone para aplicativos do sistema que possuem interfaces de usuário visíveis ou interação direta do usuário.
• [ 9.8.2 /a-1-3] deve fornecer uma possibilidade de usar o usuário para alternar o microfone no aplicativo Configurações.

Se implementações de dispositivos automotivos declararem android.hardware.camera.any , então eles:

• [ 9.8.2 /a-2-1] deve exibir o indicador da câmera quando um aplicativo está acessando dados da câmera ao vivo, mas não quando a câmera está sendo acessada apenas por aplicativos que mantêm as funções, conforme definido na seção 9.1 permissões com CDD Identificador [C-4-X].
• [ 9.8.2 /A-2-2] Não deve ocultar o indicador da câmera para aplicativos do sistema que possuem interfaces visíveis de usuário ou interação direta do usuário.
• [ 9.8.2 /A-2-3] Deve fornecer uma oferta de usuário para alternar a câmera no aplicativo Configurações.
• [ 9.8.2 /A-2-4] deve exibir aplicativos recentes e ativos usando a câmera conforme retornado da PermissionManager.getIndicatorAppOpUsageData()

Implementações de dispositivos automotivos:

• [9/a-0-1] deve declarar o recurso android.hardware.security.model.compatible .
• [ 9.11 /a-0-1] devem fazer backup da implementação do Keystore com um ambiente de execução isolado.
• [ 9.11 /a-0-2] Deve ter implementações de algoritmos criptográficos RSA, AES, EcdSA e HMAC e HHA-2 FUNCIÇÕES HASH para apoiar adequadamente os algoritmos apoiados pelo sistema de keystore de Android em uma área que é isolada segura com segurança do código em execução no kernel e acima. O isolamento seguro DEVE bloquear todos os mecanismos potenciais pelos quais o código do kernel ou do espaço do usuário possa acessar o estado interno do ambiente isolado, incluindo DMA. O Android Open Source Project (AOSP) upstream atende a esse requisito usando a implementação Trusty , mas outra solução baseada em ARM TrustZone ou uma implementação segura revisada por terceiros de um isolamento adequado baseado em hipervisor são opções alternativas.
• [ 9.11 /a-0-3] deve executar a autenticação da tela de bloqueio no ambiente de execução isolada e somente quando bem-sucedido, permitir que as chaves ligadas à autenticação sejam usadas. As credenciais da tela de bloqueio DEVEM ser armazenadas de forma que permita que apenas o ambiente de execução isolado execute a autenticação da tela de bloqueio. O Android Open Source Project upstream fornece o Gatekeeper Hardware Abstraction Layer (HAL) e o Trusty, que podem ser usados ​​para satisfazer esse requisito.
• [ 9.11 /a-0-4] deve suportar o atestado principal, onde a chave de assinatura do atestado é protegida por hardware seguro e a assinatura é executada em hardware seguro. As chaves de assinatura de atestado DEVEM ser compartilhadas entre um número grande o suficiente de dispositivos para evitar que as chaves sejam usadas como identificadores de dispositivos. Uma forma de atender a esse requisito é compartilhar a mesma chave de atestado, a menos que sejam produzidas pelo menos 100.000 unidades de um determinado SKU. Se forem produzidas mais de 100.000 unidades de um SKU, uma chave diferente PODE ser usada para cada 100.000 unidades.

Observe que se uma implementação de dispositivo já tiver sido lançada em uma versão anterior do Android, tal dispositivo estará isento do requisito de ter um armazenamento de chaves apoiado por um ambiente de execução isolado e suportar o atestado de chave, a menos que declare o android.hardware.fingerprint que requer um keystore apoiado por um ambiente de execução isolado.

Implementações de dispositivos automotivos:

• [ 9.14 /a-0-1] deve receber as mensagens de gatekeep dos subsistemas de veículos Android Framework, por exemplo, lista de mensagens permitidas da lista de permissão e fontes de mensagens.
• [ 9.14 /A-0-2] Deve Watchdog contra ataques de negação de serviço da estrutura Android ou aplicativos de terceiros. Isso contra o software malicioso inundando a rede de veículos com tráfego, o que pode levar a subsistemas de veículos com defeito.

2.5.6. Compatibilidade com ferramentas e opções do desenvolvedor

Implementações de dispositivos automotivos:

• Perfeito
  • [ 6.1 /a-0-1] deve expor binário A /system/bin/perfetto ao Usuário do Shell, que CMDline está em conformidade com a documentação perfeita .
  • [ 6.1 /a-0-2] O Binário Perfetto deve aceitar como entrada uma configuração do Protobuf que cumpre o esquema definido na documentação perfeita .
  • [ 6.1 /a-0-3] O Binário Perfetto deve escrever como saída de um rastreamento do protobuf que cumpre o esquema definido na documentação perfeita .
  • [ 6.1 /a-0-4] deve fornecer, através do binário perfeito, pelo menos as fontes de dados descritas na documentação perfeita .

2.6. Requisitos de tablet

Um dispositivo tablet Android refere -se a uma implementação do dispositivo Android que normalmente atende a todos os seguintes critérios:

• Usado segurando nas duas mãos.
• Não possui uma conclusão de molas ou conversível.
• As implementações físicas do teclado usadas com o dispositivo conectam por meio de uma conexão padrão (por exemplo, USB, Bluetooth).

• Possui uma fonte de energia que fornece mobilidade, como uma bateria.

• Tem um tamanho de tela maior que 7 ”e menos de 18", medido na diagonal.

As implementações de dispositivos de tablet têm requisitos semelhantes às implementações de dispositivos portáteis. As exceções são indicadas por um * nessa seção e observadas para referência nesta seção.

2.6.1. Hardware

Giroscópio

Se as implementações de dispositivos de tablet incluem um giroscópio de 3 eixos, eles:

• [ 7.3 .4/tab-1-1] deve ser capaz de medir alterações de orientação de até 1000 graus por segundo.

Memória e armazenamento mínimo (Seção 7.6.1)

As densidades de tela listadas para telas pequenas/normais nos requisitos de mão não são aplicáveis ​​aos tablets.

Inicie novos requisitos para 15 (AOSP Experimental)

[7.7.1/tab] (11 de dezembro de 2023 Visualização)

Modo periférico USB (Seção 7.7.1)

Se as implementações do dispositivo tablet incluem uma porta USB que suporta o modo periférico, eles:

• [ 7.7.1 /tab] pode implementar a API do Android Open Acessory (AOA).

Acabar com novos requisitos

Modo de realidade virtual (Seção 7.9.1)

Realidade virtual de alto desempenho (Seção 7.9.2)

Os requisitos de realidade virtual não são aplicáveis ​​aos tablets.

2.6.2. Modelo de segurança

Chaves e credenciais (Seção 9.11)

Consulte a seção [ 9.11 ].

Se as implementações do dispositivo tablet incluem vários usuários e não declararem o sinalizador android.hardware.telephony , eles: eles:

• [ 9.5 /T-1-1] deve suportar perfis restritos, um recurso que permite aos proprietários de dispositivos gerenciar usuários adicionais e seus recursos no dispositivo. Com perfis restritos, os proprietários de dispositivos podem configurar rapidamente ambientes separados para usuários adicionais trabalharem, com a capacidade de gerenciar restrições mais detalhadas nos aplicativos disponíveis nesses ambientes.

Se as implementações do dispositivo tablet incluirem vários usuários e declarar o sinalizador android.hardware.telephony , eles: eles:

• [ 9.5 /T-2-1] não deve suportar perfis restritos, mas devem se alinhar com a implementação do AOSP de controles para permitir que os usuários desativem /desativem os usuários de acessar as chamadas de voz e SMS.

2.6.2. Programas

• [ 3.2.3.1 /tab-0-1] devem pré-carregar um ou mais aplicativos ou componentes de serviço com um manipulador de intenções, para todos os padrões de filtro de intenção pública definidos pelas seguintes intenções de aplicação listadas aqui .

3. Software

3.1. Compatibilidade da API gerenciada

O ambiente de execução de Bytecode Dalvik gerenciado é o veículo principal para aplicações Android. A interface de programação de aplicativos Android (API) é o conjunto de interfaces da plataforma Android expostas a aplicativos em execução no ambiente de tempo de execução gerenciado.

Implementações de dispositivos:

• [C-0-1] deve fornecer implementações completas, incluindo todos os comportamentos documentados, de qualquer API documentada exposta pelo Android SDK ou qualquer API decorada com o marcador "@Systemapi" no código-fonte Android a montante.

• [C-0-2] deve apoiar/preservar todas as classes, métodos e elementos associados marcados pela anotação testapi (@Testapi).

• [C-0-3] não deve omitir nenhuma API gerenciada, alterar interfaces ou assinaturas da API, desviar-se do comportamento documentado ou incluir ninguém, exceto quando especificamente permitido por essa definição de compatibilidade.

• [C-0-4] ainda deve manter as APIs presentes e se comportar de maneira razoável, mesmo quando alguns recursos de hardware para os quais o Android inclui APIs são omitidos. Consulte a Seção 7 para obter requisitos específicos para esse cenário.

• [C-0-5] não deve permitir que aplicativos de terceiros usem interfaces não SDK, que são definidas como métodos e campos nos pacotes de idiomas Java que estão no caminho de inicialização no AOSP, e que não fazem parte dos Public SDK. Isso inclui APIs decoradas com a anotação @hide , mas não com um @SystemAPI , conforme descrito nos documentos SDK e membros privados e privados da classe.

• [C-0-6] deve ser enviado com toda e todas as interface não SDK nas mesmas listas restritas, fornecidas através das bandeiras provisórias e denilistas em prebuilts/runtime/appcompat/hiddenapi-flags.csv para a filial de nível de API apropriada em o AOSP.

• [C-0-7] deve apoiar o mecanismo de atualização dinâmica de configuração assinada para remover interfaces não SDK de uma lista restrita incorporando a configuração assinada em qualquer APK, usando as teclas públicas existentes presentes no AOSP.

  No entanto, eles:

  • Pode, se uma API oculta estiver ausente ou implementada de maneira diferente na implementação do dispositivo, mova a API oculta para o denilista ou omitra -a de todas as listas restritas.
  • Pode, se uma API oculta ainda não existir no AOSP, adicione a API oculta a qualquer uma das listas restritas.

Inicie novos requisitos para 15 (AOSP Experimental)

[C-0-8] (8 de abril de 2024 Visualização)

• [C-0-8] não deve suportar a instalação de aplicativos direcionados a um nível de API menor que 23 24 .

Acabar com novos requisitos

[C-0-8] (11 de dezembro de 2023 Visualização)

• [C-0-8] não deve suportar a instalação de aplicativos direcionados a um nível de API menor que 23 25 .

Acabar com novos requisitos

3.1.1. Extensões Android

O Android suporta estender a superfície da API gerenciada de um nível de API específico, atualizando a versão de extensão para esse nível de API. A API android.os.ext.SdkExtensions.getExtensionVersion(int apiLevel) retorna a versão de extensão do apiLevel fornecido, se houver extensões para esse nível de API.

Implementações de dispositivos Android:

• [C-0-1] deve pré-carregar a implementação da AOSP do extsouso do ExtShared da Biblioteca Compartilhado e dos ExtServices com versões maiores ou iguais às versões mínimas permitidas por cada nível da API. Por exemplo, as implementações do dispositivo Android 7.0, o nível de API em execução 24 deve incluir pelo menos a versão 1.

• [C-0-2] deve retornar apenas o número da versão de extensão válida que foi definida pelo AOSP.

• [C-0-3] deve suportar todas as APIs definidas pelas versões de extensão devolvidas por android.os.ext.SdkExtensions.getExtensionVersion(int apiLevel) da mesma maneira que outras APIs gerenciadas são suportadas, seguindo os requisitos na Seção 3.1 .

3.1.2. Biblioteca Android

Devido à depreciação do cliente HTTP Apache , implementações de dispositivos:

• [C-0-1] não deve colocar a biblioteca org.apache.http.legacy no bootclasspath.
• [C-0-2] deve adicionar a biblioteca org.apache.http.legacy ao aplicativo ClassPath Somente quando o aplicativo satisfaz uma das seguintes condições:
  • Alvo o nível de API 28 ou inferior.
  • Declara em seu manifesto que precisa da biblioteca definindo o atributo android:name de <uses-library> para org.apache.http.legacy .

A implementação da AOSP atende a esses requisitos.

3.2. Compatibilidade da API SOFT

Além das APIs gerenciadas da Seção 3.1 , o Android também inclui uma API "Soft", somente de tempo de execução significativa, na forma de coisas como intenções, permissões e aspectos semelhantes de aplicativos Android que não podem ser aplicados no tempo de compilação do aplicativo.

3.2.1. Permissões

• [C-0-1] Os implementadores de dispositivos devem suportar e aplicar todas as constantes de permissão, conforme documentado pela página de referência de permissão . Observe que a Seção 9 lista requisitos adicionais relacionados ao modelo de segurança do Android.

3.2.2. Construir parâmetros

As APIs do Android incluem uma série de constantes na classe Android.OS.Build , destinada a descrever o dispositivo atual.

• [C-0-1] Para fornecer valores consistentes e significativos nas implementações de dispositivos, a tabela abaixo inclui restrições adicionais nos formatos desses valores aos quais as implementações do dispositivo devem estar em conformidade.

Parâmetro	Detalhes
Versão.Release	A versão do sistema Android atualmente executado, em formato legível por humanos. Este campo deve ter um dos valores de string definidos nas cadeias de versão permitida para o Android 15 .
Version.sdk	A versão do sistema Android atualmente executado, em um formato acessível ao código de aplicativo de terceiros. Para o Android 15, esse campo deve ter o valor inteiro 15_INT.
Versão.sdk_int	A versão do sistema Android atualmente executado, em um formato acessível ao código de aplicativo de terceiros. Para o Android 15, esse campo deve ter o valor inteiro 15 int.
Versão.incremental	Um valor escolhido pelo implementador do dispositivo designando a construção específica do sistema Android atualmente executado, em formato legível por humanos. Esse valor não deve ser reutilizado para diferentes construções disponibilizadas para os usuários finais. Um uso típico desse campo é indicar qual número de compilação ou identificador de alteração de controle de fonte foi usado para gerar a compilação. O valor deste campo deve ser codificável como ASCII imprimível de 7 bits e corresponder à expressão regular ^[^ :\/~]+$ .
QUADRO	Um valor escolhido pelo implementador do dispositivo, identificando o hardware interno específico usado pelo dispositivo, em formato legível por humanos. Um possível uso desse campo é indicar a revisão específica da placa alimentando o dispositivo. O valor deste campo deve ser codificável como ASCII de 7 bits e corresponder à expressão regular ^[a-zA-Z0-9 -]+$ .
MARCA	Um valor refletindo o nome da marca associado ao dispositivo como conhecido pelos usuários finais. Deve estar em formato legível pelo homem e deve representar o fabricante do dispositivo ou a marca da empresa sob a qual o dispositivo é comercializado. O valor desse campo deve ser codificável como ASCII de 7 bits e corresponder à expressão regular ^[a-zA-Z0-9_-]+$ .
Suported_abis	O nome do conjunto de instruções (Tipo de CPU + Convenção ABI) do Código Nativo. Consulte a Seção 3.3. Compatibilidade da API nativa .
Suporte_32_bit_abis	O nome do conjunto de instruções (Tipo de CPU + Convenção ABI) do Código Nativo. Consulte a Seção 3.3. Compatibilidade da API nativa .
Suporte_64_bit_abis	O nome do segundo conjunto de instruções (Tipo de CPU + Convenção ABI) do código nativo. Consulte a Seção 3.3. Compatibilidade da API nativa .
Cpu_abi	O nome do conjunto de instruções (Tipo de CPU + Convenção ABI) do Código Nativo. Consulte a Seção 3.3. Compatibilidade da API nativa .
CPU_ABI2	O nome do segundo conjunto de instruções (Tipo de CPU + Convenção ABI) do código nativo. Consulte a Seção 3.3. Compatibilidade da API nativa .
DISPOSITIVO	Um valor escolhido pelo implementador do dispositivo que contém o nome de desenvolvimento ou o nome do código, identificando a configuração dos recursos de hardware e o design industrial do dispositivo. O valor deste campo deve ser codificável como ASCII de 7 bits e corresponder à expressão regular ^[a-zA-Z0-9 -]+$ . Este nome do dispositivo não deve mudar durante a vida útil do produto.
IMPRESSÃO DIGITAL	Uma string que identifica exclusivamente essa construção. Deve ser razoavelmente legível pelo homem. Deve seguir este modelo: $ (Marca)/$ (produto)/ $ (Dispositivo): $ (versão.Release)/$ (id)/$ (versão.Incremental): $ (tipo)/$ (tags) Por exemplo: acme/myProduct/ MyDevice: 15/lmyxx/3359: UserDebug/Test-Keys A impressão digital não deve incluir caracteres de espaço em branco. O valor deste campo deve ser codificável como ASCII de 7 bits.
HARDWARE	O nome do hardware (da linha de comando do kernel ou /proc). Deve ser razoavelmente legível pelo homem. O valor deste campo deve ser codificável como ASCII de 7 bits e corresponder à expressão regular ^[a-zA-Z0-9 -]+$ .
HOSPEDAR	Uma string que identifica exclusivamente o host que a construção foi construída, em formato legível por humanos. Não há requisitos no formato específico deste campo, exceto que ele não deve ser nulo ou a string vazia ("").
EU IA	Um identificador escolhido pelo implementador do dispositivo para se referir a uma versão específica, em formato legível por humanos. Esse campo pode ser o mesmo que Android.OS.Build.version.incremental, mas deve ser um valor suficientemente significativo para os usuários finais distinguirem entre as compilações de software. O valor deste campo deve ser codificável como ASCII de 7 bits e corresponder à expressão regular ^[a-zA-Z0-9._-]+$ .
FABRICANTE	O nome comercial do fabricante de equipamentos originais (OEM) do produto. Não há requisitos no formato específico deste campo, exceto que ele não deve ser nulo ou a string vazia (""). Este campo não deve mudar durante a vida útil do produto.
Soc_Manufacturer	O comércio de nome do fabricante do sistema primário no chip (SOC) usado no produto. Os dispositivos com o mesmo fabricante do SOC devem usar o mesmo valor constante. Por favor, peça ao fabricante do SOC a constante correta para usar. O valor deste campo deve ser codificável como ASCII de 7 bits, deve corresponder à expressão regular ^([0-9A-Za-z ]+) , não deve iniciar ou terminar com espaço em branco e não deve ser igual a "desconhecido" . Este campo não deve mudar durante a vida útil do produto.
Modelo Soc	O nome do modelo do sistema primário em um chip (SOC) usado no produto. Os dispositivos com o mesmo modelo SOC devem usar o mesmo valor constante. Por favor, peça ao fabricante do SOC a constante correta para usar. O valor deste campo deve ser codificável como ASCII de 7 bits e corresponder à expressão regular ^([0-9A-Za-z . /+-]+)$ , não deve iniciar ou terminar com espaço em branco e não deve ser igual para "desconhecido". Este campo não deve mudar durante a vida útil do produto.
MODELO	Um valor escolhido pelo implementador do dispositivo que contém o nome do dispositivo como conhecido pelo usuário final. Deve ser o mesmo nome sob o qual o dispositivo é comercializado e vendido para usuários finais. Não há requisitos no formato específico deste campo, exceto que ele não deve ser nulo ou a string vazia (""). Este campo não deve mudar durante a vida útil do produto.
PRODUTOS	Um valor escolhido pelo implementador do dispositivo que contém o nome de desenvolvimento ou o nome do código do produto específico (SKU) que deve ser exclusivo dentro da mesma marca. Deve ser legível por humanos, mas não se destina necessariamente à exibição dos usuários finais. O valor desse campo deve ser codificável como ASCII de 7 bits e corresponder à expressão regular ^[a-zA-Z0-9_-]+$ . Este nome do produto não deve mudar durante a vida útil do produto.
ODM SKU	Um valor opcional escolhido pelo implementador do dispositivo que contém SKU (unidade de manutenção de estoque) usado para rastrear configurações específicas do dispositivo, por exemplo, quaisquer periféricos incluídos no dispositivo quando vendidos. O valor deste campo deve ser codificável como ASCII de 7 bits e corresponder à expressão regular "[0-9a-za-z.,-])"
SERIAL	Deve retornar "desconhecido".
TAG	Uma lista separada por vírgula de tags escolhida pelo implementador do dispositivo que distingue ainda mais a compilação. As tags devem ser codificáveis ​​como ASCII de 7 bits e corresponder à expressão regular ^[a-zA-Z0-9._-]+ deve ter um dos valores correspondentes às três configurações típicas de assinatura da plataforma Android: Release-Keys, Keys dev e teclas de teste.
TEMPO	Um valor representando o carimbo de data / hora de quando a construção ocorreu.
TIPO	Um valor escolhido pelo implementador do dispositivo especificando a configuração de tempo de execução da compilação. Este campo deve ter um dos valores correspondentes às três configurações típicas de tempo de execução do Android: Usuário, UserDebug ou ENG.
DO UTILIZADOR	Um nome ou ID de usuário do usuário (ou usuário automatizado) que gerou a compilação. Não há requisitos no formato específico deste campo, exceto que ele não deve ser nulo ou a string vazia ("").
Segurança_patch	Um valor indicando o nível do patch de segurança de uma compilação. Deve significar que a construção não é de forma alguma vulnerável a nenhum dos problemas descritos através do Boletim de Segurança Pública Android designada. Ele deve estar no formato [AAA-MM-DD], correspondendo a uma string definida documentada no Boletim de Segurança Pública do Android ou no Android Security Advisory , por exemplo "2015-11-01".
OS base	Um valor que representa o parâmetro de impressão digital da construção que, de outra forma, é idêntico a essa construção, exceto pelos patches fornecidos no Boletim de Segurança Pública do Android. Ele deve relatar o valor correto e, se essa compilação não existir, relate uma string vazia ("").
Bootloader	Um valor escolhido pelo implementador do dispositivo, identificando a versão específica do carregador de inicialização usada no dispositivo, em formato legível por humanos. O valor desse campo deve ser codificável como ASCII de 7 bits e corresponder à expressão regular ^[a-zA-Z0-9. -]+$ .
getRadioversion ()	Deve (ser ou retornar) um valor escolhido pelo implementador do dispositivo, identificando a versão interna de rádio/modem específica usada no dispositivo, em formato legível por humanos. Se um dispositivo não tiver nenhum rádio/modem interno, ele deverá retornar nulo. O valor desse campo deve ser codificável como ASCII de 7 bits e corresponder à expressão regular ^[a-zA-Z0-9._-,]+$ .
getSerial ()	Deve (ser ou retornar) um número de série de hardware, que deve estar disponível e exclusivo entre os dispositivos com o mesmo modelo e fabricante. O valor deste campo deve ser codificável como ASCII de 7 bits e corresponder à expressão regular ^[a-zA-Z0-9]+$ .

3.2.3. Compatibilidade de intenção

3.2.3.1. Intenções de aplicação comuns

As intenções do Android permitem que os componentes do aplicativo solicitem funcionalidade de outros componentes do Android. O projeto Android Upstream inclui uma lista de aplicativos que implementam vários padrões de intenção para executar ações comuns.

Implementações de dispositivos:

• [C-SR-1] são fortemente recomendados para pré-carregar um ou mais aplicativos ou componentes de serviço com um manipulador de intenções, para todos os padrões de filtro de intenção pública definidos pelas seguintes intenções de aplicação listadas aqui e fornecem cumprimento, ou seja, atende à expectativa do desenvolvedor para estes intenções de aplicação comuns conforme descrito no SDK.

Consulte a Seção 2 para obter intenções de aplicação obrigatórias para cada tipo de dispositivo.

3.2.3.2. Resolução de intenções

• [C-0-1] Como o Android é uma plataforma extensível, as implementações do dispositivo devem permitir que cada padrão de intenção seja referenciado na Seção 3.2.3.1 , exceto para configurações, seja substituído por aplicativos de terceiros. A implementação de código aberto Android upstream permite isso por padrão.

• [C-0-2] Os implementadores de dispositivos não devem anexar privilégios especiais ao uso de aplicativos do sistema desses padrões de intenção ou impedir que aplicativos de terceiros se vinculem e assumam o controle desses padrões. Essa proibição inclui especificamente, mas não se limita a desativar a interface do usuário "Chooser" que permite ao usuário selecionar entre vários aplicativos que lidam com o mesmo padrão de intenção.

• [C-0-3] As implementações do dispositivo devem fornecer uma interface de usuário para os usuários modificarem a atividade padrão para as intenções.

• No entanto, as implementações de dispositivos podem fornecer atividades padrão para padrões de URI específicos (por exemplo, http://play.google.com) quando a atividade padrão fornece um atributo mais específico para o URI de dados. Por exemplo, um padrão de filtro de intenção que especifica os dados URI "http://www.android.com" é mais específico do que o padrão principal do navegador para "http: //".

O Android também inclui um mecanismo para os aplicativos de terceiros declararem um comportamento de vinculação de aplicativos padrão autorizada para certos tipos de intenções de URI da Web. Quando essas declarações autorizadas são definidas nos padrões de filtro de intenção de um aplicativo, implementações de dispositivos:

• [C-0-4] deve tentar validar qualquer filtro de intenção executando as etapas de validação definidas na especificação de links de ativos digitais, conforme implementado pelo gerenciador de pacotes no projeto de código aberto Android a montante.
• [C-0-5] deve tentar a validação dos filtros de intenção durante a instalação do aplicativo e definir todos os filtros de intenção de URI validados com sucesso como manipuladores de aplicativos padrão para seus URIs.
• Pode definir filtros de intenção de URI específicos como manipuladores de aplicativos padrão para seus URIs, se forem verificados com sucesso, mas outros filtros de URI candidatos falham. Se uma implementação de dispositivo fizer isso, ele deve fornecer ao usuário o padrão apropriado do padrão URI substituir no menu Configurações.
• Deve fornecer ao usuário controles por aplicativos por aplicativo por aplicativo nas configurações da seguinte forma:
  • [C-0-6] O usuário deve ser capaz de substituir holisticamente o aplicativo padrão vincula o comportamento de um aplicativo: sempre aberto, sempre pergunte ou nunca aberto, que deve se aplicar a todos os filtros de intenção de URI candidatos igualmente.
  • [C-0-7] O usuário deve poder ver uma lista dos filtros de intenção de URI candidatos.
  • A implementação do dispositivo pode fornecer ao usuário a capacidade de substituir os filtros de intenção de URI candidatos específicos que foram verificados com sucesso, com base no filtro por intenção.
  • [C-0-8] A implementação do dispositivo deve fornecer aos usuários a capacidade de visualizar e substituir os filtros de intenção de URI candidatos específicos se a implementação do dispositivo permite que alguns filtros de intenção de URI candidatos tenham sucesso na verificação, enquanto outros podem falhar.

3.2.3.3. Namespaces de intenção

• [C-0-1] As implementações do dispositivo não devem incluir nenhum componente Android que honre qualquer nova intenção ou padrões de intenção de transmissão usando uma ação, categoria ou outra string de chave no Android.* Ou com.android.* Namespace.
• [C-0-2] Os implementadores de dispositivos não devem incluir nenhum componente Android que honre qualquer nova intenção ou padrões de intenção de transmissão usando uma ação, categoria ou outra string de chave em um espaço de pacotes pertencente a outra organização.
• [C-0-3] Os implementadores do dispositivo não devem alterar ou estender nenhum dos padrões de intenção listados na Seção 3.2.3.1 .
• As implementações de dispositivos podem incluir padrões de intenção usando espaço para nome de forma clara e obviamente associada à sua própria organização. Essa proibição é análoga à especificada para as classes de idiomas Java na Seção 3.6 .

3.2.3.4. Intenções de transmissão

Os aplicativos de terceiros dependem da plataforma para transmitir certos intenções de notificá-los sobre alterações no ambiente de hardware ou software.

Implementações de dispositivos:

• [C-0-1] deve transmitir as intenções de transmissão pública listadas aqui em resposta aos eventos apropriados do sistema, conforme descrito na documentação do SDK. Observe que esse requisito não está conflitante com a Seção 3.5, pois a limitação para aplicações em segundo plano também é descrita na documentação do SDK. Além disso, certas intenções de transmissão estão condicionais no suporte ao hardware, se o dispositivo suportar o hardware necessário, eles devem transmitir as intenções e fornecer o comportamento em linha com a documentação do SDK.

3.2.3.5. Intenções de aplicação condicional

O Android inclui configurações que fornecem aos usuários uma maneira fácil de selecionar seus aplicativos padrão, por exemplo, para tela inicial ou SMS.

Onde faz sentido, as implementações do dispositivo devem fornecer um menu de configurações semelhantes e ser compatíveis com o padrão de filtro de intenção e os métodos de API descritos na documentação do SDK como abaixo.

Se as implementações do dispositivo relatar android.software.home_screen , elas:

• [C-1-1] deve homenagear o android.settings.HOME_SETTINGS com a intenção de mostrar um menu de configurações de aplicativo padrão para a tela inicial.

Se as implementações do dispositivo relatar android.hardware.telephony.calling , elas:

• [C-2-1] deve fornecer um menu de configurações que chamará o android.provider.Telephony.ACTION_CHANGE_DEFAULT intenção de mostrar uma caixa de diálogo para alterar o aplicativo SMS padrão.

• [C-2-2] deve homenagear o android.telecom.action.CHANGE_DEFAULT_DIALER Intenção de mostrar uma caixa de diálogo para permitir que o usuário altere o aplicativo de telefone padrão.

  • Deve usar a interface do usuário do aplicativo de telefone padrão selecionada pelo usuário para obter chamadas de entrada e saída, exceto para chamadas de emergência, o que usaria o aplicativo de telefone pré-instalado.

• [C-2-3] deve homenagear o Android.telecom.action.change_phone_accounts com a intenção de fornecer aos usuários possibilidades para configurar os ConnectionServices associados ao PhoneAccounts , bem como a um telefone padrão que o provedor de serviços de telecomunicações usará para fazer chamadas de saída. A implementação do AOSP atende a esse requisito, incluindo um menu "Opção de contas de chamadas" no menu de configurações "chamadas".

• [C-2-4] deve permitir android.telecom.CallRedirectionService para um aplicativo que detém a função android.app.role.CALL_REDIRECTION .

• [C-2-5] deve fornecer ao usuário a possibilidade de escolher um aplicativo que possua a função android.app.role.CALL_REDIRECTION .

• [C-2-6] deve homenagear o Android.intent.action.sendto e Android.intent.action.view intenos e fornecer uma atividade para enviar/exibir mensagens SMS.

• [C-sr-1] são fortemente recomendados para homenagear android.intent.action.answer , android.intent.action.call , android.intent.action.call_button , android.intent.action.view & android.intent.action. Disque as intenções com um aplicativo de discador pré -carregado que pode lidar com essas intenções e fornecer atendimento conforme descrito no SDK.

Se as implementações do dispositivo relatar android.hardware.nfc.hce , elas:

• [C-3-1] deve homenagear o Android.settings.nfc_payment_settings com a intenção de mostrar um menu de configurações de aplicativo padrão para pagamento sem contato.
• [C-3-2] deve homenagear android.nfc.cardemulation.action.action_change_default Intenção de mostrar uma atividade que abre uma caixa de diálogo para solicitar ao usuário que altere o serviço de emulação padrão do cartão para uma determinada categoria, conforme descrito no SDK.

Se as implementações do dispositivo relatar android.hardware.nfc , elas:

• [C-4-1] deve honrar esses intenções Android.nfc.action.ndef_discovered , Android.nfc.action.tag_discovered & android.nfc.action.tech_discwoved , para mostrar uma atividade que atende às expectativas dos desenvolvedores para essas intendas, conforme descrito no título Sdk.

Se as implementações do dispositivo relatar android.hardware.bluetooth , elas:

• [C-5-1] deve homenagear o 'Android.bluetooth.adapter.action.request_enable' intenção e mostrar uma atividade do sistema para permitir que o usuário ligue o Bluetooth.
• [C-5-2] deve homenagear o 'Android.bluetooth.adapter.action.request_discoverable' e mostrar uma atividade do sistema que solicita o modo descoberta.

Se as implementações do dispositivo suportarem o recurso DND, elas:

• [C-6-1] deve implementar uma atividade que responderia à intenção ACTION_NOTIFICATION_POLICY_ACCESS_SETTINGS , que, para implementações com UI_Mode_Type_Normal, deve ser uma atividade em que o usuário possa conceder ou negar o acesso ao aplicativo às configurações de política do DND.

Se as implementações do dispositivo permitirem que os usuários usem métodos de entrada de terceiros no dispositivo, eles:

• [C-7-1] deve fornecer um mecanismo acessível ao usuário para adicionar e configurar métodos de entrada de terceiros em resposta ao android.settings.INPUT_METHOD_SETTINGS Intent.

Se as implementações do dispositivo suportarem serviços de acessibilidade de terceiros, eles:

• [C-8-1] deve homenagear o android.settings.ACCESSIBILITY_SETTINGS Intenções de fornecer um mecanismo acessível pelo usuário para permitir e desativar os serviços de acessibilidade de terceiros juntamente com os serviços de acessibilidade pré-carregados.

Se as implementações do dispositivo incluirem suporte para Wi-Fi Easy Connect e expor a funcionalidade a aplicativos de terceiros, eles:

• [C-9-1] deve implementar as configurações#action_process_wifi_easy_connect_uri Intent APIs, conforme descrito na documentação SDK.

Se as implementações do dispositivo fornecerem o modo de economia de dados, elas: * [C-10-1] deverão fornecer uma interface do usuário nas configurações, que lida com o Settings.ACTION_IGNORE_BACKGROUND_DATA_RESTRICTIONS_SETTINGS intenção, permitindo que os usuários adicionem aplicativos ou remova os aplicativos da lista de permissões.

Se as implementações do dispositivo não fornecerem o modo de economia de dados, elas:

• [C-11-1] deve ter uma atividade que lida com o Settings.ACTION_IGNORE_BACKGROUND_DATA_RESTRICTIONS_SETTINGS Intent, mas pode implementá-lo como um não-OP.

Se as implementações do dispositivo declararem suporte para a câmera via android.hardware.camera.any , eles:

• [C-12-3] deve lidar e deve permitir apenas aplicativos Android pré-instalados para lidar com as seguintes intenções MediaStore.ACTION_IMAGE_CAPTURE , MediaStore.ACTION_IMAGE_CAPTURE_SECURE e MediaStore.ACTION_VIDEO_CAPTURE , conforme descrito no documento SDK .

Se as implementações do dispositivo relatar android.software.device_admin , elas:

• [C-13-1] deve honrar o Intent android.app.action.ADD_DEVICE_ADMIN para invocar uma interface do usuário para levar o usuário através da adição do administrador do dispositivo ao sistema (ou permitindo que eles o rejeitem).

• [C-13-2] deve homenagear os intenções Android.app.action.provision_managed_profile , android.app.action.set_new_parent_profile_password , android.app.action.set_new_password & Android.Aption.Start_ENCRYPtion e ter uma atividade para fornecer a cumprir Essas intenções, conforme descrito no SDK aqui .

Se as implementações do dispositivo declararem o sinalizador android.software.autofill , eles:

• [C-14-1] deve implementar totalmente as APIs AutofillService e AutofillManager e honrar o Android.Settings.Request_Set_Autofill_Service Intent de mostrar um menu Configurações de aplicativos padrão para ativar e desativar o Autofille e alterar o serviço de preenchimento automático padrão para o usuário.

Se as implementações do dispositivo incluirem um aplicativo pré-instalado ou desejar permitir que aplicativos de terceiros acessem as estatísticas de uso, eles:

• [C-SR-2] são fortemente recomendados fornecem mecanismo acessível ao usuário para conceder ou revogar o acesso às estatísticas de uso em resposta ao Android.Settings.action_usage_access_settings Intenção para aplicativos que declaram a permissão android.permission.PACKAGE_USAGE_STATS .

Se as implementações do dispositivo pretendem proibir quaisquer aplicativos, incluindo aplicativos pré-instalados, desde o acesso das estatísticas de uso, eles:

• [C-15-1] ainda deve ter uma atividade que lida com o Android.Settings.action_usage_access_settings Intent Pattern, mas deve implementá-lo como um não-operatório, ou seja, ter um comportamento equivalente como quando o usuário é recusado para acesso.

Se as implementações do dispositivo links de superfície para as atividades especificadas pelo AutoFillService_PasswordSativity em configurações ou links para senhas de usuário através de um mecanismo semelhante, eles: eles:

• [C-16-1] deve superfície tais links para todos os serviços de preenchimento automático instalados.

Se as implementações do dispositivo suportarem o VoiceInteractionService e tiver mais de um aplicativo usando esta API instalada por vez, elas:

• [C-18-1] deve homenagear o android.settings.ACTION_VOICE_INPUT_SETTINGS com a intenção de mostrar um menu de configurações de aplicativo padrão para entrada e assistência de voz.

Se as implementações do dispositivo relatarem o recurso android.hardware.audio.output , elas:

• [C-sr-3] são fortemente recomendados para homenagear android.intent.action.tts_service, android.speech.tts.engine.install_tts_data & android.speech.tts.engine.get_sample_text Os intenções têm uma atividade para fornecer contenção para esses intenentos como como descrito no SDK aqui .

O Android inclui suporte para protetores interativos, anteriormente chamados de sonhos. Os poupadores de tela permitem que os usuários interajam com os aplicativos quando um dispositivo conectado a uma fonte de energia está ocioso ou encaixado em uma doca de mesa. Implementações de dispositivos:

• Deve incluir suporte para poupadores de tela e fornecer uma opção de configurações para os usuários configurarem os poupadores de tela em resposta ao android.settings.DREAM_SETTINGS Intent.

Se implementações de dispositivos relatam android.hardware.nfc.uicc ou android.hardware.nfc.ese , eles:

• [C-19-1] deve implementar a API NFCADAPTER.ACTION_TRANSACTION_DETETED INTENT (AS "EVT_TRANSACTION" definida pelas especificações técnicas da Associação GSM TS.26-Requisitos do aparelho da NFC) .

3.2.4. Atividades em displays secundários/múltiplos

Se as implementações do dispositivo permitirem ao lançar atividades normais do Android em mais de uma tela, elas:

• [C-1-1] deve definir o android.software.activities_on_secondary_displays com o sinalizador.
• [C-1-2] deve garantir a compatibilidade da API semelhante a uma atividade em execução na tela principal.
• [C-1-3] deve atingir a nova atividade na mesma tela que a atividade que a lançou, quando a nova atividade é lançada sem especificar uma exibição de destino através da API ActivityOptions.setLaunchDisplayId() .
• [C-1-4] deve destruir todas as atividades, quando uma exibição com o sinalizador Display.FLAG_PRIVATE é removida.
• [C-1-5] deve ocultar com segurança o conteúdo em todas as telas quando o dispositivo é bloqueado com uma tela de bloqueio segura, a menos que o aplicativo opte para aparecer na tela de bloqueio usando a API Activity#setShowWhenLocked() .
• Deve ter android.content.res.Configuration , que corresponde a essa exibição para ser exibida, opere corretamente e mantenha a compatibilidade se uma atividade for iniciada na tela secundária.

Se as implementações do dispositivo permitirem o lançamento de atividades normais do Android em displays secundários e uma tela secundária, o Android.View.Display.Flag_Private Sinalizador:

• [C-3-1] Somente o proprietário daquela exibição, sistema e atividades que já estão nessa exibição devem ser capazes de iniciá-lo. Todos podem ser lançados em uma tela que tem Android.View.Display.Flag_Public Flag.

3.3. Compatibilidade da API nativa

A compatibilidade com o código nativo é desafiador. Por esse motivo, os implementadores de dispositivos são:

• [C-SR-1] Recomendado fortemente para usar as implementações das bibliotecas listadas abaixo do projeto de código aberto Android a montante.

3.3.1. Interfaces binárias do aplicativo

O Dalvik Bytecode gerenciado pode ser inserido para o código nativo fornecido no arquivo .apk do aplicativo como um arquivo ELF .so compilado para a arquitetura de hardware de dispositivo apropriada. Como o código nativo é altamente dependente da tecnologia do processador subjacente, o Android define uma série de interfaces binárias de aplicativos (ABIS) no Android NDK.

Implementações de dispositivos:

• [C-0-1] deve ser compatível com um ou mais Android NDK ABIS definido.
• [C-0-2] deve incluir o suporte para o código em execução no ambiente gerenciado para chamar o código nativo, usando a semântica padrão da interface nativa Java (JNI).
• [C-0-3] deve ser compatível com a origem (ou seja, compatível com cabeçalho) e compatível com o binário (para o ABI) com cada biblioteca necessária na lista abaixo.
• [C-0-5] deve relatar com precisão a interface binária de aplicativos nativos (ABI) suportada pelo dispositivo, via android.os.Build.SUPPORTED_ABIS , android.os.Build.SUPPORTED_32_BIT_ABIS e android.os.osetr.build.support_642_bit_bis e android.os.Build.SUPPORTED_64_BIT_ABIS , cada uma com uma lista separada de vírgula de ABIS ordenada da mais à menos preferida.

Inicie novos requisitos para 15 (AOSP Experimental)

[C-0-6] (26 de fevereiro de 2024 Visualização)

• [C-0-6] deve relatar, através dos parâmetros acima, um subconjunto da lista a seguir de ABIS e não deve relatar nenhum ABI não na lista.
  • armeabi (não mais suportado como alvo pelo NDK)
  • armeabi-v7a
  • arm64-v8a
  • x86
  • x86-64
  • riscv64

Acabar com novos requisitos

• [C-0-7] deve fabricar todas as seguintes bibliotecas, fornecendo APIs nativas, disponíveis para aplicativos que incluem código nativo:

  • libaaudio.so (suporte de áudio nativo de Aaudio)
  • libamidi.so (suporte nativo do MIDI, se o recurso android.software.midi for reivindicado conforme descrito na Seção 5.9)
  • Libandroid.so (suporte nativo da atividade Android)
  • LIBC (biblioteca C)
  • libcamera2ndk.so
  • libdl (ligante dinâmico)
  • libegl.so (gerenciamento de superfície nativo do OpenGL)
  • libglesv1_cm.so (open es 1.x)
  • libglesv2.so (openg es 2.0)
  • libglesv3.so (openg es 3.x)
  • libicui18n.so
  • libicuuc.so
  • libjnigraphics.so
  • Liblog (registro do Android)
  • libmediandk.so (suporte de APIs de mídia nativa)
  • LibM (Biblioteca de Matemática)
  • libneuralNetworks.so (API de redes neurais)
  • libopenmaxal.so (suporte OpenMax AL 1.0.1)
  • libonsles.so (opensl es 1.0.1 suporte de áudio)
  • LIBRS.SO
  • libstdc ++ (suporte mínimo para C ++)
  • libvulkan.so (vulkan)
  • Libz (compressão Zlib)
  • Interface JNI

• [C-0-8] não deve adicionar ou remover as funções públicas para as bibliotecas nativas listadas acima.

• [C-0-9] deve listar bibliotecas não AOSP adicionais expostas diretamente a aplicativos de terceiros em /vendor/etc/public.libraries.txt .

• [C-0-10] não deve expor outras bibliotecas nativas, implementadas e fornecidas no AOSP como bibliotecas de sistemas, a aplicativos de terceiros direcionados ao nível 24 ou superior da API à medida que são reservados.

• [C-0-11] deve exportar todos os símbolos da função OpenG ES 3.1 e Android Extension Pack , conforme definido no NDK, através da biblioteca libGLESv3.so . Observe que, embora todos os símbolos devam estar presentes, a Seção 7.1.4.1 descreve em mais detalhes os requisitos para quando a implementação completa de cada funções correspondentes forem esperadas.

• [C-0-12] deve exportar símbolos de função para os símbolos da função Core Vulkan 1.1, bem como o VK_KHR_surface , VK_KHR_android_surface , VK_KHR_swapchain , VK_KHR_maintenance1 e VK_KHR_get_physical_device_properties2 libvulkan.so Observe que, embora todos os símbolos devam estar presentes, a Seção 7.1.4.2 descreve em mais detalhes os requisitos para quando a implementação completa de cada funções correspondentes forem esperadas.

• Deve ser construído usando o código -fonte e os arquivos de cabeçalho disponíveis no projeto de código aberto Android a montante.

Observe que os lançamentos futuros do Android podem introduzir suporte para ABIs adicionais.

3.3.2. Compatibilidade de código nativo de braço de 32 bits

Se as implementações do dispositivo relatarem o suporte do armeabi Abi, elas:

• [C-3-1] também deve apoiar armeabi-v7a e relatar seu suporte, pois armeabi é apenas para compatibilidade com versões anteriores com aplicativos mais antigos.

Se as implementações do dispositivo relatarem o suporte do armeabi-v7a ABI, para aplicativos usando este ABI, eles:

• [C-2-1] deve incluir as seguintes linhas em /proc/cpuinfo e não deve alterar os valores no mesmo dispositivo, mesmo quando são lidos por outros ABIS.

  • Features: seguido por uma lista de qualquer recurso opcional da CPU ARMV7 suportado pelo dispositivo.
  • CPU architecture: , seguida por um número inteiro que descreve a arquitetura de braço mais alta suportada do dispositivo (por exemplo, "8" para dispositivos ARMV8).

• [C-2-2] deve sempre manter as seguintes operações disponíveis, mesmo no caso em que o ABI é implementado em uma arquitetura ARMV8, seja por meio de suporte nativo da CPU ou por meio de emulação de software:

  • Instruções SWP e SWPB.
  • Operações de barreira CP15ISB, CP15DSB e CP15DMB.

• [C-2-3] deve incluir suporte para a extensão Avançada SIMD (também conhecida como neon).

3.4. Compatibilidade da Web

3.4.1. Compatibilidade da WebView

Se as implementações do dispositivo fornecerem uma implementação completa da API android.webkit.Webview , eles:

• [C-1-1] deve relatar android.software.webview .
• [C-1-2] deve usar o projeto de cromo do projeto Android Android Android no ramo Android 15 para a implementação da API android.webkit.WebView .

• [C-1-3] A sequência do agente do usuário relatada pelo WebView deve estar neste formato:

  Mozilla/5.0 (Linux; Android $ (versão); [$ (Model)] [Build/$ (Build)]; WV) Applewebkit/537.36 (KHTML, como Gecko) Versão/4.0 $ (Chromium_ver) Safari/537.36)

  • O valor da string $ (versão) deve ser o mesmo que o valor para android.os.build.version.release.
  • A sequência $ (modelo) pode estar vazia, mas se não estiver vazia, deve ter o mesmo valor que Android.OS.Build.model.
  • "Build/$ (Build)" pode ser omitido, mas se estiver presente, a sequência $ (Build) deve ser a mesma que o valor para Android.OS.Build.id.
  • O valor da string $ (Chromium_Ver) deve ser a versão do Chromium no projeto de código aberto Android a montante.
  • As implementações do dispositivo podem omitir o celular na sequência do agente do usuário.

• O componente da WebView deve incluir o suporte para o maior número possível de recursos HTML5 e, se suportar o recurso, deverá estar em conformidade com a especificação HTML5 .

• [C-1-4] deve tornar o conteúdo fornecido ou o conteúdo remoto de URL em um processo que é distinto do aplicativo que instancia a WebView. Especificamente, o processo de renderizador separado deve manter um privilégio mais baixo, executado como um ID de usuário separado, não ter acesso ao diretório de dados do aplicativo, não ter acesso direto à rede e só tem acesso aos serviços de sistema mínimo e exigido pelo Binder. A implementação do AOSP do WebView atende a esse requisito.

Observe que, se as implementações do dispositivo forem de 32 bits ou declararem o sinalizador de recursos android.hardware.ram.low , elas serão isentas do C-1-3.

3.4.2. Compatibilidade do navegador

Se as implementações do dispositivo incluirem um aplicativo de navegador independente para navegação na web geral, elas:

• [C-1-1] deve apoiar cada uma dessas APIs associadas ao HTML5:
  • Operação de cache de aplicativos/offline
  • tag <vídeo>
  • geolocalização
• [C-1-2] deve suportar a API HTML5/W3C WebStorage e deve suportar a API HTML5/W3C IndexedDB . Observe que, como os órgãos de padrões de desenvolvimento da Web estão em transição para favorecer o indexedDB em vez de WebStorage, o IndexedDB deve se tornar um componente necessário em uma versão futura do Android.
• Pode enviar uma sequência de agente de usuário personalizada no aplicativo de navegador independente.
• Deve implementar o suporte o máximo possível do HTML5 no aplicativo de navegador independente (seja com base no aplicativo do navegador Webkit upstream ou em uma substituição de terceiros).

No entanto, se as implementações do dispositivo não incluirem um aplicativo de navegador independente, eles:

• [C-2-1] ainda deve apoiar os padrões de intenção pública, conforme descrito na Seção 3.2.3.1 .

3.5. Compatibilidade comportamental da API

Implementações de dispositivos:

• [C-0-9] deve garantir que a compatibilidade comportamental da API seja aplicada a todos os aplicativos instalados, a menos que estejam restritos conforme descrito na Seção 3.5.1 .
• [C-0-10] não deve implementar a abordagem da lista de permissões que garante a compatibilidade comportamental da API apenas para aplicativos selecionados pelos implementadores de dispositivos.

Os comportamentos de cada um dos tipos de API (gerenciados, macios, nativos e web) devem ser consistentes com a implementação preferida do projeto de código aberto Android a montante. Algumas áreas específicas de compatibilidade são:

• [C-0-1] Os dispositivos não devem alterar o comportamento ou a semântica de uma intenção padrão.
• [C-0-2] Os dispositivos não devem alterar o ciclo de vida ou a semântica do ciclo de vida de um tipo específico de componente do sistema (como serviço, atividade, conteúdo provider etc.).
• Os dispositivos [C-0-3] não devem alterar a semântica de uma permissão padrão.
• Os dispositivos não devem alterar as limitações aplicadas nos aplicativos em segundo plano. Mais especificamente, para aplicativos de fundo:
  • [C-0-4] Eles devem parar de executar retornos de chamada registrados pelo aplicativo para receber saídas do GnssMeasurement e GnssNavigationMessage .
  • [C-0-5] Eles devem limitar a frequência de atualizações fornecidas ao aplicativo através da classe API LocationManager ou do método WifiManager.startScan() .
  • [C-0-6] Se o aplicativo estiver visando o nível 25 ou superior da API, eles não deverão permitir registrar receptores de transmissão para as transmissões implícitas de intenções padrão do Android no manifesto do aplicativo, a menos que a intenção de transmissão exija uma "signature" ou "signatureOrSystem" protectionLevel Permission ou estão na lista de isenção .
  • [C-0-7] Se o aplicativo estiver direcionado ao nível 25 ou superior da API, eles deverão interromper os serviços de fundo do aplicativo, como se o aplicativo tivesse chamado o método de ' stopSelf() , a menos que o aplicativo seja colocado em uma lista de permissões temporárias Para lidar com uma tarefa visível para o usuário.
  • [C-0-8] Se o aplicativo estiver direcionado ao nível 25 ou superior da API, eles deverão liberar os wakelocks que o aplicativo mantém.
• [C-0-11] Os dispositivos devem devolver os seguintes provedores de segurança como os sete primeiros valores de matriz do método Security.getProviders() , na ordem dada e com os nomes fornecidos (conforme retornado pelo Provider.getName() ) e classes , a menos que o aplicativo tenha modificado a lista via insertProviderAt() ou removeProvider() . Os dispositivos podem retornar fornecedores adicionais após a lista especificada de provedores abaixo.
  1. Androidnssp - android.security.net.config.NetworkSecurityConfigProvider
  2. AndroidoPenssl - com.android.org.conscrypt.OpenSSLProvider
  3. CertPathProvider - sun.security.provider.CertPathProvider
  4. AndroidKeyStoreBcWorkAlound - android.security.keystore.AndroidKeyStoreBCWorkaroundProvider
  5. BC - com.android.org.bouncycastle.jce.provider.BouncyCastleProvider
  6. HarmonyJSse - com.android.org.conscrypt.JSSEProvider
  7. AndroidKeystore - android.security.keystore.AndroidKeyStoreProvider

A lista acima não é abrangente. O conjunto de testes de compatibilidade (CTS) testa partes significativas da plataforma para compatibilidade comportamental, mas não todas. É de responsabilidade do implementador garantir a compatibilidade comportamental com o projeto de código aberto do Android. Por esse motivo, os implementadores do dispositivo devem usar o código-fonte disponível através do projeto de código aberto Android sempre que possível, em vez de reimplementar partes significativas do sistema.

3.5.1. Restrição do aplicativo

Se as implementações do dispositivo implementarem um mecanismo proprietário para restringir os aplicativos (por exemplo, alteração ou restrição de comportamentos de API descritos no SDK) e esse mecanismo é mais restritivo do que o balde de espera de aplicativo restrito , eles:

• [C-1-1] deve permitir que o usuário veja a lista de aplicativos restritos.
• [C-1-2] Deve fornecer acessórios para o usuário para ligar / desligar todas essas restrições proprietárias em cada aplicativo.

• [C-1-3] não deve aplicar automaticamente essas restrições proprietárias sem evidências de mau comportamento da saúde do sistema, mas pode aplicar as restrições aos aplicativos após a detecção de um mau comportamento de saúde do sistema, como Wakelocks, de longa data e outros critérios. Os critérios podem ser determinados pelos implementadores do dispositivo, mas devem estar relacionados ao impacto do aplicativo na saúde do sistema. Outros critérios que não estão puramente relacionados à saúde do sistema, como a falta de popularidade do aplicativo no mercado, não devem ser usados ​​como critérios.

• [C-1-4] não deve aplicar automaticamente essas restrições proprietárias para aplicativos quando um usuário desativou as restrições de aplicativos manualmente e pode sugerir que o usuário aplique essas restrições proprietárias.

• [C-1-5] deve informar os usuários se essas restrições proprietárias forem aplicadas a um aplicativo automaticamente. Essas informações devem ser fornecidas no período de 24 horas, precedindo a aplicação dessas restrições proprietárias.

• [C-1-6] deve retornar true para o método de atividades

• [C-1-7] não deve restringir o aplicativo de primeiro plano superior que é explicitamente usado pelo usuário.

• [C-1-8] deve suspender essas restrições proprietárias em um aplicativo sempre que um usuário começar a usar explicitamente o aplicativo, tornando-o o aplicativo de primeiro plano superior.

• [C-1-10] deve fornecer um documento ou site público e claro que descreva como as restrições proprietárias são aplicadas. Este documento ou site deve ser vinculado a partir dos documentos Android SDK e deve incluir:

  • Acionando condições para restrições proprietárias.
  • O que e como um aplicativo pode ser restrito.
  • Como um aplicativo pode ser isento de tais restrições.
  • Como um aplicativo pode solicitar uma isenção de restrições proprietárias, se suportar uma isenção para aplicativos que o usuário possa instalar.

Se um aplicativo for pré-instalado no dispositivo e nunca foi explicitamente usado por um usuário por mais de 30 dias, [C-1-3] [C-1-5] estará isento.

Se as implementações do dispositivo estenderem as restrições de aplicativos que são implementadas no AOSP, elas:

• [C-2-1] deve seguir a implementação descrita neste documento .

3.5.2. Hibernação do aplicativo

Se as implementações do dispositivo incluirem hibernação de aplicativos incluídos no AOSP ou estender o recurso incluído no AOSP, eles: eles:

• [C-1-1] deve atender a todos os requisitos na Seção 3.5.1, exceto para [C-1-6] e [C-1-3].
• [C-1-2] deve aplicar apenas a restrição no aplicativo para um usuário quando houver evidências de que o usuário não use o aplicativo por algum período de tempo. Essa duração é fortemente recomendada como um mês ou mais. O uso deve ser definido pela interação explícita do usuário por meio da API USAGESTATS#getLastTimeVisible () ou qualquer coisa que faria um aplicativo deixar o estado parado de força, incluindo ligações de serviços, ligações de provedores de conteúdo, transmissões explícitas, etc., que serão rastreadas por uma nova API USAGESTATS#getLastTimeanyComponentUSEd ().
• [C-1-3] deve aplicar apenas restrições que afetam todos os usuários do dispositivo quando há evidências de que o pacote não foi usado por nenhum usuário por algum período de tempo. Essa duração é fortemente recomendada como um mês ou mais.
• [C-1-4] não deve renderizar o aplicativo incapaz de responder às intenções de atividade, ligações de serviços, solicitações de provedores de conteúdo ou transmissões explícitas.

A hibernação do aplicativo no AOSP atende aos requisitos acima.

3.6. Namespaces de API

O Android segue as convenções de namespace de pacote e classe definidas pela linguagem de programação Java. Para garantir a compatibilidade com aplicativos de terceiros, os implementadores de dispositivos não devem fazer modificações proibidas (veja abaixo) para estes espaços de nome de pacotes:

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

Isto é, eles:

• [C-0-1] não deve modificar as APIs expostas publicamente na plataforma Android alterando qualquer método ou assinatura de classe ou removendo classes ou campos de classe.
• [C-0-2] não deve adicionar nenhum elementos expostos publicamente (como classes ou interfaces, campos ou métodos a classes ou interfaces existentes) ou APIs de teste ou sistema nas APIs nos namespaces acima. Um "elemento exposto publicamente" é qualquer construto que não seja decorado com o marcador "@hide", conforme usado no código -fonte Android a montante.

Os implementadores de dispositivos podem modificar a implementação subjacente das APIs, mas essas modificações:

• [C-0-3] não deve afetar o comportamento declarado e a assinatura da linguagem de Java de qualquer APIs exposta publicamente.
• [C-0-4] não deve ser anunciado ou exposto a desenvolvedores.

No entanto, os implementadores de dispositivos podem adicionar APIs personalizadas fora do espaço de nome Android padrão, mas as APIs personalizadas:

• [C-0-5] não deve estar em um espaço de nome de propriedade ou referência a outra organização. Por exemplo, os implementadores de dispositivos não devem adicionar APIs ao com.google.* Ou namespace semelhante: apenas o Google pode fazê -lo. Da mesma forma, o Google não deve adicionar APIs aos namespaces de outras empresas.
• [C-0-6] deve ser empacotado em uma biblioteca compartilhada do Android, para que apenas aplicativos que os usem explicitamente (através do mecanismo <suses-Library>) sejam afetados pelo aumento do uso de memória dessas APIs.

Os implementadores de dispositivos podem adicionar APIs personalizadas em idiomas nativos, fora das APIs do NDK, mas as APIs personalizadas:

• [C-1-1] não deve estar em uma biblioteca NDK ou em uma biblioteca de propriedade de outra organização, conforme descrito aqui .

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

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

3.7. Runtime Compatibility

Implementações de dispositivos:

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

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

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

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

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

Layout da tela	Screen Density	Minimum Application Memory
Android Watch	120 dpi (ldpi)	32 MB
	140 dpi (140dpi)
	160 dpi (mdpi)
	180 dpi (180dpi)
	200 dpi (200dpi)
	213 dpi (tvdpi)
	220 dpi (220dpi)	36MB
	240 dpi (hdpi)
	280 dpi (280dpi)
	320 dpi (xhdpi)	48MB
	360 dpi (360dpi)
	400 dpi (400dpi)	56MB
	420 dpi (420dpi)	64 MB
	480 dpi (xxhdpi)	88MB
	560 dpi (560dpi)	112MB
	640 dpi (xxxhdpi)	154MB
small/normal	120 dpi (ldpi)	32 MB
	140 dpi (140dpi)
	160 dpi (mdpi)
	180 dpi (180dpi)	48MB
	200 dpi (200dpi)
	213 dpi (tvdpi)
	220 dpi (220dpi)
	240 dpi (hdpi)
	280 dpi (280dpi)
	320 dpi (xhdpi)	80MB
	360 dpi (360dpi)
	400 dpi (400dpi)	96MB
	420 dpi (420dpi)	112MB
	480 dpi (xxhdpi)	128MB
	560 dpi (560dpi)	192MB
	640 dpi (xxxhdpi)	256 MB
grande	120 dpi (ldpi)	32 MB
	140 dpi (140dpi)	48MB
	160 dpi (mdpi)
	180 dpi (180dpi)	80MB
	200 dpi (200dpi)
	213 dpi (tvdpi)
	220 dpi (220dpi)
	240 dpi (hdpi)
	280 dpi (280dpi)	96MB
	320 dpi (xhdpi)	128MB
	360 dpi (360dpi)	160MB
	400 dpi (400dpi)	192MB
	420 dpi (420dpi)	228MB
	480 dpi (xxhdpi)	256 MB
	560 dpi (560dpi)	384MB
	640 dpi (xxxhdpi)	512 MB
extra grande	120 dpi (ldpi)	48MB
	140 dpi (140dpi)	80MB
	160 dpi (mdpi)
	180 dpi (180dpi)	96MB
	200 dpi (200dpi)
	213 dpi (tvdpi)
	220 dpi (220dpi)
	240 dpi (hdpi)
	280 dpi (280dpi)	144MB
	320 dpi (xhdpi)	192MB
	360 dpi (360dpi)	240MB
	400 dpi (400dpi)	288MB
	420 dpi (420dpi)	336MB
	480 dpi (xxhdpi)	384MB
	560 dpi (560dpi)	576MB
	640 dpi (xxxhdpi)	768MB

3.8. User Interface Compatibility

3.8.1. Launcher (Home Screen)

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

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

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

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

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

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

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

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

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

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

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

If device implementations support monochrome icons, these icons:

• [C-6-1] MUST be used only when a user explicitly enables them (eg via Settings or wallpaper picker menu).

3.8.2. Widgets

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

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

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

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

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

3.8.3. Notificações

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

3.8.3.1. Presentation of Notifications

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

• [C-1-1] MUST support notifications that use hardware features, as described in the SDK documentation, and to the extent possible with the device implementation hardware. For instance, if a device implementation includes a vibrator, it MUST correctly implement the vibration APIs. If a device implementation lacks hardware, the corresponding APIs MUST be implemented as no-ops. This behavior is further detailed in section 7 .
• [C-1-2] MUST correctly render all resources (icons, animation files, etc.) provided for in the APIs, or in the Status/System Bar icon style guide , although they MAY provide an alternative user experience for notifications than that provided by the reference Android Open Source implementation.
• [C-1-3] MUST honor and implement properly the behaviors described for the APIs to update, remove and group notifications.
• [C-1-4] MUST provide the full behavior of the NotificationChannel API documented in the SDK.
• [C-1-5] MUST provide a user affordance to block and modify a certain third-party app's notification per each channel and app package level.
• [C-1-6] MUST also provide a user affordance to display deleted notification channels.

• [C-1-7] MUST correctly render all resources (images, stickers, icons, etc.) provided through Notification.MessagingStyle alongside the notification text without additional user interaction. For example, MUST show all resources including icons provided through android.app.Person in a group conversation that is set through setGroupConversation .

• [C-SR-1] Are STRONGLY RECOMMENDED to provide an affordance for the user to control the notifications that are exposed to apps that have been granted the Notification Listener permission. The granularity MUST be so that the user can control for each such notification listener what notification types are bridged to this listener. The types MUST include "conversations", "alerting", "silent", and "important ongoing" notifications.

• [C-SR-2] Are STRONGLY RECOMMENDED provide an affordance for users to specify apps to exclude from notifying any specific notification listener.

• [C-SR-3] Are STRONGLY RECOMMENDED to automatically surface a user affordance to block a certain third-party app's notification per each channel and app package level after the user dismisses that notification multiple times.

• SHOULD support rich notifications.

• SHOULD present some higher priority notifications as heads-up notifications.

• SHOULD have a user affordance to snooze notifications.

• MAY only manage the visibility and timing of when third-party apps can notify users of notable events to mitigate safety issues such as driver distraction.

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

Implementações de dispositivos:

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

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

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

If device implementations support rich notifications, they:

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

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

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

3.8.3.2. Notification Listener Service

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

Implementações de dispositivos:

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

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

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

3.8.3.3. DND (Do not Disturb) / Priority Mode

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

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

Start new requirements for 15 (AOSP experimental)

3.8.3.4. Sensitive Notification Protection

[3.8.3.4 Sensitive Notification Protection] (April 8, 2024 preview)

Device implementation:

• [C-1-1] MUST include a Notification Assistant Service (NAS) that redacts sensitive information from notification content to notification listeners, unless the listener service is:

  • System signed apps with a uid < 10000
  • IU do sistema
  • Concha
  • Designated Companion Device App (defined by CompanionDeviceManager )
  • SYSTEM_AUTOMOTIVE_PROJECTION role
  • SYSTEM_NOTIFICATION_INTELLIGENCE role
  • HOME role

The AOSP implementation of NotificationAssistantServices contained in ExtService meets these requirements.

Acabar com novos requisitos

[3.8.3.4 Sensitive Notification Protection] (February 26, 2024 preview)

Device implementation:

• [C-1-1] MUST include a Notification Assistant Service (NAS) that redacts sensitive information from notification content to notification listeners, unless that service is:

  • System signed apps with a uid < 10000
  • SysUI
  • Concha
  • Designated Companion Device App (defined by CompanionDeviceManager )
  • SYSTEM_AUTOMOTIVE_PROJECTION role
  • SYSTEM_NOTIFICATION_INTELLIGENCE role
  • HOME role

The AOSP implementation of NotificationAssistantServices contained in ExtService meets these requirements.

Acabar com novos requisitos

[3.8.3.4 Sensitive Notification Protection] (February 5, 2024 preview)

Device implementation:

• [C-1-1] MUST include a Notification Assistant Service (NAS) that redacts sensitive information from notification content to notification listeners, and MUST NOT send sensitive information to a non-exempt notification listener service unless that service is:

  • SysUI and system server app
  • Concha
  • Designated Companion Device App (as determined by the CompanionDeviceManager API)
  • SYSTEM_AUTOMOTIVE_PROJECTION role
  • SYSTEM_NOTIFICATION_INTELLIGENCE role
  • Notification being processed was sent by the same package as a particular NLS
  • HOME role

The AOSP implementation of NotificationAssistantServices contained in ExtService meets these requirements.

Acabar com novos requisitos

3.8.4. Assist APIs

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

If device implementations support the Assist action, they:

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

3.8.5. Alerts and Toasts

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

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

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

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

3.8.6. Temas

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

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

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

• [C-1-1] MUST NOT alter any of the Holo theme attributes exposed to applications.
• [C-1-2] MUST support the "Material" theme family and MUST NOT alter any of the Material theme attributes or their assets exposed to applications.

• [C-1-3] MUST either set the "sans-serif" font family to Roboto version 2.x for the languages that Roboto supports, or provide a user affordance to change the font used for the "sans-serif" font family to Roboto version 2.x for the languages that Roboto supports.

• [C-1-4] MUST generate dynamic color tonal palettes as specified in the AOSP documentation of Settings.THEME_CUSTOMIZATION_OVERLAY_PACKAGES (see android.theme.customization.system_palette and android.theme.customization.theme_style ).

• [C-1-5] MUST generate dynamic color tonal palettes using color theme styles enumerated in the Settings.THEME_CUSTOMIZATION_OVERLAY_PACKAGES documentation (see android.theme.customization.theme_styles ), namely TONAL_SPOT , VIBRANT , EXPRESSIVE , SPRITZ , RAINBOW , FRUIT_SALAD , and MONOCHROMATIC .

  "Source color" used to generate dynamic color tonal palettes when sent with android.theme.customization.system_palette (as documented in Settings.THEME_CUSTOMIZATION_OVERLAY_PACKAGES ).

• [C-1-6] MUST have a CAM16 chroma value of 5 or larger.

  • SHOULD be derived from the wallpaper via com.android.systemui.monet.ColorScheme#getSeedColors , which provides multiple valid source colors to pick one from.

  • SHOULD use the value 0xFF1B6EF3 , if none of the provided colors meet the above source color requirement.

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

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

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

If device implementations include a system status bar, they:

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

3.8.7. Papel de parede animados

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

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

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

If device implementations implement live wallpapers, they:

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

3.8.8. Activity Switching

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

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

Se as implementações do dispositivo, incluindo a tecla de navegação da função recente, conforme detalhado na seção 7.2.3, alterarem a interface, elas:

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

3.8.9. Input Management

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

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

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

3.8.10. Lock Screen Media Control

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

3.8.11. Screen savers (previously Dreams)

See section 3.2.3.5 for settings intent to congfigure screen savers.

3.8.12. Localização

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

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

3.8.13. Unicode and Font

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

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

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

If device implementations include an IME, they:

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

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

If device implementations include support for Burmese, they:

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

3.8.14. Multi-windows

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

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

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

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

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

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

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

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

Start new requirements for 15 (AOSP experimental)

[C-4-1 and C-5-1] (February 5, 2024 preview)

If device implementations include one or more foldable Android-compatible display areas, or include a folding hinge between multiple Android-compatible display areas and make such areas available to applications, they:

• [C-4-1] MUST support multi-window mode.

If device implementations support multi-window mode, they:

• [C-5-1] MUST implement the correct version of the Window Manager Extensions API level as described in WindowManager Extensions .

Acabar com novos requisitos

3.8.15. Display Cutout

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

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

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

3.8.16. Device Controls

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

See Section 2_2_3 for device-specific requirements.

3.8.17. Prancheta

Implementações de dispositivos:

• [C-0-1] MUST NOT send clipboard data to any component, activity, service, or across any network connection, without explicit user action (eg, pressing a button on the overlay), except for services mentioned in 9.8.6 Content Capture and App Search .

If device implementations generate a user-visible preview when content is copied to the clipboard for any ClipData item where ClipData.getDescription().getExtras() contains android.content.extra.IS_SENSITIVE , they:

• [C-1-1] MUST redact the user visible preview

The AOSP reference implementation satisfies these clipboard requirements.

Start new requirements for 15 (AOSP experimental)

3.8.18. Localization and Language Selection [Withdrawn]

3.8.18 [Withdrawn] (April 8, 2024 preview)

This requirement is withdrawn from Android 15 (AOSP experimental).

Acabar com novos requisitos

3.8.18 (February 5, 2024 preview)

If device implementations support multiple locales or languages, they:

• [C-1-1] MUST provide user a affordance to select a locale or language from the list returned by LocaleConfig#getSupportedLocales() for each app that returns STATUS_SUCCESS for LocaleConfig#getStatus() .

Acabar com novos requisitos

3.9. Device Administration

Start new requirements for 15 (AOSP experimental)

[3.9/C-1-1 and C-1-2] (February 26, 2024 preview)

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

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

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

Acabar com novos requisitos

3.9.1. Device Provisioning

3.9.1.1. Device owner provisioning

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

• [C-1-1] MUST support enrolling a Device Policy Client (DPC) as a Device Owner app as described below:
  • When the device implementation has neither users nor user data configured, it:
    • [C-1-5] MUST enroll the DPC application as the Device Owner app or enable the DPC app to choose whether to become a Device Owner or a Profile Owner, if the device declares Near-Field Communications (NFC) support via the feature flag android.hardware.nfc and receives an NFC message containing a record with MIME type MIME_TYPE_PROVISIONING_NFC .
    • [C-1-8] MUST send the ACTION_GET_PROVISIONING_MODE intent after device owner provisioning is triggered so that the DPC app can choose whether to become a Device Owner or a Profile Owner, depending on the values of android.app.extra.PROVISIONING_ALLOWED_PROVISIONING_MODES , unless it can be determined from context that there is only one valid option.
    • [C-1-9] MUST send the ACTION_ADMIN_POLICY_COMPLIANCE intent to the Device Owner app if a Device Owner is established during provisioning regardless of the provisioning method used. The user must not be able to proceed in the Setup Wizard until the Device Owner app finishes.
  • When the device implementation has users or user data, it:
    • [C-1-7] MUST not enroll any DPC application as the Device Owner App any more.

Start new requirements for 15 (AOSP experimental)

[C-1-2 through C-2-3] (February 26, 2024 preview)

• [C-1-2] MUST show an appropriate disclosure notice (such as referenced in AOSP ) and obtain affirmative consent from the end user prior to an app being set as Device Owner, unless the device is programmatically configured for Retail Demo Mode prior to on-screen, end-user interaction. If device implementations declare android.software.device_admin , but also include a proprietary device management solution and provide a mechanism to promote an application configured in their solution as a "Device Owner equivalent" to the standard "Device Owner" as recognized by the standard Android DevicePolicyManager APIs, they:

• [C-2-1] MUST have a process in place to verify that the specific app being promoted belongs to a legitimate enterprise device management solution and has been configured in the proprietary solution to have the rights equivalent as a "Device Owner".

• [C-2-2] MUST show the same AOSP Device Owner consent disclosure as the flow initiated by android.app.action.PROVISION_MANAGED_DEVICE prior to enrolling the DPC application as "Device Owner".

• [C-2-3] MUST NOT hard code the consent or prevent the use of other device owner apps.

Acabar com novos requisitos

3.9.1.2. Managed profile provisioning

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

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

Start new requirements for 15 (AOSP experimental)

[C-1-2] (February 26, 2024 preview)

• [C-1-2] The managed profile provisioning process (the flow initiated by the DPC using the android.app.action.PROVISION_MANAGED_PROFILE ) or by the platform), consent screen and user experience MUST align with the AOSP implementation.

Acabar com novos requisitos

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

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

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

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

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

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

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

3.9.2. Managed Profile Support

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

• [C-1-1] MUST support managed profiles via the android.app.admin.DevicePolicyManager APIs.
• [C-1-2] MUST allow one and only one managed profile to be created .
• [C-1-3] MUST use an icon badge (similar to the AOSP upstream work badge) to represent the managed applications and widgets and other badged UI elements like Recents & Notifications.
• [C-1-4] MUST display a notification icon (similar to the AOSP upstream work badge) to indicate when user is within a managed profile application.
• [C-1-5] MUST display a toast indicating that the user is in the managed profile if and when the device wakes up (ACTION_USER_PRESENT) and the foreground application is within the managed profile.
• [C-1-6] Where a managed profile exists, MUST show a visual affordance in the Intent 'Chooser' to allow the user to forward the intent from the managed profile to the primary user or vice versa, if enabled by the Device Policy Controlador.
• [C-1-7] Where a managed profile exists, MUST expose the following user affordances for both the primary user and the managed profile:
  • Separate accounting for battery, location, mobile data and storage usage for the primary user and managed profile.
  • Independent management of VPN Applications installed within the primary user or managed profile.
  • Independent management of applications installed within the primary user or managed profile.
  • Independent management of accounts within the primary user or managed profile.
• [C-1-8] MUST ensure the preinstalled dialer, contacts and messaging applications can search for and look up caller information from the managed profile (if one exists) alongside those from the primary profile, if the Device Policy Controller permits it.
• [C-1-9] MUST ensure that it satisfies all the security requirements applicable for a device with multiple users enabled (see section 9.5 ), even though the managed profile is not counted as another user in addition to the primary user.
• [C-1-10] MUST ensure that the screenshot data is saved in the work profile storage when a screenshot is captured with a topActivity window that has focus (the one the user interacted with last among all activities) and belongs to a work profile aplicativo .
• [C-1-11] MUST NOT capture any other screen content (system bar, notifications or any personal profile content) except for the work profile application window/windows when saving a screenshot to the work profile (to ensure that personal profile data is not saved in the work profile).

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

• [C-2-1] MUST support the ability to specify a separate lock screen meeting the following requirements to grant access to apps running in a managed profile only.
  • Device implementations MUST honor the DevicePolicyManager.ACTION_SET_NEW_PASSWORD intent and show an interface to configure a separate lock screen credential for the managed profile.
  • The lock screen credentials of the managed profile MUST use the same credential storage and management mechanisms as the parent profile, as documented on the Android Open Source Project Site .
  • The DPC password policies MUST apply to only the managed profile's lock screen credentials unless called upon the DevicePolicyManager instance returned by getParentProfileInstance .
• When contacts from the managed profile are displayed in the preinstalled call log, in-call UI, in-progress and missed-call notifications, contacts and messaging apps they SHOULD be badged with the same badge used to indicate managed profile applications.

3.9.3. Managed User Support

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

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

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

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

3.9.4. Device Policy Management Role Requirements

If device implementations report android.software.device_admin or android.software.managed_users , then they:

• [C-1-1] MUST support the device policy management role as defined in section 9.1 . The application that holds the device policy management role MAY be defined by setting config_devicePolicyManagement to the package name. The package name MUST be followed by : and the signing certificate unless the application is preloaded.

If a package name is not defined for config_devicePolicyManagement as described above:

• [C-2-1] Device implementations MUST support provisioning without a device policy management role holder application ( AOSP provides a reference implementation ).

If a package name is defined for config_devicePolicyManagement as described above:

• [C-3-1] The application MUST be installed on all profiles for a user .
• [C-3-2] Device implementations MAY define an application that updates the device policy management role holder before provisioning by setting config_devicePolicyManagementUpdater .

If a package name is defined for config_devicePolicyManagementUpdater as described above:

• [C-4-1] The application MUST be preinstalled on the device.
• [C-4-2] The application MUST implement an intent filter which resolves android.app.action.UPDATE_DEVICE_POLICY_MANAGEMENT_ROLE_HOLDER .

3.9.5. Device Policy Resolution Framework

If device implementations report android.software.device_admin or android.software.managed_users , then they:

• [C-1-1] MUST resolve device policy conflicts as documented in Device Policy Resolution Framework .

3.10. Acessibilidade

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

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

• [C-1-1] MUST provide an implementation of the Android accessibility framework as described in the accessibility APIs SDK documentation.
• [C-1-2] MUST generate accessibility events and deliver the appropriate AccessibilityEvent to all registered AccessibilityService implementations as documented in the SDK.
• [C-1-4] MUST provide a user affordance to control accessibility services that declare the AccessibilityServiceInfo.FLAG_REQUEST_ACCESSIBILITY_BUTTON . Note that for device implementations with a system navigation bar, they SHOULD allow the user to have the option for a button in the system's navigation bar to control these services.

If device implementations include preinstalled accessibility services, they:

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

3.11. Texto para fala

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

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

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

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

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

Start new requirements for 15 (AOSP experimental)

3.12. TV Input Framework

[3.12] (February 26, 2024 preview)

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

If device implementations support TIF, they:

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

Acabar com novos requisitos

3.13. Configurações rápidas

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

If device implementations include a Quick Settings UI component and support third-party Quick Settings, they:

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

3.14. Media UI

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

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

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

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

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

3.15. Instant Apps

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

• [C-1-1] Instant Apps MUST only be granted permissions that have the android:protectionLevel set to "instant" .
• [C-1-2] Instant Apps MUST NOT interact with installed apps via implicit intents unless one of the following is true:
  • The component's intent pattern filter is exposed and has CATEGORY_BROWSABLE
  • The action is one of ACTION_SEND, ACTION_SENDTO, ACTION_SEND_MULTIPLE
  • The target is explicitly exposed with android:visibleToInstantApps
• [C-1-3] Instant Apps MUST NOT interact explicitly with installed apps unless the component is exposed via android:visibleToInstantApps.
• [C-1-4] Installed Apps MUST NOT see details about Instant Apps on the device unless the Instant App explicitly connects to the installed application.

• Device implementations MUST provide the following user affordances for interacting with Instant Apps. The AOSP meets the requirements with the default System UI, Settings, and Launcher. Implementações de dispositivos:

  • [C-1-5] MUST provide a user affordance to view and delete Instant Apps locally cached for each individual app package.
  • [C-1-6] MUST provide a persistent user notification that can be collapsed while an Instant App is running in the foreground. This user notification MUST include that Instant Apps do not require installation and provide a user affordance that directs the user to the application info screen in Settings. For Instant Apps launched via web intents, as defined by using an intent with action set to Intent.ACTION_VIEW and with a scheme of "http" or "https", an additional user affordance SHOULD allow the user not to launch the Instant App and launch the associated link with the configured web browser, if a browser is available on the device.
  • [C-1-7] MUST allow running Instant Apps to be accessed from the Recents function if the Recents function is available on the device.

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

3.16. Companion Device Pairing

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

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

• [C-1-1] MUST declare the feature flag FEATURE_COMPANION_DEVICE_SETUP .
• [C-1-2] MUST ensure the APIs in the android.companion package is fully implemented.

Start new requirements for 15 (AOSP experimental)

[C-1-3] (February 5, 2024 preview)

• [C-1-3] MUST provide user affordances for the user to select/confirm a companion device is present and operational , which MUST use the same message as implemented in AOSP without addition or modification .

Acabar com novos requisitos

3.17. Heavyweight Apps

If device implementations declare the feature FEATURE_CANT_SAVE_STATE , then they:

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

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

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

3.18. Contatos

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

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

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

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

Implementações de dispositivos:

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

If device implementations use a custom local account :

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

Start new requirements for 15 (AOSP experimental)

3.19. Configurações de linguagem

[3.19. Language Settings] (February 26, 2024 preview)

Implementações de dispositivos:

• [C-0-1] MUST NOT provide any user affordance to select gender-specific language treatment for languages that do not support gender specific translations. See grammatical resources for more information.

Acabar com novos requisitos

4. Application Packaging Compatibility

Devices implementations:

• [C-0-1] MUST be capable of installing and running Android ".apk" files as generated by the "aapt" tool included in the official Android SDK .

  • As the above requirement may be challenging, device implementations are RECOMMENDED to use the AOSP reference implementation's package management system.

• [C-0-2] MUST support verifying ".apk" files using the APK Signature Scheme v3.1, APK Signature Scheme v3 , APK Signature Scheme v2 and JAR signing .

• [C-0-3] MUST NOT extend either the .apk , Android Manifest , Dalvik bytecode , or RenderScript bytecode formats in such a way that would prevent those files from installing and running correctly on other compatible devices.

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

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

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

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

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

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

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

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

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

Note: Device implementations that shipped on Android version 10 or earlier that cannot meet the requirements [C-0-8] and [C-0-9] through a system software update MAY be exempted from these requirements.

5. Multimedia Compatibility

Implementações de dispositivos:

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

Implementações de dispositivos:

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

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

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

5.1. Media Codecs

5.1.1. Audio Encoding

See more details in 5.1.3. Audio Codecs Details .

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

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

All audio encoders MUST support:

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

5.1.2. Audio Decoding

See more details in 5.1.3. Audio Codecs Details .

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

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

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

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

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

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

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

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

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

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

All audio decoders MUST support outputting:

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

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

• [C-7-1] MUST be able to be configured by the application using the decoding with the key KEY_MAX_OUTPUT_CHANNEL_COUNT to control whether the content is downmixed to stereo (when using a value of 2) or is output using the native number of channels (when using a value equal or greater to that number). For instance a value of 6 or greater would configure a decoder to output 6 channels when fed 5.1 content.
• [C-7-2] When decoding, the decoder MUST advertise the channel mask being used on the output format with the KEY_CHANNEL_MASK key, using the android.media.AudioFormat constants (example: CHANNEL_OUT_5POINT1 ).

If device implementations support audio decoders other than the default AAC audio decoder and are capable of outputting multi-channel audio (ie more than 2 channels) when fed compressed multi-channel content, then:

• [C-SR-2] The decoder is STRONGLY RECOMMENDED to be able to be configured by the application using the decoding with the key KEY_MAX_OUTPUT_CHANNEL_COUNT to control whether the content is downmixed to stereo (when using a value of 2) or is output using the native number of channels (when using a value equal or greater to that number). For instance a value of 6 or greater would configure a decoder to output 6 channels when fed 5.1 content.
• [C-SR-3] When decoding, the decoder is STRONGLY RECOMMENDED to advertise the channel mask being used on the output format with the KEY_CHANNEL_MASK key, using the android.media.AudioFormat constants (example: CHANNEL_OUT_5POINT1 ).

5.1.3. Audio Codecs Details

Format/Codec	Detalhes	File Types/Container Formats to be supported
MPEG-4 AAC Profile (AAC LC)	Support for mono/stereo/5.0/5.1 content with standard sampling rates from 8 to 48 kHz.	3GPP (.3gp) MPEG-4 (.mp4, .m4a) ADTS raw AAC (.aac, ADIF not supported) MPEG-TS (.ts, not seekable, decode only) Matroska (.mkv, decode only)
MPEG-4 HE AAC Profile (AAC+)	Support for mono/stereo/5.0/5.1 content with standard sampling rates from 16 to 48 kHz.	3GPP (.3gp) MPEG-4 (.mp4, .m4a)
MPEG-4 HE AACv2 Profile (enhanced AAC+)	Support for mono/stereo/5.0/5.1 content with standard sampling rates from 16 to 48 kHz.	3GPP (.3gp) MPEG-4 (.mp4, .m4a)
AAC ELD (enhanced low delay AAC)	Support for mono/stereo content with standard sampling rates from 16 to 48 kHz.	3GPP (.3gp) MPEG-4 (.mp4, .m4a)
USAC	Support for mono/stereo content with standard sampling rates from 7.35 to 48 kHz.	MPEG-4 (.mp4, .m4a)
AMR-NB	4.75 to 12.2 kbps sampled @ 8 kHz	3GPP (.3gp)
AMR-WB	9 rates from 6.60 kbit/s to 23.85 kbit/s sampled @ 16 kHz, as defined at AMR-WB, Adaptive Multi-Rate - Wideband Speech Codec	3GPP (.3gp)
FLAC	For both encoder and decoder: at least Mono and Stereo modes MUST be supported. Sample rates up to 192 kHz MUST be supported; 16-bit and 24-bit resolution MUST be supported. FLAC 24-bit audio data handling MUST be available with floating point audio configuration.	FLAC (.flac) MPEG-4 (.mp4, .m4a, decode only) Matroska (.mkv, decode only)
MP3	Mono/Stereo 8-320Kbps constant (CBR) or variable bitrate (VBR)	MP3 (.mp3) MPEG-4 (.mp4, .m4a, decode only) Matroska (.mkv, decode only)
MIDI	MIDI Type 0 and 1. DLS Version 1 and 2. XMF and Mobile XMF. Support for ringtone formats RTTTL/RTX, OTA, and iMelody	Type 0 and 1 (.mid, .xmf, .mxmf) RTTTL/RTX (.rtttl, .rtx) iMelody (.imy)
Vorbis		Ogg (.ogg) MPEG-4 (.mp4, .m4a, decode only) Matroska (.mkv) Webm (.webm)
PCM/WAVE	PCM codec MUST support 16-bit linear PCM and 16-bit float. WAVE extractor must support 16-bit, 24-bit, 32-bit linear PCM and 32-bit float (rates up to limit of hardware). Sampling rates MUST be supported from 8 kHz to 192 kHz.	WAVE (.wav)
obra	Decoding: Support for mono, stereo, 5.0 and 5.1 content with sampling rates of 8000, 12000, 16000, 24000, and 48000 Hz. Encoding: Support for mono and stereo content with sampling rates of 8000, 12000, 16000, 24000, and 48000 Hz.	Ogg (.ogg) MPEG-4 (.mp4, .m4a, decode only) Matroska (.mkv) Webm (.webm)

5.1.4. Image Encoding

See more details in 5.1.6. Image Codecs Details .

Device implementations MUST support encoding the following image encoding:

• [C-0-1] JPEG
• [C-0-2] PNG
• [C-0-3] WebP
• [C-0-4] AVIF
  • Devices must support BITRATE_MODE_CQ and Baseline Profile.

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

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

5.1.5. Image Decoding

See more details in 5.1.6. Image Codecs Details .

Device implementations MUST support decoding the following image encoding:

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

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

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

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

5.1.6. Image Codecs Details

Format/Codec	Detalhes	Supported File Types/Container Formats
JPEG	Base+progressive	JPEG (.jpg)
GIFs		GIF (.gif)
png		PNG (.png)
Veículo de combate de infantaria		BMP (.bmp)
WebP		WebP (.webp)
Cru		ARW (.arw), CR2 (.cr2), DNG (.dng), NEF (.nef), NRW (.nrw), ORF (.orf), PEF (.pef), RAF (.raf), RW2 (.rw2), SRW (.srw)
HEIF	Image, Image collection, Image sequence	HEIF (.heif), HEIC (.heic)
AVIF (Baseline Profile)	Image, Image collection, Image sequence Baseline Profile	HEIF container (.avif)

Image encoder and decoders exposed through the MediaCodec API

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

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

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

5.1.7. Video Codecs

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

If device implementations include a video decoder or encoder:

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

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

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

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

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

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

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

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

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

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

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

5.1.8. Video Codecs List

Format/Codec	Detalhes	File Types/Container Formats to be supported
H.263		3GPP (.3gp) MPEG-4 (.mp4) Matroska (.mkv, decode only)
H.264 AVC	See section 5.2 and 5.3 for details	3GPP (.3gp) MPEG-4 (.mp4) MPEG-2 TS (.ts, not seekable) Matroska (.mkv, decode only)
H.265 HEVC	See section 5.3 for details	MPEG-4 (.mp4) Matroska (.mkv, decode only)
MPEG-2	Main Profile	MPEG2-TS (.ts, not seekable) MPEG-4 (.mp4, decode only) Matroska (.mkv, decode only)
MPEG-4 SP		3GPP (.3gp) MPEG-4 (.mp4) Matroska (.mkv, decode only)
VP8	See section 5.2 and 5.3 for details	WebM (.webm) Matroska (.mkv)
VP9	See section 5.3 for details	WebM (.webm) Matroska (.mkv)
AV1	See section 5.2 and section 5.3 for details	MPEG-4 (.mp4) Matroska (.mkv, decode only)

5.1.9. Media Codec Security

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

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

If device implementations support multimedia, they:

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

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

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

If device implementations support Codec 2.0 API, they:

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

5.1.10. Media Codec Characterization

If device implementations support media codecs, they:

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

Em particular:

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

If device implementations support video codecs:

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

	SD (low quality)	SD (high quality)	Alta definição 720p	HD 1080p	Ultra HD
Resolução de vídeo	176 x 144 px (H263, MPEG2, MPEG4) 352 x 288 px (MPEG4 encoder, H263, MPEG2) 320 x 180 px (VP8, VP8) 320 x 240 px (other)	704 x 576 px (H263) 640 x 360 px (VP8, VP9) 640 x 480 px (MPEG4 encoder) 720 x 480 px (other, AV1)	1408 x 1152 px (H263) 1280 x 720 px (other, AV1)	1920 x 1080 px (other than MPEG4, AV1)	3840 x 2160 px (HEVC, VP9, AV1)

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

5.2. Video Encoding

If device implementations support any video encoder and make it available to third-party apps, and set the
MediaFormat.KEY_BITRATE_MODE to BITRATE_MODE_VBR so that the encoder operates in Variable bitrate mode, then, as long as it does not impact the minimum quality floor , the encoded bitrate :

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

If device implementations support any video encoder and make it available to third-party apps and set the MediaFormat.KEY_BITRATE_MODE to BITRATE_MODE_CBR so the encoder operates in constant bitrate mode, then the encoded bitrate:

• [C-SR-2] is STRONGLY RECOMMENDED to NOT be more than 15% over the target bitrate over a sliding window of 1 second.

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

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

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

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

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

• SHOULD support dynamically configurable bitrates for the supported encoder.

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

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

If device implementations provide HDR encoding, they:

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

5.2.1. H.263

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

• [C-1-1] MUST support QCIF resolution (176 x 144) using Baseline Profile Level 45. SQCIF resolution is optional.

5.2.2. H.264

If device implementations support H.264 codec, they:

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

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

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

	SD (Low quality)	SD (High quality)	Alta definição 720p	HD 1080p
Resolução de vídeo	320 x 240 px	720 x 480 px	1280 x 720 px	1920 x 1080 pixels
Video frame rate	20fps	30fps	30fps	30fps
Video bitrate	384 Kbps	2Mbps	4 Mbps	10 Mbps

5.2.3. VP8

If device implementations support VP8 codec, they:

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

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

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

	SD (Low quality)	SD (High quality)	Alta definição 720p	HD 1080p
Resolução de vídeo	320 x 180 px	640 x 360 px	1280 x 720 px	1920 x 1080 pixels
Video frame rate	30fps	30fps	30fps	30fps
Video bitrate	800 Kbps	2Mbps	4 Mbps	10 Mbps

5.2.4. VP9

If device implementations support VP9 codec, they:

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

	SD	Alta definição 720p	HD 1080p	Ultra HD
Resolução de vídeo	720 x 480 px	1280 x 720 px	1920 x 1080 pixels	3840 x 2160 px
Video frame rate	30fps	30fps	30fps	30fps
Video bitrate	1.6 Mbps	4 Mbps	5Mbps	20Mbps

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

• Support for 12-bit format is OPTIONAL.

5.2.5. H.265

If device implementations support H.265 codec, they:

• [C-1-1] MUST support Main Profile Level 3 up to 512 x 512 resolution.
• [C-SR-1] are STRONGLY RECOMMENDED to support the 720 x 480 SD profile and the HD encoding profiles as indicated in the following table if there is a hardware encoder.

	SD	Alta definição 720p	HD 1080p	Ultra HD
Resolução de vídeo	720 x 480 px	1280 x 720 px	1920 x 1080 pixels	3840 x 2160 px
Video frame rate	30fps	30fps	30fps	30fps
Video bitrate	1.6 Mbps	4 Mbps	5Mbps	20Mbps

5.2.6. AV1

If device implementations support AV1 codec then, they:

• [C-1-1] MUST support Main Profile including 8-bit and 10-bit content.

• [C-1-2] MUST publish performance data ie report performance data via the getSupportedFrameRatesFor() or getSupportedPerformancePoints() APIs for supported resolutions in the table below.

• [C-1-3] MUST accept HDR metadata and output it to the bitstream

If AV1 encoder is hardware accelerated, then it:

• [C-2-1] MUST support up to and including HD1080p encoding profile from the table below:

	SD	Alta definição 720p	HD 1080p	Ultra HD
Resolução de vídeo	720 x 480 px	1280 x 720 px	1920 x 1080 pixels	3840 x 2160 px
Video frame rate	30fps	30fps	30fps	30fps
Video bitrate	5Mbps	8 Mbps	16Mbps	50Mbps

5.3. Video Decoding

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

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

5.3.1. MPEG-2

If device implementations support MPEG-2 decoders, they:

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

5.3.2. H.263

If device implementations support H.263 decoders, they:

• [C-1-1] MUST support Baseline Profile Level 30 (CIF, QCIF and SQCIF resolutions @ 30fps 384kbps) and Level 45 (QCIF and SQCIF resolutions @ 30fps 128kbps).

5.3.3. MPEG-4

If device implementations with MPEG-4 decoders, they:

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

5.3.4. H.264

If device implementations support H.264 decoders, they:

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

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

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

	SD (Low quality)	SD (High quality)	Alta definição 720p	HD 1080p
Resolução de vídeo	320 x 240 px	720 x 480 px	1280 x 720 px	1920 x 1080 pixels
Video frame rate	30fps	30fps	60fps	30 fps (60 fps ^Television )
Video bitrate	800 Kbps	2Mbps	8 Mbps	20Mbps

5.3.5. H.265 (HEVC)

If device implementations support H.265 codec, they:

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

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

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

	SD (Low quality)	SD (High quality)	Alta definição 720p	HD 1080p	Ultra HD
Resolução de vídeo	352 x 288 pixels	720 x 480 px	1280 x 720 px	1920 x 1080 pixels	3840 x 2160 px
Video frame rate	30fps	30fps	30fps	30/60 fps (60 fps ^Television with H.265 hardware decoding )	60fps
Video bitrate	600 Kbps	1.6 Mbps	4 Mbps	5Mbps	20Mbps

If device implementations claim to support an HDR Profile through the Media APIs:

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

5.3.6. VP8

If device implementations support VP8 codec, they:

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

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

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

	SD (Low quality)	SD (High quality)	Alta definição 720p	HD 1080p
Resolução de vídeo	320 x 180 px	640 x 360 px	1280 x 720 px	1920 x 1080 pixels
Video frame rate	30fps	30fps	30 fps (60 fps ^Television )	30 (60 fps ^Television )
Video bitrate	800 Kbps	2Mbps	8 Mbps	20Mbps

5.3.7. VP9

If device implementations support VP9 codec, they:

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

If device implementations support VP9 codec and a hardware decoder:

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

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

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

	SD (Low quality)	SD (High quality)	Alta definição 720p	HD 1080p	Ultra HD
Resolução de vídeo	320 x 180 px	640 x 360 px	1280 x 720 px	1920 x 1080 pixels	3840 x 2160 px
Video frame rate	30fps	30fps	30fps	30 fps (60 fps ^Television with VP9 hardware decoding )	60fps
Video bitrate	600 Kbps	1.6 Mbps	4 Mbps	5Mbps	20Mbps

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

• Support for 12-bit format is OPTIONAL.

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

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

5.3.8. Visão Dolby

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

• [C-1-1] MUST provide a Dolby Vision-capable extractor.

Start new requirements for 15 (AOSP experimental)

[C-1-2] (December 11, 2023 preview)

• [C-1-2] MUST properly display Dolby Vision content either on the device screen or on an external display attached via a standard video output port (eg, HDMI).

Acabar com novos requisitos

• [C-1-3] MUST set the track ID of backward-compatible base-layer(s) (if present) to be the same as the combined Dolby Vision layer's track ID.

5.3.9. AV1

If device implementations support AV1 codec and make it available to third-party applications, they:

• [C-1-1] MUST support Main Profile including 8-bit and 10-bit content.

If device implementations provide support for AV1 codec with a hardware accelerated decoder then they:

• [C-2-1] MUST be able to decode at least HD 720p video decoding profiles from the table below when the height reported by Display.getSupportedModes() method is equal or greater than 720p.
• [C-2-2] MUST be able to decode at least HD 1080p video decoding profiles from the table below when the height reported by Display.getSupportedModes() method is equal or greater than 1080p.

	SD	Alta definição 720p	HD 1080p	Ultra HD
Resolução de vídeo	720 x 480 px	1280 x 720 px	1920 x 1080 pixels	3840 x 2160 px
Video frame rate	30fps	30fps	30fps	30fps
Video bitrate	5Mbps	8 Mbps	16Mbps	50Mbps

If device implementations support HDR Profile through the Media APIs, then they:

• [C-3-1] MUST support extracting and outputting HDR metadata from the bitstream and/or container.
• [C-3-2] MUST properly display HDR content on the device screen or on a standard video output port (for example, HDMI).

5.4. Gravação de áudio

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

5.4.1. Raw Audio Capture and Microphone Information

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

• [C-1-1] MUST allow capture of raw audio content for any AudioRecord or AAudio INPUT stream that is opened successfully. At a minimum, the following characteristics MUST be supported:

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

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

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

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

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

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

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

• [C-1-4] MUST honor the MicrophoneInfo API and properly fill in information for the available microphones on device accessible to the third-party applications via the AudioManager.getMicrophones() API, for active AudioRecord using MediaRecorder.AudioSources DEFAULT , MIC , CAMCORDER , VOICE_RECOGNITION , VOICE_COMMUNICATION , UNPROCESSED , or VOICE_PERFORMANCE . If device implementations allow AM radio and DVD quality capture of raw audio content, they:

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

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

5.4.2. Capture for Voice Recognition

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

• [C-1-1] MUST capture android.media.MediaRecorder.AudioSource.VOICE_RECOGNITION audio source at one of the sampling rates, 44100 and 48000.
• [C-1-2] MUST, by default, disable any noise reduction audio processing when recording an audio stream from the AudioSource.VOICE_RECOGNITION audio source.

• [C-1-3] MUST, by default, disable any automatic gain control when recording an audio stream from the AudioSource.VOICE_RECOGNITION audio source.

• SHOULD exhibit approximately flat amplitude-versus-frequency characteristics in the mid-frequency range: specifically ±3dB from 100 Hz to 4000 Hz for each and every microphone used to record the voice recognition audio source.

• [C-SR-1] are STRONGLY RECOMMENDED to exhibit amplitude levels in the low frequency range: specifically from ±20 dB from 30 Hz to 100 Hz compared to the mid-frequency range for each and every microphone used to record the voice recognition audio fonte.

• [C-SR-2] are STRONGLY RECOMMENDED to exhibit amplitude levels in the high frequency range: specifically from ±30 dB from 4000 Hz to 22 KHz compared to the mid-frequency range for each and every microphone used to record the voice recognition audio fonte.

• SHOULD set audio input sensitivity such that a 1000 Hz sinusoidal tone source played at 90 dB Sound Pressure Level (SPL) (measured next to the microphone) yields an ideal response of RMS 2500 within a range of 1770 and 3530 for 16 bit-samples (or -22.35 db ±3dB Full Scale for floating point/double precision samples) for each and every microphone used to record the voice recognition audio source.

• SHOULD record the voice recognition audio stream so that the PCM amplitude levels linearly track input SPL changes over at least a 30 dB range from -18 dB to +12 dB re 90 dB SPL at the microphone.

• SHOULD record the voice recognition audio stream with total harmonic distortion (THD) less than 1% for 1 kHz at 90 dB SPL input level at the microphone.

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

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

5.4.3. Capture for Rerouting of Playback

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

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

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

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

5.4.4. Acoustic Echo Canceler

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

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

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

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

5.4.5. Concurrent Capture

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

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

5.5. Reprodução de áudio

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

5.5.1. Raw Audio Playback

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

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

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

5.5.2. Efeitos de áudio

Android provides an API for audio effects for device implementations.

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

• [C-1-1] MUST support the EFFECT_TYPE_EQUALIZER and EFFECT_TYPE_LOUDNESS_ENHANCER implementations controllable through the AudioEffect subclasses Equalizer and LoudnessEnhancer .
• [C-1-2] MUST support the visualizer API implementation, controllable through the Visualizer class.
• [C-1-3] MUST support the EFFECT_TYPE_DYNAMICS_PROCESSING implementation controllable through the AudioEffect subclass DynamicsProcessing .

Start new requirements for 15 (AOSP experimental)

[C-1-4] (February 5, 2024 preview)

• [C-1-4] MUST support audio effects with floating-point input and output , when the effect results are returned to the framework audio pipeline. This refers to typical insert or aux effects such as the equalizer. Equivalent behavior is strongly recommended when the effect results are not visible by the framework audio pipeline (such as, post-processing or offloaded effects) .

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[C-1-5] (February 5, 2024 preview)

• [C-1-5] MUST make sure that audio effects support multiple channels up to the mixer channel count also known as FCC_LIMIT , when the effect results are returned to the framework audio pipeline. This refers to typical insert or aux effects, but excludes special effects such as downmix, upmix, spatialization effects which change the channel count. Equivalent behavior is recommended when the effects are not visible by the framework audio pipeline (such as, post-processing or offloaded effects) .

Acabar com novos requisitos

• SHOULD support the EFFECT_TYPE_BASS_BOOST , EFFECT_TYPE_ENV_REVERB , EFFECT_TYPE_PRESET_REVERB , and EFFECT_TYPE_VIRTUALIZER implementations controllable through the AudioEffect sub-classes BassBoost , EnvironmentalReverb , PresetReverb , and Virtualizer .
• [C-SR-1] Are STRONGLY RECOMMENDED to support effects in floating-point and multichannel.

5.5.3. Audio Output Volume

Implementações de dispositivos automotivos:

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

5.5.4. Audio Offload

If device implementations support audio offload playback , they:

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

5.6. Audio Latency

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

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

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

Start new requirements for 15 (AOSP experimental)

[TTL, RTL, MPC, and FEATURE_AUDIO_PRO definitions]

• tap-to-tone latency (TTL) , as measured by CTS Verifier, is the time between when the screen is tapped and when a tone generated as a result of that tap is heard on the speaker. This is averaged over 5 measurements using the AAudio native audio API for output.

• Round-Trip latency (RTL) , as measured by the CTS Verifier, is the Mean Continuous latency over 5 measurements, measured over a loopback path that feeds the output back to the input, using the AAudio native audio API. The loopback paths are:

  • Speaker/mic: Built-in speaker to built-in microphone.
  • Analog: 3.5mm analog jack and a loopback adapter.
  • USB: USB to 3.5mm adapter and a loopback adapter or a USB audio interface and loopback cables.

• FEATURE_AUDIO_PRO . The android.hardware.audio.pro feature is declared.

• MPC . Media Performance Class

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[head-tracking-latency definition] (February 26, 2024 preview)

• head-tracking latency . The time it takes from the head motion captured by the inertial measurement unit (IMU) to the headphone transducers' detection of the change in sound caused by this motion.

Acabar com novos requisitos

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

Start new requirements for 15 (AOSP experimental)

[C-1-1] (February 5, 2024 preview)

• [C-1-1] The output timestamp returned by AudioTrack.getTimestamp and AAudioStream_getTimestamp is accurate to +/- 2 ms.

Acabar com novos requisitos

• [C-1-2] Cold output latency of 500 milliseconds or less.

• [C-1-3] Opening an output stream using AAudioStreamBuilder_openStream() MUST take less than 1000 milliseconds.

Start new requirements for 15 (AOSP experimental)

[C-1-4] (February 5, 2024 preview)

• [C-1-4] The calculated round-trip latencies based on input and output timestamps returned by AAudioStream_getTimestamp MUST be within 200 msec of the measured round trip latency for AAUDIO_PERFORMANCE_MODE_NONE and AAUDIO_PERFORMANCE_MODE_LOW_LATENCY for speakers, wired and wireless headsets.

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[C-SR-1, C-SR-2, C-SR-4] (February 5, 2024 preview)

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

• [C-SR-1] Cold output latency of 100 milliseconds or less over the speaker data path.

• [C-SR-2] Tap-to-tone latency of 80 milliseconds or less.

• [C-SR-4] The calculated round-trip latencies based on input and output timestamps returned by AAudioStream_getTimestamp are STRONGLY RECOMMENDED to be within 30 msec of the measured round trip latency for AAUDIO_PERFORMANCE_MODE_NONE and AAUDIO_PERFORMANCE_MODE_LOW_LATENCY for speakers, wired and wireless headsets.

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[C-SR-5, C-SR-6, C-SR-7] (February 5, 2024 preview)

If device implementations meet the above requirements, after any initial calibration, when using the AAudio native audio API, for continuous output latency and cold output latency over at least one supported audio output device, they are:

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

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[C-2-1] (February 5, 2024 preview)

If device implementations do not meet the requirements for low-latency audio via the AAudio native audio API, they:

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

Acabar com novos requisitos

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

Start new requirements for 15 (AOSP experimental)

[C-3-1] (February 5, 2024 preview)

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

Acabar com novos requisitos

• [C-3-2] Cold input latency of 500 milliseconds or less.
• [C-3-3] Opening an input stream using AAudioStreamBuilder_openStream() MUST take less than 1000 milliseconds.

Start new requirements for 15 (AOSP experimental)

[C-SR-8, C-SR-11] (February 5, 2024 preview)

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

• [C-SR-8] Cold input latency of 100 milliseconds or less over the microphone data path.
• [C-SR-11] Limit the error in input timestamps, as returned by AudioRecord.getTimestamp or AAudioStream_getTimestamp , to +/- 1 ms.

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[C-SR-12] (February 5, 2024 preview)

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

• [C-SR-12] Are STRONGLY RECOMMENDED to have a Mean Continuous Round-Trip Latency of 50 milliseconds or less over 5 measurements, with a Mean Absolute Deviation less than 10 msec, over at least one supported path.

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[RTL requirements] (February 5, 2024 preview)

The following table defines the requirements for RTL for Handheld device implementations as defined in 2.2.1 that declare android.hardware.audio.output and android.hardware.microphone .

Device and Declarations	RTL (ms)	MAD (ms)	Loopback Paths
Portátil	250	30	speaker/mic, analog 3.5mm (if supported), USB (if supported)
>= MPC_T (14)	80	15	at least one path
FEATURE_AUDIO_LOW_LATENCY	50	10	at least one path
FEATURE_AUDIO_PRO	25	5	at least one path
FEATURE_AUDIO_PRO	20	5	analog (if supported)
FEATURE_AUDIO_PRO	25	5	USB (if analog not supported)

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[TTL requirements] (February 5, 2024 preview)

The following table defines the requirements for TTL for Handheld device implementations as defined in 2.2.1 that declare android.hardware.audio.output and android.hardware.microphone .

Device and Declarations	TTL (ms)
Portátil	250
>= MPC_T (14)	80
MPC_S (13)	100
FEATURE_AUDIO_PRO	80

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[C-4-1] (February 26, 2024 preview)

If device implementations include support for spatial audio with head tracking and declare the PackageManager.FEATURE_AUDIO_SPATIAL_HEADTRACKING_LOW_LATENCY flag, they:

• [C-4-1] MUST exhibit a maximum head-tracking to audio-update latency of 300ms.

Acabar com novos requisitos

5.7. Protocolos de rede

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

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

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

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

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

Media Segment Formats

Segment formats	Referências)	Required codec support
MPEG-2 Transport Stream	ISO 13818	Video codecs: H264 AVC MPEG-4 SP MPEG-2 See section 5.1.8 for details on H264 AVC, MPEG2-4 SP, e MPEG-2. Audio codecs: AAC See section 5.1.3 for details on AAC and its variants.
AAC with ADTS framing and ID3 tags	ISO 13818-7	See section 5.1.1 for details on AAC and its variants
WebVTT	WebVTT

RTSP (RTP, SDP)

Nome do perfil	Referências)	Required codec support
H264 AVC	RFC 6184	See section 5.1.8 for details on H264 AVC
MP4A-LATM	RFC 6416	See section 5.1.3 for details on AAC and its variants
H263-1998	RFC 3551 RFC 4629 RFC 2190	See section 5.1.8 for details on H263
H263-2000	RFC 4629	See section 5.1.8 for details on H263
RAM	RFC 4867	See section 5.1.3 for details on AMR-NB
AMR-WB	RFC 4867	See section 5.1.3 for details on AMR-WB
MP4V-ES	RFC 6416	See section 5.1.8 for details on MPEG-4 SP
mpeg4-generic	RFC 3640	See section 5.1.3 for details on AAC and its variants
MP2T	RFC 2250	See MPEG-2 Transport Stream underneath HTTP Live Streaming for details

5.8. Secure Media

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

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

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

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

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

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

5.9. Musical Instrument Digital Interface (MIDI)

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

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

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

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

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

• SHOULD support MIDI over USB peripheral mode, section 7.7

5.10. Professional Audio

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

• [C-1-1] MUST report support for feature android.hardware.audio.low_latency .

Start new requirements for 15 (AOSP experimental)

[C-1-2] (February 5, 2024 preview)

• [C-1-2] MUST have the continuous round-trip audio latency , meet the latency requirements for FEATURE_AUDIO_PRO as defined in section 5.6 Audio Latency of 25 milliseconds or less over at least one supported path .

Acabar com novos requisitos

• [C-1-3] MUST include a USB port(s) supporting USB host mode and USB peripheral mode.
• [C-1-4] MUST report support for feature android.software.midi .

Start new requirements for 15 (AOSP experimental)

[C-1-5] (February 5, 2024 preview)

• [C-1-5] MUST meet latencies and USB audio latency requirements using the AAudio native audio API and AAUDIO_PERFORMANCE_MODE_LOW_LATENCY .

Acabar com novos requisitos

• [C-1-6] MUST have Cold output latency of 200 milliseconds or less.
• [C-1-7] MUST have Cold input latency of 200 milliseconds or less.

Start new requirements for 15 (AOSP experimental)

[C-1-8, C-SR-1, C-SR-2, C-SR-3] (February 5, 2024 preview)

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

• [C-SR-3] Are STRONGLY RECOMMENDED to provide a consistent level of CPU performance while audio is active and CPU load is varying. This should be tested using the Android app SynthMark . SynthMark uses a software synthesizer running on a simulated audio framework that measures system performance. See the SynthMark documentation for an explanation of the benchmarks. The SynthMark app needs to be run using the "Automated Test" option and achieve the following results:

  • voicemark.90 >= 32 voices
  • latencymark.fixed.little <= 15 msec
  • latencymark.dynamic.little <= 50 msec

• SHOULD minimize audio clock inaccuracy and drift relative to standard time.

• SHOULD minimize audio clock drift relative to the CPU CLOCK_MONOTONIC when both are active.

• SHOULD minimize audio latency over on-device transducers.

• SHOULD minimize audio latency over USB digital audio.

• SHOULD document audio latency measurements over all paths.

• SHOULD minimize jitter in audio buffer completion callback entry times, as this affects usable percentage of full CPU bandwidth by the callback.

• SHOULD provide zero audio glitches under normal use at reported latency.

• SHOULD provide zero inter-channel latency difference.

• SHOULD minimize MIDI mean latency over all transports.

• SHOULD minimize MIDI latency variability under load (jitter) over all transports.

• SHOULD provide accurate MIDI timestamps over all transports.

• SHOULD minimize audio signal noise over on-device transducers, including the period immediately after cold start.

• SHOULD provide zero audio clock difference between the input and output sides of corresponding end-points, when both are active. Examples of corresponding end-points include the on-device microphone and speaker, or the audio jack input and output.

• SHOULD handle audio buffer completion callbacks for the input and output sides of corresponding end-points on the same thread when both are active, and enter the output callback immediately after the return from the input callback. Or if it is not feasible to handle the callbacks on the same thread, then enter the output callback shortly after entering the input callback to permit the application to have a consistent timing of the input and output sides.

• SHOULD minimize the phase difference between HAL audio buffering for the input and output sides of corresponding end-points.

• SHOULD minimize touch latency.

• SHOULD minimize touch latency variability under load (jitter).

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[C-SR-4] (February 5, 2024 preview)

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

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

Acabar com novos requisitos

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

Start new requirements for 15 (AOSP experimental)

[C-2-1] (February 5, 2024 preview)

• [C-2-1] MUST have a mean Continuous Round-trip Audio Latency, as defined in section 5.6 Audio Latency , of 20 milliseconds or less, over 5 measurements with a Mean Absolute Deviation less than 5 milliseconds over the audio jack path using an Audio Loopback Dongle .

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[C-SR-5] (February 5, 2024 preview)

• [C- SR 2 - 5 2 ] STRONGLY RECOMMENDED to MUST comply with section Mobile device (jack) specifications of the Wired Audio Headset Specification (v1.1) .

Acabar com novos requisitos

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

• [C-3-1] MUST implement the USB audio class.

Start new requirements for 15 (AOSP experimental)

[C-3-2, C-SR-6, C-SR-7] (February 5, 2024 preview)

• [C-3-2] MUST have a mean Continuous Round-trip Audio Latency of 25 milliseconds or less, over 5 measurements with a Mean Absolute Deviation less than 5 milliseconds over the USB host mode port using USB audio class. (This can be measured using a USB-3.5mm adapter and an Audio Loopback Dongle, or using a USB audio interface with patch cables connecting the inputs to outputs).
• [C-SR-6] Are STRONGLY RECOMMENDED to support simultaneous I/O up to 8 channels each direction, 96 kHz sample rate, and 24-bit or 32-bit depth, when used with USB audio peripherals that also support these requirements.
• [C-SR-7] Are STRONGLY RECOMMENDED to meet this group of requirements using the AAudio native audio API over the MMAP path.

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[HDMI port requirement] (February 5, 2024 preview)

If device implementations include an HDMI port, they:

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

Acabar com novos requisitos

5.11. Capture for Unprocessed

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

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

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

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

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

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

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

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

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

• [C-1-8] MUST not have any other signal processing (eg Automatic Gain Control, High Pass Filter, or Echo cancellation) in the path other than a level multiplier to bring the level to desired range. Em outras palavras:

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

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

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

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

5.12. HDR Video

Android 13 supports the HDR technologies as described in an upcoming document.

Pixel Format

If a video decoder advertises support for COLOR_FormatYUVP010, then:

• [C-1-1] MUST support the P010 format for CPU-read (ImageReader, MediaImage, ByteBuffer). In Android 13, P010 is relaxed to allow arbitrary stride for the Y and UV planes.

• [C-1-2] The P010 output buffer MUST be able to be sampled by the GPU (when allocated with GPU_SAMPLING usage). This enables GPU composition and custom tone mapping by apps.

If a video decoder advertises support for COLOR_Format32bitABGR2101010, it:

• [C-2-1] MUST support the RGBA_1010102 format for output surface and CPU-readable (ByteBuffer output).

If a video encoder advertises support for COLOR_FormatYUVP010, it:

• [C-3-1] MUST support the P010 format for input surface and CPU-writeable (ImageWriter, MediaImage, ByteBuffer) input.

Note: In Android 13, P010 is relaxed to allow arbitrary stride for the Y and UV planes. (This P010 format MAY be optimized and different from the Camera2 P010 format.)

If a video encoder advertises support for COLOR_Format32bitABGR2101010, it:

• [C-4-1] MUST support RGBA_1010102 format for input surface and CPU-writeable (ImageWriter, ByteBuffer) input. Note: Converting between various transfer curves is NOT required for encoders.

HDR Capture Requirements

For all video encoders that support HDR profiles, device implementations:

• [C-5-1] MUST NOT assume that the HDR metadata is precise. For example, the encoded frame could have pixels beyond the peak luminance level, or the histogram might not be representative of the frame.

• SHOULD aggregate HDR dynamic metadata to generate appropriate HDR static metadata for encoded streams, and they should output it at the end of each encoding session.

If device implementations support HDR capture using the CamcorderProfile APIs then they:

• [C-6-1] MUST support HDR capture through the Camera2 APIs as well.

• [C-6-2] MUST support at least one hardware-accelerated video encoder for each HDR technology supported.

• [C-6-3] MUST support (at the minimum) HLG capture.

• [C-6-4] MUST support writing the HDR metadata (if applicable to the HDR technology) into the captured video file. For AV1, HEVC, and DolbyVision this means including the metadata into the encoded bitstream.

• [C-6-5] MUST support P010 and COLOR_FormatYUVP010.

• [C-6-6] MUST support HDR to SDR tone mapping in the default hardware-accelerated decoder for the captured profile. In other words, if a device can capture HDR10+ HEVC, the default HEVC decoder MUST be able to decode the captured stream in SDR.

HDR Editing Requirements

If device implementations include video encoders that support HDR editing, then they:

• SHOULD use minimal latency for generating the HDR metadata when not present, and SHOULD gracefully handle situations where the metadata is present for some frames and not for others. This metadata SHOULD be precise (for example, represent the actual peak luminance and histogram of the frame).

If device implementation includes codecs that support FEATURE_HdrEditing, then those codecs:

• [C-7-1] MUST support at least one HDR profile.

• [C-7-2] MUST support FEATURE_HdrEditing for all HDR profiles advertised by that codec. In other words, they MUST support generating HDR metadata when not present for all HDR profiles supported that use HDR metadata.

• [C-7-3] MUST support the following video encoder input formats that fully preserve the HDR decoded signal:

  • RGBA_1010102 (already in the target transfer curve) for both input surface and ByteBuffer and MUST advertise support for COLOR_Format32bitABGR2101010.

If device implementation includes codecs that support FEATURE_HdrEditing, then the device:

• [C-7-4] MUST advertise support for EXT_YUV_target OpenGL extension.

6. Developer Tools and Options Compatibility

6.1. Ferramentas de desenvolvimento

Implementações de dispositivos:

• [C-0-1] MUST support the Android Developer Tools provided in the Android SDK.
• Android Debug Bridge (adb)

Start new requirements for 15 (AOSP experimental)

[C-0-2] (February 5, 2024 preview)

• [C-0-2] MUST support adb as documented in the Android SDK and the shell commands provided in the AOSP, which can be used by app developers, including dumpsys , cmd stats , and Simpleperf .

Acabar com novos requisitos

• [C-0-11] MUST support the shell command cmd testharness . Upgrading device implementations from an earlier Android version without a persistent data block MAY be exempted from C-0-11.
• [C-0-3] MUST NOT alter the format or the contents of device system events (batterystats, diskstats, fingerprint, graphicsstats, netstats, notification, procstats) logged via the dumpsys command.

Start new requirements for 15 (AOSP experimental)

[C-0-10] (December 11, 2023 preview)

• [C-0-10] MUST record, without omission, and make the following events accessible and available to the cmd stats shell command and the StatsManager System API class.
  • ActivityForegroundStateChanged
  • AnomalyDetected
  • AppBreadcrumbReported
  • AppCrashOccurred
  • AppStartOccurred
  • BatteryLevelChanged
  • BatterySaverModeStateChanged
  • BleScanResultReceived
  • BleScanStateChanged
  • ChargingStateChanged
  • DeviceIdleModeStateChanged
  • ForegroundServiceStateChanged
  • GpsScanStateChanged
  • InputDeviceUsageReported
  • JobStateChanged
  • KeyboardConfigured
  • KeyboardSystemsEventReported
  • PluggedStateChanged
  • ScheduledJobStateChanged
  • ScreenStateChanged
  • SyncStateChanged
  • SystemElapsedRealtime
  • TouchpadUsage
  • UidProcessStateChanged
  • WakelockStateChanged
  • WakeupAlarmOccurred
  • WifiLockStateChanged
  • WifiMulticastLockStateChanged
  • WifiScanStateChanged

Acabar com novos requisitos

• [C-0-4] MUST have the device-side adb daemon be inactive by default and there MUST be a user-accessible mechanism to turn on the Android Debug Bridge.
• [C-0-5] MUST support secure adb. Android includes support for secure adb. Secure adb enables adb on known authenticated hosts.
• [C-0-6] MUST provide a mechanism allowing adb to be connected from a host machine. Especificamente:

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

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

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

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

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

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

• Dalvik Debug Monitor Service (ddms)

  • [C-0-7] MUST support all ddms features as documented in the Android SDK. As ddms uses adb, support for ddms SHOULD be inactive by default, but MUST be supported whenever the user has activated the Android Debug Bridge, as above.

• SysTrace

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

• Perfeito

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

• Low Memory Killer

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

• Test Harness Mode If device implementations support the shell command cmd testharness and run cmd testharness enable , they:

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

• GPU work information

  Implementações de dispositivos:

  • [C-0-13] MUST implement the shell command dumpsys gpu --gpuwork to display the aggregated GPU work data returned by the power/gpu_work_period kernel tracepoint, or display no data if the tracepoint is not supported. The AOSP implementation is frameworks/native/services/gpuservice/gpuwork/ .

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

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

6.2. Opções de desenvolvedor

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

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

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

7. Hardware Compatibility

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

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

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

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

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

7.1. Display and Graphics

Android includes facilities that automatically adjust application assets and UI layouts appropriately for the device to ensure that third-party applications run well on a variety of hardware displays and configurations. An Android-compatible display is a display screen that implements all of the behaviors and APIs described in Android Developers - Screen compatibility overview , this section (7.1) and its subsections, as well as any additional device-type specific behaviors documented in section 2 of this CDD.

Implementações de dispositivos:

• [C-0-1] MUST, by default, render third party applications only onto Android-compatible displays.

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.
• densidade . The number of pixels encompassed by a linear horizontal or vertical span of 1", expressed as pixels per inch (ppi or dpi). Where ppi and dpi values are listed, both horizontal and vertical dpi must fall within the listed range.
• proporção da tela . 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) . A virtual pixel unit normalized to a screen density of 160. For some density d, and a number of pixels p, the number of density-independent pixels dp, is calculated as: dp = (160 / d) * p.

7.1.1. Screen Configuration

7.1.1.1. Screen Size and Shape

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

Implementações de dispositivos:

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

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

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

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

If device implementations support screens capable of the UI_MODE_TYPE_NORMAL size configuration and use physical display(s) with rounded corners to render these screens, they:

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

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

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

If device implementations are only capable of NO_KEYS keyboard configuration, and intend to report support for the UI_MODE_TYPE_NORMAL ui mode configuration, they:

• [C-4-1] MUST have a layout size, excluding any display cutouts, of at least 596 dp x 384 dp or greater.

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

Start new requirements for 15 (AOSP experimental)

[C-4-1] (February 5, 2024 preview)

If device implementations include one or more Android-compatible display areas that are foldable, or include a folding hinge between multiple Android-compatible display panel areas and make such display areas available to applications, they:

• [C-4-1] MUST implement the correct version of the Window Manager Extensions API level as described in WindowManager Extensions .

Acabar com novos requisitos

7.1.1.2. Screen Aspect Ratio

This section was deleted in Android 14.

7.1.1.3. Screen Density

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

Device Implementations:

• [C-0-1] MUST report one of the Android framework densities that are listed on DisplayMetrics through the DENSITY_DEVICE_STABLE API and this value must be a static value for each physical display. However the device MAY report a different DisplayMetrics.density according to the display configuration changes made by the user (for example, display size) set after initial boot.

• SHOULD define the standard Android framework density that is numerically closest to the physical density of the screen, or a value that would map to the same equivalent angular field-of-view measurements of a handheld device.

If device implementations provide an affordance to change the display size of the device, they:

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

Start new requirements for 15 (AOSP experimental)

7.1.1.4. Display Overrides

[Withdrawn] 7.1.1.4 (February 26, 2024 preview)

These requirements are withdrawn from Android 15 (AOSP experimental).

Acabar com novos requisitos

7.1.1.4 (February 5, 2024 preview)

Device implementations MAY provide user affordance to override application-specific display settings via per-app override APIs or a proprietary mechanism.

If device implementations provide one or more user affordances to override the application-specific display settings (such as screenOrientation , Activity#setRequestedOrientation() , resizeableActivity , minAspectRatio , and maxAspectRatio ), they:

• [C-1-1] MUST obtain user consent and provide an explicit indication that any override might result in unexpected application display or other user experience issues.
• [C-1-2] MUST clearly indicate how to revert such overrides.
• [C-1-3] MUST provide similarly accessible user affordances to revert such overrides.
• [C-1-4] MUST NOT allow users to override apps in bulk actions.
• [C-1-5] MUST respect APIs that disable overrides .

Acabar com novos requisitos

7.1.2. Display Metrics

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

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

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

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

7.1.3. Orientação da tela

Implementações de dispositivos:

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

If device implementations support both screen orientations, they:

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

7.1.4. 2D and 3D Graphics Acceleration

7.1.4.1. OpenGL ES

Implementações de dispositivos:

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

Start new requirements for 15 (AOSP experimental)

[Moved] [C-0-3 and C-0-4] (February 26, 2024 preview)

These requirements are moved from CDD to GMS section 3.2.9 OpenGL ES (ANGLE) .

Acabar com novos requisitos

[C-0-3 and C-0-4] (February 5, 2024 preview)

If device implementations return false for ActivityManager.isLowRamDevice() , they:

• [C-0-3] MUST include the ANGLE libraries libEGL_angle.so , libGLESv1_CM_angle.so , and libGLESv2_angle.so . Note: the AOSP reference code includes these binaries by default in the /system/${LIB} directories.
• [C-0-4] MUST provide a developer option under Settings an affordance for application developers to enable and disable the ANGLE libraries as replacements for the native OpenGL ES driver. This provision is for developer testing purposes and can be This replacement setting MUST be disabled by default.

Acabar com novos requisitos

[C-0-3 and C-0-4] (December 11, 2023 preview)

• [C-0-3] MUST include the ANGLE libraries libEGL_angle.so , libGLESv1_CM_angle.so , and libGLESv2_angle.so . Note: The AOSP reference code includes these binaries by default in the /system/${LIB} directories.
• [C-0-4] MUST provide a developer option under Settings to enable and disable the ANGLE libraries as replacements for the native OpenGL ES driver. This provision is for developer testing purposes and can be disabled by default.

Acabar com novos requisitos

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

Start new requirements for 15 (AOSP experimental)

[C-1-1] (December 11, 2023 preview)

• [C-1-1] MUST support both OpenGL ES 1.1, and 2.0, 3.0, and 3.1, as embodied and detailed in the Android SDK documentation .

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[C-SR-1] (December 11, 2023 preview)

• [C-SR-1] Are STRONGLY RECOMMENDED to support OpenGL ES 3.1.

Acabar com novos requisitos

• SHOULD support OpenGL ES 3.2.

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

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

• [C-2-1] MUST report via the OpenGL ES managed APIs and native APIs any other OpenGL ES extensions they have implemented, and conversely MUST NOT report extension strings that they do not support.
• [C-2-2] MUST support the EGL_KHR_image , EGL_KHR_image_base , EGL_ANDROID_image_native_buffer , EGL_ANDROID_get_native_client_buffer , EGL_KHR_wait_sync , EGL_KHR_get_all_proc_addresses , EGL_ANDROID_presentation_time , EGL_KHR_swap_buffers_with_damage , EGL_ANDROID_recordable , and EGL_ANDROID_GLES_layers extensions.
• [C-2-3] MUST report the maximum version of the OpenGL ES dEQP tests supported via the android.software.opengles.deqp.level feature flag.
• [C-2-4] MUST at least support version 132383489 (from Mar 1st, 2020) as reported in the android.software.opengles.deqp.level feature flag.
• [C-2-5] MUST pass all OpenGL ES dEQP Tests in the test lists between version 132383489 and the version specified in the android.software.opengles.deqp.level feature flag, for each supported OpenGL ES version.
• [C-SR-2] Are STRONGLY RECOMMENDED to support the EGL_KHR_partial_update and OES_EGL_image_external extensions.

• SHOULD accurately report via the getString() method, any texture compression format that they support, which is typically vendor-specific.

• SHOULD support the EGL_IMG_context_priority and EGL_EXT_protected_content extensions.

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

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

If device implementations support OpenGL ES 3.2, they:

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

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

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

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

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

7.1.4.2. Vulcano

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

If device implementations support OpenGL ES 3.1, they:

• [C-SR-1] Are STRONGLY RECOMMENDED to include support for Vulkan 1.3.
• [C-4-1] MUST NOT support a Vulkan variant version (ie the variant part of the Vulkan core version MUST be zero).

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

• [C-SR-2] Are STRONGLY RECOMMENDED to include support for Vulkan 1.3.

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

If device implementations include support for Vulkan, they:

• [C-1-1] MUST report the correct integer value with the android.hardware.vulkan.level and android.hardware.vulkan.version feature flags.
• [C-1-2] MUST enumerate, at least one VkPhysicalDevice for the Vulkan native API vkEnumeratePhysicalDevices() .
• [C-1-3] MUST fully implement the Vulkan 1.1 APIs for each enumerated VkPhysicalDevice .
• [C-1-4] MUST enumerate layers, contained in native libraries named as libVkLayer*.so in the application package's native library directory, through the Vulkan native APIs vkEnumerateInstanceLayerProperties() and vkEnumerateDeviceLayerProperties() .
• [C-1-5] MUST NOT enumerate layers provided by libraries outside of the application package, or provide other ways of tracing or intercepting the Vulkan API, unless the application has the android:debuggable attribute set as true or the metadata com.android.graphics.injectLayers.enable set to true .
• [C-1-6] MUST report all extension strings that they do support via the Vulkan native APIs , and conversely MUST NOT report extension strings that they do not correctly support.
• [C-1-7] MUST support the VK_KHR_surface, VK_KHR_android_surface, VK_KHR_swapchain, and VK_KHR_incremental_present extensions.
• [C-1-8] MUST report the maximum version of the Vulkan dEQP Tests supported via the android.software.vulkan.deqp.level feature flag.
• [C-1-9] MUST at least support version 132317953 (from Mar 1st, 2019) as reported in the android.software.vulkan.deqp.level feature flag.
• [C-1-10] MUST pass all Vulkan dEQP Tests in the test lists between version 132317953 and the version specified in the android.software.vulkan.deqp.level feature flag.
• [C-1-11] MUST NOT enumerate support for the VK_KHR_video_queue, VK_KHR_video_decode_queue, or VK_KHR_video_encode_queue extensions.
• [C-SR-3] Are STRONGLY RECOMMENDED to support the VK_KHR_driver_properties and VK_GOOGLE_display_timing extensions.
• [C-1-12] MUST NOT enumerate support for the VK_KHR_performance_query extension.
• [C-1-13] MUST satisfy the requirements specified by the Android Baseline 2021 profile .
• [C-SR-4] Are STRONGLY RECOMMENDED to satisfy the requirements specified by the Android Baseline 2022 profile .
• [C-SR-5] Are STRONGLY RECOMMENDED to support VkPhysicalDeviceProtectedMemoryFeatures.protectedMemory and VK_EXT_global_priority .
• [C-SR-6] Are STRONGLY RECOMMENDED to use SkiaVk with HWUI.

Start new requirements for 15 (AOSP experimental)

[C-SR-8 and C-1-14] (December 11, 2023 preview)

If device implementations include support for Vulkan, then they:

• [C-SR-8] Are STRONGLY RECOMMENDED to not modify the Vulkan loader.
• [C-1-14] MUST NOT enumerate Vulkan Device extensions of type "KHR", "GOOGLE", or "ANDROID" unless these extensions are included in the android.software.vulkan.deqp.level feature flag.

Note: C-SR-8 will become a MUST in Android 16.

Acabar com novos requisitos

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

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

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

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

• [C-SR-7] Are STRONGLY RECOMMENDED to make the VK_KHR_external_fence_fd extension available to third-party applications and enable the application to export fence payload to and import fence payload from POSIX file descriptors as described here .

7.1.4.3. RenderScript

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

7.1.4.4. 2D Graphics Acceleration

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

Implementações de dispositivos:

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

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

Implementações de dispositivos:

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

7.1.4.5. Wide-gamut Displays

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

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

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

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

7.1.5. Legacy Application Compatibility Mode

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

7.1.6. Screen Technology

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

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

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

7.1.7. Secondary Displays

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

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

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

7.2. Dispositivos de entrada

Implementações de dispositivos:

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

7.2.1. Teclado

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

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

Implementações de dispositivos:

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

7.2.2. Non-touch Navigation

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

Implementações de dispositivos:

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

If device implementations lack non-touch navigations, they:

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

7.2.3. Navigation Keys

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

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

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

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

Implementações de dispositivos:

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

• [C-SR-2] Are STRONGLY RECOMMENDED to provide all navigation functions as cancellable. 'Cancellable' is defined as the user's ability to prevent the navigation function from executing (eg going home, going back, etc.) if the swipe is not released past a certain threshold.

If device implementations provide the Menu function, they:

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

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

If device implementations provide the Assist function , they:

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

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

• [C-5-1] Navigation keys MUST use a distinct portion of the screen, not available to applications, and MUST NOT obscure or otherwise interfere with the portion of the screen available to applications.
• [C-5-2] MUST make available a portion of the display to applications that meets the requirements defined in section 7.1.1 .
• [C-5-3] MUST honor the flags set by the app through the View.setSystemUiVisibility() API method, so that this distinct portion of the screen (aka the navigation bar) is properly hidden away as documented in the SDK.

Se a função de navegação for fornecida como uma ação baseada em gestos na tela:

• [C-6-1] WindowInsets#getMandatorySystemGestureInsets() MUST only be used to report the Home gesture recognition area.
• [C-6-2] Gestures that start within an exclusion rect as provided by the foreground application via View#setSystemGestureExclusionRects() , but outside of WindowInsets#getMandatorySystemGestureInsets() , MUST NOT be intercepted for the navigation function as long as the exclusion rect is allowed within the max exclusion limit as specified in the documentation for View#setSystemGestureExclusionRects() .
• [C-6-3] MUST send the foreground app a MotionEvent.ACTION_CANCEL event once touches start being intercepted for a system gesture, if the foreground app was previously sent an MotionEvent.ACTION_DOWN event.
• [C-6-4] MUST provide a user affordance to switch to an on-screen, button-based navigation (for example, in Settings).
• SHOULD provide Home function as a swipe up from the bottom edge of the current orientation of the screen.
• SHOULD provide Recents function as a swipe up and hold before release, from the same area as the Home gesture.
• Gestures that start within WindowInsets#getMandatorySystemGestureInsets() SHOULD NOT be affected by exclusion rects provided by the foreground application via View#setSystemGestureExclusionRects() .

If a navigation function is provided from anywhere on the left and right edges of the current orientation of the screen:

• [C-7-1] The navigation function MUST be Back and provided as a swipe from both left and right edges of the current orientation of the screen.
• [C-7-2] If custom swipeable system panels are provided on the left or right edges, they MUST be placed within the top 1/3rd of the screen with a clear, persistent visual indication that dragging in would invoke the aforementioned panels, and hence not Back. A system panel MAY be configured by a user such that it lands below the top 1/3rd of the screen edge(s) but the system panel MUST NOT use longer than 1/3rd of the edge(s).
• [C-7-3] When the foreground app has either the View.SYSTEM_UI_FLAG_IMMERSIVE, View.SYSTEM_UI_FLAG_IMMERSIVE_STICKY, WindowInsetsController.BEHAVIOR_DEFAULT, or WindowInsetsController.BEHAVIOR_SHOW_TRANSIENT_BARS_BY_SWIPE flags set, swiping from the edges MUST behave as implemented in AOSP, which is documented in the SDK .
• [C-7-4] When the foreground app has either the View.SYSTEM_UI_FLAG_IMMERSIVE, View.SYSTEM_UI_FLAG_IMMERSIVE_STICKY, WindowInsetsController.BEHAVIOR_DEFAULT, or WindowInsetsController.BEHAVIOR_SHOW_TRANSIENT_BARS_BY_SWIPE flags set, custom swipeable system panels MUST be hidden until the user brings in or un-dims the system bars (aka navigation and status bar) as implemented in AOSP.

If the back navigation function is provided and the user cancels the Back gesture, then:

• [C-8-1] OnBackInvokedCallback.onBackCancelled() MUST be called.
• [C-8-2] OnBackInvokedCallback.onBackInvoked() MUST NOT be called.
• [C-8-3] KEYCODE_BACK event MUST NOT be dispatched.

If the back navigation function is provided but the foreground application does NOT have an OnBackInvokedCallback registered, then:

• The system SHOULD provide an animation for the foreground application that suggests that the user is going back, as provided in AOSP.

If device implementations provide support for the system API setNavBarMode to allow any system app with android.permission.STATUS_BAR permission to set the navigation bar mode, then they:

• [C-9-1] MUST provide support for kid-friendly icons or button-based navigation as provided in the AOSP code.

7.2.4. Touchscreen Input

Android includes support for a variety of pointer input systems, such as touchscreens, touch pads, and fake touch input devices. Touchscreen-based device implementations are associated with a display such that the user has the impression of directly manipulating items on screen. Since the user is directly touching the screen, the system does not require any additional affordances to indicate the objects being manipulated.

Implementações de dispositivos:

• SHOULD have a pointer input system of some kind (either mouse-like or touch).
• SHOULD support fully independently tracked pointers.

If device implementations include a touchscreen (single-touch or better) on a primary Android-compatible display, they:

• [C-1-1] MUST report TOUCHSCREEN_FINGER for the Configuration.touchscreen API field.
• [C-1-2] MUST report the android.hardware.touchscreen and android.hardware.faketouch feature flags.

If device implementations include a touchscreen that can track more than a single touch on a primary Android-compatible display, they:

• [C-2-1] MUST report the appropriate feature flags android.hardware.touchscreen.multitouch , android.hardware.touchscreen.multitouch.distinct , android.hardware.touchscreen.multitouch.jazzhand corresponding to the type of the specific touchscreen on the dispositivo.

If device implementations rely on an external input device such as mouse or trackball (ie not directly touching the screen) for input on a primary Android-compatible display and meet the fake touch requirements in section 7.2.5 , they:

• [C-3-1] MUST NOT report any feature flag starting with android.hardware.touchscreen .
• [C-3-2] MUST report only android.hardware.faketouch .
• [C-3-3] MUST report TOUCHSCREEN_NOTOUCH for the Configuration.touchscreen API field.

7.2.5. Fake Touch Input

Fake touch interface provides a user input system that approximates a subset of touchscreen capabilities. For example, a mouse or remote control that drives an on-screen cursor approximates touch, but requires the user to first point or focus then click. Numerous input devices like the mouse, trackpad, gyro-based air mouse, gyro-pointer, joystick, and multi-touch trackpad can support fake touch interactions. Android includes the feature constant android.hardware.faketouch, which corresponds to a high-fidelity non-touch (pointer-based) input device such as a mouse or trackpad that can adequately emulate touch-based input (including basic gesture support), and indicates that the device supports an emulated subset of touchscreen functionality.

If device implementations do not include a touchscreen but include another pointer input system which they want to make available, they:

• SHOULD declare support for the android.hardware.faketouch feature flag.

If device implementations declare support for android.hardware.faketouch , they:

• [C-1-1] MUST report the absolute X and Y screen positions of the pointer location and display a visual pointer on the screen.
• [C-1-2] MUST report touch event with the action code that specifies the state change that occurs on the pointer going down or up on the screen .
• [C-1-3] MUST support pointer down and up on an object on the screen, which allows users to emulate tap on an object on the screen.
• [C-1-4] MUST support pointer down, pointer up, pointer down then pointer up in the same place on an object on the screen within a time threshold, which allows users to emulate double tap on an object on the screen.
• [C-1-5] MUST support pointer down on an arbitrary point on the screen, pointer move to any other arbitrary point on the screen, followed by a pointer up, which allows users to emulate a touch drag.
• [C-1-6] MUST support pointer down then allow users to quickly move the object to a different position on the screen and then pointer up on the screen, which allows users to fling an object on the screen.

If device implementations declare support for android.hardware.faketouch.multitouch.distinct , they:

• [C-2-1] MUST declare support for android.hardware.faketouch .
• [C-2-2] MUST support distinct tracking of two or more independent pointer inputs.

If device implementations declare support for android.hardware.faketouch.multitouch.jazzhand , they:

• [C-3-1] MUST declare support for android.hardware.faketouch .
• [C-3-2] MUST support distinct tracking of 5 (tracking a hand of fingers) or more pointer inputs fully independently.

7.2.6. Game Controller Support

7.2.6.1. Button Mappings

Implementações de dispositivos:

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

If device implementations embed a controller or ship with a separate controller in the box that would provide means to input all the events listed in the below tables, they:

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

Botão	HID Usage ^2	Android Button
Um ^1	0x09 0x0001	KEYCODE_BUTTON_A (96)
B1^​	0x09 0x0002	KEYCODE_BUTTON_B (97)
X ^1	0x09 0x0004	KEYCODE_BUTTON_X (99)
S ^1	0x09 0x0005	KEYCODE_BUTTON_Y (100)
D-pad up ^1 D-pad down ^1	0x01 0x0039 ^3	AXIS_HAT_Y ^4
D-pad left 1 D-pad right ^1	0x01 0x0039 ^3	AXIS_HAT_X ^4
Left shoulder button ^1	0x09 0x0007	KEYCODE_BUTTON_L1 (102)
Right shoulder button ^1	0x09 0x0008	KEYCODE_BUTTON_R1 (103)
Left stick click ^1	0x09 0x000E	KEYCODE_BUTTON_THUMBL (106)
Right stick click ^1	0x09 0x000F	KEYCODE_BUTTON_THUMBR (107)
Back ^1	0x0c 0x0224	KEYCODE_BACK (4)

1 KeyEvent

2 The above HID usages must be declared within a Game pad CA (0x01 0x0005).

3 This usage must have a Logical Minimum of 0, a Logical Maximum of 7, a Physical Minimum of 0, a Physical Maximum of 315, Units in Degrees, and a Report Size of 4. The logical value is defined to be the clockwise rotation away from the vertical axis; for example, a logical value of 0 represents no rotation and the up button being pressed, while a logical value of 1 represents a rotation of 45 degrees and both the up and left keys being pressed.

4 MotionEvent

Analog Controls ^1	HID Usage	Android Button
Gatilho esquerdo	0x02 0x00C5	AXIS_LTRIGGER
Gatilho direito	0x02 0x00C4	AXIS_RTRIGGER
Left Joystick	0x01 0x0030 0x01 0x0031	AXIS_X AXIS_Y
Right Joystick	0x01 0x0032 0x01 0x0035	AXIS_Z AXIS_RZ

1 MotionEvent

7.2.7. Controle remoto

See Section 2.3.1 for device-specific requirements.

7.3. Sensores

If device implementations include a particular sensor type that has a corresponding API for third-party developers, the device implementation MUST implement that API as described in the Android SDK documentation and the Android Open Source documentation on sensors .

Implementações de dispositivos:

• [C-0-1] MUST accurately report the presence or absence of sensors per the android.content.pm.PackageManager class.
• [C-0-2] MUST return an accurate list of supported sensors via the SensorManager.getSensorList() and similar methods.
• [C-0-3] MUST behave reasonably for all other sensor APIs (for example, by returning true or false as appropriate when applications attempt to register listeners, not calling sensor listeners when the corresponding sensors are not present; etc.).

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

• [C-1-1] MUST report all sensor measurements using the relevant International System of Units (metric) values for each sensor type as defined in the Android SDK documentation.
• [C-1-2] MUST report sensor data with a maximum latency of 100 milliseconds + 2 * sample_time for the case of a sensor stream with a maximum requested latency of 0 ms when the application processor is active. This delay does not include any filtering delays.
• [C-1-3] MUST report the first sensor sample within 400 milliseconds + 2 * sample_time of the sensor being activated. It is acceptable for this sample to have an accuracy of 0.
• [C-1-4] For any API indicated by the Android SDK documentation to be a continuous sensor , device implementations MUST continuously provide periodic data samples that SHOULD have a jitter below 3%, where jitter is defined as the standard deviation of the difference of the reported timestamp values between consecutive events.
• [C-1-5] MUST ensure that the sensor event stream MUST NOT prevent the device CPU from entering a suspend state or waking up from a suspend state.
• [C-1-6] MUST report the event time in nanoseconds as defined in the Android SDK documentation, representing the time the event happened and synchronized with the SystemClock.elapsedRealtimeNano() clock.
• [C-SR-1] Are STRONGLY RECOMMENDED to have timestamp synchronization error below 100 milliseconds, and SHOULD have timestamp synchronization error below 1 millisecond.
• When several sensors are activated, the power consumption SHOULD NOT exceed the sum of the individual sensor's reported power consumption.

The list above is not comprehensive; the documented behavior of the Android SDK and the Android Open Source Documentations on sensors is to be considered authoritative.

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

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

Some sensor types are composite, meaning they can be derived from data provided by one or more other sensors. (Examples include the orientation sensor and the linear acceleration sensor.)

Implementações de dispositivos:

• SHOULD implement these sensor types, when they include the prerequisite physical sensors as described in sensor types .

If device implementations include a composite sensor, they:

• [C-2-1] MUST implement the sensor as described in the Android Open Source documentation on composite sensors .

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

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

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

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

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

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

7.3.1. Acelerômetro

Implementações de dispositivos:

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

If device implementations include an accelerometer, they:

• [C-1-1] MUST be able to report events up to a frequency of at least 50 Hz.
• [C-1-3] MUST comply with the Android sensor coordinate system as detailed in the Android APIs.
• [C-1-4] MUST be capable of measuring from freefall up to four times the gravity(4g) or more on any axis.
• [C-1-5] MUST have a resolution of at least 12-bits.
• [C-1-6] MUST have a standard deviation no greater than 0.05 m/s^, where the standard deviation should be calculated on a per axis basis on samples collected over a period of at least 3 seconds at the fastest sampling rate.
• SHOULD report events up to at least 200 Hz.
• SHOULD have a resolution of at least 16-bits.
• SHOULD be calibrated while in use if the characteristics changes over the life cycle and compensated, and preserve the compensation parameters between device reboots.
• SHOULD be temperature compensated.

Se as implementações do dispositivo incluirem um acelerômetro de 3 eixos, eles:

• [C-2-1] MUST implement and report TYPE_ACCELEROMETER sensor.
• [C-SR-4] Are STRONGLY RECOMMENDED to implement the TYPE_SIGNIFICANT_MOTION composite sensor.
• [C-SR-5] Are STRONGLY RECOMMENDED to implement and report TYPE_ACCELEROMETER_UNCALIBRATED sensor. Android devices are STRONGLY RECOMMENDED to meet this requirement so they will be able to upgrade to the future platform release where this might become REQUIRED.
• SHOULD implement the TYPE_SIGNIFICANT_MOTION , TYPE_TILT_DETECTOR , TYPE_STEP_DETECTOR , TYPE_STEP_COUNTER composite sensors as described in the Android SDK document.

If device implementations include an accelerometer with less than 3 axes, they:

• [C-3-1] MUST implement and report TYPE_ACCELEROMETER_LIMITED_AXES sensor.
• [C-SR-6] Are STRONGLY_RECOMMENDED to implement and report TYPE_ACCELEROMETER_LIMITED_AXES_UNCALIBRATED sensor.

If device implementations include a 3-axis accelerometer and any of the TYPE_SIGNIFICANT_MOTION , TYPE_TILT_DETECTOR , TYPE_STEP_DETECTOR , TYPE_STEP_COUNTER composite sensors are implemented:

• [C-4-1] The sum of their power consumption MUST always be less than 4 mW.
• SHOULD each be below 2 mW and 0.5 mW for when the device is in a dynamic or static condition.

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

• [C-5-1] MUST implement the TYPE_GRAVITY and TYPE_LINEAR_ACCELERATION composite sensors.
• [C-SR-7] Are STRONGLY RECOMMENDED to implement the TYPE_GAME_ROTATION_VECTOR composite sensor.

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

• [C-6-1] MUST implement a TYPE_ROTATION_VECTOR composite sensor.

7.3.2. Magnetômetro

Implementações de dispositivos:

• [C-SR-1] Are STRONGLY RECOMMENDED to include a 3-axis magnetometer (compass).

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

• [C-1-1] MUST implement the TYPE_MAGNETIC_FIELD sensor.
• [C-1-2] MUST be able to report events up to a frequency of at least 10 Hz and SHOULD report events up to at least 50 Hz.
• [C-1-3] MUST comply with the Android sensor coordinate system as detailed in the Android APIs.
• [C-1-4] MUST be capable of measuring between -900 µT and +900 µT on each axis before saturating.
• [C-1-5] MUST have a hard iron offset value less than 700 µT and SHOULD have a value below 200 µT, by placing the magnetometer far from dynamic (current-induced) and static (magnet-induced) magnetic fields.
• [C-1-6] MUST have a resolution equal or denser than 0.6 µT.
• [C-1-7] MUST support online calibration and compensation of the hard iron bias, and preserve the compensation parameters between device reboots.
• [C-1-8] MUST have the soft iron compensation applied—the calibration can be done either while in use or during the production of the device.
• [C-1-9] MUST have a standard deviation, calculated on a per axis basis on samples collected over a period of at least 3 seconds at the fastest sampling rate, no greater than 1.5 µT; SHOULD have a standard deviation no greater than 0.5 µT.
• [C-1-10] MUST implement the TYPE_MAGNETIC_FIELD_UNCALIBRATED sensor.

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

• [C-2-1] MUST implement a TYPE_ROTATION_VECTOR composite sensor.

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

• MAY implement the TYPE_GEOMAGNETIC_ROTATION_VECTOR sensor.

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

• [C-3-1] MUST consume less than 10 mW.
• SHOULD consume less than 3 mW when the sensor is registered for batch mode at 10 Hz.

7.3.3. GPS

Implementações de dispositivos:

• [C-SR-1] Are STRONGLY RECOMMENDED to include a GPS/GNSS receiver.

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

• [C-1-1] MUST support location outputs at a rate of at least 1 Hz when requested via LocationManager#requestLocationUpdate .
• [C-1-2] MUST be able to determine the location in open-sky conditions (strong signals, negligible multipath, HDOP < 2) within 10 seconds (fast time to first fix), when connected to a 0.5 Mbps or faster data speed internet connection. This requirement is typically met by the use of some form of Assisted or Predicted GPS/GNSS technique to minimize GPS/GNSS lock-on time (Assistance data includes Reference Time, Reference Location and Satellite Ephemeris/Clock).
  • [C-1-6] After making such a location calculation, device implementations MUST determine its location, in open sky, within 5 seconds, when location requests are restarted, up to an hour after the initial location calculation, even when the subsequent request is made without a data connection, and/or after a power cycle.

• In open sky conditions after determining the location, while stationary or moving with less than 1 meter per second squared of acceleration:

  • [C-1-3] MUST be able to determine location within 20 meters, and speed within 0.5 meters per second, at least 95% of the time.
  • [C-1-4] MUST simultaneously track and report via GnssStatus.Callback at least 8 satellites from one constellation.
  • SHOULD be able to simultaneously track at least 24 satellites, from multiple constellations (eg GPS + at least one of Glonass, Beidou, Galileo).

• [C-SR-2] Are STRONGLY RECOMMENDED to continue to deliver normal GPS/GNSS location outputs through GNSS Location Provider API's during an emergency phone call.

• [C-SR-3] Are STRONGLY RECOMMENDED to report GNSS measurements from all constellations tracked (as reported in GnssStatus messages), with the exception of SBAS.

• [C-SR-4] Are STRONGLY RECOMMENDED to report AGC, and Frequency of GNSS measurement.

• [C-SR-5] Are STRONGLY RECOMMENDED to report all accuracy estimates (including Bearing, Speed, and Vertical) as part of each GPS/GNSS location.

• [C-SR-6] Are STRONGLY RECOMMENDED to report GNSS measurements, as soon as they are found, even if a location calculated from GPS/GNSS is not yet reported.

• [C-SR-7] Are STRONGLY RECOMMENDED to report GNSS pseudoranges and pseudorange rates, that, in open-sky conditions after determining the location, while stationary or moving with less than 0.2 meter per second squared of acceleration, are sufficient to calculate position within 20 meters, and speed within 0.2 meters per second, at least 95% of the time.

7.3.4. Giroscópio

Implementações de dispositivos:

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

If device implementations include a gyroscope, they:

• [C-1-1] MUST be able to report events up to a frequency of at least 50 Hz.
• [C-1-4] MUST have a resolution of 12-bits or more.
• [C-1-5] MUST be temperature compensated.
• [C-1-6] MUST be calibrated and compensated while in use, and preserve the compensation parameters between device reboots.
• [C-1-7] MUST have a variance no greater than 1e-7 rad^2 / s^2 per Hz (variance per Hz, or rad^2 / s). The variance is allowed to vary with the sampling rate, but MUST be constrained by this value. In other words, if you measure the variance of the gyro at 1 Hz sampling rate it SHOULD be no greater than 1e-7 rad^2/s^2.
• [C-SR-2] Calibration error is STRONGLY RECOMMENDED to be less than 0.01 rad/s when device is stationary at room temperature.
• [C-SR-3] Are STRONGLY RECOMMENDED to have a resolution of 16-bits or more.
• SHOULD report events up to at least 200 Hz.

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

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

If device implementations include a gyroscope with less than 3 axes, they:

• [C-3-1] MUST implement and report TYPE_GYROSCOPE_LIMITED_AXES sensor.
• [C-SR-5] Are STRONGLY_RECOMMENDED to implement and report TYPE_GYROSCOPE_LIMITED_AXES_UNCALIBRATED sensor.

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

• [C-4-1] MUST implement a TYPE_ROTATION_VECTOR composite sensor.

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

• [C-5-1] MUST implement the TYPE_GRAVITY and TYPE_LINEAR_ACCELERATION composite sensors.
• [C-SR-6] Are STRONGLY RECOMMENDED to implement the TYPE_GAME_ROTATION_VECTOR composite sensor.

7.3.5. Barômetro

Implementações de dispositivos:

• [C-SR-1] Are STRONGLY RECOMMENDED to include a barometer (ambient air pressure sensor).

If device implementations include a barometer, they:

• [C-1-1] MUST implement and report TYPE_PRESSURE sensor.
• [C-1-2] MUST be able to deliver events at 5 Hz or greater.
• [C-1-3] MUST be temperature compensated.
• [C-SR-2] STRONGLY RECOMMENDED to be able to report pressure measurements in the range 300hPa to 1100hPa.
• SHOULD have an absolute accuracy of 1hPa.
• SHOULD have a relative accuracy of 0.12hPa over 20hPa range (equivalent to ~1m accuracy over ~200m change at sea level).

7.3.6. Termômetro

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

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

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

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

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

• [C-SR-1] Are STRONGLY RECOMMENDED to support the PowerManager.getThermalHeadroom API.

7.3.7. Fotômetro

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

7.3.8. Sensor de proximidade

• Device implementations MAY include a proximity sensor.

If device implementations include a proximity sensor and they report only a binary "near" or "far" reading, they:

• [C-1-1] MUST measure the proximity of an object in the same direction as the screen. That is, the proximity sensor MUST be oriented to detect objects close to the screen, as the primary intent of this sensor type is to detect a phone in use by the user. If device implementations include a proximity sensor with any other orientation, it MUST NOT be accessible through this API.
• [C-1-2] MUST have 1-bit of accuracy or more.
• [C-1-3] MUST use 0 centimeters as the near reading and 5 centimeters as the far reading.
• [C-1-4] MUST report a maximum range and resolution of 5.

7.3.9. High Fidelity Sensors

If device implementations include a set of higher quality sensors as defined in this section, and make available them to third-party apps, they:

• [C-1-1] MUST identify the capability through the android.hardware.sensor.hifi_sensors feature flag.

If device implementations declare android.hardware.sensor.hifi_sensors , they:

• [C-2-1] MUST have a TYPE_ACCELEROMETER sensor which:

  • MUST have a measurement range between at least -8g and +8g, and is STRONGLY RECOMMENDED to have a measurement range between at least -16g and +16g.
  • MUST have a measurement resolution of at least 2048 LSB/g.
  • MUST have a minimum measurement frequency of 12.5 Hz or lower.
  • MUST have a maximum measurement frequency of 400 Hz or higher; SHOULD support the SensorDirectChannel RATE_VERY_FAST .
  • MUST have a measurement noise not above 400 μg/√Hz.
  • MUST implement a non-wake-up form of this sensor with a buffering capability of at least 3000 sensor events.
  • MUST have a batching power consumption not worse than 3 mW.
  • [C-SR-1] Is STRONGLY RECOMMENDED to have 3dB measurement bandwidth of at least 80% of Nyquist frequency, and white noise spectrum within this bandwidth.
  • SHOULD have an acceleration random walk less than 30 μg √Hz tested at room temperature.
  • SHOULD have a bias change vs. temperature of ≤ +/- 1 mg/°C.
  • SHOULD have a best-fit line non-linearity of ≤ 0.5%, and sensitivity change vs. temperature of ≤ 0.03%/C°.
  • SHOULD have cross-axis sensitivity of < 2.5 % and variation of cross-axis sensitivity < 0.2% in device operation temperature range.

• [C-2-2] MUST have a TYPE_ACCELEROMETER_UNCALIBRATED with the same quality requirements as TYPE_ACCELEROMETER .

• [C-2-3] MUST have a TYPE_GYROSCOPE sensor which:

  • MUST have a measurement range between at least -1000 and +1000 dps.
  • MUST have a measurement resolution of at least 16 LSB/dps.
  • MUST have a minimum measurement frequency of 12.5 Hz or lower.
  • MUST have a maximum measurement frequency of 400 Hz or higher; SHOULD support the SensorDirectChannel RATE_VERY_FAST .
  • MUST have a measurement noise not above 0.014°/s/√Hz.
  • [C-SR-2] Is STRONGLY RECOMMENDED to have 3dB measurement bandwidth of at least 80% of Nyquist frequency, and white noise spectrum within this bandwidth.
  • SHOULD have a rate random walk less than 0.001 °/s √Hz tested at room temperature.
  • SHOULD have a bias change vs. temperature of ≤ +/- 0.05 °/ s / °C.
  • SHOULD have a sensitivity change vs. temperature of ≤ 0.02% / °C.
  • SHOULD have a best-fit line non-linearity of ≤ 0.2%.
  • SHOULD have a noise density of ≤ 0.007 °/s/√Hz.
  • SHOULD have calibration error less than 0.002 rad/s in temperature range 10 ~ 40 ℃ when device is stationary.
  • SHOULD have g-sensitivity less than 0.1°/s/g.
  • SHOULD have cross-axis sensitivity of < 4.0 % and cross-axis sensitivity variation < 0.3% in device operation temperature range.

• [C-2-4] MUST have a TYPE_GYROSCOPE_UNCALIBRATED with the same quality requirements as TYPE_GYROSCOPE .

• [C-2-5] MUST have a TYPE_GEOMAGNETIC_FIELD sensor which:

  • MUST have a measurement range between at least -900 and +900 μT.
  • MUST have a measurement resolution of at least 5 LSB/uT.
  • MUST have a minimum measurement frequency of 5 Hz or lower.
  • MUST have a maximum measurement frequency of 50 Hz or higher.
  • MUST have a measurement noise not above 0.5 uT.

• [C-2-6] MUST have a TYPE_MAGNETIC_FIELD_UNCALIBRATED with the same quality requirements as TYPE_GEOMAGNETIC_FIELD and in addition:

  • MUST implement a non-wake-up form of this sensor with a buffering capability of at least 600 sensor events.
  • [C-SR-3] Is STRONGLY RECOMMENDED to have white noise spectrum from 1 Hz to at least 10 Hz when the report rate is 50 Hz or higher.

• [C-2-7] MUST have a TYPE_PRESSURE sensor which:

  • MUST have a measurement range between at least 300 and 1100 hPa.
  • MUST have a measurement resolution of at least 80 LSB/hPa.
  • MUST have a minimum measurement frequency of 1 Hz or lower.
  • MUST have a maximum measurement frequency of 10 Hz or higher.
  • MUST have a measurement noise not above 2 Pa/√Hz.
  • MUST implement a non-wake-up form of this sensor with a buffering capability of at least 300 sensor events.
  • MUST have a batching power consumption not worse than 2 mW.

• [C-2-8] MUST have a TYPE_GAME_ROTATION_VECTOR sensor.

• [C-2-9] MUST have a TYPE_SIGNIFICANT_MOTION sensor which:

  • MUST have a power consumption not worse than 0.5 mW when device is static and 1.5 mW when device is moving.

• [C-2-10] MUST have a TYPE_STEP_DETECTOR sensor which:

  • MUST implement a non-wake-up form of this sensor with a buffering capability of at least 100 sensor events.
  • MUST have a power consumption not worse than 0.5 mW when device is static and 1.5 mW when device is moving.
  • MUST have a batching power consumption not worse than 4 mW.

• [C-2-11] MUST have a TYPE_STEP_COUNTER sensor which:

  • MUST have a power consumption not worse than 0.5 mW when device is static and 1.5 mW when device is moving.

• [C-2-12] MUST have a TILT_DETECTOR sensor which:

  • MUST have a power consumption not worse than 0.5 mW when device is static and 1.5 mW when device is moving.

• [C-2-13] The event timestamp of the same physical event reported by the Accelerometer, Gyroscope, and Magnetometer MUST be within 2.5 milliseconds of each other. The event timestamp of the same physical event reported by the Accelerometer and Gyroscope SHOULD be within 0.25 milliseconds of each other.

• [C-2-14] MUST have Gyroscope sensor event timestamps on the same time base as the camera subsystem and within 1 milliseconds of error.

• [C-2-15] MUST deliver samples to applications within 5 milliseconds from the time when the data is available on any of the above physical sensors to the application.

• [C-2-16] MUST NOT have a power consumption higher than 0.5 mW when device is static and 2.0 mW when device is moving when any combination of the following sensors are enabled:

  • SENSOR_TYPE_SIGNIFICANT_MOTION
  • SENSOR_TYPE_STEP_DETECTOR
  • SENSOR_TYPE_STEP_COUNTER
  • SENSOR_TILT_DETECTORS

• [C-2-17] MAY have a TYPE_PROXIMITY sensor, but if present MUST have a minimum buffer capability of 100 sensor events.

Note that all power consumption requirements in this section do not include the power consumption of the Application Processor. It is inclusive of the power drawn by the entire sensor chain—the sensor, any supporting circuitry, any dedicated sensor processing system, etc.

If device implementations include direct sensor support, they:

• [C-3-1] MUST correctly declare support of direct channel types and direct report rates level through the isDirectChannelTypeSupported and getHighestDirectReportRateLevel API.
• [C-3-2] MUST support at least one of the two sensor direct channel types for all sensors that declare support for sensor direct channel.
  • TYPE_HARDWARE_BUFFER
  • TYPE_MEMORY_FILE
• SHOULD support event reporting through sensor direct channel for primary sensor (non-wakeup variant) of the following types:
  • TYPE_ACCELEROMETER
  • TYPE_ACCELEROMETER_UNCALIBRATED
  • TYPE_GYROSCOPE
  • TYPE_GYROSCOPE_UNCALIBRATED
  • TYPE_MAGNETIC_FIELD
  • TYPE_MAGNETIC_FIELD_UNCALIBRATED

7.3.10. Biometric Sensors

For additional background on Measuring Biometric Unlock Security, please see Measuring Biometric Security documentation .

If device implementations include a secure lock screen, they:

• SHOULD include a biometric sensor

Biometric sensors can be classified as Class 3 (formerly Strong ), Class 2 (formerly Weak ), or Class 1 (formerly Convenience ) based on their spoof and imposter acceptance rates, and on the security of the biometric pipeline. This classification determines the capabilities the biometric sensor has to interface with the platform and with third-party applications. Sensors need to meet additional requirements as detailed below if they wish to be classified as either Class 1 , Class 2 or Class 3 . Both Class 2 and Class 3 biometrics get additional capabilities as detailed below.

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

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

Start new requirements for 15 (AOSP experimental)

[C-4-4] (April 8, 2024 preview)

• [C-4-4] MUST allow applications to add custom content to BiometricPrompt using the PromptContentView content display formats. The content display formats MUST NOT be extended to allow imagery, links, interactive content, or other forms of media that are not already part of the BiometricPrompt API. Stylistic adjustments that do not alter, obscure, or truncate this content can be made (such as changing position, padding, margins, and typography).

Acabar com novos requisitos

[C-4-4] (February 5, 2024 preview)

• [C-4-4] MUST NOT fundamentally change the content display formats of the BiometricPrompt (title text, description text, content body templates, etc.) if they support custom BiometricPrompt UI. The content display formats MUST NOT be extended to allow imagery, links, interactive content, or other forms of media that are not already part of the BiometricPrompt API. Minor stylistic adjustments that do not significantly alter or obscure this content can be made (paddings, margins, position, etc.).

Acabar com novos requisitos

[C-4-4] (December 11, 2023 preview)

• [C-4-4] MUST NOT fundamentally change the content display formats of the BiometricPrompt (title text, description text, content body templates, etc.) if they support custom BiometricPrompt UI. The content display formats cannot be extended to allow imagery, links, interactive content, or other forms of media that are not already part of the BiometricPrompt API. Minor stylistic adjustments that do not significantly alter or obscure this content (paddings, margins, position, etc.) MAY be allowed.

Acabar com novos requisitos

If device implementations support passive biometrics, they:

• [C-5-1] MUST by default require an additional confirmation step (eg a button press).
• [C-SR-1] Are STRONGLY RECOMMENDED to have a setting to allow users to override application preference and always require accompanying confirmation step.
• [C-SR-2] Are STRONGLY RECOMMENDED to have the confirm action be secured such that an operating system or kernel compromise cannot spoof it. For example, this means that the confirm action based on a physical button is routed through an input-only general-purpose input/output (GPIO) pin of a secure element (SE) that cannot be driven by any other means than a physical button imprensa.
• [C-5-2] MUST additionally implement an implicit authentication flow (without confirmation step) corresponding to setConfirmationRequired(boolean) , which applications can set to utilize for sign-in flows.

If device implementations have multiple biometric sensors, they:

• [C-7-1] MUST, when a biometric is in lockout (ie the biometric is disabled until the user unlocks with primary authentication) or time-bound lockout (ie the biometric is temporarily disabled until the user waits for a time interval) due to too many failed attempts, also lock out all other biometrics of a lower biometric class. In the case of time-bound lockout, the backoff time for biometric verification MUST be the maximum backoff time of all biometrics in time-bound lockout.

• [C-SR-12] Are STRONGLY RECOMMENDED, when a biometric is in lockout (ie the biometric is disabled until the user unlocks with primary authentication) or time-bound lockout (ie the biometric is temporarily disabled until the user waits for a time interval) due to too many failed attempts, to also lock out all other biometrics of the same biometric class. In the case of time-bound lockout, the backoff time for biometric verification is STRONGLY RECOMMENDED to be the maximum backoff time of all biometrics in time-bound lockout.

• [C-7-2] MUST challenge the user for the recommended primary authentication (eg: PIN, pattern, password) to reset the lockout counter for a biometric being locked out. Class 3 biometrics MAY be allowed to reset the lockout counter for a locked biometric of the same or lower class. Class 2 or Class 1 biometrics MUST NOT be allowed to complete a reset lockout operation for any biometrics.

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

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

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

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

Start new requirements for 15 (AOSP experimental)

[C-1-1] (December 11, 2023 preview)

• [C-1-1] MUST have a false acceptance rate less than 0.002% 0.001% .

Acabar com novos requisitos

• [C-1-2] MUST disclose that this mode may be less secure than a strong PIN, pattern, or password and clearly enumerate the risks of enabling it, if the spoof and imposter acceptance rates are higher than 7% as measured by the Android Biometrics Test Protocols .
• [C-1-9] MUST challenge the user for the recommended primary authentication (eg, PIN, pattern, password) after no more than twenty false trials and no less than ninety-second backoff time for biometric verification - where a false trial is one with an adequate capture quality (BIOMETRIC_ACQUIRED_GOOD) that does not match an enrolled biometric.
• [C-SR-4] Are STRONGLY RECOMMENDED to lower the total number of false trials for biometric verification specified in [C-1-9] if the spoof and imposter acceptance rates are higher than 7% as measure by the Android Biometrics Test Protocols .
• [C-1-3] MUST rate limit attempts for biometric verification - where a false trial is one with an adequate capture quality ( BIOMETRIC_ACQUIRED_GOOD ) that does not match an enrolled biometric.
• [C-SR-5] Are STRONGLY RECOMMENDED to rate limit attempts for at least 30 seconds after five false trials for biometric verification for the maximum number of false trials per [C-1-9] - where a false trial is one with an adequate capture quality (BIOMETRIC_ACQUIRED_GOOD) that does not match an enrolled biometric.
• [C-SR-6] Are STRONGLY RECOMMENDED to have all rate limiting logic in TEE.
• [C-1-10] MUST disable biometrics once primary authentication backoff has first triggered as described in [C-0-2] of section 9.11.

Start new requirements for 15 (AOSP experimental)

[C-1-11] (December 11, 2023 preview)

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

Acabar com novos requisitos

• [C-1-4] MUST prevent adding new biometrics without first establishing a chain of trust by having the user confirm existing or add a new device credential (PIN/pattern/password) that's secured by TEE; the Android Open Source Project implementation provides the mechanism in the framework to do so.

Start new requirements for 15 (AOSP experimental)

[C-1-5] (December 11, 2023 preview)

• [C-1-5] MUST completely remove all identifiable biometric data for a user when the user's account is removed (including via a factory reset) or when the recommended primary authentication (eg PIN, pattern, password) is removed .

Acabar com novos requisitos

• [C-1-6] MUST honor the individual flag for that biometric (ie DevicePolicyManager.KEYGUARD_DISABLE_FINGERPRINT , DevicePolicymanager.KEYGUARD_DISABLE_FACE , or DevicePolicymanager.KEYGUARD_DISABLE_IRIS ).

Start new requirements for 15 (AOSP experimental)

[C-1-7] (April 8, 2024 preview)

• [C-1-7] MUST challenge the user for the recommended primary authentication (eg, PIN, pattern, password) once every 24 hours or less. Note: Upgrading devices launched on Android version 9 or earlier MUST challenge the user for the recommended primary authentication (eg, PIN, pattern, password) once every 72 hours or less.

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[C-1-8] (December 11, 2023 preview)

• [C-1-8] MUST challenge the user for the recommended primary authentication (eg, PIN, pattern, password) or Class 3 (STRONG) biometric after one of the following:
  • a 4-hour idle timeout period, OR
  • 3 failed biometric authentication attempts.
  • The idle timeout period and the failed authentication count is reset after any successful confirmation of the device credentials. Note: Upgrading devices launched on Android version 9 or earlier MAY be exempted from C-1-8.

Acabar com novos requisitos

• [C-SR-7] Are STRONGLY RECOMMENDED to use the logic in the framework provided by the Android Open Source Project to enforce constraints specified in [C-1-7] and [C-1-8] for new devices.

Start new requirements for 15 (AOSP experimental)

[C-1-14] (December 11, 2023 preview)

• [ C-SR-8 C-1-14 ] Are STRONGLY RECOMMENDED to MUST have a false rejection rate of less than 10%, as measured on the device.

Acabar com novos requisitos

• [C-SR-9] Are STRONGLY RECOMMENDED to have a latency below 1 second, measured from when the biometric is detected, until the screen is unlocked, for each enrolled biometric.

Start new requirements for 15 (AOSP experimental)

[C-1-12] (December 11, 2023 preview)

• [C-1-12] MUST have a spoof and imposter acceptance rate not higher than 40% per presentation attack instrument (PAI) species , as measured by the Android Biometrics Test Protocols .

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[C-1-13] (December 11, 2023 preview)

• [ C-SR-13 C-1-13 ] Are STRONGLY RECOMMENDED to MUST have a spoof and imposter acceptance rate not higher than 30% per presentation attack instrument (PAI) species , as measured by the Android Biometrics Test Protocols .

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[C-1-14] (April 8, 2024 preview)

• [C-1-14] MUST have a false rejection rate of less than 10%, as measured on the device.

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[C-1-15] (December 11, 2023 preview)

• [C-1-15] MUST allow users to remove single or multiple biometrics enrollments.

Acabar com novos requisitos

• [C-SR-14] Are STRONGLY RECOMMENDED to disclose the biometric class of the biometric sensor and the corresponding risks of enabling it.

• [C-SR-17] Are STRONGLY RECOMMENDED to implement the new AIDL interfaces (such as, IFace.aidl and IFingerprint.aidl ).

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

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

Start new requirements for 15 (AOSP experimental)

[C-2-2] (December 11, 2023 preview)

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

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[C-2-10] (December 11, 2023 preview)

• [ C-SR-15 C-2-10 ] Are STRONGLY RECOMMENDED to MUST have a spoof and imposter acceptance rate not higher than 20% per presentation attack instrument (PAI) species , as measured by the Android Biometrics Test Protocols .

Acabar com novos requisitos

• [C-2-3] MUST perform the biometric matching in an isolated execution environment outside Android user or kernel space, such as the Trusted Execution Environment (TEE), on a chip with a secure channel to the isolated execution environment or on Protected Virtual Machine that meets requirements in Section 9.17.
• [C-2-4] MUST have all identifiable data encrypted and cryptographically authenticated such that they cannot be acquired, read or altered outside of the isolated execution environment or a chip with a secure channel to the isolated execution environment as documented in the implementation guidelines on the Android Open Source Project site or a Protected Virtual Machine controlled by hypervisor that meets requirements in Section 9.17.
• [C-2-5] For camera based biometrics, while biometric based authentication or enrollment is happening:
  • MUST operate the camera in a mode that prevents camera frames from being read or altered outside the isolated execution environment or a chip with a secure channel to the isolated execution environment or a Protected Virtual Machine controlled by hypervisor that meets requirements in Section 9.17.
  • For RGB single-camera solutions, the camera frames CAN be readable outside the isolated execution environment to support operations such as preview for enrollment, but MUST still NOT be alterable.
• [C-2-6] MUST NOT enable third-party applications to distinguish between individual biometric enrollments.
• [C-2-7] MUST NOT allow unencrypted access to identifiable biometric data or any data derived from it (such as embeddings) to the Application Processor outside the context of the TEE or the Protected Virtual Machine controlled by hypervisor that meets requirements in Section 9.17. Upgrading devices launched on Android version 9 or earlier are not exempted from C-2-7.

• [C-2-8] MUST have a secure processing pipeline such that an operating system or kernel compromise cannot allow data to be directly injected to falsely authenticate as the user. Note: If device implementations are already launched on Android version 9 or earlier and cannot meet the requirement C-2-8 through a system software update, they MAY be exempted from the requirement.

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

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

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

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

Start new requirements for 15 (AOSP experimental)

[C-3-3] (December 11, 2023 preview)

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

Acabar com novos requisitos

• [C-3-4] MUST challenge the user for the recommended primary authentication (eg PIN, pattern, password) once every 72 hours or less.
• [C-3-5] MUST re-generate Authenticator ID for all Class 3 biometrics supported on device if any of them is re-enrolled.
• [C-3-6] Must enable biometric-backed keystore keys to third-party applications.

Start new requirements for 15 (AOSP experimental)

[C-3-7] (December 11, 2023 preview)

• [ C-SR-16 C-3-7 ] Are STRONGLY RECOMMENDED to MUST have a spoof and imposter acceptance rate not higher than 7% per presentation attack instrument (PAI) species , as measured by the Android Biometrics Test Protocols .

Acabar com novos requisitos

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

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

Start new requirements for 15 (AOSP experimental)

[C-8-1 through C-8-6] [Withdrawn] (April 8, 2024 preview)

These requirements are withdrawn from Android 15 (AOSP experimental).

Acabar com novos requisitos

[C-8-1 through C-8-6] (December 11, 2023 preview)

If device implementations wish to allow a biometric sensor for binding (ie to be used as the primary user verification method bound for specific use cases), they:

• [C-8-1] MUST meet the requirements for Class 3 as defined in this section. Class 3 biometrics MAY be excluded and not participate in binding if usability under certain circumstances is a concern due to the fallback requirement below.
• [C-8-2] MUST NOT allow more than one bound biometric at a time. For example, if multiple biometric modalities are available and eligible, such as face and fingerprint, only one modality and only one enrollment of the modality (eg, only one enrolled fingerprint) can be bound at a time.
• [C-8-3] MUST NOT allow fallback to device credential (PIN/pattern/password) when the bound biometric is requested.
• [C-8-4] MUST require the presentation of a new or previously enrolled biometric to be added as a bound biometric, or the presentation of the currently bound biometric to change the bound biometric to a new or previously enrolled biometric.
• [C-8-5] MUST implement setRequireBoundBiometric(boolean) which applications can utilize to request bound biometric for authentication flows.
• [C-8-6] MUST treat a bound biometric as any other Class 3 biometric regardless of when it is requested (ie setRequireBoundBiometric(boolean )). For example, the bound biometric cannot be excluded when it is not requested or prevent applications from using a CryptoObject that would have otherwise been available.

Acabar com novos requisitos

7.3.11. Pose Sensor

Implementações de dispositivos:

• MAY support pose sensor with 6 degrees of freedom.

If device implementations support pose sensor with 6 degrees of freedom, they:

• [C-1-1] MUST implement and report TYPE_POSE_6DOF sensor.
• [C-1-2] MUST be more accurate than the rotation vector alone.

7.3.12. Hinge Angle Sensor

If device implementations support a hinge angle sensor, they:

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

7.3.13. IEEE 802.1.15.4 (UWB)

If device implementations include support for 802.1.15.4 and expose the functionality to a third-party application, they:

• [C-1-2] MUST report the hardware feature flag android.hardware.uwb .
• [C-1-3] MUST support all the following configuration sets (pre-defined combinations of FIRA UCI parameters) defined in the AOSP implementation.
  • CONFIG_ID_1 : FiRa-defined unicast STATIC STS DS-TWR ranging, deferred mode, ranging interval 240 ms.
  • CONFIG_ID_2 : FiRa-defined one-to-many STATIC STS DS-TWR ranging, deferred mode, ranging interval 200 ms. Typical use case: smart phone interacts with many smart devices.
  • CONFIG_ID_3 : Same as CONFIG_ID_1 , except Angle-of-arrival (AoA) data is not reported.
  • CONFIG_ID_4 : Same as CONFIG_ID_1 , except P-STS security mode is enabled.
  • CONFIG_ID_5 : Same as CONFIG_ID_2 , except P-STS security mode is enabled.
  • CONFIG_ID_6 : Same as CONFIG_ID_3 , except P-STS security mode is enabled.
  • CONFIG_ID_7 : Same as CONFIG_ID_2 , except P-STS individual controlee key mode is enabled.
• [C-1-4] MUST provide a user affordance to allow the user to toggle the UWB radio on/off state.
• [C-1-5] MUST enforce that apps using UWB radio hold the UWB_RANGING permission (under the NEARBY_DEVICES permission group).

Passing the relevant conformance and certification tests defined by standard organizations, including FIRA , CCC and CSA helps ensure 802.1.15.4 functions correctly.

7.4. Data Connectivity

7.4.1. Telefonia

"Telephony" as used by the Android APIs and this document refers specifically to hardware related to placing voice calls and sending SMS messages, or establishing mobile data via a mobile (eg GSM, CDMA, LTE, NR)GSM or CDMA network. A device supporting "Telephony" may choose to offer some or all of the call, messaging and data services as fits the product.

• Android MAY be used on devices that do not include telephony hardware. That is, Android is compatible with devices that are not phones.

If device implementations include GSM or CDMA telephony, they:

• [C-1-1] MUST declare the android.hardware.telephony feature flag and other sub-feature flags according to the technology.
• [C-1-2] MUST implement full support for the API for that technology.
• SHOULD allow all available cellular service types (2G, 3G, 4G, 5G, etc.) during emergency calls (regardless of the network types set by SetAllowedNetworkTypeBitmap() ).

If device implementations do not include telephony hardware, they:

• [C-2-1] MUST implement the full APIs as no-ops.

If device implementations support eUICCs or eSIMs/embedded SIMs and include a proprietary mechanism to make eSIM functionality available for third-party developers, they:

• [C-3-1] MUST declare the android.hardware.telephony.euicc feature flag.

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

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

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

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

If device implementations report the android.hardware.telephony feature, then:

• [C-6-1] The SmsManager#sendTextMessage and SmsManager#sendMultipartTextMessage MUST result in corresponding calls to CarrierMessagingService for providing text messaging functionality. SmsManager#sendMultimediaMessage and SmsManager#downloadMultimediaMessage MUST result in corresponding calls to CarrierMessagingService for providing multimedia messaging functionality.
• [C-6-2] The application designated by android.provider.Telephony.Sms#getDefaultSmsPackage MUST use SmsManager APIs when sending and receiving SMS and MMS messages. The AOSP reference implementation in packages/apps/Messaging meets this requirement.
• [C-6-3] The application which responds to Intent#ACTION_DIAL MUST support entry of arbitrary dialer codes formatted as *#*#CODE#*#* and trigger a corresponding TelephonyManager#ACTION_SECRET_CODE broadcast.
• [C-6-4] The application which responds to Intent#ACTION_DIAL MUST use VoicemailContract.Voicemails#TRANSCRIPTION to display visual voicemail transcription to users if it supports visual voicemail transcriptions.
• [C-6-5] MUST represent all SubscriptionInfo with equivalent group UUIDs as a single subscription in all user-visible affordances that display and control SIM card information. Examples of such affordances include settings interfaces that match Settings#ACTION_MANAGE_ALL_SIM_PROFILES_SETTINGS or EuiccManager#ACTION_MANAGE_EMBEDDED_SUBSCRIPTIONS .
• [C-6-6] MUST NOT display or allow control of any SubscriptionInfo with a non-null group UUID and opportunistic bit in any user-visible affordances that allow configuration or control of SIM card settings.

If the device implementations report the android.hardware.telephony feature and provide a system status bar, then:

• [C-7-1] MUST select a representative active subscription for a given group UUID to display to the user in any affordances that provide SIM status information. Examples of such affordances include the status bar cellular signal icon or quick settings tile.
• [C-SR-1] It is STRONGLY RECOMMENDED that the representative subscription is chosen to be the active data subscription unless the device is in a voice call, during which it is STRONGLY RECOMMENDED that the representative subscription is the active voice subscription.

If device implementations report the android.hardware.telephony feature, then:

• [C-6-7] MUST be capable of opening and concurrently utilizing the maximum number of logical channels (20 in total) for each UICC per ETSI TS 102 221.
• [C-6-8] MUST NOT apply any of the following behaviors to active carrier apps (as designated by TelephonyManager#getCarrierServicePackageName ) automatically or without explicit user confirmation:
  • Revoke or limit network access
  • Revoke permissions
  • Restrict background or foreground app execution beyond the existing power management features included in AOSP
  • Disable or uninstall the app

If device implementations report the android.hardware.telephony feature and all active, non-opportunistic subscriptions that share a group UUID are disabled, physically removed from the device, or marked opportunistic, then the device:

• [C-8-1] MUST automatically disable all remaining active opportunistic subscriptions in the same group.

If device implementations include GSM telephony but not CDMA telephony, they:

• [C-9-1] MUST NOT declare PackageManager#FEATURE_TELEPHONY_CDMA .
• [C-9-2] MUST throw an IllegalArgumentException upon attempts to set any 3GPP2 network types in preferred or allowed network type bitmasks.
• [C-9-3] MUST return an empty string from TelephonyManager#getMeid .

If the device implementations support eUICCs with multiple ports and profiles, they:

• [C-10-1] MUST declare the android.hardware.telephony.euicc.mep feature flag.

7.4.1.1. Number Blocking Compatibility

If device implementations report the android.hardware.telephony.calling feature, they:

• [C-1-1] MUST include number blocking support
• [C-1-2] MUST fully implement BlockedNumberContract and the corresponding API as described in the SDK documentation.

• [C-1-3] MUST block all calls and messages from a phone number in 'BlockedNumberProvider' without any interaction with apps. The only exception is when number blocking is temporarily lifted as described in the SDK documentation.

• [C-1-4] MUST write to the platform call log provider for a blocked call and MUST filter calls with BLOCKED_TYPE out of the default call log view in the pre-installed dialer app.

• [C-1-5] MUST NOT write to the Telephony provider for a blocked message.

• [C-1-6] MUST implement a blocked numbers management UI, which is opened with the intent returned by TelecomManager.createManageBlockedNumbersIntent() method.

• [C-1-7] MUST NOT allow secondary users to view or edit the blocked numbers on the device as the Android platform assumes the primary user to have full control of the telephony services, a single instance, on the device. All blocking related UI MUST be hidden for secondary users and the blocked list MUST still be respected.

• SHOULD migrate the blocked numbers into the provider when a device updates to Android 7.0.

• SHOULD provide a user affordance to show blocked calls in the pre-installed dialer app.

7.4.1.2. Telecom API

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

• [C-1-1] MUST support the ConnectionService APIs described in the SDK .
• [C-1-2] MUST display a new incoming call and provide user affordance to accept or reject the incoming call when the user is on an ongoing call that is made by a third-party app that does not support the hold feature specified via CAPABILITY_SUPPORT_HOLD .
• [C-1-3] MUST have an application that implements InCallService .

• [C-SR-1] Are STRONGLY RECOMMENDED to notify the user that answering an incoming call will drop an ongoing call.

  The AOSP implementation meets these requirements by a heads-up notification which indicates to the user that answering an incoming call will cause the other call to be dropped.

• [C-SR-2] Are STRONGLY RECOMMENDED to preload the default dialer app that shows a call log entry and the name of a third-party app in its call log when the third-party app sets the EXTRA_LOG_SELF_MANAGED_CALLS extras key on its PhoneAccount to true .

• [C-SR-3] Are STRONGLY RECOMMENDED to handle the audio headset's KEYCODE_MEDIA_PLAY_PAUSE and KEYCODE_HEADSETHOOK events for the android.telecom APIs as below:

  • Call Connection.onDisconnect() when a short press of the key event is detected during an ongoing call.
  • Call Connection.onAnswer() when a short press of the key event is detected during an incoming call.
  • Call Connection.onReject() when a long press of the key event is detected during an incoming call.
  • Toggle the mute status of the CallAudioState .

7.4.1.3. Cellular NAT-T Keepalive Offload

Implementações de dispositivos:

• SHOULD include support for Cellular keepalive offload.

If device implementations include support for Cellular keepalive offload and exposes the functionality to third-party apps, they:

• [C-1-1] MUST support the SocketKeepAlive API.
• [C-1-2] MUST support at least one concurrent keepalive slot over cellular.
• [C-1-3] MUST support as many concurrent cellular keepalive slots as are supported by the Cellular Radio HAL.
• [C-SR-1] Are STRONGLY RECOMMENDED to support at least three cellular keepalive slots per radio instance.

If device implementations do not include support for cellular keepalive offload, they:

• [C-2-1] MUST return ERROR_UNSUPPORTED.

7.4.2. IEEE 802.11 (Wi-Fi)

Implementações de dispositivos:

• SHOULD include support for one or more forms of 802.11.

If device implementations include support for 802.11 and expose the functionality to a third-party application, they:

• [C-1-1] MUST implement the corresponding Android API.
• [C-1-2] MUST report the hardware feature flag android.hardware.wifi .
• [C-1-3] MUST implement the multicast API as described in the SDK documentation.

Start new requirements for 15 (AOSP experimental)

[C-1-4] (December 11, 2023 preview)

• [C-1-4] MUST support multicast DNS (mDNS) and MUST NOT filter mDNS packets (224.0.0.251 or ff02::fb) at any time of operation, including when the screen is not in an active state, unless dropping or filtering these packets is necessary to stay within power consumption ranges required by regulatory requirements applicable to the target market.

• [C-1-4] MUST support mDNS and MUST NOT filter mDNS packets (224.0.0.251 or ff02::fb) at any time of operation, including when the screen is not in an active state, unless the multicast lock is not held and the packets are filtered by APF. The packets are not required to satisfy any mDNS operations currently requested by applications through the NsdManager APIs. However, the device MAY filter mDNS packets if doing so is necessary to stay within power consumption ranges required by regulatory requirements applicable to the target market.

Acabar com novos requisitos

• [C-1-5] MUST NOT treat the WifiManager.enableNetwork() API method call as a sufficient indication to switch the currently active Network that is used by default for application traffic and is returned by ConnectivityManager API methods such as getActiveNetwork and registerDefaultNetworkCallback . In other words, they MAY only disable the Internet access provided by any other network provider (eg mobile data) if they successfully validate that the Wi-Fi network is providing Internet access.
• [C-1-6] Are STRONGLY RECOMMENDED to, when the ConnectivityManager.reportNetworkConnectivity() API method is called, re-evaluate the Internet access on the Network and, once the evaluation determines that the current Network no longer provides Internet access, switch to any other available network (eg mobile data) that provides Internet access.
• [C-1-7] MUST randomize the source MAC address and sequence number of probe request frames, once at the beginning of each scan, while STA is disconnected.
• [C-1-8] MUST use one consistent MAC address (SHOULD NOT randomize MAC address halfway through a scan).
• [C-1-9] MUST iterate probe request sequence number as normal (sequentially) between the probe requests in a scan.
• [C-1-10] MUST randomize Probe request sequence number between the last probe request of a scan and the first probe request of the next scan.
• [C-SR-1] Are STRONGLY RECOMMENDED to randomize the source MAC address used for all STA communication to an Access Point (AP) while associating and associated.
  • The device MUST use a different randomized MAC address for each SSID (FQDN for Passpoint) it communicates with.
  • The device MUST provide the user with an option to control the randomization per SSID (FQDN for Passpoint) with non randomized and randomized options, and MUST set the default mode for new Wi-Fi configurations to be randomized.
• [C-SR-2] Are STRONGLY RECOMMENDED to use a random BSSID for any AP that they create.
  • The MAC address MUST be randomized and persisted per SSID used by the AP.
  • The DEVICE MAY provide the user with an option to disable this feature. If such an option is provided, randomization MUST be enabled by default.

If device implementations include support for Wi-Fi power save mode as defined in IEEE 802.11 standard, they:

• SHOULD turn off Wi-Fi power save mode whenever an app acquires WIFI_MODE_FULL_HIGH_PERF lock or WIFI_MODE_FULL_LOW_LATENCY lock via WifiManager.createWifiLock() and WifiManager.WifiLock.acquire() APIs and the lock is active.
• [C-3-2] The average round trip latency between the device and an access point while the device is in a Wi-Fi Low Latency Lock ( WIFI_MODE_FULL_LOW_LATENCY ) mode MUST be smaller than the latency during a Wi-Fi High Perf Lock ( WIFI_MODE_FULL_HIGH_PERF ) mode.
• [C-SR-3] Are STRONGLY RECOMMENDED to minimize Wi-Fi round trip latency whenever a Low Latency Lock ( WIFI_MODE_FULL_LOW_LATENCY ) is acquired and takes effect.

If device implementations support Wi-Fi and use Wi-Fi for location scanning, they:

• [C-2-1] MUST provide a user affordance to enable/disable the value read through the WifiManager.isScanAlwaysAvailable API method.

7.4.2.1. Wi-Fi direto

Implementações de dispositivos:

• SHOULD include support for Wi-Fi Direct (Wi-Fi peer-to-peer).

If device implementations include support for Wi-Fi Direct, they:

• [C-1-1] MUST implement the corresponding Android API as described in the SDK documentation.
• [C-1-2] MUST report the hardware feature android.hardware.wifi.direct .
• [C-1-3] MUST support regular Wi-Fi operation.
• [C-1-4] MUST support Wi-Fi and Wi-Fi Direct operations concurrently.
• [C-SR-1] Are STRONGLY RECOMMENDED to randomize the source MAC address for all newly formed Wi-Fi Direct connections.

7.4.2.2. Wi-Fi Tunneled Direct Link Setup

Implementações de dispositivos:

• SHOULD include support for Wi-Fi Tunneled Direct Link Setup (TDLS) as described in the Android SDK Documentation.

If device implementations include support for TDLS and TDLS is enabled by the WiFiManager API, they:

• [C-1-1] MUST declare support for TDLS through WifiManager.isTdlsSupported .
• SHOULD use TDLS only when it is possible AND beneficial.
• SHOULD have some heuristic and NOT use TDLS when its performance might be worse than going through the Wi-Fi access point.

7.4.2.3. Wi-Fi Aware

Implementações de dispositivos:

• SHOULD include support for Wi-Fi Aware .

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

• [C-1-1] MUST implement the WifiAwareManager APIs as described in the SDK documentation .
• [C-1-2] MUST declare the android.hardware.wifi.aware feature flag.
• [C-1-3] MUST support Wi-Fi and Wi-Fi Aware operations concurrently.
• [C-1-4] MUST randomize the Wi-Fi Aware management interface address at intervals no longer than 30 minutes and whenever Wi-Fi Aware is enabled unless an Aware ranging operation is ongoing or an Aware data-path is active (randomization is not expected for as long as the data-path is active).

If device implementations include support for Wi-Fi Aware and Wi-Fi Location as described in Section 7.4.2.5 and exposes these functionalities to third-party apps, then they:

• [C-2-1] MUST implement the location-aware discovery APIs: setRangingEnabled , setMinDistanceMm , setMaxDistanceMm , and onServiceDiscoveredWithinRange .

7.4.2.4. Wi-Fi Passpoint

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

• [C-1-1] MUST include support for Wi-Fi Passpoint .
• [C-1-2] MUST implement the Passpoint related WifiManager APIs as described in the SDK documentation .
• [C-1-3] MUST support IEEE 802.11u standard, specifically related to Network Discovery and Selection, such as Generic Advertisement Service (GAS) and Access Network Query Protocol (ANQP).
• [C-1-4] MUST declare android.hardware.wifi.passpoint feature flag.
• [C-1-5] MUST follow the AOSP implementation to discover, match and associate to Passpoint networks.
• [C-1-6] MUST support at least the following subset of device provisioning protocols as defined in the Wi-Fi Alliance Passpoint R2: EAP-TTLS authentication and SOAP-XML.
• [C-1-7] MUST process the AAA server certificate as described in Hotspot 2.0 R3 specification.
• [C-1-8] MUST support user control of provisioning through the Wi-Fi picker.
• [C-1-9] MUST keep Passpoint configurations persistent across reboots.
• [C-SR-1] Are STRONGLY RECOMMENDED to support the terms and conditions acceptance feature.
• [C-SR-2] Are STRONGLY RECOMMENDED to support the Venue information feature.

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

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

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

Implementações de dispositivos:

• SHOULD include support for Wi-Fi Location .

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

• [C-1-1] MUST implement the WifiRttManager APIs as described in the SDK documentation .
• [C-1-2] MUST declare the android.hardware.wifi.rtt feature flag.
• [C-1-3] MUST randomize the source MAC address for each RTT burst which is executed while the Wi-Fi interface on which the RTT is being executed is not associated to an Access Point.
• [C-1-4] MUST be accurate to within 2 meters at 80 MHz bandwidth at the 68th percentile (as calculated with the Cumulative Distribution Function).
• [C-SR-1] Are STRONGLY RECOMMENDED to report it accurately to within 1.5 meters at 80 MHz bandwidth at the 68th percentile (as calculated with the Cumulative Distribution Function).

7.4.2.6. Wi-Fi Keepalive Offload

Implementações de dispositivos:

• SHOULD include support for Wi-Fi keepalive offload.

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

• [C-1-1] MUST support the SocketKeepAlive API.
• [C-1-2] MUST support at least three concurrent keepalive slots over Wi-Fi

If device implementations do not include support for Wi-Fi keepalive offload, they:

• [C-2-1] MUST return ERROR_UNSUPPORTED .

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

Implementações de dispositivos:

• SHOULD include support for Wi-Fi Easy Connect (DPP) .

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

• [C-1-1] MUST have the WifiManager#isEasyConnectSupported() method return true .

7.4.2.8. Enterprise Wi-Fi Server Certificate Validation

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

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

7.4.2.9. Trust On First Use (TOFU)

If device implementations support Trust on first usage (TOFU) and allow the user to define WPA/WPA2/WPA3-Enterprise configurations, then they:

• [C-4-1] MUST provide the user an option to select to use TOFU.

7.4.3. Bluetooth

If device implementations support Bluetooth Audio profile, they:

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

If device implementations support HFP, A2DP and AVRCP, they:

• SHOULD support at least 5 total connected devices.

If device implementations declare android.hardware.vr.high_performance feature, they:

• [C-1-1] MUST support Bluetooth 4.2 and Bluetooth LE Data Length Extension.

Android includes support for Bluetooth and Bluetooth Low Energy .

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

• [C-2-1] MUST declare the relevant platform features ( android.hardware.bluetooth and android.hardware.bluetooth_le respectively) and implement the platform APIs.
• SHOULD implement relevant Bluetooth profiles such as A2DP, AVRCP, OBEX, HFP, etc. as appropriate for the device.

If device implementations include support for Bluetooth Low Energy (BLE), they:

• [C-3-1] MUST declare the hardware feature android.hardware.bluetooth_le .
• [C-3-2] MUST enable the GATT (generic attribute profile) based Bluetooth APIs as described in the SDK documentation and android.bluetooth .
• [C-3-3] MUST report the correct value for BluetoothAdapter.isOffloadedFilteringSupported() to indicate whether the filtering logic for the ScanFilter API classes is implemented.
• [C-3-4] MUST report the correct value for BluetoothAdapter.isMultipleAdvertisementSupported() to indicate whether Low Energy Advertising is supported.

• [C-3-5] MUST implement a Resolvable Private Address (RPA) timeout no longer than 15 minutes and rotate the address at timeout to protect user privacy when device is actively using BLE for scanning or advertising. To prevent timing attacks, timeout intervals MUST also be randomized between 5 and 15 minutes.

• SHOULD support offloading of the filtering logic to the bluetooth chipset when implementing the ScanFilter API .

• SHOULD support offloading of the batched scanning to the bluetooth chipset.

• SHOULD support multi advertisement with at least 4 slots.

If device implementations support Bluetooth LE and use Bluetooth LE for location scanning, they:

• [C-4-1] MUST provide a user affordance to enable/disable the value read through the System API BluetoothAdapter.isBleScanAlwaysAvailable() .

If device implementations include support for Bluetooth LE and Hearing Aids Profile, as described in Hearing Aid Audio Support Using Bluetooth LE , they:

• [C-5-1] MUST return true for BluetoothAdapter.getProfileProxy(context, listener, BluetoothProfile.HEARING_AID) .

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

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

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

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

If device implementations return true for the BluetoothAdapter.isLeAudioSupported() API, then they:

• [C-7-1] MUST support unicast client.
• [C-7-2] MUST support 2M PHY.
• [C-7-3] MUST support LE Extended advertising.
• [C-7-4] MUST support at least 2 CIS connections in a CIG.
• [C-7-5] MUST enable BAP unicast client, CSIP set coordinator, MCP server, VCP controller, CCP server simultaneously.
• [C-SR-1] Are STRONGLY RECOMMENDED to enable HAP unicast client.

If device implementations return true for the BluetoothAdapter.isLeAudioBroadcastSourceSupported() API, then they:

• [C-8-1] MUST support at least 2 BIS links in a BIG.
• [C-8-2] MUST enable BAP broadcast source, BAP broadcast assistant simultaneously.
• [C-8-3] MUST support LE Periodic advertising.

If device implementations return true for the BluetoothAdapter.isLeAudioBroadcastAssistantSupported() API, then they:

• [C-9-1] MUST support PAST (Periodic Advertising Sync Transfer).
• [C-9-2] MUST support LE Periodic advertising.

If device implementations declare FEATURE_BLUETOOTH_LE , they:

• [C-10-1] MUST have RSSI measurements be within +/-9dB for 95% of the measurements at 1m distance from a reference device transmitting at ADVERTISE_TX_POWER_HIGH in line of sight environment.
• [C-10-2] MUST include Rx/Tx corrections to reduce per-channel deviations so that the measurements on each of the 3 channels, on each of the antennas (if multiple are used), are within +/-3dB of one another for 95% of the measurements.
• [C-SR-2] Are STRONGLY RECOMMENDED to measure and compensate for Rx offset to ensure the median BLE RSSI is -60dBm +/-10 dB at 1m distance from a reference device transmitting at ADVERTISE_TX_POWER_HIGH , where devices are oriented such that they are on 'parallel planes' with screens facing the same direction.
• [C-SR-3] Are STRONGLY RECOMMENDED to measure and compensate for Tx offset to ensure the median BLE RSSI is -60dBm +/-10 dB when scanning from a reference device positioned at 1m distance and transmitting at ADVERTISE_TX_POWER_HIGH , where devices are oriented such that they are on 'parallel planes' with screens facing the same direction.

It is STRONGLY RECOMMENDED to follow the measurement setup steps specified in Presence Calibration Requirements .

7.4.4. Near-Field Communications

Implementações de dispositivos:

• SHOULD include a transceiver and related hardware for Near-Field Communications (NFC).
• [C-0-1] MUST implement android.nfc.NdefMessage and android.nfc.NdefRecord APIs even if they do not include support for NFC or declare the android.hardware.nfc feature as the classes represent a protocol-independent data representation format .

If device implementations include NFC hardware and plan to make it available to third-party apps, they:

• [C-1-1] MUST report the android.hardware.nfc feature from the android.content.pm.PackageManager.hasSystemFeature() method .
• MUST be capable of reading and writing NDEF messages via the following NFC standards as below:
• [C-1-2] MUST be capable of acting as an NFC Forum reader/writer (as defined by the NFC Forum technical specification NFCForum-TS-DigitalProtocol-1.0) via the following NFC standards:
  • NfcA (ISO14443-3A)
  • NfcB (ISO14443-3B)
  • NfcF (JIS X 6319-4)
  • IsoDep (ISO 14443-4)
  • NFC Forum Tag Types 1, 2, 3, 4, 5 (defined by the NFC Forum)

• [C-SR-1] STRONGLY RECOMMENDED to be capable of reading and writing NDEF messages as well as raw data via the following NFC standards. Note that while the NFC standards are stated as STRONGLY RECOMMENDED, the Compatibility Definition for a future version is planned to change these to MUST. These standards are optional in this version but will be required in future versions. Existing and new devices that run this version of Android are very strongly encouraged to meet these requirements now so they will be able to upgrade to the future platform releases.

• [C-1-13] MUST poll for all supported technologies while in NFC discovery mode.

• SHOULD be in NFC discovery mode while the device is awake with the screen active and the lock-screen unlocked.

• SHOULD be capable of reading the barcode and URL (if encoded) of Thinfilm NFC Barcode products.

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

Android includes support for NFC Host Card Emulation (HCE) mode.

If device implementations include an NFC controller chipset capable of HCE (for NfcA and/or NfcB) and support Application ID (AID) routing, they:

• [C-2-1] MUST report the android.hardware.nfc.hce feature constant.
• [C-2-2] MUST support NFC HCE APIs as defined in the Android SDK.

If device implementations include an NFC controller chipset capable of HCE for NfcF, and implement the feature for third-party applications, they:

• [C-3-1] MUST report the android.hardware.nfc.hcef feature constant.
• [C-3-2] MUST implement the NfcF Card Emulation APIs as defined in the Android SDK.

If device implementations include general NFC support as described in this section and support MIFARE technologies (MIFARE Classic, MIFARE Ultralight, NDEF on MIFARE Classic) in the reader/writer role, they:

• [C-4-1] MUST implement the corresponding Android APIs as documented by the Android SDK.
• [C-4-2] MUST report the feature com.nxp.mifare from the android.content.pm.PackageManager.hasSystemFeature () method. Note that this is not a standard Android feature and as such does not appear as a constant in the android.content.pm.PackageManager class.

7.4.5. Networking protocols and APIs

7.4.5.1. Minimum Network Capability

Implementações de dispositivos:

• [C-0-1] MUST include support for one or more forms of data networking. Specifically, device implementations MUST include support for at least one data standard capable of 200 Kbit/sec or greater. Examples of technologies that satisfy this requirement include EDGE, HSPA, EV-DO, 802.11g, Ethernet and Bluetooth PAN.
• SHOULD also include support for at least one common wireless data standard, such as 802.11 (Wi-Fi), when a physical networking standard (such as Ethernet) is the primary data connection.
• MAY implement more than one form of data connectivity.

7.4.5.2. IPv6

Implementações de dispositivos:

• [C-0-2] MUST include an IPv6 networking stack and support IPv6 communication using the managed APIs, such as java.net.Socket and java.net.URLConnection , as well as the native APIs, such as AF_INET6 sockets.
• [C-0-3] MUST enable IPv6 by default.
  • MUST ensure that IPv6 communication is as reliable as IPv4, for example:
    • [C-0-4] MUST maintain IPv6 connectivity in doze mode.
    • [C-0-5] Rate-limiting MUST NOT cause the device to lose IPv6 connectivity on any IPv6-compliant network that uses RA lifetimes of at least 180 seconds.
• [C-0-6] MUST provide third-party applications with direct IPv6 connectivity to the network when connected to an IPv6 network, without any form of address or port translation happening locally on the device. Both managed APIs such as Socket#getLocalAddress or Socket#getLocalPort ) and NDK APIs such as getsockname() or IPV6_PKTINFO MUST return the IP address and port that is actually used to send and receive packets on the network and is visible as the source ip and port to internet (web) servers.

The required level of IPv6 support depends on the network type, as shown in the following requirements.

If device implementations support Wi-Fi, they:

• [C-1-1] MUST support dual-stack and IPv6-only operation on Wi-Fi.

If device implementations support Ethernet, they:

• [C-2-1] MUST support dual-stack and IPv6-only operation on Ethernet.

If device implementations support Cellular data, they:

• [C-3-1] MUST support IPv6 operation (IPv6-only and possibly dual-stack) on cellular.

If device implementations support more than one network type (eg, Wi-Fi and cellular data), they:

• [C-4-1] MUST simultaneously meet the above requirements on each network when the device is simultaneously connected to more than one network type.

7.4.5.3. Captive Portals

A captive portal refers to a network that requires sign-in in order to obtain internet access.

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

• [C-1-1] MUST provide a captive portal application to handle the intent ACTION_CAPTIVE_PORTAL_SIGN_IN and display the captive portal login page, by sending that intent, on call to the System API ConnectivityManager#startCaptivePortalApp(Network, Bundle) .
• [C-1-2] MUST perform detection of captive portals and support login through the captive portal application when the device is connected to any network type, including cellular/mobile network, WiFi, Ethernet or Bluetooth.
• [C-1-3] MUST support logging in to captive portals using cleartext DNS when the device is configured to use private DNS strict mode.
• [C-1-4] MUST use encrypted DNS as per the SDK documentation for android.net.LinkProperties.getPrivateDnsServerName and android.net.LinkProperties.isPrivateDnsActive for all network traffic that is not explicitly communicating with the captive portal.
• [C-1-5] MUST ensure that, while the user is logging in to a captive portal, the default network used by applications (as returned by ConnectivityManager.getActiveNetwork , ConnectivityManager.registerDefaultNetworkCallback , and used by default by Java networking APIs such as java.net.Socket, and native APIs such as connect()) is any other available network that provides internet access, if available.

7.4.6. Configurações de sincronização

Implementações de dispositivos:

• [C-0-1] MUST have the master auto-sync setting on by default so that the method getMasterSyncAutomatically() returns "true".

7.4.7. Economia de dados

If device implementations include a metered connection, they are:

• [C-SR-1] STRONGLY RECOMMENDED to provide the data saver mode.

If device implementations provide the data saver mode, they:

• [C-1-1] MUST support all the APIs in the ConnectivityManager class as described in the SDK documentation

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

• [C-2-1] MUST return the value RESTRICT_BACKGROUND_STATUS_DISABLED for ConnectivityManager.getRestrictBackgroundStatus()
• [C-2-2] MUST NOT broadcast ConnectivityManager.ACTION_RESTRICT_BACKGROUND_CHANGED .

7.4.8. Secure Elements

If device implementations support Open Mobile API -capable secure elements and make them available to third-party apps, they:

• [C-1-1] MUST enumerate the available secure elements readers via android.se.omapi.SEService.getReaders() API.

• [C-1-2] MUST declare the correct feature flags via android.hardware.se.omapi.uicc for the device with UICC-based secure elements, android.hardware.se.omapi.ese for the device with eSE-based secure elements and android.hardware.se.omapi.sd for the device with SD-based secure elements.

7.4.9. UWB

If device implementations include support for 802.1.15.4 and expose the functionality to a third-party application, then they:

• [C-1-1] MUST implement the corresponding Android API in android.uwb.
• [C-1-2] MUST report the hardware feature flag android.hardware.uwb.
• [C-1-3] MUST support all the relevant UWB profiles defined in Android implementation.
• [C-1-4] MUST provide a user affordance to allow the user to toggle the UWB radio on/off state.
• [C-1-5] MUST enforce that apps using UWB radio hold UWB_RANGING permission (under NEARBY_DEVICES permission group).
• [C-SR-1] Are STRONGLY RECOMMENDED to pass the relevant conformance and certification tests defined by standard organizations, including FIRA , CCC and CSA .
• [C-1-6] MUST ensure the distance measurements are within +/-15 cm for 95% of the measurements in the line of sight environment at 1m distance in a non-reflective chamber.
• [C-1-7] MUST ensure that the median of the distance measurements at 1m from the reference device is within [0.75m, 1.25m], where ground truth distance is measured from the top edge of the DUT.
• [C-SR-2] Are STRONGLY RECOMMENDED to follow the measurement setup steps specified in Presence Calibration Requirements .

7.5. Câmeras

If device implementations include at least one camera, they:

• [C-1-1] MUST declare the android.hardware.camera.any feature flag.
• [C-1-2] MUST be possible for an application to simultaneously allocate 3 RGBA_8888 bitmaps equal to the size of the images produced by the largest-resolution camera sensor on the device, while camera is open for the purpose of basic preview and still capturar.
• [C-1-3] MUST ensure that the preinstalled default camera application handling intents MediaStore.ACTION_IMAGE_CAPTURE , MediaStore.ACTION_IMAGE_CAPTURE_SECURE , or MediaStore.ACTION_VIDEO_CAPTURE , is responsible for removing the user location in the image metadata before sending it to the receiving application when the receiving application does not have ACCESS_FINE_LOCATION .

If device implementations support HDR 10-bit output capability, then they:

• [C-2-1] MUST support at least the HLG HDR profile for every camera device that supports 10-bit output.
• [C-2-2] MUST support 10-bit output for either the primary rear-facing or the primary front-facing camera.
• [C-SR-1] Are STRONGLY RECOMMENDED to support 10-bit output for both primary cameras.
• [C-2-3] MUST support the same HDR profiles for all BACKWARD_COMPATIBLE-capable physical sub-cameras of a logical camera, and the logical camera itself.

For Logical camera devices which support 10-bit HDR that implement the android.hardware.camera2.CaptureRequest#CONTROL_ZOOM_RATIO API, they:

• [C-3-1] MUST support switching between all the backwards-compatible physical cameras via the CONTROL_ZOOM_RATIO control on the logical camera.

7.5.1. Rear-Facing Camera

A rear-facing camera is a world-facing camera that images scenes on the far side of the device, like a traditional camera; on handheld devices, that is a camera located on the side of the device opposite the display.

Implementações de dispositivos:

• SHOULD include a rear-facing camera.

If device implementations include at least one rear-facing camera, they:

• [C-1-1] MUST report the feature flag android.hardware.camera and android.hardware.camera.any .
• [C-1-2] MUST have a resolution of at least 2 megapixels.
• SHOULD have either hardware auto-focus or software auto-focus implemented in the camera driver (transparent to application software).
• MAY have fixed-focus or EDOF (extended depth of field) hardware.
• MAY include a flash.

If the camera includes a flash:

• [C-2-1] the flash lamp MUST NOT be lit while an android.hardware.Camera.PreviewCallback instance has been registered on a Camera preview surface, unless the application has explicitly enabled the flash by enabling the FLASH_MODE_AUTO or FLASH_MODE_ON attributes of a Camera.Parameters object. Note that this constraint does not apply to the device's built-in system camera application, but only to third-party applications using Camera.PreviewCallback .

7.5.2. Câmera frontal

A front-facing camera is a user-facing camera that is typically used to image the user, such as for video conferencing and similar applications; on handheld devices, that is a camera located on the same side of the device as the display.

Implementações de dispositivos:

• MAY include a front-facing camera.

If device implementations include at least one front-facing camera, they:

• [C-1-1] MUST report the feature flag android.hardware.camera.any and android.hardware.camera.front .
• [C-1-2] MUST have a resolution of at least VGA (640x480 pixels).
• [C-1-3] MUST NOT use a front-facing camera as the default for the Camera API and MUST NOT configure the API to treat a front-facing camera as the default rear-facing camera, even if it is the only camera no dispositivo.
• [C-1-4] The camera preview MUST be mirrored horizontally relative to the orientation specified by the application when the current application has explicitly requested that the Camera display be rotated via a call to the android.hardware.Camera.setDisplayOrientation() method . Conversely, the preview MUST be mirrored along the device's default horizontal axis when the current application does not explicitly request that the Camera display be rotated via a call to the android.hardware.Camera.setDisplayOrientation() method.
• [C-1-5] MUST NOT mirror the final captured still image or video streams returned to application callbacks or committed to media storage.
• [C-1-6] MUST mirror the image displayed by the postview in the same manner as the camera preview image stream.
• MAY include features (such as auto-focus, flash, etc.) available to rear-facing cameras as described in section 7.5.1 .

If device implementations are capable of being rotated by user (such as automatically via an accelerometer or manually via user input):

• [C-2-1] The camera preview MUST be mirrored horizontally relative to the device's current orientation.

7.5.3. External Camera

An external camera is a camera that can be physically attached or detached from the device implementation at any time and can face any direction; such as USB cameras.

Implementações de dispositivos:

• MAY include support for an external camera that is not necessarily always connected.

If device implementations include support for an external camera, they:

• [C-1-1] MUST declare the platform feature flag android.hardware.camera.external and android.hardware camera.any .
• [C-1-2] MUST support USB Video Class (UVC 1.0 or higher) if the external camera connects through the USB host port.
• [C-1-3] MUST pass camera CTS tests with a physical external camera device connected. Details of camera CTS testing are available at source.android.com .
• SHOULD support video compressions such as MJPEG to enable transfer of high-quality unencoded streams (ie raw or independently compressed picture streams).
• MAY support multiple cameras.
• MAY support camera-based video encoding.

If camera-based video encoding is supported:

• [C-2-1] A simultaneous unencoded / MJPEG stream (QVGA or greater resolution) MUST be accessible to the device implementation.

7.5.4. Camera API Behavior

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

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

All features that are common between the deprecated android.hardware.Camera class and the newer android.hardware.camera2 package MUST have equivalent performance and quality in both APIs. For example, with equivalent settings, autofocus speed and accuracy must be identical, and the quality of captured images must be the same. Features that depend on the different semantics of the two APIs are not required to have matching speed or quality, but SHOULD match as closely as possible.

Device implementations MUST implement the following behaviors for the camera-related APIs, for all available cameras. Implementações de dispositivos:

• [C-0-1] MUST use android.hardware.PixelFormat.YCbCr_420_SP for preview data provided to application callbacks when an application has never called android.hardware.Camera.Parameters.setPreviewFormat(int) .
• [C-0-2] MUST further be in the NV21 encoding format when an application registers an android.hardware.Camera.PreviewCallback instance and the system calls the onPreviewFrame() method and the preview format is YCbCr_420_SP, the data in the byte[] passed into onPreviewFrame() . That is, NV21 MUST be the default.
• [C-0-3] MUST support the YV12 format (as denoted by the android.graphics.ImageFormat.YV12 constant) for camera previews for both front- and rear-facing cameras for android.hardware.Camera . (The hardware video encoder and camera may use any native pixel format, but the device implementation MUST support conversion to YV12.)
• [C-0-4] MUST support the android.hardware.ImageFormat.YUV_420_888 and android.hardware.ImageFormat.JPEG formats as outputs through the android.media.ImageReader API for android.hardware.camera2 devices that advertise REQUEST_AVAILABLE_CAPABILITIES_BACKWARD_COMPATIBLE capability in android.request.availableCapabilities .
• [C-0-5] MUST still implement the full Camera API included in the Android SDK documentation, regardless of whether the device includes hardware autofocus or other capabilities. For instance, cameras that lack autofocus MUST still call any registered android.hardware.Camera.AutoFocusCallback instances (even though this has no relevance to a non-autofocus camera.) Note that this does apply to front-facing cameras; for instance, even though most front-facing cameras do not support autofocus, the API callbacks must still be "faked" as described.
• [C-0-6] MUST recognize and honor each parameter name defined as a constant in the android.hardware.Camera.Parameters class and the android.hardware.camera2.CaptureRequest class. Conversely, device implementations MUST NOT honor or recognize string constants passed to the android.hardware.Camera.setParameters() method other than those documented as constants on the android.hardware.Camera.Parameters . That is, device implementations MUST support all standard Camera parameters if the hardware allows, and MUST NOT support custom Camera parameter types. For instance, device implementations that support image capture using high dynamic range (HDR) imaging techniques MUST support camera parameter Camera.SCENE_MODE_HDR .
• [C-0-7] MUST report the proper level of support with the android.info.supportedHardwareLevel property as described in the Android SDK and report the appropriate framework feature flags .
• [C-0-8] MUST also declare its individual camera capabilities of android.hardware.camera2 via the android.request.availableCapabilities property and declare the appropriate feature flags ; MUST define the feature flag if any of its attached camera devices supports the feature.
• [C-0-9] MUST broadcast the Camera.ACTION_NEW_PICTURE intent whenever a new picture is taken by the camera and the entry of the picture has been added to the media store.
• [C-0-10] MUST broadcast the Camera.ACTION_NEW_VIDEO intent whenever a new video is recorded by the camera and the entry of the picture has been added to the media store.
• [C-0-11] MUST have all cameras accessible via the deprecated android.hardware.Camera API also accessible via the android.hardware.camera2 API.
• [C-0-12] MUST ensure that the facial appearance is NOT altered, including but not limited to altering facial geometry, facial skin tone, or facial skin smoothening for any android.hardware.camera2 or android.hardware.Camera API.
• [C-SR-1] For devices with multiple RGB cameras in close proximity and facing in the same direction, it is STRONGLY RECOMMENDED to support a logical camera device that lists capability CameraMetadata.REQUEST_AVAILABLE_CAPABILITIES_LOGICAL_MULTI_CAMERA , consisting of all of the RGB cameras facing that direction as physical sub-devices.

If device implementations provide a proprietary camera API to 3rd-party apps, they:

• [C-1-1] MUST implement such a camera API using android.hardware.camera2 API.
• MAY provide vendor tags and/or extensions to android.hardware.camera2 API.

7.5.5. Camera Orientation

If device implementations have a front- or a rear-facing camera, such camera(s):

• [C-1-1] MUST be oriented so that the long dimension of the camera aligns with the screen's long dimension. That is, when the device is held in the landscape orientation, cameras MUST capture images in the landscape orientation. This applies regardless of the device's natural orientation; that is, it applies to landscape-primary devices as well as portrait-primary devices.

Devices that fulfill all of the following criteria are exempt from the requirement above:

• The device implements variable-geometry screens, such as foldable or hinged displays.
• When the device's fold or hinge state changes, the device switches between portrait-primary to landscape-primary (or vice-versa) orientations.
• Device implementations that are not capable of being rotated by the user such as automotive devices.

7.6. Memória e armazenamento

7.6.1. Minimum Memory and Storage

Implementações de dispositivos:

• [C-0-1] MUST include a Download Manager that applications MAY use to download data files and they MUST be capable of downloading individual files of at least 100MB in size to the default "cache" location.

7.6.2. Application Shared Storage

Implementações de dispositivos:

• [C-0-1] MUST offer storage to be shared by applications, also often referred as "shared external storage", "application shared storage" or by the Linux path "/sdcard" it is mounted on.
• [C-0-2] MUST be configured with shared storage mounted by default, in other words "out of the box", regardless of whether the storage is implemented on an internal storage component or a removable storage medium (eg Secure Digital card slot ).
• [C-0-3] MUST mount the application shared storage directly on the Linux path sdcard or include a Linux symbolic link from sdcard to the actual mount point.
• [C-0-4] MUST enable scoped storage by default for all apps targeting API level 29 or above, except in the following situation:
  • When the app has requested android:requestLegacyExternalStorage="true" in their manifest.
• [C-0-5] MUST redact location metadata, such as GPS Exif tags, stored in media files when those files are accessed through MediaStore , except when the calling app holds the ACCESS_MEDIA_LOCATION permission.

Device implementations MAY meet the above requirements using either of the following:

• User-accessible removable storage, such as a Secure Digital (SD) card slot.
• A portion of the internal (non-removable) storage as implemented in the Android Open Source Project (AOSP).

If device implementations use removable storage to satisfy the above requirements, they:

• [C-1-1] MUST implement a toast or pop-up user interface warning the user when there is no storage medium inserted in the slot.
• [C-1-2] MUST include a FAT-formatted storage medium (eg SD card) or show on the box and other material available at time of purchase that the storage medium has to be purchased separately.

If device implementations use a portion of the non-removable storage to satisfy the above requirements, they:

• SHOULD use the AOSP implementation of the internal application shared storage.
• MAY share the storage space with the application private data.

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

• [C-3-1] MUST provide a mechanism to access the data on the application shared storage from a host computer.
• SHOULD expose content from both storage paths transparently through Android's media scanner service and android.provider.MediaStore .
• MAY use USB mass storage, but SHOULD use Media Transfer Protocol to satisfy this requirement.

If device implementations have a USB port with USB peripheral mode and support Media Transfer Protocol, they:

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

7.6.3. Adoptable Storage

If the device is expected to be mobile in nature unlike Television, device implementations are:

• [C-SR-1] STRONGLY RECOMMENDED to implement the adoptable storage in a long-term stable location, since accidentally disconnecting them can cause data loss/corruption.

If the removable storage device port is in a long-term stable location, such as within the battery compartment or other protective cover, device implementations are:

• [C-SR-2] STRONGLY RECOMMENDED to implement adoptable storage .

7.7. USB

If device implementations have a USB port, they:

• SHOULD support USB peripheral mode and SHOULD support USB host mode.
• SHOULD support disabling data signaling over USB.

7.7.1. USB peripheral mode

If device implementations include a USB port supporting peripheral mode:

• [C-1-1] The port MUST be connectable to a USB host that has a standard type-A or type-C USB port.
• [C-1-2] MUST report the correct value of iSerialNumber in USB standard device descriptor through android.os.Build.SERIAL .
• [C-1-3] MUST detect 1.5A and 3.0A chargers per the Type-C resistor standard and MUST detect changes in the advertisement if they support Type-C USB.
• [C-SR-1] The port SHOULD use micro-B, micro-AB or Type-C USB form factor. Existing and new Android devices are STRONGLY RECOMMENDED to meet these requirements so they will be able to upgrade to the future platform releases.
• [C-SR-2] The port SHOULD be located on the bottom of the device (according to natural orientation) or enable software screen rotation for all apps (including home screen), so that the display draws correctly when the device is oriented with the port at bottom. Existing and new Android devices are STRONGLY RECOMMENDED to meet these requirements so they will be able to upgrade to future platform releases.
• [C-SR-3] SHOULD implement support to draw 1.5 A current during HS chirp and traffic as specified in the USB Battery Charging specification, revision 1.2 . Existing and new Android devices are STRONGLY RECOMMENDED to meet these requirements so they will be able to upgrade to the future platform releases.
• [C-SR-4] STRONGLY RECOMMENDED to not support proprietary charging methods that modify Vbus voltage beyond default levels, or alter sink/source roles as such may result in interoperability issues with the chargers or devices that support the standard USB Power Delivery methods. While this is called out as "STRONGLY RECOMMENDED", in future Android versions we might REQUIRE all type-C devices to support full interoperability with standard type-C chargers.
• [C-SR-5] STRONGLY RECOMMENDED to support Power Delivery for data and power role swapping when they support Type-C USB and USB host mode.
• SHOULD support Power Delivery for high-voltage charging and support for Alternate Modes such as display out.
• SHOULD implement the Android Open Accessory (AOA) API and specification as documented in the Android SDK documentation.

If device implementations include a USB port and implement the AOA specification, they:

• [C-2-1] MUST declare support for the hardware feature android.hardware.usb.accessory .
• [C-2-2] The USB mass storage class MUST include the string "android" at the end of the interface description iInterface string of the USB mass storage
• SHOULD NOT implement AOAv2 audio documented in the Android Open Accessory Protocol 2.0 documentation. AOAv2 audio is deprecated as of Android version 8.0 (API level 26).

7.7.2. USB host mode

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

• [C-1-1] MUST implement the Android USB host API as documented in the Android SDK and MUST declare support for the hardware feature android.hardware.usb.host .
• [C-1-2] MUST implement support to connect standard USB peripherals, in other words, they MUST either:
  • Have an on-device type C port or ship with cable(s) adapting an on-device proprietary port to a standard USB type-C port (USB Type-C device).
  • Have an on-device type A or ship with cable(s) adapting an on-device proprietary port to a standard USB type-A port.
  • Have an on-device micro-AB port, which SHOULD ship with a cable adapting to a standard type-A port.
• [C-1-3] MUST NOT ship with an adapter converting from USB type A or micro-AB ports to a type-C port (receptacle).
• [C-SR-1] Are STRONGLY RECOMMENDED to implement the USB audio class as documented in the Android SDK documentation.
• SHOULD support charging the connected USB peripheral device while in host mode; advertising a source current of at least 1.5A as specified in the Termination Parameters section of the USB Type-C Cable and Connector Specification Revision 1.2 for USB Type-C connectors or using Charging Downstream Port(CDP) output current range as specified in the USB Battery Charging specifications, revision 1.2 for Micro-AB connectors.
• SHOULD implement and support USB Type-C standards.

If device implementations include a USB port supporting host mode and the USB audio class, they:

• [C-2-1] MUST support the USB HID class .
• [C-2-2] MUST support the detection and mapping of the following HID data fields specified in the USB HID Usage Tables and the Voice Command Usage Request to the KeyEvent constants as below:
  • Usage Page (0xC) Usage ID (0x0CD): KEYCODE_MEDIA_PLAY_PAUSE
  • Usage Page (0xC) Usage ID (0x0E9): KEYCODE_VOLUME_UP
  • Usage Page (0xC) Usage ID (0x0EA): KEYCODE_VOLUME_DOWN
  • Usage Page (0xC) Usage ID (0x0CF): KEYCODE_VOICE_ASSIST

If device implementations include a USB port supporting host mode and the Storage Access Framework (SAF), they:

• [C-3-1] MUST recognize any remotely connected MTP (Media Transfer Protocol) devices and make their contents accessible through the ACTION_GET_CONTENT , ACTION_OPEN_DOCUMENT , and ACTION_CREATE_DOCUMENT intents. .

If device implementations include a USB port supporting host mode and USB Type-C, they:

• [C-4-1] MUST implement Dual Role Port functionality as defined by the USB Type-C specification (section 4.5.1.3.3). For Dual Role Ports, On devices that include a 3.5mm audio jack, the USB sink detection (host mode) MAY be off by default but it MUST be possible for the user to enable it.
• [C-SR-2] STRONGLY RECOMMENDED to support DisplayPort, SHOULD support USB SuperSpeed Data Rates, and are STRONGLY RECOMMENDED to support Power Delivery for data and power role swapping.
• [C-SR-3] STRONGLY RECOMMENDED to NOT support Audio Adapter Accessory Mode as described in the Appendix A of the USB Type-C Cable and Connector Specification Revision 1.2 .
• SHOULD implement the Try.* model that is most appropriate for the device form factor. For example a handheld device SHOULD implement the Try.SNK model.

7.8. Áudio

7.8.1. Microfone

If device implementations include a microphone, they:

• [C-1-1] MUST report the android.hardware.microphone feature constant.
• [C-1-2] MUST meet the audio recording requirements in section 5.4 .
• [C-1-3] MUST meet the audio latency requirements in section 5.6 .
• [C-SR-1] Are STRONGLY RECOMMENDED to support near-ultrasound recording as described in section 7.8.3 .

If device implementations omit a microphone, they:

• [C-2-1] MUST NOT report the android.hardware.microphone feature constant.
• [C-2-2] MUST implement the audio recording API at least as no-ops, per section 7 .

7.8.2. Saída de áudio

If device implementations include a speaker or an audio/multimedia output port for an audio output peripheral such as a 4 conductor 3.5mm audio jack or USB host mode port using USB audio class , they:

• [C-1-1] MUST report the android.hardware.audio.output feature constant.
• [C-1-2] MUST meet the audio playback requirements in section 5.5 .
• [C-1-3] MUST meet the audio latency requirements in section 5.6 .
• [C-SR-1] STRONGLY RECOMMENDED to support near-ultrasound playback as described in section 7.8.3 .

If device implementations do not include a speaker or audio output port, they:

• [C-2-1] MUST NOT report the android.hardware.audio.output feature.
• [C-2-2] MUST implement the Audio Output related APIs as no-ops at least.

For the purposes of this section, an "output port" is a physical interface such as a 3.5mm audio jack, HDMI, or USB host mode port with USB audio class. Support for audio output over radio-based protocols such as Bluetooth, WiFi, or cellular network does not qualify as including an "output port".

7.8.2.1. Analog Audio Ports

In order to be compatible with the headsets and other audio accessories using the 3.5mm audio plug across the Android ecosystem, if device implementations include one or more analog audio ports, they:

• [C-SR-1] Are STRONGLY RECOMMENDED to include at least one of the audio port(s) to be a 4 conductor 3.5mm audio jack.

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

• [C-1-1] MUST support audio playback to stereo headphones and stereo headsets with a microphone.
• [C-1-2] MUST support TRRS audio plugs with the CTIA pin-out order.
• [C-1-3] MUST support the detection and mapping to the keycodes for the following 3 ranges of equivalent impedance between the microphone and ground conductors on the audio plug:
  • 70 ohm or less : KEYCODE_HEADSETHOOK
  • 210-290 ohm : KEYCODE_VOLUME_UP
  • 360-680 ohm : KEYCODE_VOLUME_DOWN
• [C-1-4] MUST trigger ACTION_HEADSET_PLUG upon a plug insert, but only after all contacts on plug are touching their relevant segments on the jack.
• [C-1-5] MUST be capable of driving at least 150mV ± 10% of output voltage on a 32 ohm speaker impedance.
• [C-1-6] MUST have a microphone bias voltage between 1.8V ~ 2.9V.
• [C-1-7] MUST detect and map to the keycode for the following range of equivalent impedance between the microphone and ground conductors on the audio plug:
  • 110-180 ohm: KEYCODE_VOICE_ASSIST
• [C-SR-2] Are STRONGLY RECOMMENDED to support audio plugs with the OMTP pin-out order.
• [C-SR-3] Are STRONGLY RECOMMENDED to support audio recording from stereo headsets with a microphone.

If device implementations have a 4 conductor 3.5mm audio jack and support a microphone, and broadcast the android.intent.action.HEADSET_PLUG with the extra value microphone set as 1, they:

• [C-2-1] MUST support the detection of microphone on the plugged in audio accessory.

7.8.2.2. Digital Audio Ports

See Section 2.2.1 for device-specific requirements.

7.8.3. Near-Ultrasound

Near-Ultrasound audio is the 18.5 kHz to 20 kHz band.

Implementações de dispositivos:

• MUST correctly report the support of near-ultrasound audio capability via the AudioManager.getProperty API as follows:

If PROPERTY_SUPPORT_MIC_NEAR_ULTRASOUND is "true", the following requirements MUST be met by the VOICE_RECOGNITION and UNPROCESSED audio sources:

• [C-1-1] The microphone's mean power response in the 18.5 kHz to 20 kHz band MUST be no more than 15 dB below the response at 2 kHz.
• [C-1-2] The microphone's unweighted signal to noise ratio over 18.5 kHz to 20 kHz for a 19 kHz tone at -26 dBFS MUST be no lower than 50 dB.

If PROPERTY_SUPPORT_SPEAKER_NEAR_ULTRASOUND is "true":

• [C-2-1] The speaker's mean response in 18.5 kHz - 20 kHz MUST be no lower than 40 dB below the response at 2 kHz.

7.8.4. Integridade do Sinal

Implementações de dispositivos:

• SHOULD provide a glitch-free audio signal path for both input and output streams on handheld devices, as defined by zero glitches measured during a test of one minute per path. Test using OboeTester "Automated Glitch Test".

The test requires an audio loopback dongle , used directly in a 3.5mm jack, and/or in combination with a USB-C to 3.5mm adapter. All audio output ports SHOULD be tested.

OboeTester currently supports AAudio paths, so the following combinations SHOULD be tested for glitches using AAudio:

Perf Mode	Compartilhamento	Out Sample Rate	In Chans	Out Chans
LOW_LATENCY	EXCLUSIVO	UNSPECIFIED	1	2
LOW_LATENCY	EXCLUSIVO	UNSPECIFIED	2	1
LOW_LATENCY	COMPARTILHADO	UNSPECIFIED	1	2
LOW_LATENCY	COMPARTILHADO	UNSPECIFIED	2	1
NENHUM	COMPARTILHADO	48.000	1	2
NENHUM	COMPARTILHADO	48.000	2	1
NENHUM	COMPARTILHADO	44100	1	2
NENHUM	COMPARTILHADO	44100	2	1
NENHUM	COMPARTILHADO	16.000	1	2
NENHUM	COMPARTILHADO	16.000	2	1

A reliable stream SHOULD meet the following criteria for Signal to Noise Ratio (SNR) and Total Harmonic Distortion (THD) for 2000 Hz sine.

Transdutor	THD	SNR
primary built-in speaker, measured using an external reference microphone	< 3.0%	>= 50 dB
primary built-in microphone, measured using an external reference speaker	< 3.0%	>= 50 dB
built-in analog 3.5 mm jacks, tested using loopback adapter	< 1%	>= 60 dB
USB adapters supplied with the phone, tested using loopback adapter	< 1.0%	>= 60 dB

7.9. Realidade virtual

Android includes APIs and facilities to build "Virtual Reality" (VR) applications including high quality mobile VR experiences. Device implementations MUST properly implement these APIs and behaviors, as detailed in this section.

7.9.1. Virtual Reality Mode

Android includes support for VR Mode , a feature which handles stereoscopic rendering of notifications and disables monocular system UI components while a VR application has user focus.

7.9.2. Virtual Reality Mode - High Performance

If device implementations support VR mode, they:

• [C-1-1] MUST have at least 2 physical cores.
• [C-1-2] MUST declare the android.hardware.vr.high_performance feature.
• [C-1-3] MUST support sustained performance mode.
• [C-1-4] MUST support OpenGL ES 3.2.
• [C-1-5] MUST support android.hardware.vulkan.level 0.
• SHOULD support android.hardware.vulkan.level 1 or higher.
• [C-1-6] MUST implement EGL_KHR_mutable_render_buffer , EGL_ANDROID_front_buffer_auto_refresh , EGL_ANDROID_get_native_client_buffer , EGL_KHR_fence_sync , EGL_KHR_wait_sync , EGL_IMG_context_priority , EGL_EXT_protected_content , EGL_EXT_image_gl_colorspace , and expose the extensions in the list of available EGL extensions.
• [C-1-8] MUST implement GL_EXT_multisampled_render_to_texture2 , GL_OVR_multiview , GL_OVR_multiview2 , GL_EXT_protected_textures , and expose the extensions in the list of available GL extensions.
• [C-SR-1] Are STRONGLY RECOMMENDED to implement GL_EXT_external_buffer , GL_EXT_EGL_image_array , GL_OVR_multiview_multisampled_render_to_texture , and expose the extensions in the list of available GL extensions.
• [C-SR-2] Are STRONGLY RECOMMENDED to support Vulkan 1.1.
• [C-SR-3] Are STRONGLY RECOMMENDED to implement VK_ANDROID_external_memory_android_hardware_buffer , VK_GOOGLE_display_timing , VK_KHR_shared_presentable_image , and expose it in the list of available Vulkan extensions.
• [C-SR-4] Are STRONGLY RECOMMENDED to expose at least one Vulkan queue family where flags contain both VK_QUEUE_GRAPHICS_BIT and VK_QUEUE_COMPUTE_BIT , and queueCount is at least 2.
• [C-1-7] The GPU and display MUST be able to synchronize access to the shared front buffer such that alternating-eye rendering of VR content at 60fps with two render contexts will be displayed with no visible tearing artifacts.
• [C-1-9] MUST implement support for AHardwareBuffer flags AHARDWAREBUFFER_USAGE_GPU_DATA_BUFFER , AHARDWAREBUFFER_USAGE_SENSOR_DIRECT_DATA and AHARDWAREBUFFER_USAGE_PROTECTED_CONTENT as described in the NDK.
• [C-1-10] MUST implement support for AHardwareBuffer s with any combination of the usage flags AHARDWAREBUFFER_USAGE_GPU_COLOR_OUTPUT , AHARDWAREBUFFER_USAGE_GPU_SAMPLED_IMAGE , AHARDWAREBUFFER_USAGE_PROTECTED_CONTENT for at least the following formats: AHARDWAREBUFFER_FORMAT_R5G6B5_UNORM , AHARDWAREBUFFER_FORMAT_R8G8B8A8_UNORM , AHARDWAREBUFFER_FORMAT_R10G10B10A2_UNORM , AHARDWAREBUFFER_FORMAT_R16G16B16A16_FLOAT .
• [C-SR-5] Are STRONGLY RECOMMENDED to support the allocation of AHardwareBuffer s with more than one layer and flags and formats specified in C-1-10.
• [C-1-11] MUST support H.264 decoding at least 3840 x 2160 at 30fps, compressed to an average of 40Mbps (equivalent to 4 instances of 1920 x1080 at 30 fps-10 Mbps or 2 instances of 1920 x 1080 at 60 fps-20 Mbps).
• [C-1-12] MUST support HEVC and VP9, MUST be capable of decoding at least 1920 x 1080 at 30 fps compressed to an average of 10 Mbps and SHOULD be capable of decoding 3840 x 2160 at 30 fps-20 Mbps (equivalent to 4 instances of 1920 x 1080 at 30 fps-5 Mbps).
• [C-1-13] MUST support HardwarePropertiesManager.getDeviceTemperatures API and return accurate values for skin temperature.
• [C-1-14] MUST have an embedded screen, and its resolution MUST be at least 1920 x 1080.
• [C-SR-6] Are STRONGLY RECOMMENDED to have a display resolution of at least 2560 x 1440.
• [C-1-15] The display MUST update at least 60 Hz while in VR Mode.
• [C-1-17] The display MUST support a low-persistence mode with ≤ 5 milliseconds persistence, persistence being defined as the amount of time for which a pixel is emitting light.
• [C-1-18] MUST support Bluetooth 4.2 and Bluetooth LE Data Length Extension section 7.4.3 .
• [C-1-19] MUST support and properly report Direct Channel Type for all of the following default sensor types:
  • TYPE_ACCELEROMETER
  • TYPE_ACCELEROMETER_UNCALIBRATED
  • TYPE_GYROSCOPE
  • TYPE_GYROSCOPE_UNCALIBRATED
  • TYPE_MAGNETIC_FIELD
  • TYPE_MAGNETIC_FIELD_UNCALIBRATED
• [C-SR-7] Are STRONGLY RECOMMENDED to support the TYPE_HARDWARE_BUFFER direct channel type for all Direct Channel Types listed above.
• [C-1-21] MUST meet the gyroscope, accelerometer, and magnetometer related requirements for android.hardware.hifi_sensors , as specified in section 7.3.9 .
• [C-SR-8] Are STRONGLY RECOMMENDED to support the android.hardware.sensor.hifi_sensors feature.
• [C-1-22] MUST have end-to-end motion to photon latency not higher than 28 milliseconds.
• [C-SR-9] Are STRONGLY RECOMMENDED to have end-to-end motion to photon latency not higher than 20 milliseconds.
• [C-1-23] MUST have first-frame ratio, which is the ratio between the brightness of pixels on the first frame after a transition from black to white and the brightness of white pixels in steady state, of at least 85%.
• [C-SR-10] Are STRONGLY RECOMMENDED to have first-frame ratio of at least 90%.
• MAY provide an exclusive core to the foreground application and MAY support the Process.getExclusiveCores API to return the numbers of the cpu cores that are exclusive to the top foreground application.

If exclusive core is supported, then the core:

• [C-2-1] MUST not allow any other userspace processes to run on it (except device drivers used by the application), but MAY allow some kernel processes to run as necessary.

7.10. Tátil

Devices intended to be hand-held or worn may include a general purpose haptic actuator, available to applications for purposes including getting attention through ringtones, alarms, notifications, as well as general touch feedback.

If device implementations DO NOT include such a general purpose haptic actuator, they:

• [7.10/C] MUST return false for Vibrator.hasVibrator() .

If device implementations DO include at least one such general purpose haptic actuator, they:

• [C-1-1] MUST return true for Vibrator.hasVibrator() .
• SHOULD NOT use an eccentric rotating mass (ERM) haptic actuator (vibrator).
• SHOULD implement all public constants for clear haptics in android.view.HapticFeedbackConstants namely ( CLOCK_TICK , CONTEXT_CLICK , KEYBOARD_PRESS , KEYBOARD_RELEASE , KEYBOARD_TAP , LONG_PRESS , TEXT_HANDLE_MOVE , VIRTUAL_KEY , VIRTUAL_KEY_RELEASE , CONFIRM , REJECT , GESTURE_START and GESTURE_END ).
• SHOULD implement all public constants for clear haptics in android.os.VibrationEffect namely ( EFFECT_TICK , EFFECT_CLICK , EFFECT_HEAVY_CLICK and EFFECT_DOUBLE_CLICK ) and all feasible public PRIMITIVE_* constants for rich haptics in android.os.VibrationEffect.Composition namely ( CLICK , TICK , LOW_TICK , QUICK_FALL , QUICK_RISE , SLOW_RISE , SPIN , THUD ). Algumas dessas primitivas, como LOW_TICK e SPIN só podem ser viáveis ​​se o vibrador puder suportar frequências relativamente baixas.
• SHOULD follow the guidance for mapping public constants in android.view.HapticFeedbackConstants to the recommended android.os.VibrationEffect constants, with the corresponding amplitude relationships.
• SHOULD use these linked haptic constants mappings .
• SHOULD follow quality assessment for createOneShot() and createWaveform() APIs.
• SHOULD verify that the result of the public android.os.Vibrator.hasAmplitudeControl() API correctly reflects their vibrator's capabilities.
• SHOULD verify the capabilities for amplitude scalability by running android.os.Vibrator.hasAmplitudeControl() .

If device implementations follow the haptic constants mapping, they:

• SHOULD verify the implementation status by running android.os.Vibrator.areAllEffectsSupported() and android.os.Vibrator.arePrimitivesSupported() APIs.
• SHOULD perform a quality assessment for haptic constants.
• SHOULD verify and update if needed the fallback configuration for unsupported primitives as described in the implementation guidance for constants.
• SHOULD provide fallback support to mitigate the risk of failure as described here .

7.11. Media Performance Class

The media performance class of the device implementation can be obtained from the android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS API. Requirements for media performance class are defined for each Android version starting with R (version 30). The special value of 0 designates that the device is not of a media performance class.

If device implementations return non-zero value for android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS , they:

• [C-1-1] MUST return at least a value of android.os.Build.VERSION_CODES.R .

• [C-1-2] MUST be a handheld device implementation.

• [C-1-3] MUST meet all requirements for "Media Performance Class" described in section 2.2.7 .

In other words, media performance class in Android T is only defined for handheld devices at version T, S or R.

See section 2.2.7 for device-specific requirements.

8. Performance and Power

Some minimum performance and power criteria are critical to the user experience and impact the baseline assumptions developers would have when developing an app.

8.1. User Experience Consistency

A smooth user interface can be provided to the end user if there are certain minimum requirements to ensure a consistent frame rate and response times for applications and games. Device implementations, depending on the device type, MAY have measurable requirements for the user interface latency and task switching as described in section 2 .

8.2. File I/O Access Performance

Providing a common baseline for a consistent file access performance on the application private data storage ( /data partition) allows app developers to set a proper expectation that would help their software design. Device implementations, depending on the device type, MAY have certain requirements described in section 2 for the following read and write operations:

• Sequential write performance . Measured by writing a 256MB file using 10MB write buffer.
• Random write performance . Measured by writing a 256MB file using 4KB write buffer.
• Sequential read performance . Measured by reading a 256MB file using 10MB write buffer.
• Random read performance . Measured by reading a 256MB file using 4KB write buffer.

8.3. Power-Saving Modes

If device implementations include features to improve device power management that are included in AOSP (eg App Standby Bucket, Doze) or extend the features to apply stronger restrictions than the RESTRICTED App Standby Bucket , they:

• [C-1-1] MUST NOT deviate from the AOSP implementation for the triggering, maintenance, wakeup algorithms and the use of global system settings or DeviceConfig of App Standby and Doze power-saving modes.
• [C-1-2] MUST NOT deviate from the AOSP implementation for the use of global settings or DeviceConfig to manage the throttling of jobs, alarm and network for apps in each bucket for App standby.
• [C-1-3] MUST NOT deviate from the AOSP implementation for the number of the App Standby Buckets used for App Standby.
• [C-1-4] MUST implement App Standby Buckets and Doze as described in Power Management .
• [C-1-5] MUST return true for PowerManager.isPowerSaveMode() when the device is on power save mode.
• [C-1-6] MUST provide user affordance to display all apps that are exempted from App Standby and Doze power-saving modes or any battery optimizations and MUST implement the ACTION_REQUEST_IGNORE_BATTERY_OPTIMIZATIONS intent to ask the user to allow an app to ignore battery optimizations.
• [C-SR-1] Are STRONGLY RECOMMENDED to provide user affordance to enable and disable the battery saver feature.
• [C-SR-2] Are STRONGLY RECOMMENDED to provide user affordance to display all apps that are exempted from App Standby and Doze power-saving modes.

If device implementations extend power management features that are included in AOSP and that extension applies more stringent restrictions than the Rare App Standby Bucket , refer to section 3.5.1 .

In addition to the power-saving modes, Android device implementations MAY implement any or all of the 4 sleeping power states as defined by the Advanced Configuration and Power Interface (ACPI).

If device implementations implement S4 power states as defined by the ACPI, they:

• [C-1-1] MUST enter this state only after the user has taken an explicit action to put the device in an inactive state (eg by closing a lid that is physically part of the device or turning off a vehicle or television) and before the user re-activates the device (eg by opening the lid or turning the vehicle or television back on).

If device implementations implement S3 power states as defined by the ACPI, they:

• [C-2-1] MUST meet C-1-1 above, or, MUST enter S3 state only when third-party applications do not need the system resources (eg the screen, CPU).

  Conversely, MUST exit from S3 state when third-party applications need the system resources, as described on this SDK.

  For example, while the third-party applications request to keep the screen on through FLAG_KEEP_SCREEN_ON or keep CPU running through PARTIAL_WAKE_LOCK , the device MUST NOT enter S3 state unless, as described in C-1-1, the user has taken explicit action to put the device in an inactive state. Conversely, at a time when a task that third-party apps implement through JobScheduler is triggered or Firebase Cloud Messaging is delivered to third-party apps, the device MUST exit the S3 state unless the user has put the device in an inactive state. These are not comprehensive examples and AOSP implements extensive wake-up signals that trigger a wakeup from this state.

8.4. Power Consumption Accounting

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

Implementações de dispositivos:

• [C-SR-1] STRONGLY RECOMMENDED to provide a per-component power profile that defines the current consumption value for each hardware component and the approximate battery drain caused by the components over time as documented in the Android Open Source Project site.
• [C-SR-2] STRONGLY RECOMMENDED to report all power consumption values in milliampere hours (mAh).
• [C-SR-3] STRONGLY RECOMMENDED to report CPU power consumption per each process's UID. O Android Open Source Project atende ao requisito por meio da implementação do módulo do kernel uid_cputime .
• [C-SR-4] STRONGLY RECOMMENDED to make this power usage available via the adb shell dumpsys batterystats shell command to the app developer.
• SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application.

8.5. Consistent Performance

Performance can fluctuate dramatically for high-performance long-running apps, either because of the other apps running in the background or the CPU throttling due to temperature limits. Android includes programmatic interfaces so that when the device is capable, the top foreground application can request that the system optimize the allocation of the resources to address such fluctuations.

Implementações de dispositivos:

• [C-0-1] MUST report the support of Sustained Performance Mode accurately through the PowerManager.isSustainedPerformanceModeSupported() API method.

• SHOULD support Sustained Performance Mode.

If device implementations report support of Sustained Performance Mode, they:

• [C-1-1] MUST provide the top foreground application a consistent level of performance for at least 30 minutes, when the app requests it.
• [C-1-2] MUST honor the Window.setSustainedPerformanceMode() API and other related APIs.

If device implementations include two or more CPU cores, they:

• SHOULD provide at least one exclusive core that can be reserved by the top foreground application.

If device implementations support reserving one exclusive core for the top foreground application, they:

• [C-2-1] MUST report through the Process.getExclusiveCores() API method the ID numbers of the exclusive cores that can be reserved by the top foreground application.
• [C-2-2] MUST not allow any user space processes except the device drivers used by the application to run on the exclusive cores, but MAY allow some kernel processes to run as necessary.

If device implementations do not support an exclusive core, they:

• [C-3-1] MUST return an empty list through the Process.getExclusiveCores() API method.

9. Security Model Compatibility

Implementações de dispositivos:

• [C-0-1] MUST implement a security model consistent with the Android platform security model as defined in Security and Permissions reference document in the APIs in the Android developer documentation.

• [C-0-2] MUST support installation of self-signed applications without requiring any additional permissions/certificates from any third parties/authorities.

If device implementations declare the android.hardware.security.model.compatible feature, they:

• [C-1-1] MUST support the requirements listed in the following subsections.

9.1. Permissões

Implementações de dispositivos:

• [C-0-1] MUST support the Android permissions model and the Android Roles Model as defined in the Android developer documentation. Specifically, they MUST enforce each permission and role defined as described in the SDK documentation; no permissions and no roles may be omitted, altered, or ignored.

• MAY add additional permissions, provided the new permission ID strings are not in the android.\* namespace.

• [C-0-2] Permissions with a protectionLevel of PROTECTION_FLAG_PRIVILEGED MUST only be granted to apps preinstalled in the privileged path(s) of the system image (as well as APEX files ) and be within the subset of the explicitly allowlisted permissions for each aplicativo. The AOSP implementation meets this requirement by reading and honoring the allowlisted permissions for each app from the files in the etc/permissions/ path and using the system/priv-app path as the privileged path.

Start new requirements for 15 (AOSP experimental)

[C-0-16] (February 5, 2024 preview)

• [C-0-16] Permissions with a protectionLevel of PROTECTION_SIGNATURE MUST only be granted to either:

  • Apps preinstalled on the system image (as well as APEX files ).
  • Apps allowlisted with allowed permissions if they are not included in the system image.

  The AOSP implementation meets this requirement by reading and honoring the allowlisted permissions for each app from the files in the etc/permissions/ path.

Acabar com novos requisitos

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

Implementações de dispositivos:

• [C-0-3] MUST show a dedicated interface for the user to decide whether to grant the requested runtime permissions and also provide an interface for the user to manage runtime permissions.

• [C-0-5] MUST NOT grant any runtime permissions to apps unless:

  • They are installed at time of device shipment, AND

  • The user's consent can be obtained before the application uses the permission,

    OU

  • The runtime permissions are granted by the default permission grant policy or for holding a platform role .

• [C-0-6] MUST grant the android.permission.RECOVER_KEYSTORE permission only to system apps that register a properly secured Recovery Agent. A properly secured Recovery Agent is defined as an on-device software agent that synchronizes with an off-device remote storage, that is equipped with secure hardware with protection equivalent or stronger than what is described in Google Cloud Key Vault Service to prevent brute-force attacks on the lockscreen knowledge factor.

Implementações de dispositivos:

• [C-0-7] MUST adhere to Android location permission properties when an app requests the location or physical activity data through standard Android API or proprietary mechanism. Such data includes but not limited to:

  • Device's location (eg latitude and longitude) as described in section 9.8.8 .
  • Information that can be used to determine or estimate the device's location (eg SSID, BSSID, Cell ID, or location of the network that the device is connected to).
  • User's physical activity or classification of the physical activity.

More specifically, device implementations:

• [C-0-8] MUST obtain user consent to allow an app to access the location or physical activity data.
• [C-0-9] MUST grant a runtime permission ONLY to the app that holds sufficient permission as described on SDK. For example, TelephonyManager#getServiceState requires android.permission.ACCESS_FINE_LOCATION ).

The only exceptions to the Android location permission properties above are for apps not accessing Location to derive or identify user location; especificamente:

• When apps hold the RADIO_SCAN_WITHOUT_LOCATION permission.
• For device configuration and setup purposes, where system apps hold the NETWORK_SETTINGS or NETWORK_SETUP_WIZARD permission.

Permissions can be marked as restricted altering their behavior.

• [C-0-10] Permissions marked with the flag hardRestricted MUST NOT be granted to an app unless:

  • An app APK file is in the system partition.
  • The user assigns a role that is associated with the hardRestricted permissions to an app.
  • The installer grants the hardRestricted to an app.
  • An app is granted the hardRestricted on an earlier Android version.

• [C-0-11] Apps holding a softRestricted permission MUST get only limited access and MUST NOT gain full access until allowlisted as described in the SDK, where full and limited access is defined for each softRestricted permission (for example, READ_EXTERNAL_STORAGE ).

• [C-0-12] MUST NOT provide any custom functions or APIs to bypass the permission restrictions defined in setPermissionPolicy and setPermissionGrantState APIs.

• [C-0-13] MUST use the AppOpsManager APIs to record and track each and every programmatic access of data protected by dangerous permissions from Android activities and services.

• [C-0-14] MUST only assign roles to applications with functionalities that meet the role requirements.

• [C-0-15] MUST not define roles that are duplicates or superset functionality of roles defined by the platform.

If devices report android.software.managed_users , they:

• [C-1-1] MUST NOT have the following permissions silently granted by the admin:
  • Location (ACCESS_BACKGROUND_LOCATION, ACCESS_COARSE_LOCATION, ACCESS_FINE_LOCATION).
  • Camera (CAMERA)
  • Microphone (RECORD_AUDIO)
  • Body sensor (BODY_SENSORS)
  • Physical activity (ACTIVITY_RECOGNITION)

If device implementations provide a user affordance to choose which apps can draw on top of other apps with an activity that handles the ACTION_MANAGE_OVERLAY_PERMISSION intent, they:

• [C-2-1] MUST ensure that all activities with intent filters for the ACTION_MANAGE_OVERLAY_PERMISSION intent have the same UI screen, regardless of the initiating app or any information it provides.

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

• [C-3-1] MUST show a disclaimer during fully managed device setup (device owner setup) stating that the IT admin will have the ability to allow apps to control settings on the phone including microphone, camera and location, with options for user to continue setup or exit setup UNLESS the admin has opted out of control of permissions on the device.

If device implementations pre-install any packages that hold any of the System UI Intelligence , System Ambient Audio Intelligence , System Audio Intelligence , System Notification Intelligence , System Text Intelligence , or System Visual Intelligence roles, the packages:

• [C-4-1] MUST fulfill all requirements outlined for device implementations in sections "9.8.6 OS-level and ambient data and 9.8.15 Sandboxed API implementations".

If device implementations include a default application to support the VoiceInteractionService they:

• [C-5-1] MUST NOT grant ACCESS_FINE_LOCATION as the default for that application.

9.2. UID and Process Isolation

Implementações de dispositivos:

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

9.3. Filesystem Permissions

Implementações de dispositivos:

• [C-0-1] MUST support the Android file access permissions model as defined in the Security and Permissions reference .

9.4. Alternate Execution Environments

Device implementations MUST keep consistency of the Android security and permission model, even if they include runtime environments that execute applications using some other software or technology than the Dalvik Executable Format or native code. Em outras palavras:

• [C-0-1] Alternate runtimes MUST themselves be Android applications, and abide by the standard Android security model, as described elsewhere in section 9 .

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

• [C-0-3] Alternate runtimes MUST NOT permit applications to make use of features protected by Android permissions restricted to system applications.

• [C-0-4] Alternate runtimes MUST abide by the Android sandbox model and installed applications using an alternate runtime MUST NOT reuse the sandbox of any other app installed on the device, except through the standard Android mechanisms of shared user ID and signing certificate .

• [C-0-5] Alternate runtimes MUST NOT launch with, grant, or be granted access to the sandboxes corresponding to other Android applications.

• [C-0-6] Alternate runtimes MUST NOT be launched with, be granted, or grant to other applications any privileges of the superuser (root), or of any other user ID.

• [C-0-7] When the .apk files of alternate runtimes are included in the system image of device implementations, it MUST be signed with a key distinct from the key used to sign other applications included with the device implementations.

• [C-0-8] When installing applications, alternate runtimes MUST obtain user consent for the Android permissions used by the application.

• [C-0-9] When an application needs to make use of a device resource for which there is a corresponding Android permission (such as Camera, GPS, etc.), the alternate runtime MUST inform the user that the application will be able to access that resource.

• [C-0-10] When the runtime environment does not record application capabilities in this manner, the runtime environment MUST list all permissions held by the runtime itself when installing any application using that runtime.

• Alternate runtimes SHOULD install apps via the PackageManager into separate Android sandboxes (Linux user IDs, etc.).

• Alternate runtimes MAY provide a single Android sandbox shared by all applications using the alternate runtime.

9.5. Multi-User Support

Android includes support for multiple users and provides support for full user isolation and clone user profiles with partial isolation(ie single additional user profile of type android.os.usertype.profile.CLONE ).

• Device implementations MAY but SHOULD NOT enable multi-user if they use removable media for primary external storage.

If device implementations include support for multiple users, they:

• [C-1-2] MUST, for each user, implement a security model consistent with the Android platform security model as defined in Security and Permissions reference document in the APIs.
• [C-1-3] MUST have separate and isolated shared application storage (aka /sdcard ) directories for each user instance.
• [C-1-4] MUST ensure that applications owned by and running on behalf a given user cannot list, read, or write to the files owned by any other user, even if the data of both users are stored on the same volume or sistema de arquivo.
• [C-1-5] MUST encrypt the contents of the SD card when multiuser is enabled using a key stored only on non-removable media accessible only to the system if device implementations use removable media for the external storage APIs. As this will make the media unreadable by a host PC, device implementations will be required to switch to MTP or a similar system to provide host PCs with access to the current user's data.

If device implementations include support for multiple users, then for all users except users specifically created for running dual instances of the same app, they:

• [C-2-1] MUST have separate and isolated shared application storage (aka /sdcard) directories for each user instance.
• [C-2-2] MUST ensure that applications owned by and running on behalf of a given user cannot list, read, or write to the files owned by any other user, even if the data of both users are stored on the same volume or filesystem.

Device implementations MAY create a single additional user profile of type android.os.usertype.profile.CLONE against the primary user (and only against the primary user) for the purpose of running dual instances of the same app. These dual instances share partially isolated storage, are presented to the end user in the launcher at the same time and appear in the same recents view. For example, this could be used to support the user installing two separate instances of a single app on a dual-SIM device.

If device implementations create the additional user profile discussed above, then they:

• [C-3-1] MUST only provide access to storage or data that is either already accessible to the parent user profile or is directly owned by this additional user profile.
• [C-3-2] MUST NOT have this as a work profile.
• [C-3-3] MUST have isolated private app data directories from the parent user account.
• [C-3-4] MUST NOT allow the additional user profile to be created if there is a Device Owner provisioned (see section 3.9.1) or allow a Device Owner to be provisioned without removing the additional user profile first.

If device implementations create the additional user profile discussed above, then they:

• [C-4-1] MUST allow the below intents originating from the additional profile to be handled by applications of the primary user on the device:

  • Intent.ACTION_VIEW
  • Intent.ACTION_SENDTO
  • Intent.ACTION_SEND
  • Intent.ACTION_EDIT
  • Intent.ACTION_INSERT
  • Intent.ACTION_INSERT_OR_EDIT
  • Intent.ACTION_SEND_MULTIPLE
  • Intent.ACTION_PICK
  • Intent.ACTION_GET_CONTENT
  • MediaStore.ACTION_IMAGE_CAPTURE
  • MediaStore.ACTION_VIDEO_CAPTURE

• [C-4-2] MUST inherit all device policy user restrictions and selected non-user restrictions(list below) applied on the primary user of the device to this additional user profile.

  • setScreenCaptureDisabled
  • setAccountManagementDisabled
  • setCameraDisabled
  • setPermittedInputMethods
  • setApplicationHidden
  • setPersonalAppsSuspended

• [C-4-3] MUST only allow writing contacts from this additional profile via the following intents:

  • ContactsContract.Intents.Insert.ACTION
  • Intent.ACTION_PICK
  • Intent.ACTION_EDIT
  • Intent.ACTION_INSERT_OR_EDIT

• [C-4-4] MUST NOT have contact syncs running for applications running in this additional user profile.

• [C-4-5] MUST only allow applications in the additional profile that have a launcher activity to access contacts that are already accessible to the parent user profile.

9.6. Premium SMS Warning

Android includes support for warning users of any outgoing premium SMS message . Premium SMS messages are text messages sent to a service registered with a carrier that may incur a charge to the user.

Se as implementações de dispositivos declararem suporte para android.hardware.telephony , elas:

• [C-1-1] MUST warn users before sending a SMS message to numbers identified by regular expressions defined in /data/misc/sms/codes.xml file in the device. The upstream Android Open Source Project provides an implementation that satisfies this requirement.

9.7. Recursos de segurança

Device implementations MUST ensure compliance with security features in both the kernel and platform as described below.

The Android Sandbox includes features that use the Security-Enhanced Linux (SELinux) mandatory access control (MAC) system, seccomp sandboxing, and other security features in the Linux kernel. Implementações de dispositivos:

• [C-0-1] MUST maintain compatibility with existing applications, even when SELinux or any other security features are implemented below the Android framework.
• [C-0-2] MUST NOT have a visible user interface when a security violation is detected and successfully blocked by the security feature implemented below the Android framework, but MAY have a visible user interface when an unblocked security violation occurs resulting in a successful explorar.
• [C-0-3] MUST NOT make SELinux or any other security features implemented below the Android framework configurable to the user or app developer.
• [C-0-4] MUST NOT allow an application that can affect another application through an API (such as a Device Administration API) to configure a policy that breaks compatibility.
• [C-0-5] MUST split the media framework into multiple processes so that it is possible to more narrowly grant access for each process as described in the Android Open Source Project site.
• [C-0-6] MUST implement a kernel application sandboxing mechanism which allows filtering of system calls using a configurable policy from multithreaded programs. The upstream Android Open Source Project meets this requirement through enabling the seccomp-BPF with threadgroup synchronization (TSYNC) as described in the Kernel Configuration section of source.android.com .

Kernel integrity and self-protection features are integral to Android security. Implementações de dispositivos:

• [C-0-7] MUST implement kernel stack buffer overflow protection mechanisms. Examples of such mechanisms are CC_STACKPROTECTOR_REGULAR and CONFIG_CC_STACKPROTECTOR_STRONG .
• [C-0-8] MUST implement strict kernel memory protections where executable code is read-only, read-only data is non-executable and non-writable, and writable data is non-executable (eg CONFIG_DEBUG_RODATA or CONFIG_STRICT_KERNEL_RWX ).
• [C-0-9] MUST implement static and dynamic object size bounds checking of copies between user-space and kernel-space (eg CONFIG_HARDENED_USERCOPY ) on devices originally shipping with API level 28 or higher.
• [C-0-10] MUST NOT execute user-space memory when executing in the kernel mode (eg hardware PXN, or emulated via CONFIG_CPU_SW_DOMAIN_PAN or CONFIG_ARM64_SW_TTBR0_PAN ) on devices originally shipping with API level 28 or higher.
• [C-0-11] MUST NOT read or write user-space memory in the kernel outside of normal usercopy access APIs (eg hardware PAN, or emulated via CONFIG_CPU_SW_DOMAIN_PAN or CONFIG_ARM64_SW_TTBR0_PAN ) on devices originally shipping with API level 28 or higher.
• [C-0-12] MUST implement kernel page table isolation if the hardware is vulnerable to CVE-2017-5754 on all devices originally shipping with API level 28 or higher (eg CONFIG_PAGE_TABLE_ISOLATION or CONFIG_UNMAP_KERNEL_AT_EL0 ).

• [C-0-13] MUST implement branch prediction hardening if the hardware is vulnerable to CVE-2017-5715 on all devices originally shipping with API level 28 or higher (eg CONFIG_HARDEN_BRANCH_PREDICTOR ).

• [C-SR-1] Are STRONGLY RECOMMENDED to enable stack initialization in the kernel to prevent uses of uninitialized local variables ( CONFIG_INIT_STACK_ALL or CONFIG_INIT_STACK_ALL_ZERO ). Also, device implementations SHOULD NOT assume the value used by the compiler to initialize the locals.

• [C-SR-2] Are STRONGLY RECOMMENDED to keep kernel data which is written only during initialization marked read-only after initialization (eg __ro_after_init ).

• [C-SR-3] Are STRONGLY RECOMMENDED to randomize the layout of the kernel code and memory, and to avoid exposures that would compromise the randomization (eg CONFIG_RANDOMIZE_BASE with bootloader entropy via the /chosen/kaslr-seed Device Tree node or EFI_RNG_PROTOCOL ) .

• [C-SR-4] Are STRONGLY RECOMMENDED to enable control flow integrity (CFI) in the kernel to provide additional protection against code-reuse attacks (eg CONFIG_CFI_CLANG and CONFIG_SHADOW_CALL_STACK ).

• [C-SR-5] Are STRONGLY RECOMMENDED not to disable Control-Flow Integrity (CFI), Shadow Call Stack (SCS) or Integer Overflow Sanitization (IntSan) on components that have it enabled.

• [C-SR-6] Are STRONGLY RECOMMENDED to enable CFI, SCS, and IntSan for any additional security-sensitive userspace components as explained in CFI and IntSan .

• [C-SR-7] Are STRONGLY RECOMMENDED to enable stack initialization in the kernel to prevent uses of uninitialized local variables ( CONFIG_INIT_STACK_ALL or CONFIG_INIT_STACK_ALL_ZERO ). Also, device implementations SHOULD NOT assume the value used by the compiler to initialize the locals.

• [C-SR-8] Are STRONGLY RECOMMENDED to enable heap initialization in the kernel to prevent uses of uninitialized heap allocations ( CONFIG_INIT_ON_ALLOC_DEFAULT_ON ) and they SHOULD NOT assume the value used by the kernel to initialize those allocations.

If device implementations use a Linux kernel that is capable of supporting SELinux, they:

• [C-1-1] MUST implement SELinux.
• [C-1-2] MUST set SELinux to global enforcing mode.
• [C-1-3] MUST configure all domains in enforcing mode. No permissive mode domains are allowed, including domains specific to a device/vendor.
• [C-1-4] MUST NOT modify, omit, or replace the neverallow rules present within the system/sepolicy folder provided in the upstream Android Open Source Project (AOSP) and the policy MUST compile with all neverallow rules present, for both AOSP SELinux domains as well as device/vendor specific domains.
• [C-1-5] MUST run third-party applications targeting API level 28 or higher in per-application SELinux sandboxes with per-app SELinux restrictions on each application's private data directory.
• SHOULD retain the default SELinux policy provided in the system/sepolicy folder of the upstream Android Open Source Project and only further add to this policy for their own device-specific configuration.

If device implementations use kernel other than Linux or Linux without SELinux, they:

• [C-2-1] MUST use a mandatory access control system that is equivalent to SELinux.

If device implementations use I/O devices capable of DMA, they:

• [C-SR-9] Are STRONGLY RECOMMENDED to isolate each I/O device capable of DMA, using an IOMMU (egthe ARM SMMU).

Android contains multiple defense-in-depth features that are integral to device security. In addition, Android focuses on reducing key classes of common bugs that contribute to poor quality and security.

In order to reduce memory bugs, device implementations:

• [C-SR-10] Are STRONGLY RECOMMENDED to be tested using userspace memory error detection tools like MTE for ARMv9 devices, HWASan for ARMv8+ devices or ASan for other device types.
• [C-SR-11] Are STRONGLY RECOMMENDED to be tested using kernel memory error detection tools like KASAN (CONFIG_KASAN, CONFIG_KASAN_HW_TAGS for ARMv9 devices, CONFIG_KASAN_SW_TAGS for ARMv8 devices or CONFIG_KASAN_GENERIC for other device types).
• [C-SR-12] Are STRONGLY RECOMMENDED to be using memory error detection tools in production like MTE, GWP-ASan and KFENCE.

If device implementations use an Arm TrustZone-based TEE, they:

• [C-SR-13] Are STRONGLY RECOMMENDED to use a standard protocol for memory sharing, between Android and the TEE, like Arm Firmware Framework for Armv8-A (FF-A).
• [C-SR-14] Are STRONGLY RECOMMENDED to restrict trusted applications to only accessing memory which has been explicitly shared with them via the above protocol. If the device has support for the Arm S-EL2 exception level, this should be enforced by the secure partition manager. Otherwise, this should be enforced by the TEE OS.

A Memory Safety technology is a technology that mitigates at least the following classes of bugs with a high (> 90%) probability in applications that use the android:memtagMode manifest option:

• heap buffer overflow
• use after free
• double free
• wild free (free of a non-malloc pointer)

Implementações de dispositivos:

• [C-SR-15] Are STRONGLY RECOMMENDED to set ro.arm64.memtag.bootctl_supported .

If device implementations set the system property ro.arm64.memtag.bootctl_supported to true, they:

• [C-3-1] MUST allow the system property arm64.memtag.bootctl to accept a comma-separated list of the following values, with the desired effect applied on the next subsequent reboot:

  • memtag : a Memory Safety technology as defined above is enabled
  • memtag-once : a Memory Safety technology as defined above is transiently enabled, and is automatically disabled upon, next reboot
  • memtag-off : a Memory Safety technology as defined above is disabled

• [C-3-2] MUST allow the shell user to set arm64.memtag.bootctl .

• [C-3-3] MUST allow any process to read arm64.memtag.bootctl .

• [C-3-4] MUST set arm64.memtag.bootctl to the currently requested state upon boot, it MUST also update the property, if the device implementation allows to modify the state without changing the system property.

• [C-SR-16] Are STRONGLY RECOMMENDED to show a Developer Setting that sets memtag-once and reboots the device. With a compatible bootloader, the Android Open Source Project meets the above requirements through the MTE bootloader protocol .

Start new requirements for 15 (AOSP experimental)

[C-SR-17 through C-SR-20] [Renumbered] (April 8, 2024 preview)

If a device declares android.hardware.telephony , supports the radio capability CAPABILITY_USES_ALLOWED_NETWORK_TYPES_BITMASK , and includes a cellular modem that supports 2G connections, the device implementation:

• [C-SR-17] Are STRONGLY RECOMMENDED to provide user affordance to disable and enable 2G.

• [C-SR-18] Are STRONGLY RECOMMENDED to not override the user affordance to disable and enable 2G through any other device entity except by a device admin using UserManager.DISALLOW_CELLULAR_2G .

• [C-SR-19] Are STRONGLY RECOMMENDED to call TelephonyManager.setAllowedNetworkTypesForReason with reason ALLOWED_NETWORK_TYPES_REASON_ENABLE_2G to achieve this requirement.

• [C-SR-20] Are STRONGLY RECOMMENDED to determine Cellular modem support for 2G by calling TelephonyManager.getSupportedRadioAccessFamily . See Disable 2G for details.

Note: The STRONGLY RECOMMENDED requirements (C-SR-17 through C-SR-20) will become MUSTs in Android W (AOSP experimental).

Acabar com novos requisitos

[C-4-1 through C-4-4] (December 11, 2023 preview)

If a device declares android.hardware.telephony , supports the radio capability CAPABILITY_USES_ALLOWED_NETWORK_TYPES_BITMASK , and includes a cellular modem that supports 2G connections, the device implementation:

• [C-4-1] MUST provide user affordance to disable and enable 2G.
• [C-4-2] MUST not override the user affordance to disable and enable 2G through any other device entity except by a device admin using the UserManager.DISALLOW_CELLULAR_2G .
• [C-4-3] MUST call TelephonyManager.setAllowedNetworkTypesForReason with reason ALLOWED_NETWORK_TYPES_REASON_ENABLE_2G to achieve this requirement.
• [C-4-4] MUST determine Cellular modem support for 2G by calling TelephonyManager.getSupportedRadioAccessFamily . See Disable 2G for details.

Acabar com novos requisitos

9.8. Privacidade

9.8.1. Usage History

Android stores the history of the user's choices and manages such history by UsageStatsManager .

Implementações de dispositivos:

• [C-0-1] MUST keep a reasonable retention period of such user history.
• [C-SR-1] Are STRONGLY RECOMMENDED to keep the 14 days retention period as configured by default in the AOSP implementation.

Android stores the system events using the StatsLog identifiers, and manages such history via the StatsManager and the IncidentManager System API.

Implementações de dispositivos:

• [C-0-2] MUST only include the fields marked with DEST_AUTOMATIC in the incident report created by the System API class IncidentManager .
• [C-0-3] MUST not use the system event identifiers to log any other event than what is described in the StatsLog SDK documents. If additional system events are logged, they MAY use a different atom identifier in the range between 100,000 and 200,000.

9.8.2. Gravação

Implementações de dispositivos:

• [C-0-1] MUST NOT preload or distribute software components out-of-box that send the user's private information (eg keystrokes, text displayed on the screen, bugreport) off the device without the user's consent or clear ongoing notifications.

Start new requirements for 15 (AOSP experimental)

[C-0-2] [Reverted] (April 8, 2024 preview)

• [C-0-2] MUST display a user warning and obtain explicit user consent allowing any sensitive information that is displayed on the user's screen to be captured each and every time a session to capture the screen is started via the MediaProjection.createVirtualDisplay() , VirtualDeviceManager.createVirtualDisplay() , or proprietary APIs.

Acabar com novos requisitos

[C-0-2] (February 5, 2024 preview)

• [C-0-2] MUST display a user warning and obtain explicit user consent allowing any sensitive information that is displayed on the user's screen to be captured each and every time a session to capture the screen is started via the MediaProjection.createVirtualDisplay() , VirtualDeviceManager.createVirtualDisplay() , or proprietary APIs.

Acabar com novos requisitos

• [C-0-3] MUST have an ongoing notification to the user while screen casting or screen recording is enabled. AOSP meets this requirement by showing an ongoing notification icon in the status bar.

• [C-SR-1] Are STRONGLY RECOMMENDED to display a user warning which is exactly the same message as implemented in AOSP but CAN be altered as long as the message clearly warns the user that any sensitive information on the user's screen is captured.

Start new requirements for 15 (AOSP experimental)

[C-0-4] [Reverted] (April 8, 2024 preview)

• [C-0-4] MUST NOT provide users an affordance to disable future prompts of the user consent to capture the screen, unless the session is started by a system app that the user has allowed to associate() with the android.app.role.COMPANION_DEVICE_APP_STREAMING or the android.app.role.COMPANION_DEVICE_NEARBY_DEVICE_STREAMING device profile.

Acabar com novos requisitos

[C-0-4] (February 5, 2024 preview)

• [C-0-4] MUST NOT provide users an affordance to disable future prompts of the user consent to capture the screen. , unless the session is started by a system app that the user has allowed to associate() with the android.app.role.COMPANION_DEVICE_APP_STREAMING or the android.app.role.COMPANION_DEVICE_NEARBY_DEVICE_STREAMING device profile.

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[C-0-5 and C-0-6] (April 8, 2024 preview)

Implementações de dispositivos:

• [C-0-5] MUST NOT alter an app's setting of FLAG_SECURE .

• [C-0-6] MUST provide users an affordance to turn off the screen recording for sensitive notification protection feature via Developer Options menu.

Acabar com novos requisitos

If device implementations include functionality in the system that either captures the contents displayed on the screen and/or records the audio stream played on the device other than via the System API ContentCaptureService , or other proprietary means described in Section 9.8.6 OS-level and ambient data , they:

• [C-1-1] MUST have an ongoing notification to the user whenever this functionality is enabled and actively capturing/recording.

If device implementations include a component enabled out-of-box, capable of recording ambient audio and/or record the audio played on the device to infer useful information about user's context, they:

• [C-2-1] MUST NOT store in persistent on-device storage or transmit off the device the recorded raw audio or any format that can be converted back into the original audio or a near facsimile, except with explicit user consent.

Start new requirements for 15 (AOSP experimental)

[C-3-1 through C-3-3] (April 8, 2024 preview)

If screen recording is active and is not initiated through System UI or via OEM bug reporting app, device notification implementations:

• [C-3-1] MUST display content when the notifications' visibility is VISIBILITY_PUBLIC or redacted notification content (no more than app icon and app name) on all surfaces where notification content is visible (including lock screen, heads up notifications, notification shade, bubbles, and Launcher dots) unless either of the following is true:

  • Partial screen is shared.
  • Notification content does not reveal any personal or sensitive user data such as when notification is a foreground service posted by the app recording the screen, or notification is from the Android system.

• [C-3-2] MUST hide app windows which have posted notifications containing detected one-time passwords by calling WindowState.setSecureLocked(true) .

• [C-3-3] MUST hide sensitive views or an app window when CONTENT_SENSITIVITY_SENSITIVE is visible or when the framework heuristic determines that the view contains any sensitive data as follows:

  • View.AUTOFILL_HINT_USERNAME
  • View.AUTOFILL_HINT_PASSWORD
  • InputType TYPE_TEXT_VARIATION_PASSWORD
  • InputType TYPE_TEXT_VARIATION_WEB_PASSWORD
  • InputType TYPE_NUMBER_VARIATION_PASSWORD
  • InputType TYPE_TEXT_VARIATION_VISIBLE_PASSWORD

Acabar com novos requisitos

[C-3-1 through C-3-5] (February 26, 2024 preview)

If screen sharing recording is active, device implementations:

• [C-3-1] MUST only display notification content when notifications' visibility is VISIBILITY_PUBLIC , or display redacted notification content (no more than app icon and app name) on all surfaces where notification content is visible (including lock screen, notification shade, bubbles, and Launcher dots), unless at least one of the following is true:

  • A foreground service notification is posted by the app recording the screen.
  • Screenshare is initiated by Bug report handler or System (including screen record from Quick Settings tile).
  • Partial screen sharing is in use.

• [C-3-2] MUST hide app windows which have posted notifications containing detected one-time passwords by calling WindowState.setSecureLocked(true) .

• [C-3-3] MUST hide sensitive views or app window when a sensitive view ( CONTENT_SENSITIVITY_SENSITIVE ) is visible.

• [C-3-4] MUST NOT alter an app's setting of FLAG_SECURE .

• [C-3-5] MUST provide an option for users an affordance to turn off the screen recording for sensitive notification protection feature via Developer Options menu.

Acabar com novos requisitos

[C-3-1 through C-3-3] (February 5, 2024 preview)

When screen sharing is active, a device implementation:

• [C-3-1] MUST only display notification content when setVisibility() is set to public, or display redacted notification content (only app icon and app name) on all surfaces where notification content is visible (including lock screen, notification shade, bubbles, and Launcher dots), unless either:

  • Notification is Foreground Service notification of the screen share / record app; FGS notifications can be shown fully / unredacted.
  • Screenshare is initiated by:
    • Bug report handler
    • SysUI (including screen record from Quick Settings tile)
  • Partial screen sharing is in use.

• [C-3-2] MUST hide app windows of apps that have posted notifications containing detected one-time passwords.

  • MUST be implemented by calling WindowState.setSecureLocked(true) on the app's windows.
    • Implementation SHOULD NOT interfere with apps setting FLAG_SECURE .

• [C-3-3] MUST provide an option for users an affordance to turn off the feature via developer mode.

Acabar com novos requisitos

A "microphone indicator" refers to a view on screen, which is constantly visible to the user and cannot be obscured, which users understand as a microphone is in use(through unique text, color, icon, or some combination).

A "camera indicator" refers to a view on screen, which is constantly visible to the user and cannot be obscured, which users understand as a camera is in use (through unique text, color, icon, or some combination).

After the first one second displayed, an indicator can change visually, such as becoming smaller, and is not required to show as originally presented and understood.

The microphone indicator may be merged with an actively displayed camera indicator, provided that text, icons, or colors indicate to the user that microphone use has begun.

The camera indicator may be merged with an actively displayed microphone indicator, provided that text, icons, or colors indicate to the user that the camera use has begun.

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

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

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

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

9.8.3. Conectividade

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

• [C-1-1] MUST present a user interface asking for the user's consent before allowing access to the contents of the shared storage over the USB port.

9.8.4. Tráfego de rede

Implementações de dispositivos:

• [C-0-1] MUST preinstall the same root certificates for the system-trusted Certificate Authority (CA) store as provided in the upstream Android Open Source Project.
• [C-0-2] MUST ship with an empty user root CA store.
• [C-0-3] MUST display a warning to the user indicating the network traffic may be monitored, when a user root CA is added.

If device traffic is routed through a VPN, device implementations:

• [C-1-1] MUST display a warning to the user indicating either:
  • That network traffic may be monitored.
  • That network traffic is being routed through the specific VPN application providing the VPN.

If device implementations have a mechanism, enabled out-of-box by default, that routes network data traffic through a proxy server or VPN gateway (for example, preloading a VPN service with android.permission.CONTROL_VPN granted), they:

• [C-2-1] MUST ask for the user's consent before enabling that mechanism, unless that VPN is enabled by the Device Policy Controller via the DevicePolicyManager.setAlwaysOnVpnPackage() , in which case the user does not need to provide a separate consent, but MUST only be notified.

If device implementations implement a user affordance to toggle on the "always-on VPN" function of a 3rd-party VPN app, they:

• [C-3-1] MUST disable this user affordance for apps that do not support always-on VPN service in the AndroidManifest.xml file via setting the SERVICE_META_DATA_SUPPORTS_ALWAYS_ON attribute to false .

9.8.5. Device Identifiers

Implementações de dispositivos:

• [C-0-1] MUST prevent access to the device serial number and, where applicable, IMEI/MEID, SIM serial number, and International Mobile Subscriber Identity (IMSI) from an app, unless it meets one of the following requirements:
  • is a signed carrier app that is verified by device manufacturers.
  • has been granted the READ_PRIVILEGED_PHONE_STATE permission.
  • has carrier privileges as defined in UICC Carrier Privileges .
  • is a device owner or profile owner that has been granted the READ_PHONE_STATE permission.
  • (For SIM serial number/ICCID only) has the local regulations requirement that the app detect changes in the subscriber's identity.

9.8.6. OS-level and ambient data

Android, through the System APIs, supports a mechanism for device implementations to capture the following sensitive data:

• Text and graphics rendered on-screen, including but not limited to, notifications and assist data via AssistStructure API.
• Media data, such as audio or video, recorded or played by the device.

• Input events (eg key, mouse, gesture, voice, video, and accessibility).

• Any screen or other data sent via the AugmentedAutofillService to the system.

• Any screen or other data accessible via Content Capture APIs.

• Any application data passed to the system via the AppSearchManager API and accessible via AppSearchGlobalManager.query .

• Any text or other data sent via the TextClassifier API to the System TextClassifier ie to the system service to understand the meaning of text, as well as generating predicted next actions based on the text.

• Data indexed by the platform AppSearch implementation, including but not limited to text, graphics, media data or other similar data.

• Audio data obtained as a result of using SpeechRecognizer#onDeviceSpeechRecognizer() by the Speech Recognizer Implementation.

• Audio data obtained in background (continuously) through AudioRecord , SoundTrigger or other Audio APIs, and not resulting in a user-visible indicator

• Camera data obtained in background (continuously) through CameraManager or other Camera APIs, and not resulting in a user-visible indicator

If device implementations capture any of the data above, they:

• [C-1-1] MUST encrypt all such data when stored in the device. This encryption MAY be carried out using Android File Based Encryption, or any of the ciphers listed as API version 26+ described in Cipher SDK .
• [C-1-2] MUST NOT back up either raw or encrypted data using Android backup methods or any other back up methods.
• [C-1-3] MUST only send all such data off the device using a privacy-preserving mechanism, except with explicit user consent every time the data is shared. The privacy-preserving mechanism is defined as "those which allow only analysis in aggregate and prevent matching of logged events or derived outcomes to individual users", to prevent any per-user data being introspectable (eg, implemented using a differential privacy technology such as RAPPOR ).
• [C-1-4] MUST NOT associate such data with any user identity (such as Account ) on the device, except with explicit user consent each time the data is associated.
• [C-1-5] MUST NOT share such data with other OS components that don't follow requirements outlined in the current section (9.8.6 OS-level and ambient data), except with explicit user consent every time it is shared. Unless such functionality is built as an Android SDK API ( AmbientContext , HotwordDetectionService ).
• [C-1-6] MUST provide user affordance to erase such data that the implementation or the proprietary means collects when the data is stored in any form on the device. If the user chooses to erase the data, MUST remove all collected historical data.
• [C-1-7] MUST provide a user affordance to opt-out of the data, collected via AppSearch or proprietary means from being shown in Android platform (eg launcher).

Start new requirements for 15 (AOSP experimental)

[C-SR-1] (February 26, 2024 preview)

• [C-SR-1] Are STRONGLY RECOMMENDED NOT to request the INTERNET permission.

Note: This is now the same as Android 14. Prior preview changes have been withdrawn.

Acabar com novos requisitos

[C-SR-1] (December 11, 2023 preview)

• [C- SR-1 1-8 ] Are STRONGLY RECOMMENDED NOT to MUST not request the INTERNET permission.

Acabar com novos requisitos

• [C-SR-2] Are STRONGLY RECOMMENDED to only access the internet through structured APIs backed by publicly available open-source implementations.
• [C-SR-4] Are STRONGLY RECOMMENDED to be implemented with Android SDK API or a similar OEM-owned open-source repository; and / or be performed in a Sandboxed implementation (see 9.8.15 Sandboxed API implementations).

If device implementations include a service that implements the System API ContentCaptureService , AppSearchManager.index , or any proprietary service that captures the data as described as above, they:

• [C-2-1] MUST NOT allow users to replace the services with a user-installable application or service and MUST only allow the preinstalled services to capture such data.
• [C-2-2] MUST NOT allow any apps other than the preinstalled services mechanism to be able to capture such data.
• [C-2-3] MUST provide user affordance to disable the services.
• [C-2-4] MUST NOT omit user affordance to manage Android permissions that are held by the services and follow Android permissions model as described in Section 9.1. Permission .

Start new requirements for 15 (AOSP experimental)

[C-SR-3] (February 26, 2024 preview)

• [C-SR-3] Are STRONGLY RECOMMENDED to keep the services separate from other system components (eg not binding the service or sharing process IDs) except for the following:
  • Telephony, Contacts, System UI, and Media

Note: This is now the same as Android 14. Prior preview changes have been withdrawn.

Acabar com novos requisitos

[C-SR-3] (December 11, 2023 preview)

• [C- SR-3 1-5 ] Are STRONGLY RECOMMENDED to MUST keep the services separate from other system components (eg not binding the service or sharing process IDs) except for the following:

  • Telephony, Contacts, System UI, and Media

Acabar com novos requisitos

9.8.7. Clipboard Access

Implementações de dispositivos:

• [C-0-1] MUST NOT return a clipped data from the clipboard (eg via the ClipboardManager API) unless the 3rd-party app is the default IME or is the app that currently has focus.

• [C-0-2] MUST clear clipboard data at most 60 minutes after it has last been placed in a clipboard or read from a clipboard.

9.8.8. Localização

Location includes information in the Android Location class( such as Latitude, Longitude, Altitude), as well as identifiers that can be converted to Location. Location can be as fine as DGPS (Differential Global Positioning System) or as coarse as country level locations (like the country code location - MCC - Mobile Country Code).

The following is a list of location types that either directly derive a user's location or can be converted to a user's location. This is not a comprehensive list, but should be used as an example on what Location can directly or indirectly be derived from:

• GPS/GNSS/DGPS/PPP
  • Global Positioning Solution or Global Navigation Satellite System or Differential Global Positioning Solution
  • This also includes Raw GNSS Measurements and GNSS Status
    • Fine Location can be derived from the Raw GNSS Measurements
• Wireless Technologies with unique identifiers such as:
  • Wi-Fi access points (MAC, BSSID, Name, or SSID)
  • Bluetooth/BLE (MAC, BSSID, Name, or SSID)
  • UWB (MAC, BSSID, Name, or SSID)
  • Cell Tower ID (3G, 4G, 5G… including all future Cellular Modem technologies that have unique identifiers)

As a primary point of reference, see the Android APIs which require ACCESS_FINE_Location or ACCESS_COARSE_Location permissions.

Implementações de dispositivos:

• [C-0-1] MUST NOT turn on/off device location setting and Wi-Fi/Bluetooth scanning settings without explicit user consent or user initiation.
• [C-0-2] MUST provide the user affordance to access location related information including recent location requests, app level permissions and usage of Wi-Fi/Bluetooth scanning for determining location.
• [C-0-3] MUST ensure that the application using Emergency Location Bypass API [LocationRequest.setLocationSettingsIgnored()] is a user initiated emergency session (eg dial 911 or text to 911). For Automotive however, a vehicle MAY initiate an emergency session without active user interaction in the case a crash/accident is detected (eg to satisfy eCall requirements).
• [C-0-4] MUST preserve the Emergency Location Bypass API's ability to bypass device location settings without changing the settings.
• [C-0-5] MUST schedule a notification that reminds the user after an app in the background has accessed their location using the [ ACCESS_BACKGROUND_LOCATION ] permission.

9.8.9. Aplicativos instalados

Android apps targeting API level 30 or above cannot see details about other installed apps by default (see Package visibility in the Android SDK documentation).

Implementações de dispositivos:

• [C-0-1] MUST NOT expose to any app targeting API level 30 or above details about any other installed app, unless the app is already able to see details about the other installed app through the managed APIs. This includes but is not limited to details exposed by any custom APIs added by the device implementer, or accessible via the filesystem.
• [C-0-2] MUST NOT give to any app, read or write access to files in any other app's dedicated, app-specific directory within external storage. The only exceptions are as follows:
  • The external storage provider authority (eg apps like DocumentsUI).
  • Download Provider which uses the "downloads" provider authority for downloading files to app storage.
  • Platform-signed media transfer protocol (MTP) apps which use the privileged permission ACCESS_MTP to enable transferring files to another device.
  • Apps which install other apps and have the permission INSTALL_PACKAGES can access only "obb" directories for the purpose of managing APK expansion files .

9.8.10. Connectivity Bug Report

If device implementations declare the android.hardware.telephony feature flag, they:

• [C-1-1] MUST support generating connectivity bug reports via BUGREPORT_MODE_TELEPHONY with BugreportManager.
• [C-1-2] MUST obtain user consent every time BUGREPORT_MODE_TELEPHONY is used to generate a report and MUST NOT prompt the user to consent to all future requests from the application.
• [C-1-3] MUST NOT return the generated report to the requesting app without explicit user consent.
• [C-1-4] Reports generated using BUGREPORT_MODE_TELEPHONY MUST contain at least the following information:
  • TelephonyDebugService dump
  • TelephonyRegistry dump
  • WifiService dump
  • ConnectivityService dump
  • A dump of the calling package's CarrierService instance (if bound)
  • Radio log buffer
  • SubscriptionManagerService dump
• [C-1-5] MUST NOT include the following in the generated reports:
  • Any kind of information that isn't directly related to connectivity debugging.
  • Any kind of user-installed application traffic logs or detailed profiles of user-installed applications/packages (UIDs are okay, package names are not).
• MAY include additional information that is not associated with any user identity. (eg vendor logs).

If device implementations include additional information (eg vendor logs) in bug reports and that information has privacy/security/battery/storage/memory impact, they:

• [C-SR-1] Are STRONGLY RECOMMENDED to have a developer setting defaulted to disabled. The AOSP reference implementation meets this by providing the Enable verbose vendor logging option in developer settings to include additional device-specific vendor logs in the bug reports.

9.8.11. Data blobs sharing

Android, through BlobStoreManager allows apps to contribute data blobs to the System to be shared with a selected set of apps.

If device implementations support shared data blobs as described in the SDK documentation , they:

• [C-1-1] MUST NOT share data blobs belonging to apps beyond what they intended to allow (ie the scope of default access and the other access modes that can be specified using BlobStoreManager.session#allowPackageAccess() , BlobStoreManager.session#allowSameSignatureAccess() , or BlobStoreManager.session#allowPublicAccess() MUST NOT be modified). The AOSP reference implementation meets these requirements.
• [C-1-2] MUST NOT send off device or share with other apps the secure hashes of data blobs (which are used to control access).

9.8.12. Reconhecimento Musical

Android, through the System API MusicRecognitionManager, supports a mechanism for device implementations to request music recognition, given an audio record, and delegate the music recognition to a privileged app implementing the MusicRecognitionService API.

If device implementations include a service that implements the System API MusicRecognitionManager or any proprietary service that streams audio data as described as above, they:

• [C-1-1] MUST enforce that the caller of MusicRecognitionManager holds the MANAGE_MUSIC_RECOGNITION permission
• [C-1-2] MUST enforce that a single, pre-installed, music recognition application implements MusicRecognitionService.
• [C-1-3] MUST NOT allow users to replace the MusicRecognitionManagerService or MusicRecognitionService with a user-installable application or service.
• [C-1-4] MUST ensure that when MusicRecognitionManagerService accesses the audio record and forwards it to the application implementing the MusicRecognitionService, the audio access is tracked via invocations of AppOpsManager.noteOp / startOp .

If device implementations of MusicRecognitionManagerService or MusicRecognitionService store any audio data captured, they:

• [C-2-1] MUST NOT store any raw audio or audio fingerprints on disk at all, or in memory for longer than 14 days.
• [C-2-2] MUST NOT share such data beyond the MusicRecognitionService, except with explicit user consent every time it is shared.

9.8.13. SensorPrivacyManager

If device implementations provide the user a software affordance to turn off the camera and/or microphone input for the device implementation, they:

• [C-1-1] MUST accurately return 'true' for the relevant supportsSensorToggle() API method.
• [C-1-2] MUST, when an app tries to access a blocked microphone or camera, present the user with a non-dismissable user affordance that clearly indicates that the sensor is blocked and requires a choice to continue blocking or unblock as per the AOSP implementation which meets this requirement.
• [C-1-3] MUST only pass blank (or fake) camera and audio data to apps and not report an error code due to the user not turning on the camera nor microphone via the user affordance presented per [C-1-2 ] acima.

9.8.14. Gerenciador de Credenciais

Start new requirements for 15 (AOSP experimental)

9.8.14 (February 26, 2024 preview)

Removed in Android 14.

Device implementations MUST declare support for android.software.credentials and:

• MUST honor the android.settings.CREDENTIAL_PROVIDER intent to allow selection of a preferred provider for the Credential Manager. This provider will be enabled for Autofill and will also be the default location to save new credentials entered through the Credential Manager.
• MUST support at least 2 concurrent credential providers and provide a user affordance in the Setting app to enable or disable providers.

Acabar com novos requisitos

9.8.14 (February 5, 2024 preview)

Removed in Android 14.

Device implementations MUST declare support for android.software.credentials and:

• MUST fully implement the Credential API and honor the android.settings.CREDENTIAL_PROVIDER intent to show a default app settings menu to enable and disable credential providers.
• MUST provide a user affordance in the Setting app to select a preferred provider for Autofill & Credential Manager. This provider will be enabled for autofill and will be the default location to save new credentials via Credential Manager.
• MUST support at least 2 concurrent credential providers and provide a user affordance in the Setting app to enable or disable providers.

Acabar com novos requisitos

9.8.15. Sandboxed API Implementations

Android, through a set of delegate APIs provides a mechanism to process secure OS-level and ambient data. Such processing can be delegated to a preinstalled apk with privileged access and reduced communication capabilities, known as a Sandboxed API Implementation.

Any Sandboxed API implementation:

• [C-0-1] MUST NOT request the INTERNET permission.
• [C-0-2] MUST only access the internet through structured APIs backed by publicly available open-source implementations using privacy-preserving mechanisms, or indirectly via Android SDK APIs. The privacy-preserving mechanism is defined as "those which allow only analysis in aggregate and prevent matching of logged events or derived outcomes to individual users", to prevent any per-user data being introspectable (eg, implemented using a differential privacy technology such as RAPPOR ).
• [C-0-3] MUST keep the services separate from other system components (eg not binding the service or sharing process IDs) except for the following:
  • Telephony, Contacts, System UI, and Media
• [C-0-4] MUST NOT allow users to replace the services with a user-installable application or service
• [C-0-5] MUST only allow the preinstalled services to capture such data. Unless the replacement capability is built into AOSP (eg for Digital Assistant Apps).
• [C-0-6] MUST NOT allow any apps other than the preinstalled services mechanism to be able to capture such data. Unless such capture capability is implemented with an Android SDK API.
• [C-0-7] MUST provide user affordance to disable the services.
• [C-0-8] MUST NOT omit user affordance to manage Android permissions that are held by the services and follow the Android permissions model as described in Section 9.1. Permission .

9.8.16. Continuous Audio and Camera data

Start new requirements for 15 (AOSP experimental)

9.8.16 (February 26, 2024 preview)

In addition to requirements outlined in 9.8.2 Recording, 9.8.6 OS-level and ambient data, and 9.8.15 Sandboxed API implementations, implementations that make use of Audio data obtained in background (continuously) through AudioRecord, SoundTrigger or other Audio APIs OR Camera data obtained in background (continuously) through CameraManager or other Camera APIs:

If device implementations capture any of the data as described in 9.8.2 or section 9.8.6, and if such implementations make use of Audio data obtained in background (continuously) through AudioRecord, SoundTrigger, or other Audio APIs OR Camera data obtained in background (continuously) through CameraManager or other Camera APIs, they:

Acabar com novos requisitos

• [C-0-1] MUST enforce a corresponding indicator (camera and/or microphone as per section 9.8.2 Recording), unless:
  • This access is performed in a Sandboxed implementation (see 9.8.15 Sandboxed API implementation), through a package holding one or more of the following roles: System UI Intelligence , System Ambient Audio Intelligence , System Audio Intelligence , System Notification Intelligence , System Text Intelligence , or System Visual Intelligence .
  • The access is performed through a sandbox, implemented and enforced via mechanisms in AOSP ( HotwordDetectionService , WearableSensingService , VisualQueryDetector ).
  • Audio access is performed for assistive purposes by the Digital Assistant application, supplying SOURCE_HOTWORD as an audio source.
  • The access is performed by the system and implemented with open-source code.
• [C-SR-1] Is STRONGLY RECOMMENDED to require user consent for every functionality utilizing such data, and be disabled by default.
• [C-SR-2] STRONGLY RECOMMENDED to apply the same treatment (ie follow the restrictions outlined in 9.8.2 Recording, 9.8.6 OS-level and ambient data, 9.8.15 Sandboxed API implementations, and 9.8.16 Continuous Audio and Camera data) to Camera data coming from a remote wearable device.

Start new requirements for 15 (AOSP experimental)

[C-1-1] (February 26, 2024 preview)

If the Camera data is supplied from a remote wearable device and accessed in an unencrypted form outside Android OS, sandboxed implementation or a sandboxed functionality built by WearableSensingManager , then they:

If device implementations receive Camera or Microphone data from a remote wearable device and the data is accessed in an unencrypted form outside of Android OS, sandboxed implementation or a sandboxed functionality built by WearableSensingManager , they:

Acabar com novos requisitos

• [C-1-1] MUST indicate to the remote wearable device to display an additional indicator there.

Start new requirements for 15 (AOSP experimental)

[C-2-1] (February 26, 2024 preview)

If devices provide capability to engage with a Digital Assistant Application without the assigned keyword (either handling generic user queries, or analyzing user presence through camera), they:

Acabar com novos requisitos

• [C-2-1] MUST ensure such implementation is provided by a package holding the android.app.role.ASSISTANT role.
• [C-2-2] MUST ensure such implementation utilizes HotwordDetectionService and/or VisualQueryDetectionService Android APIs.

9.8.17. Telemetria

Android stores system and app logs using StatsLog APIs. These logs are managed via StatsManager APIs which can be used by privileged system applications.

StatsManager also provides a way to collect data categorized as privacy sensitive from devices with a privacy preserving mechanism. In particular, StatsManager::query API provides the ability to query restricted metric categories defined in StatsLog .

Any implementation querying and collecting restricted metrics from StatsManager:

• [C-0-1] MUST be the sole application/implementation on the device and hold the READ_RESTRICTED_STATS permission.
• [C-0-2] MUST only send telemetry data and the log of the device using a privacy-preserving mechanism. The privacy-preserving mechanism is defined as "those which allow only analysis in aggregate and prevent matching of logged events or derived outcomes to individual users", to prevent any per-user data being introspectable (eg, implemented using a differential privacy technology such as RAPPOR ).
• [C-0-3] MUST NOT associate such data with any user identity (such as Account ) on the device.
• [C-0-4] MUST NOT share such data with other OS components that don't follow requirements outlined in the current section (9.8.17 Privacy-preserving Telemetry).
• [C-0-5] MUST provide a user affordance to enable/disable privacy-preserving telemetry collection, use, and sharing.
• [C-0-6] MUST provide user affordance to erase such data that the implementation collects if the data is stored in any form on the device. If the user chose to erase the data, MUST remove all data currently stored on the device.
• [C-0-7] MUST disclose underlying privacy-preserving protocol implementation in an open source repository.
• [C-0-8 ]MUST enforce data egress policies in this section to gate collection of data in restricted metric categories defined in StatsLog .

9.9. Data Storage Encryption

All devices MUST meet the requirements of section 9.9.1. Devices which launched on an API level earlier than that of this document are exempted from the requirements of sections 9.9.2 and 9.9.3; instead they MUST meet the requirements in section 9.9 of the Android Compatibility Definition document corresponding to the API level on which the device launched.

9.9.1. Direct Boot

Implementações de dispositivos:

• [C-0-1] MUST implement the Direct Boot mode APIs even if they do not support Storage Encryption.

• [C-0-2] The ACTION_LOCKED_BOOT_COMPLETED and ACTION_USER_UNLOCKED Intents MUST still be broadcast to signal Direct Boot aware applications that Device Encrypted (DE) and Credential Encrypted (CE) storage locations are available for user.

9.9.2. Encryption requirements

Implementações de dispositivos:

• [C-0-1] MUST encrypt the application private data ( /data partition), as well as the application shared storage partition ( /sdcard partition) if it is a permanent, non-removable part of the device.
• [C-0-2] MUST enable the data storage encryption by default at the time the user has completed the out-of-box setup experience.

• [C-0-3] MUST meet the above data storage encryption requirement by implementing one of the following two encryption methods:

  • File Based Encryption (FBE) and Metadata Encryption as described in section 9.9.3.1.
  • Per-User Block-Level Encryption as described in section 9.9.3.2.

Note: Device implementations which shipped on an API level 28 or earlier and do not meet the requirements in 9.9.2 through a system software update MUST meet the requirements in section 9.9 of the Android Compatibility Definition document corresponding to the API level on which the device enviado.

9.9.3. Encryption Methods

If device implementations are encrypted, they:

• [C-1-1] MUST boot up without challenging the user for credentials and allow Direct Boot aware apps to access to the Device Encrypted (DE) storage after the ACTION_LOCKED_BOOT_COMPLETED message is broadcasted.
• [C-1-2] MUST only allow access to Credential Encrypted (CE) storage after the user has unlocked the device by supplying their credentials (eg. passcode, pin, pattern or fingerprint) and the ACTION_USER_UNLOCKED message is broadcasted.
• [C-1-13] MUST NOT offer any method to unlock the CE protected storage without either the user-supplied credentials, a registered escrow key or a resume on reboot implementation meeting the requirements in section 9.9.4 .
• [C-1-4] MUST use Verified Boot.

9.9.3.1. File Based Encryption with Metadata Encryption

If device implementations use File Based Encryption with Metadata Encryption, they:

• [C-1-5] MUST encrypt file contents and filesystem metadata using AES-256-XTS or Adiantum. AES-256-XTS refers to the Advanced Encryption Standard with a 256-bit cipher key length, operated in XTS mode; the full length of the key is 512 bits. Adiantum refers to Adiantum-XChaCha12-AES, as specified at https://github.com/google/adiantum. Filesystem metadata is data such as file sizes, ownership, modes, and extended attributes (xattrs).
• [C-1-6] MUST encrypt file names using AES-256-CBC-CTS, AES-256-HCTR2, or Adiantum.
• [C-1-12] If the device has Advanced Encryption Standard (AES) instructions (such as ARMv8 Cryptography Extensions on ARM-based devices, or AES-NI on x86-based devices) then the AES-based options above for file name, file contents, and filesystem metadata encryption MUST be used, not Adiantum.
• [C-1-13] MUST use a cryptographically strong and non-reversible key derivation function (eg HKDF-SHA512) to derive any needed subkeys (eg per-file keys) from the CE and DE keys. "Cryptographically strong and non-reversible" means that the key derivation function has a security strength of at least 256 bits and behaves as a pseudorandom function family over its inputs.
• [C-1-14] MUST NOT use the same File Based Encryption (FBE) keys or subkeys for different cryptographic purposes (eg for both encryption and key derivation, or for two different encryption algorithms).
• [C-1-15] MUST ensure that all non-deleted blocks of encrypted file contents on persistent storage were encrypted using combinations of encryption key and initialization vector (IV) that depend on both the file and the offset within the file. In addition, all such combinations MUST be distinct, except where the encryption is done using inline encryption hardware that only supports an IV length of 32 bits.
• [C-1-16] MUST ensure that all non-deleted encrypted filenames on persistent storage in distinct directories were encrypted using distinct combinations of encryption key and initialization vector (IV).

• [C-1-17] MUST ensure that all encrypted filesystem metadata blocks on persistent storage were encrypted using distinct combinations of encryption key and initialization vector (IV).

• Keys protecting CE and DE storage areas and filesystem metadata:

  • [C-1-7] MUST be cryptographically bound to a hardware-backed Keystore. This keystore MUST be bound to Verified Boot and the device's hardware root of trust.
  • [C-1-8] CE keys MUST be bound to a user's lock screen credentials.
  • [C-1-9] CE keys MUST be bound to a default passcode when the user has not specified lock screen credentials.
  • [C-1-10] MUST be unique and distinct, in other words no user's CE or DE key matches any other user's CE or DE keys.
  • [C-1-11] MUST use the mandatorily supported ciphers, key lengths and modes.
  • [C-1-12] MUST be securely erased during bootloader unlock and lock as described here .

• SHOULD make preinstalled essential apps (eg Alarm, Phone, Messenger) Direct Boot aware.

The upstream Android Open Source project provides a preferred implementation of File Based Encryption based on the Linux kernel "fscrypt" encryption feature, and of Metadata Encryption based on the Linux kernel "dm-default-key" feature.

Note: Device implementations that shipped on API level 28 or earlier and do not meet the requirements in 9.9.3 through a system software update MUST meet the requirements in section 9.9 of the Android Compatibility Definition Document corresponding to the API level on which the device shipped .

9.9.3.2. Per-User Block-Level Encryption

If device implementations use per-user block-level encryption, they:

• [C-1-1] MUST enable multi-user support as described in section 9.5.
• [C-1-2] MUST provide per-user partitions, either using raw partitions or logical volumes.
• [C-1-3] MUST use unique and distinct encryption keys per-user for encryption of the underlying block devices.

• [C-1-4] MUST use AES-256-XTS for block-level encryption of the user partitions.

• The keys protecting the per-user block-level encrypted devices:

  • [C-1-5] MUST be cryptographically bound to a hardware-backed Keystore. This keystore MUST be bound to Verified Boot and the device's hardware root of trust.
  • [C-1-6] MUST be bound to the corresponding user's lock screen credentials.

Per-user block-level encryption can be implemented using the Linux kernel "dm-crypt" feature over per-user partitions.

9.9.4. Resume on Reboot

Resume on Reboot allows unlocking the CE storage of all apps, including those that do not yet support Direct Boot, after a reboot initiated by an OTA. This feature enables users to receive notifications from installed apps after the reboot.

An implementation of Resume-on-Reboot must continue to ensure that when a device falls into an attacker's hands, it is extremely difficult for that attacker to recover the user's CE-encrypted data, even if the device is powered on, CE storage is unlocked, and the user has unlocked the device after receiving an OTA. For insider attack resistance, we also assume the attacker gains access to broadcast cryptographic signing keys.

Especificamente:

• [C-0-1] CE storage MUST NOT be readable even for the attacker who physically has the device and then has these capabilities and limitations:

  • Can use the signing key of any vendor or company to sign arbitrary messages.
  • Can cause an OTA to be received by the device.
  • Can modify the operation of any hardware (AP, flash etc) except as detailed below, but such modification involves a delay of at least an hour and a power cycle that destroys RAM contents.
  • Cannot modify the operation of tamper-resistant hardware (eg Titan M).
  • Cannot read the RAM of the live device.
  • Cannot obtain the user's credential (PIN, pattern, password) or otherwise cause it to be entered.

By way of example, a device implementation that implements and complies with all of the descriptions found here will be compliant with [C-0-1].

9.10. Device Integrity

The following requirements ensure there is transparency to the status of the device integrity. Implementações de dispositivos:

• [C-0-1] MUST correctly report through the System API method PersistentDataBlockManager.getFlashLockState() whether their bootloader state permits flashing of the system image.

• [C-0-2] MUST support Verified Boot for device integrity.

If device implementations are already launched without supporting Verified Boot on an earlier version of Android and cannot add support for this feature with a system software update, they MAY be exempted from the requirement.

Verified Boot is a feature that guarantees the integrity of the device software. If device implementations support the feature, they:

• [C-1-1] MUST declare the platform feature flag android.software.verified_boot .
• [C-1-2] MUST perform verification on every boot sequence.
• [C-1-3] MUST start verification from an immutable hardware key that is the root of trust and go all the way up to the system partition.
• [C-1-4] MUST implement each stage of verification to check the integrity and authenticity of all the bytes in the next stage before executing the code in the next stage.
• [C-1-5] MUST use verification algorithms as strong as current recommendations from NIST for hashing algorithms (SHA-256) and public key sizes (RSA-2048).
• [C-1-6] MUST NOT allow boot to complete when system verification fails, unless the user consents to attempt booting anyway, in which case the data from any non-verified storage blocks MUST not be used.
• [C-1-7] MUST NOT allow verified partitions on the device to be modified unless the user has explicitly unlocked the bootloader.
• [C-1-8] MUST use tamper-evident storage: for storing whether the bootloader is unlocked. Tamper-evident storage means that the bootloader can detect if the storage has been tampered with from inside Android.
• [C-1-9] MUST prompt the user, while using the device, and require physical confirmation before allowing a transition from bootloader locked mode to bootloader unlocked mode.
• [C-1-10] MUST implement rollback protection for partitions used by Android (eg boot, system partitions) and use tamper-evident storage for storing the metadata used for determining the minimum allowable OS version.
• [C-1-11] MUST securely erase all user data during bootloader unlock and lock, as per '9.12. Data Deletion' (including the userdata partition and any NVRAM spaces).

Start new requirements for 15 (AOSP experimental)

[C-1-12 through C-1-14] (February 26, 2024 preview)

• [C-SR-1] If there are multiple discrete chips in the device (eg radio, specialized image processor), the boot process of each of those chips is STRONGLY RECOMMENDED to verify every stage upon booting.

• [C-1-12] MUST verify every stage upon booting, with the boot process of each of the chips, if there are multiple discrete chips in the device (eg, radio, specialized image processor).

• [C-1-14] MUST verify the signature at least once per boot for allow listed packages that are listed as require-strict-signature in system config.

Acabar com novos requisitos

[C-1-12 through C-1-14] (December 11, 2023 preview)

• [C-SR-1] If there are multiple discrete chips in the device (eg radio, specialized image processor), the boot process of each of those chips is STRONGLY RECOMMENDED to verify every stage upon booting.

• [C-1-12] MUST verify every stage upon booting, with the boot process of each of the chips, if there are multiple discrete chips in the device (eg radio, specialized image processor).

• [C-1-13] MUST verify all immutable partitions loaded during the Android boot sequence, except for the partitions that are not part of standard partitions AND that do not contain privileged apps.

• [C-1-14] MUST verify the signature at least once per boot for allow listed packages that are listed as require-strict-signature in system config.

Acabar com novos requisitos

• [C-SR-2] Are STRONGLY RECOMMENDED to verify all privileged app APK files with a chain of trust rooted in partitions protected by Verified Boot.
• [C-SR-3] Are STRONGLY RECOMMENDED to verify any executable artifacts loaded by a privileged app from outside its APK file (such as dynamically loaded code or compiled code) before executing them or STRONGLY RECOMMENDED not to execute them at all.
• SHOULD implement rollback protection for any component with persistent firmware (eg modem, camera) and SHOULD use tamper-evident storage for storing the metadata used for determining the minimum allowable version.

Start new requirements for 15 (AOSP experimental)

Note about C-1-8 to C-1-13 (February 26, 2024 preview)

If device implementations are already launched without supporting C-1-8 through C-1-11 on an earlier version of Android and cannot add support for these requirements with a system software update, they MAY be exempted from the requirements.

Acabar com novos requisitos

Note about C-1-8 to C-1-13 (November 13, 2023 preview)

If device implementations are already launched without supporting C-1-8 through C-1-11 C-1-13 on an earlier version of Android and cannot add support for these requirements with a system software update, they MAY be exempted from the requirements .

Acabar com novos requisitos

The upstream Android Open Source Project provides a preferred implementation of this feature in the external/avb/ repository, which can be integrated into the bootloader used for loading Android.

If device implementations have the ability to verify file content on the per-page basis, then they:

• [C-2-1] support cryptographically verifying file content without reading the whole file.

• [C-2-2] MUST NOT allow the read requests on a protected file to succeed when the read content is not verified per [C-2-1] above.

• [C-2-4] MUST return file checksum in O(1) for enabled files.

If device implementations are already launched without the ability to verify file content against a trusted key on an earlier Android version and can not add support for this feature with a system software update, they MAY be exempted from the requirement. The upstream Android Open Source project provides a preferred implementation of this feature based on the Linux kernel fs-verity feature.

Start new requirements for 15 (AOSP experimental)

[C-SR-4], [C-3-1], [C-3-2], and [C-3-3] (February 5, 2024 preview)

Implementações de dispositivos:

• [C-SR-4] Are STRONGLY RECOMMENDED to support the Android Protected Confirmation API .

If device implementations support the Android Protected Confirmation API they:

• [C-3-1] MUST report true for the ConfirmationPrompt.isSupported() API.

• [C-3-2] MUST ensure that code running in the Android OS including its kernel, malicious or otherwise, cannot generate a positive response without user interaction.

• [C-3-3] MUST ensure that the user has been able to review and approve the prompted message even in the event that the Android OS, including its kernel, is compromised.

Acabar com novos requisitos

9.11. Keys and Credentials

The Android Keystore System allows app developers to store cryptographic keys in a container and use them in cryptographic operations through the KeyChain API or the Keystore API . Implementações de dispositivos:

• [C-0-1] MUST allow at least 8,192 keys to be imported or generated.

Start new requirements for 15 (AOSP experimental)

[C-0-2] [Reverted] (April 8, 2024 preview)

• [C-0-2] The lock screen authentication MUST implement a time interval between failed attempts. With n as the failed attempt count, the time interval MUST be at least 30 seconds for 9 < n < 30. For n > 29, the time interval value MUST be at least 30*2^floor((n-30)/10)) seconds or at least 24 hours, whichever is smaller.

Acabar com novos requisitos

[C-0-2] (December 11, 2023 preview)

• [C-0-2] The lock screen authentication MUST implement a time interval between failed attempts. With n as the failed attempt count, the time interval MUST be at least 30 seconds for 9 < n < 30. For n > 29, the time interval value MUST be at least 30*2^floor((n-30)/10)) seconds or at least 24 hours, whichever is smaller for n > 4 the time interval value MUST be at least 60*3^(n-5) seconds. .

Acabar com novos requisitos

• SHOULD not limit the number of keys that can be generated.

When the device implementation supports a secure lock screen, it:

• [C-1-1] MUST back up the keystore implementation with an isolated execution environment.
• [C-1-2] MUST have implementations of RSA, AES, ECDSA, ECDH (if IKeyMintDevice is supported), 3DES, and HMAC cryptographic algorithms and MD5, SHA1, and SHA-2 family hash functions to properly support the Android Keystore system's supported algorithms in an area that is securely isolated from the code running on the kernel and above. O isolamento seguro DEVE bloquear todos os mecanismos potenciais pelos quais o código do kernel ou do espaço do usuário possa acessar o estado interno do ambiente isolado, incluindo DMA. O Android Open Source Project (AOSP) upstream atende a esse requisito usando a implementação Trusty , mas outra solução baseada em ARM TrustZone ou uma implementação segura revisada por terceiros de um isolamento adequado baseado em hipervisor são opções alternativas.
• [C-1-3] MUST perform the lock screen authentication in the isolated execution environment and only when successful, allow the authentication-bound keys to be used. As credenciais da tela de bloqueio DEVEM ser armazenadas de forma que permita que apenas o ambiente de execução isolado execute a autenticação da tela de bloqueio. O Android Open Source Project upstream fornece o Gatekeeper Hardware Abstraction Layer (HAL) e o Trusty, que podem ser usados ​​para satisfazer esse requisito.

Start new requirements for 15 (AOSP experimental)

[C-1-4] (December 11, 2023 preview)

• [C-1-4] MUST support key attestation where the attestation signing key is protected by secure hardware and signing is performed in secure hardware. The attestation signing keys MUST be shared across large enough number of devices to prevent the keys prevented from being used as permanent device identifiers.

  Note: To meet this requirement, you must share the same attestation key for a given SKU unless at least 100,000 units of a given that SKU are produced. If more than 100,000 units of an that SKU are produced, a different key MAY be used for each group of 100,000 units after that. Alternatively, the Remote Key Provisioning solution may be used to provision short-lived attestation keys to the device.

Acabar com novos requisitos

Observe que se uma implementação de dispositivo já tiver sido lançada em uma versão anterior do Android, tal dispositivo estará isento do requisito de ter um armazenamento de chaves apoiado por um ambiente de execução isolado e suportar o atestado de chave, a menos que declare o android.hardware.fingerprint que requer um keystore apoiado por um ambiente de execução isolado.

• [C-1-5] MUST allow the user to choose the Sleep timeout for transition from the unlocked to the locked state, with a minimum allowable timeout up to 15 seconds. Automotive devices, that lock the screen whenever the head unit is turned off or the user is switched, MAY NOT have the Sleep timeout configuration.
• [C-1-6] MUST support IKeymasterDevice 4.0, IKeymasterDevice 4.1, IKeyMintDevice version 1 or IKeyMintDevice version 2.
• [C-SR-1] Is STRONGLY RECOMMENDED to support IKeyMintDevice version 1.

9.11.1. Secure Lock Screen, Authentication and Virtual Devices

The AOSP implementation follows a tiered authentication model where a knowledge-factory based primary authentication can be backed by either a secondary strong biometric, or by weaker tertiary modalities.

Implementações de dispositivos:

• [C-SR-1] Are STRONGLY RECOMMENDED to set only one of the following as the primary authentication method:

  • A numerical PIN
  • An alphanumerical password

  • A swipe pattern on a grid of exactly 3x3 dots

    Note that the above authentication methods are referred as the recommended primary authentication methods in this document.

• [C-0-1] MUST limit the number of failed primary authentication attempts.

• [C-SR-5] Are STRONGLY RECOMMENDED to implement an upper bound of 20 failed primary authentication attempts and if users consent and opt-in the feature, perform a "Factory Data Reset" after exceeding the limit of failed primary authentication attempts.

If device implementations set a numerical PIN as the recommended primary authentication method, then:

• [C-SR-6] A PIN is STRONGLY RECOMMENDED to have at least 6 digits, or equivalently a 20-bit entropy.

Start new requirements for 15 (AOSP experimental)

[C-SR-7] [Reverted] (April 8, 2024 preview)

• [C-SR-7] A PIN of a length less than 6 digits is STRONGLY RECOMMENDED NOT to allow automatic entry without user interaction to avoid revealing the PIN length.

Acabar com novos requisitos

[C-14-1] (December 11, 2023 preview)

• [ C-SR-7 C-14-1 ] A PIN of a length less than 6 digits is STRONGLY RECOMMENDED MUST NOT to allow automatic entry without user interaction to avoid revealing the PIN length.

Acabar com novos requisitos

If device implementations add or modify the recommended primary authentication methods and use a new authentication method as a secure way to lock the screen, the new authentication method:

• [C-2-1] MUST be the user authentication method as described in Requiring User Authentication For Key Use .

If device implementations add or modify the authentication methods to unlock the lock screen if based on a known secret and use a new authentication method to be treated as a secure way to lock the screen:

• [C-3-1] The entropy of the shortest allowed length of inputs MUST be greater than 10 bits.
• [C-3-2] The maximum entropy of all possible inputs MUST be greater than 18 bits.
• [C-3-3] The new authentication method MUST NOT replace any of the recommended primary authentication methods (ie PIN, pattern, password) implemented and provided in AOSP.
• [C-3-4] The new authentication method MUST be disabled when the Device Policy Controller (DPC) application has set the password requirements policy via the DevicePolicyManager.setRequiredPasswordComplexity() with a more restrictive complexity constant than PASSWORD_COMPLEXITY_NONE or via the DevicePolicyManager.setPasswordQuality() method with a more restrictive constant than PASSWORD_QUALITY_BIOMETRIC_WEAK .
• [C-3-5] New authentication methods MUST either fall back to the recommended primary authentication methods (ie PIN, pattern, password) once every 72 hours or less OR clearly disclose to the user that some data will not be backed up in order to preserve the privacy of their data.

If device implementations add or modify the recommended primary authentication methods to unlock the lock screen and use a new authentication method that is based on biometrics to be treated as a secure way to lock the screen, the new method:

• [C-4-1] MUST meet all requirements described in section 7.3.10 for Class 1 (formerly Convenience ).
• [C-4-2] MUST have a fall-back mechanism to use one of the recommended primary authentication methods which is based on a known secret.
• [C-4-3] MUST be disabled and only allow the recommended primary authentication to unlock the screen when the Device Policy Controller (DPC) application has set the keyguard feature policy by calling the method DevicePolicyManager.setKeyguardDisabledFeatures() , with any of the associated biometric flags (ie KEYGUARD_DISABLE_BIOMETRICS , KEYGUARD_DISABLE_FINGERPRINT , KEYGUARD_DISABLE_FACE , or KEYGUARD_DISABLE_IRIS ).

If the biometric authentication methods do not meet the requirements for Class 3 (formerly Strong ) as described in section 7.3.10 :

• [C-5-1] The methods MUST be disabled if the Device Policy Controller (DPC) application has set the password requirements quality policy via the DevicePolicyManager.setRequiredPasswordComplexity() with a more restrictive complexity bucket than PASSWORD_COMPLEXITY_LOW or using DevicePolicyManager.setPasswordQuality() method with a more restrictive quality constant than PASSWORD_QUALITY_BIOMETRIC_WEAK .
• [C-5-2] The user MUST be challenged for the recommended primary authentication (eg: PIN, pattern, password) as described in [C-1-7] and [C-1-8] in section 7.3.10 .
• [C-5-3] The methods MUST NOT be treated as a secure lock screen, and MUST meet the requirements that start with C-8 in this section below.

If device implementations add or modify the authentication methods to unlock the lock screen and a new authentication method is based on a physical token or the location:

• [C-6-1] They MUST have a fall-back mechanism to use one of the recommended primary authentication methods which is based on a known secret and meet the requirements to be treated as a secure lock screen.
• [C-6-2] The new method MUST be disabled and only allow one of the recommended primary authentication methods to unlock the screen when the Device Policy Controller (DPC) application has set the policy with either:
  • The DevicePolicyManager.setKeyguardDisabledFeatures(KEYGUARD_DISABLE_TRUST_AGENTS) method
  • The DevicePolicyManager.setPasswordQuality() method with a more restrictive quality constant than PASSWORD_QUALITY_NONE .
  • The DevicePolicyManager.setRequiredPasswordComplexity() method with a more restrictive complexity bucket than PASSWORD_COMPLEXITY_NONE .
• [C-6-3] The user MUST be challenged for one of the recommended primary authentication methods (egPIN, pattern, password) at least once every 4 hours or less. When a physical token meets the requirements for TrustAgent implementations in CX, timeout restrictions defined in C-9-5 apply instead.
• [C-6-4] The new method MUST NOT be treated as a secure lock screen and MUST follow the constraints listed in C-8 below.

Se as implementações de dispositivos tiverem uma tela de bloqueio segura e incluírem um ou mais agentes confiáveis, que implementam a API do sistema TrustAgentService , elas:

• [C-7-1] MUST have clear indication in the settings menu and on the lock screen when device lock is deferred or can be unlocked by trust agent(s). For example, AOSP meets this requirement by showing a text description for the "Automatically lock setting" and "Power button instantly locks" in the settings menu and a distinguishable icon on the lock screen.
• [C-7-2] MUST respect and fully implement all trust agent APIs in the DevicePolicyManager class, such as the KEYGUARD_DISABLE_TRUST_AGENTS constant.
• [C-7-3] MUST NOT fully implement the TrustAgentService.addEscrowToken() function on a device that is used as a primary personal device (eg handheld) but MAY fully implement the function on device implementations that are typically shared (eg Android Television or Automotive device).
• [C-7-4] MUST encrypt all stored tokens added by TrustAgentService.addEscrowToken() .
• [C-7-5] MUST NOT store the encryption key or escrow token on the same device where the key is used. For example, it is allowed for a key stored on a phone to unlock a user account on a TV. For Automotive devices, it is not allowed for the escrow token to be stored on any part of the vehicle.
• [C-7-6] MUST inform the user about the security implications before enabling the escrow token to decrypt the data storage.
• [C-7-7] MUST have a fall-back mechanism to use one of the recommended primary authentication methods.
• [C-7-9] The user MUST be challenged for one of the recommended primary authentication (eg: PIN, pattern, password) methods as described in [C-1-7] and [C-1-8] in section 7.3.10 , unless the safety of the user (eg driver distraction) is of concern.
• [C-7-10] MUST NOT be treated as a secure lock screen and MUST follow the constraints listed in C-8 below.
• [C-7-11] MUST NOT allow TrustAgents on primary personal devices (eg: handheld) to unlock the device, and can only use them to keep an already unlocked device in the unlocked state for up to a maximum of 4 hours. The default implementation of TrustManagerService in AOSP meets this requirement.
• [C-7-12] MUST use a cryptographically secure (eg UKEY2) communication channel to pass the escrow token from the storage device to the target device.

If device implementations add or modify the authentication methods to unlock the lock screen that is not a secure lock screen as described above, and use a new authentication method to unlock the keyguard:

• [C-8-1] The new method MUST be disabled when the Device Policy Controller (DPC) application has set the password quality policy via the DevicePolicyManager.setPasswordQuality() method with a more restrictive quality constant than PASSWORD_QUALITY_NONE or via the DevicePolicyManager.setRequiredPasswordComplexity() with a more restrictive complexity constant than 'PASSWORD_COMPLEXITY_NONE'.
• [C-8-2] They MUST NOT reset the password expiration timers set by DevicePolicyManager.setPasswordExpirationTimeout() .
• [C-8-3] They MUST NOT expose an API for use by third-party apps to determine the lock state.

If device implementations allow applications to create secondary virtual displays and do not support associated input events, such as via VirtualDeviceManager , they:

• [C-9-1] MUST lock these secondary virtual display(s) when the device's default display is locked, and unlock these secondary virtual display(s) when the device's default display is unlocked.

If device implementations allow applications to create secondary virtual displays and support associated input events, such as via VirtualDeviceManager , they:

• [C-10-1] MUST support separate lock states per virtual device
• [C-10-2] MUST disconnect all virtual devices upon idle timeout
• [C-10-3] MUST have an idle timeout
• [C-10-4] MUST lock all displays when the user initiates a lockdown , including via the lockdown user affordance required for handheld devices (see Section 2.2.5[9.11/H-1-2] )
• [C-10-5] MUST have separate virtual device instances per user

Start new requirements for 15 (AOSP experimental)

[C-10-6] (February 5, 2024 preview)

• [C-10-6] MUST disable the creation of associated input events via VirtualDeviceManager when indicated by app streaming as indicated by DevicePolicyManager.setNearbyAppStreamingPolicy .

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

[C-10-7] (February 5, 2024 preview)

• [C-10-7] MUST either:
  • Disable clipboard usage
  • Enable a separate clipboard for each device that supports clipboards

• [C-10-7] MUST use a separate clipboard solely for each virtual device (or disable the clipboard for virtual devices)

Acabar com novos requisitos

• [C-10-11] MUST disable authentication UI on virtual devices, including knowledge factor entry and biometric prompt

Start new requirements for 15 (AOSP experimental)

[C-10-12] [Removed] (February 5, 2024 preview)

• [C-10-12] MUST restrict intents initiated from a virtual device to display only on the same virtual device

• [C-10-12]
  This requirement is removed in Android 15 (AOSP experimental).

Acabar com novos requisitos

• [C-10-13] MUST not use a virtual device lock state as user authentication authorization with the Android Keystore System. See KeyGenParameterSpec.Builder.setUserAuthentication* .

Start new requirements for 15 (AOSP experimental)

[C-10-14 and C-10-15] (February 5, 2024 preview)

• [C-10-14] MUST provide a user affordance to enable clipboard sharing between devices prior to sharing clipboard data between physical and virtual devices if the device is implementing a shared clipboard.
• [C-10-15] MUST show notifications when clipboard data is accessed across devices, and MUST make content inaccessible after one minute measured from the initial sharing time.

Acabar com novos requisitos

When device implementations allow the user to transfer the primary authentication knowledge-factor from a source device to a target device, such as for initial setup of the target device, they:

• [C-11-1] MUST encrypt the knowledge-factor with protection guarantees similar to those described in the Google Cloud Key Vault Service security whitepaper when transferring the knowledge-factor from the source device to the target device such that the knowledge-factor cannot be remotely decrypted or used to remotely unlock either device.
• [C-11-2] MUST, on the source device , ask the user to confirm the knowledge-factor of the source device before transferring the knowledge-factor to the target device.
• [C-11-3] MUST, on a target device lacking any set primary authentication knowledge-factor, ask the user to confirm a transferred knowledge-factor on the target device before setting that knowledge-factor as the primary authentication knowledge-factor for the target device and before making available any data transferred from a source device.

If device implementations have a secure lock screen and include one or more trust agents, which call the TrustAgentService.grantTrust() System API with the FLAG_GRANT_TRUST_TEMPORARY_AND_RENEWABLE flag they:

• [C-12-1] MUST only call grantTrust() with the flag when connected to a proximate physical device with a lockscreen of its own, and when the user has authenticated their identity against that lockscreen. Proximate devices can use on-wrist or on-body detection mechanisms after a one-time user unlock to satisfy the user authentication requirement.
• [C-12-2] MUST put the device implementation into the TrustState.TRUSTABLE state when the screen is turned off (such as via a button press or display time out) and the TrustAgent has not revoked trust. The AOSP satisfies this requirement.
• [C-12-3] MUST only move the device from TrustState.TRUSTABLE to the TrustState.TRUSTED state if the TrustAgent is still granting trust based on the requirements in C-12-1.
• [C-12-4] MUST call TrustManagerService.revokeTrust() after a maximum of 24 hours from granting trust, an 8 hour idle window, or when the underlying connection to the proximate physical device is lost.

If device implementations allow applications to create secondary virtual displays and support associated input events such as via VirtualDeviceManager and the displays are not marked with VIRTUAL_DISPLAY_FLAG_SECURE, they:

• [C-13-8] MUST block activities with the attribute android:canDisplayOnRemoteDevices or the meta-data android.activity.can_display_on_remote_devices set to false from being started on the virtual device.

Start new requirements for 15 (AOSP experimental)

[C-13-9] (February 5, 2024 preview)

• [C-13-9] MUST block activities which do not explicitly enable streaming and which indicate they show sensitive content, including via SurfaceView#setSecure , and FLAG_SECURE , or SYSTEM_FLAG_HIDE_NON_SYSTEM_OVERLAY_WINDOWS, from being started on the virtual device.

Acabar com novos requisitos

If device implementations support separate display power states through DeviceStateManager AND support separate display lock states through KeyguardDisplayManager , they:

• [C-SR-2] Are STRONGLY RECOMMENDED to utilize a credential meeting requirements defined in section 9.11.1 or a Biometric meeting at least Class 1 specifications defined in section 7.3.10 to allow independent unlocking from the default device display.
• [C-SR-3] Are STRONGLY RECOMMENDED to constrain separate display unlock via a defined display timeout.
• [C-SR-4] Are STRONGLY RECOMMENDED to allow user to globally lock all displays through lockdown from primary handheld device.

9.11.2. StrongBox

The Android Keystore System allows app developers to store cryptographic keys in a dedicated secure processor as well as the isolated execution environment described above. Such a dedicated secure processor is called "StrongBox". Requirements C-1-3 through C-1-11 below define the requirements a device must meet to qualify as a StrongBox.

Device implementations that have a dedicated secure processor:

• [C-SR-1] Are STRONGLY RECOMMENDED to support StrongBox. StrongBox will likely become a requirement in a future release.

If device implementations support StrongBox, they:

• [C-1-1] MUST declare FEATURE_STRONGBOX_KEYSTORE .

• [C-1-2] MUST provide dedicated secure hardware that is used to back keystore and secure user authentication. The dedicated secure hardware may be used for other purposes as well.

• [C-1-3] MUST have a discrete CPU that shares no cache, DRAM, coprocessors or other core resources with the application processor (AP).

• [C-1-4] MUST ensure that any peripherals shared with the AP cannot alter StrongBox processing in any way, or obtain any information from the StrongBox. The AP MAY disable or block access to StrongBox.

• [C-1-5] MUST have an internal clock with reasonable accuracy (+-10%) that is immune to manipulation by the AP.

• [C-1-6] MUST have a true random number generator that produces uniformly-distributed and unpredictable output.

• [C-1-7] MUST have tamper resistance, including resistance against physical penetration, and glitching.

• [C-1-8] MUST have side-channel resistance, including resistance against leaking information via power, timing, electromagnetic radiation, and thermal radiation side channels.

• [C-1-9] MUST have secure storage which ensures confidentiality, integrity, authenticity, consistency, and freshness of the contents. The storage MUST NOT be able to be read or altered, except as permitted by the StrongBox APIs.

• To validate compliance with [C-1-3] through [C-1-9], device implementations:

Start new requirements for 15 (AOSP experimental)

[C-1-10] (December 11, 2023 preview)

• [C-1-10] MUST include the hardware that is certified against the Secure IC Protection Profile BSI-CC-PP-0084-2014 or BSI-CC-PP-0117-2022 , or is evaluated by a nationally accredited testing laboratory incorporating High attack potential vulnerability assessment according to the Common Criteria Application of Attack Potential to Smartcards .

Acabar com novos requisitos

• [C-1-11] MUST include the firmware that is evaluated by a nationally accredited testing laboratory incorporating High attack potential vulnerability assessment according to the Common Criteria Application of Attack Potential to Smartcards .
• [C-SR-2] Are STRONGLY RECOMMENDED to include the hardware that is evaluated using a Security Target, Evaluation Assurance Level (EAL) 5, augmented by AVA_VAN.5. EAL 5 certification will likely become a requirement in a future release.
• [C-SR-3] Are STRONGLY RECOMMENDED to provide insider attack resistance (IAR), which means that an insider with access to firmware signing keys cannot produce firmware that causes the StrongBox to leak secrets, to bypass functional security requirements or otherwise enable access to sensitive user data. The recommended way to implement IAR is to allow firmware updates only when the primary user password is provided via the IAuthSecret HAL.

9.11.3. Identity Credential

The Identity Credential System is defined and achieved by implementing all APIs in the android.security.identity.* package. These APIs allows app developers to store and retrieve user identity documents. Implementações de dispositivos:

• [C-SR-1] are STRONGLY RECOMMENDED to implement the Identity Credential System.

If device implementations implement the Identity Credential System, they:

• [C-1-1] MUST return non-null for the IdentityCredentialStore#getInstance() method.

• [C-1-2] MUST implement the Identity Credential System (eg the android.security.identity.* APIs) with code communicating with a trusted application in an area that is securely isolated from the code running on the kernel and above. O isolamento seguro DEVE bloquear todos os mecanismos potenciais pelos quais o código do kernel ou do espaço do usuário possa acessar o estado interno do ambiente isolado, incluindo DMA.

• [C-1-3] The cryptographic operations needed to implement the Identity Credential System (eg the android.security.identity.* APIs) MUST be performed entirely in the trusted application and private key material MUST never leave the isolated execution environment unless specifically required by higher-level APIs (eg the createEphemeralKeyPair() method).

• [C-1-4] The trusted application MUST be implemented in a way such that its security properties are not affected (eg credential data is not released unless access control conditions are satisfied, MACs can't be produced for arbitrary data) even if Android is misbehaving or compromised.

The upstream Android Open Source Project provides a reference implementation of a trusted application ( libeic ) that can be used to implement the Identity Credential system.

9.12. Data Deletion

All device implementations:

• [C-0-1] MUST provide users a mechanism to perform a "Factory Data Reset".
• [C-0-2] MUST delete all data on the userdata filesystem when performing a "Factory Data Reset".
• [C-0-3] MUST delete the data in such a way that will satisfy relevant industry standards such as NIST SP800-88 when performing a "Factory Data Reset".
• [C-0-4] MUST trigger the above "Factory Data Reset" process when the DevicePolicyManager.wipeData() API is called by the primary user's Device Policy Controller app.
• MAY provide a fast data wipe option that conducts only a logical data erase.

9.13. Safe Boot Mode

Android provides Safe Boot Mode, which allows users to boot up into a mode where only preinstalled system apps are allowed to run and all third-party apps are disabled. This mode, known as "Safe Boot Mode", provides the user the capability to uninstall potentially harmful third-party apps.

Device implementations are:

• [C-SR-1] STRONGLY RECOMMENDED to implement Safe Boot Mode.

If device implementations implement Safe Boot Mode, they:

• [C-1-1] MUST provide the user an option to enter Safe Boot Mode in such a way that is uninterruptible from third-party apps installed on the device, except when the third-party app is a Device Policy Controller and has set the UserManager.DISALLOW_SAFE_BOOT flag as true.

• [C-1-2] MUST provide the user the capability to uninstall any third-party apps within Safe Mode.

• SHOULD provide the user an option to enter Safe Boot Mode from the boot menu using a workflow that is different from that of a normal boot.

9.14. Automotive Vehicle System Isolation

Android Automotive devices are expected to exchange data with critical vehicle subsystems by using the vehicle HAL to send and receive messages over vehicle networks such as CAN bus.

The data exchange can be secured by implementing security features below the Android framework layers to prevent malicious or unintentional interaction with these subsystems.

9h15. Planos de assinatura

"Subscription plans" refer to the billing relationship plan details provided by a mobile carrier through SubscriptionManager.setSubscriptionPlans() .

All device implementations:

• [C-0-1] MUST return subscription plans only to the mobile carrier app that has originally provided them.
• [C-0-2] MUST NOT remotely back up or upload subscription plans.
• [C-0-3] MUST only allow overrides, such as SubscriptionManager.setSubscriptionOverrideCongested() , from the mobile carrier app currently providing valid subscription plans.

9.16. Application Data Migration

If device implementations include a capability to migrate data from a device to another device and do not limit the application data it copies to what is configured by the application developer in the manifest via android:fullBackupContent attribute, they:

• [C-1-1] MUST NOT initiate transfers of application data from devices on which the user has not set a primary authentication as described in 9.11.1 Secure Lock Screen and Authentication .
• [C-1-2] MUST securely confirm the primary authentication on the source device and confirm with the user intent to copy the data on the source device before any data is transferred.
• [C-1-3] MUST use security key attestation to ensure that both the source device and the target device in the device-to-device migration are legitimate Android devices and have a locked bootloader.
• [C-1-4] MUST only migrate application data to the same application on the target device, with the same package name AND signing certificate.
• [C-1-5] MUST show an indication that the source device has had data migrated by a device-to-device data migration in the settings menu. A user SHOULD NOT be able to remove this indication.

Start new requirements for 15 (AOSP experimental)

9.17. Android Virtualization Framework

[9.17] (February 26, 2024 preview)

The Android Virtualization Framework (AVF) APIs ( android.system.virtualmachine.* ) allows applications to create on-device virtual machines (VMs) that load and run native binaries as payloads.

If device implementations set FEATURE_VIRTUALIZATION_FRAMEWORK to true , they:

• [C-1-6] MUST ensure that android.system.virtualmachine.VirtualMachineManager.getCapabilities() returns at least one of:
  • CAPABILITY_PROTECTED_VM
  • CAPABILITY_NON_PROTECTED_VM

Acabar com novos requisitos

[9.17] (December 11, 2023 preview)

The Android Virtualization Framework (AVF) APIs ( android.system.virtualmachine.* ) support both Protected Virtual Machines (pVMs) and Non-Protected Virtual Machines (non-pVMs) according to the following system properties:

If ro.boot.hypervisor.vm.supported is set to true then non-pVMs are supported.

If ro.boot.hypervisor.protected_vm.supported is set to true then pVMs are supported.

Note: A device implementation without EL2 software can enable non-pVMs by entering GKI at EL2.

Implementações de dispositivos:

• [C-0-1] MUST support the Android Virtualization Framework APIs ( android.system.virtualmachine.* ) for pVMs, non-pVMs and the existence of both.

If the device implements support for the Android Virtualization Framework APIs ( android.system.virtualmachine.* ), The Android host:

• [C-1-1] MUST support all the APIs defined by the android.system.virtualmachine package.

• [C- 1-2 0-2 ] MUST NOT modify the Android SELinux and permission model for the management of Protected Virtual Machines( pVM both pVMs and non-pVMs ).
• [C- 1-4 0-4 ] MUST only allow platform signed code & privileged apps pre-installed in read-only partition to create and run a pVM virtual machines . Note: This might change in future Android releases.
• [C- 1-5 0-5 ] MUST only allow a non-debuggable pVM to execute code from the factory image or their platform updates which also includes any updates to privileged pre-installed apps.

If the device implements support for the Android Virtualization Framework APIs ( android.system.virtualmachine.* ), then Any pVM instance:

• [C- 2-1 0-6 ] MUST be able to run all operating systems available in the virtualization APEX in a pVM.
• [C- 2-2 0-7 ] MUST NOT allow a pVM to run an operating system that is not signed by the device implementor or OS vendor.
• [C- 2-3 0-8 ] MUST NOT allow a pVM to execute data as code (eg SELinux neverallow execmem).
• [C- 2-5 0-9 ] MUST implement pVM defense-in-depth mechanisms (eg SELinux for pVMs) even for non-Microdroid operating systems.
• [C- 2-6 0-10 ] MUST ensure that the pVM fails to boot if images that the VM will run cannot be verified. The verification MUST be done inside the VM.
• [C- 2-7 0-11 ] MUST ensure that the pVM fails to boot if the integrity of the instance.img is compromised.

If the device implements support for the Android Virtualization Framework APIs ( android.system.virtualmachine.* ), then The hypervisor:

• [C- 3-1 0-12 ] MUST ensure that memory pages exclusively owned by a VM (either pVM or host VM guest or host pVM) or the hypervisor are accessible only to the virtual machine itself or the hypervisor, not by other virtual machines - either protected or non-protected.
• [C- 3-2 0-13 ] MUST wipe a page after it is used by a pVM and before it is returned to the host (eg the pVM is destroyed).
• [C- SR-1 0-14 ] Is STRONGLY RECOMMENDED to MUST ensure that that the pVM firmware is loaded and executed prior to any code in a pVM.
• [C- 3-4 0-15 ] MUST ensure that each VM pVM derives a per-VM secret which means that (Boot Certificate Chain) (BCC) and Compound Device Identifier (CDIs) provided to a pVM instance can only be derived by that particular VM pVM instance and changes upon factory reset and OTA.

If the device implements support for the Android Virtualization Framework APIs, then across all areas:

• [C-4-1] MUST NOT provide functionality to a pVM that allows bypassing the Android Security Model.

If the device implements support for the Android Virtualization Framework APIs, then:

• [C-5-1] MUST be capable to support Isolated Compilation but may disable Isolated Compilation feature on the device shipment.

If the device implements support for the Android Virtualization Framework APIs, then for Key Management:

• [C-SR-2] Is STRONGLY RECOMMENDED to use DICE as the per-VM secret derivation mechanism.

• [C-0-16] MUST implement rollback protection for partitions used by protected VM (eg, boot, pVM firmware), either by using tamper-evident storage for storing the metadata used for determining the minimum allowable partition version or by including the security version of the partition in the respective DICE or equivalent certificate.

Acabar com novos requisitos

Start new requirements for 15 (AOSP experimental)

9.18. Restricted Settings

[9.18] (December 11, 2023 preview)

Implementações de dispositivos:

[C-0-1] MUST implement and enable support for Restricted Settings mode. Restricted Settings apply to all apps that are side-loaded and that declare the need for certain "restricted permissions". "Restricted permissions" are not necessarily permissions, but roles and other capabilities that are considered security sensitive. Specifically, the in-scope "permissions" for Restricted Settings are:

• Acessibilidade
• Notification Listener
• Default Apps (Home, Phone, SMS)
• Device Admin Apps
• Display Over Other Apps
• Usage Access
• Media Projection
• SMS
• Chamar

An app is identified as side-loaded if it is installed from a downloaded or local file .

Acabar com novos requisitos

10. Software Compatibility Testing

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

10.1. Compatibility Test Suite

Implementações de dispositivos:

• [C-0-1] MUST pass the Android Compatibility Test Suite (CTS) available from the Android Open Source Project, using the final shipping software on the device.

• [C-0-2] MUST ensure compatibility in cases of ambiguity in CTS and for any reimplementations of parts of the reference source code.

The CTS is designed to be run on an actual device. Like any software, the CTS may itself contain bugs. The CTS will be versioned independently of this Compatibility Definition, and multiple revisions of the CTS may be released for Android 15.

Implementações de dispositivos:

• [C-0-3] MUST pass the latest CTS version available at the time the device software is completed.

• SHOULD use the reference implementation in the Android Open Source tree as much as possible.

10.2. CTS Verifier

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

Implementações de dispositivos:

• [C-0-1] MUST correctly execute all applicable cases in the CTS verifier.

The CTS Verifier has tests for many kinds of hardware, including some hardware that is optional.

Implementações de dispositivos:

• [C-0-2] MUST pass all tests for hardware that they possess; for instance, if a device possesses an accelerometer, it MUST correctly execute the Accelerometer test case in the CTS Verifier.

Test cases for features noted as optional by this Compatibility Definition Document MAY be skipped or omitted.

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

11. Updatable Software

• [C-0-1] Device implementations MUST include a mechanism to replace the entirety of the system software. The mechanism need not perform "live" upgrades—that is, a device restart MAY be required. Any method can be used, provided that it can replace the entirety of the software preinstalled on the device. For instance, any of the following approaches will satisfy this requirement:

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

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

• [C-0-3] The entire update MUST be signed and the on-device update mechanism MUST verify the update and signature against a public key stored on device.

• [C-SR-1] The signing mechanism is STRONGLY RECOMMENDED to hash the update with SHA-256 and validate the hash against the public key using ECDSA NIST P-256.

If the device implementations includes support for an unmetered data connection such as 802.11 or Bluetooth PAN (Personal Area Network) profile, then, they:

• [C-1-1] MUST support OTA downloads with offline update via reboot.

Device implementations SHOULD verify that the system image is binary identical to the expected result following an OTA. The block-based OTA implementation in the upstream Android Open Source Project, added since Android 5.1, satisfies this requirement.

Also, device implementations SHOULD support A/B system updates . The AOSP implements this feature using the boot control HAL.

If an error is found in a device implementation after it has been released but within its reasonable product lifetime that is determined in consultation with the Android Compatibility Team to affect the compatibility of third-party applications, then:

• [C-2-1] The device implementer MUST correct the error via a software update available that can be applied per the mechanism just described.

Android includes features that allow the Device Owner app (if present) to control the installation of system updates. If the system update subsystem for devices report android.software.device_admin then, they:

• [C-3-1] MUST implement the behavior described in the SystemUpdatePolicy class.

12. Document Changelog

For a summary of changes to the Compatibility Definition in this release:

• Document changelog

13. Contact Us

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