So this has been happening to my N9 the past couple weeks here and there.
When I send a text to one person in my contact list, all of a sudden it appears that it sends a text to another person in my contact list. The name changes in the header. The person I intended to get my text gets the text, but it gets threaded in the wrong contact conversation all together. If I erase all my messages it works normally but then after a week or two this behavior returns.
Any ideas of what is going on, or any way to fix it? I've did a little searching but I don't see anyone else with this issue.
This issue has been discussed earier in similar threads with no definite solutions...The thing is its not that prevalent and I've tried much but unable to replicate it...
Maybe look thru' tracker's .db files to investigate but other than that I can't think of much that could avoid/solve this bug...
I did an OTA update but it was not from a clean flash, I'd reflash it but the only issue is that the only computer I have access to right now at least till the end of the month is my work laptop and there is security on there that won't let me run flasher.
If this persists I'll reflash, anyone have any other ideas?
This particularly happens with me when I have a Message lying from a Sender who is not in my Contacts, mostly from non-cellular Sender.
Like some Institutions or Retail company sending promotional msgs, so the Sender number/name appears like '5402' or 'NBC' as such.
Later when I try to compose a new msg to someone from my Contacts, it will go through as defined. But later, this new sent msg will be lying under above mentioned Senders...
In short, it messed up... with 2 different messages lying under 1 Sender. Whereas it should be 2 different messages lying under 2 different Senders...as usual.. Isnt it ???
I haven't had this at all, and I send approx. 100 messages/day to at least 4 or 5 different contacts.I had similar with wazapp, but that was a bug in that software, not with Harmattan.
Neither one of my N9's nor my N950 (all with PR1.3) have ever had the issue.
It was most likely an issue in the OTA procedure, stuffing up tracker. The best (and seemingly permanent solution) is to do a full flash (rootfs + emmc).
