I'm interested in this topic also.
I searched around at mofv.com found an old discussion with the same questions and
posted there.
The first step of course is to identify and post the model and revision MyGig system you have. An REN version has no phone or address book at all for instance.
From what I can tell so far I doubt this is supported on any of the MyGig systems. I have a 730N RHR.
On p14 of the
UConnect manual street address data is not mentioned in the description of what gets downloaded from the phone, "names (text names) and number entries".
This is unfortunate but my guess is the standard used for bluetooth data transfers can't or doesn't accomodate this, probably because there's no standard for the way every phone stores this data.
One question I have is whether the seperate local 32 name limited editable UConnect address book has fields to enter street addresses. I haven't looked at that yet.
If it does it's logical the nav system would use them. It would be a tedious process to enter all that data using the car interface though. Plus from what I've read in the manual(s) it sounds like the system wouldn't behave well if any of those same names existed in the 1000 name uneditable Uconnect version of the phone address book. So again, not sounding promising.
EDIT re: above, checked out the
online version of the UConnect tutorial on adding a (local UConnect) phonebook entry and there are no fields for entering a street address. I think this pretty much clinches it.....
EDIT (again): p 190 in my 730N RHR manual describes a process to add names to the local 32 name limited address book including copying a name from an existing contact and adding an address to that. Re: my previous comment and the system not behaving well if the same names existed in the 1000 name uneditable Uconnect version of the phone address book, maybe it would be ok, I may have misunderstood the p 2 entry from the UConnect manual saying "It is not recommended to store similar sounding names in the Uconnect phonebook". That's probably a warning for a seperate issue. It will be interesting to see what happens after I create a contact in the local UConnect address book copied from an existing contact in the UConnect version of the phone address book and add street address data to it and attempt to navigate to or even call the entry via voice.
When I get hits using voice to dial an entry in my UConnect version of the phone address book which has a home, office and mobile number for the same entry, the hit results only show the same name repeated on multiple lines without anything else displayed ie something useful like 'home' 'office' etc or even the different phone number for each entry etc. Seems one must pick one and see, which is less than ideal.....
I plan to spend some quality time with the machine and beat on it then hit up the geeks at mofv.com for any finer points. I definitely want to try and get the most out of the 2k investment in the nav/voice system.
I'm trying to track down the standard used for Uconnect (bluetooth) data transfers if there is one. Somewhere there's a technical document describing exactly what the record data looks like, ie the defined fields, how many characters each they can be etc. The Uconnect manual mentions something about a 24 character limit but is not specific on exactly what that means (name only, name + phone number etc).
