Bluetooth related issues
Some users have been running into issues with Omnipod DASH activation failures, Medtrum Nano connectivity problems, and other pod errors related to Bluetooth. Many of these issues can be traced to one of the following issues.
Some of these issues likely apply to other Bluetooth Insulin pumps too, the Medtrum Nano has known issues with nearby device permission as well as the Omnipod DASH.
Cannot start Omnipod with Android 16
Android 16 needs at a minimum AAPS version 3.3.2.1 for the Omnipod DASH to work correctly, as this version has fixes added to specifically address known problems introduced in Android 16 for Omnipod.
Bluetooth Battery Optimisation
Newer versions of Android have enabled Battery optimisation for the system Bluetooth app. This is known to cause some issues for Bluetooth pumps and CGMs.
If you followed the Setup Wizard and followed the configuration settings in the Bluetooth Battery Optimisation section then this setting should be correct, however if you followed an older version of this guide it’s possible you have not changed this setting.
Verify this is correctly configured if you have pump and CGM disconnections.
Apps that use the “Nearby devices” Android permission can cause connection drops and Pod activation problems
Android allows you to control what each app is able to do or access on your phone via a permission model. For each app installed you can choose to allow or deny specific permissions, e.g. access files on the device, access to Bluetooth, scan for nearby devices etc.
AAPS requires a number of specific permissions to function, one which is required to ensure that Pods work is the “Nearby devices” permission. There are many other applications which also require this permission, the community is finding that a number of applications when they are granted this permission can cause issues with activating new Pods on some devices.
Apps that use “Nearby device” permissions and are known to have caused problems:
Apps in this list have been discussed in one or more places in the community as causing problems for Omnipod DASH devices and in some cases Medtrum Nano too.
Updating the list
Ping @XiTatiON on #omnipod-dash Discord channel to discuss apps to be added to this list.
myBMW MyBMW interrupted Medtrum Nano and Omnipod DASH. The MyBMW app prompts regarding permission for “find nearby devices” only once, if you don’t grant it, it still works absolutely OK
Amazon Alexa Removing “Nearby devices” for Alexa app resolved problem for some people but will break the ability to pair Matter IoT devices
MINI app Appears the app is based on myBMW app and might mirror its behavior as a result
BM2 Solar Battery Monitoring app, used in some camper van and camping solar setups: when the app was running, it prevented activation of a new Pod. Force Stopping the app while activating a new pod is a workaround to the issue. Running the app after that didn’t appear to interfere with Dash functionality (On a Pixel 8 Pro running A16).
How to revoke “Nearby device” permissions for other apps:
If you are facing issues activating a new Pod and you are running on the correct supported version of AAPS for your version of Android, it may be necessary to revoke the permission for other apps while activating a new Pod.
Follow this procedure to revoke the “Nearby device” permission for all apps except AAPS:
Menus and settings
The screenshots and instructions in this guide are from a Vanilla Android 16 install on Google Pixel 8 Pro. Other manufacturers and devices will likely not exactly match these menus and settings descriptions, adjust the steps to suit the device you have and if you are stuck see Where to get help for dash section on how to reach out to the community for support.
Open Android settings on your phone, scroll down and press on Security and privacy (1).
Scroll down and press on Privacy controls (1).
Press on Permission manager (1).
Scroll down and press on Nearby devices (1).
Browse the list of apps and press on the app you wish to revoke Nearby devices permissions for.
In this guide Android Auto (1) is the app we will revoke the permission on.
To avoid bricking more pods we advise everyone initially to revoke the permission on all apps except AAPS.
Which app to select?
If you are unsure which app is causing you an issue, disable them all (remember to check the list of known problem apps too and start with those) and if you can spare a few bricked pods on the way, enable the permission on one new app before every new Pod activation, until you can narrow down which app specifically causes your Pod issues. If you do identify new problematic apps please let us know on the #omnipod-dash Discord channel.
To revoke the permission Press on Don’t allow (1), then Press on Don’t allow anyway (2). If done correctly you should see Don’t allow (3) as the selected Toggle option. You can now go back to the Nearby device menu by pressing the Back arrow (4) and change this setting on other apps if required.
How to re-enable “Nearby device” permissions for system apps and other apps:
If required Reference the “How to revoke ‘Nearby device’ permissions for other apps” section on how to get to the app privacy settings, then once in the Nearby device configuration proceed to 2.
Browse the list of apps and press on the app you wish to allow Nearby devices permissions for.
In this guide Android Auto (1) is the app we will allow the permission on.
You will notice that Android Auto (1) is missing in the app list after the permission is revoked. This is because the Android Auto app is a System app and by default system apps are hidden.
To show hidden system apps press the three-dot menu (⋮) (1) in the top right corner, then press “Show system” (2). You should now be able to see the hidden system app in the list Android Auto (3).
Find your app
If an app is revoked you will need to scroll down until you see the list of revoked apps lower down in the list.
Follow the guidance in “How to revoke ‘Nearby device’ permissions for other apps” in reverse to re-enable permissions for each app.
Android 15 Frequent Bluetooth connection problems
After upgrading Android or moving to a recent phone, AAPS frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If you use an Omnipod DASH and your phone runs Android 15, turning on the Bluetooth bonding setting may help improve the stability of the Bluetooth connection. To turn it on:
Android 16
Only turn on Bluetooth bonding on Android 15, and only if you experience connectivity issues. DO NOT turn on bonding on Android 16.
Open the Dash settings: open the DASH pump screen with Manage > Pump and press the Settings (gear) icon in the top-right corner.
Open the Advanced Settings section and turn on Bluetooth bonding.
If the phone shows a pairing request, accept it.
Restart your phone.