Closed GoogleCodeExporter closed 9 years ago
Not sure what I can do about that. It uses the network to try to replace
*every*
cover image, it doesn't just replace the ones that are generated or missing. As
to
how effective it is, that seems to depend more on how reliable the network is
at the
time it's run.
I have 400 books in my db now and it works for me. I've also tested it on 4
different
devices, and have other users report good results. I have seen it be flaky when
the
network is flaky though.
I'll look into it more to see if I can make it any smarter.
Original comment by charlie....@gmail.com
on 28 May 2010 at 3:49
This works much more reliably now. I have tested it with 400+ books and it
works well, so long as there is a network connection (and the image providers
hold up). Changes are that the screen will not sleep during the operation now
(sleeping was messing it up), and screen will not rotate based on sensor (that
messes it up too).
Screen still rotate and causes issues if keyboard is opened on devices with
keyboards, but it just stops the task mid stream (not really an error), and
it's unlikely that people will do that will the task is running and telling
them each book it's updating.
Original comment by charlie....@gmail.com
on 14 Jun 2010 at 1:44
Original comment by charlie....@gmail.com
on 17 Jun 2010 at 1:13
Original issue reported on code.google.com by
afx...@gmail.com
on 28 May 2010 at 11:16