Been testing out the latest version and I've got a few updates and new reports:
1) The KQ3 Redux issue I reported in my previous post above (about the baseline issues and z-order messing up) are not actually due to this at all. Sorry! The actual problem -- and you're aware of this already -- is that I was running the game with the "Hardware" renderer and when opening the closet/drawer in the wizard's bedroom, an ambient tint is set to make the game background look a bit darker. The "Hardware" and "Hardware (Pixel Perfect)" settings cannot handle tints, which is why it was making the screen black with non-transparent rectangles where room objects were. The "Software" renderer works fine, though.
2) When running Al Emmo I get this crash on startup, which has only started happening since AGS_2013-01-17_19-21-51.apk:
in "GlobalScript.asc", line 263
Error: FileWriteInt: invalid file handle; file not previously opened or has been closed.
The FileWriteInt line in question is in the game_start() function.
3) An odd glitch that I noticed. I have "use custom preferences" checked for KQ3. For some reason, when I turn the phone sideways, the "use custom preferences" box suddenly shows as unchecked and all the other options revert to the 'default' state. If I then turn the phone upright again, all the checkboxes reappear. I can keep turning the phone sideways and upright and the options keep changing back and forth.
The opposite happens for another game which does not have "use custom preferences" checked. If I turn the phone sideways, then all the buttons do become checked and vice versa.
In the general/Global Preferences, I do have custom settings and checkboxes ticked. So maybe the individual game settings are getting confused and displaying those when turned sideways and upright?
Also, I can confirm that the "not being able to access the keyboard" issue persists with the Kindle Fire and Samsung Galaxy tablet. But the reason why seems different on both:
Samsung Galaxy tablet:Some of these tablets don't actually have a physical "menu" or "back" button. Instead, they display virtual "menu" and "back" buttons that sit on a persistently-visible toolbar at the bottom/top of the screen while the game (or any other app) runs. In this case, the "menu" button is visible when you run the AGS app (i.e. where you can can see the games list), but it instantly disappears from the toolbar as soon as you actually run a game. The "back" button remains visible the entire time, however.
Kindle Fire:Below is a shot of KQ1 running on the Kindle Fire:

Note that the only "button" visible is a virtual upward pointing arrow,located on a toolbar beneath the game window. Tapping this upward arrow button makes the virtual "back" and "menu" buttons appear on the toolbar. Tapping the "menu" button makes the "Keys" and "Exit Game" options appear, as expected. But long-pressing it doesn't make the on-screen keyboard appear. Likewise, tapping the "back" button acts like hitting the ESC key, but long-pressing it doesn't make the "Exit Game" prompt appear.