Good evening all,
Has anybody in the UK had success in connecting their Chromecast to A SkyHub? I have tried several times, but I cannot connect it, I have had to use my old trusted Belkin to do this...
Thanks
Matt
Hey Matt, got one of these myself a few days ago. Managed to get it connected and set up via my Sky Hub (newish white one), but then couldn't get anything to cast properly and it kept freezing up and becoming unresponsive. Have sent it back as faulty and got a replacement on the way, so will see if it was just the unit.
What problems did you have and did you ever manage to resolve them?
Chris.
All working fine here with 2 chromecasts, one UK and the other US. Black Sky hub, whcih is the newest router
You might to ask this person
http://forum.xda-developers.com/showpost.php?p=47517951&postcount=8
At least they had it working at some point...
Got mine working the other day but had problems.
I couldn't activate it via a Win7 machine, kept getting an error saying it was unable to find the chromecast online. The only way I could set it up was to use an app on my phone. Now that it's setup everything seems to be working ok.
White Sky hub approx 9 months old.
Greetings,
I've recently switched over from the Samsung galaxy s3 to the m8. I have my phone rooted, but currently on the stock rom. I have Google wallet installed on my phone, and tried to us the tap and pay function at McDonalds. I was unable to get the NFC function to work. I know the store terminal works because I used my stock nexus 7 (not rooted) a few months ago to get some coffee there.
I had the same issue on my s3, but I was running cyanogenmod on the phone, and I thought that was the problem. Now I'm wondering if it's having root access. Anyone else having problems with tap to pay on their rooted phone?
Maybe the store terminal broke since... A few months cab do that try a different store
Sent from my 831C using XDA Free mobile app
I'm having the same issue. For me, the problem started when I switched from a Sprint-specific ROM to Viper ROM (intl base). After 2 minutes of bashing my phone against the terminal at McDonald's, it did finally work. But it is not working instantly like it used to, and it acts like nothing is happening. I know it's not McDonald's terminal because it happens at another McDonald's and Walgreens where previously it was working fine. Tapping my phone to another NFC phone works so NFC itself is working.
I don't really feel like going back to a different ROM over this, but it is annoying.
Only place I have has issues is one checkout lane at meijer. Felt like pretty stupid last night since I left my wallet at home. Cancelled my order, went to a different Lane and it worked fine. So for me at least it's not an issue with the phone
Just wondering if anyone else has experienced this. I still cannot get tap and pay to work. The light on the NFC reader at walgreens will blink once when I tap it, but there is zero activity on the phone even though google wallet says "tap and pay ready". Doesn't work at McDonalds either. Friend can use his Note 3 just fine with google wallet in those locations so I know it's not the NFC reader.
I have tried RUU back to the latest stock ROM, no dice. I re-locked my bootloader and RUU'd back to the oldest available HK ROM and did all the OTAs, still same exact issue. I have not been restoring from backup either so my phone is basically 100% stock now non-rooted. The only difference is it's S-OFF, but I've been S-OFF since June and my tap and pay was working until early September so I don't think that's it. I can use NFC to share things with other phones so I know my NFC is fine.
I'm completely stumped.
I think the nfc antennas on this phone might be too weak, I have to get my phone JUST right to read nfc tags...
Sent from my HTC One_M8 using XDA Free mobile app
I don't think that's the issue I'm having. I bought the phoen right when it came out, and I used NFC just fine at McDonalds and Walgreens without having to fiddle with it. It just worked. Now it doesn't work at all. I don't know what happened, the last time I was able to get it working was early September. Not sure if there was a wallet update or something that broke it. NFC communication to other phones still works fine though.
A few stores in my area have been working fine until recently. I was starting to think they were disabling the NFC on purpose. As it turns out, quite a few retailers really are purposely disabling the NFC portion of their credit cards terminals. Found an article about it yesterday.
om4 said:
A few stores in my area have been working fine until recently. I was starting to think they were disabling the NFC on purpose. As it turns out, quite a few retailers really are purposely disabling the NFC portion of their credit cards terminals. Found an article about it yesterday.
Click to expand...
Click to collapse
Yep, Best Buy and CVS are the big ones who have disabled it. However, Walgreens and McDonalds have not. They still accept NFC payments via Google Wallet, and it still works on my friend's Note 3 as of yesterday.
Just wanted to say I've had the same problem. It seems to work when it wants to. NFC itself works fine. I feel like it stopped working after the WiFi calling update... If someone's able to go to the previous update and test it would be awesome.
Figures if it affects Apple its all over the news.
http://www.theverge.com/2014/10/25/7069863/retailers-are-disabling-nfc-readers-to-shut-out-apple-pay
My wallet hasn't worked for me the past few times I've tried (at Walgreens and my work vending machine). I'm guessing it has something to do with my ROM (Viper) or a xposed mod I have running (though I don't have much and nothing related to Wallet directly).
After the 4.4.4 update and also removing all my cards from Wallet and re-adding them, tap-to-pay is working for me now.
kwolf said:
After the 4.4.4 update and also removing all my cards from Wallet and re-adding them, tap-to-pay is working for me now.
Click to expand...
Click to collapse
I am on the 4.4.4 HK firmware but not on the 4.4.4 rom (still on Viper which hasn't updated yet). I removed my cards, wiped app data, uninstalled/reinstalled wallet, and then put my cards back in and still when I put my phone up to the reader wallet doesn't open. The error I get on one machine is "Unable to read card" and the reader just beeps on a different machine. I do have SuperCID on my phone in order to flash HK ROMs/Firmware. Don't think that should matter since I've had that on for months well before Wallet quit working.
I'll wait until Viper updates to 4.4.4 or if they take more than a few days I might try a different stock-ish rom.
henderjr said:
I am on the 4.4.4 HK firmware but not on the 4.4.4 rom (still on Viper which hasn't updated yet). I removed my cards, wiped app data, uninstalled/reinstalled wallet, and then put my cards back in and still when I put my phone up to the reader wallet doesn't open. The error I get on one machine is "Unable to read card" and the reader just beeps on a different machine. I do have SuperCID on my phone in order to flash HK ROMs/Firmware. Don't think that should matter since I've had that on for months well before Wallet quit working.
I'll wait until Viper updates to 4.4.4 or if they take more than a few days I might try a different stock-ish rom.
Click to expand...
Click to collapse
Hmm, when I had the problem the card reader barely responded at all (a light blinked and that was it).
If you open the wallet app manually, does it do anything when you tap? Or is the phone acting like nothing is happening at all?
kwolf said:
Hmm, when I had the problem the card reader barely responded at all (a light blinked and that was it).
If you open the wallet app manually, does it do anything when you tap? Or is the phone acting like nothing is happening at all?
Click to expand...
Click to collapse
Wallet doesn't react at all if I have it open or not when "tapping" my phone. I think the phone beeps too but can't remember now. I know my nfc works fine as I use a nfc tag every morning when I get to work to put it on silent.
My m8 does the same thing... I figured it was running Viper as well, but I just flashed the newest firmware and the stock rom... Same story. I hold my phone up to the NFC terminal, and the lights stop blinking on the terminal, but nothing happens on my phone. When I use my S4, the terminal beeps, my phone vibrates and it just works. I just tried deleting all my cards and trying again... No dice. I just went through a chat with HTC, and they're escalating the issue, who knows, maybe it's bad hardware. (I've never had NFC working)
Update: htc called to confirm my information and to say the turnaround time is 7-10 days. They mentioned that it's rarely a software problem if you're not getting an error. I'm not. I'm assuming that once they research some more, they'll just end up replacing my phone. We'll see.
Sent from my 831C using Tapatalk
After upgrading Viper to 4.4.4, removing all cards, removing all old devices from here (https://wallet.google.com/manage/#devices:), uninstalling/installing wallet, and adding cards back in and it now works. I don't know which one of those fixed it as I did them all before trying.
Thanks henderjr! I tried everything you had posted there, but still didn't have any luck. (holy crap, I had a ton of devices listed... One for each ROM installed in the past few years.) Hope your information helps someone else get their device working!
As title says I can't get the navigation cards to appear. They used to work initially on the original LG G Watch but since upgrading to the G Watch R I can't seem to get it to work. I say "OK Google navigate to ..." And it starts the app on my phone just fine but nothing pops up on my wrist. Am I missing something?
Same problem for me. Android 5.0.2. Latest Maps, latest Android Wear.
Same was here..
After i bought my watch it was on Android 4.4, after setup it with the phone it was updated automaticly to 5.0.1 and my navigation doesn't work. But today i've reset my watch and setup up again, and navagitaion works just fine. Maybe after system upgrade of the watch is good to do factory reset to effect of the new android.
Thanks for the reply lostindark, was hoping that would work for me but unfortunately it didn't. Just tried it and it still does the same thing. Just to confirm, you just tapped the reset from the settings menu on the watch right? I did that and it didn't work, then I also cleared the data on the wear app, re-paired the watch and still didn't have any effect Does the same thing mentioned in the OP, works fine on the phone and starts the maps app there but no cards on the watch.
Sorry to heat this, i reset my watch only through settings and notting more but it was worked for me. After the reset and pairing again android wear app put other apps automatically on my watch after that everything works just fine.
Thanks anyways for the suggestion mate, I ended up getting a Nexus 6 today and it is working just fine paired with this phone. Must have been something with my OPO but I have no idea what since it was 100% stock other than root.
Sent from my Nexus 6 using Tapatalk
Hello everyone,
first I'm sorry for my english and hope you understand everything.
I'm using Android Auto since two years with the same smartphone a galaxy s8+ (Android 9) in my opel corsa e on an Intellilink R4.0 and most of the time it worked without any problems.
But since one week it didn't starts on the Intellilink.
The last systemupdate from my galaxy was something about four weeks ago and in the mean time everything worked fine.
Each time i connect my Smartphone as usual with the car the Android Auto App shuts down and in the smartphone notification it says that Android Auto is connectet but the Intellilink didn't starts Android Auto. It only offers me to change to my Galaxy s8+ but without any result. If i try to start the Android Auto App (while the smartphone is connected to the car and i tryed it once to change to the galaxy) the "Android Auto" app shuts down immediately.
I deleted the bluetooth-connection in my smartphone and in the car and reconnected both.
I deleted the cache & AppData from "AndroidAuto", "Google Play Service" and from the "Google App".
i deleted and reinstalled the Apps.
I also tryed to use two older versions from those Apps because i thought i updated them recently before it didn't worked anymore but without any success.
I tryed three different USB-cabels...
The data-transfer to my pc works so the USB-Port from the galaxy is okay. no one in my circle of friends has a Android Auto compatible car so i can't test it there.
Somewhere i could read that it could help to enable and disable the usb-debuggin in the devolopmentmode in the galaxy but it didn't helped.
Then i disconnected the Car Battery to make a Hardrest in the Intellilink and again no success.
Confusing was that last thursday on the way home, past 20min of connection and driving it suddenly started in my car and i could use everything as usually (Voice, Maps, Spotify).
But when i arrived home and disconnected the smartphone to try it once more it didn't started.
Till Today i didn't get it to work and i dont know what problem it could be or what else i can do.
The galaxy isn't rooted i don't want to root it.
Once i had a similar problem and some App updates fixed the problem so i'll wait for an update from "Android Auto", "Google-Play-Service" and the "Google App" to try it this way before resetting the galaxy to factory settings.
But I hope that someone can help me and has another idea what i can try to do.
with best regards
xman1985
I have the same issue with my s9 on my astra. I might have a solution. Every time u connect your phone to your car and the after the notification in your phone comes saying android auto is connected go to photo gallery, search for any random video if u have in your app. Play it n hit back/return key on your phone. Yes its a bit of a struggle but mine one works every time i do this . Looks like a bug
samuhang said:
I have the same issue with my s9 on my astra. I might have a solution. Every time u connect your phone to your car and the after the notification in your phone comes saying android auto is connected go to photo gallery, search for any random video if u have in your app. Play it n hit back/return key on your phone. Yes its a bit of a struggle but mine one works every time i do this . Looks like a bug
Click to expand...
Click to collapse
Thanks,
I'm not sure if its just a coincidence but i tried it and it realy works that way.
xman1985 said:
Thanks,
I'm not sure if its just a coincidence but i tried it and it realy works that way.
Click to expand...
Click to collapse
Hi ive found out today that downgrading your aa to
4.6.593334-release (arm64-v8a works without going to gallary app n playing a video. But first just clear data of your aa before unintalling it than intall the above mentioned ver from apkmirror . Com. Have a nice day
I have an Alpine iLX-W650 and a OnePlus 7 Pro. Android Auto has been working perfectly for well over 4 years now, even through OS upgrades (currently on Android 12).
Suddenly, about a week ago I got the "Device is not supported." message. A reboot of the phone while in the car fixed it.
Then it happened again the next day, nothing I do resolves it including a new or different cable. There was an Android update this morning and I also saw a new version of Android Auto. I did both of these hoping one would fix the issue. Nothing. Multiple reboots later, including telling Android Auto to forget me unit, still nothing.
I had my wife plug in her phone and the head unit works perfectly with Android Auto, so something with my phone changed or a setting is corrupted. I'm not sure how to get things working again.
As mentioned, I tried:
another cable (several now)
"Forgetting all cars" in the settings
Forgetting connected cars in the Head Unit.
Factory resetting the Head Unit.
Double-checking the Head Unit is the latest firmware (it is).
Deleting the AA app and clearing data and cache for it and then updating to the latest.
Deleting the AA app and clearing data and cache for it and then trying to connect to let it pull down AA.
As noted above, my wife's phone works no problem with my head unit and since thing my daughter tried her phone which works too. Clearly, something on my phone got corrupted or something to cause it to not work anymore.
Rule #1 - if a OS is fast, stable and fulfilling its mission let it be! Upgrades and updates can and do break devices.
Once you sort that mess out disable auto updates.
For anyone that might stumble on this, I considered that maybe my phone's data port was at fault and causing issues. Otherwise, my OnePlus 7 Pro works great and still charges. Not really ready to let it go.
Since I've always wanted AA to be wireless, I ordered the AAwireless device and it works flawlessly. In fact, it is more responsive than when my phone was cabled. Wish I had done this years ago.
stevemajor said:
For anyone that might stumble on this, I considered that maybe my phone's data port was at fault and causing issues. Otherwise, my OnePlus 7 Pro works great and still charges. Not really ready to let it go.
Since I've always wanted AA to be wireless, I ordered the AAwireless device and it works flawlessly. In fact, it is more responsive than when my phone was cabled. Wish I had done this years ago.
Click to expand...
Click to collapse
A port pcb failure can cause data and phone service loss at least on Samsung's.
If it happens after a firmware upgrades/update it's not a hardware failure...