[Download Google Chrome For Nokia E72
Amancio Mccrae
I reset all of the devices and connected them to the new network and they are connected to the internet & currently are showing the usual picture display but in the Google home App they show as offline when i try to check the settings for each device. Therefore there is no control from the App (my iPhone running the App is connected to the same SSID as the google devices) for any of my devices and I can't get my Chromecast(s) to show, Its only the Google devices (I have Google Mini's, Google Home, and Chromecasts connected all with the same issue)
I tried resetting all the devices and reconnecting on my old NBN modem and everything works perfectly so It seems to be that there is a setting and or issue with the Nokia Fastmile 5G modem that effects the Google devices?
I have never had an issue before when casting, from my iPhone nor previous home internet. I have 2 chromecast devices 1st gen & 3Rd both were working before this new router & internet.
inhave set up both 2.4ghz & 5GHz on separate SSID etc, tried all the WAP/ ghz, options plus re-starting all devices every time I change settings.
this issue was similar to another user but the fix for him has not solved mine. I was also hoping to get up my home mini.
In the past several days. I have been experiencing difficulties marking into my Bitbucket record, and I have seen the regular objective for the issue with the going with message which appears, apparently, to be shared objective for issue:
In the beyond couple of days. I have been encountering challenges signing into my Bitbucket record, and I have seen the typical goal for the issue with the accompanying message which seems, by all accounts, to be common goal for issue:
Did a factory reset on the Nokia router.. Then changed the 2.4 & 5ghz WiFi to different names.. Configured all devices onto the same (2.4ghz) network. Then factory reset the chromecast.. Seems to work now
Did a manufacturing plant reset on the Nokia switch. Then, at that point, changed the 2.4 and 5ghz WiFi to various names.. Designed all gadgets onto the equivalent (2.4ghz) network. Then, at that point, industrial facility reset the chromecast.. Appears to work now
Factory reset on the Optus Nokia Fastmile modem proved not to be a permanent fix. My printer needed a reboot for a different reason later on, and since that reboot it again now shows "Offline" on the PC's print dialogue box. Also, the various streaming apps (Netflix, Prime, Disney, etc) on two different iOS devices may or may not show that there's a Chromecast available for streaming.
+1 for this issue; got in touch with Google, Optus and Nokia and was sent in circles. Optus noted the same compatibility issue that you mentioned and said that Nokia are "probably working on it"... so same result. I guess until that happens (if ever, or Optus changes their 5G modems) we're out of luck.
i am unable to cast anything to my android tv or to my projector (using google chromecast stick).... the best part is that all the things work fine with an older 4g modem i had previously.... its confirmed for a fact that the problem is with Nokia 5G modem... they are not compatible with chromecast... simple...
what a frustrating issue, i will also be contacting optus and i hope they have heard this query enough to take serious in finding a solution for us. it would be a shame to let 5G go because of a simple unexpected compatibility issue
... and then a few days later I changed back to default because all other devices were having intermittent connections issues. Now the Chromecast seems to mostly work but my wife can't cast from her phone but I can.... and the Fetch supplied by Optus can't connect to the internet even though everything else can. Technology.... sigh.
For me switching the 2.4GHz network to use WPA2 only fixed the casting issue temporarily, then it stopped working again. Shrug. Even if switching to WPA2 only worked it's still not ideal as devices that do support WPA3 wouldn't be able to use the higher level of security.
Had same issue until I set up my Ubiquiti access point and attaching iphone and chromecasts to this rather than directly to optus router worked fine. Setting up seperate wifi point for these additional devices seems to be a workaround.
I have not found a solution with the Google Chromecast devices. The TV I got was the cheaper end of smart TV so unless that company pushes all the streaming Apps out on it you are limited to what it has installed.
I ended up getting a Foxtel Now box which allows me to cast to & I have this plugged into the wifi box via Cable.
I ended up getting it for $30 from Kogan & it was the most inexpensive solution I could find.
Android does unusual things with DNS, I have found blocking access to the Internet on port 53 from any device but my pi-hole forces my android stuff to use the pi-hole. Many topics on this, look for port 53 and you'll find them. Also on the pi-hole reddit.
@Videopac is right.
Here is one solution.
When you have set everything like it should you will notice that ads in Firefox are being blocked.
Ads in Chrome are not blocked.
It is an implementation that Android phone makers add to the setup of the phone. Guess that Google insists on doing so.
I'm not sure why you say this....I see no ads in Google chrome, on either desktop nor mobile.
As far as I am aware, Google do not hardcode DNS servers into their software, but they perhaps do hardcode DNS servers into hardware, such as the Chromecast and Google Home devices
The basic summary of this thread is in order to get Pi-Hole functioning on an android device, I had to disable IPV6...at least for my ISP anyway.
confirmed by a fellow Sky (UK ISP provider) here in another thread
If having this issue because selecting a DNS from Android device while on WiFi causes your ISP ip6 DNS to be used, install DNS CHANGER which uses local VPN (so you can't use it with other VPNs from your Android) but you can turn off IP6 in the app and mobile browsing will have ads blocked.
Holy thread ressurection batman!
This is one workaround yes. But kind of defeats the point of a network wide ad blocker.
Easiest and most efficient solution is to disable IPV6 on the router as discussed way back.
My point was when that isn't an option, that people aren't left out of options. Googling about Android issues with this still comes here, and it was no help for me a month or so back, because I cannot configure my IPS provided modem + router, and then I found
this workaround which works until I can get a proper router. Answer provided for those in my same situation who land here like I did, Robin.
I believe this topic is still alive because there's not a clear answer. For example, I can't disable IPv6 DNS from my router. Also, I have a solution and I have figured out what Chrome on Android is doing.
First, what Android Chrome is doing. When Android gets the DNS servers when it connects to Wi-Fi it gets two addresses. The first, is pi-hole (for example 192.168.0.200) and the second DNS is typically a backup in case pi-hole is down (something external like 1.1.1.1). Chrome does a DNS lookup for an ad domain and pi-hole blocks it properly. But, Chrome then tries the secondary DNS because the first one didn't return a result. So Chrome then gets the ip of the ad domain from 1.1.1.1 which then causes the ad to show.
I've been able to confirm this action by changing my second DNS server to the Wi-Fi port on my pi-hole (IP 192.168.0.201 in my case). Now, when Android tries both DNS 1 & 2 for an ad domain, they both fail because both are pointing to my pi-hole.
While this does create a situation where if the pi-hole fails no DNS works, that has yet to happen. But, it does pinpoint the source of the problem. Android Chrome is not doing DNS correctly, it's trying DNS 2 when we're on purpose causing the DNS 1 lookup to fail.
Good luck getting Google to "fix" this, as they probably see it as a "feature". But the short answer is to point both DNS 1 and DNS 2 to your pi-hole (Ethernet port and Wi-Fi). If you don't have both Ethernet and Wi-Fi on your pi-hole, just set DNS 2 to 127.0.0.1 which is your localhost.
I have just installed 2 days ago Pi-Hole today for blocking some distraccions for sudiying (YouTube) and I have ad blocking working on Android with Samsung internet explorer, Google Chrome and all apps. I'll explain what I did:
Extra: I had everything working at this point but I highly recommend to add more blocking lists, I did it from this (excellent work): [UPDATE] The best blocking lists for the Pi-Hole + Alternative DNS servers 2019
EDIT: More details. I set Google DNS on Pi-Hole. Raspberry model: Pi 3B. Android device: Samsung Galaxy S9+, Android 9.0. I think that Android versin and device's Brand are not the problem but I add this details for more info.
TL:DR: This might work for some. Disable advanced DNS on your phone if you have it. Settings/Network & internet/Advanced/Private DNS/Off. AND/OR Turn off any DNS adblocker on your phone like dns66 or DoH client like cloudflared as they will also bypass pihole.
Good morning all, I had the same problem and hopefully this is helpful for some but it might not be for all. I have pfsense blocking all dns requests outbound and IPv6 off yet I was still getting ads on my phone (pixel 3 xl). I have cloudflared (DoH, I highly recommend setting this up if you aren't doing this already) running on my pihole server and that tunnels dns requests out via 443. I get no ads on anything at home except my phone. I was pulling my hair out trying to figure it out.
If you have advanced DNS configured, your phone will tunnel dns requests out using the servers that are configured in advanced DNS and bypass pihole. Also, if you run any other DNS redirect service on your phone like dns66 or cloudflared for DoH on your phone, that will bypass pihole. Turn those off.
Had a similar issue in 2020, set up dhcp on pihole and none of my android phones saw it or used it, all showed connected, no internet. Things were fixed when i gave them static IP addresses in phone. hope this helps.
795a8134c1