It is fantastic that you found an OEM to collaborate with you! And it seems like they take you seriously, as they work to support GrapheneOS on their phones, and improve their hardware to be secure enough.
A core security feature is the existence of a headphone jack for 2 reasons:
1. Bluetooth
Headphone jacks allow to listen to music without any wireless connection.
Bluetooth headphones add an enormous attack surface, and most consumer headphones outside of big brands will run outdated firmware.
- Other brands will not allow firmware updates from GrapheneOS, like the official Google Pixel buds, and likely Apple Airpods or other large OEMs' too
- Firmware updates usually require a proprietary App and are themselves proprietary and intransparent ("this update: more fixes and improvements").
- I expect that OEMs do not fix all existing vulnerabilities, as there is nobody who seems to actually monitor that.
I have contacted multiple manufacturers of headphones, spoken to their technical support and was forwarded, but no reply after months. I specifically asked about vulnerabilities related to the "race toolkit", reported over a year ago, affecting all "Airoha" based devices.
The vulnerabilty shows how big of an issue Bluetooth is. It did not require capturing an initial key exchange during pairing, and it was not simply an issue of audio traffic being sniffed. No, the connection to a "dumb" receiving device (like headphones of multiple OEMs) allowed attackers to execute commands on the phone!
The developers didn't get a response from the various affected OEMs they contacted either. Even if this vulnerability was fixed (again, zero transparency here), this shows what a complicated mess Bluetooth is, accelerated by these shady industry practices.
Additionally
- Bluetooth headphones have a way higher starting price than a random pair of wired headphones, and/or are (still) a security nightmare!
- They also require charging, batteries and more resources than wired ones.
- Brands like Sennheiser sell bluetooth headphones with average sound quality, while their cheaper wired headphones sound better!
2. USB-Port
Alternatively and arguably more or less securely, you could use a DAC (digital-analog-converter, here an AUX-USB-dongle) with wired headphones.
But there are many angles from where issues can arise.
- UX: DACs suck, pretty much
- They do not connect as reliably as a plug-and-play headphone jack.
- The connectors get loose.
- In combination with GrapheneOS' amazing USB-port-blocking, they at least require to unlock the device while connecting, or there is no sound.
- The lag between plugging in and being detected is longer than with an aux cable.
- Many cheap ones might have bad quality on headphones or microphone, or no microphone support at all.
- And the worst, charging your phone: either you get a bulky, expensive and complicated dongle that can do both (their USB controller resets if you put something in/out, so GrapheneOS' port blocking disables it again and you at least need to unlock the screen) or you awkwardly wait until your phone is charged, OR you give in and temporarily switch to bluetooth headphones.
- price and availability: these things are expensive!
- The official ones by Google (which they sold as an alibi for removing the jack, I bet) are apparently 50€ and unavailable in my region.
- German electronic shops usually just stock the flimsy ones from Apple (that also reduce the max volume on non-Apple devices!) and maybe some cheap ones, with the mentioned problems.
- wear:
- the dongles stick out while carrying and are the only thing you need to regularly plug in and out of the USB port, as most will charge their phones at night.
- This is horrible, as the USB port is the only port left on the phone, and required for charging and data recovery! (I have never used wireless charging, don't know how it works and if it even works out of the box).
- If this port breaks, one needs to remove the display (which is really hard without breaking it) and buy a new port from somewhere. This requires experience, materials and tools, or to pay at least 50€ for repair.
- security: last but not least, as already mentioned, if you need to keep the USB-port enabled for simple audio output, that is a huge attack surface increase for no real reason!
Conclusion
I don't know why this is even a topic. Removing the headphone jack is silly capitalist behavior to force the last remaining people into buying the company's bluetooth buds. Meanwhile, phones have not gotten smaller (heck, there aren't any secure phones at children-friendly sizes!) and could easily fit more ports. There is no technical reason to do it, everyone saying that is trying to cope.
As Motorola is listening to you, I urge you to please mention to them how your community is longing for headphone jacks. Seriously, this would be a significant reason to switch from a Pixel!