Kieron Gillespie

I am not my gatt characteristic is a standard write request with authorization required. I am not seeing the failed callback coming back to any of the callback functions registered...

This is on a Nexus 7 which in the past pairing has been a difficult pain. I tried on a different android device I am not getting this error.

So I guess I'll walk through the cycle connecting to a device, so for note these steps, except for the differences between how iOS and Android handle discovering are the...

Well I think when ever I had this issue with android devices while I was writing native BLE apps I would simply take the status 137 as a "Darn it...

I gave up trying to use this plugin for my needs. https://github.com/aporat/cordova-plugin-fetch I can recommend this plugin. It behaves like standard fetch API which everything pretty much uses and supports....

Also hoping to have this problem resolved

`Downloading Bootloader ... **** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be...

This would be a write coming from the central not internal on the embedded device it's self. Yes .writeValue works, write with response from a central device to the Curie...

So the Curie BLE stack doesn't handle long writes? There are methods in many BLE stacks, Android and iOS both support, to send what is know as a long write,...

[longWriteTest.zip](https://github.com/01org/corelibs-arduino101/files/810854/longWriteTest.zip) In this example we keep printing the I'm alive message on an interval. Once we attempt to write to the characteristic with UUID "bfe433cf-6b5e-4368-abab-b0a59666a403" with any length of data...