Related
I just received by Chromecast today and I have an older TV. I am using an HDMI to DVI converter so no sound is being transferred.
Would it be possible to keep audio playback on the controlling device instead of the TV?
apandhi said:
I just received by Chromecast today and I have an older TV. I am using an HDMI to DVI converter so no sound is being transferred.
Would it be possible to keep audio playback on the controlling device instead of the TV?
Click to expand...
Click to collapse
Not that I know of. You could get an audio adapter, but it would cost more than the device. Best bet is that we can get a client ready for the Raspberry Pi, and that can use 3.5 audio.
I doubt it. The clever bit about the Chromecast is that *it* decodes the incoming stream; once started you can turn off "the controlling device" & everything will continue to run undisturbed.
To decode the incoming stream and send the video to HDMI but redirect the audio portion as an outgoing stream to another device...
I suspect that is too much of an edge case.
Your setup, as it stands, appears incompatible with how the Chromecast operates. I'd look into returning the Chromecast as unsuitable, resell it, or invest in DVI+audio out hardware or go HDMI.
Your Milage May Vary.
Sent from my SGH-T999 using Tapatalk 4 Beta
Maggard said:
I doubt it. The clever bit about the Chromecast is that *it* decodes the incoming stream; once started you can turn off "the controlling device" & everything will continue to run undisturbed.
To decode the incoming stream and send the video to HDMI but redirect the audio portion as an outgoing stream to another device...
I suspect that is too much of an edge case.
Your setup, as it stands, appears incompatible with how the Chromecast operates. I'd look into returning the Chromecast as unsuitable, resell it, or invest in DVI+audio out hardware or go HDMI.
Your Milage May Vary.
Sent from my SGH-T999 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Might be able to use a USB sound dongle if root will let you. So I guess keep some hope alive.
INCORRECT, SEE NEXT POST FROM CHARLIE460
OLD, WRONG, POST: Not to be negative, but from the hardware descriptions the µUSB port is power only, the data lines aren't even connected.
Maggard said:
Not to be negative, but from the hardware descriptions the µUSB port is power only, the data lines aren't even connected.
Sent from my SGH-T999 using Tapatalk 4 Beta
Click to expand...
Click to collapse
You would be incorrect, custom image has been flashed via OTG already.
http://www.gtvhacker.com/index.php/Google_Chromecast#Bootloader_Exploit_Package
Correction noted
Sent from my SGH-T999 using Tapatalk 4 Beta
Chromecast HDMI to VGA + analog audio
http://www.svideo.com/cc2vga.html
$60
dkerlee said:
http://www.svideo.com/cc2vga.html
$60
Click to expand...
Click to collapse
Looks interesting. Do you know how it handles the signal timings? That will determine how compatible the device is with VGA devices. Not all devices that accept VGA will accept video 720p or 1080p resolutions correctly displayed and centered.
bhiga said:
Looks interesting. Do you know how it handles the signal timings? That will determine how compatible the device is with VGA devices. Not all devices that accept VGA will accept video 720p or 1080p resolutions correctly displayed and centered.
Click to expand...
Click to collapse
Well he was already using a DVI adaptor so chances are likely he will not have many issues displaying 720 or 1080 since any monitor with a DVI will in most cases do well above those resolutions....
but the problem he is going to run into is that things like Netflix are probably going to require HDCP which he won't get with that device.
And no converter device or adapter available will ever get him the HDCP.
Asphyx said:
And no converter device or adapter available will ever get him the HDCP.
Click to expand...
Click to collapse
HDfury is HDCP-compliant but not available in some regions for legal reasons.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
Hi @all,
I've a problem with Chromecast. My setup is that I'm using an Onkyo receiver which has plenty of HDMI slots. Since I've no TV I've connected a monitor to the Onkyo. Unfortunately the monitor works at best in 720p (I've also attached a PS3 to the system where I'm also using 720p)...
So my question is, can I force Chromecast to output its HDMI signal in 720p. I don't have any image at the moment, with the exception during booting... (I see the Chrome Logo).
Any ideas????
ccflo said:
Hi @all,
I've a problem with Chromecast. My setup is that I'm using an Onkyo receiver which has plenty of HDMI slots. Since I've no TV I've connected a monitor to the Onkyo. Unfortunately the monitor works at best in 720p (I've also attached a PS3 to the system where I'm also using 720p)...
So my question is, can I force Chromecast to output its HDMI signal in 720p. I don't have any image at the moment, with the exception during booting... (I see the Chrome Logo).
Any ideas????
Click to expand...
Click to collapse
720p is the highest and I believe the default that chromecast outputs at. You can change to 720p high or low bitrate, or 480p via the chrome browser extension.Sorry I was thinking about tab casting when I read the OP.
supernova_00 said:
720p is the highest and I believe the default that chromecast outputs at. You can change to 720p high or low bitrate, or 480p via the chrome browser extension.
Click to expand...
Click to collapse
That's false. That setting is only for the resolution of the tab-casting. Not the output of the Chromecast. Chromecast outputs a 1080p signal. (https://play.google.com/store/devices/details?id=chromecast). I beleive it even upscales lower resolution content to 1080 but I can't confirm on my current setup.
rekh127 said:
That's false. That setting is only for the resolution of the tab-casting. Not the output of the Chromecast. Chromecast outputs a 1080p signal. (https://play.google.com/store/devices/details?id=chromecast). I beleive it even upscales lower resolution content to 1080 but I can't confirm on my current setup.
Click to expand...
Click to collapse
Thank you so far.... yes, it is about the signal what's coming out of the chromecast not about casting! I definitely need 720p and I hope somebody can tell me how to force this device to do this.... Normally you could do this on any device (PCs, PS3, Xbox, Ouya...).
I'm really open to any advice.
Hi, I'm wondering if you found any answer to forcing(?) chromecast to a certain resolution. I'm wondering if the chipset inside the stick is capable of outputting anything other than 1080P? In my case I have to have 480P or 1080i (my TV is too old that it doesn't even accept 720P <LOL>). I know the Roku3 won't output anything lower than 720P so I'm wondering what the chip inside chromecast is capable & if there are ways to turn the switches on/off?
I'm still searching for a solution... none found yet.
What I figured out is that Chromecast can detect what the device can display at maximum. There is a standard to this...
But in my case (the AV receiver which accepts full resolution but the display not) I can't force it to do this... I submitted a feature request at Google help... I also read that people claim Google are very much interested in getting feedback... so I did what I can do.
So for now my Chromecast is just an Audio Stream adapter... but a quite good one so net completely useless for me
Thank you for the heads-up and I'm glad you are getting use out of it
Been looking around and found some info on the variant of SoC that is in the stick (from Marvell) as that thread suggested the info on Marvell site is thin and nothing about resolution. I sent an inquiry to their sales support but since I'm not looking to buy a lot of 10k of those SoC on the pallet so I'm not holding my breath for an answer. Also the thread said that it is not quite the same SoC so they were suspecting a neutered on customized for Google.
ccflo said:
I'm still searching for a solution... none found yet.
What I figured out is that Chromecast can detect what the device can display at maximum. There is a standard to this...
But in my case (the AV receiver which accepts full resolution but the display not) I can't force it to do this... I submitted a feature request at Google help... I also read that people claim Google are very much interested in getting feedback... so I did what I can do.
So for now my Chromecast is just an Audio Stream adapter... but a quite good one so net completely useless for me
Click to expand...
Click to collapse
I have a similar problem, as I'm trying to run my Chromecast on a non-TV.
Short of Google giving options (which would be GREAT - most HDMI sources allow selecting what resolution gets sent), you could use an in-line EDID "injector" like Gefen HDMI Detective. They also have a DVI version of it called DVI Detective.
EDIT: Another option may be the Dr HDMI
In your case I would set the HDMI Detective to report that it only supports 480P and 720P resolutions and put it after your receiver (between receiver and monitor), so all your devices see proper progressive-only EDID.
Alternatively you could try to see if you can reprogram your monitor's EDID (via something like Powerstrip), though that's significantly more dangerous especially if you're a novice.
bhiga said:
I have a similar problem, as I'm trying to run my Chromecast on a non-TV.
Short of Google giving options (which would be GREAT - most HDMI sources allow selecting what resolution gets sent), you could use an in-line EDID "injector" like Gefen HDMI Detective. They also have a DVI version of it called DVI Detective.
EDIT: Another option may be the Dr HDMI
In your case I would set the HDMI Detective to report that it only supports 480P and 720P resolutions and put it after your receiver (between receiver and monitor), so all your devices see proper progressive-only EDID.
Alternatively you could try to see if you can reprogram your monitor's EDID (via something like Powerstrip), though that's significantly more dangerous especially if you're a novice.
Click to expand...
Click to collapse
The Gefen is $129 and the Dr. HDMI is $399!
He'd be better off buying a new Monitor.
Dr. HDMI is only $99 (full boat HDfury3 is $399, Dr. HDMI is down past). But I agree, if money is to be thrown at the problem it's poetically better spent on a new monitor, unless you have something special.
Sent from my SAMSUNG-SGH-I747 using Tapatalk now Free
bhiga said:
Dr. HDMI is only $99 (full boat HDfury3 is $399, Dr. HDMI is down past). But I agree, if money is to be thrown at the problem it's poetically better spent on a new monitor, unless you have something special.
Sent from my SAMSUNG-SGH-I747 using Tapatalk now Free
Click to expand...
Click to collapse
OK, thanks for the correction. I clicked the buy now button and it showed up as $399, and I thought somethings wrong here.
OP, What monitor do you have? Does it not show any picture or is the picture quality just not good?
I recently did a search for best TV under $500 and their are some decent options for the money. My parents just picked up a 32" LCD TV from Costco on clearance for $180. It a Sceptre and 720p, but looks good and can handle a 1080p feed. It was on clearence, so might be hard to find at that price, but you can get a decent TV on the cheap with a little legwork.
Good luck.
FWIW as a test I have my Chromecast running to a Planar 1024x768 VGA monitor through a HDfury2.
The Planar says it's getting a 1280x720 signal, and I can tell from the green tint that it's receiving YPbPr (aka YUV).
So Chromecast definitely can output 720p if it thinks that's all the monitor can accept.
and I meant "probably" not "poetically" heh
any news?? I have a 720p projector connected to the onkyo. The chromecast doesn´t appear...
psikonetik said:
any news?? I have a 720p projector connected to the onkyo. The chromecast doesn´t appear...
Click to expand...
Click to collapse
If you wall power Chromecast and boot it directly connected to the projector with the projector on, do you get picture?
-= this post enhanced with bonus mobile typos =-
bhiga said:
If you wall power Chromecast and boot it directly connected to the projector with the projector on, do you get picture?
-= this post enhanced with bonus mobile typos =-
Click to expand...
Click to collapse
When the screen says "starting...." I can see the picture well, I guess its on 720p, then it appears chromecast logo blurry and then a red noise digital noise screen.
I guess I need to change chromecast output resolution...
psikonetik said:
When the screen says "starting...." I can see the picture well, I guess its on 720p, then it appears chromecast logo blurry and then a red noise digital noise screen.
I guess I need to change chromecast output resolution...
Click to expand...
Click to collapse
IIRC the boot screen is 480p.
This could be a failure of resolution negotiation (projector tells Chromecast it supports a resolution it can't handle) or missing/broken HDCP support on the projector.
Unfortunately you can't force Chromecast to a specific resolution so you'd have to control the reported supported resolutions with Dr. HDMI or similar that I mentioned earlier in the thread.
Is the digital noise blocky or more like fine random colored pixels?
-= this post enhanced with bonus mobile typos =-
The digital noise are red vertical lines at the screen, if I press the home button on my onkyo remote it changes to the casted image in 4 squares disorganized...
I find dr HDMI very expensive and I don´t think google will solve this issue. Maybe scene will do it eventually.
Well now I have a music streamer hehe, maybe I'll buy an fire tv or an apple tv...
Thanks a lot!
psikonetik said:
The digital noise are red vertical lines at the screen, if I press the home button on my onkyo remote it changes to the casted image in 4 squares disorganized...
Click to expand...
Click to collapse
Interesting. Definitely sounds like your projector doesn't like what Chromecast is sending, maybe it doesn't like 1080p. Regardless, considering the cost of Chromecast I would just use it on another display or gift it to someone else and go with a more "full" player.
-= this post enhanced with bonus mobile typos =-
We have a MiraCast capable dongle that I'd like to try connecting to with my Nook. I'm runing CM 10.1.3 right now, which I think is a new enough version of Android, and I don't see any Miracast options in the Display settings. Is it just not in the CM builds for Nook HD+?
Thank you!
Bump. Any news on Miracast support? I'm also interested.
Sent from my BN Nook HD using Tapatalk
Yeah I would also love this feature added.
So I upgraded to CM11 last night. I noticed that Miracast support appears to be present in it. I tried it, but it doesn't see either of the Miracast capable devices near me (one Netgear and one Actiontec). My Nexus 5 sees both.
Assuming the support isn't disabled in some other way, I'm guessing that the hardware in the Nook HD+ may not be sufficient. I wouldn't be surprised if there was a dual radio requirement for miracast to work. You wouldn't be able to have network access and cast at the same time if you didn't have dual radios for instance.
Thanks! I also installed cm11 and noticed the option. Tried to connect to my Sony TV, but it doesn't appear be able to see the TV. I hope it is not a hw limitation...
Sent from my BN Nook HD using Tapatalk
colema19 said:
So I upgraded to CM11 last night. I noticed that Miracast support appears to be present in it. I tried it, but it doesn't see either of the Miracast capable devices near me (one Netgear and one Actiontec). My Nexus 5 sees both.
Assuming the support isn't disabled in some other way, I'm guessing that the hardware in the Nook HD+ may not be sufficient. I wouldn't be surprised if there was a dual radio requirement for miracast to work. You wouldn't be able to have network access and cast at the same time if you didn't have dual radios for instance.
Click to expand...
Click to collapse
I am running CM11 on my Nook HD and have been able to successfully use Miracast only from the YouTube app. No other connection attempt seems to work, but YouTube definitely does. Quality is not particularly good, though.
danshane said:
I am running CM11 on my Nook HD and have been able to successfully use Miracast only from the YouTube app. No other connection attempt seems to work, but YouTube definitely does. Quality is not particularly good, though.
Click to expand...
Click to collapse
Are you talking about Chromecast? It doesn't sound like you are talking about Miracast. They aren't the same thing, if you are.
colema19 said:
Are you talking about Chromecast? It doesn't sound like you are talking about Miracast. They aren't the same thing, if you are.
Click to expand...
Click to collapse
I do not have Chromecast. It is definitely Miracast that I am referring to. Miracast is a feature on my Panasonic Blu-ray player, and the Android YouTube app specifically requests to connect to Miracast, not Chromecast.
danshane said:
I do not have Chromecast. It is definitely Miracast that I am referring to. Miracast is a feature on my Panasonic Blu-ray player, and the Android YouTube app specifically requests to connect to Miracast, not Chromecast.
Click to expand...
Click to collapse
Ah cool, I didn't realize that there were devices with Miracast support. So, I'm not surprised that Youtube looks bad. Were you watching a HD video, and in HD? If not, it was upscaled, which would mean it looks awful.
colema19 said:
Ah cool, I didn't realize that there were devices with Miracast support. So, I'm not surprised that Youtube looks bad. Were you watching a HD video, and in HD? If not, it was upscaled, which would mean it looks awful.
Click to expand...
Click to collapse
I was watching an HD (720p) video on YouTube. It looked more like SD on my 73" DLP TV. I streamed the same video through the YouTube app on my Panasonic BD player and the resolution was great.
So in my opinion, based only on my experience, Miracast does not work any better than Chromecast when it comes to redirecting video from a tablet or phone (though the concept is undoubtedly cool). Direct connection still wins out.
build.prop hack to enabling Miracast option.
Code:
$ adb root
$ adb remount
$ adb pull /system/build.prop
(add persist.debug.wfd.enable=1 to build.prop)
$ adb push build.prop /system/
$ adb shell chmod 644 /system/build.prop
$ adb reboot
after editting build.prop, settings -> display -> Cast screen -> Wireless Display check option appears.
but this is only option showing hack. I don't know your device Miracast compatibility.
s107ken, how to use this code? paste it in build.prop?
RumBle said:
s107ken, how to use this code? paste it in build.prop?
Click to expand...
Click to collapse
It probably won't matter. I didn't realize at the time I asked, that the Nook HD+ doesn't have the hardware to support miracast (dual wifi radios).
I try to use this code, not work.
Sent from my HTC One X+ using XDA Free mobile app
A year later, still can't Cast Screen using Miracast to my Roku3 (as a Miracast receiver)...
shdware said:
A year later, still can't Cast Screen using Miracast to my Roku3 (as a Miracast receiver)...
Click to expand...
Click to collapse
It will never work. The Nook HD+ does not have the required hardware to support Miracast.
colema19 said:
It will never work. The Nook HD+ does not have the required hardware to support Miracast.
Click to expand...
Click to collapse
I'm not entirely sure of that.
Kensuke has apparently been successful with miracast on OMAP.
https://github.com/kensuke/How-to-Miracast-on-AOSP/wiki
Also TI has a page on wi-fi direct,
http://processors.wiki.ti.com/index...tivity_NLCP_WiFi_Direct_Configuration_Scripts
Unfortunately his patches are for AOSP. Although it appears he also developed some patches for CM11.
http://forum.xda-developers.com/showpost.php?p=49265142&postcount=118
If someone could convince him to release his CM11 patches source....
until then it would be worth a try to install his miracast update on CM11. (The libraries should be very similar to ours anyway.)
http://forum.xda-developers.com/attachment.php?attachmentid=2505154&d=1389302451
colema19 said:
It probably won't matter. I didn't realize at the time I asked, that the Nook HD+ doesn't have the hardware to support miracast (dual wifi radios).
Click to expand...
Click to collapse
miracast doesn't required dual wifi, require wifi direct support.
Nexus 7 2012 has 2.4Ghz wifi only but miracast is working.
first, nook supported wifi direct?
https://github.com/kensuke/How-to-Miracast-on-AOSP/wiki/How-to-use-Miracast?#wi-fi-wi-fi-direct
if failed changes device name, it's meaning don't support wifi direct, the another problem for miracast.
Sent from my GT-I9305 using XDA Free mobile app
s107ken said:
miracast doesn't required dual wifi, require wifi direct support.
Nexus 7 2012 has 2.4Ghz wifi only but miracast is working.
first, nook supported wifi direct?
https://github.com/kensuke/How-to-Miracast-on-AOSP/wiki/How-to-use-Miracast?#wi-fi-wi-fi-direct
if failed changes device name, it's meaning don't support wifi direct, the another problem for miracast.
Sent from my GT-I9305 using XDA Free mobile app
Click to expand...
Click to collapse
I don't think it needs dual band. I think it needs dual radios. Wifi direct is a requirement yes, but I think dual radios is also a requirement because otherwise it cannot maintain a network connection at the same time. Strictly speaking it shouldn't need a network connection as well, but I haven't seen anything that has Miracast that doesn't have dual radios I have 3 miracast capable devices, and all have dual radios. I have gone through several devices that have miracast options, but drop immdiately after a connect attempt because the device attempts to re-grab the wifi device to use as a network connection, which interrupts the Miracast Wifi direct connection. That's why you need 2 radios, one for the Wifi direct, one for Android to use as an active network connection. Or at least to grab onto and not interfere with the Miracast connection. I'd be happy to be incorrect here, but my experience suggests that is the issue.
Sorry, correction here, it isn't dual radios that I think are needed, but dual antennas (I got the hardware piece wrong in my head). It is interesting though, that page says that he's got it working on a 2012 Nexus 7 which I believe is only a single antenna. So maybe I am way wrong here.
But, that said, I still stand by what my experience has been thus far...everything that does work has dual antennas, and everything that doesn't, doesn't have dual antennas. It could very well be in the case that you don't have dual antennas, the radio hardware itself becomes much more critical, so maybe why it may work in that Nexus 7 but hasn't worked in my devices.
Hello there,
When I plug my chromecast in my TV (chromecast is already configurated with the wifi network etc), and I boot it up, I see the boot logo, then black screen.
I already tested the chromecast on my external screen: it's working sweet on my external screen.
Lots of people have the same issue: this is related due unable to specify the output resolution of the chromecast.
My TV supports 1080i, but not 1080p. Chromecast thinks it supports 1080p, so it sends an unsupported signal to the tv, in technical terms we call it a HDMI EDID fail.
This can be fixed if they make an option for it to select the output signal. Unfortunately this is unavailable in the menu.
There MUST be a way to manually set the output signal. I know you can send commands via CURL;
For example: to force update the chromecast instead of the lame wait-timespan of 2 weeks to receive the update:
curl -X POST -H "Content-Type: application/json" -d '{"params": "ota foreground"}' http : // <chromecastIp>:8008/setup/reboot -v
So I guess there is also a setting for the output? What is the command for that?
FAQ:
TV model: 32PF9531/10
Kind regards,
Vincent
I always thought it was a HDCP issue. I've had this problem on my Sony Plasma for about 9 months now. Happens on both rooted and non rooted Chromecasts. My solution was to buy a Hdmi to rgb converter.
Sent from my Nexus 10 using XDA Premium 4 mobile app
Markyzz said:
I always thought it was a HDCP issue. I've had this problem on my Sony Plasma for about 9 months now. Happens on both rooted and non rooted Chromecasts. My solution was to buy a Hdmi to rgb converter.
Sent from my Nexus 10 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi there,
Thank you for your reply!
I haven't discovered the area of the rooted chromecasts (yet).
Can you place the model/product name of your converter?
If it doesn't cost much, I will buy the same one and end this endless search.
I already bought an hdmi to VGA adapter from ebay, but that didn't worked.
Kind regards,
vincent
So i have top tier problem
When i turn on my chromecast screen is just black it shows Chromecast.... then google logo aka multi color G and then just black screen if i stream stuff it does output audio (chromecast audio update jokesaside) i tried 2 chromecasts and both same effect (chromecast 1st,2ndgen) question is are there any ways to fix this as in shop they will throw bricks at me if i bring another chromecast claiming that its faulty :silly::silly::silly::silly:
It could have an issue with your WiFi.
Try it on a different one.
If I remember right, at least the 1st gen, supports only 2.4GHz routers.
So find one, or try it on a few.
wolfaas12345 said:
So i have top tier problem
When i turn on my chromecast screen is just black it shows Chromecast.... then google logo aka multi color G and then just black screen if i stream stuff it does output audio (chromecast audio update jokesaside) i tried 2 chromecasts and both same effect (chromecast 1st,2ndgen) question is are there any ways to fix this as in shop they will throw bricks at me if i bring another chromecast claiming that its faulty :silly::silly::silly::silly:
Click to expand...
Click to collapse
I think it has something to do with your screen, is it a 720p or a 1080P?
mnd86 said:
I think it has something to do with your screen, is it a 720p or a 1080P?
Click to expand...
Click to collapse
I made a hackish bypass i bought a hdmi to av converter and connected it to av but when it comes to tv its 1366x768
wolfaas12345 said:
I made a hackish bypass i bought a hdmi to av converter and connected it to av but when it comes to tv its 1366x768
Click to expand...
Click to collapse
I have like the same setup like you so unfortunately there is no fix. Chromecast will work only on the formats 720p or 1080p. I purchased a cheap Miracast dongle and works like a charm on a set-up like yours. Unless the converter can be setup to 720p you will be able to use it...