Originally Posted by PSX

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:

Code:

sudo gainroot

..then switch to the target directory:

Code:

cd .rtcom-eventlogger

Now dump the contents of the existing database to a raw SQL file:

Code:

sqlite3 el-v1.db .dump > el-v1.db.sql

Restore the SQL to a new database:

Code:

sqlite3 el-v1.db.new < el-v1.db.sql

You may ignore SQL errors at this stage; they occur due to corruption in the source.

Now overwrite the broken DB (you may wish to back up the original file):

Code:

cp el-v1.db.new el-v1.db

Finally, ensure that the file is owned by 'user' and is in the 'users' group so it may be read by Conversations

Code:

chown user el-v1.db
chgrp users el-v1.db

Now close and re-open your Conversations app - the changes should be immediate!

Hope this helps,

Alex