Well, may be I was not clear from my previous message. I noticed that a reboot was necessary but my problem is still there. All my messages are in the file but not all threads are displayed.
Posts
-
RE: history.sqlite reconstruct threads
-
RE: history.sqlite reconstruct threads
@advocatux Yes, I noticed that the service history needs a reboot to take into account a new sqlite file.
-
RE: history.sqlite reconstruct threads
@advocatux, that's obviously what I did first (with rsync instead of adb). But it is not working. May be My app messaging was not in the latest version when I migrated my device ? But I had no notifications...
Well I don't know the reason why it was not working. -
history.sqlite reconstruct threads
Hi everyone,
I just migrated my E4.5 to ubports. When I restored my backup, the messaging app was not working. When I opened it, the rotating circle was present and nothing happened event after 10 hours... I realized that my old history.sqlite was probably the problem. So I had to import manually my messages from my old history.sqlite to the new one (probably because the table structure is not the same : other table/columns are in the ubports database).
So it's ok for the messages themselves. But I can't see them in the message app, I need to send a message to someone in order to get the thread displayed (or at least that an event is created with someone).
I tried to copy manually my old threads table in the new database, but it doesn't work.
And this is my question : Does someone know how to reconstruct correctly the thread ?Tks.