-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bluetooth connection issues AAPS 3.2.0.4 and Accu-Chek Insight pump and with Dexcom G7 CGM (Samsung A54B with Android 14) #3617
Labels
Comments
PieterGit
changed the title
Bluetooth connection issues AAPS 3.2.04 and Accu-Chek Insight pump and with Dexcom G7 CGM (Samsung A54B with Android 14)
Bluetooth connection issues AAPS 3.2.0.4 and Accu-Chek Insight pump and with Dexcom G7 CGM (Samsung A54B with Android 14)
Dec 14, 2024
provide logfiles |
Pixel 7 with GrapheneOS build 2025010700 (updated today), I lost connection to Insight with AAPS 3.3.1.0. Some logs below, if it helps...
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context:
I'm having a lot of(bluetooth) connection issues between both APS-Insight Pump and the Samsung Phone and Dexcom G7 CGM.
I seems to be more severe with Android 14, and especially since the "Samsung 1 November 2024 security upgrade"
(OneUI 6.1, Android version 14, A546BXXUBCXK1 / A546BOXMBCXK3 / A546BXXUBCXK3).
Example
I added an Automation to set a Nightscout notification if there has not been 16 minutes or more no contact with the pump.
That yields this example where the phone was approx 1 meter from PWD. After a microbolus of 0.19 at 09:02 it reported no connection at 09:20 and it the connection was restored at 09:42 with a 0.5 SMB.
If others experience similar issues please add info on phone/cgm/pump and android (14) version you are experiencing this.
I managed to get it better. I think using the Samsung Apps in Android 14 likeGood Guardians and Galaxy app booster seems to have made it occur less, see https://dontkillmyapp.com/samsung
I will investigate logs further and see if I can get more details.
The text was updated successfully, but these errors were encountered: