International Caller ID - bug or plist hack?
OK so I've posted before on this topic, and then realised that there are loads of other posts about the same thing, mainly due to the TurboSIM guys finding this out first.
Sorry to create a new thread, but I'd like to explain my experience with UK Vodafone, the iPhone behaviour, and whether anyone can point me to a thread where this is already solved, or already discussed, since my searches aren't coming up with anything useful.
Basically, as reported by everyone here with TurboSIMs, hardware unlocks or software unlocks, incoming calls from numbers saved in your contact list as international dialling codes aren't identified as your contacts. For example, I am in the UK, and I have all my contacts saved with the UK international GSM code so they are identified when I am abroad. So, for example, my home landline is saved as +44 1732 xxxyyy.
When I test by calling my iPhone from my landline, the iPhone reports 01732 xxxyyy and doesn't pick my contact name.
This much is well documented here.
However, any SMS works. So if my girlfriend's mobile number is stored on my iPhone as +44 7977 xxxyyy (as it is), and she sends me an SMS text message, then the iPhone displays the text message *with her name on it* rather than the number.
So the SMS application works with international codes and Address Book, but the Phone application doesn't. Apologies if this is already known, but I'm trying to work out whether this is an application bug or something hackable via the config plists for each app.
I've hacked the ABPhoneFormats.plist to deal with non-US phone dialling codes, but this hasn't changed the behaviour of the Phone application. The SMS app works! All SMS text messages get identified from their sender correctly.
Currently the only way I can get it to work properly is to add local numbers for each contact (i.e. +44 7803 xxxyyy *and* 07803 xxxyyy for the same contact) but this is ugly, wasteful and prone to error, and also completely unnecessary.
If the SMS app can identify the contact, then it surely can't be a baseband or firmware issue - but instead an application bug or a plist for USA only, right?
All the threads I've seen so far seem to insinuate that this can only be fixed by an Apple update, which may re-lock the phone. Does anyone know whether I'm right that this isn't a baseband firmware thing (since SMS works)?? If so, we may be able to update the Phone app without updating from 1.0.2 baseband and therefore not worry about re-locking our phones.....