Your browser is not supported. Please update it.

4 June 2015

Google I/O: Android tweaks, Brillo and Weave provide the thrills

Google’s I/O event churned out a lot of things we expected to see from the developer conference, but also a few surprises. Most interesting were the releases of Brillo, the anticipated lightweight OS for the internet of things (IoT), and the more surprising launch of Weave, an API framework which could set Google up against Qualcomm’s AllJoyn in the fight to control IoT device discovery and interconnection.

The event also marked the release of the developer preview of Android M, even though that looks like a conservative distribution that adds a few enhancements, rather than a radical visual overhaul like Lollipop brought about last year.

There were notable absences in the announcements, including any news of Glass, Project Loon, or Google’s self-driving cars. With no announcements for the enterprise sector either, it was a testament to the size of the search giant’s portfolio that it could still hold hours of presentations without covering all of its projects and products.

On stage, Google’s SVP Sundar Pichai said that last year, eight out of 10 smartphones that shipped ran Android. There are now one billion active Android users, he said, and they downloaded 50bn apps in the past year. Meanwhile, Android Wear is now supported by seven smartwatches, and there are over 4,000 Wear apps – with support for SIM cards due to be added soon.

Brillo OS and Weave APIs for the IoT:

Two weeks before I/O, news leaked of a planned IoT-centric operating system called Brillo. The leak proved to be correct, and Google unveiled Brillo at I/O.

Google says Brillo is essentially a package that keeps the lower-level components of Android, but does away with the higher level stuff that is not needed by the kinds of devices that Brillo is designed for – those with 32-64Mbytes of RAM.

So while the modifications to the base Linux kernel and the hardware abstraction layers are still present, Brillo will be a very different beast to the flavor of Android found in smartphones. Google promises that developers will be able to reuse existing Android software stacks for Brillo, however.

The more pressing bit of news that hadn’t leaked in advance was the unveiling of the new Weave API framework, which Google says will help standardize communication between devices. Actual details about Weave are pretty scant, but the platform-agnostic schema exposes developer APIs, to help link cloud-based services to devices supporting Android and Weave. It looks like it will be pretty familiar to those who work with JSON Java, based on the preview images.

It will be the bridge between Android devices, Brillo devices, and the wider internet-enabled cloud platforms, and so rather resembles Apple’s HomeKit, which aims to allow connected objects in the smart home to talk to iDevices and Apple’s cloud services without the need for direct application support. However, we won’t know much more about the mechanics behind the platform until developers get their hands on it, or until Google starts letting more details out.

Weave joins a number of initiatives aimed at tackling the inter-communication issues that are so prevalent in the IoT. In functionality, it appears to resemble the most notable of those, the AllSeen Alliance’s AllJoyn framework, developed and backed by Qualcomm, as well as its closest rival, the Open Interconnect Consortium’s IoTivity project. Both aim to enable device discovery and consequent communication, and effectively serve as device-level software-driven discovery protocols that can configure smart homes dynamically.

Weave may well be Google’s attempt to steal the thunder from those two initiatives and add to its own collection of would-be IoT standards, such as the Thread connectivity protocol (devised by its Nest subsidiary). However, Weave is not a separate protocol like AllJoyn, but a lightweight schema for developers.

In terms of their release, Google says Q3 for Brillo and Q4 for Weave, which should see them emerge after version 1.0 of the Thread radio protocol is released. This technology is backed by the Thread Group, an industry body founded by Google-owned Nest to develop the 802.15.4-based 6LoWPAN mesh networking protocol. This is likely to form the backbone of an Android-based smart home initiative from Google/Nest, in which Brillo and Weave will also have key roles.

With full-fat Android controlling larger devices in the smart home, such as TVs and dedicated smart home hubs, Brillo can be used to run the smaller devices such as thermostats, security cameras and video-based intercoms. Linking these devices to even smaller microcontroller-based devices (too small to run Brillo) will be the Thread protocol, as well as a combination of WiFi and Bluetooth in all likelihood.

And by the looks of it, Weave will support the actual bits and bytes conveyed around the smart home by these three radio protocols – allowing an interoperable network of connected smart home kit, and of course other applications in business or industrial deployments.

The Android M news:

With Android M, Pichai said that the release was more about improving the core user experience with polish and quality, rather than radical rethinks or feature additions. It seems that a lot of background work has been done to improve how Android behaves as an operating system, which won’t be visible to the user but should afford an improvement in the user’s experience.

Android Pay, Google’s mobile payments platform, will be rolling out to some 700,000 US stores, and will also be integrated into applications directly – including Groupon, GrubHub and Lyft. API support for fingerprint scanners will allow Android M to imitate Apple Pay, but the system will still work on devices without them.

