Definición de compatibilidad con Android 8.0

1. Introducción

Este documento enumera los requisitos que se deben cumplir para que los dispositivos sean compatibles con Android 8.0.

El uso de “DEBE”, “NO DEBE”, “REQUERIDO”, “DEBE”, “NO DEBE”, “DEBE”, “NO DEBE”, “RECOMENDADO”, “PUEDE” y “OPCIONAL” es según el IETF. estándar definido en RFC2119 .

Tal como se utiliza en este documento, un "implementador de dispositivos" o "implementador" es una persona u organización que desarrolla una solución de hardware/software que ejecuta Android 8.0. Una “implementación de dispositivo” o “implementación” es la solución de hardware/software así desarrollada.

Para ser considerada compatible con Android 8.0, las implementaciones de dispositivos DEBEN cumplir con los requisitos presentados en esta Definición de compatibilidad, incluido cualquier documento incorporado mediante referencia.

Cuando esta definición o las pruebas de software descritas en la sección 10 no dicen nada, son ambiguas o están incompletas, es responsabilidad del implementador del dispositivo garantizar la compatibilidad con las implementaciones existentes.

Por esta razón, el Proyecto de Código Abierto de Android es a la vez la implementación de referencia y preferida de Android. Se RECOMIENDA ENCARECIDAMENTE a los implementadores de dispositivos que basen sus implementaciones en la mayor medida posible en el código fuente "ascendente" disponible en el Proyecto de código abierto de Android. Si bien hipotéticamente algunos componentes pueden reemplazarse con implementaciones alternativas, se RECOMIENDA ENCARECIDAMENTE no seguir esta práctica, ya que pasar las pruebas de software será sustancialmente más difícil. Es responsabilidad del implementador garantizar la compatibilidad total del comportamiento con la implementación estándar de Android, incluido y más allá del Compatibility Test Suite. Finalmente, tenga en cuenta que este documento prohíbe explícitamente ciertas sustituciones y modificaciones de componentes.

Muchos de los recursos vinculados en este documento se derivan directa o indirectamente del SDK de Android y serán funcionalmente idénticos a la información contenida en la documentación de ese SDK. En cualquier caso en el que esta Definición de compatibilidad o el Conjunto de pruebas de compatibilidad no estén de acuerdo con la documentación del SDK, la documentación del SDK se considera autorizada. Cualquier detalle técnico proporcionado en los recursos vinculados a lo largo de este documento se considera por inclusión parte de esta Definición de compatibilidad.

1.1 Estructura del documento

1.1.1. Requisitos por tipo de dispositivo

La Sección 2 contiene todos los requisitos que se aplican a un tipo de dispositivo específico. Cada subsección de la Sección 2 está dedicada a un tipo de dispositivo específico.

Todos los demás requisitos, que se aplican universalmente a cualquier implementación de dispositivo Android, se enumeran en las secciones posteriores a la Sección 2 . Estos requisitos se denominan "Requisitos básicos" en este documento.

1.1.2. ID de requisito

El ID de requisito se asigna a los requisitos MUST.

• La identificación se asigna únicamente para los requisitos MUST.
• Los requisitos MUY RECOMENDADOS están marcados como [SR] pero no se asigna una ID.
• La ID consta de: ID de tipo de dispositivo - ID de condición - ID de requisito (por ejemplo, C-0-1).

Cada ID se define de la siguiente manera:

• ID de tipo de dispositivo (ver más en 2. Tipos de dispositivo)
  • C: Core (Requisitos que se aplican a cualquier implementación de dispositivo Android)
  • H: dispositivo portátil Android
  • T: dispositivo de televisión Android
  • R: Implementación de Android Automotive
  • Pestaña: Implementación de tableta Android
• ID de condición
  • Cuando el requisito es incondicional, este ID se establece en 0.
  • Cuando el requisito es condicional, se asigna 1 para la primera condición y el número aumenta en 1 dentro de la misma sección y el mismo tipo de dispositivo.
• ID de requisito
  • Este ID comienza desde 1 y aumenta en 1 dentro de la misma sección y la misma condición.

1.1.3. ID de requisito en la Sección 2

El ID de requisito en la Sección 2 comienza con el ID de sección correspondiente seguido del ID de requisito descrito anteriormente.

• El ID de la Sección 2 consta de: ID de sección/ID de tipo de dispositivo - ID de condición - ID de requisito (por ejemplo, 7.4.3/A-0-1).

2. Tipos de dispositivos

Si bien el Proyecto de código abierto de Android proporciona una pila de software que se puede utilizar para una variedad de tipos de dispositivos y factores de forma, hay algunos tipos de dispositivos que tienen un ecosistema de distribución de aplicaciones relativamente mejor establecido.

Esta sección describe esos tipos de dispositivos y los requisitos y recomendaciones adicionales aplicables a cada tipo de dispositivo.

Todas las implementaciones de dispositivos Android que no se ajusten a ninguno de los tipos de dispositivos descritos DEBEN cumplir todos los requisitos de las otras secciones de esta Definición de compatibilidad.

2.1 Configuraciones del dispositivo

Para conocer las principales diferencias en la configuración de hardware por tipo de dispositivo, consulte los requisitos específicos del dispositivo que aparecen a continuación en esta sección.

2.2. Requisitos de mano

Un dispositivo portátil Android se refiere a una implementación de dispositivo Android que normalmente se usa sosteniéndolo en la mano, como un reproductor de mp3, un teléfono o una tableta.

Las implementaciones de dispositivos Android se clasifican como dispositivos portátiles si cumplen con todos los criterios siguientes:

• Contar con una fuente de energía que proporcione movilidad, como una batería.
• Tener un tamaño de pantalla diagonal física en el rango de 2,5 a 8 pulgadas.

Los requisitos adicionales en el resto de esta sección son específicos de las implementaciones de dispositivos portátiles Android.

2.2.1. Hardware

Implementaciones de dispositivos portátiles:

• [ 7.1 .1.1/H-0-1] DEBE tener una pantalla de al menos 2,5 pulgadas de tamaño diagonal físico.
• [ 7.1.1.3/H-SR ] Se RECOMIENDA ENCARECIDAMENTE brindar a los usuarios la posibilidad de cambiar el tamaño de la pantalla. (Densidad de la pantalla)
• [ 7.1 .5/H-0-1] DEBE incluir soporte para el modo de compatibilidad de aplicaciones heredadas tal como lo implementa el código fuente abierto de Android. Es decir, las implementaciones de dispositivos NO DEBEN alterar los desencadenantes o umbrales en los que se activa el modo de compatibilidad, y NO DEBEN alterar el comportamiento del modo de compatibilidad en sí.
• [ 7.2 .1/H-0-1] DEBE incluir soporte para aplicaciones de editor de métodos de entrada (IME) de terceros.
• [ 7.2 .3/H-0-1] DEBE proporcionar las funciones Inicio, Recientes y Atrás.
• [ 7.2 .3/H-0-2] DEBE enviar tanto el evento de pulsación normal como el de pulsación larga de la función Atrás ( KEYCODE_BACK ) a la aplicación de primer plano.
• [ 7.2 .4/H-0-1] DEBE admitir la entrada de pantalla táctil.
• [ 7.3 .1/H-SR] Se RECOMIENDA ENCARECIDAMENTE incluir un acelerómetro de 3 ejes.

Si las implementaciones de dispositivos portátiles incluyen un acelerómetro de 3 ejes,:

• [ 7.3 .1/H-1-1] DEBE poder informar eventos con una frecuencia de al menos 100 Hz.

Si las implementaciones de dispositivos portátiles incluyen un giroscopio,:

• [ 7.3 .4/H-1-1] DEBE poder informar eventos con una frecuencia de al menos 100 Hz.

Implementaciones de dispositivos portátiles que pueden realizar una llamada de voz e indicar cualquier valor distinto de PHONE_TYPE_NONE en getPhoneType :

• [ 7.3 .8/H] DEBE incluir un sensor de proximidad.

Implementaciones de dispositivos portátiles:

• [ 7.3 .12/H-SR] Se RECOMIENDAN para admitir el sensor de pose con 6 grados de libertad.
• [ 7.4 .3/H]DEBE incluir soporte para Bluetooth y Bluetooth LE.

Si las implementaciones de dispositivos portátiles incluyen una conexión medida,:

• [ 7.4 .7/H-1-1] DEBE proporcionar el modo de ahorro de datos.

Implementaciones de dispositivos portátiles:

• [ 7.6 .1/H-0-1] DEBE tener al menos 4 GB de almacenamiento no volátil disponible para los datos privados de la aplicación (también conocida como partición "/data").
• [ 7.6 .1/H-0-2] DEBE devolver "verdadero" para ActivityManager.isLowRamDevice() cuando hay menos de 1 GB de memoria disponible para el kernel y el espacio de usuario.

Si las implementaciones de dispositivos portátiles son de 32 bits:

• [ 7.6 .1/H-1-1] La memoria disponible para el kernel y el espacio de usuario DEBE ser de al menos 512 MB si se utiliza cualquiera de las siguientes densidades:

  • 280 ppp o menos en pantallas pequeñas/normales ^*
  • ldpi o inferior en pantallas extra grandes
  • mdpi o inferior en pantallas grandes

• [ 7.6 .1/H-2-1] La memoria disponible para el kernel y el espacio de usuario DEBE ser de al menos 608 MB si se utiliza cualquiera de las siguientes densidades:

  • xhdpi o superior en pantallas pequeñas/normales ^*
  • hdpi o superior en pantallas grandes
  • mdpi o superior en pantallas extra grandes

• [ 7.6 .1/H-3-1] La memoria disponible para el kernel y el espacio de usuario DEBE ser de al menos 896 MB si se utiliza cualquiera de las siguientes densidades:

  • 400 ppp o más en pantallas pequeñas/normales ^*
  • xhdpi o superior en pantallas grandes
  • tvdpi o superior en pantallas extra grandes

• [ 7.6 .1/H-4-1] La memoria disponible para el kernel y el espacio de usuario DEBE ser de al menos 1344 MB si se utiliza cualquiera de las siguientes densidades:

  • 560 ppp o superior en pantallas pequeñas/normales ^*
  • 400 ppp o más en pantallas grandes
  • xhdpi o superior en pantallas extra grandes

Si las implementaciones de dispositivos portátiles son de 64 bits:

• [ 7.6 .1/H-5-1] La memoria disponible para el kernel y el espacio de usuario DEBE ser de al menos 816 MB si se utiliza cualquiera de las siguientes densidades:

  • 280 ppp o menos en pantallas pequeñas/normales ^*
  • ldpi o inferior en pantallas extra grandes
  • mdpi o inferior en pantallas grandes

• [ 7.6 .1/H-6-1] La memoria disponible para el kernel y el espacio de usuario DEBE ser de al menos 944 MB si se utiliza cualquiera de las siguientes densidades:

  • xhdpi o superior en pantallas pequeñas/normales ^*
  • hdpi o superior en pantallas grandes
  • mdpi o superior en pantallas extra grandes

• [ 7.6 .1/H-7-1] La memoria disponible para el kernel y el espacio de usuario DEBE ser de al menos 1280 MB si se utiliza cualquiera de las siguientes densidades:

  • 400 ppp o más en pantallas pequeñas/normales ^*
  • xhdpi o superior en pantallas grandes
  • tvdpi o superior en pantallas extra grandes

• [ 7.6 .1/H-8-1] La memoria disponible para el kernel y el espacio de usuario DEBE ser de al menos 1824 MB si se utiliza cualquiera de las siguientes densidades:

  • 560 ppp o superior en pantallas pequeñas/normales ^*
  • 400 ppp o más en pantallas grandes
  • xhdpi o superior en pantallas extra grandes

Tenga en cuenta que la "memoria disponible para el kernel y el espacio de usuario" anterior se refiere al espacio de memoria proporcionado además de cualquier memoria ya dedicada a componentes de hardware como radio, video, etc. que no están bajo el control del kernel en las implementaciones del dispositivo.

Implementaciones de dispositivos portátiles:

• [ 7.6 .2/H-0-1] NO DEBE proporcionar un almacenamiento compartido de aplicaciones de menos de 1 GiB.
• [ 7.7 .1/H] DEBE incluir un puerto USB que admita el modo periférico.

Si las implementaciones de dispositivos portátiles incluyen un puerto USB que admite el modo periférico,:

• [ 7.7 .1/H-1-1] DEBE implementar la API del accesorio abierto de Android (AOA).

Implementaciones de dispositivos portátiles:

• [ 7.8 .1/H-0-1] DEBE incluir un micrófono.
• [ 7.8 .2/H-0-1] DEBE tener una salida de audio y declarar android.hardware.audio.output .

Si las implementaciones de dispositivos portátiles incluyen soporte para el modo VR,:

• [ 7.9 .1/H-1-1] DEBE declarar la función android.software.vr.mode .

Si las implementaciones de dispositivos declaran la función android.software.vr.mode , estas:

• [ 7.9 .1/H-2-1] DEBE incluir una aplicación que implemente android.service.vr.VrListenerService que las aplicaciones de realidad virtual puedan habilitar a través de android.app.Activity#setVrModeEnabled .

Si las implementaciones de dispositivos portátiles son capaces de cumplir con todos los requisitos para declarar el indicador de función android.hardware.vr.high_performance ,:

• [ 7.9 .2/-1-1] DEBE declarar el indicador de función android.hardware.vr.high_performance .

2.2.2. Multimedia

Las implementaciones de dispositivos portátiles DEBEN admitir la siguiente codificación de audio:

• [ 5.1 .1/H-0-1] RAM-NB
• [ 5.1 .1/H-0-2] AMR-WB
• [ 5.1 .1/H-0-3] Perfil MPEG-4 AAC (AAC LC)
• [ 5.1 .1/H-0-4] Perfil MPEG-4 HE AAC (AAC+)
• [ 5.1 .1/H-0-5] AAC ELD (AAC de bajo retardo mejorado)

Las implementaciones de dispositivos portátiles DEBEN admitir la siguiente decodificación de audio:

• [ 5.1 .2/H-0-1] RAM-NB
• [ 5.1 .2/H-0-2] AMR-WB

Las implementaciones de dispositivos portátiles DEBEN admitir la siguiente codificación de video y ponerla a disposición de aplicaciones de terceros:

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

Las implementaciones de dispositivos portátiles DEBEN admitir la siguiente decodificación de video:

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

2.2.3. Software

Implementaciones de dispositivos portátiles:

• [ 3.4 .1/H-0-1] DEBE proporcionar una implementación completa de la API android.webkit.Webview .
• [ 3.4 .2/H-0-1] DEBE incluir una aplicación de navegador independiente para la navegación web del usuario general.
• [ 3.8 .1/H-SR] Se RECOMIENDA ENCARECIDAMENTE implementar un iniciador predeterminado que admita la fijación de accesos directos y widgets en la aplicación.
• [ 3.8 .1/H-SR] Se RECOMIENDA ENCARECIDAMENTE implementar un iniciador predeterminado que proporcione acceso rápido a los accesos directos adicionales proporcionados por aplicaciones de terceros a través de la API ShortcutManager .
• [ 3.8 .1/H-SR] Se RECOMIENDA ENCARECIDAMENTE incluir una aplicación de inicio predeterminada que muestre insignias para los íconos de las aplicaciones.
• [ 3.8 .2/H-SR] Se RECOMIENDA ENCARECIDAMENTE para admitir widgets de aplicaciones de terceros.
• [ 3.8 .3/H-0-1] DEBE permitir que aplicaciones de terceros notifiquen a los usuarios sobre eventos notables a través de las clases API Notification y NotificationManager .
• [ 3.8 .3/H-0-2] DEBE admitir notificaciones enriquecidas.
• [ 3.8 .3/H-0-3] DEBE admitir notificaciones de aviso.
• [ 3.8 .3/H-0-4] DEBE incluir un tono de notificación, que brinde al usuario la capacidad de controlar directamente (por ejemplo, responder, posponer, descartar, bloquear) las notificaciones a través de las posibilidades del usuario, como los botones de acción o el panel de control, según se implemente. en la AOSP.
• [ 3.8 .4/H-SR] Se RECOMIENDA ENCARECIDAMENTE implementar un asistente en el dispositivo para manejar la acción de asistencia .

Si las implementaciones de dispositivos portátiles Android admiten una pantalla de bloqueo,:

• [ 3.8 .10/H-1-1] DEBE mostrar las notificaciones de la pantalla de bloqueo, incluida la plantilla de notificación de medios.

Si las implementaciones de dispositivos portátiles admiten una pantalla de bloqueo segura,:

• [ 3.9 /H-1-1] DEBE implementar la gama completa de políticas de administración de dispositivos definidas en la documentación del SDK de Android.

Implementaciones de dispositivos portátiles:

• [ 3.10 /H-0-1] DEBE admitir servicios de accesibilidad de terceros.
• [ 3.10 /H-SR] Se RECOMIENDA ENCARECIDAMENTE precargar servicios de accesibilidad en el dispositivo comparables o superiores a la funcionalidad de los servicios de accesibilidad Switch Access y TalkBack (para idiomas admitidos por el motor de texto a voz precargado) tal como se proporciona en el talkback abierto. proyecto fuente .
• [ 3.11 /H-0-1] DEBE admitir la instalación de motores TTS de terceros.
• [ 3.11 /H-SR] Se RECOMIENDA ENCARECIDAMENTE incluir un motor TTS que admita los idiomas disponibles en el dispositivo.
• [ 3.13 /H-SR] Se RECOMIENDA ENCARECIDAMENTE incluir un componente de interfaz de usuario de Configuración rápida.

Si las implementaciones de dispositivos portátiles Android declaran compatibilidad con FEATURE_BLUETOOTH o FEATURE_WIFI ,:

• [ 3.15 /H-1-1] DEBE admitir la función de emparejamiento de dispositivos complementarios.

2.2.4. Rendimiento y potencia

• [ 8.1 /H-0-1] Latencia de fotogramas consistente . La latencia de fotogramas inconsistente o un retraso en la renderización de fotogramas NO DEBEN ocurrir con más frecuencia de 5 fotogramas por segundo, y DEBEN ser inferiores a 1 fotograma por segundo.
• [ 8.1 /H-0-2] Latencia de la interfaz de usuario . Las implementaciones de dispositivos DEBEN garantizar una experiencia de usuario de baja latencia al desplazarse por una lista de 10.000 entradas de lista según lo definido por Android Compatibility Test Suite (CTS) en menos de 36 segundos.
• [ 8.1 /H-0-3] Cambio de tarea . Cuando se han iniciado varias aplicaciones, volver a iniciar una aplicación que ya se está ejecutando después de haberla iniciado DEBE tomar menos de 1 segundo.

Implementaciones de dispositivos portátiles:

• [ 8.2 /H-0-1] DEBE garantizar un rendimiento de escritura secuencial de al menos 5 MB/s.
• [ 8.2 /H-0-2] DEBE garantizar un rendimiento de escritura aleatoria de al menos 0,5 MB/s.
• [ 8.2 /H-0-3] DEBE garantizar un rendimiento de lectura secuencial de al menos 15 MB/s.
• [ 8.2 /H-0-4] DEBE garantizar un rendimiento de lectura aleatoria de al menos 3,5 MB/s.
• [ 8.3 /H-0-1] Todas las aplicaciones exentas de los modos de ahorro de energía App Standby y Doze DEBEN ser visibles para el usuario final.
• [ 8.3 /H-0-2] Los algoritmos de activación, mantenimiento, activación y el uso de la configuración global del sistema de los modos de ahorro de energía App Standby y Doze no DEBEN desviarse del Proyecto de código abierto de Android.

Implementaciones de dispositivos portátiles:

• [ 8.4 /H-0-1] DEBE proporcionar un perfil de energía por componente que defina el valor de consumo actual para cada componente de hardware y el consumo aproximado de batería causado por los componentes a lo largo del tiempo, como se documenta en el sitio del Proyecto de código abierto de Android.
• [ 8.4 /H-0-2] DEBE informar todos los valores de consumo de energía en miliamperios hora (mAh).
• [ 8.4 /H-0-3] DEBE informar el consumo de energía de la CPU por el UID de cada proceso. El proyecto de código abierto de Android cumple con el requisito mediante la implementación del módulo del kernel uid_cputime .
• [ 8.4 /H-0-4] DEBE hacer que este uso de energía esté disponible a través del comando adb shell dumpsys batterystats shell para el desarrollador de la aplicación.
• [ 8.4 /H] DEBE atribuirse al propio componente de hardware si no se puede atribuir el uso de energía del componente de hardware a una aplicación.

Si las implementaciones de dispositivos portátiles incluyen una pantalla o salida de video,:

• [ 8.4 /H-1-1] DEBE respetar la intención android.intent.action.POWER_USAGE_SUMMARY y mostrar un menú de configuración que muestre este uso de energía.

2.2.5. Modelo de seguridad

Implementaciones de dispositivos portátiles:

• [ 9.1 /H-0-1] DEBE permitir que aplicaciones de terceros accedan a las estadísticas de uso a través del permiso android.permission.PACKAGE_USAGE_STATS y proporcionar un mecanismo accesible para el usuario para otorgar o revocar el acceso a dichas aplicaciones en respuesta a android.settings.ACTION_USAGE_ACCESS_SETTINGS intención.

2.3. Requisitos de televisión

Un dispositivo Android Television se refiere a una implementación de dispositivo Android que es una interfaz de entretenimiento para consumir medios digitales, películas, juegos, aplicaciones y/o TV en vivo para usuarios sentados a unos diez pies de distancia (un usuario “reclinado” o “usuario de 10 pies”). interfaz").

Las implementaciones de dispositivos Android se clasifican como Televisión si cumplen con todos los criterios siguientes:

• Han proporcionado un mecanismo para controlar de forma remota la interfaz de usuario representada en la pantalla que podría estar a tres metros de distancia del usuario.
• Tener una pantalla integrada con una longitud diagonal superior a 24 pulgadas O incluir un puerto de salida de video, como VGA, HDMI, DisplayPort o un puerto inalámbrico para visualización.

Los requisitos adicionales en el resto de esta sección son específicos de las implementaciones de dispositivos Android Television.

2.3.1. Hardware

Implementaciones de dispositivos de televisión:

• [ 7.2 .2/T-0-1] DEBE admitir D-pad .
• [ 7.2 .3/T-0-1] DEBE proporcionar las funciones Inicio y Atrás.
• [ 7.2 .3/T-0-2] DEBE enviar tanto el evento de pulsación normal como el de pulsación larga de la función Atrás ( KEYCODE_BACK ) a la aplicación de primer plano.
• [ 7.2 .6.1/T-0-1] DEBE incluir soporte para controladores de juegos y declarar el indicador de función android.hardware.gamepad .
• [ 7.2.7 /T] DEBE proporcionar un control remoto desde el cual los usuarios puedan acceder a la navegación no táctil y a las entradas de las teclas de navegación principales .

Si las implementaciones de dispositivos de televisión incluyen un giroscopio,:

• [ 7.3 .4/T-1-1] DEBE poder informar eventos con una frecuencia de al menos 100 Hz.

Implementaciones de dispositivos de televisión:

