Hi,
Thanks for your question. Determining the target aspect ratio for full screen apps by the window metrics should be fine. I have some questions about the problem you mentioned - "In some device preview quality is getting downgraded while binding at 16:9 aspect ratio,so need to check first or create a fall back".
1. What is the device and what is the selected preview resolution for this device?
2. What is the created fallback that could improve the preview quality issue on the specific device. What is the selected preview resolution after applying your fallback rule?
3. Could you provide some screenshots to explain the "preview quality is getting downgraded" problem? (may comparing with the results after applying the fallback mechanism)
BTW, CameraX supports the new
ResolutionSelector API in 1.3.0 and deprecated the legacy setTargetAspectRatio and setTargetResolution API. I'll recommend you to use the new API which can support more settings and can also avoid the migration efforts in the future when the legacy API is removed.
Thanks.