Neither do most phones these days unfortunately. The ones that do have them are not mainstream phones, which means the chances of a fully working custom ROM for them is next to zero.

I'd be rocking a pixel phone if it weren't for this. really sad tbh

Nah, I feel cheated by Fairphone. With the whole FP3 and FP3+, they were leading with the idea that they have settled on the form factor, and then just evolve the separate mainboard/camera/display modules independently

Fair enough. From my perspective it was ambitious thinking anyway: I was actually curious as to how Fairphone got things like the replaceable camera to work (had a peek in their git, it kind of works: they init the old driver and try to turn on the camera, if it returns an error then they load the new driver). The truth is though, a 100% truly modular phone, in the same way a PC is modular, cannot happen without some serious standardization.

Unlike webcams that use USB internally, and laptop displays that use standardized connectors and protocols (like eDP), mobile phones are almost entirely proprietary devices with a finite hardware-limited range of peripherals they can support at a low level.

Qualcomm in particular doesn't care about backwards compatibility when it comes to their SoCs, meaning the MIPI interface for the phone display on one SoC may be moved to completely different pins on another Qualcomm SoC, or may use a completely different number of pins. The same applies to the camera interface, although the main concern there will be the SoC, as it ultimately determines what resolutions/framerates etc you can achieve within the limits of the camera module.

Those are both solvable problems though. The real issue in my eyes is the lack of a proper BIOS to build a device tree and the other stuff that an OS build would need to be device-agnostic, like closed-source blobs for fingerprint scanners, display brightness control etc. These essentially limit mobile ARM devices to OSes made specifically for that hardware, preventing drop-in upgrades for cameras and the like from being a thing - unless you take Fairphone's approach and handle it in user space

With the FP4, they scraped all that and just chased whatever was trendy at the time and cranked the "but the environment" marketing.

I agree. To me most of the FP4 marketing material felt a bit like greenwashing, and the excuse for the headphone jack removal was pretty poor considering they also released completely unrepairable earbuds shortly after. The materials used may be fairer, but the pros end there as far as the buds are is concerned.

The FP5 marketing material is not as bad in that regard I think, and the Fairbuds XL should have been what they released originally compared to the unrepairable buds cash grab, even if they offered it discounted (IIRC) with the FP4.

I paid the Fairphone premium knowing that the specs were crap, but that at least in the future I wouldn't need to upgrade by buying a whole phone. Promising to have software upgrades for 8 years is nice, but it's worthless if you can not upgrade any of the hardware in the meantime.

For now I will just go buy a "budget premium" Android and pray that the people from frame.work decide to extend into phones as well in the next 2-3 years.

True. I feel unless the software updates are optimized to take advantage of the phone's hardware as it ages, the performance will fall off a cliff, especially as consumables like the EMMC storage uses up its write cycles, and takes longer to identify suitable areas of its NAND to use for operations.

A Framework phone would also be something I'm interested in, especially if it follows the likes of Project Ara's design