Assigned
Status Update
Comments
ar...@google.com <ar...@google.com> #2
Hi, thanks for reaching out to the Chromecast support team!
Is it possible to provide a sample app that we can use to reproduce this issue?
thanks
jo...@gmail.com <jo...@gmail.com> #3
The app I'm developing https://github.com/JohnStrunk/wahoo-results uses pychromecast for its interaction w/ the CC device. Since that's an unsupported (by Google) sender library, my initial report describes how to reproduce the problem using Google's own cactool as the sending app.
Will that be sufficient?
Will that be sufficient?
ar...@google.com <ar...@google.com> #4
Thanks, I have raised an internal ticket for further follow up with Engineering team. We will keep you posted with our findings soon.
ar...@google.com <ar...@google.com> #5
Hi, is this still an issue?
thanks
jo...@gmail.com <jo...@gmail.com> #6
Yes, this continues to be an issue.
OS build: STTE.240315.002
OS build: STTE.240315.002
Description
Please answer all relevant questions below so that we have enough information to investigate your issue. Providing incomplete information will delay investigation of your issue.
Bug Report Template
Describe the issue: expected vs. observed behavior and/or appearance.
When casting images to a Chromecast w/ GoogleTV device using the default media receiver, the receiver times out after 10 minutes and returns to ambient mode even when new images are being sent.
This behavior on CCw/GTV is different than either the Gen1 or Gen3 Chromecasts which do not timeout as long as new images are being sent.
On Gen1 and Gen3, the timeout resets w/ each new image, on CCw/GTV, it does not.
List steps to reproduce the issue, if known.
Connect to the default media receiver using cactool (
image1:
{
"media": {
"contentUrl": "
}
}
image2:
{
"media": {
"contentUrl": "
}
}
Continue sending images at regular intervals that are less than the idle timeout (i.e., send an image once per minute).
On Gen1 and Gen3 devices, new images will continue to be displayed, on CCw/GTV, the device will return to ambient mode 10 minutes after the receiver was launched, regardless of the images being sent.
I have also tried a custom receiver w/ "disableIdleTimeout=true", and this makes no difference.
The only workaround that I have found is to enable developer options and set "Stay awake". However, it is unreasonable to expect the users of my app to do this.
Which version of the Cast SDK are you using?
CCw/GTV: Chromecast HD, build STTE.221215.004.A1
On which version(s) of the OS (iOS, Android) do you observe the problem?
N/A
On which device type(s) such as phones, tablets or laptops (iPad, iPhone, etc.) do you observe the problem?
N/A
Do you observe the problem when running on a physical device, or the simulator, or both?
If this is a device discovery or device connectivity issue: Do you observe the problem over Cellular (using Guest Mode), WiFi (using either Guest Mode or local connection), or both?
N/A
If this is strictly a UI appearance/styling issue, please take screenshot(s) (for iOS, and Android) illustrating the problem and attach them to the bug report. Also mention whether the problem occurs in portrait orientation, landscape orientation, or both.
If this is not a UI appearance/styling issue, please capture logs from the SDK for a time interval leading up to and including the occurrence of the problem, and attach them to the bug report. For issues relating to device discovery, the log should cover at least 20 seconds. For issues relating to device connectivity, the log should cover the entire time during which you attempted to start a Casting session.
Obtaining iOS Cast SDK Logs:
Obtaining Android Cast SDK Logs: