Status of standby mode and robustness improvements?

It's cool that the K2 keeps improving with some frequency. However, two things have had me leave it at home and use my old computer (both reported/requested by many people including myself already):

1. The seeming lack of persistent state in the unit, i.e. if the unit crashes, it should start up again with all state preserved, e.g. your ride as it looked when the unit crashed should still be there. There are so many posts in this forum about unpredictable behavior and lost rides.

2. As an extension of 1 - standby mode. I can maybe live with the unit taking ages to boot up every time, and requiring me to remember to turn it off or it will die after a few hours. Having a standby mode for instant startup is a (very) nice to have, but I guess not essential. But I can't live without the possibility to put the unit in standby mode in the middle of a ride, leave it there for as long as I want (think longer than the battery life) and then pick up my ride where I was. Actually recycling power should be an exceptional event (which I do maybe 3-4 times a year with my other equivalent device, when it too freezes or crashes, which is probably inevitable. The difference is that no data is ever lost on that device, it will boot up with the data intact.)

What kind of priority do these have in the engineering backlog?