Settings Database Editor
Provides direct access to the Android settings database
4A · by4a.setedit22
UpdatedNov 7, 2025
PublishedJun 9, 2023
Packageby4a.setedit22
MD5a9fb0d792147996c5258db5f6bfc6a9d
SHA1 (signer)17:4D:21:4F:6B:CA:A0:5E:90:F6:0F:AF:33:61:E8:6B:FC:D7:F6:AB
Signed byO=4A
Architecturesx86, x86-64, armeabi-v7a, arm64-v8a
Malware scanTRUSTED
Contact[email protected]
Privacy policyView
What's new
* Android Q and later will warn that SetEdit "may not work properly". This is incorrect. We can't stop this warning without reducing SetEdit's functionality, and we will not do that.
v2018.10.31:
* Added support for the SetEdit Community Translation Project
* Due to Google Play policy changes, for the foreseeable future, there will be no more updates to the main SetEdit app. All future updates will come in the form of addons, such as the Feature Pack and the Community Translation Project.
v2018.10.31:
* Added support for the SetEdit Community Translation Project
* Due to Google Play policy changes, for the foreseeable future, there will be no more updates to the main SetEdit app. All future updates will come in the form of addons, such as the Feature Pack and the Community Translation Project.
Description
WARNING -- We do not guarantee that problems caused by the improper use of this utility can be fixed, and we are unable to help you with any such problems. We support only this app, not your device's system software. Settings Database Editor (SetEdit) is invaluable if you need it, but if you're not careful you're very likely to mess something up.
By default, for your protection, Android prevents you from modifying the SECURE and GLOBAL tables. If you have Android Jellybean or later, you can remove this protection from an ADB shell using the command "pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS". On earlier versions, you can only remove this protection on a rooted device by installing SetEdit to the system partition.
By default, for your protection, Android prevents you from modifying the SECURE and GLOBAL tables. If you have Android Jellybean or later, you can remove this protection from an ADB shell using the command "pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS". On earlier versions, you can only remove this protection on a rooted device by installing SetEdit to the system partition.
Permissions (2)
Settings Database Editor requests the following Android permissions:
- Write Secure Settings android.permission.WRITE_SECURE_SETTINGS
- Write Settings android.permission.WRITE_SETTINGS
