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

Navid200 commented 3 years ago

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 commented 3 years ago

@gfginter No, you should not.
You should exactly follow the advice of jamorham, the developer, in this thread, and only that.

What version of xDrip are you using. Please check on your classic status page to find out.

rhyspeck92 commented 3 years ago

It says to have it enabled in the docs, I was never told to turn it off

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

@gfginter https://github.com/gfginter No, you should not. You should exactly follow the advice of jamorham, the developer, in this thread, and only that.

What version of xDrip are you using. Please check on your classic status page to find out.

— 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-804425009, or unsubscribe https://github.com/notifications/unsubscribe-auth/APTP7G3BZXY7DZX4WOORII3TE647LANCNFSM4YPURUUQ .

gfginter commented 3 years ago

I will only follow jamorham's advice, thank you. I am on the latest nightly 17cbcf0-2021.03.08

Navid200 commented 3 years ago

@rhyspeck92 I fear multiple conversations are going on. That's why some of us quote people to make it clear whom we are talking to.

I understand that you are happy because after following jamorham's work-around approach, you have not had any more pair requests. That is great. If a new release comes out to address the work-around, I will post here to inform everyone.

In the meantime, please don't change any of your settings and report if the problem occurs again. Thanks

rhyspeck92 commented 3 years ago

No problem, thanks again for all the help and support, if any problems arise I will update you 🙏

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

@rhyspeck92 https://github.com/rhyspeck92 I fear multiple conversations are going on. That's why some of us quote people to make it clear whom we are talking to.

I understand that you are happy because after following jamorham's work-around approach, you have not had any more pair requests. That is great. If a new release comes out to address the work-around, I will post here to inform everyone.

In the meantime, please don't change any of your settings and report if the problem occurs again. 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-804429599, or unsubscribe https://github.com/notifications/unsubscribe-auth/APTP7G5EWX6SX772BU4UFYLTE66C3ANCNFSM4YPURUUQ .

gfginter commented 3 years ago

I successfully made it through last night without disconnecting. Of course I will continue to monitor throughout the day and let you know if I begin to experience issues again. Thanks for all you do.

vguttmann commented 3 years ago

For anyone reading this in the future: An update to Android 11 seems to be safe. I updated my Samsung A40 this night, and so far, there were no problems with the March 26th nightly build.

Navid200 commented 3 years ago

@gfginter and @rhyspeck92, any updates?

rhyspeck92 commented 3 years ago

Mine seems to have been working fine :) occasionally but not often I don't get a reading for like 7/8 mins instead of the normal 5 mins but apart from that it's been perfect

On Wed, 31 Mar 2021, 22:29 Navid200, @.***> wrote:

@gfginter https://github.com/gfginter and @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-811478272, or unsubscribe https://github.com/notifications/unsubscribe-auth/APTP7G5NKGIJKBBBIVXTZPDTGOH5DANCNFSM4YPURUUQ .

gfginter commented 3 years ago

@Navid200 I have had no issues either. Have been upgrading to the nightlies with no problem.

Roozeboom007 commented 3 years ago

xDrip version: 2021.05.10

G6 8H

OnePLus 7T

It is Andoid 11.

All xDrip settings are the recommended settings.

Twice a day Signal loss, which is not automatically resolved. Restarting the phone does help. With xDrip version 2020.07.25 this problem was not present

charliegenge commented 3 years ago

Hi,

@jamorham I've been discussing this issue with @Navid200 on the Facebook group. I have all of the recommended settings except that 'Allow OB1 unbonding' is disabled.

I'm using: Xiaomi Mi9 on MIUI 12.5 (android 11) Xdrip nightly build 2021.08.18 G6 sensor Am looping with AAPS