• [ 7.4 .3/T-0-1] DEBE admitir Bluetooth y Bluetooth LE.
• [ 7.6 .1/T-0-1] DEBE tener al menos 4 GB de almacenamiento no volátil disponible para los datos privados de la aplicación (también conocida como partición "/data").

Si las implementaciones de dispositivos de TV son de 32 bits:

• [ 7.6 .1/T-1-1] La memoria disponible para el kernel y el espacio de usuario DEBE ser de al menos 896 MB si se utiliza cualquiera de las siguientes densidades:

  • 400 ppp o más en pantallas pequeñas/normales
  • xhdpi o superior en pantallas grandes
  • tvdpi o superior en pantallas extra grandes

Si las implementaciones de dispositivos de TV son de 64 bits:

• [ 7.6 .1/T-2-1] La memoria disponible para el kernel y el espacio de usuario DEBE ser de al menos 1280 MB si se utiliza cualquiera de las siguientes densidades:

  • 400 ppp o más en pantallas pequeñas/normales
  • xhdpi o superior en pantallas grandes
  • tvdpi o superior en pantallas extra grandes

Tenga en cuenta que la "memoria disponible para el kernel y el espacio de usuario" anterior se refiere al espacio de memoria proporcionado además de cualquier memoria ya dedicada a componentes de hardware como radio, video, etc. que no están bajo el control del kernel en las implementaciones del dispositivo.

Implementaciones de dispositivos de televisión:

• [ 7.8 .1/T] DEBE incluir un micrófono.
• [ 7.8 .2/T-0-1] DEBE tener una salida de audio y declarar android.hardware.audio.output .

2.3.2. Multimedia

Las implementaciones de dispositivos de televisión DEBEN admitir la siguiente codificación de audio:

• [ 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 bajo retardo mejorado)

Las implementaciones de dispositivos de televisión DEBEN admitir la siguiente codificación de vídeo:

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

Implementaciones de dispositivos de televisión:

• [ 5.2 .2/T-SR] Se RECOMIENDA ENCARECIDAMENTE que admitan la codificación H.264 de vídeos con resolución de 720p y 1080p.
• [ 5.2 2/T-SR] Se RECOMIENDA ENCARECIDAMENTE admitir la codificación H.264 de vídeo con resolución de 1080p a 30 fotogramas por segundo (fps).

Las implementaciones de dispositivos de televisión DEBEN admitir la siguiente decodificación de video:

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

Se RECOMIENDA ENCARECIDAMENTE que las implementaciones de dispositivos de televisión admitan la siguiente decodificación de vídeo:

• [ 5.3 /T-SR] MPEG-2

Si las implementaciones de dispositivos de televisión admiten decodificadores H.264,:

• [ 5.3 .4/T-1-1] DEBE admitir el nivel de perfil alto 4.2 y el perfil de decodificación HD 1080p (a 60 fps).
• [ 5.3 .4/T-1-2] DEBE ser capaz de decodificar videos con ambos perfiles HD como se indica en la siguiente tabla y codificados con el perfil base, el perfil principal o el perfil alto nivel 4.2

Si las implementaciones de dispositivos de televisión admiten el códec H.265 y el perfil de decodificación HD 1080p,:

• [ 5.3 .5/T-1-1] DEBE admitir el nivel principal de perfil principal 4.1.
• [ 5.3 .5/T-SR] Se RECOMIENDA ENCARECIDAMENTE que admitan una velocidad de fotogramas de vídeo de 60 fps para HD 1080p.

Si las implementaciones de dispositivos de televisión admiten el códec H.265 y el perfil de decodificación UHD, entonces:

• [ 5.3 .5/T-2-1] El códec DEBE admitir el perfil de nivel principal Main10 Nivel 5.

Si las implementaciones de dispositivos de televisión admiten el códec VP8,:

• [ 5.3 .6/T-1-1] DEBE admitir el perfil de decodificación HD 1080p60.

Si las implementaciones de dispositivos de televisión admiten el códec VP8 y admiten 720p,:

• [ 5.3 .6/T-2-1] DEBE admitir el perfil de decodificación HD 720p60.

Si las implementaciones de dispositivos de televisión admiten el códec VP9 y la decodificación de vídeo UHD,:

• [ 5.3.7 /T-1-1] DEBE admitir una profundidad de color de 8 bits y DEBE admitir VP9 Perfil 2 (10 bits).

Si las implementaciones de dispositivos de televisión admiten el códec VP9, ​​el perfil de 1080p y la decodificación de hardware VP9,:

• [ 5.3 .7/T-2-1] DEBE admitir 60 fps para 1080p.

Implementaciones de dispositivos de televisión:

• [ 5.8 /T-SR] Se RECOMIENDA ENCARECIDAMENTE para admitir la decodificación simultánea de transmisiones seguras. Como mínimo, se RECOMIENDA ENCARECIDAMENTE la decodificación simultánea de dos vapores.

Si las implementaciones de dispositivos son dispositivos Android Television y admiten resolución 4K,:

• [ 5.8 /T-1-1] DEBE admitir HDCP 2.2 para todas las pantallas externas cableadas.

Si las implementaciones de dispositivos de televisión no admiten la resolución 4K:

• [ 5.8 /T-2-1] DEBE admitir HDCP 1.4 para todas las pantallas externas cableadas.

Implementaciones de dispositivos de televisión:

• [ 5.5 .3/T-0-1] DEBE incluir soporte para el volumen maestro del sistema y la atenuación del volumen de salida de audio digital en las salidas admitidas, excepto para la salida de paso de audio comprimido (donde no se realiza ninguna decodificación de audio en el dispositivo).

2.3.3. Software

Implementaciones de dispositivos de televisión:

• [ 3 /T-0-1] DEBE declarar las funciones android.software.leanback y android.hardware.type.television .
• [ 3.4 .1/T-0-1] DEBE proporcionar una implementación completa de la API android.webkit.Webview .

Si las implementaciones de dispositivos Android Television admiten una pantalla de bloqueo,:

• [ 3.8 .10/T-1-1] DEBE mostrar las notificaciones de la pantalla de bloqueo, incluida la plantilla de notificación de medios.

Implementaciones de dispositivos de televisión:

• [ 3.8 .14/T-SR] Se RECOMIENDA ENCARECIDAMENTE admitir el modo de ventana múltiple de imagen en imagen (PIP).
• [ 3.10 /T-0-1] DEBE admitir servicios de accesibilidad de terceros.
• [ 3.10 /T-SR] Se RECOMIENDA ENCARECIDAMENTE precargar servicios de accesibilidad en el dispositivo comparables o superiores a la funcionalidad de los servicios de accesibilidad Switch Access y TalkBack (para idiomas admitidos por el motor de texto a voz precargado) tal como se proporciona en el talkback abierto. proyecto fuente .

Si las implementaciones de dispositivos de televisión informan la función android.hardware.audio.output ,:

• [ 3.11 /T-SR] Se RECOMIENDA ENCARECIDAMENTE incluir un motor TTS que admita los idiomas disponibles en el dispositivo.
• [ 3.11 /T-1-1] DEBE admitir la instalación de motores TTS de terceros.

Implementaciones de dispositivos de televisión:

• [ 3.12 /T-0-1] DEBE admitir el marco de entrada de TV.

2.2.4. Rendimiento y potencia

• [ 8.1 /T-0-1] Latencia de fotogramas consistente . La latencia de fotogramas inconsistente o un retraso en la renderización de fotogramas NO DEBEN ocurrir con más frecuencia de 5 fotogramas por segundo, y DEBEN ser inferiores a 1 fotograma por segundo.
• [ 8.2 /T-0-1] DEBE garantizar un rendimiento de escritura secuencial de al menos 5 MB/s.
• [ 8.2 /T-0-2] DEBE garantizar un rendimiento de escritura aleatoria de al menos 0,5 MB/s.
• [ 8.2 /T-0-3] DEBE garantizar un rendimiento de lectura secuencial de al menos 15 MB/s.

• [ 8.2 /T-0-4] DEBE garantizar un rendimiento de lectura aleatoria de al menos 3,5 MB/s.

• [ 8.3 /T-0-1] Todas las aplicaciones exentas de los modos de ahorro de energía App Standby y Doze DEBEN ser visibles para el usuario final.

• [ 8.3 /T-0-2] Los algoritmos de activación, mantenimiento, activación y uso de la configuración global del sistema de los modos de ahorro de energía App Standby y Doze no DEBEN desviarse del Proyecto de código abierto de Android.

Implementaciones de dispositivos de televisión:

• [ 8.4 /T-0-1] DEBE proporcionar un perfil de energía por componente que defina el valor de consumo actual para cada componente de hardware y el consumo aproximado de batería causado por los componentes a lo largo del tiempo, como se documenta en el sitio del Proyecto de código abierto de Android.
• [ 8.4 /T-0-2] DEBE informar todos los valores de consumo de energía en miliamperios hora (mAh).
• [ 8.4 /T-0-3] DEBE informar el consumo de energía de la CPU por el UID de cada proceso. El proyecto de código abierto de Android cumple con el requisito mediante la implementación del módulo del kernel uid_cputime .
• [ 8.4 /T] DEBE atribuirse al propio componente de hardware si no se puede atribuir el uso de energía del componente de hardware a una aplicación.
• [ 8.4 /T-0-4] DEBE hacer que este uso de energía esté disponible a través del comando adb shell dumpsys batterystats shell para el desarrollador de la aplicación.

2.4. Requisitos del reloj

Un dispositivo Android Watch se refiere a una implementación de dispositivo Android destinada a usarse en el cuerpo, tal vez en la muñeca.

Las implementaciones de dispositivos Android se clasifican como Watch si cumplen con todos los criterios siguientes:

• Tener una pantalla con una longitud diagonal física en el rango de 1,1 a 2,5 pulgadas.
• Disponer de un mecanismo para llevar en el cuerpo.

Los requisitos adicionales en el resto de esta sección son específicos de las implementaciones de dispositivos Android Watch.

2.4.1. Hardware

Ver implementaciones de dispositivos:

• [ 7.1 .1.1/W-0-1] DEBE tener una pantalla con un tamaño diagonal físico en el rango de 1,1 a 2,5 pulgadas.

• [ 7.2 .3/W-0-1] DEBE tener la función Inicio disponible para el usuario y la función Atrás excepto cuando está en UI_MODE_TYPE_WATCH .

• [ 7.2 .4/W-0-1] DEBE admitir la entrada de pantalla táctil.

• [ 7.3 .1/W-SR] Se RECOMIENDA ENCARECIDAMENTE incluir un acelerómetro de 3 ejes.

• [ 7.4 .3/W-0-1] DEBE ser compatible con Bluetooth.

• [ 7.6 .1/W-0-1] DEBE tener al menos 1 GB de almacenamiento no volátil disponible para los datos privados de la aplicación (también conocida como partición "/data")

• [ 7.6 .1/W-0-2] DEBE tener al menos 416 MB de memoria disponible para el kernel y el espacio de usuario.

• [ 7.8 .1/W-0-1] DEBE incluir un micrófono.

• [ 7.8 .2/W] PUEDE pero NO DEBE tener salida de audio.

2.4.2. Multimedia

Sin requisitos adicionales.

2.4.3. Software

Ver implementaciones de dispositivos:

• [ 3 /W-0-1] DEBE declarar la característica android.hardware.type.watch .
• [ 3 /W-0-2] DEBE admitir uiMode = UI_MODE_TYPE_WATCH .

Ver implementaciones de dispositivos:

• [ 3.8 .4/W-SR] Se RECOMIENDA ENCARECIDAMENTE implementar un asistente en el dispositivo para manejar la acción de asistencia .

Observe las implementaciones de dispositivos que declaran el indicador de función android.hardware.audio.output :

• [ 3.10 /W-1-1] DEBE admitir servicios de accesibilidad de terceros.
• [ 3.10 /W-SR] Se RECOMIENDA ENCARECIDAMENTE precargar servicios de accesibilidad en el dispositivo comparables o superiores a la funcionalidad de los servicios de accesibilidad Switch Access y TalkBack (para idiomas admitidos por el motor de texto a voz precargado) tal como se proporciona en el talkback abierto. proyecto fuente .

Si las implementaciones de dispositivos Watch informan la función android.hardware.audio.output,:

• [ 3.11 /W-SR] Se RECOMIENDA ENCARECIDAMENTE incluir un motor TTS que admita los idiomas disponibles en el dispositivo.

• [ 3.11 /W-0-1] DEBE admitir la instalación de motores TTS de terceros.

2.5. Requisitos automotrices

La implementación de Android Automotive se refiere a la unidad principal de un vehículo que ejecuta Android como sistema operativo para parte o la totalidad del sistema y/o la funcionalidad de infoentretenimiento.

Las implementaciones de dispositivos Android se clasifican como automotrices si declaran la característica android.hardware.type.automotive o cumplen con todos los criterios siguientes.

• Están integrados como parte de un vehículo automotor o se pueden conectar a él.
• Están utilizando una pantalla en la fila del asiento del conductor como pantalla principal.

Los requisitos adicionales en el resto de esta sección son específicos de las implementaciones de dispositivos Android Automotive.

2.5.1. Hardware

Implementaciones de dispositivos automotrices:

• [ 7.1 .1.1/A-0-1] DEBE tener una pantalla de al menos 6 pulgadas de tamaño diagonal físico.

• [ 7.1 .1.1/A-0-2] DEBE tener un diseño de tamaño de pantalla de al menos 750 dp x 480 dp.

• [ 7.2 .3/A-0-1] DEBE proporcionar la función Inicio y PUEDE proporcionar funciones Atrás y Recientes.

• [ 7.2 .3/A-0-2] DEBE enviar tanto el evento de pulsación normal como el de pulsación larga de la función Atrás ( KEYCODE_BACK ) a la aplicación de primer plano.

• [ 7.3 .1/A-SR] Se RECOMIENDA ENCARECIDAMENTE incluir un acelerómetro de 3 ejes.

Si las implementaciones de dispositivos automotrices incluyen un acelerómetro de 3 ejes,:

• [ 7.3 .1/A-1-1] DEBE poder informar eventos con una frecuencia de al menos 100 Hz.
• [ 7.3 .1/A-1-2] DEBE cumplir con el sistema de coordenadas del sensor del automóvil de Android.

Si las implementaciones de dispositivos automotrices incluyen un receptor GPS/GNSS e informan la capacidad a las aplicaciones a través del indicador de función android.hardware.location.gps :

• [ 7.3 .3/A-1-1] La generación de tecnología GNSS DEBE ser del año "2017" o posterior.

Si las implementaciones de dispositivos automotrices incluyen un giroscopio,:

• [ 7.3 .4 /A-1-1] DEBE poder informar eventos con una frecuencia de al menos 100 Hz.

Implementaciones de dispositivos automotrices:

• [ 7.3 .11/A] DEBE proporcionar la marcha actual como SENSOR_TYPE_GEAR .

Implementaciones de dispositivos automotrices:

• [ 7.3 .11.2/A-0-1] DEBE admitir el modo día/noche definido como SENSOR_TYPE_NIGHT .
• [ 7.3 .11.2/A-0-2] El valor del indicador SENSOR_TYPE_NIGHT DEBE ser consistente con el modo día/noche del tablero y DEBE basarse en la entrada del sensor de luz ambiental.

• El sensor de luz ambiental subyacente PUEDE ser el mismo que el fotómetro .

• [ 7.3 .11.3/A-0-1] DEBE admitir el estado de conducción definido como SENSOR_TYPE_DRIVING_STATUS , con un valor predeterminado de DRIVE_STATUS_UNRESTRICTED cuando el vehículo está completamente detenido y estacionado. Es responsabilidad de los fabricantes de dispositivos configurar SENSOR_TYPE_DRIVING_STATUS de conformidad con todas las leyes y regulaciones que se aplican a los mercados donde se envía el producto.

• [ 7.3 .11.4/A-0-1] DEBE proporcionar la velocidad del vehículo definida como SENSOR_TYPE_CAR_SPEED .

• [ 7.4 .3/A-0-1] DEBE admitir Bluetooth y DEBE admitir Bluetooth LE.

• [ 7.4 .3/A-0-2] Las implementaciones de Android Automotive DEBEN admitir los siguientes perfiles de Bluetooth:
  • Llamadas telefónicas a través del perfil manos libres (HFP).
  • Reproducción de medios a través del perfil de distribución de audio (A2DP).
  • Control de reproducción multimedia a través del perfil de control remoto (AVRCP).
  • Compartir contactos mediante el perfil de acceso a la agenda telefónica (PBAP).

• [ 7.4.3 /A] DEBE admitir el perfil de acceso a mensajes (MAP).

• [ 7.4.5 /A] DEBE incluir soporte para conectividad de datos basada en redes celulares.

• [ 7.6 .1/A-0-1] DEBE tener al menos 4 GB de almacenamiento no volátil disponible para los datos privados de la aplicación (también conocida como partición "/data").

Si las implementaciones de dispositivos automotrices son de 32 bits:

• [ 7.6 .1/A-1-1] La memoria disponible para el kernel y el espacio de usuario DEBE ser de al menos 512 MB si se utiliza cualquiera de las siguientes densidades:

  • 280 ppp o menos en pantallas pequeñas/normales
  • ldpi o inferior en pantallas extra grandes
  • mdpi o inferior en pantallas grandes

• [ 7.6 .1/A-1-2] La memoria disponible para el kernel y el espacio de usuario DEBE ser de al menos 608 MB si se utiliza cualquiera de las siguientes densidades:

  • xhdpi o superior en pantallas pequeñas/normales
  • hdpi o superior en pantallas grandes
  • mdpi o superior en pantallas extra grandes

• [ 7.6 .1/A-1-3] La memoria disponible para el kernel y el espacio de usuario DEBE ser de al menos 896 MB si se utiliza cualquiera de las siguientes densidades:

  • 400 ppp o más en pantallas pequeñas/normales
  • xhdpi o superior en pantallas grandes
  • tvdpi o superior en pantallas extra grandes

• [ 7.6 .1/A-1-4] La memoria disponible para el kernel y el espacio de usuario DEBE ser de al menos 1344 MB si se utiliza cualquiera de las siguientes densidades:

  • 560 ppp o más en pantallas pequeñas/normales
  • 400 ppp o más en pantallas grandes
  • xhdpi o superior en pantallas extra grandes

Si las implementaciones de dispositivos automotrices son de 64 bits:

• [ 7.6 .1/A-2-1] La memoria disponible para el kernel y el espacio de usuario DEBE ser de al menos 816 MB si se utiliza cualquiera de las siguientes densidades:

  • 280 ppp o menos en pantallas pequeñas/normales
  • ldpi o inferior en pantallas extra grandes
  • mdpi o inferior en pantallas grandes

• [ 7.6 .1/A-2-2] La memoria disponible para el kernel y el espacio de usuario DEBE ser de al menos 944 MB si se utiliza cualquiera de las siguientes densidades:

  • xhdpi o superior en pantallas pequeñas/normales
  • hdpi o superior en pantallas grandes
  • mdpi o superior en pantallas extra grandes

• [ 7.6 .1/A-2-3] La memoria disponible para el kernel y el espacio de usuario DEBE ser de al menos 1280 MB si se utiliza cualquiera de las siguientes densidades:

  • 400 ppp o más en pantallas pequeñas/normales
  • xhdpi o superior en pantallas grandes
  • tvdpi o superior en pantallas extra grandes

• [ 7.6 .1/A-2-4] La memoria disponible para el kernel y el espacio de usuario DEBE ser de al menos 1824 MB si se utiliza cualquiera de las siguientes densidades:

  • 560 ppp o más en pantallas pequeñas/normales
  • 400 ppp o más en pantallas grandes
  • xhdpi o superior en pantallas extra grandes

Tenga en cuenta que la "memoria disponible para el kernel y el espacio de usuario" anterior se refiere al espacio de memoria proporcionado además de cualquier memoria ya dedicada a componentes de hardware como radio, video, etc. que no están bajo el control del kernel en las implementaciones del dispositivo.

Implementaciones de dispositivos automotrices:

• [ 7.7 .1/A] DEBE incluir un puerto USB que admita el modo periférico.

Implementaciones de dispositivos automotrices:

• [ 7.8 .1/A-0-1] DEBE incluir un micrófono.

Implementaciones de dispositivos automotrices:

• [ 7.8 .2/A-0-1] DEBE tener una salida de audio y declarar android.hardware.audio.output .

2.5.2. Multimedia

Las implementaciones de dispositivos automotrices DEBEN admitir la siguiente codificación de audio:

• [ 5.1 /A-0-1] Perfil MPEG-4 AAC (AAC LC)
• [ 5.1 /A-0-2] MPEG-4 He AAC Perfil (AAC+)
• [ 5.1 /A-0-3] AAC ELD (AAC de baja retraso mejorado)

Las implementaciones de dispositivos automotrices deben admitir la siguiente codificación de video:

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

Las implementaciones de dispositivos automotrices deben admitir la siguiente decodificación de video:

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

Se recomiendan las implementaciones de dispositivos automotrices para admitir la siguiente decodificación de video:

• [ 5.3 /a-sr] H.265 HEVC

2.5.3. Software

Implementaciones de dispositivos automotrices:

• [ 3 /A-0-1] debe declarar la función android.hardware.type.automotive .
• [ 3 /a-0-2] debe admitir uiMode = ui_mode_type_car .

• [ 3 /A-0-3] Las implementaciones automotrices de Android deben admitir todas las API públicas en el espacio de nombres android.car.* .

• [ 3.4 .1/A-0-1] debe proporcionar una implementación completa de la API android.webkit.Webview .

• [ 3.8 .3/A-0-1] debe mostrar notificaciones que usan la API Notification.CarExtender .

• [ 3.8 .4/A-0-1] debe implementar un asistente en el dispositivo para manejar la acción de asistencia .

• [ 3.14 /A-0-1] debe incluir un marco de UI para admitir aplicaciones de terceros utilizando las API de medios como se describe en la Sección 3.14.

2.2.4. Rendimiento y potencia

Implementaciones de dispositivos automotrices:

• [ 8.3 /A-0-1] Todas las aplicaciones eximidas de la aplicación en espera y los modos de ahorro de alimentación de Doze deben hacerse visibles para el usuario final.

• [ 8.3 /A-0-2] Los algoritmos de activación, mantenimiento, atención y el uso de la configuración del sistema global de los modos de ahorro de energía de APP en espera y Doze no deben desviarse del proyecto de código abierto de Android.

• [ 8.4 /A-0-1] debe proporcionar un perfil de potencia por componente que define el valor de consumo actual para cada componente de hardware y el drenaje de la batería aproximado causado por los componentes con el tiempo como se documenta en el sitio del proyecto de código abierto de Android.

• [ 8.4 /A-0-2] debe informar todos los valores de consumo de energía en las horas miliámicas (mAh).
• [ 8.4 /A-0-3] debe informar el consumo de energía de la CPU según el UID de cada proceso. El proyecto de código abierto de Android cumple con el requisito a través de la implementación del módulo del núcleo uid_cputime .
• [ 8.4 /a] debe atribuirse al componente de hardware en sí mismo si no puede atribuir el uso del componente de hardware a una aplicación.
• [ 8.4 /A-0-4] debe hacer que este uso de energía esté disponible a través del comando adb shell dumpsys batterystats Shell para el desarrollador de aplicaciones.

