Zargonians

We are full-time RVers and rely mostly on cell service. We changed locations yesterday and I have 5 bars of AT&T 4G service and tried a 3 cache list and it worked. Then I tried a 250 cache list for our next location that won't have good cell service and it failed after appearing to get all the way to the end of the download. I then connected to my Verizon hot spot (which only shows 2 bars of 4G) and it successfully downloaded the 250 cache list. Fortunately, we have a Garmin Montana GPSr and use GSAK to download caches to it, so we do have a backup. If we were relying just on our cell phones, we wouldn't be doing much caching if we relied on downloading offline lists.

Tried again tonight and it is FINALLY downloading! I downloaded three offline lists sucessfully. Hope that it continues to work the next time I need it. Thanks to whoever fixed it.

I have also been having this issue for weeks. Sure wish someone at Groundspeak would check into this. I have a Samsung Galaxy S9+.

I have been trying to download various offline lists for at least three weeks with no luck at all. Each time I try, I get List Download Failed. Have tried with wi-fi and without. Previously I could download an offline list with no problem whatsoever, but something has changed and I can no longer do this. Would someone at Groundspeak please take a look into this issue. We often cache in areas with no cell service and without an offline list, we are dead in the water. Help!

I have been trying to download a seven cache list for two days. Each and every time I try it I get "List download failed". Have tried downloading other lists with no luck as well. Can't geocache in areas with no cell service without it. Have tried downloading using wifi and cell service, same issue.

Thank you! Yes, I suppose we are unique in that we move pretty much weekly, except for four months in one place in the winter. I could leave the home coordinates as they have always been since we began geocaching, but then I won't get notifications of new caches where we are at the moment. I didn't reaize that FindStatGen can generate stats based on history of home coordinates. Will have to try that out! Thanks for your input!

Ah! Great idea! Thanks for that...wouldn't have thought of doing that!

Thank you! Did not know that. Now to decide if we should change it or not!

Thanks for the link to setting the home coordinates. That was not quite the answer to the question I asked though. If I do change my home coordinates, will all of my statistics change as well; i.e., finds furthest from home and distance to finds. This could mess up some challenges we are working on.

We are now full-time RVers, so don't technically have a "Home" base, so we have never changed our home location in geocaching.com. The longest we stay in any one place is Florida for four months every year. We are originally from Alabama. If we change our home coordinates to our Florida winter home, how does that affect our statistics; i.e., finds furthest from home, distance to finds, etc. Does it automatically readjust all of our finds stats to match the new location, or will it pick up from the date we change our home coordinates. Also will it change our state standings? Thanks for any help you can give!

Sorry! Just noticed this as I don't log on to the forums often. I am using Version 5.8.3, Android 7.0, Samsung SM-G930A (Galaxy S7). I do have several lists saved for offline, but not sure how many at the time of the issue. Since I posted a few weeks ago, I have had no further issues of solved coordinates not showing up on the Geocaching app and my map populates super quick now instead of taking at least two minutes to load. Uninstalling and reinstalling the app seems to have solved my problem for now! I will say (although not pertinent to the subject post) that the app is lagging again as it did when it first went live. I will be navigating towards a cache and the distance will constantly read 640 feet (for example) and will continue to read the same distance no matter how far I walk. Luckily my caching partner carries his GPSr and we are able to navigate using that method. I experienced this problem for probably the first month or so after the "new" app went live, but it finally resolved (maybe after an update). Not sure why it is suddenly reverting to that behavior.

I was also having this same issue and came here to see if anyone else was experiencing the same thing. Some of my solved puzzles showed up in the app at the solved coordinates whereas others for no apparent reason, would not show up at corrected coords (even though they do on geocaching.com). I read through all of the info above and decided to delete my app and reinstall. Even though it appears to be the same version as it was before I uninstalled/reinstalled, it solved the problem. Also solved an issue I was having of taking a couple of minutes to load caches on the map. Now, my solved puzzles are showing up at corrected coords on the map online as well as in the app and caches are loading on the map much faster as well! I'm a happy camper!

