developer left out lesser known model of Fenix6s in compatible devices, can I sideload somehow?

Not quite sure where to ask this question but developers would know, Garmin feel free to move the question otherwise

the alphaHRV developer is not responding to queries so I am trying to find a way to get that app onto my Fenix6s standard which is lesser known than the pro model and somehow got left off the list even though it's the same hardware

https://apps.garmin.com/apps/1a69b10a-1d31-4afe-a32f-6a579ae20d9f

So Garmin doesn't offer my watch to install

Can I download the prg somehow and sideload it onto my Fenix6s via usb?

You can see all the Fenix5 and Fenix6 models are listed, it's just an oversight

  • It's not the same "hardware", at least not from the CIQ datafield point of view. Look here: https://github.com/flocsy/garmin-dev-tools/blob/main/csv/device2memory-datafield.csv to see how much memory the 2 devices have:

    fenix6:32768
    fenix6pro:131072
    fenix6s:32768
    fenix6spro:131072
    fenix6xpro:131072

  • ooooh!

    Many thanks for that education

    I always thought the difference was just the storage level on the standard vs pro as I only have 64mb vs 16gb pro

    But you are right, there's also a working memory difference

    What's interesting is other complex datafields can still work just fine, dozenrun, stryd, etc.

    But I guess alphaHRV has to look at a large window of data

    I wonder if there are coding tricks that could reduce the resource demands

    Eh I can live without realtime alpha1, it's better in post-analysis anyway for error-correction

  • I don't know how it's code looks, but most certainly there are things that can be optimized. Depending on how it is written it can free up a few percent or maybe even 10% of memory.

    As for the data structures, there's even more that can be spared usually. If it's using some kind of window, then this window could be made smaller for devices with less memory (I'm just doing something like this in one of my datafields)

  • slightly different question but you have so much knowledge it's too tempting not to ask you here since it's vaguely related

    there was a great widget I used on the Fenix6 that I've now lost on the Fenix7 which showed the weather internals from Garmin compared to a local Tempe and kept the tempe persistent

    Will the developer be able to easily update it for the Fenix7 and make it into a Glance instead?

    it was  mTempe and I've not found anything quite like it yet

    https://apps.garmin.com/apps/dd3e0666-b9d6-4b3a-9e98-672a256bc890

    I'm really annoyed the Fenix7 took away Widget support, a Widget is just an opened Glance

    Garmin could make an option for all/select Glances to become Widgets by forcing them open as if they were selected and just scroll through opened Glances

    btw I can now of course run this alphaHRV on the Fenix7 as it has the max 256mb of memory

    but not sure all the trade-offs was worth it, Fenix6 may have been peek Garmin

  • If you want something similar to mTemp, try my Temps app.

    Temps | Connect IQ Store

  • I didn’t see this topic before. As mentioned above, fenix6 and 6s are restricted in terms of datafields memory size more than their corresponding pro versions.

     Believe me, alphaHRV is really optimized, but even in this case, it’s not possible to built it for fenix6-6s

  • ah good to hear from you!

    I've very recently this month upgraded to a Fenix7s so I can finally run alphaHRV and now I get why it wouldn't work on the Fenix6s with the lower memory

    (7s has full 256mb RAM vs 32mb RAM on the 6s, I just wish it had 4x CIQ support, still only 2x)

    alphaHRV is an absolutely amazing datafield, in some ways more powerful than many FirstBeat metrics

    It seems to get my respiratory rate more correct than the FirstBeat methods and the heartrate must be R-R based as that also is not identical to what the native HR reports and likely more accurate

    My only complaint now about alphaHRV is it demands GPS to function? 

    Is that a limitation of the Garmin API or might you be able to work around it?

    When I run, I use Stryd as the source of distance+pace as it is more accurate than GPS but at least the datafield will still work as there is GPS outside

    But of course it then refuses to work when I use the indoor cycle trainer despite having cadence+speed sensors

    Shouldn't alphaHRV still be useful on a cycle trainer? It's fixed gear and not freewheel so the cadence+speed is actually accurate

    I can produce higher heartrate on the trainer, sometimes maxHR which is why I would be curious to see what alphaHRV records

    Keep up the great work and thanks for sharing it

  • alphaHRV only needs a HRM that transmits RR-ints connected in BLE or ANT mode. No GPS or any other sensor is required

    Contact with me using the option in the store and I will be happy to help