<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;CUYNQns9eCp7ImA9WhBaEUU.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363</id><updated>2013-05-21T19:39:53.560-05:00</updated><title>For What It's Worth</title><subtitle type="html">I'll be sharing my views on the world of travel-related technology, GPS, satellite navigation and other Android, iPhone and iPad apps.  Along the way, I'll throw in commentary on things that cross my mind.</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://jkcarp.blogspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>31</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/blogspot/nrDSI" /><feedburner:info uri="blogspot/nrdsi" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry gd:etag="W/&quot;AkEGQH8zcCp7ImA9WhBbGEU.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-3022399854459780946</id><published>2013-05-18T09:00:00.001-05:00</published><updated>2013-05-18T09:50:21.188-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-18T09:50:21.188-05:00</app:edited><title>Rand McNally "Good Sam" RVND 7725-LM GPS - First Impressions</title><content type="html">I just received my new Good Sam RVND 7725-LM GPS powered by Rand McNally. I am going to share some initial thoughts and first impressions with you today. After a road test in a couple of weeks, I will post some more impressions after that longer use.&lt;br /&gt;
&lt;br /&gt;
The 7725 is a new model, sold through Camping World only, as far as I can tell. It is branded as Good Sam on the bottom left of the GPS, but otherwise seems nearly identical to the Rand McNally branded 7720. &amp;nbsp;Whether there is any advantage to buying the 7725 over the 7720 remains to be seen. The fact is, in the online forums at least, no one seems to know. The 7725 curiously, is no where on Rand McNally's website, even in the support section. That is a little disconcerting.&lt;br /&gt;
&lt;br /&gt;
I have a long history with personal navigation devices. &amp;nbsp;A long one. I also travel a lot, both for business and pleasure. I estimate approximately 25,000 miles per year on the road in some form - almost of all of which is with some sort of navigation device (or smartphone software) running. &amp;nbsp;I have a GPS on all the time, especially in later years as solutions like Google Maps, TomTom and Waze use my driving to feed its predictive traffic database. Over the years, I have owned and used the following products: Garmin SP III, SP 2710, SP 2730, Garmin i5, Garmin c330, Garmin 760, Garmin 885T, Dash Navigation, TeleNav for Sprint, TomTom 740 Live, CoPilot Live v8, Navigon for Android, Navigon for iPad, Google Navigation, Waze, Garmin Nuvi 3490LMT, Garmin 3590LMT, Scout by Telenav, TomTom for Android, Rand McNally 7725LM. &amp;nbsp;I've used each of those over the years, at least for one trip at a minimum.&amp;nbsp;&lt;b&gt;&lt;i&gt;eBay is a wonderful thing!&lt;/i&gt;&lt;/b&gt;&lt;br /&gt;
&lt;b&gt;&lt;i&gt;&lt;br /&gt;&lt;/i&gt;&lt;/b&gt;
I guess you could say that I am still searching for my perfect solution - no one has nailed it yet. The RVND 7725 will NOT be that perfect solution, but I knew that before I ever bought it. I purchased it with my expectations in check.&lt;br /&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;/div&gt;
This blog post is not going to walk through each screen or explain the use of each feature in detail. Rand McNally has a very good&amp;nbsp;&lt;a href="http://www.randmcnally.com/support/documents/rv-gps" target="_blank"&gt;user guide&lt;/a&gt; (use the one for the 7720) that does a great job of explaining everything this unit does. &amp;nbsp;I'll focus on what is not written and share my initial impressions.&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;/div&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://4.bp.blogspot.com/-wIToUrVj-wY/UZaxMzF6QKI/AAAAAAAAVbM/CHSPzcDLyF4/s1600/2013-05-17+11.15.57.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" height="240" src="http://4.bp.blogspot.com/-wIToUrVj-wY/UZaxMzF6QKI/AAAAAAAAVbM/CHSPzcDLyF4/s320/2013-05-17+11.15.57.jpg" width="320" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;Branding of the 7725 on the box&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;br /&gt;
The 7725 is packaged in a solid box with a premium feel to it - no rattles or other signs of unsecured parts flying around in there. Immediately upon opening the box a "quick start" guide is available. Nice approach. There is a thick layer of&amp;nbsp;Styrofoam&amp;nbsp;before you reach the GPS itself, which is then packed inside of a thin Styrofoam bag within a form-fitting egg crate type shell. &amp;nbsp;Well packaged and presented. &amp;nbsp;Underneath the GPS itself is another egg crate with preformed areas that house the windshield mount, AC power cord, DC power cord and USB cable.&lt;br /&gt;
&lt;br /&gt;
This is a big device. I knew that. I knew I was buying a 7" GPS but when I opened it I still laughed a little about how big it is. This is also a rugged looking device. This is not going to win any beauty awards in the design department. It isn't an elegant &lt;a href="http://images.pcworld.com/images/article/2012/06/google_nexus_7-2-11378965.jpg" target="_blank"&gt;7" tablet&lt;/a&gt;. This device is bulky, thick and somewhat gaudy, down to the bright orange power button, a color which seems totally unnecessary given how obvious the button is to begin with. &amp;nbsp;The average consumer knows how to operate those little smartphone and tablet power buttons. Certainly they can operate this massive power button without it being bright orange.&lt;br /&gt;
&lt;br /&gt;
The actual GPS material is nice. It is that cross between rubber and plastic that will immediately be familiar to anyone with lots of experience in smartphone cases. It is hard to explain to those unfamiliar with it, but I like the texture.&lt;br /&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;/div&gt;
&lt;table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://2.bp.blogspot.com/-UFaF6O3LEj0/UZaxNHRPKjI/AAAAAAAAVbQ/KEjGRa7liWs/s1600/2013-05-17+11.21.01.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" height="240" src="http://2.bp.blogspot.com/-UFaF6O3LEj0/UZaxNHRPKjI/AAAAAAAAVbQ/KEjGRa7liWs/s320/2013-05-17+11.21.01.jpg" width="320" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;Size comparison to standard office pen&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://3.bp.blogspot.com/-M11itraZZps/UZaxP6IZSnI/AAAAAAAAVbk/-acLvH8eNC0/s1600/2013-05-17+11.21.37.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" height="240" src="http://3.bp.blogspot.com/-M11itraZZps/UZaxP6IZSnI/AAAAAAAAVbk/-acLvH8eNC0/s320/2013-05-17+11.21.37.jpg" width="320" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;Yes, this is one thick GPS&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
I also ordered the Rand McNally 7" GPS case. It gets the job done and looks decent. No issues with the case at all. Below is the 7725 mounted inside the case. &amp;nbsp;There appears to be room for the DC adapter. Putting the AC adapter in this case is not going to happen.&lt;br /&gt;
&lt;br /&gt;
&lt;table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://3.bp.blogspot.com/-M5lUijUpoL4/UZaxRWdvK5I/AAAAAAAAVb0/tw-Djn3gZSE/s1600/2013-05-17+11.25.58.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" height="240" src="http://3.bp.blogspot.com/-M5lUijUpoL4/UZaxRWdvK5I/AAAAAAAAVb0/tw-Djn3gZSE/s320/2013-05-17+11.25.58.jpg" width="320" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;Rand McNally 7" GPS accessory case (sold separately)&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;div&gt;
I find the screen to have a good level of brightness when mounted in my car. Our RV is a Class C so with the cab over, I can't imagine having any concerns with the screen at all. I have not owned a previous Rand McNally GPS so I can't compare this to others. I have read complaints though, from owners of previous models. All I can say is that I don't have any concerns. &amp;nbsp;The picture below does not do the screen brightness justice. The screen is brighter than in the photo below.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://2.bp.blogspot.com/-OKyKH2jE52E/UZaxS0wf71I/AAAAAAAAVb8/aEUuNvcJm7E/s1600/2013-05-17+16.37.04.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" height="240" src="http://2.bp.blogspot.com/-OKyKH2jE52E/UZaxS0wf71I/AAAAAAAAVb8/aEUuNvcJm7E/s320/2013-05-17+16.37.04.jpg" width="320" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;Screen brightness in a car&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;div&gt;
I experienced no technical issues with the startup or setup of the 7725. Rand McNally doesn't do a good job of explaining whether to connect the GPS to the computer &lt;i&gt;before&lt;/i&gt;&amp;nbsp;installing the PC Dock software or after. However, when installing the PC Dock software, if the GPS isn't connected to the computer, eventually the installation will tell you that a GPS must be connected to continue. There was a small update available that took 10 seconds to apply to my newly shipped GPS. However, the area within the Dock software that is for update release notes simply said "this is the area where update release notes will be displayed." &amp;nbsp;Not helpful for the update that was just provided.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
When I registered the device and connected it to the Dock software, the Dock software knows the content and version numbers of what is on my GPS. It would be nice if Rand McNally associated that information with my registration email address to proactively notify me every time there is something new in the Dock software to update. However, I have seen no evidence that this is the case, so I will plan on blindly connecting the 7725 to the Dock software periodically and certainly before every trip.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
OK - let's talk about shortcomings. &amp;nbsp;All of these items are things that I knew about before buying so I can't complain. However, based on my previous GPS experience I miss them and the 7725 not having them caused me to think long and hard about buying it.&lt;/div&gt;
&lt;div&gt;
&lt;ol&gt;
&lt;li&gt;No voice recognition. &amp;nbsp;It seems like a premium GPS sold in 2013 ought to have this. &amp;nbsp;I knew it didn't. I bought it anyway. But I find it annoying that it doesn't come with it, especially for use in a RV.&lt;/li&gt;
&lt;li&gt;Lack of traffic included. I knew this too, but I find it petty that the 7725 doesn't come with the lifetime traffic receiver. The&amp;nbsp;Magellan RoadMate RV9165T-LM includes lifetime traffic at this same price point. Rand McNally should have included traffic at this price point.&lt;/li&gt;
&lt;li&gt;Lack of&amp;nbsp;Bluetooth&amp;nbsp; The weather feature is nice and it seems well implemented. What I find incredibly shortsighted is that this feature only works over WIFI. The fact that it &lt;i&gt;does&lt;/i&gt; work over WIFI is great, don't get me wrong. The issue is that it doesn't work over&amp;nbsp;Bluetooth.&amp;nbsp;It seems clear that many PND's such as Garmin Smartphone Link and Magellan SmartGPS, and many telematics solutions like Toyota Entune and others have gone the route of sharing a smartphone's data connection over&amp;nbsp;Bluetooth&amp;nbsp; This costs the customer nothing and it supplies a robust pipeline of data to the GPS. Rand McNally not including this functionality was almost a deal breaker for me.&lt;/li&gt;
&lt;/ol&gt;
&lt;div&gt;
&lt;b&gt;Immediate Dislikes&lt;/b&gt;&lt;/div&gt;
&lt;div&gt;
&lt;b&gt;&lt;br /&gt;&lt;/b&gt;&lt;/div&gt;
&lt;div&gt;
First of all, I &lt;i&gt;hate&lt;/i&gt;&amp;nbsp;the mount. I mean I despise it. &amp;nbsp;The mount itself is sturdy, built decent (as far as plastic builds can go) and is fully adjustable for any conceivable mounting situation. &amp;nbsp;However, when it comes to usability, it earns an 'F' and almost earned a chuck out the window on my first day of ownership. &amp;nbsp;Now, to be fair, if you want to mount this GPS and never move it again, then this mount is just fine. &amp;nbsp;In fact, it probably works well for that. However, I do not ever leave my GPS device visible&amp;nbsp;on the windshield when parked (even when going into a restaurant or truck stop). &amp;nbsp;Once I get the mount set in the perfect position and angle I want to leave the mount alone. I will remove and replace the GPS from the mount when I park and leave the vehicle unattended. &amp;nbsp;This mount is a &lt;i&gt;disaster &lt;/i&gt;if that is your mode of operation.&lt;/div&gt;
&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://3.bp.blogspot.com/-4A5g4inA088/UZaxQE02rNI/AAAAAAAAVbo/PZh26B_hmaU/s1600/2013-05-17+11.23.40.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" height="320" src="http://3.bp.blogspot.com/-4A5g4inA088/UZaxQE02rNI/AAAAAAAAVbo/PZh26B_hmaU/s320/2013-05-17+11.23.40.jpg" width="240" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;The 7725 mount. Well made and sturdy.&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;div&gt;
Here is the problem with the mount. The mount itself uses a large flat plastic "plate" which slides into a mating "slot" on the GPS. You have to line up the plate with the slot perfectly, in two planes, then slide the GPS down onto the plate and lock it in place. It is a nice secure fit. However, this is not a task that is easy to do blind. If the windshield mount stays on the windshield such that you can't see whether you've got the plate lined up with the slot (in two planes) then good luck trying to remount the GPS onto the windshield mount. &amp;nbsp;In addition, this is not a powered mount. The USB power cable plugs directly into the GPS itself, directly out of the back of the unit. Again, it is not easy to plug in the power cable blind.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://2.bp.blogspot.com/-dUbSgcrTFRM/UZaxTHOv6lI/AAAAAAAAVcA/JlIu7WoMLdI/s1600/2013-05-17+17.09.32.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" height="320" src="http://2.bp.blogspot.com/-dUbSgcrTFRM/UZaxTHOv6lI/AAAAAAAAVcA/JlIu7WoMLdI/s320/2013-05-17+17.09.32.jpg" width="240" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;Mate the GPS slot to the mount's plate. Don't try this without a direct view.&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;div&gt;
Removing the GPS from the mount requires some force. You must break the GPS free from the mount by sliding it in the reverse direction such that the GPS slot disengages from the mount's plate. It takes some force to overcome this tight fit and requires two hands. It takes a force such that a few times I've broken the windshield mount's suction from the windshield.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
I've owned this device for one day and that is all it took to know that this mount isn't going to meet my needs. There is no way that I am going to fight with trying to attach the GPS to the mount blind every time I go into a store or truck stop. Nor am I going to remove the suction cup mount in its entirety from the windshield every time.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
So, I added to my purchase cost and purchased a &lt;a href="http://www.rammount.com/Products/XGriptradeMounts/XGriptrade7TabletMounts/tabid/4690/Default.aspx" target="_blank"&gt;RAM Mounts X-Grip mount for tablets&lt;/a&gt;. &amp;nbsp;I already have this mount for my smartphone and it is stunningly awesome. &amp;nbsp;I look forward to using it with the 7725, despite the fact that it increased my purchase price by $45.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://1.bp.blogspot.com/-PAPzlJvQt28/UZdvU0XC19I/AAAAAAAAVcU/bwGFn_GNrU0/s1600/ramholun8iu2a.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" height="320" src="http://1.bp.blogspot.com/-PAPzlJvQt28/UZdvU0XC19I/AAAAAAAAVcU/bwGFn_GNrU0/s320/ramholun8iu2a.jpg" width="274" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;RAM Mount X-Grip Tablet mount&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;div&gt;
&lt;b&gt;Some First Impressions&lt;/b&gt;&lt;/div&gt;
&lt;div&gt;
&lt;b&gt;&lt;br /&gt;&lt;/b&gt;&lt;/div&gt;
&lt;div&gt;
Having to acknowledge the Warning and Legal Consent screen every single time I turn the device on is lame. &amp;nbsp; The lawyers from Garmin, Google and TomTom don't seem to think that this is necessary. &amp;nbsp;Someone needs to go slap the Rand McNally attorneys upside the head and remove this annoyance in a future update.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
I love the fact that this device has predictive traffic, powered by Navteq. It remains to be seen how robust this traffic content is compared to TomTom IQRoutes. Navteq is definitely in catch-up mode on this. However, predictive traffic is a crucial feature for a modern GPS and I am glad to see it in this device. &amp;nbsp;I was surprised to see that the predictive traffic slow downs appeared on the map by coloring coding the roads. This is a nice touch. &amp;nbsp;I will combine my use of the 7725 with a more robust traffic solution (either Google Navigation or TomTom for Android) while on the road. The 7725 will use its predictive traffic for general route planning purposes while Google Nav or TomTom will assist with the real world live traffic should something develop&amp;nbsp;en route. I think it is a good combination.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
It is extremely annoying that my selection of turning predictive traffic on doesn't stick through a power cycle. Every single time I turn on the device I have to turn predictive traffic back on. Annoying and unnecessary. Please fix this Rand McNally.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
I like the layout of the screen. The screen is huge and there are a lot of pieces of information presented around the screen, but there is still a massive amount of screen left for the map. &amp;nbsp;I don't share the complaints others have voiced online about the busyness of the screen or the map being too small. &amp;nbsp;I've also found that the autozoom function works well so far in my limited use of the device today.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
The male voice is significantly better than the female voice in my opinion. The female voice is too robotic but the male voice improves on that significantly. &amp;nbsp;I find the speaker to be a very good quality sound with a volume range that is more than adequate.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
We know that this device has Navteq for the maps. As far as quality, it doesn't get better than Navteq for built-in maps. What we don't know is what vintage these maps are. Additionally, Rand McNally's&amp;nbsp;archaic&amp;nbsp;policy of only releasing one map update per year will do nothing but help ensure that maps remain 18 months to 2 years old on this device at best.&amp;nbsp;Quarterly&amp;nbsp;map updates should be provided on this device like most competitors but I knew that wasn't the case when I bought it and I still bought it.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
I was really surprised to see the way Rand McNally implemented WIFI. If I have WIFI on and connected to a WAP, when I turn the GPS off (or let it turn off when turning the ignition off), &lt;i&gt;they do not enable WIFI and reconnect to the WAP when power is restored&lt;/i&gt;. What? EVERY time you turn the device on you have to enable WIFI again in the settings and reconnect to the WAP. That is unbelievably annoying. WIFI should stay on once I turn it on and it should reconnect to the WAP when the GPS is turned back on. &amp;nbsp;Has anyone at Rand McNally ever used a WIFI tablet before?&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Concerning the WIFI, it is used for the weather content. I really wish Rand McNally would have used the WIFI for more robust traffic content as well. The separate, external Rand McNally traffic receiver gets slammed in online reviews. Plus, it is old school RDS traffic anyway. I find it frustrating that this device isn't being supplied traffic content using HD Radio or better yet online through WIFI. Navteq has traffic available in both of these more robust formats. Rand McNally has chosen to use neither. This seems like a very short-sighted design decision. &amp;nbsp;Let's hope that a future update brings us more robust traffic through the WIFI connection.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
I like the fact that the device announces whether your destination is on the right or the left. &amp;nbsp;Navteq data makes this possible. &amp;nbsp;Nice touch.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
I like the easily accessible slide-out menu that shows you an overview of your route. There is an option button at the bottom of this screen that shows you your route in different ways including an overview map. I wish Rand McNally would allow us to set one of these views as a default for the slide-out menu. I &lt;i&gt;always&lt;/i&gt;&amp;nbsp;check an overview map on any GPS to ensure the route that the device picked passes the smell test. I wish that this overview map could be set as my personal default for the route detail slide-out menu.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
I like the fact that this GPS has packed in a lot of little niceties such as warnings for state line crossings, speed limit changes, time zone changes, curves and more. My family loves to take pictures of state welcome signs as we travel, so this will be a nice feature to have. I've read some online reviews about these features having inconsistent performance (alerting on some curves but not on worse curves) so it remains to be seen after more extended use how well this is implemented.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
The RV database seems pretty robust and is likely the reason most people buy this unit. It contains a wealth of information about each location. One disappointment is that it doesn't seem to have local, city camping locations, even those that have hookups.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
I like the inclusion of a directional compass on the map. This is something that I think Garmin is insane for never including on their GPS devices.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
I've run many test routes from my home. In&amp;nbsp;&lt;i&gt;every &lt;/i&gt;case so far the 7725 has selected the "right" route as I see it. This is especially true for one of my big "test routes" which separates the men from the boys for PND routing. That route is the route from Des Moines, IA to St. Louis, MO. &amp;nbsp;I've written an &lt;a href="http://jkcarp.blogspot.com/2012/01/navigation-test-1-route-8-products.html" target="_blank"&gt;extensive blog post&lt;/a&gt; about why this route is a great test route. I am glad to see that the 7725 nailed this route, both in the route selected as well as the ETA. &amp;nbsp;That is good news. &amp;nbsp;In other tests where I personally feel a non-interstate route is best, but an interstate route is also&amp;nbsp;available&amp;nbsp;as a close temptation, the 7725 seems to be more in line with my thinking by picking the non-interstate route. I've always felt like the Rand McNally website does a good job with route selection and ETA so I am glad to see that the 7725 behaves much like the website in this regard.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
While I appreciate that the 7725 has route preferences to avoid things like tollways and gravel roads, I wish that it would give you these options on a route-by-route basis. I hope that Rand McNally will change this feature to act more like TomTom. After TomTom calculates a route, it prompts you with "This route contains a tollway (or dirt road). Would you like to use it or avoid it?" &amp;nbsp;When I am familiar with the route, there are times when I want to avoid a tollway and times when I want to take the tollway. &amp;nbsp;I'd like to quickly tell the unit my choice on a route-by-route basis instead of having to change a preference setting. &amp;nbsp;For example, if I am traveling from Indiana to the east coast, I may desire to avoid the Ohio turnpike. Upon route calculation, it would be nice to be asked whether I want to avoid tollways or not and have the unit recalculate taking US-30 instead. &amp;nbsp;Other times, say if I am using the device in my car and driving from the KOA West Chicago into downtown, I'd answer "yes, use the tollway" in that scenario.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Navteq data has car pool lanes available in the dataset. Garmin uses that data. Since the 7725 has a car mode and can be used in a toad or rental car, I wish that it also had car pool lane information. When driving in a major city using or avoiding car pool lanes can produce a major change to the route selected and the ETA, especially when the unit already has predictive traffic. &amp;nbsp;I hope the Rand McNally adds this feature.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;b&gt;Conclusion&lt;/b&gt;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
I am looking forward to getting this device out on the road in a couple weeks on our first RV trip of the season. I am glad that when I do, I will have the RAM Mount X-Grip to replace the awful mount that comes with the 7725. &amp;nbsp;I will be glad to have route planning that is using Navteq's predictive traffic content as well as (what appears so far at least) to be Rand McNally's pretty good routing and ETA algorithm that is similar to my positive experience with their website directions. I'll be happy to be able to advance plan my trip in the multi-stop route planner. I'll be pleased to execute the trip with a unit where the volume level will easily overcome all of the road noise of a RV.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
I will look forward to having a weather overlay on the map while I navigate but be cussing Rand McNally every time that I have to enable WIFI and reconnect to the WAP when the 7725 turns on. This frustration will be equaled only by the&amp;nbsp;frustration&amp;nbsp;that I'll have as I start out on my journey only to realize that the map isn't being shown yet because I haven't stroked the Rand McNally attorney's ego yet by&amp;nbsp;acknowledging&amp;nbsp;the legal garbage &lt;i&gt;every&lt;/i&gt;&amp;nbsp;time I turn the device on.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
I'll drive down the road wishing that I had Bluetooth and wishing that my wife had a Rand McNally Android or iPhone app so she could be searching the POI database while I drive and pushing a stopover or destination to my 7725 over Bluetooth while I drive. &amp;nbsp;I won't regret not buying the Magellan SmartGPS for this feature but I will wish that my 7725 had it.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
And I'll be using my 7725 with my smartphone running either Google Navigation or TomTom for Android to ensure I have more current maps and the most up-to-date live traffic to augment what the 7725 thinks it wants me to do. &amp;nbsp;Current maps and live traffic content will not be a strength of the 7725, I know that and I'll work around that until / if Rand McNally decides to improve that for us.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
When I return from my trip in early June, I'm sure that I'll find that the 7725 worked pretty well, with a few drawbacks - much like my feeling about the device when I decided to buy it. &amp;nbsp;We'll see!&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/EdXkPVqtLAY" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/3022399854459780946/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2013/05/rand-mcnally-good-sam-rvnd-7725-lm-gps.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/3022399854459780946?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/3022399854459780946?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/EdXkPVqtLAY/rand-mcnally-good-sam-rvnd-7725-lm-gps.html" title="Rand McNally &quot;Good Sam&quot; RVND 7725-LM GPS - First Impressions" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/-wIToUrVj-wY/UZaxMzF6QKI/AAAAAAAAVbM/CHSPzcDLyF4/s72-c/2013-05-17+11.15.57.jpg" height="72" width="72" /><thr:total>1</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2013/05/rand-mcnally-good-sam-rvnd-7725-lm-gps.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk8DRn47eCp7ImA9WhBSEkU.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-1835863712207900571</id><published>2013-02-19T08:41:00.000-06:00</published><updated>2013-02-19T08:41:17.000-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-02-19T08:41:17.000-06:00</app:edited><title>These retrans disputes are so confusing. I've asked Sinclair and the NAB for help!</title><content type="html">Another day, another retrans dispute using customers as pawns in the chess game played by corporate conglomerates.&amp;nbsp; Since these retrans disputes are so confusing, I've reached out to Sinclair and NAB and asked them for their assistance.&amp;nbsp; I really hope they help me!&lt;br /&gt;
&lt;br /&gt;
&lt;blockquote class="tr_bq"&gt;
I need some assistance from you in determining which cable provider to use. You see, in August 2012 Sinclair indicated that I should switch from Dish Network because they were treating you bad. Since there is nothing more important in my life than the Fox programming that Sinclair provides, I listened! Thanks for being my guiding light. I switched from Dish Network that day and went to DirecTV, because in August 2012 they were apparently being nice to you. But now I read in February 2013 that DirecTV isn't being nice to you anymore. That stinks because I just switched to them 6 months ago when they were being nice to you and Dish wasn't. But hey, I guess it is cool that Dish is being nice to you again now. I'm glad you guys made up in these last 6 months because things seemed really bad in August 2012 between you two.&lt;br /&gt;
&lt;br /&gt;
But now I am so confused!&amp;nbsp; I am just not sure who to switch to now. Can you please tell me who is being nice to you so that I can switch to them? I also have an option of Mediacom in my area.&amp;nbsp; But I read that in 2006 AND 2009 they weren't being nice to you either. That agreement will probably be up soon and I am afraid that when it is up THEY won't be nice to you either. This is all so confusing. I don't have access to Suddenlink, Time Warner or Comcast, but even if I did I probably shouldn't pick them either because I've read that none of them were nice to you in 2006, 2007 and 2010. Darn it all.&amp;nbsp; All of these providers are so mean to you guys. I just don't understand it. And it is so confusing to me because I just don't know who to select as my provider now. It is clear to me that since you have been involved in at least 8 retrans disputes in 6 years that the providers must be colluding against you. Clearly all of those companies are bad and you guys are good. I just need some help from you to determine which of those companies are "less bad" so that I can watch TV. Thanks Sinclair. You guys are awesome!&lt;/blockquote&gt;
&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/cjFY_orc0ew" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/1835863712207900571/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2013/02/these-retrans-disputes-are-so-confusing.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/1835863712207900571?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/1835863712207900571?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/cjFY_orc0ew/these-retrans-disputes-are-so-confusing.html" title="These retrans disputes are so confusing. I've asked Sinclair and the NAB for help!" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2013/02/these-retrans-disputes-are-so-confusing.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0cNQnc8fyp7ImA9WhNWEkg.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-6531380335189207438</id><published>2012-12-11T13:44:00.001-06:00</published><updated>2012-12-11T13:44:53.977-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-12-11T13:44:53.977-06:00</app:edited><title>Copy2Contact's Ridiculous Apple vs Android Blog Post</title><content type="html">I was pretty surprised today to see a &lt;a href="http://www.copy2contact.com/blog/746/race-between-ios-android-not-even-close" target="_blank"&gt;blog post&lt;/a&gt; today by &lt;a href="http://www.copy2contact.com/" target="_blank"&gt;Copy2Contact&lt;/a&gt; with a 5th grade playground "my Dad is bigger than your Dad' post taking sides in the iOS vs Android debate.&amp;nbsp; I mean, really?&amp;nbsp; What kind of business potentionally alienates, on purpose, half of their customer base with nonsense unrelated to their core product?&amp;nbsp;Choice can't be left to choice?&amp;nbsp; &lt;br /&gt;
&lt;br /&gt;
But as I read their post by an unnamed author I was stunned at the amateur arguments and opinions-disguised-as-facts approach to the blog post.&amp;nbsp; As a personal customer of Copy2Contact back when it was Anagram (and still a customer today), I found myself, for the first time since they acquired me as a customer, thinking "who are these boneheads?"&amp;nbsp; And for importantly, would I give them any more of my money with this kind of amateur nonsense?&amp;nbsp; That is a bit harsh, but seriously, read their piece and decide for yourself.&amp;nbsp; I HOPE that this was a bait piece, in an attempt to simply draw traffic to their site.&amp;nbsp; If they actually employ someone this void of deductive reasoning skills then heaven help them.&lt;br /&gt;
&lt;br /&gt;
My house has the following: 5 iPods (1 original and 4 Touch's across 3 generations), an iPad 1, an iPhone 4S, 1 Android tablet and 3 Android smartphones, plus two laptops and a desktop.  I get technology. &lt;br /&gt;
&lt;br /&gt;
So forgive me while I roll my eyes at an author that admits just starting to "dabble" (his word) in Android this year and then goes on to lecture us about the two platforms and superiority of one of them. &amp;nbsp; Reminds me of the 50 First Dates mentality.&amp;nbsp; Live with both options for a couple years and then come back to us with an opinion that is relevant.&lt;br /&gt;&lt;br /&gt;Now, let's dissect this blog post piece by piece and decide for yourself if you want to do&amp;nbsp;business with a company this insanely shortsighted about their opinions on technology.&lt;br /&gt;&lt;br /&gt;This author believes in being "open-minded when it comes to technology." And then he proceeds to use his experience in "dabbling" in one type of technology as the basis for his self-important declaration about the superiority of the one he prefers.  Pure nonsense.&lt;br /&gt;&lt;br /&gt;He compares using Android to using Windows (vs Mac) and reinstalling the OS countless times or tinkering with anti-virus software.  Well, I get to live with 4 post-iOS5 devices that WILL NOT upgrade the OS via USB on an Intel i5 with 8 GB RAM. They won't. They wipe the devices, then fail, all of them (WIPED), EVERY time, with a USB error that Apple swears is the computer's problem. Nevermind the GPS devices, Android devices, printers, external drives, my Fitbit, 2 digital cameras,  and my kids talking donkey toy, all of which don't seem to have a problem with that same computer and that same USB port.  But you are probably right. It has to be my computer's problem.  Sure.  And I am sure it was user error when I had to put my iPad and 2 different gen2 iPod's in airplane mode and back to get the WIFI to work after the device was dormant for awhile.&lt;br /&gt;&lt;br /&gt;"For users that want to have the best phone possible, Android’s deals with half a dozen different manufacturers makes that impossible."  I simply cannot make sense of that statement. I have no idea what that is supposed to mean.  Here is my sentence:  "For users that want to have the best phone possible the user walks into the store and buys the best phone possible."  Manufacturers make cheap garbage phones and they make rock stars like the Galaxy S3 or Galaxy Note 2. If you want the best phone possible YOU BUY IT. If I want a Galaxy Note 2, the fact that there is a cheap Chinese android phone for sale in the next aisle MEANS NOTHING TO ME.  This is just a bonehead comment.&lt;br /&gt;&lt;br /&gt;Then he follows it up with this whopper: "there is a good chance a better version of your Android phone will be released by a different manufacturer within weeks or months of your purchase."  Um, no, not really.  There was 1 year between the original HTC EVO and the Samsung Galaxy.  It took 2.5 years to get from the original Galaxy to the Galaxy S3.  Several high end Motorola devices came out in that year (YEAR, not week). The Galaxy S3 has been out for 10 months now and there is no apparent successor yet.  The Galaxy Note 2 came out 10 months after the S3 and 1.1 years after the Note 1.  This comment is factually inaccurate and ignorant.&amp;nbsp; What was the lifespan between the iPad 3 and the iPad 4 by the way?&lt;br /&gt;&lt;br /&gt;"Want to upgrade your iOS 5 to iOS 6? No problem."  Oh really?  Want to explain to us how to upgrade my iPad 1 to iOS6?  Please.  Hear that?  It is called fragmentation in iOS. Now, without question fragmentation in Android is more robust but spare us the idea that it is non-existent in Apple land.&amp;nbsp; Oh and thanks for the iPad fragmentation too, otherwise known as the "press this icon to blow up your app 2x because we don't have another strategy until the developer writes a different app specifically for this device."&amp;nbsp; Fragmentation.&amp;nbsp; Look it up.&lt;br /&gt;&lt;br /&gt;I love this one. In his discussion comparing app stores, he says "But when you go into the Apple store, you never get malware."  Really?  http://www.wired.com/gadgetlab/2012/07/first-ios-malware-found/&amp;nbsp;&amp;nbsp; What is that you say? Yes, it is&amp;nbsp;malware in the app store. Yes, real, factual, credible information FROM JULY. More flat out factual inaccuracies from this writer.&lt;br /&gt;&lt;br /&gt;"I’m big on securing business data and the lack of checks in the Android environment simply puts your data at too much risk."  What an amateur.  First of all, connecting an Android smartphone to a corporate Exchange server gives the Administrator complete control over the device.  Has this author even READ the permissions that are granted when an exchange server connection is initiated on the device for the first time?  Obviously not.  But let's not stop there.  Here is a cute article *FROM 2010* about the Device Policy feature set added to Android in version 2.2 (yeah, 2.2). (http://www.addictivetips.com/mobile/administer-control-android-phones-with-google-apps-device-policy-app/).  Let's also not forget about one of many third party security solutions that can be added on top of these other two things AT THE USER AND COMPANY's DISCRETION.  Do you understand the word discretion?  It means the USER AND COMPANY get to decide - not Apple.&lt;br /&gt;&lt;br /&gt;Next, on to the rant about the "junk" in the app store when entering a search by app function instead of app name.  For kicks I entered the search "take notes by hand."  I searched the Google Play store.  I got 1000 results and the first ten were: Handrite Note Free, Antipaper Notes, ListNote, TT Note, Free Note, Jotter, Note Stacks, My Script, Jot It and Notebooks.  But it really does piss me off that I had to jump over all of that garbage to find the few apps that were really relevant to what I wanted to search for.&amp;nbsp; Damn you Google.&amp;nbsp; And I am just SURE that the first 3 of 4 of those are actually Chinese hackers that will steal my thumb print from the phone the next time I touch the screen.&lt;br /&gt;
&lt;br /&gt;
In the Apple store I got "No results for "take notes by hand.""  But I am sure that I just didn't "search right."  At least Apple was there to protect me against downloading a non-approved app for taking notes by hand. I feel protected now.&lt;br /&gt;&lt;br /&gt;"Every phone is also preloaded with a ton of bloatware from whatever manufacturer you chose."  Um. No.  Try this press release from *A YEAR AND A HALF AGO* when Sprint announced removal of preloaded apps on current phones and no more preloaded apps on future Android phones.  http://community.sprint.com/baw/community/sprintblogs/announcements/blog/2011/07/08/did-you-know-sprint-allows-removal-of-most-preloaded-apps-on-htc-evo-3d    But, I am sure that in a year and half you just didn't have time to read that press release.  You likely were still pondering the deep thought that went into this blog post.&amp;nbsp; This is a CARRIER decision, not Google's decision.&amp;nbsp; Really? Are you that uninformed?&lt;br /&gt;&lt;br /&gt;And I LOVE this one:  "Searching for ways to get my Android phone to work the way I wanted, I headed straight to Google, where the only suggestions were that I “root” the phone. Is it too much to ask that the phone be ready out of the box?"  Notice no examples were provided?  Hey uninformed blog author: give us three example of ways you can make your iPhone "work the way you want" without jailbreaking that you cannot do on an Android phone without rooting?  Just three.  Go.&lt;br /&gt;&lt;br /&gt;Then we get to the "iOS is far more intuitive" comment.  You know, an opinion that is stated as a fact without providing any examples?  Here is an example of that intuitiveness.  Just suppose I want to do something nuts like send an email to someone and attach any file on my phone, whether in internal memory, or the SD card and send it to someone.  I know - that is far out.  How is that working out for you on your iOS device?  Just browse to the SD ca.....oh, yeah, nevermind.  Well, browse on your internal memory for the file that you transferred to your iPhone by hard connecting it via USB and performing a full phone synchronization (you know, like you did on that Palm Pilot device in 1994).  Oh, I know, you didn't want to transfer the 1GB movie from iTunes right now in order to transfer that 50KB work related file, but iTunes knows best, right?.  So go ahead and open your email program and attach that document.  What?  You mean that document type isn't one of the Apple sanctioned document types that you can attach to an email?  OK. Well Apple must know best.  That can't be an important file type to begin with then.  Go ahead and change what you needed to do because it was clearly wrong. See how intuitive that was?&lt;br /&gt;&lt;br /&gt;And then he closes with the predicable "battery life and speed" comparison.  Except that the two blogs referenced were written in September. Better recheck the phones that are referenced as the "fastest" and the "most battery life" since it is almost three months later.&lt;br /&gt;
 &lt;br /&gt;
This Apple vs Android war perpetuated by these ridiculous bloggers is nonsense.  To each his own and that is why we have personal choices.  Imagine the ego that it takes to declare one's personal technology choice as superior to anothers.  Add to that the factual inaccuracies noted above and you've got a bad case of a guy that seems to be trying really hard to find an audience for attention.&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/VIBzhrHDLPo" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/6531380335189207438/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/12/copy2contacts-ridiculous-apple-vs.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/6531380335189207438?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/6531380335189207438?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/VIBzhrHDLPo/copy2contacts-ridiculous-apple-vs.html" title="Copy2Contact's Ridiculous Apple vs Android Blog Post" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><thr:total>1</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/12/copy2contacts-ridiculous-apple-vs.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkYDQXo8fip7ImA9WhJRFUU.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-855326346521348410</id><published>2012-07-17T21:49:00.002-05:00</published><updated>2012-07-17T21:56:10.476-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-07-17T21:56:10.476-05:00</app:edited><title>Garmin Smartphone Link v1.3 - More problems</title><content type="html">If you spend a few minutes reading my past blog posts, you'll see a history of documented problems with Garmin Smartphone Link.  Unfortunately, tonight, with the v1.3 update, it is more of the same from Garmin.&amp;nbsp;
&lt;br /&gt;
&lt;br /&gt;
The phrase that ought to strike fear in every Garmin executive (and shareholder) is "good enough."  In other words "Google Navigation is &lt;i&gt;good enough&lt;/i&gt;."  Or "Waze is &lt;i&gt;good enough&lt;/i&gt;."  You could even preface the comment with "It's no Garmin, &lt;i&gt;but&lt;/i&gt;..."&lt;br /&gt;
&lt;br /&gt;
Those apps move closer to be "good enough" for mainstream consumers in the following ways:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;Garmin continues to try to sell a dedicated navigation device for the same price as a Samsung Galaxy S3 smartphone or for MORE than a Google Nexus 7.&lt;/li&gt;
&lt;li&gt;The features of Google Navigation (or Waze or others) continues to improve while Garmin continues to artificially restrict software features on existing models to protect future hardware sales.&amp;nbsp;&lt;/li&gt;
&lt;li&gt;Garmin becomes a pain in the ass to deal with.&lt;/li&gt;
&lt;/ol&gt;
&lt;br /&gt;
Tonight, I have arrived at #3.&lt;br /&gt;
&lt;br /&gt;
I've moved on from the Smartphone Link problems that I've described in detail in my blog.  I've moved on from the ridiculous amount of effort it took for me to spoon feed the details of their problems to someone at Garmin that actually knew what Smartphone Link was.  I was willing to forgive and forget.  Then they do it again.  They release v1.3 tonight and what do you know - more problems.&lt;br /&gt;
&lt;br /&gt;
Smartphone Link v1.2 worked fine for me today on 3 different occasions.  I updated to v1.3 tonight while enjoying the pot roast sandwich at Culver's (you should try it - it is good!)  I jumped back into my car and the little Smartphone Link icon turned blue, the Smartphone Link icon on my Nuvi appeared and I was off - driving home.&lt;br /&gt;
&lt;br /&gt;
Except....the temperature on my Nuvi was listed as "--" instead of the ridiculously hot 99 degrees that it is here.  I went to the weather app on my Nuvi and I was greeted by an advertisement telling me all the great features of Advanced Weather.  I know.  I already bought it (&lt;a href="http://jkcarp.blogspot.com/2012/03/garmin-completely-unresponsive-to.html"&gt;twice actually&lt;/a&gt;).&lt;br /&gt;
&lt;br /&gt;
I go to the Smartphone Link services icon on my phone and low and behold, all 4 services that I own and already used today are now shown with a price tag.  My "subscribed services" are blank.  As is typical with an in-app purchase, sometimes you have to let the app and the server communicate so that the server can tell the app "hey, app - this guy already purchased this feature - light it up for him chief."  Except, I couldn't find a way to do that in the app.&lt;br /&gt;
&lt;br /&gt;
I picked the cheapest service: "Advanced Weather" for $4.99 and selected purchase.  I figured that I'd get into the process deep enough that at some point the server would inform the app that I purchased it already.  Then I see the email notification from Google.  I got a fresh, new, shiny $4.99 in-app charge.&lt;br /&gt;
&lt;br /&gt;
I decided that I'd uninstall the Smartphone Link app and reinstall it.  Maybe it was just a glitch.  Upon reinstalling it, now I find even the $4.99 that I just purchased 2 minutes ago is no longer listed as subscribed.  It too now shows up in services that I can purchase.&lt;br /&gt;
&lt;br /&gt;
Since this is an in-app charge, there is no 15 minute return policy.  I have to deal with Garmin.

Well, I've &lt;a href="http://jkcarp.blogspot.com/2012/03/garmin-completely-unresponsive-to.html"&gt;been down that road before&lt;/a&gt;.  Garmin, to this day, has never responded to double billing me.  NOW, they have triple billed me.&lt;br /&gt;
&lt;br /&gt;
So I call Garmin support on the phone.  Guess what.  They are only open from 8am - 6pm Monday through Friday.  I'll be damned if I am going to take time off from work to sit in my car to trouble shoot their sloppy software development.&lt;br /&gt;
&lt;br /&gt;
So for me, tonight, Garmin has officially fallen into #3 above - being a total pain in the ass to deal with.&lt;br /&gt;
&lt;br /&gt;
I bit the bullet on #1 above - buying a $399 Nuvi after not owning one since the 885T.  I've lived with my 3590 rebooting multiple times per week (yes, even after the latest firmware).  Now I officially regret my purchase.  Tonight it just crossed the threshold into "not worth it" territory.  Google Navigation became "good enough" for me. Tonight I can see myself looking back on this day referring to the last Garmin I ever purchased.&lt;br /&gt;
&lt;br /&gt;
Garmin should be better than this.  Their products are priced at a premium.  They are the world leader in consumer navigation.  These sloppy problems should come from the #3 or #4 company in the industry, or the free app guys - not the supposed top player.  Garmin should quit using their customers as beta testers.  And they ought to try providing a 2012 level of customer service.  Social media can be used for more than promoting your racing team you know!&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/RnRioXoSoEg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/855326346521348410/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/07/garmin-smartphone-link-v13-more-problems.html#comment-form" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/855326346521348410?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/855326346521348410?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/RnRioXoSoEg/garmin-smartphone-link-v13-more-problems.html" title="Garmin Smartphone Link v1.3 - More problems" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><thr:total>2</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/07/garmin-smartphone-link-v13-more-problems.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkIBSXg6cSp7ImA9WhJREkU.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-5941850086017473621</id><published>2012-07-14T12:53:00.000-05:00</published><updated>2012-07-14T12:55:58.619-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-07-14T12:55:58.619-05:00</app:edited><title>Mapquest for Android - How does it stack up?</title><content type="html">In my never ending quest to find the right navigation solution for my needs, I've been spending some time with the Mapquest app for Android.&lt;br /&gt;
&lt;br /&gt;
The map has a lot to offer as well as some things that it needs to improve on. &amp;nbsp;Here is a quick look:&lt;br /&gt;
&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;Full voice guidance including text-to-speech, auto-reroute, auto map rotation.&lt;/li&gt;
&lt;li&gt;The use of your own TTS engine rather than a lower quality bundled TTS engine like you'll find in Waze for example. &amp;nbsp;For those of us that have purchased a higher quality TTS engine like SVOX, we can use our SVOX voices within Mapquest. &amp;nbsp;This also allows you to benefit from the&amp;nbsp;pronunciation&amp;nbsp;correction features of SVOX. &amp;nbsp;If a street name is pronounced wrong, just change it's&amp;nbsp;pronunciation&amp;nbsp;in SVOX! &amp;nbsp;Thanks Mapquest!&lt;/li&gt;
&lt;li&gt;Voice search is provided, using the Google voice input feature.&lt;/li&gt;
&lt;li&gt;Multi-step routing. &amp;nbsp;This is a great feature that is missing from Google Navigation. You can enter multiple stops in your route. &amp;nbsp;Mapquest needs to take this to the next level and allow us to save, edit and recall planned trips.&lt;/li&gt;
&lt;li&gt;A robust traffic feed is in the app and comes from Inrix, a respected name in traffic content. &amp;nbsp;In my mid-market region of 500,000 people the Inrix feed is by far the most robust content of any traffic source on any device. &amp;nbsp;The traffic feed includes incident &amp;amp; flow data updated every 5 minutes.&lt;/li&gt;
&lt;li&gt;The map is interactive meaning that you can long-press anywhere on the map and route to that point or save it as a favorite. &amp;nbsp;But unfortunately, it doesn't appear that the map has any auto zoom capability based on the distance to the next turn.&lt;/li&gt;
&lt;li&gt;Mapquest has included a great use of Android shortcuts. &amp;nbsp;This allows you to add a one-touch icon to your home screen (or within a folder on your home screen) that is "pre-configured" to a specific destination address. &amp;nbsp;When you press this icon, Mapquest opens and begins navigating to that destination without further user intervention.&lt;/li&gt;
&lt;li&gt;Android calendar and contact integration. When you press an address in your calendar, contacts, a 3rd party app or a website, if you have your navigation default preferences cleared in Android then Mapquest is one of the options to receive the address. &amp;nbsp;This passes the address directly to Mapquest from the source app without requiring the user to enter it or copy and paste it.&lt;/li&gt;
&lt;li&gt;Mapquest's ETA seems very good. &amp;nbsp;My biggest complaint about Google Maps is their very conservative ETA's. &amp;nbsp;Mapquest seems to be right on with their ETA calculations.&lt;/li&gt;
&lt;/ol&gt;
&lt;div&gt;
The Mapquest app has improved greatly from its initial launch but it still has a ways to go. &amp;nbsp;Here are some things that need work in this app.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;ol&gt;
&lt;li&gt;Voice search requires an extra step that shouldn't be necessary. &amp;nbsp;When you speak a search the Mapquest app uses voice recognition only to populate the search box with text. &amp;nbsp;It doesn't actually execute the search. &amp;nbsp;Therefore, the user has to touch the search button. &amp;nbsp;This is an unnecessary step while driving. &amp;nbsp;Contrast that to Google Navigation. When you speak a search, Google receives your voice, translates it to text and automatically executes the search. &amp;nbsp;If it isn't sure or there are multiple options, you are presented with a "Did you mean:" box of options. &amp;nbsp;Mapquest needs to remove this&amp;nbsp;unnecessary&amp;nbsp;step from its voice input workflow.&lt;/li&gt;
&lt;li&gt;The text size used for street names in the Mapquest app is simply unusable and I have a 4.7" smartphone screen. &amp;nbsp;Both Google and Waze do a much better job with the readability of the street name text. &amp;nbsp;This remains the biggest downfall with the Mapquest map in my opinion. &amp;nbsp;When I navigate in an unfamiliar area, even though there is turn by turn guidance, I like to compare the street signs with the streets I see on the map to get a better feel for how many more blocks I have before my turn. This is impossible with the Mapquest app because of their problem display the text of street names.&lt;/li&gt;
&lt;li&gt;Despite having a robust traffic feed from Inrix in the app, and despite Mapquest telling us that they use that data in determining routes and ETA's, to date, I have not found any evidence that Mapquest ever shows the user any indication of the impact of the traffic. &amp;nbsp;In other words, if there is traffic and it is impacting my ETA, Mapquest should tell me that. &amp;nbsp;Google does this by a simple black, red, yellow or green light. &amp;nbsp;ALK, in their CoPilot product, also using Inrix traffic, has perhaps the best implementation of this with their traffic bar on the side of the screen. &amp;nbsp;Not only does it tell you the traffic situation but does so graphically in a way that represents the distance the traffic is away from you. &amp;nbsp;If Mapquest is going to use this traffic content, I want to see how it is using it and impacting my route when I use the app.&lt;/li&gt;
&lt;li&gt;The Mapquest app has no ability to show you multiple route options. &amp;nbsp;Everyone: Google Navigation, Waze, Telenav, Navigon and ALK has this now and it needs to be in the Mapquest app.&lt;/li&gt;
&lt;li&gt;While the Mapquest app is integrated with contacts and calendar, it is not integrated with apps like Vlingo. &amp;nbsp;Mapquest can do this by themselves without Vlingo's cooperation. &amp;nbsp;On my Android home screen, when I long-press the search button it starts the Vlingo recognition app. &amp;nbsp;I can then speak "Navigate to 123 Main St, Anytown, USA." &amp;nbsp;Since I've cleared my navigation defaults, I am prompted by Android to pick an app to carry out my navigation request. &amp;nbsp;In that list is Google Navigation, Telenav and Garmin Smartphone Link (used with my Nuvi over bluetooth). &amp;nbsp;Mapquest needs to register this app within Android in a way that puts it on that list. &amp;nbsp;For the record Waze hasn't figured this out yet either.&lt;/li&gt;
&lt;li&gt;Mapquest, like Telenav does, needs to leverage their online website and link it to their navigation app. &amp;nbsp;We should be able to define favorites, search and select destinations and create routes on the Mapquest website, all of which we should be able to send to the Mapquest app. &amp;nbsp;Mapquest is behind Google and Telenav in this regard.&lt;/li&gt;
&lt;/ol&gt;
&lt;div&gt;
Here are some questions that I'd love for Mapquest to answer:&lt;/div&gt;
&lt;/div&gt;
&lt;div&gt;
&lt;ol&gt;
&lt;li&gt;Is Inrix used for real time traffic only or do your ETA's take historical traffic into account?&lt;/li&gt;
&lt;li&gt;Does the use of the app send data back to Inrix for purposes of real time flow determination?&lt;/li&gt;
&lt;li&gt;How does the deal with TomTom for map data impact the ETA? &amp;nbsp;Are you getting only raw map data from TomTom or does the data include IQRoutes data which then impacts the Mapquest ETA?&lt;/li&gt;
&lt;/ol&gt;
&lt;/div&gt;
&lt;div&gt;
I like the Mapquest app. &amp;nbsp;It has potential to be a good app, especially given its quality ETA calculations and great Inrix traffic feed but it has some things it needs to improve on.&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/00gStB1kAKU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/5941850086017473621/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/07/mapquest-for-android-how-does-it-stack.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/5941850086017473621?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/5941850086017473621?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/00gStB1kAKU/mapquest-for-android-how-does-it-stack.html" title="Mapquest for Android - How does it stack up?" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/07/mapquest-for-android-how-does-it-stack.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkYHQXg9eCp7ImA9WhVaFkg.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-4727601461457564526</id><published>2012-06-14T00:02:00.001-05:00</published><updated>2012-06-14T00:02:10.660-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-06-14T00:02:10.660-05:00</app:edited><title>My take on the Apple Maps announcement</title><content type="html">There has been a ton of speculation about the Apple Maps announcement this week. &amp;nbsp;The announcement was perhaps the worst kept secret of the event. &amp;nbsp;Everyone knew it was coming. &amp;nbsp;Google and Apple have a huge need for you to use their phones for your location based activities so that eventually when the mobile advertising market grows up, they can capitalize. &amp;nbsp;What better way to capture your location based activities than to create a robust app that navigates you whether driving, walking, biking, or using public&amp;nbsp;transportation. &amp;nbsp;Neither Google or Apple could care less about the navigation itself. &amp;nbsp;They care about &lt;u&gt;&lt;i&gt;knowing about&lt;/i&gt;&lt;/u&gt; your navigation. &amp;nbsp;And therefore, both have now planted both of their feet firmly in the navigation app space. &amp;nbsp;The only way to do it, they believe and I agree, is to provide a robust navigation app that will be your go-to solution for all forms of personal navigation so they have a constant opportunity to serve you mobile ads.&lt;br /&gt;
&lt;br /&gt;
What does this Apple announcement mean? &amp;nbsp;No one knows for sure but here are my thoughts.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;&lt;u&gt;TomTom&lt;/u&gt;&lt;/b&gt;&lt;br /&gt;
No one knows the details of the relationship between Apple and TomTom for sure, other than the very short press release that TomTom released. &amp;nbsp;The only fact that we know is that Apple is using TomTom's maps (TeleAtlas actually - owned by TomTom). What we do &lt;i&gt;not&lt;/i&gt;&amp;nbsp;know is:&lt;br /&gt;
&lt;br /&gt;
1) Did Apple only buy the underlying mapping data from TomTom (TeleAtlas) and Apple built their own UI on top of that underlying mapping data?&lt;br /&gt;
2) Is the routing algorithm TomTom's or Apple's? &amp;nbsp;If TomTom's, does it use IQRoutes data?&lt;br /&gt;
3) Will Apple's crowd sourcing feed back into TomTom to support TomTom's IQRoutes feature?&lt;br /&gt;
4) Will Apple's crowd sourcing traffic feature feed back into TomTom's traffic service?&lt;br /&gt;
&lt;br /&gt;
If Apple only bought "dummy" map data from TomTom then in my opinion TomTom sold it's soul to the devil because of it's reportedly precarious financial position. Apple has a lot to prove in terms of their ability to develop their own routing algorithm and ETA calculations if they are not using TomTom's. &amp;nbsp;Only after consumer use of the new app will we know for sure how good they are at this new game.&lt;br /&gt;
&lt;br /&gt;
I've said many times that TomTom's main remaining value in the US is it's intellectual property: IQRoutes and HD Traffic. &amp;nbsp;Those two services need users, and lots of them, or these features wither and die. &amp;nbsp;Without users, TomTom cannot sustain the accuracy and timeliness of these features. &amp;nbsp;And without those features, TomTom has little to offer the US consumer that is unique. &amp;nbsp;TomTom already missed the boat badly in the US by not expanding their user base by adding Android users.&lt;br /&gt;
&lt;br /&gt;
We know that Apple has announced that the Apple Maps app will feature crowdsourced traffic. &amp;nbsp;What we do not know if is if it will also contain historical traffic. &amp;nbsp;If it &lt;i&gt;does&lt;/i&gt;, this would presumably&amp;nbsp;&lt;i&gt;have&lt;/i&gt;&amp;nbsp;to be TomTom IQRoutes because Apple has no history in this space by which to have any historical traffic data. &amp;nbsp;If it does not use historical data at product launch, then Apple has a long way to go to catch up to their competitors. &amp;nbsp;Not having historical traffic data would be a bad sign for those hoping that the Apple Maps app will be back feeding TomTom's IQRoutes and HD Traffic.&lt;br /&gt;
&lt;br /&gt;
If Apple's app&lt;i&gt;&amp;nbsp;&lt;/i&gt;is &lt;i&gt;not&lt;/i&gt;&amp;nbsp;back feeding TomTom's IQRoutes and HD Traffic then that is a clear sign of the trouble that TomTom is in in my opinion. &amp;nbsp;Apple clearly has the user base to build up their own data that would resemble IQRoutes and HD Traffic. &amp;nbsp;It would take them several years, less in larger cities, but they clearly have the user base to build it like no one other than Google can. &amp;nbsp;It would appear that Apple does not necessarily &lt;i&gt;need&lt;/i&gt;&amp;nbsp;TomTom, except for a short term jump start. &amp;nbsp;Clearly the release of Apple Maps will cause a significant reduction in sales of TomTom's own iPhone app. &amp;nbsp;There would be little to justify the expense. &amp;nbsp;If Apple is &lt;i&gt;not&lt;/i&gt;&amp;nbsp;using IQRoutes or HD Traffic, then those features would remain as selling points for TomTom's own app, but that advantage will be short lived as Apple builds up their own data. &amp;nbsp;And Apple's own app will likely simply be more fun to use anyway, further drawing users away from TomTom's own paid app. &amp;nbsp;The Apple app will be integrated with Siri and you can bet that Apple will nail the UI.&lt;br /&gt;
&lt;br /&gt;
If Apple Maps is not feeding back into TomTom IQRoutes and HD Traffic then those features, in my view, are dead in the US. &amp;nbsp;Apple Maps will drastically draw users away from TomTom's own apps, their PND's are already in deep decline. &amp;nbsp;There simply do not appear to be enough users out there using IQRoutes and HD Traffic "feeder devices" to make those features viable.&lt;br /&gt;
&lt;br /&gt;
After all of that explanation and speculation my prediction is that Apple buys TomTom.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;&lt;u&gt;Garmin&lt;/u&gt;&lt;/b&gt;&lt;br /&gt;
Garmin's public comment downplaying the impact of Google Maps screams of a historical 800 pound gorilla still trying hard to be seen as the major player it once was in the industry. &amp;nbsp;Garmin is positioning itself as the "premium" player in a market of less-featured free or freemium solutions. &amp;nbsp;The problem with that strategy, as I pointed out in previous blog posts, is that their so called premium devices are typically full of "half baked" features that never seal the deal. &amp;nbsp;They get their devices 85% right in my view, but never finish the 15% of the features that would truly put it over the top, justify its high cost, and make it too good to pass up. &amp;nbsp;Instead, they are onto developing another 10 skus of product, end-of-life'ing devices after 12 -16 months and trying to convince me to pay another several hundred dollars for the next "latest and greatest" device. &amp;nbsp;Fool me once Garmin....Actually you fooled me twice, I just bought a 3590 after owning nothing since the 885. &amp;nbsp;Not sure there is another Garmin device in my future that I can see.&lt;br /&gt;
&lt;br /&gt;
Garmin is the only major player left that is at the mercy of a twice removed company for its core foundation - the maps. &amp;nbsp;Garmin is at the mercy of Navteq, who is in the hands of Nokia, for its maps, a problem that no other player has. &amp;nbsp;Part of Garmin's premium justification is Navteq maps - once the clear premier mapping provider. &amp;nbsp;In the hands of Nokia, I am not sure Navteq remains in that position long term.&lt;br /&gt;
&lt;br /&gt;
The future of Garmin's app on the iPhone seems destined to niche status, perhaps only for those customers sophisticated enough to know that they want Navteq maps and are willing to pay the fee, or for customers that still are blindly brand loyal to Garmin.&lt;br /&gt;
&lt;br /&gt;
Garmin has no play in the Android space. &amp;nbsp;Google will continue to exert pressure on Garmin and Garmin simply has no answer. &amp;nbsp;Smartphone Link (Garmin's Android app that mates to a Nuvi via bluetooth) appears to be a lightly used niche app as evidence by the download numbers. &amp;nbsp;For the record, I use the app and love it.&lt;br /&gt;
&lt;br /&gt;
Garmin's problem with Smartphone Link however is that it holds my phone hostage because of its use of my bluetooth connection. &amp;nbsp;That means I can't use a bluetooth headset, I can't use the bluetooth phone feature of my car and I can't use the bluetooth telematics feature in my car with its in-dash apps. &amp;nbsp;Am I willing to give that up long term just to maintain my Garmin Nuvi? &amp;nbsp;No. &amp;nbsp;Smartphone Link is Garmin's Android v2.0 strategy and I think this will also be&amp;nbsp;short lived, like the phones they tried a couple years ago.&lt;br /&gt;
&lt;br /&gt;
Garmin seems only to be able to compete by convincing customers that premium PND's are the way to go. &amp;nbsp;I don't see a competent and sustainable go-forward strategy yet from them to compete in a smartphone dominated world.&lt;br /&gt;
&lt;br /&gt;
My prediction: &amp;nbsp;Garmin buys Navteq from Nokia and tries to position themselves as the premium map set and the premium navigation solution. &amp;nbsp;They may get smart about developing an Android app and continue their iPhone app development and also position their apps as the premium answer to the free alternatives. &amp;nbsp;Whether they have enough features to truly differentiate and justify their premium cost remains to be seen.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;&lt;u&gt;Google&lt;/u&gt;&lt;/b&gt;&lt;br /&gt;
Frankly, I don't see Google impacted much by Apple Maps. &amp;nbsp;I don't see that iPhone users make up a significant portion of Google's crowdsourcing user base. &amp;nbsp;I don't see that Google's data will miss these users much. &amp;nbsp;I also don't think Apple Maps will convert any significant quantity of Android customers. &amp;nbsp;I just don't see that Apple Maps provides any advantage over Google Maps. &amp;nbsp;I think that iPhone customers will remain iPhone customers and Android customers will remain Android customers. &amp;nbsp;There is no doubt though that there will be a huge competition between Google and Apple to see who has the best navigation app to attact new users. &amp;nbsp;This is a win-win for consumers. &amp;nbsp;We can expect great strides from both players as they try to one-up each other.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;&lt;u&gt;Inrix&lt;/u&gt;&lt;/b&gt;&lt;br /&gt;
I don't know what to think about Inrix. &amp;nbsp;I like their app and I like their traffic content, but I never use their app. &amp;nbsp;Why? &amp;nbsp;Because knowing the existence of traffic is only part of the equation. &amp;nbsp;I want to know what to &lt;i&gt;do about it&lt;/i&gt;&amp;nbsp;and their app (at least for Android) doesn't tell me that. &amp;nbsp;Frankly, the Inrix app is just not an app that will get my attention on my phone right now. From what I know, I don't see that Inrix has any role in either Google or Apple in this new smartphone navigation app battle. &amp;nbsp;I am not&amp;nbsp;knowledgeable&amp;nbsp;enough about their business relationships to comment on what role Inrix has going forward that would have a direct consumer impact.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;&lt;u&gt;Others&lt;/u&gt;&lt;/b&gt;&lt;br /&gt;
I don't consider the other players worth spending much time on at this point. &amp;nbsp;This is clearly a Google versus Apple battle. &amp;nbsp;Players like Waze offer a unique solution. &amp;nbsp;But I can't see them offering a compelling enough case to draw customers away from Google or Apple in enough quantity to create critical mass for their own crowdsourced apps. &amp;nbsp;I see Waze as a small niche player that will drawn numbers similar to Open Street Map or Mapquest. &amp;nbsp;Actually, I would bet good money that Waze will be&amp;nbsp;acquired&amp;nbsp;at some point.&lt;br /&gt;
&lt;br /&gt;
ALK, TeleNav, Sygic, NDrive and the others have no upside in my view. &amp;nbsp;There is just no compelling story here for any of them to justify not using Google or Apple. &amp;nbsp;Once the general public gets a taste of the power of crowdsourced historical and real time traffic, these small niche players that don't have that data will have a hard time making a case for their app. &amp;nbsp;Perhaps the inclusion of Inrix data in some of these apps will continue to be a compelling enough drawn for some people that are smart enough in this industry to know the difference and care but I have a hard time seeing a long term business case for these other players.&lt;br /&gt;
&lt;br /&gt;
The same goes for the small PND players like Magellan, Rand McNally, etc. &amp;nbsp;These players will turn into niche suppliers for specific industries like trucking, RV/Motorhomes, etc.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;&lt;u&gt;Conclusion&lt;/u&gt;&lt;/b&gt;&lt;br /&gt;
Who knows? &amp;nbsp;How is that for a conclusion? &amp;nbsp;We all talk smart about what will happen but the truth is that none of us know. &amp;nbsp;I see:&lt;br /&gt;
&lt;br /&gt;
1) Google continuing down their current path, crowdsourcing map data, using their users as probes for their historic and real time data, and using field vehicles primarily for streetview.&lt;br /&gt;
&lt;br /&gt;
2) Apple will get a few months into their Apple Maps app and determine their confidence in building their own map data (ala Google) including using their users as probes to build their own historic and real time data. &amp;nbsp;If they see roadblocks or think the data is building too slowly, I can see Apple making a play for TomTom to get TeleAtlas. &amp;nbsp;I could also see Apple buying Waze instead to get the technology that Waze has and apply it to the user base that Waze doesn't have.&lt;br /&gt;
&lt;br /&gt;
3) Garmin will remain as the viable premium old-school player in the market, still trying to convince the user base to buy dedicated devices. &amp;nbsp;I can see Garmin making a play for Navteq as a fire sale from Nokia and trying to mold themselves into a services and software company. &amp;nbsp;Their play could be premium map data, not relying much on crowdsourcing, built into premium apps and dedicated&amp;nbsp;premium&amp;nbsp;PND's.&lt;br /&gt;
&lt;br /&gt;
That is my two cents on recent events.&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/qP6LbLh0SG8" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/4727601461457564526/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/06/my-take-on-apple-maps-announcement.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/4727601461457564526?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/4727601461457564526?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/qP6LbLh0SG8/my-take-on-apple-maps-announcement.html" title="My take on the Apple Maps announcement" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><thr:total>1</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/06/my-take-on-apple-maps-announcement.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Ak8CQ3wzeCp7ImA9WhVaEk0.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-7621328175892971927</id><published>2012-06-08T21:27:00.002-05:00</published><updated>2012-06-08T21:27:42.280-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-06-08T21:27:42.280-05:00</app:edited><title>The Case for Incremental Map Updates or "Why Google and Waze might be eating Garmin &amp; TomTom's lunch!"</title><content type="html">&lt;br /&gt;
&lt;div class="MsoNormal"&gt;
Nothing
frustrates a GPS user more than map mistakes. &amp;nbsp;After all, that is what a GPS is supposed to
do – efficiently route you to your destination on a map.&amp;nbsp; Every user has an expectation, as unrealistic
as it is that the maps will always be timely and accurate.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
Rational
users know that maps in your GPS will always and forever be a lagging
technology.&amp;nbsp; The maps will ALWAYS be out
of date.&amp;nbsp; The digital roads will always be
“built” after the physical roads are.&amp;nbsp; Even
though we understand that, it doesn’t make it any less frustrating when we
experience a GPS map error.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
However,
that doesn’t mean that we shouldn’t expect the GPS industry to innovate and
compress the time between the physical road and the digital road.&amp;nbsp; Has the legacy GPS industry done that?&amp;nbsp; Are they resting or are they innovating?&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
Let’s
take a look at the legacy GPS industry – those manufacturers primarily deriving
their consumer revenue by selling hardware.&amp;nbsp;
We know these brands well – Garmin, TomTom, Magellan, etc.&amp;nbsp; These legacy manufacturers sell hardware that
contains digital maps on the device. &amp;nbsp;Contrast that to a company like Google, Waze
or Mapquest that is primarily a software company that serves you the maps
online without dedicated GPS hardware.&amp;nbsp;
(However, with Google’s announcement this week that offline maps are
coming to Google Maps for Mobile, the line will further blur – not good for the
legacy companies.)&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
Let’s
start with a basic undeniable truth. The legacy GPS industry as we know it is
threatened by the smartphone. That pressure is only going to increase not
decrease.&amp;nbsp; Garmin tried to play in the
smartphone market but couldn’t shake the obsession to make hardware.&amp;nbsp; The idea crashed and burned.&amp;nbsp; Now they are trying smartphone idea 2.0 which
is the Garmin Smartphone Link app, which bridges the smartphone to the traditional
PND through a Bluetooth data connection.&amp;nbsp;
The Android Market shows the app has been downloaded between 10,000 and
50,000 times.&amp;nbsp; That is a paltry fraction
of the GPS market (Google Navigation has been downloaded between 100 and 500
MILLION times) so it remains to be seen how long Garmin’s approach will
continue to be supported by development resources.&amp;nbsp; Coincidentally, a smartphone “link” to a PND
was something that TomTom did years ago, but for all practical purposes has
abandoned.&amp;nbsp; In the smartphone space, TomTom
has been available for the iPhone for a while.&amp;nbsp;
But as you know, they have been AWOL on Android despite talking about it
publicly for nearly 3 years now. Time will tell if it is too little, too late
should it ever become available.&amp;nbsp; Garmin
too, has an iPhone app but has shown no signs of making a US app available for
Android.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
This
is not a blog post to discuss the merits of a dedicated GPS versus a
smartphone.&amp;nbsp; There are many things that a
legacy GPS does better than a smartphone.&amp;nbsp;
But there is no question that the legacy GPS is finding itself in a
position of having to justify itself and its cost more and more every day.&amp;nbsp; Why spend $399, $299, $199 or even $99 when a
smartphone solution is “good enough.”&amp;nbsp; The
phrase “good enough” should make Garmin, TomTom and the others cringe!&amp;nbsp; The only thing that the likes of Garmin and
TomTom should be focused on is to make their products so good that the
smartphone solutions &lt;i&gt;aren’t&lt;/i&gt; “good
enough.”&amp;nbsp; Alternatively, they could just
become really great software developers and get firmly in the smartphone app
game.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;
I come back to my opening paragraph and say that one of the things most
important to GPS users is the maps.&amp;nbsp;
Customers want accurate and timely maps.&amp;nbsp;
Garmin could be leveraging their dominance in the industry by providing
an innovative delivery mechanism for their maps. But to date, there is no public
evidence that Garmin is or will do so.&amp;nbsp; And
finally, after a long introduction, that is the subject of my blog post today:
the lack of innovation in the delivery of map updates.&lt;br /&gt;
&lt;!--[if !supportLineBreakNewLine]--&gt;&lt;br /&gt;
&lt;!--[endif]--&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
Take
a look at some advertisements that you see from Garmin or TomTom. You'll see
that they are probably promoting the fact that their products have quarterly
map updates. But, let’s step back.&amp;nbsp; Is
that supposed to be something consumers should be excited about? In 2012?&amp;nbsp; I am not so sure about that.&amp;nbsp; The fact that they still are advertising that
as a feature today, I would argue, points to a lack of innovation in their
industry.&amp;nbsp; They &lt;i&gt;should&lt;/i&gt; be embarrassed by that, not proud.&amp;nbsp; I am not sure that they see it that way
though.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;
The maps that Garmin uses in their GPS devices actually come from a vendor,
Navteq (owned by Nokia).&amp;nbsp; TomTom’s maps
come from TeleAtlas, which TomTom owns. I have absolutely no inside knowledge
of how this works.&amp;nbsp; The following is
complete speculation on my part.&amp;nbsp; I could
be completely wrong on this, but I’ve observed the industry for long enough
that I think I know some of the details of how it works.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
The
quarterly update that you're spending hours downloading and installing tonight isn’t
accurate up to the time the map is released.&amp;nbsp;
There is a lag between the data that Navteq provides to Garmin and the
data that Garmin actually sends out to customers.&amp;nbsp; That seems obvious, but you still see posts
on the Internet from customers complaining that their street was added 6 months
ago – why isn’t it in the map update I just got?&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
There
is an additional lag inside Navteq.&amp;nbsp;
Certainly Navteq faces a “cut off” point in order to prep their data for
delivery to Garmin.&amp;nbsp; And thus the data
that Garmin gets from Navteq is also not the most current data available.&amp;nbsp; It is only the most current data that Navteq
has in &lt;i&gt;deliverable&lt;/i&gt; form.&amp;nbsp; The actual data could be several quarters, to
a year old or more.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;
The other day, I discovered a simple map error.&amp;nbsp;
Within a large intersection, an errant one-way segment was defined.&amp;nbsp; It prevented a simple left turn from one
major road to a US highway.&amp;nbsp; It is the
kind of thing that makes you wonder how the error gets there in the first
place, that intersection hasn’t changed in 10 years, but nonetheless, it is
there. It took me less than 5 min. to correct this error on Navteq’s website. &lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://1.bp.blogspot.com/-e_rhPnhmC_g/T9K0hJSOv2I/AAAAAAAAQiE/0WjATZNyjh4/s1600/Road_Error.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="171" src="http://1.bp.blogspot.com/-e_rhPnhmC_g/T9K0hJSOv2I/AAAAAAAAQiE/0WjATZNyjh4/s400/Road_Error.JPG" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
Five
minutes.&amp;nbsp; The error was fixed, by me, in
five minutes.&amp;nbsp; That, however, is not the
important timeframe to care about.&amp;nbsp; The
question is, how long will I have to wait until that simple 5 minute fix ends
up in my GPS so the maps quit generating a ridiculous work-around at that
intersection?&amp;nbsp; I will bet that I will
wait a year or more before I will see that error actually corrected in my
GPS.&amp;nbsp;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
Waiting
a year for a map error fix that took me 5 minutes to correct online will
ultimately try the patience of the legacy GPS consumer in a smartphone age to
the point that customers, at some point, will simply not put up with it any
more.&amp;nbsp; Again, to sell a $299 PND in a smartphone
age Garmin has to justify that cost, every day.&amp;nbsp;
Waiting over a year for a simple map correction is not a great way to
justify a $299 product cost to your customer.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
If
the legacy GPS companies don’t start thinking and start innovating the delivery
of their maps quicker than they are, I believe that they will continue to lose
ground.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
The
legacy GPS companies might argue that waiting one quarter for map updates is a
great thing, right? After all, it was only two years ago that we were receiving
map updates once per year.&amp;nbsp; And, after
all, if you buy a car with a built in GPS, those updates are still only once a
year.&amp;nbsp; See!&amp;nbsp; The legacy GPS companies ARE being
innovative!&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
How
legacy companies do compared to built-in GPS companies isn’t the relevant
question.&amp;nbsp; The relevant question is how the
legacy GPS companies do in comparison to their REAL competitors – nimble
software-thinking IT-centric companies that would laugh at thinking about the
prospect of only updating their product once a quarter.&amp;nbsp; These competitors are going to eat their
lunch someday if they don’t change their approach.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
In
the time Garmin has continued to offer only quarterly updates, other companies have
been thinking strategically and blowing the quarterly map delivery model out of
the water.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;
Of course I'm speaking about alternative map delivery approaches from the likes
of Google Navigation and Waze.&amp;nbsp; Now, let
me make something perfectly clear before I go on. I am in no way suggesting
that the current iteration of these competing products are best in class or
that they are better products than my current legacy GPS. I do not believe that
they are. But again, that isn’t the question.&amp;nbsp;
The appropriate question is are they “good enough” to not spend another
$299 on a PND and rather, to “settle” for the free alternative.&amp;nbsp; Garmin’s job is to widen the gap to the point
that the answer is no.&amp;nbsp; In my opinion,
Garmin is doing nothing to widen the gap.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
Whether
customers are familiar with Google’s MapMaker map editor or Waze’s editor is
not really the point.&amp;nbsp; I would argue that
most customers also don’t contribute to Navteq’s Map Reporter or TeleAtlas’s
Map Insight editor either.&amp;nbsp; The relevant
point is what happens downstream of those editors and what that means to the consumer.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
Google
and Waze have revolutionized the mapping world by developing a solution that
pushes edited and moderated map changes to the customer quicker than the industry
has ever seen before.&amp;nbsp; As a Google Trusted
Editor for my area, most edits that I map in Google MapMaker are updated &lt;i&gt;instantaneously&lt;/i&gt; in the web version of
Google Maps.&amp;nbsp; THAT is innovation.&amp;nbsp; Those edits find themselves pushed to the
Google Maps for Mobile platform in a couple of weeks.&amp;nbsp; Waze has a similar track record of updates,
making changes available to customers within weeks of the initial edit.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
The
Google and Waze approach sets the bar going forward.&amp;nbsp; It moves the “is it good enough” bar closer
to the free smartphone solutions and away from the dedicated PND.&amp;nbsp; Garmin just sits and lets it happen.&amp;nbsp; In my opinion Garmin is in a bit of a bind.&amp;nbsp; After all, they are using Navteq maps, which
are owned by Nokia.&amp;nbsp; Garmin gets to deal
with the corporate bureaucracy of Navteq &lt;i&gt;and&lt;/i&gt;
Nokia, not to mention the bureaucracy within Garmin itself.&amp;nbsp; The chance of nimble innovation with these
three goliaths is likely too much to ask for frankly.&amp;nbsp; &lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;
TomTom was on the right track, purchasing TeleAtlas so they own both the map
and the delivery mechanism for the maps (the PND and the software).&amp;nbsp; However, looking at the example of TomTom for
Android, TomTom has proven to be no more nimble now than they were when
TeleAtlas was a separate company.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
What
should Garmin do?&amp;nbsp; Here is my
premise:&amp;nbsp; It is INSANE that in 2012, we
are still downloading 2 GB map updates once per quarter.&amp;nbsp; No, I not suggesting that we should be
downloading 2 GB map updates once per month or once per week.&amp;nbsp; I am suggesting that we should be downloading
10 KB or 100 KB or 2 MB map updates once per day, once per week or on whatever
schedule we wish.&amp;nbsp; TomTom is well known
for stating that 18% of the road network changes each year.&amp;nbsp; If that is true, why are we downloading 100%
of the road network every single quarter?&amp;nbsp;
If a single map update is 2 GB that means that only 360 MB of that map
actually changes in a year.&amp;nbsp; Yet, in a
year, if we perform all 4 quarterly updates, we are downloading 8 GB of data to
obtain 360 MB of updates.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
I
have to wait over a year for a small (but important to me) map update to get
incorporated into a massive 2 GB quarterly map update when it could have easily
been pushed to me as a 10 KB map update a couple weeks after I fixed the error
online.&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
Garmin
should be innovating and pushing incremental map updates to customers.&amp;nbsp; Full 2 GB map updates should be history.&amp;nbsp; Incremental map updates would move the bar
further away from the Google Navigation and Waze approaches and breathe life
towards Garmin’s corner in the battle of “is it good enough?”&amp;nbsp; In fairness, TomTom does have their MapShare
program which pushes some incremental map changes to customers.&amp;nbsp; However, we still face a large quarterly full
download every quarter regardless of whether we use MapShare.&lt;br /&gt;
&lt;!--[if !supportLineBreakNewLine]--&gt;&lt;br /&gt;
&lt;!--[endif]--&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;
&lt;div class="MsoNormal"&gt;
Critics will say “you don’t get it.”&amp;nbsp; And you are right, I probably don’t.&amp;nbsp; But I shouldn’t have to either.&amp;nbsp; I am the consumer and it is my $399 that
Garmin is trying to get.&amp;nbsp; Clearly as the
industry leader, Garmin should have the intellectual talent to innovate in
these kinds of ways.&amp;nbsp; What I believe they
lack is the will.&amp;nbsp; The more product
generations that I wait over a year for a small map fix, the less likely it is
that I will spend that $399 again with Garmin.&amp;nbsp;
THAT, I do get.&amp;nbsp; The solutions
from Google Navigation and Waze are very close to “good enough” today and that
gap appears to be doing nothing but closing.&amp;nbsp;
Garmin should be very concerned with that.&amp;nbsp;&lt;o:p&gt;&lt;/o:p&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/FmZoVjfVNzI" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/7621328175892971927/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/06/case-for-incremental-map-updates-or-why.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/7621328175892971927?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/7621328175892971927?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/FmZoVjfVNzI/case-for-incremental-map-updates-or-why.html" title="The Case for Incremental Map Updates or &quot;Why Google and Waze might be eating Garmin &amp; TomTom's lunch!&quot;" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/-e_rhPnhmC_g/T9K0hJSOv2I/AAAAAAAAQiE/0WjATZNyjh4/s72-c/Road_Error.JPG" height="72" width="72" /><thr:total>1</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/06/case-for-incremental-map-updates-or-why.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0IER30_cCp7ImA9WhVbEEg.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-5967608093710795909</id><published>2012-05-26T11:58:00.000-05:00</published><updated>2012-05-26T11:58:26.348-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-05-26T11:58:26.348-05:00</app:edited><title>Garmin - add this feature to this screen please!  Finish it!</title><content type="html">One of the things I've learned after years of using Garmin GPS devices is that the GPS can be trusted 95% of the time. &amp;nbsp;But that last 5% of the time - watch out! &amp;nbsp;Therefore, I always take a quick glance at Garmin's selected route to make sure it makes sense to me. &amp;nbsp;Garmin makes this fairly easy.&lt;br /&gt;
&lt;br /&gt;
1) After a route is calculated, press the horizontal green bar at the very top center of the screen.&lt;br /&gt;
2) An route overview list is shown.&lt;br /&gt;
3) Click on the menu icon in the upper left of the screen.&lt;br /&gt;
4) Click on the word MAP.&lt;br /&gt;
&lt;br /&gt;
Here you will see an overview map of the calculated route.&lt;br /&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://3.bp.blogspot.com/-ggJ-SG3v9ww/T8EGSzExUyI/AAAAAAAAQgk/LxqzD-K6Pkk/s1600/20120526_104832.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="300" src="http://3.bp.blogspot.com/-ggJ-SG3v9ww/T8EGSzExUyI/AAAAAAAAQgk/LxqzD-K6Pkk/s400/20120526_104832.jpg" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
One of my continued critiques of Garmin is that their devices never seem to be completely done in terms of functionality. &amp;nbsp;They never seal the deal. &amp;nbsp;As the industry leader who still tries to push devices at the $399 price point, I expect the devices to be done. &amp;nbsp;Here is a perfect example of being almost-done.&lt;br /&gt;
&lt;br /&gt;
So, here we are shown a nice route overview map. &amp;nbsp;It is relatively easily accessible in 3 clicks from the main navigation screen. &amp;nbsp;Some Garmin devices, this being one of them, includes the ability to be shown multiple routes to your destination. &amp;nbsp;That is a nice feature. &amp;nbsp;But in typical almost-done style, Garmin doesn't connect the dots. &amp;nbsp;What if I don't like the chosen route above?&lt;br /&gt;
&lt;br /&gt;
It would make perfect sense to invoke the multiple route selection feature from this screen. With a simple menu icon in the upper left corner of this screen, we could be provided with a multiple route selection screen complete with ETA, miles and traffic delay on each of the chosen routes. &amp;nbsp;Select one and go!&lt;br /&gt;
&lt;br /&gt;
In fact, no where on a Garmin GPS, once you are navigating a route, can you ever initiate an overview screen of route choices to your destination. &amp;nbsp;Take the example above. &amp;nbsp;There are three perfectly good options to get from Des Moines to Dubuque. &amp;nbsp;There are all within 10 miles and 15 minutes of each other on this 3.5 hour trip. &amp;nbsp; &amp;nbsp;But once you commit to a route, there becomes multiple ways to traverse a &lt;i&gt;portion&lt;/i&gt;&amp;nbsp;of your route after that. &amp;nbsp;Let's say that I commit to the route above. &amp;nbsp;Once I am near Cedar Rapids on I-80, there becomes three legitimate ways to get from &lt;i&gt;there&lt;/i&gt;&amp;nbsp;to Dubuque. &amp;nbsp;As I approach Cedar Rapids, I'd love to regenerate route options quickly to select my preferred route for the remainder of the trip.&lt;br /&gt;
&lt;br /&gt;
The multiple route option feature can only be selected on the initial activation of a route. So to be presented with those options again, you essentially have to select your destination again and start over. &amp;nbsp;Hint: if you select your destination from the History list you can do this quicker.&lt;br /&gt;
&lt;br /&gt;
From the screen above it is &lt;i style="font-weight: bold;"&gt;9&lt;/i&gt;&amp;nbsp;button clicks in order to see route options other than the route shown on the screen. &amp;nbsp;It &lt;i&gt;could&lt;/i&gt;&amp;nbsp;be done in 2 mouse clicks from the screen above if implemented correctly.&lt;br /&gt;
&lt;br /&gt;
Garmin: have the courage to go all the way with your devices. &amp;nbsp;Finish it.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/KVREwIu2WPA" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/5967608093710795909/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/05/garmin-add-this-feature-to-this-screen.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/5967608093710795909?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/5967608093710795909?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/KVREwIu2WPA/garmin-add-this-feature-to-this-screen.html" title="Garmin - add this feature to this screen please!  Finish it!" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/-ggJ-SG3v9ww/T8EGSzExUyI/AAAAAAAAQgk/LxqzD-K6Pkk/s72-c/20120526_104832.jpg" height="72" width="72" /><thr:total>1</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/05/garmin-add-this-feature-to-this-screen.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0cGQHw5fSp7ImA9WhVbEEk.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-2977806531902094894</id><published>2012-05-26T11:17:00.000-05:00</published><updated>2012-05-26T11:17:01.225-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-05-26T11:17:01.225-05:00</app:edited><title>Use your smartphone calendar as a GPS trip planning tool!</title><content type="html">You wouldn't initially think about using your smartphone calendar as a GPS trip planning tool. &amp;nbsp;One of the drawbacks of Google Navigation, or any of the other navigation apps, is that they lack a planning tool. &amp;nbsp;
A trip planning tool is convenient when you are taking a trip that has multiple stops. &amp;nbsp;Various 3rd party apps have been developed to attempt to fill this gap. &amp;nbsp;But no one needs a 3rd party app to do this. Even more powerful is combining your smartphone calendar with your Smartphone Link compatible Nuvi to achieve some great functionality.&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
When we take our motorhome across the US it is not unusual to have a route that might contain 4, 5 or more stopovers including preferred truck stops, overnight campgrounds, or along-the-way sightseeing opportunities. &amp;nbsp;Some of these stops can be somewhat tricky to find, especially remote campgrounds. &amp;nbsp;Once we arrive at our destination, some of our sightseeing locations can be remote and difficult to find as well. &amp;nbsp;While the motorhome gives us freedom, it also allows us to travel to remote areas that can't be navigated to with a standard street address. &amp;nbsp;Trip planning to a series of stopovers with very defined street addresses may not warrant using this method. &amp;nbsp;Users may find it easier to simply write the addresses on an index card and use the voice recognition features of your GPS to input them along your route. &amp;nbsp;However, this method is most useful when your locations can only be described using latitude / longitude. &amp;nbsp;Another example of this is when you want to take a specific route to a destination that you know the GPS won't calculate using the automatic method. &amp;nbsp;The easiest way to do this is to find the latitude / longitude of the center drive lane of the road of interest and enter that latitude / longitude as a stopover point in your route.&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
If you are fortunate enough to have an Android smartphone, a Garmin GPS and Garmin Smartphone Link, I will show you how to use your smartphone's calendar as the ultimate trip planning tool that is especially useful for navigating to even the most remote places in the US. &amp;nbsp;&lt;/div&gt;
&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
This method leverages a little known fact about Google Maps for Mobile. &amp;nbsp;It allows you to pass a latitude / longitude to it from 3rd party apps (like the Calendar app). &amp;nbsp;The format is as follows:&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
loc:&lt;i&gt;latitude&lt;/i&gt;,-&lt;i&gt;longitude&lt;/i&gt;&lt;/div&gt;
&lt;div&gt;
&lt;i&gt;&lt;br /&gt;&lt;/i&gt;&lt;/div&gt;
&lt;div&gt;
There can be no spaces within that syntax. It all runs together, including the comma and the "-" ahead of the longitude. &amp;nbsp;In one of &lt;a href="http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-revolutionary.html" target="_blank"&gt;my first posts&lt;/a&gt; about Garmin Smartphone Link I went into great detail about how you can use the Location field of the&amp;nbsp;smartphone&amp;nbsp;calendar to pass street addresses from your calendar appointments to your Garmin GPS. This technique builds on this wonderful capability and leverages the loc: syntax noted above.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
At this point, some of you may be thinking I am crazy. &amp;nbsp;After all, any Garmin GPS that can use Smartphone Link also has a built-in trip planning tool. &amp;nbsp;True, however, in my experience at least, I have found that Garmin has a horrible track record of preserving the functionality of your trip plan across map updates. &amp;nbsp;So if I am going to spend the time building a trip plan, I am going to build it in something that is fully under my control.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Let's pretend that we want to visit the Grand Canyon. &amp;nbsp;I've read an article about a great scenic view from a place called Toroweap Overlook. Google Earth is a fantastic tool for finding places like this. &amp;nbsp;Here is a view of the location of Toroweap Overlook from Google Earth. The actual location of the lookout is where the small photo icon is located. &amp;nbsp;You can see the road on Google Earth.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;/div&gt;
&lt;table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://1.bp.blogspot.com/-MQB-lcbcC14/T8Dylx_U8gI/AAAAAAAAQZo/-lMFI_a6Ts8/s1600/grand+canyon.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" height="266" src="http://1.bp.blogspot.com/-MQB-lcbcC14/T8Dylx_U8gI/AAAAAAAAQZo/-lMFI_a6Ts8/s400/grand+canyon.jpg" width="400" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;Google Earth location of desired destination&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
A great feature of Google Earth is that&amp;nbsp;wherever&amp;nbsp;you hover your mouse, the latitude and longitude is shown at the bottom of the screen. &amp;nbsp;As you zoom in closer you can get down to a very close level of detail, in this case to what appears to be a turn out along the road. &amp;nbsp;Hover your mouse there and then write down the latitude and longitude. I continue using Google Earth until my entire trip stopovers and all of my sightseeing destinations are found and I've recorded the latitude and longitude. &amp;nbsp;I prefer to put my entire trip in my calendar so I will also keep a list of destinations that include good street addresses as well.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
From here, I move to my calendar. &amp;nbsp;You can perform this step in multiple ways depending on the calendar you use on your phone. &amp;nbsp;You can enter it directly into your phone's calendar, enter it in Outlook if you use Exchange sync or enter it on the web in Google Calendar. &amp;nbsp;I will enter these directly into my Android device's calendar in this example.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
After I've collected all of my trip data from Google Earth, I now enter it into my calendar. &amp;nbsp;Using the calendar has the added advantage of being able to invite friends and family to the appointment, entering the travel itinerary in a way that is time-appropriate, having your work's free/busy functionality be accurate for your trip, etc.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Here is what this appointment looks like in my Android calendar, by putting the loc: syntax discussed above in the Location field of the calendar appointment:&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://2.bp.blogspot.com/-gIvgd68fgzE/T8D35Srv4BI/AAAAAAAAQfU/muacilMVkbk/s1600/20120526_102352.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" height="320" src="http://2.bp.blogspot.com/-gIvgd68fgzE/T8D35Srv4BI/AAAAAAAAQfU/muacilMVkbk/s320/20120526_102352.jpg" width="240" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;Android calendar appointment for travel destination&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
All of the steps discussed above would be performed as a pre-trip, planning activity. &amp;nbsp;Your calendar should be populated with all of the individual locations that you need on your trip on the days and times you plan to travel to them. &amp;nbsp;Once your calendar contains all of your locations, you can head out on your trip.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Now we will discuss what happens on your trip. &amp;nbsp;You should &lt;a href="http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-revolutionary.html" target="_blank"&gt;read this post first&lt;/a&gt; in order to better understand the capabilities of Garmin Smartphone Link.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
When you head to your first destination, open your smartphone's calendar appointment and click on the loc: syntax in the Location field. &amp;nbsp;It should be underlined. &amp;nbsp;This will open Google Maps automatically and zoom into your desired location. &amp;nbsp;You can visually confirm from Google Maps that the location is the same as what you manually found in Google Earth.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://2.bp.blogspot.com/-ojiD7nhRZm8/T8D5niTkAqI/AAAAAAAAQfo/UVkzy40hAyg/s1600/20120526_102531.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" height="300" src="http://2.bp.blogspot.com/-ojiD7nhRZm8/T8D5niTkAqI/AAAAAAAAQfo/UVkzy40hAyg/s400/20120526_102531.jpg" width="400" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;Google Maps for Mobile location of latitude / longitude of destination&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Now, as outlined &lt;a href="http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-revolutionary.html" target="_blank"&gt;in my previous post&lt;/a&gt;, click on the latitude and longitude shown above in Google Maps. &amp;nbsp;Click on the word "Direction" on the next screen. &amp;nbsp;Then click on the blue navigation triangle at the bottom left of the next screen. Select "Smartphone Link" as the fulfillment action. &amp;nbsp;This will pass your location to your Garmin GPS.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Here is the result of this location being passed to my Garmin Nuvi 3590LMT. &amp;nbsp;Notice that the Garmin doesn't include this road, rather the closest known road is the north/south road to the west where the backwards "C" curve is located. &amp;nbsp;This perfectly illustrates that it would be impossible to find and navigate to this specific location without the use of a tool like Google Earth as there is no viable street address.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://3.bp.blogspot.com/-fSFhRI-4iLM/T8D8HNPoVCI/AAAAAAAAQgI/pJm_ERCWhyI/s1600/20120526_104657.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="300" src="http://3.bp.blogspot.com/-fSFhRI-4iLM/T8D8HNPoVCI/AAAAAAAAQgI/pJm_ERCWhyI/s400/20120526_104657.jpg" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
As your travel day or vacation week continues, you simply return to your smartphone calendar for each stop and repeat this procedure. &amp;nbsp;The actual procedure of clicking on the link in the calendar and transferring it to your GPS through Smartphone Link takes about 5 - 10 seconds. Arguably you can't enter a street address manually into your GPS in this amount of time. &amp;nbsp;Even better, your co-traveling companion could do this for you while you drive.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Enjoy this great method of traveling planning. &amp;nbsp;&lt;a href="https://twitter.com/#!/jeffcarp" target="_blank"&gt;Follow me on Twitter&lt;/a&gt; for more.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/j1izlhe6cKs" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/2977806531902094894/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/05/use-your-smartphone-calendar-as-gps.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/2977806531902094894?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/2977806531902094894?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/j1izlhe6cKs/use-your-smartphone-calendar-as-gps.html" title="Use your smartphone calendar as a GPS trip planning tool!" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/-MQB-lcbcC14/T8Dylx_U8gI/AAAAAAAAQZo/-lMFI_a6Ts8/s72-c/grand+canyon.jpg" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/05/use-your-smartphone-calendar-as-gps.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0UHQ3g_fSp7ImA9WhVXGU8.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-27064020654053784</id><published>2012-04-20T07:33:00.001-05:00</published><updated>2012-04-20T07:33:52.645-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-04-20T07:33:52.645-05:00</app:edited><title>Garmin Trip Planner App &amp; ETA's - Disconnected?</title><content type="html">&lt;div&gt;&lt;p&gt;Sometimes the choices that manufacturers make in products just leave me shaking my head. For many of these things I can except the fact that I am not the target customer. I am a power user, but most products are made with the casual user in mind.&amp;nbsp; This particular issue though leaves me shaking my head when I consider the viewpoint of any user of the product.&lt;/p&gt;
&lt;p&gt;The Garmin 3590 is their flagship consumer product. It includes an app called trip planner. Trip planner is a great feature that allows you to build a trip in advance including multiple stopovers and route waypoints.&amp;nbsp; A great option within trip planner is the ability to define a stopped duration time at any of the defined waypoints.&lt;/p&gt;
&lt;p&gt;On Wednesday, I had a need to drive from Des Moines Iowa to Chicago Illinois and back in the same day with only a short 30 minutes stop in Chicago for some quick business.&amp;nbsp; I know, it's insane, but some things just have to be done.&amp;nbsp; There were two very important ETA's in this route. My ETA in Chicago was very very important. In addition I had to be home at a specific time in order to participate in one of my daughters activities.&amp;nbsp; I knew exactly where I would stop for gas and exactly where I would stop for lunch. I built this route within the trip planner app and included the gas station stops as well as lunch and provided stopover times at each of these waypoints. Imagine my surprise when I activated this route and found that Garmin takes none of this stop over time into account into the ETA they present. They do take the additional driving time to get to the waypoint but they do not take the stop time into account. Absolutely insane. &lt;/p&gt;
&lt;p&gt;If I build a waypoint into a route for a gas station, the route planner allows me to tell it that my stop time will be say, 20 minutes. If I am building a cross-country route that I will take in our RV, and I have three gas stops along the way, that is an hour of time that I will be stopped on my route.&amp;nbsp; Using this feature, it allows me to get a more accurate picture of my route that day due to my stops.&lt;/p&gt;
&lt;p&gt;So I am taking the time to build this route and I'm spoon feeding Garmin's routing algorithm the fact that the route will take one hour longer than it should, yet Garmin completely ignores this information. &lt;/p&gt;
&lt;p&gt;I would love to hear the explanation for this one. &lt;/p&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/V3_tzsodWrM" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/27064020654053784/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/04/garmin-trip-planner-app-eta.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/27064020654053784?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/27064020654053784?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/V3_tzsodWrM/garmin-trip-planner-app-eta.html" title="Garmin Trip Planner App &amp;amp; ETA&amp;#39;s - Disconnected?" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/04/garmin-trip-planner-app-eta.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkUNQXs_eCp7ImA9WhVRGUU.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-1374564847851947414</id><published>2012-03-28T21:31:00.002-05:00</published><updated>2012-03-28T21:31:30.540-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-03-28T21:31:30.540-05:00</app:edited><title>Garmin Nuvi 34xx/35xx updates firmware &amp; Smartphone Link - Traffic Problems Solved?</title><content type="html">Today Garmin released&amp;nbsp;&lt;a href="http://www8.garmin.com/support/download_details.jsp?id=5303" target="_blank"&gt;firmware v6.2&lt;/a&gt; for the Nuvi 34xx and 35xx devices, as well as a &lt;a href="https://play.google.com/store/apps/details?id=com.garmin.android.apps.phonelink" target="_blank"&gt;Smartphone Link for Android&lt;/a&gt; app update. &amp;nbsp;The release notes make reference to several Smartphone Link and Traffic improvements that insinuate that perhaps we finally have a fix for an apparent problem that I outlined several months ago in &lt;a href="http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-live-traffic.html" target="_blank"&gt;this post&lt;/a&gt; and &lt;a href="http://jkcarp.blogspot.com/2012/01/further-testing-of-garmin-smartphone.html" target="_blank"&gt;this post&lt;/a&gt;. &amp;nbsp;I won't restate those posts other than to say that the problem was an apparent incompatibility when using both Smartphone Link Live Traffic and the GTM-60 HD traffic receiver.&lt;br /&gt;
&lt;br /&gt;
After updating my Nuvi 3590LMT to v6.2 and upgrading my Smartphone Link for Android app, I set out to determine whether the problems have been solved. &amp;nbsp;Tonight I report that I &lt;i&gt;think&lt;/i&gt;&amp;nbsp;that most of the issues are resolved. &amp;nbsp;I say that I &lt;i&gt;think&lt;/i&gt;&amp;nbsp;they are resolved because there is one little nuance that I observed that I am not entirely sure how to interpret. &amp;nbsp;In addition there remains one issue that appears to still be unresolved. &amp;nbsp;Here we go...&lt;br /&gt;
&lt;br /&gt;
I began this test with Smartphone Link connected and the Nuvi connected to a non-traffic-receiver DC power source. &amp;nbsp;As expected, traffic was received without issue through Smartphone Link.&lt;br /&gt;
&lt;br /&gt;
&lt;table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://3.bp.blogspot.com/-osBthpszC58/T3OsBwDrNlI/AAAAAAAAO-Y/xJLERtey8bE/s1600/20120328_180723.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" height="240" src="http://3.bp.blogspot.com/-osBthpszC58/T3OsBwDrNlI/AAAAAAAAO-Y/xJLERtey8bE/s320/20120328_180723.jpg" width="320" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;Smartphone Link connected, GTM-60 disconnected.&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;br /&gt;I then turned off my smartphone's bluetooth service and turned off the Nuvi. &amp;nbsp;I turned the Nuvi back on with the non-traffic-receiver DC power source to ensure that all knowledge of any traffic detail was gone. &amp;nbsp;I confirmed this by attempting to go to the traffic screen. &amp;nbsp;I was shown this screen:&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://3.bp.blogspot.com/-5XgEAjf8ZTE/T3OslPPp-RI/AAAAAAAAO-g/XE9lku5Hoz4/s1600/20120328_180940.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" height="240" src="http://3.bp.blogspot.com/-5XgEAjf8ZTE/T3OslPPp-RI/AAAAAAAAO-g/XE9lku5Hoz4/s320/20120328_180940.jpg" width="320" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;Bluetooth off / Smartphone Link disconnected / GTM-60 disconnected&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;div&gt;
Next, I connected the GTM-60 while bluetooth was still turned off (thus Smartphone Link disconnected). &amp;nbsp;The Nuvi began to acquire traffic from the GTM-60 as shown in the following screen:&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://3.bp.blogspot.com/-jm1nk9VsqgY/T3OtPL8648I/AAAAAAAAO-w/Q1STnQqlsZE/s1600/20120328_181034.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" height="240" src="http://3.bp.blogspot.com/-jm1nk9VsqgY/T3OtPL8648I/AAAAAAAAO-w/Q1STnQqlsZE/s320/20120328_181034.jpg" width="320" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;Bluetooth off / Smartphone Link disconnected / Obtaining traffic signal from the GTM-60&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;div&gt;
Once the GTM-60 successfully connected to the traffic service, I obtained traffic content. &amp;nbsp;Bluetooth and Smartphone Link are still disconnected. &amp;nbsp;You can be assured that the traffic being received comes from the GTM-60 because of the green signal strength bars at the top of the screen below. &amp;nbsp;These are not present when using Smartphone Link as your traffic source.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://2.bp.blogspot.com/-BSCjVJdCkdg/T3OtnaQ7XxI/AAAAAAAAO-4/jFnwtliuqvc/s1600/20120328_181050.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" height="240" src="http://2.bp.blogspot.com/-BSCjVJdCkdg/T3OtnaQ7XxI/AAAAAAAAO-4/jFnwtliuqvc/s320/20120328_181050.jpg" width="320" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;Bluetooth off / Smartphone Link disconnected / GTM-60 connected&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;div&gt;
So far, everything works as expected. &amp;nbsp;But it worked like this up to this point two months ago too. &amp;nbsp;Now is the step that will test if anything has been fixed from two months ago. &amp;nbsp;With the GTM-60 connected, I will now enable bluetooth and connect Smartphone Link.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://4.bp.blogspot.com/-T_WFGai9D7U/T3OuVGvoczI/AAAAAAAAO_A/4KEz-DBf4Jw/s1600/20120328_181120.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" height="240" src="http://4.bp.blogspot.com/-T_WFGai9D7U/T3OuVGvoczI/AAAAAAAAO_A/4KEz-DBf4Jw/s320/20120328_181120.jpg" width="320" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;Smartphone Link connected / GTM-60 connected&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;div&gt;
Yeah! &amp;nbsp;Unlike what happened two months ago, I received a Traffic Up To Date message from Smartphone Link while the GTM-60 is connected. &amp;nbsp;The traffic incident shown above was short lived and within a couple seconds of seeing this screen, the screen changed to this:&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://2.bp.blogspot.com/-PNxJKYnRW38/T3OvUnhRkTI/AAAAAAAAO_I/VEDW8CR1RHE/s1600/20120328_181524.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" height="240" src="http://2.bp.blogspot.com/-PNxJKYnRW38/T3OvUnhRkTI/AAAAAAAAO_I/VEDW8CR1RHE/s320/20120328_181524.jpg" width="320" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;Smartphone Link connected / GTM-60 connected&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;div&gt;
This is still a positive sign. &amp;nbsp;The GTM-60 is connected. Smartphone Link is connected. &amp;nbsp;I am seeing messages that reinforce that this is working as it should. &amp;nbsp;It is reporting Traffic Up To Date and No Traffic In Area. &amp;nbsp;This reinforces that a signal is being received from Smartphone Link and the content of that traffic signal is no traffic content. &amp;nbsp;However, while observing this screen I find that this screen only lasts a matter of seconds. &amp;nbsp;The screen then switches to the screen below for a significant amount of time (several minutes). &amp;nbsp;The switching from the screen above to the screen below is what makes me unsure that this is working exactly as I'd expect it to be.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;table align="center" cellpadding="0" cellspacing="0" class="tr-caption-container" style="margin-left: auto; margin-right: auto; text-align: center;"&gt;&lt;tbody&gt;
&lt;tr&gt;&lt;td style="text-align: center;"&gt;&lt;a href="http://2.bp.blogspot.com/-Kd0K0S_GaI8/T3OxBI221LI/AAAAAAAAO_Q/EoLpYxUPaTs/s1600/20120328_181134.jpg" imageanchor="1" style="margin-left: auto; margin-right: auto;"&gt;&lt;img border="0" height="240" src="http://2.bp.blogspot.com/-Kd0K0S_GaI8/T3OxBI221LI/AAAAAAAAO_Q/EoLpYxUPaTs/s320/20120328_181134.jpg" width="320" /&gt;&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class="tr-caption" style="text-align: center;"&gt;Smartphone Link connected / GTM-60 connected&lt;/td&gt;&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
&lt;div&gt;
This screen is what makes me unsure about whether this is really fixed or not. &amp;nbsp;This screen is only seen when BOTH Smartphone Link and the GTM-60 are connected. &amp;nbsp;You never see this screen when using only Smartphone Link or only the GTM-60. &amp;nbsp;Garmin needs to be consistent about the messages it presents to the user so that confidence is instilled in the user that the service is working as it should be.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
I must presume how this should be working because Garmin doesn't document the specifics. &amp;nbsp;I presume that there are two aspects of receiving traffic data on this unit. &amp;nbsp;First, you must have a data connection to the traffic server. &amp;nbsp;Garmin has provided us two ways to make this data connection, either using HD Radio through the GTM-60, or using bluetooth through Smartphone Link. &amp;nbsp;Once this data connection is made to the traffic server, then we obtain traffic CONTENT from it.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
When only the GTM-60 is used, Garmin nicely presents the status of the traffic CONNECTION by showing the green signal strength bars at the top of the screen. &amp;nbsp;However, when the Smartphone Link app is used, there is NO confirmation provided to the user that there is a traffic&amp;nbsp;CONNECTION&amp;nbsp;being made. &amp;nbsp;All we know is that there is a bluetooth connection to our phone. &amp;nbsp;That is not the equivalent of the green signal strength bars when the GTM-60 is used. &amp;nbsp;Bluetooth can be connected without there being a connection to the traffic server.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Therefore, when Garmin shows the message above "Waiting for Traffic Data" it leads the user to say "Why?" &amp;nbsp;Why are you waiting for the traffic data? &amp;nbsp;Do you not have communication with the traffic server? Or is this simply the dormant period while the Nuvi waits 2 minutes (or whatever the time is) before it checks for the next traffic message and everything is operating as expected? &amp;nbsp;There is no way for the user to know this.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
One thing left unresolved is the intelligent switching between Smartphone Link and the GTM-60 for users on a 3G CDMA network (Verizon, Sprint and others). &amp;nbsp;On a 3G CDMA network there is no data connection while on a voice call. &amp;nbsp;But when in a voice call, the Nuvi screen shown above never changes. &amp;nbsp;This perpetuates the confusion. &amp;nbsp;When on a phone call on a 3G CDMA network there is no way that the Nuvi will receive traffic data but it continues to say "Waiting for Traffic Data." &amp;nbsp;There is no data connection available on the smartphone. &amp;nbsp;The Nuvi should be intelligent enough to detect the loss of connection to the traffic server from the smartphone and switch to the GTM-60. &amp;nbsp;Instead, the Nuvi sits there "Waiting for Traffic Data" when there is no chance of receiving it until the phone call is over.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
This perpetuates the confusion of the "Waiting for Traffic Data" message when &lt;i&gt;not&lt;/i&gt;&amp;nbsp;on a call. &amp;nbsp;Since it has been shown that this message is displayed while on a phone call when there is no possibility that it could be connected to the traffic server, it gives me no confidence as to whether I am actively connected to the traffic server or not.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
The user should be shown the connection status to the traffic server, the signal strength of that connection (GTM-60 only) and the content of the traffic message. &amp;nbsp;Those three pieces of information permit users to know what is happening with their traffic service at all times.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
One other annoyance remains not addressed in this update. &amp;nbsp;This issue involves Garmin's use of the green traffic icon on the main map display. &amp;nbsp;Consider the following example: &amp;nbsp;you are driving on the freeway between two major cities. &amp;nbsp;You are using the GTM-60 traffic receiver. &amp;nbsp;As you travel between major cities, somewhere in the middle you will be well beyond the reception range of the GTM-60. &amp;nbsp;You are therefore not receiving any traffic content at all. &amp;nbsp;However, because the GTM-60 is simply physically connected to the Nuvi, Garmin displays a green traffic icon on the map. &amp;nbsp;This is inaccurate. &amp;nbsp;A green traffic icon indicates that traffic is clear. &amp;nbsp;The Nuvi doesn't know this however, because it doesn't have a traffic signal at all. &amp;nbsp;The icon should be a gray or similar color to indicate a lack of a traffic signal. &amp;nbsp;Visually, Garmin should not be presenting "No Traffic in Area" the exact same way as not having a traffic signal at all. &amp;nbsp;It is inaccurate and misleading.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Bottom line - it appears that the traffic problems when using both Smartphone Link and the GTM-60 are resolved. &amp;nbsp;However, there is much work that could be done to improve the presentation of this information to the user. &amp;nbsp;And there is an unresolved problem for 3G CDMA users that still needs to be addressed. &amp;nbsp;The majority of CDMA users will not be using 4G (which does allow&amp;nbsp;simultaneous&amp;nbsp;voice &amp;amp; data) until well after the 34xx and 35xx series devices will likely be discontinued. &amp;nbsp;Garmin should fix this 3G CDMA oversight.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/vwpInUnT9_c" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/1374564847851947414/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/03/garmin-nuvi-34xx35xx-updates-firmware.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/1374564847851947414?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/1374564847851947414?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/vwpInUnT9_c/garmin-nuvi-34xx35xx-updates-firmware.html" title="Garmin Nuvi 34xx/35xx updates firmware &amp; Smartphone Link - Traffic Problems Solved?" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/-osBthpszC58/T3OsBwDrNlI/AAAAAAAAO-Y/xJLERtey8bE/s72-c/20120328_180723.jpg" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/03/garmin-nuvi-34xx35xx-updates-firmware.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0MMQXY4eSp7ImA9WhVRGUo.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-8286241100945937535</id><published>2012-03-28T19:04:00.002-05:00</published><updated>2012-03-28T19:04:40.831-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-03-28T19:04:40.831-05:00</app:edited><title>Garmin adds Tracker feature to Smartphone Link - Beware surprise privacy issues!</title><content type="html">Today, Garmin released an update to Smartphone Link which added an exciting feature called Tracker. &amp;nbsp;Think of tracker as Garmin's version of Google Latitude. &amp;nbsp;This feature requires an update to &lt;a href="https://play.google.com/store/apps/details?id=com.garmin.android.apps.phonelink" target="_blank"&gt;Smartphone Link&lt;/a&gt; in the Android Play Market as well as an upgrade to &lt;a href="http://www8.garmin.com/support/download_details.jsp?id=5303" target="_blank"&gt;Nuvi firmware v6.2&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
The Tracker functionality allows you to use your smartphone to keep track of other Garmin Tracker user's location. &amp;nbsp;However, the Tracker feature also lets you post messages and location information to both Facebook and Twitter. &amp;nbsp;Interestingly, Garmin's implementation of this feature seems to require both the Facebook and Twitter apps to be on your phone. &amp;nbsp;You enable this feature from within the Smartphone Link app, not on your Nuvi. &amp;nbsp;It appears to derive your login information for these services from the Facebook and Twitter apps themselves rather than having you enter them into the Smartphone Link app. &amp;nbsp;When selecting the social network services you wish to use, appropriate permissions are requested and confirmed within the Smartphone Link app.&lt;br /&gt;
&lt;br /&gt;
You can enable a "follow me" functionality that can be time limited. &amp;nbsp;This feature allows you to select other Tracker users, as well as Facebook and Twitter posts, to be the recipient of periodic "check-ins" of your location. &amp;nbsp;I have not yet experimented with how often the follow me check-ins occur.&lt;br /&gt;
&lt;br /&gt;
There is also a manually initiated feature that allows you to "send" your current location to other Tracker users, to Facebook and to Twitter. &amp;nbsp;You can select or deselect any of those services as you choose. &amp;nbsp;Garmin has provided canned messages such as "running late" or "stuck in traffic" that can be selected. &amp;nbsp;In a nice touch, Garmin has also populated the canned messages with messages that are "location aware." &amp;nbsp;In other words, my current location city was populated as a&amp;nbsp;select-able canned message. &amp;nbsp;Also available was a message that said "it is 72 degrees here" obviously pulling that information from the Smartphone Link Advanced Weather feature. Job well done on this Garmin.&lt;br /&gt;
&lt;br /&gt;
I selected a canned message that said "In Des Moines, IA" and posted it to Twitter and Facebook. &amp;nbsp;The Nuvi presents a confirmation screen that the message was posted. &amp;nbsp;Upon reviewing the resulting post on both Facebook and Twitter, I was pleased with the presentation, but also very concerned about the privacy implications of what I found.&lt;br /&gt;
&lt;br /&gt;
On Facebook my message "In Des Moines, IA" was posted with the expected footer message indicating that it was posted by Garmin Tracker. &amp;nbsp;But there was also a clickable image of a website in the post! On Twitter, it also said "In Des Moines, IA" but also contained a clickable URL!&lt;br /&gt;
&lt;br /&gt;
When clicking either the Facebook or Twitter link, I was brought to this webpage:&lt;br /&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://2.bp.blogspot.com/-TMY1Jozb1Mo/T3OiyE2pykI/AAAAAAAAO-M/QGhFTNx_qFs/s1600/GarminTracker.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="171" src="http://2.bp.blogspot.com/-TMY1Jozb1Mo/T3OiyE2pykI/AAAAAAAAO-M/QGhFTNx_qFs/s400/GarminTracker.JPG" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
I was very surprised to find the amount of detail being revealed that I found on this website. &amp;nbsp;At the top of the page (not shown here) was my name, exactly how I'd entered it into the Garmin Tracker app. &amp;nbsp;But more disturbing was the availability of data that included an exact street address, latitude / longitude, and speed I was traveling. &amp;nbsp;There was also a map that included zoom controls that provides viewers with house-level precision of my location!&lt;br /&gt;
&lt;br /&gt;
Perhaps I am too used to Google Latitude and its privacy controls, but I did not expect Garmin Tracker to reveal this level of detail about my location. &amp;nbsp;I very often use social media to inform friends of my location, but in a very general sense. &amp;nbsp;I might post that I've arrived "In Chicago, IL" or "Landed at LAX." &amp;nbsp;But seldom do I want anyone but my immediate family to know my precise location to the level shown above.&lt;br /&gt;
&lt;br /&gt;
The level of detail revealed by Garmin Tracker might be fine for my wife to know. &amp;nbsp;But I probably don't want my Facebook friends to know that level of detail. &amp;nbsp;And, for sure, I don't want my Twitter followers, who I might not even know, to know this level of detail.&lt;br /&gt;
&lt;br /&gt;
Tying a location notification feature to your Garmin Nuvi &amp;nbsp;makes perfect sense and it is well implemented by Garmin with this new Tracker feature. &amp;nbsp;However, it badly needs user controls for the granularity of information shared, like Google Latitude currently offers. &amp;nbsp;There are obvious reasons why, for the same location notification post, that I'd like my wife's Garmin Tracker ID to know my precise location, but my Facebook friends and Twitter followers to know only the town I am in. &amp;nbsp;I can think of no case where revealing my speed is necessary or important.&lt;br /&gt;
&lt;br /&gt;
Garmin has some work to do on disclosing and tightening up this privacy issue, but Tracker is a great start to a useful feature.&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/n8j_-HqP4RU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/8286241100945937535/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/03/garmin-adds-tracker-feature-to.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/8286241100945937535?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/8286241100945937535?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/n8j_-HqP4RU/garmin-adds-tracker-feature-to.html" title="Garmin adds Tracker feature to Smartphone Link - Beware surprise privacy issues!" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/-TMY1Jozb1Mo/T3OiyE2pykI/AAAAAAAAO-M/QGhFTNx_qFs/s72-c/GarminTracker.JPG" height="72" width="72" /><thr:total>1</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/03/garmin-adds-tracker-feature-to.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0QHRn07eip7ImA9WhVRGEo.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-3056936100970536886</id><published>2012-03-27T13:32:00.002-05:00</published><updated>2012-03-27T14:08:57.302-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-03-27T14:08:57.302-05:00</app:edited><title>Garmin completely unresponsive to Google Play Market customer service channel</title><content type="html">At CES, Garmin introduced the Smartphone Link app to the &lt;a href="https://play.google.com/store/apps/details?id=com.garmin.android.apps.phonelink" target="_blank"&gt;Android Market&lt;/a&gt;. &amp;nbsp;&lt;a href="http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-revolutionary.html" target="_blank"&gt;As I've blogged before&lt;/a&gt;, this app introduced integration between a conventional PND and the smartphone is some potentially powerful and profound ways.&lt;br /&gt;
&lt;br /&gt;
Consumers beware: &amp;nbsp;you better hope you don't experience any customer service issues with this app, because Garmin has been completely unresponsive to contact through the Google Play Market in over 2.5 months.&lt;br /&gt;
&lt;br /&gt;
In previous blog posts, I've outlined problems with the&amp;nbsp;&lt;a href="http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-live-traffic.html" target="_blank"&gt;traffic&lt;/a&gt; and &lt;a href="http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-advanced-weather.html" target="_blank"&gt;weather&lt;/a&gt;&amp;nbsp;features of the Smartphone Link app. &amp;nbsp;In the course of troubleshooting these problems with me, Garmin telephone support had me remove the Smartphone Link app and&amp;nbsp;re-install&amp;nbsp;it. &amp;nbsp; As part of that process you have to re-establish that you purchased the premium services in order to get them back. &amp;nbsp;To do that, I "re-purchased" the Premium Weather feature. &amp;nbsp;Once I re-purchased the Premium Weather feature, the system recognized that I also owned the other 3 services as well and re-enabled them automatically. &amp;nbsp;I fully expected that since I purchased Premium Weather the day before, Garmin's system would recognize me as a customer of that feature and re-enable it. &amp;nbsp;Imagine my surprise when I was billed AGAIN by Garmin for $4.99. &amp;nbsp;Here is my purchase history from Google Wallet:&lt;br /&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://4.bp.blogspot.com/-lGatD2q6348/T3IDY42ltgI/AAAAAAAAO8o/ThVeyQOJWxM/s1600/purchase+history.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="52" src="http://4.bp.blogspot.com/-lGatD2q6348/T3IDY42ltgI/AAAAAAAAO8o/ThVeyQOJWxM/s400/purchase+history.JPG" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
As you can see, I was billed on both January 9th and January 10th for Advanced Weather for $4.99 despite this being used on the same phone, in the same app.&lt;br /&gt;
&lt;br /&gt;
No problem I thought. &amp;nbsp;I'll just contact Garmin and get this resolved. &amp;nbsp;As every software developer does, Garmin provides contact information in the Google Play Market for customer contact. &amp;nbsp;With a huge company like Garmin, I would assume that this contact would be a contact best suited to deal with a particular issue like a billing issue in the Google Play Market. &amp;nbsp;That is a pretty niche and obscure issue. &amp;nbsp;Here is a screenshot of where Garmin provides this customer contact method inside of Google Play Market:&lt;br /&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://1.bp.blogspot.com/-Ow3dH7rYvMA/T3IET5HOF7I/AAAAAAAAO8w/btsKB249QVc/s1600/googleplay_garmin.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="82" src="http://1.bp.blogspot.com/-Ow3dH7rYvMA/T3IET5HOF7I/AAAAAAAAO8w/btsKB249QVc/s400/googleplay_garmin.JPG" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
See the "Contact Garmin International, Inc." link above? &amp;nbsp;Yes, so did I. &amp;nbsp;I've used it twice. &amp;nbsp;Take a look at my contact history above, thoughtfully summarized by Google in the Google Play Market order history. &amp;nbsp;You can see that I first contacted Garmin on January 10th, the day that I was billed twice for the same feature. &amp;nbsp;I received no response after a month. I sent a second request on February 17. &amp;nbsp;Here we are, almost 6 weeks later and I've gotten no response whatsoever from Garmin.&lt;br /&gt;
&lt;br /&gt;
In normal circumstances, I'd simply dispute this on my credit card. &amp;nbsp;Clearly, I'd succeed. &amp;nbsp;However, in this case, I am afraid that given Garmin's apparent incompetence at dealing with basic customer service issues, they'd fail to understand that this is a duplicate billing issue and rather assume that I was simply disputing the charge for Advanced Weather. &amp;nbsp;The repercussions of this would be that they could simply shut off the app on the service side. &amp;nbsp;Despite Advanced Weather &lt;a href="http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-advanced-weather.html" target="_blank"&gt;not working like it should right now&lt;/a&gt;, I don't want to loose access to it.&lt;br /&gt;
&lt;br /&gt;
This is very disappointing Garmin. &amp;nbsp;Garmin badly flubbed &lt;a href="http://jkcarp.blogspot.com/2012/01/strike-1-for-garmin-supports-response.html" target="_blank"&gt;their initial response to me&lt;/a&gt; when I reported problems with Smartphone Link. &amp;nbsp;They've been in possession of detailed data about the problems, including screen shots, for over 11 weeks now with no fix being issued. &amp;nbsp;And now as you can see, they've completely ignored a basic customer service contact for over 12 weeks. &amp;nbsp;I'd call them about this but quite frankly I've got better things to do with my time than wait on hold for 30 minutes. &amp;nbsp;I've used the customer contact method closest to the source of my problem, as provided by Garmin, and Garmin has completely ignored it.&lt;br /&gt;
&lt;br /&gt;
In Garmin's investor relations information they proclaim in their Code of Conduct that Garmin's values "shine through in our interactions with customers." &amp;nbsp;It is difficult to take that seriously given the experiences that I've outlined in this blog.&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/O4KiCiyiAlQ" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/3056936100970536886/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/03/garmin-completely-unresponsive-to.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/3056936100970536886?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/3056936100970536886?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/O4KiCiyiAlQ/garmin-completely-unresponsive-to.html" title="Garmin completely unresponsive to Google Play Market customer service channel" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/-lGatD2q6348/T3IDY42ltgI/AAAAAAAAO8o/ThVeyQOJWxM/s72-c/purchase+history.JPG" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/03/garmin-completely-unresponsive-to.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkEBQX8yfCp7ImA9WhVRGEo.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-1241260366466042046</id><published>2012-03-27T12:50:00.004-05:00</published><updated>2012-03-27T12:50:50.194-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-03-27T12:50:50.194-05:00</app:edited><title>Garmin 3590 Road Test in LA: The good &amp; the bad</title><content type="html">I just returned from a week long vacation to Los Angeles. &amp;nbsp;During my trip, I drove about 480 miles in southern California traffic, using my Garmin 3590LMT the entire time. &amp;nbsp;The verdict? &amp;nbsp;It was a good experience overall, however I experienced two significant problems.&lt;br /&gt;
&lt;br /&gt;
First, the good....The routing combined with the 3D Traffic service was very, very good. &amp;nbsp;You can say one thing about LA - there is always "another way" to get everywhere. &amp;nbsp;The Garmin unit seemed to find them. &amp;nbsp;The unit seemed to do a good job in general, of avoiding traffic jams. &amp;nbsp;There were three times when it actually got me off the freeway and back on later down the road to avoid a significant traffic issue. &amp;nbsp;Unfortunately, in one case confirmed by visual confirmation, the traffic incident was false. &amp;nbsp;Overall though, I was very impressed with the routing and the traffic. &amp;nbsp;I've had very different experiences with the traffic quality on the 3590 in other markets, but in LA I found it to be very good.&lt;br /&gt;
&lt;br /&gt;
The awareness of POV lanes, lane guidance and freeway sign imagery were extremely valuable on this trip. &amp;nbsp;I do not know LA freeways at all. &amp;nbsp;I am driving blindly for the most part, trusting the Garmin. &amp;nbsp;Gladly, I could trust it and the guidance features it provides make a dedicated PND much better than most smartphone solutions. &amp;nbsp;Had we been driving our RV instead of a rental car, I would proclaim the lane guidance (in particular)&amp;nbsp;irreplaceable.&lt;br /&gt;
&lt;br /&gt;
Unfortunately, the 3590 exhibited a significant problem with random rebooting. &amp;nbsp;Upon landing in LA, my unit rebooted *6* times in the 30 minute trip from the airport to our condo. &amp;nbsp;In the course of the week, the unit rebooted over a dozen times. &amp;nbsp;This is very disappointing, but unfortunately par for the course with Garmin in recent years it seems. &amp;nbsp;Do a Google search for Nuvi rebooting and you'll find thousands of discussions dating back to the 7xx series. &amp;nbsp;Garmin can justify spending $300+ dollars on a PND in a smartphone world only if they can show significantly better features and rock solid reliability. &amp;nbsp;The features? Yeah, I think they do that. &amp;nbsp;Reliability? &amp;nbsp;Not so much.&lt;br /&gt;
&lt;br /&gt;
Upon rebooting, I found the unit to have very sketchy reliability in terms of reconnecting to bluetooth on my smartphone. &amp;nbsp;Since I am using Garmin Smartphone Link, reestablishing smartphone bluetooth connectivity is essential to getting my traffic content back - a must when traveling on LA freeways. &amp;nbsp;In many cases, the only way to&amp;nbsp;reestablish&amp;nbsp;bluetooth connectivity with my smartphone was to disable bluetooth in the Nuvi settings and&amp;nbsp;re-enable&amp;nbsp;it. &amp;nbsp;Having to do this changes the reboot problem on the 3590 from an annoyance to a complete hassle. &amp;nbsp;A random reboot on a Nuvi is like a Windows blue screen of death. &amp;nbsp;It makes you cuss Garmin as much as people cuss Microsoft. &amp;nbsp;Frankly, I expect better from Garmin.&lt;br /&gt;
&lt;br /&gt;
The second big problem that I experienced is with the Smartphone Link Advanced Weather feature. &amp;nbsp;I outlined the complete failure of the weather alert feature in &lt;a href="http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-advanced-weather.html" target="_blank"&gt;a previous blog post&lt;/a&gt;. &amp;nbsp;Unfortunately, the performance of this feature got worse on my trip. &amp;nbsp;I have two locations set in the weather alerts settings. &amp;nbsp;I have my hometown (Des Moines, IA) and my "current location." &amp;nbsp;While traveling in LA, I routinely received WINTER STORM ALERTS while driving in LA. &amp;nbsp;Huh? &amp;nbsp;It was March, in LA - there is no winter there. &amp;nbsp;Of course when I pressed the weather alert icon, I received no information because Garmin isn't providing the text of the weather alerts as I outlined in my &lt;a href="http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-advanced-weather.html" target="_blank"&gt;previous post&lt;/a&gt;. &amp;nbsp;Perhaps, I thought, the alert wasn't for my current location in LA, but rather was for my other defined location of Des Moines, IA. &amp;nbsp;However, the problem with that idea, is that I knew that on that day in Des Moines the weather was approaching 80 degrees! &amp;nbsp;In no way was there any Winter Storm Alerts in Des Moines, IA or Los Angeles, CA last week. &amp;nbsp;Had Garmin implemented this feature in a way that actually shows us the text of the weather alert, I might have been able to figure out what was actually going on. &amp;nbsp;Since the weather alert text content is blank, it is impossible to trouble shoot. &amp;nbsp;What I know is that from this experience and the experience that I &lt;a href="http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-advanced-weather.html" target="_blank"&gt;outlined earlier&lt;/a&gt;&amp;nbsp;the Smartphone Link weather service is not worthy of a charge and I would not recommend that anyone purchase it until Garmin fixes the problems.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/5l0oUEFq2QU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/1241260366466042046/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/03/garmin-3590-road-test-in-la-good-bad.html#comment-form" title="5 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/1241260366466042046?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/1241260366466042046?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/5l0oUEFq2QU/garmin-3590-road-test-in-la-good-bad.html" title="Garmin 3590 Road Test in LA: The good &amp; the bad" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><thr:total>5</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/03/garmin-3590-road-test-in-la-good-bad.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkAGRns8fSp7ImA9WhVSGEw.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-3442759676507675575</id><published>2012-03-15T07:32:00.001-05:00</published><updated>2012-03-15T07:32:07.575-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-03-15T07:32:07.575-05:00</app:edited><title>Garmin Guidance 3.0 Traffic - not impressed</title><content type="html">&lt;div&gt;&lt;p&gt;I have had some time now to play with both the new Garmin 3590 as well as my previous Garmin 3490, both of which have new Garmin guidance 3.0 along with the new Navteq HD traffic.&lt;/p&gt;
&lt;p&gt;While these are both pretty good PND devices, I have to say that my experience so far with the traffic service is pretty underwhelming.&amp;#160; I mean, it is great that the higher bandwidth service provides us with more granularity in the traffic data. However, if the content is just wrong it doesn't matter how granular it is, it is wrong.&lt;/p&gt;
&lt;p&gt;I have run into many situations with the traffic service where it leaves me scratching my head as to how the traffic data can report what it is reporting.&amp;nbsp; Or worse yet, not reporting what it should be.&amp;nbsp;&amp;nbsp; Navteq has always had an arrogance about themselves.&amp;nbsp; It would just be nice if that arrogance were backed up by rock solid product content. &lt;/p&gt;
&lt;p&gt;A recent example was a trip to Las Vegas. There's an intersection of two major freeways just south of the strip in Las Vegas. This interstate intersection and several portions of the connecting interstates is in the middle of a major construction project.&amp;#160; This construction project has closed several ramps between interstates. And when I say closed I mean closed as in "the pavement has been dug up" closed. I don't mean closed as in "hey we need to close this ramp for half a day so we can move some equipment in and out" closed. If you go to the DOT website for Nevada, this construction project and these closures are well-documented. But despite all that, my Garmin backed by Navteq traffic, tries to route me right through the closed ramps on the course of my trip.&lt;/p&gt;
&lt;p&gt;I mean really Navteq. How hard is it to hire an intern and tell them to review the websites for the DOT? Is it really that hard to incorporate documented construction data into your traffic service? In 2012? Wow.&lt;/p&gt;
&lt;p&gt;They have the opposite problem in other areas. In the Des Moines market, Navteq has a perpetual traffic delay at exit 68 where I-35 connects to Iowa 5.&amp;#160;&amp;#160; There is no delay there. It doesn't exist. And without question, that delay does not exist 24 hours a day. This is Des Moines Iowa folks. There is no traffic delay that exists outside of about a two hour window during rush hour.&lt;/p&gt;
&lt;p&gt;Today, traveling on I 88 into Chicago I was warned of a 9 mile 15 minute delay. Here's a picture of what the road looked like smack dab in the middle of that so-called delay.&amp;#160; This wasn't I 88 in Chicago mind you. This was I 88 in the middle of rural Illinois about 100 miles west of the closest Chicago suburbs.&amp;#160; Short of a meteor landing in the middle of the highway, there is no traffic out here. Ever.&lt;/p&gt;
&lt;p&gt;I will spend the following week in Los Angeles. I look forward to seeing what kind of accuracy this new traffic service has in a major market like LA. I will blog about my experiences when I return. So far, to say I'm underwhelmed is an understatement.&lt;/p&gt;
&lt;br/&gt;&lt;img src='http://lh6.ggpht.com/-71R2D0ZoPac/T2HhRVK3BoI/AAAAAAAAO0I/u-QsRUAlvXo/20120315_070251.png' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/w_zduUOJp58" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/3442759676507675575/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/03/garmin-guidance-30-traffic-not.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/3442759676507675575?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/3442759676507675575?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/w_zduUOJp58/garmin-guidance-30-traffic-not.html" title="Garmin Guidance 3.0 Traffic - not impressed" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://lh6.ggpht.com/-71R2D0ZoPac/T2HhRVK3BoI/AAAAAAAAO0I/u-QsRUAlvXo/s72-c/20120315_070251.png" height="72" width="72" /><thr:total>0</thr:total><georss:featurename>Rochelle, null</georss:featurename><georss:point>41.996983 -89.32269</georss:point><feedburner:origLink>http://jkcarp.blogspot.com/2012/03/garmin-guidance-30-traffic-not.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0cNQnc_fyp7ImA9WhVTEEk.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-148362684982425154</id><published>2012-02-23T17:51:00.001-06:00</published><updated>2012-02-23T17:51:33.947-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-02-23T17:51:33.947-06:00</app:edited><title>Garmin Nuvi 3590LMT vs 3490LMT Comparison Pictures</title><content type="html">I picked up a Garmin Nuvi 3590LMT today to replace my Nuvi 3490LMT. &amp;nbsp;The 3490 will grace my wife's car from now on. &amp;nbsp;On paper, I wasn't expecting a big difference between the 3590LMT and the 3490LMT, especially when looking closely at the specs. &amp;nbsp;My wife simply needed a new unit, so I figured I'd order the newest one for myself while I had the opportunity. &amp;nbsp;These two devices are generally referred to as a 5" model and a 4" model respectively. &amp;nbsp;But when you examine the spec sheets and look at the actual dimensions you figure out that there really isn't a 1" difference. &amp;nbsp;That led to my lack of expectation for a big difference.&lt;br /&gt;
&lt;br /&gt;
Wow! Was I wrong. &amp;nbsp;I frankly don't care what the spec sheet says. &amp;nbsp;The 3590LMT is huge compared to the 3490LMT and I like it 100% better for that reason only. &amp;nbsp;I found myself having to really focus on reading text on the 3490LMT especially on things like photoReal junction imagery. &amp;nbsp;Those concerns are gone with the 3590LMT.&lt;br /&gt;
&lt;br /&gt;
Here are some comparison pictures between the two devices:&lt;br /&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://1.bp.blogspot.com/-VSBys26Q-cI/T0bNQxY1NeI/AAAAAAAAOZc/Yu7G50u6Gtw/s1600/20120223_150445.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="240" src="http://1.bp.blogspot.com/-VSBys26Q-cI/T0bNQxY1NeI/AAAAAAAAOZc/Yu7G50u6Gtw/s320/20120223_150445.jpg" width="320" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="separator" style="clear: both; text-align: left;"&gt;
The difference in the screen experience in this photo is real. &amp;nbsp;The 3490LMT is brighter, but the colors are more washed out. &amp;nbsp;The colors on the 3590LMT are more rich and deeper. &amp;nbsp;I much prefer the 3590LMT screen after having both devices side by side.&lt;/div&gt;
&lt;div class="separator" style="clear: both; text-align: left;"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="separator" style="clear: both; text-align: left;"&gt;
Something is up with the routing on these two devices. &amp;nbsp;I have the exact same route calculated on both devices. &amp;nbsp;The two devices agree 100% on the route to take. They agree on the miles. &amp;nbsp;But the 3590 has me arriving over 2 hours earlier than the 3490 on this 22 hour trip. &amp;nbsp;I've never driven it so I don't know which is more accurate. &amp;nbsp;Also note that the 3590 is 2 hours quicker WITH a red traffic icon, showing a 15 minute delay leaving Las Vegas. &amp;nbsp;The 3590 is getting a traffic signal through Smartphone Link. &amp;nbsp;The 3490 does not have a traffic source.&lt;/div&gt;
&lt;div class="separator" style="clear: both; text-align: left;"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="separator" style="clear: both; text-align: left;"&gt;
I wonder, since the 3490 has no traffic source in the photo above, if because of that it doesn't take historical traffic data into account? &amp;nbsp;Perhaps that feature only works when there is a traffic source connected?&lt;/div&gt;
&lt;div class="separator" style="clear: both; text-align: left;"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="separator" style="clear: both; text-align: left;"&gt;
The only other difference between the two units is that the 3590 has a firmware v4.70 upgrade available for download out of the box. &amp;nbsp;The 3490 reports the latest available as v4.40. &amp;nbsp;Not sure if the firmware update has any impact on routing calculation or not.&lt;/div&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://2.bp.blogspot.com/-qlhuHrijqfQ/T0bNXFc3TNI/AAAAAAAAOZk/_BONgqHCwNA/s1600/20120223_150501.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="240" src="http://2.bp.blogspot.com/-qlhuHrijqfQ/T0bNXFc3TNI/AAAAAAAAOZk/_BONgqHCwNA/s320/20120223_150501.jpg" width="320" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;br /&gt;
There is no difference in glare on the two device screens. &amp;nbsp;The apparent glare on the photo above is strictly a limitation of the environment that I took the photo in.&lt;br /&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://4.bp.blogspot.com/-dJcjS_vuW3k/T0bNcUIcAiI/AAAAAAAAOZs/3JxjgTF141k/s1600/20120223_150556.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="240" src="http://4.bp.blogspot.com/-dJcjS_vuW3k/T0bNcUIcAiI/AAAAAAAAOZs/3JxjgTF141k/s320/20120223_150556.jpg" width="320" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
There is a thickness difference as well between the two devices as can be seen here.&lt;br /&gt;
&lt;br /&gt;
I was somewhat disappointed to see that, out of the box this brand new unit had two-version-old 2012.2 maps installed. &amp;nbsp;I had to do a map update out of the box to get to 2012.4. &amp;nbsp;Not sure why a brand new device that just shipped two days again would have 6 month old map data on it. &amp;nbsp;I could see having 2012.3. Perhaps I simply don't understand the production cycle on devices like this.&lt;br /&gt;
&lt;br /&gt;
Finally, note that currently the 3590LMT has the same problem of an incompatibility between Smartphone Link Live Traffic and the HD Radio traffic described in my earlier blog posts. &amp;nbsp;No update from Garmin as of yet to fix this problem.&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/QjkIm8UMJMw" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/148362684982425154/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/02/garmin-nuvi-3590lmt-vs-3490lmt.html#comment-form" title="6 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/148362684982425154?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/148362684982425154?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/QjkIm8UMJMw/garmin-nuvi-3590lmt-vs-3490lmt.html" title="Garmin Nuvi 3590LMT vs 3490LMT Comparison Pictures" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/-VSBys26Q-cI/T0bNQxY1NeI/AAAAAAAAOZc/Yu7G50u6Gtw/s72-c/20120223_150445.jpg" height="72" width="72" /><thr:total>6</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/02/garmin-nuvi-3590lmt-vs-3490lmt.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkcGRng7fyp7ImA9WhRUEUQ.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-2482874148356449719</id><published>2012-01-21T17:53:00.003-06:00</published><updated>2012-01-21T17:53:47.607-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-21T17:53:47.607-06:00</app:edited><title>TomTom and Android - My View</title><content type="html">One of the lingering questions in the turn-by-turn navigation industry is why TomTom has failed to answer the challenge that Android has presented them. &amp;nbsp;Because of TomTom's (near) silence on the issue, we are left to speculate. &amp;nbsp;Here is my speculation. &amp;nbsp;TomTom does not have an Android solution for one of the following reasons:&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;They&amp;nbsp;&lt;i&gt;want&lt;/i&gt;&amp;nbsp;a solution but can't get it out the door for technical reasons.&lt;/li&gt;
&lt;li&gt;They&amp;nbsp;&lt;i&gt;don't want&lt;/i&gt;&amp;nbsp;a solution and view it as a strategy to compete with Android. (Doubtful)&lt;/li&gt;
&lt;li&gt;They view partner solutions as "good enough."&lt;/li&gt;
&lt;/ul&gt;
&lt;div&gt;
Each of these are viable reasons, based on TomTom's own actions.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Let's start with public comments made by TomTom executives in &lt;u style="font-weight: bold;"&gt;2009&lt;/u&gt;, yes almost 3 years ago. &amp;nbsp;In 2009, senior VP for TomTom onboard mobile Benoit Simery was quoted as saying "We cannot ignore such a successful platform as Android." &amp;nbsp;Well, it is three years later. &amp;nbsp;You've done a pretty good job of ignoring it so far.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Android was growing in 2009, no question. &amp;nbsp;Today, however, Android's popularity dwarfs what it was in 2009. &amp;nbsp;It would be one thing if TomTom was blind to Android's growing popularity in 2009, but clearly they weren't. &amp;nbsp;Clearly Android's popularity exploded since that statement was made. &amp;nbsp;Yet, not only was TomTom unable to muster a response to that popularity that allowed them to ride the popularity wave upward, they remain without an answer to this day, nearly 3 years later.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
In the spring of 2011, another TomTom executive, Corinne Vigreux made a public statement that "(they) are currently working on an Android version." &amp;nbsp;TomTom would have been better served by Ms. Virgreux not saying a word. &amp;nbsp;To state that, yet not deliver almost a year later, fuels technical incompetence discussions.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
TomTom publicly announced the need to address Android in 2009. &amp;nbsp;They publicly announced, two years later, that they are working on an Android solution. &amp;nbsp;Now, nearly a year after that, they still haven't delivered.&amp;nbsp;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
TomTom's own &lt;a href="http://discussions.tomtom.com/t5/NAVIGATOR-and-MOBILE/bd-p/navigator" target="_blank"&gt;mobile discussion forum&lt;/a&gt;&amp;nbsp;is dominated by two discussions posts, both discussing Android. &amp;nbsp;Between the two posts, they have received 27,000 views - by far the most of any posts on the forum. &amp;nbsp;Yet, despite TomTom's willingness for their two executives to speak publicly about Android on two occasions, they have allowed these two threads to develop and be viewed over 27,000 times without a single comment. &amp;nbsp;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
If TomTom truly wants an Android solution but can't get it out the door&amp;nbsp;for technical reasons I question their technical competence. &amp;nbsp;ALK, Navigon, Waze, Mapquest, Sygic, NDrive, NNG and others are all on &lt;i&gt;at least&lt;/i&gt;&amp;nbsp;their second generation Android products. &amp;nbsp;There is no reasonable explanation for why a technical problem is preventing TomTom from getting a first generation product to the Android market.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
I rule out TomTom not wanting an Android product as a (misguided) strategy for how to compete with Android, given the two executive comments highlighted above. &amp;nbsp;If there has been a change of heart at TomTom about Android then TomTom owes their customers a similar pubic statement indicating that they will not support Android. &amp;nbsp;Close the door on the issue if that is the case.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
If TomTom is content with partner solutions like Route66, my personal opinion is that this is a highly misguided strategy. &amp;nbsp;Maps are becoming a commodity. &amp;nbsp;Automated map correct solutions, such as those being used by Waze, will make solutions like TomTom MapShare obsolete in my opinion. &amp;nbsp;TomTom appears to have no answer.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
In my opinion, the only company today, with the power to differentiate their maps from a competitive perspective is Navteq. &amp;nbsp;TeleAtlas has greatly improved from years ago, but I personally do not believe they are equal to Navteq when it comes to the details. &amp;nbsp;Compare the text of a Navteq freeway exit sign image to the text of a TomTom freeway exit sign image and you will see what I mean. &amp;nbsp;Navteq's text is usually 100% accurate when compared to the actual freeway sign. The TeleAtlas text is usually close, but often times appears to have been built from the Exit number and intersection road names only, positioned on a sign to look like a sign. &amp;nbsp;They often lack the specific text of the road signs themselves, like the city name, landmark and other details that are unrelated to the actual exit number or road name.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
All of this leads me to this conclusion, which is my personal opinion: &amp;nbsp;TomTom &lt;i&gt;does&lt;/i&gt;&amp;nbsp;have two pieces of valuable intellectually property left, that are currently not commodities. &amp;nbsp;However, their lack of an answer for Android squanders any remaining advantage of that intellectual property on a daily basis. &amp;nbsp;I believe that the US market will look back at TomTom and say "remember when TomTom screwed up their Android strategy? &amp;nbsp;They had a shot at one time." &amp;nbsp;Will TomTom become tomorrow's Kodak?&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;b&gt;&lt;u&gt;TomTom's remaining, valuable intellectual property is IQRoutes and HDTraffic&lt;/u&gt;&lt;/b&gt;.&lt;/div&gt;
&lt;div&gt;
Clearly TomTom/TeleAtlas had a competitive advantage over Navteq with IQRoutes. &amp;nbsp;Navteq is in catch up mode on that feature. &amp;nbsp;But TomTom is &lt;i&gt;allowing&lt;/i&gt;&amp;nbsp;Navteq to catch up. &amp;nbsp;A competent TomTom strategy would have been a strategy that leverages the head start of IQRoutes and builds on it to remain far ahead of Navteq. &amp;nbsp;Smartphones, both Android and iPhone, had to be a key part of that strategy for it to work. &amp;nbsp;TomTom is blowing that opportunity.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
&lt;u&gt;IQRoutes (and HDTraffic) needs users&lt;/u&gt;. &amp;nbsp;Users are TomTom's probes for these features. These features are nothing without users. &amp;nbsp;For these features to remain accurate and thus valuable, they need to continue to be fueled with user data from a &lt;i&gt;growing&lt;/i&gt;&amp;nbsp;user base.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
TomTom should be doing everything in its power to continue to build its user base, in order to preserve the value of its intellectual property of IQRoutes. &amp;nbsp;Instead, TomTom has been completely incompetent on an Android strategy, which has resulted in not adding users. For users that have switched to Android as their navigation choice, TomTom gets nothing from them. &amp;nbsp;Out of nearly 1,000,000 potential customers PER DAY, TomTom get NONE of them. &amp;nbsp;TomTom is allowing Waze to succeed at TomTom's own game because of TomTom's lack of a competent Android strategy. &amp;nbsp;Do you think TomTom will ever get those users back? &amp;nbsp;I think not. &amp;nbsp;Even if TomTom eventually does come up with a competent Android strategy, they have given their potential customers so long to use a competitor's solution that I think most of them will say "so long TomTom" for good. &amp;nbsp;&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
But in my opinion, TomTom still has a small chance. &amp;nbsp;They do still have a large customer base and solutions like Waze have a long way to go in mid to small markets where IQRoutes is more complete. &amp;nbsp;If you read a TomTom Facebook post, you will see that it is getting increasingly difficult for them to not get bombarded with customer posts blasting them about their lack of Android&amp;nbsp;presence on nearly anything TomTom posts there. &amp;nbsp;While that has to be unbelievably frustrating and perhaps&amp;nbsp;embarrassing&amp;nbsp;for TomTom, they should see one sliver of good news in the current situation: &amp;nbsp;customers still care.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
When customers quit caring and asking for a TomTom for Android solution, that is when TomTom should be very, very worried. &amp;nbsp;That day is not far off.&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/jNsc3biJoqo" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/2482874148356449719/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/01/tomtom-and-android-my-view.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/2482874148356449719?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/2482874148356449719?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/jNsc3biJoqo/tomtom-and-android-my-view.html" title="TomTom and Android - My View" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/01/tomtom-and-android-my-view.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D04BR385fyp7ImA9WhRUEUU.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-743078568776207833</id><published>2012-01-21T16:45:00.003-06:00</published><updated>2012-01-21T16:45:56.127-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-21T16:45:56.127-06:00</app:edited><title>Garmin Nuvi Speed Limit Alerts - A Lost Opportunity</title><content type="html">My current Garmin GPS is a Nuvi 3490LMT. &amp;nbsp;I've owned it for about 2 weeks. &amp;nbsp;Prior to that, I've owned about 8 Garmin GPS devices going back to the very first StreetPilot III. &amp;nbsp;But after owning the 885T, I took a couple years off from Garmin products due to my frustration with Garmin's products and their support.&lt;br /&gt;
&lt;br /&gt;
As I've said here before, Smartphone Link is what brought me back to Garmin again. &amp;nbsp;But that doesn't mean that my frustration with Garmin has gone away. &amp;nbsp;Little things that I've encountered over the last 2 weeks have fueled that frustration again.&lt;br /&gt;
&lt;br /&gt;
The Nuvi 3490LMT, until next month, is the top of the line. It does one thing: it is a PND. &amp;nbsp;It is priced the same as most smartphones and some tablets - both of which are devices that do much more than a PND does. &amp;nbsp;In my opinion, for Garmin to continue to sell $399 PND in a smartphone world, it better do navigation better than anything else can do navigation. &amp;nbsp;In many ways, the 3490LMT delivers on that expectation. But in some ways, and they are seemingly simple things, Garmin drops the ball. &amp;nbsp;Dropping the ball on the little things reduces the justification for buying a $399 PND and further props up their smartphone competitors.&lt;br /&gt;
&lt;br /&gt;
&lt;u&gt;&lt;b&gt;One opportunity that Garmin is squandering is the handling of speed limits.&lt;/b&gt;&lt;/u&gt;&lt;br /&gt;
&lt;u&gt;&lt;b&gt;&lt;br /&gt;&lt;/b&gt;&lt;/u&gt;&lt;br /&gt;
Navteq map data has historically been best in class. It remains to be seen how crowd sourced solutions like Google Map Maker, Waze and OpenStreetMaps will change that. &amp;nbsp;But today, I'd argue that given all the characteristics that make a map accurate (roads, road class definitions, speed limits, freeway signage, etc.) Navteq remains best in class by a large margin.&lt;br /&gt;
&lt;br /&gt;
Navteq's knowledge of speed limits is very, very good. It amazes me to drive down rural highways in the middle of Iowa and see the speed limit indicator change almost simultaneously with the speed limit sign as you drive through a small town. &amp;nbsp;Companies that use Navteq data have an advantage to leverage.&lt;br /&gt;
&lt;br /&gt;
Garmin leverages Navteq's quality speed limit data in a half-hearted way at best. &amp;nbsp;They should do better.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;&lt;u&gt;Why does this matter?&lt;/u&gt;&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
It is rumored that with the release of iPhone 5, Apple will implement a built-in turn-by-turn navigation solution based on some quite acquisitions that they've made. Clearly Android has had that advantage for some time now, which has created pressure on traditional PND manufacturers like Garmin, TomTom and Navigon. &amp;nbsp;If the iPhone includes this capability as well, the pressure on Garmin and TomTom will only increase.&lt;br /&gt;
&lt;br /&gt;
Garmin must continue to innovate and be better than anyone else for customers to continue to justify spending as much as a smartphone for a dedicated PND device. Google Navigation and any future built-in iPhone solution will NOT have Navteq maps. For the remaining time that Navteq remains best in class, Garmin should leverage that advantage to the greatest extent possible. &amp;nbsp;They aren't.&lt;br /&gt;
&lt;br /&gt;
Garmin's current implementation of a speed limit alert feature seems to smack of a company that thinks it is the king of the marketplace &amp;nbsp;- resting on their laurels, rather than a company that faces an ever increasing challenge to their entire consumer business model in the near future. &amp;nbsp;It is almost as if they just want to check off a marketing spec sheet box that says "speed limit alerts" rather than actually improving the feature to make it useful.&lt;br /&gt;
&lt;br /&gt;
My most significant complaint about Garmin's current speed limit implementation is the&amp;nbsp;inability&amp;nbsp;to use the feature without actually looking at your GPS. &amp;nbsp;Currently, the only speed limit alert that Garmin has is a "feature" which turns the speed limit sign on the screen red in color when the speed limit is exceeded by 1 MPH. &amp;nbsp; This means that the user is informed that they are exceeding the speed limit only on the off chance that they happen to be looking at their PND screen. &amp;nbsp;The technology should permit so much more and customers of a $399 PND should be demanding it.&lt;br /&gt;
&lt;br /&gt;
Here is what Garmin should do to fix their current speed limit alert implementation:&lt;br /&gt;
&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;Garmin has a TTS engine on the GPS. &amp;nbsp;USE IT. &amp;nbsp;There should be no reason that Garmin can't use the TTS engine for a simple "Speeding Alert" message.&lt;/li&gt;
&lt;li&gt;A notification of speeding at 1 MPH over the posted speed limit is not useful. &amp;nbsp;Car speedometers don't permit a visual accuracy of 1 MPH. &amp;nbsp;No one cares if they are speeding by 1 MPH. &amp;nbsp;No policeman cares if a car is speeding by 1 MPH. &amp;nbsp;There is no way that knowing you are speeding by 1 MPH provides any safety benefit whatsoever. &amp;nbsp;It is a complete waste of a potentially useful feature. &amp;nbsp;Garmin should give customers a simple menu option to select the speed overage that they care about. &amp;nbsp;At a bare minimum, the alert should be set at an overage that actually means something, such as 5 MPH.&lt;/li&gt;
&lt;/ol&gt;
&lt;div&gt;
There shouldn't need to be a blog written to address the two things mentioned above. Customers should have expected that kind of improvement from one firmware version to another shortly after speed limit alerts was first introduced.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
What Garmin &lt;i style="text-decoration: underline;"&gt;should&lt;/i&gt;&amp;nbsp;be doing, is moving beyond the fixes noted above, in order to continue to innovate and leverage the quality of the Navteq data they have. &amp;nbsp;Garmin &lt;u style="font-style: italic;"&gt;should&lt;/u&gt;&amp;nbsp;be adding features such as:&lt;/div&gt;
&lt;div&gt;
&lt;ul&gt;
&lt;li&gt;Proactively warn customers of an upcoming speed reduction on their route such as when driving into a small town where the highway speed limit changes from 55 MPH to 35 MPH or other drastic changes using TTS voice alerts. &amp;nbsp;"Caution: Speed Limit Reduction Ahead." &amp;nbsp;Now &lt;i&gt;that&lt;/i&gt;&amp;nbsp;is useful use of the available Navteq data.&lt;/li&gt;
&lt;/ul&gt;
&lt;div&gt;
&lt;b&gt;&lt;u&gt;Garmin: use the differentiating data that you have at your finger tips and give us differentiating features&lt;/u&gt;&lt;/b&gt;.
&lt;/div&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/VzllDMsOIGw" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/743078568776207833/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/01/garmin-nuvi-speed-limit-alerts-lost.html#comment-form" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/743078568776207833?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/743078568776207833?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/VzllDMsOIGw/garmin-nuvi-speed-limit-alerts-lost.html" title="Garmin Nuvi Speed Limit Alerts - A Lost Opportunity" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><thr:total>2</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/01/garmin-nuvi-speed-limit-alerts-lost.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkMNQ3o_fyp7ImA9WhRUEEw.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-5058333025470436864</id><published>2012-01-19T17:03:00.001-06:00</published><updated>2012-01-19T17:08:12.447-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-19T17:08:12.447-06:00</app:edited><title>Garmin Smartphone Link Advanced Weather - Half baked or Another Broken Feature?</title><content type="html">&lt;span style="font-family: inherit;"&gt;

&lt;/span&gt;&lt;span style="font-family: inherit;"&gt; I am 10 days into my experience with Garmin Smartphone Link.
Since my initial post my clear excitment for the strategy has wanned somewhat
as I've run into some technical problems.&lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;div class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;
&lt;span style="font-family: inherit;"&gt;&lt;span style="background-color: white;"&gt;&lt;span style="background-color: white; color: red;"&gt;&lt;u&gt;Something is not right with Smartphone Link Advanced
Weather&lt;/u&gt;&lt;/span&gt;.&lt;/span&gt; At least I hope it is a technical problem. If this is how it is intended
to work, then I've been duped into thinking Garmin got the Smartphone Link
strategy right. If this is "how it works" I was clearly wrong.
Advanced Weather is a premium annual subscription option in Smartphone Link.
Here is what Garmin says about it:&lt;/span&gt;&lt;br /&gt;
&lt;/div&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://2.bp.blogspot.com/-t2Lv2P9tpM8/Txgm3pg-72I/AAAAAAAAORw/Yx2qYvteGxQ/s1600/weather.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" src="http://2.bp.blogspot.com/-t2Lv2P9tpM8/Txgm3pg-72I/AAAAAAAAORw/Yx2qYvteGxQ/s1600/weather.JPG" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;div class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;
&lt;br /&gt;
&lt;span style="font-family: inherit;"&gt;So far, the animated radar images have worked fine - as have
the current conditions and the forecasts. Today's problem is with the severe
weather alerts feature. Today we had our first instance of severe weather in my
area. As I am driving on a route, my Nuvi alerted me. Cool, a weather alert!
Look at the black weather warning icon below:&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://4.bp.blogspot.com/-GzM1IqRuEVc/TxgnFKR7j4I/AAAAAAAAOR4/TPskudjJAZ0/s1600/20120119_065951.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="300" src="http://4.bp.blogspot.com/-GzM1IqRuEVc/TxgnFKR7j4I/AAAAAAAAOR4/TPskudjJAZ0/s400/20120119_065951.jpg" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;div class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;
&lt;br /&gt;
&lt;span style="font-family: inherit;"&gt;A few minutes later while at a red light, I clicked on the
black weather alert cloud. I looked forward to reading about this weather
alert. Here is what I got:&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://3.bp.blogspot.com/-LwYRDa7Cl-s/TxgnQ18rymI/AAAAAAAAOSA/M4-l0iGD9MM/s1600/20120119_070012.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="300" src="http://3.bp.blogspot.com/-LwYRDa7Cl-s/TxgnQ18rymI/AAAAAAAAOSA/M4-l0iGD9MM/s400/20120119_070012.jpg" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;div class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;
&lt;/div&gt;
&lt;span style="font-family: inherit;"&gt;

