Android Jetpack: Understand the CameraX Camera-Support Library (Google I/O'19)

Learn how to get started with the new CameraX support library in Jetpack, which provides the best support across a wide selection of Android Camera hardware with minimal effort to integrate machine learning.

Watch more #io19 here:
Android & Play at Google I/O 2019 Playlist →
Google I/O 2019 All Sessions Playlist →
Learn more on the I/O Website →

Subscribe to the Android Developers Channel →…


  1. He it is not use…
    No proper documentation is there …
    I am finding touchtofocus feature in camerax no documentation is therefor that

  2. Can anybody comment on whether or not CameraX is able to access front and back camera's concurrently on devices who's hardware supports it?

  3. How come Google Pixel devices don't have full CameraX support? Why can I not use Google Camera's night mode (Night Sight) by using CameraX API?

  4. Well its a really Good Effort by Android but there are still things that needed to be focused on. As there is a flipping issue on front camera, there must be a feature to easily turn on and off mirror image. Also in this api front camera crashes.

  5. I recently used the camera 2 API to build a camera app as part of a university project. I hated every bit of the development process. First of all there are alot of things to account for, i want to develop i a camera app i really don't need to have 2 classes to query the device about its screen size and its resolution output. The one thing that bugged me the most is consistency. I tested the camera app on an HTC u11, samsung note 9, and google pixel 1. unsurprisingly everything worked fine on the pixel BUT the front camera straight up refused to work on the note and the flash refused to work on the htc. After this project i fully understand why instagram and snapchat uses to capture a screen view instead of a photo straight from the sensor. developing android camera app that works well across every android device is semi impossible.

  6. 1:53 Same consistency as Camera1 via the Camera2 legacy layer is not true. For example the CameraCharacteristics.SCALER_STREAM_CONFIGURATION_MAP does not output at all the same resolutions that are available with the "old" Camera1 API… Is this because you limit the resolution to 1920×1080 in the preview use case? But still the list returned in SCALER_STREAM_CONFIGURATION_MAP is a lot shorter than with camera.getParameters().getSupportedPreviewSizes() even for low resolutions!

  7. I m just glad I m understanding what is being said .the very fact is making me feel happy😄😄😄

  8. Now atleast Snapchat app can be improved, only if there engineering team works on this.

  9. I just spend a day today trying to bring camera2 to live for my image analysis demo app. Was a wasted day. Thank you so much.

  10. Camera2 API was a disaster. Not too hopeful about CameraX – they still like to throw in lots of helper classes for specialized use cases instead of covering the most common uses with defaults. E.g. why not just pass a SurfaceView reference to the builder for the preview destination? Was there a need to introduce a new ImageProxy class instead of using existing ones? And if so, why not place useful methods in it, e.g. rotate & crop the image?

Leave a Reply

Your email address will not be published. Required fields are marked *