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🤠
  • 6 months ago in reply to FlowState

    It's not about the white background. This way I easily noticed it, but I would go crazy similarly if I would draw a circle and it disappears to one side.

  • 6 months ago

    > 2 minutes of typing, and 10 minutes of hacking my way through the stupid forum bugs...

    Clearly Garmin isn't willing or able to fix these problems ¯\_(ツ)_/¯

    It's an evergreen complaint for all things Garmin

  • 6 months ago

    My point is that it's disingenuous to say that pixel shifting doesn't mitigate the burn-in effects of your app when you know that your app isn't playing by the rules.

    For apps that use a black background, I think pixel shifting can be beneficial.

  • 6 months ago in reply to flocsy🤠

    2 minutes of typing, and 10 minutes of hacking my way through the stupid forum bugs...

  • 6 months ago

    > Why does a 1 line pixel burn in more than a huge area?

    Like I said, I think pixel shifting makes sense for apps which already play by the rules - i.e. they don't draw a solid white background on an AMOLED device.

    Garmin explictly says to use black backgrounds on AMOLED devices.

    If you prefer, they could also apply watchface-style burn in protection rules to data fields, and shut your data field down completely for using too much luminance.