Re: "open" bluetooth devices

Yes Jeffrey, the TI sensor tag is pretty cool and I'm using it too. The
wiki for the sensor tag is also very useful
http://processors.wiki.ti.com/index.php/Bluetooth_SensorTag?INTC=SensorTag&HQS=sensortag-wiki
..

Thanks for the link on the Chromw app samples - hope to code some demos
with the TI sensor tag + the chrome packaged apps ble api
https://developer.chrome.com/apps/bluetoothLowEnergy


On Fri, Aug 22, 2014 at 6:43 AM, Jeffrey Yasskin <jyasskin@google.com>
wrote:

> I think we're using
> http://www.ti.com/ww/en/wireless_connectivity/sensortag/ to write some
> test apps. The apps at
>
> https://github.com/GoogleChrome/chrome-app-samples/tree/master/bluetooth-samples
> don't include it though.
>
> Even an app that uses a proprietary protocol might be interesting to
> poke at, though. GATT exposes a partially self-describing tree, so you
> might be able to figure out what each part does, and then write an app
> against that.
>
> Re Cary, I'm probably going to want to test with that sort of headset
> a couple months from now. I'll ask when I'm closer to being able to
> use it productively.
>
> Thanks,
> Jeffrey
>
> On Thu, Aug 21, 2014 at 7:58 AM, Marcos Caceres <marcos@marcosc.com>
> wrote:
> > Hi All,
> > during last week's call we decided that a few of us should buy some blue
> tooth devices on which to prototype that API.
> >
> > I've been looking on Amazon for a few things, but I'm worried that the
> devices will be tethered trough a proprietary protocol to an native app
> (over bluetooth, of course). My question is, does anyone have any
> recommendations for devices that I could purchase that will (more or less)
> work for our experimentation?
> >
> > Thanks!
> >
> > --
> > Marcos Caceres
> >
> >
> >
>
>