cancel
Showing results for 
Search instead for 
Did you mean: 
Replies are disabled for this topic. Start a new one or visit our Help Center.

Chromecast Shutting Off While Inactive (Part 2)

Chook71
Community Member

Google you are unbelievable

Why has the original thread about this issue been closed as answered 

https://www.googlenestcommunity.com/t5/Chromecast/Chromcast-Shutting-Off-While-Inactive/m-p/453323#M...

The so-called "solution" DOES NOT WORK and is NOT A FIX FOR THE ISSUE.

At best what you have offered is a workaround that is only applicable to some users but does NOT resolve the underlying issue that Google caused with a software update in April this year. 

The device still shutdown after 4 hours. This is still the case. 

Why does Google close all support cases submitted about this issue? 

Why will Google not resolve this issue? 

Why will Google not give customers their money back for these now faulty devices. 

Why will Google NOT provide any kind of support for ANY of their products

 

 

16 REPLIES 16

Chook71
Community Member
The Power and Energy setting to automatically turn off the TV when inactive is set to Never. 
 
When the device is "idle" and displaying ambient mode or when I am streaming my Nest Outdoor security camera to the device it displays the following after exactly 4 hours
IMG_3698.JPG
 
This only appears for a few seconds and then the TV will turn off. 
 
Now I have tried changing this setting and this is what I have found. 
 
If you set it to anything under 4 hours, then it appears to work correctly. 
 
i.e. if you have it set to turn the TV off after 15 min after 15 min (from when ambient mode was activated). 
 
I have tested the following with the same results. 
 
15min - TV turns off after 15min from when ambient mode was activated
30min - TV turns off after 30min from when ambient mode was activated
1 hr - TV turns off after 1hr from when ambient mode was activated
 
If you set it to anything 4 hours or above then after 4 hours it will display the above and if no button is pressed the system will turn off. 
 
I have tested the following: 
 
 
12hrs - TV turns receive pop-up as above after 4 hours of the device being turned on. if you don't press a button the system turns off
24hrs - TV turns receive pop-up as above after 4 hours of the device being turned on. if you don't press a button the system turns off
Never - TV turns receive pop-up as above after 4 hours of the device being turned on. if you don't press a button the system turns off
 
Somewhere in the system, it seems 4 hours has been set as the maximum regardless of what you select on the device. 
 
From what I have experienced if you are watching Netflix, YouTube etc the device stays on it is only when the system thinks it is idle. 
 
Now I received a response from the @Madebygoogle Twitter account stating "There's no confirmed bug about this" which I find extremely hard to believe given there are numerous entries on Google's own Community forum page as well as Reddit outlining this exact issue from hundreds of people all around the world to which we received responses from a so called "Community Specialist" stating "the team is still investigating". 
 
Google Nest Community Links: 
 
 
Reddit Links: 
 
 
As reported by a number of users on both forum sites the only solution currently available is to put the device in developer mode. 
 
 
At this point, I have not done this as I would prefer Google to acknowledge and fix the issue. 
 
This is clearly an issue with the code from the update released in March/April this year this is when it started happening (has nothing to do with the network). 
 
The devices were working fine before the update and had issues after the update. 
 
There was a further software update released 1st June, STTE.230319.008.R1, this also did not fix the issue. 
 
I feel with the information I have provided as well as the information available within the above forums confirming everything I have said above and previously that Google should be able to resolve this issue. 

Chook71
Community Member

The workaround suggested in the now closed thread is to put the device in developer mode. This is something that Google stated for months was NOT recommended and NOT supported yet now claims that this is currently the only solution. 

Putting the device in Developer Mode does not stop the device switching off ambient mode after 4 hours. As this is specifically what I and others purchased the devices for Google has effectively made these devices useless and NOT FIT FOR PURPOSE! 

This is 100% Googles fault yet the refuse to provide any kind of support. 

The fact that Google keep closing support cases and closing Community threads on the topic proves they have no intention of addressing or resolving the issue. 

If you are affected by this issue I recommend that you lodge a complaint with your Consumer regulator

aostang
Community Member

I am still having the original issue as stated in this thread. At least we have the workaround, but should not have to do that. Also lose ambient mode with that developer tweak. This has been ongoing for 6 months now. I'm tired of having to rush over to the remote every day as I have a TV on while I am working. FIX THIS!!

