Tuesday, June 17, 2014

Garmin surprises with Android navigation app "viago" - First Impressions

Garmin, once unquestionably the navigation leader, has an interesting way of trying to keep itself relevant. Of late it seems that Garmin does so right about the time you almost stop thinking about them.  This week is no exception.

Garmin has finally made a real Android play by releasing a standalone Android app called viago.  Garmin has dabbled with Android before when it created the defunct nuvifone.   At that time Garmin couldn't shake their fixation on producing hardware.  Many of us argued that the Garmin name wasn't strong enough to dictate the consumer's smartphone hardware and mobile carrier choice and eventually that reality played out. The nuvifone was discontinued.  Many critics said Garmin needed to start thinking like a software developer.  After having an iOS app for some time Garmin appears to be moving into the pure software development world head-on with this new Android play.

I've downloaded and used the viago app for a short time.  I've explored the features and settings.  I've taken some drives.  The viago app is a nice looking, solid v1.0 entry into the market.  The problem is that this is a v1.0 entry and it is 2014.  This app would be a great play if it were 2012.  It isn't.  For that reason, it underwhelms given where Garmin's competitors are at with their product plays.

Competitors Google Maps, TomTom, Waze, Scout (Telenav), MapQuest, CoPilot and Sygic are all multiple generations into their product offerings.  I'd expect the supposed industry leader, when it finally makes a market play, to do so with force - to blow away the current offerings with something new, fresh and unique.  Instead, what Garmin has given us is a "me too" app that lacks in basic features.  At the same time, they include things that attempt to differentiate like Real Directions.  What good is that kind of differentiation however, when you haven't nailed the basics yet?

Lacking in basically features is fully expected with a 1.0 product some will argue.  Unfortunately with Garmin being this late to the game, they needed this 2014 release to be their 2.0 attempt.  A 1.0 release from Garmin doesn't cut it in 2014.

I'll hit the deal-breaker (for me) first.  Garmin has failed to register the viago app as an Android intent handler for any 3rd party apps.  Intent handling (the ability to open one app with specific content obtained from another app) is the beauty of Android smartphones.  It is also a fantastic feature in every Android navigation app I've used (and I've used every one of those mentioned above).  All of them allow you to click on an address in Contacts, Calendar, Yelp, Tripadvisor, etc., and pick their navigation app as the destination of that address search.  You get one-click navigation to that address with the navigation app of your choice.  Sadly, Garmin has missed the boat on that important feature.  I clicked on an address in my Contact app and the image below is what I received.  (I've removed most of the navigation apps noted above from my phone).  Garmin viago is not listed as a choice and that is a huge oversight.  Who decides to release this without that simple, core Android feature?

Garmin's viago not shown as an Android intent handler



The next biggest "what are they thinking" issue with viago is that it doesn't have "Search Along Route" functionality.  Granted, this is a missing feature in Google Maps too, but Google Maps is free.  It doesn't have to be better, it just has to be "good enough" to beat Garmin.  The comparison is TomTom, CoPilot, Scout, and the other paid apps.  All of them have this important feature and Garmin decided to leave it out for this v1.0 release.  I can't attempt to understand the logic of that decision.

Yet, Garmin did decide to implement a trip planner where you can enter multiple via points along a route to your destination.  Now, my typical use of a trip planner may be different than the norm, but I like to calculate a route from my origin to my destination.  From there, I like to "search along the route" just calculated to find gas stations, food stops, hotels, or maybe even attractions along the way.  Alas, there is no way to do that because Garmin left out search along the route.  Perhaps others use the trip planner in another way but I find that it completely misses the mark without this search capability.

Visually, I like this app.  It is clean and the user interface has the potential to be straightforward.

The nicely done UI of Garmin viago



I don't like how Garmin has split up various features and settings between two different menus.  The traditional Android menu (the three horizontal lines at the top right) doesn't actually contain Settings.  Instead, Garmin has placed settings in a second menu that is accessible by clicking on the blue triangle in the upper left.  I can see the upper left blue triangle being the place to put navigation specific commands and features but it should not contain Settings (or Shop or Tools), especially when Garmin is also using the standard Android menu symbol.  If they are going to use it, then that is where you should put Settings.

This is all Garmin is using the standard Android menu for:

Garmin's use of Android's standard menu command

Clicking on the Traffic option gives you an incident list.

Traffic incident list


It is disappointing to find that you can't see traffic incidents when casually browsing an area overview map.

