@wharp95 It is sad that no one wants to acknowledge this issue... I'm not sure what would make them pay attention at this stage. There's plenty of negative reviews on the store; it's not like we haven't raised it here. It's clearly not a priority for them.
I don't know if reporting the game will have any effect as I suspect it just gets fed into another data pipeline for machines to analyze until a significant pattern is found. And I suspect existing reports would have been enough for that (given that Google will already have auotomatic reports for crashes from many users). Do let us know if anything does come of this, though.
In the meantime, I'm having one last go at trying to quantify how to check the safety of playing a match on my device. If I can find a way to show when you are in danger, I'll post as my workaround for the bug.
If anyone else is interested, I'm using
https://play.google.com/store/apps/details?id=com.spencerstudios.ramlogger to check free RAM on my device as I play. I hope to find a dangerous level at which point I will need to close and restart the game. Thus far I have got down to 300MB free and safely played a full battle.
