G6 Anubis Transmitter randomly unpairs, sends pair request, then stops sensor upon accepting the request

[breckstenson]

Hi everyone. I have a Samsung Galaxy S24U running Android 15. I use xDrip with AAPS and an Anubis G6 transmitter and up until the other day have had no problems. A few days ago, my transmitter randomly disconnected. It was towards the end of its battery life, so I changed the battery. After getting it to pair with my phone, I started a new sensor. The following has been happening endlessly since then:

• 50 minute sensor warmup
• sensor starts giving readings, some wildly offbase
• 30mins - a few hours pass with some noisy readings
• Transmitter unpairs completely and promps to pair again
• Either:
  • I accept the request. Sensor is immediately stopped, and I must re-start it from the beginning. Repeat the above events
  • I deny the request. The sensor does not stop, but it does not give any readings. After a minute or so, I am prompted again.

I am truly at my witts end here. I have tried the recommended settings listed in the documentation, random settings suggested by other users with similar problems, updating xDrip, downgrading xDrip, re-installing xDrip, forgetting the device, putting an incorrect transmitter ID in then putting in the correct one, you name it. EDIT: I forgot to mention: I have checked to ensure xDrip is not battery optimized and have even set it as a "pinned" app in my phones recent apps menu.

I will send my logs in a few minutes with a message containing "bubbyboo." I have seen the devs request the OB1 logs, so I have those enabled as well. Please help!

[jamorham]

I don't think this is an xDrip issue or that there is anything we can do based on the fact that the sensor session is also stopping by itself. It points to an issue with the transmitter. I would suggest contacting Anubis for support. You could try changing the battery again if it could be related to poor battery contact.

If the transmitter was unpairing and the sensor session was not stopping then I would say that it is a phone issue which is particularly common with Samsung and which google have put a workaround in Android 16 so in that case I would be recommending to update to Android 16.

[Navid200]

As mentioned already, if the battery keeps disconnecting, the transmitter is getting hard reset every time. That could explain the unpairing.
Every time the battery disconnects and reconnects, the transmitter will start from scratch. On your status page, you can see:
Transmitter Days: 0
Battery Last queried: 3 hours ago.
After a hard reset and after a successful reconnect, those two will both go back to 0.

You could also have incorrect settings.
There could also be a combination.

It doesn't hurt to check your settings. For example, by any chance, do you have the Allow OB1 unbonding under Dex Debug Settings enabled? If yes, that along with other incorrect settings could lead to the unpairing.

This shows all the recommended settings:
https://navid200.github.io/xDrip/docs/G6-Recommended-Settings.html

Since you use a Samsung, in addition to disabling battery optimization, you should also review this:
https://dontkillmyapp.com/samsung

[breckstenson]

Thank you for the information! I think you may be right that its an issue with the battery disconnecting. I've tried a sensor with a stock transmitter for now, and it seems to be working.