GrapheneOS telephone app and microphone access

gray-wolf

I join the topic and questions above. If there is a global setting that allows the user to block the microphone, the microphone must be blocked from any applications or activities that use the microphone as a means of transmitting acoustic information. Dot! If "global mute" does not actually disable the microphone, but pursues other goals or uses some algorithms for combinations of actions and the like, then the developers should describe all the logical actions of "locks" and their combinations in a sequence of existing algorithms so that the user understands which processes actually occur under which combinations of locks. But in my opinion, the only correct decision of the developers on this issue is to implement the absolute priority of global blocking over all other settings. That is, complete and unconditional disconnection of the microphone from the system. Just like it's implemented (hopefully implemented!) with a smartphone's USB port.

bellaph

GrapheneOS

I don't really get how this affects the system wide setting to turn off the microphone permission, or is this bypassed by the "carrier-based calling implementation"? And if so, why doesn't it show up anywhere that the microphone has been used by the carrier based call implementation? Is that a system service (The "telephony service")?

When I look at the Microphone permission it says "Device Microphone is blocked Microphone data may still be shared when you call an emergency number". But this is not correct if the microphone data is shared by all carrier-based calls, and seems worrying when the user isn't notified by this at all.

I'm kind of surprised if this is actually expected behavior. Or maybe I'm just misunderstanding it. Hopefully this could be explained and clarified further.

Emmy

It seems this might be a bug already reported, and the @GrapheneOS issue tracker seems to list it as open:

https://github.com/GrapheneOS/os-issue-tracker/issues/5653

It's a bit of a mystery why it's flagged as solved here instead of acknowledging it's an open upstream bug, if that's what it is?

schweizer

Emmy Thank you for finding the link.

I am slightly disappointed to read the bug was confirmed in june however we are told here in october that we would just misunderstand the way Android/GOS works.

Let' hope this now gets fixed soon.

Emmy

schweizer Indeed, that "explanation" post isn't the most helpful one to start with, and it hasn't gotten better after finding the bug tracker.

I mean, we aren't whining or anything, it's just that something doesn't quite work as intended/expected, so you should be able to discuss it with those in the know. That's what user forums should be for.

« Previous Page