Acknowledged
5 months ago

bug: fr965 (real) 1 Field layout is off-center

Somewhat similar to https://forums.garmin.com/developer/connect-iq/i/bug-reports/bug-vivoactive5-has-bad-screen-position-for-1-field-datafield-layout-in-simulator except that this happens on a real fr965 with FW 21.19 (and it doesn't happen in the sim): My full-screen data field is added to a 1 Field layout, the default setting on the device is black background, and onUpdate starts with:

dc.setColor(Graphics.COLOR_WHITE, Graphics.COLOR_WHITE);
dc.clear();

Note that I don't use clipping in my code.

I started an activity and noticed that it's slightly off-center to the left, top. Took this screenshot, note in the right and the bottom an arc is "missing":

Then a minute later, still in the same activity it changed to this (note that now the right is OK, only the bottom is missing):

flocsy🤠
Parents
  • 6 months ago

    > as I literally drew thousands of white pixels on the whole screen that don't move for all the duration of the activity

    > Only around the texts it will have any effect, and of course in the "edges" where sometimes we see the black arc.

    This would still tend to avoid burn-in for things like text and line graphics, which I assume is the main purpose of pixel shifting.

    Even if all of those white pixels burned in, seems like it would be less noticeable than burned-in black text

    Ofc it's not recommended at all for you to draw a data field with a solid white background on an AMOLED device (pretty sure Garmin explicitly says somewhere that black backgrounds are preferred for AMOLED). There's a reason that AMOLED devices don't even allow you to select a white background for a native watchface or activity.

    So you can hardly fault Garmin for inadequately guarding against the effects of a dev doing something that they don't recommend doing.

Comment
  • 6 months ago

    > as I literally drew thousands of white pixels on the whole screen that don't move for all the duration of the activity

    > Only around the texts it will have any effect, and of course in the "edges" where sometimes we see the black arc.

    This would still tend to avoid burn-in for things like text and line graphics, which I assume is the main purpose of pixel shifting.

    Even if all of those white pixels burned in, seems like it would be less noticeable than burned-in black text

    Ofc it's not recommended at all for you to draw a data field with a solid white background on an AMOLED device (pretty sure Garmin explicitly says somewhere that black backgrounds are preferred for AMOLED). There's a reason that AMOLED devices don't even allow you to select a white background for a native watchface or activity.

    So you can hardly fault Garmin for inadequately guarding against the effects of a dev doing something that they don't recommend doing.

Children