Thread: N900 SMS pending / not saving
View Single Post
LondonBenji is offline LondonBenji
2011-01-28 , 02:02
Posts: 67 | Thanked: 36 times | Joined on Feb 2010
#11
Eeek, sorry.

Okay so I told my friend my conversations were acting funny, we did a little research and it's an sqlite3 database file. Databases being databases they can get fragmented and corrupted, this being no exception.

My friend isn't a SQL expert but a little trick they use when he works on databases in a similar situation is to use the SQL tools to read out the entire contents of the database and write it to a new file.

So we tried it and it worked in so much that the database seems to be stable now although certain texts/messages show as unsent and also one text conversation (admittedly one that was getting heavily corrupted) has a red exclamation on it in the conversations window (I have no idea what that means).

Anyway, here is what we did, note that these instructions may not be 100% accurate which you should not do unless you know what you are doing and if they are wrong could well make you loose all your data! DO NOT BLAME ME, YOU PERFORM THE BELOW AT YOUR OWN RISK! IF YOU GET STUCK AT ANY STAGE, IF ANY OF THE COMMANDS ARE WRONG, IF YOU LOOSE ALL YOUR DATA OR YOU COMPLETELY BRICK YOUR PHONE I CANNOT BE HELD RESPONSIBLE!

1. First of all make sure ALL conversations are closed including the Conversations window itself and then preferably go into Offline/Airplane/Tablet mode so it's not possible you'll receive any new messages of any kind.


2. Open a terminal and change to root:

Code:
sudo gainroot

3. Change to the directory where the database is stored:

Code:
cd /home/user/.rtcomm-eventlogger

4. Read the contents out the database and write it to a new file (NOTE: The filename is for the newer version of the database file introduced in PR1.2 I believe!!):

Code:
echo .dump | sqlite3 el-v1.db | sqlite3 el-v1-new.db

5. Move the existing file to another file to back it up:

Code:
mv el-v1.db el-v1-old.db

6. Move the newly created file to the proper name:

Code:
mv el-v1-new.db el-v1.db

7. You might need change the permissions on the file:

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

8. For completeness, why not reboot the phone:

Code:
init 6

9. Whilst it's rebooting it should ask 'Exit offline mode?', select 'Yes' and you should be back up and running, open Conversations and check to see if everything is there and if it is now more stable.


I think this post is doing the same thing but in a slightly different way.

Hope this helps.

Benji
 

The Following 17 Users Say Thank You to LondonBenji For This Useful Post: