In This Article
When the Wi-Fi or Bluetooth toggle on an Android phone refuses to turn on (it greys out, flickers, or shows a spinner that never resolves) the cause is almost always a specific cached service rather than hardware failure. The 2026 fixes are the same family of fixes that worked in 2022, with one new wrinkle: Android 14 and later occasionally bind the toggle to a permission revocation that the user did unknowingly.
Here is the working diagnostic flow, in order from quickest to most invasive, with a clear stop point if you reach hardware-level symptoms.
TL;DR
The pick: First move: Settings, Apps, See all apps, scroll to System processes, Wi-Fi Service, Storage, Clear Cache. Do the same for Bluetooth.
Runner-up: Runner-up: Settings, System, Reset options, Reset network settings.
Skip if: If neither works after a reboot, the radio module may be failing; do not keep flashing software, take it to service.
For a deeper reference, see Google’s official Android Help Center.
Why the toggle gets stuck
The Wi-Fi and Bluetooth toggles call into system services that occasionally hang on a corrupted state file. The state file is part of the system app, not your settings, so clearing the cache for the relevant system service unblocks the toggle without losing your saved networks or pairings.
Less commonly, the toggle is bound to a location permission. Bluetooth scanning requires Nearby Devices permission to be enabled; if you revoked it, certain pairing flows appear broken.
The two-minute fix
Open Settings, Apps, See all apps. Tap the kebab menu and pick “Show system”. Scroll to the Wi-Fi Service entry (or Bluetooth Service), open Storage, and tap Clear Cache. Reboot. The toggle usually works again on the next try.
If that fails, repeat with the Network Stack service. These are system apps; clearing their cache is safe and does not affect your data.
Reset network settings
If clearing the cache does not help, go to Settings, System, Reset options, Reset Wi-Fi, mobile, and Bluetooth. This wipes your saved networks and pairings but restores the toggles to a clean state.
After the reset, reconnect to your home Wi-Fi and re-pair your important Bluetooth devices. This is the highest-yield fix when the cache clear fails.
Hardware-level signs to stop on
If the toggle works but Wi-Fi cannot see any networks, even hotspots from a nearby phone, the radio module may be failing. The same applies if Bluetooth pairs but cannot maintain a connection beyond a few seconds, on multiple known-good devices.
Do not keep flashing system images or factory-resetting; hardware failures on the radio module do not respond to software fixes. Take the phone in for service while it is still under warranty if possible.
The setup, step by step
- 1
Reboot once
A clean reboot fixes about half of stuck toggles.
- 2
Clear cache on Wi-Fi and Bluetooth services
Settings, Apps, Show system, Wi-Fi Service, Storage, Clear Cache.
- 3
Check Nearby Devices permission
Settings, Apps, Bluetooth, Permissions, Nearby Devices, Allow.
- 4
Reset network settings
Settings, System, Reset options, Reset Wi-Fi mobile and Bluetooth.
- 5
Take to service if needed
If the radio still does not see networks after the reset, treat it as a hardware fault.
FAQ
Is this safe?
Yes. Clearing the cache on a system service does not touch your data. The reset wipes saved networks and pairings, which you can re-add in five minutes.
Why did this happen suddenly?
Often after a system update that did not migrate the state file cleanly. The cache clear or network reset rebuilds it.
Will a factory reset fix it?
It almost always fixes software-side toggle bugs. Try the cache clear and the network-settings reset first; both are far less invasive and equally effective in most cases.
Bottom line
A stuck Wi-Fi or Bluetooth toggle is almost always a cached state problem. Clear the system service cache, reboot, and if that fails, reset network settings. If the toggle works but the radio still cannot see anything after a clean state, the hardware is asking for service and no amount of software work will move the needle. The cache clear alone fixes more than half of the cases we see.
