Redefining the PC

Why Microsoft's Surface phone could be MUCH more than a mere 'phone'

Surface Pwn 5

Surface Pro 5, Project NEON details leaked on LinkedIn?

XP-YESSSSSSS

Dell's already awesome XPS 15 gets even better in 2017

Surface table meets Windows 10

Yes, we did put Windows 10 on the original Surface table ... and it rocks

Cream o' the crop

Before buying a Microsoft laptop, check out our pick for the absolute best

Simple and secure, just the way I like it

We think Windows 10 Cloud is a great idea, here's why

uber micro

Halo Wars 2 has something for everyone. Here's our full review.

Oldie but goldie

We reviewed Microsoft's decade-old Surface table

Creators Update comin' at ya

These are the coolest new features in the next big Xbox One update (video)

Buyer's guide

The Razer Blade 14 is the best laptop Razer has to offer

Windows 10 app gems

10 terrific Windows 10 apps you should be using

Tower of power

Here's what we think of Dell's XPS Tower Special Edition

Quite a deal

Grab the complete C# coding bootcamp for $41!

Your go-to laptop guide

Introducing our ultimate laptop buyer's guide

Listen here

Attn Android and iPhone users: What you need to know about Windows phone

Old is new?

The original Surface Pro still holds its own in the 2-in-1 world

Xbox Greenlight?

No, internet, Microsoft isn't opening Xbox to all UWP games

Falling in love

HP Envy 34 review: An ultrawide curved all-in-one after my heart

2015 machine in 2017?

Surface 3 still holds its own in 2017

Let Kodi cut your cord

You should be using Kodi for Windows 10

< >
Welcome to the Windows Central Forums Create Your Account or Ask a Question Answers in 5 minutes - no registration required!
Results 1 to 10 of 10
  1. kazanti's Avatar
    Member

    Posts
    5 Posts
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
       #1  
    Hello, this is a problem reported by dozens of people and in various countries and networks and with different WP7 models (HTC Trophy - HTC Mozart - HTC HD7 - Samsung).

    e.g. if the caller id is 12345678 and my saved contact has value +44 12345678 - the caller id does not resolve to the contact name and instead the phone number is displayed on the screen. The same issue is when the caller id is +44 12345678 and my saved contact has value 12345678.

    It is also reported all over the internet that this is related to a wrong WP7 registry entry CallerIDMatch which has an incorrect value.

    To fix this issue you need to do the WP7 Registry tweak :

    [HKEY_CURRENT_USER\ControlPanel\Phone]
    "CallIDMatch"=dword:7

    But everybody knows that this is a priviledge for registered developers only.

    The problem remains even after the NODO update is applied. I use a HTC Trophy (sim unlocked). I reconfirmed just today with colleagues working in our company branches in Norway, UK and Cyprus that they experience the exact same problem before and after the NODO update. Phones used by other experiencing the same problem are HTC and Samsung (all phones are sim unlocked)

    So ... since the problem is general and ongoing for months (initially reported back in November 2010) and no fix has been issued either by Microsoft or the WP7 manufacturers or the carriers ... what do we WP7 users have to do?
  2. gibbyhome's Avatar
    Member

    Posts
    563 Posts
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    #2  
    Kaxanti,
    have you called Microsoft on this issue or reported it to the windowsphone support boards ? I am supprised that this has not been fixed or looked at ..
  3. kazanti's Avatar
    Member

    Posts
    5 Posts
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
       #3  
    it's reported all over the internet and it is an issue that can hardly be missed. I reported the same on MSDN WP7 forum but no reply yet.
  4. Verizon Hopeful's Avatar
    Member

    Posts
    43 Posts
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    #4  
    This is certainly in the category of fixes for which Microsoft ought to be able to issue quick fixes that completely bypass the "service" providers. There is no reason Microsoft should wait, roll this into a huge, twice a year Service Pack and then wait again for "testing" by Verizon, AT&T, Sprint, etc. These nagging usability problems may not be considered "high priority" issues by Microsoft, but they make a huge difference to consumers who just want these phones to work.
  5. canesfan625's Avatar
    Member

    Posts
    489 Posts
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    #5  
    I had this same problem in Android before. country code seemed to be the sole cause
  6. kazanti's Avatar
    Member

    Posts
    5 Posts
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
       #6  
    any suggestions how do we push this issue to microsoft for immediate attention?

    it is really annoying!
  7. cdook's Avatar
    Member

    Posts
    675 Posts
    Global Posts
    704 Global Posts
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    #7  
    I'd message Microsoft's @winphonesupport on Twitter. They're usually pretty good about helping out.
  8. bome#WP's Avatar
    Member

    Posts
    2 Posts
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    #8  
    I have the same problem in Bosnia: If my contact is saved as +387 65 xxxxxx, caller will not be recognized as contact and phone number without international code will be displayed, but SMS sender will be recognized. On the other hand, if my contact is saved as 065 xxxxxx, caller will be recognized as contact, but SMS sender will not, because international code number will be dispalyed (+387 65 xxxxxx). The only solution for now is to save two numbers for one contact, with and without international code, that I don't want to do.
    I've been asking from HTC Customer Support (my device is HTC Trophy) from January to solve this issue and I am getting answer that they are seriously working on it.
    Rumors are that my and similar devices are made for US market and that is why we, from Europe, have this problem.
    This is very basic issue and, I suppose easy to solve, but after three updates (pre-NoDo, NoDo and HTC Update for Windows Phone) it still remains...
    No other option but to wait...
  9. Kibosh's Avatar
    Member

    Posts
    70 Posts
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    #9  
    Quote Originally Posted by Verizon Hopeful View Post
    This is certainly in the category of fixes for which Microsoft ought to be able to issue quick fixes that completely bypass the "service" providers. There is no reason Microsoft should wait, roll this into a huge, twice a year Service Pack and then wait again for "testing" by Verizon, AT&T, Sprint, etc. These nagging usability problems may not be considered "high priority" issues by Microsoft, but they make a huge difference to consumers who just want these phones to work.
    I didn't have the issue yet on my phone, the HTC Mozart. I save all my contacts with +32 xxx, but I don't receive international calls. I'll will watch it, and post back when it happens.

    Yep, We consumers want our phones to work! I coudn't have cared less about Nodo, I only wanted some fixes to the basics of the phone. I have a feeling MS is to busy working on Mango and forgetting the rest.

    MS is forgetting one big thing about consumers, and that is mounth to mounth publicity. If someone asks me, should I by a WP7 phone, my answer is: not yet! And that's not because it can't multi-task, not because it doesn't have the new IE, nope, it's just because some items, that should be standard, aren't yet what it should be.

    Instead of the list what's extra with Mango, I would prefer a list with what they are fixing
    Last edited by Kibosh; 04-18-2011 at 12:05 PM.
  10. rassac's Avatar
    Member

    Posts
    1 Posts
    Global Posts
    2 Global Posts
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    #10  
    hello guys...it's end of 2012 and apparently this phone issue hasnt been resolved yet! I have HTC HD7. Posted on twitter a few weeks ago but had no reply either! maybe microsoft believed in 2012 as end of the world...

Tags for this Thread

Posting Permissions