The specific changes I attempted were to a database entry following instructions in this question: Possible to turn on Airplane mode with WiFi on only?

The changes to either row would take effect immediately but are reset following a reboot. The updated rows retain their row-id but revert to the previous/default data following reboot.

the exact command I used was:

adb shell settings put global airplane_mode_radios  "cell,bluetooth,nfc,wimax"

The following command would result in an exception where it is unable to find the key:

adb shell content update --uri content://settings/global --bind value:s:'cell,bluetooth,nfc,wimax' --where "name='airplane_mode_radios'"

I'm using Android 4.2.2 and the latest ADB available as of end of March.

  • Does "settings put" not persist? I've been using it to modify my captive portal and navigation bar settings, and those do persist as far as I see. – Andy Yan Apr 28 '17 at 23:41
  • Also, it's suggested that you open a full adb shell and execute the command within, instead of doing everything in a single line. – Andy Yan Apr 28 '17 at 23:42
  • Confirm Yan's words: mine are persisted too. Your problem lies elsewhere. – Suncatcher Apr 29 '17 at 6:10
  • 1
    I confirm that on my phone they are not persisted, on a LG G6 with Android 8.0.0. Opening adb shell didn't help. – Marco Lackovic Jul 19 '18 at 12:27
  • Having the same problem. My settings set by adb put don't persist after reboot, which is annoying. – Jay Zus Oct 2 '18 at 11:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.