Infeasible
Status Update
No update yet.
Comments
ba...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
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.
Expected output
What do you expect to occur?
Current output
What do you see instead?
Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
NOTE: Please upload the files to Google Drive and share the folder to android-bugreport@google.com, then share the link here.
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.
Expected output
What do you expect to occur?
Current output
What do you see instead?
Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
NOTE: Please upload the files to Google Drive and share the folder to android-bugreport@google.com, then share the link here.
ba...@google.com
ok, I did some more research, turns out that callback notification goes to the if we press "cancel" button but goes wrong when authentication succeeds
as you can see in the attached project
if you open the bio-prompt in the 1st Fragment and authenticate
and after that you go to the 2nd Fragment and authenticate in the bio-prompt
callback notifies the Fragment1 instead of the Fragment2 as you can see in the logs
expected result is that Fragment2 is notified instead of Fragment1
also if you first go to Fragment2 and after that you go to Fragment1 always opening the prompt and doing the authentication
Fragment2 is notified instead of Fragment1
funny thing is that doing cancel instead of authentication notification works ok
https://drive.google.com/open?id=1ZVhp9sFBJ6pa1bKzHg1AM5tF5XnmyFMM
as you can see in the attached project
if you open the bio-prompt in the 1st Fragment and authenticate
and after that you go to the 2nd Fragment and authenticate in the bio-prompt
callback notifies the Fragment1 instead of the Fragment2 as you can see in the logs
expected result is that Fragment2 is notified instead of Fragment1
also if you first go to Fragment2 and after that you go to Fragment1 always opening the prompt and doing the authentication
Fragment2 is notified instead of Fragment1
funny thing is that doing cancel instead of authentication notification works ok
Description
Connect a bluetooth headset first.
Acquiring a communication device via getAvailableCommunicationDevices() returns a AudioDeviceInfo.TYPE_BLUETOOTH_SCO device in the list and setCommunicationDevice() works. Also startBluetoothSco() works. Able to switch audio to bluetooth headset.
Plug in a wired headset.
- What happened:
AudioDeviceInfo.TYPE_BLUETOOTH_SCO device missing from the list returned by getAvailableCommunicationDevices() therefore can't switch audio to bluetooth headset using setCommunicationDevice(). startBluetoothSco() doesn't work.
Unable to switch audio to bluetooth headset.
This state will remain until the bluetooth headset is enabled manually by the user from the settings ("Connected devices") screen.
- What you think the correct behavior should be:
AudioDeviceInfo.TYPE_BLUETOOTH_SCO device present in the list returned by getAvailableCommunicationDevices() after a wired headset is plugged in. Able to switch audio to bluetooth headset programmatically.
Pixel 4 XL
Android 12
Build Number: SP1A.211105.002
Please also run "adb bugreport" and archive the output: