The Treehouse Blog

Who buys a satnav in 2019? A review of the Garmin Drive 65

on Aug.24, 2019, under Technology

I recently purchased a new Garmin Drive 65 to replace my aging Garmin nuvi 200W I purchased in 2008.

Why replace it? The 200W still works, though its internal battery does not. I had purchased the lifetime map updates at one point, though it needs an SD card for more capacity, and takes forever to update. I also was interested in adding capabilities like a higher resolution display, lane guidance, topography, and traffic.

I also have other options, of course. In the RAV4, I have an android-based radio, that itself is aging and far from latest in terms of operating system, but can run a variety of things like Google Navigator, Open Street Maps, and Waze. I also have a cell phone and several older ones that could do the same. The F-150 has the 8″ Sync2, which didn’t come with navigation, but I added it by buying a map card and some reconfiguration. But none of these is perfect. The RAV4’s unit has a small screen that is essentially impossible to type on while driving and lacks useful voice recognition. Navigation with Google is great, but is useless when out of cell range, which is still happens often enough when I’m out exploring. The navigation and driving user interface for Open Street Maps is lacking, but the offline maps and topography are great. And the Sync2 lacks the ability to input coordinates, which is often essential when out exploring. So, despite using these other systems when their limitations do not matter, I still feel the need for a standalone satnav, and take along the nuvi.

I’ve take two test drives with the Drive 65 so far. Here are some of my observations.

Directions. The voice navigation prompts are improved versus the nuvi in that it speaks street names and gives meaningful prompts like “at the stop sign.” Unfortunately, this is outweighed by the fact that in many cases, it skips over steps. More than once, where there are two back-to-back intersections, it will speak the direction for the next one, not the one you are at, skipping it. Sometimes this leads to being given the exact wrong direction for your current location. Now, I’ve had this happen on the nuvi I’m sure as well, but it seems far worse on the Drive, and I wonder if this has as much to do with the map data it’s using as it does the algorithms it uses.

Traffic. The Drive comes with a traffic-receiving power cable. Unfortunately, it does not pick up any service in the local area. It can also get traffic data via a Bluetooth link to your cell phone, so I set that up. I don’t really mind this, since traffic information would be generally more useful in cell-available areas anyway. When driving home from the Letterykenny area, it wanted me to take Route 11. Route 11 is currently closed on the other side of Shippensburg for a bridge replacement. This closure is beyond my route home, so it should have had no effect on me. It would calculate a route using 11, and then say “Route 11 is closed” and change the route. Then when I would start driving a different route, it thankfully no longer says “recalculating” when you do this, but after it rerouted, it would say “Route 11 closed” and do it again. Incredibly annoying, so I turned off traffic.

Terrain. Terrain matters a lot to me, as when you’re in the mountains, vertical separation is significant. It also helps give visual cues as to where you are when looking a the map. I almost always have Google Maps in Terrain mode. The Drive 65 has the “3-D buildings and terrain” feature. This is presented on the screen by shading. It’s not particularly high resolution, but it does let you see some contours. It’s really not great though. The “bright” side of the shading seems indistinguishable from the white background of the map, leaving you only to see the dark side of the shading, which is deceiving as you only see about half of the terrain feature. There appears to be no way to turn on iso-lines to give you a better indication of the terrain features.

Screen. The screen is bright and easy to see and huge at 6.95″ diagonal. It might even be too big for the application. 1024 x 600 pixels, glass, multitouch – this is where it really shines over the nuvi. With the “bean bag mount” using it at a downward angle in the office, sometimes touches on the keyboard are not registered as well as I would like. Not sure if this is just angle or what. So far have not noticed that while in the vehicle. There is plenty of room for information on the screen, and there are options as to what you want to display which seem useful. One tidbit I don’t like is that on the coordinate entry page, there is no backspace button, though you can select a digit to modify it.

GNSS. The satellite status page shows both GPS and Galileo satellites, but not GLONASS.

Points of Interest. The points of interest database is something I have grown to depend on in the nuvi. When saving locations for an upcoming trip, the Drive cannot find Lake Durant Campground, which is a New York State public campground – so something it should find. With network connection, it finds it using Foursquare, but gives the wrong location for it.

