Complete
over 4 years ago

WERETECH-8476

Display bug from firmware update or SDK? Fenix 6x Sapphire misreporting screen shape (probably)

I have three products that all use logic based on screen shape and obscurity flags to layout the screen.

They seem to work well until I released an upgrade recently... changing SDK 3.1.5 to SDK 3.1.6 despite the known issues in debug environment because I wanted to support the newer watches. This immediately resulted in a bug report from a customer. So I downgraded to SDK 3.1.5 and the bug persisted.

As the identical (seriously) code used to work and now doesn't with both the newer and the older SDK, I have to put this down to external factors.

The customer confirms that there was a system update between his using my DataField and his noticing the bug. Therefore, it looks probable that the firmware might be at issue.

For reference, the following conditional breaks on Fenix 6s Sapphire and didn't previously..

var settings = System.getDeviceSettings();

var isSemiRound = settings.screenShape == System.SCREEN_SHAPE_SEMI_ROUND;
if (!isSemiRound && obscurityFlags == (OBSCURE_RIGHT | OBSCURE_LEFT | OBSCURE_BOTTOM | OBSCURE_TOP)) {
 // THIS SHOULD MATCH THE FENIX 6S
} else {

  // THIS SHOULD NOT MATCH THE FENIX 6S

 }

The code is misreporting so that it displays for a square layout when it should display for a round one.

I am at a loss to know what to do here. 

PLEASE HELP!

9635560
Parents
  • over 5 years ago

    Hi,

    I replied to Stephen over the weekend and it doesn't seem to be displaying...

    So, to ensure the data gets there:

    1. Yes, flags are DataField.getObscurityFlags();

    2. (8 | 4 | 2 | 1) == 15 because the binary operator does (1000 | 100 | 10 | 1) == (1111)

    3. This code is _not_ new code - it works when the input data is good

    4. The device as reported to me by the customer is:

    Fenix 6x Sapphire Asia.

    Software ver. 5.10

    Sorry to repeat myself if my comments are simply awaiting moderation somewhere, but if that is the case, then PLEASE make that information available to me so that I don't have to follow up like this.

    G

Comment
  • over 5 years ago

    Hi,

    I replied to Stephen over the weekend and it doesn't seem to be displaying...

    So, to ensure the data gets there:

    1. Yes, flags are DataField.getObscurityFlags();

    2. (8 | 4 | 2 | 1) == 15 because the binary operator does (1000 | 100 | 10 | 1) == (1111)

    3. This code is _not_ new code - it works when the input data is good

    4. The device as reported to me by the customer is:

    Fenix 6x Sapphire Asia.

    Software ver. 5.10

    Sorry to repeat myself if my comments are simply awaiting moderation somewhere, but if that is the case, then PLEASE make that information available to me so that I don't have to follow up like this.

    G

Children
  • over 5 years ago in reply to 9635560

    Thanks I see how your code snippet is working now. I had to refresh on how bitwise or actually works :) 

    Also, thanks for clarifying that this was on an Asia device. There are differences between the Asia devices, so it is possible this issue is only seen on those devices, which I wasn't using when I originally tested for this issue. We will take a look on that specific device/fw combination for this issue.