![]() Private var screenheight: int = Math.min(Capabilities.screenResolutionX, Capabilities.screenResolutionY) ![]() Private var screenwidth: int = Math.max(Capabilities.screenResolutionX, Capabilities.screenResolutionY) The final work around code is like this (the timer is used because at first the orientation may return "unknown"): If it was, I do the Kindle Fire work arounds. I use a variable that tells me that the app was bought n the Amazon Appstore for that. No other Android device has these issues, so you have to tell whether you should be attempting the work around at all. One way to do that is to check the screen size. Which means finding a way to detect an old Kindle Fire versus a newer one. Now, because the original Kindle Fire has the opposite issue to the later ones, I have to work around its issues in the opposite way. So, after a lot of attempted fixes the only way I found to make it predictable was to turn off auto rotation and to also do a work around for the initial incorrectness. If you do a fix for that, the app will be correct, but if the user turns the device at all, the app becomes upside down, and remains that way until they force quit. If the user is holding it the other way up (by the way, I’m just describing landscape here), then on the original Kindle Fire it may work, but on the new ones it will be upside down. If the user holds the Kindle Fire the correct way up (either the USB connector is to the right if there is no camera, or the camera is at the top or left if there is a camera), everything works ok. Here’s a description of the general problem: There are various works arounds to the issue, but most of those have serious possible side effects. Also, the original Kindle Fire had the same issue, but for a different reason.
0 Comments
Leave a Reply. |