Quote:
Originally Posted by kjhadfield
i get pretty much the same error message w/ mostly twitter using spb backup. but i havent noticed if it really matters or not. i did do a restore even thou i had those errors on the backup but everything restored fine w/ no probs. so you might not have to worry bout it. and it doesnt matter what rom im on i get the same "twitter" error. \
so i suggest do a full backup...you will get the "twitter" error mainly. also do a pim (custom) backup just to save your contacts (thats what i do at least) and when you flash back to the rom you backed up then just restore and it should go fine (dont 4get a hard reset as norm. b4 you do the restore)
|
Well thanks for your input but i was more concerned with the two error messages found at the bottom of the log: These 2
2010-02-23 16:42:51 Unable to read from file "\Windows\ET9IMEDB\eT9Rudb.Rdb".
2010-02-23 16:42:51 Unable to read from file "\Windows\ET9IMEDB\eT9AsDb.Adb".
not sure if that file is important or not.
Now this is not the first time i see this error message. I have seen it since R7 and i have attempted to do a restore regardless of the errors and i just felt it wasnt as snappy even after a fresh hard reset or fresh flash. idk what the importance of those files are but my guess is it has something to do with the responsiveness of the ROM overall and thats why i am looking for a solution. Thanks for your input.