Page 10 of 13 FirstFirst 12345678910111213 LastLast
Results 91 to 100 of 130
Discuss Phone Number format at the iPhone "2G" (Rev. 1) - Hackint0sh.org; Using only small format works fine. The only problem is the sms notification dialog. It ...
  1. #91
    Senior Professional Array

    Join Date
    May 2006
    Posts
    205
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    18

    Default

    Using only small format works fine. The only problem is the sms notification dialog. It shows the number. But when you tap View, the contact is found and SMS app link the sms to the right contact. So it avoids 2 numbers. Incoming calls are displayed correctly. But I don't think searching contact like Nokia is a good idea. Last 6 digits are not always different (I'm talking about swiss numbers. we are using 10 numbers. The 3 first for the zone. so there may be same numbers in different zones). Contacts are in a sqllite database. When a phone comes in, the iPhone just have to find the short and long version and do a query in the db. All phones are able to do that now, without cutting the phone number. Nokia did this because the phone, at that time, was not powerful enough to do long queries.


  2. #92
    Senior Professional Array

    Join Date
    Sep 2007
    Posts
    115
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    12

    Default

    Quote Originally Posted by jacoch View Post
    Using only small format works fine. The only problem is the sms notification dialog. It shows the number. But when you tap View, the contact is found and SMS app link the sms to the right contact. So it avoids 2 numbers. Incoming calls are displayed correctly. But I don't think searching contact like Nokia is a good idea. Last 6 digits are not always different (I'm talking about swiss numbers. we are using 10 numbers. The 3 first for the zone. so there may be same numbers in different zones). Contacts are in a sqllite database. When a phone comes in, the iPhone just have to find the short and long version and do a query in the db. All phones are able to do that now, without cutting the phone number. Nokia did this because the phone, at that time, was not powerful enough to do long queries.
    LAST (ie trailing) 6 digits won't even involve area codes... what are you talking about???

    and there is literally a 1 in 1,000,000 chance that someone else ringing you is going to incorrectly match an entry in your phone book... even so what's the problem if it does happen??

  3. #93
    Senior Professional Array

    Join Date
    Aug 2007
    Posts
    193
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    16

    Default

    Just changed the format to Australian. Thanks alot!

  4. #94
    Advanced Array

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

    Default

    Quote Originally Posted by Dell View Post
    Just changed the format to Australian. Thanks alot!
    Hey mate can you tell me what you did to do this? and if they show correctly for both calls and when you rcv. sms?

  5. #95
    Senior Professional Array

    Join Date
    May 2006
    Posts
    205
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    18

    Default

    Quote Originally Posted by joe_hensonn View Post
    LAST (ie trailing) 6 digits won't even involve area codes... what are you talking about???

    and there is literally a 1 in 1,000,000 chance that someone else ringing you is going to incorrectly match an entry in your phone book... even so what's the problem if it does happen??
    I'm saying here the phone format is xxx yyy yy yy. xxx is the area. So if you check only the 6 last digits, you may miss numbers. Sure chances are quite small to have two in the address book. But if something needs to be written, why use a workaround used by Nokia some years ago because of phones with slow processors and capacity, when our iphone stores contacts in a sqllite db that could be queried very quickly and searching for the phone numbers without cutting it.


  6. #96
    Senior Professional Array

    Join Date
    Jul 2007
    Posts
    445
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    30

    Default

    it should be ok for sms but no workaround for calls yet

  7. #97
    Senior Professional Array

    Join Date
    Aug 2007
    Location
    Budapest, Hungary
    Posts
    248
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    19

    Default

    Quote Originally Posted by RVN84 View Post
    it should be ok for sms but no workaround for calls yet
    For calls you just need to put every number twice, once with +internationalprefix-local and once only local.

    Cheers

    Ben

  8. #98
    Senior Professional Array

    Join Date
    Aug 2007
    Posts
    208
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    20

    Default

    I have tried hard to edit a plist file with Windows without any success. Even with the website provided from Chinaet, I still don't understand how to do it .

    Anyone can help, pleeeeeeease.
    Many, Many Thanks in advance.

  9. #99
    Senior Professional Array

    Join Date
    Sep 2007
    Posts
    115
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    12

    Default

    Quote Originally Posted by jacoch View Post
    I'm saying here the phone format is xxx yyy yy yy. xxx is the area. So if you check only the 6 last digits, you may miss numbers. Sure chances are quite small to have two in the address book. But if something needs to be written, why use a workaround used by Nokia some years ago because of phones with slow processors and capacity, when our iphone stores contacts in a sqllite db that could be queried very quickly and searching for the phone numbers without cutting it.
    i think 8 digits would be fine.. remember it's a factor of 10 for each additional digit.

    anyway i think you miss my point slightly.

    the algo would roughly be:

    1. read CID from incoming call
    2. truncate string to LAST 8 digits
    3. look for truncated string in phone book
    4. if found, display name
    5. if not found, display CID only.

    the only fault of this method would be if someone NOT in your phonebook calls you and the 8 digits of their number matches someone in your address book. i think this is a pretty remote chance.

    i played around with my nokia some time ago and i found that if you have 2 numbers recorded with same last 6 digits it will display the first one you created.

    in any case someone needs to find and reverse eng the application on the iphone to use this or any method. you would also have to program that app to deal with the wide range of number formats in the plist files.

  10. #100
    Senior Professional Array

    Join Date
    May 2006
    Posts
    205
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    18

    Default

    Don't get the factore of 10. Doing SELECT * FROM contacts WHERE (mobile = 'shortnum') OR (mobile = 'longnum') won't be much longer than searching for a single num that have been cut to 8 chars. And you're sure you find exactly what you are searching for.


 

 

Similar Threads

  1. phone number format issue
    By khaled_cs in forum Turbo-, Supersim and Simcloning Solution
    Replies: 0
    Last Post: 11-28-2008, 04:45 AM
  2. Phone number format
    By elfmund in forum Free Toolchain Software (Cydia App's)
    Replies: 5
    Last Post: 12-05-2007, 05:44 AM
  3. phone number format help
    By grantsmith in forum iPhone "2G" (Rev. 1)
    Replies: 3
    Last Post: 11-03-2007, 01:52 AM
  4. Help me with Phone number format
    By kherlen in forum General
    Replies: 2
    Last Post: 10-09-2007, 06:24 PM
  5. Phone book number format
    By ppervoy in forum General
    Replies: 6
    Last Post: 09-23-2007, 11:53 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 11:37 PM.
twitter, follow us!