i have to do an update release in my app,
i've changed a control in an internal activity.
Now during the testing, i 'have noted that the app has a problem showing icons on main page, but only in a Samsung Galaxy Nexus device.
I have checked all the code, i've made test with other device with same resolution (xhdpi) and in all other devices work fine, only in the Galaxy Nexus show the icon (not all, 8 on 9) too large.
here's a screenshot:
Any suggestion to understand this problem and solve it?
many thanks
I've Found the problem!
I'ts a bug of android, i've set the targetSdkVersion to 19, like the suggestion of eclipse, and i was them that give the error.
Now i set the targetSdkVersion to 17 and all work fine!
Related
We have received issues from Customers who are seeing Black screen on Samsung Note 5, Samsung Galaxy s7 after they updated their device to Marshmallow. My application target SDK is 19. Basically the user are able to see the Launcher Activity A, but when they click on other activity B they see a Black screen. Activity A--> singletask and Activity B has default launch mode.
We have tested this application on other Vendors Marshmallow( Motorola, Nexus) devices and it seems to be working well. We have also seen some customer using our application on Samsung Galaxy s7 Edge(Marshmallow) too. We had one of the customer facing the same issue on Marshmallow Note 5, but he resolved that issue after Backing up the data from old Samsung J7 device, in which our application was running well. I am not sure, how backing up the data resolve this issue. Is there any device setting which is turned on or any thing which may be causing this issue. We do not have the Samsung Devices with Marshmallow and could not reproduce this issue.
Any advice appreciated, and let me know what could have caused this issue. Thanks in advance.
We received ANR Logs from the users on Playstore and we found out the issue was due to the Spannable String which we had used. The issue seems to be on only Samsung Marshmallow (6.0) Devices. This issue has been fixed in Marshmallow 6.0.1. Really don't understand, why Android is customized to such extent by Samsung. As our application is running well on Motorola Marshmallow 6.0. Here is the entire Logs from Samsung Marshmallow. Hope this might help some one who is facing similar issue.
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1477)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1468)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1473)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1468)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1468)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1468)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1473)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1473)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1473)
... repeated 3 times
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1468)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1468)
at android.text.SpannableStringBuilder.calcMax(SpannableStringBuilder.java:1468)
at android.text.SpannableStringBuilder.restoreInvariants(SpannableStringBuilder.java:1510)
at android.text.SpannableStringBuilder.setSpan(SpannableStringBuilder.java:762)
at android.text.SpannableStringBuilder.setSpan(SpannableStringBuilder.java:662)
Additional Logs on other Samsung Galaxy Edge Marshmallow 6.0 devices related to Spannable Text View
at android.text.SpannableStringBuilder.countSpans(SpannableStringBuilder.java:857)
at android.text.SpannableStringBuilder.countSpans(SpannableStringBuilder.java:864)
at android.text.SpannableStringBuilder.countSpans(SpannableStringBuilder.java:844)
at android.text.SpannableStringBuilder.countSpans(SpannableStringBuilder.java:864)
at android.text.SpannableStringBuilder.countSpans(SpannableStringBuilder.java:864)
at android.text.SpannableStringBuilder.countSpans(SpannableStringBuilder.java:864)
... repeated 7 times
at android.text.SpannableStringBuilder.countSpans(SpannableStringBuilder.java:844)
at android.text.SpannableStringBuilder.countSpans(SpannableStringBuilder.java:864)
at android.text.SpannableStringBuilder.countSpans(SpannableStringBuilder.java:844)
at android.text.SpannableStringBuilder.getSpans(SpannableStringBuilder.java:823)
at android.text.SpannableStringBuilder.sendSpanAdded(SpannableStringBuilder.java:1053)
at android.text.SpannableStringBuilder.setSpan(SpannableStringBuilder.java:763)
at android.text.SpannableStringBuilder.setSpan(SpannableStringBuilder.java:662)
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.
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.
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.
Recently I developed a launcher app for a Samsung tab 2 running android 4.0.3. During development/debugging everything was running fine. But when I created a release/signed apk we started experiencing problems with font rendering and the system home button not behaving properly.
Tested it again on the same tablet upgraded to 4.0.4 and everything was fine again.. can anyone tell me why?
I believe that the Galaxy Tab 2 reported its pixel density as 170dpi and screen bucket of hdpi in 4.0.3 . This was fixed in 4.0.4 to report as mdpi. I know this personally as I work on a comic reader application as was a pain in the ass to compensate for.
This answer has way more definitive information.
I hope this helps you Erik.