Connection won't last

[JSSSVZ]

I just downloaded the newest APK on my moto edge and was able to successfully pair my X2 pump. But the app seems to cycle through connecting and loosing connection every few seconds. It won't stay connected long enough to even attempt a mobile bolus.

I've tried turning Bluetooth off and on, restarting the app, turning off mobile connections on the phone all multiple times.

Does this mean it just won't work for my phone and I should give up? Thank you for doing this, y'all are amazing.

[JSSSVZ]

The error I seem to be getting is "connection error now: writing characteristic"

[jwoglom]

Hi @JSSSVZ , can you go to Debug > Download debug logs and attach it while this is occurring? Thanks!

[JSSSVZ]

Debug logs

Sorry, if there is a better way to attach these I'm just not seeing it.

[jwoglom]

@JSSSVZ Unfortunately that didn't share any of the contents here -- just the text "Debug logs". If you click on the option, and select Open with and choose Google Docs that might be the best option to get them shareable.

[JSSSVZ]

Hopefully this works, I keep getting an error when I try to load the debug logs on Google docs.

[gregbender]

@JSSSVZ - I had same connect/disconnect loop issue.

Just ControlX2 by itself was fine, but enabling connection sharing with t:connect always started the disconnects. This is what ultimately worked for me:

1. Un-pair and re-pair pump fresh in t:connect, write down pairing code
2. Force stop t:connect
3. Fresh install of ControlX2 app (or delete prior storage)
4. During ControlX2 pump setup, use pairing code from 1. Be sure to enable connection sharing service during ControlX2 setup.

Awesome app, thanks @jwoglom

[jwoglom]

@gregbender thanks for sharing the process you've followed. Personally, right now I'm just swapping between whether I have ControlX2's service enabled or the t:connect app in use because like you mentioned the connection sharing is not in an especially stable state. Some of this is tandem's app's fault, in that it doesn't know how to handle a different app essentially sharing the active BT connection to the pump. But a good amount of this should be able to be resolved with better handling on the PumpX2/ControlX2 side to ensure we aren't fighting with the t:connect app whenever we get a response back from the pump to send the first message to it.

[JSSSVZ]

@JSSSVZ - I had same connect/disconnect loop issue.

Just ControlX2 by itself was fine, but enabling connection sharing with t:connect always started the disconnects. This is what ultimately worked for me:

1. Un-pair and re-pair pump fresh in t:connect, write down pairing code
2. Force stop t:connect
3. Fresh install of ControlX2 app (or delete prior storage)
4. During ControlX2 pump setup, use pairing code from 1. Be sure to enable connection sharing service during ControlX2 setup.

Awesome app, thanks @jwoglom

Thank you, this seems to be helping with the connection issues. It still won't allow me to remote bolus, but is at least displaying the pump information which is progress.

I noticed it says that I have control IQ on (which I don't, I'm still using basal IQ). Does the app only work with pumps that have been upgraded to control IQ?

[jwoglom]

I noticed it says that I have control IQ on (which I don't, I'm still using basal IQ). Does the app only work with pumps that have been upgraded to control IQ?

@JSSSVZ I think this is a UI bug. I don't have a basal IQ pump to test with at the moment, but should have enough information from the pump to fix this. The home screen UX is definitely a work in progress and not final -- eventually will hope to display a CGM/basal graph there and a design which isn't just lines of descriptive text.