Hi Guys,
Now, I noticed this issue first a few months ago when I updated my
Best Night Light app on Google Play; but only on a Samsung Galaxy Tab 2 tablet (running Android 4.x) which I just put down to just being an old device as none of my other test devices showed the same problem.
The above image is an example of the problem. You can see the the text on the black menu area hangs over the edge into the rest of the UI, also if you look closely the Lava lamp button (and the other two mode buttons, but they are hidden) are miss-shapen, they're supposed to be square). It also plays havoc with the help and about texts.
To be honest when I saw this I was confused as to how it'd managed to get through testing. I personally had tested it (on the player at least) on half a dozen test devices including the Tab 2. So I fired up the AppGameKit player on the tablet and lo and behold, this is what I saw...
It looks exactly as it does on all the other devices (which is how it's supposed to look!). I did bring this up with some other AGKers at the time, but nothing much came of it. However, the screen shots above aren't from the Galaxy Tab 2!! They are from a Kindle Fire 8 (6th Gen)!! So my issue isn't just limited to older devices, as the Kindle is fairly recent; but it also highlights a difference in behaviours between a compiled AppGameKit app, and one playing on the player.
It's been compiled with the latest version of AppGameKit, and I'm using percentage resolution with setscissor(0,0,0,0) in effect to remove the black bars.
So firstly, if anyone here with a spare 5 minutes and an Android phone/tablet to hand, can you just download my app and check out whether the screen looks like image 1 (bad) or image 2 (good). I'm concerned that such a bug is currently affecting an unknown percentage of devices, and could be a significant portion of my audience. (I have mostly Samsung Devices, which all have hardware buttons. The two tablets which showed the problem have buttons which appear at the bottom of the screen)
Secondly, and this is aimed more at Paul than anyone else, but can you look at why the Player is handling the screen properly but not the compiled apk? I will try and write a simple demonstration of this but I can't test it for a day or two currently as the Kindle was a loaner, and one of my kids has broken the charging wire for the Tab 2. I'm waiting on Amazon delivering me a new one.
Thanks in advance
=PRoF=