Ever noticed your phone running hot and the battery tanking on the commute, then realised it's been desperately hunting for a 5G signal that barely exists in that area? You're not imagining it. The problem is real, and the fix, to automate 5G by location so your phone switches to LTE where 5G is rubbish and flips back when you're somewhere with proper coverage, sounds simple. Turns out it's a bit more involved than you'd hope. So here's what actually works, in order of difficulty, with no filler.

Why Automating 5G by Location Is Harder Than It Should Be

Here's the thing: Android doesn't give every app or automation tool the same level of access to the radio. The preferred network type setting, the one that lets you pick between 5G, LTE, or automatic, sits in a part of the system that carriers and manufacturers can lock down. So while your phone clearly knows where it is, and clearly knows what network it's on, connecting those two facts and acting on them isn't always permitted by the software.

Carrier firmware is a big part of this. Some carriers actively remove or grey out the LTE-only option because they want your phone on 5G whenever a signal exists, even a weak one. Others rename the menu entirely, which is why Samsung's path through Settings is different from a Pixel's. And if you're on a carrier-branded handset, the options you see might be a stripped-down version of what an unlocked phone would show.

Then there's the automation side. Apps like Tasker are brilliant at detecting your location using GPS, Wi-Fi networks, or cell towers. But detecting location and changing the radio mode are two separate things. Android's permission model treats telephony settings as privileged, so most automation apps can toggle mobile data on or off, but they can't directly tell the modem to prefer LTE over 5G. That requires either a manufacturer-level hook (which Samsung provides in some One UI versions), root access, or an ADB shell command.

Battery Saver mode is one thing that does disable 5G automatically, and some people use it as a rough workaround. But it also throttles performance and background activity, so it's not really a clean solution for this specific problem. And using airplane mode as a substitute is a bad idea because it drops your cellular connection entirely, including calls and SMS.

The good news is there are real options. They just depend on what phone you have.

Quick routeStart here

Automate 5G by Location: Quick Manual Fix First

Manual Preferred Network Type Switch Easy

Open Settings
On a Pixel or near-stock Android device, go to Network & internet, then SIMs, then tap your carrier name.
Find Preferred network type
Tap Preferred network type. On Samsung, the path is Settings > Connections > Mobile networks > Network mode. The option names differ but you're looking for a choice between 5G, LTE, or automatic.
Select LTE in weak-5G areas
Choose LTE (sometimes listed as LTE/3G/2G) when you're somewhere 5G is patchy, causing battery drain or heat. This stops the modem hunting for a signal it can barely hold.
Restore 5G when you're back in good coverage
Return to the same menu and select 5G/LTE automatic or equivalent. Avoid selecting 5G-only unless your carrier specifically recommends it, as it can cause call issues in mixed-coverage areas.
If the option is missing
Check whether Battery Saver is active, as it may already be forcing LTE. Also check for a carrier update that may have moved or hidden the menu. On Pixel, you can reset mobile network settings via Settings > System > Reset options > Reset Mobile Network Settings if the menu is behaving oddly.

Your phone should now stay on LTE in that area without hunting for 5G. Battery use and heat should drop noticeably within 30 minutes.

This manual approach is the safest option because it uses the carrier-supported interface and requires no third-party apps, root, or ADB. The downside is obvious: you have to remember to switch. That's why the solutions below exist.

For context on how Android handles network settings at the OS level, Google's official Android network help pages cover what's exposed to users versus what's locked to carriers.

Intermediate routeKeep going if needed

Automate 5G by Location with Samsung Modes and Routines

Samsung Modes and Routines Location Trigger Medium

Open Modes and Routines
Go to Settings > Modes and Routines. If you don't see this, your One UI version may be older. It appeared in One UI 5 and has been updated in subsequent releases.
Create a new Routine
Tap Routines at the bottom, then the + button. Tap Add condition and select Location. Drop a pin on the area where 5G is weak, such as your office building or a regular commute stop, and set a geofence radius. Use at least 200 to 300 metres to avoid the routine firing repeatedly as you walk near the boundary.
Add the network mode action
Tap Add action and look for options related to Mobile network, Network mode, or Connectivity. The exact label depends on your One UI version and carrier firmware. Set it to LTE.
Create the exit routine
Go back and create a second Routine. Use the same location but set the condition to Leave rather than arrive. Add the same network mode action but set it back to 5G/LTE automatic.
Test both triggers
Walk into and out of the geofence area with mobile data active and the phone unlocked. Check the preferred network type in Settings after each trigger fires to confirm it changed. The routine can take 30 to 60 seconds to activate after you enter the zone.

When working correctly, your phone will quietly drop to LTE as you arrive at the weak-5G location and restore 5G automatic when you leave, no manual switching needed.

If Network mode doesn't appear as an available action in Modes and Routines, your carrier firmware has blocked it. Samsung's software can only expose controls the carrier permits. In that case, skip to the Tasker or ADB solution below.

Non-Samsung phones aren't completely out of luck here. Motorola has a Rules feature, Xiaomi has its own automation tools, and some other manufacturers include similar built-in options. The process is the same: look for a location condition and a network mode or preferred network type action. But realistically, most of them only expose mobile data on/off, Wi-Fi, and Bluetooth. If that's all you see, those toggles won't help you automate 5G by location in any meaningful way.

