[BUG REPORT]
Forerunner 965 software version 21.20
- After recent "Moon Phase" APP introduced, I found in last moon cycle and in this moon cycle, "Moon Phase" widget prints incorrect "upcoming moon-rise/-set time" info after the 1st quarter in a moon cycle, in cases when the moon sets in later half of the night (ie next morning before dawn). One week or so later, the "upcoming moon-rise/-set time" info is correct in later phase of a moon cycle. For example, tested in location in Taiwan, moon set at 00:46 and rise at 12:17 of Jan 8, 2025, and moon set at 01:50 and rise at 12:58 of Jan 9, 2025 (noticed that moon sets earlier than rises in that day). Moon Phase widget prints:
- (at 21:48 on Jan 8) "moonrise in 4H 3M". That info is incorrect. The correct info should be "moonset in 4H 3M".
- (at 00:01 on Jan 9) "moonrise in 12H 57M". That info content is correct, but the upcoming moonset is closer to happen than is moonrise. It should print "moonset in 1H 49M".
- "Body Battery" APP has "Last 12 Hours" page chart looks incorrect: the upper part curves of data points and the bottom color bars have mismatched time offset error if the watch have been removed from the wrist for a while on the same day. The chart looked correct on the next "Last 4 Hours" page.
- It is very easy to find the chart mismatched error with Body Battery significant events during a day. For example, after a long good night sleep, and wake up to go out for morning jogging for a couple of dozen minutes, and then cool off and remove the watch from wrist for another couple of dozen minutes. It is easy to see "Last 12 Hours" page chart to have the diagram of "body battery" and "stress" data points too leftward errors mismatched than the bottom horizontal color bars (blue for sleep and green for run).
- To "pan char", moving the cursor that shows the time of the events, and "factor", "body battery" and "stress" data point of the time. The numbers of the "body battery" and "stress" data points are supposedly NOT the numbers at the cursor time.
- Sometimes a too long time "nap" will be detected as a "sleep" (longer than about 2 and more hours). When multiple "sleep"s are detected in a day, some sleep related scores will have unreasonable values (sleep score, sleep history, HRV status, etc of the day).
- suggesting that a "nap" is NOT qualified as a "sleep" in a day, if there were already a "better" sleep existed in the sleep history of the same day. (if a later "nap" is detected as a "sleep", an earlier "worse sleep" of the day can be down graded as a "nap")
- In recent software version updates, in some cases the scale of a map is shown as a long arc on top. It is not easy for users to roughly estimate the distances between any 2 points on the map. Zooming in and out the different scales of the map, the numbers shown at the long arc as ..., 345 m, 580 m, 925 m, 1 km, 2 km, etc.
- 345 m, 580 m, 925 m are not very easy for normal humans to use as a multiple or partition of a unit to measure distances in mind. A traditional short line of "200 m", "300 m", "600 m" is more appropriate for this purpose.
- "925 m", "1 km" are supposedly 2 very close lengths in numbers, but the map in the 2 scales look much different in sizes. Scales of "1 km", "2 km" are supposedly doubled in numbers but the 2 scales of the map look not that different as doubled in sizes. I'd guess "1 km" and "2 km" are rounded or truncated from "1.x km". For the purpose of expressing the distance across the total watch face, suggesting the numbers at the long arc should have at least 2 (or even more) effective digits. (For example if arc >= 1 km and arc < 10 km then show 1 more digit)