2.2.5. Modelo de seguridad

Si las implementaciones de dispositivos automotrices incluyen múltiples usuarios, ellos:

• [ 9.5 /A-1-1] debe incluir una cuenta de invitado que permita todas las funciones proporcionadas por el sistema de vehículos sin requerir que un usuario inicie sesión.

Implementaciones de dispositivos automotrices:

• [ 9.14 /A-0-1] Debe hacer mensajes de Gatekeep de Android Framework Vehicle Subsistems, por ejemplo, la lista de mensajes permitidos y las fuentes de mensajes permitidos.
• [ 9.14 /A-0-2] debe vigilar los ataques de denegación de servicios del marco de Android o aplicaciones de terceros. Esto protege contra el software malicioso que inundan la red de vehículos con tráfico, lo que puede conducir a los subsistemas de vehículos que no funcionan mal.

2.6. Requisitos de tableta

Un dispositivo de tableta Android se refiere a una implementación de dispositivos Android que generalmente se usa al contener ambas manos y no en un factor de formulario de poca luz.

Las implementaciones de dispositivos de Android se clasifican como una tableta si cumplen con los siguientes criterios:

• Tener una fuente de energía que proporcione movilidad, como una batería.
• Tener un tamaño de pantalla diagonal físico en el rango de 7 a 18 pulgadas.

Las implementaciones de dispositivos de tabletas tienen requisitos similares a las implementaciones de dispositivos portátiles. Las excepciones están indicadas por y * en esa sección y se observan como referencia en esta sección.

2.4.1. Hardware

Tamaño de pantalla

• [ 7.1 .1.1/TAB-0-1] debe tener una pantalla en el rango de 7 a 18 pulgadas.

Memoria y almacenamiento mínimo (Sección 7.6.1)

Las densidades de pantalla enumeradas para pantallas pequeñas/normales en los requisitos portátiles no son aplicables a las tabletas.

Modo periférico USB (Sección 7.7.1)

Si las implementaciones de la tableta incluyen un puerto USB que admite el modo periférico, ellos:

• [ 7.7.1 /tab] puede implementar la API de accesorios abiertos de Android (AOA).

Modo de realidad virtual (Sección 7.9.1)

Realidad virtual Alto rendimiento (Sección 7.9.2)

Los requisitos de realidad virtual no son aplicables a las tabletas.

3.software

3.1. Compatibilidad de API administrada

El entorno de ejecución de bytecode administrado de Dalvik es el vehículo principal para las aplicaciones de Android. La interfaz de programación de aplicaciones (API) de Android es el conjunto de interfaces de la plataforma Android expuestas a aplicaciones que se ejecutan en el entorno de ejecución administrado.

• Las implementaciones del dispositivo [C-0-1] deben proporcionar implementaciones completas, incluidos todos los comportamientos documentados, de cualquier API documentada expuesta por el SDK de Android o cualquier API decorada con el marcador "@systemapi" en el código fuente de Android aguas arriba.

• [C-0-2] Las implementaciones del dispositivo deben admitir/preservar todas las clases, métodos y elementos asociados marcados por la anotación de TestApi (@Testapi).

• [C-0-3] Las implementaciones de dispositivos no deben omitir ninguna API administrada, alterar interfaces o firmas de API, desviarse del comportamiento documentado, o incluir OPS NO-OPS, excepto cuando se permita específicamente esta definición de compatibilidad.

• [C-0-4] Las implementaciones de dispositivos aún deben mantener las API presentes y comportarse de manera razonable, incluso cuando se omiten algunas características de hardware para las cuales Android incluye API. Consulte la sección 7 para conocer los requisitos específicos para este escenario.

3.1.1. Extensiones de Android

Android incluye la compatibilidad para ampliar las API administradas manteniendo la misma versión de nivel de API.

• [C-0-1] Las implementaciones de dispositivos de Android deben precargar la implementación de AOSP tanto de los ExtShared servicios y servicios ExtServices servicios de biblioteca compartida con versiones superiores o iguales a las versiones mínimas permitidas por cada nivel de API. Por ejemplo, las implementaciones de dispositivos Android 7.0 que ejecutan el nivel API 24 DEBEN incluir al menos la versión 1.

3.2. Compatibilidad de API suave

Además de las API administradas de la sección 3.1 , Android también incluye una importante API "suave" solo en tiempo de ejecución, en forma de intenciones, permisos y aspectos similares de las aplicaciones de Android que no se pueden aplicar en el momento de la compilación de la aplicación.

3.2.1. Permisos

• [C-0-1] Los implementadores del dispositivo deben admitir y hacer cumplir todas las constantes de permiso según lo documentado por la página de referencia de permiso . Tenga en cuenta que la sección 9 enumera requisitos adicionales relacionados con el modelo de seguridad de Android.

3.2.2. Parámetros de construcción

Las API de Android incluyen una serie de constantes en la clase android.os.Build cuyo objetivo es describir el dispositivo actual.

• [C-0-1] Para proporcionar valores consistentes y significativos en las implementaciones del dispositivo, la siguiente tabla incluye restricciones adicionales en los formatos de estos valores a los que deben conformarse las implementaciones del dispositivo.

3.2.3. Compatibilidad de intenciones

3.2.3.1. Intenciones principales de la aplicación

Los intents de Android permiten que los componentes de la aplicación soliciten funcionalidad de otros componentes de Android. El proyecto ascendente de Android incluye una lista de aplicaciones consideradas aplicaciones principales de Android, que implementa varios patrones de intención para realizar acciones comunes.

• [C-0-1] Las implementaciones del dispositivo deben incluir estas aplicaciones, componentes de servicio o al menos un controlador, para todos los patrones de filtro de intención pública definidos por las siguientes aplicaciones de Android en AOSP:

  • Reloj de escritorio
  • Navegador
  • Calendario
  • Contactos
  • Galería
  • Búsqueda global
  • Lanzacohetes
  • Música
  • Ajustes

3.2.3.2. Resolución de intención

• [C-0-1] Como Android es una plataforma extensible, las implementaciones de dispositivos deben permitir que cada patrón de intención hace referencia en la Sección 3.2.3.1 se anule mediante aplicaciones de terceros. La implementación de código abierto de Android Upstream permite esto de forma predeterminada.

• [C-0-2] Los implementadores de DVICE no deben adjuntar privilegios especiales al uso de aplicaciones del sistema de estos patrones de intención, o evitar que las aplicaciones de terceros se vinculen y asuman el control de estos patrones. Esta prohibición incluye específicamente, entre otras, la desactivación de la interfaz de usuario "Selector" que permite al usuario seleccionar entre múltiples aplicaciones que manejan el mismo patrón de intención.

• [C-0-3] Las implementaciones de dispositivos deben proporcionar una interfaz de usuario para que los usuarios modifiquen la actividad predeterminada para intentos.

