Android: BLE read of a characteristic longer than 21 byte fails
Reported by
brianbre...@gmail.com,
Dec 4
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36 Steps to reproduce the problem: 1. Connect to a BLE health device 2. Read the Device Information Service Reg-Cert-Data-List characteristic that is correctly populated for the device 3. It will fail The Roche glucose monitor and Omron BP cuff have such What is the expected behavior? The characteristic shall be read What went wrong? The read fails. Did this work before? No Chrome version: 72.0.3609.3 Channel: stable OS Version: 10.0 Flash Version: It seems the Chromebook is having issues with a 'blob' read
,
Dec 4
We need clarification on this bug (and the others you filed). You have logged them against the Windows platform but then comment on "Android" and "Chromebook" for them. Can you clarify what platform you are running them on? Is this ARC on a chromebook, Android alone? Or Windows? Which API are you calling?
,
Dec 11
I am running an Android app on an HP Chromebook x360 11 G1 EE. There is a sticker on the Chromebook that says 'Intel Inside'. I am no master at using this and all I see on it are Android apps.
,
Dec 11
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 11
I am using several of the Bluetooth APIs. In this particular case it centers on the BTLE APIs. The failure is on a ReadCharacteristic (The RegCertDataList Characteristic of the DIS).
,
Dec 11
,
Dec 11
I am further questioning this behavior because a sniff reveals an invalid offset error from the device (though the offset is fine). Though all other Android platforms let this error by the Chromebook aborts. Since I am assuming (perhaps incorrectly) this platform should behave like all other Androids it appeared to be a Chromebook error. I don't understand the difference in behavior and I am not sure what is correct.
,
Dec 11
,
Dec 12
,
Dec 12
Heard from the partner that they are confident that this issue can be reproduced with any touchscreen Chromebook. They are using an HP Chromebook x360 11 G1 EE. (http://www8.hp.com/us/en/products/laptops/product-detail.html?oid=15747870). I have inquired with the partner regarding the bluetooth devices that they seem to be having issues to see if we are able to receive loaner devices for testing.
,
Jan 2
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by swarnasree.mukkala@chromium.org
, Dec 4