Re: [Ankidroid] Media download all over again *everytime?

134 views
Skip to first unread message

Flavio Lerda

unread,
Sep 10, 2012, 5:55:34 AM9/10/12
to anki-a...@googlegroups.com
Hello,

Which version is this happening with? Is this with 2.0 beta 16?
This sounds like a bug. Definitely that does not happen with the decks I have (they are quite big as well).

As a temporary workaround, you might be able to disable "Fetch media on sync" in "Preferences -> General" but there is probably an issue that needs to be fixed before release.
Is there a similar issue at http://code.google.com/p/ankidroid/issues? If not, could you create one with as much detail as possible?

-Flavio

On Sun, Sep 9, 2012 at 4:13 PM, Daniel_ar <hokan...@gmail.com> wrote:
Hi!
Everytime I synchronize ALL the media is downloaded again to my cellphone... that does not make sense! Shouldn't the program check for updates and download only what's different? I have about 100mb on media and if the wifi gets cut off for some reason then I have to start all over again.
Can the media be added manually? I have "minna no nihongo" deck files that are 20mb, I guess all the media is in there, so unless there's a way to extract it and then I can copy everything to my cell through USB...
I appreciate any help you can provide.

--
You received this message because you are subscribed to the Google Groups "AnkiDroid" group.
To view this discussion on the web, visit https://groups.google.com/d/msg/anki-android/-/EbMKcie-UVkJ.
To post to this group, send an email to anki-a...@googlegroups.com.
To unsubscribe from this group, send email to anki-android...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/anki-android?hl=en-GB.



--
Flavio Lerda

iniju

unread,
Sep 10, 2012, 9:20:24 AM9/10/12
to anki-a...@googlegroups.com
There is a bug indeed, but haven't found what causes it. It makes the sanity check at the end of media syncing fail on the counts, which forces the next media syncing to be full in hope that it will recover from the bug.

I meant to investigate this more as it is currently the most frequent error reported in triage (it's not a crash but we still report it for monitoring how frequent it is), but the last few weeks I'm swamped with real work and my free time has disappeared.
Reply all
Reply to author
Forward
0 new messages