Sorry to keep bothering you but when I go into AndroidAPS I do not have the Git toption then the Clone option under VCS. How do I get that in there??
Actually, I only very briefly tried Android APS. I don’t even use a pump having been on MDI for 48 years.
Hopefully one of our members who has used Android APS can chime in.
Good question. I have to get to my computer to try to replicate the problem which will take a couple of days.
There is an AndroidAPS help group on facebook that can get you answers quicker for troubleshooting technical problems. The group is “androidAPS users”
I can help with using part of things anytime.
If it doesn’t bother you I have some questions and concerns about xdrip + androidaps + nightscout + omnipod in a system.
I finally managed to be able to buy an omnipod and pads.It’s on the way and I started to test the system I wrote a bit upper.
Can I contact you for some tutoring / guidance ?
@bulgariuv Sorry to not respond sooner.
Go ahead and ask your questions. If you have general questions, then ask them in the forum so other people can learn too. If you have specific questions, feel free to send a direct message .
Just so you know, AndroidAPS does not automatically control the Omnipod (yet***). You select “Virtual Pump” for the pump type in AndroidAPS and then you manually have to enter the suggested basal rates into the Omnipod PDM. So it is not really all that automatic.
I used AndriodAPS more to track total insulin on board (the Omnipod PDM only tracks the bolus on board - if you use a temp basal or a suspend you have no idea how much your total IOB really is) and to predict blood glucose based on carbs and insulin. xdrip does BG predictions but you can’t select the insulin type (I use FIASP and I find that AndroidAPS does a better prediction job than xdrip)
AndroidAPS also gives temp basal suggestions that I use that as an alarm for me to look to see if I need to make a correction of some sort. Generally I just either bolus if I am going to go high or temp basal if I am going low.
***Controlling the Omnipod remotely from a Mobile Phone + a RileyLink (a bridge between Bluetooth and the radio frequency that the omnipod uses) is still in development. The developers have mostly working program and are able to control PODs from their phones, but a lot of testing is still required. It sounds like “Loop” will be the first APS program that will be ready. AndroidAPS is longer off. THis applies to the old non-DASH pods.
TidepoolLoop is working with Omnipod to use their APS algorithm with the DASH system (DASH=new bluetooth pods that are controlled with an dedicated Android phone based PDM). This “official” APS may be earlier than the non-official one.
Totally awesome! Thanks Aaron. is there anywhere we can watch the progress of Omnipod and the various loop options?
Thank you for replying.
I do have a lot of questions starting from basics to specific ones.I don’t mind posting them here but I’ll have to write the novel first…
Just so we talk the same language you self-compiled the apk from the source code, right?
For testing I used the already made apk in github but something feels weird about it.I do thing there are some bugs maybe…it does not run in the background ( all the permissions given and battery related stuff -> it only updates when I am watching the dasboard on my phone screen ), it does not make suggestions based on the NS profile ( basal, bolus and so on) or notifications, it does not show anything in the “food” field and some other things.
But I think it would be way better to self-compile the source code, no?
Most certainly I will have a lot of dumbass questions.
I already use virtual pump but I am not very sure for all the settings I should input in the app to make it link with NS 100%.
I am am aware of the Omnipod limitations and research in the closed loop field.
But sadly I can’t rely on something I don’t 101% understand to take such drastic decisions for me.And APS is something a bit hard to understand ( at least for me ) with all the options and variables in there.
Too bad there isn’t a user manual to fully explain each option / field as I was only able to find the installation documentation.
Now don’t get me wrong I think APS is extraordinary for existing and as a possibility but still risky without thorough testing
So can you please put some initial installation settings here?
Do you use NS also? Does it link ok with APS?
Hi @bpollina - there is a “Slack” channel where updates are sometimes posted by developers, although, I think most of the read work is happening elsewhere. (99.999% of the people on the channel are not contributing )
@bulgariuv - I will try to answer…
I complied my own APK from the source code using Android Studio. I am running on a Samsung Galaxy S5. I am running a version from last year but I generally followed these instructions from the wiki. I do not see a big benefit to compiling from source code.
Pre-compiled APKs have recently become available here if you want to try those.
I used to use NS but I gave up about 6 months ago becasue I was not using it. I had to dev version of NS for AndriodAPS to work. I switched over to using Tidepool for data (there is an xdrip setting to upload to Tidepool). I do not have any followers so no reason for me to use NS.
Android APS is based on the openAPS oref0 algorthim (basically it is an Android version of OpenAPS). Although they may be working on oref1 as I may be behind. In order to understand what is going on, I read through the openAPS manual. From a control system perspective it is a very simple algorithm - I liken it to a simple model predictive controller that predicts BGs based on Insulin on board and carbs on board and then selects at temp basal to correct the BG into the range based on a timeframe. Here is the link:
To really figure it out, I looked at the openAPS source code on github and wrote out all the equations to see the actual formulas. In AndroidAPS, you can enable a tab called “OPENAPS AMA” which shows all of the calculation results which starts to make things make sense.
Thanks for your reply.
What do you mean by “I had to dev version of NS” ?
In the last version of androidaps I can’t find anywhere “OPENAPS AMA”…?!?
Even if I get predictions in xdrip I am not seeing anything in androidaps.Not the app’s own predictions not the linked xdrip ones.
Also in my NS page the openaps pill shows unknown, any clue about that, did it happen to you?
@bulgariuv In AndroidAPS, under Config Builder, scroll down to APS, and tick OpenAPS AMA.
On the config tab there is section called “APS”. If you click the checkbox on the right side (for the APS you are using) you will get a tab for the APS that shows all of the parameters.
For nightscout setup with Android APS here is the link. When I said dev, that was old news. Dev was a build veraion. It looks like it just needs to be greatee than version 0.10.
Thank you guys but my dashboard or whatever you call it doesn’t look as what Aaron posted.
Maybe because I used the already made apk instead of compiling it myself.Perhaps it has less options / settings
@bulgariuv I would try a precompiled APK to start. The ConfigBuilder tab allows you to pick what is visible. If you cannot see config builder then you need to try a new Apk.
Are you aware of this…
I do have the ConfigBuilder in settings and also as a tab but no APS field with openAPS AMA in it
this is nice, worth a test.
aaah…too bad it does not support miaomiao
I am now I new it was getting really close.
I may give a a try just for fun, but I do not have an iphone so I will have to wait a bit
Ultimately the value in any of these things - either homegrown or released by a pump company - comes down to how accurate a person’s CGM is.
@Nickyghaleb, if you don’t mind my asking, how much of your 670G frustration do you attribute to the algorithm they used, and how much of it was from the Enlite sensors?
So the 670G uses Guardian sensors, not Enlite. I mention it only because Guardians are supposed to be better, and they are, but they’re still really way too weak to be determining dosing and suspends. In my experience— I should say that. In my experience, the Guardian sensors were probably… maybe…half the problem. With the new transmitter, there’s been improvement in sensor performance, but that’s where the algorithm still is just not aggressive enough. I’m sure it would also be even better with the new transmitter, but it won’t solve everything. Overnight, when my blood sugar is often stable and normal and my Guardian knows it, it still withholds a really good deal of insulin. Then in the morning, as my blood sugar starts to climb, the algorithm is limited in what it can do to contain it. So… it’s a combination of lag, accuracy, and algorithm. It’s just limited.
In my experience. Some people love it.
The already built apk was the problem.
Compiled it myself and now all the sweet things are present