ERGENCY ISSUE - LOST ALL TAGS

[GoogleCodeExporter]

Failed to get tags from cache>
java.io.EOFException

My phone, due to lack of battery power, shut down suddenly. 
Now all my tags are gone.

What can I do? I have the exam next week and need to study kanji. :(

Original issue reported on code.google.com by dezorian...@gmail.com on 28 Jan 2015 at 8:41

[GoogleCodeExporter]

Original comment by dezorian...@gmail.com on 28 Jan 2015 at 8:57

Attachments:

• Screenshot_2015-01-28-21-56-33.png

[GoogleCodeExporter]

Hm, this shouldn't happen as Aedict first saves the whole data to the new 
temporary file, then, when this operation succeeds, it will move the temp file 
over the old one. Perhaps the file system got broken by the unexpected shut 
down and the tag file itself has been trimmed to zero size.
Please attach your phone via USB to your computer, or launch some file browser 
app on your phone, and head to where the dictionaries are stored. This is by 
default /Android/data/sk.baka.aedict3/ - here somewhere, but you might have 
configured the location differently. In this directory, there should be a file 
named entrytags.bin - please mail me that file, perhaps I can save some data 
from that file.
If that file is zero-sized, then unfortunately your data is lost :( unless you 
have a backup.

Original comment by martin.v...@gmail.com on 29 Jan 2015 at 7:54

[GoogleCodeExporter]

If you have a backup, do not restore it via Aedict - it will overwrite all 
files, including notepad etc. Instead, you can manually unpack the backup zip 
file on your computer, get the entrytags.bin file from the zip and overwrite 
the one on your phone.

Original comment by martin.v...@gmail.com on 29 Jan 2015 at 7:56

[GoogleCodeExporter]

Thanks for the fast response.
I have setup aedict to make a backup every day to Dropbox.
I hope that is the backup you were talking about. there is also an option
to save/backup notepad (inside notepad).
I will send you that file later today.
 Am 29.01.2015 08:54 schrieb <aedict@googlecode.com>:

Original comment by dezorian...@gmail.com on 29 Jan 2015 at 7:59

[GoogleCodeExporter]

Yes, you're right - you can first backup notepad only, then restore everything 
from Dropbox, then restore the notepad only :-D
Jesus, how I got persuaded to create so many backup options is beyond me :-D

Original comment by martin.v...@gmail.com on 29 Jan 2015 at 8:08

[GoogleCodeExporter]

Ok, I will do that in 3 hours. can you tell me the difference between
notepad save and the backup that you can setup to regularly backup to
Dropbox?
Am 29.01.2015 08:56 schrieb <aedict@googlecode.com>:

Original comment by dezorian...@gmail.com on 29 Jan 2015 at 8:12

[GoogleCodeExporter]

Backup (to Dropbox or ownCloud or even to the internal memory) is a zip file 
containing all of your data: tags, notepad, SRS and recently-viewed. The 
notepad save only contains one file - the notepad itself. When restoring 
notepad from the notepad save to your live data, only the notepad gets 
overwritten. On the other side, when restoring the full backup (e.g. from 
Dropbox), all of your data gets overwritten - tags, notepad, SRS and 
recently-viewed.
Please let me know if this explanation is clear.

Original comment by martin.v...@gmail.com on 29 Jan 2015 at 8:43

[GoogleCodeExporter]

Perhaps I should implement support for selective restore from backup, e.g. only 
tags or only the notepad from the backup file.

Original comment by martin.v...@gmail.com on 29 Jan 2015 at 11:01

[GoogleCodeExporter]

yeah, some options to individually handle a backup would be great.
I just saw that the entrytag file was indead zerosized and I deleted it, so I 
won't be getting that error message again. I was so close to actually making a 
backup 10 min before the shutdown. Bad luck I guess. Still, you were talking 
about the strangeness of that event, corrupting the cache file leaving it 
zerosized. 
Is there a way to prevent that to ever happen again?

I surely will have my backup setup to save every half hour from now on.
So much one can do (and lose) in such a short time...

Original comment by dezorian...@gmail.com on 29 Jan 2015 at 1:48

[GoogleCodeExporter]

I restored my backup that was from one day ago. So not much damage on my side.
Looks good so far - tags are in place.

One should always make backups, eh. Anyways, thanks for the swift help.

Original comment by dezorian...@gmail.com on 29 Jan 2015 at 1:54

[GoogleCodeExporter]

That's good to hear. Regarding the prevention of corrupting the cache file: 
unfortunately, this happens on the OS file-system level, so there is not much I 
can do. The best way to prevent this from happening is to:

1. configure regular backups to Dropbox or ownCloud

AND

2. never allow your phone to shut down abnormally - watch your battery status 
and never yank it out of your phone :)

Original comment by martin.v...@gmail.com on 29 Jan 2015 at 2:04

[GoogleCodeExporter]

Yep, amen to that.
Am 29.01.2015 15:04 schrieb <aedict@googlecode.com>:

Original comment by dezorian...@gmail.com on 29 Jan 2015 at 5:20

[GoogleCodeExporter]

Original comment by martin.v...@gmail.com on 30 Jan 2015 at 12:05

• Changed state: Fixed