3.3.1.2 Continual Bluetooth Pairing Requests

[32423676573]

Using Omnipod Dash. The Bluetooth Pairing Requests started mid-pod as soon as I upgraded from. 3.3.1.0 to 3.3.1.2.

Each time AAPS connects to the pod I receive a series of 3 pairing requests, with the device matching the MAC of the pod.

Accepting the pairing request breaks connectivity between AAPS and the pod. Once the pod is unpaired the communication works.

In this state every few minutes my phone is flooded with pairing requests as AAPS sends instructions to the pod, or each time I change a setting.

Will upload logs.

[olorinmaia]

I'm guessing your on android 15. Did you have issues with Dash before upgrading to 3.3.1.2?

[32423676573]

Hey Alf, You're right, My device is a OnePlus 11 5G on oxygen OS 15 (Android 15). I've confirmed it's 3.3.3.2 specific as I've rolled back to 3.3.1.0 and the Bluetooth prompts went away. Let me know if there's anything else I can provide to assist. -------- Original Message --------On 2025-01-16 4:45 p.m., Alf Einar Johnsen wrote: I'm guessing your on android 15. Did you have issues with Dash before upgrading to 3.3.1.2? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***> [ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "#3749 (comment)", "url": "#3749 (comment)", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[olorinmaia]

Hi again! I would like to know if you got a stable connection to dash with android 15 in 3.3.1.0😉

[32423676573]

You got it. No problems at all with Android 15 on 3.3.1.0 -------- Original Message --------On 2025-01-16 4:52 p.m., Alf Einar Johnsen wrote: Hi again! I would like to know if you got a stable connection to dash with android 15 in 3.3.1.0😉 —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***> [ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "#3749 (comment)", "url": "#3749 (comment)", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[olorinmaia]

@MilosKozak also see my comment in #3471 (comment)

I think the best way forward is to revert this change for Dash in Master branch or keep it in a separate branch. If you want to keep it in Master we should make it an option in Dash settings defaulted off.

I got a strong feeling that for many it will make things worse. And for the ones having issues they can try enabling option for manual bonding.

[m4nnihuber]

I am having same issues regarding Android 15.
see Issue #3746
Also no Problems on 3.3.1.0 and below

[mjhuisman]

Here same problem: Android 15 with dash at 3.3.1.0 no issues, but at 3.3.1.2 i have to bond pod, but after bonding its impossible for aaps to connect. Aaps got stuck with handshaking.
Im using Xiaomi Redmi note 13 pro.

[m4nnihuber]

Looks like it gets way better when i delete old "twi boards" in bluetooth list before starting new pod

[Not-AriStienfeld]

Same issue, it goes away after unpairing and repairing but comes back after less than a minute

[MilosKozak]

8abfbd5