Page 32 of 132 FirstFirst ... 122223242526272829303132333435363738394041425282 ... LastLast
Results 311 to 320 of 1316
Discuss [Solution] International/local caller ID matching at the iPhone "2G" (Rev. 1) - Hackint0sh.org; Originally Posted by timschuerewegen I have updated CheckAppSupport with support for "phoneNumbersEqual". http://www.hackint0sh.org/forum/showpost.php?p=120538 Please experiment ...
  1. #311
    The Man Array aviegas's Avatar

    Join Date
    Sep 2007
    Posts
    1,108
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    73

    Default

    Quote Originally Posted by timschuerewegen View Post
    I have updated CheckAppSupport with support for "phoneNumbersEqual".

    http://www.hackint0sh.org/forum/showpost.php?p=120538

    Please experiment with strict "0" and "1". It relates to how two decomposed phonenumbers are compared.
    I did several checks and this is what I think:

    1 - Strict check
    Decompose according to country
    Must match local + area code
    Ignores valid NDD even if different (that is ok and correct)


    0 - Loose check
    Decompose according to country
    Must match local
    If both have area code, must match
    If only one has area code, ignore it <<--- This is the difference
    Ignores valiud NDD even if different (That is ok and correct)


    So that is the trick. MobileSMS.app and the "recent calls" list uses the loose check, while the dialpad uses a strict check.

    Is it hard to make an option to patch

    Code:
    unsigned long CPPhoneNumbersEqualStrict( char *str1, char *str2)
    {
    return phoneNumbersEqual( str1, 0, str2, 0, 1, 0);
    }
    to

    Code:
    unsigned long CPPhoneNumbersEqualStrict( char *str1, char *str2)
    {
    return phoneNumbersEqual( str1, 0, str2, 0, 0, 0);
    }
    ????

    like either an option flag "-loose" or add a line in the file that will set the mode

    mode strict
    mode loose

    For a test, if you tell me the offset for the "0" or "1" string, I can test if the dialpad will act as expected.


  2. #312
    Senior Professional Array timschuerewegen's Avatar

    Join Date
    Aug 2007
    Location
    Belgium
    Posts
    450
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    34

    Default

    Quote Originally Posted by aviegas View Post
    For a test, if you tell me the offset for the "0" or "1" string, I can test if the dialpad will act as expected.
    At offset 0x8510 in the AppSupport file, change byte 0x01 into 0x00.

  3. #313
    Senior Professional Array

    Join Date
    Aug 2007
    Location
    Brasil
    Posts
    111
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    12

    Default

    tim, thanks for the great effort!! this app rules!

    aviegas, it does matches in the keypad, but it works only when dialing the format you stored the contact in the address book. give it a try.
    in my case i store contacts in local formats only, and it matches showing the contact`s name below the dialed number.

    bb
    Last edited by baalbeck; 11-17-2007 at 04:19 PM.

  4. #314
    The Man Array aviegas's Avatar

    Join Date
    Sep 2007
    Posts
    1,108
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    73

    Default

    Quote Originally Posted by timschuerewegen View Post
    At offset 0x8510 in the AppSupport file, change byte 0x01 into 0x00.
    Doesn't work

    So it's not there that is the difference.

  5. #315
    The Man Array aviegas's Avatar

    Join Date
    Sep 2007
    Posts
    1,108
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    73

    Default

    Quote Originally Posted by baalbeck View Post
    tim, thanks for the great effort!! this app rules!

    aviegas, it does matches in the keypad, but it works only when dialing the format you stored the contact in the address book. give it a try.
    in my case i store contacts in local formats only, and it matches showing the contact`s name below the dialed number.

    bb
    I store 041-21-81112222 and it matches both 041-21-8111222 and 021-81112222 and 21-81112222. But does not match just 81112222

    So if you store the version with the NDD (041-21-81112222), then there is not match when performing local dialing.

    I have a valid and active AT&T SIM and I will perform some tests with it and let you know. I have several US numbers in my contacts.

    Stay tuned


  6. #316
    Professional Array

    Join Date
    Sep 2007
    Posts
    97
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    11

    Default

    I took all the pain to finally get to 1.1.2 version. Badly, now I have the Phone.app and SMS app problem as everybody here....I'm in Singapore and the service here has 8 digits (excluding the area code). Please! can someone tell me which patch should I use and where do I get it....
    I have tried a lot of methods but after reboot the phone just hang at Apple logo. Any help would be appreciated, thanks in advance!

  7. #317
    The Man Array aviegas's Avatar

    Join Date
    Sep 2007
    Posts
    1,108
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    73

    Default

    Ok, look at this.

    Test number: (212) 444-5555, NDD: 1
    Mode: AT&T valid and active SIM card:

    # ./CheckAppSupport CPPhoneNumberCopyActiveCountryCode
    us
    # ./CheckAppSupport CPPhoneNumbersEqualStrict 4445555 12124445555
    0
    # ./CheckAppSupport CPPhoneNumbersEqualStrict 2124445555 12124445555
    1


    Test number: (21) 8111-2222, NDD: 041
    Mode: Brazilian SIM

    # ./CheckAppSupport CPPhoneNumbersEqualStrict 81112222 0412181112222
    0
    # ./CheckAppSupport CPPhoneNumbersEqualStrict 2181112222 0412181112222
    1

    So it's consistent across countries. Like in Brazil, US numbers can be stored with the NDD and area code (in the US, with AT&T at least, you can omit even the NDD) and the network will handle local numbers as necessary.

    My guess is that this approach is quite common, and that's why a number is bronken in IDD/NDD/Area code/Number all over the world. The carrier can remove unneeded parts.

    This is specially handy for anyone that travels. Having the contats with the NDD+AreaCode allows using it no matter where you are calling from.

    That's why ALL OTHER manufacturers opt for the x-rightmost digits approach.

    The interesting part is that on the iPhone it does not work only in the dialpad. It looks like they are using/calling a different routine for the match, specially since they are doing it at each keystroke. I do not know.

    Anyway, it's really strange that you type a number and it will not match when you dial, but it will when you look at the "recent calls" list.

    Any ideas?

  8. #318
    The Man Array aviegas's Avatar

    Join Date
    Sep 2007
    Posts
    1,108
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    73

    Default

    For completeness:

    the patch at 0x8510 works as expected by "loosing up" calls to CPPhoneNumbersEqualStrict, as we predicted. It's just that the dialpad is not checking thru CPPhoneNumberEqualStrict.

    Results with US SIM with the Loose patch:

    # ./CheckAppSupport CPPhoneNumberCopyActiveCountryCode
    us
    # ./CheckAppSupport CPPhoneNumbersEqualStrict 4445555 12124445555
    1

    Without the patch:
    # ./CheckAppSupport CPPhoneNumbersEqualStrict 4445555 12124445555
    0

    Maybe the dialpad is calling phoneNumbersEqual directly?

  9. #319
    Senior Professional Array timschuerewegen's Avatar

    Join Date
    Aug 2007
    Location
    Belgium
    Posts
    450
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    34

    Default

    Quote Originally Posted by aviegas View Post
    Doesn't work

    So it's not there that is the difference.
    But MobilePhone uses CPPhoneNumbersEqual, not CPPhoneNumbersEqualStrict, so yeah, you don't notice a difference.

  10. #320
    Senior Professional Array timschuerewegen's Avatar

    Join Date
    Aug 2007
    Location
    Belgium
    Posts
    450
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    34

    Default

    Quote Originally Posted by aviegas View Post
    My guess, is that the "recents calls list" and the SMS.app use the "Equal" call while the diapad is calling "EqualStrict".
    It's actually the other way around. MobilePhone uses "Equal" and MobileSMS uses "EqualStrict".


 

 

