Skip to content
Snippets Groups Projects
  1. Jun 29, 2018
  2. Jun 28, 2018
  3. Jun 27, 2018
  4. Jun 26, 2018
    • Jian Yu's avatar
      Fix issue that ro.telephony.default_network can't be read per slot · bbb439e7
      Jian Yu authored
      "ro.telephony.default_network" can define as comma-separated Sting per
      slot for multi SIM device. However, it cannot be read correctly due to
      it defined as Int in property_contexts file.
      
      Bug: 110626665
      Test: manual - Checked the ro.telephony.default_network can be read per
      slot for multi SIM device.
      Change-Id: I900620e46c819c14bf339751f00a1db1473fd45f
      bbb439e7
    • Yi Jin's avatar
      Allow incidentd to read kernel version · 880de35b
      Yi Jin authored
      Bug: 110230810
      Test: N/A
      Change-Id: Ide135dd5a8da05f0ea639bf03ce9612862108225
      880de35b
    • Samuel Ha's avatar
      Revert "Revert "Reduce the number of processes that can start adbd"" · 22f98197
      Samuel Ha authored
      This reverts commit b5dc6137.
      
      Reason for revert: Reverted incorrect change
      
      Change-Id: Ieafa3338e28ffeed40bcceb73486cffbfbd08b9d
      22f98197
    • Samuel Ha's avatar
      Revert "Reduce the number of processes that can start adbd" · b5dc6137
      Samuel Ha authored
      This reverts commit faebeaca.
      
      Reason for revert: broke the build
      
      Change-Id: I3d61ce011ad42c6ff0e9f122de3daa37e846407a
      b5dc6137
    • Luis Hector Chavez's avatar
      Reduce the number of processes that can start adbd · faebeaca
      Luis Hector Chavez authored
      This change makes it such that only init can start adbd directly. It
      also introduces new rules for ctl.{start,stop,restart} properties such
      that only usbd and recovery (and su, since it's permissive) can directly
      ask init to start adbd.
      
      Bug: 64720460
      Test: adbd still runs
      Test: /data/nativetest64/adbd_test/adbd_test
      Test: python system/core/adb/test_adb.py
      Test: "USB debugging" in System Settings still start/stop adbd
      Test: Recovery menu still make the device show as "recovery" in adb
            devices
      Test: "Apply update from ADB" in recovery menu still works
      Change-Id: Iafcda8aa44e85129afcc958036b472d856fa1192
      faebeaca
  5. Jun 25, 2018
    • Eino-Ville Talvala's avatar
      Make system property audio.camerasound.force a vendor-writable property, · 3ac71f8d
      Eino-Ville Talvala authored
      This property is read by the audio service in system server to toggle
      camera shutter sound enforcement on a device-specific basis.
      
      Test: Camera shutter sound enforcement works when audio.camerasound.force is set
      Bug: 110126976
      Change-Id: I2720d3c699c4712d1a328f59dde0b16bbf1016f3
      3ac71f8d
    • Neil Fuller's avatar
      Add label for time (zone) system properties · b794ad0f
      Neil Fuller authored
      This adds a label for system properties that will affect system-wide
      time / time detection logic.
      
      The first example will be something like:
      persist.time.detection_impl_version
      
      Bug: 78217059
      Test: build
      Change-Id: I46044f1e28170760001da9acf2496a1e3037e48a
      b794ad0f
  6. Jun 22, 2018
    • Treehugger Robot's avatar
      0474b119
    • Treehugger Robot's avatar
      4b9a3128
    • Peiyong Lin's avatar
      Allow SurfaceFlinger to use Power HAL. · 02be5975
      Peiyong Lin authored
      When we have wide color gamut content, SurfaceFlinger might want to send a
      PowerHint through Power Hal to boost GPU to higher frequency, to make sure GPU
      composition can finish in time.
      
      BUG: 110112323
      Test: adb shell cat /sys/class/kgsl/kgsl-3d0/devfreq/cur_freq
      Change-Id: If60c13aedc4ff84eaefd3430794dc15a478c5a73
      02be5975
    • Dario Freni's avatar
      512e1c4d
    • Jeff Vander Stoep's avatar
      Update socket ioctl restrictions · 0597ade1
      Jeff Vander Stoep authored
      Grant access to icmp_socket to netdomain. This was previously
      labeled as rawip_socket which apps are allowed to use. Neverallow
      all other new socket types for apps.
      
      Kernels versions > 4.9 redefine ICMP sockets from rawip_socket
      to icmp_socket. To pass neverallow tests, we need to define
      which IOCTLs are allowed (and disallowed).
      
      Note that this does not change behavior on devices with
      kernel versions <=4.9. However, it is necessary (although not
      sufficient) to pass CTS on kernel version 4.14.
      
      Bug: 110520616
      Test: Grant icmp_socket in net.te and build.
      Change-Id: I5c7cb6867d1a4cd1554a8da0d55daa8e06daf803
      0597ade1
  7. Jun 21, 2018
  8. Jun 19, 2018
  9. Jun 15, 2018
  10. Jun 14, 2018
  11. Jun 13, 2018
    • Treehugger Robot's avatar
      Merge changes from topic "sharedlib_in_recovery" · b6639b0f
      Treehugger Robot authored
      * changes:
        init is a dynamic executable
        adbd is allowed to execute shell in recovery mode
      b6639b0f
    • Jiyong Park's avatar
      init is a dynamic executable · 90b21ee4
      Jiyong Park authored
      init is now a dynamic executable. So it has to be able to execute the
      dynamic linker (/system/bin/linker) and shared libraries (e.g.,
      /system/lib/libc.so). Furthermore, when in recovery mode, the files are
      all labeled as rootfs - because the recovery ramdisk does not support
      xattr, so files of type rootfs is allowed to be executed.
      
      Do the same for kernel and ueventd because they are executing the init
      executable.
      
      Bug: 63673171
      Test: `adb reboot recovery; adb devices` shows the device ID
      Change-Id: Ic6225bb8e129a00771e1455e259ff28241b70396
      90b21ee4
    • padarshr's avatar
      Add ueventd to mnt_vendor_file neverallow exemption list · 44ae7c2c
      padarshr authored
      Legacy hardware and code still depends on the ueventd helpers to
      locate the firmware supported files which are on new mount path
      labeled with mnt_vendot_file. For ueventd helper to work we need dir search
      and read permission on this new label so moving ueventd to exempted list.
      
      Already ueventd has the vendor_file_type read access.
      
      Bug:110083808
      
      Change-Id: Ia15cc39ecef9e29b4f1f684efdddbeb78b427988
      44ae7c2c
  12. Jun 12, 2018
  13. Jun 11, 2018
    • Steven Moreland's avatar
      Make hal_allocator use hal_attribute_hwservice. · 90996388
      Steven Moreland authored
      If you can get or serve the hal allocator interface,
      you should be a hal_allocator_client or
      hal_allocator_server.
      
      Bug: 80319537
      Test: boot aosp_walleye and (sanity) take photos
      Change-Id: Iea14c67c4aa56df7a74ebdb17e99b78b1d3aa105
      90996388
    • Neil Fuller's avatar
      Allow telephony to call system service · 60d79e48
      Neil Fuller authored
      The timedetector_service will be called from the
      telephony process
      
      Bug: 78217059
      Test: build / local testing with a client
      Change-Id: I25dfa4daabaa80e6b5e697ad1b1e2f7f72377702
      60d79e48
    • Mark Salyzyn's avatar
      persist.sys.boot.reason is cleared once read by bootstat · a1bce779
      Mark Salyzyn authored
      To ensure a surprise reboot does not take the last boot reason on
      face value especially if coming from more than one boot sessions ago.
      We shift and clear the value from persist.sys.boot.reason to
      sys.boot.reason.last and establish a correct last reboot reason in
      the canonical sys.boot.reason property.  As a result, the power
      manager should read the canonical sys.boot.reason for a definitive
      result rather than relying on the possibly incorrect values in the
      persistent storage.  sys.boot.reason should be a core property as
      it represents the canonical boot reason API.
      
      Test: compile
      Bug: 86671991
      Bug: 63736262
      Change-Id: If3742c487d6c0ab69c464f056bf48c786b66a945
      a1bce779
  14. Jun 08, 2018
    • Jiyong Park's avatar
      adbd is allowed to execute shell in recovery mode · bacf3648
      Jiyong Park authored
      The shell is now available directly in the recovery ramdisk. We no
      longer need to mount system.img to /system as the recovery ramdisk is
      self-contained. However, there is a problem that every file in the
      ramdisk is labeled as rootfs because the ramdisk does not support xattr.
      
      This CL adds several recovery-only rules that are required to make the
      recovery ramdisk self-contained. Most importantly, adbd is allowed to
      domain_trans to shell. Also shell is allowe to execute files of type
      rootfs. Finally, the recovery is allowed to mount on tmpfs since it now
      mounts system.img to /mnt/system.
      
      Bug: 63673171
      Test: `adb reboot recovery; adb devices` shows the device ID
      Test: `adb root && adb shell` and then
      $ lsof -p `pidof adbd` shows that libm.so, libc.so, etc. are loaded from
      the /lib directory.
      
      Change-Id: If21b069aee63541344a5ca8939fb9a46ffef4d3e
      bacf3648
Loading