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

Commit 5e1db1e6 authored by Chinmay Dhodapkar's avatar Chinmay Dhodapkar
Browse files

remove gating for statsd logging of anomaly atoms 

Make sure anomaly atoms are always logged to statsd. The intent
sent to oem can still remain gated by a platform experiments
flag

Fixes: 268376781
Test: manual
Change-Id: I34fbc2b152e56bcea777bbfba2f25468a82e9dca
parent 2fb65e66

telephony/java/android/telephony/AnomalyReporter.java

+9 −8
Original line number Diff line number Diff line
@@ -110,8 +110,15 @@ public final class AnomalyReporter { 
            return;

        }



        // Don't report if the server-side flag isn't loaded, as it implies other anomaly report

        // related config hasn't loaded.

        //always write atoms to statsd

        TelephonyStatsLog.write(

                TELEPHONY_ANOMALY_DETECTED,

                carrierId,

                eventId.getLeastSignificantBits(),

                eventId.getMostSignificantBits());



        // Don't report via Intent if the server-side flag isn't loaded, as it implies other anomaly

        // report related config hasn't loaded.

        try {

            boolean isAnomalyReportEnabledFromServer = DeviceConfig.getBoolean(

                    DeviceConfig.NAMESPACE_TELEPHONY, KEY_IS_TELEPHONY_ANOMALY_REPORT_ENABLED,
@@ -122,12 +129,6 @@ public final class AnomalyReporter { 
            return;

        }



        TelephonyStatsLog.write(

                TELEPHONY_ANOMALY_DETECTED,

                carrierId,

                eventId.getLeastSignificantBits(),

                eventId.getMostSignificantBits());



        // If this event has already occurred, skip sending intents for it; regardless log its

        // invocation here.

        Integer count = sEvents.containsKey(eventId) ? sEvents.get(eventId) + 1 : 1;