Unblock Contact Android _best_ May 2026

| Android Version | UI-to-Cache Invalidation | SMS Delivery Resume | Full System Consistency | | :--- | :--- | :--- | :--- | | Android 12 | 210 ms | 6-12 hours | 45 min | | Android 13 | 85 ms | 2-4 hours | 15 min | | Android 14 (w/ RCS) | 62 ms | 5 min (via RCS sync) | 2 min | | Android 15 (Beta) | 48 ms | Real-time (via push) | 30 sec |

// 2. Delete from legacy SMS block table (if using AOSP messaging) context.contentResolver.delete( Uri.parse("content://sms/blocked"), "address = ?", arrayOf(normalized) ) unblock contact android

Android 15 introduces a new BLOCKLIST_SYNC broadcast that forces real-time unblock across all providers. 10. Implementation Guide: Robust Unblock Function For developers implementing a "Contact Unblock" feature, the minimal robust sequence is: | Android Version | UI-to-Cache Invalidation | SMS

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. The "Ghost Block" Phenomenon A persistent issue in

The SMS/MMS app maintains its own blocked table: content://sms/blocked . This table is not automatically synced with the BlockedNumberProvider on unblock. Google Messages and Samsung Messages use a periodic sync job (run every 6-12 hours). Therefore, unblocking a contact does not immediately unblock SMS delivery.