![]() |
2011-06-18
, 23:55
|
|
Posts: 127 |
Thanked: 19 times |
Joined on Jul 2010
@ Wales
|
#62
|
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-06-19
, 01:00
|
Posts: 122 |
Thanked: 17 times |
Joined on Jun 2010
|
#63
|
![]() |
2011-09-12
, 12:14
|
Posts: 16 |
Thanked: 1 time |
Joined on Oct 2010
|
#64
|
![]() |
2011-10-12
, 03:38
|
Posts: 31 |
Thanked: 3 times |
Joined on Sep 2010
|
#65
|
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
The Following User Says Thank You to ashwin For This Useful Post: | ||
![]() |
2011-10-12
, 07:28
|
Posts: 176 |
Thanked: 190 times |
Joined on Jun 2011
@ Italy
|
#66
|
![]() |
2011-10-30
, 14:51
|
|
Posts: 1,312 |
Thanked: 736 times |
Joined on Sep 2009
|
#67
|
The Following User Says Thank You to somedude For This Useful Post: | ||
![]() |
2011-11-18
, 14:56
|
Posts: 85 |
Thanked: 97 times |
Joined on May 2011
|
#68
|
![]() |
2012-11-04
, 02:27
|
Posts: 258 |
Thanked: 76 times |
Joined on Sep 2010
@ Lima-Peru
|
#69
|
![]() |
2013-02-24
, 15:55
|
Posts: 466 |
Thanked: 335 times |
Joined on Jan 2010
@ Vienna, Austria
|
#70
|
![]() |
Tags |
misused tags, troll tags, troll thread |
|
im experiencing this problem again..
iv tried doing everything and it still keeps not working
i would send an sms, and it would show that the msg is still waiting to send... and it stays this way (but the sms actually is already sent)
and when i close conversations and reopen, everything is gone and its no longer in chronological order
last time the only way i fixed it was to restore a backup..
i dont want to do this because i will lose all my highscores!!! NOOOO!
i understand its because some corrupt data or something is going on...
but does anyone know what could be causing this? and how to prevent it?