I'm new at this gpx stuff, but I'm having quite the fun and, for the most part I'm successful at putting custom POI in my Garmin Nuvi 3760T. I did find, however when I load up a gpx file, such as the one for offbeat attractions US, I can't get the phone numbers to dial. My cell phone is paired with the nuvii, and it dials calls from the dial pad, and receives calls, but when I hit the dial button from a poi, it beeps, but doesn't dial.
I've tried preceeding the phone number with a +1, and I've tried it with speed and proximity numbers filled in and without, but nothing seems to work.
What software did you use to create/edit the GPX file?
The file must be configured in a certain way in order to make the phone numbers dialable.
Have you tried TurboCCC's Extra_POI_Editor?
Thanks for the followup. All of the files are a straight gpx download from POI factory with no editing. I have tried Extra_POI_Editor. I am using POI Loader to send the files to the Garmin.
Can you give us an example (the link) of a file you downloaded from here that is giving you trouble. One of us might be able to try and confirm that it works for them.
That will isolate it to either a problem with the file or a problem with your specific setup/phone.
One of them was the diners, drive-in and dives gpx version
(123) 456-7890 -vs- 123-456-7890
That is the only difference that I could find with another gpx file I have.
Just a thought
Dave, I concur. All my POI's are listed as 123-456-789, and no problems at all.
I tried it both ways and neither xxx-xxx-xxxx or (xxx) xxx-xxxx dial when I send the gpx file to the nuvi using POI Loader. The file ends up in a place on the "where to" menu called extras custom poi. The dial button is present, it makes a beep sound when you press it, but the phone icon doesn't come up on the screen and it doesn't dial.
If I open the gpx file in Extra POI and send just one of the entries to "favorites" using the send to favorites in Extra POI, the number will dial as it should.
I think that this must be a firmware issue with the 3760t.
I loaded that file plus dave's Harley file to my Zumo and they dialed just fine.
But on my 3760t, nothing happens when you touch the Call button.
I think the files are fine and you aren't doing anything incorrectly.
Garmin will have to fix this.
Motorcycle Mama -- Thanks for validating the issue. I've been working at it all day thinking I was doing something wrong. How do I make Garmin aware of the issue. Is it just a support call that I make?
I would send an email. That way it is documented.
Don't hold your breath though waiting for them to fix it.
They still need to fix the issue with the unit not accepting routes from MapSource, so hopefully soon.
any time a new garmin product come out, there modo is to get out in to the market and deal with software issues later. so now it becomes a waiting game to see how long before the new firmware is posted. good luck
For some reasons, maybe your GPS only dials the phone numbers in the Favorites?
turboccc -- That's what it's coming down to. It sounds like a bug in the firmware. If the poi is sent to favorites, it dials as expected. If the poi is sent to extras custom poi, it doesn't. I'll report it to garmin and "hold my breath."
What's weird is that it will dial Favorites and dials numbers from the phone's phonebook with no problem.
With the Custom POIs, the "Call" button comes up (so it's recognizing the phone number), but pressing the button doesn't do anything.
I know. After all the time I and you guys spent trying to run down the problem, it's disturbing. After seeing everything just-about work, I was excited and thinking of the possibilities of preparing custom poi files for sharing with the group. Now... I'm stuck in the disappointment cycle of not being able to fully test gpx files on my Garmin.
Doesn't it seem like every time Garmin releases a new device they write the firmware from scratch?
I believe the 37xx series is based on a Linux platform, so in that perspective it would be similar to the 5000 and 8xx units and unlike the other nuvi's. I wonder if Garmin started with the 8xx/5000 software base or if they started over?
Yes, they could be patching up codes from other nuvi together. I have seen some similar "re-use" approach which basically leads to the same thing. They think you can put A and B together because they work on other products, but integration brings sometimes new issues. Test and QC is the only way to find unexpected bugs.
Since I do not have a GPS with dialable phone, Can someone please verify which format is preferred on GPX file that will make the phone dialable:
Do I need the leading 1
1 (312) xxx-xxxx
Just curious since I do maintain the DDD file but have no way to test the phone options.
I don't think the format matters as it is for readability only. As to needing a leading "1", that would depend on your phone. My cell does not require a leading 1, yours might. The BT should parse the data to be sent as a dial string and remove any formatting characters to send just the digits.
I haven't met a cell phone yet that wants, or needs, the 1 before a phone number. As far as he phone number itself, I don't think it matters since both formats work in my cell phone and it shouldnt matter with the bluetooth.
I wrote to the Garmin folks. Of course, they won't acknowledge that it's a problem with the firmware and insist that it's a problem with the coding of the the gpx file. I explained that the individual entries work well if they're dialed from the favorites, but not from the custom poi. I also reminded them that others experienced the same problem while testing the identical gpx file on the exact model I have. They won't listen.
Well, and the other thing that they are not realizing perhaps is that the same Custom POI files dial just fine when they are loaded to my Zumo 550. So it's not the files.
I was extremely angry with their canned response. I wrote back and explained the problem again, and told them not to blow me off, but to load a custom PO into the both the custom POI and favorites on the Nuvi 3760T and see for themselves. I finally go a response saying they test it, found my report to be valid, and said, "...I have tested the problem and have found the exact same problem you are talking about. I have sent this to our engineering department to see if they can get this error fixed. Hopefully there will be a software update out eventually to fix this error, however I do not have an estimated time of when this will be done."
While I won't hold my breath, at least they're working to appease me.
terms | privacy | contactCopyright © 2006-2019