Device is marked as bonded but we are being asked to bond so attempting to unbond first

[Navid200]

xDrip version: 2020.11.27

G6 8K

Moto G Power (2020)

It is Andoid 10, not 11.

All xDrip settings are the recommended settings.

Expected behavior

After the user taps on pair in response to the pair request once, the pair request should never appear again.

Actual behavior

This is not the frequent pair request. xDrip has already been updated to November 27, 2020.
But, occasionally (once every few days), the device unpairs.

Steps to reproduce the behavior:

I cannot reproduce this issue

@nickb24 @jamorham I'm so sorry for tagging you guys. I have never seen this before. It is on facebook. I don't understand why this happens.

[Navid200]

I have already asked the user if she had an old phone with xDrip or Dexcom app on it. Waiting for a response.

[Navid200]

I hope that it is another device that is competing for attention and causing the unbonding. I will update as soon as I hear back. So, I am closing this.
But, we can still use it to communicate. So, please let me know if you have any ideas.

[Navid200]

The only other device is the Dexcom receiver.

[tswire]

Adding to this.

Samsung Galaxy S21 Ultra Android 11 Feb 1, 2021 Security patch (most updated version) Dexcom G6 All xdrip settings correct based on posted recommendations Running xdrip nightly Feb 11th version (was on most recent with same problem, downgraded to Feb 11th, no change) Happens daily but randomly. Cannot find trigger. Only have Galaxy Watch paired as other device. I reinstalled xdrip (over existing), "forgot" transmitter in System status, asked to repair minutes later. nothing seems to fix.

[Navid200]

Would you please try the latest xDrip release, March 8, 2021?

[tswire]

will do and report back here

[tswire]

Same issue after updating to march nightly.

[jamorham]

Can you use the log upload when this has happened fairly recently and include some reference in the log upload that I can use to identify yours. Also what firmware version is reported on the G6 status page?

[tswire]

Many disconnects last night. How do I upload the log?

[Navid200]

Go to event logs. At the bottom, tap on "Upload Logs".

Include in the message 1664_tswire

Also, please post a screenshot of your system status page here, which shows the firmware version (2.27.2.98).

[tswire]

I uploaded them (twice, first one forgot to include all errors). Let me know if you got them.

[Karumble]

Hi guys, I found this while looking for the same error. I have a new Galaxy S10+ and an old S7 with the app installed but its off and it keeps ocurring every 5min. (have to accept the bonding manually) Happy to get updates. Hope it was ok to post here.

[Navid200]

@Karumble Please update xDrip at least to November 27, 2020. That will stop the frequent pairing request. It is not exactly what this issue is about. You can find more detail about the issue you are experiencing here: https://www.facebook.com/groups/xDripG5/permalink/4603084736431652

[tswire]

Interesting to note, since middle of the night when I was woken up to pair, I have had no pairing requests all day. I have confirmed that it's not localized to home (other bluetooth devices) since it did it around 7:30pm yesterday while out at an appointment. I sure hope I don't have another awful sleep due to this! lol thanks for looking into it

[Navid200]

@tswire You can go to Settings -> Hardware Data Source and scroll all the way down and tap on disable collection.

Then, use xDrip on your old phone and set it up to collect. In the morning, you can do the opposite. To enable collection, you go back to the hardware data source page and select G5/G6 Transmitter.

You should never have both phones collect from the same transmitter at the same time. So, disable one before enabling the other.

There is no way to know how long this is going to take. So, please be patient.

[vguttmann]

I had the same problems on a Samsung A40 with Android 10. I have now upgraded to the March nightly, and have so far not had any problems.

[rhyspeck92]

I am experiencing the same issue Xdrip version 2021.02.17 Samsung s21 ultra (android 11) G6 8M All xdrip settings as recommended, the device will ask to pair at least twice a day, majority of the times its early hours of the morning.

[tswire]

Sounds like a samsung s21 ultra specific bluetooth stack issue. You have exact same issues as me. I don't think the failure time matters as mine was random but only a couple times per day. For what it's worth, I switched to dexcom build your own app temporarily and solid for 2 days with no disconnects. Not promoting it just saying it works and needed something to work while the devs take a look at this

[Navid200]

Solving a device-specific issue is extremely challenging, if not impossible, when the developer doesn't have access to the specific device. So, please be patient.

[tswire]

Absolutely. 100% agree and will be patient

