We have an native Android application developed in Java and Android Studio.
We started observing a phenomenon which seems to be related with rendering (but might not?).
In the photo bellow the table is rendered correctly:
When ticking one of the checkboxes to select a row, the fields show only the first letter:
Setting focus to one of the textboxes, or turning the tablet (horizontal / vertical) temporarily fixes the issue, and the table is rendered correctly.
It doesn't matter at which point you click the checkboxes, the problem shows again.
We ran the app on different devices:
Samsung S4 mini, Android 4.4.2 (not showing error)
Lenovo Tablet, Android 4.4.2 (not showing error)
Samsung S4, Android 4.2.2 (showing the error)
Winmate tablet, Android 4.2.2 (showing the error)
What can this be?
Any advice on how to solve this?
Thanks in advance,
Shy.
I was having the same issue. I discover that RowLayout has this bug on some Android versions (I saw this bug on Android 4.2 version but not on 4.4 versions). Try changing RowLayout for LinearLayout, that'll do the trick.
Related
I am a newbie of Android programming, and I am using the latest version of Android Studio on a Mac.
My problem is with the emulator, in particular, the tablet emulators (Pixel C, Nexus 9, and 10) which is giving me a hard time understanding why any click I do on the emulator display is displaced up (on the y axis) a great number of pixels. For example, if I click the Chrome icon present on the home screen, in reality, the emulator is taking the click about 100-150 pixels up that location! Why's that?
I have no problems with all phone emulators. This issue appears only with tablets. Any ideas?
Thanks in advance for any possible solutions to this problem.
All the best,
Fab.
Ok, I solved this problem by unchecking the option Launch in a tool window" inside Preferences > Tools > Emulator.
It appears that making the emulator run inside a window is buggy and gives this click-location issue.
I have two devices in my GenyMotion application. One is nexus 7 4.2.2 API. The other is a saumsung galaxy s4 4.3 API. The nexus emulator starts up fine and works well. However when I tried starting the s4 emulator, the android loading screen doesn't even show up, all i get is a black screen. When I go to DDMS, the devices tab tells me that the samsung galaxy s4 is online and debuggable. Does anyone know how to fix this issue? It make more sense if both show a black screen but why does one show a black screen and the other doesn't. I don't see anything out of the ordinary in the console.
I just tested this, and notice the blank screen is due to Genymotion version mismatch. Once i downloaded the latest genymotion (v2.3.0) , i was able to see Galaxy S4 startup properly.
If you do not see the navigation bar, you can manually enable it in Configure virtual device, see below.
this worked for me : In Configure Virtual Device (as shown in ashoke's answer) I changed Screen size to one of predefineds resolutions.
I currently work on an Android application with two developpement phones :
1 SGS GT I-9000 with Android 2.3 at first, then Cyanogen 10.1.3 with Android 4.2
1 SGS III GT I-9300 with Android 4.0.4
My problem is that when my application triggers an unhandled exception while testing my code, the behavior is radically different on the two handsets : The old Galaxy S displays a force close popup (either on Android 2.3 or 4.2), but the Galaxy S III completly crashes and I have to reboot it each time.
Is there a parameter that i have missed ?
Edit : I also tried to run the app on AVD with a deliberate NullPointerException. It is correctly trapped.
I finally managed to get rid of this problem : I downloaded a new ROM for SGS III and flashed the phone with ODIN 3.09. Exceptions don't crash the handset anymore and the force close popup is correctly displayed.
(For those who wonder why i didn't simply update the current ROM, the response is : I tried, but it changed nothing)
I'm currently developing an application that was originally meant to be run solely on Nexus 7 and Android 4.2. However, there was a change of plans and now it is meant to run on the Galaxy Tab 2, Android 4.1.1 instead.
I am using a custom font that rendered great on the Nexus 7. However, when downgrading the version of Android and switching to the Galaxy Tab 2, the font kerning got completely messed up and looks terrible. Spacing is way off from what it should be.
Any tips to point me in the right direction for fixing this issue? I don't have the slightest idea how to fix this, except for switching to a different font, which is less than ideal.
Sounds like you may have run across the kerning problem described here: Android Custom View code stopped working correctly in Jelly Bean 4.2
It is possible to work around it.
I've received several reports from users that large parts of UI in my application just went invisible on their Galaxy Nexus with Android 4.1 and they are still clickable. I'm not able to reproduce it on any Android 4.1 emulator.
So the question is, what did Google mess up this time? Is it a known bug?
I ran into this myself. My problem was in using layerType="software" in some layouts. Getting rid of that fixed it.