camera2 | camera2 API的使用，camera1API的使用，连拍的实现，拍照预览，录像等等 | Camera library

Here's the code where you're getting the crash

Check this article on medium where there is explanation for why setValue would fail. https://medium.com/@valokafor/firebase-realtime-database-by-example-with-android-1e597819e24b . You might want to check Firebase rules

There's no reason you can't keep using the deprecated version of createCaptureSession - it works just as well as it did before. You'll just have to ignore the Android Studio deprecation warnings.

Basically, over time, we kept having to add more overloads of createCaptureSession with more and more variations of parameters and optional parameters, and it was getting excessive.

So we created SessionConfiguration as a configuration object that's more flexible over time (easier to add new parameters to it), set up one more createCaptureSession that accepts that, and deprecated all the prior versions to direct folks to the one we'd add today if we were designing the API again.

If you want to use the newest option, then you can take a look at OutputConfiguration (it just wraps the list of output Surfaces plus some other optional settings) - you can build one with just the surface you put in the Arrays.asList() call in your sample code.

But you can just keep using what you have - we won't actually break the old methods.

After testing around a bunch I found the following answer to my question.

For JPEG images:

Use the CaptureRequest directly and set the value for the tag JPEG_ORIENTATION according to the devices orientation. I simply used the display rotation, since only values of 0, 90, 180, 270 are allowed anyway:

The underlying camera2 API has a fairly strictly defined set of rules on how having multiple output resolutions works, in terms of cropping. The docs for the SCALER_CROP_REGION (digital zoom) control have useful diagrams about this; for your case, just assume the CROP_REGION covers the whole active array.

On top of that, CameraX PreviewView applies further cropping to its input, since the camera device itself only supports a few sizes. So PreviewView will pick a supported resolution that has a reasonable aspect ratio, and then crop it if necessary when displaying it to fill your View layout area.

So, the relationship between the ImageAnalysis and Preview use cases and their fields of view depends on both the resolutions CameraX selects for the use cases under the hood, and PreviewView's additional cropping.

What's probably happening here is that your landscape PreviewView is selecting an underlying resolution that's wider than ImageAnalysis is selecting. You could check what's actually selected via adb shell dumpsys media.camera if you have developer access to a device, while your app is running. That command dumps out a lot of info, including exactly what CameraX has configured the camera device to do.

You could try using the setTargetAspectRatio or the setTargetResolution methods on Preview.Builder to match the aspect ratio of the ImageAnalysis; that should ensure that the PreviewView is only ever a crop of what ImageAnalysis receives.

Ok, I found out the solution. So basically within the code there is this:

cameraX does not have a Camera API1 fallback. They rely on camera2 LEGACY support, but yes, the library includes many workarounds for specific problems. Please look at the list of devices they tested: https://developer.android.com/training/camerax/devices.

You don't explain what are "all the cases" you were previously using the camera1 fallback for, but if you have such list, you can go through the release notes to check whether they are addressed by the current version of the library. If they are not, you are welcome to add them to the issues list.

As the error message suggests, the same stuff seams to be around in two separate dependencies: once in ":PoseDetector-release:" and once in ":androidx.camera.camera-camera2-1.1.0-alpha02:"

I have run in this issue before, and was able to solve it. Sometimes it takes longer to find out which dependencies to remove.

The solution to this error is to remove one of the duplicate dependencies, in my case I believe it was removing the android plugin folder of some SDK in my Project's Assets Folder, due to the fact that the same dependency was already included by some package I downloaded and imported via the unity package manager.

The two cases I can think of, where my answer is garbage are:

• The collision is NOT due to collision between same dependencies, but just between namespaces

• You can not remove neither of the two dependencies because they only overlap, but BOTH each contain MORE stuff you need, which is NOT already included in the other one