Android的BLE盖特特性WRITE_TYPE_NO_RESPONSE不工作 [英] Android BLE Gatt Characteristic WRITE_TYPE_NO_RESPONSE not working

查看:3676
本文介绍了Android的BLE盖特特性WRITE_TYPE_NO_RESPONSE不工作的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经开发了一个Android应用程序,连接到CC2540 BLE外设。

I have developed an Android app that connects to a CC2540 BLE peripheral.

当我这样做型没有反应(WRITE_TYPE_NO_RESPONSE)的特性写的,我仍然可以在应用程序级别回调onCharacteristicWrite。这种行为是正确的吗?

When I do a Characteristic write of type no response (WRITE_TYPE_NO_RESPONSE), I still get the callback onCharacteristicWrite at the app level. Is this behavior correct?

据我了解有可能是的Andr​​oid设备和外围之间出现低水平的确认。

I understand there is probably a low level acknowledgement that occurs between the Android device and the peripheral.

但我问的原因是因为这是造成了一个问题,当我收到此回调,这是速度变慢的应用程序,我只能给写。

But the reason I am asking is because this is causing an issue where I can only send a write once I have received this callback, which is slowing things down in the app.

此行为的任何光线将AP preciated它。

Any light on this behavior would be appreciated it.

谢谢,

推荐答案

我没碰上,当我试图做一些性能测试同样的问题,发现,当我用WRITE_TYPE_DEFAULT具体我停下得到响应。有可能是与被引起逆行为的android常数的错误,但我不是很不清楚。

I did run into the same problem when I was trying to do some performance testing and found that when I used the WRITE_TYPE_DEFAULT specifically I stopped getting a response. There might be a bug with the android constants that is causing inverse behavior, but I am not quite not sure.

这篇关于Android的BLE盖特特性WRITE_TYPE_NO_RESPONSE不工作的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