[Bug] Call out of recent call list can switch to wrong number (reproducable)

asked 2014-03-16 11:40:30 +0300

CLR64 gravatar image

updated 2014-07-28 10:03:38 +0300

jiit gravatar image

I yesterday stumbled over a really silly bug that can cause you much trouble. If you have some contacts with same name in your contact list (out of mistake or an additional old phone-number of a friend for example like in my case) a call out of the recent-call-list does not make sure it uses the phone-number that called you. It seems to pick the contact name and searches in the contact list for the number. This took the wrong number for me.

This is a serious problem also that it shouldn't affect many.

Steps to reproduce:

  1. Add two contacts with same name and different numbers you have both access to.
  2. Call from one number. Hang up if your jolla got the call.
  3. Answer call from recent-call-list. Or just look to which contact the entry got linked - Im not sure if this is enough.
  4. If the outgoing call get sent to the wrong number, thats the problem, otherwise start from #2 with the other phone-number.

Update 2014-03-17:

With several numbers of one contact and with deactivated fast-call out of recent-call-list there is no chance to see which phone-number called you. The phone number has to be highlighted and on top of the list or the only entry. If fast-call is activated the right phone-number get called.

I'm not quiet sure if the right phone-number also would get called for the initial problem I described if you have fast-call activated and the bug only got introduced for the contact-list linking. I guess it would.

edit retag flag offensive close delete



I think the problem exists with only one contact and several phone numbers for this contact: recent call list seems to be tied to the contact, not the phone number, so you have to explicitely choose the right number, otherwise it will take the first one. Which is bad.

alci ( 2014-03-17 13:03:29 +0300 )edit

If you are right the problem is much worse because that is a configuration many uses.

EDIT: I updated the question. You are right I tested it. But the bug wo'nt happen with fast-call. This problem has to get fixed too because you maybe simply select the first one and/or don't know which one called you. But it is a design problem and not really a bug as the one I described in the question. In the case of a wrong linking with only one number you don't read which number it is before you call.

CLR64 ( 2014-03-17 13:22:40 +0300 )edit

One contact -> many numbers behaviour if the bug, when in design. With quick call activated "recent contact" call in Phone app dials recent number of the contact. But this phone number is not shown together with name during the dialling and you are not sure which number you call. "Recent" list in People app always opens the contact and you shall select the number manually. That could work if you have simple way to put most used numbers on first place. I'd prefer same (#) behaviour in both apps

SergeiStPete ( 2014-03-22 00:55:39 +0300 )edit

very annoying, really. I Have a lot of contacts with private, work and mobile numbers. It's also not possible to see which number is being used while the phone is ringing.

casanunda ( 2014-03-30 21:43:18 +0300 )edit