Component Overview

AndroidAPS is not just a (self-built) application, it is just one of serveral modules of your closed loop system. Before deciding for components, it would be a good idea to have a look at the component setup, too.

Compontents overview



The foundation of AndroidAPS safety features discussed in this documentation is built on the safety features of the hardware used to build your system. It is critically important that you only use a tested, fully functioning FDA or CE approved insulin pump and CGM for closing an automated insulin dosing loop. Hardware or software modifications to these components can cause unexpected insulin dosing, causing significant risk to the user. If you find or get offered broken, modified or self-made insulin pumps or CGM receivers, do not use these for creating an AndroidAPS system.

Additionally, it is equally important to only use original supplies such as inserters, cannulas and insulin containers approved by the manufacturer for use with your pump or CGM. Using untested or modified supplies can cause CGM inaccuracy and insulin dosing errors. Insulin is highly dangerous when misdosed - please do not play with your life by hacking with your supplies.

Necessary Modules

Good individual dosage algorithm for your diabetes therapy

Even though this is not something to create or buy, this is the ‘module’ which is probably underestimated the most but essential. When you let an algorithm help manage your diabetes, it needs to know the right settings to not make severe mistakes. Even if you are still missing other modules, you can already verify and adapt your ‘profile’ in collaboration with your diabetes team. Most loopers use circadian BR, ISF and CR, which adapt hormonal insulin sensitivity during the day.

The profile includes

  • BR (Basal rates)
  • ISF (insulin sensitivity factor) is your blood glucose unit per one unit insulin
  • CR (carb ratio) is gramms carbohydrate per one unit insulin
  • DIA (duration of insulin acting).


You need an Android smartphone with Google Android 6.0 or above. Users are creating a list of tested phones and watches

To record a phone or watch that isn’t already listed in the spreadsheet then please fill in the form.

Any problems with the spreadsheet please send an email to, any donations of phone/watch models that still need testing please send an email to

Insulin pump

AndroidAPS currently works with

Other pumps that may have the potential to work with AndroidAPS are listed on the Future (possible) Pumps page.

If you need to privately buy a pump then you can find various distributors is in this spreadsheet, please share the details of yours if not already listed.

So what’s the best pump for looping with AndroidAPS?

The Combo, the Insight and the older Medtronics are solid pumps, and loopable. The Combo has the advantage of many more infusion set types to choose from as it has a standard luer lock. And the battery is a default one you can buy at any gas station, 24 hour convenience store and if you really need one, you can steal/borrow it from the remote control in the hotel room ;-).

The advantages of the DanaR/RS vs. the Combo as the pump of choice however are:

  • The Dana*R/RS connects to almost any phone with Android >= 5.1 without the need to flash lineage. If your phone breaks you usually can find easily any phone that works with the Dana*R/RS pumps as quick replacement... not so easy with the Combo. (This might change in the future when Android 8.1 gets more popular)
  • Initial pairing is simpler with the Dana* RS. But you usually only do this once so it only impacts if you want to test a new feature with different pumps.
  • So far the Combo works with screen parsing. In general that works great but it is slow. For looping this does not matter much as everything works in the background. Still there is much more time you need to be connected so more time where the BT connection might break, which isn’t so easy if you walk away from your phone whilst bolusing & cooking.
  • The Combo vibrates on the end of TBRs, the Dana* R vibrates (or beeps) on SMB. At night time you are likely to be using TBRs more than SMB. The Dana* RS is configurable that it does neither beeps or vibrates.
  • Reading the history on the RS in a few seconds with carbs makes it possible to switch phones easily while offline and continue looping as soon a soon as some CGM values are in.
  • All pumps AndroidAPS can talk with are waterproof on delivery. Only the Dana pumps are also “waterproof by warranty” due to the sealed battery compartment and reservoir filling system.

BG Source

This is just a short overview of all compatible CGMs/FGM with AndroidAPS. For further details, look here. Just a short hint: if you can display your glucose data in xDrip+ app or Nightscout website, you can choose xDrip+ (or Nightscout with web connection) as BG source in AAPS.

  • Dexcom G4: These sensors are quite old, but you can find instructions on how to use them with xDrip+ app
  • Dexcom G5: It works with xDrip+ app or patched Dexcom app
  • Dexcom G6: It works with xDrip+ app or patched Dexcom app
  • Libre 1: You need a transmitter like Bluecon or MiaoMiao for it (build or buy) and xDrip+ app
  • Libre 2: It works with xDrip+ (no transmitter needed), but you have to build your own patched app (see these instructions for more details)
  • Eversense: It works so far only in combination with ESEL app and a patched Eversense-App (works not with Dana RS and LineageOS, but DanaRS and Android or Combo and Lineage OS work fine)
  • Enlite: quite complicated with a lot of extra stuff


Nightscout is a open source web application that can log and display your CGM data and AndroidAPS data and creates reports. You can find more information on the website of the Nightscout project. You can create your own Nightscout website using Heroko, use the semi-automated Nightscout setup on or host it on your own server (this is for IT experts).

Nightscout is independent of the other modules. You will need it to fulfill Objective 1.

Additional information on how to configure Nightscout for use with AndroidAPS can be found here.

AAPS-.apk file

The basic component of the system. Before installing the app, you have to build the apk-file (which is the filename extension for an Android App) first. Instructions are here.

Optional Modules


You can choose any smartwatch with Android Wear 1.x and above. Most loopers wear a Sony Smartwatch 3 (SWR50) as it is the only watch that can get readings from Dexcom G5/G5 when phone is out of range. Some other watches can be patched to work as a standalone receiver as well (see this documentation for more details).

Users are creating a list of tested phones and watches. There are different watchfaces for use with AndroidAPS, which you can find here.

To record a phone or watch that isn’t already listed in the spreadsheet then please fill in the form.

Any problems with the spreadsheet please send an email to, any donations of phone/watch models that still need testing please send an email to


Even if you don’t need to have the xDrip+ App as BG Source, you can still use it for i.e. alarms or a good blood glucose display. You can have as many as alarms as you want, specify the time when the alarm should be active, if it can override silent mode, etc. Some xDrip+ information can be found here. Please be aware that the documentations to this app are not always up to date as its progress is quite fast.

Sample Setup

If you want to get a step by step example, you might want to look at a sample setup. The first sample setup is quite old, but should be still up-to-date.

What to do while waiting for modules

It sometimes takes a while to get all modules for closing the loop. But no worries, there are a lot of things you can do while waiting. It is NECESSARY to check and (where approporiate) adapt basal rates (BR), insulin-carbration (IC), insulin-sensitivity-factors (ISF) etc. And maybe open loop can be a good way to test the system and get familiar with AndroidAPS. Using this mode, AndroidAPS gives treatment advices you can manually execute.

You can keep on reading through the docs here, get in touch with other loopers online or offline, read documentations or what other loopers write (even if you have to be careful, not everything is correct or good for you to reproduce).

Done? If you have your AAPS components all together (congrats!) or at least enough to start in open loop mode, you should first read through the Objective description (Overview Part 2) before each new Objective and setup up your hardware.