FORUMS

[Q] Setup issue. Black home screen

8 posts
Thanks Meter: 0
 
By santi.marro, Junior Member on 21st February 2014, 07:44 PM
Post Reply Email Thread
8th March 2014, 06:22 PM |#31  
Member
Thanks Meter: 5
 
More
Hi bhiga, that didn't helped either... but thanks for the help.

I have spoken with mighty ddggttff3 he made me try a "vanilla" 16041 which didn't make it and asked me to open up a thread at google chromecast support.

So anyone with similar issues should post in this thread:

https://productforums.google.com/d/t...e8g/discussion

Cheers!
The Following User Says Thank You to mrstimpy For This Useful Post: [ View ] Gift mrstimpy Ad-Free
8th March 2014, 10:39 PM |#32  
bhiga's Avatar
Recognized Contributor
Thanks Meter: 1,027
 
Donate to Me
More
Quote:
Originally Posted by mrstimpy

Hi bhiga, that didn't helped either... but thanks for the help.

I have spoken with mighty ddggttff3 he made me try a "vanilla" 16041 which didn't make it and asked me to open up a thread at google chromecast support.

So anyone with similar issues should post in this thread:

https://productforums.google.com/d/t...e8g/discussion

Thanks for the update!

IMO, everyone who has an issue with a Google update should be sure to provide feedback to Google, even if it's a known issue. Since non-rooted devices cannot refuse Google OTA updates, it essentially means Google could unintentionally make your Chromecast unusable (for you) on any update, and that's not cool, even for a "cheap" $35 device.

Google needs to know that forced automatic updates are not what people want. Heck, even Nintendo let me refuse updates with the warning that "Hey, this game won't work if you don't update."
9th March 2014, 04:44 AM |#33  
EarlyMon's Avatar
Senior Member
Thanks Meter: 1,279
 
More
Quote:
Originally Posted by bhiga

Thanks for the update!

IMO, everyone who has an issue with a Google update should be sure to provide feedback to Google, even if it's a known issue. Since non-rooted devices cannot refuse Google OTA updates, it essentially means Google could unintentionally make your Chromecast unusable (for you) on any update, and that's not cool, even for a "cheap" $35 device.

Google needs to know that forced automatic updates are not what people want. Heck, even Nintendo let me refuse updates with the warning that "Hey, this game won't work if you don't update."

Remember that control issue I had that 15250 fixed, brought on by a previous update?

I reported it. Said it affected everything.

After it was fixed, they emailed me and told me that my report was rejected, I had to contact Netflix, despite the problem appearing on YouTube and despite others adding to my report.

I agree with you, I'll support it and post there.

I don't think they'll listen but I'll keep asking.
9th March 2014, 07:06 AM |#34  
bhiga's Avatar
Recognized Contributor
Thanks Meter: 1,027
 
Donate to Me
More
Quote:
Originally Posted by EarlyMon

Remember that control issue I had that 15250 fixed, brought on by a previous update?

I reported it. Said it affected everything.

After it was fixed, they emailed me and told me that my report was rejected, I had to contact Netflix, despite the problem appearing on YouTube and despite others adding to my report.

I agree with you, I'll support it and post there.

I don't think they'll listen but I'll keep asking.

Big companies tend to reject "onesy-twosy" problem so often times it takes the snowball to build a bit. But of course the snowball can't build if people can't get their snow together... Always tough, but support tickets are usually the best way to get counted. Even a forum thread with 50+ pages and 200+ posts is too easy for a manager to say "Well, it's a forum. They complain."
200+ support tickets on a similar issue is a bit more difficult to ignore.

I'm not speaking for Google here, just from my own experience working in the Silicon Valley tech industry.
9th March 2014, 03:55 PM |#35  
Member
Thanks Meter: 5
 
More
This is the correct link to open a support ticket:

https://support.google.com/chromecas...cast_technical

The other was just a forum thread.

Make yourselves heard...

By the way, I have just got the first reply, of course, blaming my converter, telling me it must not support HDCP. To which I replied if that was required only AFTER because my adapter worked before being upgraded to 15250...

Hating google right now...
9th March 2014, 10:47 PM |#36  
bhiga's Avatar
Recognized Contributor
Thanks Meter: 1,027
 
Donate to Me
More
Quote:
Originally Posted by mrstimpy

This is the correct link to open a support ticket:

https://support.google.com/chromecas...cast_technical

The other was just a forum thread.

Make yourselves heard...

By the way, I have just got the first reply, of course, blaming my converter, telling me it must not support HDCP. To which I replied if that was required only AFTER because my adapter worked before being upgraded to 15250...

Hating google right now...

Be patient and wade through the "playbook" until you get them stumped and they escalate to an actual bug report.

-= this post enhanced with bonus mobile typos =-
9th March 2014, 10:48 PM |#37  
kelvinvalencio's Avatar
Senior Member
Flag Strasbourg
Thanks Meter: 39
 
More
Have you solved this problem?

Sent from my N986 using xda premium
14th March 2014, 01:15 PM |#38  
Skazki's Avatar
Member
Flag Moscow
Thanks Meter: 2
 
More
I has the same problem yesterday and cant fix it!

"After this update my chromecast doesnt boot Only Google Logo then black screen on my TV Samsung... Thx Google...
I tried to disconnect USB and plug in it to POWER adapter - it doesnt help me, then I tried to hard reset from physical button on Chromecast - it doestnt helps to me too! Any ideas? After HR chromecast now displays on my TV like "Player". Chromecast app cant connect to Chromecast..."

Any ideas? I think my Chromecast died
2nd September 2014, 12:12 AM |#39  
Member
Thanks Meter: 12
 
More
Please don't blame me for bringing up an old thread, but I'm experiencing the same problem with my Chromecast (on the latest software build) when connected to my 1080p-HDCP-capable HDMI to VGA converter (which is connected to my VGA-only projector). My Chromecast itself is fine as it works perfectly when connected to a newer LG 1080p TV.

Is there anything new on this topic?
2nd September 2014, 01:51 AM |#40  
bhiga's Avatar
Recognized Contributor
Thanks Meter: 1,027
 
Donate to Me
More
Quote:
Originally Posted by YassinTP

Please don't blame me for bringing up an old thread, but I'm experiencing the same problem with my Chromecast (on the latest software build) when connected to my 1080p-HDCP-capable HDMI to VGA converter (which is connected to my VGA-only projector). My Chromecast itself is fine as it works perfectly when connected to a newer LG 1080p TV.

Is there anything new on this topic?

What resolution is your HDMI to VGA converter sending to the projector - and what resolutions do your projector support?
2nd September 2014, 03:46 AM |#41  
Member
Thanks Meter: 16
 
More
Quote:
Originally Posted by YassinTP

Please don't blame me for bringing up an old thread, but I'm experiencing the same problem with my Chromecast (on the latest software build) when connected to my 1080p-HDCP-capable HDMI to VGA converter (which is connected to my VGA-only projector). My Chromecast itself is fine as it works perfectly when connected to a newer LG 1080p TV.

Is there anything new on this topic?

HDCP?
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes