I'm trying to use Geocoder.getFromLocationName() and although the same search string works fine on these actual devices:
Nexus 1 (2.3.6)
Samsung Galaxy SIII (4.0.4)
Galaxy Nexus (4.1.1)
on my Nexus 7 (4.1.1), the method throws a "Service not available" IOException
Here is the simplified code:
Geocoder geocoder = new Geocoder(mContext);
List<Address> addressFromSearch = geocoder.getFromLocationName("10918", 1);
I've also tried each device using mobile data and wifi-only and they all work fine. So far the only device/OS that does not work is the Nexus 7. I've also checked Geocoder.isPresent() -- and it returns true.
Any thoughts on what I may be missing?
After the OTA-Update for Galaxy Nexus to 4.1.2 this problem is solved finally. It was a bug regarding the Android version 4.1.1
I also get this issue on samsung galaxy tab 2 android 4.0.4, I'm going to see if theres an update but definitely I'm up voting the issue.
Looks like there is a work around for my device!
If you reboot your machine on the samsung galaxy tab 2...it actually starts working!...thats what I call a work around!
Related
Most of the time I use UTF-8 on Android but I'm recently testing wchar_t too.
I know wchar_t was horrible in the early days, but I don't care about too old devices so thought it would be fine to work with wchar_t now.
Tested on:
Physical devices: Samsung Galaxy Note2 (4.4.2), Galaxy S7 Edge (7.0)
Software emulators: HTC One (4.3), Samsung Galaxy S6 (5.0, 6.0), S8 (7.0), Google Pixel C (7.1.0)
In my simple tests, wcslen(), wcscpy(), wcscat() worked as expected,
but swprintf() did nothing on HTC One (4.3) and Note2(4.4.2).
I couldn't test all the devices out there, but my conclusion is that swprintf() just doesn't work on Android Kitkat and below. It may just return doing nothing.
Could someone confirm my theory, please? Is there any workaround for this?
Whether practical or not, I just want to know.
Don't ask me why, but until L Android only had a stub implementation of vswprintf that just returns -1.
https://android.googlesource.com/platform/bionic/+/kitkat-release/libc/bionic/wchar.cpp#74
The workaround would be to use libandroid_support. This is automatic if you're using libc++ (and that's the best option for NDK r16+).
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)
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
The Camera on my galaxy s2(Android 4.4.2) looks like this when i run the color blob sample code. The same code works on my galaxy tab 2 (also Android 4.4.2).
Tried with writing the code from scratch and other sample codes. There are no errors on both devices, but the image looks like this on the S2
Does anybody know how to fix this?
I have the exact same result running OpenCV Samples on my S2 i9100 with Neatrom 3.6 (4.4.2) and ART enabled. Changing ART back to Dalvik does not change anything (for what it`s worth).
Using Stock Samsung Rom fixes the problem. Seems to be something in the Custom Rom which causes the problem.
After some testing this seems to be the only working Rom for me.
I checked without success the following Roms:
CyanogenMod 10.1
CyanogenMod 10.2
CyanogenMod 11
SlimSaber 4.4.2
Biftor™SlimKat-Rom-V6.0-i9100-4.4.2
I9100_4.4.2_AOSP_NeatROM_v3.6
SlimBean 4.2.2
I am beginner of Android Developer.I just published a app on google and I get some of feedback which is screen keep on blinking in Samsung Galaxy S2. But I tested it with Nexus4 and Samsung galaxy S3 with no such problem at all. and also tested it with simulator Android 2.3.3(API 10)also No problem with it.
Since I do not own a Galaxy S2 device, do you guys have any idea which part I should look for in order to find out the problem? because I really no idea, Please help and give advice. thanks.
the app implemented some of external library which is:
(jfeinstein10) - SlidingMenu and (chrisbanes) -Android-PullToRefresh