I use android face detection API with Camera.FaceDetectionListener .
I have several tablets.
A Galaxy Tab GT-P5110 2 version 4.0.3 (Kernel: 3.0.8-365113-user dpi DELL155 # # 1)
A Galaxy Tab GT-P5110 2 version 4.1.1 (Kernel: 3.0.31-523998 se.infra # SEP-98 # 1)
A Galaxy Tab GT-P5210 3 version 4.2.2 (Kernel: 3.4.34-1135839 se.infra # S0210-10 # 1)
The detection works perfectly on the first but on the second Tab 2, as soon as I turn on face detection, preview flick and detection is slow.
On Tab 3, the listener is never invoked as if it did not detect any faces.
I also tried this sample : http://developer.samsung.com/android/samples/Mad-Hatter-Face-Recogition
but I have the same issues.
Is there a known bug on Samsung devices ?
Thanks
It is known that Samsung's devices perform differently. So you have to treat different Samsung's device carefully. You can use two steps to investigate this issue: 1. pass a bitmap directly to the detection API to check whether it can work. 2. check the preview FPS. maybe you have to set different parameters to improve camera performance.
Related
Following the Camera 2 sample I've created simple camera class to capture the images. When it's okay with capturing both flash/non-flash images on any device with Android < 7.0, on mine Nexus 5X with Android 7.1 the same config fire the flash only once on the preview. Pre-sequences are the next:
for the preview I'm using CameraDevice.TEMPLATE_PREVIEW with AE mode set to CameraMetadata.CONTROL_AE_MODE_ON_ALWAYS_FLASH
the same I use for the capture still picture, but with CameraDevice.TEMPLATE_STILL_CAPTURE
If someone can help me with this case - I'll be really appreciated.
This is just additional information on the above issue. I wish to draw some attention to this problem!
My application takes a photo every 5 seconds. I (1) select the camera, (2) acquirer a session and then with each loop I (3) create a Capture request in which I set the Flash Mode and call the capture method on the session.
I have no issues with my Samsung SM-G550T (Android version 6.01), but I was having some issues with the Flash Mode on my Moto G4 (Android version 7.0). I got both phones to Flash, but only with this setting:
CaptureRequest.Builder requestBuilder = mCameraDevice.createCaptureRequest(CameraDevice.TEMPLATE_STILL_CAPTURE);
requestBuilder.set(CaptureRequest.FLASH_MODE, CaptureRequest.FLASH_MODE_SINGLE);
I am presently having an issue with a LG device (M210N) (Android version 7.0). Using the settings I stated above I get the device to flash just once. If I completely re-initialize the camera (as described above) the device will flash again only once.
If I add the CONTROL_AE_MODE_ON_ALWAYS_FLASH setting to the above requestBuilder, then the LG does not flash at all. So I had to remove that flag.
I have tried many different additional settings and combination for settings and none of them have eliminated this issue. I wonder how many devices are affected by this issue.
I am using the CWAC camera within my app. The mirrorFFC set to true in my custom camera host class, is working fine with my Xiaomi Redmi2 i.e it correctly mirrors the image. However when I sent a build to a friend who has the Samsung S4, the image is not mirrored. Do I need to make any specific change for Samsung devices or for specific devices?
Most likely, the image is too big for the available heap space, and we ran out of memory attempting to mirror the image. The documentation contains some advice for this scenario.
Also note that this library is no longer being actively developed, due to the issues outlined in the project README.
I want to create an AVD to test apps on a Samsung Galaxy Note 2.
I have checked similar questions, but they are intended for older AVD versions.
Which device should I use?
Should I set the target as "Android 2.3.3 - API Level 10"?
I know the following:
Screen Size 5.55"
Resolution 720w x 1280h
Density xhdpi
RAM 2 GiB
Hardware buttons*
The rest I just left at the defaults:
Sensors: Accelerometer, GPS, Gyroscope, Proximity Sensor
Cameras: Front, Rear
Input: No Nav
Size: Large
Screen Ratio: long
Buttons: Software
Portrait: Enabled
Device States: Enabled
*Picture does not show the "Buttons" as hardware, but it should be.
Hope this helps!
This link will definitely help you with galaxy note 3 smart phone emulator.
http://developer.samsung.com/android/tools-sdks/Samsung-GALAXY-Tab-Emulator
download file from this link and follow simple steps.
Hope this helps someone.....
Which device should I use?
Unless Samsung has some downloadable device definitions that you can use, you should define your own device that matches the Note II as closely as you can.
Should I set the target as "Android 2.3.3 - API Level 10"?
Only if for some reason you downgraded your Note II to Android 2.3.3. The Note II ships with Android 4.1 AFAIK.
I would like to post one more answer, though others are good enough.
Some times emulator doesn't work as expected when we are looking for emulator which compatible with the real device. I faced may frustrating problem like this, after some exploration I found that Samsung provides a significant solution for this i.e RTL (Remote Test Lab) it is free.
For more information and how to use it check out Samsung RTL Solution
Hope this one help you.
What are the lines that need to be added in android_usb.inf, so that I can use Samsung Galaxy Note 2 in developer's mode?
What are other changes needs to be made?
I'm developing android camera application. Tested on some devices and it work's, but on samsung galaxy i9003 setparameters didn't work.
Here how I do it:
cameraParams.setColorEffect([some supported effect]);
camera.setPrameters(cameraParams);
[some supported effect] I get with cameraParams.getSupportedColorEffects().
My code is not as simple as I wrote , but in the end it do this.
It works on many devices including samsung galaxy s i9000 ( though I must do some trick on i9000, there is known bug in params when you get params with params.flatten() there is spaces in parameters).
Please some help, it's first time I'm writing here.
Different devices will have different camera capabilities so you should check that the parameter that you wish to set is indeed supported by the device e.g. call getSupportedColorEffects() - this gives you a list of supported effects or null so you can check this before you try to set them.