No traffic shown at the scale of a metro overview map
Compare this to Google Maps which allows you to see an entire metro area's traffic situation at a glance:

Google Maps, in comparison, nicely shows overall traffic conditions on a metro overview map


The traffic information that is displayed during a route was not a great experience.  As you can see in the image below, the traffic information area takes up a lot of screen real estate.  When you combine that with the inefficient use of space for the next turn text you end up with a very small map area.  There is an blue 'x' next to the display of the current street (106th St) but when you click on it instead of closing the current street line it closes the traffic section instead.

The UI becomes much less functional and the map much smaller, with traffic content displayed

I've tried to understand the traffic bar implementation on this app and I just can't make sense of it.  Clearly I understand that there are 2 traffic incidents that are causing a 2 minute delay.  However, I don't understand the information being conveyed in the traffic bar that contains the yellow line.  If the traffic bar represents my total route and the yellow bar represents the "location" of the traffic slow down along my route then it would be helpful if the bar actually moved while I progressed on the route.  It didn't though.  It stayed static.   So I really have no idea where that yellow section was compared to my actual location in the route.  I also am not sure if the yellow bar and the orange symbol represent 2 different incidents or not?  Is the yellow bar traffic flow data while the orange banner is a construction incident?  I also don't know if the 1 mile represents the distance that the construction is away from me now, the distance the construction is away from the start of my route or the length of the construction "section" in the road itself?  It is a very confusing implementation of traffic given that there is no movement of or along the bar while driving.

Below is a screen shot that is even more confusing.  I am 0.2 miles from my destination (literally about 1 minute).  There is no construction or traffic involved in the route any longer.  Yet, the display still shows 2 traffic issues with a 2 minute delay.  It no longer shows the yellow bar but does show the orange construction icon.  None of this makes any sense to me.  Why is it showing traffic that is in the past?  It doesn't mean anything to me any more because I'm already through it.  I just am not understanding Garmin's thought process on how they are presenting traffic information at all.

Very confusing traffic implementation showing traffic conditions in the past


For comparison, here is Google's presentation along the same route.  There is quite a difference in the space made available for the map.  To each their own on this issue but I don't believe that Garmin has done much to optimize their use of screen real estate, mainly due to the unnecessary amount of space dedicated to the traffic information.


Google Maps' use of screen real estate as a comparison


This is what is found in Garmin's blue triangle menu.  They've got the placement of Tools, Shop and Settings in the wrong menu in my opinion and I hope they change it.

Garmin's blue triangle menu options

My Destinations is the place to find your saved favorites as well as your recently found destinations.  Contacts is a nice feature to see however it was implemented without search capability so it is almost useless.  The only option within Contacts is to browse a list - useless for someone with hundreds or thousands of contacts.

I did use the Contacts feature of the app though and browsed to various contacts.  It failed 100% of the time to reconcile the address.  These addresses are in the Android People app found on the Nexus 5 with Android 4.4.3 and the People app is synchronized to an Exchange server.  The screenshot below shows one contact that I tried which, like all my other contacts, reconciles nicely in Google Maps.

Reconciling a Contact's address in Google Maps


However, like every other contact I tried, the address did not reconcile in Garmin's viago app.  It appears that Garmin is not parsing the address text correctly and is attempting to put the entire address in the street name cell.  Of course this wouldn't be an issue at all if Garmin wasn't using such an archaic means of address entry in the first place.

Garmin's viago can't parse the same Contact


Settings offers a nice selection of things to avoid on the route.  The inclusion of carpool lanes is a big plus and an omission from Google Maps (but not TomTom) that is very convenient in a few major cities.  I much prefer the TomTom implementation to avoidances though.  TomTom asks you on every route if it detects that item on the route during calculation.  This approach matches reality as there are some routes that I know about an unpaved road or a toll and I also know the consequences of avoiding them.  I will decide to use those items for that route while wanting to avoid them completely on a different route.  TomTom is unique in that regard.   All other vendors, including this Garmin viago app require you to change the settings each time in order to have that flexibility.

Navigation avoidance options


The shortcomings of this app begin to be evident as soon as you start exploring the navigation features within the blue triangle menu.  Selecting the "Where To?" option brings up a very nuvi-familiar list of choices:

Garmin viago's Where To? menu options


