<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Bluetooth on Brave New Geek</title><link>https://bravenewgeek.com/tag/bluetooth/</link><description>Recent content in Bluetooth on Brave New Geek</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 19 Mar 2013 16:01:49 -0600</lastBuildDate><atom:link href="https://bravenewgeek.com/tag/bluetooth/index.xml" rel="self" type="application/rss+xml"/><item><title>Bluetooth Blues</title><link>https://bravenewgeek.com/bluetooth-blues/</link><pubDate>Tue, 19 Mar 2013 16:01:49 -0600</pubDate><guid>https://bravenewgeek.com/bluetooth-blues/</guid><description>&lt;p&gt;I spent the better part of two days working on Bluetooth connectivity for an Android app I’m developing. Going into it, I had virtually no experience working with Bluetooth, especially on Android. I quickly discovered some of the peculiarities of the platform’s Bluetooth API.&lt;/p&gt;
&lt;p&gt;In addition to connecting to Bluetooth devices, the client wanted to pair and unpair from the app. The easy way out, and probably &lt;em&gt;The Android Way&lt;/em&gt;™, would be to pass that responsibility off to the OS, à la an Intent:&lt;/p&gt;</description></item></channel></rss>