Version: 1.2/current play store version
Device: Shield Tablet K1 with 6.0.1
Minecraft version: any
It matters not what version of Minecraft I run, I cannot seem to escape from this pesky beetle.
When I press the keyboard button, my Navbar pops up, it gets slow, then about ten seconds later, the keyboard finally shows -but doesn't do anything- and then the game gives me a fc prompt. I do keep my device in Fullscreen mode all the time, and the navbar interacts wierd with the game when it pops up, so perhaps it could be something to do with an unexpected change in window size?
And now for my minor complaints:
It still uses a GL to GLES conversion filter on devices capable of native GL, negatively impacting performance on higher end devices no doubt. Perhaps it could have an automatic test to check if the device is capable of native OpenGL 1.4 or higher functions before deciding whether or not to use GLShim?
It's so SLOOOOOW (Sorry, I had to)
Controls could use an overhaul as well as a basic options menu for customizability.
Since the multitasking of android N is going to involve unexpected window size changes, I'd say that it gives you all the more reason to work out those window size change related crashes now, before they become a problem in android 6.2/7.0/N/something.
Version: 1.2/current play store version Device: Shield Tablet K1 with 6.0.1 Minecraft version: any It matters not what version of Minecraft I run, I cannot seem to escape from this pesky beetle. When I press the keyboard button, my Navbar pops up, it gets slow, then about ten seconds later, the keyboard finally shows -but doesn't do anything- and then the game gives me a fc prompt. I do keep my device in Fullscreen mode all the time, and the navbar interacts wierd with the game when it pops up, so perhaps it could be something to do with an unexpected change in window size?
And now for my minor complaints: It still uses a GL to GLES conversion filter on devices capable of native GL, negatively impacting performance on higher end devices no doubt. Perhaps it could have an automatic test to check if the device is capable of native OpenGL 1.4 or higher functions before deciding whether or not to use GLShim? It's so SLOOOOOW (Sorry, I had to) Controls could use an overhaul as well as a basic options menu for customizability. Since the multitasking of android N is going to involve unexpected window size changes, I'd say that it gives you all the more reason to work out those window size change related crashes now, before they become a problem in android 6.2/7.0/N/something.