Having experienced issues on android 10 (and after discussing with @Navid200 ) I upgraded to android 11 yesterday and was successfully connected until 16:00 today when I moved out of range of my phone for the first time and got the "Device is marked as bonded but we are being asked to bond.." message in the logs. It now only connects once or twice every hour (hard to tell exactly from the logs or the screen as it's backfilling the missing data).

Thanks for anything anyone can help with...I'm close to giving up on the phone and getting one that works better with xdrip.

I've uploaded the logs with comment '#1664_charliegenge'

Rebooting phone does help, but only temporarily.

Thanks!

jamorham commented 3 years ago

Xiaomi phones often remove the battery optimization whitelist setting that xDrip requests after a reboot. Normally xDrip will detect this and ask for it again when you first open the home screen or enter the settings page in xDrip. I suspect this could be related (note the slow wakeup) - Investigate the phone settings to see if there is any other "power saving" or other restriction being applied to xDrip which may be present in the new android version. Wherever possible, whitelist xDrip from any restrictions to background processing.

charliegenge commented 3 years ago

Hi @jamorham ,

Xdrip is whitelisted with no battery optimisation (as far as I can tell) and it has no restricted permissions.I've not noticed xdrip asking to be whitelisted again after a reboot, the phone appears to be maintaining the battery status.

bsw-del commented 2 years ago

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 <#1664 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/APTP7G6HQXMXL5IVSBI5A3DTE62PXANCNFSM4YPURUUQ .

Hey, Just wanted to say, ran into this problem on Pixel 6, changed settings as described here, and yes it is missing signal occasionally, but no longer requesting the pairing. Thanks for this, so far so good.

supercoiler commented 2 years ago

Hey, also ran into this problem on my Pixel 6 Pro using the same exact settings from my S21+. I then disabled "Allow OB1 unbonding" and had the other two settings already. Also unchecked the Samsung buggy workaround. It no longer asks to re-pair but still asks to bond when it is. Sometimes it goes as long as 45 minutes and the only way to get it going again is to unpair the sensor. Then it connects normally. But it never seems to work longer than 2 hours without messing up again. May temporarily go back to my s21+ until this problem is resolved. Or until that upgrades to Android 12 and if I have the problem again. I really love Pixel phones, only downfall is we get updates first and become the guinea pigs...

Navid200 commented 2 years ago

@supercoiler

Also unchecked the Samsung buggy workaround.

Samsung workaround should not be disabled by anyone.

supercoiler commented 2 years ago

Really? Even if you're not using a Samsung?

Navid200 commented 2 years ago

Really? Even if you're not using a Samsung?

xDrip only uses the Samsung work-around if it is needed. But, if you disable the setting, xDrip will not be allowed to use it even if it needs to.

icnich commented 2 years ago

Has this original issue been remedied?

Navid200 commented 2 years ago

@icnich I ask everyone to go through these steps: https://navid200.github.io/xDrip/docs/Intermittent.html There are a few devices that need to disable "Allow OB1 unbonding". For example, Samsung S21.

If you are asking if xDrip works by default for all devices with the default settings, the answer is no.

icnich commented 2 years ago

@Navid200 thank you so much for the super quick reply (and just, you know, your contributions in general)! I'll run through these

JoernKO commented 2 years ago

Hi, I have had a new smartphone for a few days, a Samsung S21 Ultra with Android 11. Unfortunately, I have constant disconnections between the Dexcom G6 sensor and XDrip. A connection is only established after restarting the smartphone and only lasts about an hour. After that, the connection is no longer re-established. I have granted the app all the required permissions. It worked without any problems with the previous Samsung S10 smartphone. I am happy to help with troubleshooting.

I have exactly the same behavoir and the Message "Device is marked as bonded but we are being asked to bond so attempting to unbond first"

As mentioned in the thread, I have now disabled the setting "Allow OB1 unbonding". Was this really a solution for the problem.

It looks like that this setting prevents the connection from beeing disconnected.

22:09 "Device is marked as bonded but we are being asked to bond so attempting to unbond first" 22:09 "Would have tried to unpair but preference settings prevents it. (unbound)

Any help with this problem?

Regards Joern

Navid200 commented 2 years ago

@JoernKO Yes, for your phone, that is the solution. Make sure you go over every setting here: https://navid200.github.io/xDrip/docs/G6-Recommended-Settings.html

Then, for your phone, disable "Allow OB1 unbonding" only from those recommended settings.

Please open a discussions and I can see why you are still having problems if that doesn't help: https://github.com/NightscoutFoundation/xDrip/discussions

Navid200 commented 2 years ago

Would everyone please try the latest Nightly and see if enabling "Allow OB1 unbonding" still causes problems?

https://github.com/NightscoutFoundation/xDrip/releases/tag/2022.06.09

bsw-del commented 2 years ago

Would everyone please try the latest Nightly and see if enabling "Allow OB1 unbonding" still causes problems?

https://github.com/NightscoutFoundation/xDrip/releases/tag/2022.06.09

Trying it out now.

charliegenge commented 2 years ago

This seems to have worked for me, thanks so much for your help

On Thu, 9 Jun 2022, 17:28 bsw-del, @.***> wrote:

Would everyone please try the latest Nightly and see if enabling "Allow OB1 unbonding" still causes problems?

https://github.com/NightscoutFoundation/xDrip/releases/tag/2022.06.09

Trying it out now.

— Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/1664#issuecomment-1151348841, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACH6KC3GM7HUSJ47TNO62MLVOILURANCNFSM4YPURUUQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

Navid200 commented 1 year ago

The G6 collector has been tweaked multiple times since this was opened. This problem must have been resolved already.

Please have a look here for the current suggested approach: https://navid200.github.io/xDrip/docs/Intermittent.html

NightscoutFoundation / xDrip