Android Community
Results 1 to 5 of 5

Thread: 1.6 Incoming Call Problem, CallerID not recognised

  1. #1
    Join Date
    Nov 2009
    Posts
    2

    Default 1.6 Incoming Call Problem, CallerID not recognised


    Hello

    I've been looking for a solution to this problem that showed up after I upgraded to 1.6 in vain, and it seems like most solutions are US centric solutions that do not apply or solutions to a 1.5 bug about CLIP, which I do not have.

    The problem is simple, Donut no longer recognises incoming calls' number as the one stored in contacts. Before you jump the gun, this is not due to the 10 number dialling issue that came up with donut.

    All my contacts are stored in the international dialing format since I travel a lot. This means I have +CC (AAA) NNN NNNN or similar format where CC is country code AAA is area code and N's are the local number. This has been the way I store phones for a long time.

    Before the upgrade to Donut, incoming calls from my carrier mapped correctly to the contacts. Usually the carrier sends the calling number ID as 0AAANNNNNNN, where the leading 0 is a local long distance dial prefix.

    Before, Android could identify that 0AAANNNNNNN was the same as +CCAAANNNNNNN and display the associated contact, now however every call from a local phone is unkown.

    If the calling party is calling from abroad and the calling number is actually +CCAAANNNNN the contact is displayed, thus eliminating any possible link to having a faulty, non working caller ID issue witht he carrier/phone.

    My question is, is anyone else having this issue, is there a way to solve this? My phone is unrooted HTC Magic, is there maybe an option to downgrade back to 1.5? I cannot use my phone like this.

    Thanks for any info.

  2. #2
    Join Date
    Mar 2009
    Location
    UK
    Posts
    3,343

    Default Re: 1.6 Incoming Call Problem, CallerID not recognised

    I've heard of quite a few people having this problem. There are other threads about it on this forum, but I don't know if any had a solution as I wasn't that interested in them as I don't suffer from this issue.

    Have a search for them...

  3. #3
    Join Date
    Nov 2009
    Posts
    2

    Default Re: 1.6 Incoming Call Problem, CallerID not recognised

    Hi ex

    Thanks for the heads up. I did a search before but the three threads I found were related to the 10 number dialling issue that is restricted to the US and local numbers. This is not the same issue (maybe related to same bits of code).

    There are two main locations where I found this being discussed with other international users suffering the same problem. I have verified it with friends in Eastern Europe that are using Android handsets and they are all suffering from the same issue.

    The only 'bootstrap' solution we can apply is no solution at all. We have to add the incoming number format to the Contact as an additional number. This bloats your phone book, adds duplicate numbers with different formats and is generally not a good thing to do to keep an organized phonebook.

    Google Code thread:
    http://code.google.com/p/android/issues/detail?id=4134

    Google Mobile thread:
    http://www.google.com/support/forum/...0478c9fe82c077


    Unfortunately no solution, just more places to post the problem to add to the people experiencing it and try to get 'some' google attention to a core feature of a GSM phone that is not working under the latest google OS.

  4. #4
    Join Date
    Mar 2009
    Location
    UK
    Posts
    3,343

    Default Re: 1.6 Incoming Call Problem, CallerID not recognised

    I know the phone number matching did change in Donut (or was it Cupcake?).

    It used to just match on the last few digits of the phone number, because this was easiest to program. In theory, the last few digits never change, but the first few digits can change depending on where you are... for example it may or may not include the area code if the incoming call is local. It may or may not include the country code if the call is coming from the same country, etc. It depends how the network chooses to send the caller ID information.

    However - this caused problems in that there are people out there who do have similar numbers for different people in their phone, that only differ in the first few digits.

    So... they fixed it. But, they seem to have broken it for other people at the same time.

    Google are aware of the issue (there are a few bugs filed with them that sound identical or very similar). So I imagine it'll be fixed... at some point...

  5. #5
    Join Date
    Dec 2009
    Posts
    1

    Default Re: 1.6 Incoming Call Problem, CallerID not recognised


    Fix here:

    http://forum.xda-developers.com/showthread.php?t=606728

    ask an update for any other country codes

Similar Threads

  1. Picture of incoming call??
    By travel4696 in forum General Phone Chat
    Replies: 18
    Last Post: 07-08-2011, 08:37 AM
  2. 1.6 donut contact, text, and incoming call problem!!!!!
    By paxon2011 in forum General Phone Chat
    Replies: 4
    Last Post: 11-27-2009, 07:31 AM
  3. Recommend an incoming call BLOCK app
    By barqw1982 in forum All About Andorid Software
    Replies: 0
    Last Post: 09-02-2009, 12:55 AM
  4. G1 force closes & doesn't get incoming call
    By NotAHero in forum General HTC Chat
    Replies: 6
    Last Post: 07-08-2009, 01:37 PM
  5. Idea for Incoming/outgoing call picture
    By Ward in forum Developers Guild
    Replies: 4
    Last Post: 12-21-2008, 07:43 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •