Google devices (Android 15, ChromeOS) losing WiFi connectivity

Why do you ask, ExtraChrispy; did you suffer the same intermittent denial of service, and searching the forums, found this thread, in order to share your success in solving this intermittent connectivity issue that is neither caused nor resolved by changing my configuration?

I'm just a guy that owns an IT Managed Services shop that focuses on providing contract outsourced IT infrastructure, support, and compliance services.  I'm not actually having issues myself but I've used Google devices on Cox Internet and not experienced issues to the extent that you've reported.

I can report however that Google devices by way of the features I've suggested tinkering with amongst others, have a curious way of dickering with tried and true principles of Internet connectivity in the name of privacy but in my opinion cause problems.  To this day, it still upsets me that Google devices prioritize external DNS over anything you may have configured internal making it very difficult for things like Android phones to see services you may have internally hosted and no amount of custom configuring your network infrastructure will correct said behavior.

But on that topic, I will also say that the Cox Pananorama wifi gateways have been known to tinker with the connection in similar ways.  I believe WAN isolation is enabled by default which will make things like Nest devices not see each other.  On that note, you may want to explore the security features in your Cox Wifi app further and see if anything could be going on there.

>> curious way of dickering with tried and true principles of Internet connectivity in the name of privacy but in my opinion cause problems.  To this day, it still upsets me that Google devices prioritize external DNS over anything you may have configured internal making it very difficult for things like Android phones to see services

=Yes, indeed I definitely agree with this. My frustration can definitely stem from daily struggling against Google CHrome and against Google Android and against Google Apps as they "tryt o keep you safe on the Internet" and very zealously implement their vision of User Privacy, which has begun to cause me financial problems, even. 

[There have also been instances of ISPs modifying DNS requests, for example, and responses "in-transit", and interposing advertisements and other non-compliant responses that would confuse users and confuse our hardware/software network equipment, and for the same reasons, to advance business interests of ISPs]

I foolishly attempt to do a lot of "household business" from home on the Cox network with my Google Devices, and it's difficult for the reasons you outline here. Google always finds new ways to break connecgtivity, break web pages and web apps, and break mobile apps, but sometimes these are "information security necessities" to stay ahead of malicious actors, but often times also to stay ahead of their competition and advnce Google's business interests. So, shrug, what can we do?

>> IPV4 and IPv6 isn't the issue.

Darkatt, please tell us in this thread, before posting again, whether you are affiliated with any provider of network services, a provider of mobile wireless services, a provider of IPv6 transit or routing services, a provider of Home Internet services similar to those provided by Cox Communications? I'm curious why you keep responding to my threads and shooting down my diagnoses and ignoring the OP?

>> IPV4 and IPv6 isn't the issue.

We haven't ruled out dual-stack IPv6 anomalies. The main issue may be Google's own methods of detecting "Internet Access Available" or something, and Google's nearest datacenter to me is hundreds of miles west of here, in another state. Dual-stacking IPv6 is a huge problem for consumers and service providers alike; here's an outdated but informative link: 

The main trouble with troubleshooting dual-stack is that IPv6 cannot be disabled anywhere in the network. I asked Cox who can't disable it over there. Not on the router. Not on any of my devices. IPv6 is forced-on and co-existing with IPv4, including DNS servers: who knows how they flake out. I've often personally traced flaky network errors to IPv6 being broken, firewalled, or IPv4 suddenly failing when IPv6 was also in-use. All we can do for now is ensuring there are no IPv6-only blocks or firewall rules, or routing that could be causing anomalies. Most people don't realize that there are now two paths to the Internet and modern devices are trying to juggle both at once, while network administrators must configure them separately and uniquely.

There is no WiFi reception issue. Please refer to the original post. The WiFi is 5/5 bars, fine 96% of the time and 100% of the time, 5/5 bars always, on the Motorola Android 11 phone. There's no issue with the WiFi connection itself. The LAN is fine and healthy.

>> your pano router

My apartment is less than 700 sqft. Reception issues are nonexistent here, and I've been 52 years a member of an amateur radio/DXing family, so I'm familiar with issues of RFI. There may be congestion and that's why I've disabled 2.4GHz, because 5GHz is quite clear on most/all channels. All of your helpful suggestions are already implemented and not mentioned in the OP, because we've ruled out reception issues already. Thanks! I stopped studying for my FCC license, because I'm quite uninterested in radio comms, except as a consumer and troubleshooting them with qualified professionals at Cox Communications.

It's Internet Access issues between each of two Google devices and wherever Google's trying to reach.

I worked for Cox for 16 years, the bulk of it in Data Tier 2. During that time, myself and Leland, wrote ALL the troubleshooting documentation for the Cox Home networking, including multiple routers and operating systems. While I haven't used the Cox App for Pano modems in several years, there USED to be a way to disable IPv6. 

