nostr:nprofile1qqstnr0dfn4w5grepk7t8sc5qp5jqzwnf3lejf7zs6p44xdhfqd9cgspzdmhxue69uhhwmm59e6hg7r09ehkuef0xzlnyc I see the green microphone in use icon pop up as soon as I grant global microphone access, even though there is no app actively using the microphone, and nothing in the history of microphone access.
Any idea what's up here?
#GrapheneOS
Been wondering this myself. #asknstr
Some disturbed old spirits from apple, google, facebook, trying to regain access? o.0
Jokes aside, I hope you find the source soon!
I don't have that icon.
Is it possible that the app you granted access is running in the background?
Same happens when I close all apps, and stop all active apps.
There's a permissions manager app that lets you see what permissions were granted to a sensor.
Do you have apps allowed to access the mic all the time or only while in use?
Yes, same happens when none are allows and only a few are ask every time.
In privacy dashboard > microphone usage, it shows jitsi at times where general microphone access was granted, but jitsi was fully closed and not running in the background.
Yeah that's odd. I know I occasionally get the location icon unexpectedly appear but when I check, I've left an app running. It disappears when I close it.
My gut feel is that you've got a rogue app that's accessing your microphone.
It'd be cool if Graphene told you what was accessing the mic.
It's a known Android 15 QPR2 bug on the stock OS. Happens here too and it's looking at being resolved. Your mic isn't actually in use.
Currently fixing this wouldn't the top priority because of recent major circumstances. Team are desperate in working towards a smooth port to Android 16 (we don't have early access to the source) and general updates / security patches above all.
Thanks for the conformation!
Where can we help to make the work smoother?
We did a call on the other platforms that someone who works at an Android partner could get us access to the Android 16 sources to allow us to prepare early for migration to Android 16 in June.
If someone can provide that to us, the transition would be much smoother. We had relied on the lead developer who was forcibly conscripted to a military training camp to do a lot of their superhuman work. They are a huge reason why the upgrade to the latest major releases were so fast. All of this is strictly a consequence of losing them.
We could move over to Android 16 but not all features would be available. For example, the 2-factor fingerprint could get dropped for the initial release and then added it back later with user configuration being preserved so it works as before. Android 16 changed lock screen code by a lot.
We didn't need the access to these sources before then. GrapheneOS are willing to work as independent contractors for OEMs who provide it.
I'll see if I can find someone...
