Hello,
I just got my Chromecast and it is pretty awesome. It's going to be great for business travel and I want to watch Netflix and stuff. I do have one concern though. When I first installed the Chromecast, my TV wouldn't recognize the HDMI signal. It was saying "no signal detected" our something along those lines. I unplugged the Chromecast from the TV and plugged it back in and out worked like a charm. I'm not an expert with how HDMI works, but should this be a cause for concern? I've tried to recreate the problem by unplugging it and plugging it back in (and even having it half plugged in) and I wasn't able to make the problem occur again. I guess I would just like some opinions. After all, I don't want to have a faulty unit, and if I do, I want to exchange it before my local Best Buy sells out.
Thanks!
thenoname said:
Hello,
I just got my Chromecast and it is pretty awesome. It's going to be great for business travel and I want to watch Netflix and stuff. I do have one concern though. When I first installed the Chromecast, my TV wouldn't recognize the HDMI signal. It was saying "no signal detected" our something along those lines. I unplugged the Chromecast from the TV and plugged it back in and out worked like a charm. I'm not an expert with how HDMI works, but should this be a cause for concern? I've tried to recreate the problem by unplugging it and plugging it back in (and even having it half plugged in) and I wasn't able to make the problem occur again. I guess I would just like some opinions. After all, I don't want to have a faulty unit, and if I do, I want to exchange it before my local Best Buy sells out.
Thanks!
Click to expand...
Click to collapse
I wouldn't worry unless I see it again multiple times
could be a fluke... we all know how hdcp/drm can mess things up
I can't get a signal on any of my tvs. Worked last night unplugged it during the day and tonight doesn't even show a signal.
Could the hdmi plug be damaged?
Sent from my SGH-M919 using xda premium
paperWastage said:
I wouldn't worry unless I see it again multiple times
could be a fluke... we all know how (link omitted since xda won't let me post links yet ) hdcp/drm can mess things up
Click to expand...
Click to collapse
Thanks for the info! I didn't realize HDMI did a handshake before connecting. If I see it again, I'll worry more. I think if I see it again, I'll either take it back to BestBuy or contact Google for a warranty replacement. Do you know how I would do that? I can't seem to find a support website for the Chromecast.
scoop_dtx said:
I can't get a signal on any of my tvs. Worked last night unplugged it during the day and tonight doesn't even show a signal.
Could the hdmi plug be damaged?
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
I would try a factory reset either by using the desktop app or by holding the button on the back for 25 seconds. Also, even though I don't need it, I use the HDMI extender that comes with the Chromecast for two reasons:
1) so when I'm moving it around my house, I don't have to unplug and replugin the actual unit. If the pins on the extender get damaged, its cheaper and easier to replace.
2) for stress relief so the unit doesnt get bent/pulled down over time.
I managed to get two Chromecasts from Amazon via relatives in the USA. The one at my sons house installed and worked immediately. Very impressed down in sunny Southampton.
In my case, I've got mine plugged into a Toshiba 37X3030D TV, which is full 1080p. However, all I get is a blue screen and no sound on either of he two HDMI ports.
I've managed to install it blind using the Chromecast app on my MacBook Air (at least after I turned AP Isolation off on my Netgear router), and both my Mac and Chromebook Pixel think they are successfully streaming to it.
Any ideas what could be wrong? Any help, guidance or pointers would be really appreciated.
Sounds like it's time to call Google or Customer Support... can't fix hardware issues and so far this thing isn't hacked open very much to look at any software problems.
IanWaring said:
I managed to get two Chromecasts from Amazon via relatives in the USA. The one at my sons house installed and worked immediately. Very impressed down in sunny Southampton.
In my case, I've got mine plugged into a Toshiba 37X3030D TV, which is full 1080p. However, all I get is a blue screen and no sound on either of he two HDMI ports.
I've managed to install it blind using the Chromecast app on my MacBook Air (at least after I turned AP Isolation off on my Netgear router), and both my Mac and Chromebook Pixel think they are successfully streaming to it.
Any ideas what could be wrong? Any help, guidance or pointers would be really appreciated.
Click to expand...
Click to collapse
Has it done a software update yet? Lots of people were having issues with it working in their HDMI ports, until the software updates were pushed to it.
Have you tried doing a factory reset?
Seen the Chrome logo briefly!
Did a reboot using the Mac Chromecast app and briefly saw the Chrome logo on restart - then back to the blue screen.
I can't see what version of the firmware it's running, as neither the Mac app or anything on my Pixel or iOS devices can relay this data.
My sons one worked first time on his, so I will call Toshiba support next working day to see if they have firmware > 2.9 for my 37X3030D, hoping that may fix things. The TV should work on all the various US and UK line resolutions, 418i to 1080p. And will leave the Chromecast on just in case it picks up any updates.
Try doing the factory reset, not a reboot, using the button on the Chromecast next to the power cable. Press it for 15 - 20 seconds while it is powered up.
Done that
maelias said:
Try doing the factory reset, not a reboot, using the button on the Chromecast next to the power cable. Press it for 15 - 20 seconds while it is powered up.
Click to expand...
Click to collapse
Chrome logo appears, spins, and then back to BSOD colour. Stil on the 12840 release though...
Fixed!
I rebooted the Chromecast this morning and it did a software update - with all progress viewable on the screen. On completion, up it came, Ready to cast. So, very happy, all working fine.
Hello all,
This is my first post on XDA Dev.
I bought a Chromecast last week and plugged it in and set it all up. So far I am well impressed with it except for 1 thing. When I go to cast from YouTube either via my phone, tablet or laptop to my TV it sounds like the people are under water. When I cast my chrome browser tab with YouTube loaded and enlarge the video it sounds perfect.
I just cant quite get my head around why its doing this. All other apps like BBC iPlayer work a charm with no problems whatsoever.
I've powered things down, tried to plug into different HDMI ports, tried different power sockets and USB ports but still it's the same.
Any ideas chaps?
thanks.
Have you tried completely resetting the Chromecast recently, via your laptop I believe?
Sent from my Galaxy S5
Hi there,
I have reset the thing numerous times from using the button to using my phone and laptop. Still no joy.
Does the chromecast depend on certain TV drivers / firmware? I must admit I have never updated my TV since getting it and do not even know if there are any new downloads for it to be honest.
The TV I have is a Samsung UE55B7000 and the firmware that I am using is T-CHU7DEUC-2009.0 (so quite old)
Cheers
I've recently bought the new vw golf with the android auto function. I've updated my galaxy note 3 to the latest lollipop 5.0 UK version so i can use AA.
The phones initial connection is fine. Open the AA app, connect USB to car, car recognises the phone via AA. Phone changes connection type to USB instead of Media. AA app then prompts a few questions (as its new connection to the car) and then AA is good to go on the car screen.
All is well until the next time i hop into the car and connect the USB to the phone. you would a expect that as my phone made an initial connection, the car should be able to pick it up and AA will then load up. However the car display will keep going into a loop where it tries to read my phone but connection keeps failing. likewise for my phone it will keep shifting between connection as media and connection as USB (which is the connection type for AA). AA wouldn't load at all on my phone. i go into the app and tried connecting again but the app will just quit by itself. i've tried USB debugging, no luck. i'm using the samsung original USB cable so didn't think there would be issue here.
the funny thing is that i figured that in order to get AA to connect successfully is to go into the app and go to the settings to forget the car that i initially had it connected to. so next time i plug in the usb and go into the app, it will start the new connection prompts and voila it will work again. but next time i plug in the phone it will just go back to the connection loop and won't be able to trigger AA to load on the phone.
there was only one time that the phone managed to connect to the car and load AA without the need to forget car and connect as new. its very hit and miss and i'm not sure whether this is a bug in the app or the car's.
anyone else having similar connection issues?
AA is buggy but I'd have to say......
rafalucas said:
I've recently bought the new vw golf with the android auto function. I've updated my galaxy note 3 to the latest lollipop 5.0 UK version so i can use AA.
The phones initial connection is fine. Open the AA app, connect USB to car, car recognises the phone via AA. Phone changes connection type to USB instead of Media. AA app then prompts a few questions (as its new connection to the car) and then AA is good to go on the car screen.
All is well until the next time i hop into the car and connect the USB to the phone. you would a expect that as my phone made an initial connection, the car should be able to pick it up and AA will then load up. However the car display will keep going into a loop where it tries to read my phone but connection keeps failing. likewise for my phone it will keep shifting between connection as media and connection as USB (which is the connection type for AA). AA wouldn't load at all on my phone. i go into the app and tried connecting again but the app will just quit by itself. i've tried USB debugging, no luck. i'm using the samsung original USB cable so didn't think there would be issue here.
the funny thing is that i figured that in order to get AA to connect successfully is to go into the app and go to the settings to forget the car that i initially had it connected to. so next time i plug in the usb and go into the app, it will start the new connection prompts and voila it will work again. but next time i plug in the phone it will just go back to the connection loop and won't be able to trigger AA to load on the phone.
there was only one time that the phone managed to connect to the car and load AA without the need to forget car and connect as new. its very hit and miss and i'm not sure whether this is a bug in the app or the car's.
anyone else having similar connection issues?
Click to expand...
Click to collapse
I think this is your radio hardware and not the AA app. But you never really disclosed what phone you are using and if it has been modified or what so there is no clear help answer that I can assist you with.
hi, i've got the Note 3 (SM-N9005) running stock lollipop 5.0 (baseband N9005XXUGBOI2). my phone was previously running 4.4.2 kitkat with root.
the connection is very hit and miss. it will keep trying to read my phone when plugged to the car and the phone will keep shifting between "connected as a media device" or "connected as a USB accessory". When its connected as usb accessory, the phone screen will black out for a second and then goes back into the previous screen which is usually home page of the launcher. i think the "blackout" might be the phone trying to boot or load android auto app but gets disconnected as it tries to get in.
i have to plug the usb in and out a few times and sometimes by lottery, it will establish a successful connection and AA loads on the car screen. i've found that if i open the app first on the phone and then plug in the usb, it will have higher chance of getting a successful handshake.
hope this makes sense.
I have the exact same issue: VW App-Connect in a new 2016 vehicle with a Galaxy S5 running Lollipop. Very annoying because once the two are connected it does work reasonably well.
rafalucas said:
I've recently bought the new vw golf with the android auto function. I've updated my galaxy note 3 to the latest lollipop 5.0 UK version so i can use AA.
The phones initial connection is fine. Open the AA app, connect USB to car, car recognises the phone via AA. Phone changes connection type to USB instead of Media. AA app then prompts a few questions (as its new connection to the car) and then AA is good to go on the car screen.
All is well until the next time i hop into the car and connect the USB to the phone. you would a expect that as my phone made an initial connection, the car should be able to pick it up and AA will then load up. However the car display will keep going into a loop where it tries to read my phone but connection keeps failing. likewise for my phone it will keep shifting between connection as media and connection as USB (which is the connection type for AA). AA wouldn't load at all on my phone. i go into the app and tried connecting again but the app will just quit by itself. i've tried USB debugging, no luck. i'm using the samsung original USB cable so didn't think there would be issue here.
the funny thing is that i figured that in order to get AA to connect successfully is to go into the app and go to the settings to forget the car that i initially had it connected to. so next time i plug in the usb and go into the app, it will start the new connection prompts and voila it will work again. but next time i plug in the phone it will just go back to the connection loop and won't be able to trigger AA to load on the phone.
there was only one time that the phone managed to connect to the car and load AA without the need to forget car and connect as new. its very hit and miss and i'm not sure whether this is a bug in the app or the car's.
anyone else having similar connection issues?
Click to expand...
Click to collapse
I believe Verizon phones were having USB connection issues because of some special app they had that did stuff over USB, and an update fixed it.
Some USB connection issues can be solved by changing the mode of USB: MTP, Charge Only, etc.
Some issues can be worked around by enabling (or disabling) USB debugging. This is under Developer settings after Dev mode is entered by tapping Build number 7 times.
Hi Mike, I've got an Australian stock unbranded note 3.
i've spoken to the vw dealer and apparently vw is working diligently for a software upgrade to the car's infotainment system which may or may not fix the connectivity issue.
it's just frustrating that in order to get a consistent connection, i have to go into the app and "forget" the car, then it will go through the new connection prompts.
i'm hoping the next app update might fix the issue but at the moment its unclear whether its the app, or my phone or the car's problem.
I have similar issues with my 2016 Skoda Fabia Combi. I'm guessing the infotainment system in the Skoda is pretty much the same as in the Volkswagen. Many parts are because Skoda is owned by VW. After tons of trial and error, I've had some success connecting my LG G3 but first let me tell you how I ended up in the current situation.
I have tried to connect thee different android devices (LG G3, HTC One M7 and Nexus 7 tablet all running Lollipop) with bunch of different USB cables. The result is always the same. On the phone I see black screen flashing before it returns to home screen and nothing else happens. From the recent apps view I can see that the black screen was AA trying to launch. CarPlay with iPhone works fine.
I live in Finland so I have sideloaded the AA app and at first I thought that the issue is caused by AA not being officially available here yet. After searching this forum and other android forums I found out that other people are having the same issues in countries where AA is supported so maybe this is not the case. Obviously it's not also a device problem because I get exactly same results with different devices from different manufacturers. Only common nominator seems to be the VW/Skoda infotainment system? Correct me if I'm wrong here..
In the Skoda smartlink menu you can choose your preferred connection protocol from Android Auto and Mirrorlink. This affects the order the car attempts to establish the connection. I read from a Skoda forum that someone had a successful connection after he had changed these options around so I tried it. I checked Mirrorlink as a preferred method and tried the connection: no luck. I changed back to AA as preferred method and to my amazement after this the AA launched on the phone and I had a successful connection! If the VW has similar option I suggest you VW guys also try this.
My current situation is that most of the time the phone does not connect at first try but after changing the preferred method around it does. I have also other issues with AA. After connecting I cannot adjust the volume first from steering wheel/stereo volume knob. Spotify audio goes to a wrong channel at first (I can hear it only when i activate voice command) After changing music app to Google Play Music and then back to Spotify it starts working normally and I can also adjust volume. And of course the restriction on browsing your Spotify library. It is the most stupid thing I've ever seen at that level of software development.
rafalucas said:
Hi Mike, I've got an Australian stock unbranded note 3.
i've spoken to the vw dealer and apparently vw is working diligently for a software upgrade to the car's infotainment system which may or may not fix the connectivity issue.
it's just frustrating that in order to get a consistent connection, i have to go into the app and "forget" the car, then it will go through the new connection prompts.
i'm hoping the next app update might fix the issue but at the moment its unclear whether its the app, or my phone or the car's problem.
Click to expand...
Click to collapse
Auto dealers tend to know almost nothing about software and smartphones. They know how to sell cars, and the mechanics tend to know how to fix them mechanically, more or less.
And they can almost always say that there is likely an update due at some point.
If you, or anyone having a problem on the car/HU side, has a USB OTG cable and a bit of time to test, you should consider trying my Headunit app; see my sig.
If you get it working you can get a better idea if your car HU is at fault.
I wonder if there are car stereo shops where you can plug your phone into a Pioneer AA unit, like 4100NEX, and see if it works OK on that.
I've had my 2015 Seat Leon (also VW group) for four months now and also having trouble with Android Auto through the SEAT 'Full Link' connection. It seems to be russian roulette whether it'll make a connection and start AA when you plug it in. Sometimes you'll get a 'Connection failed' message, other times you will see the system try AA, fail, then try MirrorLink then fail on that too (as my Nexus 5 doesn't support MirrorLink). As others have said you see the phone screen go black then crash out and goes back to the home screen.
The only solution I have is to restart my phone and try again. Its almost my routine now to restart my phone just before I know I'm about to go for a drive. It beats having to sit in the car watching my phone reboot before I set off!
I didn't know you can change the USB settings on the phone, so I'm going to go through the various settings in developer options to see if any of these help. I'm thinking 'Charge only' might be useful, unless AA needs MTP or network connection to operate?
seems like i'm not the only one! sounds to me its more and more likely to do with the vw made headunit (could be the firmware). I just tried a mate's phone with the AA app but it also went in a connection loop before finally establishing a handshake with the phone. hopefully next firmware update to the car's headunit may be able to fix but but i won't bet on that happening anytime soon.
guess everyone has to trial and error and find ways to establish a successful consistent connection. for me is to forget the car and establish a new connection to the car.
still frustrating as ever and i don't want to have to spend 2 - 3 mins each time before i drive to wait for AA to load.
anyone else having connection issues with other car makes?
rafalucas said:
anyone else having connection issues with other car makes?
Click to expand...
Click to collapse
With my Pioneer or my Headunit app, one of the biggest issues is quality of the USB cable and USB connections.
Testing with different/known high quality cables is worthwhile.
nimdy said:
'Charge only' might be useful, unless AA needs MTP or network connection to operate?
Click to expand...
Click to collapse
"Charge Only" is what I try to aim for. Despite it's name apps like Android Auto can use the USB in this state.
AA does not need or use MTP or network connections via USB. Trying to use USB for other things, like network connection, would only be possible via a USB hub, but it's a crap-shoot whether that would even work.
mikereidis said:
With my Pioneer or my Headunit app, one of the biggest issues is quality of the USB cable and USB connections.
Testing with different/known high quality cables is worthwhile.
Click to expand...
Click to collapse
i've tried various cables but i find the original samsung cable that came with the phone the most "consistent" in establishing a successful connection.
mikereidis said:
"Charge Only" is what I try to aim for. Despite it's name apps like Android Auto can use the USB in this state.
AA does not need or use MTP or network connections via USB. Trying to use USB for other things, like network connection, would only be possible via a USB hub, but it's a crap-shoot whether that would even work.
Click to expand...
Click to collapse
i'll give this a go tonight
PHEW. I thought maybe it was just me. I have just purchased a Skoda Fabia 2016 with Android Auto (I imagine this will be the same underlying system for VW/Skoda/Seat/Audi). I find that sometimes, I plug it in and then it magically works fine. Other times it can't connect to the device and tries to connect to MirrorLink instead....which also fails. I'm using a Samsung Note 3 official UK lollipop build - but rooted. When it fails, I have to go through the process of telling it that I want to connect to the device.
Incidentally when it has connected, it's rock solid every time (well with one random crash & reboot of the car's entertainment system).
It's just annoying. I want to get in my car, plug it in, AA to launch and that's it!
What's also slightly annoying is that there's no button to go right to AA on the dash. I have to go to 'Menu' and find Android Auto in that menu to launch back into it if I go to something else within the car's entertainment system. Grr! Not anything anyone can do on here, but just venting!
jonboyuk said:
PHEW. I thought maybe it was just me. I have just purchased a Skoda Fabia 2016 with Android Auto (I imagine this will be the same underlying system for VW/Skoda/Seat/Audi). I find that sometimes, I plug it in and then it magically works fine. Other times it can't connect to the device and tries to connect to MirrorLink instead....which also fails. I'm using a Samsung Note 3 official UK lollipop build - but rooted. When it fails, I have to go through the process of telling it that I want to connect to the device.
Incidentally when it has connected, it's rock solid every time (well with one random crash & reboot of the car's entertainment system).
It's just annoying. I want to get in my car, plug it in, AA to launch and that's it!
What's also slightly annoying is that there's no button to go right to AA on the dash. I have to go to 'Menu' and find Android Auto in that menu to launch back into it if I go to something else within the car's entertainment system. Grr! Not anything anyone can do on here, but just venting!
Click to expand...
Click to collapse
Galaxy s6 Stock firmware and my octavia android auto 1.4 work very well.
No luck with LG G3
Good day everyone, I just purchased a 2016 VW GTI and I have an LG G3 with Lollipop 5.01 rooted. and I can not get it to work with mirrorlink or android auto. Mirror link default or AA default. I tried different cables, plugged in car on before the car was on. MTP, PPP, charge. The head unit does see it as an LG phone but nothing works.. usb debugging on or off.. Kind of bums me out. Oh I keep getting a make sure the phone is unlocked message I turned screen lock off, and the phone is awake when I try to connect.
mikereidis said:
If you, or anyone having a problem on the car/HU side, has a USB OTG cable and a bit of time to test, you should consider trying my Headunit app; see my sig.
Click to expand...
Click to collapse
Yes! This is the best option for check if the problem is the HU/car or the phone.
From my point of view typically the most issues are related to the phone (ROM, AA app, etc.). For example, with my previous Lollipop 5.0 one month ago... the AA was inestable. With a new 5.1 phone and with the last AA app version (upgraded 1 week ago) I don't have any problem.
Please, try this before post about problems. Sometimes the problems isn't the car or the Head Unit. :angel:
Hi all. Further to my last post, I'm also sure it is a device/ROM issue. It doesn't work all the time, but most of the time the workaround for me is to open the open apps list, swipe them all off to close them, including AA app, then re-open AA. This increases the chances of my phone connecting to the car, but every so often I get a connection error and have to try again a second/third time.
I think I may have asked before, but is there anywhere we can report these bugs to? AA is technically beta (as with most Google products) so I'm sure they would welcome our bug reports.
Connection Memory ?
Hi,
I have the same experience as many others that the connection to AA is very random. I've tried:
Different phones (Nexus 5 and Nexus 6 on stock Android 6.0)
Different USB cables
AA app on and off
Screen locked and unlocked
All without being able to see a pattern. Sometimes it connects automatically in 15 seconds, sometimes automatically in 1 minute and sometimes I need to manually push the connect on the HUD (VW Passat 2106).
The only thing that is consistent is that once you are connected to AA and then disconnect, if you re-connect the phone it works flawless every time ! It seems to be working even if the re-connect happens after a few minute (e.g. not rigth away). So it seems that either the HUD or the phone has some sort of connection memory. Once it expires the connection problem reappears.
Anyone else that can confirm this ? Any ideas on where the problem can be ? I guess this rules out the USB cabel as suggested by many.
// J
I bought an Elgato HD60S to be able to stream through my laptop or desktop from the phone. I connected the Usb C cable from sideport to elgato then HDMI from elgato to pc. Phone is recognized and its screen displayed in elgato's capture software. Now the issue; elgato loses image from the phone every other second or so and there's absolutely no consistency to screen capture. It also displays the gray distortation-like screen on every cutoff like old TV's used to do when the antenna wouldnt work. I looked it up and although there is not a whole lot of info on rog phone 2 regaering this issue, I read that a powered HDMI splitter would solve it, the issue being caused by HDCP. Ordered that, hooked it up, and still the same exact thing. Then, read elsewhere that the Asus Pro Dock is the only working way to stream from the phone. Ordered that, hooked it up, and still it's exactly the same. At this point I am absolutely clueless as to how to workaround this issue. Please help
FYI I am trying to stream PUBG and tried with both my laptop and desktop and multiple different cables, so there's that. Elgato doesnt mention the actual "HDCP" text until I reconnect the phone a couple times to it. Streaming works perfect with my Note 9 in the same setup.
Is it working now
Inorderd to bypass the hdcp block we need hdmi splitter
Is that working
rajuginne said:
Inorderd to bypass the hdcp block we need hdmi splitter
Is that working
Click to expand...
Click to collapse
Nope. Splitter didnt work for me. However, I did find a workaround which is to use "ASUS Pro Dock" in conjuction with Elgato. The culprit here is that you have to power the Dock with its Usb C port to make it work. When connected, it might seem like its still not working but it smooths out after a minute or so. Then when it is working, you can unplug that Usb C and it should remain working fine. In the end, I was still having issues with poor audio quality (crackling/popping and slowed-down speedwise), but got a fix for that as well.
The android 10 beta is here for the device try that and see if it works
@twinklejadoo bro i faced the same issue and solved it by using online hdmi splitter
Sent from my [device_name] using XDA-Developers Legacy app