SDK 3.2 On-Device Settings and Memory Usage. Workaround?

I am designing a watchface with on-device settings. However, accessing on-device settings triggers Out of Memory error (for devices with lower memory limits, e.g., fenix 6s). I gather it is consuming more memory on top of the memory being used by the watchface. Is there a workaround (i.e., clear the memory stack)?

jim_m_58 over 5 years ago

Your setting code is actually part of the watch face. How much is used is based on how you implemented it.

yp over 5 years ago

When you are in on-device setting, you can free some memory in the main view which now is not usded. After on-device setting and return to the main view, then free the on-device setting object and then re-alloc what you freed before. By this means, you can save some memory.

gekaram over 4 years ago in reply to yp

Can you exemplify?

jim_m_58 over 4 years ago in reply to gekaram

What you'll likely have issues with is not the runtime memory, but the extra code need for on device settings. It could push you beyond the memory limit for an app.