Under Review
11 months ago

VenuSQ Disconnects from Phone after multiple makeWebRequest calls

I have a watch app which has been working very well for several years (https://github.com/OpenSeizureDetector/Garmin_SD/tree/master/WatchApp/source).

It collects 5 seconds worth of accelerometer data and a heart rate measurement, then transfers it to an Android phone app that is running a local web server using makeWebRequest() (https://github.com/OpenSeizureDetector/Garmin_SD/blob/master/WatchApp/source/GarminSDComms.mc#L49)

Recently users with VenuSQ devices have reported that after a watch firmware update they have an issue that after several hours of running, the watch disconnects from the phone (Garmin Connect shows the watch as disconnected).   The only way we have found to reconnect the watch is  to re-boot it.   I have a VenuSQ device and am seeing the same issue using Garmin Connect V4.71 and the VenuSQ firmware V4.90.

I suspect that this may be to do with multiple makeWebRequest calls happening simultaneously if for example  the data transfer is slow or the web server responds slowly, so I have tried making a different version of my app where I can tell it to transfer less data.   It seems to run for longer, but the fault still happened after about 10 hours when I tested it.

The same app code is working ok on a ForeRunner 245 - I have only had reports from users about the VenuSQ devices.   

My bug tracker issue for the problem is here:  https://github.com/OpenSeizureDetector/Garmin_SD/blob/master/WatchApp/source/GarminSDComms.mc#L49

So I think a recent watch firmware for the VenuSQ must have changed something.    I do not know how to obtain an old version of the watch firmware and install it so I can test to see if this is true or not - but if someone can give me some guidance I will do it.

Please let me know if you need any other information or would like me to try a different watch firmware.

GrahamJones
  • 5 months ago

    We found a copy of Firmware V410 on your web site (https://www8.garmin.com/support/download_details.jsp?id=16030).  I have tried that and it resolves this issue, so you should be able to identify the issue from the differences in the makeWebRequest implementation between these two versions?

    I can not find an old copy of a VenuSQ2 firmware - please will you point us to one from over 6 months ago and we will try that on a VenuSQ2 which is having a similar problem.

  • 5 months ago

    This bug is still present after the recent update to Firmware Version 5, so I have given up recommending people buy Garmin devices to use with my application, and am telling them ot to accept any software updates from Garmin in case it breaks their device.   

    I also have a report of a recent update to the VenuSQ2 introducing the same issue (after a user purchased a VenuSQ2 to avoid the problem he was having with his VenuSQ...)

    We have done some more testing and  if we comment out all of the MakeWebRequest() calls from our app, it runs without seeing this issue. 

    I have tried a different version of my App which uses fewer makeWebRequest() calls and we seem to get a longer run before the watch disconnects. 

    So I am confident that it is MakeWebRequest that is somehow making the watch disconnect from the phone (it shows as Not Connected in Garmin Connect, until we reboot the watch) - is there a memory leak in your makeWebRequest code or something like that which is crashing the bluetooth system?

    Is there any intention on the Garmin side to investigate and fix this?    Can you suggest a work-around that we could implement?

  • 9 months ago

    I tried to avoid the update but my son accidentally accepted it for me.
    5.0 works about as bad as 4.9 did for me, so I am a bit less unlucky than

    Make no misstake though, my Venu SQ is as broken with both 4.9 as it is with 5.0. I wish I could downgrade several versions to get back to a, for me, stable firmware.

  • 9 months ago

    Garmin Connect just invited me to update the VenuSQ watch firmware.  I did this and it is now showing the SW Version as 5.00.

    It now only runs for a few minutes 3-5 before the whole watch re-boots.   There is nothing untoward in my app log files, and there is no CIQ_LOG.TXT file to give a clue about what the issue is.

    Do you have any idea what might be causing this or how we should diagnose it, because this latest firmware has changed the VenuSQ from being unreliable, to not working at all!

    Thanks,


    Graham.

  • 11 months ago

    I can confirm that I too started experiencing this problem after the connect app updated the firmware on my Venu sq to firmware v4.90