I was disappointed to see that the Address entry process was an old-school process of separate text-entry fields for each portion of the address.  Yes, that is correct. Despite knowing the ease of address entry in other products that have been available on Android for a long time, the screenshot below is what you get to "fill out" when using Garmin viago.  To make matters worse, there is no text auto-complete so you can't start typing and have the app start to guess the remainder of what you intend to enter.  You must type the whole thing.  Only then, after filling out this 2010 style form do you get to see if what you entered is in the database when you go to the next screen.  Quite frankly I'm stunned that Garmin settled for this archaic method of address entry in this product.  Why viago is not a robust voice recognition platform as its main user interface is beyond me.

It is hard to understand the thought process, when you know that you can literally speak "OK Google, Navigate to 123 Main Street in Anytown, IA" when using Google Maps (and not much more than that with Waze), that someone inside Garmin decided that the method of address entry below was worthy of going live with in 2014.  Stunningly misguided.

Garmin's address entry process

This screenshot is a nice representation of the screen while navigating during a calculated route.  You can see the route statistics at the top (see below for how this can be customized).  You can also see that traffic is being reported within the app and shown on the map.  I've turned on the display of some POI's on the map (you can see the gas station icon).  This does not appear to be working as described by the menus however.  More on that below.  You can also see the speed limit and my current speed.

A nice UI displaying many pieces of information

The three route statistics at the top of the screen are user selectable.  The choices include:

Customization of route statistics in the map view


There are a couple of disappointments to note when looking at the map above.  First, the POI's are not selectable from the map.  Think about driving down the freeway and wanting some lunch.  There is no way to see the Food icon, click it, and see what restaurant it is.  The POI's are displayed and are not interactive.  And of course with no "search along route" functionality, you can't determine what any of those POI's really are when navigating.

The menu shows the screen where you can select the POI categories to show on the map.  You can see the phrase "Unselect All" which implies more than one could be selected.  However, when you select one category from the menu below, it deselects the previously one selected.  That makes little sense given the wording of this menu and is likely a bug that needs to be fixed.

A potential bug prevents multiple POI categories from being selected


You can also display POI categories on the map while browsing the map without navigating.  However, this feels like a feature that isn't finished.  First, the categories don't have visually recognizable icons.  Instead, they have this meaningless blue icon seen below.  Worse, when you click on the blue dot it doesn't tell you what the POI is.  It simple shows the latitude and longitude which is completely worthless.

Like the POI issue show below, you can also long press anywhere on the map to select a location. However, when pressing on a road, Garmin does not reverse geocode that location and display an address.  It only shows the latitude / longitude.  Reverse geocoding and showing the address would be a much more user friendly feature.

Useless display of POI's in map browsing mode


Even when clicking on the 'i' icon you still are not given anything useful.  Here is the result of that click:

Additional info is not helpful


You'll notice in the image above that the standard Android menu icon is present in the Destination screen.  Here is what you get when you click it in this screen though:

Inconsistent menu content results in nothing displayed


Clicking on the speed limit graphic on the map, I expected to be given a menu to indicate an incorrect speed limit.  Instead, I was given the setting below, which is an odd place to hide a setting.  Why not just include it in the main setting menu?  I set this to on, then proceeded to speed up to 50 mph and was not given an alert.

A random setting that doesn't appear to work and isn't in the main app Settings


So, where do I think this Garmin viago v1.0 app positions itself at launch?  It will make Garmin enthusiasts who still use their nuvi but wish they didn't have to very happy.  Google Maps, Waze, Scout and MapQuest users will be underwhelmed by the archaic text entry interface and lack of any voice recognition features.  TomTom users will find the feature set (such as lack of detours, multiple route options, etc.) to be unimpressive.  In the end that leaves Garmin joining the Android club without outmaneuvering anyone and not capturing anyone's attention other than customers that need offline navigation or who still navigate to Garmin for the name.  That is a small and shrinking audience.  The situation will just get worse upon the release of some new competitor's app updates that are currently in beta.  If Garmin was swinging for the fences with viago's release - they missed.

Sunday, May 18, 2014

Did Google put Waze functionality in Google Maps 8.0?

Most commentators were pretty excited by the improvements made to Google Maps for Android 8.0.  Having spent over 13 hours with the update this weekend on a 700+ mile trip I can say that this update is nothing short of extraordinary. The biggest reason for my enthusiasm is a feature that appears to be unadvertised.

While not the focus on my blog post, the lane guidance feature is truly unreal.  I was expecting lane guidance on major freeways in major cities.  What we got instead is lane guidance on local roads in small to midsize towns.  Outstanding!

Lane guidance on local roads!


Now, on to the good stuff....

