How to Fix Mismatched Contact Data on Your Android Device

How to Fix Mismatched Contact Data on Your Android Device

A number of Android users have been complaining about contact data mismatch which is turning their whole phonebook into a mess. The issue is primarily being reported by Redmi Note 4, Redmi 4, Mi 5 owners, though some other Android device owners have also been complaining about the same issue. 

The issue stems from the fact that for some reason, the contact data of one person is being merged with another. So, for example, if you have ‘A’ and ‘B’ in your contact list, their data is merged so A can become ‘AB’ with contacts number for both individuals showing up under one. In other cases, a single number ends up showing up as the default number for all contacts in one’s phonebook.

This is creating a lot of confusion among Redmi users, with many of them clueless on how to fix it. It is unclear if the issue is occurring due to WhatsApp or Truecaller or an underlying bug in Android OS itself. Whatever the case might be and whoever is to blame here, that does not solve the problem of your contact data mixing up.

Thankfully, since the problem primarily affects Redmi device owners, Xiaomi has released a fix for this problem.

Fix Contact Data Mismatch on Redmi 4, Redmi Note 4, Redmi 4A, Redmi 5A, and Other Android Devices

Step 1: Download the Contact Corrector APK from here and install it on your device.

Step 2: Open the app and tap the Check button. It will then automatically go through your contact list and identify the contacts with data mismatch issue.

Step 3: Once identified, simply tap Correct for the app to fix the mismatch data of all identified contacts. This should hopefully fix the contact mismatch issue for all the contacts in your phonebook.

To avoid the issue from occurring again, make sure to disable syncing for WhatsApp and Truecaller from Settings -> Sync. 

If the above fix works for you, drop a comment and let us know about it! Also, don’t forget to let us know which device you were using on which you faced the issue.