Tag: Bluetooth setup

Articles

Most recent Android smartphones may be able to support one-touch pair-up for Bluetooth accessories

Android ‘Fast Pair’ will quickly connect Bluetooth devices | Engadget

Announcing Fast Pair – effortless Bluetooth pairing for Android | Android Developers Blog

My Comments

Google has answered the setup method that Apple has implemented for their AirPod wireless in-ear headset by implementing a software-driven “quick-pair” setup that will be part of Android.

This method, called Bluetooth Fast Pairing, works on Android handsets and other devices that run Android 6.0 Marshmallow onwards and have Google Play Services 11.7 or newer installed and support Bluetooth 4.0 Low Energy (Bluetooth Smart) connectivity. You will have to enable Bluetooth and Location functionality in your handset, but you don’t have to look at Bluetooth device lists on your smartphone for a particular device identifier to complete the setup process.

Click or tap this image to see Google Fast Pairing in action

It is meant to provide quick discovery of your compliant Bluetooth accessory device in order to expedite the setup process that is involved with new devices or to “repair” Bluetooth connections that have failed. This latter situation can easily occur if data in the device regarding associated Bluetooth devices becomes corrupted or their is excessive Bluetooth interference.

The user experience will require you to put your accessory device like a Bluetooth headset, speakers or car stereo in to Bluetooth-setup mode. This may simply be through you holding down the “setup” or “pair” button till a LED flashes a certain way or you hear a distinct tone. On the other hand in the case of home and car audio equipment that has a display of some form, you using the “Setup Menu” to select “Bluetooth Setup” or something similar.

Then you receive a notification message on your Android device which refers to the device you just enabled for pairing, showing its product name and a thumbnail image of the device. Tap on this notification to continue the setup process and you may receive an invitation to download a companion app for those devices that work on the “app-cessory” model for extended functionality.

Google implements this by using Bluetooth Low Energy “beacon” technology to enable the device-discovery process. This is similar to the various beacon approaches for marketing and indoor navigation that are being facilitated by Bluetooth Low Energy, but they only appear while your accessory device is in “Bluetooth setup” mode.

The Google Play servers provide information about the device such as its thumbnail image, product name or link to a companion app based on a “primary-key” identifier that is part of the Bluetooth Low Energy “beacon” presented by the device. Then, once you tap the notification popup on your Android device, the pairing and establishment process takes place under Bluetooth Classic technology.

I see this also as being similar to the various “Plug And Play” discovery process implemented in Microsoft Windows and Apple MacOS whenever you connect newer peripherals to your computer. This is where Microsoft and Apple keep data about various peripherals and expansion cards that are or have been on the market to facilitate installation of any necessary drivers or other software or invocation of class drivers that are part of the operating system. For Google and the Android platform, they could take this further with USB-C and USB Micro-AB OTG connectivity to implement the same kind of “plug and play” setup for peripherals connected this way to Android devices.

This system could be taken further by integrating similar logic and server-hosted databases in to other operating systems for regular and mobile computer platforms to improve and expedite the setup process for Bluetooth devices where the host device supports Bluetooth Low Energy operation. Here, I would like to see it based on the same identifiers broadcast by each of the accessory devices.

The Bluetooth Fast Pairing ability that Google gave to the Android platform complements NFC-based “touch and go” pairing that has been used with that platform as another method to simplify the setup process. This is more for manufacturers who don’t have enough room in their accessory device’s design to provide an NFC area for “touch-and-go” setup thanks to very small devices or where NFC doesn’t play well with the device’s aesthetics or functionality.

It may be a point of confusion for device designers like Alpine with their car stereos who place their devices in “discoverable” or “pairing” mode all the time so you can commence enrolling your accessory device at your phone’s user interface. Here, the device manufacturer may have to limit its availability to certain circumstances like no devices paired or connected, or you having to select the “Bluetooth” source or “Setup” mode to invoke discoverability.

At least Google have put up a way to allow quicker setup for Bluetooth accessories with their Android platform devices without the need to build the requirement in to the hardware.

There may be difficulties running a Bluetooth speaker like this with multiple source devices in the same room

The Bluetooth A2DP audio playback setup which provides a wireless link between a mobile device and a sound system or Bluetooth speaker has now brought along its own set of complications. This is something that will show up more as the number of Bluetooth-capable wireless speakers, audio adaptors and music systems in circulation increases.

