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.
Related
May be my question seems to be dumb as i'm new baby to this...
I'm trying to run an android application in 7 inch Samsung Galaxy tab(7 inch)...everything work fine but when i move on to Samsung Galaxy Tab S2(10 inch) i faced an alignment issue in my application...Getting crashed sometimes too.
Can anyone suggest what should i do to resolve it...Have to create separate layout files for 10 inch tablet????
Please also tell me how can i test my application in an Samsung Galaxy Tab S2 10 inch emulator.
I can really recommend using Genymotion as an Emulator. It' very fast, and only has some minor limitations as free version, like you might not be able to use Google APIs.
It also provides predefined settings for different Devices.
If you don't want to use a third Party Emu, you could of course use the Android Studio Emulator too.
For the crashes: get used to use the Debugger and to using Unit Tests.
I would also recommend switching from Eclipse to Android Studio, since Eclipse is no longer the supported IDE by Google. Migrating your project shouldn't be a hassle.
Without your Layout code people won't be able to help you on that part.
In my app, I'm facing a weird issue I can't explain. I can't even give you a logcat or something as I don't know where it is actually coming from, I can only describe the error:
My app Daily works well on some 5.0 and 5.1 devices, the HTC One Max for example. It does NOT work for Samsung and Sony devices running 5.1 and 5.0, maybe also at a 6.0 Samsung. The app just stays white for a few seconds and nothing happens then.
If you have any further questions about the app itself, you can just ask.
The app is using a MultiDexApplication and MultiDex itself if this might help.
Thanks.
My app runs with many devices but 2 users have send me simular images as below.
As far as I know the behaviour is only seen on Android 4.2.2 (Samsung S4).
On the full HD screen there seem to be 3 compressed tiles of 160x600 pixels.
I have tried an AVD with full HD screen but that fails to start.
On 4.03 devices I don't see this. I don't use tiles.
Does anybody have a hint what or where this goes wrong ?
This looks like a possible bug in the Android platform on Samsung's S4 devices with that particular Android version. My experience tells me that it's a very real possibility. It could also be that you do something wrong in your app that only causes actual problems on that version (and maybe even only on that device), but there is no indication of that from what you tell. Android 4.2.2 should be backwards compatible with 4.0.3, so in general it should work on the later version too, of course.
I would advice you (or anyone in the same situation) to try it out on other devices with the same Android version if possible. Also, double check that you're not violating anything in the Android API documentation.
Please add more info about what you're doing and how if you need more detailed answers. I guess you've probably found a solution or workaround by now, but still adding my answer here.
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 have recently completed development on a game for Android smartphones.
It was designed using the android 2.1 sdk and runs no problem on my test devices a 2.1 samsung galaxy europa and a 2.2 samsung galaxy tab and seems to run fine in the emulator for 2.3.3.
Up until recently it ran fine on my friends HTC desire S but suddenly it stopped working, crashing on start.
It would appear that the error is caused by a resource not being found.
This code has not been touched for the past 2 months and ran no problem on my 2.1 and 2.2 devices but I must have done something. It seems that suddenly that some phones can't see the resources but unfortunately I cannot replicate this bug and my friend is not around enough and is getting quite pissed at me for pestering him for me to take his phone and keep trying to fix it.
Any help would be much appreciated as this is driving me mad especially as I cannot replicate this bug with any of my equipment. I haven't even got a confirmation that it works on 2.3.3 as the people who have downloaded my app aren't leaving any useful feedback or submitting many error reports. Hopefully it is just a bug with HTC's variant of android.
I sometimes have errors like this when I'm rapidly iterating (tweak/test) on the emulator. They're usually solved by doing an "ant clean" and then recompiling. You could try cleaning and then doing a fresh build, installing it on your friends device, and then seeing if you still get the error.
-Kurtis
Have you considered/researched whether or not this actually is a resource problem...meaning does this resource actually exist in the folder Android is trying to draw from?
I'm currently facing the crash in a production application and have found the problem. This crash is only happening on HTC devices. Seems like HTC changed the core Android method that decode a Resource.
The documentation of BitmapFactory.decodeResource says :
Returns
The decoded bitmap, or null if the image could not be decode.
But HTC version of that crashes :(
In my case, I had mis-placed the "xml" folder. It was on the root of the project, but just moved within "/res" folder and the error was gone.