Sprint Diamond / WM 6.1: After backup, threaded texts display in incorrect order

[exi]

Last night, I used PIM Backup 2.8 to backup my call log and text messages. I use OggSync for contacts and calendar, so I didn't bother with those.

Then came the three-hands-almost-requred hard reset.

After all that, and after reinstalling OggSync to get my contacts back on there, I restored my call log and text messages. Interestingly, the call log correctly resolved all contact numbers to their names (which wasn't happening as I described in my previous thread about that).

The problem: my text messages are clumped by sender in their threads with their respective recipients, not ordered by timestamp as they should be. There were almost 2,000 of them, and I know it can take time to process, but this was done last night.

I tried changing from threaded to classic, rebooting, and changing back to threaded and rebooting again. Tried leaving the messenging app open. Neither seems to help.

Thoughts?

[exi]

bump.

[makkonen]

I've had this same problem, backing up both with PIM Backup and with PowerSMS. That it happens with both seems to point to the problem being something fundamental to the way messages are timestamped/sorted, and how they get reinserted into the database from a backup.

Here's a thread from xda that seems to suggest it's fixable. The most promising idea seems to be to wipe the sms box clean, and then turn off threading -> restore -> turn on threading. (I, like you, tried turning theading off and back on, but the messages were already inserted at that point.)

http://forum.xda-developers.com/show....php?p=2663807

Of course, post #1 in that thread also says that if you use powersms you don't have to worry about it, and that isn't my experience. (I might be using an old version, though.)

I'll probably play with it next time I flash a rom, but I don't care about misthreaded sms that much until that point.

[exi]

Originally Posted by makkonen

I've had this same problem, backing up both with PIM Backup and with PowerSMS. That it happens with both seems to point to the problem being something fundamental to the way messages are timestamped/sorted, and how they get reinserted into the database from a backup.

Here's a thread from xda that seems to suggest it's fixable. The most promising idea seems to be to wipe the sms box clean, and then turn off threading -> restore -> turn on threading. (I, like you, tried turning theading off and back on, but the messages were already inserted at that point.)

http://forum.xda-developers.com/show....php?p=2663807

Of course, post #1 in that thread also says that if you use powersms you don't have to worry about it, and that isn't my experience. (I might be using an old version, though.)

I'll probably play with it next time I flash a rom, but I don't care about misthreaded sms that much until that point.

Wonderful link - thank you.