&lt;/span&gt;&lt;span style="font-family: inherit;"&gt;I got nothing. What I expected on this screen was the text
of the severe weather alert at a minimum. I thought that Garmin might surprise
me, given that it is a GPS, and actually show me more than text. Perhaps they
will show me a map with the area of the alert highlighted - maybe with an
overview map of my current route overlayed? Nope. Instead I get a black screen.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;div class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;
&lt;span style="font-family: inherit;"&gt;Yes, Smartphone Link was connected fine. Yes, my phone had a
data connection. Yes, other Smartphone Link services were working. That isn't
the problem.&lt;/span&gt;&lt;br /&gt;
&lt;/div&gt;
&lt;div class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;
&lt;span style="font-family: inherit;"&gt;A few minutes later, driving on the route, I received
another severe weather alert. This time the black cloud icon changed. Notice
the '2' underneath the cloud symbol. That must mean there are now 2 severe
weather alerts.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/div&gt;
&lt;span style="font-family: inherit;"&gt;

&lt;/span&gt;&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://1.bp.blogspot.com/-PKoSPEdYzc0/TxgndKGTZmI/AAAAAAAAOSI/sgsLA1_1Tps/s1600/20120119_070232.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="300" src="http://1.bp.blogspot.com/-PKoSPEdYzc0/TxgndKGTZmI/AAAAAAAAOSI/sgsLA1_1Tps/s400/20120119_070232.jpg" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;div class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;
&lt;/div&gt;
&lt;span style="font-family: inherit;"&gt;

