[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] Penman:
I expierenced a "java.lang.NoSuchMethodException: android.hardware.Camera.openOPService" issue followed by some other obvious jar-mismatching issues. Not sure, what was the cause. I reflashed Firmware and then ROM but no success.

I did a factory reset and reflashed the ROM again and the camera is working partially now. It takes photos, but my beloved Pro Mode seems to have issues with dark pictures and high shutter time. Not sure if it's firmware or framework issue.

04-06 16:03:30.760 833 15859 E mm-camera: <MCT ><ERROR> 99: mct_bus_sof_thread_run: FATAL Session 4: SOF Freeze! Sending error message
04-06 16:03:30.760 833 15859 I mm-camera: <MCT >< INFO> 134: mct_bus_sof_thread_run: Sending HW_ERROR from MCT on session =4
04-06 16:03:30.760 833 15807 E mm-camera: <MCT ><ERROR> 832: mct_controller_send_cb: FATAL: Sending HW_Error
04-06 16:03:30.761 833 15829 E QCamera : <HAL><ERROR> camEvtHandle: 766: Fatal, camera daemon died
04-06 16:03:30.765 833 1608 E QCamera : <HAL><ERROR> processCaptureRequest: 5250: Unblocked on timeout!!!!
04-06 16:03:30.765 833 1608 E CamDevSession@3.2-impl: processOneCaptureRequest: HAL process_capture_request call failed!
04-06 16:03:30.765 1006 15833 E Camera3-Device: Camera 0: sendRequestsBatch: RequestThread: Unable to submit capture request 214 to HAL device: Function not implemented (-38)
04-06 16:03:30.767 11831 11947 E CameraImpl: Device '0' error
04-06 16:03:30.767 11831 13742 W CameraImpl: onDeviceError() - Current state is OPENED
04-06 16:03:30.767 11831 13742 E CameraThread: onCameraError() - Camera : Camera2[ID=0, Facing=BACK]
04-06 16:03:30.767 11831 13742 D CameraImpl: [Property] State(id=312) : OPENED -> CLOSING
04-06 16:03:30.767 11831 13742 W CameraImpl: stopCaptureSession() - Stop capture session for camera '0'
04-06 16:03:30.767 11831 13742 W CameraImpl: stopCaptureSession() - Stop capture and wait for completion
04-06 16:03:30.767 11831 13742 D CameraImpl: [Property] CaptureState(id=203) : STARTED -> STOPPING
04-06 16:03:30.767 11831 13742 W CameraImpl: stopCaptureInternal() - Elapsed 5190 ms from capturing
04-06 16:03:30.767 11831 13742 W CameraImpl: stopCaptureInternal() - Abort captures
04-06 16:03:30.768 11831 13742 E CameraImpl: stopCaptureInternal() - Fail to abort captures
04-06 16:03:30.768 11831 13742 E CameraImpl: android.hardware.camera2.CameraAccessException: CAMERA_ERROR (3): The camera device has encountered a serious error
04-06 16:03:30.768 11831 13742 E CameraImpl:	at android.hardware.camera2.impl.CameraDeviceImpl.checkIfCameraClosedOrInError(CameraDeviceImpl.java:2577)
04-06 16:03:30.768 11831 13742 E CameraImpl:	at android.hardware.camera2.impl.CameraDeviceImpl.flush(CameraDeviceImpl.java:1180)
04-06 16:03:30.768 11831 13742 E CameraImpl:	at android.hardware.camera2.impl.CameraCaptureSessionImpl.abortCaptures(CameraCaptureSessionImpl.java:430)
04-06 16:03:30.768 11831 13742 E CameraImpl:	at com.oneplus.camera.CameraImpl.stopCaptureInternal(CameraImpl.java:7099)
04-06 16:03:30.768 11831 13742 E CameraImpl:	at com.oneplus.camera.CameraImpl.stopCaptureSession(CameraImpl.java:7172)
04-06 16:03:30.768 11831 13742 E CameraImpl:	at com.oneplus.camera.CameraImpl.close(CameraImpl.java:2363)
04-06 16:03:30.768 11831 13742 E CameraImpl:	at com.oneplus.camera.CameraImpl.onDeviceError(CameraImpl.java:3487)
04-06 16:03:30.768 11831 13742 E CameraImpl:	at com.oneplus.camera.CameraImpl.access$2300(CameraImpl.java:106)
04-06 16:03:30.768 11831 13742 E CameraImpl:	at com.oneplus.camera.CameraImpl$DeviceStateCallback$3.run(CameraImpl.java:625)
04-06 16:03:30.768 11831 13742 E CameraImpl:	at android.os.Handler.handleCallback(Handler.java:883)
04-06 16:03:30.768 11831 13742 E CameraImpl:	at android.os.Handler.dispatchMessage(Handler.java:100)
04-06 16:03:30.768 11831 13742 E CameraImpl:	at android.os.Looper.loop(Looper.java:214)
04-06 16:03:30.768 11831 13742 E CameraImpl:	at com.oneplus.base.BaseThread.run(BaseThread.java:393)
04-06 16:03:30.768 11831 13742 W CameraImpl: stopCaptureInternal() - Stop capture directly

Since restoring procedure took a while and was annoying thanks to appbundles and Titanium Backup not supporting them, I want to avoid this as much as possible.

When I was researching I became curious why people decide for the no-verity option. What gains do you expect? Minimal performance boost? Easier recovery because storage is unencrypted?

Another question: When I'm creating a Backup with TWRP, I have to remove /data/per_app directory first, otherwise it crashes in the middle of the progress.

I:addFile '/data/per_boot' including root: 1
==> set selinux context: u:object_r:system_data_file:s0
failed to lookup tar policy for '/data/per_boot' - '850973f4f0415287'
I:Error adding file '/data/per_boot' to '/data/media/0/TWRP/BACKUPS/xxxxxx/2020-04-06--15-47-21_QQ2A200305003/data.ext4.win003'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/xxxxxx/2020-04-06--15-47-21_QQ2A200305003/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.

Any ideas on that?

/edit

More things: How do I get rid of the "SIM cards changed" notification after every boot? It's been there since I've changed to Android Q.

Second: How do I get rid of the "Finish setting up Pixel" bubble in Settings app on the top? I cannot simply click "OK". Nothing is happening.