I am convinced that Google Maps for Android now includes traffic rerouting technology from Waze!

In previous versions, Google Maps included the ability to show multiple routes and to reroute if a quicker route was available (apparently with a 5 minute threshold). In my experience with this however was that this was not a very granule feature.  Before a route was offered as an option the alternative route seemed to have to differ from the original by a fairly significant minimum "threshold percentage" before it was offered as an alternative.  On long trips of several hundred miles, that meant that very small route diversions were never offered because the diversion was too statistically similar to the original route.

Something appears to have changed in version 8. My suspicion is that Google has included some Waze technology into their traffic rerouting algorithm.  Before we get to the reason for my suspicion let's look at the significant change in how Google handles traffic and route options in the new version.

First, Google now displays live traffic conditions on the main map while navigating. That is a huge, welcome change in my opinion.

Second, multiple route options are both automatically displayed and manually available on the main map screen. From my experience this weekend these route options do not appear to be static in any way. They appear to be very dynamic route options, constantly reevaluated using the latest traffic information and also route progress.   As you get closer to your destination the available route options are made more granular as you progress.

Here is a graphic that shows the automatic route options that are displayed on the map as you drive. As traffic conditions change, as you approach an optional route, you'll see right on the map what your options are. Faster options are displayed as are options that are slower.  If you like a presented option you simply click on the banner that says "faster" or "slower."

Alternative routes offered in a local situation
Alternative route offered in a citywide routing situation
The same route options are available in more of an overview perspective by clicking the route button on the map. This allows you to see the route options at your leisure and not wait until you are close upon the maneuver for the automatic display of the option on the map screen.

One huge downside right now is that Google provides no audible alert that a faster route option is being presented. You just have to watch the map. I hope that changes quickly.

Now, on to the reason why I think version 8 includes some Waze technology....I was on a route from Des Moines to Chicago this weekend. That is 300+ miles and there really isn't much of any route choice. I-80 in Iowa is pretty much it. Prior versions of Google Maps would show you options but they were pretty nonsensical such as using US-30 for example.  Slower traffic on I-80 usually meant waiting it out on I-80 because the alternative route such as US-30 is so far out of the way.

On this trip, only about 60 miles into the trip I received a Google Now notification of a Waze-reported accident on I-80. Upon reviewing Google Maps, I was now being shown a 12 mile detour off of I-80 onto county roads, starting before the freeway backup and putting me back on I-80 at the first entrance ramp after the wreck. The detour was 7 minutes faster than sitting in the I-80 traffic.

I've experienced these types of slow downs on I-80 before and I've never had Google Maps offer such a small detour like this. In the past it seemed that these kinds of small detours were not statistically different enough from the original route to he offered by Google.

It seems that now we finally have a real and useful tool to navigate real world traffic problems and my bet is that Google is using technology from Waze to get it accomplished.

Saturday, May 18, 2013

Rand McNally "Good Sam" RVND 7725-LM GPS - First Impressions

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.

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.  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.

I have a long history with personal navigation devices.  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.  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.  I've used each of those over the years, at least for one trip at a minimum. eBay is a wonderful thing!

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.

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 user guide (use the one for the 7720) that does a great job of explaining everything this unit does.  I'll focus on what is not written and share my initial impressions.


Branding of the 7725 on the box

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 Styrofoam before you reach the GPS itself, which is then packed inside of a thin Styrofoam bag within a form-fitting egg crate type shell.  Well packaged and presented.  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.

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 7" tablet. 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.  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.

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.

Size comparison to standard office pen
Yes, this is one thick GPS
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.  There appears to be room for the DC adapter. Putting the AC adapter in this case is not going to happen.

Rand McNally 7" GPS accessory case (sold separately)
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.  The picture below does not do the screen brightness justice. The screen is brighter than in the photo below.

Screen brightness in a car
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 before 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."  Not helpful for the update that was just provided.

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.

OK - let's talk about shortcomings.  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.
  1. No voice recognition.  It seems like a premium GPS sold in 2013 ought to have this.  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.
  2. 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 Magellan RoadMate RV9165T-LM includes lifetime traffic at this same price point. Rand McNally should have included traffic at this price point.
  3. Lack of Bluetooth  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 does work over WIFI is great, don't get me wrong. The issue is that it doesn't work over Bluetooth. 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 Bluetooth  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.
Immediate Dislikes

