jev-block-android-ad
Android notification and SMS noise gate: local OTP and blacklist rules first, then Jev decides what is noise, failing open on uncertainty.
Overview
JevNoiseGate is an Android app that filters unwanted notifications and SMS. Instead of brittle keyword lists, which eventually swallow verification codes and miss novel ads, it asks Jev whether each message is noise and suppresses only what the model explicitly flags. Every uncertain path, including network failure, missing credentials, timeouts, HTTP errors or a category outside the configured answer set, resolves to allow, enforced in one DecisionMapper.
Two mechanisms deliberately stay local: an OTP gate that matches verification-code shapes and allows the message with no network request at all, observable via an upload counter on the diagnostics screen, and an exact-match SMS sender blacklist that blocks without a network call. Notifications and SMS share one pipeline that runs OTP gate, blacklist, then the model. The author's reasoning is that leaking one ad is a moment of annoyance while swallowing one code can cost an account. The app is MIT licensed, with a TypeSafe client ported from MIT upstream work.
What the decision model decides
| Type | Question | Answers |
|---|---|---|
| Choice | Is this notification or SMS noise (e.g. advertising) or legitimate?(inferred) | — |
How it works
- Notification or SMS arrives
- OTP gate allows verification codes locally
- SMS blacklist blocks known senders locally
- Jev classifies the rest; only explicit noise is suppressed
- Any failure allows the message
Strengths
- Verification codes never leave the device
- Fails open, so important messages are not lost
- Hard rules work without network
Caveats
- Non-OTP message text is sent to the API
- Ads may leak through when the model is unsure
At a glance
- Type
- Project
- Status
- beta
- Language
- Kotlin
- Runtime
- Android app
- Has code
- yes
- License
- MIT
Use cases and integrations
How curated lists describe it
An Android notification and SMS filter that applies local OTP rules before asking Jev whether a message is advertising noise.
logicrw/awesome-jev-projectsJevNoiseGate filters unwanted notifications and SMS on Android. Rather than matching keywords, an LLM decides what's noise — and only what it explicitly flags is blocked. Verification codes are matched on-device and never uploaded; anything uncertain passes through.
hellogumbo/awesome-jev
Frequently asked questions
What does Jev decide?
Whether each non-OTP notification or SMS is noise to suppress.
Are verification codes sent to the API?
No. They are matched on-device and no request is made.
What happens on errors?
Every uncertain or failed path allows the message.
Related projects
Chrome extension that uses your Jev key to hide high-confidence sexual and solicitation replies on X behind reversible placeholders.
Browser extensionproductionTypeScriptChrome extension and Workers API that score X posts and replies for AI writing, solicitation and paraphrase bots using Jev.
Browser extensionbetaTypeScriptChrome/Edge extension that flags low-quality, spam and promoted X posts with Jev and overlays a translucent STOP or AD watermark.
ProjectbetaJavaScriptChrome extension that labels every X post you scroll past with six typed Jev questions and shows a live cost counter.
Browser extensionbetaTypeScriptChrome extension that scores each X timeline post with one batched Jev Noul request for engagement value, virality and tags such as spam.
Browser extensionprototypeJavaScriptChrome and Firefox extension that hides AI-written posts on X, LinkedIn, Reddit and YouTube by asking Jev 30 narrow style questions.
Browser extensionproductionJavaScript