Don't automatically backup settings in Android demo apps

[grisaitis]

When re-installing the android demo apps, the OS caches and re-populates values in the settings pane.

I think this might cause some confusion for people trying out the demos but who aren't experienced native app devs (like me 🙂).

specifically for me, the settings caching made me think that old files that i had pushed, removed, and then replaced with other files were still on the device somehow. eg, i replaced a tokenizer.bin with a tokenizer.model, and the settings still said tokenizer.bin... this made me think maybe the old tokenizer was still floating around in app storage or something.

to change the behavior is 1 loc for each demo app. in examples/demo-apps/android/*Demo/app/src/main/AndroidManifest.xml,

-        android:allowBackup="true"
+        android:allowBackup="false"

i made a PR for personal glory but no worries if you want to do something else.

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/5822

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 2 New Failures

As of commit 552cbbe with merge base 152e22d ():

NEW FAILURES - The following jobs have failed:

• Android / run-emulator (gh)
  ##[error]EACCES: permission denied, mkdir '/opt/android/sdk/cmdline-tools'
• pull / unittest-arm (buck2) / linux-job (gh)
  ../../dev/ops/test_add.py::TestSimpleAdd::test_add2_tosa_BI_4

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[facebook-github-bot]

@kirklandsign has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[facebook-github-bot]

@kirklandsign merged this pull request in dae765e.