[rhyspeck92]

I was orginially build your own dexcom app but wanted to switch back to xdrip as I find it better for infomation, but I was getting frequent signal loss from it like 7/8 times a day from 5 mins to over 30 mins, at first I thought it might of been the new transmitter I am using so I rang dexcom and they couldn't do anything due to me being on android 11.... I may try dexcom app again until issue is resolved

[jamorham]

@tswire Sorry the log doesn't contain enough information, can you enable ob1 debugging see here: https://github.com/NightscoutFoundation/xDrip/wiki/Enabling-Debugging-for-OB1-collector and then submit log after it happens again after that is enabled. thanks

[jamorham]

Additionally, is this only happening when syncing data from glucose meter is enabled? If so please try disabling bluetooth glucose meter integration feature and rebooting phone and see if the issue still occurs. Thanks

[Navid200]

@rhyspeck92 Please use the link that jamorham has provided, and follow the instructions there, to enable OB1 debugging. When the disconnect happens next time after having enabled OB1 debugging, go to event logs and upload. Before submitting, add the following to the message to identify yourself: 1664_rhyspeck92

[rhyspeck92]

i how now enabled the OB1 debugging via the QR code in the link, i will keep you updated to see if it has helped with the pairing requests, just to add i am not using any glucose meter, just xdrip and G6. thankyou

[Navid200]

@rhyspeck92 Thanks for enabling the debugging. Please note all that does is to produce more detail logs. That is not meant to fix the issue. With more details in the logs, jamorham may have a better chance of figuring out what could possibly be causing the disconnect.

[rhyspeck92]

Ahh I see :) well I will keep you posted, when it next asks for a pair request I will screen shot the event logs and post

On Mon, 15 Mar 2021, 15:13 Navid200, @.***> wrote:

@rhyspeck92 https://github.com/rhyspeck92 Thanks for enabling the debugging. Please note all that does is to produce more detail logs. That is not meant to fix the issue. With more details in the logs, jamorham may have a better chance of figuring out what could possibly be causing the disconnect.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/1664#issuecomment-799499128, or unsubscribe https://github.com/notifications/unsubscribe-auth/APTP7GYJNBCXZIOG5DR7CV3TDYPYTANCNFSM4YPURUUQ .

[Navid200]

@rhyspeck92 Please don't do that!

The next time it happens, go to event logs and tap on "Upload Logs", at the bottom of the page. Before tapping on "Send message", add the following to the message so that jamorham knows what the message is about. 1664_rhyspeck92

[rhyspeck92]

No problem will do 👍

On Mon, 15 Mar 2021, 15:34 Navid200, @.***> wrote:

@rhyspeck92 https://github.com/rhyspeck92 Please don't do that!

The next time it happens, go to event logs and tap on "Upload Logs", at the bottom of the page. Before tapping on "Send message", add the following to the message so that jamorham knows what the message is about. 1664_rhyspeck92

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/1664#issuecomment-799516311, or unsubscribe https://github.com/notifications/unsubscribe-auth/APTP7G5XLKMPLEQCEWZQZCDTDYSILANCNFSM4YPURUUQ .

[rhyspeck92]

As requested event log has been sent when pairing request was made with OB1 debugging enable

On Mon, 15 Mar 2021, 15:38 Rhys Peck, @.***> wrote:

No problem will do 👍

On Mon, 15 Mar 2021, 15:34 Navid200, @.***> wrote:

@rhyspeck92 https://github.com/rhyspeck92 Please don't do that!

The next time it happens, go to event logs and tap on "Upload Logs", at the bottom of the page. Before tapping on "Send message", add the following to the message so that jamorham knows what the message is about. 1664_rhyspeck92

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/1664#issuecomment-799516311, or unsubscribe https://github.com/notifications/unsubscribe-auth/APTP7G5XLKMPLEQCEWZQZCDTDYSILANCNFSM4YPURUUQ .

[jamorham]

@rhyspeck92 thank you for the logs. They apparently show that the phone simply is not using the bonded connection causing the transmitter to complain. This smells like a framework bug, but it may be possible to work around. Can you confirm that you have both the Minimize Scanning and Avoid Scanning options set to enabled in the advanced G5 settings? These are the default work-arounds for Android 10+ and I'm concerned from your logs that they may not be enabled. Can you check that and if not see if they make any difference? Thanks.

[rhyspeck92]

