stephenblackwasalreadytaken / xdrip Goto Github PK

When activated by the setting "Run Collection Service in foreground", there is an Android persistent notification, but it doesn't show any useful information.

Perhaps it would be useful to have the BG number displayed in the notification.

Looks like export is already present, can we get import too?

I've found the BLE module flashing due to not being connected, but Dexdrip is happily chugging along without data or notification

Would be nice to have a status menu/screen accessible via menu.

Info to be put there:

• sensor start time/date;
• last calibration time;
• Bluetooth status;
• wixel battery status/level;
• dexcom transmitter battery status/level;
• last reading time;
• number of reading missed in last hour, last 24 hours, since sensor start;

Start sensor in app immediately after insertion;
After 2 hours double calibration was introduced.
Application displayed the all previous readings (for 2 hours) as 40 and further the algorithm was messed up.

Workarround was to stop and restart sensor.

Solution here seems to not add as BgReadings data provided in the first 1h 45mins from start sensor time.

Unable to see data on Dexcom follow app. I have Dexcom Share enabled in xdrip settings and have entered dexcom username and pw. Any ideas?

As a heads up everything on 2.0.1 was working fine until I updated to the latest Google app (5.1.17.19). Following that the bluetooth will not stay connected. Im not 100% if this is the direct cause or if it is something else because I havent had the time to roll back a few things to make sure....

Im not even sure if the Google app would cause this but it was the only thing that changed on my phone yesterday. I will continue to try to roll back to 5.1.17.16 or even roll back the Play Services but as of now the app will not stay connected to the receiver.

If there is something that I can get you to help let me know...

as discussed this is the log of issue for Pebble time not loading xdrip watch face just released. PT get stuck on uploading sequence everything else remains good .Uploader phone(Samsung S4 xdrip soldered in) does not lose BT pairing with watch and all other watch faces do work properly.

My setup: Dexcom G4 platinum
My use case: using LV to create a glucose controller, I've done all the work of controlling, but still have to manually input values. Is there an API or something in xDrip that would allow me to pull individual values to be fed into my software?

Just found this awesome project, was starting to lose faith that I'd ever be able to close the loop.

Hi, I was looking at the battery voltage measuring circuit and I think it can be improved. I modified it and it seems to work. Please find my working below and let me know what you think:

The voltage divider in the hardware_setup.md document uses a 1K and 2.2K ohm resistor. This creates a circuit with 3.2K ohm resistance which is always closed.

At 3.7 volts this will use 1.15 milliamps constantly (3.7 / 3200). Over 48 hours (typical battery life?) this would be 55 mAh which is >10% of a 500mAh battery's capacity.

Changing these resistors to both be 10K ohm gives a 20K circuit which would use 8.8 mAh over a 48 hour period which is ~1.6% of the battery capacity.

My tests with these 10K resistors appear to work, with convincing millivolt readings reducing over time for the battery in a 48 hour period.

Depending on the current required/resistance of the ADC on the Wixel, it might be possible to increase these resistors further and get even better power reductions. I haven't investigated this yet.

Changing the resistor ratios means that this voltage divider is now dividing the voltage in half.

This reduces the accuracy of the original circuit, but has the advantage that batteries up to the 6.5volt the Wixel can support can now be used without overloading the ADC.

It also slightly simplifies the voltage divider circuit, a builder doesn't have to worry about which resistor is which as they are both the same.

After re-soldering these resistors a few times myself, I can't imagine that anyone who has already built an xdrip is going to want to change their existing configuration! But I thought it was worth mentioning as an issue to improve the design and could be even more significant if people wanted to use even smaller batteries.

Please let me know any thoughts on this. I searched and I didn't find anything implying it had already been covered.

Should show a warning if someone tries walking through bluetooth device setup with BT turned off

This isn't so much as a question that I don't know where else to ask. On the Dexcom I can enter events for things like carbs eaten, insulin taken, exercise, alchohol consumed, etc...

Is this data being captured by xDrip currently? If not, is it possible it could be in the future, or is the proper data not being exposed from the Dexcom device to allow for this?

I recently purchased the Samsung Gear S smartwatch and I would love to see the NightWatch app be compatible with it. Is this possible? How complex is the process? I don't know a lot about coding and it took me a while to get my DexDrip unit up and running.

On a whim, I tried moving time forward on my phone to skip the sensor warmup period. That worked. It probably shouldn't have.

Also, can we optionally skip sensor warmup if the sensor is already running?

Hi! Quick one, as it looks like the BgReading create method isn't setting noise from the EGVRecord unless the calculated_value is <= 13. I just bumped it out a level, as I insert (and use) the noise value w/ every BG record I drop into my web service. Thnx.

The graph is in accordance with the values shown by the meter.
But the number reported above the graph as well as the tendency is not correct

For example:
Graph shows a value round about 100 and is more or less unchanged since an hour.
Nevertheless the number shown above shows HIGH and a double arrow down or up.
(High alarm is set to 270)

I successfuly loaded the app on the device, but it won't allow me to scroll down to accept the End User agreement. Is there a way to bypass this or edit a file on the device to show that I have accepted it?

Stale data is displayed initially, then refreshed a second or two later

After some calibration fun, i've been shown values including 14887 and -24122. BG values shouldn't be shown if negative or (possibly) above something like 800 or 1k.

The low blood sugar alarm at 55 mg/dl is currently uneditable and overrides the phone's silent mode. This might be a good idea when the data source is xDrip hardware, but it's annoying when the source is the Dexcom Share receiver, because the receiver already has an unsilenceable alarm at 55. Please make this editable, at least when the source is Dexcom Share.

It would be nice to store the calibration data after "stop sensor".
If i eject the transmitter after 10 days for contact cleaning or other tuning tasks
and insert it again, the accuracy is not as good as before. So it would be nice to
see the question "Would you like to use your previous calibration data for this sensor?" or
a check box "Same Sensor as before" in the start sensor - insertion time mask.

Cheers

When starting a new sensor, I wasn't prompted for double calibration after receiving >2 data points.

This causes post-calibration delay in displaying the newly calibrated value.

Changed out my sensor site this morning and the app crashed shortly after I put the BG values into the share receiver. I tried to force close and reopen...I cleared cache....forced the app to reconnect and it seems to have settled down.

I'm writing in behalf of another user:

In the current beta 2.0.1 the menu button to export database (usually right upper corner) is no longer there.

The screen resolution is: 1920x1080

I manage to build and install everything.. but when I look at pictures from the comparison of drip vs 505, it looks like the curves in the app are quite "smooth". Mine aren't.. I am not using 505 yet since it is not available in sweden, but I have the old one, and the one in the Animas vibe pump to compare with.. This is what I see that is strange to me.. the values are quite scattered, and look at for example 21.00 it looks like I have two different values at the same time? can this be due to an installation mistake, or due to that I view the result in mmol? The values are not that scattered in the other two..

Right now tapping the bg widget doesn't seem to have any effect. If it opens xdrip, that's one less thing I need on my home screen.

I ran into a problem setting up my nephew's uploader to submit to the Nightscout API instead of MongoDB directly. According to this ssl test, it should work with Android 4.4.2, but "This site works only in browsers with SNI support." (news to me, but that's a different problem).

From the Android SSL docs:

Fortunately, HttpsURLConnection supports SNI since Android 2.3. Unfortunately, Apache HTTP Client does not, which is one of the many reasons we discourage its use. One workaround if you need to support Android 2.2 (and older) or Apache HTTP Client is to set up an alternative virtual host on a unique port so that it's unambiguous which server certificate to return.

I checked and sure enough, the Nightscout uploader uses the Apache library.

The other option appears to be to use a newer version of Apache's library, which probably requires fewer changes.

Any interest?

I was looking into, but new at programming android, other than theming and slight modifications. I was wanting to have it when bs got low or high or high/low rate to send a text message. I was wanting something to display in my car when I'm driving. Any input on where to look into, please let me know.

Using xbridge 2 i have delta error on nightscout and pebble. Some times i have erroneous arrows Like +7 with arrow straight up

BG Alert-Notifications show, even if in snooze time. Sound doesn't play.

I guess in file https://github.com/StephenBlackWasAlreadyTaken/xDrip/blob/master/app/src/main/java/com/eveningoutpost/dexdrip/UtilityModels/Notifications.java in line 214
} else if ((userNotification != null) && (userNotification.timestamp >= ((new Date().getTime()) - (60000 * bg_snooze)))) {

the >= should be a <=.

Greetings, Adrian

My usb charging module is delicate and the port has broken a few times and I've resoldiered it. This morning it happened again. I plugged into the Wixel USB port with a charger and it charged the battery some. I wonder though if this will mess up the lipo battery? It is passing the charge back through the lipo charger module before it hits the battery. Any ideas of the charging module will turn it off from charging like it is supposed to do when naturally plugged in. Just curious if this work around is good. The Wixel USB port is much stronger than the USB one I have.

Anyone tried this http://www.adafruit.com/product/1697?

Hi Stephen,

Let me congratulate you, fantastic job. I would like to make my own xDrip I live in Czech Republic and buying from US can cause some delays and complications. I have found a HM 10 Bluetooth but I'm not sure is the right one. Could you please advise me whether this is the right one to buy? Description and link to shop below.

HM-10 Bluetooth 4.0 RS232 UART Modul Master / Slave Arduino

Popis produktu

Bluetooth 4.0 modul podporuje master/slave
Bluetooth čip: CC2541
Bluetooth: V4.0 Ble
UART rozhraní
Provozní napětí: 3.3V
Rozměry desky: 27mm x 13mm

http://robotstore.cz/obchod/arduino/hm-10-bluetooth-4-0-rs232-uart-modul-master-slave-arduino/

Best regards,
Rodrigo

When DST changes occur the sensor age alters significantly (either older by 1 hour or younger by one hour). Likely due to the Sensor Start time being recorded in localtime rather than GMT/UTC. This should be rectified. Discovered it when I found my android phone was on the wrong time zone after starting a sensor. When I set it up correctly and changed the time to match, the sensor age was now 1 hour younger than it was previously. DST changes will show this up.
Cheers

Hi There,

Wondering if there are plans to also support the mmol/l glucose measurements. This measurement is widely used outside of the USA.

Conversion from mg/dl is trivial: http://www.faqs.org/faqs/diabetes/faq/part1/section-9.html
Simply divide by 18 or multiply by 0.055.

Thanks.

Jon

Rather than compiling a transmitter ID into the wixel app, allow a user to configure it within the android app.

I'm running two uploading phones on two different dexcom shares and run into issues where the data hasn't been uploaded for 20 min or longer and its regularly in the 9-15 min since the last upload. I'm not sure if the issue is between the dex reciever/app or the app/database. Restarting the collector fix's it, but would be nice not to have to wake up at night and hit the restart collector to continue getting data when it goes past the 20 min and my alarm goes off. Both phones are on wifi only and do not have active sim cards. Any help would greatly be appriciated.

I'm currently running xdrip w/Mongo only (ie no night/scout /Azure)

The app, and the notifications both have 'working' bg status arrows, but the widget only displays a 'steady' or horizontal arrow.

It would be the bees knees if the widget also made use of the trend arrows!

Thanks!

The calendar and time selector are both cut-off on the StartNewSensor activity, for example.

Please add a new data collection method "USB Wixel" in addition to "Bluetooth Wixel" and "Wifi Wixel".

I love DexDrip and Nightwatch but I'm a bit confused by the arrows displayed. For one they are different on the DexDrip app compared to Nightwatch. They also seem rather random, I'll have double arrow up, followed by arrow down then up again when the 3 results are extremely close. I'm thinking it has to do with the fact I use mmols. It seems that on the display on my watch, the result just under the arrow is sometimes wrong, ie, the BG itself shows little or no change but under the arrow it shows a change of say 1.9 mmol when I think it should probably be 0.19. Sorry, I don't know if I make any sense!

Dexdrip running 24/7 will stop uploading (seemingly) randomly. I use the BACK button in Android to get out of Dexdrip then relaunch. It will then backfill some but not always all of the "missing" BG numbers to my Mongo DB. Phone is Droid mini running 4.4.4

I built a working app a few weeks ago, but now when I try to build again with the latest updates I get this error (same machine, and I have made no changes):
Error:A problem occurred configuring project ':app'.

Could not resolve all dependencies for configuration ':app:_debugCompile'.
Could not resolve com.getpebble:pebblekit:2.6.0.
Required by:
DexDrip-master:app:unspecified
> Could not GET 'https://jcenter.bintray.com/com/getpebble/pebblekit/2.6.0/pebblekit-2.6.0.pom'.
> jcenter.bintray.com

I tested that I could reach the https address and that was no problem.. any ideas?

I think I may have discovered an issue with Dexcom uploads. My device is a second gen moto e.

I've never done any android development but I muddled my way around enough to enable logging in the app and connect to android studio. Everything seems to go fine until I see the following log messages:

07-26 16:22:49.617    3947-3964/? W/ShareRest﹕ About to call ShareRest!!
07-26 16:22:49.618    1023-1990/? W/ActivityManager﹕ Unable to start service Intent { cmp=com.eveningoutpost.dexdrip/.ShareModels.ShareRest (has extras) } U=0: not found

If there's something I can try/change let me know and I'll give it a shot.

Any idea how to get around this? Alternatively, any chance you could make the latest version available as an .apk in the Releases section of GitHub?

UnsupportedMethodException
Failed to set up Android modules in project 'DexDrip': Unsupported method: BaseArtifact.getJavaCompileTaskName().
The version of Gradle you connect to does not support that method.
To resolve the problem you can change/upgrade the target version of Gradle you connect to.
Alternatively, you can ignore this exception and read other information from the model.

Put some of this data on my wrist.

http://i.imgur.com/eRaemGo.jpg

The scale on the graph is reasonable, the BG is not.