As I told you already, I personally have zero experience with Android phones - and as such, no idea how to pull logs from them. As I noted in my last response to you: have you filed a ticket with 505 CS via the link in their signature? If so, have you done so recently (say the last 3-4 months) since they completely reset their entire CS department? They are the closest to the port, they have that experience with Android and would know how best to pull said crash logs and to sort it out/get it to the devs.
Throwing shade and rage on here is all well and good, but doesn't actually do one thing to fix whatever issue it is that you have. Clearly the "it always crashes in 10m" bug isn't a 100% "happens to everyone" thing: rather it's isolated in some way...either to certain devices or something else that is being done. That is what the crash log will be needed to help sort out. Absent that, it's like asking to find a broken needle in a haystack of needles.
With all of this stuff, what I've consistently told everyone is - if you are really truly interested in making sure it gets fixed, then the best thing to do is to file the bug/ticket officially and then work with 505 directly to provide info and actually solve the problem. So many people have done this to good results for themselves and others - and I personally thank them for all their help there....it truly makes things better for everyone. Other folks choose to beat their fists against the wall - which may be cathartic, but is far from helpful.
That said, it's also the weekend - and I am not sure who all they have in the office since your last post. As for me, personally, I have work and family commitments that preclude me from spending hours googling "how to pull android crash logs" (which - of course - you could have already done if you were so inclined). As time allows, I'll look - but I repeat once again that the singular best way you can fix your issue is to file that ticket and work directly with 505 - tomorrow being Monday, I'll bet you guys could figure it out next week.
In the meantime, if anyone here knows how to pull Android crash logs and could share it for everyone, that would be awesome. I can help anyone with iOS logs.
As for refunds, my understanding is that those are all processed via the device stores themselves. I am not sure if their policies will allow a refund for a game played for years with no ticket filed to attempt to let the publisher (505) or dev (codeglue) work with you to sort it out. If that's what you truly want, then you are welcome to pursue that. I would submit that making the ticket and working to fix it would be the wisest choice.
I'm honestly not sure what else to tell you. I am trying my level best to point you in the right direction, but it only appears to be equal parts unappreciated and to drive your angry outbursts further - so I'll just leave you with the above and you can decide what you want to do from there.
Everyone knows there are issues on mobile - and they are being worked on, as evidenced by the handful of fix patches this year and with more already coming. So, be part of the solution if you want, but the endless raging without actually helping is fruitless. I promise you that when I have actionable stuff to push 505/CG on, I do - daily.
Light a few candles instead of endlessly cursing the darkness. We would all be thankful for the light.
I'll await those crash logs - or, again, anyone with an issue should really report it via the bug reporting/CS link and get involved in a direct dialogue with 505 to root out and squash the issue.