Obsolete
Status Update
No update yet.
Comments
iv...@gmail.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.
iv...@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.
st...@piobyte.de
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.
xp...@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
iv...@gmail.com
Nexus 5x is supported but not nexus 6p. How weird...
sa...@google.com
Please enable Volte in India for Jio sim on Nexus 6P
Description
When connecting to a BLE device that requires bonding through a PIN, the system no longer presents the dialog to input the PIN and instead broadcasts the state BONDED directly.
What I see from my app is that after calling BluetoothDevice.createBond(), the system broadcasts ACTION_BOND_STATE_CHANGED with EXTRA_BOND_STATE = BOND_BONDING and EXTRA_PREVIOUS_BOND_STATE = BOND_NONE (everything ok until now). Then, without asking for a PIN, it broadcasts ACTION_BOND_STATE_CHANGED with EXTRA_BOND_STATE = BOND_BONDED and EXTRA_PREVIOUS_BOND_STATE = BOND_BONDING.
The Bluetooth settings in the system settings also reports the bonding completed without asking for the pairing PIN.
Although the connection is successful and I can read non-encrypted characteristics, I don't receive any answers for the encrypted characteristics. I don't receive any GATT_INSUFFICIENT_AUTHENTICATION or GATT_INSUFFICIENT_ENCRYPTION errors either, simply no response.