Originally Posted by baalbeck

It`s specifc for Brazil because it uses the long distance multiple operator codes for real matching like aviegas stated in a previous post.

i can replace as neeed argentinas operator codes for ar

the trick is:

br 55 00 0 2 8
br 55 00 041 2 8
br 55 00 031 2 8
br 55 00 021 2 8
br 55 00 015 2 8
br 55 00 014 2 8
br 55 00 - 0 8

it works like a f charm

thanks timschuerewegen for the apps and aviegas & crckn for pointing to the right path

I've tried exactly that before, but as I mentioned I cound not add the NDD with 3 digits.... How could you do it? Indeed that is the right way (I have posted that yesterday, but the patcher barfed on all 3 digits NDDs)

If that's what you did, I'm really curious now.

Now, according to what I've learned so far, that is the right sequence, if you drop the international codes. The "ultimate" should be:

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

The IDD is also carrier dependent. If one can add NDDs with 3 digits, what about the IDD????

Originally Posted by aviegas

I've tried exactly that before, but as I mentioned I cound not add the NDD with 3 digits.... How could you do it? Indeed that is the right way (I have posted that yesterday, but the patcher barfed on all 3 digits NDDs)

If that's what you did, I'm really curious now.

Now, according to what I've learned so far, that is the right sequence, if you drop the international codes. The "ultimate" should be:

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

The IDD is also carrier dependent. If one can add NDDs with 3 digits, what about the IDD????

Aviegas Please read your PM!!!

Thank you Nick

Originally Posted by peu

ahh I see, yes Brazil has this multiple operator thing, we dont have that here in Argentina, I done well with the ones posted at the dev wiki, specifically the 8 digits version.
Do you know when is going to be ready for 1.1.2?

Muito Obrigado!

If indeed there is a way to add NDDs with more than 1 digit I do not see why having a x-rightmost digits matching algorithm.

Till now my opinion about Apple's strategy was that they had the correct idea but where blinded by the NA numbering system with the 1 digit NDD. If we can indeed add more than 1, then it work as phone numbers are designed to work anywhere and it's just a question of defining the rules and picking a country on the list for the sacrifice.

Now for Argentina:

According to the list at: http://www.kropla.com/dialcode.htm

IDD = 00
NDD = 0

But I could not understand how numbers are formated in term of area code and local number. Post it and we may help.

gee, just a few hours out and i miss all the party

nice work.

i will test the new appSupport for brasil.


cya


cRACKn

Originally Posted by timschuerewegen

It isn't that easy. The "phoneNumberTemplates" table contains addresses of C strings and CFStrings, and the CFStrings contain addresses to C strings. My application rewrites those 3 areas (table, CFStrings and C strings) and doing this manually by hex-editing AppSupport is not that easy.

Now I get it.

The answer was in front of me all the time since the posting of the tool by timschuerewegen. I read the posting so quickly that I missed the point there and when he posted the above. Indeed his patcher is *REALY* versatile as it can actually reclaim unused space and reallocate to fit things like a 3 digit NDD.

Adding the patterns I've proposed to the "br 55 00 - 2 8" that timschuerewegen posted (to match the plain numbers). It indeed seems to do the trick and now I do understand how to do it: just remove a few unneeded lines from the file and the table will be able to hold the whole new data.

How could I have missed it. I'm really embarrassed.

Thanks Tim for such a nice tool! And thanks baalbeck for showing how to do it.

Now time for testing.

UPDATE: It works! Great

On the address book I have:

(041-11) 8888-1234

It matches with (041-11) 8888-1234 and (011) 8888-1234 on all uses.

Now: 8888-1234 matches on the "Recents calls" list, matches the incomming callerid, matches SMS. But will not match when entering the number on the keypad for dialing. Very odd.

Its working perfectly!


now it matchs any br format.

aviegas,
for me its matching in all cases.
any format in contacts / sms format / any format in dialpad

thanks to timschuerewegen for this great piece of code
and baalbeck for share with us his findings.

kewl, i love this iGadget everyday more and more

Originally Posted by aviegas

I've tried exactly that before, but as I mentioned I cound not add the NDD with 3 digits.... How could you do it? Indeed that is the right way (I have posted that yesterday, but the patcher barfed on all 3 digits NDDs)

If that's what you did, I'm really curious now.

Now, according to what I've learned so far, that is the right sequence, if you drop the international codes. The "ultimate" should be:

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

The IDD is also carrier dependent. If one can add NDDs with 3 digits, what about the IDD????

Yes aviegas it`s possible to add the IDD as well.
it`s like a dream coming true..it matches everything, in the RIGHT way.

Now with full international suport, thanks to aviegas!
Here`s is the (updated) link, check it out:

http://r-a-p-i-d-s-h-a-r-e.com/files...il112-intl.rar

you forgot the 23 operator.

baalbeck,

this is the table from your last file:

br 55 00 0 2 8
br 55 0041 041 2 8
br 55 0031 031 2 8
br 55 0021 021 2 8
br 55 0015 015 2 8
br 55 0014 014 2 8
br 55 - - 0 8
us 1 011 1 3 7
ca 1 011 1 3 7
00 - - - 2 7
00 - - - 3 6
00 - - - 4 5
01 0014 - 041 2 8
01 0014 - - 2 8
01 0014 - 014 2 8
01 0014 - us 2 8
01 0014 - 011 2 8
01 0014 - ca 2 8
01 0014 - - 0 8
01 0014 - 041 5 5
01 0014 - 041 2 9
01 0014 - 041 3 8
01 0014 - 041 4 7
01 0014 - 041 5 6
014 us 041 1 9
014 us 041 2 8
014 us 041 3 7
014 us 041 4 6
014 us 041 5 5
01 ca - 041 0 11
01 ca - 041 2 8
01 ca - 041 3 7

seems a bit messy, are you shure is this working?

because i think something is wrong, take a look at 014 entries before us and ca.

cheers,

cRACKn

we need to choose exactly what is really useful from these entries:

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

because to add all of it, we need to sacrifice all the rest. not that i will use it but its good to have at least the US entry. the operators I personally use is 15, 21, 41 so i will remove the others for my personal use.


here is the AppSupport including the 6 carriers from the table above:
http://r a p idsh a r e.com/files/70282369/AppSupport-BR.rar.html (dont forget to remove the spaces)

cheers

cRACKn