Prior to that I worked as an L2 for Dell, and prior to that Head of field engineering for a data processor, responsible for over 5000 pieces of equipment in the field. I hold certifications in Novell, Micom, Bay Networks, Newbridge Mainstreet, Cisco, Microsoft MCSE, Okidata, Symplex, Gandalf and several others. During that time, I was responsible for network design for both LAN and WAN networks. I also was a beta tester for several companies, (Somewhere I think I still have an old Linksys WAP 11).

The reason I do not believe it's an issue with IPv6, is you would have the same problems across all of your Google OS style devices, as they utilize the same code for networking. If one exhibited the issue, they all should. Since that isn't the case based on the OP, we have to focus on the devices that have the issue, and determine what is different in their usage vs the other devices. I was looking at the WiFi, since it's possible the devices were being used in differing areas of your apartment, and that can lead to variances in WiFi reception as well as differences in emi or rf interference. 

BTW, WiFi in apartments are well known to be affected by neighboring apartments due to thin walls and large numbers of people with wireless devices in smaller areas causing congestion. This could lead to devices in certain areas of your apartment to getting a burst of noise, causing data transfer problems, but remaining connected to your WiFi, and receiving an error that you mentioned, connected to SSID, no internet, and then disconnecting from WiFi. IF this was an IPv6 Dual-Stack issue, it wouldn't affect WiFi connectivity from device to router which is separate from internet connectivity. All of which again, leads me to emi/rf or signal issue.

>> I worked

>>Prior to that I worked

That is not what I asked about past résumé or credentials. They matter not a bit in this forum today on March 10, 2025. Documentation I read on Cox is not for Chromebook, or Pixel 8 Pro; in fact it's inaccurate when applied to these devices because the Settings and Configuration screens change all the time.Cox documentation is basic consumer-level stuff that I've already run through and tried and exhausted all options before turning to unemployed experts on forums. I am sorry that I neglected to exhaustively list all the troubleshooting I've tried because that's a lot to wade through, but surely everyone expects that I am ignorant of basic procedures and that I've not bothered to contact Cox Complete Care 5 times already about this.

My 4 devices do not use the "same code for networking". One device is HP; another is Android 11 (written by Google AOSP but modified who-knows by Motorola and my carrier(s)) and there's the Google smartphone and an Acer running ChromeOS. The latter two are acting the same way--so yes, if it's the same codepath then the same errors manifest. We still have no evidence that IPv6 (or dual-stack IPv4) can be ruled out. It doesn't matter what code they're using if the error is beyond our control, outside Cox's backbone, in Google's Datacenter, or somewhere in a router hop hundreds of miles/milliseconds away? It's an intermittent error!!! It usually self-resolves within a few minutes. It would probably resolve even if I didn't intervene or tinker immediately.

It may be informative to know that Google's Pixel/Android/ChromeOS platform team is in a shambles after a staffing shakeup and merging of departments last year. I was Super-Reluctant to leave behind Android 14 which was stable, but I cannot be sure if Android 14 was more reliable than 15 is now.

Indeed we have not entirely ruled out RFI or malice on the local airwaves. Indeed a nearby device/human could be hacking/clogging the airwaves and causing denial-of-service for us. Cox's Panoramic WiFi 6 router may be defending itself against malware. We don't--and can't--know this. But we're hypothesizing ignoring/against facts presented as evidence.

But I have located, on Google Support forums, that at least 200 other people are having issues now with Android 15. I sincerely suspect this is not a Cox problem, not a WiFi or radio issue, but a Google problem, because I keep repeating myself that my Motorola device is always fine and there's no interference or RFI or denials-of-service on this Android 11 device but we can keep imagining scenarios that don't exist and that I've not posted about? If this thread is another waste of pixels fand bytes and keystrokes? f

or us?

There's a wide, wide gap between 11 and 15, and surely the networking code is perhaps just a little different in the Motorola hardware, and this definitely comports with your prediction that both of the freshly-updated Google devices are the only ones exhibiting this issue.

I also received certifications (and I can upload those images) but the point of troubleshooting is first to determine a probable cause and you do that by asking questions and helping the user diagnose with the tools at my disposal, not by shooting down my perfectly viable hypotheses and ignoring the evidence I already presented; thank you

Google's staffing and merger "shakeups" in the news:

https://www.businessinsider.com/google-big-shakeup-gives-more-power-to-deepmind-pixel-leaders-2024-4

https://www.businessinsider.com/google-voluntary-exit-pixel-android-group-2025-1

Mod here. I know having issues and the multitude of troubleshooting options you can go through without success can be frustrating, but please be kind to each other. I dislike having to remove posts that may otherwise help someone else out. Thanks!