card.io SDK for android integrated in my app works on different devices but on Galaxy S5 it does not come to "snap" after focusing around the camera. I know S5 has quite a different CPU and GPU and some different camera properties. Anyone having the same experience?
Solved thanks to comment from tomwhipple above: just adding "android:hardwareAccelerated="false"" does the trick.
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
I'm using the barcode-reader project in two Samsung devices (SM-N9005 or SM-G920F) and they are not capable of recognize any barcode. There are no problems in others like One plus one, or others Samsung devices like S3 or S4.
There is not a problem of the autofocus, because it is working fine, the barcode is focus properly.
With this devices, the camera opens but nothing happens.
HELP please.
Have you take a look a this already ?
It looks like freed some space is also effective, have you enough space on this devices (more than 10% of the total space) ?
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
I am facing a weird issue, which is already driving me crazy, so ANY help is most welcome and appreciated.
I have created an Android application, which is working quite fine on all kinds of phones and tablets, but on some Galaxy S3 devices, the images are not loaded at all.
Here are the facts, both from myself and information that I gathered from the complaining users of the app:
all images are packaged in the application, in the drawable folder, so accessible from all resolutions
the images are referenced either by mypackage.R.drawable.image_id, or directly via #drawable/image_id in the XML
the images are semi-transparent and are stored in .gif format
there are about 40 images altogether, each is 25x25 pixels, the "largest" is 1.25Kb
for now I have got only complaints from S3 owners
the issue occurs on the standard OS and not on custom roms (at least I have no info about custom roms)
at least one S3 owner, who is facing the issue, claims that his phone is updated to the latest Android version
on many S3 devices the issue is not reproducible and the application works as designed
I am testing my apps on S2, S3, HTC Desire, Sony tablet S and of course the emulator - on all those I am not able to reproduce the issue
I am using FrameLayout, where the main drawing area takes the whole space, the controls (where the images are used) are packed in a LinearLayout, which is floating above
Here is a link to the application on the market:
https://play.google.com/store/apps/details?id=com.rts.android.spacesim&feature=search_result
This is NOT intended as some weird way to promote my app, if you are an S3 owner and decide to check if the issue is reproducible on your device, please write a comment here if it is and if not - what do you observe.
My questions are:
have anyone observed such an issue?
any ideas how to overcome it?
The following links suggest that GIF support might be broken again on 4.1, which most Galaxy S3's are running if I'm not mistaken. My personal phone is a Galaxy S3 at the moment, and I have 4.1.1 on it
GIF doesn't display on Samsung Galaxy Note 2
http://code.google.com/p/android/issues/detail?id=3422
Why not use png?