I don't know if this is the right place to ask for a solution.
I have a weird bug on Samsung S9 Android 8.0:
The area for the 3 Buttons (Menu, Home, Back) is blocked for some apps, so their UI ends on the top border of this area although I set these buttons to not fixed so that I have to swipe up to see them. One of these apps is Instagram.
Also, there is the problem that the outline of some UI is shining through the current UI of each app, no matter which app is currently running. This UI is always the same. I removed all UI elements from an app I'm working on so that I have a completely white screen. Then I made a video because on screenshots the UI fragments are not visible:
https://der-magere-student.com/public/media/WIN_20210115_02_29_04_Pro.mp4
On the bottom you can see:
In more or less black: the android menu buttons (BUT NOT THE REAL ONES, the real ones are hidden until I swipe up)
In more or less white: 4 of the five toolbar button of Instagram (home (house icon), the magnifying glass, the Plus (inside the android home button), and the heart) The fifth is not visible
On the top you can see:
The right side of the WhatsApp toolbar: From right to left. The more icon, the call icon, and the video call icon
horizontally centered with a bit offset from the top display border you maybe can see a little bar. I don't know where this comes from
There is a lot more but it's not visible on the video and also not identifiable for me. But I can see something.
Does anyone know where this bug comes from? Is it known? How to fix it?
You're looking at OLED screen burn-in. It's not a software problem; it's actually wear on the screen that happens slowly over time.
The UI you're seeing at the bottom of the screen is Android's navigation buttons, which are particularly notorious for getting burned into the screen (see, for instance, this image from this article), because they're always in about the same spot. Newer versions of Android take measures to reduce the burn-in from them, but there's only so much that it's possible to do.
Try opening something that shows a white screen with the navigation buttons hidden: you'll see the same thing.
Related
When titanium android app is running smooth. I didn’t find any crash or run time error. But the problem is when I minimise it and reopen it from background after some time(1 hr or 2 hr) its going white blank. Any help to fix this?
Check the logic in your application. Are you adding and removing UI elements on the screen after the background process runs? Sounds like you are looking at a window or view with a white background. I think if you don't assign a background, it comes up black.
Often find that when this happens to me, it is some view I didn't set a height and size for. It covers over or pushes down all the other UI elements so it appears blank when is reality the other UI elements are beyond the edge of the screen.
To troubleshoot, I often give my views and windows different colors to figure out exactly what view, or window, I'm looking at. Often it isn't the one I suspected or a view that is larger than I wanted it to be.
In the guides of how to put a correct banner from AdMob guidelines, they told that the best place to put it is aligned in the bottom of the screen. I am doing that in all my apps, allways.
I noticed that in Android 4.4 kitkat, the banner is extremely near of the screeen buttons of back, home and menu. I attach a image in the next lines.
Is this dangerous??? Can my account be banned for this?
Thanks
Image:
No I don't think it can be banned for something as minimal as this, but to be safe, you could add paddings at the bottom of the screen so that there is a little screen space before you touch the hardware buttons.
The things that could get you banned would be making an automatic click on the banner periodically to get CPM, that is very dangerous and unethical. If you are also uncomfortable with it being down the screen, you could put it on top to be safe. I hope I helped you
I'm trying to make a textField that accepts input. My problem is, that when a user taps a textField, the input field is maximized so that it covers half the background image (the keyboard covering the other half).
The picture below shows what the background image looks like before the user taps one of the five textFields (the grey bars).
The image below and to the left shows what currently happens when I tap a textField: the input field is enlarged and completely covers the background image. What I WANT to happen, however, is what I've tried to show below and to the right: the textField is focused and the user can start writing while the background is still visible.
The app works fine on my Samsung Galaxy tablet, but for some reason I have this issue on my Nexus 5 phone only. The phone has plenty of other apps where the example to the right is what happens, so I at least know that it's possible. How do you do it?
(Was unable to find a tag for the Nexus 5)
This is a common problem. See http://forums.coronalabs.com/topic/36320-keyboard-covers-my-textfield-when-placed-on-botton-of-the-screen/ for some ideas. Some devs create their own virtual kb, see eg https://developer.coronalabs.com/category/tags/keyboard for some libs to help with this.
This is the ExtractEditText UI; you just need to add a flag to disable it. On your EditText, set the attribute:
android:imeOptions="flagNoExtractUi"
So I'm testing out a site on my Nexus 4, the layout when you browse to the page on mobile looks like so:
It turns out on my phone, I can scroll or move the scroll bar down, by tapping the very edge of a screen. When I try to tap the right arrow, sometimes it will think that this is an attempt to scroll and move me down the page.
My question is, is this limited to the Nexus 4 device, Android or is it the Chrome Browser? I've tried it on both a HTC and even the Nexus 10 and it isn't possible so it seems to be localised to the Nexus 4 device. More importantly, is it possible to disable this?
Although the scrollbar is not always visible in Chrome for Android, it is always present (when the page extends past the end of the screen) and will intercept touches on the edge of the screen.
As you scroll vertically on the Nexus, look for a gray bar on the right side. It is hidden when you are not scrolling, but it is still there and will still receive touches. The color of the scroll bar can also make it hard to see on certain backgrounds (such as the gray I see in your screenshot).
When I'm not touching the screen:
When I'm scrolling:
There's problem with HTC Hero and AndEngine's BaseGameActivity: when launched, there's only white screen, without any graphics like background and sprites. But I can see objects like lines (org.anddev.andengine.entity.primitive.Line) etc. and also I can tap on invisible buttons and my code is performing, but it's still white screen.
When I'm launch this app on other devices everything is ok.
Where is the problem?
Seems like my TextureAtlases was too big for this phone and I have to use several smaller atlases.