Quote:
Originally Posted by cybmole
when I come back to the app it is usually as I left it - even if the tablet has been in overnight sleep - so If I was connected to content server I am still connected, if I was in bookshelf view, then I see that, if the last thing i did was look at metadata details & launch a reader app tehn that;s what i see.... in all those cases I would have "quit" like I do with any other android app, by bringing up & tapping "home".
|
None of this means that the app wasn't killed and restarted. For example, the save/restore state part of the content server activity re-creates the connection on restart. The book details activity re-attaches itself to the database. I see evidence of this behavior all the time in debug logs where where CC's start is logged then immediately it goes into a subactivity like book details.
Part of the state that is saved is the trace of activities that an app went through to get to some point. That is why the back button still works even if the app was killed.
Quote:
|
I wonder if the folks with th crashes do something different ?
|
This is an excellent question.
We had no end of problems in the beginning with CC being killed at inopportune times. Background "tasks" would suddenly find themselves without a parent. Network connections would disappear. Variables would change value. It took a long time to work through all the possibilities so CC could survive what Android does to it. All this to say that there may be some sequence that we haven't accounted for where CC's state is getting corrupted. In this case I would expect to see crash logs, but sometimes even those don't happen correctly.