Although the documentation says that this bug is fixed (see: Add the navigation flag), I am experiencing the same problem.
From my application I want to add new Android contact, and after the saving is completed I want to get back to my application (the activity that called the insert new android contact intent). That's why I am using:
i.putExtra("finishActivityOnSaveCompleted", true);
Adding this line, I get the expected behaviour on some phones, and others just behave differently (the user is not navigated back to my application).
I have experienced this problems on Sony Xperia Z, Sony Xperia Z2 and LG G2 mini, all running on 4.4.2, and also LG G3 and Sony Z2 running Lollipop.
Does someone know what is the problem here, and if something has changed.
The saving works properly on for example HTC M8 with 4.4.3 and Samsung Galaxy Note 3 with Lollipop.
Nevertheless, if someone knows a solution, please please share. Thx
Related
I have a problem on galaxy s8 and galaxy s9 with dynamic links from firebase. On other android devices it works. A strange loading screen appears, then returns to the application from which there was an attempt to open the application. Anyone had a similar problem or potentially knows a solution? The application is not installed. Certificate SHA-1 is attached. https://drive.google.com/open?id=15BTDWjFgMtijZ7RVILN7DUq-fG0BzlE7
on the next day the links started to work correctly ... it looked like a problem with permissions on devices
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 an activity which handles any URL events within my application and it opens them within a web view. The issue which I currently have is that if i turn off the WiFi and turn it back on the URLs which were previously working before in the webview do not load and it eventually timeouts. The puzzling thing is that I have tried this within the same application across other phones (HTC, Samsung S5, LG Nexus 5, Samsung S4, One Plus One) and it works perfectly.
I am wondering if anyone has a solution for this or at least an explanation as to why this is happening.
The reason I'm asking this is on here is because although it seems to be a device specific issue, before to get another issue with my webview to work with samsungs i had to enable webView.getSettings().setCacheMode(WebSettings.LOAD_NO_CACHE);
I want to know if there would be something similar to help me with this S6 issue.
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)
WallpaperEngine.onOffsetsChanged not being called using a HTC Sensation, but it is ok with my other two devices (Nexus 7, and a Nexus S).
I understand that this issue is related to the HTC Sense 3 carousel.
I have downloaded a number of Live wallpapers to test them out on the device and quite a lot of them don't pan between home screens.. But some do, so there MUST be a workaround for this bug/restriction.
Anyone know what it is?