Description: When user has two ICE contacts with different names but the same number, tapping second contact on emergency call screen shows first contact being called in Dialer. Repro Steps: Pre-Requisites: - Have two contacts with different names, but the same number (do not merge) with each set as an ICE contact - Have lockscreen with passcode enabled 1) Update a Flame to 20150424010200 2) Tap power button to turn off screen 3) Tap power button again and slide to unlock 4) Press Emergency Call button 5) Tap ICE Contacts button and select second ICE contact Actual: Call screen shows phone dialing out to first contact. Expected: Contact selected is shown as the one being called on call screen. Environmental Variables: Device: Flame 3.0 Build ID: 20150424010200 Gaia: 0c5e2ee1173f3c53379ef3cd10de714836258fe8 Gecko: 22a157f7feb7 Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b Version: 40.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0 Repro frequency: 3/3, 100% See attached: Youtube video clip: http://youtu.be/SngZty74cWE

Issue does reproduce on Flame 2.1 and 2.2 Making an emergency call to the second ice contact causes the callscreen to show me as calling first ice contact Device: Flame 2.1 Build ID: 20150424001201 Gaia: bbe983b4e8bebfec26b3726b79568a22d667223c Gecko: 6a68a038146a Gonk: ebad7da532429a6f5efadc00bf6ad8a41288a429 Version: 34.0 (2.1) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Device: Flame 2.2 Build ID: 20150424002507 Gaia: b838d0e7c163e66660dcb6e387d8339944a7a30e Gecko: 5fe76b26e55f Gonk: ebad7da532429a6f5efadc00bf6ad8a41288a429 Version: 37.0 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 ICE Contact functionality does not exist in 2.0, unable to test that branch

Not nominating to block on this since both contacts have the same number and it is just showing the wrong contact information. It is not a regression but this should be fixed.

Likely the same root cause as bug 1044028. Please reopen if you don't think it's the case.