Skip to content
Snippets Groups Projects
Select Git revision
  • android-7.1.2_r28_klist
  • master default protected
  • pie-cts-release
  • pie-vts-release
  • pie-cts-dev
  • oreo-mr1-iot-release
  • sdk-release
  • oreo-m6-s4-release
  • oreo-m4-s12-release
  • pie-release
  • pie-r2-release
  • pie-r2-s1-release
  • oreo-vts-release
  • oreo-cts-release
  • oreo-dev
  • oreo-mr1-dev
  • pie-gsi
  • pie-platform-release
  • pie-dev
  • oreo-cts-dev
  • android-o-mr1-iot-release-1.0.4
  • android-9.0.0_r8
  • android-9.0.0_r7
  • android-9.0.0_r6
  • android-9.0.0_r5
  • android-8.1.0_r46
  • android-8.1.0_r45
  • android-n-iot-release-smart-display-r2
  • android-vts-8.1_r5
  • android-cts-8.1_r8
  • android-cts-8.0_r12
  • android-cts-7.1_r20
  • android-cts-7.0_r24
  • android-o-mr1-iot-release-1.0.3
  • android-cts-9.0_r1
  • android-8.1.0_r43
  • android-8.1.0_r42
  • android-n-iot-release-smart-display
  • android-p-preview-5
  • android-9.0.0_r3
40 results

charger.te

Blame
    • Sandeep Patil's avatar
      c73d0022
      healthd: create SEPolicy for 'charger' and reduce healthd's scope · c73d0022
      Sandeep Patil authored
      
      healthd is being split into 'charger' and 'healthd' processes, that
      will never run together. 'charger' is to be run only in charge-only
      and recovery, while healthd runs with Android.
      
      While they both share much of battery monitoring code, they both now
      have reduced scope. E.g. 'charger', doesn't need to use binder anymore
      and healthd doesn't need to do charging ui animation. So, amend the
      SEPolicy for healthd to reduce it's scope and add a new one for charger.
      
      Test: Tested all modes {recovery, charger-only, android} with new policy
      
      Change-Id: If7f81875c605f7f07da4d23a313f308b9dde9ce8
      Signed-off-by: default avatarSandeep Patil <sspatil@google.com>
      c73d0022
      History
      healthd: create SEPolicy for 'charger' and reduce healthd's scope
      Sandeep Patil authored
      
      healthd is being split into 'charger' and 'healthd' processes, that
      will never run together. 'charger' is to be run only in charge-only
      and recovery, while healthd runs with Android.
      
      While they both share much of battery monitoring code, they both now
      have reduced scope. E.g. 'charger', doesn't need to use binder anymore
      and healthd doesn't need to do charging ui animation. So, amend the
      SEPolicy for healthd to reduce it's scope and add a new one for charger.
      
      Test: Tested all modes {recovery, charger-only, android} with new policy
      
      Change-Id: If7f81875c605f7f07da4d23a313f308b9dde9ce8
      Signed-off-by: default avatarSandeep Patil <sspatil@google.com>