It could be that the android browser requires the content-disposition header, which I haven't supplied. That is probably a bug, but I can see why they would do it. The header provides an unambiguous filename. There is a new 0.2.3beta release that includes the content-disposition header.
As for the timeouts, I don't know why they would be there. I didn't think that I changed much. I did change the way the prev and next buttons work, but it uses basic html. My son is coming to visit in a few days, and he has an android phone. We will play.
