Bug: Inbound calls don't display Contact Name
All my inbound calls show a number (instead of contact name) despite having that person in my address book. I believe the reason is that the Phone app is doing a direct string compare instead of considering the + country code.
Address Book Entry: +354 666 0000
Inbound Call: 666 0000
This seems like a pretty easy fix, and is pretty crucial to the user experience of knowing who is calling your phone
Did you see this: https://together.jolla.com/question/8887/contact-name-doesnt-appear-when-receiving-a-call/? I'm not sure if this is a duplicate, as the linked question is kind of Lebanon-specific. :)
Anyway, in that question there is discussion about phone number matching: 8 digits are compared, and having only 7 digits (like in your example) causes the number not to be identified. It could be the same issue, though if it happens with all your contacts, maybe not.
I don't think it's about having the country code saved in your contacts or not, both work for me.
ssahla ( 2014-02-17 21:51:13 +0200 )editNo, I haven't seen this. I wrote my previous post to quickly. Yes, it's possible if the SN is and NDC together shorter than 8 digit. :( I don't remember exactly for 3GPP or ETSI CLI standard, should be checked there what is sent to mobile. If possible to figure out the number format, then the CLI should be modified to NDC+SN format, the length calculated and compare the NDC+SN CLI in the calculated length. But it is just theory, the standard should be checked first.
jliebe ( 2014-02-17 22:23:01 +0200 )edit@jliebe sorry, I'm not sure what the following acronyms mean "SN, NDC, 3GPP, ETSI" but I assume they are either segments of phone numbers, or mobile carrier metadata. I'm located in Iceland, also not sure if the carriers here are particularly weird in terms of metadata.
In any case, this user experience really shouldn't be happening, it makes the most basic feature (phone) a pain to use. It does not happen in iOS or Android with the exact same contacts I'm experiencing this Jolla bug in.
bnvk ( 2014-02-18 02:22:21 +0200 )editThis is still happening even after the most recent OS update to 1.0.4.20, ugh!
bnvk ( 2014-03-26 01:53:33 +0200 )edit