The error you're encountering indicates that the android.permission.WRITE_SETTINGS permission is managed by a role on One UI (Samsung's Android skin). This means you cannot grant it directly via ADB for com.termux.api or any other app. Instead, you must assign the app to a role that includes this permission.

---

How to Grant WRITE_SETTINGS on One UI

Method 1: Use ADB to Assign a Role

One UI restricts WRITE_SETTINGS to apps assigned to the "Settings Manager" role. You can assign this role to com.termux.api using ADB:

1. Check available roles (optional):

   bash
   Copy
   adb shell dpm list-roles

   Look for android.app.role.SETTINGS_MANAGER or similar.

2. Assign the role to Termux:API:

   bash
   Copy
   adb shell dpm set-role-holder com.termux.api android.app.role.SETTINGS_MANAGER

   If this fails, try:

   bash
   Copy
   adb shell dpm set-role-holder com.termux.api android.app.role.WRITE_SETTINGS

3. Verify the role assignment:

   bash
   Copy
   adb shell dpm get-role-holders android.app.role.SETTINGS_MANAGER

Method 2: Manually Enable in Settings (No Root)

If ADB fails, try enabling it manually:

1. Open Settings > Apps.

2. Tap the three-dot menu > Special Access > Write system settings.

3. Enable com.termux.api (Termux:API) in the list.

   (Note: This path may vary slightly depending on your One UI version.)

Method 3: Use Shizuku (Alternative)

If the above fails, use Shizuku to grant the permission via ADB:

1. Install Shizuku and start it via ADB.
2. Use an app like App Ops to enable WRITE_SETTINGS for Termux:API.

---

Why This Happens

• One UI (and some other OEMs) restrict sensitive permissions like WRITE_SETTINGS to roles for security.
• The pm grant command fails because the permission is not a runtime permission but a role-managed permission.

---

Next Steps

Try Method 1 first. If it doesn’t work, check if com.termux.api appears in the Special Access menu (Method 2).