Instinct 2x has API lvl 3.4.0 instead of 4.2.0

Hello, 

I'm building some app and want to use Flashlight API for Instinct 2x that has flashlight. But i noticed that 2x has API lvl 3.4.0 and Flashlight API becomes available from 4.2.0. So I'm a little confused now. Is Garmin planning to upgrade API lvl for Instinct 2x?

Top Replies

All Replies

  • Garmin will continue to get rid of MIP screens wherever they can

    "wherever they can"

    I already guessed above that Enduro, Fenix (and maybe Instinct) will continue to have MIP screens in the near future. (Many others have guessed the same thing, so I'm not claiming to be original)

    As DC Rainmaker already commented on one of his reviews, the MIP ship has sailed for Forerunners, and I'd guess for any line which has gone full AMOLED.

    I also see that a Tactix AMOLED edition has been released, which makes me wonder what "Fenix 8" (or whatever) will look like. EDIT: Now I see that the new Tactix is an Epix Pro variant which makes a lot of sense.

    As a runner I don't really care about Fenix that much anyway since I wouldn't buy a Fenix for running. (They're too big and heavy for me. I've seen ppl have GPS issues in the past, possibly because of the metal construction. Not sure if that's still an issue or not, though.)

    Oh well, all new tech has downsides, but when it's "good enough", people will usually ignore the downsides (and that's ok). Just too bad that I don't see MIP existing alongside AMOLED 2 to 5 years from now, unlike say, Wi-FI and wired ethernet.

  • Thank you! Garmin also tried to sell people on the benefits of transreflective screens, but apparently failed. I linked this before: Garmin Chroma Display. Funny that if I search for "Garmin Chroma Display", the 2nd result is a Garmin forum post entitled "Really disappointing screen Fenix 5 Plus Saphire" from 2018.

    I think the problem is once you have to "convince" someone with "facts and logic" that product X is better than product Y despite the evidence of their lying eyes, you've already lost the war. I mean if someone looks at AMOLED and MIP side-by-side (especially indoors) and decides that AMOLED looks much nicer, it's pretty hard to tell them that their opinion is "wrong".

    Just like when I tried to explain why Garmins are better in some ways than Apple Watch to a coworker training for his first marathon in 2019.

    Him (rocking an apple watch): "Why do you guys wear garmins???"

    Me: [useless iPad / Kindle analogy, followed by unsuccessful appeals to outdoor readability and battery life *]

    Other coworker (who was also wearing a garmin): Well, Garmin was there first

    The apple watch guy ended up implying that we were basically running snobs who look down on non-garmin users ("well I guess I'm a f--- loser for wearing an apple watch :/")

    (*)

    Me: My Garmin is super readable in bright daylight!

    Him: So is my apple watch!

    Me: I get great battery life from my Garmin!

    Him: I just charge my watch every night

    Me: I like to wear my Garmin to sleep so I can track sleep metrics and resting HR

    Him: I'm not really interested in that stuff

    etc.

  • (I do think AMOLED is probably a *lot* better for maps, so that's the one exception where I'd find it to be the superior choice of display tech for a forerunner.)

  • Speaking of recurring bugs / corporate culture, I just saw this newly reported bug:

    Connect IQ SDK .dmg download for Mac is not working. Please update or fix it.

    It's identical to a bug I reported years ago and is currently marked as "Complete".

    I get it: Garmin doesn't have the resources to fix every bug, which is fine. I just happen to see this stuff over and over again (in the products, Connect IQ, the website, and the forums) and it gives me a bad impression of Garmin. That also doesn't matter, since my opinion won't destroy or save Garmin either.

    It's just pretty annoying to me. Same as when I post some code which the forum platform happily accepts, but then when I try to make any edits to the same code, the forum returns a big "security error".

    Speaking of software issues, I'll just leave this here:

    https://news.ycombinator.com/item?id=27529664

    https://blog.smashrun.com/2021/05/21/a-new-garmin-api/

    https://chrislukic.com/2021/06/16/techniques-to-prevent-adoption-of-your-api/

    Techniques to prevent adoption of your API

    This appears to be the Garmin API, ...

    Their software has always been a major detraction from their really solid hardware.

    It's one thing to say that legacy products can't be completely redesigned. It's another thing to note bugs and design issues with every new thing that comes out. Again, I'm sure all the devs and engineers at Garmin are nice ppl who are very passionate about their jobs. I just don't think "being good at software" is part of the corporate culture. It isn't necessarily a reflection on any individual person, but there's something about the whole that's less than the sum of the parts, I think.

    I get it, I worked at a place like that for years (which also sold hardware, also had a ton of legacy products, and also went through a phase of reinventing/modernizing some of their older product lines.)

    I'll note that I found the "Techniques to prevent adoption of your API" post first -- it doesn't explicitly mention Garmin, only a "major fitness brand", but it was immediately obvious to me it was Garmin.

    So, how do you build an API that has technical hurdles so high that you can defeat a 20 year veteran who up until this moment has always found a way. How do you drive him slowly insane and drive all joy from a vocation he loves.

  • Seems, that in new update Garmin will add API for flashlight beta 14.09 Grinning

  • Nope, it doesn't. 

    In released version 14.12 changelog is

    Enabled Torch support for CIQ apps.

    But in emulator and on real device i can't see that this api is working.

    I use this check to show menu item:

        if(Attention has :setFlashlightMode){
            ...
        }
    

    And menu item does not shows

    Also i've noticed that for setFlashlightMode changed API lvl to 3.4.3 instead of 4.2.0 but Instinct 2x does have 3.4.2 API lvl.

  • I've checked that device does have 3.4.3 CIQ.

  • Have you tried that code on a real device? The device file in the SDK has not been updated to 3.4.3, it still says 3.4.2 so if the function is only available on 3.4.3 I'd not expect it to be available in the sim. But if a real watch is on 3.4.3 then it should be available on the real thing.

  • Hi ,

    Yes, i have tried code on real device and can't confirm that torch api is working. But i'm assuming that did something wrong. I'll create test app to check this issue more deeply.

  • I've made simple app with this code

        if(Attention has :setFlashlightMode){
            dc.drawText(self.w/2, self.h/2, Graphics.FONT_SMALL, "Flashlight api exists", Graphics.TEXT_JUSTIFY_CENTER | Graphics.TEXT_JUSTIFY_VCENTER);
        }else{
            dc.drawText(self.w/2, self.h/2, Graphics.FONT_SMALL, "Flashlight api \nDOES NOT exists", Graphics.TEXT_JUSTIFY_CENTER | Graphics.TEXT_JUSTIFY_VCENTER);
        }
    

    and get negative result, means that func setFlashlightMode does not exists. I did check on real device.