In this document
- Developer preview 1
This document outlines issues and fixes related to each release of the Android Things developer preview.
Please file bugs using the Android Things template for issues discovered in the system, hardware support, and documentation. Before filing a bug, please check this page for known issues and ensure you are running the latest version of the preview system image.
Developer Preview 1
Date: December 2016
Build Number: NIF73/NIF74
Preview APIs Javadoc reference.
This preview release is for developers and early adopters to use for development and compatibility testing on supported hardware platforms. Please note the following general guidelines about the preview:
- This release may have various stability issues on supported hardware. Please file bugs to report issues that you discover.
- Not all APIs are enabled in this preview. APIs known to be disabled are documented in the Known Issues section.
- Developer Preview 1 is available on the Intel Edison, NXP Pico, and Raspberry Pi 3 development boards.
- System power management is currently disabled. Devices will not suspend and wake locks are not necessary.
- Bluetooth APIs are currently disabled.
- USB APIs are currently disabled.
- Dangerous permissions
requested by apps are not granted until the next device reboot. This includes
new app installs and new
<uses-permission>elements in existing apps.
- Apps using Google Play Services APIs must compile against SDK version 10.0.0 or newer.
- Google Play Services requires 2-3 minutes on first boot to pre-optimize dex. App installs are blocked until this process is complete.
- When multiple activities contain an intent filter for the
IOT_LAUNCHERcategory, the system displays an app chooser that isn't accessible on devices without display support. Android Things only supports a single launcher app, and this behavior will be disabled in a future release.
- Peripherals do not clear or reset after calling
close(). Outputs will retain their state and serial ports may continue to transmit previously buffered data.
- GPIO pins cannot be used as an output if they were previously enabled as an input with an edge trigger enabled since the last reboot.
- User sensors cannot currently be unregistered manually. They are unregistered automatically when the app process terminates.
- User sensors only support continuous and on-change sensors. One-shot and special reporting modes may not function as expected.
- Audio: Recording is not currently supported.
- I/O: GPIO pin GP77 is listed by
PeripheralManagerService, but is not accessible to apps.
- RESET: The RESET button on the Arduino breakout board can temporarily leave your board in an inconsistent state where GPIO pins are named GPXX instead of IOXX until power is disconnected. Instead of using the onboard RESET button, disconnect and reconnect power to reboot.
- Network: Ethernet is currently disabled.
falsewhen the pin is configured as an output.
- Network: Wi-Fi cannot connect to the internet if Ethernet is also connected to a network without internet access.
- Graphics: Hardware graphics acceleration is not currently enabled.
- Camera: A new
CameraCaptureSessioncannot be created with more than one target output surface.
- Camera: The first request in any
CameraCaptureSessionalways queues two images. This can cause each subsequent
CaptureRequestin the same session to return a buffered frame from a previous capture.
- I/O: Shared pins BCM13/PWM0 and BCM18/PWM1 cannot be used for GPIO if they were previously enabled for PWM since the last reboot.
- I/O: GPIO pins BCM23 and BCM24 are both currently mapped to control BCM23 (physical pin J8-16).