Status Update
No update yet.
Comments
co...@punchthrough.com
Upon further testing, this issue appears to be completely random. On a fifth reboot, I'm now able to get past the onCharacteristicRead phase successfully, after which I'm running into a different issue covered in
ab...@gmail.com
vi...@google.com Restricted+
vi...@google.com
The logs provided in
For steps to capture a bug report, please refer:
Capture the issue in a screenshot
Press the volume down and power buttons simultaneously. The image will appear in the picture gallery. Attach the screenshot image to this issue.
Note: Please avoid uploading directly to the issue using attachments. Please upload to google drive and share the folder to android-bugreport@google.com, then share the link here.
vi...@google.com
Thanks for the inputs. From the provided logs in error code: 133, also could not find the traces of bond states changed from BONDED to NOT BONDED or BONDED to BONDED.
To proceed with further investigation, could you please share a sample app with us and also a full bugreport after reproducing the issue.
co...@punchthrough.com
The issue was observed in a proprietary app that I replaced the package name to be something generic. Unfortunately when the issue happened I did not capture a bug report, the only thing I had was the Logcat output attached in the original issue description.
I am now having trouble reproducing the issue. It is unclear what caused the system to get into that state where onCharacteristicRead is no longer surfaced for a read on an encrypted characteristic.
vi...@google.com
vi...@google.com
Our development team has fixed the issue you have reported, hence closing this. Please feel free to create a new bug along with the relevant details if you encounter it again.
co...@punchthrough.com
Thank you! Any idea when this will make a public build for Pixel devices?
Description
Ever since updating my Pixel 6 to the Android 13 September update (
TP1A.220905.004), I have been unable to read the value of an encrypted Bluetooth Low Energy GATT characteristic.Specifically, upon issuing a
readCharacteristicBluetoothGatt, and upon accepting the pairing confirmation dialog (twice!), theonCharacteristicReadThis is a big issue because reading an encrypted value is what kicks off the Bluetooth bonding process via an insufficient authentication handling within the operating system's Bluetooth stack, and being able to obtain the value of the characteristic is what informs the app that bonding has successfully completed.
Repro steps
onCharacteristicReadExpected behavior after step 4 is for the OS to deliver an
onCharacteristicReadGATT_SUCCESSstatus and with the read value alongside it.