Chook71
Community Member

Ok so there has been another update released which appears at this stage to have resolved the issue.

System Firmware version: STTK.230808.004

I installed this on Monday, and it hasn't turned itself off since. 

There was an issue initially where when ambient mode had been running for a few hours it seemed to get out of sync as the clock was showing the wrong time and I was unable to go back to the home screen. Had to power cycle the device. 

I haven't been home long enogh since to see if it happens again. 

Fingers crossed that after 7 months this has finally been resolved. 

Kimy
Community Specialist
Community Specialist

Hi folks,

 

Thanks for posting here in the Google Nest Community. I’m glad that it’s finally sorted out, @Chook71. For other users who're still experiencing this, there's an ongoing update that will be rolled out in the coming days. It includes patch fixes for most of the recognized bugs. It should be the versions STTE.230615.004 and STTE.230615.004.1 where this patch fix kicks in. Once you have the update available, make sure to install it. If it's not available yet, give it a few more days. Keep us posted.

 

Thanks,

Kimy

Kev1965
Community Member

I have the latest update and the issue is still there. Power set to never still powers off after 4 hours.

Wrybread
Community Member

How bizarre that Google locked part 1 of this discussion, even when the bug still remains. And apparently firmware upgrade STTK.230808.004 didn't fix this bug... Come on Google, you can do better than this. When you do things like that it makes people think you don't care about this product.

Anyway I really needed this bug fixed so I made an APK that you can load onto your Chromecast that will keep it from going into standby mode after 4 hours, and it will still let the screensaver function normally. You can download the APK and all source code here:

https://github.com/wrybread/KeepAwake

To use it you'll need to sideload the APK and then run it once. No further action is needed, it will then continue running in the background doing its thing and will run when you reboot. To make it stop simply uninstall it.

Wrybread
Community Member

Should have said, more details here:

More details in this Reddit post:

https://www.reddit.com/r/Chromecast/comments/176gl3x/i_made_an_app_to_keep_the_chromecast_from_going...

Note the alternative method I came up with linked at the bottom of that post (a Python script that you can run from a computer on the same network). But the APK above is probably easier.

Kimy
Community Specialist
Community Specialist

Hi everyone,

 

Thanks for posting. The estimated full completion of the update is until the last week of this month. Let’s give it a little more time. We appreciate your understanding.

 

Let us know if you have any other questions.

 

Sincerely,

Kimy

Wrybread
Community Member

I'll believe it when I see it, but thanks for posting Kimy.

Kimy
Community Specialist
Community Specialist

Hi Wrybread,

 

We hear you. Hopefully, once it’s completed, this will be resolved once and for all. Keep us posted.

 

Regards,

Kimy

Chook71
Community Member

Oh my god. I cannot believe Google appears to have done it again. After running perfectly fine for over 2 weeks my device is now back to displaying a blue screen after a few hours. im going to guess it’s 4 hours but to be  honest I really don’t care anymore. 

I’m moving to Amazon. Can’t be any worse. Already binned my Google Nest Cameras, Chromecasts and Nest wifi are next. 

will be telling everyone who will listen to avoid Google devices like the plague, unless they like spending good money on products that the vendor will then make useless.

 

 

Wrybread
Community Member

Firesticks are a nightmare... I switched to Chromecasts from Firesticks because Firesticks fill the thing with ads. The launcher is literally 90% ads by screen size, probably more, and they don't let you switch launchers.

I made an app that keeps the Chromecast from falling asleep, it's here if you want to try it. 

https://github.com/wrybread/KeepAwake

taona04
Community Member

How's it going mate, did you say you posted the APK or just the source. I can't seem to find the APK

Wrybread
Community Member

Oops, looks like I accidentally deleted the APK, I just put it back.

https://github.com/wrybread/KeepAwake

Let me know how it goes if you try it.

Kimy
Community Specialist
Community Specialist

Hi folks,

 

I’m sorry for the delay in response. I’m just checking in to see if you finally received your update. The rollout should’ve been completed already, as it was estimated to be completed by the end of October. Let me know if you’re still experiencing the issue.

 

We look forward to your responses.

 

Thanks,

Kimy