Dexcom on ANDROID!


#1

I am a rabid Android fan. I just got my Dexcom G5 a couple of months ago and bought everything Apple, ditching my Samsung Note 5 :frowning:

Dexcom’s site announcing their CGM on Android: https://www.dexcom.com/get-started-cgm/29

Having worked in the tech industry, you never go with the first generation or you wait for the first service update before you go to a new product. What are the thoughts about timing in jumping the Apple ship for Android based Dexcom?


#3

Avid Dexcom lover/user here. I hate Apple with a passion and finally dove in head first without looking and started using the “Beta” versions of xDrip+ (part of the OpenAPS.org developers). It’s information, graphs, ability to go back weeks and even months to see details, averages, etc. is far superiour. However, you might miss a few readings here/there. I noticed about 2 or 3 once or twice a day using Nexus 6 but overall, it does pretty well. Being a developer in years passed, I can understand the issue with the way the Bluetooth in the Android phone isn’t designed for this type of application but it doesn’t do too bad of a job. Haven’t looked back. (With xDrip+, never use 2 phones at once but you can use 1 phone and 1 Dexcom receiver simultaneously).


#4

I don’t quite follow that. Could you please elucidate?


#5

Get the receiver if your nervous. I would get the receiver anyway, as a backup, incase you loose your phone or drop it.


#6

I’ve been using the G5 with my Samsung Galaxy S7 for a few days now and it works very well. Best of all the alarms that people complain about with the iPhone app don’t sound if the phone is on vibrate, which is fantastic!


#7

I’m jealous, Scott. Just got a G5, and have an S7 (fantastic phone!), but alas, I’m on Medicare, so I’m not allowed to use any mobile devices with the G5. Does using the Dexcom app affect battery life, or is it too soon to tell? Is the UI a lot nicer in the mobile app than on the receiver? I wish the receiver had larger numbers for non-alert bg numbers (ie, the bg readings at the top of the receiver are quite small, comparatively), and that the graphs didn’t go all the way to 400, so that a small difference in bg’s would show up more readily.


#8

How would anyone know what device you are using as a receiver?


#9

@jjm335 - If using the official Dexcom App on a Smart Device, this requires a Dexcom account and the data is transferred to the Clarity Cloud application.

Using the X2 as a receiver or using xdrip is an entirely different story.

On top of that, I believe @Dave44 said that he was requested/required to sign a document along these lines. For some people, it is just a stupid document. For other people, it is their promise to abide by the rules.


#10

@Dave44 - Don’t want to rub any salt, but to address this part of your post. On the app, there is a setting to change the scale from 400 to 300. (I think - app not actually in front of me - hope I didn’t get that wrong!!!)

Also, Dexcom Technical Support has told me that the more simultaneous devices you have paired with the G5 transmitter, the faster the battery in the transmitter will run down. Dexcom provides a warranty on the transmitter for 3 months intended for 2 devices if the transmitter is first used within six months of the SB date on the box. (Again from memory - if wrong - please correct me.) Both the Dexcom App and the Dexcom Receiver (and presumably the X2) have a software switch which will disable use of the transmitter after about 3 months and 3 weeks since it was first activated. So, using 1 device or 2 devices with either the Dexcom App, Dexcom Receiver or Tandem X2 will not practically matter as the Transmitter should still last 3 months and 3 weeks.

xdrip bypasses the software switch so that is entirely different.


#11

Out of curiosity, how can Medicare stop you from downloading the app on your phone and using it? It does drain my battery quicker I find. I compensated for it by shutting off push email which made a huge difference! The graph is definitely easier to read but it’s disappointing that certain basic features are lacking, such as being able to see clarity statistics right in the app (i.e. average glucose, standard deviation, etc.).


#12

Medicare can not stop you from using the Dexcom App. Medicare can request that you not do so. Medicare could request that Dexcom provide information on who has done so. (I have no idea if they DO that but certainly it is technically feasible.)

Dexcom has the technical ability to block the Dexcom App for any individual. (I have no idea if Dexcom would do such but again - it is technically feasible…)


#13

I’m not going to test anyone’s theory that Medicare can’t find out if I use the mobile app. No way can I afford to pay for Dexcom supplies myself. This is all so new, that any anecdotal evidence at the moment that someone is using the Mobile App and hasn’t been kicked off of Medicare for doing so, would be highly premature and presumptive. If those of you on Medicare want to give it a try, I say, more power to you. I simply cannot afford the consequences of being denied my Dexcom coverage.


#14

I can pretty much guarantee you that if Medicare WANTS to find out (usage of the Dex App) and if Dexcom cooperates, that Medicare would know. IMHO that is cut and dry.

@Dave44 - Your approach sounds very reasonable. This entire situation is not written in stone for all time. Right now it is what it is. The Dexcom CEO has already publicly stated he intends on working this but he first wanted to get everything moving (ie - equipment and supplies being shipped) for people on Medicare as well as getting the reimbursements properly flowing from Medicare back to Dexcom. There is every reason to believe this is not the end of the story.

However be sure to upload your receiver into the Dexcom Clarity app. That is 100% allowed. Certainly call Dexcom if you have questions. But this is the best way (IMHO) to analyze your data, look for trends and potentially make changes that will provide even better results going forward. Note that the receiver also uploads into Diasend. Quite possibly other apps that I don’t know of.


#15

Thanks, Tim!

I’ve uploaded once to Clarity. Need to do it again, though–I did it when I had less than a day’s data. :slight_smile:

Yesterday I looked into the receiver updates feature, but found out my receiver’s s/w is up-to-date, so didn’t install the updater. It was like pulling teeth to get Dex tech support to verify if my sw was the latest, so that I wouldn’t waste time installing the updater on my PC just to find out there was no need to. I expected the tech to know the sw revision off the top of his head.

I’ve .called Dex at least 5 times. :slight_smile:


#16

Oh, NO!, you didn’t!! :slight_smile: Big Sammy fan here, too. Love my S7. The camera is so good, my poor Nikon feels abandoned. Even when on vacation, nearly all my photos are taken with the S7. Technology!


#17

I have always used an iPhone. I am hoping to start looping and have a Samsung S6 on order to use as a CGM receiver and to run Android APS. My iPhone is always mislaid somewhere, or on charge. It seems sensible to have a dedicated device to use only to run Xdrip and the loop software. I will continue to use the iPhone as a smartphone.


#18

My apologies for the late response but will answer for future readers. If you try to have 2 phones act as a receiver, it won’t work. But If you have 1 phone acting as a receiver and then other phones as followers it works fine. (SAMe as witb Using dexcom g5 mobile). You can also use a traditional receiver along with the 1 phone receiver with No issue.


#19

Dexcom G5 mobile app is no longer working for me upon updating my Google Pixel 2 XL to Android 8.1. As I open the app it simply crashes during the startup. Has anyone been encountering same issue any help?

Update: Got the error fix simply by doing an uninstall and re-installation of the app.


Shawn Yadav
Showbox Tutuapp


#20

I suppose I will never be able to use the app because they only have Samsung and Pixel devices supported, with seemingly no intention of supporting others.


#21

Officially, you are correct.
In reality, there are ways to get it to run on a lot of android phones.