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
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?
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.
I'm involved in developing a webapp aimed at iOS 5 and Android >=2.2
using Phonegap (Cordova 1.6.0). During testing I got back results from
one of the testers running ICS on his Samsung Galaxy S2, saying that a
menu in the app was not working. Digging in to it i realize that, even
if it visually stays in place (fixed position bottom-menu), the actual
clickable areas of the buttons in questions follow the scroll. So if
you scroll the page "half a button-height" up, only the upper half of
the buttons in the menu at the bottom is clickable.
This error only appears using touch-events (works fine when using for
example the click-event) and in a webview, not in the native browser.
It also appears as this problem does not exist in the "vanilla" ICS
that the Nexus runs.
Any ideas what might be causing this?
I have a very simple Android app. It is one Activity with Text and Buttons, and as you click on the buttons (onTouch events), they become invisible and the text changes.
This works fine for Android 3 and Android 2.3.3 simulators, but when I use the BlackBerry nature in Eclipse to send the app to a BlackBerry playbook simulator, funny things happen. As I click on the buttons they go invisible, but other buttons change too.
Buttons that were only ever visible, stay visible. Some Buttons that were invisible, become visible. Some buttons that had become visible earlier, return to being invisible.
It feels like a redraw problem, or some strange caching on the button state.
Anybody got any ideas? Wild guess excepted ...
Get a playbook or wait until RIM updates their broken simulator.
I converted an app for the playbook and the code was running fine on the simulator. It's a very simple app too, like a binary calculator. A couple of toggleButtons, Buttons and a TextView.
The app had visual issues, similar to yours. Buttons disappeared. Buttons were highlighted when I pressed buttons around them. ToggleButtons didn't change state. And much much more.
Since I don't have a playbook I couldn't test it on a real device. I tried layout changes, code changes and tried different settings. But nothing helped, those issues stayed.
After some reading in their forum I came to the conclusion that this might be an issue with the simulator.
So I submitted the app to the AppWorld 5 days ago. It got approved today.
So there is a chance that your app is alright, and the problem is the simulator.
I just took a look on different devices and their soft keyboards. They are all looking a bit different. I attach two screenshots. One is from my HTC Desire (Android 2.2), another one from Emulator (Android 2.3).
As you can see on the device the enter key is on device just a symbol, on emulator it is "send".
Can I change it somehow?
I had this problem a year ago, my problem was that the numeric keypad is very different from each provider (not only on style but on the buttons that are shown)
In my personal experience is a pain to try to change that, you would need to create your own SoftKeyboard class with your own images.
If it's not an important issue I recommend to just pass over it, or find a keyboard type that satisfies your needs.
However, I don't know if in the newest versions of Android you get an easier way to customize keyboards.
Good luck on there :)