Posted via Dave Smith, Developer Advocate for IoT
Earlier this yr at CES, we showcased client merchandise powered via Android Things from companions like Lenovo, LG, JBL, iHome, and Sony. We are excited to look Android Things allow the broader developer ecosystem as smartly. Today we’re saying the overall preview free up of Android Things, Developer Preview eight, earlier than the impending solid free up.
Feature whole SDK
Developer Preview eight represents the overall API floor uncovered within the Android Things strengthen library for the impending solid free up. There will likely be not more breaking API adjustments earlier than the solid v1.zero free up of the SDK. For main points on the entire API adjustments integrated in DP8, see the discharge notes. Refer to the up to date SDK reference to study the categories and strategies within the ultimate SDK.
This free up additionally brings new options within the Android Things developer console to make development and managing manufacturing units more uncomplicated. Here are some notable updates:
Production-focused console improvements
With an eye fixed against development and delivery manufacturing units with the impending LTS free up, now we have made a number of updates to the Android Things developer console:
- Enhanced OTA: Unpublish the present OTA construct when problems are found out within the box.
- Visual garage format: Configure the instrument garage allotted to apps and knowledge for each and every construct, and get an outline of ways a lot garage your apps require.
- Font/locale controls: Configure the set of supported fonts and locales packaged into each and every construct.
- Group sharing: Product sharing has been prolonged to incorporate strengthen for Google Groups.
The new app library lets you set up APKs extra simply with out the want to bundle them in combination in a separate zipped package. Track particular person variations, evaluation permissions, and percentage your apps with different console customers. See the app library documentation for extra main points.
On cell units, apps request permissions at runtime and the top consumer grants them. In previous previews, Android Things granted those identical permissions mechanically to apps on instrument boot. Beginning in DP8, those permissions are granted the use of a brand new interface within the developer console, giving builders extra regulate of the permissions utilized by the apps on their instrument.
This exchange does no longer have an effect on building, as Android Studio grants all permissions via default. Developers the use of the command line can append the
-g flag to the
adb set up command to get the similar habits. To check how apps to your instrument behave with positive permissions revoked, use the
$ adb shell pm [grant|revoke] <permission-name> ...
App release habits
Embedded units want to release their number one utility mechanically after the instrument boots, and relaunch it if the app terminates impulsively. In previous previews, the primary app at the instrument may just pay attention for a customized
IOT_LAUNCHER intent to allow this habits. Beginning in DP8, this class is changed via the usual CATEGORY_HOME intent.
<task android:call=".HomeActivity"> ... <!-- Launch task mechanically on boot, relaunch on termination. --> <intent-filter> <motion android:call="android.intent.action.MAIN"/> <class android:call="android.intent.category.HOME"/> <class android:call="android.intent.category.DEFAULT"/> </intent-filter> </task>
Apps that include an
IOT_LAUNCHER intent clear out will not be brought on on boot. Update your apps to make use of CATEGORY_HOME as a substitute.
Thanks to all of you within the developer neighborhood for sharing your comments with us during developer preview. Join Google’s IoT Developers Community on Google+ to tell us what you might be development with Android Things and the way we will be able to enhance the platform in long term releases that can assist you construct hooked up units at scale!
Android Developers Blog: Android Things Release Candidate