Skip to content
Snippets Groups Projects
  1. Jan 30, 2019
  2. Jan 29, 2019
    • Shuzhen Wang's avatar
      Revert "Cameraserver: Allow cameraserver to access /data/misc/cameraserver" · 6b4caaa3
      Shuzhen Wang authored
      This reverts commit 4e1497c7.
      
      Reason for revert: Write temporary file to in-memory tmpfs instead
      
      Test: testHeic CTS test
      Bug: 123526741
      Change-Id: Ifa7f5a0b50c46ee3e1a5695595233b17adc99222
      6b4caaa3
    • Mathieu Chartier's avatar
    • Treehugger Robot's avatar
      Merge "Fix perfetto CTS test" · 13fdfa44
      Treehugger Robot authored
      13fdfa44
    • Mathieu Chartier's avatar
      Rename runtime -> runtime_native property namespace · 669cef88
      Mathieu Chartier authored
      The convention for native properties is to use _native suffix.
      
      Bug: 123524494
      Bug: 120794191
      Test: set a property and ensure it can be read in AndroidRuntime.cpp
      
      Change-Id: I69feab9be78f24d812b8f953d3ec06a5d8d18f15
      669cef88
    • Roland Levillain's avatar
      Introduce a `postinstall_apex_mnt_dir` label for `/postinstall/apex`. · a42ebf41
      Roland Levillain authored
      Directory `/postinstall/apex` is used as a mount point for a tmpfs
      filesystem during A/B OTA updates. APEX packages from the new system
      partition are mounted ("activated") in subdirectories of
      `/postinstall/apex`, so that they are available when `otapreopt` is
      running.
      
      Directory `/postinstall/apex` used to be of type `tmpfs` for SELinux
      purposes. The new `postinstall_apex_mnt_dir` label is more
      restrictive, and tightens permissions granted to `otapreopt_chroot`,
      `otapreopt` (running as `postinstall_dexopt`), and `dex2oat`,
      regarding the apexd logic recently added to `otapreopt_chroot`.
      
      Test: A/B OTA update test (asit/dexoptota/self_full).
      Bug: 113373927
      Bug: 120796514
      Change-Id: I03f0b0433d9c066a0c607f864d60ca62fc68c990
      a42ebf41
    • Jiyong Park's avatar
      Label APEX files correctly when TARGET_FLATTEN_APEX=true · e7fab185
      Jiyong Park authored
      When TARGET_FLATTEN_APEX=true, APEX files are not packaged in *.apex
      files but flattened to the system partition under /system/apex/<name>
      directories. There was a bug that those flattened files are not labeled
      because the per-APEX file_contexts were applied only when building
      *.apex. Fixing this by converting the file_contexts files so that
      /system/apex/<name> path is prepended and applying the generated
      file_contexts file for system.img when TARGET_FLATTEN_APEX=true.
      
      Bug: 123314817
      Test: TARGET_FLATTEN_APEX=true m
      ls -alZ /system/apex/*/* shows that the files are correctly labeled
      
      Change-Id: Ia82740a1da0083d5bcfd71354a6d374d2a918342
      e7fab185
    • Mathieu Chartier's avatar
  3. Jan 28, 2019
  4. Jan 27, 2019
  5. Jan 26, 2019
  6. Jan 25, 2019
Loading