Yeah, I did, though I haven't gotten around to doing most of those things. It's a little bit frustrating as the advice feels a bit like cargo-culting random things that may have helped in other situations.
Main Wifi router is connected to a non-router modem that I supplied myself. No devices are dropping from the network, just the overall internal network gets slower and slower. I'm not sure what a paused device is, so my guess is that I have no paused devices.
The issue isn't potential interference, otherwise I would not be having the same issue on my desktop that's hardwired to the main Wifi router.
The thing about the network name and password having special characters makes very little sense. If that is an issue, that's something Google should fix. Either way, there are no special characters in mine.
If IPV6 is broken, again, this is something Google should fix.
This is not DNS related. DNS related issues tend to manifest themselves as running into set timeouts - e.g., I had a docker container that kept taking ~5 seconds to do something that should normally take 10ms, and that was due to the default 5 second DNS timeout in the linux distro I was using as the base container. Sustained file transfers/streams generally don't do a lot of DNS lookups as they go.
Nothing has changed from a hardware perspective over the past couple of years, but this problem only started six or so months ago. Most of these suggestions sound like they are trying to fix a misconfiguration, which generally would be something constantly present, not cropping up over time.
At any rate, I've tried the couple that might be applicable, the IPV6 and DNS changes. I'd like to avoid the factory reset route for now, but will try that if this doesn't help.