One main complication is that the last-connected Bluetooth-capable source device “lays claim” to the Bluetooth-capable sound system until either device’s Bluetooth functionality is turned off. This is even though the user of that source device stopped playing the audio content using the media player and can cause complications where, for example, an “established” Bluetooth device like a tablet cannot be used with the sound system it is normally used with because a guest “walked up” to the sound system and paired their iPhone full of their music collection to that unit to play some of their tunes.

The practice is expected to be common with music systems that are operated during a party where you want to let a guest “look after the tunes” for the evening; and will become common with cars when a group of people go on a long journey and one of these passengers offers to “look after the tunes” for a part of the trip. At the Australian Audio And AV Show 2013, the people who were demonstrating the Aktimate active speakers with a Bluetooth adaptor allowed me to try the speakers with a track on my phone but asked me to make sure the Bluetooth on my phone is off or the speakers removed from the phone’s devices list after I had finished playing the music.

Two or more devices paired to the one Bluetooth headset and on in the same vicinity may cause problems.

It can also show up when you use the same Bluetooth headset or audio adaptor amongst a group of devices which is common when you want to use your headset with your smartphone while walking down the street or use it with your laptop to make that Skype or Lync call.

How do you handle this situation

When you have finished using a Bluetooth sound system, especially one you use on an ad-hoc basis, you have to make sure you logically disconnect your computer or mobile device from that sound system. Most commonly, you may have to turn off your computer’s or mobile device’s Bluetooth functionality. But if you are using your own Bluetooth peripherals, then you have to enable the Bluetooth functionality again.

Logically disconnecting the device

The recent versions of the Android mobile operating system handle this better by allowing a Bluetooth device to be “disconnected” without the Android smartphone or tablet losing its paring data. Here, you enter the Android Bluetooth menu to tap on the currently-connected device to disconnect it immediately.  The ability to retain the pairing is important if you are using a particular Bluetooth device regularly such as a car sound system in the car you regularly drive or a commonly-used Bluetooth-capable hi-fi setup.

Unpairing or removing the device from your operating system

Most other desktop and mobile platforms require you to “remove” or “”unpair” the music system from the Bluetooth-capable source device. Then if you want to use the same Bluetooth device again, you have to put that device in to pairing mode which typically requires you to press and hold a button to invoke this mode; and use the operating system’s Bluetooth menu or “Add New Device” menu to add or pair with a new Bluetooth device.

In Windows, this requires you to go to the Devices Menu, select the device and select the Remove option to remove the sound system. There is the Bluetooth icon in the Taskbar which has the right-click option to “Show Connected Devices” to bring up all the Bluetooth devices associated with your system.

Macintosh users have to click on the “System Preferences” item under the Apple menu, select the Bluetooth icon in the System Preferences window, select the device in the left-hand list box and click the “-“ button to remove the device.

For iOS, you may have to go to the Bluetooth menu under Settings – General. and touch “Unpair” to detach the sound system.

What needs to happen

Support for “connect / disconnect” on all desktop and mobile operating systems

An improvement that needs to be able to exist for an operating system’s Bluetooth functionality is to allow the user to logically “connect” and “disconnect” a Bluetooth peripheral manually. Here, the parings are retained in the host device while it is disconnected yet, when you connect, they come in to play as part of attempting to connect up with the device. This doesn’t remove the ability for a device to immediately connect when it is paired but  allows it to stay paired without being connected.

Bluetooth-capable audio equipment to support multiple connections

We are starting to see some Bluetooth headsets, speakers and in-car setups able to support multiple connections to different devices. This is typically to facilitate a media-player-only device like an Apple iPod Touch to play content while the device serves as a hands-free for a smartphone that is not necessarily used as a media player. Sony has made an effort with their SBH-20 Bluetooth headset adaptor to support the multiple-connection requirement for two smartphones thus facilitating one-touch answer from either phone.

Similarly, a Bluetooth-capable audio device could implement a multiple-connection setup where it can stay connected to many Bluetooth host devices. Each of these host devices can be enumerated as a virtual source as far as the Bluetooth-capable audio device is concerned and there is a user interface on the Bluetooth audio device to select between the different hosts.

Automotive implementations could allow multiple smartphones to connect with one being determined as a “primary” device for making and taking calls and receiving messages and others determined as either “secondary” devices used primarily to take calls or as “media-player” devices that only play media.

Conclusion

This issue of having Bluetooth devices, especially Bluetooth audio devices, work with multiple host computing devices is something that has caused headaches and will be doing so until the people designing the operating systems and devices can handle this reality properly and easily.