Contact Android [new] - Unblock

| 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 |

After unblocking, the user must open the Phone app → Settings → Caller ID & Spam → "Delete spam feedback history" for that specific number. 8. Forensic Artifacts of Unblocking For digital forensics, an unblock operation leaves distinct traces: 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

return rowsDeleted;

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. Google Messages and Samsung Messages use a periodic

// Delete from telephony provider context.contentResolver.delete(BlockedNumbers.CONTENT_URI, ...) // Also delete from SMS provider context.contentResolver.delete(Uri.parse("content://sms/blocked"), ...) // Force sync via Carrier Messaging Client SmsManager.getDefault().clearBlockedNumberForSubscriber(subId, phoneNumber) Carrier Call Filtering: For RCS (Rich Communication Services) and VoLTE, carriers (T-Mobile, Verizon, Jio) maintain their own block list on the IMS core. When a user unblocks a contact on Android, the OS sends a CarrierConfigManager update via the TelephonyManager . However, if the carrier's network has a stale cache, the number remains blocked at the network level for up to 24 hours .