Cadillac posted a teaser video on YouTube (watch it here) ahead of their August 18th concept car launch event. The teaser video shows their approach to the in-car display technology for the telematics and infotainment system. Cadillac appears to be going with an array of multiple curved OLED displays. We'll see if updates to Cadillac's CUE infotainment system come to the concept car as well.
Discuss this news here.
Anything that's on my mind might appear here but I'll be focused on automotive technology, telematics and navigation, including Android and iOS navigation apps.
Monday, August 15, 2016
Tuesday, July 12, 2016
3200 Miles with CoPilot RV: It's the Best of Bad Choices for RV Navigation
We just returned from a 3200 mile, 12-day RV vacation starting in and returning to Iowa and hitting the states of Illinois, Missouri, Oklahoma, Texas, New Mexico and Kansas. Here's our route:
Six years ago this week, we were on a nearly 4100 mile trip to the east and southeast US. On that trip, in 2010, I road tested ALK's CoPilot app for the first time. A thorough look at my experience with that app became one of my first substantial blog posts. As my now 6 year old blog post outlined, there was good, bad and ugly in my experience with CoPilot. For me, the bad and the ugly outweighed the good and I stopped using the app for many years.
Completely dissatisfied with the current choices available for RV navigation, I immediately spent $50 to purchase CoPilot RV the first day it was released this spring. I was willing to give the app another chance 6 years after my last CoPilot experience. On this trip, for all 3200 miles, I ran CoPilot RV on a Samsung Tab S2 8.0 tablet as well as Google Maps on a Samsung Galaxy Note 5 smartphone. CoPilot was rock solid from a performance and stability perspective. In 3200 miles (48 hours of driving), the app never locked up, froze or crashed once.
Disclosure and About Me: I'm a bit of technology evangelist, both personally and professionally. I have a strong interest in navigation but have not worked professionally in the field. I am a volunteer beta tester for 3 navigation companies and am also a volunteer Google MapMaker Regional Lead. Over the last decade I have owned and used the following solutions: Garmin SP III, Garmin SP 2710, Garmin 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, TomTom for Android, Rand McNally 7725, Rand McNally 7735, Garmin viago, Rand McNally RVND, CoPilot RV for Android.
CoPilot navigation apps have a long history across many different mobile platforms. ALK should be commended for believing in the smartphone navigation space and sticking with it through many years. In general, CoPilot apps are extremely feature-rich, accomplishing nearly every feature you'd find on a traditional dedicated navigation unit. The abundant features make CoPilot RV an attractive alternative for RV navigation. Notable features include:
I'll cut to the chase first and then provide more detail for those interested. The title of this blog post is "It's the best of bad choices for RV navigation." That summarizes my feelings about CoPilot RV. CoPilot has drastically improved in the key feature of route/ETA calculation since my experience in 2010. However, like was the case in 2010, CoPilot RV's map quality remains a significant downfall. Unlike after my 2010 trip with CoPilot, I will continue to use CoPilot RV but will be watching and hoping for other solutions due to the map quality issue. A RV navigation app carries an additional burden of having RV-specific attributes such as weight, height, size and propane restrictions. I'm unclear how ALK suggests customers should have confidence in the accuracy of these very important RV-specific attributes given the persistence map quality issues over the years.
The Details
This blog will not be an exhaustive look at CoPilot's features. My 2010 blog post provides this and actually, the look and feel of the app has remained similar to the 2010 app. Normally that would be a red flag but, despite CoPilot not abiding by any Google material design guidelines in any way, I find it visually pleasing and relatively easy to use. CoPilot does register as an intent handler within Android so clicking addresses within Contacts, Calendar, etc., can be handled by CoPilot automatically.
CoPilot's route/ETA calculation has been fixed from my 2010 experience and is now very good. However, users MUST buy the optional $9.95 annual traffic package in order to experience the improvement. On this trip we traveled 6 - 11 hours per day on our drive days. I found the ETA that CoPilot calculated to be realistic for the total trip time (i.e., inclusive of gas stops). Comparatively, Google Maps' ETA calculation seemed to be more accurate for actual drive time, but would then add time for each gas stop.
My recommendation is simple, do not use CoPilot RV without buying the optional traffic subscription. I'll explain.
Without the optional traffic package, CoPilot has poor "knowledge" of road speeds. CoPilot appears to classify roads in groups of similar road types and then assigns a generic speed to each road type. The user, in a setting that has not changed since 2010, can input custom road speeds for each of the generic road categories, and also select the user's preference for driving on each road type. As you can read in my 2010 blog post, the result, even when using default settings, is disastrous route calculations and ETA times.
Here is an example of a route/ETA calculation in the current CoPilot RV app using the default app settings and not using the optional traffic package. From personal experience, a time of 8:43 is absurd for this route, as CoPilot itself will confirm once you actually activate the traffic package.
CoPilot Support will say "well, just change the default speed to something more realistic." Nope. The problem with that is CoPilot road categories don't distinguish between rural and urban roads when setting custom user speeds. So, if the user sets a divided highway custom speed to 50 mph for example, CoPilot applies that speed to a divided highway whether it runs through rural farm land or is an urban divided highway in the middle of a dense urban area. If the user corrects the ETA in this rural route example by raising the custom speed, it may bring down the 8:43 ETA to something more realistic but the result will also drastically underestimate the ETA in an urban environment where the custom speed cannot be maintained on urban streets badged as a highway. Luckily, CoPilot has "fixed" this problem if you purchase the optional traffic package.
Here is the exact same route with the optional traffic package activated. An ETA of 6:42 is a very realistic calculation for this route. This optional feature saves CoPilot RV from being removed from my Android tablet, never to be used again, like occurred in 2010.
So what is going on here? The optional CoPilot traffic package actually includes two features. The first feature is branded ActiveTraffic, which is real-time traffic content. The second feature is ActiveRoutes, which is essentially historical traffic content. ALK describes it as follows: "ActiveRoutes calculates your route using actual road speeds at the specific time of day and day of week you're traveling."
This means that the generic road category and road category speeds are not used when ActiveRoutes is active. Instead, the route and route ETA is calculated using a massive (3rd party) database of knowledge about actual road speeds and how those speeds vary by time of day. This is how other modern smartphone navigation apps like Google Maps calculate routes and the ETA. This feature is vital to making CoPilot RV usable.
2D View
I believe that most people prefer to use navigation apps in 3D mode (the default view in Google Maps). However, I really enjoy CoPilot RV's 2D view using the "zoom to next turn" feature. Theoretically, this feature allows for a nice overview of long stretches of your trip while zooming into the details as you approach a turn. While the next turn remains far away, the 2D view is north up but switches to "direction up" as you get within a dozen or so miles of a turn. I find that the 2D view provides a great overview of your overall route and gives you an at-a-glance sense of your trip's progress. Here is an example of the 2D view with a next turn far in the distance.
"Splits Off" Annoyance
I used the word "theoretically" in the paragraph above because in practice, this 2D view is interrupted by a flaw in CoPilot RV. I refer to the problem as the "splits off fixation." CoPilot constantly provides a meaningless instruction to "Stay on Road1 while Road2 splits off." And every time it provides this meaningless instruction, it defines a point on the map that CoPilot considers a "next turn." As a result, CoPilot RV's 2D display is always zooming closer and closer to these meaningless "splits off" points. I'd estimate that over the course of this 3200 mile trip that CoPilot provided a "splits off" instruction at least 100 times that I'd categorize as completely unnecessary.
Even worse, I have CoPilot set to provide three audible upcoming turn prompts as the next turn is approached. CoPilot uses these three prompt distances to announce these "splits off" warnings too. So 100 unnecessary uses of the "splits off" alert turns into 300 audible prompts.
The "splits off" alert has good intentions. It is a nice feature in the specific circumstance where a road legitimately "forks" and the driver could go multiple ways. However, CoPilot RV provides this "splits off" instruction on things like standard freeway exit ramps even when the ramp isn't one of the freeway drive lanes. It also repeatedly does it when two highways intersect, even when that intersection would require a right or left turn using a dedicated lane. Here is an example. Notice the intersecting Highway 1695. It has absolutely nothing to do with my route. At Highway 1695, I-70 is elevated and Highway 1695 passes below. Highway 1695 is accessible via standard freeway entrance and exit ramps. Despite this, CoPilot RV insists on warning me "Stay on Interstate 70 as Highway 1695 splits off." It's a ridiculous instruction and it occurs over and over again in the app.
Here's another example. It's the same scenario, this time with Highway 40. I could have screen captured dozens and dozens of these situations.
So, we have this annoying "splits off" situation but yet there are situations where CoPilot is silent when there should be instructions provided. As I approached this small Kansas town on Highway 56, notice where the yellow arrow is. This arrow represents the "next turn" as far as CoPilot is concerned. It is 1.6 miles away from my current location. The problem here is obvious. There should be a left turn instruction where Highway 56 meets "Old 56" on the map. This is a stop sign, not a curve in the street. CoPilot is silent in this important scenario yet chirps unnecessary "splits off" warnings where it isn't needed.
Here is another example of CoPilot not providing instructions when instructions are warrantied. This is another example where the trip required a stop and a right turn in order to stay on the highway but CoPilot provided no instructions at all.
Search Along Route is Broken
A key feature in any RV navigation app is a "search along route function" for finding the next truck stop, dump station or campground. CoPilot RV has a "search along route" feature but, at least in my usage, it's completely broken. It simple does not return any content, despite there unquestionably being content that should be returned. Here is the result of "search along route" for gas stations. The search was started on I-70 east of Topeka headed towards Kansas City (not yet to Lawrence). Gas stations are plentiful along this route. The round icon to the left of the "Map" button spins continuously. This screenshot was taken after letting the screen sit for at least a mile.
POI Inadequacy
CoPilot RV allows you to input your own custom points-of-interest databases from sites like POI Factory. It's a good thing this feature exists because I found the built in POI database to be outdated and paltry. We overnighted in the small town of Dodge City, KS. It also served as a RV gas stop. CoPilot RV says there are three gas stations in Dodge City. Nope.

