yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] bhiga:
Nice names. :)

Well, you're on the latest firmware build (15250) so either Google broke something in the newest update, or your TV is finicky.

Since your TV is Smart, it might have a firmware update available.

Wait... The specs say "TruMotion 100Hz" - is your TV PAL? It might not support NTSC input...
[Google Chromecast] EarlyMon:
HDMI doesn't care about PAL vs NTSC frequencies by design, exactly why so many in the UK were able to adopt early last year.
[Google Chromecast] bhiga:
While I agree that it shouldn't matter in this day and age, they still exist separately in the EDID data because of the differing pixel clocks.

It's possible (though ill-advised) for a modern display to reject an input signal based on it being 50/100 Hz or 60/120 Hz.

I deal with a lot of AV stuff and have run into this issue from time to time.
[Google Chromecast] EarlyMon:
Well, TIL then.
[Google Chromecast] bhiga:
:) I'm learning every day... sometimes the hard way.

Traditionally European TV sets have been more forgiving than their US counterparts, accepting NTSC "nudged" into PAL-60 or NTSC 4.43 in the analog realm.

While the transition to HD did unify the display resolutions and pixel aspect ratios (everything's square, yay!), the differences in refresh/sampling rates remained. :(

One day my friend, one day... everything will be 600 Hz or better so 24, 25, 30, 50 and 60 fps content will all be supported and play without judder or needing interpolation. :cyclops:

So back to the topic at hand, it's possible the OP's TV doesn't know what to do with a 30/60 Hz input from Chromecast, though that would be quite silly of LG to impose such a restriction. Still, silly happens more often than you think for all kinds of reasons (gray market sales due to varying exchange rates and import/export laws often is a concern, as we burden on regional support that got no revenue from the foreign sale).

TBH, I

don't

know for certain whether Chromecast is capable of 25/50 Hz output, it might be. But being that Google isn't selling it outside of US/Canada yet, I doubt they've tested it.

>> Anybody in Europe, can you confirm me whether Chromecast outputs 720/50p, 1080/50i or 1080/50p to your TV? <<
[Google Chromecast] santi.marro:
Thank you for all your replies,

For what I know, my TV accept NTSC but I'm not 100% sure. I am from South America by the way, in theory electronics here are NTSC.

That TV in the picture you posted is very similar to the one I have. Did you have any problem using the chromecast device?
[Google Chromecast] EarlyMon:
The link I gave was from the Eastern Mediterranean, I was more curious about verifying your resolution at the time. There's a 60/120 Hz (NTSC) version of your set, same model number, popular in several South American countries.

I apologize for adding the confusion.
[Google Chromecast] kDnZP:
I have not any problem with LG 26LE3300 (1366x768 native resolution).
[Google Chromecast] bhiga:
Hmm, should work.

Worst-case, since you have other displays that Chromecast does display properly on, you could try this: (it worked on 13300, haven't had need or opportunity to try it on 14975 or 15250)

Locate working monitor and LG TV in close proximity

Connect Chromecast to working monitor and wall power

Once Chromecast is booted, unplug Chromecast

from monitor only

Plug Chromecast into LG TV

Likely this will not survive a Chromecast reboot though... :(
[Google Chromecast] AustinMartin:
I've got a Sanyo DP50740, and my Chromecast is now showing this same behavior. It used to work fine, but I think that the update to firmware 15250 broke something with hdcp in some TV's.

I filed a bug with Google, but the end result was that the google helpdesk can't tell what was updated in the latest build.

I suggest you file a similar bug with Google, so that they see that this is happening with multple TV models.

Until they fix this I'm stuck with a paperweight.

:(
[Google Chromecast] bhiga:
It won't sync up even if you hot-plug Chromecast HDMI after it's already booted?
[Google Chromecast] AustinMartin:
Nope, tried that. The only thing I haven't tried is to boot up plugged into another device then plug in. Don't have any portable monitors with hdmi input. It might be that they fixed this glitch in the latest firmware.

This is the annoyance of allowing google to update firmware at will. They can break your device, and there's then nothing you can do except wait for the next release. That's why I encourage the original poster to file a bug with them. That's their only window into what's happening.
[Google Chromecast] bhiga:
The no HDMI and different HDMI scenarios should be different, they have been in my case at least, but understand not having a practical means to try.

Agree. That's the danger of forced updates.

Sent from a device with no keyboard. Please forgive typos, they may not be my own.
[Google Chromecast] mrstimpy:
Having the same here after the 15250 update, (I am using a digital to analog converter device with VGA and 3.5mm plug outputs) at first I thought that I did something wrong before rebooting, but it used to work on 1680x1050 and after reboot it went blank on me, I can see the splash screen on boot, then blank, I can connect to the Web and I see it online, but my monitor is reporting it is on 1920x1080 resolution and asking me to switch back. I even tried manually flashing the 15250 eureka_image.zip file again from the recovery, but I still get blank screen.

I will manually flash the 14975.002 back and let you guys know how it went...

Thanks!!
[Google Chromecast] bhiga:
Definitely sounds like Google changed the resolution negotiation between 14975 and 15250. Not sure why, but maybe they're doing some optimizations for specific resolutions (might make sense for optimization of screen mirroring).

Look forward to hearing your result.

FWIW, 15250 is still working fine through my HDfury2 but that's going to Component and not VGA (it seems to be stuck in YUV mode regardless of the YUV/RGB switch setting), and also through a downscaler. Not sure if the downscaler will tell me whether it's getting 1080p, 1080i, 720p, 480p or 480i... will have to look when I get a chance to take over that TV.
[Google Chromecast] mrstimpy:
14975.002 didn't make it... there's something in what got changed in 15250 that was not tampered with before it. I will flash flashcast+pwnedcast-1.0 back then gradually upgrade and see how it goes. Will keep you guys posted...
[Google Chromecast] bhiga:
Just to make sure, did you unplug the Chromecast from the TV and re-plug it after the re-flash? Often times HDMI needs a connection cycle for a full reset.
[Google Chromecast] AustinMartin:
This would make sense why it's not working on my TV, as it's a 720P plasma screen. This probably means it doesn't work with any 720P TV though, so you think they would have seen this in testing.
[Google Chromecast] mrstimpy:
Yeah... many times I also did powercycle the digital to analog adapter with no luck... I still haven't been able to downgrade, but I will post the results as soon as I do...

Cheers!
[Google Chromecast] mrstimpy:
Well... I don't have good news...

I Factory reset the CC, then flashed flashcast 1.1.1 and Pwned-Cast Rom with same results: Black Screen...

So I really don't know what's going on here...

I think I will try going back to a previous version of Flashcast too... but I don't think that would make it either... :(
[Google Chromecast] bhiga:
If your TV/monitor/adapter has multiple HDMI ports - try a different one.
[Google Chromecast] mrstimpy:
Unfortunately it only has one HDMI port, which I am pretty sure it works properly as I also connect the cable box there...

I went back to flashcast 1.0 bin, then flashcast-1.1 rom. Same black screen... :(

I was thinking maybe there is like a partition on the chromecast that only got modified after flashing 15250 as I can't find any other explanation...

I will join the irc channel and ask the guys if they can think of anything... Thanks bhiga!
[Google Chromecast] bhiga:
Only other thing I can think of is perhaps it somehow caches device IDs and/or resolutions.

Successfully connecting to a different device might give it the necessary kick or reset.

I'm sure the guys will be able to help out more. :)

-= this post enhanced with bonus mobile typos =-
[Google Chromecast] 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/topic/chromecast/xXyNrzm-e8g/discussion

Cheers!
[Google Chromecast] 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."
[Google Chromecast] 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.
[Google Chromecast] bhiga:
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.
[Google Chromecast] mrstimpy:
This is the correct link to open a support ticket:

https://support.google.com/chromecast/contact/chromecast_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...
[Google Chromecast] bhiga:
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 =-
[Google Chromecast] kelvinvalencio:
Have you solved this problem?
[Google Chromecast] Skazki:
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 :(
[Google Chromecast] 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?
[Google Chromecast] bhiga:
What resolution is your HDMI to VGA converter sending to the projector - and what resolutions do your projector support?
[Google Chromecast] halfluck:
HDCP?
[Google Chromecast] YassinTP:
The converter is just sending the input resolution to the projector, which will be 720p or 1080p with the Chromecast, I guess, as soon as it has booted. I am able to see everything until the Chrome logo - this is sent in 480p according to this thread, isn't it? - then the screen turns black.

The projector supports up 1024x768, Epson doesn't tell anything about scaling capabilities. It is, however, able to work just fine with 1080p input - when I connected my Thinkpad and chose 1920x1080 for the projector, it displayed just fine.

Yes, the converter is HDCP capable - I was able to play back a rented movie from iTunes using a Thinkpad X301, Displayport-HDMI cable and the converter connected to my projector.
[Google Chromecast] bhiga:
Yes, the Chromecast boot seems to be 480p, which lets it show up on the majority of devices unless the input hasn't been recognized/locked when the screen shows up.

What happens with your projector is two-stage:

Chromecast will "negotiate" a supported resolution with your display device (converter)

Projector will - or won't - accept the converter's output

Likely the problem is in #1 - Chromecast may be negotiating a resolution with the converter than the projector doesn't like. It might be YCbCr instead of RGB, or something else.

Since you said Chromecast works with your LG 1080p TV, you can try this:

Get either a USB battery pack or a power cable long enough to reach from Chromecast connected to both your LG 1080p TV and your projector.

Connect Chromecast to your LG TV and power it up.

Keeping the power connected, unplug Chromecast from your LG TV and plug it into the converter on your projector.

[*}See if you get output on your projector

I haven't checked recently, but back in the 15xxx firmware at least, Chromecast kept its resolution as long as it was powered. If that's still true and you get output, #1 is the issue - the converter and Chromecast are negotiating a format/resolution that your projector doesn't like.

Unfortunately not a good solution for this unless you can change the EDID on your converter so it only reports specific formats/resolutions (HDfury can do this).
[Google Chromecast] rbeavers:
I had the same thing? Got just the boot screen and then black. Tried all my HDMI connections dvd and cable box were black. I unplugged TV for 15 minutes and when I plugged it back in, then got Chromecast can't connect. Unplugged CC and plugged back on and it connected working now.??
[Google Chromecast] Skazki:
Did you solve that problem? Mine Chromecast works fine now.
[Google Chromecast] YassinTP:
Okay, seems to be a converter-specific issue. I remembered that my HP ZR24w (1920x1200) has VGA input and a nice OSD, so I set the converter up, connected the Chromecast and watched what happened:

- "Chromecast..." was displayed

- The "Chrome" Logo showed, but not in 480p - it was really sharp, so it has to be 720p or 1080p output, OSD tells "1920x1080 @60 Hz"

- The screen turned black (not off), just like with the projector. OSD still shows 1080p.

Could it help to try another HDMI VGA converter? I found another HDCP-capable one from another manufacturer, maybe that's worth a try...
[Google Chromecast] bhiga:
If you want best guarantee of working you need a converter that has scaling functionality, so it can output different resolution from what it's sent.
[Google Chromecast] YassinTP:
So HDFury would be worth a try, right?

I just found out my projector has an info OSD built in. I just performed a Chromecast update which displayed just fine, but the screen went black afterwards again. Of course, I didn't think of checking during the update, but now, OSD shows "1440x900" at 59,90 Hz. Will this resolution make Chromecast turn off the display output?
[Google Chromecast] bhiga:
1440x900 is 16:10 aspect. Is it showing a black screen, or no signal? If it's no signal that might be the native resolution of the panel, or Chromecast may have picked a strange resolution (likely).

While I have had great success with the HDfury products, I don't believe any of them actually scale. I know the original HDfury through the HDfury2 do not.

Looks like the HDfury3 does not either, but the EDID banks may be helpful in your situation. What might be happening is the projector says it supports a resolution, say 1920x1080p, but when Chromecast feeds it, the project doesn't like it. Changing the EDID data so Chromecast doesn't see certain resolutions as supported may help get the two in agreement.

Ahh, looks like 3Dfury / HDfury4 has beta scaling/scan-conversion features... Nice, but the price tag is not so much, but it really depends on the cost of a newer/equivalent projector versus the cost of making Chromecast work on your existing hardware.

Personally, unless you have other applications for the converter, you're probably better off applying the $400 price tag toward an update to a 1080p projector.
[Google Chromecast] YassinTP:
All the screens I tested are showing a black screen, not "no signal". However, my HP ZR24w displays 1920x1080 resolution while the projector recognizes 1440x900.

I did some tests with the LG Full HD TV today and I'm now thinking that it's rather a converter-specific issue than a problem with the resolution.

As described earlier in this thread, I tried to connect the running Chromecast to the converter while running on mobile power - so I plugged my Chromecast into the TV, connected the power to my notebook and the Chromecast booted just fine. The TV also has VGA input, so I connected the HDMI-VGA-converter to it and tried moving the running Chromecast from the TV's HDMI input to the converter's input - and as you can already guess, the TV showed a black screen.

Because I know that the TV as well as the converter support 1080p just fine (as well as all other forms of Full HD and normal HD input), I think it isn't a resolution-based issue but has to do with an incompatibility of the Chromecast with my specific HDMI-VGA-converter.

What do you think on that? I'm not too keen on spending several hundred bucks on a new projector because I don't use it that much, so I tend to trying out at least one other converter - not necessarily an HDfury, just another one in the same category...
[Google Chromecast] ImCoKeMaN:
I'm pretty sure the black screen with Chromecast and your VGA converter is due to HDCP. It sounds backwards, but HDCP compliant actually will mean that it will not work for HDCP inputs like a Chromecast.
[Google Chromecast] bhiga:
That's possible too, though in the case of HDfury the converter itself is an HDCP-compatible display device so it shows picture.

Technically if the converter obeys HDCP rules it should turn off its analog outputs or down scale to SD when fed an HDCP protected source.

That's a possibility too. In theory, with Chromecast sending 1080p, you should either have picture or a scrambled digital mess from HDCP decryption failure.

Black screen alone, especially at the is resolution may be the converter saying "I'm not sure what to do with this." Maybe the converter doesn't know how to handle YCbCr input and only does RGB which would explain why computer output works.
[Google Chromecast] YassinTP:
Okay, the mailman just dropped off my new converter - which is actually working! Partially, at least.

The Chromecast's "home screen" displays fine, but looks a bit blurry. Casting YouTube from my Nexus 5 will either show the YouTube "app" correctly and display only a small part (I would say, about 1/10) of the video, or show only that part of the whole app. Casting my screen does only work in landscape mode, and also only that small part of the screen.

The projector's OSD now shows "640x480 @60,00 Hz". Attaching the Chromecast to my HP monitor does not work as the Chromecast decides on 1080p output at 30,00 Hz, which is not supported by the monitor.

Is there something I can do about this problem, maybe with a rooted Chromecast OS? Or is it telling me that it just won't work with my old projector?
[Google Chromecast] bhiga:
Root currently won't help with resolution detection/selection.

Your image is blurry because each of those 640x480 pixels is being stretched to 3 pixels wide and 2.5 pixels tall. ;)

This could be due to lack of HDCP, as downconverting to analog SD is an option when there's no HDCP negotiation.

What you probably need is either a converter that negotiates as HDCP-compliant and can set the EDID information like I mentioned earlier (HDfury3), or an inline device like Dr. HDMI* that can force specific EDIDs - that way Chromecast won't choose a stupid resolution.

Not sure how much more money you want to invest in this project though...

* No, I do not get paid by the HDfury folks - I just reference their products often because I have had good experience with them personally and in the case of Dr. HDMI, it's cheaper than similar products from Gefen and others.
[Google Chromecast] bhiga:
Since I recently got one, some HDMI splitters will let you force EDID as well, so that might be a cheaper alternative than a full-fledged EDID configurator, assuming one of the modes work...

I bought this one and it supports

Read from Monitor 1

Read from Monitor 2

Full HD 1080p60 24bit 2D video 7.1 audio

Full HD 1080p60 24 bit 2D video 2.0 audio

Full HD 1080p60 36-bit 2D video 7.1 audio

Full HD 1080p60 36-bit 2D video 2.0 audio

1080p30/1080i60/720p60 24bit 2D video 2.0 audio

1080p60 24-bit 3D video 2.0 audio
[Google Chromecast] YassinTP:
I decided to get the Dr. HDMI EDID Manager you mentioned above. Had it delivered in the mail today - and it works! :) I am using "720p only" and the Chromecast displays perfectly on the projector. I actually have to use the new converter, which makes the whole project somewhat more expensive - the old one still stays black, so I will get rid of that one and use the newer one which is smaller anyway and has RCA audio output, so I can connect it directly to my stereo.

Thank you very much for your help!
[Google Chromecast] bhiga:
Glad to see you got it going! :victory:
[Google Chromecast] mohit_gkp:
I ran into same black screen after G logo issue today and after struggling a bit I realized my TV HDCP settings were set to OUT, I changed it to IN and it worked.
[Ornate TrueSmart] arovaris:
Hello ! Someone can extract omate ui, swipe gestures and settings configuration from a omate or x201 series? And put here how .apk files? I buyed a zgpax s5 and would like to put in it. Its possible? Thanks.
[Ornate TrueSmart] funky0308:
I would like to see full firmware somewhere (stock, unchanged) too.
[Ornate TrueSmart] Lokifish Marz:
You could also DL the firmware and unpack the system img.
[Ornate TrueSmart] funky0308:
I must admit I haven't used search button but I could do that, yeah... I just have to find it.

Would you mind if I work a bit on your ROM?

I will not release it or something similar, just want to check few things in framework and systemUI files to be prepared when my TS arrives...
[Ornate TrueSmart] Lokifish Marz:
Almost everything x201 is in the sticky.

Feel free to play with the ROM. If you make any headway let me know as I have an alternate gesture layout I want to try and wouldn't mind working with a themer on some stuff as well.
[Ornate TrueSmart] funky0308:
I would be honored to work with you, mate.

It's a bit tricky to work, for now (for me) because my watch is still in LLP's hands.

I always test my MODs and apps before releasing but I could try few things without watch...
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] tasaly:
1 I want a setting.apk modified (like the one of jelly bean) and how to use it for s6102

2 can i use the themes of y for y dous
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] tasaly:
helppppppppppppp
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] TheFixItMan:
1 . questions go in the q & a section NOT a dev section

2. look in the theme section

3. depends what the theme is eg you cant use a systemui.apk from a 5360 in duos without modding it first

4. search for guides in order to do things