Closed GoogleCodeExporter closed 9 years ago
Please quantify the "very late". Also, explain what you mean by incorrect
streaming position. If you want to report any issues with timing, you need to
create a styled receiver and time all the communications, from sender to
receiver, from receiver where it receives that till it gets to the video
element, when media element fires the event, when it gets to the Media Manager
and from media manager back to sender. Without having all pieces, we cannot
provide any valuable feedback.
Original comment by anad...@google.com
on 17 Jan 2015 at 1:01
Please provide the required information if you are still facing the issue.
Original comment by na...@google.com
on 27 Jan 2015 at 12:43
Hi All,
Sorry for the late reply.
I verified the above issue by debugging the logs in styled receiver and
observed that there is no delay.
Rather in sender application I used different method to get the current media
streaming position.
i.e. 'mRemoteMediaPlayer.getApproximateStreamPosition()' - It was giving me the
exact streaming position both in foreground and background.
whereas previsously I used 'mediaStatus.getStreamPosition()' method but
sometimes its giving me the inaccurate streaming position.
Original comment by chromeca...@gmail.com
on 30 Jan 2015 at 1:36
Please close the issue.
Original comment by chromeca...@gmail.com
on 30 Jan 2015 at 1:37
Closing this issue. Please refrain from submitting issues that are duplicates
of previously submitted issues.
Original comment by jonathan...@google.com
on 30 Jan 2015 at 5:49
Original issue reported on code.google.com by
chromeca...@gmail.com
on 16 Jan 2015 at 10:46