Originally Posted by timschuerewegen

It's actually the other way around. MobilePhone uses "Equal" and MobileSMS uses "EqualStrict".

I just realized one thing, I can't really comment on MobileSMS.app because all SMS in Brazil arrive with 0+Area_Code+number, so the EqualStrict will match as expected.

What puzzles me is that you said MobilePhone.app uses plain "Equal" only and it does not provide any extact parameter to strengthen it up.

Does MobilePhone.app calls any other AppSupport routine?

Just a reminder that the order of phone number templates for a given country is very important. The first template decompo*******Number thinks can be applied to the normalized phone number string will be used. If this is a "bad" template (remember "2 7" and "1 7" issue?) then decomposedPhoneNumbersEqual will most probably return 0 because the decomposed phone number is bad.

Originally Posted by aviegas

Does MobilePhone.app calls any other AppSupport routine?

Apart from those 3 I mentioned in an earlier post, I don't think so.

I am going to try http://www.hackint0sh.org/forum/show...&postcount=299 myself. Can you give me the address book phone number string, dialpad phone number string and your "br" templates?

Originally Posted by timschuerewegen

I am going to try http://www.hackint0sh.org/forum/show...&postcount=299 myself. Can you give me the address book phone number string, dialpad phone number string and your "br" templates?

Here it goes:

Address book: (041-21) 8111-2222
Valid dial strings: 0412181112222 or 81112222
SMSs arrive as 02181112222

Dialpad will match the fist form, but not the second. SMS matches fine.

BR Template:

br 55 00 0 2 8
br 55 0014 014 2 8
br 55 0015 015 2 8
br 55 0021 021 2 8
br 55 0031 031 2 8
br 55 0041 041 2 8
br 55 004121 0 0 8
br 55 00 - 0 8

As I posted it also happens with the US template.
Address Book: 1-212-444-5555
Valid dial: 12124445555, 2124445555 and 4445555

Dialpad will match the first 2, but not the last!

OK. I added your "br" templates to my AppSupport. Here are my results. They look correct, right? In other words, dialpad should be able to match that phone number in its 3 string formats to that one contact.

Code:

# ./CheckAppSupport CPPhoneNumberCopyNormalized "(041-21) 8111-2222"
0412181112222
# ./CheckAppSupport CPPhoneNumbersEqual "(041-21) 8111-2222" 0412181112222 br
1
# ./CheckAppSupport CPPhoneNumbersEqual "(041-21) 8111-2222" 81112222 br
1
# ./CheckAppSupport CPPhoneNumbersEqual "(041-21) 8111-2222" 02181112222 br
1
# ./CheckAppSupport decompo*******Number 0412181112222 br
1,"55","041","21","81112222"
# ./CheckAppSupport decompo*******Number 81112222 br
1,"55","","","81112222"
# ./CheckAppSupport decompo*******Number 02181112222 br
1,"55","0","21","81112222"

And after some "trickery" the results of CPPhoneNumbersEqualStrict.

Code:

# ./CheckAppSupport CPPhoneNumbersEqualStrict "(041-21) 8111-2222" 0412181112222
1
# ./CheckAppSupport CPPhoneNumbersEqualStrict "(041-21) 8111-2222" 81112222
0
# ./CheckAppSupport CPPhoneNumbersEqualStrict "(041-21) 8111-2222" 02181112222
1

Originally Posted by aviegas

Here it goes:

Address book: (041-21) 8111-2222
Valid dial strings: 0412181112222 or 81112222
SMSs arrive as 02181112222

Dialpad will match the fist form, but not the second. SMS matches fine.

BR Template:

br 55 00 0 2 8
br 55 0014 014 2 8
br 55 0015 015 2 8
br 55 0021 021 2 8
br 55 0031 031 2 8
br 55 0041 041 2 8
br 55 004121 0 0 8
br 55 00 - 0 8

As I posted it also happens with the US template.
Address Book: 1-212-444-5555
Valid dial: 12124445555, 2124445555 and 4445555

Dialpad will match the first 2, but not the last!

my guess is apple did that on purpose.

given you are roaming with your phone, when dialing the last option (4445555) you will not call your stored contact, but someone who has this phone number in the given city in that moment. that`s why it`s not intended to match.

It matches the first two options, because it will actually call the stored contact propely.

Originally Posted by timschuerewegen

And after some "trickery" the results of CPPhoneNumbersEqualStrict.

Code:

# ./CheckAppSupport CPPhoneNumbersEqualStrict "(041-21) 8111-2222" 0412181112222
1
# ./CheckAppSupport CPPhoneNumbersEqualStrict "(041-21) 8111-2222" 81112222
0
# ./CheckAppSupport CPPhoneNumbersEqualStrict "(041-21) 8111-2222" 02181112222
1

That is the same I got. "Equal" matches all 3 and EqualStrict matches all but the one that has just the "local" number.

"Recent Calls" will map all 3, so my "educated" guess is that the use the Equal call.

The dialpad does not match the simple "local" number. So my "educated" guess *was* that they were using EqualStrict, but as proven they are not.

The big question is: how are they doing the test and how can we patch it.

Originally Posted by timschuerewegen

It's actually the other way around. MobilePhone uses "Equal" and MobileSMS uses "EqualStrict".

Not sure what I was smoking but MobileSMS also uses CPPhoneNumbersEqual, not CPPhoneNumbersEqualStrict. So both Phone and SMS use Equal, not EqualStrict.