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.
Related
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.
im developing an android app on android studio, when i run my app the layout looks a bit different from the preview as well as on other phones,
for example: the buttons are in different order (from right to left instead from left to right) or other changes similar to this.
as well as on some phones the layout doesn't fit perfectly on the screen for example: the buttons on the sides of the screen appear to be cut out.
how can i fix it so the app will look the same with every phone and not only some of them?
About the Right-to-left/ Left-to-right, you can choose the globe icon in the preview options bar frame and then choose Preview Right-to-Left Layout option. This will "fix" the buttons order in preview.
About the buttons that appear to be cut out - make sure you use dp units instead of pixels. You can read more about it here:
http://developer.android.com/guide/practices/screens_support.html
Make sure you check if you have used the constraints on your components properly. Usually that's what makes the layout messy after running the app on your phone/emulator, even tho it looks perfect on your XML file.
so I'm making a really simple app that just shows some buttons and images,
it looks great on the simulator (because I guess that's the resolution I've been working on ...)
but when I try to build it to my phone it looks differently (the buttons are more stretched out and there is allot more background space in between the buttons and the end of the screen,
I guess it's something that's suppose to be simple but how to I make my app "zoom stretch" to the phone content it's going to be on, meaning it will look the same on any phone and if necessary will stretch the image a bit to fit the screen ?
Thx
In your XML, its important to not use specific(dp,px,etc.) sizes for laying buttons/text boxes/etc. out. For example, for a button thats on the page, use a "layout_width" of "match_parent" and add padding (if necessary from there). This will allow your button to stretch properly without having that extra whitespace.
On android , is it possible to create a opaque filter that displays only half the screen ? Think of it like a half screen advertisement in black allowing you to see only half the screen and working on a service i.e in the background.
Any code for this would be helpful as i am a bit clueless.
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"