If you're having broader Android connectivity issues alongside this, our guide to Android mobile data problems covers related settings that can interfere with network mode switching.

Advanced routeChange one thing at a time

Advanced: Automate 5G by Location with Tasker and ADB

Tasker Plus ADB Shell for Location-Based 5G Switching Hard

Install Tasker and set up location permissions
Get Tasker from the Play Store. Grant it precise location access and allow background location. Tasker needs this to fire reliably when you enter or leave an area, not just when the app is open.
Create a location Profile
In Tasker, tap the + to add a Profile, select Location, and drop a pin on your target area. Set the radius to at least 250 metres. Alternatively, use a Wi-Fi Connected or Cell Near context if your target location has a consistent Wi-Fi network or cell tower, as these can be more reliable than GPS indoors.
Enable Developer options and USB debugging
Go to Settings > About phone, tap Build number seven times to unlock Developer options. Then go to Settings > Developer options and enable USB debugging. Connect the phone to a computer that has Android Debug Bridge (ADB) installed.
Test the telephony command manually
On the computer, open a terminal and run adb shell to confirm the connection. The command to check preferred network type varies by device. On some Pixel and Samsung builds, settings get global preferred_network_mode returns the current value. Changing it requires a privileged shell on modern Android, which is why this step matters: test it manually before attaching it to Tasker. If the command is rejected, root is required.
Attach the shell command to Tasker tasks
Create an Entry task for the location Profile. Add a Shell action with the LTE command. Create an Exit task with the 5G automatic command. Add a Wait action of 30 to 60 seconds before the shell command in each task to avoid repeated firing at the geofence edge.
Revoke USB debugging when done
Once the Tasker profile is working, go back to Developer options and disable USB debugging. Leaving it on is a minor security risk, especially on a phone that connects to public Wi-Fi.

If the ADB command works on your device, Tasker will now fire it automatically when you enter or leave the defined area. Check the preferred network type in Settings after the first real-world trigger to confirm it's working.

This approach is not universal. Modern Android builds, carrier firmware, and OEM security policies may reject the telephony command or silently restore the previous setting after a reboot. Always test manually before relying on it. And do not use undocumented radio commands unless you have a way to recover if something goes wrong.

One thing people often miss: Tasker's built-in cellular variables let you check the current network type before running the switch. So you can add a condition like 'only run this if currently on 5G' to avoid unnecessary radio changes. That's a small but useful refinement, especially if you're near the boundary of a 5G area and the phone is already on LTE.

If your phone needs root for this and you're not sure whether your device supports it safely, our Android battery drain troubleshooting guide covers some of the same underlying issues through safer settings changes that don't require root access.

For a broader look at how Android handles network mode preferences at the OS level, HowToGeek's Developer Options explainer is a solid reference if you haven't enabled them before.

Preventing Battery Drain While You Sort the Automation

While you're getting the automation set up, a few habits make a real difference. The biggest one: use 5G/LTE automatic rather than 5G only. Most carriers set automatic as the default, and it means the phone will drop to LTE on its own when 5G is too weak to be useful. It's not location-aware, but it does stop the modem hammering away at a signal it can barely see.

Second, keep your geofence large. A 100-metre radius sounds precise, but GPS on a phone indoors can drift by 50 to 100 metres on its own. If your geofence is too small, the phone will enter and exit it repeatedly as the GPS position wobbles, and the automation will fire over and over. That's worse than no automation at all. 250 to 500 metres is more practical for most use cases.

Always add a delay before the mode change fires. 30 to 60 seconds is usually enough. It stops the routine triggering when you're just passing through an area rather than actually stopping there.

After any software update, SIM swap, or carrier configuration change, check that your preferred network type setting hasn't been reset. Carrier updates in particular have a habit of quietly restoring defaults, and you might not notice until you're wondering why the battery is draining again. Same goes after a factory reset or if you switch to an eSIM.

One thing that catches people out: turning off mobile data is not the same as switching to LTE. You can have mobile data off and still be on a 5G radio, which still uses power. The preferred network type setting is the one that matters for battery and heat, not the mobile data toggle.

Automate 5G by Location: Summary

To automate 5G by location on Android, start with your phone's built-in tools. Samsung's Modes and Routines is the most accessible option and works without any extra apps or computer access, provided your carrier hasn't blocked the network mode action. On other Android phones, the manual preferred network type switch is the safest and most reliable fix for the underlying battery drain and heat problem, even if it's not automatic.

If you want true location-based 5G switching on a non-Samsung device, Tasker combined with ADB shell commands is the most powerful route, but it comes with real limitations on modern Android. Carrier firmware, OEM security policies, and Android's permission model all work against you. Test everything manually before trusting it.

The goal is simple: LTE where 5G is rubbish, 5G where it's actually good. Getting there automatically takes a bit of work, but once it's set up and tested, it runs quietly in the background and your battery will thank you.

Automate 5G by Location on Android: Here's What Actually Works