Backup current firmware possible?

You can roll back to any firmware version without any problems. The main thing is to have the firmware file itself. Most of them are available from socorsu. You can ask him

DR said:

I have no issues with that firmware version. 

Strong recommendation: if it is running w/o issues for you leave it there. I'm doing a comparison right now with two units - one at 15.77 and one on 21.19 - for exactly the same reason you'd wish to upgrade: CIQ. But so far I have to say: Rather no CIQ than what I observed with 21.19 so far.  

DR said:

It seems that it is possible to downgrade firmware versions

It is, and you found the the best support you can get for things like that already: socorsu. The how to is essentially the way described in the  Beta announcements for the first minor version of a newly announced major version. In the package for your system is a description. However, we tuned that a little for better reliability. I could send it to you, if you enable "PM". As for the software package: for F7 pro (all sizes) I do only have 15.77. Which should do fine. But I'm almost sure that socorsu has 18.16 also for the F7 pro (make sure that yours is indeed a F7 pro, F7X pro & F7S pro need other files) - he is really the man to go to and one cannot praise his work enough. You may send him a PM.

DR said:

if I can extract it somehow from my current watch firmware?

No, there is no way since a lot of files are hidden with no way for us to make them visible. But see statement above.

DR said:

Maybe some are open source and I can just compile and side load them myself.

That being another topic and so far I don't see another way than write a message to the developer of your favorite app, WF or DF and ask him whether he would send you a version of his work compatible with 18.16 as .prg. I did not do this so far but when I see how my comparison tests are going a long I might give that a try in the near future. Probably it won't be enough to copy the .prg into the Apps folder. I'm unsure how to do the configuration is made with a sideloaded app. Will it be seen in Garmin Express or Garmin IQ Connect?  

ALK1980 said:

Most of them are available from socorsu.

Erik T7 said:

the best support you can get for things like that already: socorsu.

Thank for the pointers, seems like socorsu is real GOAT.

Erik T7 said:

Rather no CIQ than what I observed with 21.19 so far.  

Yikes, what issues are you seeing with 21.19 to want to stay on the older firmware?

Erik T7 said:

Probably it won't be enough to copy the .prg into the Apps folder.

I'm not an expert, since I only recently started dabbling with ConnectIQ, but as far as I understand it the .prg file is enough to sideload an app or watch face, including any settings it might expose that get configured through Garmin Connect. These are generated dynamically based on config compiled into the .prg. I could be wrong.

One of the app I'm missing the most is Spotify and that I won't get as a .prg from Garmin themselves :p 

Erik T7 said:

Probably it won't be enough to copy the .prg into the Apps folder. I'm unsure how to do the configuration is made with a sideloaded app. Will it be seen in Garmin Express or Garmin IQ Connect?  

DR said:

I'm not an expert, since I only recently started dabbling with ConnectIQ, but as far as I understand it the .prg file is enough to sideload an app or watch face, including any settings it might expose that get configured through Garmin Connect. These are generated dynamically based on config compiled into the .prg. I could be wrong.

If you sideload an app, settings which are normally configured in the Connect IQ app (or Garmin Express) are unavailable.

So you're stuck with the default settings unless:

- the app also has settings on the device itself

or

- the app developer would be willing to generate a customized settings file for you (which you would have to copy to the watch manually, similar to how you copy the PRG file). Ofc this process would have to be repeated any time you would need to change settings, so it's hardly practical

The technical reason for this is that the metadata for app settings is in the CIQ store, and Garmin is unable (or unwilling) to provide that metadata for sideloaded apps (as they are not installed from the store).

A similar limitation is that if a sideloaded app writes data to the activity FIT file, the corresponding graphs and/or summary data won't appear in Connect as they would if the app was installed from the store.

Interesting, learned something new today. Thanks FlowState!

DR said:

Yikes, what issues are you seeing with 21.19 to want to stay on the older firmware?

Just have a look into my postings here done lately as answers to problem reports. I'm doing a comparison with two units, one on 15.77, one on 21.19, which I wear simultaneously. I'll provide a full report when I'm done. Basically all metrics connected to HR are loopsided probably b/o the  erratic behavior of OHR when HR changes more or less rapidly. This impacts intensity minutes, recovery time, stress, body battery & HRV (exept during the night when HR is quite steady). Breath rate never has been accurate (which is not be expected with an optical wrist sensor)but is now easy 100% off, barometer sensor drifting way more than before. Battery life is good though.

FlowState said:

Ofc this process would have to be repeated any time you would need to change settings, so it's hardly practical

That's what I suspected given your explanations in previous posts. Thanks a lot for the clarification. It seems the is always a price to pay - I mean in addition to what I shelled out already to Garmin which was not small buck. I 'd still prefer my system to be reasonable accurate even if that costs me the CIQ. What a pitty, I really liked it and maybe some far day we get a decent software version again - it's suppost to be the maintenance phase now isn't it. 

So, it turns out not as bad as I though. If you are compiling a CIQ app anyways, you can run it in the simulator and through there, configure the settings. That generates a file in the temp folder of the simulator, matching the watch directory layout. You can simply copy this file to the watch and the settings are applied.

I thought the developer had to do something extra special, but if I can do it myself, that's not half as bad.It's cumbersome for sure, but I rarely fiddle with configs, once I have them set the way I want, so this is quite workable for me. I actually tried it out earlier today with Segment34 MkII, an excellent open source watchface.

Thanks for this very promising idea. I planned already to play around a little with watchfaces (which are still be seen on 15.77 unlike apps & data fields and unlike 21.19 where all prg are hidden now) when I hook up with my test unit next time and I'll include this idea for sure.

If that works out that would mean that it's "just" about to have a helpful developer who is willing to send the prg. I have no idea whether some were willing to do so though.

DR said:

I rarely fiddle with configs, once I have them set

Me neither, usually.

Btw: some apps can be customized on device already, Manuel B. is a pioneer in this department with his excellent watchfaces. See here: https://apps.garmin.com/de-DE/developer/6436a326-9f3d-4e5d-a6c6-2ec8550bd37b/apps No we are not affiliated, I just like the approach he drives and the results. ;-) 

Seems we are narrowing in to a even more agreeable downgrade scenario...

Great hint, thx.