@computerinfo21 I think you'll find it more problematic when messages have a null group_uid than a missing remote_uid.. it's group_uid that lets the phone assign a message to a conversation... e.g. if I text these numbers: +447711223344 07711223344 00447711223344 (for most countries where 00 is the international escape code) It goes to the same person but the remote_uid field is different in each case. As is standard with phones, they take the last 7 digits and assume it's unique to a contact, thus removing the problem that prefixes cause the same number to appear differently Try it by calling your friend, but swap some number *not* in the last 7 digits, for another.. Phone will say youre calling ur friend, but the call wont connect For SMS in el.db the group_uid is the last 7 digits of the phone number.. Its also used in groupcache and from what I've seen so far groupcache is the table that influences the appearance of the message list (error icons, unread msgs etc)
you should also take care to truly only implement fixes of the nature described here on rows where service_id = 3 (sms) because you may end up screwing up your calls and chat lists if you apply blanket changes to services 1 (calls) and 2 (chat)