|
Aug 2015
10:15am, 13 Aug 2015
16,035 posts
|
flanker
Didn't know you could back up settings. How does that work?
|
|
Aug 2015
11:18am, 13 Aug 2015
5,422 posts
|
Badger
Mount it via USB and copy the relevant files somewhere. To restore, mount again, copy the files into garmin\newfiles (hidden by default), eject and they'll be restored.
See:
https://support.garmin.com/support/searchSupport/case.faces?caseId={783045f0-96a4-11e4-6479-000000000000}
|
|
Aug 2015
11:18am, 13 Aug 2015
5,423 posts
|
Badger
The close curly bracket at the end of that link should be part of the link.
|
|
Aug 2015
4:22pm, 13 Aug 2015
5,424 posts
|
Badger
4.3 has been pulled because of the settings issue. It does actually seem to be working OK now that I've got the settings back.
|
|
Aug 2015
4:58pm, 13 Aug 2015
16,038 posts
|
flanker
I've upgraded mine, and lost the bike and hike apps, needing a factory reset and restoring backups.
However it then took another 30 minutes to reset everything that the backups didn't include - wifi settings, routes (should have seen that one coming), BT, grid ref datum, etc etc.
I don't think I've ever come across a major company that releases such buggy software as Garmin. They're even worse than MS! It make you wonder if they test their updates at all on real-world devices.
|
|
Aug 2015
8:36pm, 18 Aug 2015
16,048 posts
|
flanker
4.4 is out, and guess what ... it trashes any custom settings you may have, and just restores all the default apps.
only Garmin could update a pulled update and compound the mess they made the first time.
|
|
Aug 2015
8:41pm, 18 Aug 2015
5,455 posts
|
Badger
The word on the forums is that users who were lucky enough not to update to 4.30 before they pulled it didn't lose their settings with 4.40; it deliberately scorched the Earth on watches running 4.30. Oh well, I'm too broken to run at the moment anyway, might as well waste time restoring backups again.
Does extended timeout still work for you with 4.40? It doesn't for me.
|
|
Aug 2015
1:52pm, 19 Aug 2015
16,049 posts
|
flanker
if you mean the the extended timeout before going into stand-by (?) then I have no idea as I don't use it 
You've got about 4 weeks to get yourself fixed before RNR!
|
|
Aug 2015
2:02pm, 19 Aug 2015
5,460 posts
|
Badger
That's the one, yes.
My physio is aware of my deadlines (and is surprisingly optimistic about Abingdon Marathon!)
|
|
Sep 2015
7:43pm, 25 Sep 2015
16,101 posts
|
flanker
If anyone still hasn't upgraded to 3.7 firmware I'd suggest you don't.
Ever since doing it my F3 has lost the run within the first 1/4 mile, just going back to the watch screen. Restating seems to be ok ... Until you finish the run, when it goes into a crashing loop that means you can't save or discard the run.
When this happens to really ruby R nose in it, it lose 90% of your steps.
|