In reality, there are over three times that many including a Love's and a Flying J truck stop. Google Maps (correctly in my opinion) includes truck stops when searching for gas stations (but not vice versa obviously). CoPilot however, does not. The Love's and Flying J are not found in the gas station POI search in CoPilot but are found when searching the truck stop category. In my opinion, the truck stop category should be a subset of the gas station category. They should not be mutually exclusive.
Signpost Imagery - CoPilot Creative Marketing
ALK advertises signpost imagery as a feature of CoPilot RV. Signpost imagery is a great feature because it helps drivers associate the maneuvers shown on the screen with what they are seeing in real life. Combined with lane guidance, these are meaningful features for RV drivers since quick, last minute lane changes are hard to make in a RV. These features make big city driving easier.
So as not to be accused of making an incorrect interpretation of ALK's marketing, I will post exactly what their website says about this feature. Notice the phrase "Real Signposts." When I read that advertisement I have an expectation, like in Google Maps and solutions built from HERE maps, that I will be shown real signpost content. In over 7200 miles of driving with CoPilot (2010 trip and this trip), CoPilot seldom showed real signpost content.
In my experience, CoPilot's database does not have knowledge of what the real signpost physically has written on it. Instead, I believe that ALK is simply using knowledge of the crossing or connecting street to generate what it thinks the signpost might say. In some cases that really is what the signpost says on it. In those cases, CoPilot happens to get it right, by chance. In many other cases, the signpost does not contain the crossing or connecting street. Instead, it contains city names, attractions, local road names (instead of highway numbers) and other subtleties. In 7200 miles, I've observed no case where CoPilot accurately shows the real signpost content when the real signpost contains something other than the crossing or connecting street.
Here is just one example of a real signpost image from CoPilot in Kansas City. This sign in real life says "Des Moines." On a long trip like this, literally dozens of examples could be provided like this.
I'll end this particular issue by simply calling it creative marketing though my personal feelings about ALK's advertising of this particular feature are stronger than that.
Speed Limits - Why Bother?
CoPilot RV displays speed limits and also has a nice feature that provides speeding warnings at a user-defined threshold above the speed limit. Great feature. However, that assumes that the speed limits are actually accurate. In my experience, that isn't the case.
The speed limits errors are symptomatic of a larger problem which plagued my experience with CoPilot in 2010 and remains an issue on this trip - map quality.
I found speed limit mistakes on large sections of freeways in almost every state that we traveled on this trip. I'm not talking about missing the change in a speed limit by a mile or so. I'm talking about entire freeways having the wrong speed limit when that speed limit has been set for years. I'm not talking about wrong speed limits in towns on highways (this could be hard to track because individual towns change them) because I've not found CoPilot to even include speed limits on anything other than freeways.
Illinois: I-74 has the wrong speed limit. It changed in January 2014.
Kansas: I-70 has the wrong speed limit. It changed in the summer of 2011.
In addition, I found incorrect freeway speed limits in Missouri, Oklahoma and Texas.
Maps
In my 2010 blog post, map quality was my biggest disappointment and complaint with CoPilot. Sadly, while the route/ETA calculation has been fixed with the ActiveRoutes functionality, I find no material change that improves the map situation in CoPilot.
CoPilot does update their maps. A completely new freeway interchange was recently added in my home town. I submitted it through CoPilot's MapSure program and it was added in the next quarterly map update. That being said, the problem appears to be what is not reported through MapSure. So, while CoPilot's maps contain this new interchange that I reported, they still have an old freeway configuration in another location in my town (I did not report it) that has been complete for 2.5 years. This is a major US freeway. If major US freeways are outdated by 2 or 3 years, what is the condition of CoPilot's map data on city streets and residential subdivisions?
I have no idea what ALK's internal map update process is. What I do know from experience with the app, is that it isn't good enough. I have raised the map quality issue with ALK in a few ways including their support forum and social media. In all cases, their only response has been to point me to the instructions for submitting map updates to them. On their support forum, they pointed out the link to MapSure then took the unusual step of locking the forum from further comment.
There is much enthusiasm in the GIS industry about user-contributions to maps and crowdsourcing. However, two important distinctions must be made here. First, when it comes to Google MapMaker, Waze and OpenStreetMap, user contributions are used to make really good maps even better. In the case of ALK's maps it is my opinion that they are not starting with "really good maps." Second, customers are paying for this product. Sure, other paid map providers have similar programs. HERE has Map Creator and TomTom has Map Share. However, it is my experience with HERE and TomTom that even without user submission, within a few quarterly updates the internal processes at HERE and TomTom discover and implement many map changes. I readily admit that even with 7200 miles of travel with CoPilot, I have personally experienced a small amount of the ALK map database. However, even with that limited experience, there are enough map errors involving roads that have not changed or have been complete for 2, 3 or more years to question ALK's map update process, especially when directly compared to competitor's maps.
Some examples....On this trip I experienced incorrect freeway exit numbers on I-44 in the middle of St Louis. These were changed in the spring of 2014 and have yet to be updated by ALK. You'll notice in my 2010 blog post that I experienced incorrect freeway exit numbers on that trip as well, on the Florida turnpike.
I encountered problems with the app suggesting maneuvers that are impossible to make in a RV and should not be suggested by any RV navigation app.
Here is an example of CoPilot routing me to a gas station that is located on a major divided highway by routing me instead, in a RV, while using the app's RV mode, onto small residential streets and suggesting that I access the gas station by using a dirt cow path.
I'm not sure if a U-turn was legal at this major intersection in Albuquerque, NM but a RV navigation app, set in RV mode, should never, in any circumstance, suggest this maneuver. Ever.
I also encountered several instances of routing busts. This included:
There were two instances of this inexplicable maneuver that should be a simple right turn:

