You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As reported in a review on Google Play (now deleted) it worked once, beautifully, on my Samsung Galaxy Tab S3. Ever since it was appalling slow, to the point of being unplayable. I tried clearing the data. I tried uninstalling the version from F-Droid and installing it from Google Play instead.
Finally I had moment of inspiration and re-booted the Tab S3 and then re-installed 2050 (from F-Droid) and ... it works a treat, in fact it's faster then it was originally.
So my tentative conclusion is that for some reason the game gets slower the longer the device has been running for (which can be many days in the case of my Tab S3). Having said that no other app has ever exhibited this behaviour so it does seem odd.
If and when it slows down again I'll see if I can work out how to generate a logcat output but I thought I'd raise the ticket now in case it rings any bells with you as to what might be going on.
The text was updated successfully, but these errors were encountered:
As reported in a review on Google Play (now deleted) it worked once, beautifully, on my Samsung Galaxy Tab S3. Ever since it was appalling slow, to the point of being unplayable. I tried clearing the data. I tried uninstalling the version from F-Droid and installing it from Google Play instead.
Finally I had moment of inspiration and re-booted the Tab S3 and then re-installed 2050 (from F-Droid) and ... it works a treat, in fact it's faster then it was originally.
So my tentative conclusion is that for some reason the game gets slower the longer the device has been running for (which can be many days in the case of my Tab S3). Having said that no other app has ever exhibited this behaviour so it does seem odd.
If and when it slows down again I'll see if I can work out how to generate a logcat output but I thought I'd raise the ticket now in case it rings any bells with you as to what might be going on.
The text was updated successfully, but these errors were encountered: