If I set write type WRITE_TYPE_SIGNED, I get status code as 135 and write fails. However when I used write type as WRITE_TYPE_NO_RESPONSE I getsuccess status code. My device advertises WRITE_NO_RESPONSE as property of characteristic which I am trying to write.
What else I can try for this? On Wednesday, September 25, 2013 1:53:58 PM UTC+5:30, gjs wrote: > > Hi, > > So far I've only used BLE successfully with devices that don't need to use > encryption, however the docs seem to infer that BluetoothGattCharacteristic > requires setWriteType (int writeType) where writeType is WRITE_TYPE_SIGNED > - Write characteristic including authentication signature - prior to > performing encrypted write operations ? > > See > http://developer.android.com/reference/android/bluetooth/BluetoothGattCharacteristic.html#setWriteType(int) > > Also as far as I know there is no need to explicitly pair with BLE > devices, it just happens automagically. You just scan for available devices > and connect with the ones your interested in using. > > Hope that helps. > > Regards > > > On Tuesday, September 24, 2013 9:28:40 PM UTC+10, Ashwini wrote: >> >> I am developeing an application which can talk to few smart(bluetooth >> 4.0) devices. I tested the code on Nexus 4 running Android OS version 4.3. >> >> The application is able to connect to nordic chip programmed as heart >> rate monitor. For this device, I am able to read services, characteristics >> and even get updates for heart rate values. >> However, when I programmed the same chip for encrypted characteristics, I >> am facing some issues. >> >> - Connection drops sometimes after write characteristic descriptor is >> performed. >> - The devices once paired with phone can not be un-paired. (This is >> known issue and confirmed the same from android issue tracker). >> - Getting following statement in logs quite often but not able to >> understand the status code - 133. >> >> D/BluetoothGatt(1780): onClientConnectionState() - status=133 clientIf=4 >> device=CC:F3:A5:4D:CB:3F >> >> >> - The phone also logs this statement for state change. >> >> In stable state, received invalid newState: 10 >> >> >> >> I do not seem to find a way to instruct the phone to get paired with the >> chip. Also there is no way to specify that we want to perform *encrypted >> read-write operations*. >> >> Any help is appreciated. >> >> >> -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
