Bluetooth Issue

chas1776

Hello all. This is my first post. I've been using GrapheneOS for a week and I'm liking it. I have play services installed and it no longer ignores my dns blocklist and does not overide my vpn. The only thing I've missed is extended unlock via my garmin watch.
Until now....
I have a Camp Chef smoker that connects to bluetooth. When it is connected, I get notifications for meat temps, etc. At first, it connects fine but after a period of time, I get a notification from the native bluetooth app- 'For your security, forget this device, then pair it again'. Repairing works until I open the app again to check things then I get the same notification. I have dug through all of the setting and reinstalled the app to no avail.

sank-swooned-ditzy

Same issue here, with a Wear OS device. That can't be used anymore.
It used to works fine for several months... Maybe one of the recent GrapheneOS version broke it.

PhantomRunner

GrapheneOS has the ability to automatically disable bluetooth and wi-fi also, after a set time for inactivity. This maybe what you're encountering. Go to settings/security & privacy/exploit protection and adjust it accordingly to see if the helps.

sank-swooned-ditzy

My "Turn Off Bluetooth Automatically" was set as never, and I still get the same issue.

mmos

I've got a same issue with a WearOS device. I gave up after a few cycles of re-pairing and forced device wipe.

There's an r/GooglePixel thread with a similar issue where the Google support responded. Maybe we could make some noise there for some attention.

I did a small research where does "For your security, forget this device, then pair it again" come from. It seems that this string is defined in the strings.xml file under bluetooth_key_missing_message key. My current guess is that the security key for the paired device is getting wiped somehow on the phone (dunno, why). When this happens, there's no coming back – "device pair" is no longer usable and the only possible action is to remove the entry itself.

Perhaps I've got it wrong. That's how I understand this issue for now.