A new Doze feature has also been added, which Google says has increased the standby time of test handsets by 100%. Doze uses motion sensors to guess how deep a sleep it should enter, and so will essentially deactivate just the screen when it thinks it’s in someone’s hand, but might shut down all redundant systems if it thinks it’s on a bedside table after its owner has gone to sleep themselves.

One of the more interesting additions to Android M is Now on Tap (NoT), a poorly-named but admittedly useful digital assistant that analyzes on-screen content. The example use case saw a text conversation about dry cleaning trigger a calendar entry to remind the user to go and collect it, and a conversation about a film was augmented with suggested trailers and cast information – all powered by Google’s extensive cloud platforms and machine learning algorithms.

Wear has also received a battery-life buff, with the addition of a monochrome lock screen that will display the time – to cut down on users having to wake a blank screen in order to use the main function of their watch. Other apps on the watches can also be set to an always-on mode, so that the screen won’t power down while they are open. Wrist gestures support has also been added, meaning that movements can trigger apps or functions, such as turning the screen on when the watch is raised to be looked at.

Google’s Android Auto has also been rolled out, with support from 35 manufacturers. The first car to support the IVI (in-vehicle infotainment) platform is the Hyundai Sonata, which will essentially allow the user’s smartphone to be controlled using the in-car controls – to prevent drivers from fiddling with the phone while driving. Since the car will be leveraging the phone for the apps, this also neatly brings Google Now and Google Maps into the automotive sphere.

The new Nvidia Shield console/set-top hybrid frames a few tweaks to Android TV, which largely introduced new live-esque channels playing on-demand content (a weird almost backwards step), and additions to Chromecast to better support in-home streaming.

Also announced was the separation of the Photos service from the abortive social media platform that is Google+. Photos will now live as a separate entity, and in an attempt to spur usage, Google is offering unlimited storage for photos and video (up to 16-megapixels for photos, and 1080p video at 60 frames per second). Android One, the bare-bones version of the OS for emerging market handsets, will also be rolling out to Bangladesh, Nepal, the Philippines and Turkey, while a trial of image blocking and offline-playable YouTube continues in India.

ATAP projects – smart clothing and gesture chips:

Google’s Advanced Technology and Projects (ATAP) division was on-hand to unveil its latest R&D activities, including Project Jacquard – an initiative to integrate device controls into clothing, whose name is derived from a style of machine weaving.

ATAP’s previous output includes modular smartphones (Project Ara), and the 3D environmental mapping Project Tango (see separate item), and the new project uses conductive wires that are woven into fabric to interpret touch. This means that clothing could end up acting like the touchscreen on a smartphone, allowing users to input controls via their garments – or any other fabric textile.

According to project lead Ivan Poupyrev, “if you can weave the sensor into the textile, as a material, you’re moving away from the electronics. You’re making the basic materials of the world around us interactive”. While the concept isn’t new, its compatibility with mass manufacturing techniques is. Now Google just has to convince manufacturers to adopt the tech, by creating viable use cases for it leveraging Android.

Also announced was Project Soli, which is as small radar-based chip and software framework to allow a device to understand hand gestures. The chip is very small, and could feasibly be integrated into smartphones, furniture or other objects, allowing users to interact with physical objects.

The last of the ATAP-related announcements came in an update on Project Abacus, which is attempting to replace the password with a unique identifier based on a user’s mannerisms. Passwords might be intercepted, but it’s a lot harder to replicate the way a user holds their phone and physically types on its keyboard.

The idea with Abacus is to bypass the need for login details to use apps or payments, by allowing the phone to know who is using it based on those usage patterns. In its trials with 33 universities, Google was convinced of the viability of the technology, and claims it is 10 times more secure than relying on a fingerprint scanner.

It looks like it will act as a more evolved version of Andoid’s smartlock function, which can be used to automatically identify a user, usually through facial recognition. Google says it can have granular permissions, but if the system doesn’t recognize the person operating it, it will ask for a password for authorization.

Next – Apple WWDC:

So now we just have to wait for Apple’s WWDC (Worldwide Developers’ Conference), which follows I/O as night follows day and will surely come with its own share of new announcements in hot fields like wearables and IoT. The core content, of course, will be centered on the next releases of iOS and OS X – with pundits anticipating a more major upgrade for iOS than Android received this year.

They are also expecting news about the much-anticipated music streaming service, based on Apple’s acquisition of Beats, though Apple TV may well be a no-show, except – according to Macworld – to become a HomeKit hub, the voice-activated Siri to control smart home items. A completely overhauled iOS Maps and enhanced Siri are also favorite rumors, as well as an initiative, leaked last month by 9to5Mac, called Proactive, which would unite Siri, Spotlight, Calendar, Maps and other apps to result in a more proactive digital personal assistant.

On the wearables side, Apple Watch is likely to get an open software developers’ kit with support for third party apps running natively, not just on the iPhone. That would allow them to tap directly into Watch features like the heart rate sensor, rather than going via the handset.