jstevensog
commented
8 years ago Hi Timm, The 25 second reconnection time came about from me. I found that the previous >60 seconds did not always reliably allow BLE reconnection to occur. Google's own recommendation is to kill off the GATT on disconnect, then re-establish it. I am not sure when this made it into the DexCollectionService code, but previously we had left the GATT open the whole time. The same issue of the GATT randomly deciding not to pass characteristic changes to the collection service, requiring a BT off/on cycle, or a Collection service restart, still occurred back then. Personally, I hope what you are trying works out. I would love a GATT that reliably works indefinitely.
I do find that this issue occurs mostly when WiFi is in use. I spent 2 weeks in South America last year, mostly disconnected from WiFi, and didn't have to cycle BT once. I also don't generally have the issue when I am travelling to/from work, or when I don't bother to connect to the guest WiFi in the office. Mostly around home and if I forget to turn WiFi off is when the issue arises for me. Cheers
On Fri, Jun 24, 2016 at 7:09 AM, Timm Korte notifications@github.com wrote:
I'm using an Android 6 phone and an xBridgeWixel where the BLE is turned off between data samplings. This leads to failures where I have to completely disable and re-enable BT on my phone in order to receive any further sensor-values from the wixel. Looking at the code in DexCollectionService and comparing it to the DexShareCollectionService, one can see, that the classic DexCollectionService will close the GATT every time the connection to the GATT server is lost. Comparing that to the DexShare service where it does not close the GATT, I changed the code for this disconnect event to mirror the one from DexShare. Also I changed the retry_in calculation to match the one from DexShare to not set the Alarm to just 25 seconds (since the wixel will be sleeping for more than 4 minutes) - but calculate a value like it is done in the DexShare service. Currently running the code on my phone and will report if this helps to solve the issue here.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/StephenBlackWasAlreadyTaken/xDrip-Experimental/issues/354, or mute the thread https://github.com/notifications/unsubscribe/AIQs8x4HG2aILSFp5KKoHXRQFUWxQg-Dks5qOvYegaJpZM4I9Pfg .
John Stevens "You are how you live, not what you have."
savek-cc
ericandloriapps
I'm using an Android 6 phone and an xBridgeWixel where the BLE is turned off between data samplings. This leads to failures where I have to completely disable and re-enable BT on my phone in order to receive any further sensor-values from the wixel. Looking at the code in DexCollectionService and comparing it to the DexShareCollectionService, one can see, that the classic DexCollectionService will close the GATT every time the connection to the GATT server is lost. Comparing that to the DexShare service where it does not close the GATT, I changed the code for this disconnect event to mirror the one from DexShare. Also I changed the retry_in calculation to match the one from DexShare to not set the Alarm to just 25 seconds (since the wixel will be sleeping for more than 4 minutes) - but calculate a value like it is done in the DexShare service. Currently running the code on my phone and will report if this helps to solve the issue here.