I thought it might be nice, or usefull, to have a single topic with confirmed bugs and issues with the forerunner 955 watches. Having the solar myself and noticing at least 2 serious bugs, this is good to know for users and Garmin themselves. Perhaps it can be stickied?
People can comment or mention bugs in the comments, or message me directly, and if confirmed by others (or me) I will update the main post. Preferably with as much info as possible.
Maps and navigation
- Navigate -> Use map: Impossible to select target location (FW 10.10)
Trying to use the map to navigate to a target point doesn't work. Most of the times the crossharis needed to select a location aren't visible and long-pressing start (usually needed to select the location) doesn't do anything. There are also no other ways to select a location on the map. Sometimes they DO appear and selecting the location is possible, however actually starting the navigation reboots the watch.
This seems to happen when the location you select results in multiple options (in my case for example ', , ') if I somehow am able to select a location with no alternative options it does not seem to crash. Crosshairs still appear only the first (few?) times after a reboot.
- Starting a course directly from the "Navigation" app redirects you to the 'Navigation selection screen' (which is then a bit hard to get out of)
When going to the Navigation activity and select a course to follow it seems to load the course but then redirects you to the same selection screen where you get the option to again select a course, point of interest, etc. Pressing back once stays in the navigation screen, you need to press back a few times quickly to exit. When then starting another activity the course selected above IS loaded. Other ways such as selecting a saved location DO work and selecting a course for navigation directly from another activity also works.
- Some custom maps might crash watch?
Hard to verify
- Incorrect/garbled rendering of custom maps
3rd party OSM based maps seem to render incorrectly, while working on the fenix 7 and FR945 watches.
- Autozoom - Map toggles between extremely zoomed out view and normal zoom level (when showing turns/changing view?) during navigation
While using navigation and with map autozoom set to enabled, the map screen switches between a way zoomed out state making it impossible to see context regarding streets, etc and normal view when you switch screens or when an instruction is shown. Again switching screens toggles it back, this actually could be reproduced constently (both during cycling as walking activities). When autozoom is disabled and setting a specific zoom level manually this doesn't happen.
- Map Zoom level reverts back to default (FW 10.10)
When zooming in or out of the map the zoom level is not retained, it however reverts back to the default zoom level when going back to the map/different screen. Scrolling/pannign around IS saved/stored.
Apparently this is by design, and can be fixed by turning of auto-zoom for maps:
- Swipe from left to right on the map (in order to pan) triggers the menu to open
When making the swip motion from left to right on the map to pan it will open the menu (and exiting can reset zoom on map if autozoom is set). A workaround is to either swipe slowly, or don't remove your finger from the screen right away but let it rest for just a bit longer before releasing the touch screen (might take some getting used to). Not limited to maps, also in other screens.
Fixed in 11.12
- Touch with a map screen in an activity only works when "General Touch" is enabled
When touch is enabled for an activity but not for general use, touch can not be used on the map-datafield for that specific activity. The map touch funcitonality ONLY works when general touch use is enabled, no matter the specific activity settings
- Widgets are not touch interactive
Unlike with other touch devices, trying to use touch to scroll through graphs on widgets does not work.
- Changes to lists are not saved
When for example renaming a saved location, the changed name is not saved and the original name is shown. (Also going into details after changing the name messes up the name string)
- Battery drain (FW 10.10) after an activity
Battery usage is higher then expected, currently overnight it used 0.4 to 0.45% per hour (about twice as much as my 3 year old Forerunner 945 with the same watchface and settings). PulseOX is turned off, no notifactions from smartphone etc.
Might be (partially) connected to the stryd sensor, I removed it from the watch (use it in standalone only) and battery drained 6% in the last 24 hrs
It seems battery drain is high AFTER an activity, perhaps sensors still connected/searching in the background or GPS not properly disabled? After a reboot the watch uses 0.2-0.3%/hr, after an activity this is ~2%/hr. Rebooting again fixes it.
This actually seems to be causes by the 'connectiq fields keep running in the background' issue listed below
- Garmin power + stryd power gives doubled values (FW10.10)
Garmin and stryd power don't play well together, both are shown in connect but the garmin values are uploaded to stryd (and them differing a lot messes things up). Might be a Stryd issue though, but still a bug occurring on the watch.
- Can't edit (sport specific) heartrate (or power zones?) on watch or connect
When adjusting the sports specific (for example runnng or cycling) in the connect mobile app or on the watch the values aren't saved. Instead the general zone values are used. Adjusting the general zones DOES work (and these seem to be used for the specific sports, so can be used as a workaround)
- Automatic max heartrate detection behaves strange
When auto max HR detection is enabled it detects a lower max heartrate then the one actually measured. This is also done based on very low intensity workouts, resulting in nonsense max heart rates being detected and the max hr being updated to an incorrect value.
- Buffer overflow something in steps view of morning report
Values that indicate some overflow issue are displaye in the steps page of the morning report for some users.
- ConnectIQ datafields keep running in background after finishing activity
Even after finishing/saving/discarding an activity a connectiq field keeps running in the background. Only starting a new activity without these fields or a restart fixes this. This causes the batteyr drain noticed with connect iq fields and external sensors (as they keep on trying to set up a connection) but also other fields possibly.
Tested and validated with a field vibrating every 10 seconds, even after the activity and while in the watchface the watch kept vibrating every 10 seconds until a new activity was started.
- Adding 2 connectiq fields often results in the 2nd fields crashing, showing the IQ! message (FW 10.10)
When one of the 2 fields is more intensive (happens all the time with an ANT enabled field, but also many others) adding the 2nd field causes it to crash, showing the IQ! message and the field being removed. Adding 2 very simple fields seems possible but more often then not the issue occurs. Also confirmed on the 945LTE (but working fine on the 945). Does not seem to be a memory issues, having made the Auxiliary Heart Rate v2 datafield myself memory usage is VERY low (as confirmed in the emulator) while the 955 has plenty of memory.
- Race Calendar widget causes crash when french (or specific other non-english) language is used
When french is selected as the language and scrolling through the widgets the race calendar (calendrier des courses) causes the watch to restart. Changing language to english fixes this.
- Missing widgets (FW 10.10)
Maybe not a bug, but still an issue or not following the manual. Health Stats widget is missing, as is Device Usage. Very useful widgets and would be a shame if not available.
This might be by design:
"Garmin changed how the Widgets work two years ago.
The widgets you see now are mini versions of watch apps (the apps you can start via the start button) running in the background. That means higher reliability, higher security and easier programming esp for third party programmers, but also that widgets cannot get informations from other apps.
The latter unfortunately was the end of such summary widgets like My Day."
- Weather does not seem to work properly in combination with ios 16.1 beta
Not really a garmin/955 bug, but still noteworthy. Weather (widget) does not show any info when paired with ios 16.1 beta phone, older versions (and android) seem to work fine.
Fixed with the most recent version of garmin connect
- Open-water swim distance recorded is way off
Despite the track looking good and distance apparently being recorded properly in the .fit//gpx file the reported distance by garmin is way off (and much lower)
- Elevation datafields not available for Ultra Run activity, available datafields actually seem inconsistent between activities in general
No elevation fields for ultra activities:
No running dynamics in track run and not clickable in trail runs:
No running dynamics in triathlon:
Where for an ultra this can be very important information, the elevation fields are not available in that activity (and quite a number of other fields aren't either?!)