Android keeps saying my Wi-Fi is “low quality” even with good signal    

I’ve been fighting this for months and I honestly don’t understand what Android means by “low quality Wi-Fi”.

My phone will randomly decide my home Wi-Fi is bad and stop using it properly, even though the signal bars look fine. Sometimes WhatsApp barely loads, sometimes pages hang, and then the phone acts like mobile data is the better option — which is annoying because 4G is terrible where I live.

I’m on a 200 Mbps fiber connection. Wi-Fi is 2.4 GHz only because 5 GHz range is awful in this house and drops too much. I live in a rural area, no nearby apartments, no obvious neighbor networks, no microwave running, no big electronics nearby. So I really don’t think it’s classic “crowded Wi-Fi” interference.

Router/AP setup is just basic mesh gear from TP-Link. I already rebooted and reset it once, but nothing changed.

What does “low quality Wi-Fi” actually mean, and is there a way to force Android to ignore it and stay on Wi-Fi anyway?

“Low quality” doesn’t just mean weak bars. Android can look at stuff like signal strength, link speed, packet retries, failed transmissions, and whether it can actually reach the gateway/internet. So the phone may show decent signal but still decide the connection sucks because packets are being retried or dropped. Basically: full bars can still be bad Wi-Fi.

@Young_Lefessy That’s the part that confused me. I thought if the bars were good, the Wi-Fi should be fine. I only need it for low-demand stuff too — WhatsApp, text, browsing. Not gaming or streaming 4K.

Before buying new routers, measure what’s happening. Run NetSpot or another Wi-Fi analyzer and walk around the house. Look at the actual signal level in dBm, not just the icon. Also watch whether the signal is stable or jumping up and down a lot. Check it right next to the AP, then 2–3 meters away, then in the spots where Android calls it low quality. If the signal drops fast or keeps oscillating, that explains why the phone doesn’t trust the connection. NetSpot can also show the 2.4 GHz channel situation, so you can confirm whether there really is no interference instead of guessing.

Rural doesn’t mean interference is impossible. It may not be neighbor Wi-Fi, sure. But 2.4 GHz can get messed with by random stuff: bad power supplies, wireless cameras, Bluetooth-heavy devices, old appliances, thick walls, metal, cinderblock, mesh node placement, etc. Also, mesh nodes with weak backhaul can make the client connection look okay while the actual network path is garbage.

Also make sure it’s not the fiber/internet side. Plug a computer into the router with Ethernet and run a few tests when the phone says Wi-Fi is low quality. If wired internet is also dropping packets or timing out, Android might be blaming Wi-Fi when the actual issue is upstream. If wired is solid and Wi-Fi is bad, then focus on AP placement, mesh backhaul, channel, and maybe replacing the AP.

Ok, this makes a lot more sense now.