• Replies 9 replies
  • Subscribers 20 subscribers
  • Views 1377 views
  • Users 0 members are here
Options
Related

Possible settings issue

Shent-Aurkhan (SHN)

hi mates,

I've been reported several time that when the settings want to be changed,

when they are saved, the watchface goes back to "default settings" (when first installed)

if they go back to the settings, they show what it was set but the watchface is stuck to "default"

hope i explain it weel...

does anyone have this issue?

  • I am facing not exactly the same but similar issue, i guess it is related. Watchface goes to default settings after settings change, but in my case only after user leave the watchface screen e.g. to widgets or any other app.
    I ve had garmin involved but never got real clue what the issue is. In simulator it demonstrate itself in form of appearing and disappearing (deleted) SET file and i suspect it may be related to the memory consumption during settings change.

  • in reply to tomulli

    Hi, 

    This issue seems to come back, do you have any clue now ? Memory issue ? 

  • in reply to Shent-Aurkhan (SHN)

    I believe settings are saved periodically, definitely at app exit. If there’s a crash prior to save, settings may be lost. 

    Was there anything in ERA?

  • in reply to 9635560

    Nothing on ERA, and no CIQ logo on watch face, just rested to "default" settings

  • in reply to Shent-Aurkhan (SHN)

    The only time the .set file should get corrupted is when it's saved - something like trying to save more than is allowed.

    If you are using the .set file to save things without an associated setting, you should save them to Storage instead.  It reduced the size of the .set file, and there's less chance of corruption.

    the .set file will be saved when an app does a setProperty/setValue, so minimizing those should help with this.

  • in reply to Shent-Aurkhan (SHN)

    I gave up. I deeply believe they have some systemic flaw there which is coming out from time to time. And i would not be surprised if default settings are sometimes pushed from server just like that. I have even experienced to have my watchface one version lower then released one install on the watch while set file was from the latest one. Also when automatic over the air watch firmware update is performed by Garmin without me requesting it weird things are happening. Last occurrence this morning being suddenly updated to 13.10 and face went crazy until watch got rebooted.

    Settings and memory consumption is another mystery to me, did uncountable amount of testing coming to various result but always way out of  what i would expect even if they would do copy of settings in the memory for merging purposes.
    I ve never received explanation for evidence of unexpected behavior with regards to available memory i have provided.

    Since  they allowed on devices settings i am slowly moving this direction as it seems to behave differently for some reason. Unfortunately in my case it results in extremely user unfriendly way of configuring things.

    From my ERA i can see many watches report error when attempting reading settings even default ones. So definitely something smells on Garmin side.

  • in reply to tomulli

    The .set file maxes out at about 8k.  That's keys, values, and some overhead.

    With on device settings, you really don't need the .set file at all, as you can just use Application Storage, which maxes out at about 8k per key, and about 100k in total, so much more room to breath. And don't forget, it's only for devices running 3.2 or greater.

  • in reply to tomulli

    Many thanks for you reply, I asked to them today and nothing wrong anymore, might be a "servor" issue.

    or as Jim said may be their device run out of memory and "corrupt" the .set file

    I use the old way to do (prior CIQ 2.4)

  • in reply to Shent-Aurkhan (SHN)

    If you can, witch to the "new way", even if it means using a "has" to determine which.  I've found the "new way" less problematic.