When you open SetEdit and try to switch to the Secure Table or Global Table, you might see the dreaded message:
"setedit does not currently support editing this table"
In some versions, the error also appears as: "Editing of this table is not supported on this device."
On Android Automotive (car head units) and some Android TV devices, the secure table is locked by the car manufacturer or TV vendor for safety reasons. You cannot unlock this without an engineering build of the OS.
Recommendation: Avoid using setedit for any table other than system, global, or secure. Use settings list global to confirm available namespaces.
The "SetEdit does not currently support editing this table" error usually appears when you try to modify the Global or Secure tables on newer versions of Android (Android 11 and above). Google has tightened permissions, blocking apps from changing these system-level settings without manual authorization. 🛠️ The Quick Fix
To bypass this, you must grant the WRITE_SECURE_SETTINGS permission using a computer and ADB (Android Debug Bridge).
Enable Developer Options on your phone (Tap "Build Number" 7 times). Turn on USB Debugging in the Developer menu. Connect your phone to a PC with a USB cable.
Open a Command Prompt/Terminal on your PC and type:adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS Restart SetEdit. The error should disappear. 🔍 Why This Happens
System Protection: Android restricts third-party apps from touching the Secure and Global tables to prevent malware from breaking your phone.
Android 14+ Limits: On the latest Android versions, even the ADB fix might fail for certain specific "read-only" keys.
App Updates: The original SetEdit hasn't been updated in years; some modern system tables use a format the app doesn't recognize. 💡 Alternative Apps setedit does not currently support editing this table
If SetEdit still won't behave, try these modern alternatives that handle newer Android permissions better:
LADB (Local ADB): Lets you run the permission command directly on your phone without a PC (uses Wireless Debugging).
SystemUI Tuner: A more user-friendly interface for many common SetEdit tweaks.
Brevent: Excellent for managing deep system behaviors on Android 12+.
💡 Pro Tip: Always screenshot the original value before you change anything. A single typo in these tables can cause your phone to boot-loop or disable the touchscreen. If you'd like, I can help you: Walk through the ADB installation step-by-step Find the specific command for LADB (no PC needed)
Check if the specific setting you want to change is even possible on your Android version
Which setting were you trying to change when the error popped up?
The error message "SetEdit does not currently support editing this table" typically appears when a user attempts to modify values in the Secure or Global tables without having granted the application the necessary elevated permissions via Android Debug Bridge (ADB). Cause of the Issue
By default, Android restricts third-party applications from modifying the SECURE and GLOBAL tables to protect system stability and security.
Missing ADB Permissions: Without the specific WRITE_SECURE_SETTINGS permission, the app is "locked" from making changes to these critical tables.
Android 14+ Restrictions: Newer Android versions have introduced stricter "Restricted Settings" and API limitations that can block SetEdit (which often targets older APIs to maintain functionality) from operating correctly.
Incompatibility: Some manufacturers (like Xiaomi or Samsung on newer One UI versions) have implemented software-level rejections that prevent these edits even if permissions appear to be granted. Resolution Steps When you open SetEdit and try to switch
To resolve this error and "unlock" the restricted tables, you must manually grant the app permission using a computer with ADB or an on-device shell terminal. 1. Grant Permission via ADB (Computer)
Enable Developer Options and USB Debugging on your Android device. Connect your phone to a computer with ADB installed.
Open a terminal/command prompt and enter the following command:adb shell pm grant io.github.muntashirakon.setedit android.permission.WRITE_SECURE_SETTINGS(Note: Replace io.github.muntashirakon.setedit with the exact package name of your version, such as by4a.setedit22 for the Play Store version). 2. On-Device Workarounds (No PC)
HELP Poco X3 NFC haptic feedback issue - battery saver turned off
This error message appears because Android blocks standard apps from modifying the Secure and Global tables for security reasons. To bypass this, you must manually grant the app elevated permissions using ADB (Android Debug Bridge) or a similar tool. How to Fix It
You need to grant the WRITE_SECURE_SETTINGS permission to the app. Choose the method that fits your setup: Method 1: Using a PC (ADB)
Enable Developer Options on your phone (Settings > About Phone > Tap "Build Number" 7 times). Enable USB Debugging in the Developer Options menu.
Connect your phone to a PC and open a terminal/command prompt.
Run the following command:adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS(Note: If you use the open-source version from GitHub, the package name might be io.github.muntashirakon.setedit instead.) Method 2: No PC (Wireless Debugging)
If you don't have a computer, you can use apps like LADB or Brevent to run commands directly on your device: Enable Wireless Debugging in Developer Options.
Pair the terminal app (like Brevent) with your device using the pairing code provided in Wireless Debugging settings.
Enter the same command as above:pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS Important Notes "setedit does not currently support editing this table"
Android 14+ Restrictions: On newer versions of Android, standard SetEdit may have issues because it targets older APIs. Users often recommend downloading the latest open-source version from the official GitHub repository to ensure compatibility.
Rooted Devices: If your device is rooted, you can grant permissions directly through a terminal emulator app (like Termux) by typing su first, though using ADB is often more reliable.
Are you trying to change a specific setting, like the refresh rate or a system feature, that I can help you find the correct table for?
The error message "SetEdit does not currently support editing this table" typically appears when you try to modify the tables without the necessary system-level permissions
. Android restricts these tables by default to prevent accidental system damage. How to Fix the Error To unlock these tables, you must grant SetEdit the WRITE_SECURE_SETTINGS permission using ADB (Android Debug Bridge) Option 1: Using a PC (Standard ADB) Enable Developer Options Settings > About Phone Build Number Enable USB Debugging Developer Options , toggle on USB Debugging Connect to PC
: Connect your phone to your computer and open a command prompt or terminal in your ADB folder. Run the Command : Type the following command and press Enter:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS (Note: Use io.github.muntashirakon.setedit instead if you are using the open-source version from Option 2: No PC Required (Wireless Debugging) If you don't have a computer, you can use apps like to run commands directly on your phone. Wireless Debugging in Developer Options. Open your chosen terminal app (e.g.,
) and pair it using the code provided in your system settings. Enter the same command mentioned above. Why this happens on Android 14+
Starting with Android 14, system software often rejects these edits even with permissions due to stricter security policies. Use an Alternative : If SetEdit continues to fail on Android 14 or 15, use "Exec command" feature to put settings directly: settings put [table_name] [flag_name] [value] settings put system peak_refresh_rate 120 Version Check : Ensure you are using the latest version of SetEdit from GitHub
, as the Play Store version may not be fully compatible with newer Android versions.
Editing these tables can lead to system instability or bootloops if incorrect values are entered. Always record the default value before making changes. ADB command for a particular setting you're trying to change? How to set "PREFERRED NETWORK" to 5G Only/4G Only
On non-rooted, production (user) builds, writing to secure or global is restricted. setedit may read from these tables but cannot write, generating this error.
For rooted devices, directly modify /data/data/com.android.providers.settings/databases/settings.db using sqlite3.