Suchiman @Suchiman has a fossil gen 5 carlyle with AAPS watchface
@ntiliakos_twitter See my note above about NS_UPLOAD_ONLY
Is anyone seeing warnings for /W:ConnectionTracker in the dev branch? IE :
2021-02-02 16:56:03.398 10448-17016/info.nightscout.androidaps W/ConnectionTracker: Exception thrown while unbinding
java.lang.IllegalArgumentException: Service not registered: lt@ee79828
at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:1490)
at android.app.ContextImpl.unbindService(ContextImpl.java:1655)
at android.content.ContextWrapper.unbindService(ContextWrapper.java:716)
at ci.f(:com.google.android.gms.dynamite_measurementdynamite@205016051@20.50.16 (040408-0):1)
at ci.d(:com.google.android.gms.dynamite_measurementdynamite@205016051@20.50.16 (040408-0):2)
at lu.E(:com.google.android.gms.dynamite_measurementdynamite@205016051@20.50.16 (040408-0):9)
at le.a(:com.google.android.gms.dynamite_measurementdynamite@205016051@20.50.16 (040408-0):3)
at eg.run(:com.google.android.gms.dynamite_measurementdynamite@205016051@20.50.16 (040408-0):3)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:457)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at iz.run(:com.google.android.gms.dynamite_measurementdynamite@205016051@20.50.16 (040408-0):5)Looks very similar to this error:
Apparently, in a few cases, the BT stack on the Combo can get stuck somehow
In most cases though it is an issue with the Android BT stack, with the underlying BT chip, or with ruffy itself
the first one being the most likely especially if vendors crammed their "specials" on top and apply aggressive power saving on it all
keep in mind that Bluetooth itself is a "system app". in the list of applications (via settings), you can get a list of all apps, including system ones. bluetooth is among them, and it has options for whether or not "battery optimization" is applied. turn that off.
Also, keep in mind that the Bluetooth app has its own Cache and Data that can be cleared. If you are having Bluetooth issues it never hurts clear the cache (and if need be data).
Hello, I’m using AAPS with Roche Combo Pump + libre + miaomiao2. On my AAPS a few days ago (since 2.8.1) the TDD shows 0 For Basal and Bolus, as shown on the image above. Does anyone knows why this is happening?
Hello All, I am a user of AndroidAPS-2.7.1-dev-omnipod branch since Octtober 2020 on LG G5 running Android 7. I am running it in Loop mode since early on. I have been receiving info about available updates 2.8.1 and now 2.8.2 within the AndroidAPS app. It has also started to warn me that at some point (60 days), loop will disable and at 90 days Low glucose suspend will also disable. Is there a way for me to continue using what I have? It is working fine, and I prefer to postpone the AndroidAPS update to whenever I decide to upgrade my phone. I do not think my LG G5 phone is going to get upgraded to Android 8 or later. At the moment, my phone is also working fine so I do not have an immediate need to upgrade the phone. I read the docs (release notes), and I also searched on facebook page just in case this issue has been discussed but did not come across any related info. Thanks.
And autotune
@bhatiaa there is no way. you must upgrade
@rapocalypse , TDD insulin statistics is read from the pump and Combo does not support basal and bolus statistics separately, only TDD. AAPS top right corner has a menu called Statistics that has basal and bolus counts but these are counted in AAPS application.
4 replies
is there a way to export the raw data such as insulin units, carbohydrates, catheter changes directly from the app, e.g. for a visit to the doctor? Or do I have to go the way of a nightscout installation? what possibilities are there there apart from the reports? so I would like to have the figures and display them myself.
@MilosKozak Also, would it perhaps make sense to add a button to explicitely download some careportal data from NS to AAPS? I am specifically talking here about sensor insert date, last reservoir change, last infusion site change, last battery change. If I set up AAPS from scratch and import settings, that information isn't there.
alright, nevermind then
is adding this to the existing nsclient something you would consider worthwhile for someone to spend time on? or do you think that it would make more sense to write a new nsclient on top of the new V3 nightscout API if someone wants to contribute to AAPS?
Yea thats the only use I had for disabling the NS upload only. I would upload all the data to NS and then reinstall AAPS. After reinstall I disables NS upload only to pull all the history from NS. After this was done I would again enable NS upload only. I think als long as you only update the app (not reinstall) the history data should remain.
After updating from 2.7 to 2.8.2, I am confronted with syncing issues between AAPS loophandy, NS und NClients for parents. It is true that treatments must be entered solely via AAPS because syncing from NS to AAPS is completely disabled - right?
For parents, this is a huge step backwards: using NSClients for editing carbs, TTs and profile switching is important when kids are at Kindergarten oder school. Can somebody please give a rough outline - are there plans for rewriting the code to re-enable these features and NSClients in the near future?
For parents, this is a huge step backwards: using NSClients for editing carbs, TTs and profile switching is important when kids are at Kindergarten oder school. Can somebody please give a rough outline - are there plans for rewriting the code to re-enable these features and NSClients in the near future?
@baurat_gitlab As far as I know that is correct, unless you want to switch to engineering mode. Did you try searching the Facebook Group or de.loopercomminuty.org? I think it has been discussed in the group. By the way: non-Germans will not understand "loophandy", which means "smartphone that AndroidAPS is running on" and "oder", which means "or".
Thanks @ArthurusDent - bad habits and lack of practice kill my English, thanks for "translating" ;)
No Facebook, known reasons. I read about engineering__mode, but this is what I would like to know first-hand: if it were ready-to-use, it would be enabled by default. So I am careful and asking about the internal roadmap - what priority does syncing and proper use of NSClient have?
No Facebook, known reasons. I read about engineering__mode, but this is what I would like to know first-hand: if it were ready-to-use, it would be enabled by default. So I am careful and asking about the internal roadmap - what priority does syncing and proper use of NSClient have?
@baurat_gitlab Firefox now puts Facebook's websites behind virtual bars, meaning it prevents tracking. I think it's pretty safe to use Facebook now. [DE] https://www.mozilla.org/de/firefox/facebookcontainer/, [EN] https://www.mozilla.org/en-US/firefox/facebookcontainer/ By the way: the addon that puts up the bars can't be run in a private windows, so keep that in mind.
if the basal rate shape is ok, but the overall dosage is too high, then AAPS will more or less consistently set <100% TBRs
too strong ISFs (read: too low ISF values) lead to a similar though somewhat different behavior
that one becomes obvious when you keep in mind that AndroidAPS is essentially a control loop. and what happens when a control loop regulates too aggressively?