That's pretty much sums up the question. I have an AIR Mobile Flex App project in FlashDevelop that is using views to show content. Everything works fine, I can add a TextInput or TextArea to the stage, select it (Soft Keyboard shows up then), type some text. But when I press enter or change focus to the other element to hide the keyboard, the screen turns completely white except for the text that has been entered in the field.
Now it becomes interesting. If I rotate my tablet to force the screen to adjust, the content becomes again visible. Sometimes it doesn't even show a white screen, but rather a pitch black one that shows a blank preview when looking at the list of the running apps.
I cannot grasp the logic besides this behavior. It seems that somehow screen just doesn't want to redraw.
UPD:
AIR verison: 3.1
Tested on HYUNDAI SmartPad H-SP701G, Android 4.0.4
UPD2:
Tested on SANSUI ETAB 801VP, still getting the same effect.
The problem is in your application configuration XML.
Check your tag.
Entering value of "auto" or "cpu" should fix the problem.
<renderMode>auto</renderMode>
In my case I set direct and this was the cause of the issue. Using direct render mode caused the application to not work on HTC Evo 3D and Samsung galaxy s3. It did work on HTC Desire though.
Related
I am running an app built in Flutter on Pax A920 device with Android 7.1.2 installed.
Whenever the keyboard appears, the screen jumps down, and shows parts of the current view above the screen. When I dismiss the keyboard, everything goes back to normal.
This behaviour can be seen in the photo below. Sorry for the image quality, I cannot take screenshots on this device.
Photo of the unexpected behaviour
I cannot really show any code examples since this happens every time the keyboard appears, from different screens with different navigation stacks.
This works fine on iOS devices and on the Android emulators I have tried, so clearly this has something to do with the device/OS I'm running this on.
Has anyone experienced this or something similar and has an idea of how to prevent this?
Hey guys I am trying to trouble shoot an issue that seems to be only happening on certain Android devices that are version 5 or older.
What happens is, when I touch an input field say email-address or password to login, the page refreshes which makes it impossible to ever enter any information.
This is not just limited to those fields, but any form fields in the application. We have a leave feedback page and that form field also refreshes the page.
I had assumed I was having the same issue as Disabling android's chrome pull-down-to-refresh feature
But none of those solutions seem to be working for me and I just can't figure out what exactly is happening.
The information on my Android device:
Samsung Galaxy Tab A
Version 5.0.2
Is happening on Firefox, and Chrome on the device.
I am a little new to debugging on Android and could not find the version of touch my device is using.
We are using Jquery mobile for the front-end and some bootstrap javascript/css for forms.
So what I found out, was that whenever the screen resizes we do a refresh event for the new screen size.
What was happening on Android is that we had a css property `
orientation: landscape
on landscape mode. Well what was happening is you would click the form field on Android the keyboard fires and resizes the screen. Which was triggering a refresh, which took the keyboard away and sized the screen back to the regular screen with no keyboard event.
How we fixed this was using:
min-aspect-ratio: 13/9
This however was not happening on iOS because as far as I can tell, iOS just triggers a scroll-bar event instead of a screen resize event when the keyboard opens.
I initially started making an application on a Samsung Tab 3, and recently changed to a Samsung Active tablet. Since making the change, I noticed that the numeric keyboard is detached from the bottom of the screen, and is movable. I really want the numeric keyboard to be locked to the bottom of the screen, just like the regular keyboard.
Does anyone know how to fix this?
Note: I'm running version 4.4.4
I have a form-based app where each form is a scrollable layout of various types of view (RadioButton, Spinner, EditText views, etc). I have tested the app on a Galaxy Nexus with Android 4 and an Advent Vega with Android 4 and there are no issues with focus. I can scroll through the form without any problems.
However, when I test on the target device (a Android 3.2 Orange Tahiti which is a rebranded Huawei MediaPad), suddenly the focus behaviour is very different. It's difficult to know exactly what the tablet is trying to do. If I hide the soft keyboard and scroll, the tablet tries to focus on EditText views as they come into view and pops up the keyboard every time it successfully focuses which is very annoying. Also, on occasion the tablet will randomly jump to the last EditText in the form, scrolling the user away from their position in the form.
I have tried various focus settings (requestFocus, clearFocus(), descendantFocusability, etc) to no avail. However, I doubt the problem has anything to do with config as it works fine on other devices.
Is it possible that the focus behaviour in Honeycomb is different to all other versions of Android? I doubt it but it's worth finding out for sure before resorting to installing a custom ROM just in case I have overlooked a Honeycomb-specific config setting that might fix the problem.
Seems as this is a problem (or included "feature") of the branded version of Honeycomb that comes with an Orange Tahiti.
Upgrading to ICS will sort it out and scrolling, etc will behave as you would expect. Follow the below link for instructions...
http://forum.xda-developers.com/showthread.php?t=1544855
I have this browser launching application which didn't have any problem till now: when it is being tested on Samsung Galaxy 10.1 (Model Number: GT-P7510) with Android 3.1 Honeycomb.
The issue is this: whenever I tap on a text box, the whole screen will flash across a black screen for a moment and revert back to normal. It starts flickering/blinking the black screen when I leave a focus on any text box as well.
Currently, I've no idea what is causing this issue as I've tested this application on several devices e.g. Samsung Galaxy S, Samsung Galaxy Tab 7-inch with previous version of OS from 2.1 to 2.3.
Anyone who has any clue as to what is going on whether be it a compatibility issue with the app or a change in function in honeycomb 3.1 or the device itself, please share your information and enlighten me on this matter please. Any kind of help is greatly appreciated!
Thanks
I'm sorry that this is not a solution, but I think I can shed some light on the problem.
We have recently been testing a functional jQuery Mobile HTML5 app wrapped with PhoneGap Android 2.x phones to the Galaxy tab 10.1. We have seen something very similar, with the exception that we have defined a splash screen for our app. What we see is that when an input field is given focus, the screen flashes up the splash screen momentarily. Very annoying! To verify if this is the same problem, define a splash screen for your PhoneGap app and see if the screen flahes your image instead of a black background. Knowing something about what's going on with PhoneGap and the Android WebView, this is my best estimation of what is happening: PhoneGap loads the main App activity with a black background and displays the splash screen (if defined) in that initial window. PhoneGap then starts the WebView and opens it on top of the main Window. When a field is selected, the Android invalidates the component wach time it updates it based on a focus event or keypress, or whatever, and Android redraws everything. So it redraws the main window behind the WebView and then redraws the WebView with the HTML page content on top of it. Since the device is not properly double-buffered, you see all of this redrawing in all its ugly glory right in front of your eyes.
We have seen serious glitches with Android web forms on some Android 2.x phones we have tested, and this looks like yet another glitch, but this time on the Galaxy Tab running Honeycomb (3.0).
We have attempted to use CSS -webkit-backface-visibility to resolve issues on some phones when experiencing flicker in the past - but this has caused serious rendering issues in HTML forms. Be warned! In theory this should be a viable fix to introduce some double-buffering into the mix, but in our experience it causes more problems than it solves.
I am not confident that this can be resolved, except by an Android software update from Google/Samsung.