Closed GoogleCodeExporter closed 8 years ago
We're looking into it.
Original comment by jonathan...@google.com
on 26 Oct 2015 at 10:55
What Chromecast firmware version are you using?
Can you reproduce the issue, capture the logs, and provide them here as a text
file?
Original comment by jonathan...@google.com
on 27 Oct 2015 at 9:09
Firmware version: 1.16.44433
Log is attached.
Original comment by ca...@doubleencore.com
on 28 Oct 2015 at 12:50
Attachments:
Hi, mediaControlChannelDidUpdateQueue would not be called unless the queue is
updated. If the item just finishes and moves to next one, it is not considered
to be that the queue has updated. In this scenario, I think you should only get
the callback when the queue finishes, and that is when currentItemId and
queueItemCount would both be 0.
But I would appreciate if you could also attach logs from iOS side.
Original comment by jieh...@google.com
on 29 Oct 2015 at 11:44
On iOS the queue updated callback is triggered after the first item in the
queue completes playing. After that it is not triggered between the remainder
of the items. Please see the attached log.
On Android the queue updated callback is triggered after every item in the
queue completes.
Original comment by ca...@doubleencore.com
on 30 Oct 2015 at 4:55
Attachments:
Original comment by jonathan...@google.com
on 2 Nov 2015 at 7:33
Hi Caleb, can you use the same repro steps and provide the equivalent receiver
logs for Android (which should work correctly)?
Original comment by jonathan...@google.com
on 5 Dec 2015 at 12:56
We were not able to reproduce this with the default player. There may be
something that your custom receiver application does to trigger this, i.e.
forcing a media status to be sent when it is not expected.
Original comment by jonathan...@google.com
on 15 Dec 2015 at 1:00
Original issue reported on code.google.com by
ca...@doubleencore.com
on 23 Oct 2015 at 10:59