Unable to read Miaomiao data after upgrade to Android 10

[btdkomplex]

Title says it all really. Was working find until the latest Android upgrade. Can't find any errors anywhere. Changed a lot of the bluetooth settings around and no luck. xDrip can see the MiaoMiao device in bluetooth but just fails to connect.

If I switch to Wear collection it is able to perform one data collection before then starting to fail again.

Not sure what logs I'm able to provide as they have no errors.

[igoneporto]

I am having same problem. It was working perfectly till monday. And since day, can not anymore read with xdrip.

[igoneporto]

However, my android is not 10, but 9....so i think thats not the origin of the problem. Which xdrip version are u using @btdkomplex ??

[tzachi-dar]

The logs in your case says that reading data from the MM is OK.

How does your calibration graph look like?

We need to get more loggings to try and understand the problem. Can you please go to settings->less common settings->extra loggings->extra tags for logging And there add: bgreading:v and send us the results.

[igoneporto]

@tzachi-dar if u are talking to me, i admit that with the language change, i dont not what should i include in the bgreading:v case.

I have erased all the callibrations today and i can not enter new callibrations. I will change the sensor today and try resetting miao again. Dont know but i think its a bluetooth problem, although i am not able to find which is the problem. Thanks.

[tzachi-dar]

I think you need to move your phone to english to see where to set the logs. In any case, if you see a line like: "We have all the data that we need 363 checksum_ok =true " This means that xdrip has connected to the MM, got a full reading, this reading is correct. For some reason xDrip was not able to calculate BG from that, but no problem with bluetooth.

[igoneporto]

The problem is that every log i get are errors....

El mié., 4 sept. 2019 13:39, tzachi-dar notifications@github.com escribió:

I think you need to move your phone to english to see where to set the logs. In any case, if you see a line like: "We have all the data that we need 363 checksum_ok =true " This means that xdrip has connected to the MM, got a full reading, this reading is correct. For some reason xDrip was not able to calculate BG from that, but no problem with bluetooth.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/996?email_source=notifications&email_token=AK2JFJF4GFD7ETTKQKIJR6TQH6NAHA5CNFSM4ITN4IKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD53I5II#issuecomment-527863457, or mute the thread https://github.com/notifications/unsubscribe-auth/AK2JFJECYKOSXTE3OGNK7OTQH6NAHANCNFSM4ITN4IKA .

[igoneporto]

Will try later to reinstall everything and try with a new sensor. And comment back here.

Thanks

El mié., 4 sept. 2019 13:49, Igone Porto igoneporto@gmail.com escribió:

The problem is that every log i get are errors....

El mié., 4 sept. 2019 13:39, tzachi-dar notifications@github.com escribió:

I think you need to move your phone to english to see where to set the logs. In any case, if you see a line like: "We have all the data that we need 363 checksum_ok =true " This means that xdrip has connected to the MM, got a full reading, this reading is correct. For some reason xDrip was not able to calculate BG from that, but no problem with bluetooth.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/996?email_source=notifications&email_token=AK2JFJF4GFD7ETTKQKIJR6TQH6NAHA5CNFSM4ITN4IKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD53I5II#issuecomment-527863457, or mute the thread https://github.com/notifications/unsubscribe-auth/AK2JFJECYKOSXTE3OGNK7OTQH6NAHANCNFSM4ITN4IKA .

[btdkomplex]

Oddly it started to work again after disabling bluetooth, force quitting xDrip, restarting the phone, and resetting the Miaomiao. It then continued to fail to take readings for another 10 minutes or so and then started working as if nothing was wrong.

[reedhuish]

XDrip worked fine for me until yesterday, when I upgraded to Android 10. I have a Pixel 3 XL phone. Everything was working perfectly until the Android 10 upgrade. Tried a new Libre sensor with the MiaoMiao charge & reset. This always works. But it is the Android 10 to MiaoMiao bluetooth communication issue. XDrip can see the MiaoMiao (on Bluetooth Scan), and I select the MiaoMiao, then XDrip says "communicating to device". And nothing happens. It never gets any data from the MiaoMiao. It is a bluetooth communication issue. When I use NFC instead I get the readings perfectly. Any update for XDrip?

[tzachi-dar]

@reedhuish Can you please post a picture of your logs?

[reedhuish]

@reedhuish Can you please post a picture of your logs?

