Dexcom G6 and Xdrip

[Curly815]

hey everyone! So Dex is my collector (because my doctors wants to be able to see clarity) and Xdrip is set as a share follower. It works well but then at times the signal will miss and be out for like 20 min or longer at times (like at this very moment signal has been missed for 21min) and i have noticed that signal misses when i lock my phone. I have checked all the settings and permissions on my phone to make sure Xdrip isnt killed when closing app and pretty sure all the settings on Xdrip are correct. I have notice a slight improvement if i leave the app open and not kill it. I also notice that if i got to the status tab and restart collector, 9 out of 10 times it refreshes with updated data. Not sire if this has been addressed and this is my first post so if this is repetitive, my bad! Any advice or suggestions would be great. Thanks and i love the Xdrip app! has been a total life saver!

Here is a screen shot of the log. Thanks!!!

[Navid200]

Please have a look at this issue:
#1849

Is it the same issue?

[Curly815]

so then the best setup would be to have xdrip with the share follower setting right?

[Navid200]

If you Dexcom app or receiver is your collector, and you still want to use xDrip, yes, you need to set it up as a follower using Dex share servers.

[Curly815]

Exactly, which bring me to the issue of the random missed signal errors and having to restart collector multiple times to get it to go and if anyone on the team has identified a fix besides that one post you directed me too.

[Navid200]

I think we already went over this.
I stated already that there is a proposal, which has not been approved yet.

[Curly815]

i think we did also. sorry about that and thanks

[Navid200]

I thought the problem was that the readings would be delayed. Not that it would stop until you restart collector.
Does it stop?

[Curly815]

I think you are completely misunderstanding me. On xdrip, I get the error signal missed. All the dexcom stuff works fine. It's when xdrip tries to collect the data and it doesn't and it causes a signal miss. That's why I shared a screenshot of the event log.