Thanks for getting back to me I have no enabled both minimize scanning and avoid scanning to see if this helps

On Tue, 16 Mar 2021, 13:00 JamOrHam, @.***> wrote:

@rhyspeck92 https://github.com/rhyspeck92 thank you for the logs. They apparently show that the phone simply is not using the bonded connection causing the transmitter to complain. This smells like a framework bug, but it may be possible to work around. Can you confirm that you have both the Minimize Scanning and Avoid Scanning options set to enabled in the advanced G5 settings? These are the default work-arounds for Android 10+ and I'm concerned from your logs that they may not be enabled. Can you check that and if not see if they make any difference? Thanks.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/1664#issuecomment-800237886, or unsubscribe https://github.com/notifications/unsubscribe-auth/APTP7GYMSB4IRNJA6MKCBALTD5JALANCNFSM4YPURUUQ .

[rhyspeck92]

Just sent some more logs over, I did have a better connection for at least 24 hours without a pairing request but just asked for another pairing request now Thanks Rhys

On Tue, 16 Mar 2021, 13:26 Rhys Peck, @.***> wrote:

Thanks for getting back to me I have no enabled both minimize scanning and avoid scanning to see if this helps

On Tue, 16 Mar 2021, 13:00 JamOrHam, @.***> wrote:

@rhyspeck92 https://github.com/rhyspeck92 thank you for the logs. They apparently show that the phone simply is not using the bonded connection causing the transmitter to complain. This smells like a framework bug, but it may be possible to work around. Can you confirm that you have both the Minimize Scanning and Avoid Scanning options set to enabled in the advanced G5 settings? These are the default work-arounds for Android 10+ and I'm concerned from your logs that they may not be enabled. Can you check that and if not see if they make any difference? Thanks.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/1664#issuecomment-800237886, or unsubscribe https://github.com/notifications/unsubscribe-auth/APTP7GYMSB4IRNJA6MKCBALTD5JALANCNFSM4YPURUUQ .

[jamorham]

@rhyspeck92 ok try this setting as a test for a work-around: Uncheck the setting Allow OB1 unbonding - I would like to know what this does when turned off for you. What I am hoping is that even you might get a pairing request, if you ignore it then following readings may work without intervention. Could you try that and see if it helps at all? This may not work but it is the next thing to experiment with.

[rhyspeck92]

Of course I will try these settings as recommended and update you

On Wed, 17 Mar 2021, 14:56 JamOrHam, @.***> wrote:

@rhyspeck92 https://github.com/rhyspeck92 ok try this setting as a test for a work-around: Uncheck the setting Allow OB1 unbonding - I would like to know what this does when turned off for you. What I am hoping is that even you might get a pairing request, if you ignore it then following readings may work without intervention. Could you try that and see if it helps at all? This may not work but it is the next thing to experiment with.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/1664#issuecomment-801151151, or unsubscribe https://github.com/notifications/unsubscribe-auth/APTP7GZMSPBLNVFFWDY5ZA3TEC7IVANCNFSM4YPURUUQ .

[Navid200]

@rhyspeck92 Any updates?

[rhyspeck92]

Seems to be working alot better I've had no pairing requests so far but I've had a couple of sensor errors and it's kicked back in around 45 mins later

On Sat, 20 Mar 2021, 12:59 Navid200, @.***> wrote:

@rhyspeck92 https://github.com/rhyspeck92 Any updates?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/1664#issuecomment-803314740, or unsubscribe https://github.com/notifications/unsubscribe-auth/APTP7GYUAXFNV2RX72R3RL3TESLZ5ANCNFSM4YPURUUQ .

[Navid200]

I think sensor error is something else. It could be caused by anything that could cause readings that seem unexpected to the transmitter. It has nothing to do with loss of connectivity. I'm not saying you should ignore them. I'm saying we can talk about those somewhere else.

[Navid200]

@tswire Have you had a chance to try the settings @jamorham suggested? Or, are you still on the Dexcom app?

[tswire]

I am still on dexcom and just had to switch transmitters so didn't feel comfortable testing right now. Nex sensor I will. Sorry

---

From: Navid200 @.> Sent: Saturday, March 20, 2021 10:31:49 AM To: NightscoutFoundation/xDrip @.> Cc: tswire @.>; Mention @.> Subject: Re: [NightscoutFoundation/xDrip] Device is marked as bonded but we are being asked to bond so attempting to unbond first (#1664)

@tswirehttps://github.com/tswire Have you had a chance to try the settings @jamorhamhttps://github.com/jamorham suggested? Or, are you still on the Dexcom app?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/NightscoutFoundation/xDrip/issues/1664#issuecomment-803363400, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHFUB5RGREEZQ37S2GO2BD3TESWVLANCNFSM4YPURUUQ.

[Navid200]

@jamorham

Can you confirm that you have both the Minimize Scanning and Avoid Scanning options set to enabled in the advanced G5 settings? These are the default work-arounds for Android 10+

When you say default work-arounds for Android 10+, does it mean if someone installs xDrip on Android 11 and selects G5/G6, those two settings will automatically be set?

Are those two settings that anyone on Android 11 should set?

[jamorham]

@Navid200 yes those settings should automatically be set. If that isn't working then I need to review that code.

[gfginter]

I was having major issues with this since upgrading to my s21 Ultra. When it was asking to reconnect it was turning on my screen so my battery was draining like crazy as well. Minimize Scanning and Avoid Scanning options were set to disabled by default so after seeing this thread I enabled them this morning. Will report back after a day or two on my experience and can provide logs if need be.

[gfginter]

Well I can report back that there is no difference in behavior I am still getting bond state unpaired.

[Navid200]

@gfginter Thanks for reporting. Please enable detail logs: https://github.com/NightscoutFoundation/xDrip/wiki/Enabling-Debugging-for-OB1-collector

Would you please now disable "Allow OB1 unbonding" while still leaving minimize scanning and avoid scanning settings enabled?

[rhyspeck92]

Since I have enabled this I haven't had any pairing requests since

On Mon, 22 Mar 2021, 21:35 Navid200, @.***> wrote:

@gfginter https://github.com/gfginter Thanks for reporting. Please enable detail logs: https://github.com/NightscoutFoundation/xDrip/wiki/Enabling-Debugging-for-OB1-collector

Would you please now disable "Allow OB1 unbonding" while still leaving minimize scanning and avoid scanning settings enabled?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/1664#issuecomment-804411482, or unsubscribe https://github.com/notifications/unsubscribe-auth/APTP7G53JELYGYIJKNK4LO3TE6ZZ7ANCNFSM4YPURUUQ .

[Navid200]

@rhyspeck92 Please confirm you mean since you disabled "Allow OB1 unbonding". And thanks so much for the update.

[rhyspeck92]

I have disabled "Allow OB1 unbonding" and have "minimize scanning" and "allow scanning" enabled, I have been running for around a week now without a pairing request.

On Mon, 22 Mar 2021, 21:41 Navid200, @.***> wrote:

@rhyspeck92 https://github.com/rhyspeck92 Please confirm you mean since you disabled "Allow OB1 unbonding". And thanks so much for the update.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/1664#issuecomment-804414491, or unsubscribe https://github.com/notifications/unsubscribe-auth/APTP7G6HQXMXL5IVSBI5A3DTE62PXANCNFSM4YPURUUQ .

[gfginter]

@gfginter Thanks for reporting. Please enable detail logs: https://github.com/NightscoutFoundation/xDrip/wiki/Enabling-Debugging-for-OB1-collector

Would you please now disable "Allow OB1 unbonding" while still leaving minimize scanning and avoid scanning settings enabled?

I did disable AllowOB1 unbonding and it still asked to pair. I am doing it again. Should I also disable "Allow OB1 initiate bonding" ???

I have enabled the detailed logs as requested.

[rhyspeck92]

Yes Allow OB1 initiate bonding, I have this enabled

On Mon, 22 Mar 2021, 21:55 Garrett, @.***> wrote:

@gfginter https://github.com/gfginter Thanks for reporting. Please enable detail logs: https://github.com/NightscoutFoundation/xDrip/wiki/Enabling-Debugging-for-OB1-collector

Would you please now disable "Allow OB1 unbonding" while still leaving minimize scanning and avoid scanning settings enabled?

I did disable AllowOB1 unbonding and it still asked to pair. I am doing it again. Should I also disable "Allow OB1 initiate bonding" ???

I have enabled the detailed logs as requested.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/1664#issuecomment-804421520, or unsubscribe https://github.com/notifications/unsubscribe-auth/APTP7G5R6PCAKQMDGPFBQOTTE64D3ANCNFSM4YPURUUQ .