[AVDA] Use InMilliseconds with presentation_timestamp

[AVDA] Use InMilliseconds with presentation_timestamp

AndroidVideoDecodeAccelerator::DequeueOutput fails to call SendDecodedFrameToClient
even when bitstream_buffer_id for presentation_timestamp exists in
bitstream_buffers_in_decoder_.

BUG=637606

[DaleCurtis, 2016-08-19 16:34:12]

dalecurtis@chromium.org changed reviewers:
+ dalecurtis@chromium.org

[DaleCurtis, 2016-08-19 16:34:13]

This fix doesn't seem correct. Are you implying that the Shield MediaCodec is
throwing away microsecond precision when decoding buffers?

[akshaya, 2016-08-20 01:29:58]

On 2016/08/19 16:34:13, DaleCurtis wrote:
> This fix doesn't seem correct. Are you implying that the Shield MediaCodec is
> throwing away microsecond precision when decoding buffers?




>>
This fix doesn't seem correct
>>

I agree. I uploaded this WAR as an attempt to collaborate and open a discussion
to take suggestions on why this part of code is behaving incorrectly (not trying
to say that Millisecond precision is a better solution) based on my recent
findings. 


>>
Shield MediaCodec is throwing away microsecond precision when decoding buffers?
>>

Yes, I suspect so. May be the timestamp of the buffer given as an input to
AMediaCodec is coming back back modified in Chrome's AMediaCodec driver. Shall
look further into it from NV side. 

In the meantime, if you have any other suggestions, then please post it here. It
will be helpful.

[DaleCurtis, 2016-08-21 22:50:19]

I think we want something like this https://codereview.chromium.org/2260913003