• Sin embargo, las implementaciones de dispositivos PUEDEN proporcionar actividades predeterminadas para patrones de URI específicos (por ejemplo, http://play.google.com) cuando la actividad predeterminada proporciona un atributo más específico para el URI de datos. Por ejemplo, un patrón de filtro de intención que especifica el URI de datos "http://www.android.com" es más específico que el patrón de intención principal del navegador para "http://".

Android también incluye un mecanismo para que las aplicaciones de terceros declaren un comportamiento de vinculación de aplicaciones predeterminado autorizado para ciertos tipos de intenciones de URI web. Cuando dichas declaraciones autorizadas se definen en los patrones de filtro de intención de una aplicación, las implementaciones del dispositivo:

• [C-0-4] debe intentar validar cualquier filtros de intención realizando los pasos de validación definidos en la especificación de enlaces de activos digitales implementados por el administrador de paquetes en el proyecto de código abierto de Android ascendente.
• [C-0-5] debe intentar la validación de los filtros de intención durante la instalación de la aplicación y establecer todos los filtros de intención de URI validados con éxito como controladores de aplicaciones predeterminados para sus URI.
• PUEDE establecer filtros de intención de URI específicos como controladores de aplicaciones predeterminados para sus URI, si se verifican correctamente pero otros filtros de URI candidatos no superan la verificación. Si la implementación de un dispositivo hace esto, DEBE proporcionar al usuario anulaciones de patrones por URI apropiadas en el menú de configuración.
• DEBE proporcionar al usuario controles de enlaces de aplicaciones por aplicación en Configuración de la siguiente manera:
  • [C-0-6] El usuario debe poder anular integral el comportamiento predeterminado de enlaces de la aplicación para que una aplicación esté: siempre abierto, siempre pregunte o nunca abrir, lo que debe aplicarse a todos los filtros de intención de URI candidatos por igual.
  • [C-0-7] El usuario debe poder ver una lista de los filtros de intención de URI candidato.
  • La implementación del dispositivo PUEDE proporcionar al usuario la capacidad de anular filtros de intención de URI candidatos específicos que se verificaron con éxito, por filtro por intención.
  • [C-0-8] La implementación del dispositivo debe proporcionar a los usuarios la capacidad de ver y anular los filtros de intención de URI candidatos específicos si la implementación del dispositivo permite que algunos filtros de intención de URI candidatos tengan éxito, mientras que otros pueden fallar.

3.2.3.3. Espacios de nombres de intención

• [C-0-1] Las implementaciones del dispositivo no deben incluir ningún componente de Android que honre cualquier nuevo intención o patrones de intención de transmisión utilizando una acción, categoría u otra cadena clave en Android. o com.android. espacio de nombres.
• [C-0-2] Los implementadores de dispositivos no deben incluir componentes de Android que honre cualquier nuevo intención o patrones de intención de transmisión utilizando una acción, categoría u otra cadena clave en un espacio de paquete perteneciente a otra organización.
• [C-0-3] Los implementadores de dispositivos no deben alterar ni extender ninguno de los patrones de intención utilizados por las aplicaciones principales enumeradas en la Sección 3.2.3.1 .
• Las implementaciones de dispositivos PUEDEN incluir patrones de intención que utilizan espacios de nombres asociados clara y obviamente con su propia organización. Esta prohibición es análoga a la especificada para las clases de lenguaje Java en la sección 3.6 .

3.2.3.4. Intenciones de transmisión

Las aplicaciones de terceros dependen de la plataforma para transmitir ciertos intentos de notificarles sobre cambios en el entorno de hardware o software.

Implementaciones de dispositivos:

• [C-0-1] debe transmitir las intenciones de transmisión pública en respuesta a los eventos del sistema apropiados como se describe en la documentación SDK. Tenga en cuenta que este requisito no está en conflicto con la Sección 3.5, ya que la limitación para las aplicaciones de fondo también se describe en la documentación SDK.

3.2.3.5. Configuración predeterminada de la aplicación

Android incluye configuraciones que brindan a los usuarios una manera fácil de seleccionar sus aplicaciones predeterminadas, por ejemplo, para la pantalla de inicio o SMS.

Cuando tenga sentido, las implementaciones de dispositivos DEBEN proporcionar un menú de configuración similar y ser compatibles con el patrón de filtro de intención y los métodos API que se describen en la documentación del SDK como se muestra a continuación.

Si las implementaciones de dispositivos informan android.software.home_screen , ellos:

• [C-1-1] debe honrar el android.settings.home_settings intención de mostrar un menú de configuración de aplicación predeterminado para la pantalla de inicio.

Si las implementaciones de dispositivos informan android.hardware.telephony , ellos:

• [C-2-1] debe proporcionar un menú de configuración que llame al android.provider.telephony.action_change_default intención para mostrar un diálogo para cambiar la aplicación SMS predeterminada.

Si las implementaciones de dispositivos informan android.hardware.nfc.hce , ellos:

• [C-3-1] debe honrar el android.settings.nfc_payment_settings intención de mostrar un menú de configuración de la aplicación predeterminada para tocar y pagar.

Si las implementaciones de dispositivos informan android.hardware.telephony , ellos:

• [C-4-1] debe honrar el android.telecom.action.change_default_dialer intención para mostrar un cuadro de diálogo para permitir al usuario cambiar la aplicación del teléfono predeterminada.

Si las implementaciones de dispositivos admiten el servicio de interacción Voice, ellos:

• [C-5-1] debe honrar el android.settings.action_voice_input_settings intención de mostrar un menú de configuración de la aplicación predeterminada para entrada y asistencia de voz.

3.2.4. Actividades en pantallas secundarias

Si las implementaciones de dispositivos permiten el lanzamiento de actividades normales de Android en pantallas secundarias, ellos:

• [C-1-1] debe establecer el indicador android.software.activities_on_secondary_displays .
• [C-1-2] debe garantizar la compatibilidad de API similar a una actividad que se ejecuta en la pantalla primaria.
• [C-1-3] debe aterrizar la nueva actividad en la misma pantalla que la actividad que la lanzó, cuando se inicia la nueva actividad sin especificar una pantalla objetivo a través de la API ActivityOptions.setLaunchDisplayId() .
• [C-1-4] Debe destruir todas las actividades, cuando se elimina una pantalla con la bandera Display.FLAG_PRIVATE .
• [C-1-5] debe cambiar el tamaño en consecuencia todas las actividades en un VirtualDisplay si la pantalla en sí se redimensiona.
• Puede mostrar un IME (editor de métodos de entrada, un control de usuario que permite a los usuarios ingresar texto) en la pantalla primaria, cuando un campo de entrada de texto se enfoca en una pantalla secundaria.
• Debe implementar el enfoque de entrada en la pantalla secundaria independientemente de la pantalla primaria, cuando se admiten entradas táctil o clave.
• Debe tener android.content.res.Configuration que corresponde a esa pantalla para mostrarse, operar correctamente y mantener la compatibilidad si se lanza una actividad en la pantalla secundaria.

Si las implementaciones de dispositivos permiten el lanzamiento de actividades normales de Android en pantallas secundarias y las pantallas primarias y secundarias tienen diferentes android.util.displaymetrics :

• [C-2-1] Las actividades no resistentes (que tienen resizeableActivity=false en AndroidManifest.xml ) y las aplicaciones dirigidas al nivel 23 o inferior no deben permitirse en las pantallas secundarias.

Si las implementaciones de dispositivos permiten el lanzamiento de actividades normales de Android en pantallas secundarias y una pantalla secundaria tiene Android.view.display.flag_private Flag:

• [C-3-1] Solo el propietario de esa pantalla, sistema y actividades que ya están en esa pantalla deben poder lanzarse. Todos pueden iniciarse a una pantalla que tiene android.view.display.flag_public .

3.3. Compatibilidad API nativa

La compatibilidad del código nativo es un desafío. Por esta razón, los implementadores de dispositivos son:

• [SR] Muy recomendable para usar las implementaciones de las bibliotecas que se enumeran a continuación del proyecto de código abierto de Android ascendente.

3.3.1. Interfaces binarias de aplicaciones

El código de bytes de Dalvik administrado puede llamar al código nativo proporcionado en el archivo .apk de la aplicación como un archivo ELF .so compilado para la arquitectura de hardware del dispositivo adecuada. Como el código nativo depende en gran medida de la tecnología del procesador subyacente, Android define una serie de interfaces binarias de aplicaciones (ABI) en el NDK de Android.

Implementaciones de dispositivos:

• [C-0-1] debe ser compatible con uno o más ABIS definido e implementar compatibilidad con el NDK de Android.
• [C-0-2] debe incluir soporte para el código que se ejecuta en el entorno administrado para llamar al código nativo, utilizando la semántica estándar de la interfaz nativa de Java (JNI).
• [C-0-3] debe ser compatible con la fuente (es decir, compatible con el encabezado) y compatible binario (para el ABI) con cada biblioteca requerida en la lista a continuación.
• [C-0-4] debe apoyar el ABI equivalente de 32 bits si se respalda ABI de 64 bits.
• [C-0-5] debe informar con precisión la interfaz binaria de la aplicación nativa (ABI) compatible con el dispositivo, a través de android.os.Build.SUPPORTED_ABIS , android.os.Build.SUPPORTED_32_BIT_ABIS y android.os.Build.SUPPORTED_64_BIT_ABIS parámetros cada uno una lista separada por coma de ABIS ordenada de la más preferida a la menos preferida.
• [C-0-6] debe informar, a través de los parámetros anteriores, solo aquellos ABI documentados y descritos en la última versión de la documentación de administración de ABI de Android NDK , e deben incluir soporte para la extensión Avanzada SIMD (AKA Neon).

• [C-0-7] Debe hacer que todas las bibliotecas siguientes, proporcionando API nativas, disponibles para aplicaciones que incluyan código nativo:

  • Libbaaudio.so (soporte de audio nativo de Aaudio)
  • libandroid.so (soporte de actividad nativo de Android)
  • libc (biblioteca C)
  • libcamera2ndk.so
  • libdl (enlazador dinámico)
  • libEGL.so (gestión de superficie nativa OpenGL)
  • libGLESv1_CM.so (OpenGL ES 1.x)
  • libGLESv2.so (OpenGL ES 2.0)
  • libGLESv3.so (OpenGL ES 3.x)
  • libicui18n.so
  • libicuuc.so
  • libjnigraphics.so
  • liblog (registro de Android)
  • libmediandk.so (soporte de API de medios nativos)
  • libm (biblioteca de matemáticas)
  • libOpenMAXAL.so (soporte para OpenMAX AL 1.0.1)
  • libOpenSLES.so (soporte de audio OpenSL ES 1.0.1)
  • libRS.so
  • libstdc++ (soporte mínimo para C++)
  • libvulkan.so (Vulkan)
  • libz (compresión Zlib)
  • interfaz JNI

• [C-0-8] no debe agregar ni eliminar las funciones públicas para las bibliotecas nativas enumeradas anteriormente.

• [C-0-9] debe enumerar bibliotecas adicionales que no son de AOSP expuestas directamente a aplicaciones de terceros en /vendor/etc/public.libraries.txt .
• [C-0-10] no debe exponer ninguna otra biblioteca nativa, implementadas y proporcionadas en AOSP como bibliotecas del sistema, a aplicaciones de terceros que dirigen el nivel 24 o superior de API a medida que están reservadas.
• [C-0-11] debe exportar todos los símbolos de la función de paquete de extensión OpenGL ES 3.1 y Android , como se define en el NDK, a través de la biblioteca libGLESv3.so . Tenga en cuenta que si bien todos los símbolos deben estar presentes, la Sección 7.1.4.1 describe con más detalle los requisitos para cuándo se espera la implementación completa de cada funciones correspondientes.
• [C-0-12] Debe exportar símbolos de función para los Symobbls de funciones Core Vulkan 1.0, así como VK_KHR_surface libvulkan.so VK_KHR_android_surface , VK_KHR_swapchain , VK_KHR_maintenance1 y VK_KHR_get_physical_device_properties2 Extensions Tenga en cuenta que si bien todos los símbolos deben estar presentes, la Sección 7.1.4.2 describe con más detalle los requisitos para cuándo se espera la implementación completa de cada funciones correspondientes.
• DEBE construirse utilizando el código fuente y los archivos de encabezado disponibles en el proyecto de código abierto de Android.

Tenga en cuenta que las versiones futuras del NDK de Android pueden incluir compatibilidad con ABI adicionales.

3.3.2. Compatibilidad con código nativo ARM de 32 bits

Si las implementaciones del dispositivo son dispositivos ARM de 64 bits, entonces:

• [C-1-1] Aunque la arquitectura ARMV8 desaproba varias operaciones de CPU, incluidas algunas operaciones utilizadas en el código nativo existente, las siguientes operaciones desaprobadas deben permanecer disponibles para el código de brazo nativo de 32 bits, ya sea a través del soporte de CPU nativo o mediante emulación de software:

  • Instrucciones SWP y SWPB
  • Instrucción ESTABLECER
  • Operaciones de barrera CP15ISB, CP15DSB y CP15DMB

Si las implementaciones de dispositivos incluyen un brazo ABI de 32 bits, ellos:

• [C-2-1] debe incluir las siguientes líneas en /proc/cpuinfo cuando se lee mediante aplicaciones ARM de 32 bits para garantizar la compatibilidad con las aplicaciones construidas utilizando versiones heredadas de Android NDK.

  • Features: seguido de una lista de cualquier característica opcional de CPU ARMV7 admitidas por el dispositivo.
  • CPU architecture: seguido de un entero que describe la arquitectura ARM más alta del dispositivo (p. Ej., "8" para dispositivos ARMV8).

• No debe alterar /proc/cpuinfo cuando se lea mediante aplicaciones ARM o no brazo de 64 bits.

3.4. Compatibilidad web

3.4.1. Compatibilidad con WebView

Si las implementaciones de dispositivos proporcionan una implementación completa de la API android.webkit.Webview , ellos:

• [C-1-1] debe informar android.software.webview .
• [C-1-2] debe usar la compilación del proyecto Chromium desde el proyecto de código abierto de Android ascendente en la rama Android 8.0 para la implementación de la API android.webkit.WebView .

• [C-1-3] La cadena del agente de usuario informada por la vista web debe estar en este formato:

  Mozilla/5.0 (Linux; Android $(VERSIÓN); $(MODEL) Build/$(BUILD); wv) AppleWebKit/537.36 (KHTML, como Gecko) Versión/4.0 $(CHROMIUM_VER) Mobile Safari/537.36

  • El valor de la cadena $(VERSION) DEBE ser el mismo que el valor de android.os.Build.VERSION.RELEASE.
  • El valor de la cadena $(MODEL) DEBE ser el mismo que el valor de android.os.Build.MODEL.
  • El valor de la cadena $(BUILD) DEBE ser el mismo que el valor de android.os.Build.ID.
  • El valor de la cadena $(CHROMIUM_VER) DEBE ser la versión de Chromium en el proyecto de código abierto de Android ascendente.
  • Las implementaciones de dispositivos PUEDEN omitir Mobile en la cadena del agente de usuario.

• El componente WebView DEBE incluir soporte para tantas funciones HTML5 como sea posible y, si es compatible, la función DEBE ajustarse a la especificación HTML5 .

3.4.2. Compatibilidad del navegador

Si las implementaciones del dispositivo incluyen una aplicación de navegador independiente para navegación web general, ellos:

• [C-1-1] debe apoyar cada una de estas API asociadas con HTML5:
  • caché de aplicaciones/operación sin conexión
  • etiqueta <vídeo>
  • geolocalización
• [C-1-2] debe admitir la API HTML5/W3C WebStorage y debe admitir la API HTML5/W3C indexedDB . Tenga en cuenta que a medida que los organismos de estándares de desarrollo web están haciendo la transición para favorecer IndexedDB sobre el almacenamiento web, se espera que IndexedDB se convierta en un componente requerido en una versión futura de Android.
• Puede enviar una cadena de agente de usuario personalizado en la aplicación de navegador independiente.
• Debería implementar soporte para la mayor cantidad de HTML5 posible en la aplicación de navegador independiente (ya sea basada en la aplicación del navegador WebKit ascendente o un reemplazo de terceros).

Sin embargo, si las implementaciones del dispositivo no incluyen una aplicación de navegador independiente, ellos:

• [C-2-1] aún debe apoyar los patrones de intención pública como se describe en la Sección 3.2.3.1 .

3.5. Compatibilidad de comportamiento de API

Los comportamientos de cada uno de los tipos de API (administrada, software, nativa y web) deben ser coherentes con la implementación preferida del proyecto de código abierto de Android ascendente. Algunas áreas específicas de compatibilidad son:

• [C-0-1] Los dispositivos no deben cambiar el comportamiento o la semántica de una intención estándar.
• [C-0-2] Los dispositivos no deben alterar el ciclo de vida o la semántica del ciclo de vida de un tipo particular de componente del sistema (como servicio, actividad, contenido, etc.).
• [C-0-3] Los dispositivos no deben cambiar la semántica de un permiso estándar.
• Los dispositivos no deben alterar las limitaciones aplicadas en las aplicaciones de fondo. Más específicamente, para aplicaciones de fondo:
  • [C-0-4] Deben dejar de ejecutar devoluciones de llamada que están registradas por la aplicación para recibir salidas del GnssMeasurement y GnssNavigationMessage .
  • [C-0-5] Deben calificar la frecuencia de las actualizaciones que se proporcionan a la aplicación a través de la clase API LocationManager o el método WifiManager.startScan() .
  • [C-0-6] Si la aplicación está dirigida a la API nivel 25 o superior, no deben permitir registrar receptores de transmisión para las transmisiones implícitas de las intenciones estándar de Android en el manifiesto de la aplicación, a menos que la intención de transmisión requiera una "signature" o "signatureOrSystem" protectionLevel permiso o están en la lista de exención .
  • [C-0-7] Si la aplicación está dirigida a la API nivel 25 o superior, debe detener los servicios de fondo de la aplicación, como si la aplicación hubiera llamado el método stopSelf() de los servicios, a menos que la aplicación se coloque en una lista de permiso temporal para manejar una tarea visible para el usuario.
  • [C-0-8] Si la aplicación está dirigida a la API nivel 25 o superior, deben liberar los wakelocks que posee la aplicación.

La lista anterior no es exhaustiva. El Compatibility Test Suite (CTS) prueba partes importantes de la plataforma para determinar la compatibilidad del comportamiento, pero no todas. Es responsabilidad del implementador garantizar la compatibilidad del comportamiento con el Proyecto de código abierto de Android. Por esta razón, los implementadores de dispositivos DEBEN utilizar el código fuente disponible a través del Proyecto de código abierto de Android siempre que sea posible, en lugar de volver a implementar partes importantes del sistema.

3.6. Espacios de nombres API

Android sigue las convenciones de espacio de nombres de paquetes y clases definidas por el lenguaje de programación Java. Para garantizar la compatibilidad con aplicaciones de terceros, los implementadores de dispositivos NO DEBEN realizar modificaciones prohibidas (ver a continuación) en estos espacios de nombres de paquetes:

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

Es decir, ellos:

• [C-0-1] no debe modificar las API expuestas públicamente en la plataforma Android cambiando cualquier método o firma de clase, o eliminando clases o campos de clase.
• [C-0-2] no debe agregar ningún elemento expuesto públicamente (como clases o interfaces, o campos o métodos a las clases o interfaces existentes) o probar o API del sistema a las API en los espacios de nombres anteriores. Un "elemento expuesto públicamente" es cualquier construcción que no esté decorada con el marcador "@hide" como se usa en el código fuente de Android aguas arriba.

Los implementadores de dispositivos pueden modificar la implementación subyacente de las API, pero tales modificaciones:

• [C-0-3] no debe afectar el comportamiento establecido y la firma en idioma Java de ninguna API expuesta públicamente.
• [C-0-4] no debe anunciarse ni expuestos a los desarrolladores.

Sin embargo, los implementadores de dispositivos pueden agregar API personalizadas fuera del espacio de nombres de Android estándar, pero las API personalizadas:

• [C-0-5] no debe estar en un espacio de nombres propiedad o referirse a otra organización. Por ejemplo, los implementadores de dispositivos NO DEBEN agregar API al espacio de nombres com.google.* o similar: solo Google puede hacerlo. De manera similar, Google NO DEBE agregar API a los espacios de nombres de otras empresas.
• [C-0-6] debe empaquetarse en una biblioteca compartida de Android para que solo las aplicaciones que las usen explícitamente (a través del mecanismo <suse-library>) se vean afectadas por el aumento del uso de la memoria de dichas API.

Si un implementador de dispositivo propone mejorar uno de los espacios de nombres de paquetes anteriores (por ejemplo, agregando nuevas funciones útiles a una API existente o agregando una nueva API), el implementador DEBE visitar source.android.com y comenzar el proceso para contribuir con cambios y código, según la información de ese sitio.

Tenga en cuenta que las restricciones anteriores corresponden a convenciones estándar para nombrar API en el lenguaje de programación Java; Esta sección simplemente tiene como objetivo reforzar esas convenciones y hacerlas vinculantes mediante su inclusión en esta Definición de compatibilidad.

3.7. Compatibilidad en tiempo de ejecución

Implementaciones de dispositivos:

• [C-0-1] debe admitir el formato completo de Dalvik Ejecutable (DEX) y la especificación y semántica de Bytecode Dalvik .

• [C-0-2] debe configurar Dalvik Runtimes para asignar la memoria de acuerdo con la plataforma Android ascendente, y según lo especificado por la siguiente tabla. (Consulte la sección 7.1.1 para conocer las definiciones de tamaño y densidad de pantalla).

• Debería usar Android Runtime (ART), la implementación de referencia aguas arriba del formato ejecutable de Dalvik y el sistema de gestión de paquetes de la implementación de referencia.

• Debe ejecutar pruebas de fuzz en varios modos de ejecución y arquitecturas de destino para asegurar la estabilidad del tiempo de ejecución. Consulte JFuzz y Dexfuzz en el sitio web del Proyecto de código abierto de Android.

Tenga en cuenta que los valores de memoria especificados a continuación se consideran valores mínimos y las implementaciones de dispositivos PUEDEN asignar más memoria por aplicación.

3.8. Compatibilidad de la interfaz de usuario

3.8.1. Lanzador (pantalla de inicio)

Android incluye una aplicación de inicio (pantalla de inicio) y soporte para aplicaciones de terceros para reemplazar el iniciador del dispositivo (pantalla de inicio).

Si las implementaciones del dispositivo permiten aplicaciones de terceros para reemplazar la pantalla de inicio del dispositivo, ellos:

• [C-1-1] debe declarar la función de la plataforma android.software.home_screen .
• [C-1-2] debe devolver el objeto AdaptiveIconDrawable cuando la aplicación de terceros use la etiqueta <adaptive-icon> para proporcionar su icono, y se llaman a los métodos PackageManager para recuperar iconos.

Si las implementaciones del dispositivo incluyen un lanzador predeterminado que admite la fijación en la aplicación de accesos directos, ellos:

• [C-2-1] Debe informar true para ShortcutManager.isRequestPinShortcutSupported() .
• [C-2-2] debe tener el servicio del usuario solicitando al usuario antes de agregar un acceso directo solicitado por las aplicaciones a través del método API ShortcutManager.requestPinShortcut() .

Por el contrario, si las implementaciones del dispositivo no admiten la fijación en la aplicación, ellos:

• [C-3-1] debe informar false para ShortcutManager.isRequestPinShortcutSupported() y AppWidgetManager.html#isRequestPinAppWidgetSupported() .

Si las implementaciones de dispositivos implementan un lanzador predeterminado que proporciona acceso rápido a los accesos directos adicionales proporcionados por las aplicaciones de terceros a través de la API de ShatCutManager , ellos:

• [C-4-1] debe admitir todas las características documentadas de acceso directo (p ShortcutManager Ej.

Si las implementaciones del dispositivo incluyen una aplicación de lanzador predeterminada que muestra insignias para los iconos de la aplicación, ellos:

• [C-5-1] debe respetar el método API NotificationChannel.setShowBadge() . En otras palabras, muestre una capacidad visual asociada con el icono de la aplicación si el valor se establece como true , y no muestre ningún esquema de insignias de icono de la aplicación cuando todos los canales de notificación de la aplicación han establecido el valor como false .
• Puede anular las insignias de ícono de la aplicación con su esquema de insignia patentado cuando las aplicaciones de terceros indican el soporte del esquema de insignia propietario mediante el uso de API patentadas, pero deben usar los recursos y valores proporcionados a través de las API de las insignias de notificación descritas en el SDK , como The Notification.Builder.setNumber() y The Notification.Builder.setBadgeIconType() API.

3.8.2. widgets

Android admite widgets de aplicaciones de terceros definiendo un tipo de componente y un ciclo de API y vida correspondiente que permite que las aplicaciones expongan un "AppWidget" al usuario final.

Si las implementaciones de dispositivos admiten widgets de aplicaciones de terceros, ellos:

• [C-1-1] debe declarar soporte para la función de plataforma android.software.app_widgets.
• [C-1-2] debe incluir soporte incorporado para AppWidgets y exponer las posibilidades de la interfaz de usuario para agregar, configurar, ver y eliminar AppWidgets directamente dentro del lanzador.
• [C-1-3] debe ser capaz de hacer widgets de 4 x 4 en el tamaño de la cuadrícula estándar. Consulte las pautas de diseño de widget de la aplicación en la documentación de Android SDK para más detalles.
• Puede admitir widgets de aplicación en la pantalla de bloqueo.

Si las implementaciones de dispositivos admiten widgets de aplicaciones de terceros y fijación en la aplicación de accesos directos, ellos:

• [C-2-1] debe informar true para AppWidgetManager.html.isRequestPinAppWidgetSupported() .
• [C-2-2] debe tener el servicio del usuario solicitando al usuario antes de agregar un acceso directo solicitado por las aplicaciones a través del método API AppWidgetManager.requestPinAppWidget() .

3.8.3. Notificaciones

Android incluye Notification y NotificationManager que permiten a los desarrolladores de aplicaciones de terceros notificar a los usuarios de eventos notables y atraer la atención de los usuarios utilizando los componentes de hardware (p. Ej. .

3.8.3.1. Presentación de notificaciones

Si las implementaciones de dispositivos permiten que las aplicaciones de terceros notifiquen a los usuarios de eventos notables , ellos:

• [C-1-1] debe admitir notificaciones que usan características de hardware, como se describe en la documentación SDK, y en la medida posible con el hardware de implementación del dispositivo. Por ejemplo, si la implementación de un dispositivo incluye un vibrador, DEBE implementar correctamente las API de vibración. Si la implementación de un dispositivo carece de hardware, las API correspondientes DEBEN implementarse como no operativas. Este comportamiento se detalla más en la sección 7 .
• [C-1-2] debe representar correctamente todos los recursos (iconos, archivos de animación, etc.) proporcionados en las API, o en la Guía de estilo de icono de estado/estado del sistema, aunque pueden proporcionar una experiencia de usuario alternativa para las notificaciones que la proporcionada por la implementación de código abierto de Android de referencia.
• [C-1-3] debe honrar e implementar adecuadamente los comportamientos descritos para las API para actualizar, eliminar y grupos de notificaciones.
• [C-1-4] debe proporcionar el comportamiento completo de la API de NotificationChannel documentada en el SDK.
• [C-1-5] debe proporcionar una posibilidad del usuario para bloquear y modificar una determinada notificación de la aplicación de terceros según cada canal y nivel de paquete de aplicaciones.
• [C-1-6] también debe proporcionar una posibilidad del usuario para mostrar canales de notificación eliminados.
• Debe apoyar notificaciones ricas.
• Debería presentar algunas notificaciones de mayor prioridad como notificaciones de frente.
• Debe tener el servicio del usuario para dormir las notificaciones.
• Solo puede administrar la visibilidad y el momento de cuándo las aplicaciones de terceros pueden notificar a los usuarios de eventos notables para mitigar problemas de seguridad, como la distracción del conductor.

Si las implementaciones de dispositivos admiten notificaciones ricas, ellos:

• [C-2-1] debe usar los recursos exactos según lo dispuesto a través de la clase Notification.Style Class de API de estilo y sus subclases para los elementos de recursos presentados.
• Deben presentar todos y cada uno de los elementos de recursos (por ejemplo, icono, título y texto de resumen) definidos en la clase API Notification.Style y sus subclases.

Si las implementaciones de dispositivos admiten notificaciones de aviso: ellos: ellos:

• [C-3-1] debe usar la vista de notificación y los recursos de aviso como se describe en la Notification.Builder Clase de API de constructor cuando se presentan notificaciones de aviso.

3.8.3.2. Servicio de oyentes de notificación

Android incluye las API NotificationListenerService que permiten que las aplicaciones (una vez habilitadas explícitamente por el usuario) reciban una copia de todas las notificaciones a medida que se publican o se actualizan.

Implementaciones de dispositivos:

• [C-0-1] debe actualizar de manera correcta y de inmediato las notificaciones en su totalidad a todos estos servicios de oyentes instalados y habilitados para el usuario, incluidos todos y cada uno de los metadatos adjuntos al objeto de notificación.
• [C-0-2] debe respetar la llamada API snoozeNotification() y descartar la notificación y hacer una devolución de llamada después de la duración de la repetición que se establece en la llamada API.

Si las implementaciones de dispositivos tienen la posibilidad del usuario de las notificaciones de repetición, ellos:

• [C-1-1] debe reflejar el estado de notificación repetidos correctamente a través de las API estándar, como NotificationListenerService.getSnoozedNotifications() .
• [C-1-2] debe hacer que este proceso de usuario esté disponible para dormir las notificaciones de cada aplicación de terceros instaladas, a menos que sean de servicios persistentes/de primer plano.

3.8.3.3. Dnd (no molestar)

Si las implementaciones de dispositivos admiten la función DND, ellos:

• [C-1-1] debe implementar una actividad que responda a la intención Action_Notification_Policy_Access_Settings , que para implementaciones con UI_MODE_TYPE_Normal debe ser una actividad donde el usuario puede otorgar la aplicación acceso a configuraciones de políticas DND.
• [C-1-2] debe, para cuando la implementación del dispositivo, ha proporcionado un medio para que el usuario otorgue o denegue aplicaciones de terceros para acceder a la configuración de la política DND, muestre las reglas DND automáticas creadas por aplicaciones junto con las aplicaciones junto con el usuario. -Las reglas definidas.
• [C-1-3] Debe honrar los valores suppressedVisualEffects pasados ​​a lo largo de NotificationManager.Policy y si una aplicación ha establecido cualquiera de los indicadores Supressed_Effect_Screen_off o Supressed_Effect_Screen_on, debe indicar al usuario que los efectos visuales se suprimen en el menú DND de la configuración.

3.8.4. Buscar

Android incluye API que permiten a los desarrolladores incorporar la búsqueda en sus aplicaciones y exponer los datos de su aplicación en la búsqueda del sistema global. En términos generales, esta funcionalidad consta de una única interfaz de usuario para todo el sistema que permite a los usuarios ingresar consultas, muestra sugerencias a medida que los usuarios escriben y muestra resultados. Las API de Android permiten a los desarrolladores reutilizar esta interfaz para proporcionar búsqueda dentro de sus propias aplicaciones y permitir a los desarrolladores proporcionar resultados a la interfaz de usuario de búsqueda global común.

• Las implementaciones de dispositivos Android DEBEN incluir búsqueda global, una interfaz de usuario de búsqueda única, compartida y en todo el sistema capaz de realizar sugerencias en tiempo real en respuesta a las entradas del usuario.

Si las implementaciones de dispositivos implementan la interfaz de búsqueda global, ellos:

• [C-1-1] debe implementar las API que permitan que las aplicaciones de terceros agregen sugerencias al cuadro de búsqueda cuando se ejecute en modo de búsqueda global.

Si no se instalan aplicaciones de terceros que utilizan la búsqueda global:

• El comportamiento predeterminado debe ser mostrar los resultados y las sugerencias del motor de búsqueda web.

Android también incluye las API de asistencia para permitir que las aplicaciones elijan cuánta información del contexto actual se comparte con el asistente en el dispositivo.

Si las implementaciones de dispositivos admiten la acción de asistencia, ellos:

• [C-2-1] debe indicar claramente al usuario final cuando se comparte el contexto, por cualquiera:
  • Cada vez que la aplicación de asistencia accede al contexto, que muestra una luz blanca alrededor de los bordes de la pantalla que cumplen o exceden la duración y el brillo de la implementación del proyecto de código abierto de Android.
  • Para la aplicación de asistencia preinstalada, proporcionando una oferta del usuario a menos de dos navegaciones del menú predeterminada de entrada de voz y configuración de la aplicación de asistente , y solo compartir el contexto cuando el usuario invoca explícitamente la aplicación de la clave de navegación de Hot Word o Assist.
• [C-2-2] La interacción designada para iniciar la aplicación Assist como se describe en la Sección 7.2.3 debe iniciar la aplicación de asistencia seleccionada por el usuario, en otras palabras, la aplicación que implementa VoiceInteractionService , o una actividad que maneja la intención ACTION_ASSIST .
• [C-SR] Muy recomendable para usar Long Press en HOME Key como esta interacción designada.

3.8.5. Alertas y tostadas

Las aplicaciones pueden usar la API Toast para mostrar cadenas no modales cortas al usuario final que desaparece después de un breve período de tiempo, y usar la API de tipo de ventana TYPE_APPLICATION_OVERLAY para mostrar Windows de alerta como una superposición sobre otras aplicaciones.

Si las implementaciones del dispositivo incluyen una pantalla de pantalla o video, ellos:

• [C-1-1] debe proporcionar una posibilidad del usuario para bloquear una aplicación para mostrar Windows de alerta que usan el TYPE_APPLICATION_OVERLAY . La implementación de AOSP cumple con este requisito al tener controles en la sombra de notificación.

• [C-1-2] debe honrar la API de tostadas y mostrar tostadas de aplicaciones a usuarios finales de una manera muy visible.

3.8.6. Temas

Android proporciona "temas" como mecanismo para que las aplicaciones apliquen estilos en toda una actividad o aplicación.

Android incluye una familia de temas "holo" y "material" como un conjunto de estilos definidos para que los desarrolladores de aplicaciones lo usen si quieren que coincidan con el aspecto del tema de Holo y la sensación definida por el SDK de Android.

Si las implementaciones del dispositivo incluyen una pantalla de pantalla o video, ellos:

• [C-1-1] no debe alterar ninguno de los atributos del tema de Holo expuestos a las aplicaciones.
• [C-1-2] debe apoyar a la familia de temas "material" y no debe alterar ninguno de los atributos del tema del material o sus activos expuestos a aplicaciones.

Android también incluye una familia de temas de "dispositivo predeterminado del dispositivo" como un conjunto de estilos definidos para que los desarrolladores de aplicaciones usen si desean coincidir con el aspecto del tema del dispositivo según lo definido por el implementador del dispositivo.

• Las implementaciones del dispositivo pueden modificar los atributos del tema predeterminados del dispositivo expuestos a las aplicaciones.

Android admite un tema variante con barras de sistema translúcido, que permite a los desarrolladores de aplicaciones llenar el área detrás del estado y la barra de navegación con el contenido de su aplicación. Para permitir una experiencia de desarrollador consistente en esta configuración, es importante que el estilo del ícono de la barra de estado se mantenga en diferentes implementaciones de dispositivos.

Si las implementaciones del dispositivo incluyen una barra de estado del sistema, ellos:

• [C-2-1] debe usar White para los iconos de estado del sistema (como la resistencia a la señal y el nivel de la batería) y las notificaciones emitidas por el sistema, a menos que el icono indique un estado problemático o una aplicación solicite una barra de estado de luz utilizando el System_UI_FLAG_STATUS_BAR FLAG .
• [C-2-2] Las implementaciones del dispositivo Android deben cambiar el color de los iconos de estado del sistema a negro (para más detalles, consulte R.Style ) cuando una aplicación solicita una barra de estado de luz.

3.8.7. Fondos de pantalla vivos

Android define un tipo de componente y la API y el ciclo de vida correspondiente que permite que las aplicaciones expongan uno o más "fondos de pantalla en vivo" al usuario final. Los fondos de pantalla en vivo son animaciones, patrones o imágenes similares con capacidades de entrada limitadas que se muestran como fondo de pantalla, detrás de otras aplicaciones.

Se considera que el hardware es capaz de ejecutar de manera confiable fondos de pantalla en vivo si puede ejecutar todos los fondos de pantalla en vivo, sin limitaciones de funcionalidad, a una velocidad de fotogramas razonable y sin efectos adversos en otras aplicaciones. Si las limitaciones del hardware provocan que los fondos de pantalla y/o las aplicaciones fallen, funcionen mal, consuman demasiada energía de la CPU o de la batería, o se ejecuten a velocidades de fotogramas inaceptablemente bajas, se considera que el hardware es incapaz de ejecutar fondos de pantalla en vivo. Por ejemplo, algunos fondos de pantalla en vivo pueden usar un contexto OpenGL 2.0 o 3.x para representar su contenido. El fondo de pantalla en vivo no se ejecutará de manera confiable en hardware que no admita múltiples contextos OpenGL porque el uso del fondo de pantalla en vivo de un contexto OpenGL puede entrar en conflicto con otras aplicaciones que también usan un contexto OpenGL.

• Las implementaciones de dispositivos capaces de ejecutar fondos de pantalla en vivo de manera confiable, como se describe anteriormente, DEBEN implementar fondos de pantalla en vivo.

Si las implementaciones de dispositivos implementan fondos de pantalla en vivo, ellos:

• [C-1-1] debe informar el indicador de la función de la plataforma android.software.live_wallpaper.

3.8.8. Cambio de actividad

El código fuente de Android ascendente incluye la pantalla de descripción general , una interfaz de usuario a nivel de sistema para el cambio de tareas y la muestra actividades y tareas recientemente accedidas utilizando una imagen en miniatura del estado gráfico de la aplicación en el momento en que el usuario dejó la aplicación por última vez.

Las implementaciones de dispositivos, incluida la clave de navegación de la función reciente, como se detalla en la Sección 7.2.3 , puede alterar la interfaz.

Si las implementaciones del dispositivo, incluida la clave de navegación de la función de reciente, como se detalla en la Sección 7.2.3 , altere la interfaz, ellos:

• [C-1-1] debe admitir al menos hasta 20 actividades mostradas.
• Debería al menos mostrar el título de 4 actividades a la vez.
• [C-1-2] debe implementar el comportamiento de fijación de pantalla y proporcionar al usuario un menú de configuración para alternar la función.
• Debe mostrar resaltar color, icono, título de pantalla en recientes.
• Debe mostrar una posibilidad de cierre ("x"), pero puede retrasar esto hasta que el usuario interactúe con las pantallas.
• Debe implementar un atajo para cambiar fácilmente a la actividad anterior
• Debería activar la acción de conmutación rápida entre las dos aplicaciones utilizadas más recientemente, cuando la tecla de función de recientes se aprovecha dos veces.
• Debe activar el modo multibindow de pantalla dividida, si es compatible, cuando la tecla de funciones de recientes se presiona por mucho tiempo.

• Puede mostrar recientes afiliados como un grupo que se mueve juntos.

• Las implementaciones del dispositivo [C-SR] se recomiendan encarecidamente para usar la interfaz de usuario de Android ascendente (o una interfaz basada en miniatura similar) para la pantalla de descripción general.

3.8.9. Gestión de entradas

Android incluye soporte para la administración de entrada y soporte para editores de métodos de entrada de terceros.

Si las implementaciones de dispositivos permiten a los usuarios usar métodos de entrada de terceros en el dispositivo, ellos:

• [C-1-1] debe declarar la función de la plataforma android.software.input_methods y admitir API IME como se define en la documentación SDK de Android.
• [C-1-2] MUST provide a user-accessible mechanism to add and configure third-party input methods in response to the android.settings.INPUT_METHOD_SETTINGS intent.

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

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

3.8.10. Control de medios de pantalla de bloqueo

La API del cliente de control remoto está en desuso de Android 5.0 a favor de la plantilla de notificación de medios que permite que las aplicaciones de medios se integren con los controles de reproducción que se muestran en la pantalla de bloqueo.

3.8.11. Salvapantallas (anteriormente Dreams)

Android incluye soporte para InteractivesScreensavers , previamente denominados sueños. Los ahorradores de pantalla permiten a los usuarios interactuar con las aplicaciones cuando un dispositivo conectado a una fuente de alimentación está inactiva o acoplada en un muelle de escritorio. Los dispositivos de vigilancia de Android pueden implementar ahorradores de pantalla, pero otros tipos de implementaciones de dispositivos deben incluir soporte para los ahorradores de pantalla y proporcionar una opción de configuración para los usuarios para configurar los ahorradores de pantalla en respuesta a android.settings.DREAM_SETTINGS Intent.

3.8.12. Ubicación

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

• [C-1-1] location modes MUST be displayed in the Location menu within Settings.

3.8.13. Unicode y fuente

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

3.8.14. Ventanas múltiples

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] Applications can indicate whether they are capable of operating in multi-window mode in the AndroidManifest.xml file, either explicitly via setting the android:resizeableActivity attribute to true or implicitly by having the targetSdkVersion > 24. Apps that explicitly set this attribute to false in their manifest MUST NOT be launched in multi-window mode. Older apps with targetSdkVersion < 24 that did not set this android:resizeableActivity attribute MAY be launched in multi-window mode, but the system MUST provide warning that the app may not work as expected in multi-window mode.
• [C-1-3] MUST NOT offer split-screen or freeform mode if the screen height < 440 dp and the screen width < 440 dp.
• Las implementaciones del dispositivo con el tamaño de la pantalla xlarge deben admitir el modo Freeform.

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

• [C-2-1] MUST preload a resizeable launcher as the default.
• [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 minimum width and height of 108 dp for the PIP window and minimum width of 240 dp and height of 135 dp for the PIP window when the Configuration.uiMode is configured as UI_MODE_TYPE_TELEVISION

3.9. Administración de dispositivos

Android incluye características que permiten que las aplicaciones conscientes de la seguridad realicen funciones de administración de dispositivos a nivel del sistema, como hacer cumplir las políticas de contraseña o realizar una limpieza remota, a través de la API de administración de dispositivos Android ].

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 .
• [C-1-3] MUST declare the support of manged profiles via the android.software.managed_users feature flag, except for when the device is configured so that it would report itself as a low RAM device or so that it allocate internal (non-removable) storage as shared storage.

3.9.1 Aprovisionamiento de dispositivos

3.9.1.1 Aprovisionamiento del propietario del dispositivo

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 no user data is configured yet, it:
    • [C-1-3] MUST report true for DevicePolicyManager.isProvisioningAllowed(ACTION_PROVISION_MANAGED_DEVICE) .
    • [C-1-4] MUST enroll the DPC application as the Device Owner app in response to the intent action android.app.action.PROVISION_MANAGED_DEVICE .
    • [C-1-5] MUST enroll the DPC application as the Device Owner app 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 .
  • Cuando la implementación del dispositivo tiene datos de usuario, TI:
    • [C-1-6] MUST report false for the DevicePolicyManager.isProvisioningAllowed(ACTION_PROVISION_MANAGED_DEVICE) .
    • [C-1-7] MUST not enroll any DPC application as the Device Owner App any more.
• [C-1-2] MUST NOT set an application (including pre-installed app) as the Device Owner app without explicit consent or action from the user or the administrator of the device.

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

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

3.9.1.2 Aprovisionamiento de perfil administrado

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

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

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

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

  • Un icono consistente u otro proceso del usuario (por ejemplo, el icono de información AOSP aguas arriba) para representar cuándo una configuración particular está restringida por un administrador del dispositivo.
  • Un breve mensaje de explicación, según lo proporcionado por el administrador del dispositivo a través del setShortSupportMessage .
  • El icono de la aplicación DPC.

3.9.2 Soporte de perfil administrado

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:
  • Contabilidad separada de batería, ubicación, datos móviles y uso de almacenamiento para el usuario principal y el perfil administrado.
  • Gestión independiente de aplicaciones VPN instaladas dentro del usuario primario o perfil administrado.
  • Gestión independiente de aplicaciones instaladas dentro del usuario primario o perfil administrado.
  • Gestión independiente de cuentas dentro del usuario primario o perfil administrado.
• [C-1-8] MUST ensure the preinstalled dialer, contacts and messaging applications can search for and look up caller information from the managed profile (if one exists) alongside those from the primary profile, if the Device Policy Controller permits it.
• [C-1-9] MUST ensure that it satisfies all the security requirements applicable for a device with multiple users enabled (see section 9.5 ), even though the managed profile is not counted as another user in addition to the primary user.
• [C-1-10] MUST support the ability to specify a separate lock screen meeting the following requirements to grant access to apps running in a managed profile.
  • Las implementaciones de dispositivos deben honrar el DevicePolicyManager.ACTION_SET_NEW_PASSWORD Intent y mostrar una interfaz para configurar una credencial de pantalla de bloqueo separada para el perfil administrado.
  • Las credenciales de la pantalla de bloqueo del perfil administrado deben usar los mismos mecanismos de almacenamiento y gestión de credenciales que el perfil principal, como se documenta en el sitio del proyecto de código abierto de Android
  • Las políticas de contraseña de DPC deben aplicarse solo a las credenciales de pantalla de bloqueo del perfil administrado a menos que se solicite la instancia DevicePolicyManager devuelta por GetParentProfileInstance .
• Cuando los contactos del perfil administrado se muestran en el registro de llamadas preinstalado, la interfaz de usuario de guardia, las notificaciones en progreso y las aplicaciones, contactos y mensajes de inscripción en el progreso y las aplicaciones de mensajería, deben ser identificadas con la misma insignia utilizada para indicar aplicaciones de perfil administradas.

3.10. Accesibilidad

Android proporciona una capa de accesibilidad que ayuda a los usuarios con discapacidades a navegar sus dispositivos más fácilmente. Además, Android proporciona API de plataforma que permiten que las implementaciones de servicios de accesibilidad reciban devoluciones de llamada para eventos de usuario y sistema y generen mecanismos de retroalimentación alternativos, como texto a voz, comentarios hápticos y navegación Trackball/D-Pad.

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

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

If device implementations include preloaded accessibility services, they:

• [C-2-1] MUST implement these preloaded 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 a voz

Android incluye API que permiten que las aplicaciones utilicen servicios de texto a voz (TTS) y permitan a los proveedores de servicios proporcionar implementaciones de los servicios TTS.

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

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

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

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

3.12. Marco de entrada de TV

Android Television Input Framework (TIF) simplifica la entrega de contenido en vivo a dispositivos Android Television. TIF proporciona una API estándar para crear módulos de entrada que controlan dispositivos Android Television.

If device implementations support TIF, they:

• [C-1-1] MUST declare the platform feature android.software.live_tv .
• [C-1-2] MUST preload a TV application (TV App) and meet all requirements described in section 3.12.1 .

3.12.1. Aplicación de televisión

If device implementations support TIF:

• [C-1-1] The TV App MUST provide facilities to install and use TV Channels and meet the following requirements.

The TV app that is required for Android device implementations declaring the android.software.live_tv feature flag, MUST meet the following requirements:

• Device implementations SHOULD allow third-party TIF-based inputs ( third-party inputs ) to be installed and managed.
• Las implementaciones de dispositivos pueden proporcionar una separación visual entre las entradas preinstaladas basadas en TIF (entradas instaladas) y entradas de terceros.
• Device implementations SHOULD NOT display the third-party inputs more than a single navigation action away from the TV App (ie expanding a list of third-party inputs from the TV App).

The Android Open Source Project provides an implementation of the TV App that meets the above requirements.

3.12.1.1. Guía electrónica de programas

If device implementations support TIF, they:

• [C-1-1] MUST show an informational and interactive overlay, which MUST include an electronic program guide (EPG) generated from the values in the TvContract.Programs fields.
• [C-1-2] On channel change, device implementations MUST display EPG data for the currently playing program.
• [SR] The EPG is STRONGLY RECOMMENDED to display installed inputs and third-party inputs with equal prominence. The EPG SHOULD NOT display the third-party inputs more than a single navigation action away from the installed inputs on the EPG.
• The EPG SHOULD display information from all installed inputs and third-party inputs.
• El EPG puede proporcionar una separación visual entre las entradas instaladas y las entradas de terceros.

3.12.1.2. Navegación

If device implementations support TIF, they:

• [C-1-1] MUST allow navigation for the following functions via the D-pad, Back, and Home keys on the Android Television device's input device(s) (ie remote control, remote control application, or game controller):

  • Cambiar los canales de TV
  • Apertura EPG
  • Configuración y ajuste de entradas basadas en TIF de terceros
  • Menú de configuración de apertura

• SHOULD pass key events to HDMI inputs through CEC.

3.12.1.3. Vinculación de aplicaciones de entrada de TV

If device implementations support TIF:

• [C-1-1] Android Television device implementations MUST support TV input app linking , which allows all inputs to provide activity links from the current activity to another activity (ie a link from live programming to related content).
• [C-1-2] The TV App MUST show TV input app linking when it is provided.

3.12.1.4. Cambio de hora

If device implementations support TIF, they:

• [SR] STRONGLY RECOMMENDED to support time shifting, which allows the user to pause and resume live content.
• SHOULD provide the user a way to pause and resume the currently playing program, if time shifting for that program is available .

3.12.1.5. grabación de televisión

If device implementations support TIF, they:

• [SR] STRONGLY RECOMMENDED to support TV recording.
• SHOULD provide a user interface to play recorded programs.
• If the TV input supports recording and the recording of a program is not prohibited , the EPG MAY provide a way to record a program .

3.13. Ajustes rápidos

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

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

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

3.14. Media UI

If device implementations include the UI framework that supports third-party apps that depend on MediaBrowser and MediaSession , they:

• [C-1-1] MUST display MediaItem icons and notification icons unaltered.
• [C-1-2] MUST display those items as described by MediaSession, eg, metadata, icons, imagery.
• [C-1-3] MUST show app title.
• [C-1-4] MUST have drawer to present MediaBrowser hierarchy.

3.15. Aplicaciones instantáneas

Device implementations MUST satisfy the following requirements:

• [C-0-1] Instant Apps MUST only be granted permissions that have the android:protectionLevel set to "ephemeral" .
• [C-0-2] Instant Apps MUST NOT interact with installed apps via implicit intents unless one of the following is true:
  • The component's intent pattern filter is exposed and has CATEGORY_BROWSABLE
  • The action is one of ACTION_SEND, ACTION_SENDTO, ACTION_SEND_MULTIPLE
  • The target is explicitly exposed with android:visibleToInstantApps
• [C-0-3] Instant Apps MUST NOT interact explicitly with installed apps unless the component is exposed via android:visibleToInstantApps.
• [C-0-4] IInstalled Apps MUST NOT see details about Instant Apps on the device unless the Instant App explicitly connects to the installed application.

3.16. Companion Device Pairing

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

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

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

4. Compatibilidad del embalaje de la aplicación

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 systemDevice implementations.
• [C-0-2] MUST support verifying “.apk” files using the 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 prompt, as documented in the SDK for the DELETE_PACKAGE permission. Las únicas excepciones son la aplicación del verificador del paquete del sistema que maneja el paquete_needs_verification intent y la aplicación de almacenamiento Manager Manejo de 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.

5. Compatibilidad multimedia

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

Implementaciones 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.
  • No debe aferrarse a los tampones decodificados por más tiempo que según lo especificado por el estándar (por ejemplo, SPS).
  • No debe aferrarse a los tampones codificados más tiempo de lo requerido por la estructura del Partido Republicano.

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.

Tenga en cuenta que ni Google ni Open Handset Alliance garantizan que estos códecs estén libres de patentes de terceros. Se advierte a quienes deseen utilizar este código fuente en productos de hardware o software que las implementaciones de este código, incluso en software de código abierto o shareware, pueden requerir licencias de patente de los titulares de patentes correspondientes.

5.1. Códecs multimedia

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 the following audio encoding:

• [C-1-1] PCM/WAVE

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 the following audio decoders:

• [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-5] FLAC
• [C-1-6] MP3
• [C-1-7] MIDI
• [C-1-8] Vorbis
• [C-1-9] PCM/WAVE
• [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

5.1.3. Audio Codecs Details

5.1.4. Codificación de imágenes

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

5.1.5. Decodificación de imágenes

See more details in 5.1.6. Image Codecs Details .

Device implementations MUST support encoding the following image decoding:

• [C-0-1] JPEG
• [C-0-2] GIF
• [C-0-3] PNG
• [C-0-4] BMP
• [C-0-5] WebP
• [C-0-6] Raw

5.1.6. Detalles de códecs de imagen

5.1.7. Códecs de vídeo

• 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 flexible color format (COLOR_FormatYUV420Flexible).

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.

5.1.8. Lista de códecs de vídeo

5.2. Codificación de vídeo

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

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

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

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

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

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

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

• SHOULD support dynamically configurable bitrates for the supported encoder.

5.2.1. H.263

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

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

5.2.2. H-264

If device implementations support H.264 codec, they:

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

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

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

5.2.3. VP8

If device implementations support VP8 codec, they:

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

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

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

5.2.4. VP9

If device implementations support VP9 codec, they:

• SHOULD support writing Matroska WebM files.

5.3. Decodificación de vídeo

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.

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

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

5.3.1. MPEG-2

If device implementations support MPEG-2 decoders, they:

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

5.3.2. H.263

If device implementations support H.263 decoders, they:

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

5.3.3. MPEG-4

If device implementations with MPEG-4 decoders, they:

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

5.3.4. H.264

If device implementations support H.264 decoders, they:

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

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

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

5.3.5. H.265 (HEVC)

If device implementations support H.265 codec, they:

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

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

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

5.3.6. VP8

If device implementations support VP8 codec, they:

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

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

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

5.3.7. VP9

If device implementations support VP9 codec, they:

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

If device implementations support VP9 codec and a hardware decoder:

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

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

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

5.4. Grabación de audio

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

5.4.1. Captura de audio sin procesar

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

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

  • Formato : PCM lineal, 16 bits
  • Sampling rates : 8000, 11025, 16000, 44100 Hz
  • Canales : mono

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

  • Formato : PCM lineal, 16 bits
  • Sampling rates : 22050, 48000 Hz
  • Canales : estéreo

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. Captura para reconocimiento de voz

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

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

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

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

5.4.3. Captura para redirigir la reproducción

La clase android.media.MediaRecorder.AudioSource incluye la fuente de audio REMOTE_SUBMIX .

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.5. Reproducción de audio

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

5.5.1. Raw Audio Playback

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

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

  • Formato : PCM lineal, 16 bits
  • Tasas de muestreo : 8000, 11025, 16000, 22050, 32000, 44100
  • Canales : mono, estéreo

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

  • Tasas de muestreo : 24000, 48000

5.5.2. Efectos de audio

Android provides an API for audio effects for device implementations.

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

• [C-1-1] MUST support the EFFECT_TYPE_EQUALIZER and EFFECT_TYPE_LOUDNESS_ENHANCER implementations controllable through the AudioEffect subclasses Equalizer , LoudnessEnhancer .
• [C-1-2] MUST support the visualizer API implementation, controllable through the Visualizer class.
• SHOULD support the EFFECT_TYPE_BASS_BOOST , EFFECT_TYPE_ENV_REVERB , EFFECT_TYPE_PRESET_REVERB , and EFFECT_TYPE_VIRTUALIZER implementations controllable through the AudioEffect sub-classes BassBoost , EnvironmentalReverb , PresetReverb , and Virtualizer .

5.5.3. Volumen de salida de audio

Automotive device implementations:

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

5.6. Latencia de audio

La latencia de audio es el retraso de tiempo cuando una señal de audio pasa a través de un sistema. Muchas clases de aplicaciones dependen de latencias cortas, para lograr efectos de sonido en tiempo real.

Para los fines de esta sección, use las siguientes definiciones:

• output latency . The interval between when an application writes a frame of PCM-coded data and when the corresponding sound is presented to environment at an on-device transducer or signal leaves the device via a port and can be observed externally.
• cold output latency . The output latency for the first frame, when the audio output system has been idle and powered down prior to the request.
• continuous output latency . The output latency for subsequent frames, after the device is playing audio.
• input latency . The interval between when a sound is presented by environment to device at an on-device transducer or signal enters the device via a port and when an application reads the corresponding frame of PCM-coded data.
• lost input . The initial portion of an input signal that is unusable or unavailable.
• cold input latency . The sum of lost input time and the input latency for the first frame, when the audio input system has been idle and powered down prior to the request.
• continuous input latency . The input latency for subsequent frames, while the device is capturing audio.
• cold output jitter . The variability among separate measurements of cold output latency values.
• cold input jitter . The variability among separate measurements of cold input latency values.
• continuous round-trip latency . The sum of continuous input latency plus continuous output latency plus one buffer period. The buffer period allows time for the app to process the signal and time for the app to mitigate phase difference between input and output streams.
• OpenSL ES PCM buffer queue API . The set of PCM-related OpenSL ES APIs within Android NDK .
• AAudio native audio API . The set of AAudio APIs within Android NDK .

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

• [SR] Cold output latency of 100 milliseconds or less
• [SR] Continuous output latency of 45 milliseconds or less
• [SR] Minimize the cold output jitter

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

• [SR] STRONGLY RECOMMENDED to report low latency audio by declaring android.hardware.audio.low_latency feature flag.
• [SR] STRONGLY RECOMMENDED to also meet the requirements for low-latency audio via the AAudio API.

If device implementations do not meet the requirements for low-latency audio via the OpenSL ES PCM buffer queue API, they:

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

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

• [SR] Cold input latency of 100 milliseconds or less
• [SR] Continuous input latency of 30 milliseconds or less
• [SR] Continuous round-trip latency of 50 milliseconds or less
• [SR] Minimize the cold input jitter

5.7. Protocolos de red

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

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

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

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

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

Media Segment Formats

RTSP (RTP, SDP)

5.8. Medios seguros

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 wired external displays.

5.9. Interfaz digital para instrumentos musicales (MIDI)

If a device implementation supports the inter-app MIDI software transport (virtual MIDI devices), and it supports MIDI over all of the following MIDI-capable hardware transports for which it provides generic non-MIDI connectivity, it is:

• [SR] STRONGLY RECOMMENDED to report support for feature android.software.midi via the android.content.pm.PackageManager class.

The MIDI-capable hardware transports are:

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

If the device implementation provides generic non-MIDI connectivity over a particular MIDI-capable hardware transport listed above, but does not support MIDI over that hardware transport, it:

• [C-1-1] MUST NOT report support for feature android.software.midi.

5.10. Audio profesional

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

• [C-1-1] MUST report support for feature android.hardware.audio.low_latency .
• [C-1-2] MUST have the continuous round-trip audio latency, as defined in section 5.6 Audio Latency , MUST be 20 milliseconds or less and SHOULD be 10 milliseconds or less over at least one supported path.
• [C-1-3] MUST include a USB port(s) supporting USB host mode and USB peripheral mode.
• [C-1-4] MUST report support for feature android.software.midi .
• [C-1-5] MUST meet latencies and USB audio requirements using the OpenSL ES PCM buffer queue API.
• SHOULD provide a sustainable level of CPU performance while audio is active.
• 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 underruns (output) or overruns (input) under normal use at reported latency.
• SHOULD provide zero inter-channel latency difference.
• SHOULD minimize MIDI mean latency over all transports.
• SHOULD minimize MIDI latency variability under load (jitter) over all transports.
• SHOULD provide accurate MIDI timestamps over all transports.
• SHOULD minimize audio signal noise over on-device transducers, including the period immediately after cold start.
• SHOULD provide zero audio clock difference between the input and output sides of corresponding end-points, when both are active. Examples of corresponding end-points include the on-device microphone and speaker, or the audio jack input and output.
• SHOULD handle audio buffer completion callbacks for the input and output sides of corresponding end-points on the same thread when both are active, and enter the output callback immediately after the return from the input callback. Or if it is not feasible to handle the callbacks on the same thread, then enter the output callback shortly after entering the input callback to permit the application to have a consistent timing of the input and output sides.
• SHOULD minimize the phase difference between HAL audio buffering for the input and output sides of corresponding end-points.
• SHOULD minimize touch latency.
• SHOULD minimize touch latency variability under load (jitter).

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

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

If device implementations meet the requirements via the OpenSL ES PCM buffer queue API, they:

• [SR] STRONGLY RECOMMENDED to also meet the same requirements via the AAudio API.

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

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

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

• [C-3-1] MUST have a continuous round-trip audio latency of 20 milliseconds or less.
• The continuous round-trip audio latency SHOULD be 10 milliseconds or less over the USB host mode port using USB audio class.

If device implementations include a USB port(s) supporting USB host mode, they:

• [C-4-1] MUST implement the USB audio class.

If device implementations include an HDMI port, they:

• [C-5-1] MUST support output in stereo and eight channels at 20-bit or 24-bit depth and 192 kHz without bit-depth loss or resampling.

5.11. Captura para sin procesar

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

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

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

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

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

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

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

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

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

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

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

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

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

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

6. Compatibilidad de opciones y herramientas de desarrollador

6.1. Herramientas de desarrollo

Implementaciones de dispositivos:

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

• Android Debug Bridge (adb)

  • [C-0-2] MUST support all adb functions as documented in the Android SDK including dumpsys .
  • [C-0-3] MUST NOT alter the format or the contents of device system events (batterystats , diskstats, fingerprint, graphicsstats, netstats, notification, procstats) logged via dumpsys.
  • [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 incluye soporte para ADB seguro. Secure ADB habilita ADB en hosts autenticados conocidos.

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

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

• Dalvik Debug Monitor Service (ddms)

  • [C-0-7] MUST support all ddms features as documented in the Android SDK. Como DDMS usa ADB, el soporte para DDMS debe estar inactivo de forma predeterminada, pero debe ser compatible cada vez que el usuario haya activado el puente de depuración de Android, como se indicó anteriormente.
• Mono
  • [C-0-8] MUST include the Monkey framework and make it available for applications to use.
• SysTrace
  • [C-0-9] MUST support systrace tool as documented in the Android SDK. Systrace must be inactive by default and there MUST be a user-accessible mechanism to turn on Systrace.

6.2. Opciones de desarrollador

Android incluye soporte para los desarrolladores para configurar la configuración relacionada con el desarrollo de aplicaciones.

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. La implementación de Android ascendente oculta el menú Opciones de desarrollador de forma predeterminada y permite a los usuarios iniciar opciones de desarrollador después de presionar siete (7) veces en la configuración > Acerca del dispositivo > El elemento del menú de número de compilación .
• [C-0-2] MUST hide Developer Options by default and MUST provide a mechanism to enable Developer Options without the need for any special allowlisting.
• 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. Compatibilidad de hardware

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.

Si una API en el SDK interactúa con un componente de hardware que se declara opcional y la implementación del dispositivo no posee ese componente:

• [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. Pantalla y gráficos

Android includes facilities that automatically adjust application assets and UI layouts appropriately for the device to ensure that third-party applications run well on a variety of hardware configurations . Los dispositivos deben implementar adecuadamente estas API y comportamientos, como se detalla en esta sección.

Las unidades a las que se hace referencia por los requisitos en esta sección se definen de la siguiente manera:

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

7.1.1. Configuración de pantalla

7.1.1.1. Tamaño de pantalla

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 .

• [C-0-1] Device implementations 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] Device implementations 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.

7.1.1.2. Relación de aspecto de pantalla

While there is no restriction to the screen aspect ratio value of the physical screen display, the screen aspect ratio of the logical display that third-party apps are rendered within, as can be derived from the height and width values reported through the view.Display APIs and Configuration API, MUST meet the following requirements:

• [C-0-1] Device implementations with the Configuration.uiMode set as UI_MODE_TYPE_NORMAL MUST have an aspect ratio value between 1.3333 (4:3) and 1.86 (roughly 16:9), unless the app can be deemed as ready to be stretched longer by meeting one of the following conditions:

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

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

7.1.1.3. Densidad de la pantalla

El marco de la interfaz de usuario de Android define un conjunto de densidades lógicas estándar para ayudar a los desarrolladores de aplicaciones a dirigir los recursos de aplicaciones.

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

  • 120 ppp (ldpi)
  • 160 ppp (mppp)
  • 213 ppp (TV ppp)
  • 240 ppp (alta resolución)
  • 260 dpi (260dpi)
  • 280 ppp (280 ppp)
  • 300 dpi (300dpi)
  • 320 ppp (xhdpi)
  • 340 dpi (340dpi)
  • 360 ppp (360 ppp)
  • 400 ppp (400 ppp)
  • 420 ppp (420 ppp)
  • 480 ppp (xxhdpi)
  • 560 ppp (560 ppp)
  • 640 ppp (xxxhdpi)

• Las implementaciones de dispositivos deben definir la densidad de marco de Android estándar que está numéricamente más cercana a la densidad física de la pantalla, a menos que esa densidad lógica empuje el tamaño de la pantalla informado por debajo del mínimo admitido. Si la densidad de marco de Android estándar que está numéricamente más cercana a la densidad física da como resultado un tamaño de pantalla que es más pequeño que el tamaño de pantalla compatible más pequeño compatible (ancho de 320 dp), las implementaciones del dispositivo deben informar la siguiente densidad de marco de Android más baja.

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

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

7.1.2. Mostrar métricas

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

• [C-1-1] MUST report correct values for all 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 reasonable values for all display metrics defined in the android.util.DisplayMetrics API for the emulated default view.Display .

7.1.3. Orientación de la pantalla

Implementaciones 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. Es decir, el dispositivo debe respetar la solicitud de la aplicación de una orientación de pantalla específica.
• [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. Aceleración de gráficos 2D y 3D

7.1.4.1 OpenGL ES

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

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

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

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

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

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

• [C-3-1] MUST export the corresponding function symbols for these version in addition to the OpenGL ES 2.0 function symbols in the libGLESv2.so library.

If device implementations support OpenGL ES 3.2, they:

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

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

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

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

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

7.1.4.2 Vulkan

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

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

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

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

• SHOULD include support for Vulkan 1.0.

Device implementations, if including support for Vulkan 1.0:

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

Device implementations, if not including support for Vulkan 1.0:

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

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.

Implementaciones 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 incluye un objeto TextureView que permite a los desarrolladores integrar directamente las texturas de OpenGL con aceleración de hardware como objetivos de representación en una jerarquía de UI.

Implementaciones 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 NTSC 1953 in CIE 1931 xyY space.
• [C-1-4] MUST support OpenGL ES 3.0, 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_colorspace_scrgb_linear , and EGL_GL_colorspace_display_p3 extensions.
• [SR] Are STRONGLY RECOMMENDED to support GL_EXT_sRGB .

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

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

7.1.5. Modo de compatibilidad de aplicaciones heredadas

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. Tecnología de pantalla

La plataforma Android incluye API que permiten que las aplicaciones generen gráficos ricos en la pantalla. Los dispositivos deben admitir todas estas API definidas por el SDK de Android a menos que se permita específicamente en este documento.

Implementaciones de dispositivos:

• [C-0-1] MUST support displays capable of rendering 16-bit color graphics.
• SHOULD support displays capable of 24-bit color graphics.
• [C-0-2] MUST support displays capable of rendering animations.
• [C-0-3] MUST use the display technology that have a pixel aspect ratio (PAR) between 0.9 and 1.15. Es decir, la relación de aspecto del píxel debe estar cerca de la cuadrada (1.0) con una tolerancia al 10 ~ 15%.

7.1.7. Pantallas secundarias

Android incluye soporte para la pantalla secundaria para habilitar las capacidades de intercambio de medios y las API de desarrollador para acceder a pantallas externas.

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. Los dispositivos de entrada

Implementaciones 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 preloaded software keyboard.

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

7.2.2. Navegación no táctil

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

Implementaciones 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. La implementación de código abierto de Android Upstream incluye un mecanismo de selección adecuado para su uso con dispositivos que carecen de entradas de navegación no táctiles.

7.2.3. Teclas de navegación

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:

• [C-0-1] MUST provide the Home function.
• 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 indicación.

Implementaciones de dispositivos:

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

If device implementations provide the Menu function, they:

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

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. [SR] STRONGLY RECOMMENDED to use long press on HOME function as this designated interaction.

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

• [C-5-1] Navigation keys MUST use a distinct portion of the screen, not available to applications, and MUST NOT obscure or otherwise interfere with the portion of the screen available to applications.
• [C-5-2] MUST make available a portion of the display to applications that meets the requirements defined in section 7.1.1 .
• [C-5-3] MUST honor the flags set by the app through the View.setSystemUiVisibility() API method, so that this distinct portion of the screen (aka the navigation bar) is properly hidden away as documented in the SDK.

7.2.4. Entrada de pantalla táctil

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. Dado que el usuario toca directamente la pantalla, el sistema no requiere ninguna posibilidad adicional para indicar los objetos que se manipulan.

Implementaciones 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), they:

• [C-1-1] MUST report TOUCHSCREEN_FINGER for the Configuration.touchscreen API field.
• [C-1-2] MUST report the android.hardware.touchscreen and android.hardware.faketouch feature flags

If device implementations include a touchscreen that can track more than a single touch, they:

• [C-2-1] MUST report the appropriate feature flags android.hardware.touchscreen.multitouch , android.hardware.touchscreen.multitouch.distinct , android.hardware.touchscreen.multitouch.jazzhand corresponding to the type of the specific touchscreen on the dispositivo.

If device implementations do not include a touchscreen (and rely on a pointer device only) and meet the fake touch requirements in section 7.2.5 , they:

• [C-3-1] MUST NOT report any feature flag starting with android.hardware.touchscreen and MUST report only android.hardware.faketouch .

7.2.5. Entrada táctil falsa

Fake touch interface provides a user input system that approximates a subset of touchscreen capabilities. Por ejemplo, un control remoto o mouse que impulsa un cursor en pantalla se aproxima al tacto, pero requiere que el usuario apunte o se concentre y luego haga clic. Numerosos dispositivos de entrada como Mouse, TrackPad, Air Mouse, Gyro-Pointer, Gyro-Pointer, Joystick y Multi-Touch Trackpad pueden soportar interacciones táctiles falsas. Android includes the feature constant android.hardware.faketouch, which corresponds to a high-fidelity non-touch (pointer-based) input device such as a mouse or trackpad that can adequately emulate touch-based input (including basic gesture support), and indicates that the device supports an emulated subset of touchscreen functionality.

If device implementations do not include a touchscreen but include another pointer input system which they want to make available, they:

• SHOULD declare support for the android.hardware.faketouch feature flag.

If device implementations declare support for android.hardware.faketouch , they:

• [C-1-1] MUST report the absolute X and Y screen positions of the pointer location and display a visual pointer on the screen.
• [C-1-2] MUST report touch event with the action code that specifies the state change that occurs on the pointer going down or up on the screen .
• [C-1-3] MUST support pointer down and up on an object on the screen, which allows users to emulate tap on an object on the screen.
• [C-1-4] MUST support pointer down, pointer up, pointer down then pointer up in the same place on an object on the screen within a time threshold, which allows users to emulate double tap on an object on the screen.
• [C-1-5] MUST support pointer down on an arbitrary point on the screen, pointer move to any other arbitrary point on the screen, followed by a pointer up, which allows users to emulate a touch drag.
• [C-1-6] MUST support pointer down then allow users to quickly move the object to a different position on the screen and then pointer up on the screen, which allows users to fling an object on the screen.
• [C-1-7] MUST report TOUCHSCREEN_NOTOUCH for the Configuration.touchscreen API field.

If device implementations declare support for android.hardware.faketouch.multitouch.distinct , they:

• [C-2-1] MUST declare support for android.hardware.faketouch .
• [C-2-2] MUST support distinct tracking of two or more independent pointer inputs.

If device implementations declare support for android.hardware.faketouch.multitouch.jazzhand , they:

• [C-3-1] MUST declare support for android.hardware.faketouch .
• [C-3-2] MUST support distinct tracking of 5 (tracking a hand of fingers) or more pointer inputs fully independently.

7.2.6. Soporte de controlador de juego

7.2.6.1. Asignaciones de botones

If device implementations declare the android.hardware.gamepad feature flag, they: [C-1-1] MUST have embed a controller or ship with a separate controller in the box, that would provide means to input all the events listed in the below mesas. [C-1-2] MUST be capable to map HID events to it's associated Android view.InputEvent constants as listed in the below tables. La implementación de Android ascendente incluye la implementación para controladores de juegos que satisfacen este requisito.

1 KeyEvent

2 The above HID usages must be declared within a Game pad CA (0x01 0x0005).

3 This usage must have a Logical Minimum of 0, a Logical Maximum of 7, a Physical Minimum of 0, a Physical Maximum of 315, Units in Degrees, and a Report Size of 4. The logical value is defined to be the clockwise rotation away from the vertical axis; for example, a logical value of 0 represents no rotation and the up button being pressed, while a logical value of 1 represents a rotation of 45 degrees and both the up and left keys being pressed.

4 MotionEvent

1 MotionEvent

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

Implementaciones 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 streamed with a minimum required latency of 5 ms + 2 * sample_time when the application processor is active. This delay does not include any filtering delays.
• [C-1-3] MUST report the first sensor sample within 400 milliseconds + 2 * sample_time of the sensor being activated. It is acceptable for this sample to have an accuracy of 0.

• [SR] SHOULD report the event time in nanoseconds as defined in the Android SDK documentation, representing the time the event happened and synchronized with the SystemClock.elapsedRealtimeNano() clock. Existing and new Android devices are STRONGLY RECOMMENDED to meet these requirements so they will be able to upgrade to the future platform releases where this might become a REQUIRED component. The synchronization error SHOULD be below 100 milliseconds.

• [C-1-4] For any API indicated by the Android SDK documentation to be a continuous sensor , device implementations MUST continuously provide periodic data samples that SHOULD have a jitter below 3%, where jitter is defined as the standard deviation of the difference of the reported timestamp values between consecutive events.

• [C-1-5] MUST ensure that the sensor event stream MUST NOT prevent the device CPU from entering a suspend state or waking up from a suspend state.

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

The list above is not comprehensive; the documented behavior of the Android SDK and the Android Open Source Documentations on sensors is to be considered authoritative.

Some sensor types are composite, meaning they can be derived from data provided by one or more other sensors. (Examples include the orientation sensor and the linear acceleration sensor.)

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

7.3.1. Acelerómetro

• Device implementations SHOULD include a 3-axis accelerometer.

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

• [C-1-1] MUST be able to report events up to a frequency of at least 50 Hz.
• [C-1-2] MUST implement and report TYPE_ACCELEROMETER sensor.
• [C-1-3] MUST comply with the Android sensor coordinate system as detailed in the Android APIs.
• [C-1-4] MUST be capable of measuring from freefall up to four times the gravity(4g) or more on any axis.
• [C-1-5] MUST have a resolution of at least 12-bits.
• [C-1-6] MUST have a standard deviation no greater than 0.05 m/s^, where the standard deviation should be calculated on a per axis basis on samples collected over a period of at least 3 seconds at the fastest sampling rate.
• [SR] are STRONGLY RECOMMENDED to implement the TYPE_SIGNIFICANT_MOTION composite sensor.
• [SR] are STRONGLY RECOMMENDED to implement the TYPE_ACCELEROMETER_UNCALIBRATED sensor if online accelerometer calibration is available.
• SHOULD implement the TYPE_SIGNIFICANT_MOTION , TYPE_TILT_DETECTOR , TYPE_STEP_DETECTOR , TYPE_STEP_COUNTER composite sensors as described in the Android SDK document.
• SHOULD report events up to at least 200 Hz.
• SHOULD have a resolution of at least 16-bits.
• SHOULD be calibrated while in use if the characteristics changes over the life cycle and compensated, and preserve the compensation parameters between device reboots.
• SHOULD be temperature compensated.
• SHOULD also implement TYPE_ACCELEROMETER_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-2-1] The sum of their power consumption MUST always be less than 4 mW.
• SHOULD each be below 2 mW and 0.5 mW for when the device is in a dynamic or static condition.

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

• [C-3-1] MUST implement the TYPE_GRAVITY and TYPE_LINEAR_ACCELERATION composite sensors.
• SHOULD implement the TYPE_GAME_ROTATION_VECTOR composite sensor.
• [SR] Existing and new Android devices are STRONGLY RECOMMENDED to implement the TYPE_GAME_ROTATION_VECTOR sensor.

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

• [C-4-1] MUST implement a TYPE_ROTATION_VECTOR composite sensor.

7.3.2. Magnetómetro

• Device implementations SHOULD include a 3-axis magnetometer (compass).

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

• [C-1-1] MUST implement the TYPE_MAGNETIC_FIELD sensor.
• [C-1-2] MUST be able to report events up to a frequency of at least 10 Hz and SHOULD report events up to at least 50 Hz.
• [C-1-3] MUST comply with the Android sensor coordinate system as detailed in the Android APIs.
• [C-1-4] MUST be capable of measuring between -900 µT and +900 µT on each axis before saturating.
• [C-1-5] MUST have a hard iron offset value less than 700 µT and SHOULD have a value below 200 µT, by placing the magnetometer far from dynamic (current-induced) and static (magnet-induced) magnetic fields.
• [C-1-6] MUST have a resolution equal or denser than 0.6 µT.
• [C-1-7] MUST support online calibration and compensation of the hard iron bias, and preserve the compensation parameters between device reboots.
• [C-1-8] MUST have the soft iron compensation applied—the calibration can be done either while in use or during the production of the device.
• [C-1-9] MUST have a standard deviation, calculated on a per axis basis on samples collected over a period of at least 3 seconds at the fastest sampling rate, no greater than 1.5 µT; SHOULD have a standard deviation no greater than 0.5 µT.
• SHOULD implement TYPE_MAGNETIC_FIELD_UNCALIBRATED sensor.
• [SR] Existing and new Android devices are STRONGLY RECOMMENDED to implement the TYPE_MAGNETIC_FIELD_UNCALIBRATED sensor.

If device implementations include a 3-axis magnetometer, an accelerometer sensor and a 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

Implementaciones de dispositivos:

• SHOULD 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).
  • [SR] After making such a location calculation, it is STRONGLY RECOMMENDED for the device to be able to determine its location, in open sky, within 10 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.
  • DEBE poder rastrear simultáneamente al menos 24 satélites, de múltiples constelaciones (por ejemplo, GPS + al menos uno de Glonass, Beidou, Galileo).
  • [C-1-5] MUST report the GNSS technology generation through the test API 'getGnssYearOfHardware'.
  • [SR] Continue to deliver normal GPS/GNSS location outputs during an emergency phone call.
  • [SR] Report GNSS measurements from all constellations tracked (as reported in GnssStatus messages), with the exception of SBAS.
  • [SR] Report AGC, and Frequency of GNSS measurement.
  • [SR] Report all accuracy estimates (including Bearing, Speed, and Vertical) as part of each GPS Location.
  • [SR] are STRONGLY RECOMMENDED to meet as many as possible from the additional mandatory requirements for devices reporting the year "2016" or "2017" through the Test API LocationManager.getGnssYearOfHardware() .

If device implementations include a GPS/GNSS receiver and report the capability to applications through the android.hardware.location.gps feature flag and the LocationManager.getGnssYearOfHardware() Test API reports the year "2016" or newer, they:

• [C-2-1] MUST report GPS measurements, as soon as they are found, even if a location calculated from GPS/GNSS is not yet reported.
• [C-2-2] MUST report GPS pseudoranges and pseudorange rates, that, in open-sky conditions after determining the location, while stationary or moving with less than 0.2 meter per second squared of acceleration, are sufficient to calculate position within 20 meters, and speed within 0.2 meters per second, at least 95% of the time.

If device implementations include a GPS/GNSS receiver and report the capability to applications through the android.hardware.location.gps feature flag and the LocationManager.getGnssYearOfHardware() Test API reports the year "2017" or newer, they:

• [C-3-1] MUST continue to deliver normal GPS/GNSS location outputs during an emergency phone call.
• [C-3-2] MUST report GNSS measurements from all constellations tracked (as reported in GnssStatus messages), with the exception of SBAS.
• [C-3-3] MUST report AGC, and Frequency of GNSS measurement.
• [C-3-4] MUST report all accuracy estimates (including Bearing, Speed, and Vertical) as part of each GPS Location.

7.3.4. Giroscopio

Implementaciones de dispositivos:

• SHOULD include a gyroscope (angular change sensor).
• SHOULD NOT include a gyroscope sensor unless a 3-axis accelerometer is also included.

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-2] MUST implement the TYPE_GYROSCOPE sensor and SHOULD also implement TYPE_GYROSCOPE_UNCALIBRATED sensor.
• [C-1-3] MUST be capable of measuring orientation changes up to 1,000 degrees per second.
• [C-1-4] MUST have a resolution of 12-bits or more and SHOULD have a resolution of 16-bits or more.
• [C-1-5] MUST be temperature compensated.
• [C-1-6] MUST be calibrated and compensated while in use, and preserve the compensation parameters between device reboots.
• [C-1-7] MUST have a variance no greater than 1e-7 rad^2 / s^2 per Hz (variance per Hz, or rad^2 / s). The variance is allowed to vary with the sampling rate, but MUST be constrained by this value. In other words, if you measure the variance of the gyro at 1 Hz sampling rate it SHOULD be no greater than 1e-7 rad^2/s^2.
• [SR] Existing and new Android devices are STRONGLY RECOMMENDED to implement the SENSOR_TYPE_GYROSCOPE_UNCALIBRATED sensor.
• [SR] Calibration error is STRONGLY RECOMMENDED to be less than 0.01 rad/s when device is stationary at room temperature.
• SHOULD report events up to at least 200 Hz.

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

• [C-2-1] MUST implement a TYPE_ROTATION_VECTOR composite sensor.

If device implementations include a gyroscope and a accelerometer sensor, they:

• [C-3-1] MUST implement the TYPE_GRAVITY and TYPE_LINEAR_ACCELERATION composite sensors.
• [SR] Existing and new Android devices are STRONGLY RECOMMENDED to implement the TYPE_GAME_ROTATION_VECTOR sensor.
• SHOULD implement the TYPE_GAME_ROTATION_VECTOR composite sensor.

7.3.5. Barómetro

• Device implementations SHOULD include a barometer (ambient air pressure sensor).

If device implementations include a barometer, they:

• [C-1-1] MUST implement and report TYPE_PRESSURE sensor.
• [C-1-2] MUST be able to deliver events at 5 Hz or greater.
• [C-1-3] MUST be temperature compensated.
• [SR] STRONGLY RECOMMENDED to be able to report pressure measurements in the range 300hPa to 1100hPa.
• SHOULD have an absolute accuracy of 1hPa.
• SHOULD have a relative accuracy of 0.12hPa over 20hPa range (equivalent to ~1m accuracy over ~200m change at sea level).

7.3.6. Termómetro

Device implementations: MAY include an ambient thermometer (temperature sensor). MAY but SHOULD NOT include a CPU temperature sensor.

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

• [C-1-1] MUST be defined as SENSOR_TYPE_AMBIENT_TEMPERATURE and MUST measure the ambient (room/vehicle cabin) temperature from where the user is interacting with the device in degrees Celsius.
• [C-1-2] MUST be defined as SENSOR_TYPE_TEMPERATURE .
• [C-1-3] MUST measure the temperature of the device CPU.
• [C-1-4] MUST NOT measure any other temperature.

Note the SENSOR_TYPE_TEMPERATURE sensor type was deprecated in Android 4.0.

7.3.7. Fotómetro

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

7.3.8. Sensor de proximidad

• Device implementations MAY include a proximity sensor.

If device implementations include a proximity sensor, they:

• [C-1-1] MUST measure the proximity of an object in the same direction as the screen. That is, the proximity sensor MUST be oriented to detect objects close to the screen, as the primary intent of this sensor type is to detect a phone in use by the user. If device implementations include a proximity sensor with any other orientation, it MUST NOT be accessible through this API.
• [C-1-2] MUST have 1-bit of accuracy or more.

7.3.9. Sensores de alta fidelidad

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.
  • MUST have a measurement resolution of at least 1024 LSB/G.
  • MUST have a minimum measurement frequency of 12.5 Hz or lower.
  • MUST have a maximum measurement frequency of 400 Hz or higher.
  • MUST have a measurement noise not above 400 uG/√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.
  • SHOULD have a stationary noise bias stability of \<15 μg √Hz from 24hr static dataset.
  • SHOULD have a bias change vs. temperature of ≤ +/- 1mg / °C.
  • SHOULD have a best-fit line non-linearity of ≤ 0.5%, and sensitivity change vs. temperature of ≤ 0.03%/C°.
  • SHOULD have white noise spectrum to ensure adequate qualification of sensor's noise integrity.

• [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.
  • MUST have a measurement noise not above 0.014°/s/√Hz.
  • SHOULD have a stationary bias stability of < 0.0002 °/s √Hz from 24-hour static dataset.
  • 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 white noise spectrum to ensure adequate qualification of sensor's noise integrity.
  • SHOULD have calibration error less than 0.002 rad/s in temperature range 10 ~ 40 ℃ when device is stationary.

• [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 uT.
  • MUST have a measurement resolution of at least 5 LSB/uT.
  • MUST have a minimum measurement frequency of 5 Hz or lower.
  • MUST have a 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.
  • SHOULD have white noise spectrum to ensure adequate qualification of sensor's noise integrity.
• [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 which:
  • MUST implement a non-wake-up form of this sensor with a buffering capability of at least 300 sensor events.
  • MUST have a batching power consumption not worse than 4 mW.
• [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 sensor and Magnetometer MUST be within 2.5 milliseconds of each other.
• [C-2-14] MUST have Gyroscope sensor event timestamps on the same time base as the camera subsystem and within 1 milliseconds of error.
• [C-2-15] MUST deliver samples to applications within 5 milliseconds from the time when the data is available on any of the above physical sensors to the application.
• [C-2-16] MUST not have a power consumption higher than 0.5 mW when device is static and 2.0 mW when device is moving when any combination of the following sensors are enabled:
  • SENSOR_TYPE_SIGNIFICANT_MOTION
  • SENSOR_TYPE_STEP_DETECTOR
  • SENSOR_TYPE_STEP_COUNTER
  • SENSOR_TILT_DETECTORS
• [C-2-17] MAY have a TYPE_PROXIMITY sensor, but if present MUST have a minimum buffer capability of 100 sensor events.

Note that all power consumption requirements in this section do not include the power consumption of the Application Processor. It is inclusive of the power drawn by the entire sensor chain—the sensor, any supporting circuitry, any dedicated sensor processing system, etc.

If device implementations include direct sensor support, they:

• [C-3-1] MUST correctly declare support of direct channel types and direct report rates level through the isDirectChannelTypeSupported and getHighestDirectReportRateLevel API.
• [C-3-2] MUST support at least one of the two sensor direct channel types for all sensors that declare support for sensor direct channel
• TYPE_HARDWARE_BUFFER
• TYPE_MEMORY_FILE
• SHOULD support event reporting through sensor direct channel for primary sensor (non-wakeup variant) of the following types:
• TYPE_ACCELEROMETER
• TYPE_ACCELEROMETER_UNCALIBRATED
• TYPE_GYROSCOPE
• TYPE_GYROSCOPE_UNCALIBRATED
• TYPE_MAGNETIC_FIELD
• TYPE_MAGNETIC_FIELD_UNCALIBRATED

7.3.10. Sensor de huellas dactilares

If device implementations include a secure lock screen, they:

• SHOULD include a fingerprint sensor.

If device implementations include a fingerprint sensor and make the sensor available to third-party apps, they:

• [C-1-1] MUST declare support for the android.hardware.fingerprint feature.
• [C-1-2] MUST fully implement the corresponding API as described in the Android SDK documentation.
• [C-1-3] MUST have a false acceptance rate not higher than 0.002%.
• [C-1-4] MUST rate limit attempts for at least 30 seconds after five false trials for fingerprint verification.
• [C-1-5] MUST have a hardware-backed keystore implementation, and perform the fingerprint matching in a Trusted Execution Environment (TEE) or on a chip with a secure channel to the TEE.
• [C-1-6] MUST have all identifiable fingerprint data encrypted and cryptographically authenticated such that they cannot be acquired, read or altered outside of the Trusted Execution Environment (TEE) as documented in the implementation guidelines on the Android Open Source Project site.
• [C-1-7] MUST prevent adding a fingerprint without first establishing a chain of trust by having the user confirm existing or add a new device credential (PIN/pattern/password) that's secured by TEE; the Android Open Source Project implementation provides the mechanism in the framework to do so.
• [C-1-8] MUST NOT enable 3rd-party applications to distinguish between individual fingerprints.
• [C-1-9] MUST honor the DevicePolicyManager.KEYGUARD_DISABLE_FINGERPRINT flag.
• [C-1-10] MUST, when upgraded from a version earlier than Android 6.0, have the fingerprint data securely migrated to meet the above requirements or removed.
• [SR] STRONGLY RECOMMENDED to have a false rejection rate of less than 10%, as measured on the device.
• [SR] STRONGLY RECOMMENDED to have a latency below 1 second, measured from when the fingerprint sensor is touched until the screen is unlocked, for one enrolled finger.
• SHOULD use the Android Fingerprint icon provided in the Android Open Source Project.

7.3.11. Sensores exclusivos de Android Automotive

Automotive-specific sensors are defined in the android.car.CarSensorManager API .

7.3.11.1. Equipo actual

See Section 2.5.1 for device-specific requirements.

7.3.11.2. Modo día noche

See Section 2.5.1 for device-specific requirements.

7.3.11.3. Estado de conducción

See Section 2.5.1 for device-specific requirements.

7.3.11.4. Velocidad de la rueda

See Section 2.5.1 for device-specific requirements.

7.3.12. Sensor de postura

Implementaciones 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.4. Conectividad de datos

7.4.1. Telefonía

“Telephony” as used by the Android APIs and this document refers specifically to hardware related to placing voice calls and sending SMS messages via a GSM or CDMA network. While these voice calls may or may not be packet-switched, they are for the purposes of Android considered independent of any data connectivity that may be implemented using the same network. In other words, the Android “telephony” functionality and APIs refer specifically to voice calls and SMS. For instance, device implementations that cannot place calls or send/receive SMS messages are not considered a telephony device, regardless of whether they use a cellular network for data connectivity.

• Android MAY be used on devices that do not include telephony hardware. That is, Android is compatible with devices that are not phones.

If device implementations include GSM or CDMA telephony, they:

• [C-1-1] MUST declare the android.hardware.telephony feature flag and other sub-feature flags according to the technology.
• [C-1-2] MUST implement full support for the API for that technology.

If device implementations do not include telephony hardware, they:

• [C-2-1] MUST implement the full APIs as no-ops.

7.4.1.1. Compatibilidad con bloqueo de números

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

• [C-1-1] MUST include number blocking support
• [C-1-2] MUST fully implement BlockedNumberContract and the corresponding API as described in the SDK documentation.
• [C-1-3] MUST block all calls and messages from a phone number in 'BlockedNumberProvider' without any interaction with apps. The only exception is when number blocking is temporarily lifted as described in the SDK documentation.
• [C-1-4] MUST NOT write to the platform call log provider for a blocked call.
• [C-1-5] MUST NOT write to the Telephony provider for a blocked message.
• [C-1-6] MUST implement a blocked numbers management UI, which is opened with the intent returned by TelecomManager.createManageBlockedNumbersIntent() method.
• [C-1-7] MUST NOT allow secondary users to view or edit the blocked numbers on the device as the Android platform assumes the primary user to have full control of the telephony services, a single instance, on the device. All blocking related UI MUST be hidden for secondary users and the blocked list MUST still be respected.
• SHOULD migrate the blocked numbers into the provider when a device updates to Android 7.0.

7.4.2. IEEE 802.11 (Wi-Fi)

Implementaciones 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 Andr:oid API.
• [C-1-2] MUST report the hardware feature flag android.hardware.wifi .
• [C-1-3] MUST implement the multicast API as described in the SDK documentation.
• [C-1-4] MUST support multicast DNS (mDNS) and MUST NOT filter mDNS packets (224.0.0.251) at any time of operation including:
  • Even when the screen is not in an active state.
  • For Android Television device implementations, even when in standby power states.
• SHOULD randomize the source MAC address and sequence number of probe request frames, once at the beginning of each scan, while STA is disconnected.
  • Each group of probe request frames comprising one scan should use one consistent MAC address (SHOULD NOT randomize MAC address halfway through a scan).
  • Probe request sequence number should iterate as normal (sequentially) between the probe requests in a scan
  • Probe request sequence number should randomize between the last probe request of a scan and the first probe request of the next scan
• SHOULD only allow the following information elements in probe request frames, while STA is disconnected:
  • SSID Parameter Set (0)
  • DS Parameter Set (3)

7.4.2.1. Wi-Fi directo

Implementaciones 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.
• SHOULD support Wi-Fi and Wi-Fi Direct operations concurrently.

7.4.2.2. Configuración de enlace directo con túnel Wi-Fi

Implementaciones 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

Implementaciones 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 then 30 minutes and whenever Wi-Fi Aware is enabled.

7.4.2.4. Punto de acceso Wi-Fi

Implementaciones de dispositivos:

• SHOULD include support for Wi-Fi Passpoint .

If device implementations include support for Wi-Fi Passpoint, they:

• [C-1-1] MUST implement the Passpoint related WifiManager APIs as described in the SDK documentation .
• [C-1-2] MUST support IEEE 802.11u standard, specifically related to Network Discovery and Selection, such as Generic Advertisement Service (GAS) and Access Network Query Protocol (ANQP).

Conversely if device implementations do not include support for Wi-Fi Passpoint:

• [C-2-1] The implementation of the Passpoint related WifiManager APIs MUST throw an UnsupportedOperationException .

7.4.3. Bluetooth

If device implementations support Bluetooth Audio profile, they:

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

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, AVCP, OBEX, etc. as appropriate for the device.

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

• [C-3-1] MUST declare the hardware feature android.hardware.bluetooth_le .
• [C-3-2] MUST enable the GATT (generic attribute profile) based Bluetooth APIs as described in the SDK documentation and android.bluetooth .
• [C-3-3] MUST report the correct value for BluetoothAdapter.isOffloadedFilteringSupported() to indicate whether the filtering logic for the ScanFilter API classes is implemented.
• [C-3-4] MUST report the correct value for BluetoothAdapter.isMultipleAdvertisementSupported() to indicate whether Low Energy Advertising is supported.
• SHOULD support offloading of the filtering logic to the bluetooth chipset when implementing the ScanFilter API .
• SHOULD support offloading of the batched scanning to the bluetooth chipset.

• SHOULD support multi advertisement with at least 4 slots.

• [SR] STRONGLY RECOMMENDED to implement a Resolvable Private Address (RPA) timeout no longer than 15 minutes and rotate the address at timeout to protect user privacy.

7.4.4. Comunicaciones de campo cercano

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

• [SR] STRONGLY RECOMMENDED to be capable of reading and writing NDEF messages as well as raw data via the following NFC standards. Note that while the NFC standards are stated as STRONGLY RECOMMENDED, the Compatibility Definition for a future version is planned to change these to MUST. These standards are optional in this version but will be required in future versions. Existing and new devices that run this version of Android are very strongly encouraged to meet these requirements now so they will be able to upgrade to the future platform releases.

• [C-1-3] MUST be capable of transmitting and receiving data via the following peer-to-peer standards and protocols:

  • ISO 18092
  • LLCP 1.2 (defined by the NFC Forum)
  • SDP 1.0 (defined by the NFC Forum)
  • NDEF Push Protocol
  • SNEP 1.0 (defined by the NFC Forum)
• [C-1-4] MUST include support for Android Beam and SHOULD enable Android Beam by default.
• [C-1-5] MUST be able to send and receive using Android Beam, when Android Beam is enabled or another proprietary NFC P2p mode is turned on.
• [C-1-6] MUST implement the SNEP default server. Valid NDEF messages received by the default SNEP server MUST be dispatched to applications using the android.nfc.ACTION_NDEF_DISCOVERED intent. Disabling Android Beam in settings MUST NOT disable dispatch of incoming NDEF message.
• [C-1-7] MUST honor the android.settings.NFCSHARING_SETTINGS intent to show NFC sharing settings .
• [C-1-8] MUST implement the NPP server. Messages received by the NPP server MUST be processed the same way as the SNEP default server.
• [C-1-9] MUST implement a SNEP client and attempt to send outbound P2P NDEF to the default SNEP server when Android Beam is enabled. If no default SNEP server is found then the client MUST attempt to send to an NPP server.
• [C-1-10] MUST allow foreground activities to set the outbound P2P NDEF message using android.nfc.NfcAdapter.setNdefPushMessage , and android.nfc.NfcAdapter.setNdefPushMessageCallback , and android.nfc.NfcAdapter.enableForegroundNdefPush .
• SHOULD use a gesture or on-screen confirmation, such as 'Touch to Beam', before sending outbound P2P NDEF messages.
• [C-1-11] MUST support NFC Connection handover to Bluetooth when the device supports Bluetooth Object Push Profile.
• [C-1-12] MUST support connection handover to Bluetooth when using android.nfc.NfcAdapter.setBeamPushUris , by implementing the “ Connection Handover version 1.2 ” and “ Bluetooth Secure Simple Pairing Using NFC version 1.0 ” specs from the NFC Forum. Such an implementation MUST implement the handover LLCP service with service name “urn:nfc:sn:handover” for exchanging the handover request/select records over NFC, and it MUST use the Bluetooth Object Push Profile for the actual Bluetooth data transfer. For legacy reasons (to remain compatible with Android 4.1 devices), the implementation SHOULD still accept SNEP GET requests for exchanging the handover request/select records over NFC. However an implementation itself SHOULD NOT send SNEP GET requests for performing connection handover.
• [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. Capacidad mínima de red

Implementaciones 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 200Kbit/sec or greater. Examples of technologies that satisfy this requirement include EDGE, HSPA, EV-DO, 802.11g, Ethernet, Bluetooth PAN, etc.
• [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.
• 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.

The required level of IPv6 support depends on the network type, as follows:

If devices implementations support Wi-Fi networks, they:

• [C-1-1] MUST support dual-stack and IPv6-only operation on Wi-Fi.

If device implementations support Ethernet networks, they:

• [C-2-1] MUST support dual-stack operation on Ethernet.

If device implementations support cellular data, they:

• [C-3-1] MUST simultaneously meet these requirements on each network to which it is connected when a device is simultaneously connected to more than one network (eg, Wi-Fi and cellular data), .
• SHOULD support IPv6 operation (IPv6-only and possibly dual-stack) on cellular data.

7.4.6. Configuración de sincronización

Implementaciones 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. Ahorro de datos

If device implementations include a metered connection, they are:

• [SR] STRONGLY RECOMMENDED to provide the data saver mode.

If device implementations provide the data saver mode, they:

• [C-1-1] MUST support all the APIs in the ConnectivityManager class as described in the SDK documentation
• [C-1-2] MUST provide a user interface in the settings, that handles the Settings.ACTION_IGNORE_BACKGROUND_DATA_RESTRICTIONS_SETTINGS intent, allowing users to add applications to or remove applications from the allowlist.

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

• [C-2-1] MUST return the value RESTRICT_BACKGROUND_STATUS_DISABLED for ConnectivityManager.getRestrictBackgroundStatus()
• [C-2-2] MUST NOT broadcast ConnectivityManager.ACTION_RESTRICT_BACKGROUND_CHANGED .
• [C-2-3] MUST have an activity that handles the Settings.ACTION_IGNORE_BACKGROUND_DATA_RESTRICTIONS_SETTINGS intent but MAY implement it as a no-op.

7.5. Cámaras

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

7.5.1. Cámara trasera

A rear-facing camera is a camera located on the side of the device opposite the display; that is, it images scenes on the far side of the device, like a traditional camera.

Implementaciones 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.
• PUEDE incluir un 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 Objeto Camera.Parameters . Tenga en cuenta que esta restricción no se aplica a la aplicación de cámara integrada del sistema del dispositivo, sino solo a aplicaciones de terceros que utilizan Camera.PreviewCallback .

7.5.2. Cámara frontal

A front-facing camera is a camera located on the same side of the device as the display; that is, a camera typically used to image the user, such as for video conferencing and similar applications.

Implementaciones 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 en el 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. Cámara externa

Implementaciones 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 port.
• 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. Comportamiento de la API de la cámara

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

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

Device implementations MUST implement the following behaviors for the camera-related APIs, for all available cameras. Implementaciones 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 .
• [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 on the android.hardware.Camera.Parameters 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 . Es decir, las implementaciones del dispositivo deben admitir todos los parámetros de cámara estándar si el hardware lo permite, y no debe admitir tipos de parámetros de cámara personalizados. 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.

7.5.5. Orientación de la cámara

If device implementations have a front- or a rear-facing camera, such camera(s):

• [C-1-1] MUST be oriented so that the long dimension of the camera aligns with the screen's long dimension. That is, when the device is held in the landscape orientation, cameras MUST capture images in the landscape orientation. This applies regardless of the device's natural orientation; that is, it applies to landscape-primary devices as well as portrait-primary devices.

7.6. Memoria y almacenamiento

7.6.1. Memoria y almacenamiento mínimos

Implementaciones 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. Aplicación Almacenamiento compartido

Implementaciones 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 enforce the android.permission.WRITE_EXTERNAL_STORAGE permission on this shared storage as documented in the SDK. El almacenamiento compartido debe ser redactado por cualquier aplicación que obtenga ese permiso.

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 protion of the non-removable storage to satisfy the above requirements, they:

• SHOULD use the AOSP implementation of the internal application shared storage.
• MAY share the storage space with the application private data.

If device implementations include multiple shared storage paths (such as both an SD card slot and shared internal storage), they:

• [C-2-1] MUST allow only pre-installed and privileged Android applications with the WRITE_EXTERNAL_STORAGE permission to write to the secondary external storage, except when writing to their package-specific directories or within the URI returned by firing the ACTION_OPEN_DOCUMENT_TREE intent.

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. Almacenamiento adoptable

If the device is expected to be mobile in nature unlike Television, device implementations are:

• [SR] STRONGLY RECOMMENDED to implement the adoptable storage in a long-term stable location, since accidentally disconnecting them can cause data loss/corruption.

If the removable storage device port is in a long-term stable location, such as within the battery compartment or other protective cover, device implementations are:

• [SR] STRONGLY RECOMMENDED to implement adoptable storage .

7.7. USB

If device implementations have a USB port, they:

• SHOULD support USB peripheral mode and SHOULD support USB host mode.

7.7.1. Modo periférico USB

If device implementations include a USB port supporting peripheral mode:

• [C-1-1] The port MUST be connectable to a USB host that has a standard type-A or type-C USB port.
• [C-1-2] MUST report the correct value of iSerialNumber in USB standard device descriptor through android.os.Build.SERIAL .
• [C-1-3] MUST detect 1.5A and 3.0A chargers per the Type-C resistor standard and MUST detect changes in the advertisement if they support Type-C USB.
• [SR] The port SHOULD use micro-B, micro-AB or Type-C USB form factor. Existing and new Android devices are STRONGLY RECOMMENDED to meet these requirements so they will be able to upgrade to the future platform releases.
• [SR] The port SHOULD be located on the bottom of the device (according to natural orientation) or enable software screen rotation for all apps (including home screen), so that the display draws correctly when the device is oriented with the port at bottom . Existing and new Android devices are STRONGLY RECOMMENDED to meet these requirements so they will be able to upgrade to future platform releases.
• [SR] SHOULD implement support to draw 1.5 A current during HS chirp and traffic as specified in the USB Battery Charging specification, revision 1.2 . Existing and new Android devices are STRONGLY RECOMMENDED to meet these requirements so they will be able to upgrade to the future platform releases.
• [SR] STRONGLY RECOMMENDED to not support proprietary charging methods that modify Vbus voltage beyond default levels, or alter sink/source roles as such may result in interoperability issues with the chargers or devices that support the standard USB Power Delivery methods. While this is called out as "STRONGLY RECOMMENDED", in future Android versions we might REQUIRE all type-C devices to support full interoperability with standard type-C chargers.
• [SR] STRONGLY RECOMMENDED to support Power Delivery for data and power role swapping when they support Type-C USB and USB host mode.
• SHOULD support Power Delivery for high-voltage charging and support for Alternate Modes such as display out.
• SHOULD implement the Android Open Accessory (AOA) API and specification as documented in the Android SDK documentation.

If device implementations including a USB port, 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. Modo de host USB

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).
• [SR] STRONGLY RECOMMENDED to implement the USB audio class as documented in the Android SDK documentation.
• SHOULD support charging the connected USB peripheral device while in host mode; advertising a source current of at least 1.5A as specified in the Termination Parameters section of the USB Type-C Cable and Connector Specification Revision 1.2 for USB Type-C connectors or using Charging Downstream Port(CDP) output current range as specified in the USB Battery Charging specifications, revision 1.2 for Micro-AB connectors.
• SHOULD implement and support USB Type-C standards.

If device implementations include a USB port supporting host mode and the USB audio class, they:

• [C-2-1] MUST support the USB HID class .
• [C-2-2] MUST support the detection and mapping of the following HID data fields specified in the USB HID Usage Tables and the Voice Command Usage Request to the KeyEvent constants as below:
  • Usage Page (0xC) Usage ID (0x0CD): KEYCODE_MEDIA_PLAY_PAUSE
  • Usage Page (0xC) Usage ID (0x0E9): KEYCODE_VOLUME_UP
  • Usage Page (0xC) Usage ID (0x0EA): KEYCODE_VOLUME_DOWN
  • Usage Page (0xC) Usage ID (0x0CF): KEYCODE_VOICE_ASSIST

If device implementations include a USB port supporting host mode and the Storage Access Framework (SAF), they:

• [C-3-1] MUST recognize any remotely connected MTP (Media Transfer Protocol) devices and make their contents accessible through the ACTION_GET_CONTENT , ACTION_OPEN_DOCUMENT , and ACTION_CREATE_DOCUMENT intents. .

If device implementations include a USB port supporting host mode and USB Type-C, they:

• [C-4-1] MUST implement Dual Role Port functionality as defined by the USB Type-C specification (section 4.5.1.3.3).
• [SR] STRONGLY RECOMMENDED to support DisplayPort, SHOULD support USB SuperSpeed Data Rates, and are STRONGLY RECOMMENDED to support Power Delivery for data and power role swapping.
• [SR] STRONGLY RECOMMENDED to NOT support Audio Adapter Accessory Mode as described in the Appendix A of the USB Type-C Cable and Connector Specification Revision 1.2 .
• SHOULD implement the Try.* model that is most appropriate for the device form factor. For example a handheld device SHOULD implement the Try.SNK model.

7.8. Audio

7.8.1. Micrófono

If device implementations include a microphone, they:

• [C-1-1] MUST report the android.hardware.microphone feature constant.
• [C-1-2] MUST meet the audio recording requirements in section 5.4 .
• [C-1-3] MUST meet the audio latency requirements in section 5.6 .
• [SR] Are STRONGLY RECOMMENDED to support near-ultrasound recording as described in section 7.8.3 .

If device implementations omit a microphone, they:

• [C-2-1] MUST NOT report the android.hardware.microphone feature constant.
• [C-2-2] MUST implement the audio recording API at least as no-ops, per section 7 .

7.8.2. Salida de audio

If device implementations include a speaker or an audio/multimedia output port for an audio output peripheral such as a 4 conductor 3.5mm audio jack or USB host mode port using USB audio class , they:

• [C-1-1] MUST report the android.hardware.audio.output feature constant.
• [C-1-2] MUST meet the audio playback requirements in section 5.5 .
• [C-1-3] MUST meet the audio latency requirements in section 5.6 .
• [SR] STRONGLY RECOMMENDED to support near-ultrasound playback as described in section 7.8.3 .

If device implementations do not include a speaker or audio output port, they:

• [C-2-1] MUST NOT report the android.hardware.audio output feature.
• [C-2-2] MUST implement the Audio Output related APIs as no-ops at least.

For the purposes of this section, an "output port" is a physical interface such as a 3.5mm audio jack, HDMI, or USB host mode port with USB audio class. Support for audio output over radio-based protocols such as Bluetooth, WiFi, or cellular network does not qualify as including an "output port".

7.8.2.1. Puertos de audio analógico

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

If 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.
• [SR] STRONGLY RECOMMENDED to 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
• SHOULD support audio plugs with the OMTP pin-out order.
• SHOULD 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.3. Ultrasonido cercano

Near-Ultrasound audio is the 18.5 kHz to 20 kHz band.

Implementaciones 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.9. Realidad 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. Modo de realidad virtual

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. Realidad virtual de alto rendimiento

If device implementations identify the support of high performance VR for longer user periods through the android.hardware.vr.high_performance feature flag, they:

• [C-1-1] MUST have at least 2 physical cores.
• [C-1-2] MUST declare android.software.vr.mode feature .
• [C-1-3] MUST support sustained performance mode.
• [C-1-4] MUST support OpenGL ES 3.2.
• [C-1-5] MUST support Vulkan Hardware Level 0 and SHOULD support Vulkan Hardware Level 1.
• [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 , and expose the extensions in the list of available EGL extensions.
• [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-8] MUST implement GL_EXT_multisampled_render_to_texture , GL_OVR_multiview , GL_OVR_multiview2 , GL_OVR_multiview_multisampled_render_to_texture , GL_EXT_protected_textures , and expose the extensions in the list of available GL extensions.
• [C-1-9] MUST implement support for AHardwareBuffer flags AHARDWAREBUFFER_USAGE_GPU_DATA_BUFFER and AHARDWAREBUFFER_USAGE_SENSOR_DIRECT_DATA as described in the NDK.
• [C-1-10] MUST implement support for AHardwareBuffers with more than one layer.
• [C-1-11] MUST support H.264 decoding at least 3840x2160@30fps-40Mbps (equivalent to 4 instances of 1920x1080@30fps-10Mbps or 2 instances of 1920x1080@60fps-20Mbps).
• [C-1-12] MUST support HEVC and VP9, MUST be capable to decode at least 1920x1080@30fps-10Mbps and SHOULD be capable to decode 3840x2160@30fps-20Mbps (equivalent to 4 instances of 1920x1080@30fps-5Mbps).
• [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 be FullHD(1080p) and STRONGLY RECOMMENDED TO BE be QuadHD (1440p) or higher.
• [C-1-15] The display MUST update at least 60 Hz while in VR Mode.
• [C-1-16] The display latency on Gray-to-Gray, White-to-Black, and Black-to-White switching time MUST be ≤ 3 ms.
• [C-1-17] The display MUST support a low-persistence mode with ≤5 ms 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 .
• [SR] STRONGLY RECOMMENDED to support android.hardware.sensor.hifi_sensors feature and MUST meet the gyroscope, accelerometer, and magnetometer related requirements for android.hardware.hifi_sensors .
• MAY provide an exclusive core to the foreground application and MAY support the Process.getExclusiveCores API to return the numbers of the cpu cores that are exclusive to the top foreground application.

If exclusive core is supported, then the core:

• [C-2-1] MUST not allow any other userspace processes to run on it (except device drivers used by the application), but MAY allow some kernel processes to run as necessary.

8. Rendimiento y potencia

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. Coherencia de la experiencia del usuario

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. Rendimiento del acceso a E/S de archivos

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. Modos de ahorro de energía

Android includes App Standby and Doze power-saving modes to optimize battery usage. [SR] All Apps exempted from these modes are STRONGLY RECOMMENDED to be made visible to the end user. [SR] The triggering, maintenance, wakeup algorithms and the use of global system settings of these power-saving modes are STRONGLY RECOMMENDED NOT to deviate from the Android Open Source Project.

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 implements S3 and S4 power states as defined by the ACPI, they:

• [C-1-1] MUST only enter these states when closing a lid that is physically part of the device.

8.4. Contabilidad del consumo de energía

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.

Implementaciones de dispositivos:

• [SR] STRONGLY RECOMMENDED to provide a per-component power profile that defines the current consumption value for each hardware component and the approximate battery drain caused by the components over time as documented in the Android Open Source Project site.
• [SR] STRONGLY RECOMMENDED to report all power consumption values in milliampere hours (mAh).
• [SR] STRONGLY RECOMMENDED to report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the uid_cputime kernel module implementation.
• [SR] STRONGLY RECOMMENDED to make this power usage available via the adb shell dumpsys batterystats shell command to the app developer.
• SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application.

8.5. Rendimiento consistente

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.

Implementaciones 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. Compatibilidad del modelo de seguridad

Implementaciones 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. Specifically, compatible devices MUST support the security mechanisms described in the follow subsections.

9.1. Permisos

Implementaciones de dispositivos:

• [C-0-1] MUST support the Android permissions model as defined in the Android developer documentation. Specifically, they MUST enforce each permission defined as described in the SDK documentation; No se pueden omitir, alterar o ignorar los permisos.

• 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 preloaded in the privileged path(s) of the system image and within the subset of the explicitly allowlisted permissions for each app. The AOSP implementation meets this requirement by reading and honoring the allowlisted permissions for each app from the files in the etc/permissions/ path and using the system/priv-app path as the privileged path.

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

Implementaciones 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-4] MUST have one and only one implementation of both user interfaces.
• [C-0-5] MUST NOT grant any runtime permissions to preinstalled apps unless:
• the user's consent can be obtained before the application uses it
• the runtime permissions are associated with an intent pattern for which the preinstalled application is set as the default handler

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

• [SR] are STRONGLY RECOMMENDED provide user-accessible mechanism to grant or revoke access to the usage stats in response to the android.settings.ACTION_USAGE_ACCESS_SETTINGS intent for apps that declare the android.permission.PACKAGE_USAGE_STATS permission.

If device implementations intend to disallow any apps, including pre-installed apps, from accessing the usage statistics, they:

• [C-1-1] MUST still have an activity that handles the android.settings.ACTION_USAGE_ACCESS_SETTINGS intent pattern but MUST implement it as a no-op, that is to have an equivalent behavior as when the user is declined for access.

9.2. UID y aislamiento de procesos

Implementaciones 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. Permisos del sistema de archivos

Implementaciones de dispositivos:

• [C-0-1] MUST support the Android file access permissions model as defined in the Security and Permissions reference .

9.4. Entornos de ejecución alternativos

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. En otras palabras:

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

• Los tiempos de ejecución alternativos pueden proporcionar una sola caja de arena de Android compartida por todas las aplicaciones utilizando el tiempo de ejecución alternativo.

9.5. Soporte multiusuario

Android includes support for multiple users and provides support for full user isolation.

• Device implementations MAY but SHOULD NOT enable multi-user if they use removable media for primary external storage.

If device implementations include multiple users, they:

• [C-1-1] MUST meet the following requirements related to multi-user support .
• [C-1-2] MUST, for each user, implement a security model consistent with the Android platform security model as defined in Security and Permissions reference document in the APIs.
• [C-1-3] MUST have separate and isolated shared application storage (aka /sdcard ) directories for each user instance.
• [C-1-4] MUST ensure that applications owned by and running on behalf a given user cannot list, read, or write to the files owned by any other user, even if the data of both users are stored on the same volume or filesystem.
• [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 multiple users and do not declare the android.hardware.telephony feature flag, they:

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

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

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

9.6. Advertencia de SMS premium

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.

If device implementations declare support for android.hardware.telephony , they:

• [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. Funciones de seguridad del núcleo

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. Implementaciones 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 explotar.
• [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. Implementaciones 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 ).
• [SR] STRONGLY RECOMMENDED to keep kernel data which is written only during initialization marked read-only after initialization (eg __ro_after_init ).
• [SR} STRONGLY RECOMMENDED to implement static and dynamic object size bounds checking of copies between user-space and kernel-space (eg CONFIG_HARDENED_USERCOPY ).
• [SR] STRONGLY RECOMMENDED to never execute user-space memory when running in the kernel (eg hardware PXN, or emulated via CONFIG_CPU_SW_DOMAIN_PAN or CONFIG_ARM64_SW_TTBR0_PAN ).
• [SR] STRONGLY RECOMMENDED to never 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 ).
• [SR] 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 ).

If device implementations use a Linux kernel, they:

• [C-1-1] MUST implement SELinux.
• [C-1-2] MUST set SELinux to global enforcing mode.
• [C-1-3] MUST configure all domains in enforcing mode. No permissive mode domains are allowed, including domains specific to a device/vendor.
• [C-1-4] MUST NOT modify, omit, or replace the neverallow rules present within the system/sepolicy folder provided in the upstream Android Open Source Project (AOSP) and the policy MUST compile with all neverallow rules present, for both AOSP SELinux domains as well as device/vendor specific domains.
• 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, they:

• [C-2-1] MUST use an mandatory access control system that is equivalent to SELinux.

9.8. Privacidad

9.8.1. Historial de uso

Android stores the history of the user's choices and manages such history by UsageStatsManager .

Implementaciones de dispositivos:

• [C-0-1] MUST keep a reasonable retention period of such user history.
• [SR] Are STRONGLY RECOMMENDED to keep the 14 days retention period as configured by default in the AOSP implementation.

9.8.2. Grabación

If device implementations include functionality in the system that captures the contents displayed on the screen and/or records the audio stream played on the device, 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 to infer useful information about user's context, they:

• [C-2-1] MUST NOT store in persistent on-device storage or transmit off the device the recorded raw audio or any format that can be converted back into the original audio or a near facsimile, except with explicit user consent.

9.8.3. Conectividad

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áfico de red

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

9.9. Cifrado de almacenamiento de datos

If device implementations support a secure lock screen as described in section 9.11.1 , they:

• [C-1-1] MUST support data storage encryption of the application private data ( /data partition ), as well as the application shared storage partition ( /sdcard partition ) if it is a permanent, non-removable part of the device.

If device implementations support a secure lock screen as described in section 9.11.1 and support data storage encryption with Advanced Encryption Standard (AES) crypto performance above 50MiB/sec, they:

• [C-2-1] MUST enable the data storage encryption by default at the time the user has completed the out-of-box setup experience. If device implementations are already launched on an earlier Android version with encryption disabled by default, such a device cannot meet the requirement through a system software update and thus MAY be exempted.

• SHOULD meet the above data storage encryption requirement via implementing File Based Encryption (FBE).

9.9.1. Arranque directo

Implementaciones 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. Cifrado basado en archivos

If device implementations support FBE, 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-3] MUST NOT offer any method to unlock the CE protected storage without the user-supplied credentials.
• [C-1-4] MUST support Verified Boot and ensure that DE keys are cryptographically bound to the device's hardware root of trust.
• [C-1-5] MUST support encrypting file contents using AES with a key length of 256-bits in XTS mode.

• [C-1-6] MUST support encrypting file name using AES with a key length of 256-bits in CBC-CTS mode.

• The keys protecting CE and DE storage areas:

• [C-1-7] MUST be cryptographically bound to a hardware-backed Keystore.

• [C-1-8] CE keys MUST be bound to a user's lock screen credentials.
• [C-1-9] CE keys MUST be bound to a default passcode when the user has not specified lock screen credentials.

• [C-1-10] MUST be unique and distinct, in other words no user's CE or DE key matches any other user's CE or DE keys.

• [C-1-11] MUST use the mandatorily supported ciphers, key lengths and modes by default.

• SHOULD make preloaded essential apps (eg Alarm, Phone, Messenger) Direct Boot aware.

• MAY support alternative ciphers, key lengths and modes for file content and file name encryption.

The upstream Android Open Source project provides a preferred implementation of this feature based on the Linux kernel ext4 encryption feature.

9.9.3. Cifrado de disco completo

If device implementations support full disk encryption (FDE), they:

• [C-1-1] MUST use AES with a key of 128-bits (or greater) and a mode designed for storage (for example, AES-XTS, AES-CBC-ESSIV).
• [C-1-2] MUST use a default passcode to wrap the encryption key and MUST NOT write the encryption key to storage at any time without being encrypted.
• [C-1-3] MUST provide the user the possibility to AES encrypt the encryption key, except when it is in active use, with the lock screen credentials stretched using a slow stretching algorithm (eg PBKDF2 or scrypt).
• [C-1-4] The above default password stretching algorithm MUST be cryptographically bound to that keystore when the user has not specified a lock screen credentials or has disabled use of the passcode for encryption and the device provides a hardware-backed keystore.
• [C-1-5] MUST NOT send encryption key off the device (even when wrapped with the user passcode and/or hardware bound key).

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

9.10. Integridad del dispositivo

The following requirements ensures there is transparency to the status of the device integrity. Implementaciones 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. The FLASH_LOCK_UNKNOWN state is reserved for device implementations upgrading from an earlier version of Android where this new system API method did not exist.

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

• [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 boot loader.
• [SR] If there are multiple discrete chips in the device (eg radio, specialized image processor), the boot process of each of those chips is STRONGLY RECOMMENDED to verify every stage upon booting.
• [SR] STRONGLY RECOMMENDED to use tamper-evident storage: for when the bootloader is unlocked. Tamper-evident storage means that the boot loader can detect if the storage has been tampered with from inside the HLOS (High Level Operating System).
• [SR] STRONGLY RECOMMENDED to prompt the user, while using the device, and require physical confirmation before allowing a transition from boot loader locked mode to boot loader unlocked mode.
• [SR] STRONGLY RECOMMENDED to implement rollback protection for the HLOS (eg boot, system partitions) and to use tamper-evident storage for storing the metadata used for determining the minimum allowable OS version.
• 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.

The upstream Android Open Source Project provides a preferred implementation of this feature in the external/avb/ repository, which can be integrated into the boot loader used for loading Android.

Device implementations with Advanced Encryption Standard (AES) crypto performance above 50 MiB/seconds:

• [C-2-1] MUST support verified boot for device integrity.

If a device implementation is already launched without supporting verified boot on an earlier version of Android, such a device can not add support for this feature with a system software update and thus are exempted from the requirement.

9.11. Claves y Credenciales

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 . Implementaciones de dispositivos:

• [C-0-1] MUST at least allow more than 8,192 keys to be imported.
• [C-0-2] The lock screen authentication MUST rate-limit attempts and MUST have an exponential backoff algorithm. Beyond 150 failed attempts, the delay MUST be at least 24 hours per attempt.
• SHOULD not limit the number of keys that can be generated

When the device implementation supports a secure lock screen, it:

• [C-1-1] MUST back up the keystore implementation with secure hardware.
• [C-1-2] MUST have implementations of RSA, AES, ECDSA and HMAC cryptographic algorithms and MD5, SHA1, and SHA-2 family hash functions to properly support the Android Keystore system's supported algorithms in an area that is securely isolated from the code running on the kernel and above. Secure isolation MUST block all potential mechanisms by which kernel or userspace code might access the internal state of the isolated environment, including DMA. The upstream Android Open Source Project (AOSP) meets this requirement by using the Trusty implementation, but another ARM TrustZone-based solution or a third-party reviewed secure implementation of a proper hypervisor-based isolation are alternative options.
• [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. The upstream Android Open Source Project provides the Gatekeeper Hardware Abstraction Layer (HAL) and Trusty, which can be used to satisfy this requirement.
• [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 from being used as device identifiers. One way of meeting this requirement is to share the same attestation key unless at least 100,000 units of a given SKU are produced. If more than 100,000 units of an SKU are produced, a different key MAY be used for each 100,000 units.

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

9.11.1. Pantalla de bloqueo seguro

If device implementations have a secure lock screen and include one or more trust agent, which implements the TrustAgentService System API, then they:

• [C-1-1] MUST indicate the user in the Settings and Lock screen user interface of situations where either the screen auto-lock is deferred or the screen lock can be unlocked by the trust agent. The AOSP meets the requirement by showing a text description for the "Automatically lock setting" and "Power button instantly locks setting" menus and a distinguishable icon on the lock screen.
• [C-1-2] MUST respect and fully implement all trust agent APIs in the DevicePolicyManager class, such as the KEYGUARD_DISABLE_TRUST_AGENTS constant.
• [C-1-3] MUST NOT fully implement the TrustAgentService.addEscrowToken() function on a device that is used as the primary personal device (eg handheld) but MAY fully implement the function on device implementations typically shared.
• [C-1-4] MUST encrypt the tokens added by TrustAgentService.addEscrowToken() before storing them on the device.
• [C-1-5] MUST NOT store the encryption key on the device.
• [C-1-6] MUST inform the user about the security implications before enabling the escrow token to decrypt the data storage.

If device implementations add or modify the authentication methods to unlock the lock screen, then for such an authentication method to be treated as a secure way to lock the screen, they:

• [C-2-1] MUST be the user authentication method as described in Requiring User Authentication For Key Use .
• [C-2-2] MUST unlock all keys for a third-party developer app to use when the user unlocks the secure lock screen. For example, all keys MUST be available for a third-party developer app through relevant APIs, such as createConfirmDeviceCredentialIntent and setUserAuthenticationRequired .

If device implementations add or modify the authentication methods to unlock the lock screen if based on a known secret then for such an authentication method to be treated as a secure way to lock the screen, they:

• [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] MUST not replace any of the existing authentication methods (PIN,pattern, password) implemented and provided in AOSP.
• [C-3-4] MUST be disabled when the Device Policy Controller (DPC) application has set the password quality policy via the DevicePolicyManager.setPasswordQuality() method with a more restrictive quality constant than PASSWORD_QUALITY_SOMETHING .

If device implementations add or modify the authentication methods to unlock the lock screen if based on a physical token or the location, then for such an authentication method to be treated as a secure way to lock the screen, they:

• [C-4-1] MUST have a fall-back mechanism to use one of the primary authentication methods which is based on a known secret and meets the requirements to be treated as a secure lock screen.
• [C-4-2] MUST be disabled and only allow the primary authentication to unlock the screen when the Device Policy Controller (DPC) application has set the policy with either the DevicePolicyManager.setKeyguardDisabledFeatures(KEYGUARD_DISABLE_TRUST_AGENTS) method or the DevicePolicyManager.setPasswordQuality() method with a more restrictive quality constant than PASSWORD_QUALITY_UNSPECIFIED .
• [C-4-3] The user MUST be challenged for the primary authentication (egPIN, pattern, password) at least once every 72 hours or less.

If device implementations add or modify the authentication methods to unlock the lock screen based on biometrics, then for such an authentication method to be treated as a secure way to lock the screen, they:

• [C-5-1] MUST have a fall-back mechanism to use one of the primary authentication methods which is based on a known secret and meets the requirements to be treated as a secure lock screen.
• [C-5-2] MUST be disabled and only allow the primary authentication to unlock the screen when the Device Policy Controller (DPC) application has set the keguard feature policy by calling the method DevicePolicyManager.setKeyguardDisabledFeatures(KEYGUARD_DISABLE_FINGERPRINT) .
• [C-5-3] MUST have a false acceptance rate that is equal or stronger than what is required for a fingerprint sensor as described in section 7.3.10, or otherwise MUST be disabled and only allow the primary authentication to unlock the screen 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_BIOMETRIC_WEAK .
• [C-5-4] The user MUST be challenged for the primary authentication (egPIN, pattern, password) at least once every 72 hours or less.

If device implementations add or modify the authentication methods to unlock the lock screen and if such an authentication method will be used to unlock the keyguard, but will not be treated as a secure lock screen, then they:

• [C-6-1] MUST return false for both the KeyguardManager.isKeyguardSecure() and the KeyguardManager.isDeviceSecure() methods.
• [C-6-2] MUST be disabled when the Device Policy Controller (DPC) application has set the password quality policy via the DevicePolicyManager.setPasswordQuality() method with a more restrictive quality constant than PASSWORD_QUALITY_UNSPECIFIED .
• [C-6-3] MUST NOT reset the password expiration timers set by DevicePolicyManager.setPasswordExpirationTimeout() .
• [C-6-4] MUST NOT authenticate access to keystores if the application has called KeyGenParameterSpec.Builder.setUserAuthenticationRequired(true) ).

9.12. Eliminación de datos

All device implementations:

• [C-0-1] MUST provide users a mechanism to perform a "Factory Data Reset".
• [C-0-2] MUST delete all user-generated data. That is, all data except for the following:
  • The system image
  • Any operating system files required by the system image
• [C-0-3] MUST delete the data in such a way that will satisfy relevant industry standards such as NIST SP800-88.
• [C-0-4] MUST trigger the above "Factory Data Reset" process when the DevicePolicyManager.wipeData() API is called by the primary user's Device Policy Controller app.
• MAY provide a fast data wipe option that conducts only a logical data erase.

9.13. Modo de arranque seguro

Android provides Safe Boot Mode, which allows users to boot up into a mode where only preinstalled system apps are allowed to run and all third-party apps are disabled. This mode, known as "Safe Boot Mode", provides the user the capability to uninstall potentially harmful third-party apps.

Device implementations are:

• [SR] STRONGLY RECOMMENDED to implement Safe Boot Mode.

If device implementations implement Safe Boot Mode, they:

• [C-1-1] MUST provide the user an option to enter Safe Boot Mode in such a way that is uninterruptible from third-party apps installed on the device, except when the third-party app is a Device Policy Controller and has set the UserManager.DISALLOW_SAFE_BOOT flag as true.

• [C-1-2] MUST provide the user the capability to uninstall any third-party apps within Safe Mode.

• SHOULD provide the user an option to enter Safe Boot Mode from the boot menu using a workflow that is different from that of a normal boot.

9.14. Aislamiento del sistema de vehículos automotrices

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.

10. Pruebas de compatibilidad de software

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. Conjunto de pruebas de compatibilidad

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

El CTS está diseñado para ejecutarse en un dispositivo real. Como cualquier software, el CTS puede contener errores. The CTS will be versioned independently of this Compatibility Definition, and multiple revisions of the CTS may be released for Android 8.0.

Implementaciones 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. Verificador CTS

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.

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

Implementaciones 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. Software actualizable

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

Se puede utilizar cualquier método, siempre que pueda reemplazar la totalidad del software preinstalado en el dispositivo. Por ejemplo, cualquiera de los siguientes enfoques satisfará este requisito:

• “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. Tenga en cuenta que el software Android ascendente incluye un mecanismo de actualización que satisface este requisito.

If the device implementations includes support for an unmetered data connection such as 802.11 or Bluetooth PAN (Personal Area Network) profile, then, they:

• [C-1-1] MUST support OTA downloads with offline update via reboot.

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

Also, device implementations SHOULD support A/B system updates . The AOSP implements this feature using the boot control HAL.

If an error is found in a device implementation after it has been released but within its reasonable product lifetime that is determined in consultation with the Android Compatibility Team to affect the compatibility of third-party applications, then:

• [C-2-1] The device implementer MUST correct the error via a software update available that can be applied per the mechanism just described.

Android includes features that allow the Device Owner app (if present) to control the installation of system updates. If the system update subsystem for devices report android.software.device_admin then, they:

• [C-3-1] MUST implement the behavior described in the SystemUpdatePolicy class.

12. Registro de cambios del documento

For a summary of changes to the Compatibility Definition in this release:

• Document changelog

For a summary of changes to individuals sections:

1. Introducción
2. Tipos de dispositivos
3. Software
4. Empaquetamiento de aplicaciones
5. Multimedia
6. Developer Tools and Options
7. Hardware Compatibility
8. Rendimiento y potencia
9. Modelo de seguridad
10. Software Compatibility Testing
11. Updatable Software
12. Document Changelog
13. Contáctenos

12.1. Consejos para ver el registro de cambios

Changes are marked as follows:

• CDD
  Substantive changes to the compatibility requirements.

• Documentos
  Cosmetic or build related changes.

For best viewing, append the pretty=full and no-merges URL parameters to your changelog URLs.

13. Contáctenos

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