diff options
| author | 2023-04-19 15:10:06 +0100 | |
|---|---|---|
| committer | 2023-05-16 11:20:52 +0000 | |
| commit | 9939267f44f997972a05d9cb9c12d97b73596bd8 (patch) | |
| tree | 7026e88bf0a2d986c0e8e876b96f2048a597fe15 /compiler/optimizing/code_generator.h | |
| parent | 94d58fe6c99f83037e3b1587bf90c84c154f045a (diff) | |
Propagate useartservice setting from experiment flag to global flag.
Only propagate it if it turns off ART Service - if OEMs have disabled
it with dalvik.vm.useartservice then we shouldn't enable it.
Introduce a new art_boot binary to do it, which is only run at boot
through a oneshot service.
We cannot use setprop commands directly in the init script, because
non-vendor APEXes are prohibited from using `on` actions (b/278862348).
Test: boot
-> Check that dalvik.vm.useartservice is not false
adb root
adb shell setprop persist.device_config.runtime_native_boot.useartservice false
-> Check that dalvik.vm.useartservice is not false
adb reboot
-> Check that dalvik.vm.useartservice is false
on udc-dev
Test: Same as above, but with an unbundled ART module build installed
on git_sc-release and git_tm-release.
Test: boot
-> Check that dalvik.vm.useartservice is unset
adb root
adb shell setprop persist.device_config.runtime_native_boot.useartservice true
-> Check that dalvik.vm.useartservice is unset
adb reboot
-> Check that dalvik.vm.useartservice is unset
on udc-dev with dalvik.vm.useartservice unset
Bug: 272056722
Change-Id: Ifc552ed924818d7363aef822cd3060f7adfc92b6
(cherry picked from commit 4cdcab58b438a91c91cd5b09235c703251c6e328)
Merged-In: Ifc552ed924818d7363aef822cd3060f7adfc92b6
Diffstat (limited to 'compiler/optimizing/code_generator.h')
0 files changed, 0 insertions, 0 deletions