Please enable JavaScript.

Coggle requires JavaScript to display documents.

Android Things (Supported Android features (Firebase (Firebase Analytics,…

- - - - The Peripheral I/O APIs let your apps communicate with sensors and actuators using industry standard protocols and interfaces. The following interfaces are supported: GPIO, PWM, I2C, SPI, UART.
        
        General Purpose Input/Output (GPIO)
        
        Use this API for simple sensors such as motion detectors, proximity detectors, and level switches that report their current state as a binary value—high or low.
        
        Pulse Width Modulation
        
        Use this API for servo motors, DC motors, and lights that require a proportional signal to provide fine-grained control over the output.
        
        Serial Communication
        
        Use these APIs to transfer larger payloads of data between two or more smart devices connected on the same local bus. The following table outlines the basic attributes of each supported serial protocol:
    - - User drivers extend existing Android framework services and allow apps to inject hardware events into the framework that other apps can access using the standard Android APIs
        
        Note: You cannot customize the behavior of device drivers in the Linux kernel or Hardware Abstraction Layer (HAL) to add new functionality to a device.
        
        Benefits
        
        Portability: Application code that purely targets the Android framework can run on a variety of different boards and configurations without additional abstractions for the device driver implementation.
        
        Reuse: You can pull existing Android code snippets and libraries into your application without the need to modify or fork them to handle your specific hardware implementation.
        
        Integration: Android often combines data from various services together to enhance the information reported to apps or create new virtual data sets. User drivers can contribute to this process.
        
        Device Driver Types
        
        GPS - GPS provides high accuracy physical location information to apps. Integrating the location results from GPS devices with a user driver allows the framework to connect that data with other location sources, such as WiFi, and Google's Fused Location Provider.
        
        HID - Human Interface Devices (HID) provide user input to apps. Touch pads, keyboards, and game controllers are all examples of devices that provide this type of input. Input user drivers let devices interact with the enhanced input framework APIs, such as Gesture Support or Drag and Drop.
        
        Sensors - Sensors measure and report the conditions of the physical environment. The Android sensor framework implements sensor fusion to combine the raw data from multiple physical sensors into a single virtual sensor. This is particularly common with motion sensors, such as accelerometers and gyroscopes. Connecting your sensor to the framework with a user driver allows the data it produces to be included in sensor fusion.
        
        Audio - The Android media framework provides a rich API surface for audio playback and recording. Using audio drivers, you can extend the set of input/output devices available to Android. Your app can also define which audio device should be considered the default.
      - Classes
        AudioInputDriver Driver to replace the android audio HAL for a specific device.
        AudioOutputDriver Driver to replace the android audio HAL for a specific device.
        GpsDriver Driver to interface with user-connected GPS sensors.
        InputDriver Driver to interface with user-connected input devices.
        InputDriver.Builder Builder class for InputDriver objects.
        UserDriverManager Manager for all user drivers.
        UserSensor A user-defined sensor backed by a UserSensorDriver.
        UserSensor.Builder Builder to allow for flexible UserSensor construction.
        UserSensorDriver Driver to interface with a user-connected sensor.
        UserSensorReading A single user-sensor reading.
- - - - All of Android hardening is enabled for Android Things
        
        Permissions, application sandbox, mandatory access control(SELinux),kernal syscall filtering(Seccomp-BPF),full ASLR, FORTIFY, stack-protector-strong
    - - Google takes care of building and serving all updates. The SoM model allows this to scale efficiently
      - Automatic updates (monthly)
      - Developers controls
        
        Developers will have the chance to test every update before it pushes. With no developer action, the default is to push
      - Device Controls
        
        An API to delay the update process (including reboot) during critical operations.
      - Per-Product Keys
        
        Hardware is permanently bound to a single product and this is checked during verification. Two products built on the same hardware SoM will fail to verify each other's software images.
      - Rollback Protection
        
        For both software images and signing keys
    - - Signing By Google
        
        Google takes care of signing images and updates.AVB reference code is always used for verification (except bootloaders). Hardware partners take care of bootloaders verification
      - Verified Boot Hash
    - - Cryptographic Keys
        
        Encrypt Sensitive Data
        
        Full Disk Encryption is not required or expected Applications should use hardware-backed keys to encrypt and authenticate sensitive, persistent data.
        
        AndroidKeyStore API
    - - Attest to What? Authentic AndroidThings device, Product info, device identity, device state, key attributes
      - Certificate Authority Operated by Google. Google provides the authorty for all Android Things attestation certificate chains.
      - Factory Provisioning Factory Appliance from Google. Developers choose wheater to key their devices. Keys are required if integrationg with Cast and /or Assistant
      - Anonymous Attestation Supporting crypotographic mechanisms both for identity and anonymiy gives flexibiltiy
- - - - EAGLE
        
        KiCAD
        
        Altium
- - - - Protocol Bridge
        
        MQTT protocol
        
        Automatic load balancing
        
        Global data access with Pub/Sub
      - Device Manger
        
        Configure individual devices
        
        Update and control devices
        
        Role level access control
        
        Console ad APIs for device deployment and montioring