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

Top Replies

flocsy🤠 10 days ago +1

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…

All Replies

0 flocsy🤠 10 days ago

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

0 RinseRepeat 10 days ago in reply to flocsy🤠

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

0 flocsy🤠 10 days ago in reply to RinseRepeat

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)