JohnCNA

Thanks for the clarification. Early on, I did not like the 'Next stage' function and quickly stopped using it. I may not have been using it properly but what would happen was: 1. With a 3 or 4 stage multi, stage 3 Next Stage overwrote stage 2 Next Stage. And 4 overwrote 3. I would only have a record of stage 4 afterwards. 2. Doing another multi would overwrite the Next Stage from the previous multi. So I just used waypoints for the stages after that.

You are misremembering what you did on the 64x. I have the 64s/t and you cannot edit anything on the Geocaching dashboard. It is on the map screen where you can select 2 or 4 data fields. This is my preferred display and I have the 4 fields set to Pointer, Heading, Distance, Time. I can't speak for the 66x, but I would guess it will be the same. Personally, I found the Geocaching dashboard to be useless since you could be navigating to a waypoint or geocache but the small dashboard compass arrow will always point to the nearest unfound cache, not what you have selected.

"Left side of trail" I guess if we knew from which trailhead the CO had started, this might be considered useful.

I don't understand why you should see this as a problem. It could a compliment, actually. I have had a couple other cachers tell me that they look at my profile occasionally to see where I have been because they share the same interests as me. "You like long walks off the beaten trail and so do I." or, "I would never had known about that nice preserve/park/trail/cache series if I had not seen your logs." If I'm looking at some cache logs ahead of an outing and see some recent found logs from cachers I know, I feel more confident in my potential success.

It's not necessary to have separate lists in Basecamp and merge them. My work flow is to create the empty Basecamp list first. Then select File/Import. Navigate to the folder where I unzipped the PQ. Hold the shift key and select both the geocaches and waypoints GPX files. Basecamp will import both files into the same list in that one step.

Are you using the Geocaching Dashboard? When I used the Geocaching Dashboard on my eTrex 30, it did exactly what you mentioned. It stopped navigating when I got close to where it thought the cache was. Try using the compass screen or the map screen instead to see if it makes a difference. I ended up liking the map screen set up with 4 data fields much more and haven't used the Geocaching Dashboard since.

The only watches (and companion phone apps) I am aware of that directly support geocaching are the iPhone/Apple Watch/Cachly, and Android Wear/Samsung Watch/Locus Map The iPhone/Apple Watch/Cachly combination is really excellent. On Android, the geocaching support on Android Wear or Samsung watches with Locus Map is quite limited but functional.

If our handhelds behave the same as Nuvi's, current.gpx is created and overwritten by the device itself every time it boots up. It does not load it into memory first. This would explain why copying a current.gpx file to the device will not work. I highly recommend using Basecamp if you want to use and/or manage previous tracks. I do this very often myself. Basecamp will allow you to combine a group of waypoints, geocaches and tracks into a single output GPX file on the GPS or you can manage/copy them inpedently if you wish. Just don't name it current.gpx. Then in the Track Manager on the GPS, select the track and set "show on map". Or Navigate. To turn off the current track from displaying, go to settings, track recording and set it to 'record but do not show'.

I think you're right. So sad that the Groundspeak app doesn't import GPX files like all the other third-party apps do.

There is a way to share a GPX with others. Sort of. ? Make a list and make it shareable. Click Share and email the link to others. The others click the link and open your list. They click Copy List. This copies your list into their Lists page. In the Geocaching app, they select Lists from the menu and select the list. Will this work for Basic members as well?

You could try Locus set for Guide On to the geocache, with Google Navigate set to the parking coords. I just tried it with my tablet, Locus zoomed out to show the entire distance and Google of course shows zoomed in turn by turn. It's actually rather cool, I think.

Well that was an interesting experiment. With a forced rotation to landscape, the compass orientation is still towards the top of the phone/tablet. So although the screens are properly redrawn, the compass still thinks North is at the top. Not so useful after all, in my opinion. Perhaps other similar utilities might compensate for this but I wouldn't think so. I don't use the Geocaching app so I never noticed the compass issue. Apps that I know natively handle handle landscape mode are Locus (my favorite) and GCDroid. I'm thinking the OP would be better served to just switch apps.

