FP5 Camera App crash (null pointer exception on missing camera)

Hi, I’ve had a FP5 for just over a year and has started having a random issue where the three cameras (back wide + normal + selfie) all intermittently stop working which isn’t global, (sometimes snapchat/whatsapp work with different cameras where sometimes a third party camera app fails - all apps except the native camera app give you an error popup if a camera isn’t available, where the native app just crashes). If this happens, a full restart typically fixes it temporarily. It gets especially worse if you turn the screen off using the power button while the camera is in use but is very non-deterministic.

Gist link with everything with specific lines linked below

For the native app crashes, I pulled the logs which gives a very clear cause, especially when you look at the source from pulled the camera APK - if a camera returns a null modeInfo, getPictureSize is passed a null value which causes the crash

But weirdly there are checks elsewhere for if (modeInfo == null) { return; }

As for the camera missing, I have no idea where to start, dumpsys media.camera shows the selfie camera just re-appears after a reboot, e.g. compare before a reboot and after.

Build Number: FP5.VT2Q.C.092.20260330

Hi and welcome to the community forum.

Could you indicate your Settings > About phone > Build number?

Thanks for looking at this, it’s FP5.VT2Q.C.092.20260330

OK so stock FP OS latest release.

There were some problems with the camera crashing earlier on, a couple of years back, but more recent problems have I think been imputed to the A15 generic memory management problems that were fixed in C.089.

It’s certainly worth opening a ticket with official Fairphone Support. I don’t remember seeing recently a problem similar to yours. This might be due to a faulty component. Warranty would presumably apply.

You could also try swapping in camera modules to test. Maybe contact a Fairphone angel if there’s one near you.

Sure. Developers are inconsistent :wink: In theory no app should crash but gracefully notify the problem …

Cheers, I’ll try making a support ticket again - I made one last September, but it got automatically closed in November with no reply

If you can find someone to lend modules for test that would be ideal, maybe an angel as suggested above.

Warranty always (I think) requires sending the phone in. Use the “Diagnose and repair” option.

But you could begin with a detailed e-mail, maybe pointing to this thread, option “Create a support ticket” at bottom of the page. Also maybe live chat weekday mornings.