|
The hardest part is tracking down the person id if you have a lot of contacts. I had an opportunity to exercise this fix today because of something strange the messaging app did last night. I got a text from someone yesterday that I did not have a contact entry for (not sure why, because I have texted them before). That established a chat thread for this person using the phone number as the display name. I then saved the number to my contacts by tapping the header and selecting add to contacts, then add to new contact. I typed the person's name and saved it. The display name for the chat thread was then updated with their name. This morning I went to send them another message, and the chat thread was locked! So there's one scenario where it can happen, which does not make sense to me.
To fix it, you have to get the id of the chat thread and the person using Impostah. The easiest thing to do is save the object to a file while viewing it in Impostah (you will prob have to change the filename, as the display name for the chat thread and person id are likely the same, and that is what is used for the default filename. I prefixed the chat thread filename with "chatthread"). Finding the person id can take a while if you have a lot of contacts. Then run this command, filling in the chat thread id and person id. The phone# is probably not required, but I supplied it anyway, just copying the value from the chat thread.
Code:
#Person object and chatthread object saved from Impostah so we can grab the chatthread id and person id for the merge command.
#Update chat thread person id and locked flag. Reply address prob not necessary (it is not changing)
luna-send -n 1 -a com.palm.app.messaging luna://com.palm.db/merge '
{"objects":[{"_id":"XXXXXXXX","personId":"XXXXXXX","flags":{"locked":false},"replyAddress":"(999) 555-1212"}]}'
#Get chatthread to confirm changes.
luna-send -n 1 -a com.palm.app.messaging luna://com.palm.db/get '{"ids":["XXXXXXXX"]}'
|
|
|