First to say I love the changes that have been made in the latest update as far as the map icons being so much more useful/visible and the compass not going to sleep after 30 seconds. However, the most fundamental function of the geocaching app is to find a cache and it is almost impossible using this app. Was very frustrated yesterday as I was wandering around aimlessly waiting for my compass to count down even though I had moved more than 100 feet, in each and every case. My caching partner was using his GPS and walking in a completely different direction than I and finding the caches. I never did find a cache yesterday using the new geocaching app. I used c:geo if I really wanted to navigate to and find a cache. The GPS lag on Android is a huge problem and makes navigating to a cache impossible. My Samsung Galaxy S7 is updated with Android 7:Nougat.

From what I can tell, the Trails map type does not show exit numbers, but the Google Map "Street" view does. Alternately, if you start navigating to a cache, a button should show up in the about page that will open up driving directions (arrow in a diamond, in the top right). I use the driving directions a lot when navigating city streets to a cache. However, this still does not help for pre-planning a long road trip and making a list of caches in counties along the route. We often travel pulling our travel trailer, so look for exits with caches at truck stops or other RV friendly parking places in the counties we want to cache in. I am using the Google map preference on geocaching.com and have also tried the OSM preference, but neither shows exit numbers on major highways. This is frustrating when comparing Project-GC maps for counties in a state, which does show exit numbers, with the geocaching.com map that no longer displays exits. It takes much more effort to pinpoint exactly which exit is needed for the cache in that county we want to hunt. I can still pull up the Classic app and it still displays the exit numbers, which helps a little, but only until March 23rd. Not being able to look at highway exits on geocaching.com is definitely making it much more difficult to do something that was so easy before.

We've been planning a lot of trips around geocaching lately and hunting for caches in counties along our route. For planning purposes, the old app shows the exit numbers along highways, but the new app does not. Also noticed that the website no longer shows exit numbers on highways either. I know that it used to from planning previous trips. Now it is almost impossible without a lot of research to figure out which exit to use to hunt a cache. Is this something that might be fixed soon?

Add to the laundry list the fact that the GPS goes to sleep after 30 seconds which requires waking up the phone to continue navigation. I changed the timeout on my phone screen to 1 minute, which now keeps the GPS navigational compass up for one minute, but if I don't pay attention and continuously touch the screen, it will go to sleep after a minute. What sort of GPS navigation is that? It did not happen in the Classic app, nor in Google maps, c:geo or any other GPS based navigation system I've used. This is a necessary feature of the game...navigating to the cache, which also goes along with Item 3 in your list. How can you navigate to a cache when the GPS constantly gets stuck at a certain distance and won't budge no matter how far you travel? I am so dreading March 23rd when I can no longer jump over to Classic to do what I should be able to do in the new app.

Really? My app is up to date and it is not there. Just one of the many reasons why I am going back to C:Geo. It works and has all the features I want and need. It is not in the section with the other log types (Found, Did Not Find, Write Note), which makes no sense at all. After all, you are still making a log for Needs Maintenance or Needs Archiving. In order to log a NM or NA log, open the cache that needs the log, click on the three dots in the upper right and select, Report a Problem.

#2 - Yeah - that's bad. Never seen a navigation app that doesn't keep your phone up. What if you've got it mounted on your bike's handlebars? #3 - Actually, I like this. I open lots of caches from the map. Doesn't mean I'm going after them. I like being able to read them, look at logs, then decide. I don't want to kick off the navigation portion of the program until I WANT to. #5 - In a previous thread, I posted my experience with this. Don't remember if I ended up being correct, but here's a thread link. See post #17. ClickMe Thank you for all your feedback. Very helpful! The blanking out screen really is irksome and cannot understand why the developers did not think to work that into the app. It's most necessary! #3- Can live with, just noting it's an extra step from Classic and #5, will just have to use geocaching.com to manage travel bugs until they get that fixed.

