Bluetooth reconnection BLE Watch

cchalk commented 2 months ago

Issue type

User interface

Device

Peridot

crDroid version

crDroid 10

Exact version / Build date

10.7/2024-08-26

Bug description

My Amazfit watch never connects to my POCO F6 (peridot).

The pin is showing on my watch and matches what's shown on the phone screen.

I try and pair them but it keeps reconnecting and goes in a loop asking for different pin codes.

Other Bluetooth devices work like my Bluetooth earphones.

https://paste.crdroid.net/6neG9W

Steps to reproduce

open Bluetooth settings to add a new device
accept pin code on watch
accept pin code on phone
looping pin code entry

Relevant log (logcat/build log)

08-28 02:23:17.211 W/BluetoothMetrics(23410): packages/modules/Bluetooth/system/gd/os/android/metrics.cc:428 - LogMetricManufacturerInfo: Failed for xx:xx:xx:xx:27:54, source_type 1, source_name N:SDP::DIP::0x0000, manufacturer 0x0000, model 0x0000, hardware_version 0x0000, software_version , MAC address type 0 MAC address prefix 216 128 60, error -19
08-28 02:23:17.211 W/BluetoothMetrics(23410): packages/modules/Bluetooth/system/gd/os/android/metrics.cc:106 - LogMetricRemoteVersionInfo: Failed for handle 8, status 0x00, version 0xff, manufacturer_name 0xffff, subversion 0xffff, error -19
08-28 02:23:17.211 W/BluetoothMetrics(23410): packages/modules/Bluetooth/system/gd/os/android/metrics.cc:84 - LogMetricLinkLayerConnectionEvent: Failed to log status 0x0000 , reason 0x0001, from cmd 0x000fffff, event 0x0003,  ble_event 0x0fff, for xx:xx:xx:xx:27:54, handle 8, type 0x0001, error -19
08-28 02:23:17.213 W/btm_acl (23410): BTM_SetLinkSuperTout: Role is peripheral so unable to set supervision timeout:80.00ms bd_addr:xx:xx:xx:xx:27:54
08-28 02:23:17.214 W/BluetoothMetrics(23410): packages/modules/Bluetooth/system/gd/os/android/metrics.cc:311 - LogMetricClassicPairingEvent: Failed for xx:xx:xx:xx:00:00, handle 8, hci_cmd 0x00000411, hci_event 0x0fff, cmd_status 0x0fff, reason 0x0fff, event_value 0, error -19
08-28 02:23:17.214 W/btm_acl (23410): acl_peer_supports_sniff_subrating: Checking remote features but remote feature read is incomplete
08-28 02:23:17.214 W/btm_acl (23410): BTM_ReadRemoteVersion: Remote version information is invalid
08-28 02:23:17.223 E/bt_btu_hcif(23410): btu_hcif_hdl_command_complete: Command complete for opcode:0x80d should not be handled here
08-28 02:23:17.229 W/BluetoothMetrics(23410): packages/modules/Bluetooth/system/gd/os/android/metrics.cc:311 - LogMetricClassicPairingEvent: Failed for xx:xx:xx:xx:00:00, handle 8, hci_cmd 0x00000411, hci_event 0x000f, cmd_status 0x00ff, reason 0x0001, event_value 0, error -19
08-28 02:23:17.243 W/GmsStrictMode(16028): DISK_READ [CONTEXT service_id=256 ]
08-28 02:23:17.243 W/GmsStrictMode(16028): android.os.strictmode.DiskReadViolation
08-28 02:23:17.243 W/GmsStrictMode(16028):  at android.os.StrictMode$AndroidBlockGuardPolicy.onReadFromDisk(StrictMode.java:1679)

Screenshots or videos

No response

Solution

No response

Additional context

No response

Acknowledgements

[X] I've checked device is officially supported (for device specific reports and not source related).
[X] I'm running latest version available on crdroid.net for this device
[X] I have searched the existing issues and this is a new and no duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] I filled out all of the requested information in this issue properly.

gwolf2u commented 1 month ago

can you try on latest build?

cchalk commented 1 month ago

Still present in 10.8 September 15th build.

oczkers commented 1 month ago

I've got exactly the same problem on Redmi Note 13 Pro 5g and Amazfit Balance full log

Vikas-V2 commented 1 month ago

That Xiaomi own issue unless xiaomi fix their firmware you have to wait or use stock ROM

crdroidandroid / issue_tracker