Look at where your phone actually is
The idea: Android's privacy dot fires correctly every time. The problem is that your phone is almost never somewhere you can see it — and more usefully, where your phone is changes what a sensor access actually means. The same camera access is meaningless in one place and worth investigating in another.
Android 12 and later show a small green dot in the top corner whenever an app opens your camera or microphone. It lasts about five seconds. It works exactly as advertised, and I've written before about what it does and doesn't cover.
This is a different question. Not "what does the dot tell you" but: where is your phone standing when it fires?
Because that turns out to matter twice over. It determines whether you see the warning at all — and it determines whether the access was worth warning you about in the first place.
Here are the five places phones actually spend their day, roughly in order of how much a sensor access there should concern you.
1. At the bottom of a bag
Under the keys, beside the reading glasses, screen against the lining.
An app opens the camera here and gets a black frame. It opens the microphone and gets muffled fabric. In terms of what could actually be captured, this is the least interesting place on the list.
But it's a perfect illustration of the underlying point: the access still happened. It's still a fact about how that app behaves — an app that reaches for your camera while it's buried in a handbag is an app that reaches for your camera without checking whether that makes any sense. The footage is worthless. The behavioural signal isn't.
2. In a pocket
The most common position by a mile, and the first one where the two sensors part company.
The camera sees the inside of your coat. Fine. The microphone works perfectly — it's a small hole on the edge of the phone, and fabric barely troubles it.
So a camera access in a pocket is close to meaningless, and a microphone access in the same position is the most consequential thing on this page. If you only ever learn one distinction about phone privacy, make it that one: for most realistic concerns, the microphone is the sensor that matters, and it's the one people worry about least.
3. Face down on the table at dinner
There's a small irony here worth naming.
Putting your phone face down is a privacy gesture. You do it out of courtesy and a vague sense of switching off. And it works — for the front camera, which now faces a tablecloth.
What it also does is hide the one live warning you had. The indicator is on the screen. The screen is against the table. If an app opens your microphone during dinner, the dot fires into the woodgrain.
The rear camera, meanwhile, is pointing at the ceiling, and the microphone is picking up your conversation exactly as well as it would in any other orientation. The gesture that feels most private is the one that most reliably removes your ability to notice anything.
4. On charge in another room
Face up on the kitchen counter, lighting an empty room, while you're two doors away.
This one is different in kind. In the previous three you were at least in the vicinity. Here there is nobody in the room at all. The dot can fire as brightly as it likes for as long as it likes.
It's also the position where duration starts to matter. A phone left alone for two hours is a phone where the difference between a 200-millisecond access and a four-minute one is enormous — and the difference the privacy indicator cannot express, because a dot that's on is just a dot that's on.
5. On the nightstand at 3am
The one that actually matters.
Screen locked. Room dark. Nobody awake. Eight hours in which every property that makes an access ordinary — you were using the phone, an app was open, you'd just tapped something — is absent by definition.
This is why lock state is the single most useful field in any sensor log. It's the difference between an access that explains itself and one that doesn't. A video app opening the camera fifty times while you're using it is a video app working. The same app, three times, at 3am, with the phone locked, is a question you'd want to ask.
And it's the one moment you are structurally guaranteed not to be looking at the screen. Not unlikely to be. Guaranteed.
The count that follows from this
On my own phone, in one ordinary day, sensor accesses fired 340 times for the camera and 28 for the microphone. I saw none of them.
Not "I missed a few". None. Because on any given day my phone is in a pocket, in a bag, face down, charging in the kitchen, or on the nightstand — and the number of hours it spends held in front of my face with my eyes on the top-right corner is close to zero.
Android recorded every one of those accesses and told me about none. The full log is here, including the one at 11:43 that was flagged as background access.
What to do with this
Two things, both free.
Read yesterday. Settings → Privacy → Privacy dashboard → Camera, then Microphone. Android keeps 24 hours of it on Android 12, 7 days from Android 13. When you look, read it with placement in mind: an access at 3am is a different object from an access at 3pm, even though the dashboard prints them identically.
Cut the list down. Settings → Privacy → Permission manager → Camera and Microphone. Anything that doesn't need a sensor shouldn't have it — full walkthrough here. This is the highest-value ten minutes available to you.
And if you want the part that watches when you can't: Spytrap alerts you the second an app opens your camera or mic — including on the lock screen, which is the whole point — and logs which app, when, for how long, and whether your screen was locked, with background access flagged as background.
One-time $0.99, on-device, no account, nothing uploaded.
Where is your phone right now? Could you see the dot from where you're sitting?
Get Spytrap on Google Play — $0.99 →