Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 42b79ddd authored by Prashanth Swaminathan's avatar Prashanth Swaminathan Committed by Hyundo Moon
Browse files

Lower potentially noisy alarm logs to debug 

In a failure path where alarms are getting scheduled repeatedly without
data to read, printing in 'info' can add a lot of noise to the logs.
Reduce these to 'debug' so that we can continue to get information when
this happens but also allows logd to suppress.

Bug: 377601619
Flag: EXEMPT, log change
Test: m -j;
Test: Verified logs print in 'debug' only.
Change-Id: Ie7167014c32b7e39db045882eaefd88eadfedbaa
parent 61a37427

system/gd/os/linux_generic/alarm.cc

+2 −2
Original line number Diff line number Diff line
@@ -86,9 +86,9 @@ void Alarm::on_fire() { 
  lock.unlock();



  if (com::android::bluetooth::flags::non_wake_alarm_for_rpa_rotation() && bytes_read == -1) {

    log::info("No data to read.");

    log::debug("No data to read.");

    if (errno == EAGAIN || errno == EWOULDBLOCK) {

      log::info("Alarm is already canceled or rescheduled.");

      log::debug("Alarm is already canceled or rescheduled.");

      return;

    }

  }