WFS - Pixel Watch - [SC] tag issue

[amoledwatchfaces]

Looks like [SC] tag in our watch faces doesn’t work good on Pixel Watch.

[SC] tag works fine for steps below 1000 (0 - 999)

When steps count is higher (> 1000), Pixel watch reports value divided by 1000
2500 steps = 2.5
Looks like [SC] tag is not able to recognize this value and shows 25 steps.

Maybe [SC] tag is able to read only numerical characters? (0123456789)
2.5 = 25

[r.liechty_SDR]

@amoledwatchfaces

Does it work correctly without the comma, separator ?

Ron
Samsung Developer Relations

[amoledwatchfaces]

Hi Ron, I’m not sure what do you mean by that.

I’m just reporting that on Pixel Watch, [SC] tag doesn’t show steps count greater than 999 properly. Looks like the watch face is pulling 2,3 K steps instead of 2259 (maybe pixel watch default reporting is set to thousands in decimal). WFS [SC] tag somehow does not know how to interpret 2,3 (2.3) and shows it without comma (dot)

[Matteo_Dini]

I confirm this “bug”. Another user who bought the Google Pixel Watch sees the numbers rounded with [SC] tag.

Example:

4000 steps are displayed in 4K on Pixel Watch.

[amoledwatchfaces]

Yes, [SC] tag results
4000 steps (4 K) = 4
4100 steps (4.1 K) = 41
500 steps = 500 [OK]

[Matteo_Dini]

Another example received by a user (picture a bit blurry)

[amoledwatchfaces]

[SC] tag is completely unusable on Pixel Watch. Also, every stat which is calculated based on [SC], for example km, miles, calories.

[Matteo_Dini]

We need to understand if this issue can be fixed with the final version of WFS or with a Pixel Watch update.

@sinjae
@catherina00
@r.liechty_SDR

any toughts?

Thank you.

[Matteo_Dini]

Looks like it’s a bug with the HR tag too.

If automatic heart rate detection is set, for example every 10 minutes, automatic heart rate detection stops working after some time.

I don’t know if it is somehow related to WFS but I have received reports from some users also for this issue.

[sinjae]

Hi all,
it is difficult to answer it because we don’t yet have the opportunity to use the Pixel watch in our hands.
We will figure out what we can do on the Pixel Watch after hands-on.

Thanks for the report!

[Matteo_Dini]

I would update this post indicating that even Fossil Gen 6, with the latest Wear OS 3.2 update, does not show the [SC] (steps) tag.

[amoledwatchfaces]

Can confirm, also - small correction, not working [SC] tag on Fossil Gen 6 with Wear OS 3.2 is not a WFS issue. Fossil most probably forgot to properly set Wellness app as a default system steps provider. I’ve already contacted Fossil support. Here is their answer:

@Fossil support

Hi Tomas,

Thank you for your reply. Our team will now escalate the case further to the team in charge for future improvement on this. We truly hope for your patience in the meantime.

Please monitor the device and feel free to drop us an email anytime if you have any other concerns or questions. We are always here to help.

Fossil will probably have to update the whole Wear OS system once again. This may take a long time…

[Matteo_Dini]

Good to know.

Now we have to understand if Google has also made a similar mistake with the Pixel Watch and can fix it with an update… Above all “when”.

[sinjae]

Hi all
I confirmed today that the latest Pixel watch firmware provides a correct value for [SC] tag rather than ‘K’ notation.

[amoledwatchfaces]

Hi @sinjae
It looks like this was partially fixed. For steps count lower than 10000, Pixel Watch is now reporting correct values = 6500 == 6500. For step count value >= 10000, problem is still present. 15500 = 15.5 K

Our [SC] and [SC_PER] tags therefore work correctly only when the number of steps is lower than 10000

Can someone confirm this? @Matteo_Dini

[amoledwatchfaces]

More info from Erik J.:

@Erik J.

The progress bar is correct until 10000 steps, yes. And up until 10000 steps, the step count is shown using the full number.

When the watch was first released, I used to see “K” for thousands under 10000, but that stopped at some point. Maybe they changed that in the November update?

What happens now is that you don’t see “K” until you reach 10000. Once you reach 10000, you see “10K”, “11K”, etc. So, it looks like this:

6492 steps: 6492

8531 steps: 8531

9999 steps: 9999

10000 steps: 10K

10099 steps: 10K

10100 steps: 10.1K

10615 steps: 10.6K

13824 steps: 13.8K

It shows the K only after 10000 steps, and it shows a decimal (for example, 10.1K) when the hundreds place is >= 1. So, 10K for 10000 - 10099, 10.1 K for 10100 - 10199, etc.). You can still see the total step count if you launch the “Fitbit Today” app, so the total step count is still kept somewhere, it just doesn’t show on the watch face. I don’t know if Watch Face Studio has access to the real step count or not.

[Matteo_Dini]

HI @amoledwatchfaces , @sinjae

Yes, I confirm this issue, Numbers are rounded after 10000 on Pixel Watch

Example:

From 10000 to 10099 = 10K
From 10100 to 10199 = 10.1K

and so on. …

[sinjae]

Thanks for the reporting.
communicating this issue with Google.

[amoledwatchfaces]

Hello, @sinjae can you also take a look at this?

Pixel Watch & other Wear OS 3 AODs turn off when using old faces (9to5google.com)

I believed it was enough to rebuild watch faces with WFS 1.3.12 (as it uses newer libraries) but looks like it’s still not enough. Some users are reporting this issue even when using watch faces created with WFS 1.3.12

@Matteo_Dini, thanks for confirming previous one.
Don’t you get similar emails about AOD on Pixel Watch? Would you be able to look at it?

Edit:
More info:
Screen turns off after 15 mins with AOD on on Pixel Watch with non-jetpack watchfaces [254441511] - Visible to Public - Issue Tracker (google.com)

I wish you a pleasant Christmas holiday

[sinjae]

WFS supports to use the latest jetpack watch face library.

I didn’t know about this problem, but according to the issue tracker’s thread, pixel watch will be fixed soon,
so we’ll have to wait and see how it’s modified.

Thank you for the reporting.