A bug in The Camera2APi High Speed recording Session 2

Camera2APi - CameraConstrainedHighSpeedCaptureSession
My code works on Samsung S20 also now.
It was working on S20 Plus & Ultra but not in the last update. I get allot of complains from users about it.
I manage to capture video using even 120FPS & 240 using my S20 (also on Pixel devices - it is not a problem in my code) but not on the s20 Plus & Ultra.
Also - the normal(not fast) recording session was allowing 60 FPS on S20, S20 Plus, S20 Ultra. and now on none of them(but managed on Pixel). I manage on my S20 to get to 60 & 90 FPS with the CameraConstrainedHighSpeedCaptureSession [30-120] or the [60-120]

Please check why :

  1. the S20 Plus & Ultra FastSession do not support 120/240 FPS
  2. If you can allow again for the S20, S20plus, S20 Ultra to record on normal session at 60 FPS(it was before)

CHI : [SS_ERR ]: [CHI_FAST_AEC]: chxsecusecasefastaec.cpp: SessionCbPartialCaptureResult: 663: Result: Cannot Accept NULL private data here for = 0
02-27 12:04:07.859 942 2798 E CHI : [SS_ERR ]: [CHI_FAST_AEC]: chxsecusecasefastaec.cpp: SessionCbPartialCaptureResult: 663: Result: Cannot Accept NULL private data here for = 1
02-27 12:04:07.860 942 2798 E CHI : [SS_ERR ]: [CHI_FAST_AEC]: chxsecusecasefastaec.cpp: SessionCbPartialCaptureResult: 663: Result: Cannot Accept NULL private data here for = 2
02-27 12:04:07.865 1147 28728 E Camera3-Device: Video size: 1280x720 @ 120-120 fps
02-27 12:04:07.865 1147 28728 E Camera3-Device: Matching high speed configuration found. Limit batch size to 2
02-27 12:04:07.865 1147 28728 E Camera3-Device: Limit max batch size to 2
02-27 12:04:07.872 892 1709 E device_utils: update_device_list: Invalid device: 0
02-27 12:04:07.880 1108 2114 E CoverManager: getCoverState : coverState is null
02-27 12:04:07.887 989 3022 E NativeCustomFrequencyManager: [NativeCFMS] BpCustomFrequencyManager::acquire()
02-27 12:04:07.892 942 2798 E CHIUSECASE: [ERROR ] chxusecase.cpp:980 ReturnFrameworkResult() ChiFrame: 0 App Frame: 0 - pResult contains more buffers (1) than the expected number of buffers (0) to return to the frameworklogsamsung.txt|attachment (937.4 KB)logsamsung.txt (937.4 KB)

You can submit the bug here for better support, https://developer.samsung.com/dashboard/support