LinkBacks (?)

  1. 07-13-2009, 03:48 PM
  2. 03-17-2009, 03:51 PM
  3. 03-17-2009, 12:45 PM
  4. 03-17-2009, 12:43 PM
  5. 03-16-2009, 04:14 PM
  6. 02-14-2009, 03:43 PM
  7. 01-14-2009, 03:29 PM
  8. 01-14-2009, 02:08 PM

Similar Threads

  1. [1.1.3] International Caller ID Problem
    By GreatLicker in forum iPhone "2G" (Rev. 1)
    Replies: 3
    Last Post: 03-05-2008, 07:20 PM
  2. Replies: 106
    Last Post: 03-03-2008, 06:53 PM
  3. Caller ID for local numbers... is it possible?
    By nemesis1218 in forum Free Toolchain Software (Cydia App's)
    Replies: 4
    Last Post: 01-08-2008, 11:48 PM
  4. Replies: 21
    Last Post: 11-22-2007, 01:23 PM
  5. Matching contacts to UK caller ids?
    By jhrfc in forum General
    Replies: 7
    Last Post: 09-23-2007, 11:54 AM

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
  •  
Powered by vBulletin®
Copyright © 2014 vBulletin Solutions, Inc. All rights reserved.
Search Engine Friendly URLs by vBSEO
(c) 2006-2012 Hackint0sh.org
All times are GMT +2. The time now is 06:12 AM.
twitter, follow us!