When I got my phone in July, I didn't even consider that it would mess up my blood glucose monitoring. I have a Dexcom G7 continuous glucose monitor and wear a sensor with a built-in transmitter on my arm, which then pairs with a device such as a smartphone. I can then, through a lovely free app that some kind soul provided, run that from my smartphone through my watch face through what's known as a complication on my Samsung watch. This was all working splendidly on my 3-year-old Samsung Galaxy Z Flip 4 phone and Galaxy 5 Watch.
Then I came across a deal on T-Mobile for the upgraded version of my phone, the Flip 7, that essentially gave me credits that made the phone, which is usually $1100, free except for taxes and activation, plus a preorder incentive of 512 GB storage rather than the standard 128 GB. Since I'd almost capped my storage on my device and had kept it a long time, through three iterations of the Flip, I thought that was a pretty good deal, plus I didn't mind getting locked into the credits because I've been a T-Mobile customer for 25 years (okay, I'm not happy about the Starlink partnership, I will admit).
The problem is, Dexcom has to test new phones to check the compatibility with their applications, the Dexcom app and their Clarity app, and neither of those are yet because they haven't been tested with my new phone. You can check it on their compatibility page. This is for the G7, but you can hit a tab for the G6 system as well. The Stelo has a different page altogether, so you'll have to search that.
Today, while doing my periodic checking (they update regularly, and it populates with each day as the most recent list), the companion phone, in fact, the bigger phone that was released at the same time, the other foldable, the Samsung Galaxy Z Fold 7, is now listed on the page. That might mean mine will be soon, so I'm excited.
By the way, if you can't use your smartphone, all is not lost. There is a receiver you can pair the sensors to, and that will provide readings. I've always had a receiver and have paired it to both phone and receiver, to have a backup, as it can be paired to two devices at once (remember, the watch just piggybacks off the phone, sharing data from it).
For more information on that watch app, look for the Gwatch app in the Google store if you're using a watch that uses the Wear app for its settings, etc. and has complications. There is another for older watches in the Samsung Galaxy store. There is a Facebook group that is helpful for questions. It's a private group, so if you can't join, let me know and I can send an invitation, or you can ask me for technical help and I might be able to help you with the basics.
Here's a picture of what it looked like when the complication was working on the watch. I could just look down and see if I were getting low or not. Since I'm not supposed to drive if I'm under 100, that's useful info. In the example, my blood sugar was very, very low on waking up (my phone and receiver had probably woken me up to an alarm), as it was only 39. It's there on the top. Not only was I not going to drive, I was dangerously low. I'd have had some orange juice or glucose tabs to get it up to at least 80 before I did much of anything else, and definitely not gotten behind the wheel until it was higher. Fortunately, it was Sunday, so I wasn't going anywhere, but that was probably why I took a picture, because it was an outlier. I don't normally go so low, thankfully. This was sometime last year, I think. Oh, and the arrow means it was falling.
.png)
No comments:
Post a Comment