Loading today’s stories
Build1 distinct publisher3 min readPublished
The ongoing foreground-service notification can be denied, dismissed or missed, so if you need to prove a repurposed handset is recording, the durable evidence sits in the two indicators the Compatibility Definition Document mandates and no app can reach.
The Engineer · Build desk
Compiled by The EngineerSomething wrong?How this is made
Start with what the platform actually forces. Background recording needs a foreground service, and Google's documentation says apps "must include a notification when they start a foreground service" [6]. Separately, the same guidance says apps do not need the POST_NOTIFICATIONS permission in order to launch a foreground service [10]. The object is required at service start; whether a human ever sees it is settled by a different permission [10].
The platform does block one obvious dodge. An app cannot push that notification below PRIORITY_LOW without the system adding its own message to the drawer [7]. Quiet ranking is not a hiding place. Denial is: Android 13 turned notifications into a runtime permission and foreground services were not exempted [8], and Google's text is explicit that users who deny it "don't see notices related to foreground services in the notification drawer" while "users still see notices related to foreground services in the Task Manager, regardless of whether the notification permission is granted" [9].
Note the vocabulary. The platform text says Task Manager; the write-up calls the same surface the Active apps list in the notification drawer [4][9]. A test plan that greps the docs for "Active apps" comes back empty.
The version arithmetic decides how much of this protects a repurposed handset. The status-bar camera indicator starts at Android 12 and the Active apps list at Android 13 [3][4], both as Compatibility Definition Document requirements that neither the device nor the app can switch off [5]. A phone on Android 11 has neither, which leaves the deniable notification as the entire disclosure surface [20]. A phone on Android 12 has one of the two [21]. Android 13 is the first release carrying both mandated indicators, and also the release that made the notification deniable and dismissable by default [22]. The signals you cannot suppress arrive on the same schedule as the off-switches for the one you can.
On dismissal, the two first-party pages contradict each other. The Android 13 behaviour-changes page says users can dismiss notifications associated with foreground services by default on Android 13 or higher [12]. The Android 14 page claims the change for itself and says the behaviour of FLAG_ONGOING_EVENT changed to make such notifications actually dismissable [13]. Both are live and carry the same last-updated date, so both cannot be a complete description [14]. Only the Android 14 page states exceptions, and they matter: the notification stays non-dismissible when the phone is locked and when the user hits Clear all [15]. That page also excludes whole categories, including CallStyle notifications, media notifications, enterprise device-policy controllers and the default Search Selector package, and a third-party camera app is none of those [16]. The Android 13 sentence's own supporting link points at an anchor that its target page no longer contains [17]. For the Android 13 wording to transfer to your build, it would have to describe the same code path with the same exception list, and it publishes no exception list at all.
So I would take the write-up's recommendation as written: cite Android 14 for the dismissal behaviour, and test dismissal on the phone you are actually deploying [18]. The author states that every claim is quoted from Google's developer documentation, the AOSP platform docs or the Compatibility Definition Document, with gaps named where the documentation is silent [24], and that the app in frame, Background Camera RemoteStream, is bound by every one of these rules like any other app [25]. My addition is about where the assertion lives. The drawer entry is the signal teams were taught to look for and the only one that goes away [19]; the indicator and the Task Manager entry are the two an app has no documented way to touch [5].
Ranked by verification strength, evidence, and original report placement.
The write-up argues that for an old Android phone run as a security camera, the system-mandated notification is the one thing standing between a camera running in the background and a hidden camera.
The write-up says the user can deny the notification, dismiss it, or simply not see it for the first ten seconds: three documented mechanisms, added in three separate Android releases.
The camera indicator in the status bar exists on Android 12 and up.
The Active apps list in the notification drawer exists on Android 13 and up.
Both the status-bar camera indicator and the Active apps list are required by Android's Compatibility Definition Document, and neither the device nor the app can switch them off; an app has no documented way to touch either.
Background recording requires a foreground service, and Google's docs say apps "must include a notification when they start a foreground service."
Distinct publishers with included, body-backed reporting in this cluster.
dev.to
1 article · September 2, 2026
Follow any of these and your For You feed starts watching them — no settings page required.
build
Geofencing beats GPS polling on power, then loses to the OEM battery optimiser1 distinct publisher
product
Google's latest Android update adds a car-sickness overlay among new features1 distinct publisher
security
The EncroChat "national security secret" was exploit code sitting on GitHub1 distinct publisher
product
Google explained Pulse to a press outlet before it explained it to Android users1 distinct publisher
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
First-party quotes, one set of eyes
The raw material is the right material: platform behaviour-change pages, the permission guide and the Compatibility Definition Document, quoted rather than paraphrased, with release floors specific enough that a reader can falsify them on a handset. What holds the score down is that a single dev.to byline did all the quoting, nobody re-checked the pages, and the author reports two of the supporting links — the Android 13 dismissal anchor and the Android 12 exceptions list — as dead, which means part of the documentary trail cannot be walked at all.
Nothing counted
Not one number in this reporting describes the world: no share of handsets on Android 11 or lower, where neither mandated indicator exists, no count of devices where dismissal was actually tested, no install or usage figure for the app named in the text. The story is about what the platform promises, and it never crosses into what shipped hardware does.
Caveats arrive before the conclusions
The headline sounds like a debunking, but the piece consistently argues down from its own findings: it says 'no documented way' rather than impossible, flags where Google is silent, and ends by telling you to test the handset instead of trusting the page it just recommended. If anything it undersells a useful practical result — that two disclosure surfaces sit outside app control — because it will not claim more than the documents say. What keeps this from sitting further below zero is that nothing was tried on a real phone, and closing that gap is left entirely to the reader.
The conclusion flatters a camera app
A developer blog post that names Background Camera RemoteStream and concludes that Android's un-removable indicators, not the app's own notification, are the durable proof of recording is a conclusion any background-camera vendor would happily publish. The relationship between author and app is never stated. Two things cap the concern: the argument is built out of quotable Google documentation rather than product claims, and it hands the reader more ammunition against camera apps in general than for this one.
Trust the ordering, not the edge cases
We are reasonably sure of the shape of this story — three ways the notification vanishes, two surfaces an app cannot reach — because it is anchored in documentation any reader can pull up. We are much less sure about specifics on any given phone: the dismissal question is unresolved in Google's own pages, no device was tested, and there is no second publisher to catch a misread quote. That combination sets a ceiling well below where a documentation-quoting piece would otherwise land.