Android Wi-Fi Keeps Turning Back On? How to Find the Cause

If your Android Wi-Fi keeps turning back on after you've switched it off, the symptom can reflect one of three different states: the radio actually reactivated, the phone reconnected to a network it already knows, or background scanning kept running while the radio stayed off the whole time. Each one has a different fix, and figuring out which applies matters more than reaching for a factory reset (Sekin; How-To Geek).

A Google Pixel Community thread posted nearly four months ago contains reports from owners of Pixel 8, Pixel 9 Pro, and Pixel 9 Pro XL describing Wi-Fi reactivating even after they confirmed the relevant toggle was off, in discussions tied to the Android 17 rollout. The thread doesn't establish how widespread the behavior is, whether Android 17 caused it, or whether the various posters are even describing the same underlying problem.

Before working through the fixes below, it helps to note when the problem happens: right after leaving Airplane Mode, overnight while charging, near a network you've saved, or the moment you connect to a car for Android Auto. That detail points toward one of the causes below faster than guessing does.

Why does my Android Wi-Fi turn on automatically?

The first setting to check is "Turn on Wi-Fi automatically." It restores Wi-Fi only when two conditions line up at once: the network has to be one you've already saved, and the signal has to be strong enough for a stable connection (TechBone). It isn't a general "react to anything" switch, and the Android Open Source Project traces it back to Android 9, so this isn't new behavior, it's just easy to forget exists (Sekin, citing AOSP).

The cited guide also notes several conditions that can keep the feature from working at all: Location turned off, Battery Saver or Airplane Mode active, a hotspot or tethering session running, or background Wi-Fi scanning disabled (Sekin). Those conditions can change whether the feature works, which is worth checking before assuming anything is misbehaving.

Check whether the radio is actually off, not just disconnected

Tapping the Wi-Fi tile in Quick Settings feels like turning Wi-Fi off, but on Pixel phones it isn't the same action. A Pixel Community responder described tapping the tile as disconnecting the current network and pausing reconnection, while leaving the Wi-Fi radio itself powered on in the background (Google Pixel Community).

To see the real state on Pixel, long-press the tile to open full Internet settings and check the master "Use Wi-Fi" switch. If that switch is on, Wi-Fi was never fully off no matter what the tile showed. This is community guidance describing current Pixel behavior, not an official support ruling, so confirm it on your own phone before assuming it's the explanation.

Leaving a network, disabling the radio, and disabling scanning are three separate actions in Android (Sekin). Mixing them up is the most common reason people think Wi-Fi "turned itself back on" when it technically never went off.

How to disable Turn on Wi-Fi automatically on Android

On Pixel, the documented path is Settings > Network & internet > Internet > Network preferences > Turn on Wi-Fi automatically (Sekin; Google Pixel Community). Turning it off should stop Wi-Fi from re-enabling near a saved network.

The setting can also depend on Location being on. One Pixel Community poster reported that with Location off, the toggle displayed as off in the interface while Wi-Fi behaved as though it were still on, a single reported case rather than confirmed behavior across devices (Google Pixel Community).

If the toggle is confirmed off and Wi-Fi still comes back, that matches the open, unresolved reports from Pixel owners in the same thread. It contains no Google confirmation of a cause.

Is Wi-Fi scanning on, or did Android Wi-Fi turn on by itself?

Android can keep scanning for nearby networks under Settings > Location > Location services even when the Wi-Fi radio is switched off; the exact menu wording varies by manufacturer, but some version of this setting exists on most Android phones. That scanning supports location-accuracy features, not reconnection (How-To Geek).

Scanning by itself shouldn't reconnect you to a network or flip "Use Wi-Fi" to on. A useful check is opening Settings > Network & internet > Internet on Pixel (the path differs on other brands) and looking at two things: whether "Use Wi-Fi" shows on, and whether a specific network name appears as connected rather than just an icon flicker in the status bar (How-To Geek; Sekin). A connected SSID strongly suggests the radio reactivated.

If there's no SSID shown, scanning may be what you're seeing. You can temporarily disable Wi-Fi scanning as a test, but that may also disable automatic Wi-Fi restoration, so treat it as a diagnostic step rather than a permanent fix (Sekin).

Saved networks and auto-connect: a trade-off, not a clean fix

If Wi-Fi still reconnects after the checks above, test auto-connect on the specific saved network via Settings > Network & internet > Internet > gear icon next to the network. One Pixel Community poster, in a separate thread posted nearly four months ago, confirmed that turning off auto-connect stopped the unwanted reconnection, but it also meant the phone stopped automatically reconnecting to home Wi-Fi on arrival (Google Pixel Community). That's a genuine trade-off: no surprise reconnections, but no convenient auto-join either.

Samsung Galaxy: how to stop Wi-Fi from turning on

Galaxy phones don't necessarily follow the same settings path as Pixel. Android has no single menu sequence that works across every manufacturer, and Samsung doesn't document one universal route through its own interface either (Sekin).

A useful Galaxy-specific tool is Wi-Fi control history, found at Settings > Connections > Wi-Fi > More options > Advanced > Wi-Fi control history. It can show apps that automatically controlled Wi-Fi, with Samsung listing examples like Quick Share, Google Play services, and the Galaxy Watch plug-in (Sekin). Availability varies by model, region, and One UI version, so don't be surprised if the menu looks different or is missing entirely on some Galaxy devices.

Wireless Android Auto: a narrow cause worth testing, not a confirmed one

A forum report from last year ties Wi-Fi reactivation to wireless Android Auto, with a workaround of disabling it under Settings > Apps > Android Auto. Both the original poster and a second commenter noted the toggle isn't available on every phone (Android Central forum). Test this only if you use wireless Android Auto and the behavior lines up with connecting to a car; treat it as a lead, not a confirmed cause for Wi-Fi turning on by itself.

How to turn off Wi-Fi automatically on Android when you leave home

That's a different goal from stopping unwanted reactivation, and it's optional. Supported Galaxy phones can build it with Modes and Routines, using a "Wi-Fi disconnected from [network]" condition paired with an explicit Wi-Fi-off action; Pixel and most other Android phones need a third-party app like Tasker set to an explicit "Off" action rather than "Toggle," since Toggle can re-enable Wi-Fi if another setting has already changed the radio state (Sekin). If you rely on Wi-Fi calling, test call quality after setting this up, since cutting Wi-Fi automatically can affect indoor reception depending on carrier.

What to do next

Each test above points to a different fix. If "Use Wi-Fi" was never actually off, the Quick Settings tile caused the confusion on Pixel, and the master switch in full Internet settings is the one to trust. If "Turn on Wi-Fi automatically" was still on, disabling it under Network preferences resolves the issue for most people. If that setting was already confirmed off and the radio still reactivated, the cause likely sits with Wi-Fi scanning, saved-network auto-connect, or an app like wireless Android Auto, none of which are confirmed or universal explanations.

For Pixel owners seeing the behavior line up with the Android 17 rollout, the most useful next step is documentation, not a reset. Note the device model, Android version, when Wi-Fi turns back on, and the exact state of every relevant setting, then check Google's official Pixel support channels for an acknowledged fix. There is not enough evidence here to justify a factory reset as the next step.