Delete leftover AdServices files using a one-time boot-completed receiver

AdServices code is included in the ExtServices APK on S-, and generates multiple files that are stored in the data directory during normal operation. After OTA to T, the AdService code is removed from the ExtServices APK, but these data files are left behind. We're adding a new boot-completed receiver that's only enabled on T+ which will delete these files on reboot. After successful delete, the receiver disables itself since there's no need for it to run again.

Bug: 294912203
Test: atest, manual

Change-Id: I0fa1d452c4928cbc1c43efa5ba70124b75c12fd7
12 files changed
tree: c59141be2e567f42c5fdaf6156495ef6098363e4
  1. apex/
  2. java/
  3. jni/
  4. native/
  5. .clang-format
  6. Android.bp
  7. AndroidManifest.xml
  8. EmptyManifest.xml
  9. jarjar-rules.txt
  10. NOTICE
  11. OWNERS
  12. PREUPLOAD.cfg
  13. proguard.proguard
  14. README.md
  15. TEST_MAPPING
README.md

ExtServices module

Introduction

ExtServices is an updatable Mainline module that contains the logic used by Android framework components such as storage cache, autofill, textclassifier, package watchdog, notifications and notification ranking that runs continually. These are algorithms for framework, making the module updatable to introduce the new features or bug fixes more frequently with monthly release than a platform quarter release cycle.

Development (internal)

Before you start to develop on ExtServices, please read go/smart-os-extservices to get the guideline.

Other resources