N9 Called ID and phonebook lookup problem
 

Hi All,

I have discovered a weird issue with my N9 today.

I have in phonebook two different entries as follows:

1] Name : Tom Klaus
CellNo: +811234 333333

2] Name : Rita Klaus
CellNo: +818772 333333

So, if you notice, the last 6 digits are same for both their phone numbers.

Now, when I got an incoming call from "Tom Klaus" above, it only showed me the phone number on the call screen. Same when I got an SMS from him.

When I go to the messages thread , it shows up there that there are 2 contacts matching with this number!!!!!!!!

So it looks to me that N9 is matching only the last 5-6 digits of the incoming call/sms !! This is really weird!!

I was wondering if anyone here knows about this issue.

PS: Ofcourse the names and phone numers above are made up!! But they reflect how they really are!

Edit: Corrected some typos

Re: N9 Called ID and phonebook lookup problem
 

I had the same problem.
When I called one of my friends, his name apeared on the screen, but not in call log, just his number.
Then my girlfriends number appered on SMS, not her name.

And that's fixes after I flashed my phone with 1.1.1.

Re: N9 Called ID and phonebook lookup problem
 

where do i get 1.1.1 ? I am still on 1.1

Re: N9 Called ID and phonebook lookup problem
 

From Navifirm...

Re: N9 Called ID and phonebook lookup problem
 

oh ok..but why is it not showing up in updates..I'm curious

Re: N9 Called ID and phonebook lookup problem
 

It's a MEA update, you'll not get it through NSU or OTA, get it from Navifirm and flash the phone.
Do some search on google how to flash Nokia N9.

Re: N9 Called ID and phonebook lookup problem
 

I think I recall reading that there's some minor fixes in 1.1.1...
Aside from Arabic support, which is the main difference from 1.1.
I could be wrong though, you could always re-flash with a 1.1 image 1st.

This issue was definitely discussed in the messaging thread, no more than several pages back IIRC.
So you could try reviewing it to see what abustany (Nokia dev) has said.

Re: N9 Called ID and phonebook lookup problem
 

^^
I went through the whole thread "N9/N950 Contacts/IM - Get help & give feedback here" and did not find something similar by the Nokia dev abustany. I also searched by his username. Anyways, I will just post my initial post in the other thread too so that the Nokia dev knows about his. (Heck he may already know!!)

Re: N9 Called ID and phonebook lookup problem
 

Must've been something similar in nature.
Still worthwhile sharing it with him...
You won't get a response for a while this time of yr.

Re: N9 Called ID and phonebook lookup problem
 

Yea I guess.. its holiday time :D .. Happy Holidays and Merry Christmas to all :D

Re: N9 Called ID and phonebook lookup problem
 

Thanks mate. Good luck.

Re: N9 Called ID and phonebook lookup problem
 

i can confirm that flashing to pr 1.1.1 fixes this bug.

Re: N9 Called ID and phonebook lookup problem
 

As far as I know the last 7 digits are used for matching, not the last 6... But that setting is per country. We had a better code for number matching, but management didn't give the approval to release it :-/

Re: N9 Called ID and phonebook lookup problem
 

Thats sad! I wish there were a fix for this .

Re: N9 Called ID and phonebook lookup problem
 

they should release the fix as a mini update for those not getting 1.1.1

any downsides to flashing pr 1.1.1 if not from that area?

Re: N9 Called ID and phonebook lookup problem
 

I couldn't agree more. Why don't they release the mini update fix for this issue? Unless PR 1.2 is just around the corner (which I highly doubt)....

Re: N9 Called ID and phonebook lookup problem
 

@abustany.

Why not release a minor update that includes fixes/improvements that came with MEA's PR1.1.1?*
This should be relatively trivial to do, & would allow you take a bit longer with 1.2.
And thereby ensure it's a very broad "feature" release (less emphasis on bugs/stability/perf/security).

*plus some extra fixes for the most critical/nasty bugs still in 1.1 & 1.1.1.

Re: N9 Called ID and phonebook lookup problem
 

i've used pr 1.1.1 since 5 days and so far there are no issues with it even though i'm not from that area. pr 1.1.1 also has upcoming calendars in the feed screen.

i highly recommend installing it as its more stable in the sense the occassional lags of pr 1.1 are not there. it could be a placebo effect but overall i think its a good idea to install it.

edit: the n9 auto-detects your region and language if your sim card is inserted during flashing so you shouldn't be seeing any MEA inputs or languages. Try not to restore settings after flashing as i lost the ability to use devel-su. Had to re-flash to get the function back. It could be as i'd developer mode on before the flash.

Re: N9 Called ID and phonebook lookup problem
 

You should come across some nasty bugs in 1.1.1 that it shares w/1.1.
Tis just matter of time, but it also depends on exactly how you use it.

Re: N9 Called ID and phonebook lookup problem
 

There are no bugs...

Re: N9 Called ID and phonebook lookup problem
 

What are you talking about, of course there are...
Just because you've come across none, doesn't mean they don't exist.
Read all the threads & the tracker, & that becomes very evident.
1.1.1 is not magically immune to many of the same issues.
It'll have many of the flaws 1.1 has....
They just haven't been revealed, as not as many people are using it.

Re: N9 Called ID and phonebook lookup problem
 

I can't say "there are bugs" if I don't see them.

Re: N9 Called ID and phonebook lookup problem
 

Well, you can say I haven't come across any yet.
"There are no bugs" = you claiming there are none *period*.
Which is simply not correct....
Anyway this is all off-topic, so I'll shut-it now...

Re: N9 Called ID and phonebook lookup problem
 

Hi,

I am using an N9 64GB in India. I am facing exactly the same problem. I am running PR1.3 (I flashed the Singapore CTR image using NaviFirm).

How many numbers are being used to match the call ID for India ? Any information would be really helpful. I assume this problem was never really solved.