Conclusion
CoPilot RV is a feature-rich app that easily replaces a dedicated navigation device and matches it feature-for-feature. It's advanced route planning features and ability to build, save and recall multiple routes, each containing multiple stops, is unequaled in the smartphone navigation space and extremely attractive to RV drivers.
The app's route selection is very good, picking routes that I subjectively, would pick myself. The resulting ETA is very good assuming ActiveRoutes is purchased and activated.
The knowledge (and visual confirmation within the app) of RV road restrictions, low clearances and other RV-specific attributes provides peace of mind to the RV driver.
All of those positive qualities are undermined by the user experiencing outdated maps, incorrect speed limits and inexplicable routing anomalies presumably caused by old map data. I remain wholly unconvinced that map updates via CoPilot user submissions is a viable model for maintaining a quality product going forward. As more and more users see the experience of having Google Map Maker edits pushed to Maps within hours, it is my opinion that users will not tolerate road changes not being dealt with by ALK for years. It remains unclear if ALK will get the message and change. A quick read of CoPilot reviews in the iOS and Google app stores will show that map quality is a common CoPilot complaint and has been for a long time. There is no outward evidence based on this user's experience, that ALK has acted on that customer criticism.
An app with CoPilot's feature set, CoPilot's reliability, OpenStreetMaps' timeliness, ActiveTraffic's coverage and ActiveRoutes ETA impact is a winner. Fix your maps ALK. Stop undermining an otherwise great app.
Six years ago this week, we were on a nearly 4100 mile trip to the east and southeast US. On that trip, in 2010, I road tested ALK's CoPilot app for the first time. A thorough look at my experience with that app became one of my first substantial blog posts. As my now 6 year old blog post outlined, there was good, bad and ugly in my experience with CoPilot. For me, the bad and the ugly outweighed the good and I stopped using the app for many years.
Completely dissatisfied with the current choices available for RV navigation, I immediately spent $50 to purchase CoPilot RV the first day it was released this spring. I was willing to give the app another chance 6 years after my last CoPilot experience. On this trip, for all 3200 miles, I ran CoPilot RV on a Samsung Tab S2 8.0 tablet as well as Google Maps on a Samsung Galaxy Note 5 smartphone. CoPilot was rock solid from a performance and stability perspective. In 3200 miles (48 hours of driving), the app never locked up, froze or crashed once.
Disclosure and About Me: I'm a bit of technology evangelist, both personally and professionally. I have a strong interest in navigation but have not worked professionally in the field. I am a volunteer beta tester for 3 navigation companies and am also a volunteer Google MapMaker Regional Lead. Over the last decade I have owned and used the following solutions: Garmin SP III, Garmin SP 2710, Garmin 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, TomTom for Android, Rand McNally 7725, Rand McNally 7735, Garmin viago, Rand McNally RVND, CoPilot RV for Android.
CoPilot navigation apps have a long history across many different mobile platforms. ALK should be commended for believing in the smartphone navigation space and sticking with it through many years. In general, CoPilot apps are extremely feature-rich, accomplishing nearly every feature you'd find on a traditional dedicated navigation unit. The abundant features make CoPilot RV an attractive alternative for RV navigation. Notable features include:
- Ability to pre-plan, save and recall routes. Multiple routes can be saved.
- Routes can contain many stops and stops can be manually managed or automatically optimized.
- User-installed points-of-interest (POI) databases are supported so content from sites like POI Factory can be installed.
- User-entered RV dimensions and weight are used in route calculations.
I'll cut to the chase first and then provide more detail for those interested. The title of this blog post is "It's the best of bad choices for RV navigation." That summarizes my feelings about CoPilot RV. CoPilot has drastically improved in the key feature of route/ETA calculation since my experience in 2010. However, like was the case in 2010, CoPilot RV's map quality remains a significant downfall. Unlike after my 2010 trip with CoPilot, I will continue to use CoPilot RV but will be watching and hoping for other solutions due to the map quality issue. A RV navigation app carries an additional burden of having RV-specific attributes such as weight, height, size and propane restrictions. I'm unclear how ALK suggests customers should have confidence in the accuracy of these very important RV-specific attributes given the persistence map quality issues over the years.
The Details
This blog will not be an exhaustive look at CoPilot's features. My 2010 blog post provides this and actually, the look and feel of the app has remained similar to the 2010 app. Normally that would be a red flag but, despite CoPilot not abiding by any Google material design guidelines in any way, I find it visually pleasing and relatively easy to use. CoPilot does register as an intent handler within Android so clicking addresses within Contacts, Calendar, etc., can be handled by CoPilot automatically.
CoPilot's route/ETA calculation has been fixed from my 2010 experience and is now very good. However, users MUST buy the optional $9.95 annual traffic package in order to experience the improvement. On this trip we traveled 6 - 11 hours per day on our drive days. I found the ETA that CoPilot calculated to be realistic for the total trip time (i.e., inclusive of gas stops). Comparatively, Google Maps' ETA calculation seemed to be more accurate for actual drive time, but would then add time for each gas stop.
My recommendation is simple, do not use CoPilot RV without buying the optional traffic subscription. I'll explain.
Without the optional traffic package, CoPilot has poor "knowledge" of road speeds. CoPilot appears to classify roads in groups of similar road types and then assigns a generic speed to each road type. The user, in a setting that has not changed since 2010, can input custom road speeds for each of the generic road categories, and also select the user's preference for driving on each road type. As you can read in my 2010 blog post, the result, even when using default settings, is disastrous route calculations and ETA times.
Here is an example of a route/ETA calculation in the current CoPilot RV app using the default app settings and not using the optional traffic package. From personal experience, a time of 8:43 is absurd for this route, as CoPilot itself will confirm once you actually activate the traffic package.
CoPilot Support will say "well, just change the default speed to something more realistic." Nope. The problem with that is CoPilot road categories don't distinguish between rural and urban roads when setting custom user speeds. So, if the user sets a divided highway custom speed to 50 mph for example, CoPilot applies that speed to a divided highway whether it runs through rural farm land or is an urban divided highway in the middle of a dense urban area. If the user corrects the ETA in this rural route example by raising the custom speed, it may bring down the 8:43 ETA to something more realistic but the result will also drastically underestimate the ETA in an urban environment where the custom speed cannot be maintained on urban streets badged as a highway. Luckily, CoPilot has "fixed" this problem if you purchase the optional traffic package.
Here is the exact same route with the optional traffic package activated. An ETA of 6:42 is a very realistic calculation for this route. This optional feature saves CoPilot RV from being removed from my Android tablet, never to be used again, like occurred in 2010.
So what is going on here? The optional CoPilot traffic package actually includes two features. The first feature is branded ActiveTraffic, which is real-time traffic content. The second feature is ActiveRoutes, which is essentially historical traffic content. ALK describes it as follows: "ActiveRoutes calculates your route using actual road speeds at the specific time of day and day of week you're traveling."
This means that the generic road category and road category speeds are not used when ActiveRoutes is active. Instead, the route and route ETA is calculated using a massive (3rd party) database of knowledge about actual road speeds and how those speeds vary by time of day. This is how other modern smartphone navigation apps like Google Maps calculate routes and the ETA. This feature is vital to making CoPilot RV usable.
2D View
I believe that most people prefer to use navigation apps in 3D mode (the default view in Google Maps). However, I really enjoy CoPilot RV's 2D view using the "zoom to next turn" feature. Theoretically, this feature allows for a nice overview of long stretches of your trip while zooming into the details as you approach a turn. While the next turn remains far away, the 2D view is north up but switches to "direction up" as you get within a dozen or so miles of a turn. I find that the 2D view provides a great overview of your overall route and gives you an at-a-glance sense of your trip's progress. Here is an example of the 2D view with a next turn far in the distance.
"Splits Off" Annoyance
I used the word "theoretically" in the paragraph above because in practice, this 2D view is interrupted by a flaw in CoPilot RV. I refer to the problem as the "splits off fixation." CoPilot constantly provides a meaningless instruction to "Stay on Road1 while Road2 splits off." And every time it provides this meaningless instruction, it defines a point on the map that CoPilot considers a "next turn." As a result, CoPilot RV's 2D display is always zooming closer and closer to these meaningless "splits off" points. I'd estimate that over the course of this 3200 mile trip that CoPilot provided a "splits off" instruction at least 100 times that I'd categorize as completely unnecessary.
Even worse, I have CoPilot set to provide three audible upcoming turn prompts as the next turn is approached. CoPilot uses these three prompt distances to announce these "splits off" warnings too. So 100 unnecessary uses of the "splits off" alert turns into 300 audible prompts.
The "splits off" alert has good intentions. It is a nice feature in the specific circumstance where a road legitimately "forks" and the driver could go multiple ways. However, CoPilot RV provides this "splits off" instruction on things like standard freeway exit ramps even when the ramp isn't one of the freeway drive lanes. It also repeatedly does it when two highways intersect, even when that intersection would require a right or left turn using a dedicated lane. Here is an example. Notice the intersecting Highway 1695. It has absolutely nothing to do with my route. At Highway 1695, I-70 is elevated and Highway 1695 passes below. Highway 1695 is accessible via standard freeway entrance and exit ramps. Despite this, CoPilot RV insists on warning me "Stay on Interstate 70 as Highway 1695 splits off." It's a ridiculous instruction and it occurs over and over again in the app.
Here's another example. It's the same scenario, this time with Highway 40. I could have screen captured dozens and dozens of these situations.
So, we have this annoying "splits off" situation but yet there are situations where CoPilot is silent when there should be instructions provided. As I approached this small Kansas town on Highway 56, notice where the yellow arrow is. This arrow represents the "next turn" as far as CoPilot is concerned. It is 1.6 miles away from my current location. The problem here is obvious. There should be a left turn instruction where Highway 56 meets "Old 56" on the map. This is a stop sign, not a curve in the street. CoPilot is silent in this important scenario yet chirps unnecessary "splits off" warnings where it isn't needed.
Here is another example of CoPilot not providing instructions when instructions are warrantied. This is another example where the trip required a stop and a right turn in order to stay on the highway but CoPilot provided no instructions at all.
Search Along Route is Broken
A key feature in any RV navigation app is a "search along route function" for finding the next truck stop, dump station or campground. CoPilot RV has a "search along route" feature but, at least in my usage, it's completely broken. It simple does not return any content, despite there unquestionably being content that should be returned. Here is the result of "search along route" for gas stations. The search was started on I-70 east of Topeka headed towards Kansas City (not yet to Lawrence). Gas stations are plentiful along this route. The round icon to the left of the "Map" button spins continuously. This screenshot was taken after letting the screen sit for at least a mile.
POI Inadequacy
CoPilot RV allows you to input your own custom points-of-interest databases from sites like POI Factory. It's a good thing this feature exists because I found the built in POI database to be outdated and paltry. We overnighted in the small town of Dodge City, KS. It also served as a RV gas stop. CoPilot RV says there are three gas stations in Dodge City. Nope.

In reality, there are over three times that many including a Love's and a Flying J truck stop. Google Maps (correctly in my opinion) includes truck stops when searching for gas stations (but not vice versa obviously). CoPilot however, does not. The Love's and Flying J are not found in the gas station POI search in CoPilot but are found when searching the truck stop category. In my opinion, the truck stop category should be a subset of the gas station category. They should not be mutually exclusive.
Signpost Imagery - CoPilot Creative Marketing
ALK advertises signpost imagery as a feature of CoPilot RV. Signpost imagery is a great feature because it helps drivers associate the maneuvers shown on the screen with what they are seeing in real life. Combined with lane guidance, these are meaningful features for RV drivers since quick, last minute lane changes are hard to make in a RV. These features make big city driving easier.
So as not to be accused of making an incorrect interpretation of ALK's marketing, I will post exactly what their website says about this feature. Notice the phrase "Real Signposts." When I read that advertisement I have an expectation, like in Google Maps and solutions built from HERE maps, that I will be shown real signpost content. In over 7200 miles of driving with CoPilot (2010 trip and this trip), CoPilot seldom showed real signpost content.
In my experience, CoPilot's database does not have knowledge of what the real signpost physically has written on it. Instead, I believe that ALK is simply using knowledge of the crossing or connecting street to generate what it thinks the signpost might say. In some cases that really is what the signpost says on it. In those cases, CoPilot happens to get it right, by chance. In many other cases, the signpost does not contain the crossing or connecting street. Instead, it contains city names, attractions, local road names (instead of highway numbers) and other subtleties. In 7200 miles, I've observed no case where CoPilot accurately shows the real signpost content when the real signpost contains something other than the crossing or connecting street.
Here is just one example of a real signpost image from CoPilot in Kansas City. This sign in real life says "Des Moines." On a long trip like this, literally dozens of examples could be provided like this.
I'll end this particular issue by simply calling it creative marketing though my personal feelings about ALK's advertising of this particular feature are stronger than that.
Speed Limits - Why Bother?
CoPilot RV displays speed limits and also has a nice feature that provides speeding warnings at a user-defined threshold above the speed limit. Great feature. However, that assumes that the speed limits are actually accurate. In my experience, that isn't the case.
The speed limits errors are symptomatic of a larger problem which plagued my experience with CoPilot in 2010 and remains an issue on this trip - map quality.
I found speed limit mistakes on large sections of freeways in almost every state that we traveled on this trip. I'm not talking about missing the change in a speed limit by a mile or so. I'm talking about entire freeways having the wrong speed limit when that speed limit has been set for years. I'm not talking about wrong speed limits in towns on highways (this could be hard to track because individual towns change them) because I've not found CoPilot to even include speed limits on anything other than freeways.
Illinois: I-74 has the wrong speed limit. It changed in January 2014.
Kansas: I-70 has the wrong speed limit. It changed in the summer of 2011.
In addition, I found incorrect freeway speed limits in Missouri, Oklahoma and Texas.
Maps
In my 2010 blog post, map quality was my biggest disappointment and complaint with CoPilot. Sadly, while the route/ETA calculation has been fixed with the ActiveRoutes functionality, I find no material change that improves the map situation in CoPilot.
CoPilot does update their maps. A completely new freeway interchange was recently added in my home town. I submitted it through CoPilot's MapSure program and it was added in the next quarterly map update. That being said, the problem appears to be what is not reported through MapSure. So, while CoPilot's maps contain this new interchange that I reported, they still have an old freeway configuration in another location in my town (I did not report it) that has been complete for 2.5 years. This is a major US freeway. If major US freeways are outdated by 2 or 3 years, what is the condition of CoPilot's map data on city streets and residential subdivisions?
I have no idea what ALK's internal map update process is. What I do know from experience with the app, is that it isn't good enough. I have raised the map quality issue with ALK in a few ways including their support forum and social media. In all cases, their only response has been to point me to the instructions for submitting map updates to them. On their support forum, they pointed out the link to MapSure then took the unusual step of locking the forum from further comment.
There is much enthusiasm in the GIS industry about user-contributions to maps and crowdsourcing. However, two important distinctions must be made here. First, when it comes to Google MapMaker, Waze and OpenStreetMap, user contributions are used to make really good maps even better. In the case of ALK's maps it is my opinion that they are not starting with "really good maps." Second, customers are paying for this product. Sure, other paid map providers have similar programs. HERE has Map Creator and TomTom has Map Share. However, it is my experience with HERE and TomTom that even without user submission, within a few quarterly updates the internal processes at HERE and TomTom discover and implement many map changes. I readily admit that even with 7200 miles of travel with CoPilot, I have personally experienced a small amount of the ALK map database. However, even with that limited experience, there are enough map errors involving roads that have not changed or have been complete for 2, 3 or more years to question ALK's map update process, especially when directly compared to competitor's maps.
Some examples....On this trip I experienced incorrect freeway exit numbers on I-44 in the middle of St Louis. These were changed in the spring of 2014 and have yet to be updated by ALK. You'll notice in my 2010 blog post that I experienced incorrect freeway exit numbers on that trip as well, on the Florida turnpike.
I encountered problems with the app suggesting maneuvers that are impossible to make in a RV and should not be suggested by any RV navigation app.
Here is an example of CoPilot routing me to a gas station that is located on a major divided highway by routing me instead, in a RV, while using the app's RV mode, onto small residential streets and suggesting that I access the gas station by using a dirt cow path.
I'm not sure if a U-turn was legal at this major intersection in Albuquerque, NM but a RV navigation app, set in RV mode, should never, in any circumstance, suggest this maneuver. Ever.
I also encountered several instances of routing busts. This included:
- Two instances of the routing not using the separate right hand turn lanes (they were correctly shown in the app) and instead showing a 90-degree right hand turn from the go-forward lanes of the + intersection.
- One instance of the app suggesting that I travel the wrong way into oncoming traffic of a divided highway, then turn right across my current lane in order to make a right turn.
There were two instances of this inexplicable maneuver that should be a simple right turn:

