Status Update
Comments
ra...@google.com <ra...@google.com> #3
For us to further investigate this issue, please provide the following additional information:
Steps to reproduce
What steps are needed to reproduce this issue? Frequency of occurrence?
Expected output
What is the expected output?
Current output
What is the current output?
Android build
Which Android build are you using? (e.g. UQ1A.240205.002)
Device used
Which device did you use to reproduce this issue?
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report to google drive and share the folder to android-bugreport@google.com, then share the link here.
me...@gmail.com <me...@gmail.com> #4
Description:
I have problems when I try to pair a bluetooth device based on RN-42 Microchip module, the android's bluetooth interface says "It's not possible to connect to (device name)" (Image1).
This issue appeared since Android 14 was released, a few updates later this bug was fixed but now it's failing again (2 or 3 months ago). It works fine on Android 13 and previus versions.
My application works with the bonded devices list then I cannot do anything to solve this issue.
This issue was tested on Samsung A14 (SM-A146M):
- Android version 14
- Android build: UP1A.231005.007.A146MUBU4CXE2
- Kernel version: 5.15.123-android13-3-28577532 #1 Fri May 3 01:13:00 KST 2024
- Last update: July 1, 2024
Thanks in advance.
Regards
ra...@google.com <ra...@google.com> #5
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report to google drive and share the folder to android-bugreport@google.com, then share the link here.
cb...@gmail.com <cb...@gmail.com> #6
However, the issue is still present and I did create a Bug report now which I uploaded to Google Drive:
I hope you can give us a hint how to resolve the issue.
Kind regards,
Claudio Becker-Foss
ti...@gmail.com <ti...@gmail.com> #7
ti...@gmail.com <ti...@gmail.com> #8
ti...@gmail.com <ti...@gmail.com> #9
ra...@google.com <ra...@google.com> #10
Reply to
Thanks for the information. For us to further investigate this issue, please provide the following additional information:
- Can you confirm if this issue is reproducible on Pixel/Nexus device? If yes, please share the bugreport.
cb...@gmail.com <cb...@gmail.com> #11
me...@gmail.com <me...@gmail.com> #12
Reply to
Hi I can not provide a bug report or a sample project because the error that I got It's outside from my App, my application doesn't throw me an error. The issues is in Android's bluetooth Interface (please refer to Image1). Maybe you can guide me how to give you a report from Android's bluetooth.
Thanks
ra...@google.com <ra...@google.com> #14
Reply to
We have shared the steps in
ra...@google.com <ra...@google.com> #15
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
cb...@gmail.com <cb...@gmail.com> #16
I got access requests to the bureport files from two people with @
ra...@google.com <ra...@google.com> #17
Reply on
Thanks for the information. Please ignore the request for access to the bugreport file.
cb...@gmail.com <cb...@gmail.com> #18
When can we expect a feedback? We have customers waiting for a solution of this issue.
cb...@gmail.com <cb...@gmail.com> #19
cb...@gmail.com <cb...@gmail.com> #20
vi...@google.com <vi...@google.com> #21
For further investigation, please provide the detail (like product name) of the remote device you're using that has the RN-42 Microchip module.
cb...@gmail.com <cb...@gmail.com> #22
Sure. How can I send you a direct message? I can give you all the details but would prefer to not do that in a public thread.
ra...@google.com <ra...@google.com> #23
ra...@google.com <ra...@google.com> #24
Reply on
You can put all details in Google doc and share to
cb...@gmail.com <cb...@gmail.com> #25
Here is the link to the shared directory. I put the manual of our product in the directory. As far as Android is concerned it is as simple as using RN-42 to make a Bluetooth connection to Android. Then our app uses the Bluetooth connection to exchange serial data. But the issue under discussion here is, that the pairing does not work anymore in the first place. So the app is not even in the picture.
cb...@gmail.com <cb...@gmail.com> #26
ch...@gmail.com <ch...@gmail.com> #28
ra...@google.com <ra...@google.com> #29
Thanks for reporting this issue. Could you please check and confirm if this issue is still reproducible on the latest Android-16 beta build? Thanks
Description
Description has been deleted.