Skip to content
Snippets Groups Projects
  1. Sep 27, 2017
  2. Sep 26, 2017
  3. Sep 24, 2017
  4. Sep 23, 2017
  5. Sep 21, 2017
  6. Sep 20, 2017
  7. Sep 19, 2017
  8. Sep 18, 2017
  9. Sep 16, 2017
  10. Sep 15, 2017
    • Bill Yi's avatar
      Merge remote-tracking branch 'aosp/oreo-cts-dev' into HEAD - DO NOT MERGE · 0d4b5539
      Bill Yi authored
      am: c8ef107a  -s ours
      
      Change-Id: I781386a8ae37105a5f8c494b0471f6625a84cf0b
      0d4b5539
    • Tomasz Wasilczyk's avatar
      resolve merge conflicts of c998f319 to stage-aosp-master · 6ba6705c
      Tomasz Wasilczyk authored
      Test: after cherry-pick - it builds
      Merged-In: I57c0150a52c13f1ce21f9ae2147e3814aad0fb7e
      Change-Id: I7da8160a95e09946d283bd849628bd5392410353
      6ba6705c
    • Tomasz Wasilczyk's avatar
      Branch out Broadcast Radio 1.2 HAL. · a9159dd1
      Tomasz Wasilczyk authored
      Bug: 62945293
      Test: instrumentation, VTS
      Change-Id: I7e896b64bf0ee907af21d08f6b78561fadc7f0e3
      a9159dd1
    • Bill Yi's avatar
      Merge remote-tracking branch 'aosp/oreo-cts-dev' into HEAD - DO NOT MERGE · c8ef107a
      Bill Yi authored
      Change-Id: I88e2887b0691ce3c5018578556abf7c420fe5a1b
      c8ef107a
    • Tomasz Wasilczyk's avatar
    • Tomasz Wasilczyk's avatar
      Move Broadcast Radio HAL to a separate binary. · 26ff5eb6
      Tomasz Wasilczyk authored
      Bug: 63600413
      Test: VTS, instrumentation, audit2allow
      Test: after cherry-pick - it builds
      Change-Id: I57c0150a52c13f1ce21f9ae2147e3814aad0fb7e
      (cherry picked from commit 567b947d)
      26ff5eb6
    • Tri Vo's avatar
      Merge "Explicitly label logd's dependencies in /proc." · 82fe6916
      Tri Vo authored
      am: cfdbaf33
      
      Change-Id: I2206c2e99dbfc3c1efd5beee3b73c744187f7c32
      82fe6916
    • Tri Vo's avatar
      cfdbaf33
    • Mark Salyzyn's avatar
      bootstat: lock down *_boot_reason_prop · 67ec37a3
      Mark Salyzyn authored
      am: 397b07b3
      
      Change-Id: I59221e03d3cdbbaa4fb416605ba66e9243afb5b9
      67ec37a3
    • Mark Salyzyn's avatar
      bootstat: lock down *_boot_reason_prop · 397b07b3
      Mark Salyzyn authored
      Add series of neverallow rules to restrict components from reading or
      writing bootloader_boot_reason_prop, system_boot_reason_prop and
      last_boot_reason_prop to trusted set of domains.
      
      The policy is that bootloader_boot_reason_prop (ro.boot.bootreason)
      has a compliance issue due to the sheer momentum of near unparseable
      content as filed by the wide variety (8000 different devices at last
      count) bootloaders and is only to be accessible to a series of
      responsible system components.  It can be inaccurate as it provides
      no means to evaluate a shutdown, likely reporting "cold" (from
      initial power up) or the more generic "reboot".
      
      The last_boot_reason_prop (persist.sys.boot.reason) contains
      inaccurate information as it is only valid after a controlled reboot
      or shutdown.  The value can linger around after less controlled
      scenarios.  Since the information could be false, we do not want to
      support it as an open API, so we again block access to only
      responsible components.
      
      The system_boot_reason_prop (sys.boot.reason) is a canonical boot
      reason that takes into account parsing bootloader_boot_reason_prop,
      boot_loader_boot_reason_prop and other system and HAL generated hints
      to determine a parseable and most accurate reason for the last time
      the system was rebooted.
      
      For now the policy for system_boot_reason_prop is to audit users of
      the API, and on a need to know basis via device additions to the
      selinux rules.  If vendors need their components to access the boot
      reason, they need to comply first with CTS tests and spirit with
      regards to controlled reboot messaging and in turn read the
      system_boot_reason_prop for the canonical information.  It will
      contain validated content derived from bootloader_boot_reason_prop
      in the scenarios that count.
      
      The controlled reboot APIs include:
      - android_reboot(ANDROID_RB_<TYPE>, int flag, const char* reason)
      - PowerManagerService.lowLevelShutdown(String reason);
      - PowerManagerService.lowLevelReboot(String reason);
      - ShutdownThread.shutdown(context, String reason, boolean confirm);
      - ShutdownThread.reboot(context, String reason, boolean confirm);
      - PowerManager.shutdown(boolean confirm, String reason, boolean wait);
      - PowerManager.reboot(String reason);
      
      Any others (including the direct linux reboot syscall) create
      problems for generating an accurate canonical boot reason.
      
      Test: compile
      Bug: 63736262
      Bug: 65686279
      Change-Id: I2e5e55bbea1c383c06472eb2989237cfeb852030
      397b07b3
    • Peng Xu's avatar
      Merge changes Id4ac3552,I2068f6f4 · 5d06d481
      Peng Xu authored
      am: 48284512
      
      Change-Id: I3096c5d0871872de5484f862f9f9878d6a8fce13
      5d06d481
    • Peng Xu's avatar
      Allow sensor to use gralloc handle and access ion device · e1ff551f
      Peng Xu authored
      am: d1a9a2f4  -s ours
      
      Change-Id: Ifa7aee2d178fe4187f59e4a5b35e2643f0e69459
      e1ff551f
Loading