Simulator Bug: Clears Memory after Sending Settings

That may not be "plenty" based on what you are doing with settings, as changing settings requires a bunch of memory - the app has to merge the old with the new and can be in the 2+kb range,   What do you see as the current memory usage (check "view memory" vs the bottom line of the sim).

The problem you describe is what you can see when there's not enough memory to update the settings.

That may not be "plenty" based on what you are doing with settings, as changing settings requires a bunch of memory - the app has to merge the old with the new and can be in the 2+kb range,   What do you see as the current memory usage (check "view memory" vs the bottom line of the sim).

The problem you describe is what you can see when there's not enough memory to update the settings.

Will do, and only 11

Instead of using properties for everything, use storage where it makes sense.  Unless it's something that the user can change with settings, it really doesn't need to be a property but can just be in local storage

What is your total for properties?

Yes

are you mixing properties with settings and properties without settings?  

One thing to try is switching to a target with a larger sized (memory wise) data field, and see what peak is there after changing settings

A fr245 has the 28.6k max, while a 245m has a max of 60.6k for example