I did a bunch of experiments today and it happens no matter how I re-open the app. Via "recently opened", via the shortcut or the app drawer.
Many times I can resume fine, but given enough other apps (presumably enough memory pressure to kick DraStic out of memory), and I lose state and need to ...
Search found 3 matches
- Tue Nov 05, 2013 10:43 pm
- Forum: Help and Compatibility
- Topic: autosave on forced exit
- Replies: 6
- Views: 15383
- Tue Nov 05, 2013 7:59 am
- Forum: Help and Compatibility
- Topic: autosave on forced exit
- Replies: 6
- Views: 15383
Re: autosave on forced exit
Apps can know this: http://developer.android.com/reference/ ... ause%28%29 Android's Activity.onPause() is built for precisely this purpose.
I agree the ideal workflow is to save state, but it really sucks when something urgent comes in and you lose your save...
I agree the ideal workflow is to save state, but it really sucks when something urgent comes in and you lose your save...
- Tue Nov 05, 2013 12:24 am
- Forum: Help and Compatibility
- Topic: autosave on forced exit
- Replies: 6
- Views: 15383
autosave on forced exit
After playing for a while, I'll get a phone call or email and switch to another view.
Before I know it, I'll have done ten other things and when I come back to DraStic, it's been closed by android.
I can restore from a save state or a savegame, but autosave doesn't seem to happen when android kills ...
Before I know it, I'll have done ten other things and when I come back to DraStic, it's been closed by android.
I can restore from a save state or a savegame, but autosave doesn't seem to happen when android kills ...