I am using e/os/ 3.3-a15 with a Fairphone 6 and the side switch is set to enable / disable camera and mic.
The feature works perfectly well, if an app wants to use any of them a modal will appear asking to unblock those components.
The issue I encounter several times a day is that sometimes on the launcher while not yet actively in any application I can see the notification “Camera & mic enabled”. The switch has not been touched and I have no idea what application managed to suddenly forced-enabled those components.
Is their anyway for me to know what happens and which application managed that while in the background ?
It is not only sonce couple days, that message comes since the switch exists. I guess there is some logic which checks in the background the position of the switch. Then the message appears, the same as if you would have switched it…Not really a bug but also not neatly implemented…
But I get the message as if the switch was in the opposite state.
The switch is currently in “disabled mode“ but the notification and the state is suddenly in the “enabled mode“. The goal of the switch is to block any app from accessing those components but something seems to workaround the limitation (I can confirm that all app have access to the component).
Ohh, I see (sorry did not read your issue unti the end ). I have so far used it to put it into flight mode. Since 3.4 and the addition of Moments, I switched to that option and it never has worked wrongly. But I also usually have it in the top position.
Oh I don’t think the issue is with the Switch itself.
I’m afraid that the issue is with the feature that keeps the mic and camera disabled until an app request them and then ask if I want to unblock it.
Something seems to unblock in the background, which I don’t like.
Can someone please file this as a bug report here?
It’s tremendously unsettling having the camera access (which was deactivated) constantly activating by itself like a ghost or a hacker. Especially for a privacy focused OS and device (providing something similar like a hardware switch, but obviously not similar enough) this is very bad.
I have opened us a ticket, if you have any additional information useful to the case, please keep it coming
@rXp you said you got the problem on eOS 3.3, are you using a FP6 e/OS edition or a post-purchase transitioned FP6 e/OS? Can you give me the whole version string from the phone settings?
On the Telegram channel a user expressed this as opening or use of an app which does have mic and Camera permission will cause this notification and the notification tells you that the “Switch” was over-ridden.
This, say, might include say incoming use of an app … even including phone / missed call or might include an app running in the background capable of waking for some Network check or similar at intervals. ??
Might this fit your experience or is this an oversimplification or are one or two apps possible culprits?
Yeah this could also be the culprid, but tbh I don’t have enough data to say with certainty that it is coming from such app requests in general yet.
So to answer your questions - it would fit my case that it is a general issue, not one of a specific app, but I can not yet rule out that it is maybe the type of app or the implementation of rights in those apps.
Update: since two days it never happened again for me!
I changed the following (not sure which one caused the solution) :
Installed the 3.6 update
Changed the Slider Switch action (this setting moved btw in the menu to system - buttons) to dark/light mode.
Note that since that actually the dark/light mode didn’t change by itself like the camera activation did before. Neither did the camera/mic access (I have put them prominently in the quick settings so I would notice that, and now use the settings buttons instead of the slider).
So the problem seems solved for me. I don’t dare changing it back but maybe someone can experiment with it and report if it would remain like this with 3.6 even if the slider action is back to camera/mic.
). I have so far used it to put it into flight mode. Since 3.4 and the addition of Moments, I switched to that option and it never has worked wrongly. But I also usually have it in the top position.