I am making a div invisible by setting div.style.visibility="hidden"; which perfectly works in samsung, sony phones. Also perfectly works for desktop browsers, chrome mozilla. (And it should be.. )
But sometimes, it is not working in google nexus 4 (android 4.3). Tested in multiple nexus 4 device.
observations :
I have multiple dialogs, which navigates between one another. In this process, I hide the previous dialog and make the next dialog visible. This works perfectly fine until I open a heavy dialog, which has 100 divs with multiple images. Now, when I try to go back to a previous dialog, div visibility and opacity stop working. All dialogs remain visible in the background. style.opacity = 0 also doesn't work. visibility and opacity works perfectly fine, doesn't matter how many time I switch between dialogs, until I create that heavy dialog.
when a div is visible in the background, which should not be visible at all, and I lock and unlock the phone, this problem gets resolved. Everything starts working smoothly. Also, if I wait for sometime, everything falls back in place. Starts working perfectly again.
Tried couple of things :
1. webView.setLayerType(View.LAYER_TYPE_SOFTWARE/HARDWARE, null);
2. webSettings.setRenderPriority(RenderPriority.HIGH/LOW);
I will make that div small (with less inner divs) and try again tomorrow.
I will test in nexus 7 tab and other devices if possible.
I will test in nexus web browser.
For the time being, if anyone has any suggestion, please let me know
Related
I'm new to Android development and my first application is looking good.
Curious if anyone has ran into problems with admob:
I have a ListFragment that displays a list with ads at the top and bottom of the list. The display is fine and everything runs ok except -
when I click on the ads and after the browser loads up, clicking back does nothing except for "going" back on the browser and it doesn't go back to the app.
Strangely enough this is happening on my Samsung s3 device but not on my HTC device.
This is because Samsung uses their own custom browser (not stock), and its deciding what to do with the back button. I don't think there's anything you can do- their browser has the focus, it gets to decide what to do with all IO. Your app is in the background and doesn't have any say over IO response.
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 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.