This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Big bug in FW 3.40 with CIQ apps

So, I was planning/training in the last 14 weeks for a trail marathon race that took place yesterday. My Expedition was on FW 3.40 with two CIQ apps running: Runscribe Lite and RunPower. I also have 2 Runscribe pods that were connected as such:

- A -  through watch sensors: (1) left RS pod as FP and giving pace; (2) left RS pod as power meter to give power

- B - through Runscribe Lite CIQ app, both RS pods connected as usual.

I want to say that I have been using this setup before while training.

I start the race, minute 30, A2 stops sending power, I check sensors in watch to see that I have 'searching' - I had this issue before in previous runs, if it happens is always around 30-40min - other users experienced the same thing (if you check this forum https://community.runscribe.com/t/support-for-new-garmin-forerunners/2207/152)

Later on the race, don't remember exactly when, but after minute 30 and probably before 1 hour my Marq restarts (it happened while I was changing my screen - up or down) - I see logo, than loading maps ! After that it asks me if I want to resume activity so at least I did not loose everything, only the bit while restarting. I check my screens I see that Runscribe Lite has been replaced with Elapsed Time. So could be from RS Lite, but this is definitely the first in all my years on Garmin watches! I replace Elapsed Time with Runscribe Pus (similar with lite) and it works till the end.

So, you could of course understand why I am a 'little' concern here, I was not in the beta anymore and it was a race, I could have lost everything! Well, I wrote a longer message hoping for a solution for these two issues (sensors in searching mode and restarts).

Top Replies

  • , From my experience of reporting watch crashes to the team behind the beta threads, as long as you haven’t had another crash since, it would be invaluable to grab the err_log.bak and ram.txt files…

All Replies

  • , From my experience of reporting watch crashes to the team behind the beta threads, as long as you haven’t had another crash since, it would be invaluable to grab the err_log.bak and ram.txt files (and any other files that have a date and time that matches the crash) from the Garmin/Debug folder on your watch, compress them in to a zip file and email them to [email protected] with your issue description text posted above copied in to the email too (that email address comes from the 3.34 beta thread).  Those 2 files are usually only generated when a watch crashes and apparently contain a lot of data that helps the Garmin software folks figure out what caused it and generate a fix.

  • Many thanks for the idea, I wrote to them and added extra the FIT file and the CIQ_log file.