Unblock Contact Android < Instant ✦ >
Unblocking via the Contacts app must issue a ContentResolver.delete() on BlockedNumberContract.BlockedNumbers.CONTENT_URI and update the raw_contacts table. If either transaction fails (e.g., database lock), the contact appears unblocked in the UI but remains blocked by the telephony stack. 4. The Unblock Transaction: Atomicity Analysis Executing an unblock triggers the following sequence (Android 13+):
// Simplified sequence from BlockedNumberProvider.java public int delete(Uri uri, String selection, String[] selectionArgs) // 1. Validate caller has WRITE_BLOCKED_NUMBERS permission // 2. Acquire a database write lock on blocked_numbers.db // 3. Delete the row matching the normalized phone number (E.164 format) int rowsDeleted = mDb.delete(TABLE_BLOCKED, whereClause, args); // 4. Trigger a ContentObserver notification to TelephonyManager Intent intent = new Intent(TelephonyManager.ACTION_BLOCKED_NUMBER_REMOVED); mContext.sendBroadcast(intent, BLOCKED_NUMBER_PERMISSION);
Even after unblock, the fact that the number was blocked remains recoverable via the deleted flag in telephony.db for up to 30 days. 9. Performance Benchmarks Unblock latency across Android versions (measured on Pixel 7, averaged over 100 runs): unblock contact android
| Artifact | Path / Key | Value on Unblock | | :--- | :--- | :--- | | settings.db | secure:blocked_numbers_list | Entry removed | | call_log | CALL_BLOCK_REASON | Changed from 1 to 0 (but old log retained) | | logcat (kernel) | Event: 0x12f4c | BLOCKLIST_REMOVE action logged | | telephony.db | carriers/blocked_entries | deleted=1 (soft delete) |
Look at carrier_blocked_timestamp in call_log . If this timestamp is after the user's unblock action, the carrier is overriding the OS. 7. Android 14+ Auto-verify and Spam Persistence Android 14 introduced "Auto-verify" (Google Play Services) and "Verified SMS." These features create a third-party spam score attached to a number, stored in Google's SafetyNet database (cloud-side). Unblocking via the Contacts app must issue a ContentResolver
Between step 3 and step 5, an incoming call can still be rejected because the telephony stack's mBlockedNumbers cache hasn't been invalidated. Typical window: 50-150ms . 5. The "Ghost Block" Phenomenon A persistent issue in Android 12-14 is the Ghost Block — a contact appears unblocked, but SMS/MMS messages still fail to arrive.
| Storage Location | URI / Path | Purpose | | :--- | :--- | :--- | | | content://com.android.blockednumber/blocked | Primary source of truth for telephony. | | Contacts DB | data/data/com.android.providers.contacts/databases/contacts.db (Table: raw_contacts ) | Marks STARRED (0) and CUSTOM_RINGTONE (null) but also flags CONTACT_STATUS for blocked. | | Call Log | content://call_log/calls | Adds CALL_BLOCK_REASON column (Value: 1 for user block). | | SMS Provider | content://sms/blocked | Isolated blocking for Messaging app. | Delete the row matching the normalized phone number (E
// 6. Force a contacts provider sync val cr = context.contentResolver cr.update(ContactsContract.RawContacts.CONTENT_URI, ContentValues().apply put("contact_blocked", 0) , "phone_number = ?", arrayOf(normalized)) Unblocking a contact on Android is a distributed transaction problem, not a simple state change. The complexity arises from the fragmentation between telephony, SMS, contacts, and carrier systems. As of Android 15, the platform is moving toward a unified BlockedNumberService API that promises eventual consistency within 500ms. However, for older devices (Android 12 and below), a full unblock is only guaranteed after a device reboot or a carrier network cache timeout — a fact rarely documented in user-facing help articles.