it's actually just a bug -- one that's fixed in development and will be fixed in the next release. currently, the progress wil jump to the point it left out at the second a queryhit comes in from the network. what the fix will do is let it display the correct progress immediately after resuming.