Android的BLE 4.3 onDescriptorWrite扶持特性通知返回128状态 [英] Android BLE 4.3 onDescriptorWrite returns status 128 on enabling characteristics notification

问题描述

使用使特性问题上的新的Andr​​oid 4.3 BLE：

A question on enabling characteristics using the new android BLE 4.3:

我没有得到从BLE设备的任何通知，虽然我使用异步队列启用通知的特征一个接一个。

I am not getting any notification from the BLE device though I enable notification on characteristics one by one asynchronously using a queue.

我也写有UUID00002902-0000-1000-8000-00805f9b34fb与ENABLE_NOTIFICATION_VALUE描述符。

I also write the descriptor with UUID "00002902-0000-1000-8000-00805f9b34fb" with ENABLE_NOTIFICATION_VALUE.

我按照谷歌从SDK文档从各种论坛的建议，以及建议。

I have followed the recommendation from Google sdk doc and as well suggestions from various forums.

通过我得到onDescriptorWrite状态= 128的方式。任何想法，这是什么状态表示？

By the way I get status = 128 on "onDescriptorWrite". Any idea as what this status means?

我去谷歌直通code，并没有看到有这方面的信息。即使源$ C ​​$ C不抛出任何光线如何此状态被设定。

I went thru google code and did not see any info on this. Even the source code does not throw any light as how this status is being set.

让我知道如果你们任何人都有这样的经历，当你启用了身体媒体设备的通知。也有时我得到的描述符写状态133。我用最新的Nexus 7为我的测试。

Let me know if any of you have experienced this when you enabled notifications for the body media device. Also at times I get status 133 on descriptor write. I use latest Nexus 7 for my tests.

推荐答案

我有同样的问题，并通过禁用和重新启用蓝牙接口解决它。

I had the same problem, and solved it by disabling and reenabling the bluetooth interface.

Android的BLE堆栈似乎还很不成熟，并从不稳定问题的困扰。

The Android BLE stack seems to be still immature and suffers from instability problems.

这篇关于Android的BLE 4.3 onDescriptorWrite扶持特性通知返回128状态的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！