Google Pixel 3a, Dexcom G5 #1009
Comments
|
Not exactly sure what fixed it, but it's working now on my Pixel 3a. Things I did:
|
|
Having the exact same issue on my Pixel 3a XL ever since changing the sensor yesterday; no Bluetooth connection and seeing "No valid timestamp stored for transmitter". Still not working after changing the phone / BT name. |
|
I ran into the issue again after closing this issue, but fumbling for a bit was able to clear it up. Still not exactly sure what fixed it as my "fix" was more analogous to a monkey pounding on the keyboard, doing most of this with my BG hovering around 40-60 mg/dL . (Love xdrip, but its UI does require way too much cognitive load for me in that state.) Probably the most relevant things I did while flailing about:
Been working for about 2 days now without issue. Really not sure what's going on. EDIT: I also disabled collection in xdrip, re-installed the modified "official" G5 app, did 2 & 3 from above, got it working there, then uninstalled the "official" app, re-enabled G5/G6 in xdrip, (didn't work), then started flailing about as above. |
|
Glad it's working for you!
In an effort to troubleshoot I tried going back to the G6 receiver... It also couldn't find or pair with the transmitter.
So I'm assuming the transmitter is defective, just spoke to Dexcom support and they are sending a replacement.
…________________________________
From: Webifi <notifications@github.com>
Sent: Saturday, September 14, 2019 4:06:01 PM
To: NightscoutFoundation/xDrip <xDrip@noreply.github.com>
Cc: Isaac Roitman <isaac_roitman@hotmail.com>; Comment <comment@noreply.github.com>
Subject: Re: [NightscoutFoundation/xDrip] Google Pixel 3a, Dexcom G5 (#1009)
I ran into the issue again after closing this issue, but fumbling for a bit was able to clear it up. Still not exactly sure what fixed it as my "fix" was more analogous to a monkey pounding on the keyboard.
Things I did, in random order while flailing about:
1. Set scan for G5 constantly.
2. Removed any G5 pairings in the phone's Bluetooth settings.
3. Restarted phone. (both restart, and power of,f power on.)
4. Opened up the phone's bluetooth pairing screen and Xdrip in split screen mode. Keeping the phone awake, waited for the G5 to pop up on the phone's Bluetooth list (didn't pair it there), and hit "RESTART COLLECTOR" in Xdrip's "Classic Status Page", then switched to "G5/G6 Status" and waited for a successful connection. (Probably did 3 & 4 a half dozen times before it started to work again.)
Been working for about 2 days now without issue. Really not sure what's going on.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#1009?email_source=notifications&email_token=AMUPPYY2IDBEZHGWZKKWNSDQJU72TA5CNFSM4IVN6SYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6XDBGI#issuecomment-531509401>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMUPPYYBFENTBPAZ3EAJN4DQJU72TANCNFSM4IVN6SYA>.
|
|
Do you still having errors? I am also using a Pixel 3a, but did not upgrade to Android 10 yet. |
|
Working so far. Not sure if/when I'll run in to issues again, nor am I exactly sure what I did to fix it. |
|
I've also upgraded my Pixel 3a to Android 10. Missed the first reading but that was probably because the setup was still running afert the first reboot. Since then no issues, runs as fine as with Android 9. |
|
Looks good now! Was actually a defective Dexcom transmitter and not the Android 10 upgrade, just weird timing.
…________________________________
From: nsghub <notifications@github.com>
Sent: Saturday, September 28, 2019 10:53:00 AM
To: NightscoutFoundation/xDrip <xDrip@noreply.github.com>
Cc: Isaac Roitman <isaac_roitman@hotmail.com>; Comment <comment@noreply.github.com>
Subject: Re: [NightscoutFoundation/xDrip] Google Pixel 3a, Dexcom G5 (#1009)
I've also upgraded my Pixel 3a to Android 10. Missed the first reading but that was probably because the setup was still running afert the first reboot. Since then no issues, runs as fine as with Android 9.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#1009?email_source=notifications&email_token=AMUPPY6SOFL5G7BT2BARBJ3QL5VUZA5CNFSM4IVN6SYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD723KWY#issuecomment-536196443>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMUPPY76FOHOCVHBBCBGAHTQL5VUZANCNFSM4IVN6SYA>.
|
|
My transmitter was working perfectly until I upgraded to Android 10; Now the brainstate is caught in "scanning" forever and no values are received. My Dexcom receiver worked for an hour and then it stopped receiving data too. @jamorham Maybe XDrip+ in combination with Android 10 is killing the transmitters?! Edit: Using Dexcom G6. |
|
it looks like android 10 has some strange/new behaviours with BLE bonding. |
|
@gregorybel |
|
then it confirms it has something to do with Android 10. thanks for info. let's hope google provides a fix soon. |
|
@gregorybel https://developer.android.com/about/versions/10/privacy/changes#methods-fine-location |
|
I got it to work , it was being difficult untill I Adb shell pm grant com.eveningoutpost.dexdrip Android.permissions.WRITE_SECURE_SETTINGS I'm typing that off the top of my head so if it doesn't work make sure the package name is right Adb shell pm list packages | grep -i xdrip; |
|
@jamorham |
|
That is on Android 10 sorry I should have clarified |
|
I executed the command opened the app and then it asked if I wanted to whitelist it I hit ok and it worked and had all the other permissions in settings enabled already |
|
@Webifi solution worked for me. My Bluetooth name was "Pixel 3a" I changed it to "Pixel3a" (without the space) and immediately I could connect to the Dexcom G6 app |
|
On Android 10 you need to enable an additional permission/setting:
After I added this permission it started working on Android 10. // EDIT: And it stopped working again after a reboot. Thank you Google for Android 10. |
|
For what it's worth, I turned off OB1 Collector last night in the G5/G6 Debug Settings and it's been night and day better since then. I have a Pixel 3a running Android 10. |
|
I struggled for 24 hours with new transmitter on what had been working on my 3a with prior transmitter, and then appinfo suggestion (above, 10/18/19) from nshtg solved the issue. Thank you! |
|
I've tried enabling that permission, as well as the unbounding option. Granted this transmitter is way past its expiration date. I'll give it a day or so fiddling with the settings. If I can't get it to work I'll just use an old Android phone as a receiver until it dies, then maybe move to the Dexcom receiver until there's a permanent solution. I know these major updates are a pain, but thank you again @jamorham for all the hard work. I mentioned it in another thread, but if you are interested in purchasing a Pixel 3a (assuming thats the most affordable reference device for these updates) I'm sure many of us would love to help. You have single handedly saved me so much money over the past 3 years or so. |
|
I have the following set, though I'm not sure if they're all required for things to work:
The steps that seem to most reliably fix the issue for me are:
|
|
@Webifi With all of those steps and settings, you have had good result? Does it stick after a reboot or is it a temporary fix? |
|
Seems to have stuck so far. Been running on a new transmitter since Oct. 13th without issue. |
|
I'll share my settings as well. My coverage has been fantastic since I turned off OB1 and used these (few) settings with my G5 and Pixel 3a. After rebooting my device this morning for the newest security patch, I did need to
|
|
I've noticed that not using the native algorithm kills the battery on my G5 transmitters pretty quickly, so I recommend using it. If the native algorithm is disable from being too old, you can reset the transmitter's timer: |
Whatever voodoo magic this is, has made mine work properly for the past 2 hours. I have commented on a few other threads with these issues, so after a day or so I will copy your solution over. |
|
@Webifi - thanks for the battery tip. I had no idea! I just switched to trying out the settings you shared. I'll give it another go. |
|
@Webifi Was out of range for one reading, and then it went back to failing to read and scanning. Something you did definitely made it work better, but still must be something off. I'm going to keep messing with settiings and hopefully I'll get something to click. |
|
Post a screenshot of your G5/G6 Status page if you can. |
|
First picture is a screenshot 15 minutes or so after it lost connection. As of right now the phone has been in range and it is 47 minutes since last reading. I can fix by "forgetting device" in xdrip app, and it works great until next time it missed a reading.
|
|
Here was the screenshot of it before it lost connection. |
|
Battery is getting kinda low there. Could be the transmitter isn't waking up exactly at its predicted 5 min intervals. How long has that transmitter been active. Do you have "Less common settings" -> "Aggressive service restarts" enabled? Also "Less common settings" -> "Bluetooth Settings" -> "G5 Bluetooth Watchdog"? |
|
@Webifi Yes I have those settings. I let it continue to go and usually within an hour it did pick back up, and then filled in the missing data, without me having to forget the device. Definitely is an old transmitter, so that could be the issue. I am glad to see that it does eventually resolve itself, even if it takes a bit longer. Thanks for all your help! |
|
Lost connection this morning and it failed to regain signal. Thought I would do a test, as I have an old android phone here at work running Android 8 (LG G6). I reconnected my Dexcom to the old phone, force closed the xdrip app on my current phone, to see if I could deduce the problem. I purposefully took the phone a distance away to make it miss a reading, and after 15 minutes or so, I went to retrieve it, and it reconnected on the next available opportunity. Considering that my OnePlus 6T worked flawlessly on Android 9, and the fact that this transmitter works perfectly with the LG G6 device, there has to be something in my Android 10 update that is causing connection issues. Also, there aren't many phones with Android 10 on it (may just be Pixels and OnePlus phones). So it is possible that it is just OnePlus Android 10 that is the culprit, which is why it doesn't reproduce this on the Pixels. Who knows. This is the screenshot of the LG G6 status screen for comparison to my OnePlus 6T screenshot if that is helpful. |
|
Update: Tried something this afternoon when i experienced the inability for xdrip to automatically reconnect. I deleted the app, and downloaded the latest nightly (November 2nd). Going on 6 hours with multiple walk away disconnects and everything is working great so far. Not sure if it was the fact of just redownloading any xdrip app, or if specifically getting the newer nightlies made the difference, either way so far it is working great. |
|
Sorry, should have asked what version x-drip you're running. I've been running on the alpha update channel for awhile now. |
|
Thought I would jump in - got a new OnePlus 7T last night - received some initial readings then during the evening dropped and have not been able to connect. Was on my way to the store to get another phone and saw this thread. Really appreciate everyone taking the time to look. What I did was the following, as above: Unchecked the "Use the OB1 Collector" - I was immediately asked to provide a calibration. I also through Android - went into Apps & Notifications - xDrip - Advanced - Modify System Settings and enabled Allow modifying system settings. As stated above. Since doing this, I have been able to reboot, walk-away from my phone and haven't dropped. Will keep everyone posted but so far so good. Again appreciate the info above, it is greatly appreciated!! |
|
Made the mistake of updating to the most recent nightly of x-drip. Now, even after reverting to the previous version, X-Drip stops getting data from my G5, requiring me to jump through my aforementioned hoops to get it going again -- which will only last a couple hours or less. Can't seem to get my x-drip back in to the magic state it was in before. |
|
Webifi, I'm having same issue, since recent nightly update I can't maintain a decent connection to g5 on pixel 3 w Android 10. I downgraded Xdrip to last version that worked but no change .... |
|
Not sure if it's just a coincidence or if it will actually last, but since doing the following, xdrip has not lost connection with my G5:
|
|
Must have been a coincidence, since it finally broke again. Uninstalled x-drip, and re-installed x-drip (lost my history and settings), then re-configured. Seems to be working so far. |
|
@Webifi Would you please close this issue? These issues are supposed to be used for reporting bugs and feature requests. |
|
I'll close this issue, but documentation that require you create an account to read, as is often the case with facebook, or require you to sift through an endless thread of messages and/or create an account to be one of the many that re-ask the same questions over and over, as is the case with gitter, is a non-starter for me, and likely many others. |
|
That's a valid point. Needs to be addressed. We are aware. |
Anyone have any luck with xDrip on a Google Pixel 3a running android 10 connecting to Dexcom G5?
My logs show continuous "No valid timestamp stored for transmitter: 41U5BR", and Classic Status Page says "Bluetooth Device: None Set". Was working with a Moto G6 before.
The text was updated successfully, but these errors were encountered: