Newest Android update 8.0

[jo1st]

Let me first say that I currently use a Samsung S7 Edge which recently a few days back received the newest Android update 8.0 and the new Samsung Experience 9.0. I've been using this device with xdrip and a blucon with the Libre sensor for a very long time now and beside a few glitches you guys might remember I never really had such a big issue.

At the time the phone was updated I was already wearing a sensor on my arm and it was already connected to xdrip and the transmitter so everything continued just fine. Now what happened yesterday when I had to replace the sensor and of course going through the usual way to replace it by stopping and restarting it, what's happening is the actual phone is not receiving any initial data, is just stuck there doesn't move doesn't receive anything so he never reaches the calibration, there no data received.

So I clear the app cache and the app data and tried a little bit of everything. I changed battery in the blucon and for a minute I thought that maybe the blucon was a fault and maybe was damaged but eventually it will connect to just fine through Bluetooth but it will never show connected into the xdrip.

The Libre sensor is fine I scanned it with the reader just okay, no problem with that.

So I decided to install xdrip on my other phone a Samsung Note 4 with Android version 6.0.1. I used the same version xdrip installed on my Samsung S7, the latest stable which was updated a few days back.

That's when I started suspecting the problem was some kind of bug or I'm not sure what. Because data collection was completely successful and very fast. Connection to the phone was successful and now I'm actually currently using that phone to read my levels. Of course that's not the best option for me because my other phone is a phone that I don't use at all, is just there at home connected on the Wi-Fi network to use Wi-Fi calling to the States because I'm located in Japan so I need to try to solve the situation with my main phone which always worked for a year almost until the most recent Android/xdrip update.

please guys try to help me out I would really appreciate it

[jo1st]

I just wanted to let everybody know that I was able to find the solution. What I did I reset the Bluetooth so I went into the settings apps show system apps and I clear the cache and the data of the Bluetooth then I reinstalled xdrip and I was able to successfully get it to collect the data and start successfully.

[jo1st]

I just sang the victory too early. Unfortunately that continues this connecting connecting disconnecting a mostly disconnected all the time there is definitely an issue with Android 8.0 Bluetooth and eventually xdrip can anybody help me find a solution?

[Son1k02]

Updated 20 mins ago, no connection since. BluCon keeps showing up as limitter in system status. I have tried rolling it back, but this didn't solve the problem =(

[jo1st]

What do you mean you updated 20 minutes ago? do you mean that you updated your Android system or did you updated the app? You roll back what?

Can anyone comment on this issue because this is a big problem? I can't use my other phone, the note 4 and carry 2 phones just for blucon and xdrip. I for example ride my motorcycle all the time and I use Google Map on my Galaxy S7 and I usually have the xdrip levels reading through Bluetooth to my headphones while riding but now I cannot do that anymore.

[PMFabre]

Hello all - My name is Pierre and I am in the process of setting up a APS system for my wife since begin June. I was right in the middle of doing this in the past weeks when I was hit by these Bluecon/Android issues I do not think that it has much to do with xDrip. Blucon/BT/XDrip was running fine on Samsung Galaxy S4 mini (serranoltexx) (my wife's phone) running stock android 4.X. willing to use AAPS (requires android v5 or above), I flashed the latest LineageOS 14.1 on the S4mini (which I understand also replaced the stock Modem firmware to a recent one) - blucon/BT started to be erratic from this time on. I switched to Samsung Galaxy A5 2017 (my business phone, can't root/flash) running stock android 7 => everything was fine, very stable connection and perfect xDrip. I bought a Samsung Galaxy A3 2017 shipped with stock android 7 - unfortunately at 1 boot, the system upgraded to Oreo => impossible to connect. Under Oreo, blucon is recognized by OS, blucon PIN can be entered and sometimes (I guess it has to do with when the 1st value is TX by the blucon), the 1st reading is done. In the meantime to get the 2nd/3rd values, the blucon shuts down and somehow pairing/connection to Oreo gets lost. On various forums (xda, phonandroid...) many people seem to have similar issues with all sorts of BT devices (car entertainment, headsets...) since mid 2017 (about the time when some security issues were found between BT and android, followed by Modem/OS updates) I subsequently blocked auto-updates on the A5 through developer mode. I can try to reproduce issues and send logs if this can be helpful to more technical savvy users/developers - please let me know. This weekend I will try to flash the S4mini back to a 6.X version of the OS and let you know.

