Bluetooth pairing error

lawman

I can seem to pair my 7s on latest gos to my car anymore.

It used to work before I reset my phone.

I've tried pairing from secondary and primary profiles

Tried resetting Bluetooth via developer options in owner profile

Nothing works.

When trying to pair in secondary profile or gives me error "can't communicate with " then adds car Bluetooth address similar to Mac address.

In owner profile or didn't give me any error and just stops after trying for a while.

Most other devices connect fine, except for eufy a1 smart scales which also have same problem. Won't connect to me but connect fine to everyone else.

How can I resolve this please as it used to work before I reset my phone look my car at least.

I can see a lot of Bluetooth options in developer mode but haven't touched anything.

lawman

lawman I meant 7a

Johnnyloans

lawman

Developer options can cause random weird, issues
Settings > system > developer options > very top is an off toggle > Reboot device

This'll help narrow down the issue:
Attempt to connect to the car then save the logs after it fails
Settings > apps > all apps > 3 dots top right > show system > Search "blue" > Tap bluetooth > View logs

Copy and paste the logs into a message here, Select it all (ctrl + A works), then push the exclamation mark ( ! ) caution symbol on the row with bold, italicize, etc. (This puts the big log into a collapsible button to click on.)
Now type any message you'd like to add.

lawman

I'll do this and report back.

A few questions:

1) Should I wipe log before trying to connect to car so you can focus on issue at hand? I can't see an option for this.

2) LOG BUFFER: should I log radio buffers? This is unchecked ATM

3) LOG LEVEL : should I log verbose, debug, error level?

After adding developer options and resetting Bluetooth, it connected fine to eufy smart scales in secondary profile.

Car still refused to connect in either secondary or primary profiles. this is with developer off initially not also on. I tried primary first after turning developer on, as that used to work before.

I'll report back .

Thanks

Johnnyloans

lawman

1) rebooting the phone wipes the logs
2) radio too (check all of them)
3) verbose

Also, making note of the UTC time when you try to connect via bluetooth helps. ( https://duckduckgo.com/?t=ffab&q=utc%20time )

Johnnyloans

Might be this issue
https://issuetracker.google.com/issues/491346038

Since google won't give us QPR3, maybe we gotta wait till QPR4 or android 17? i think they don't do QPR4..

Johnnyloans

lawman

Thanks.

Unfortunately, it is the same issue as the one reported below. Google says they already fixed it. I think the next AOSP release from google is in the summer. Sorry mate.

Feel free to delete that zip file

Johnnyloans https://issuetracker.google.com/issues/491346038
Same issue reported on GOS: https://github.com/GrapheneOS/os-issue-tracker/issues/7388

lawman

Normal and system log attached

Also attached logs before and after trying to connect

I connected about 10.22am UTC / London time

There was no option to attach here and the copy/paste was too large so link below to download

Thanks again

Download Bluetooth logs

lawman

Thanks for clarifying.

Strange that it used to work with gos before.