nightscout
Dash BT connection issues
Now that I don't know what to do anymore I ask here. Dash lost connection after a couple of hours after connecting. Tried restarting BT, AAPS and phone. Deleted permission for devices nearby for other apps. Enabled/disabled the BT bond setting in AAPS. I really don't know what to do, already lost 4 pods and even after updating AAPS the issue is still there. Help please 🥲 Omnipod Dash + S24+ (ignore the BG, this sh.. is stressingme out so it's going down.. just like my hope for solving this issue 🙄)
Which Android? There was fix rolled out for A16. And someone else posted similar ticket like you for A15, with some hints...
Which Android? There was fix rolled out for A16. And someone else posted similar ticket like you for A15, with some hints...
Android 15. Yes, I saw that and tried all these things, but nothing helped :/
Did you try to delete the Mac address into the pairing list, enable bond and make sure to confirm pairing?
Cordialement. Grégory
Le sam. 13 sept. 2025, 15:13, redorchid89-sudo @.***> a écrit :
redorchid89-sudo created an issue (nightscout/AndroidAPS#4153) https://github.com/nightscout/AndroidAPS/issues/4153
Now that I don't know what to do anymore I ask here. Dash lost connection after a couple of hours after connecting. Tried restarting BT, AAPS and phone. Deleted permission for devices nearby for other apps. Enabled/disabled the BT bond setting in AAPS. I really don't know what to do, already lost 4 pods and even after updating AAPS the issue is still there. Help please 🥲 Omnipod Dash + S24+ (ignore the BG, this sh.. is stressingme out so it's going down.. just like my hope for solving this issue 🙄)
547013545_24764223749857254_7984868742199395610_n.jpg (view on web) https://github.com/user-attachments/assets/d26497c3-6cac-44f9-9ed3-fe94a1589014 547024315_24764223913190571_6989258005100986059_n.jpg (view on web) https://github.com/user-attachments/assets/2a02c686-2b8c-4590-9d3e-0ddb30bd835f 547374232_24764224079857221_8279526700319294558_n.jpg (view on web) https://github.com/user-attachments/assets/8da01a05-08d4-42ba-9162-43d6eb72f793
— Reply to this email directly, view it on GitHub https://github.com/nightscout/AndroidAPS/issues/4153, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFY4TENBJXMMQMRI53CUSO33SQJ6TAVCNFSM6AAAAACGNI7JN2VHI2DSMVQWIX3LMV43ASLTON2WKOZTGQYTGNBVGI3TSMA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Did you try to delete the Mac address into the pairing list, enable bond and make sure to confirm pairing?
Cordialement. Grégory Beloncle
Le sam. 13 sept. 2025, 15:13, redorchid89-sudo @.***> a écrit : …
Yes, I always delete before pairing a new one and aaps always asks if I want to pair. I have enabled bond constantly for the moment, the new pod I put on is going well so far, but it's only ~3h. :/
Did enabling bond constantly solve the issue?
No, nothing is solved.
Since last week, I used two Omnipods. One died yesterday with a similar error message as described here. I use an Google Pixel 8a with Android16 and AAPS 3.3.3.a+aisf3.1.0. The option „Bond BT device on Android 15+ (Pixel phones workaround)“ is enabled. During starting a new pod, I had another error message, short before inserting the new cannula „Allgemeiner Fehler: app.aaps.pump.omnipod.dash.driver.comm.exceptions.ConnectException: Service not found: xxxxx“. Disabling and enabling bluetooth in the backround helps to go further starting the pod and inserting the cannula. Sorry for posting these two errors in two different issues.
Problems solved: Don‘t enable the „Bond BT device on Android 15+ …“ on Android 16. This option is for Android 15 only. The „+“ sign in the name of this option should be removed.