Overall, I would say I’m disappointed with the purchase, but planning to stick with it. I’m not surprised, and hold little hope that other products are better at this time. I hope Garmin commits to improving the software of this unit, as most of the problems likely could be solved. I may have more to say on it after my fall expeditions.

Comments Off on Who buys a satnav in 2019? A review of the Garmin Drive 65 :, , , more...

Fedora 27, Nvidia, Gnome, and Wayland

on Mar.26, 2018, under Linux

I’ve been having trouble recently with my home desktop having gnome-shell chew through 100% CPU and leave the system unresponsive.  Ordinarily, it seemed that updating the binary Nvidia drivers shortly thereafter would fix it, but not most recently.  I followed someone’s suggestion to switch to lightdm instead of GDM, and while that worked, lightdm does not play nicely with Gnome in some ways – specifically screen locking does not integrate, which is quite annoying.  Ultimately, I think the problem is the switch from Xorg to Wayland, and the Nvidia drivers not playing nicely with that.  I just now switched WaylandEnable=false in /etc/gdm/custom.conf.  So far that seems to be working.

Comments Off on Fedora 27, Nvidia, Gnome, and Wayland more...


on Mar.25, 2018, under Philosophy

I just finished reading Trekonomics, a book on the economics in Star Trek, by Manu Saadia.  The book is interesting for trying to accumulate a lot of the economic references in Star Trek and make sense of them.  In the end, I think it falls short – while the 24th century Trek tries to represent a post-scarcity near-utopia where physical needs are met at no real cost, where automation has displaced the need for all labor, this is clearly a contradiction.  Particularly with Deep Space Nine, the Federation has finite limits on resources such as ships and non-replicable materials.  Throughout Star Trek there are people that perform repairs and maintenance – despite ubiquitous automation.  I’m not convinced we’re on the verge of becoming post-scarcity or post-labor.  While our economic progress has meant the improvement in the quality of life of essentially everyone, we are still facing challenges with automation displacing labor, not unlike what we have encountered since the industrial revolution.  Whether we reach a point where automation permanently prevents a large segment of the population from gainful employment, and how we handle it, remains to be seen.  Star Trek, understandably, does not dwell on what place the inept have in its society, instead focusing on the top of the class.  Still, an interesting read.

Comments Off on Trekonomics :, more...

Android File Manager

on Feb.25, 2018, under Android

It annoys me that Android has no native file management application. I know, I know, “it’s a phone, not a computer and phones don’t have files”, or some such nonsense. I’ve mostly used OI File Manager, since it is used as the file choose for some (old?) apps, and it’s been around a long time. Any more though, I tend to get lost in the navigation, having to close the app for it to see files again. This morning I went through a lot of the file management apps on F-Droid, and concluded that Amaze is the best for my needs currently. It seems to be actively maintained (latest release less than 6 months ago). It supports root access. The navigation seems smooth and intuitive. Have you found a better free or open source file manager? I’d be curious to know.

Comments Off on Android File Manager more...

Fedora 27 Nautilus does not open files on double-click

on Jan.15, 2018, under Linux

Recently, I’ve been encountering an annoyance on my Fedora 27 desktop machine. When I would try to open a file by double-clicking it in Nautilius, it would refresh the display, show the “wait” cursor, and then do nothing. Today I finally spent some time to trace it down. A strace of nautilus showed:

[pid 32262] execve("/usr/bin/exo-open", ["exo-open", "--launch", "FileManager", "/home/balleman/Documents/...

Manually running this exo-open command gives the results I was experiencing – it reloads Nautilus but does not open the file. exo-open is part of the Xfce desktop environment, which I’m not actively using. Removing the exo packages and dependencies on it appears to have fixed the problem. Not a perfect solution, but I will gladly take it over spending more time on this.

One reference I found to this possibly being a bug is here:

Comments Off on Fedora 27 Nautilus does not open files on double-click more...

October 2019
« Aug    


Content Copyright © 2004 - 2018 Brady Alleman.
All Rights Reserved.