-
Notifications
You must be signed in to change notification settings - Fork 7
Frequently Asked Questions (FAQ)
Welcome to the NetToggle FAQ. This page explains how network modes, Root and Shizuku execution, Quick Settings cycles, SIM targeting, automation, shortcuts, themes, and diagnostics work.
For the latest changes, see NetToggle latest Release
Network mode support varies by Android version, device firmware, OEM implementation, modem, SIM provisioning, carrier configuration, and local network deployment. A mode appearing in NetToggle does not guarantee that the device or carrier will successfully register on that network.
Changing the preferred cellular network type requires elevated telephony privileges such as MODIFY_PHONE_STATE. Standard third-party Android apps cannot normally hold this permission.
NetToggle therefore requires either:
- Shizuku, which is recommended for most users
-
Root, through a compatible
suimplementation
NetToggle uses the authorized execution method to communicate with Android's telephony framework and apply supported network preferences.
Shizuku is recommended for most users because it provides a convenient privileged connection without granting full Root access directly to NetToggle.
Shizuku can be started through:
- Root
- ADB
- Wireless Debugging
Trusted Shizuku-compatible implementations or forks may also provide convenience features such as start on boot, watchdog operation, or TCP mode. Availability depends on the chosen implementation, Android version, and device firmware.
Root mode remains available for users who prefer Magisk, KernelSU, APatch, or another compatible su solution.
Yes. Shizuku can use Root to start its privileged service. In this configuration, NetToggle communicates through Shizuku instead of requesting Root access directly.
This can provide a cleaner authorization flow and allow multiple compatible apps to use the same Shizuku service.
Read Phone State is an optional performance permission.
When granted, NetToggle can use native Android subscription APIs to resolve:
- Active SIM subscriptions
- Physical SIM slots
- Default mobile-data SIM
- Carrier names
- Per-SIM network capabilities
Without this permission, NetToggle attempts to use slower privileged shell fallbacks where available. Switching can still work, but SIM and capability detection may take longer or be less reliable on heavily modified devices.
NetToggle uses the permission only for SIM, subscription, carrier, and capability resolution. NetToggle does not include analytics, trackers, Internet access, or functionality for transmitting phone-state information.
NetToggle does not run a persistent background service.
The startup receiver runs briefly after a reboot or app update to clear stale Quick Settings state. This prevents the tile from displaying a cached mode from before the restart.
The tile reads the current state again when required.
Some modern Root managers do not automatically display a permission prompt for background requests.
Open the Root manager and check its Superuser or Permissions section:
- Find NetToggle.
- Enable Root access.
- Return to NetToggle.
- Select Root again or reopen the app.
Also verify that your Root implementation provides a functional su command.
Check the following:
- Open the Shizuku application.
- Open Authorized applications.
- Ensure NetToggle is authorized.
- Verify that the Shizuku service is currently running.
- If the device was restarted, start Shizuku again unless your Shizuku implementation supports automatic startup.
- Return to NetToggle and select Shizuku again.
If the status remains unavailable, restart Shizuku and then reopen NetToggle.
NetToggle provides six curated modes:
| Mode | Radio access behavior |
|---|---|
| Preferred 5G | Allows 5G, LTE, 3G, and 2G where supported |
| 5G Only | Allows NR only and disables LTE, 3G, and 2G |
| Preferred 4G | Disables 5G but allows LTE, 3G, and 2G |
| 4G Only | Allows LTE only and disables 5G, 3G, and 2G |
| Preferred 3G | Allows 3G and 2G while disabling LTE and 5G |
| 2G Only | Allows GSM or EDGE only |
Please find below:
| Mode | What It Does Under the Hood | Best For |
|---|---|---|
| Prefer 5G (5G / LTE / 3G / 2G) | Allows 5G NSA (EN-DC), 5G SA, 4G LTE, and legacy fallback. Actively requests 5G/UW/5G+ when available while retaining LTE anchoring. | Recommended for daily 5G use, 5G Ultra Wideband, and reliable calls/data. |
| 5G Only (NR Only) | Forces the modem to connect strictly to 5G Standalone (5G SA). All 4G LTE, 3G, and 2G radio bands are disabled. | Pure 5G SA networks (e.g., T-Mobile SA, Jio 5G True5G, specialized 5G private networks). |
| Prefer 4G (LTE / 3G / 2G) | Disables 5G modems entirely while keeping 4G LTE, 3G, and 2G active. | Battery saving, reducing phone heat, or avoiding unstable/flickering 5G fringe areas. |
| 4G Only (LTE Only) | Locks the modem to LTE. Drops connection if 4G signal is lost instead of degrading to 3G/2G. | Ensuring high-speed data without falling back to slow 2G/3G in weak signal pockets. Requires VoLTE for phone calls. |
| Prefer 3G (3G / 2G) | Disables 4G and 5G; allows UMTS/HSPA/GSM connections. | Ultra-low bandwidth or legacy 3G network testing. |
| 2G Only (GSM / EDGE Only) | Locks to basic 2G cellular network. | Extreme battery conservation, emergency standby, or basic voice/SMS where 2G is still active. |
A Preferred mode keeps fallback networks available.
For example:
- Preferred 5G can fall back to LTE, 3G, or 2G where supported.
- Preferred 4G can fall back to 3G or 2G.
- Preferred 3G can fall back to 2G.
An Only mode disables other radio-access generations.
For example:
- 5G Only disables LTE, 3G, and 2G.
- 4G Only disables 5G, 3G, and 2G.
- 2G Only disables higher generations.
Preferred modes are generally safer for daily use. Only modes are useful when strict radio selection is specifically required.
5G NSA, or Non-Standalone, uses LTE as an anchor for signaling and attaches a 5G NR carrier for additional data capacity. This is commonly called EN-DC.
In NSA operation:
- LTE remains required.
- Calls commonly use VoLTE.
- The 5G carrier may attach only when data demand increases.
- Disabling LTE can prevent the device from connecting to 5G.
5G SA, or Standalone, connects directly to a 5G Core network without requiring LTE as an anchor.
In SA operation:
- LTE is not required for initial 5G registration.
- Voice calls require carrier and device support for VoNR or another supported fallback mechanism.
- The SIM, plan, firmware, and local network must all permit SA access.
5G Only is an NR-only mode. It disables LTE, 3G, and 2G.
The connection may be lost when:
- The local 5G network uses NSA and requires LTE anchoring.
- The SIM or mobile plan is not provisioned for 5G SA.
- The device firmware disables SA for the selected carrier.
- The local tower does not provide a compatible SA signal.
- VoNR is unavailable and the device cannot maintain voice service.
- The modem or OEM does not fully support NR-only operation.
If this occurs, use Preferred 5G instead.
Preferred 5G allows the modem to use supported 5G SA or NSA frequencies, including carrier-branded services such as UW, UC, 5G+, or 5G++, where available.
Access still depends on:
- Device radio hardware
- Supported frequency bands
- Carrier provisioning
- Mobile plan
- SIM configuration
- Device firmware
- Local network availability
NetToggle selects the permitted radio-access technologies. The modem and carrier decide the exact band, aggregation combination, and premium-network indicator.
This is normally controlled by the device and network.
On NSA networks, the secondary 5G carrier may be released while the device is idle to conserve power and reduce heat. The carrier can reconnect the 5G radio when higher data activity begins.
As a result, the status icon may change between LTE, 5G, UW, UC, or 5G+ even while the device remains in the same location.
Preferred 5G allows 5G access when the network decides to attach it, but NetToggle does not force a specific status-bar icon.
Calls require working VoLTE support from the device, firmware, SIM, plan, and carrier.
If VoLTE is unavailable, 4G Only prevents the phone from falling back to 3G or 2G for voice calls. Incoming and outgoing calls may therefore fail.
Use Preferred 4G or Preferred 5G if calls do not work.
Calls normally require:
- 5G Standalone registration
- VoNR support
- Carrier provisioning
- Compatible device firmware
- A supported local network
On an NSA network, 5G Only disables the LTE anchor required for registration and calls. Mobile service may be lost completely.
Use Preferred 5G for ordinary daily use.
4G Only permits LTE radio access. LTE Advanced and Carrier Aggregation remain controlled by the modem, firmware, carrier, signal conditions, and local tower configuration.
NetToggle does not independently force a particular Carrier Aggregation combination.
Android modem profiles generally represent 2G restriction through a 2G-only setting. A mode that prioritizes 2G while automatically moving upward to newer generations is not consistently available across Android devices.
Use 2G Only when strict GSM or EDGE access is required.
NetToggle evaluates available device, subscription, and carrier information.
A mode may be removed when:
- The device does not support the required radio generation.
- The selected SIM does not support it.
- The carrier configuration disables it.
- A known carrier has retired 2G or 3G service.
- Both-SIM mode is selected and one SIM does not support the mode.
Capability detection is conservative, but OEM and carrier reporting is not always complete. Actual switching support must still be tested on the device.
NetToggle applies network-mode preferences through Android telephony interfaces and privileged system commands. It does not modify baseband firmware, modem partitions, SIM firmware, or hardware limits.
An incompatible Only mode can temporarily cause No Service, unavailable data, or failed calls. Returning to a compatible Preferred mode normally restores connectivity.
NetToggle supports:
- Auto
- SIM 1
- SIM 2
- Both
Auto targets the active mobile-data subscription. Manual targets apply the change to the selected physical SIM slot.
Auto first identifies the current default mobile-data subscription and maps it to the correct physical SIM slot.
When Read Phone State is granted, NetToggle uses native subscription APIs for faster resolution. If native resolution is unavailable, NetToggle can attempt privileged shell fallbacks.
Select SIM 1 or SIM 2 manually from the Home tab.
Auto detection can fail on:
- Custom ROMs
- Heavily modified OEM telephony frameworks
- Devices reporting invalid subscription information
- Temporarily inactive data subscriptions
- Unusual eSIM or multi-SIM configurations
Both-SIM mode applies the selected network mode to SIM 1 and SIM 2.
Before presenting modes, NetToggle intersects the capabilities of both active SIMs. A mode is offered only when it is considered compatible with both SIMs.
Both applications are performed as separate telephony operations.
NetToggle reads each SIM separately.
If the modes differ, NetToggle selects a compatible mode from the configured Quick Tile Cycle and synchronizes both SIMs to that mode.
This automatic synchronization does not replace the intentionally saved mode used by Auto Restore.
A partial failure means the mode was applied to one SIM but failed on the other.
When this occurs:
- The shared cached mode is invalidated.
- The QS tile enters an error state.
- NetToggle records which SIM succeeded and which failed.
- A diagnostic report is made available in the app.
Open the diagnostic banner for details.
No. Both-SIM mode uses the intersection of SIM 1 and SIM 2 capabilities. A mode unsupported by either SIM is removed from Both-SIM configuration options.
Open the Home tab and choose two or three modes in the Quick Tile Cycle section.
The selection order becomes the tile order. For example:
Preferred 5G → 4G Only → Preferred 4G
Each tile tap applies the next mode in the cycle.
A cycle needs at least two modes to perform a meaningful switch. NetToggle therefore prevents the cycle from being reduced below the supported minimum.
The tile icon indicates the active target:
- 1 for SIM 1
- 2 for SIM 2
- + for Both SIMs
- A dashed Auto-style badge for automatic data-SIM targeting
The text in the center represents the active or cached network mode.
No. NetToggle uses cached state and limited passive refresh checks.
The app does not run a continuous polling service. Modem readbacks are controlled to reduce unnecessary privileged operations and background work.
Auto Restore remembers the last intentionally selected mode.
If Android, the modem, thermal management, or the carrier later changes the active mode, NetToggle can attempt to restore the saved mode when the QS tile refreshes.
Auto Restore respects the selected target, including Both-SIM mode.
No. Synchronization performed when Both-SIM mode is selected does not overwrite the intentionally saved preferred mode.
The active mode can be unknown when:
- The system does not expose a readable mode.
- The Root or Shizuku service is unavailable.
- SIM resolution fails.
- SIM 1 and SIM 2 use different modes in Both-SIM mode.
- The modem returns a bitmask that cannot be mapped reliably.
- A partial dual-SIM operation occurred.
The tile can refresh again when execution access and subscription information become available.
Verify that:
- Root or Shizuku is active and authorized.
- At least two Quick Tile Cycle modes are selected.
- The selected SIM is active.
- Both SIMs are active when Both is selected.
- The requested mode is supported for the selected target.
- No previous switching operation is still running.
Open NetToggle to view setup status and any diagnostic banner.
Network-mode changes are serialized to protect the modem from overlapping requests.
While one operation is running, additional tile taps are ignored until the current operation completes.
The Automate tab allows up to four configurable shortcut actions.
Each shortcut can have:
- A custom name
- A network mode
- A target SIM
- SIM 1, SIM 2, or Both-SIM capability filtering
The configured actions can appear as Android dynamic app shortcuts.
Dynamic shortcuts appear in the launcher’s app-shortcut menu when NetToggle is long-pressed.
Pinned shortcuts are requested as independent launcher icons placed on the home screen.
Pinned-shortcut availability and confirmation behavior depend on the launcher.
Supported OEM automation tools can launch NetToggle’s shortcut actions where the operating system exposes app shortcuts as routine actions.
Compatibility depends on the OEM and its automation application.
No. NetToggle’s own shortcuts execute internally through the shared automation engine.
The external broadcast opt-in and token are required only for requests sent by other applications.
Yes. A shortcut launches the internal shortcut action and sends the request to the automation executor.
Root or Shizuku must still be active and authorized at execution time.
Shortcut mode lists are filtered using the capabilities of the selected SIM.
For Both-SIM shortcuts, only modes considered supported by both SIMs are shown.
The previously selected mode may not be supported by the newly selected SIM. NetToggle rebuilds the mode list for the new target and selects an available compatible mode.
NetToggle provides four managed shortcut slots to keep the interface predictable and compatible with launcher and routine integrations.
Pinned home-screen shortcuts can have unique identifiers, but the in-app routine editor manages up to four primary configurations.
Broadcast automation allows supported external tools to request a network-mode change by sending an explicit Android broadcast to NetToggle.
It can be used with tools such as:
- Tasker
- MacroDroid
- Automate
- Compatible terminal or ADB workflows
- Other applications capable of sending explicit broadcasts
No. External automation is disabled by default.
The feature must be enabled manually in the Automate tab after Root or Shizuku has been authorized.
The token prevents unrelated applications from using NetToggle’s exported broadcast receiver without permission.
An external request must include the token currently shown in NetToggle.
The token can be:
- Copied
- Regenerated
- Disabled by turning off external automation
Treat the token as a local secret.
All existing external automation profiles using the previous token stop working.
Update the token in Tasker, MacroDroid, Automate, scripts, or other calling applications.
NetToggle’s internal shortcuts are not affected.
Supported values correspond to NetToggle’s network modes, such as:
-
5G(or5G_ONLY) -
4G(or4G_ONLY,LTE) -
PREF_5G(orPREFERRED_5G) -
PREF_4G(orPREFERRED_4G) -
PREF_3G(orPREFERRED_3G) -
2G(or2G_ONLY)
Use the command preview or copied broadcast specification shown in the Automate tab to avoid spelling errors.
The automation interface uses:
-
1for SIM 1 -
2for SIM 2 -
3for Both SIMs
Use NetToggle’s generated command preview for the exact current format.
No. External requests use the same central automation executor as NetToggle shortcuts.
Requests are validated against:
- Execution authorization
- Requested mode
- Requested target
- Active SIM availability
- Per-SIM capabilities
- Both-SIM capability intersection
Intentional shortcut and broadcast actions can update the last preferred mode so that Auto Restore does not immediately undo a valid automation request.
Internal maintenance operations, such as automatic Both-SIM synchronization, do not redefine the preferred mode.
Common reasons include:
- External automation is disabled.
- The token is missing or incorrect.
- Root or Shizuku is unavailable.
- The requested mode is invalid.
- The requested SIM is unavailable.
- The mode is unsupported by the selected SIM.
- Both-SIM mode was requested without two active SIMs.
- Another telephony operation is still running.
Check NetToggle’s diagnostic banner when a backend execution failure occurs.
NetToggle uses a three-tab pill-shaped navigation interface:
- Home
- Automate
- Guide
The layout adapts to portrait and landscape orientation.
The Home tab contains:
- Execution Mode setup
- Root and Shizuku authorization status
- Target SIM selection
- Quick Tile Cycle configuration
- Auto Restore control
- Theme toggle in the top-right area
- Error and diagnostic status when applicable
The Automate tab contains two subtabs:
- Broadcast
- Shortcuts
Broadcast provides external automation controls, token management, command previews, copied specifications, and testing.
Shortcuts provides up to four configurable routine actions, dynamic app shortcuts, testing, and launcher pinning.
The Guide tab contains:
- Execution-mode guide
- Target-SIM guide
- Quick Settings tile guide
- Shortcut and routine guide
- Broadcast automation guide
- Troubleshooting and FAQ links
- App information
- Version information
- License information
- Developer information and project links
NetToggle provides:
- Auto
- Light
- Dark
- AMOLED
Auto follows the device’s current day or night configuration.
AMOLED uses pure-black surfaces where configured to reduce illuminated pixels on OLED displays. A black theme can reduce power usage in some conditions, but it does not guarantee prevention of display burn-in.
Target SIM, Quick Tile Cycle, automation, and shortcut testing require an authorized execution backend.
The controls remain visually locked or dimmed until Root or Shizuku is active and authorized.
The updated interface includes:
- English
- Bengali
- Chinese
- Portuguese
- Russian
- Spanish
Some Android system messages, Root-manager screens, Shizuku screens, carrier strings, or OEM dialogs may continue to use the device or external application language.
NetToggle combines several available signals:
- Device-level radio profile information
- Android-version capability assumptions
- Active subscription and physical-slot information
- Carrier configuration values
- A maintained registry for known LTE-and-above networks
- Cached capabilities associated with the current subscription ID
The result is used to hide modes that are unlikely to work on the selected SIM.
NetToggle calculates the intersection of SIM 1 and SIM 2 capabilities.
For example:
- SIM 1 supports 5G and SIM 2 does not: 5G modes are hidden for Both.
- SIM 1 supports 2G and SIM 2 does not: 2G Only is hidden for Both.
- Both SIMs support 4G: 4G modes remain available.
Yes. OEM firmware and carrier configuration output can be incomplete, inconsistent, or modified.
NetToggle uses conservative fallbacks when capability information cannot be determined reliably. Actual modem behavior remains the final test.
Per-slot capability information is associated with the subscription ID.
When a different subscription is detected, NetToggle invalidates the previous slot cache and resolves capabilities again.
Auto Restore remembers the last mode intentionally selected through supported NetToggle actions.
This can include:
- QS tile switching
- NetToggle shortcuts
- Valid external automation
Automatic internal synchronization is not treated as a new user preference.
Auto Restore is checked during controlled state refreshes. It does not continuously monitor the modem.
If the current readable mode differs from the saved preferred mode and the configured conditions are met, NetToggle can attempt to restore it.
NetToggle uses controlled refresh timing and serialized telephony execution to avoid rapid repeated requests.
However, Android, the modem, device thermal management, or the carrier may enforce a different mode. If a mode is repeatedly rejected or reverted, disable Auto Restore or select a more compatible Preferred mode.
Possible causes include:
- Device restart
- Airplane mode
- SIM re-registration
- Carrier configuration updates
- Thermal management
- Loss of compatible coverage
- Modem recovery
- OEM power-saving behavior
- Network-policy enforcement
NetToggle cannot override every hardware or carrier restriction.
Open NetToggle and tap the error banner.
The diagnostic report can include:
- Execution mode
- Target SIM
- Resolved slot and subscription information
- Attempted command or Binder method
- Exit code
- Standard output
- Standard error
- Exception message
- Root or Shizuku status
- Failure timestamp
Copy the report and review its contents before sharing it.
Binder failures do not always produce shell standard error. Instead, the useful reason may be stored as an exception message.
Use the complete diagnostic report rather than checking only the stderr field.
This is a partial Both-SIM failure.
Possible causes include:
- One SIM became inactive.
- One subscription ID changed.
- One SIM rejected the selected mode.
- The OEM telephony framework handled the two subscriptions differently.
- Shizuku or Root access failed during the second operation.
- The carrier restored one SIM to another mode.
Open the diagnostic report to identify the failed SIM and operation.
NetToggle displays cached state immediately for a responsive tile experience, then performs controlled readback where appropriate.
The tile can briefly show the previous mode while the modem applies or reports a new state. If the state remains incorrect, reopen the app and check diagnostics.
Android System UI, the OEM framework, and the carrier may cache or smooth network indicators.
NetToggle performs a best-effort refresh nudge when supported, but the modem and System UI control the final displayed icon.
A shared Both-SIM mode is reported only when both SIMs return the same known mode.
If SIM 1 and SIM 2 differ, NetToggle returns Unknown rather than displaying an incorrect shared value.
Without the optional permission, NetToggle may need to run privileged shell commands to resolve subscriptions and slots.
Native Android subscription APIs are usually faster than parsing shell output.
Check the selected execution mode:
- Restart Shizuku if it is not automatically started.
- Confirm NetToggle is still authorized in Shizuku.
- Confirm Root access remains enabled in the Root manager.
- Open NetToggle and verify the execution status.
- Confirm the selected SIM is active.
- Check the error banner for diagnostics.
An Android or ROM update can change:
- Hidden telephony method signatures
- Required permissions
-
cmd phonebehavior - Subscription reporting
- Carrier configuration output
- Root policies
- Shizuku behavior
Reauthorize the selected execution mode, reopen the app, and generate a new diagnostic report if the issue continues.
No. NetToggle does not request Internet permission.
No. NetToggle does not include advertisements, analytics, telemetry, or tracking SDKs.
NetToggle stores and validates the token locally. The app does not include Internet permission for transmitting it.
External automation tools may store the token in their own profiles. Review the privacy and backup behavior of those tools separately.
A diagnostic report may include:
- Device model and Android version
- App version
- Execution mode
- Selected SIM target
- Subscription IDs
- Carrier names
- Commands and output
- Error and exception information
Review the report before posting it publicly.
Open an issue in the NetToggle GitHub repository.
For discussion and community support, join the NetToggle Project Chat on Telegram.
Include:
- Device manufacturer and model
- Android version
- ROM or OEM software version
- Root or Shizuku execution mode
- Selected SIM target
- Requested network mode
- Whether the problem affects the app, QS tile, shortcut, or broadcast
- Whether the device has one or two active SIMs
- The copied NetToggle diagnostic report
- Steps required to reproduce the issue
Remove any information you do not want to share publicly.
Open the Guide tab inside NetToggle. It includes cards for:
- Execution Mode configuration
- Target SIM setup
- Quick Settings tile setup
- App shortcuts and routines
- Broadcast automation
- Troubleshooting
The Guide tab also includes app details, license information, version information, developer information, and project links.