commit 1e3118b2154b477481c2f100d1ce1c45f99c921c
author roldenburg <roldenburg@google.com> Wed Aug 30 14:31:21 2017 -0700
committer Eric Erfanian <erfanian@google.com> Wed Aug 30 18:54:36 2017 -0700
tree 36e966303f70f62591e770be029eef9bc0d6f5fa
parent 03c62631ff02b8fba0c65673b875f1180c4a670c

Do not duplicate call history data in call details screen

If we store the merged values we get the duplication. Instead, we send the merged values to the adapter but store only the call info in the Activity.

Bug: 65207281
Test: manual
PiperOrigin-RevId: 167050403
Change-Id: I30262cfeb4946163d8297e3b702906d676d4a05b

java/com/android/dialer/calldetails/CallDetailsActivity.java

diff --git a/java/com/android/dialer/calldetails/CallDetailsActivity.java b/java/com/android/dialer/calldetails/CallDetailsActivity.java
index 385b4d1..569aaa5 100644
--- a/java/com/android/dialer/calldetails/CallDetailsActivity.java
+++ b/java/com/android/dialer/calldetails/CallDetailsActivity.java
@@ -182,11 +182,10 @@
     Map<CallDetailsEntry, List<HistoryResult>> mappedResults =
         getAllHistoricalData(contact.getNumber(), entries);
 
-    entries =
+    adapter.updateCallDetailsEntries(
         generateAndMapNewCallDetailsEntriesHistoryResults(
-            contact.getNumber(), entries, mappedResults);
-
-    adapter.updateCallDetailsEntries(entries.getEntriesList());
+                contact.getNumber(), entries, mappedResults)
+            .getEntriesList());
   }
 
   @NonNull