I use an app called 'Ultimate Rotation Control'. It allows you to force screen rotation on apps that won't do it on their own. I just verified that it forces the Geocaching app to rotate as desired, both on my phone and tablet. It also allows you you to force apps to a specific orientation on an app by app basis. I have a couple apps that force landscape mode on my tablet and this forces them to rotate to portrait as well. So it works both ways. I see that there are several rotation apps in the store but I only have experience with this one. It's a paid app with a free trial. I bought it several years ago so I don't remember what I paid. $2 maybe? Anyway, there are some easy solutions to what you need.

FizzyCalc is a wonderful app on Windows. On Android, I highly recommend 'GCC - Geocache Calculator' for when you need to do projection (and many other) calculations in the field.

Yes, the included basemap is pretty limited. Some favorite free map sites are: http://garmin.openstreetmap.nl/ http://www.gpsfiledepot.com/

Since the OP has expressed a desire to have a wrist-based solution and has an Android phone, you might also look at a smart watch instead of a fitness tracker for your wrist. Currently on Android, Locus Map supports both Android Wear and Samsung Galaxy watches. I have a Galaxy S9+ paired with a Galaxy S3 watch, running The Locus Map phone and watch apps. Basically, I select a cache or waypoint on the phone, select "Guide" and it shows my position on the map with a bearing line and distance as you would expect. Put the phone away and look at the watch and it duplicates that display on the watch screen. The watch app also lets you Start/Pause/Stop track recording. And it will run concurrently with a fitness tracker app on the watch. I just thought I'd mention another alternative to what you're looking for.

Isn't this a rules violation? I thought Groundspeak had changed the rules to disallow CO's requiring posting selphies in cache logs.

Good lists! Since I do a lot of woodsy caching I add: One pill bottle with some: Advil, Ibuprofen, Sudafed Benadryl stick Insect repellant Cammo tape A few sheets of paper towels Last two items can be used for cache repair as well as makeshift bandages.

I would expect to use it the same way i use it with my phone. When i see the battery getting low, connect the brick. Check the charged status in 30-60 minutes. Disconnect and put the brick away when it shows it's charged.

All USB are 5 volts. Mini, Micro, C and even Lightning.

I wonder if anyone has used a recharging brick to recharge the batteries in the Garmin. Should work, in theory. If you already carry one for your phone on longer outings anyway, all you'd need is the appropriate cable.

And nothing liquid, please.

This seems to be an oversight. I wanted to download the latest puzzles from a particular CO. View the geocaches owned on his profile page. Checkbox the ones I want. The only option is to download waypoints (LOC file). Shouldn't it be showing a full GPX option for us premium members?

My friend has a 62s and I have a 64s. We will usually 'zero out' pretty close to each other, but in maybe 20% of the time, we will zero out 30-40 feet apart. As we search over 15-20 minutes, we usually end up pretty close again. We both have WAAS enabled. I have turned GLONASS on and off but have not seen that it makes any difference in how often our handhelds agree or not. Given enough time, the devices eventually 'settle' pretty close to each other. I suspect that the filtering/averaging firmware might be slightly different. The antennas look the same, but you're right that they could be a little different under the cover, too.

I've been using the new map and search for a while, but some new changes just popped up today (12/06). A LOT of functionality has just been lost if we're using a mobile browser. Using a mobile browser on my Android tablet or phone using Chrome, I can no longer tap on an icon on the map and have it open the description in the pop out panel. This works on the default internet browser, but not in Chrome. The Filter option works as before on the Android tablet but is no longer functional on the smaller screen of the phone. The Filter page on my phone stops at the checkboxes for the cache types. It will not scroll beyond that to show the rest of the filter options. This is happening with both browsers on the phone. (Android 8.0.0) I get that the new option to "search this area" reduces server hits, and it actually makes it easier/faster to pan the map to a new area. But it's pretty annoying to move the map a mere millimeter or on a mobile device have it interpret a screen tap as a millimeter pan function and have it pop up the "search this area" button again. You should really be looking at the amount of map change first to determine if a refresh search is necessary.