First of all, I hate the mount. I mean I despise it.  The mount itself is sturdy, built decent (as far as plastic builds can go) and is fully adjustable for any conceivable mounting situation.  However, when it comes to usability, it earns an 'F' and almost earned a chuck out the window on my first day of ownership.  Now, to be fair, if you want to mount this GPS and never move it again, then this mount is just fine.  In fact, it probably works well for that. However, I do not ever leave my GPS device visible on the windshield when parked (even when going into a restaurant or truck stop).  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.  This mount is a disaster if that is your mode of operation.

The 7725 mount. Well made and sturdy.
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.  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.

Mate the GPS slot to the mount's plate. Don't try this without a direct view.
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.

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.

So, I added to my purchase cost and purchased a RAM Mounts X-Grip mount for tablets.  I already have this mount for my smartphone and it is stunningly awesome.  I look forward to using it with the 7725, despite the fact that it increased my purchase price by $45.

RAM Mount X-Grip Tablet mount
Some First Impressions

Having to acknowledge the Warning and Legal Consent screen every single time I turn the device on is lame.   The lawyers from Garmin, Google and TomTom don't seem to think that this is necessary.  Someone needs to go slap the Rand McNally attorneys upside the head and remove this annoyance in a future update.

I love the fact that this device has predictive traffic. 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.  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.  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 en route. I think it is a good combination.

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.

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.  I don't share the complaints others have voiced online about the busyness of the screen or the map being too small.  I've also found that the autozoom function works well so far in my limited use of the device today.

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.  I find the speaker to be a very good quality sound with a volume range that is more than adequate.

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 only releases one map update per year so maps will remain 18 months to 2 years old on this device at best. Quarterly 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.

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), they do not enable WIFI and reconnect to the WAP when power is restored. 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.  I hope that there is not a technical reason that this cannot be changed by Rand McNally.

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. Let's hope that a future update brings us more robust traffic through the WIFI connection.

I like the fact that the device announces whether your destination is on the right or the left.  Navteq data makes this possible.  Nice touch.

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 always 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.

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.

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.

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.

I've run many test routes from my home. In every 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.  I've written an extensive blog post 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.  That is good news.  In other tests where I personally feel a non-interstate route is best, but an interstate route is also available 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.

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?"  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.  I'd like to quickly tell the unit my choice on a route-by-route basis instead of having to change a preference setting.  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.  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.

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.  I hope the Rand McNally adds this feature.

Conclusion

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.  I will be glad to have route planning that is using 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.

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 frustration 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 acknowledged the legal disclaimer every time I turn the device on.

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.  I won't regret not buying the Magellan SmartGPS for this feature but I will wish that my 7725 had it.

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.  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.

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.  We'll see!

Tuesday, February 19, 2013

These retrans disputes are so confusing. I've asked Sinclair and the NAB for help!

Another day, another retrans dispute using customers as pawns in the chess game played by corporate conglomerates.  Since these retrans disputes are so confusing, I've reached out to Sinclair and NAB and asked them for their assistance.  I really hope they help me!

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.

But now I am so confused!  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.  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.  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!

Tuesday, December 11, 2012

Copy2Contact's Ridiculous Apple vs Android Blog Post

I was pretty surprised today to see a blog post today by Copy2Contact with a 5th grade playground "my Dad is bigger than your Dad' post taking sides in the iOS vs Android debate.  I mean, really?  What kind of business potentionally alienates, on purpose, half of their customer base with nonsense unrelated to their core product? Choice can't be left to choice? 

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.  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?"  And for importantly, would I give them any more of my money with this kind of amateur nonsense?  That is a bit harsh, but seriously, read their piece and decide for yourself.  I HOPE that this was a bait piece, in an attempt to simply draw traffic to their site.  If they actually employ someone this void of deductive reasoning skills then heaven help them.

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.

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.   Reminds me of the 50 First Dates mentality.  Live with both options for a couple years and then come back to us with an opinion that is relevant.

Now, let's dissect this blog post piece by piece and decide for yourself if you want to do business with a company this insanely shortsighted about their opinions on technology.

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.

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.

"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.

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.  What was the lifespan between the iPad 3 and the iPad 4 by the way?

"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.  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."  Fragmentation.  Look it up.

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/   What is that you say? Yes, it is malware in the app store. Yes, real, factual, credible information FROM JULY. More flat out factual inaccuracies from this writer.

"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.

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.  Damn you Google.  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.

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.

"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.  This is a CARRIER decision, not Google's decision.  Really? Are you that uninformed?

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.

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?

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.

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.