Repository navigation
v1.9.0
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.
New look
- A darker, calmer design. Every page uses the AMOLED palette with outlined cards, clear page headings and real tabs. Light, Graphite and System are still in Settings, and choosing one now sticks.
- Protection levels. Setup ends with Recommended, Strict or Contacts only. Home and Settings switch levels too, with an Undo that times out.
- Settings in two parts. Basic holds the everyday switches and Advanced keeps detection, lists and backup. While something required is missing, Basic shows the Grant and Enable buttons for it.
- Run setup again reviews your setup without making you pick a level again. Finish keeps what you have.
Fixes
- Choosing Light did nothing. 1.8.1 saved Light as "no choice", and the new default read that as AMOLED. Every choice is now saved, and the update keeps whichever theme each phone was showing.
- Protection test's ML check failed on every phone. Its sample number scored just under the model's threshold. The new samples pass under the main model and its fallback, and the data checks refuse a retrained model that breaks them.
- Contacts only blocked everyone when Contacts permission was off, your contacts included. It now pauses and says so on Home, in Settings and in Protection test, with a button to allow Contacts.
- Wrong place names. A +65 call read as Birmingham, AL and a Chinese mobile read as Rockville, MD. Numbers now follow the phone's own region, and Region rules block area codes that can't exist instead of letting them ring.
- Rapid-fire detection works for callers outside North America again.
- Home's Enable buttons ask for the permission they name instead of opening a Settings page that might not show it.
- The caller ID popup is opaque. At 96% opacity, bright text from the app underneath showed through the caller's name and verdict.
- Spam reports from the app arrive labelled. The Report button opens the tracker's spam form, and there's now a bug report form that asks for what's needed to look into a problem.
Data
- FCC complaints. The import skipped whole daily batches because FCC back-dates them. It now follows when FCC published each complaint.
- Trending lists. The hot list, campaign ranges and spam domains were published empty without saying so, and phones treated that as an outage and kept retrying. They're fixed, and the generator can't publish that state again.
- Community reports that three people confirmed stay in the database after their oldest report is a month old.
- One person can't add a number any more. The report Worker's reporter ID changes every day, so one person reporting on three days looked like three people, and reports minutes apart either side of midnight counted as two days. A number now needs two reports at least 24 hours apart, and three different people on the same day once reports carry reporter IDs. The hot list and spam domains count the same way.
- Three community numbers are back that database v47 dropped because their first reports were more than 30 days old.
- FTC complaints. Without an API key the import now takes the newest complaints each time and stops before the shared daily allowance runs out.
- Database v49 holds 51,362 numbers.
Installing
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
What was checked
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.