I noticed a strange issue with my app on a Galaxy S4 LTE updated to Android 4.4.2.
If i go back to the launcher with the home button and try to reopen my application from the launcher menu, it restarts from the main activity instead of resuming from where it was send on background. Issue isn't present if I go back on my app from the task manager.
The issue isn't present on my Nexus devices (7 2012 with some months old CM11 build and 5 with last Cyanogenmod rom) and another Samsung Device (Galaxy Ace 2 I8160 running 4.1.2) I tested my app on.
Other apps behaviour are correct on the Galaxy S4 (IE: Facebook resumes correctly) so I think I'm missing some flags on my AndroidManifest.xml. Any help?
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)
I have a problem running my app on a device.
Not on all devices!
On many devices(Lenovo android 4.2.2, Lenovo 4.4, Nexus 4 android 4.4 and more) it's running perfectly!
Unfortunately on some devices, such Samsung with android 4.4(upgrade to 5.0), Wiko android 4.4.4 app crashes without any message.
When I click on the app icon, the app opens then it shows a white screen for less than 1 second before the app closes.
I've made a apk file like this: In Android Studio I press "run" triangle, after it finished building I copy apk from "appname\app\build\outputs\apk". app-debug.apk
Does anyone have the same problem ?
Thanks for any helpful information !
Important:
The device is for 2,500 kilometers from me
UPD:
I try to launch "empty" app and it works!
I'm asking this because it's only happening in nexus 7 device. I had an Asus nexus 7 2013 .
Issue is when my app goes into background [clicking home button] i go back to main menu and click my app icon. It simply Restarts from Splash Screen and no other app is open in background, RAM is 1.3 GB free.
This should be happening if system is running on low memory and kills my app while in background.
I had tested my apk in other tablets it's working fine as it should work.
But Specifically in Nexus 7 it is showing rouge behavior.
Android version is 4.4.3
Is this a generic Bug or just Specific case.
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 put together my first Mono for Android project (targeting API level 8, minimum Android 2.2) and deployed it to an HTC Incredible [1] running 2.3.4. Everything worked great and breakpoints in my main activities OnCreate, OnStart, OnResume, OnPause, and OnStop all triggered as described on Xamarin's Activity Lifecycle tutorial.
Without changing any project settings, I swapped for a Samsung Galaxy Nexus running 4.0.2 and deployed the same app. It called OnCreate just fine, but never triggered any of the other events when I switched away from the app.
How do I get these activity events to trigger in Ice Cream Sandwich (ICS) on the Galaxy Nexus?
While running the first deployment on a Galaxy Nexus, you will see it deploying the "armeabi-v7a - 40202" assemblies. For some reason that stuck in my head when this issue started making things difficult.
If you go to the project properties and check the box for "armeabi-v7a" under "Supported architectures", these events will start being triggered as expected.