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+).
Related
We are developing a motorbikes racing game under Unity 5.3.4p4 for Android.
I have a spotlight attached to a gameobject (the motorbike), the farther it is from the center of the world (0, 0) the more unstable/shaking it becomes when moving. I've tested on many devices with different GPU and Android versions but this only happens in Samsung Galaxy Edge S6 and S7 devices (MALI GPU).
Does anyone has the same problem or know any solution for this?.
Thanks for your time.
EDIT:
After a lot of testing there seems to work fine only using Deferred instead of Forward rendering and enabling OpenGLES3, at least for the S7, the S6 has the same problem no matter what I do.
I've also tried downgrading to Unity 5.2.5 and upgrading to unity 5.3.5 without success.
As #Paul-Jan says, it seems it also affects iOS: https://community.unity.com/t5/Graphics/Problems-with-spotlight-on-mobile-precision-issue/td-p/2473711
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.
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
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?
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!