[PMFabre]

Hi again I flashed the S4mini with a CM13 version of 12/2016 and the bluetooth connections seems to be working OK with Xdrip+. I really think it has to do with the Oreo.

[jo1st]

Thank you. is the CM13 version of? xdrip? where can I get it?

[jo1st]

I do agree with you that this issue appeared because of the new oreo update but I have a lot of Bluetooth devices which are working just fine like headphones, my Samsung watch and so on.

Also as I said on my initial post once the update happened I had already One sensor on my arm and everything kept working just fine, the sensor was already paired the phone prior to the update. Once the sensor died and I had to replace it the pairing process went completely wrong and even when I was successful clearing data and cache of the Bluetooth app still connection never went good and kept disconnecting. I do believe there is something with xdrip as well with this new update of the Android system and I would appreciate if any of the programmers/authors to maybe step in and give us their input. thanks guys

[PMFabre]

Hi all,

Take a look at this link: https://productforums.google.com/forum/#!topic/nexus/QxcbWBsnvWc My understanding is that, in fact, these BT issues have to do with a combination of 2 a) the BT/BT-LE module that is built in your device; HM10 (and clones therof) and the Texas Instruments chip that powers it CC2540 and CC2541 seem to be very popular (it's cheap); it require a firmware to functions. Some FW are reported to work with Oreo, others not. but since, unless you have built (soldered) your own DIY device, you're stuck with what you were shipped (eg Bluecon or MiaoMiao) b) the Android OS version you are running. Many problems have been reported with H10/H11 with some version 7.0, 7.1 and most 8.0 versions. The problems are we do not control the stack! Alternative to HM10 is a Nordic Semiconductor one that is said to be OK with Oreo

I think we (with Bluecon/MiaoMiao) have to "wait" again util the android OS developer find a way out in the next OS versions.

CM stands for Cyanogen Mod - it is a alternative, non official version of the Android OS (up to version 6) that you can flash onto your android device. You need to findout first if a version of CM was compiled for your android device. Another possibility is to use the successor of CM which is LineageOS. My guess is that the oldest stabe OS version you can use is the best!

[jstevensog]

I'm currently using the same bridge I first made with a HM-10, and haven't updated the firmware in two years, and connecting with a Pixel 2 running Oreo 8.1.0. While on occasion the BT on the phone plays up, it usually recovers in an hour and since xBridge2.47e which cleanly disconnects the HM-1X before going to sleep, this is rare. The beta xBridge2.48b has had no issues in over a week, likely due to the packet cache hiding them. So, maybe there is more to the story than the article suggests.

xBridge2.47e/f also supports HM-16/17 modules which do not allow updating of firmware and are based on an entirely different chipset. Not sure off the top of my head which set it is. But this also works very reliably, but on occasion still has issues with the Android BLE stack.

The Android BLE issues have been around since 6, and are still yet to be fixed. But, I believe reported issues based on the model of BLE module may be overstated, or due to incorrect disconnect. Something I missed for a long time until @keencave pointed it out to me. Cheers

On Mon, Jun 25, 2018 at 5:13 PM, PMFabre notifications@github.com wrote:

Hi all,

Take a look at this link: https://productforums.google. com/forum/#!topic/nexus/QxcbWBsnvWc http://url My understanding is that, in fact, these BT issues have to do with a combination of 2 a) the BT/BT-LE module that is built in your device; HM10 (and clones therof) and the Texas Instruments chip that powers it CC2540 and CC2541 seem to be very popular (it's cheap); it require a firmware to functions. Some FW are reported to work with Oreo, others not. but since, unless you have built (soldered) your own DIY device, you're stuck with what you were shipped (eg Bluecon or MiaoMiao) b) the Android OS version you are running. Many problems have been reported with H10/H11 with some version 7.0, 7.1 and most 8.0 versions. The problems are we do not control the stack! Alternative to HM10 is a Nordic Semiconductor one that is said to be OK with Oreo

