[email protected] crashes

[sm131313]

Whenever I start the builtin round camera for quick videorecordings I receive below crash.

It works perfectly fine with official Telegram FOSS client but Forkclient crashes it.
I tried reinstalling on a new profile, same thing happened there too, so I take into conclusion its related to the app.
ForkClient 10.9.2.0 and older doesn't have this issue.
ForkClient 10.9.3.0 and newer has this issue.

The picture is blurred and camera won't run and a crash dialog pops up.
I can take a built in photo just fine.
I can start the standalone camera app itself and take a video recording both sides of camera all fine.
But whenever I start the builtin camera for recording video within the app the camera crashes. Telegram doesn't crash at all and runs perfectly fine.

Phone is Google Pixel 8, running GrapheneOS.

Below is the crashlog

`type: crash
osVersion: google/panther/panther:14/AP1A.240505.005/2024050700:user/release-keys
uid: 1000 (u:r:hal_camera_default:s0)
cmdline: /apex/com.google.pixel.camera.hal/bin/hw/[email protected]
processUptime: 0s

abortMessage: Check failed: *physical_mode_info.virtual_output == virtual_mode_info.output (*physical_mode_info.virtual_output={image: {size: {width: 1720, height: 1224}, virtual_channel: 0, data_type: raw_10}, pd: N/A, embedded: N/A}, virtual_mode_info.output={image: {size: {width: 3440, height: 2000}, virtual_channel: 0, data_type: raw_10}, pd: N/A, embedded: N/A}) The virtual output of physical driver mismatches with virtual camera output

signal: 6 (SIGABRT), code -1 (SI_QUEUE)
threadName: RunnerH:P+:B:0

backtrace:
    /apex/com.android.runtime/lib64/bionic/libc.so (abort+164, pc 64e84)
    /system/lib64/liblog.so (__android_log_default_aborter+12, pc 625c)
    /apex/com.android.vndk.v35/lib64/libbase.so (android::base::LogMessage::~LogMessage()+352, pc 18fd0)
    /apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc 84e78c)
    /apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc 52a02c)
    /apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc 4a0d48)
    /apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc 6753b0)
    /apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc 44e8b8)
    /apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc 677478)
    /apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc 3e3ba8)
    /apex/com.google.pixel.camera.hal/lib64/liblyric_hwl.so (pc dde2d8)
    /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204, pc cf93c)
    /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64, pc 66730)`

[sm131313]

I just want to say that my issue has been solved in the latest updated version
— Updated to 10.9.5 build of the official Telegram.
Version code: 491109.

I do not experience this issue anymore.