-
Notifications
You must be signed in to change notification settings - Fork 19
6 Troubleshooting
This page in intended to present possible hints and/or solutions for solving general problems with using AndroidAPS-Omnipod.
While trying to build I get an error stating the file name is too long. Possible solutions:
- Move your sources to a directory closer to the root directory of your drive (e.g. "c:\src\AndroidAPS-EROS")
From Android Studio:
- Make sure "Gradle" is done syncing and indexing after opening the project and pulling from GitHub
- Execute a Build->Clean Project before doing a Rebuild Project
AndroidAPS is not running in "developer mode" (see below)
AndroidAPS is not running in "developer mode".
AAPS shows the following message: "running dev version. Closed loop is disabled". You can not select Omnipod for pump.
-
Make sure AndroidAPS is running in "developer mode" by placing a file named "engineering_mode" at the location where logfiles are stored: "Android/data/info.nightscout.androidaps/files". Any file will do as long as it is properly named.
Hint: Make a copy of an existing logfile and rename it to "engineering_mode" (note: no file extension!). Make sure to restart AndroidAPS for it to find the file and go into "developer mode".
Settings files will be stored on your phone's internal storage in the directory "AAPS".
The settings files are in .json format and are encrypted by default. Optionally you can disable encryption of the settings files from the Maintenance menu settings.
WARNING: Make sure not to loose your password as without it you will not be able to import an encrypted settings file!
Upgrading when on an active Pod is possible but there is a small risk you loose the Pod. That is is why we recommend upgrading when the Pod is about to expire i.e. before activating a new Pod.
To minimize the risk on Pod failures when upgrade with an active Pod go about as follows:
- Suspend the Pod using the SUSPEND button on the POD tab. This ensures AAPS cannot make any more changes to the state of the pod.
- Export your settings. This ensures the pod state is captured in your settings file.
Make sure you have the master password as set in AndroidAPS or you will not be able to import your settings later!
You now have 2 choices:
- Do an "inplace update" of your existing installation (only when updating to a next version)
- Install the updated version.
- Un-suspend the Pod using the "Resume-delivery" button on the POD tab
You are done!
- Reinstall a new version
- Uninstall AAPS (make sure to export settings first!).
- Install the new version.
- Make sure to place the engineering_mode file (see above) and configure the phones battery savings.
- In AndroidAPS set your master password.
- Import your settings.
- Un-suspend the Pod using the "Resume-delivery" button on the POD tab
You are done!
No! You may loose your Pod unless...
In addition to your preference settings and Objectives the settings file also stores the current Pod state:
-
Importing an older settings file will import an outdated Pod state and your currently active Pod will be lost.
-
When you are on an active Pod you can import settings that were saved after the Pod was activated. Use this when you need to uninstall and then reinstall AndroidAPS.
Remark (unsupported: request for help on our Discord channel): Provided the settings files are unencrypted, there are options to "hack" your current Pod state into an older settings file by replacing all JSON "AAPS.Omnipod" content attributes.
The AAPS logfiles are located on your phone in the directory "Android/data.info.nightscout.androidaps/files".
There are several ways to get the logfiles, for instance to add them to an issue you are reporting on GitHub. Use whatever option is the most convenient for you:
-
On the phone, open the logfile location. Maybe to attach them from your e-mail client or upload them to cloud storage like OneDrive or Dropbox.
-
Attach the phone to your PC using an USB cable.
-
E-mail the logfiles from AAPS:
For this you need to configure the e-mail address to use for sending logfiles. Go to preferences, scroll all the way down. Then, under maintenance Settings, Advanced, enter your e-mail address under Email recipient. You can now send the latest logfiles to the e-mail address configured directly from AAPS by going to the Maintenance menu and choosing "SEND LOGS BY EMAIL".
The setup instructions mention Disabling Power Management (aka Battery savings).
Properly configuring Power Management is important to prevent your Phone's OS to suspend AndroidAPS and related app's and services when your phone is not being used. As a result AAPS can not do its work and/or Bluetooth connections for sensor and Rileylink (RL) may be shut down causing "pump disconnected" alerts and communication errors.
On the phone, go to settings->Apps and disable battery savings for:
- AndroidAPS
- xDrip or patched Dexcom app
- The Bluetooth system app (you may need to select for viewing system apps first)
Alternatively, fully disable all battery savings on the phone. As a result your battery may drain faster but it is a good way to find out if battery savings is causing your problem.
The way battery savings is implemented greatly depends on the phone's brand, model and/or OS version. Because of this it is almost impossible to give instructions to properly set battery savings for your setup. Experiment on what settings work best for you.
For additional information, see also Don't kill my app
Make sure your phone stays in Bluetooth reach from RileyLink (RL). Depending on the phone, RL and the environment Bluetooth range may vary from a few meters to up-to 30 meters. When the phone looses the connection with RL it tries to reconnect. Especially when this takes longer then a few minutes AAPS may fail to restore the connection. To reconnect, exit AAPS through the "..." menu and restart.
(see also battery savings)
Your phone may be suspending AAPS services or even Bluetooth causing it to loose connection to RL.
(see battery savings)
Make sure pump unreachable alerts are configured to 120 minutes by going to the top right-hand side three-dot menu, selecting Preferences->Local Alerts->Pump unreachable threshold [min].
Try one of the following:
- Restart AAPS by exiting through the "..." menu.
- Restart the phone.
- Reset RileyLink (by switching it on/off).
Sometimes AAPS reports is connected but is unable to communicate with the pump. When restarting AAPS or the phone does not resolve the problem, "resetting" your RileyLink by switching it "off" and "on" may restores communication.
-
This can be caused by Nightscout issues.
- Make sure your Nightscout site is operating as expected.
- On xDrip+ check the connection to your Nightscout site. Nightscout should display recent BG values.
-
You specific phone Brand/model/OS may be having BT issues causing problems to connect both RL and your sensor source. Check if your phone is on the list of phone that have been tested to work for other users (see wiki home page)
Yes you can. To switch go about as follows:
- Suspend the Pod from the POD tab (just to be on the safe side...).
From the OmniPod Plugin preferences menu:
- Select "RileyLink and "REMOVE" the current selected RileyLink.
- Switch on the new RL device power.
- Select "SCAN" and wait until the new device shows up.
- Select the new device.
Go back to the POD tab and check/wait until "RileyLink" status shows "Connected".
- Once connected you can "RESUME DELIVERY".
In case of any problems just re-select the original RileyLink by redoing the sequence starting from (2) As always: no guarantee. Things can happen. If you do not want or can take the risk of loosing the Pod, best to wait until it is about to expire!
- Join our the Discord channel and ask for help.
- Report your issue on GitHub
- Join our the Discord channel and share this information (More info on the main Wiki page).
- Remind us to add your solution to this list.