Hi Todor, When using the camss driver trough one of its /dev/videoX device nodes, applications are currently unable to see the video controls the camera sensor exposes. Same goes for other ioctls such as VIDIOC_ENUM_FMT, so the only valid resolution setting for applications to use is the one that was previously set through the media controller layer. Applications usually query the available formats and then pick one using the standard V4L2 APIs, and many can't easily be forced to use a specific one. If I'm getting this right, could you explain what's the rationale here? Is that simply a missing feature or was that approach chosen on purpose? Thanks, Daniel