Forerunner 235 obscurity flags - ok in sim but not on real device

Just a quick heads up in case anybody else has noticed this, I'm still debugging and will post further info later tonight.

I've developed a datafield targeting the 235. I'm reading the obscurity flags to re-format the layout depending on number of datafields per screen. It works fine in the simulator, but when I sideload onto real device running firmware v3.10, it appears as though the flags are not being read, or are returned as zero.

It's time consuming to debug as I have to sideload for each run, and debug output has to go to the real device screen rather than system.println on the console.

Nikeow over 9 years ago

The FR235/230/630 are currently problematic from what I can tell.
I bang'ed my head more than a few times trying to sort things out.

And Garmin's official word is that they know there are these quirks on the watch. So, they acknowledge it.

Obscurity flags, Is it not an option to utilise the watch screen as the debug output?
I do that at times, better that than pluugging in and out and looking at the debug output on the LOG file. (which If I am reading right - that's exactly what you are doing?)

Former Member over 9 years ago

The obscurity flags were not set on the device in the initial release due to an oversight. They are being updated to match the flags seen in the simulator and will be corrected on the device in the next release.

PatFelstead over 9 years ago

Thanks Brian, good to know.

PatFelstead over 9 years ago

Obscurity flags, Is it not an option to utilise the watch screen as the debug output?

Yes I am doing this

I do that at times, better that than pluugging in and out and looking at the debug output on the LOG file. (which If I am reading right - that's exactly what you are doing?)

No didn't know I could do that - thanks

PatFelstead over 9 years ago

The obscurity flags were not set on the device in the initial release due to an oversight. They are being updated to match the flags seen in the simulator and will be corrected on the device in the next release.

It looks like the new FR235 beta 3.13 didn't fix this - at least not for me. Can you confirm please?

travis.vitek over 9 years ago

Confirmed that problem still exists on 630 v3.13. Here is a test case.

using Toybox.Graphics as Gfx;
using Toybox.WatchUi as Ui;
using Toybox.Application as App;

class TestView extends Ui.DataField
{
    function initialize() {
        View.initialize();
    }

    function onUpdate(dc) {
        var color = getBackgroundColor();

        dc.setColor(color, color);
        dc.clear();

        dc.setColor(~color & 0xffffff, Gfx.COLOR_TRANSPARENT);

        var cx = dc.getWidth() / 2;
        var cy = dc.getHeight() / 2;

        dc.drawText(cx, cy, Gfx.FONT_SMALL, getObscurityFlags().toString(), Gfx.TEXT_JUSTIFY_CENTER | Gfx.TEXT_JUSTIFY_VCENTER);
    }
}

class TestApp extends App.AppBase {

    function initialize() {
        AppBase.initialize();
    }

    function getInitialView() {
        return [ new TestView() ];
    }
}

Former Member over 9 years ago

I did see this fix go through, so it must have just missed the 3.13 beta release. I'll try to double check something didn't get messed up.