QUOTE (jthomas8946 @ Dec 28 2010, 11:24 AM)
index.php?act=findpost&pid=384097
I am curious if anyone has found a fix for this. It seems to be happening to the latest phones with the latest Bluetooth Stack (IPhone 4, Evo 4G, etc...)
Thanks
Not quite that simple... Unfortunately, although BlueTooth is a "standard", and manufacturers of BT compatible equipment can make their devices BT 2.0 or 3.0 compliant, that still leaves tremendous room for varying implementations. If you start to dig down into the BT protocol definitions, you'll find that "name" is actually a single field called "Name" that is supposed to hold a "structured representation of the name", and another called "Formatted Name" which is described as...(you guessed it) a "formatted representation of the name". It's up to the implementer to select a parsing character (e.g., a semi-colon) to separate first and last name...and of course, it's conceivable that some phones store the name internally as "first name / last name" while others store it as "last name / first name" in this "structured field". Same goes for "formatted name".
Transferring the name adds another layer of potential confusion, as names have been, until this past year, transferred using OBEX (object exchange protocol) which is intended to be extremely generalized. As such - it's powerful and flexible, but this also means that there's a lot of room for varying implementation of code that interprets the files being received (and sometimes getting them wrong). Recently, a new BT Profile was introduced - "PBAP", which is intended to support transfer of contacts using vCard format. Many of you will recognized the term "vCard", as this is yet another standard used by programs such as MS Outlook for exporting and important contacts. However, take a look at this sample of vCard 2.1 encoding (just the first few lines of a contact):
BEGIN:VCARD
VERSION:2.1
N:Gump;Forrest
FN:Forrest Gump
ORG:Bubba Gump Shrimp Co.
TITLE:Shrimp Man
TEL;WORK;VOICE
111) 555-1212
TEL;HOME;VOICE
404) 555-121
Notice that, once again, the "N" field allows the implementer to store first and last name in one field, separated by a semi-colon. Sometimes the programmers writing the software that interprets vCards will attempt to parse the names in different ways than were intended by the programmers who wrote the software that encoded the vCards. This issue won't hurt normal use of a device -- just mess things up when it tries to talk to another device that doesn't understand non-standard encoding.
Hopefully, one day, this will be a bit more explicitly standardized -- or at least BT implementations will us, as users, to determine how name fields are parsed (e.g., let us tell the Sonata's BT device whether the contacts it's receiving for a particular paired device are in FN/LN order, or LN/FN, so it knows how to interpret them when the phone book is transferred in).
--
In the meantime - re: new vs old BT devices being compatible or not:
Some old (3 years) Blackberry's, and old BT compliant phones work just fine with the Sonata's BT stack. My 8900 (from T-Mobile), does NOT work properly with my Sonata (2011 2.4L Limited, no Nav) -- it pairs, receives calls fine, initiates calls, number dialing by voice is superb and accurate -- dialing by name, by voice, is unusable. However I was just at the dealer today with a service writer -- we tried the 8900 (which is listed as fully compatible on the Hyundai website) with several cars. Turns out that voice recognition is fine with a Nav-based BT unit -- but not with the no-Nav audio (although the names still come through Last Name first).
However...we tried an iPhone 3, and it worked fine with my car -- excellent voice dialing / recognition, however this was STILL backwards. Today, we also tried a Droid X, newest of the all the devices we've tried -- and it was perfect. Phonebook transferred in a few seconds (a couple of hundred contacts), and name recognition was excellent -- using First Name / Last Name. It was even smart enough to allow us to mention first name only, and it offered up the phonebook entry with that first name -- properly pronouncing first and last name.
So "new" isn't necessarily the distinction that determines whether BT phone book transfer will work properly or not. There's clearly some internal file encoding going on, and some manufacturers do it in a way that the Hyundai BT implementation understands, and some don't.
I wish there were a better answer, as I'm currently very frustrated. One decision I've made is this: before getting another BT compliant phone, I intend to have salesperson from the mobile carrier walk out to my car with me so we can test compatibility together on the spot. No more time consuming surprises!
- Jon