Dealing with Object Store Save on User Reboot

I'm pretty sure this shouldn't work this way. The device should shut the watchface down before it powers off. I'll report the issue to the product teams.

I'm pretty sure this shouldn't work this way. The device should shut the watchface down before it powers off. I'll report the issue to the product teams.

Thank you .. :cool:

Brian. I tried a couple of simple tests for this.

A watchface on the va-hr with the latest beta FW, and a watch-app on a 230 with the latest beta FW.

In both cases, the Object Store isn't saved if you power down after the OS was changed (setProperty() ) in the code while the watchface/app was running. When powered back up, the OS in both cases has the value from the last clean exit and not from the power down. So this isn't unique to the va-hr.

I've always thought this was just the way it worked.

I'm sure it is "just the way it works", but it is pretty silly not to shutdown and save things in ConnectIQ when we are intentionally powering the device down. It's not like pressing the power button is disconnecting the battery. I don't think this will be a hard fix for the device teams to make, but I suspect it might not make it into all the releases for 2.1/1.3.

I'm sure it is "just the way it works", but it is pretty silly not to shutdown and save things in ConnectIQ when we are intentionally powering the device down. It's not like pressing the power button is disconnecting the battery. I don't think this will be a hard fix for the device teams to make, but I suspect it might not make it into all the releases for 2.1/1.3.

Thank you Brian .. I would be very interested in finding out when this is fixed for the VAHR in particular as that is the device I use. I cannot comment on the other devices but I think that jim_m_58 has confirmed for us that this is not an isolated issue. Thank you to him for doing this testing. :)

Brian - it occurred to me that you might want to add something for the the report/ticket to the platform teams.

This is something I didn't test (it takes a lot of time to drain the battery!), but it could be that if the .str isn't being saved for a normal power down, it also might not be saved when the FW shuts the watch down due to a low battery. (at something below 10% IIRC)

Update:

and for low battery shutdown in the case if a CIQ recording app take care of doing a "session.stop()/session.save()" so the .fit data is preserved?

As far as I know, low battery should go through the same flow as manual power off, so I think fixing this should cover both cases.

FIT should already be stopping the activity when the device powers off, and any non-finalized ConnectIQ recordings that are present when the device powers on should be automatically saved.

Yeah... I think the FIT stuff still doesn't work how it is supposed to across the board. The way I describe above is the behavior that is supposed to be implemented. I ran across an issue this week with this not working as it should.

Might it make sense to add a callback for watch-apps (onPoweringOff() ?) so the CIQ app can clean up things when the power is going off?