Route all existing screen view events through the Logger
* The logger is responsible for sending it to its logging
implementation, and also to AnalyicsUtil.
* Standardize logic for creating a tagged version of a screen
name
Bug: 23164804
Change-Id: I9b817fba5359f78340f2d9fdba54af9ea73cdb37
diff --git a/src/com/android/dialer/DialtactsActivity.java b/src/com/android/dialer/DialtactsActivity.java
index dabe590..4fa4bc2 100644
--- a/src/com/android/dialer/DialtactsActivity.java
+++ b/src/com/android/dialer/DialtactsActivity.java
@@ -81,6 +81,7 @@
import com.android.dialer.list.SearchFragment;
import com.android.dialer.list.SmartDialSearchFragment;
import com.android.dialer.list.SpeedDialFragment;
+import com.android.dialer.logging.Logger;
import com.android.dialer.settings.DialerSettingsActivity;
import com.android.dialer.util.DialerUtils;
import com.android.dialer.util.IntentUtil;
@@ -526,7 +527,7 @@
// This is only called when the activity goes from resumed -> paused -> resumed, so it
// will not cause an extra view to be sent out on rotation
if (mIsDialpadShown) {
- AnalyticsUtil.sendScreenView(mDialpadFragment, this);
+ Logger.logFragmentView(mDialpadFragment);
}
mIsRestarting = false;
}
@@ -741,7 +742,9 @@
}
mDialpadFragment.setAnimate(animate);
- AnalyticsUtil.sendScreenView(mDialpadFragment);
+ // logScreenView is used here explicitly to provide the activity as the DialpadFragment
+ // might not have been attached yet.
+ Logger.logScreenView(DialpadFragment.class.getSimpleName(), this, null);
ft.commit();
if (animate) {