MyCamera | Example of how to use Android camera | Camera library

If you say in general it behaves as expected unless you rotate this object:

Translate has an optional parameter Space relativeTo which by default (if not provided) is Space.Self

Applies transformation relative to the local coordinate system.

e.g.

By dereferencing we get a value of this address. And this value assign to reference?

You cannot assign a reference. You can only initialise a reference.

Now consider this:

With regards to the image analysis resolution, the documentation of ImageAnalysis.Builder.setTargetResolution() states that:

The maximum available resolution that could be selected for an ImageAnalysis is limited to be under 1080p.

So setting a size of 2560x800 won't work as you expect. In return CameraX seems to be selecting the maximum ImageAnalysis resolution that has the same aspect ratio you requested (2560/800 = 1280/400).

File fileName = new File(Environment.getExternalStorageDirectory() + "/" + "FILENAME");

if (!fileName.exists()) fileName.createNewFile();

You can set the rotation of your camera with Quaternion.Euler

If you want to set the rotation on the Y axis it would be:

You can't add a Surface in a CaptureRequest that wasn't part of the Surfaces given to createCaptureSession. In your code, you're creating an ImageReader only once you want to take a picture, and the API is telling you that's not valid:

Caused by: java.lang.IllegalArgumentException: CaptureRequest contains unconfigured Input/Output Surface!

So either set up the ImageReader the same time you're setting up your capture session and include its Surface in the output target list, or create a new capture session in takePicture that includes the newly-created ImageReader.

The latter isn't really recommended, because creating a new capture session will pause preview briefly. So create the ImageReader where you're calling CameraDevice.createCaptureSession, and make sure you keep the ImageReader as part of your enclosing class to avoid it getting garbage-collected.

One solution could be to have inside the ball gameObject 2 childs, one with the ball that will rotate, and another one with the camera. This way the camera will follow the parent gameObject, who doesn't rotate (but you should update the position).

The other one, and the one I like it the most is to do not child the camera on to the ball gameObject, just update the camera position from the ball position, JUST the position, not the rotation. Something like:

Add your script file to your angular.json in the script section

There is a space at the end of the JSON.