Conclusion
CoPilot RV is a feature-rich app that easily replaces a dedicated navigation device and matches it feature-for-feature. It's advanced route planning features and ability to build, save and recall multiple routes, each containing multiple stops, is unequaled in the smartphone navigation space and extremely attractive to RV drivers.
The app's route selection is very good, picking routes that I subjectively, would pick myself. The resulting ETA is very good assuming ActiveRoutes is purchased and activated.
The knowledge (and visual confirmation within the app) of RV road restrictions, low clearances and other RV-specific attributes provides peace of mind to the RV driver.
All of those positive qualities are undermined by the user experiencing outdated maps, incorrect speed limits and inexplicable routing anomalies presumably caused by old map data. I remain wholly unconvinced that map updates via CoPilot user submissions is a viable model for maintaining a quality product going forward. As more and more users see the experience of having Google Map Maker edits pushed to Maps within hours, it is my opinion that users will not tolerate road changes not being dealt with by ALK for years. It remains unclear if ALK will get the message and change. A quick read of CoPilot reviews in the iOS and Google app stores will show that map quality is a common CoPilot complaint and has been for a long time. There is no outward evidence based on this user's experience, that ALK has acted on that customer criticism.
An app with CoPilot's feature set, CoPilot's reliability, OpenStreetMaps' timeliness, ActiveTraffic's coverage and ActiveRoutes ETA impact is a winner. Fix your maps ALK. Stop undermining an otherwise great app.
Friday, August 28, 2015
Connecting Android Auto in a 2015 Hyundai Sonata
One thing is for certain. Android Auto should work reliably by plugging in your phone to your car's USB port. It doesn't and that is a problem for mainstream adoption. However, there are some things you can do as a consumer rather than simply waiting for Google to fix the problem.
I'll say one thing right off the bat. Don't get mad at Hyundai for this. Hyundai stepped up and was the first US car company to provide Android Auto to us. The problems with Android Auto are certainly not Hyundai's fault and we shouldn't discourage them from being progressive in the future by blaming them for Google's issues.
Here is how I've been able to get a fairly reliable connection of Android Auto in my 2015 Hyundai Sonata. These steps assume that you've already made the initial Android Auto connection to your car and your car and phone have Bluetooth setup as well.
Android Auto / 2015 Hyundai Sonata Connection Steps
I'll say one thing right off the bat. Don't get mad at Hyundai for this. Hyundai stepped up and was the first US car company to provide Android Auto to us. The problems with Android Auto are certainly not Hyundai's fault and we shouldn't discourage them from being progressive in the future by blaming them for Google's issues.
Here is how I've been able to get a fairly reliable connection of Android Auto in my 2015 Hyundai Sonata. These steps assume that you've already made the initial Android Auto connection to your car and your car and phone have Bluetooth setup as well.
Android Auto / 2015 Hyundai Sonata Connection Steps
- Enable Developer Mode on your phone. This is a ridiculous step to have to take, but nonetheless it is where we find ourselves. To do that:
- Open your phone's settings. You are looking for a piece of information called the Build Number. Depending on the brand of your phone, it could be found in a couple of different places. Try:
- Settings then About Phone
- Settings then About Device
- Settings then About Phone then Software Information
- Settings then About then Software Information (and then More possibly)
- Click on the Build Number at least 7 times in rapid succession. You're looking for a message that says "You are now a developer."
- Upon completion of this step you will now find a Developer Mode menu in your phone's Settings.
- In Developer Mode settings click USB Debugging.
- DO NOT CONNECT YOUR PHONE TO YOUR CAR.
- Start your car.
- The Android Auto connection is extremely unreliable if you connect it to your car before the car and your phone have completed their communications over Bluetooth. This includes the initial Bluetooth handshake, the exchange of data between the car and phone and can also include an updated download of the phone's contacts. Unfortunately, this exchange of information occurs every time you start the car and it take a couple of minutes. You can tell when this exchange of information is occurring by watching your car's screen. The phone symbol with the arrow on it shows that your car and phone are actively exchanging information. Don't connect your phone to the USB cable as long as this symbol or similar is on the screen.
- A blue colored Bluetooth symbol wrapped in a headset icon with a musical note icon next to it is the symbol that you want to wait for! Once you see that, only then do you stand a chance of starting a reliable Android Auto connection.
- At that point, plug your phone in and hope that you have an Android Auto connection. Even after waiting for this symbol there are times where I have to unplug and plug the USB cable back in 3 or 4 times (yes I've tried multiple cables) before I will get an Android Auto connection. However, if I don't wait for this symbol then there has been no instance of getting an Android Auto connection ever. This is your best shot.
The downside of this process is that you have to wait, often for several minutes before you can connect your phone and begin navigation with Google Maps. It doesn't take very many days before waiting 2 or 3 minutes every time you want to drive somewhere get really old. Read on:
How to being Google Maps Navigation before you have an Android Auto connection
- Connect the USB cable to your phone but connect the other end to a USB charger plugged into the DC power port in your dash. Do not plug that end into the car's USB port!
- Enable "OK Google" functionality on any screen of your phone.
- Open the Google app from your app drawer.
- Go to Settings, then Voice, then OK Google Detection and turn on the "From any screen" functionality.
- Start your car and begin your drive at your leisure.
- Activate your Google Maps navigation session by saying "OK Google, Navigate to ______."
- Google Maps will open on your phone and your navigation session will begin.
- As driving conditions allow, keep an eye out for the icon discussed above. Upon seeing the icon, unplug the car's end of the USB cable from the DC power adapter and plug it into the USB port in your car.
- With some luck you will have a reliable Android Auto connection and can activate Android Auto from your car's touchscreen.
- The Google Maps navigation session that you started on your phone will remain active when you switch to Android Auto! Your phone's screen will go blank and your navigation instructions will resume on your car's screen.
Two Weeks With Android Auto - The Good & The Ugly
I've only been an Android Auto user for a few weeks but in that short time a few things have become clear.
My setup is a 2015 Hyundai Sonata with the LG G4 on the Sprint network. It is hard to express how much better the Hyundai infotainment system is (even without the Android Auto functionality) in comparison to my 2012 Toyota with Entune. I couldn't wait to get rid of Entune and I thought that Android Auto was the answer. What I've learned in a short time is that Android Auto is great, but I'm using the very-well-thought-out Hyundai system more than I ever thought I would. The Hyundai navigation system is very feature rich. I love the Bluelink cellular-powered, voice-activated Google Search feature. However, the Hyundai navigation solution uses the yawn-inducing SiriusXM traffic service which leaves a lot to be desired. In hindsight, my urge to switch cars was more rooted in how bad Entune was and not in how good Android Auto is.
Google Maps
Having Google Maps in-dash is fantastic and by itself a reason to get Android Auto. When I expect traffic on my route I turn to Google Maps. I find it to have very accurate ETAs. The micro-rerouting that results from the traffic content is unparalleled and the machine learning predictions related to navigation that appear through Google Now are great.
The biggest issue with Google Maps through Android Auto is the inability to control the volume of the navigation instructions independently of the media audio. When you have to turn up the volume of a news podcast in BeyondPod, prepare to be blasted deaf by the navigation instruction from Google Maps. That has to change.
Google Play Music
Google Play Music. Wow. What a mess. My Library in Google Play Music (all of which are cached offline) consists of:
Stations that originate from the Songza functionality portion of Google Play Music are completely non-functional through Android Auto. One of my stations is called Today's Biggest Hits Radio. However, in the Stations section of Android Auto there is nothing called "Today's Biggest Hits Radio." Instead, the station is listed by whatever the first song happens to be in that station. Try distinguishing one station from another when it displays stations like that!
Clicking on the first song in that station results in a long pause followed by the error message "Google Play Music doesn't appear to be working." There is also a crash of the Google Play Music app on the phone though it is concealed behind the Android Auto screen saver. I've submitted this error report about a half dozen times so far, so lets hope Google gets this mess cleaned up.
Every station originating from the Songza functionality of Google Play Music has the same problem and that problem persists after uninstalling, reinstalling and clearing the cache of the Google Play Music app. It's a big no-go for that functionality.
Subscribed playlists built from others also have difficulty through Android Auto. They at least appear correctly in the station list, however starting a song in that playlist causes Google Play Music on the phone to crash and the phone's app to restart.
Google Play Music is by far the weakest link for Android Auto in my limited experience and needs lots of attention.
Podcasts
There is a very limited selection of Android Auto apps at this point but I am enjoying podcast apps immensely. Trying to use a podcast app over a Bluetooth connection while operating a vehicle was a losing proposition but Android Auto makes listening to Podcasts extremely easy.
USB Connection
This is a big area of concern. It's pretty simple: the reliable use of Android Auto should not require activating developer mode on your phone and turning on USB debugging. No mainstream Joe is going to use Android Auto unless they can plug their phone in and it works. Right now, it doesn't. There is a way to connect the phone in the 2015 Hyundai Sonata so that Android Auto usually connects reliability. Read about it in this blog post.
Conclusion
Android Auto has tremendous potential. Having voice-activated phone calls and text messaging capability is wonderful. Having Google Maps in-dash is the ultimate for me. However, the USB connection reliability is ridiculous and Google Play Music is a mess. We all know as early adopters that this will evolve over time. However, the known issues list on the Android Auto website doesn't give you a lot of comfort that Google is aware of, acknowledging and fixing these issues.
- Having Google Maps in-dash is fantastic.
- Google Maps volume control isn't fantastic.
- Google Music through Android Auto is a mess.
- Podcast apps are a great example of what's been missing in-dash.
- The initial USB connection is finicky.
My setup is a 2015 Hyundai Sonata with the LG G4 on the Sprint network. It is hard to express how much better the Hyundai infotainment system is (even without the Android Auto functionality) in comparison to my 2012 Toyota with Entune. I couldn't wait to get rid of Entune and I thought that Android Auto was the answer. What I've learned in a short time is that Android Auto is great, but I'm using the very-well-thought-out Hyundai system more than I ever thought I would. The Hyundai navigation system is very feature rich. I love the Bluelink cellular-powered, voice-activated Google Search feature. However, the Hyundai navigation solution uses the yawn-inducing SiriusXM traffic service which leaves a lot to be desired. In hindsight, my urge to switch cars was more rooted in how bad Entune was and not in how good Android Auto is.
Google Maps
Having Google Maps in-dash is fantastic and by itself a reason to get Android Auto. When I expect traffic on my route I turn to Google Maps. I find it to have very accurate ETAs. The micro-rerouting that results from the traffic content is unparalleled and the machine learning predictions related to navigation that appear through Google Now are great.
The biggest issue with Google Maps through Android Auto is the inability to control the volume of the navigation instructions independently of the media audio. When you have to turn up the volume of a news podcast in BeyondPod, prepare to be blasted deaf by the navigation instruction from Google Maps. That has to change.
Google Play Music
Google Play Music. Wow. What a mess. My Library in Google Play Music (all of which are cached offline) consists of:
- Personally built playlists
- Subscribed playlists created by others
- Stations built myself seeded from artists or songs
- Stations that originate from the "Play music for..." section (the Songza functionality)
Stations that originate from the Songza functionality portion of Google Play Music are completely non-functional through Android Auto. One of my stations is called Today's Biggest Hits Radio. However, in the Stations section of Android Auto there is nothing called "Today's Biggest Hits Radio." Instead, the station is listed by whatever the first song happens to be in that station. Try distinguishing one station from another when it displays stations like that!
Clicking on the first song in that station results in a long pause followed by the error message "Google Play Music doesn't appear to be working." There is also a crash of the Google Play Music app on the phone though it is concealed behind the Android Auto screen saver. I've submitted this error report about a half dozen times so far, so lets hope Google gets this mess cleaned up.
Every station originating from the Songza functionality of Google Play Music has the same problem and that problem persists after uninstalling, reinstalling and clearing the cache of the Google Play Music app. It's a big no-go for that functionality.
Subscribed playlists built from others also have difficulty through Android Auto. They at least appear correctly in the station list, however starting a song in that playlist causes Google Play Music on the phone to crash and the phone's app to restart.
Google Play Music is by far the weakest link for Android Auto in my limited experience and needs lots of attention.
Podcasts
There is a very limited selection of Android Auto apps at this point but I am enjoying podcast apps immensely. Trying to use a podcast app over a Bluetooth connection while operating a vehicle was a losing proposition but Android Auto makes listening to Podcasts extremely easy.
USB Connection
This is a big area of concern. It's pretty simple: the reliable use of Android Auto should not require activating developer mode on your phone and turning on USB debugging. No mainstream Joe is going to use Android Auto unless they can plug their phone in and it works. Right now, it doesn't. There is a way to connect the phone in the 2015 Hyundai Sonata so that Android Auto usually connects reliability. Read about it in this blog post.
Conclusion
Android Auto has tremendous potential. Having voice-activated phone calls and text messaging capability is wonderful. Having Google Maps in-dash is the ultimate for me. However, the USB connection reliability is ridiculous and Google Play Music is a mess. We all know as early adopters that this will evolve over time. However, the known issues list on the Android Auto website doesn't give you a lot of comfort that Google is aware of, acknowledging and fixing these issues.
Friday, October 31, 2014
First look at the HERE beta navigation app for Android
If you've used a Garmin, Navigon or Magellan GPS then you are a HERE customer and likely didn't know it. HERE's maps power devices by those PND brands.
HERE seems to be making a push to establish themselves as a brand that consumers identify with. Having primarily been a B2B (business-to-business) brand, HERE finds themselves fighting for their survival against the powerful ecosystems that Google and Apple have created.
They share that fight with their historical business customers. Both in-dash and PND navigation face huge challenges from the smartphone that contains Google Maps, Apple Maps, Waze and other free alternatives. But the challenge for HERE is more than just a smartphone vs in-dash fight since soon Google and Apple will be making a play for the in-dash space as well through bluetooth-linked smartphone / in-dash hybrid telematics solutions known as Android Auto and Apple CarPlay. This is becoming a war of ecosystems and presents a monumental challenge for HERE. Establishing credible consumer brand recognition is a good first step.
HERE's challenge is enough on it's own but unfortunately for HERE they've also been part of changing corporate bureaucracies which is tough for any company trying to be laser-focused on their goals. Long in the hands of Phillips, HERE was known as Navteq in the hayday of PND's (and as NavTech before that). Around 2007, Navteq was purchased by Nokia and got caught up in Nokia's disintegration which took nearly 5 years to play out. Oh what might have been! In 2012 Navteq became HERE (the only thing left now of what was once Nokia) as the Nokia brand marched towards the storied end in 2014 after Microsoft's purchase of the remaining pieces. Got that?
The purpose of explaining that history is that in same ways, to the consumer, the emergence of the new HERE consumer brand really does represent something new. Perhaps, give their tumultuous history, that is exactly what HERE needs - a fresh start.
What does their first attempt at this fresh start look like?
HERE for Android is a navigation play that competes head-to-head for the same customer as Google Maps and Waze. HERE brings one significant advantage though, offline maps, providing users with the ability to use navigation without a data connection. Whether you are out of mobile phone range or out of mobile data allotment, offline maps can be an important option to have.
HERE is certainly not the first to offer offline maps for Android. Scout (Telenav) offers offline maps (now using OpenStreetMap) as does ALK Copilot, TomTom and Sygic (using TomTom maps). Interestingly, HERE was beat to Android in recent months by one of their own customers, Garmin with the viago app. It is a crowded market to enter in 2014 but there can be no argument that HERE enters it with one of the most well respected maps datasets available (albeit one that most consumers have never heard of). Check out my 8-device road test from back in 2012 where Navteq-powered Garmin killed the competition.
It is important to note that you don't have to download the HERE maps. HERE works just fine as an online solution as well, sending the maps to your smartphone over your data connection.
HERE does a nice job of allowing flexibility in which maps to download. The storage needed to store maps is tremendous so you are going to need a smartphone with lots of capacity (or an external SD card) to download a lot of maps offline. The entire US for example is nearly 5 GB but luckily HERE allows you to pick individual States for much more modest sized downloads. It is curious how much bigger the HERE maps are compared to the Garmin viago maps. It makes me wonder what else is in the HERE map dataset that we just aren't seeing yet with the immature feature set of the HERE beta app.
My experience with the HERE beta app so far has been that the app is very fluid, fast and stable. I've had no crashes, lock-ups or stuttering. The map is cleanly presented on the screen in a readable way. It does a nice job of showing road classes using distinct color. You can compare the HERE map with Google Maps:
![]() |
| HERE |
![]() |
| Google Maps |
![]() |
| HERE map view options |
![]() |
| HERE w/ traffic view on |
![]() |
| Google Maps w/ traffic view on. |
Notice the granularity difference in the traffic flow between Google and HERE. It is tough to make an accuracy argument between the two but there is no question that Google Maps is purporting to know more about the current traffic conditions over a wider range of roads than HERE is. Again - accuracy can be debated.
It the current beta version the HERE maps offers a pretty bare bones navigation experience. Here is a look at HERE's main app menu:
![]() |
| HERE menu in MAPS mode |
![]() |
| Setting in DRIVE mode. |
Here is what the MAPS mode settings menu looks like:
![]() |
| MAPS settings menu |
![]() |
| DRIVE mode settings |
In the MAPS menu it is called Voice Navigation but in the DRIVE menu it is called Voice Options. They control the same thing. In the MAPS menu Day/night view has it's own option but in the DRIVE menu it is buried within the Map options menu.
Worse, despite both menus having some of the same functionality the UI for that common setting is different depending upon which menu you started in.
This setting fiasco distracts from an otherwise pretty decent app and I simply don't understand it. I've used a ton of PND's and navigation apps over the years and I can't think of a single reason why there needs to be two different settings menus within the same app.
Hang with me because this is by far their worst of the app. It gets better from here (for HERE!).
There are the usual suspects present in the Route Options setting but strangely missing is commuter lanes. I am not sure why, but I hope that finds itself into the app quickly, as it is an irreplaceable feature found in both TomTom's and Garmin's Android apps.
![]() |
| No commuter lane route options |
Searching in the app
The main map screen has a search field. HERE did a great job with the search field, making it a universal search. You can type in an address, a POI name or a category and it will show you the results. This is well done. It is a giant leap forward from Garmin's archaic address entry system in their viago app that requires you to separately enter the house number, street name, city and state like you had to do 10 years ago in a Garmin PND. Bravo HERE, for implementing universal search.
In this version, universal search does not include your contacts sadly. I hope that we see this feature added in a future version. That does not mean that you can't easily use HERE to navigate to a contact though. Thankfully, even in this early beta, HERE has registered the app as an Android intent handler, which means it is one of the apps available to "handle your intent" when you click on an address in a 3rd party app. In this screen shot, I clicked on an address in my Nexus 5's People app (you could do the same in your calendar or Yelp or TripAdvisor, etc.) and HERE is one of the apps that can fulfill my request when clicking on the address:
![]() |
| HERE as an Android intent handler option |
Whether you have searched from within the HERE app, or passed HERE an address from a 3rd party app, this is screen that you are shown once you have found a single search result:
![]() |
| HERE search results |
![]() |
| Route options screen |
Also in the screen above you can see that there is an ability to change your "don't include" route restrictions as well as go to settings. (I wonder which settings menu THIS will take me to?)
Your path to navigation continues by clicking the route you desire from the screen above. Unfortunately, you are still not quite ready to navigate though. For some reason HERE has decided to visually show me the routes that were just shown to me in a list in the prior screen.
![]() |
| A second route selection screen |
Personally, I'd much prefer coming directly to this screen. I like pictures so I like to see the visual representation of the route options. Should I desire to change to transit or walking then I'd gladly hit a button here to take me to that selection, but I'd rather not waste a step being presented with that every single time I calculate a route.
Google Maps has figured out an elegant way to present the content of both of these redundant HERE screens on a single screen and quickly begin navigation. I hope that HERE spends some time optimizing this in the app.
I've noticed some very strange results when searching for places rather than addresses. For example, I often receive no results when searching for things that are plentiful in my area.
![]() |
| No Eat & Drink near me? |
![]() |
| No place to Go Out? |
![]() |
| Only found one place when searching "mall" |
However, when I searched specifically for "Merle Hay Mall" and "Valley West Mall" then they were located when they could not be found when searching only for the word "mall."
![]() |
| Not found when searching only for "mall" |
![]() |
| Also not found when searching only for "mall" |
Other searches worked as expected. Here is an example of the results of searching for "subway." It shows the closest one by default and you can swipe the banner at the bottom to the left to cycle through the search results.
The navigation map is well done. It is fluid and presents the information clearly.
![]() |
| Navigation screen |
![]() |
| Navigation mode options |
You can also activate a new "alternate route" calculation manually from this screen which is nice to see. I have not yet faced a routing situation where traffic has created a different, quicker route so I can't comment on how the app handles that situation.
Additional Features (or not)
The list of features not yet in this beta app is long. You won't find any PND features such as detours, route avoidance or via points. The app doesn't support multi-stop routes. I haven't seen any evidence of signpost imagery or lane guidance.
I have experienced the 3D buildings and found the app to be extremely quick and fluid in displaying the building models.
When browsing the map, the map is "live" in terms of being able to long-press anywhere on the map and receive the address of that location (ready to begin navigation) just like you had searched for that location.
Any location (place, address, etc.) can be saved to a "Collection" or "favorite" as I typically think of it. Collections can be categorized as desired.
You can also share any location that you have selected within the app. Sharing can be via the standard Android sharing options but the HERE app has a special bonus. You can also share through built-in Glympse functionality. While this is a nice feature, I hope that the integration between HERE and Glympse improves. As it exists today, you must select the amount of time to share through Glympse just like if you were using the standalone app. However, this is a navigation app. The app knows my ETA. The app should be able to share through Glympse until I've arrived at my destination without me having to manually adjust the time.
Lastly, there is no functionality in the current version of the app to display POI's outside of a search. I like to travel with gas station, food and rest stop POI's visible on the map. That option doesn't exist in the app yet.
There is no ability to download maps in the background while doing other things in the app. Leave the screen and you cancel your download. On initial map download be prepared to give up use of your device for awhile.
Incremental Map Updates!!!!!
HERE deserves a massive round of applause for introducing incremental map updates in the app. That means that users can download new map content to the app but only have to download the portion of the map that is new or changed. Say goodbye to the days of downloading massive 5GB map updates every time there is an update. Incremental map updates was something that I blogged about back in 2012 and it is great to finally see someone implement it. I have not yet read anything that confirms how often incremental map updates will be available or if we'll have to periodically download full map datasets every so often with incremental updates in between (similar to TomTom's MapShare program and ALK's MapSure method). I hope not, but we will see. Having small incremental map updates available every couple weeks goes a long ways towards competing with the near instantaneous nature of Google's MapMaker program.
Final Thoughts
One item that HERE should clarify is exactly how offline mode works. It appears, though I have no way of knowing, that the app is either 100% online or 100% offline. The confusion stems from the warning received when activating "Use app offline." This warning indicates that the data connection will not be used. Does this mean that when I am online and using the data connection (i.e., for traffic, search, etc.) that I am also being served ONLINE maps rather than the maps that I've already downloaded?
My preferred mode of use would be to use the downloaded maps where I've downloaded them irrespective of whether I am in online or offline mode. I'd prefer to use offline maps where I have then and still use the data connection for traffic, search, etc. I'd only want to use online maps in areas where I haven't downloaded any maps. This would lighten the data load but still make data available for other uses within the app.
It is unclear how this works and I hope HERE will clarify.
Conclusion:
This app has good bones. The app is extremely fluid, fast, clean and stable. The map is very readable. It seems to be a great base to build from. I think HERE needs to clean up the horribly confusing two-settings menus issue. I also hope that they quickly streamline the steps it takes to actually begin navigation. Contact integration is something that I hope is coming soon. And the "must have" feature if you are going to effectively compete with Google Maps is voice recognition. Interestingly Google just announced that Google Now will have ability to be used with 3rd party apps. That might present a great opportunity (combined with HERE's universal search feature) to make the primary interface to HERE your voice. That would be huge.
The app has a long way to go in terms of features if the goal is a PND-like experience on our smartphone. But lucky for HERE, in my opinion, NO ONE in this space has nailed it yet. Everyone comes close but falls short of "my perfect solution." HERE has a chance.
Over time, I could see this app earning some dedicated storage on my phone. I hope that this is successful enough to continue to get development resources because competition is good for the consumer.
Subscribe to:
Posts (Atom)


