&lt;/span&gt;&lt;span style="font-family: inherit;"&gt;This time, after pressing the cloud, I come to this screen:&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://2.bp.blogspot.com/-NpX_-nE9Sis/TxgnspYsCPI/AAAAAAAAOSQ/0F7RU-1MBPc/s1600/20120119_070243.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="300" src="http://2.bp.blogspot.com/-NpX_-nE9Sis/TxgnspYsCPI/AAAAAAAAOSQ/0F7RU-1MBPc/s400/20120119_070243.jpg" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;div class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;
&lt;br /&gt;
&lt;span style="font-family: inherit;"&gt;That is better! Now I see that I have been notified of 2
winter storm warnings. Great. Let's find out more. I clicked on each of the
yellow banner icons:&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://3.bp.blogspot.com/-LwYRDa7Cl-s/TxgnQ18rymI/AAAAAAAAOSA/M4-l0iGD9MM/s1600/20120119_070012.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="300" src="http://3.bp.blogspot.com/-LwYRDa7Cl-s/TxgnQ18rymI/AAAAAAAAOSA/M4-l0iGD9MM/s400/20120119_070012.jpg" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;
&lt;span style="font-family: inherit;"&gt;I got nothing. Again. Over the course of the day, the cloud icon built up to 5 alerts in quantity with 5 identical &amp;nbsp;winter storm warning boxes with&amp;nbsp;5 blank black screens when you clicked them. Clearly there is no useful purpose in how this feature is currently implemented, assuming of course this isn't a technical problem.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/div&gt;
&lt;span style="font-family: inherit;"&gt;

