The Following User Says Thank You to demonspectre For This Useful Post: | ||
![]() |
2011-03-23
, 08:29
|
Posts: 49 |
Thanked: 7 times |
Joined on Apr 2010
|
#52
|
![]() |
2011-04-02
, 00:15
|
Posts: 92 |
Thanked: 6 times |
Joined on Jul 2010
|
#54
|
Deletion of the DB has been covered before and hopefully shouldn't be necessary.. refer to my post #40: http://talk.maemo.org/showpost.php?p...2&postcount=40
- Follow the instructions dump the conversations database and restore without the corrupt elements, thus keeping your whole conversation history.
Alex
![]() |
2011-04-02
, 05:28
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#55
|
The Following User Says Thank You to Mentalist Traceur For This Useful Post: | ||
![]() |
2011-04-11
, 02:31
|
Posts: 2 |
Thanked: 0 times |
Joined on Apr 2011
|
#56
|
![]() |
2011-04-11
, 13:18
|
Posts: 2 |
Thanked: 0 times |
Joined on Apr 2011
|
#57
|
Found a workaround for this today - the problem occurs because the Headers table in the /home/user/.rtcom-eventlogger/el-v1.db becomes corrupt. Happily this is repairable, on the device:
First gain root access:
..then switch to the target directory:Code:sudo gainroot
Now dump the contents of the existing database to a raw SQL file:Code:cd .rtcom-eventlogger
Restore the SQL to a new database:Code:sqlite3 el-v1.db .dump > el-v1.db.sql
You may ignore SQL errors at this stage; they occur due to corruption in the source.Code:sqlite3 el-v1.db.new < el-v1.db.sql
Now overwrite the broken DB (you may wish to back up the original file):
Finally, ensure that the file is owned by 'user' and is in the 'users' group so it may be read by ConversationsCode:cp el-v1.db.new el-v1.db
Now close and re-open your Conversations app - the changes should be immediate!Code:chown user el-v1.db chgrp users el-v1.db
Hope this helps,
Alex
![]() |
2011-04-11
, 13:36
|
|
Posts: 1,637 |
Thanked: 4,424 times |
Joined on Apr 2009
@ Germany
|
#58
|
![]() |
2011-04-16
, 10:54
|
|
Posts: 1,648 |
Thanked: 2,122 times |
Joined on Mar 2007
@ UNKLE's Never Never Land
|
#59
|
The Following User Says Thank You to Saturn For This Useful Post: | ||
![]() |
2011-05-21
, 09:40
|
Posts: 53 |
Thanked: 20 times |
Joined on Feb 2010
|
#60
|
![]() |
Tags |
misused tags, troll tags, troll thread |
|
From my observations, there seems to be a definite correlation between receiving multi-part SMS and corrupting the conversations database. (By multi-part I mean a text message so long that it has to be broken into two separate text messages.)
I have tested this on two n900s (both on T-Mobile USA), and the correlation is practically 100%.
Sometimes the problem doesn't appear on multi-part text messages sent between two phones on the same network. However, EVERY time my n900 receives a multi-part SMS from a phone on another network (Verizon, AT&T) the associated conversation thread disappears. At that point, the only solution is to erase the thread, or repair it as described earlier.
For me, a workable solution has been to immediately erase any SMS conversation thread that receives a multi-part text message. It's annoying, but it works.
Hope this helps.
(Also: thank you to everyone who posted other fixes.)