List
camera2 API Android issue
Posted Date: 2018-05-09 20:25     Edited Date: 2018-05-18 10:59     Writer: inactive

1. SDK Version: 3.5
2. Development Environment: Native Android
3. Tracker/Scanner: both
4. License Type: Pro-One Time Fee
5. Target Device: Nexus 5X

TrackedImage appears rotated (Issue appears in MaxST sample app too). It seems like CameraDevice use deprecated Camera class, as described here: https://developer.android.com/reference/android/hardware/camera2/package-summary If so, did you plan SDK update?  Or you can give advice on how to get around this case? 

Thank you!

Posted Date: 2018-05-10 2:25     Edited Date: 2018-05-10 2:25     Writer: inactive

Hi,

Did you use face camera by any chance? Our sdk provides camera configuration sample and you can find camera rotation sample code.

Our sdk does not use camera2 api for android yet because some of android devices give low fps camera frame.

But we have plan to use camera2 api of coursely and it's not so far future.

Thank you

Jack

SDK Team, Maxst

 

 

Posted Date: 2018-05-10 17:02     Edited Date: 2018-05-10 17:02     Writer: inactive

Hi,

thanks for the answer! if I understood correctly, you mean:

CameraDevice.getInstance().flipVideo(CameraDevice.FlipDirection.VERTICAL, true);

But this is not exactly what I need. I use the real camera and all I need is to rotate the image by 180 degrees to avoid this bug. I think I can just rotate the transformation matrix for nexus 5x, but maybe there is a more correct solution to foresee such bugs on other devices?  

Posted Date: 2018-05-11 0:24     Edited Date: 2018-05-11 0:24     Writer: inactive

Yes, it is one of the solution and actually it's not the perfect solution like you said.

Before new release we have tested sdk on most of devices which we have.

But unfortuanately we don't have nexus 5x at this time.

So..could you please let us know your problem are same on other android phone?

If same problem can be seen on other devices we will be able to find the solution more easily.

Thank you

 

Posted Date: 2018-05-11 22:33     Edited Date: 2018-05-11 22:33     Writer: inactive

At the moment the problem is reproduced only on this device, as far as I know.

Posted Date: 2018-05-13 23:16     Edited Date: 2018-05-13 23:16     Writer: inactive

Ok, thanks for letting us know.

Posted Date: 2018-05-17 23:18     Edited Date: 2018-05-17 23:18     Writer: inactive

is there any chance that this issue will be fixed in the 3.5.x SDK version?

Posted Date: 2018-05-18 3:56     Edited Date: 2018-05-18 3:56     Writer: inactive

Yes, we are working for this now.

 

Posted Date: 2018-05-18 10:59     Edited Date: 2018-05-18 10:59     Writer: inactive

good news! we will looking forward to :)