LGB_Flyer wrote:
I am on the 30-day trial, coming over from another Android app and giving this one a try. The first thing i noticed while chair-flying is that the app is fairly intuitive, and I like the configurable instrument overlays. Unfortunately, I also noticed that the map orientation is dependent on how I am holding the table when I start the app. For example, if I start in portrait mode and hold it that way, it is fine. But if I rotate the tablet (Samsung Galaxy Tab A) to landscape, things get bad. The orientation of the screen changes, but the map is shown with large black bars on either side of the display. The app retains the same aspect ratio as the portrait mode. Additionally, if I touch the screen while it is doing this, it is apparently mapping to what should be displayed there, not the actual display.
This behavior would be fine since I always want to use the tablet in portrait mode and I dont plan on switching the display one the app is launched, except that I cannot lock the screen rotation. Selecting the toggle to disable auto-rotate in the display settings menu within the iFly app does not have any noticeable effect, the behavior is the same whether it is selected or not. Additionally, disabling auto-rotation from the tablet settings does not have any effect while the iFly app is on top. When the app is not running, the tablet appropriately respects the disabling of the auto-rotate function, but when the app is running the behavior describe above happens. Sine I keep the tablet on my kneeboard, it is prone to shifting around, and it is necessary that I lock the display to portrait mode so that it is not arbitrarily rotating.
Am I missing something, or is this a bug?
Thanks
YOU FOUND A NEW BUG! Thanks for posting. I just now confirmed that on previous versions of Android, it works, but on my new Android 8.0 tablet, this bug exists!
I consider this a critical bug, but I wasn't aware of it until this morning. Cobra and Tim are correct in how it is supposed to work. I may be releasing a patch to fix this ASAP, as this is a critical bug for Android 8 on a kneeboard -- as you have pointed out.
I'm not sure why Android changed the API for us on how rotation is to work, but they did.