Ouch, you're right. Thanks for catching this bug. I found that the return value of Units.getReadableTime(duration) can be in "hr:min" format. This confuses the if (readableDuration.value > 0) loop. Commenting out the sanity checking makes the time display correctly. Please verify this solution if you can, if it doesn't introduce new bug, then I think this is an easy fix and can be pushed to unstable patch.