Open-source spam call and text blocker for Android. GitHub-hosted spam database, no API keys, no subscriptions.
Repo SysAdminDoc/CallShield, read from GitHub 1 min ago. SysAdminDoc has not joined Take My Repo.
Spanish and Brazilian Portuguese are in the app now, and a strict offline switch under Advanced stops every network request while blocking keeps working from the database on your phone. Long-press calls in Recent or the Blocked log to block or report several at once. You can mark a number that never calls you, like the line on the back of your bank card, and a call showing it gets blocked even when it's saved in your contacts. On a tablet held sideways, a number's page opens next to the tabs. Everything that changed is below, and under v1.14.0 in CHANGELOG.md.
scripts/neighbor_spoof_report.py reruns the count on newer complaints.*21*, **21* and the other GSM codes, Verizon's *72, Jio's *401*) now gets a warning of its own. Dialing one sends your calls to someone else, including the calls banks make to confirm it's you, so the warning says that and how to undo it with ##002# (*73 on Verizon). It shows even with text screening off, and Lookup's message check explains it the same way. Codes that only check or cancel forwarding aren't flagged.--allow-collapse. That flag turns the shrink check off for every feed the run writes, which was far more than a feed staying empty called for. Staying empty after a published clear deletes nothing, so the check lets it through now, and a feed with rows behind it still can't go empty without both flags.scripts/device_smoke.py deletes its last screen dump before taking a new one. A dump that failed used to leave the old file in place, so a step could act on labels from the screen before.Download CallShield-v1.14.0.apk below and install it over your current version. Releases since v1.7.37 share one signing key, so the update keeps your settings and blocklist.
Signer certificate SHA-256:
92:0E:58:3A:E6:CE:9F:38:63:A6:B3:B8:84:7E:92:7D:53:A6:6C:38:A2:45:E1:2E:30:CE:12:4C:9F:4A:75:F5
2,314 JVM unit tests and the 26 data pipeline suites pass, along with lint, detekt, ktlint and the release build's drift, SBOM and reproducibility checks. The 134 instrumented tests pass, 130 of them on a Galaxy S25 Ultra with Android 17 and the four notification tests on a Galaxy S22 with Android 16, and that includes every database migration up to the new 21 to 22 step. On the S22 I installed 1.14.0 over 1.13.0, the copy it had run since October 30. It opened on 1.14.0 with no crash, and setup and the synced database carried over. This APK also went on the S25 over the 1.13.0 download from its release page and opened to setup with no crash. The release smoke pass went 9 for 9. That covers the database sync, What's new showing this version, and the recommended lists. A Paris number offers to block all +33 1 numbers in Lookup and on the number's screen, Undo takes that rule back off, and a Japanese number gets no offer. Not spam followed by Undo sent nothing, and Report spam number in More opens Lookup. The tablet and foldable layout ran on a foldable emulator, and so did the 10 minute wait before protection can be turned off after a call from a number you don't know. No real call or text went through CallShield on either phone.
Report on a number's screen or in Lookup now blocks the number on your phone too, with Undo, and the Rules screen can sort its Blocked list and act on many rows at once. Links in WhatsApp, Signal, Gmail and the other chat apps you screen are checked only against the OpenPhish list CallShield keeps on your phone. On Android 15 and later, a one-time code Android hides is left alone, and a code that shows up during a call from an unknown number still gets a warning. Everything that changed is below, and under v1.13.0 in CHANGELOG.md.
scripts/device_smoke.py runs the release's phone checks over adb and prints PASS or FAIL for each one. They cover sync, What's new, the recommended lists, both area code offers with Undo, a number with no offer, Not spam's Undo and More's Report spam number. --report adds Report's block and Undo, and it sends a real report.(\d{3}){3}, and suggests the simple form. It used to save the rule, show it as active, and never match a call with it.+15551234567 # 3 reports) read the comment's digits as part of the number, and a comma in that comment could make the whole list read as CSV. Lists that start with a byte-order mark also lost a JSON list's format, its own refresh interval, or a CSV list's first column name.Download CallShield-v1.13.0.apk below and install it over your current version. Releases since v1.7.37 share one signing key, so the update keeps your settings and blocklist.
Signer certificate SHA-256:
92:0E:58:3A:E6:CE:9F:38:63:A6:B3:B8:84:7E:92:7D:53:A6:6C:38:A2:45:E1:2E:30:CE:12:4C:9F:4A:75:F5
2,134 JVM unit tests and the 24 data pipeline suites pass, along with lint, detekt, ktlint and the release build's drift, SBOM and reproducibility checks. The 134 instrumented tests, database migrations included, pass on a Galaxy S22 with Android 16. On that phone I installed 1.12.0 fresh, went through setup and synced the database (51,407 numbers), then installed this APK over it. Setup, the synced database and CallShield's call screening role all carried over, with no crash. The in-app changelog shows 1.13.0, and Settings lists the same four recommended lists as before. A Paris number offers to block all +33 1 numbers, both in Lookup and on the number's screen, and Undo takes the rule back off. A Japanese number gets no offer at all. Not spam followed by Undo sent nothing. Report spam number in More opens Lookup. Report on a number from the FCC complaints now says it's blocked on this phone, and Undo lifts the block. The report itself reached the community queue a second later. The phone has no SIM, so no real call or text was screened.
Reports from other CallShield users now show up as a "not confirmed" label that never blocks a call by itself, and Report on a number's screen finally sends the anonymous report that counts. Home can also spot a slow campaign that calls from a new number in the same exchange every day and offer to block that exchange. Everything that changed is below, and under v1.12.0 in CHANGELOG.md.
adb install.Download CallShield-v1.12.0.apk below and install it over your current version. Releases since v1.7.37 share one signing key, so the update keeps your settings and blocklist.
Signer certificate SHA-256:
92:0E:58:3A:E6:CE:9F:38:63:A6:B3:B8:84:7E:92:7D:53:A6:6C:38:A2:45:E1:2E:30:CE:12:4C:9F:4A:75:F5
1,968 JVM unit tests and the 23 data pipeline suites pass, along with lint, detekt, ktlint and the release build's drift, SBOM and reproducibility checks. On a Galaxy S22 with Android 16 I installed this APK over 1.11.0 and synced the database (51,368 numbers). The in-app changelog shows 1.12.0, and Settings lists four recommended lists with Lista Hũ among them. A Paris number's screen offers to block all +33 1 numbers, and Undo takes the rule back off. A Japanese number gets no offer at all. Not spam followed by Undo sent nothing. Report on a number from the FCC complaints went through, and My reports shows it as sent. Protection test passed 25 of 28. The misses were the same as last time, SMS interception (Android 16 treats it as advisory), notification access and the phone's own security patch level. The phone has no SIM, so Home's exchange suggestion stays hidden (it needs the phone's own number) and no real call or text was screened.
Better at the calls and texts that scams lead to, and your own lists now survive a damaged database. The complete list is under v1.11.0 in CHANGELOG.md.
evil.com.), a user name in front of the host (paypal.com@evil.com) or a backslash (evil.com\@paypal.com) no longer hides the real one.Download CallShield-v1.11.0.apk below and install it over your current version. Releases since v1.7.37 share one signing key, so the update keeps your settings and blocklist.
Signer certificate SHA-256:
92:0E:58:3A:E6:CE:9F:38:63:A6:B3:B8:84:7E:92:7D:53:A6:6C:38:A2:45:E1:2E:30:CE:12:4C:9F:4A:75:F5
1,831 JVM unit tests and the data pipeline suites pass, along with lint, detekt, ktlint and the release build's drift, SBOM and reproducibility checks. On a Galaxy S22 with Android 16 I installed this APK fresh, finished setup and synced the database (51,363 numbers). The in-app changelog shows 1.11.0, Settings lists the three recommended blocklists from the catalog that ships inside the app, and Lookup flags the Munich number from #27 as a reviewed database entry. Protection test passed 25 of 28. The misses were SMS interception, which Android 16 treats as advisory, notification access, which I skipped in setup, and the phone's own security patch level. The test phone has no SIM, so no real call or text was screened. The callback hold, the code warning and the text checks were covered by their tests rather than on the phone.
There's a newer CallShield. This version still updates its spam data, but it won't tell you about new releases unless you turned on update checks in Settings. Get the latest release and install it over this one. It updates in place and your settings stay.
Let unknown callers ring when you're waiting for a call, plus a fix that keeps the spam database blocking between updates. The complete list is under v1.10.0 in CHANGELOG.md.
data/spam_numbers.txt, one number per line, signed like the app's feeds.Download CallShield-v1.10.0.apk below and install it over your current version. Releases since v1.7.37 share one signing key, so the update keeps your settings and blocklist.
Signer certificate SHA-256:
92:0E:58:3A:E6:CE:9F:38:63:A6:B3:B8:84:7E:92:7D:53:A6:6C:38:A2:45:E1:2E:30:CE:12:4C:9F:4A:75:F5
1,640 JVM unit tests and the data pipeline suites pass, along with lint, detekt, ktlint and the release build's drift, SBOM and reproducibility checks. On a Galaxy S22 with Android 16 I installed this APK fresh and finished setup. I started Expecting a call from Home and from the Quick Settings tile, watched the countdown notification, and ended it with End now. In Lookup, a database number was let through during the window and flagged again after it, and the Munich number from #27 is flagged from the synced database. Protection test passed 25 of 28. The three misses were notification access, which I skipped in setup, SMS interception, which Android 16 treats as advisory, and the phone's own security patch level. The test phone has no SIM, so no real call was screened, and the caller ID popup screenshot in the README predates this release's TalkBack changes.
A redesign of every screen, protection levels you can switch in one tap, and a long list of fixes from a full review of the app and its data pipeline. The complete list is under v1.9.0 in CHANGELOG.md.
Download CallShield-v1.9.0.apk below and install it over your current version. Releases since v1.7.37 share one signing key, so the update keeps your settings and blocklist.
Signer certificate SHA-256:
92:0E:58:3A:E6:CE:9F:38:63:A6:B3:B8:84:7E:92:7D:53:A6:6C:38:A2:45:E1:2E:30:CE:12:4C:9F:4A:75:F5
1,580 JVM unit tests and 20 pipeline suites pass, along with lint, detekt and ktlint. On an Android 15 emulator I checked Home, the Blocked log, Lookup, the caller ID popup on an incoming call, Protection test (26 of 28; the two misses are the emulator's RCS listener and its security patch level), Settings and More, plus the contacts-only pause and the Enable buttons. The outgoing-call warning wasn't checked this time, because the emulator drops outgoing calls after a second. The report Worker's new rate limits are in the code and take effect at its next deploy.