I've spent a long time using various Android phones and apps to navigate on a motorbike, and mostly been unimpressed with dedicated satnavs. I've written a not-unbiased comparison of dedicated units with phones and generally while I'm not completely satisfied with the app offerings, they do seem better than using a dedicated unit.
I did, though, found myself with a surprise £350 and thought I'd figure out what the fuss is about; I bought a Garmin 346 LM in September 2018 (shortly after its release) and here I've noted down my first impression, my opinion after using it for its first week-long trip, and again about ten months later. I've been editing this 'backwards' so that the most-recent opinion is at the top.
It's now July 2019, I've been using this for 10 months during which there's been many one-day rides, fewer extended trips, a bunch of trail riding, an awful lot of routine 'take me to this postcode' and I think I've formed a proper opinion.
In summary: as of mid-2020, it's in a box on a shelf and hasn't come out for a few months. I've taken the brackets off my bikes and if anyone wants to borrow it to find out what they're missing, let me know.
Contrary to my initial assumptions, there's some things it does well
- The mounting bracket is very good - one-handed fitting or removal of the unit, and it's obviously always automatically charging. It comes with a complete RAM mount.
- As promised, the screen does not go bonkers in the rain (because it's resistive touch); combined with the powered mount you don't need to think about the rain at all.
- It can be set to always track your route, so if the device is on you don't need to think about whether to start tracking or not.
There's also a few things that are good ideas that just feel a bit unfinished; it's not-as-good as the competition but does still function:
- Perhaps most surprisingly, it's bad at showing maps. It takes a long time to render maps (redrawing when scrolling/zooming), the quality is poor (presumably a function of the low screen res) and the density of information makes it hard to recognise what's being looked at. The Talky Toaster maps resolve the last of this, but at the expense of proper routing - you cannot show one set of maps while navigating with another.
- There is a Garmin phone app which allows you to send points to the device from your phone, so you can find a POI in your satnav of choice, or using Google maps, and 'share' it to the Garmin. The process is clunky and only mostly-reliable, and cannot send routes (only single points). It does work, but it feels more 2004 than 2019. Bafflingly, it also requires an Internet connection, for some reason.
- The search is still leftover from the '90s. The norm for satnav apps is to have a search box into which you can enter a postcode, or an address, or the name of a business and it'll just find it. The garmin has no such thing, and you instead need to navigate one or more different search field to find where you want to go. There is something that looks like it will just search everything, but I've never managed to use it to find where I'm going and I'm still not sure what it's actually supposed to be for.
- Perhaps relatedly, it's not clear what the difference is between searching 'Foursquare' or 'Tripadvisor', but many things are in both, and many things are also only in one or the other. Quite a lot of POIs are in neither; mostly I transcribe postcodes from my phone.
- Garmin's way of routing using specific roads is using a "shaping point". When you're in the mode for adding these to a route, the maximum zoom level is much less than in other modes, which is frustrating when what you want to do is put a point at a specific part of the map.
- There's a relatively-useful fuel tracker, where you set a tank range and it can warn you when you're at only 10% or 15% or whatever of fuel-range left. When this is on, though, *every* time you start the bike you get a full-screen warning telling you that it is strictly only for bike use and not car use, which does not disappear of its own accord. As far as I can tell, the only way to see the currently-remaining fuel range is to add it to the navigation screen, but in that case it's only populated when the device has a satellite fix, for some reason (so you cannot consult it while at a cafe stop, or something).
- One of my favourite functions of CoPilot is the 'On Route Alerts' which means you can have an icon display on the app when there's a POI in one or more of your chosen categories within 50 miles and tap it to see what it is. I set that to show petrol stations and if that's not displaying by the time my fuel range countdown reckons I've ~75 miles left I'll pull over and find a petrol station. Garmin's 'Up ahead' feature is probably going to be this useful in the future, but isn't yet. It cannot only display things on-route so there is no way to use it passively - you always need to tap through the menu to find out where the thing is. It also can't be set to show only petrol stations, you need to set three categories (I have petrol stations, cafes and cashpoints). Perhaps most-tellingly, I tried using it for a bit and now I just always pull over at 75 miles range and check.
- It doesn't automatically-adjust the screen brightness, which I suspect I only find surprising because most phones can do that and it seems weird to need to find the brightness setting manually these days.
- It can't be set to work in portrait mode, only landscape, which is very strange on an device whose main purpose is to show what's coming up.
- The maps are out of date - there's a series of junction changes in Central London that predate this device existing by several years, and are not represented on the latest maps. The device is best ignored when navigating around London (and presumably other large cities?) and I don't know what to recommend to people who don't know their way round there. There's a petrol station near me which has been closed for long enough that the building that replaced it has been itself replaced, and that's still offered to me as a petrol station.
- The device is built around the assumption that you will always do any planning on a PC and transfer it over - there is no pleasant way to set up a route on the device; the built-in map display is a very low resolution, and the device is incredibly slow at rendering the maps so even if they were easier-to-read the scrolling is still an exercise in patience. But when you plug in the USB cable, it will count down 20 seconds before presenting itself to the PC. There is no way to skip this, and given both the clunkiness of the process (plug device in, wait, copy GPX file, reboot satnav, import route, view route on map) and the tendency for it to not-work, this gets very frustrating very quickly.
- It's really slow; recalculation often takes so long that you've already muddled your way back onto the original route round whatever the blockage was before it's figured it out; it can take upwards of ten seconds to render the screen when scrolling around in the maps viewer; and converting from a GPX track to Garmin's internal idea of a route can take between 30 and 60 seconds for a 100mi route with four or five waypoints (during which the device can turn itself off through perceived idleness).
- Your options for planning a route while out-and-about are to either use an app on your phone (garmin doesn't specifically support any but Locus Maps can, for example, export its routes as GPX) and a USB-OTG cable to copy files over and then convert that to a trip, or to be carrying a laptop (and a USB cable). It's very tedious and it's telling that I've still not had a road trip that I've been confident to use the Garmin to navigate me round, it's all been one-day trips.
(October 2018) I went round a bit of the TET and used the Garmin as my main navigation tool for it. The idea was to just follow the GPX downloaded from www.transeurotrail.org and follow it, occasionally routing off it to find things like petrol stations.
So, the Garmin is very good at drawing a line on a map, which is all it can reasonably do with a GPX that involves trails; even with the Talky Toaster OSM maps it was very unreliable at turn-by-turn on the trail. I wasn't comparing directly (and I've never ridden those trails before) but it felt much less useful than Locus Maps' off-road navigation.
Bafflingly, while the Garmin Connect app lets you send locations to the satnav, you can't send routes. The only reasonable way to plan routes mid-trip is to use a USB OTG cable and/or micro-sd card reader. The unreasonable-but-expected way is to just carry a laptop with you... I'd opted for the latter for several reasons, and found that basecamp relies fairly heaving on having a proper mouse, too, since that's the only not-infuritating way to zoom onthe map...
I tried using the tools I'm used to (Viewranger and Locus Maps on Android) to create GPXes and send them to the garmin to create on-road routes, but it *always* complained that there were too many "waypoints2, and offered to convert them to "shaping points". I don't know what the difference is, but often I seemed to get the right sort of routes, though I don't know how reliable this is.
So, generally, I stuck to having it just draw the GPX route and follow it by keeping an eye on the screen, which is fine at dirt-bike speeds. I did try to use it to find things to use - petrol stations, restaurants/cafes, motorbike shops etc. - and it was all but useless at this, to the point where I think I must have got something wrong. It was *always* faster and easier to use my phone and either transcribe the postcode, or send the location to the satnav.
I think that most of the obvious failings of the device - that you cannot reasonably view or plot maps on it because the screen resolution is so poor - is probably explainable as a result of it needing to be a resitive touch screen and those having a poor resolution. I've not really researched it, but I want to believe there's good reason my £350 navigation device is so bad at navigation. And I've not yet managed to explain why it takes so long to render the map.
I can now see myself using this for trail riding and off-road biased trips where I can create a GPX route and send it to the device and have it drawn on the map. I haven't yet worked out how I'd make it work on an extended road-riding trip, where I'll need something less prone to reinterpretation than a GPX route. But I haven't yet looked.
(September 2018) I’ve resolved to try to not have fully decided how good an idea this was until at least post-Christmas, but from a first week-and-weekend’s riding (some commuting, two blood runs and a day’s errand-running) this is better than my phone at:
- Plugging in one-handed
- Not worrying about charging
- Always being a satnav and never accidentally-switching to something else
And worse at:
- Sending me to petrol stations that haven’t existed for five years
- Finding its position quickly
- Recalculating a route quickly when I turn off (perhaps because of a road-closure that’s been in place for years…)
- Creating a route on-the-fly out of a series of waypoints
- Showing an overview map that conveys much information
I expect some of this this will get better and the rest just more-acceptable with time, but I’ve really not had the “why didn’t I do this sooner” thing that I keep hearing about other people doing.
The "Favourites" feature is very crude and unconfigurable (which it may be worth me figuring out Baseamp to fiddle with?) but the Garmin Connect app installs itself as a mapping thing, so when you "open" a location on the phone (from a calendar event, say) you can send it to the satnav. I suspect that I’ll carry on using my phone for storing locations and whatnot, and just send them to the satnav as I'm used to sending it to a satnav app.
Right now, I think it’s worth having (and will feel less lacking if I can move more audio-player controls to my headset from my phone) and I’m not really thinking about just getting shot of it yet, but I can’t see myself becoming one of those people who advises other people buy one. This is definitely lacking in almost every way compared to CoPilot and friends, and I’m not (yet) convinced that that’s just familiarity.
It's 20th September and it's arrived!
Out of the box, first impressions are not great; they're still using the USB socket that's so old that I know it as "the one GoPro use", and I don't even have a GoPro (or any of those cables):
The bracketry is all easy to fit and the lead's surprisingly long and thing; the 12v/5v step-down box is partly along the wire, but does mean that it doesn't *need* to be on the bars or right by the battery, and is easy to hide away in the plastics.
Bizarrely the screen seems to only have a landscape mode. Hopefully I'll figure out where that setting is later.
There's very limited options here, really. The Zumos have the widest selection of features and are the most-modern, the Montana is specifically aimed at off-road riding, and the Monterra is actually an Android device and so may solve all my problems.
The Monterra is an Android 4 device (Android 5 came out in 2014; 4 years ago at time of writing; 8 is current) so even if the apps I like now do work on it, it's likely they will stop at some point in the future. This was clearly Garmin's experiment with Android, and they've sadly decided to not keep it up.
The Montana is the one everyone recommends, because it's got an 'off road' mode and an 'on road' one. The off-road mode doesn't appear to add anything; it's not any more aware of rights of way than the road-mode one and is still largely used to display GPX routes. The on-road mode is much more primitive than that found on the Zumos.
The Zumo can be loaded up with an off-road map (courtesy of TalkyToaster, who is recommended for the Montanas over Garmin's mapping anyway) and can have a GPX file displayed over the top. While you can trivially switch between off-road and on-road on the Montana, it seems you can do similar on the Zumo just by changing whether the map has just-roads or everything on it. It's also got the much-better road mode, and the modern ones have some sort of smartphone syncing.
|Front Axle Allen Key||14mm|
|Rear Axle Nut||22mm|
|Spark Plug||NGK CR7E|
|Front Brake Pads||EBC FA209/2|
|Rear Brake Pads||EBC FA213|
(fill 2L, pause to let it flow down, fill last 0.9L)
The brake pads are the same (both front and rear) as a Husky 701
Footpegs are compatible with the XT250 (08-18), YZ/WR 125/250/500 (91-96), YZ80 (91-04), XTZ750 Super Ten (89-18) and Husky TC85: https://pivotpegz.com/search?q=PP-16
It's often said that a standalone satnav is far superior than a smartphone app, often for a multitude of reasons that are demonstrably wrong ("offline maps", "better signal", "better routing"). Here, I aim to compile all my related arguments on the topic :)
Relatedly, I did give in and buy a Garmin, and I'm documenting my finding out what I've been missing separately.
There's no technical reason for apps to be less good at the important bits than a normal satnav - smartphones have plenty of storage space for maps, use the same or similar GPS and GLONASS chips and are at least as likely to be able to use GSM and WiFi to get better/faster fixes. There's some obvious benefits, too (drawbacks are listed further down): a smartphone is more of a general-purpose computer so you're less dependent on the way the satnav happens to implement podcasts or music, and can just use whatever app you prefer. You're not tied to any particular route-transfer options since you can just email them to yourself, and you can use the web browser to look up addresses not already in the device. Get your calendaring and route planning right and you can turn up to ferry terminals with the booking reference appearing on your screen as a notification. You can even use multiple satnav apps - mid-route I'll often switch to a different one to find a petrol station or lunch stop, for example, and I use different ones for road and off-road riding. Finally, the hardware's generally better - the maps render faster, the screen resolution is much better so looking at maps when looking at an overview of the route, or modifying it, is a much more pleasant task.
I use a few of them quite frequently:
It's generally regarded by anyone who has tried anything else as pretty unideal, but it's catching up and is workable if you're not interested in plotting a route and instead just want to go to your destination; I keep it around to use when I'm already in a town and want to find a restaurant or something, but I'd hate to have to use it to do anything substantial. It occasionally gains and loses support for multiple waypoints, but each time it supports them, if you cause it to recalculate for any reason (by going off-route) it'll recalculate directly to the destination rather than considering all your waypoints.
- Probably already installed
- Has every POI
- Not great at planned routes; if you go off-course it'll often recalculate directly to your last point, ignoring all waypoints
- Offline mapping is strange; you download small regions at a time and they are prone to expire
- No offline route-calcuation
CoPilot's popular among people who plan routes with several waypoints; one of their big markets for which they make another app is caravanners and another is truck drivers.
One of the big features for me is that you can set 'Routing Profiles' where you can adjust the priority/cost of using each road category (dual carriageways, main roads, urban roads, small roads etc.), and save a series of profiles - I have a 'rideout' one that generally sticks to good roads, a 'Dirt Bike' one that sticks to shit roads, a 'No Motorways' one that does what you'd expect, and a 'Normal' one that's like all the other satnavs. An other is the "POI Alerts" (which are confusingly in the "Safety Alerts & Warnings" menu); you choose a series of POI categories and a range, and a little icon appears on the map display when a matching POI is in range and on- or near-route. You can tap on the icon to scroll-through them, and there' s a button on each to set it as the next waypoint on the current route.
I think it's about £35 to get CoPilot premium and the UK maps. You get a few days free as a trial, during which there's no voices for navigation (but still icons on the screen) and no automatic recalculation - you have to hit a button on the screen.
- Designed for planned-routes; easy to create and edit routes on the device
- Handy features - route profiles, up-ahead alerts, traffic routing, speed limits etc.
- Uses its own route format (.trp) and loading the route into CoPilot involves copying it to the right folder manually; you can't open a .trp you emailed yourself with copilot.
Calimoto's big feature is routing based on corners; it's meant to be the 'windy roads' option, basically. It's very good at that, but seems unaware of the sizes of those roads - sometimes you'll get gravelly singletrack roads, other times it's swooping major arteries. That said, it's very good at not being boring. You can use a map region online indefinitely for free; you pay to get all maps, offline maps and to be able to tune the routing.
- Easy to share routes with other Calimoto users at the beginning of a ride
- Featureful storage/search/recall of tracked rides so you can go out again
- Can open-with on a GPX file so you can use anything else to plan the routes
- Reliably produces non-boring routes
- Entirely useeful without paying
- Feels quite different in different regions; I get singletrack roads in Hertfordshire, but major A roads in Surrey, say.
- Lots of cutesey prompts that get in the way more than they entertain
- The map drawing is _really_ buggy; though the route is always drawn correctly sometimes it doesn't match the map underneath.
This is excellent as a take-me-to-a-postcode app; it can't do multiple-waypoint routing, but it much simpler and clearer than TomTom, with decent traffic estimates (when you've got data on) and speed camera warnings, and it's all free. You can download the maps or use them online, and it's completely free in either case.
- Simple to use, feels finished & polished
- Good traffic estimates & speed limit awareness
- Lots of POIs
- Can't do multiple-waypoints; no way to load a route in
The killer feature here is turn-by-turn navigation off-road, but this is also a featureful and functional, if a little clunky, road satnav. I use this primarily to store my PoIs (cafes, ferries, trails, covid-compliant laybys etc.) and for navigation off-road
- Turn-by-turn off-road routing (but as a bicycle, so you need to have a high-resolution route)
- Can create, load, edit and export GPXes; it's a pretty good GPX editor to go alongside any other satnav
- Useful for all outdoorsy things; can buy OS maps and local equivalents, or use various types of OSM map for free
- Excellent for PoI management/storing - good categorisation, exporting/importing of GPXes
- Very configurable in display and instruction
- * Route calculation is online-only and requires the installation of a helper app (bRouter)
- Quite clunky; definitely a map app first and a satnav second
- Very poor search; best used as an app you 'open' a location with, rather than searching in the app itself
Some I've not used much recently
These all might have changed somewhat since I wrote this:
Like Locus, this is map first and satnav second, but it's a hugely better search for PoIs. I barely use it now because Locus has all my PoIs in it now, but I've nothing against it.
The app's fine; it's like the modern TomToms (not the Rider V1/2, but the 300 series); the UI is really modern feeling, but a bit surprising and oddly lacking in features. I've not yet managed to plan the route I actually want to do in it, and while it's got this neat 'timeline' down the right hand side of the screen to tell you where on your route any roadworks and petrol stations are it doesn't give you any information about them (like how far away they are). It does have a really handy thing that keeps track of your average speed in average speed camera zones, though. It feels polished rather than finished, really. It's £30/year, but you get 50miles per month indefinitely as a free trial (maps are free). Aside from the average-speed zone handling and familiarity with the TomTom interface there's no great reason to get this over Here, to my mind.
It's completely free, but the user interface is pretty surprising. I know people who've got used to it, though, and now don't mind it. You get one country's map free with the install and it's actually pretty good at points of interest, but it doesn't do anything exceptionally well - I can't think of a reason to use it over Here Maps.
Garmin's app. It's long been famed for being atrocious, I'm amazed it's still on the play store. But I'm also amazed people still buy Garmins. :)
is now a Google product, but it's actually good :) For a long time its main feature was the community - it's all about showing you user-reported cameras, accidents, and traffic. Surprisingly, it still works for that, and despite being Google underneath it seems a pretty reasonable satnav, though I've not used it for a couple of years.
Weirdly, when this argument comes up on forums and suchlike, the people arguing in favour of standalone satnavs seem to generally cite features that are commonly available in all the apps (like offline mapping) as if they're comparing with a quick glance they took at Google Maps. The things that make standalone satnavs better are those that come from the 'standalone' bit, and they're almost all to do with the hardware.
If you were to design a standalone satnav for a motorbike, you'd have a bracket you can clip the satnav in with one hand, and make it such that as the satnav's put in some sort of robust, waterproof power connection is engaged so that the thing is always charging. You'd use a screen with something to prevent glare, which works well with gloved hands (perhaps resistive, and a UI that doesn't demand multitouch?) and you'd probably have a series of hardware buttons in addition to whatever's on the screen.
When using a phone, you'll generally use a pouch or a Ram X-Grip which is only complicatedly one-handed and often obscures buttons or bits of the screen, and you'll need separately to plug in your relatively fragile, not-waterproof USB micro lead (which has until now just been dangling about) as a second step to just mounting the device. Android's glove mode doesn't really work and "touch-screen compatible " gloves rarely are and that really bright and vivid screen that's great for looking at photos (and maps) isn't great for glare (and a case is only going to compound that). Iphones only have one physical button, and of Android's three, one's famously unpredictable.
I don't know many people who have started using a dedicated satnav in the past four or five years. I know lots of people who last used one four or five years ago (in the days of the Rider 2 and the Zumo 550) and have been put off them for life (I'm in that camp). Everyone I know who uses one now, though, used one back then.
It's really hard to get a decent go on a dedicated satnav, though - none of the people selling them seem to think that offering test rides is particularly worthwhile - so I don't really know much about the options hardware-wise any more, and I've been told that extrapolating anything from my use of a Rider v2 and a Zumo 550 would be incredibly unfair.
What I do
I don't think what I do is necessarily universally right, but it works for me. I almost exclusively use my phone as a satnav - I've a Cat S60 and a Ram X-Grip. I also now have a Garmin Zumo 349 which I'm trying to force myself to use more, but I tend to default to my phones.
If I'm doing any off road riding I use Viewranger to check the OS maps and plan the route (because I happen to have bought the whole of the UK in that now), and Locus Maps for navigating. If I'm doing all-road I'll just use CoPilot for planned routes or Here Maps if I just want to get to an address.