I think we (with Bluecon/MiaoMiao) have to "wait" again util the android OS developer find a way out in the next OS versions.

CM stands for Cyanogen Mod - it is a alternative, non official version of the Android OS (up to version 6) that you can flash onto your android device. You need to findout first if a version of CM was compiled for your android device. Another possibility is to use the successor of CM which is LineageOS. My guess is that the oldest stabe OS version you can use is the best!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/NightscoutFoundation/xDrip/issues/486#issuecomment-399854579, or mute the thread https://github.com/notifications/unsubscribe-auth/AIQs8-EmnwRm0bNzK2bwfLcq_so0FBTJks5uAI1_gaJpZM4UzEQg .

-- John Stevens "You are how you live, not what you have."

[jo1st]

I just wanted to let you know that I reverted to the previous stable version of xdrip and it's been working decently enough with just some random disconnects on my Samsung S7 edge with the Oreo 8.0.

On everything it was discussed above on the last reply it's a little bit too technical for me in this particular area to really make anything out of it just a little bit but I thank everybody for participating in this discussion and if anybody has any suggestion please share with us

[luckyboypl]

Guys, any solutions found? I use dexcom G5, in system status i got "phone got data" but after changing new sensor i cant collect initial readings for first calibrations, still no data recieved yet :( I was trying some solutions from facebook groups but nothing works i have samsung S7 if that matter

[jo1st]

I have an S7 like you and I reverted to the previous version of Xdrip and of course before doing that I completely uninstalled and then I also cleared cache and the data from the Bluetooth apps. try and let me know. Of course I do like the latest version of xdrip lots of improvements but unfortunately with Oreo it doesn't work

[luckyboypl]

can you tell me what xdrip version currently do you have? i have 2018.05.30

[luckyboypl]

ok no idea, i did everyting i could and dont work :/

[jo1st]

2018.01.22

[jamorham]

Guys I made some changes specifically for pairing issues on Android 8.0 in the last few days, try the latest nightly and use the OB1 collector. https://github.com/NightscoutFoundation/xDrip/wiki/How-to-get-the-Nightlies-on-Automatic-Update

[jo1st]

what's the OB1? I think I would rather wait when this particular version becomes a stable one for now I am sticking to the version prior to the last.

[luckyboypl]

after upgrade to latest nightly nothing changed, phone is conected to transmiter and got data but cant get glucose readings :/

[chip83]

jamorham I have try the last nightly but I have the same issue. My smarthphone is a S7 edge with Oreo 8.0 with miaomiao and freestyle libre. When I lost the connection (out of range or other) the only way to reconnect the miaomiao is try the bluetooh paring in android bluetooh setting. Every time I lost the connection I need to do the procedure again and again...

[hjortling]

I run Samsung S8 and i have updated to the latest xDrip build. I cleared the app and Bluetooth cache. App found and connected to Miaomiao directly. Now it has been running for 8 hours flawlessly, so it looks good, but i have with previous versions got a few days before connetion errors occur, so keeping my fingers crossed Will also do a sensor change tonight. Will get back with results.

[jo1st]

First let me say that The 2 devices are completely different, also the Bluetooth Version used I believe that the blucon uses an out dated version and miaomiao carries at the 4.0 which is more compatible with Oreo.

Regarding the blucon, and users using s7 edge with Oreo. I cleared data and cache of all Bluetooth system apps and reinstalled the xdrip version d8e7097-2018.01.22 and it's working just fine with just some random disconnect as usual,

I decided to purchase Miaomiao tho, seems a better device then blucon.

[rafaelmathieu]

It looks like that the latest nightly release (73cfa6d) has fixed the issue for me. (using the G5). I have not lost connection since that update 2 days ago.

[jamorham]

Marking as resolved