G7: yesterday low battery warning, today Sensor Failed 8

[ovinator]

Hi,
anyone encountered this already or has an idea?
Yesterday the G7 Sensor after 5 days:
"Transmitter battery has dropped to: 276 it may fail soon" failure message in the Android notification section. I ignored it.
Since this morning voltage is at: A 278, B 213 (no change between 8 am and 5 pm).

Now in the main xdrip window as well as in system status, "Sensor Status: Sensor Failed 8"

No real indication in log.

Just updated to latest version without change.

Any one am idea what to do? Is it just a bad sensor?

Samsung A52, recently updated to Android 14 (15 Sep - with the predecessor Sensor that worked well)

[Navid200]

It helps if you post a screenshot of the Dex status page.

[ovinator]

Yesterday evening:

This morning:

This afternoon:

Here you are.

[Navid200]

Can you provide a screenshot of the battery voltage logs?
https://navid200.github.io/xDrip/docs/Dexcom/BatteryVoltageLogs.html

[ovinator]

[WesSec]

1.4.2024 / 30.9.2025

Damn, was just researching why i'm getting a sensor failed 8 error and my dates match exactly yours, guess it was a bad batch

[Navid200]

The only way to know if something is wrong with G7 is to use Dexcom app for verification.
There is no way to be sure just because something does not work with xDrip.

[WesSec]

I tried connecting it to the G7 app on another phone, but it wouldn't even connect anymore, probably the battery is depleted

[Navid200]

That is a possibility as long as you have checked with a scanner to make sure it is not transmitting: https://navid200.github.io/xDrip/docs/Bluetooth-Scanner.html
If you see that it is not transmitting after having been inserted, you should use the magnet trick:
https://navid200.github.io/xDrip/docs/Dexcom/G7_Troubleshooting.html
If that doesn't fix it, I guess it has to be damaged.

[WesSec]

just to clarify and make sure we're on the same page, the sensor was working fine for 5 days, the battery level was reported low, but did not have a significant decrease the last logs, i called dexcom and they replaced it without issue, i just found it interesting that this sensor is probably from the same batch as reported by OP :)