Don't expect to see this in a modern app. Unlike previous phones or GPS receivers, modern cell phones have alternate ways of calibrating the on-board compass. If an app developer puts this function into his or her app, the app is bigger, and they run the risk of finding phones where the procedure is different. Think of it like Windows programs. When you click "Save", the "Save" dialog box isn't part of the program you're running. Your program asks Windows for the current "Save" dialog box - that's why they all look the same. Android has no such API call for compass calibration, so you have to do it manually. There are two normal procedures: Pointing the phone away from you, move your hand from side to side in a figure-eight pattern (up, circle down to the right, cross up to the left, circle down to the left, up to the right, etc.) Repeat this four or five times. Point your phone away from you. Turn it over three times around each of its three axes. This means flip it over 360 degrees sideways three times, then flip over forward 360 degrees three times, then spin it flat facing up 360 degrees three times. When my compass goes squonky, I do both of these things. Makes me look like an idiot, but both methods work. Thanks for this information. Did not know that you could do this without a calibration button as was available in the Classic app. So, to do this, you don't have to be in the app?

We got the notices about the new app months ago like everyone else and tried it right away, but couldn't even navigate to a cache. Every cache, no matter how far, said it was 1.2 miles away. Decided at that point not to use it and went back to the almost perfect Geocaching Classic app and never looked back. Until a few days ago that is, when we started getting an annoying message that the Classic app would be retiring on March 27th of this year. This annoying problem occurred right in the middle of a geocaching trip to southwestern Georgia where cell service was almost nil. Had created an offline map in Classic to use, but decided to try to use the new app to get acclimated in areas where we had service. Many unrepeatable expletives later, we were ready to throw the Android out the window! We overshot many caches as the navigational compass hung repeatedly and gets stuck on a certain number and won't budge no matter how far you travel! Get out of the car and the compass says its 102 feet to the cache...walk 75 feet and the compass still reads 102 feet to the cache! Fortunately, I still had my offline list on Classic and we were able to find the caches using the "old" app. Here are a few of the problems (in no particular order) that we experienced over the last several days trying our best to learn the new app and trying to love it, but failing miserably: 1. No way to calibrate the compass in the new app. The classic app had the ability to calibrate the compass when the arrow refuses to point in the right direction. 2. While navigating to a cache, the phone constantly blacks out and have to unlock the screen again to continue navigating. The Classic app stayed on as long as you were navigating without blacking out the screen. 3. Having to click "Start" to navigate to a cache seems counter-intuitive. On the Classic app, after clicking on the cache from the map, you could just select Navigate from that screen. In the new app, you click to open the cache, then have to click start, and then click on the compass icon to navigate. That's an additional step. 4. The very loud and obnoxious message that comes up when you get near each geocache is annoying and so unnecessary. Why isn't there a setting that we can use to turn that off? 5. Difficult to log or visit travel bugs in caches. The classic app wasn't perfect in that aspect, but at least all the travel bugs in your inventory appeared all together on one screen and you could choose to drop off or visit all or any of them. Also, noticed that travel bugs we have dropped off weeks ago and logged into caches still appear in our inventory on the new app, even though Classic and geocaching.com show they are gone from our inventory. 6. No way to log a Needs Maintenance or Needs Archived log in the new app. We had this choice in Classic, why isn't it in the new app? The items above are what we observed over a couple of days of trying our best to use this app. There are other things that bug us about it, but we will probably get used to over time. We want to love it and hope that the developers listen to us and tweak it so that it is at least as functional as Classic. If not, why the change just for the sake of change?

The February 8th release added the ability to log "Needs Maintenance" or "Needs Archived" from the App. How do you get the February 8th release? I uninstalled and reinstalled the app just now and there is still no choice to log a Needs Maintenance or Needs Archived. Frustrated with this app!

Not sure if it was just a glitch, but was just able to click All Visited on my trackable inventory and then was able to Submit successfully.

I've been trying to log caches from yesterday and can now finally do it after the fix last night; however, another issue noted is that when clicking All Visited on the trackable inventory before submitting a log and then trying to click Submit, nothing happens. I can submit the log if I don't click the button for All Visited.

Well, spoke too soon! It worked long enough for me to read logs on Rock Town, then when I tried to pull up the cache listing page for Iron Horse, got the weird page display again. Aaargh! Maybe they'll get it fixed for good soon!

Figures! This had been going on since last night, but shortly after posting, the web pages started displaying correctly.