raphidae What permissions or access could possibly be required to add a toggle to start a recording for every call?
I wouldn't know. I'm not a GrapheneOS dev or even a programmer. You'd have to ask them, which you didn't do maturely and sensibly as I said. You went straight to accusations of some shadowy pressure group or whatever.
Call recording already exists, the issue is that it needs to be manually triggered for every single call.
Which once again, takes a measly few seconds to do (and so, isn't anywhere near as much as an issue as you think it is)
I'm just saying I think automation for this being missing is weird
Not really. The GrapheneOS team do an incredible job with what limited resources are available to them. Resources that they prioritise for actually important features (primarily those to do with security) and not minor ones like this, which only people with very niche/specific needs like you treat as a major issue. In fact, call recording wasn't even added at all until April of this year and (I think) it only got added to Graphene because of relatively high demand for it if I recall.
What automation would save is not even a few seconds and there's no need to go into any settings menu at all, it just means the user needs to tap the record button for every single call. However, obviously this is a problem when calling hands-free.
My bad, I don't really use the feature (as I don't make many calls), so I forgot its just a record button but being a simple button only makes it even easier/faster to use. As for calling hands-free, I don't see why this is an issue? Hands-free just means the phone isn't in your hand. You can still press the button unless your hands are busy, such as when carrying something (that you can't immediately put down). If its just hands-free like the phone is sitting in the holder in your car or laying on a table, which I imagine to be the most likely "hands-free" scenarios to be in, then you can still easily press the button.
I am legally required to have all my calls automatically recorded. So, this tiny missing feature means I cannot use GrapheneOS at all. If you read up, there's someone else that describes their entire company wanting to switch to GOS but not being able to because of this as well.
Ok??? So the device just doesn't suit your needs at this time. In situations like this, all someone should do is make a request for their desired feature (or check if its already been requested), get/find the response and then make whichever decision is appropriate (wait/come back later/move on to something that does suit your needs).
There are many, many people for whom automatic call recording is either a contractual or legal requirement. Ironically, especially in professions where they work with privileged or otherwise sensitive client data where using GrapheneOS would not only benefit them but also their clients. So, this could impact the security of millions of people.
Sure, but that doesn't justify you behaving in a way that, at best, is immature/demanding, and at worst, is seen as a smear job. Of course GrapheneOS would be especially helpful for situations such as yours (sensitive client data), but as I've said, resource limits are in fact a thing and any dev team (not just GrapheneOS) can only do the best within the limits they're dealing with. This will almost always mean that the more niche stuff will be sidelined in order to prioritise the more broadly essential things. If you want to try to help the development and get to those "niche things", you need to support the team by either contributing code or donating.