Fixed
Status Update
No update yet.
Comments
su...@google.com
It seemed huawei or google has not enable VoLTE(of Nexus 6p, both H1511 and H1512 variant) in certain carriers that VoLTE has been officially enabled.
uw...@gmail.com
So if i post here is there a chance they will in future software updates? Well it works on the nexus 5x so why google or Huawei disabled it on there premium offering the 6p? Currently using a phone without the ability to call because my network only uses lte no 2g or 3g network.
le...@gmail.com
Hi,
Can you provide the below requested information to better understand the issue:
Android bug report:
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 bug report to google drive and share the folder to android-bugreport@google.com, then share the link here.
Can you provide the below requested information to better understand the issue:
Android bug report:
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 bug report to google drive and share the folder to android-bugreport@google.com, then share the link here.
le...@gmail.com
Hi,
We have passed this defect on to the development team and will update this issue with more information as it becomes available.
Thanks
We have passed this defect on to the development team and will update this issue with more information as it becomes available.
Thanks
su...@google.com
Nexus 5x is supported but not nexus 6p. How weird...
le...@gmail.com
Please enable Volte in India for Jio sim on Nexus 6P
su...@google.com
Google has not enabled volte for India
Is this not a discrimination against Indians
Is this not a discrimination against Indians
be...@gmail.com
Please enable VoLTE asap
pk...@gmail.com
We have observed this issue from Android OS 10 to Android OS 13 versions....Observations - 1. Sometimes it does not reconnect to already paired device when disconnection interval is less (Reconnection failure is very less when interval of disconnection with paired device is less). 2 It mostly fails to reconnect when disconnection interval is more say more than 40-50 minutes. (Reconnection failure is very high in this case but sometimes device gets reconnected).The solution we have implemented is to redirect user to Android Bluetooth setting and unpair the same device....It works pretty well and devices are reconnected immediately.....Seems to be an issue of Android bluetooth stack not refreshing the paired device cache. (The existing pairing packet that needs to cleared is not working and when manually removing the pairing removes the old pairing packet). But this is just a patch. It impacts auto reconnection feature and user has to intervene. Our is very critical medical product. Can not launch it because of this issue.
ao...@gmail.com
Hi team,
Please be advised that a large group of people are affected by this issue and want the fix ASAP. Kindly keep the thread updated with the progress.
Please be advised that a large group of people are affected by this issue and want the fix ASAP. Kindly keep the thread updated with the progress.
ao...@gmail.com
Please modify the priority as Critical or atleast High. We are not able to make calls
Description
- Steps to reproduce the problem (including sample code if appropriate).
Initiate BT scan from the app, use primary service UUID as a filter.
Wait for the scan result, initiate connect.
Run step above for 5 peripherals (app is working with 5 peripherals simultaneously).
Observe peripherals are not connecting.
- What happened.
When calling BluetoothGatt.connect(...) for a peripheral, Android 13 system doesn't pass command to the BT controller to whitelist it so as a result, there is no attempt to initiate connect and the OS instead returns timeout (error code 133) to the app in 30s.
Relevant bugreport logs with timestamp:
08-18 10:31:04.523 10312 13808 15650 D BluetoothGatt: connect() - device: 60:98:66:5D:A8:D5, auto: false
08-18 10:31:04.523 10312 13808 15650 D BluetoothGatt: registerApp()
08-18 10:31:04.523 10312 13808 15650 D BluetoothGatt: registerApp() - UUID=9ae527eb-8527-4585-903e-e0e22c3e5b6a
08-18 10:31:04.526 1002 24434 24530 I bluetooth: packages/modules/Bluetooth/system/stack/gatt/gatt_api.cc:1020 GATT_Register: Allocated name:GattClient uuid:5c365b87-6d1a-07e2-907a-74d84aefa118 gatt_if:8 eatt_support:0
08-18 10:31:04.527 10312 13808 20175 D BluetoothGatt: onClientRegistered() - status=0 clientIf=8
08-18 10:31:04.530 1002 24434 24490 I bt_btif_gattc: packages/modules/Bluetooth/system/btif/src/btif_gatt_client.cc:365 btif_gattc_open_impl: Transport=2, device type=2, address type =0, phy=1
08-18 10:31:04.530 1002 24434 24530 I bt_stack: [INFO:gatt_attr.cc(882)] gatt_sr_init_cl_status: bda=60:98:66:5d:a8:d5, cl_supp_feat=0000, aware=1
08-18 10:31:04.531 1002 24434 24530 I bluetooth: packages/modules/Bluetooth/system/stack/gatt/gatt_main.cc:346 gatt_update_app_use_link_flag: check_acl_link is false, no need to check
- Phone models/OS build:
Android 13, Pixel 4XL, Pixel 5 (OS build TP1A.220624.014)
- What you think the correct behavior should be.
Calling BluetoothGatt.connect should whitelist the device on the BT controller level. Should work when connecting up to 5 peripherals.
- Is this a security related issue? Yes/No
No