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

Swim2 Bug lists SW version 2.30

This is a collection for the bugs remained or introduced at 2.30 (edited after some clarification, last edit 03.06.2020)

- Weekly swim total is wrong after the update (I am not sure if it was ok ever...). Weekly total is correct after a new week begins.

- In open water, even if the units are set to metric, the distance, and distance alerts are displayed in yards.. Solution is to go to settings, units, select statute, then select meters again. 

- auto lock does not work

- Personal record saving do not support 33 and 1/3m pools. With 33 and 1/3m pools, 3 lengths are not considered as 100m, but something very close, but not EXACTLY 100m. Wth this bug the watch can not recognize the laps as exact lengths, causing not record saving.

- In history, when browsing intervals, first page correct (intervals 1-4), then next is intervals 5-8, but if you browse up to 1-4 and back to 5-8 it changes to intervals 4-7. You still can browse between 1-4 and 4-7. If you browse further down, suddenly you lose the first 4 intervals. But it depends of the actual number of intervals, and the interval history can go a bit mad. (very similar issue can be read for Forerunner 45 as well, see FR45 forum, bug reports after 3.10) - with new activities this seems to be corrected in 2.30

Unfortunately the history is still not perfect. My last two swims, recorded with 2.30 still have problems when seeing the history, and scrolling back and forth. Some laps still disappear. Interestingly while reproducing with drill log (the fastest way to generate many laps), the history seems to be correct. But with swim recording (or in the room shaking the watch to generate lengths and laps) it still has the problem.

- auto lap can be set for OW swim only for 0.5 km or miles, can not be changed to individual distances

- backlight control is faulty. "During activity" and "not during activity" are not separate options, they are connected somewhat. You either turn off backlight completely or turn it on completely, but can not separate the behavior depending on activity or watch mode. (option is available, but during and not during activity settings affect each other)

- Massive GPS drift with OW swims. Watch is useless for OW swim! - actually the watch gets OW distance/pace information from both the accelerometers and GPS. If GPS is lost, accelerometer data is used, but when GPS found, it simply adds up GPS distance, resulting overinflated swim distance.  - This is NOT a bug actually. When OW tracks are recorded well, they are extremely good. If symptoms are: in pace chart constant pace, then suddenly very fast pace spike, then the same constant pace, etc. , map track is uncomplete, just some straight lines, many times do not follow the real path, then disable all of the extra features, switch off bluetooth during swim, perform soft reset, use standard watch face, check the track. If track is good, slowly add back features what you need.

- Data screen customization is a complete mess. I could not find a logic in that, but recently I had to perform a factory reset, and add the data screens back to my liking. Nearly after each change the watch changed the data fields to something different. As an addition to that, this bug might be a major contributor for the occasional inability of OW swim tracking.

  • Unfortunately the history is still not perfect. My last two swims, recorded with 2.30 still have problems when seeing the history, and scrolling back and forth. Some laps still disappear. Interestingly while reproducing with drill log (the fastest way to generate many laps), the history seems to be correct. But with swim recording (or in the room shaking the watch to generate lengths and laps) it still has the problem.

  • User Profile > Height is now 5'11" instead of 180cm

    User Profile > Weight is now 152lbs instead of 69kg

  • What is the official way/channel to file bug reports? I have some “findings” (imo bugs) not mentioned in the list above.

  • The issue regarding the history/browsing the intervals mentioned by the TE is imo still not solved. I updated yesterday to 2.30 and was today in the pool. Activity recorded with 2.30 and displayed with 2.30. Test scenario:

    - browse to the pool swim widget

    - push a few times the start button, until the today's pool session / activity is loaded

    - press the down button, until you see the intervals 5-8

    - press the up button

    - instead of the intervals 1-4, the watch/widget displays the previous page (anaer. TE, Cal, HR)

    - if you press the down button, the widget shows only the intervals 5-8. The interval list contains only this 4 intervals, even if you have 20 intervals.

    Anyway, this is imo not really critical, because if you press the back button and then reload the activity and scroll beyond the page with the intervals 5-8, then you can also scroll correct back. The bug is only if you scroll up from the 2nd interval page (5-8).

    Regarding backlight: I turned all the backlight settings off (during activity, not during activity), because I don't like the automatic backlight. The backlight stays generally off with 2 exceptions. When I press up or down to show the heart rate widget or the stress widget (only while measuring!), the backlight goes on. It looks like measuring (the heart rate) automatically turns the backlight on, even if all backlight settings are off.

  • The official way is to report via Garmin support

    support.garmin.com/.../

  • I can also confirm that the activity browsing issue is still not solved with 2.30, following bleiente step-by-step. Also for me, it usually happens the first time I browse an activity, but not always.

  • My activity screens for run and cycle are stuck in miles even though my device settings are all for the metric killometer settings. Also my weather is showing in Farenheight as well.

  • Sometimes it helps to sync with Garmin Express on the PC/Mac. Set every possible unit option in Garmin Express on metric and sync with the watch (connected via USB cable). Maybe you need to switch back and forth and synchronize a few times.

    A few users could solve some issues with this workaround.

  • Massive GPS drift with OW swims. Honestly it seems that all other activities have some drift when started, but it settles down. But not for open water. As a result I get overinflated distance, about twice as much as normal. 

    - I swim only front crawl
    - I had my FR910XT on as a control device (I thought that it will be the first and only time I need to evaluate, but unfortunately not). FR910XT could cope the swim, showed proper distance and track line, and checking with google maps show that FR910XT measured the correct distance.
    - I found that there is a huge GPS drift if I do not move or stop for a rest (I kept the watch immediately over the surface). I think this is the main contributor for the overinflated numbers.
    - I swim slowly, according to the GPS track about at 2:30/100m pace, but as I stop, the pace (or GPS drift) immediately goes up high to 0:30/100m pace! This even does not fit to a pattern of proper ded reckoning, as the pace goes immediately from 2:30 pace to 0:20. It seems to settle down after a while though, giving an about 0:30 average pace for the rest.
    - I used GPS+GLONASS settings, according to some review it should be (or was) good earlier.
    The watch is on software vers. 2.30, GPS 2.90, sensor hub 3.11.
    I made two swims (the second one just a short control swim). With the first I had CPE=expired, but for the control swim CPE was current. Similar amount of drift is visible on both tracks, maybe updated CPE makes things a little bit better, but not significantly.
    I noticed that GPS drift is also present with FR910XT, but 1-2 meters only in several minutes, not like 1-2 meters in every second like with Swim2. I made some GPS drift test in the garden with different GPS settings (GPS only, GPS+GLONASS, GPS+GALILEO), but the results seem to be quite similar, with moderate to rapid GPS drift.
    actually the watch gets OW distance/pace information from both the accelerometers and GPS. If GPS is lost, accelerometer data is used, but when GPS found, it simply adds up GPS distance, resulting overinflated swim distance.  - this is a major bug!