Shintaro Kawamura | 635e5b4 | 2025-03-06 16:21:12 +0900 | [diff] [blame^] | 1 | on property:sys.boot_completed=1 |
| 2 | # When mmd package is not included in the image, we need to initialize |
| 3 | # `mmd.enabled_aconfig` sysprop instead of `mmd --set-property`. |
| 4 | # |
| 5 | # This is because of the consideration for devices in Trunkfood and Nextfood |
| 6 | # under mmd being launched via AConfig flag. The devices set up zram with |
| 7 | # mmd if `mmd_enabled` AConfig flag is enabled, otherwise set up zram with |
| 8 | # swapon_all init command. Since AConfig does not support any init script |
| 9 | # integration, we use `mmd.enabled_aconfig` copied by `mmd --set-property` |
| 10 | # instead of AConfig flag itself and we need mmd.enabled_aconfig to be empty |
| 11 | # by default, to let swapon_all command wait until aconfig flag value is |
| 12 | # loaded to the system property. |
| 13 | # Devices in Trunkfood and Nextfood needs to execute swapon_all command on |
| 14 | # `on property:mmd.enabled_aconfig=*` trigger. So initializing |
| 15 | # `mmd.enabled_aconfig` sysprop is required on images without mmd package. |
| 16 | # |
| 17 | # Note that this init file must not be in the image if mmd is built into the |
| 18 | # image. |
| 19 | setprop mmd.enabled_aconfig false |