>> 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
