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

Commit e3a056f2 authored by Hyundo Moon's avatar Hyundo Moon
Browse files

[Metrics] Cast the parameter for avoiding ambiguity in a new atom 

When adding a new atom BluetoothContentProfileErrorReported, it
introduces an ambiguity when using stats_write native method.
This CL fixes the issue.

Bug: 294797589
Test: m -j
Merged-In: Iaed9bf788e5e9a04cd866e302e73ea21bdd8f769
Change-Id: Iaed9bf788e5e9a04cd866e302e73ea21bdd8f769
parent 8e555b6a

system/gd/os/android/metrics.cc

+6 −1
Original line number Diff line number Diff line
@@ -494,7 +494,12 @@ void LogMetricBluetoothRemoteSupportedFeatures( 
  if (!address.IsEmpty()) {

    metric_id = MetricIdManager::GetInstance().AllocateId(address);

  }

  int ret = stats_write(BLUETOOTH_REMOTE_SUPPORTED_FEATURES_REPORTED, metric_id, page, features, connection_handle);

  int ret = stats_write(

      BLUETOOTH_REMOTE_SUPPORTED_FEATURES_REPORTED,

      metric_id,

      page,

      static_cast<int64_t>(features),

      connection_handle);

  if (ret < 0) {

    LOG_WARN(

        "Failed for LogMetricBluetoothRemoteSupportedFeatures, "