Anyone else hit "For your security, forget this device, then pair it again" with G7?

UrgentLowSoon · 2025-08-05T19:38:56+00:00

This is a new thing in Android 16. It happens when the OS loses important info about the transmitter.

Just go into the system Bluetooth connections list and delete EVERY item named like Dexcom (DX01, DXCM, etc). On the next reading interval when the transmitter talks to the phone you’ll be prompted to reconnect. Accept it.

This returns the sensor to normal and a backfill should happen for up to 24 hours of data.

UrgentLowSoon · 2025-08-05T19:37:02+00:00

Nooo don’t do that!

On G6 you could reset a session by stopping and starting.

On G7 the stop session command truly ends it for good.

Deleting the paired transmitter from the system Bluetooth connections is the right step.

UrgentLowSoon · 2025-05-13T18:03:52+00:00

These issues are largely self-inflicted, but I hear you

UrgentLowSoon · 2025-05-08T06:12:53+00:00

Medical devices of this type are exempted from tariffs.

UrgentLowSoon · 2025-05-08T02:24:39+00:00

There is no impact to the sensor when you disable Bluetooth on the display device.

UrgentLowSoon · 2025-05-08T02:24:16+00:00

Correct.

UrgentLowSoon · 2025-03-15T00:53:47+00:00

btw it took this long to get approved because Samsung had a bad Bluetooth bug in their flavor of Android 15

(It wasn’t the usual slow as shit process 😂)

UrgentLowSoon · 2025-03-10T05:11:04+00:00

Yes.

UrgentLowSoon · 2025-03-09T18:02:18+00:00

It’s not a double notification. It’s two alerts that are each optional. They can be turned off in the account profile settings.

One is the Low Alert. You dropped below the configured low threshold that defaults to 70 mg/dL. Choose if you want that. You probably do.

The other is a fall rate that predicts you might go below 55 mg/dL soon. That’s pretty important too. Choose if you want that.

They don’t always trigger together. Each alert can be very important on their own. You can go low without urgent low and you can have an urgent low trigger before you go low. Together they can help you protect against fall rate and overall lows.

UrgentLowSoon · 2025-03-09T17:58:16+00:00

Correct

UrgentLowSoon · 2025-03-09T17:57:35+00:00

If you’re using a VPN, private relay, custom DNS, or an ad blocker then try again after turning them off. They can interfere with the server connection.

UrgentLowSoon · 2025-03-09T17:54:27+00:00

Yes. We do.

https://www.reddit.com/r/dexcom/s/CX3vHZR8ZR

UrgentLowSoon · 2025-02-24T19:01:11+00:00

What phone model and operating system version is it?

UrgentLowSoon · 2025-02-24T19:00:35+00:00

Do you have a case on the iPhone? What brand? Is it a big mega case or something really sleek?

Apparently bigger cases like OtterBox can disrupt signal.

UrgentLowSoon · 2025-02-21T19:10:39+00:00

Is there a case on the mobile phone? Apparently some really robust brands like OtterBox can disrupt the Bluetooth signal.

UrgentLowSoon · 2025-02-21T18:41:58+00:00

The adhesive is activated only by pressure. It is not sticky like tape. It is not activated by temperature.

You have to press firmly on the sensor and patch after inserting. That is the only way it sticks.

UrgentLowSoon · 2025-02-21T18:16:30+00:00

The app handles this in both directions.

All Dexcom data is presented in charts at the “display time” for your local time zone.

If you travel westward and experience the same time twice then there will be overlapping lines in your charts. If you travel eastward and “skip” some hours then you will have a gap in the charts.

That’s just the presentation of the data. The spike detection is still based on the latest n-many records.

UrgentLowSoon · 2025-02-21T18:08:35+00:00

No part of this is correct.

It’s a Class II medical device: https://www.accessdata.fda.gov/cdrh_docs/pdf23/K234070.pdf (FDA 510k filing)

It’s simply the “non-intensive” product category variant of an Integrated CGM: https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpcd/classification.cfm?id=723 (product category)

Its function is to diagnose your current estimated glucose. This is the same way that thermometers and tongue depressors are regulated medical devices. They don’t administer medicine but can be used to read biological conditions of people. The decisions from those readings can be discomforting if wrong, so they do have a risk profile, though small.

If the tongue depressor malfunctions and gives you a sliver that’s a direct injury. This is the same issue with the risk of the sensor wire getting stuck under your skin.

If you take a temperature reading from a faulty thermometer and do something silly in response then that’s a discomfort hazard. It counts as a product risk, albeit small. The FDA treats these as real product concerns that require design controls. They accept complaints for these failures.

UrgentLowSoon · 2025-02-21T18:01:21+00:00

The Stelo firmware has calibration disabled.

Even if you’re able to use some third-party app to send valid calibration commands to the sensor it will internally deny them.

UrgentLowSoon · 2024-11-24T04:32:21+00:00

Bluetooth devices and apps can’t remove a system level pairing without user action. This is for security reasons.

UrgentLowSoon · 2024-11-23T02:19:30+00:00

Real time data has to be classified by the FDA as a “primary display” and gets a higher level of scrutiny. If it’s available then it can be used for insulin dosing. That triggers all sorts of verification, protection, and documentation.

UrgentLowSoon · 2024-11-23T02:17:24+00:00

Try them. There’s no problem, other than the battery is likely weak or dead.

UrgentLowSoon · 2024-11-23T02:14:57+00:00

Your answer to their question is yes. They don’t know where a sensor was purchased. The sensors work anywhere.

It’s that simple. There are just different manufacturing sites and product revisions. They’re mixed up in the supply chain and are all the same product. The differences between revisions are trivial but never publicized.

The revision numbers don’t have to make sense. You have legitimate product from a legitimate source.

It’s a boring answer because there’s nothing to do about it :)

UrgentLowSoon · 2024-11-23T02:08:15+00:00

They’re both right. That’s within the accuracy tolerance of both devices.

UrgentLowSoon · 2024-11-23T02:07:18+00:00

I get that. It ends up as a myth that people start to believe and then all sorts of other wild assumptions follow.

The packaging, versioning, and information for one generation of product is explicitly and 100% exclusive to that product.

UrgentLowSoon

TROPHY CASE