&lt;/span&gt;&lt;o:p&gt;&lt;span style="font-family: inherit;"&gt;&amp;nbsp;&lt;/span&gt;&lt;/o:p&gt;&lt;br /&gt;
&lt;span style="font-family: inherit;"&gt;

&lt;/span&gt;&lt;span style="font-family: inherit;"&gt;Three explanations that I can think of:&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;&lt;span style="font-family: inherit;"&gt;The feature
is half-baked and what I expect to happen above isn't done yet. In this
scenario marketing had to get Smartphone Link out by CES and engineering wasn't
ready. In that case, the fact that they are charging a subscription fee for the
above is just bad business.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span style="font-family: inherit;"&gt;The feature
is fully implemented but isn't working correctly. &amp;nbsp;In this case, some things clearly haven't changed at Garmin.&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span style="font-family: inherit;"&gt;The feature
is fully implemented and this experience represents what Garmin had intended
the feature to do. If that is the case then run people. Run as far as you can
from these subscription services in Smartphone Link because they are an utter
waste of your hard earned money.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;br /&gt;
&lt;div class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;
&lt;span style="font-family: inherit;"&gt;This feature is significantly lacking in substance.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;
&lt;ol&gt;
&lt;li&gt;&lt;span style="font-family: inherit;"&gt;Why show me multiple, &amp;nbsp;identical "Winter Storm Warning" icons if you aren't going to
tell me the details of the multiple winter storm warnings? What good does knowing
there are multiples of them do me?&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;&lt;span style="font-family: inherit;"&gt;What
possible good do these warning provide me when you don't tell me anything about
their location? Are they near my current location, along my route or near my
destination? What time did they start? What time do they end? What is the
nature of the weather event I'll experience during the time span of the alert?&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;/div&gt;
&lt;br /&gt;
&lt;div class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;
&lt;span style="font-family: inherit;"&gt;Think about it Garmin. I HAVE a smartphone, or I wouldn't be
using Smartphone Link. I HAVE free weather programs available from multiple
vendors. I can access weather information with my voice on my smartphone with
SpeaktoIt, Nuance Dragon Go, Vlingo and others. I don't NEED one more weather
app. What I NEED is Garmin to leverage that weather content against my current
location and planned route and present it to me in an innovative way that only can be done on a PND. The above, if that is truly it, fails badly at this.&lt;/span&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/oUBIuV3nOSk" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/5058333025470436864/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-advanced-weather.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/5058333025470436864?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/5058333025470436864?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/oUBIuV3nOSk/garmin-smartphone-link-advanced-weather.html" title="Garmin Smartphone Link Advanced Weather - Half baked or Another Broken Feature?" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/-t2Lv2P9tpM8/Txgm3pg-72I/AAAAAAAAORw/Yx2qYvteGxQ/s72-c/weather.JPG" height="72" width="72" /><thr:total>1</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-advanced-weather.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkAFSX09eCp7ImA9WhRUEEw.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-5002059111039155240</id><published>2012-01-13T07:38:00.004-06:00</published><updated>2012-01-19T17:11:58.360-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-19T17:11:58.360-06:00</app:edited><title>Garmin Smartphone Link - Ideas for Improvements &amp; New Features</title><content type="html">If you read this blog you know my enthusiasm for Garmin's new &lt;a href="https://buy.garmin.com/shop/shop.do?pID=111441" target="_blank"&gt;Smartphone Link app&lt;/a&gt; for Android.&amp;nbsp; If you don't then &lt;a href="http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-revolutionary.html" target="_blank"&gt;read here&lt;/a&gt; to catch up.&amp;nbsp; Here is where I'll keep&amp;nbsp;a running list of all the ideas for fixes, improvements and changes to the Nuvi with Smartphone Link.&amp;nbsp; Here we go:&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Add a proximity alert feature to photoLive traffic cameras. When you drive through the defined point, show a preselected camera video in split screen.&lt;/li&gt;
&lt;li&gt;Provide an indication of bluetooth connection status on the map screen.&lt;/li&gt;
&lt;ul&gt;
&lt;li&gt;In my use of Smartphone Link I've found the bluetooth connection to be generally good but finicky at the same time. I've been driving for awhile and only when I by chance returned to the main menu screen did I learn that the Nuvi wasn't connected via bluetooth.&lt;/li&gt;
&lt;/ul&gt;
&lt;li&gt;Provide an ice warning when the weather data indicates precipitation and the temperature indicates &amp;lt; 32 degrees.&lt;/li&gt;
&lt;li&gt;Show the current temperature on the map screen while in a route. This is important when traveling in near-freezing conditions.&lt;/li&gt;
&lt;li&gt;Develop a "Meeting Travel Planner" in Smartphone Link.&lt;/li&gt;
&lt;ul&gt;
&lt;li&gt;Read my phone's calendar.&lt;/li&gt;
&lt;li&gt;Read the address from my calendar appointment's Location field.&lt;/li&gt;
&lt;li&gt;Obtain my phone's current location.&lt;/li&gt;
&lt;li&gt;Calculate the travel time to my next appointment in the Garmin Cloud.&lt;/li&gt;
&lt;ul&gt;
&lt;li&gt;Take knowledge of current traffic conditions into account.&lt;/li&gt;
&lt;/ul&gt;
&lt;li&gt;Alert me on my smartphone that I need to leave for the appointment, including a user defined amount of extra minutes.&lt;/li&gt;
&lt;li&gt;Pass the destination from the calendar appointment's Location field to my Nuvi.&lt;/li&gt;
&lt;li&gt;Send me on my way.&lt;/li&gt;
&lt;/ul&gt;
&lt;/ul&gt;
Subscribe to this blog to be notified as I add more ideas.&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/mUF_mWXIOus" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/5002059111039155240/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-ideas-for.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/5002059111039155240?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/5002059111039155240?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/mUF_mWXIOus/garmin-smartphone-link-ideas-for.html" title="Garmin Smartphone Link - Ideas for Improvements &amp; New Features" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-ideas-for.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkACRHcyeCp7ImA9WhRVFE4.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-255995173936436606</id><published>2012-01-12T22:59:00.003-06:00</published><updated>2012-01-12T22:59:25.990-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-12T22:59:25.990-06:00</app:edited><title>GSM or CDMA? Why YMMV with Garmin's Smartphone Link</title><content type="html">I'm a couple days into the use of Garmin's Smartphone Link with my Nuvi 3490LMT. &amp;nbsp;&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Today my 2 hour drive included a 1 hour conference call. &amp;nbsp;The Nuvi bluetooth provided for an easy, safe method of carrying on a conference call for that length of time. &amp;nbsp;I really don't need to carrier my Motorola T505 bluetooth speakerphone anymore. &amp;nbsp;One less device in my bag!&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Bored, and 15 minutes into the call I realized that I no longer had traffic content. &amp;nbsp;Duh! &amp;nbsp;I have a CDMA phone. &amp;nbsp;And of course we all know from the AT&amp;amp;T iPhone commercials that only AT&amp;amp;T (GSM) allows you to enjoy simultaneous voice and data. &amp;nbsp;Using Verizon? Sprint? Another regional carrier using CDMA technology? Nope. &amp;nbsp;Sorry. You can have voice or data, but not both at the same time on the 3G network.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
When Garmin fixes the Smartphone Link and GMT-60 issues so that Smartphone Link Live Traffic can be used while plugged into the GMT-60 I hope that Garmin thinks through how the Smartphone App and the GMT-60 should work for CDMA customers.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Without any proof to back up this statement, I am going to go out on a limb and suggest that today's typical customer of a $400 PND and the Smartphone Link app is a tech-savvy road warrior. &amp;nbsp;And being one of those likely means phone calls while on the road are a regular&amp;nbsp;occurrence.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Based on what we know today, the HD Radio Traffic from the GMT-60 appears to take a back seat to Smartphone Link Live Traffic. &amp;nbsp;This means that it appears that if Smartphone Link is active and connected to your phone, the Nuvi uses Live Traffic only and not HD Traffic.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Take a phone call on a CDMA network though, and you've got a problem. &amp;nbsp;While your Smartphone Link app and Nuvi are still bluetooth connected during a voice call, your phone isn't receiving data from your CDMA cellular carrier so your Nuvi isn't receiving any traffic content from your phone. &amp;nbsp;Take a call on a long stretch of rural Interstate - no problem. &amp;nbsp;Take a call during the last 15 miles into downtown Chicago and you've got a problem!&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
If your using Smartphone Link, your Nuvi has this perfectly good GTM-60 HD Radio Traffic receiver sitting around doing nothing but providing power - it &lt;i&gt;should&lt;/i&gt;&amp;nbsp;be able to provide traffic content to your Nuvi in the event of a loss of content from the Smartphone Link app.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
It is my hope that Garmin improves the detection and switchover of traffic sources between Smartphone Link Live Traffic and GTM-60 HD Radio traffic in an intelligent way. &amp;nbsp;Clearly the Nuvi knows that the phone is in voice call mode because the Nuvi is capable of handling the call. &amp;nbsp;I think that Garmin should include logic where the Nuvi automatically switches to the GTM-60 HD Traffic receiver when the phone is in a voice call state. &amp;nbsp;Garmin could include a menu setting that asks the customer what cellular carrier they are using (or detect it somehow through the Smartphone Link app - is that possible?). &amp;nbsp;For GSM carriers - no switchover is necessary. &amp;nbsp;For CDMA carriers the switchover could be implemented.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
With both the GTM-60 and Smartphone Link at the Nuvi's disposal, I hope Garmin doesn't settle for a complete loss of traffic content during a CDMA voice call as being an acceptable operating scenario just because one of two available sources isn't available any more. &amp;nbsp;Switch us to the other source Garmin - please!&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/jzldTxzb0HI" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/255995173936436606/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/01/gsm-or-cdma-why-ymmv-with-garmins.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/255995173936436606?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/255995173936436606?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/jzldTxzb0HI/gsm-or-cdma-why-ymmv-with-garmins.html" title="GSM or CDMA? Why YMMV with Garmin's Smartphone Link" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/01/gsm-or-cdma-why-ymmv-with-garmins.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0cDRHo-fSp7ImA9WhRVFE8.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-8245733232735288791</id><published>2012-01-12T22:31:00.001-06:00</published><updated>2012-01-12T22:31:15.455-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-12T22:31:15.455-06:00</app:edited><title>A Note About Me</title><content type="html">I am self-admitted GPS fanatic. &amp;nbsp;I have been for years. &amp;nbsp;I remember my first rental car when the Hertz Neverlost system was first rolled out. &amp;nbsp;When I learned that this was actually a rebranded Magellan system that consumers could buy I was elated - until I found out the cost. &amp;nbsp;The technology was&amp;nbsp;reminiscent&amp;nbsp;of cellular bag phones. &amp;nbsp;There was a huge "black box" that had to be hidden away somewhere with multiple cables running to the head unit. &amp;nbsp;And then I found Garmin and their StreetPilot III and I've never looked back. &amp;nbsp;Oh how fun those days were - when full map coverage meant a combination of City Navigator and MetroGuide and you hoped like hell that those two products matched up at their boundaries. &amp;nbsp;I remember a route from Des Moines to Madison, WI where the GPS told me the electronics equivalent of "you can't get there from here." &amp;nbsp;
We've come a long way since those days!&lt;div&gt;
&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Here is my GPS experience since then:&lt;/div&gt;
&lt;div&gt;
&lt;span style="background-color: white; color: midnightblue; font-family: Verdana, Arial, Helvetica;"&gt;&lt;span style="font-size: x-small;"&gt;Nav experience: Garmin SP III, SP 2710, SP 2730, Garmin i5, Garmin c330, Garmin 760, Garmin 885T, Dash Navigation, TeleNav for Sprint, TomTom 740 Live, CoPilot Live v8, Navigon for Android, Navigon for iPad, ALK CoPilot Premium, Google Navigation, Waze, Garmin Nuvi 3490LMT w/ Garmin Smartphone Link.&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;
&lt;span style="background-color: white; color: midnightblue; font-family: Verdana, Arial, Helvetica; font-size: xx-small;"&gt;&lt;br /&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;
I've actually owned and used all of those devices - some for hundreds of miles, some for thousands, many for tens of thousands. &amp;nbsp;In every case either the technology moved on, or I moved on from the technology (the i5? Wow was that painful!). &amp;nbsp;Each product's story is different - why I bought it and why it ran out of favor with me.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
And now I found myself with the Garmin Nuvi 3490LMT w/ Smartphone Link. &amp;nbsp;It is, without a doubt, the single best overall navigation experience I've had. &amp;nbsp;The Nuvi 3490LMT by itself is not. &amp;nbsp;I let that product stay on store shelves for a long time, until the day that Garmin announced Smartphone Link. &amp;nbsp;Once it was announced (it's announcement was a surprise to me), I was at Best Buy within 2 hours with a 3490LMT in hand. &amp;nbsp;A month ago I would have been the first to tell you that there is no role for a $399 PND in a $299 smartphone world. &amp;nbsp;Smartphone Link proved me wrong.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
I have an order placed for the 3590LMT as well. &amp;nbsp;I look forward to its ship date. &amp;nbsp;And when it arrives, my wife will enjoy a very nice 3490LMT product while I will take over the 3590LMT as my main GPS device.&lt;/div&gt;
&lt;div&gt;
&lt;br /&gt;&lt;/div&gt;
&lt;div&gt;
Garmin has nailed it with the Smartphone Link app, initial problems aside, and I look forward to many miles of enjoyment.&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/yzwlx0A4OhY" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/8245733232735288791/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/01/note-about-me.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/8245733232735288791?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/8245733232735288791?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/yzwlx0A4OhY/note-about-me.html" title="A Note About Me" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/01/note-about-me.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CE8EQn8yfCp7ImA9WhRVFEw.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-7746665579975469589</id><published>2012-01-12T18:00:00.000-06:00</published><updated>2012-01-12T18:00:03.194-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-12T18:00:03.194-06:00</app:edited><title>Navigation Test - 1 Route, 8 Products</title><content type="html">There are a a lot of reasons why people choose navigation products.&amp;nbsp; Today, there are a lot of choices to pick from.&amp;nbsp; Smartphone navigation has gained popularity in recent years on both Android and iOS platforms.&amp;nbsp; Dedicated PND's have seen their market share decline but they continue to try to innovate.&amp;nbsp; Garmin's release of Smartphone Link for Android is perhaps one of the most innovative approachs to the PND that we've seen in the last couple years.&amp;nbsp; I wrote about it &lt;a href="http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-revolutionary.html" target="_blank"&gt;here&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
Arguably though, what matters most is accurate maps and timely ETA's.&amp;nbsp; Who meets that challenge the best?&amp;nbsp; I decided to try and find out.&amp;nbsp; I have, at my disposal, a Garmin Nuvi 3490LMT, a TomTom 740 Live,&amp;nbsp;an iPad 3G and a Samsung Galaxy S2 Android smartphone.&amp;nbsp; Here is who I tested: Google Navigation, Telenav (for Android), Navigon* (for iPad), Mapquest (for Android), Waze (for Android), MotionX Drive, TomTom (TeleAtlas), Garmin (Navteq).&amp;nbsp; All products used were the current versions of the app, or current version of an available&amp;nbsp;downloadable map.&amp;nbsp;&lt;span style="font-size: x-small;"&gt; &lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;span style="font-size: x-small;"&gt;* Note: this test was done prior to Navigon's new app with the optional map update subscription, however,&amp;nbsp;the test did include&amp;nbsp;the most recent map version Navigon made available at the time. I could not test ALK CoPilot because they can't get their new&amp;nbsp;software to run on some (my) US variant of the Samsung Galaxy S2.&lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;
There is a particularly challenging route in the Midwest that really separates the men from the boys when it comes to routing algorithms and map accuracy.&amp;nbsp; It is the route from Des Moines, IA to St Louis, MO.&amp;nbsp; Here is what that route looks like:&lt;br /&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://2.bp.blogspot.com/-muh2oXX8gso/Tw7k_B56I3I/AAAAAAAAONs/L-F_KmxAr38/s1600/route.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="330" src="http://2.bp.blogspot.com/-muh2oXX8gso/Tw7k_B56I3I/AAAAAAAAONs/L-F_KmxAr38/s400/route.JPG" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
I picked this route because it provides so many challenges to overcome when determining the best route.&amp;nbsp; The highlighted route is, in my opinion, the best route to take.&amp;nbsp; Why?&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;99% of this route is a 4-lane divided US or State highway at a speed limit of 65 mph, with some limited 55 mph zones near towns.&amp;nbsp; &lt;/li&gt;
&lt;li&gt;There is only 1 through-town section where your speed has to reduce to slower speeds.&amp;nbsp; But it is also a good, and necessary, gas stop along the way.&lt;/li&gt;
&lt;li&gt;It is one of the shortest options when total miles are considered.&lt;/li&gt;
&lt;/ul&gt;
What makes this route challenging?&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;About 60% of this route is known as the Avenue of the Saints. This is a federally designated highway system connecting St Louis, MO to St Paul, MN.&lt;/li&gt;
&lt;ul&gt;
&lt;li&gt;The Avenue of the Saints starts in St Louis and the route above follows it completely until the route turns directly west halfway between Keokuk, IA and Mt Pleasant, IA.&lt;/li&gt;
&lt;li&gt;Note: The Avenue of the Saints continues directly north from where this route diverts to the west, through Iowa City, IA and eventually up to St. Paul, MN.&lt;/li&gt;
&lt;/ul&gt;
&lt;li&gt;To create this Avenue of the Saints, extensive construction was required over about a decade, to make this route 4 lane.&lt;/li&gt;
&lt;li&gt;As part of this extensive construction, a significant number of highway bypasses were constructed around small towns.&amp;nbsp; What used to be a 2 lane highway directly through many small towns is now a 4 lane highway bypass around nearly all of those towns.&lt;/li&gt;
&lt;li&gt;This route uses almost no freeways until the last 25 miles in the metro St. Louis area.&lt;/li&gt;
&lt;li&gt;There are many tempting alternatives.&lt;/li&gt;
&lt;ul&gt;
&lt;li&gt;Des Moines to Kansas City to St Louis - it's all freeway.&lt;/li&gt;
&lt;li&gt;Des Moines to Davenport to Peoria to St Louis - it's all freeway.&lt;/li&gt;
&lt;li&gt;Des Moines to Iowa City then south to join this route - it's more freeway at least.&lt;/li&gt;
&lt;/ul&gt;
&lt;/ul&gt;
As you can see, this route is a great test. It tests the company's map accuracy.&amp;nbsp; It tests their road speed accuracy.&amp;nbsp; It tests their algorithm.&amp;nbsp; It test their bias for things like freeways.&amp;nbsp; And it tests their ETA accuracy.&lt;br /&gt;
&lt;br /&gt;
&lt;em&gt;This route, with an actual speed that averaged no more than 5 mph over the posted speed limit took &lt;strong&gt;&lt;u&gt;5 hours and 35 minutes&lt;/u&gt;&lt;/strong&gt; to drive with 2 refreshment stops that included a gas fill-up along the way.&lt;/em&gt;&lt;br /&gt;
&lt;br /&gt;
Obviously, I could not use all 8 of these solutions while driving.&amp;nbsp; Instead, while parked at my starting location, I calculated a route to the same final address on all&amp;nbsp;8 products and immediately recorded the resulting ETA.&amp;nbsp; I did this on all 8 devices within 5 minutes of each other.&amp;nbsp; I calculated the route at approximately 10:00pm CST in hopes of minimizing any bias from traffic reports.&lt;br /&gt;
&lt;br /&gt;
Here is how they did:&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;Google Navigation: 6 hours 37 minutes (off by +1 hour 2 minutes)&lt;/li&gt;
&lt;li&gt;Telenav: 6 hours 28 minutes (off by + 53 minutes)&lt;/li&gt;
&lt;li&gt;Navigon: 7 hours&amp;nbsp;0 minutes (off by +1 hour 25 minutes)&lt;/li&gt;
&lt;li&gt;Mapquest: 6 hours 16 minutes (off by + 41 minutes)&lt;/li&gt;
&lt;li&gt;Waze: 6 hours 34 minutes (off by +59 minutes)&lt;/li&gt;
&lt;li&gt;&lt;span style="color: red;"&gt;MotionXDrive: 7 hours 11 minutes (worst result, off by +1 hour 36 minutes)&lt;/span&gt;&lt;/li&gt;
&lt;li&gt;TomTom: 5 hours 53 minutes (off by +18 minutes)&lt;/li&gt;
&lt;li&gt;&lt;span style="color: #6aa84f;"&gt;Garmin: 5 hours 44 minutes (off by +9 minutes)&lt;/span&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://1.bp.blogspot.com/-D-bXyzpmIHo/Tw7sQsX93eI/AAAAAAAAON0/Qn6f87jtfVs/s1600/routegraph.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="416" src="http://1.bp.blogspot.com/-D-bXyzpmIHo/Tw7sQsX93eI/AAAAAAAAON0/Qn6f87jtfVs/s640/routegraph.JPG" width="640" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;span style="color: black;"&gt;This is a single route.&amp;nbsp; This is not a comprehensive test of different routes. It is not a scientific test.&amp;nbsp; It is simply one real world example that applies to me personally.&amp;nbsp; For this route, on this day, there are some interesting conclusions:&lt;/span&gt;&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;The so-called advantage of "online" maps isn't an advantage at all.&lt;/li&gt;
&lt;ul&gt;
&lt;li&gt;Online maps &lt;em&gt;should&lt;/em&gt; be more accurate because the latest maps is always available.&lt;/li&gt;
&lt;li&gt;In practice, for this route, every online map provider fails to live up to that claim and has squandered the leverage they &lt;em&gt;could&lt;/em&gt; have.&lt;/li&gt;
&lt;li&gt;Online maps were actually some of the worst performers in the test.&lt;/li&gt;
&lt;/ul&gt;
&lt;li&gt;There is a curious difference between Navigon and Garmin - both Navteq customers.&lt;/li&gt;
&lt;ul&gt;
&lt;li&gt;There could be differences between Navigon and Garmin's routing algorithm that accounts for the some of the difference in time.&amp;nbsp; In my experience, they are pretty close generally, on other routes.&lt;/li&gt;
&lt;li&gt;More likely, we are seeing a real life example of what Navteq gets accomplished in sequential map updates. As I stated above, this test was done before Navigon changed to their new quarterly subscription update option. Therefore, the Navteq maps in their app were&amp;nbsp;older than the Navteq maps in the Garmin Nuvi.&lt;/li&gt;
&lt;/ul&gt;
&lt;li&gt;The crowd-sourced map approach doesn't yield best in class results.&amp;nbsp; Both Google Navigation and Waze are in the middle of the pack when it comes to the route time.&lt;/li&gt;
&lt;ul&gt;
&lt;li&gt;While Google &lt;em&gt;did&lt;/em&gt; select my opinion of the ideal route, their ETA is way too conservative - a common complaint about Google Navigation.&lt;/li&gt;
&lt;/ul&gt;
&lt;li&gt;Crowd-sourced "real world" speeds seem to be having an impact. TomTom IQRoutes, once considered the king of "real world" driving conditions seems to be continuing to hold its own, at least in this limited test.&lt;/li&gt;
&lt;li&gt;Garmin's ETAs were always pretty good.&amp;nbsp; It appears that with their map data now incorporating trafficTrends functionality, that their ETAs might be getting even better.&amp;nbsp; They clearly were spot on in this test.&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/cSGlKlms60A" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/7746665579975469589/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/01/navigation-test-1-route-8-products.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/7746665579975469589?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/7746665579975469589?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/cSGlKlms60A/navigation-test-1-route-8-products.html" title="Navigation Test - 1 Route, 8 Products" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/-muh2oXX8gso/Tw7k_B56I3I/AAAAAAAAONs/L-F_KmxAr38/s72-c/route.JPG" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/01/navigation-test-1-route-8-products.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkANQ3c-fyp7ImA9WhRUEEw.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-4214499868391617362</id><published>2012-01-12T10:45:00.000-06:00</published><updated>2012-01-19T17:13:12.957-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-19T17:13:12.957-06:00</app:edited><title>Strike 1 for Garmin Support's Response on Smartphone Link</title><content type="html">I've documented, in detail, my problem, testing and conclusions about a potential conflict between Garmin's new Smartphone Link Live Traffic service and the GTM-60 HD Radio Traffic service. You can read about that in detail by clicking &lt;a href="http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-live-traffic.html" target="_blank"&gt;here&lt;/a&gt; and &lt;a href="http://jkcarp.blogspot.com/2012/01/further-testing-of-garmin-smartphone.html" target="_blank"&gt;here&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
I also did what any good customer should do and filed a detailed support ticket using the Contact Us support feature on Garmin's website.&amp;nbsp; They have a specific menu selection for the mobile team, and the Smartphone Link product.&amp;nbsp; I would assume then, that this would go to someone knowledgable about the Smartphone Link app - someone who could start to assist in solving this problem.&lt;br /&gt;
&lt;br /&gt;
Arrogance is not something I like.&amp;nbsp; But&amp;nbsp;good lord Garmin, between my email below and this blog, I've spoon fed you 1000% times more than&amp;nbsp;most consumers are going to on this&amp;nbsp;problem.&amp;nbsp; Solve it.&amp;nbsp; Don't blow me off with marketing auto replies and call that support.&lt;br /&gt;
&lt;br /&gt;
Here is what I sent Garmin (click to enlarge):&lt;br /&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://4.bp.blogspot.com/-n61YazpNujk/Tw8CumOoPAI/AAAAAAAAON8/7pmKkMsg-Bo/s1600/problem.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="107" src="http://4.bp.blogspot.com/-n61YazpNujk/Tw8CumOoPAI/AAAAAAAAON8/7pmKkMsg-Bo/s400/problem.JPG" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
And here is the ridiculous response that I got (click to enlarge):&lt;br /&gt;
&lt;br /&gt;
&lt;div class="separator" style="clear: both; text-align: center;"&gt;
&lt;a href="http://1.bp.blogspot.com/-7_ichllCy-M/Tw8C573V5jI/AAAAAAAAOOE/OHp_YrcnCJI/s1600/response.JPG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="191" src="http://1.bp.blogspot.com/-7_ichllCy-M/Tw8C573V5jI/AAAAAAAAOOE/OHp_YrcnCJI/s400/response.JPG" width="400" /&gt;&lt;/a&gt;&lt;/div&gt;
&lt;br /&gt;
In response to a detailed technical support question, complete with screen shot example links, I get back basically an auto-reply&amp;nbsp;marketing brochure for the product that I am having a problem with.&amp;nbsp; Note:&amp;nbsp; this is NOT the auto-reply that I got immediately after filing the support claim.&amp;nbsp; This is the "personal support" response that I waited 3 business days for.&lt;br /&gt;
&lt;br /&gt;
I actually did call the 800 support number the night that I started having this problem.&amp;nbsp; Her response was "Is Smartphone Link a Garmin product?"&amp;nbsp; "Where did you get it?"&amp;nbsp; "What does it do?"&amp;nbsp; Really Garmin?&lt;br /&gt;
&lt;br /&gt;
So between a clueless telephone support response and a I-could-care-less email auto-reply response, it appears that Garmin support is about what it was when I quit using my 885T out of frustration - useless for anyone that happens to know a thing or two about technology and electronics.&lt;br /&gt;
&lt;br /&gt;
Really Garmin?&amp;nbsp; Is this the best you have to offer your customers who are purchasing your latest and greatest products?&amp;nbsp; Frustrating beyond belief.&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/Be4b_yjABUg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/4214499868391617362/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/01/strike-1-for-garmin-supports-response.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/4214499868391617362?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/4214499868391617362?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/Be4b_yjABUg/strike-1-for-garmin-supports-response.html" title="Strike 1 for Garmin Support's Response on Smartphone Link" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/-n61YazpNujk/Tw8CumOoPAI/AAAAAAAAON8/7pmKkMsg-Bo/s72-c/problem.JPG" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/01/strike-1-for-garmin-supports-response.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0EHRX88eyp7ImA9WhRVE04.&quot;"><id>tag:blogger.com,1999:blog-8100718645327131363.post-1746185623453454474</id><published>2012-01-11T21:40:00.002-06:00</published><updated>2012-01-11T21:40:34.173-06:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-01-11T21:40:34.173-06:00</app:edited><title>Impress your Siri-Loving Friends: Garmin's Smartphone Link &amp; SpeakToIt Assistant - Your iPhone Can't Do This!</title><content type="html">&lt;a href="http://www.apple.com/iphone/features/siri.html" target="_blank"&gt;Siri&lt;/a&gt; is cool. No question. &amp;nbsp;But it can't do it all. &amp;nbsp;Once in awhile I love to show my "no one does it better than Apple" friends something that someone does better than Apple. &amp;nbsp;That day has arrived with Garmin's &lt;a href="http://sites.garmin.com/smartphonelink/android.php" target="_blank"&gt;Smartphone Link&lt;/a&gt; app for Android, a compatible Garmin Nuvi and &lt;a href="https://market.android.com/details?id=com.speaktoit.assistant&amp;amp;hl=en" target="_blank"&gt;Assistant by Speaktoit&lt;/a&gt;. &amp;nbsp;This is the closest you can get today, to natural language processing on a PND.&lt;br /&gt;
&lt;br /&gt;
I've &lt;a href="http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-revolutionary.html" target="_blank"&gt;previously covered&lt;/a&gt; the awesome (and largely undocumented) features of the Smartphone Link app. Smartphone Link combined with Assistant by Speaktoit provides you with one of the most user friendly and fast navigation interfaces that I've ever seen.&lt;br /&gt;
&lt;br /&gt;
Using Assistant by Speaktoit is beyond the scope of this post. &amp;nbsp;But it is voice recognition - how hard can it be, right? &amp;nbsp;The Assistant app can be started on Android in a number of ways. &amp;nbsp;A simple application shortcut can be installed on your main screen. There is a widget available for quicker access directly to the voice recognition engine. &amp;nbsp;Or the app can even be assigned to the long-press of the search key on your phone. &amp;nbsp;Take your pick.&lt;br /&gt;
&lt;br /&gt;
Now for the Garmin integration. &amp;nbsp;Check it out:&lt;br /&gt;
&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;Start Assistant using the method of your choice discussed above.&lt;/li&gt;
&lt;li&gt;Speak your search such as "Show me the nearest coffee shops."&lt;/li&gt;
&lt;li&gt;Within Speaktoit, you will see a Google Map "widget" of the nearest coffee shops.&lt;/li&gt;
&lt;li&gt;Press the large quadruple arrow button (looks like a&amp;nbsp;cartoonish&amp;nbsp;"X' button) in the upper right hand corner to open the Google Maps app. &amp;nbsp;Speaktoit passes your spoken search query to Google Maps automatically.&amp;nbsp;&lt;/li&gt;
&lt;li&gt;Now that Google Maps is open, follow the instruction in &lt;a href="http://jkcarp.blogspot.com/2012/01/garmin-smartphone-link-revolutionary.html" target="_blank"&gt;my previous blog post&lt;/a&gt;&amp;nbsp;to pass this to your Nuvi.&lt;/li&gt;
&lt;/ol&gt;
&lt;div&gt;
This may seem like a&amp;nbsp;convoluted&amp;nbsp;process. &amp;nbsp;In reality it takes about 10 seconds from the time you speak your search to the time your Nuvi has the address. &amp;nbsp;Do it twice and it will become second nature. Handsfree. Voice Recognition. Natural Language Search. Fast.&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/blogspot/nrDSI/~4/Yc84xzG-fEs" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://jkcarp.blogspot.com/feeds/1746185623453454474/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://jkcarp.blogspot.com/2012/01/impress-your-siri-loving-friends.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/1746185623453454474?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8100718645327131363/posts/default/1746185623453454474?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/blogspot/nrDSI/~3/Yc84xzG-fEs/impress-your-siri-loving-friends.html" title="Impress your Siri-Loving Friends: Garmin's Smartphone Link &amp; SpeakToIt Assistant - Your iPhone Can't Do This!" /><author><name>Jeff Carpenter</name><uri>https://plus.google.com/101152350674312372772</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh6.googleusercontent.com/-lK3yI1sc-vM/AAAAAAAAAAI/AAAAAAAATcg/WadhWk91zJU/s512-c/photo.jpg" /></author><thr:total>0</thr:total><feedburner:origLink>http://jkcarp.blogspot.com/2012/01/impress-your-siri-loving-friends.html</feedburner:origLink></entry></feed>