You can see some glucose readings on my xdrip (yes, I'm running low this morning). Those were all done via NFC capture.

Bluetooth doesn't work to my miaomiao / libre combination (and it worked PERFECTLY as of yesterday, before the upgrade to Android 10 on my Pixel 3 XL)

Sorry if I posted too many logs :(

Thank you,

Reed

[reedhuish]

oops. I forgot, and here are my bluetooth settings in Xdrip (yes, I have the very latest version of XDrip with a 1 Sep 2019 release date)

Trust auto-connect always has to be turned off with any phone I've used (Samsung Note5 and my Pixel 3 XL)

Reed

[reedhuish]

oops. I forgot, and here are my bluetooth settings in Xdrip (yes, I have the very latest version of XDrip with a 1 Sep 2019 release date)

Trust auto-connect always has to be turned off with any phone I've used (Samsung Note5 and my Pixel 3 XL)

Reed

On Sat, Sep 7, 2019 at 11:44 AM Reed Huish reed@huish.net wrote:

You can see some glucose readings on my xdrip (yes, I'm running low this morning). Those were all done via NFC capture.

Bluetooth doesn't work to my miaomiao / libre combination (and it worked PERFECTLY as of yesterday, before the upgrade to Android 10 on my Pixel 3 XL)

Thank you,

Reed

On Sat, Sep 7, 2019 at 10:37 AM tzachi-dar notifications@github.com wrote:

@reedhuish https://github.com/reedhuish Can you please post a picture of your logs?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/996?email_source=notifications&email_token=AKUE5NGZHRNZUVP3DV2P42TQIPREPA5CNFSM4ITN4IKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6E53JY#issuecomment-529128871, or mute the thread https://github.com/notifications/unsubscribe-auth/AKUE5NDQVO6ZRWXVAFK7BD3QIPREPANCNFSM4ITN4IKA .

--

============================================================= Reed Huish Mesa, Arizona, USA Tel: (+1) 602-476-1085 Email: reed@huish.net SKYPE: reedhuish

--

============================================================= Reed Huish Mesa, Arizona, USA Tel: (+1) 602-476-1085 Email: reed@huish.net SKYPE: reedhuish

[tzachi-dar]

Thanks @reedhuish It seems that there are no signs of bluetooth activity on your phone. Can you please: go to settings->less common settings->extra loggings->extra tags for logging And there add: bgreading:v,DexCollectionService:v

Let it run for 15 minutes and post the logs again.

By the way are you using wear, or using your phone directly?

Thanks Tzachi

[reedhuish]

hello Tzachi, I really do appreciate your help on this. Many many thanks. I've felt crappy even being off CGM for 1 day. :(

I am using the phone directly (Pixel 3 XL bluetooth) to grab the glucose readings from my MiaoMiao (which is connected to my Freestyle Libre)

I do have an Android Wear watch, which does NOT collect any glucose readings -- I wish that part worked, but it doesn't (grabbing the MiaoMiao readings directly from the Android Wear watch doesn't work).

The Android Wear only displays the glucose readings, when my Pixel 3 XL sends it to my Android Wear Ticwatch E.

I know you are not doubting me. But just to confirm, I did not change a thing in XDrip. It was communicating just perfectly. Pixel 3 XL to my MiaoMiao / Libre combination....

UNTIL last night I upgraded to the Android 10 version on my Pixel 3 XL.

Then, after the Android 10 upgrade, it will "see" the MiaoMiao in the Bluetooth Scan (see the images below), and it says "connecting to the device", but it doesn't get any glucose readings from the MiaoMiao. Nothing. Nada. Zip.

(the only readings it gets is when I do an NFC scan)

And my Pixel 3 XL bluetooth is working perfectly. Been busy on phone calls this morning (through my bluetooth headsets).

In summary, XDrip is not compatible with bluetooth on Android 10.

Thank you, Reed

FYI - my MiaoMiao is device: E0:92:F2:85:B5:F1

[tzachi-dar]

It seems that you are getting status 133 on your phone while trying to connect which is not a good thing.

There are two things that you can try and do: 1) Turn the value of trust autoconnect to on (this is on settings->less common settings->bluetooth setting). 2) Install an application that is called "nrf connect". This application when opened will scan for devices and show the miaomiao. Press connect there. If it will succeed, there is a chance that xDrip will also connect to the miaomiao.

I hope this helps.

[reedhuish]

I did what I wrote:

1. Autoconnect turned on (see screen shot)
2. Installed NRF Connect and connected to my MiaoMiao. It says connected not bonded.

But nope. XDrip didn't grab readings from MiaoMiao.

I tried doing the bluetooth / reset thing in XDrip, and it found MiaoMiao on the scan, but still won't grab any glucose readings.

FYI - MiaoMiao has their own app, called Tomato, which they recommend (in addition to XDrip and Spike).

