Mark

Previously the interval timer was started when the previous photo was taken, i.e. after any delay to actually take the photo - so a 1s delay actually giving more like 1.1s. Now it's measured from when the camera requests to take a photo, which in general should lead to more regular times closer to the requested interval. I think what's happening here is it's caught in a cycle where: 0.0s: request to take a photo 0.9s: photo took 0.9s 1.0s: request to take a photo 1.0s: photo taken immediately (0.1s...

I wasn't clear on your response - is Open Camera now working without crashing (when using Camera2 API under Settings)? And does the flash timing now work okay with Camera2 API?

It's miscalculating the phone's angle

Thanks - I wasn't sure what the test menu is(?) but glad Open Camera's calibration has helped.

Open Camera supports selecting cameras, when either they are exposed as a dedicated "logical" camera, or as a physical camera. But this requires the manufacturer to be supporting the standard Android APIs for third party applications.

See https://sourceforge.net/p/opencamera/tickets/1019/ .

Thanks for the bug report. Although flash is indeed controlled by software, this exact behaviour in this case is handled by the camera driver. How do other third party camera applications behave? In Open Camera, does Settings/"Camera API" show? If so, try "Camera2 API" do any better? (With this option, Open Camera will have more control over the flash timing/behaviour.)

Just to check, how did you test your sensors are calibrated? Open Camera has its own calibration in case that helps: Settings/More camera controls/"Calibrate level angle" (perhaps first try "Reset" in case that got set somehow; but if not, follow the instructions to calibrate).