I tried Tomato again (after disabling XDrip, which you can now do in Android 10 -- pretty cool!). Tomato will "see" the MiaoMiao, but this app also will not grab any glucose readings from the MiaoMiao.

Maybe that is called "binding" or something like that.

So everything I've tried, XDrip, Tomato, now even Glimp.

Android 10 updated bluetooth communication. Something just isn't working now with bluetooth communication to external devices.

And when more people upgrade to Android 10, I think more and more clients will have issues connecting from XDrip to their bluetooth glucose device.

[jannesaukko]

I have same issue. Can this be fixed somehow?

[loop2016]

I have the same issue after the Update to Android 10. But on my OnePlus 7 and my Dexcom G6. No readings.

[reedhuish]

the solution for me is posted on:

https://github.com/NightscoutFoundation/xDrip/issues/1001

I followed the instructions posted by: elrufoelrufo

[GlimpRemco]

Same issue after upgrading my OnePlus 7 pro to Android 10. No connection with Xdrip+ or Tomato

[loop2016]

Same issue after upgrading my OnePlus 7 pro to Android 10. No connection with Xdrip+ or Tomato

Wasn't the instruction from @reedhuish helpful to you?

[jannesaukko]

Yes it works now but i have to do same procress always again when xdrip disconnects miaomaio. This happens among other things every single night.

[GlimpRemco]

Thank you, after executing the instructions, Xdrip can connect again

[James866]

Hi Guys,

Hope you can help me solve this Bluetooth Android puzzle as I am having the same issue Btdkomplex describes. Every night between 3 and 4 am my phone (Oneplus6T) shows 'missed reading' on Xdrip+ (6d4d283-2019.10.27). This occurs since the Android upgrade to v10.3.0. Previously I had NO issues what so ever.

It seems that the Libre sensor itself is working fine (since I can use Abbott's LibreLink app via NFC without problems). Also there appears to be a bluetooth connection (in system status xDrip+ is showing 'connected' and in the event logs I see these "We have all the data that we need 363 checksum_ok = true" lines.

I already disabled all the power saving options, 'digital welfare' settings, etc to make sure the BT connection isn't lost due to some power saving mode.

Furthermore, I performed elrufoelrufo's instructions without any luck. Even toggling the 'trust auto-connect' option off or on doesn't make a difference.

There are a few options as workaround that seem to get the readings back:

• rebooting the phone, followed by turning BT off and on several times, together with scanning and connection to the MM in xDrip+
• connection the phone to the carkit BT
• taking the MM off, resetting it (many) times, followed by the same BT toggling and reconnecting steps previously described

As you can imagine, neither is a 'welcome' option in the middle of the night.

Hope anyone of you has an idea what this annoying problem can solve... many thanks in advance for your help! I attach some screenshots of the BT settings and error logs beneath.

[tzachi-dar]

@James866 Is there a new power saving feature that needs to be disabled?

Can you try the different combinations of the following setting: 1) trust auto connect. 2) use scanning. 3) close gatt on ble disconnect.

And see if any of them works for you (Since there are 3 switches, there should be 8 combinations)?

[loop2016]

I had similar problems with my OnePlus 7 and its aggressive power saving. Please check this thread for further information.

[James866]

Thanks guys for your quick replies! @tzachi-dar I switched all three to 'enabled' now. will let you know tomorrow how it went through the night. @loop2016 thanks for the suggestion! I read through the thread(s). The deep optimisation and sleep standby optimisation were already both disabled (had a previous issue with them). I read about the 'minimize scanning' but I am not using a Dexcom (MM and Libre combi), so I cannot tweak this setting, isn't it.

[James866]

Hi guys, I promised to get back to you, however the first night I had to work, so wasn't really sure if it was really the different settings that made the difference. However, last night my phone did NOT loose the BT connection. Thumbs up to you guys. The only minor downside: sometimes when I go out of BT reach and come back to my phone, the connection is not re-established (and xDrip+ is showing 'not connected'). I'm already happy it stays connected trough the night. For other (oneplus) users, I'll past the BT settings below. Thanks for your help and wishing you all a happy new year!

[rodrigowebjump]

Mine works yesterday after disable the trust auto connect option

Thanks

[Navid200]

@btdkomplex Would you please close this issue if your problem has been resolved? Otherwise, you can use the support channels to consult with users to ensure you are aware of any possible solutions or work-arounds. https://www.facebook.com/groups/xDripG5 https://gitter.im/jamorham/xDrip-plus Thanks

[Navid200]

Closing due to inactivity