Explaining all details of Geocaching would be a little to much here. However there are some facts you need to know to start Geocaching with c:geo:
You need an account on a geocaching platform to use it in c:geo:
Choose the platform you would like to use, go to the website and create an account (basic accounts are usually free of charge).
After you retrieved a username and password for one of the platforms, enter them in c:geo settings to allow c:geo to login to the server.
You have to learn about the different cache types, D/T-ratings, etc.
You might not be successful finding a cache by just selecting a random one in c:geo and navigating to it. There is a lot more which you need to know in order to pick a cache which is suitable for you.
Most of the mentioned platforms offer detailed tutorials about how Geocaching works. We strongly suggest, that you read through these tutorials to learn what you need to know to find your first cache and how to log it.
Especially you should be aware of the different types of caches (You will typically not find a mystery cache at the given coordinates) and the T-rating (a rating of 5 means, that you need to climb/swim/dive to get the cache).
Find a cache near you and try it:
Use the “Live Map” or the “Nearby” function of c:geo to see which caches are around you. Pick a cache (a traditional cache with a low D/T rating will be a good starting point) which you would like to find and go for it!
Once again: You should make yourself familiar with the different types, terrain ratings, attributes, etc. before starting out to find a cache.
When you start c:geo the first time it will directly take you to the service settings where you can enter your username and password for the desired caching platforms.
To access the service menu manually from the c:geo main screen please select:
Menu → Settings → Services
After you entered your username and password there, all you have to do is pressing the back key on your device until you reach the c:geo main menu. On the next start c:geo will automatically take you there.
When you are at the main menu, most functions should be self explanatory. Otherwise you might also find some hints in this FAQ.
If you managed to see caches on the map or in the nearby list, select a cache and open its details.
Read the listing text and pay attention to the D/T-ratings and attributes to learn more about how to log this cache.
If you are good to go, press the “Navigate” icon (Pointing arrow) in the title bar.
You will have several options depending on your needs. Here is a brief description of the most important navigation methods:
It will constantly show you distance and direction to the cache.
If you installed an app supporting radar functions this will open a radar screen. It is similar to the compass, but the working mode is a little different. You will typically see the cache coordinates as a marker on the radar. If the marker reaches the center, you reached the cache coordinates.
Navigation (Drive, Walk, Cycle):
This will start turn-by-turn navigation using Google Maps
When you reach the coordinates, remember that GPS has an accuracy of several meters/feet only (also depending on your phones GPS performance). So you should look around your position as well to find the cache.
c:geo is only using the login details you specified on the geocaching website.
You have to go to the geocaching website to reset your password. After you successfully restored your password there, please go to c:geo settings and enter the new login data.
First of all please check carefully whether you entered the correct username and password.
You can find this in:
Menu → Settings → Services Afterwards select “Check Login” (for geocaching.com users only) to see if login is either now possible or what error is returned.
If you have double-checked your credentials and still get an error message (e.g. Login failed, Unknown Error) the following might be helpful:
Please check that your phone is working with the correct date and time. If the date is wrong this might lead to problems establishing a secure connection to the server.
Sometimes network providers insert messages into the HTML-traffic which prevents c:geo from logging in while on mobile network. A clear indication for this problem is, that c:geo only works on your WiFi connection at home but not while on a mobile network. In this case please go to the c:geo settings Menu → Settings → Services and enable “Identify as Android Browser”. Afterwards you might have to restart your phone to be sure these settings take effect.
There have been reports, that in rare cases the login still fails although the login data is OK and also “Identify as Android browser” did not help. In this case we recommend resetting c:geo to factory defaults as described here:
If the problem still persists, please contact our support and provide a system log.
This procedure will delete all stored caches and app settings!
c:geo uses metric units by default but should detect automatically if your phones default is set to imperial units.
You can also manually select your preference in c:geo settings:
c:geo Menu → Settings → Appearance → “Use Imperial units”
In order to minimize the network traffic c:geo downloads caches only once and stores them temporary or permanently (if you save them on your list).
So if you miss some information (e.g. newest logs are missing, description has changed,etc.) please refresh the stored cache by selecting “Refresh” on the cache detail page.
In case you are not logged in the geocaching website does not provide correct coordinates. So it seems you did not provide login data or the login data you provided is not correct.
Please refer to Getting started to learn how to login with c:geo.
The initial idea of c:geo is to provide a free (and open source) app for mobile geocaching for everybody.
What would change with the API?
There are also problems with the development:
While Groundspeak’s API would fix most of our current problems, c:geo would then force users to pay money to a corporation. This is not the open-source spirit. If Groundspeak says OK to our ideas then c:geo might have an API some day…
c:geo is accessing the geocaching website as a customized internet browser.
In order to retrieve the information from the website it needs to have reliable information. Therefore c:geo will change the language to English when logging in, because it cannot support all different languages.
Feel free to change the language on the website back to your desired language anytime when using it. c:geo will detect this and automatically switch back to English on the next login.
The address information shown at the bottom of the main screen is an information we receive from a geocoding database based on your position. Sometimes this database has no address information for your location or the service is not running. In this case ‘Unknown Location’ or even a wrong city could be shown.
This does not have any impact on the c:geo functionality. As long as you have a GPS fix everything will work normal.
If you want you can also disable the address information in c:geo settings so your coordinates are shown on the main screen instead of the address information:
Menu → Settings → Appearance → “Show Address”
c:geo supports geocoordinate notations in the following formats:
Degrees and decimal minutes (MinDec)
Notation: DDD° MM.MMM’ Example: N 51° 20.382 E 007° 01.820
Degrees, decimal minutes and seconds (DMS)
Notation: DDD° MM’ SS.SSS” Example: N 51° 20’ 22.920” E 007° 01’ 49.200”
Only degrees (DegDec)
Notation: DDD.DDDDD° Example: 51.339700° 7.030333°
Format 1 is commonly used for Geocaching and thus also the default notation used in c:geo.
You can change to the other formats by short tap on coordinates shown for caches and waypoints. When entering coordinates in c:geo (e.g. creating a waypoint) you can select the desired format in the headline of the dialog according to the notations listed above.
The conversion from and to UTM notation is currently not supported by c:geo. In case you need to convert coordinates to UTM you can copy the cache coordinates by long tap on them to perform conversion in another app.
If you select to take a new picture it will be saved to a directory which follows a system default.
On most devices it can be found in a directory “/sdcard/Picures/cgeo”.
No, this is not possible and we do not have plans to implement this on short term. Please use the geocaching website to edit your log after you posted it.
There are two things we are storing on your device:
The geocache database containing basically the content of your lists
The database is stored in an internal folder on your device (not accessible without root access). Typically this database will only have a size of some megabyte. For the database you can choose in the c:geo settings whether it is stored internally or on the SD card.
The additional data (e.g. images, maps) for all the caches stored in the database
This additional data can be much larger as it contains the images of the cache description and (optionally) the images retrieved from logs and (optionally) static maps. The additional data is stored on SD card by default (in a folder called “.cgeo”).
Some users are complaining, that the additional data as well as the database (if external storage is selected) are still stored in the internal memory of their devices. We always place the folder on the storage medium that the device tells us is the sdcard. And in fact, technically this is on some devices only a part of the internal memory which is mounted as a SD card (It’s like a SD card fixed mounted in your device).
Unfortunately there is no standardized method to find the location of a real SD card on your device. There are some workarounds but those might fail on some devices, thus we decided not to implement them for now. Furthermore starting with Android 4.4 write access to the real SD card is forbidden for apps.
No, the login via Facebook is an option on the geocaching website only. In order to login to geocaching.com via c:geo you need to enter the username and password dedicated to the website.
In case you currently only use Facebook to login to geocaching.com, you have to go to the Password Reset Page to set up a regular password first. After you got this password you can use it together with your username to log in with c:geo.
No, currently c:geo does only support Twitter as a social network. As the development team has limited resources and is focusing on new geocaching features we currently do not have plans to implement a Facebook connection.
However if you are Twitter user already and/or you are looking for a way to post your findings to Facebook, please note that there is a possibility to link Twitter to Facebook. Doing so all your tweets will also be posted on Facebook (including the c:geo tweets).
You can find more info on the Twitter support website.
As current smartphones can produce high res pictures with a size of several MB the upload of those can take some minutes (depending on the connection speed) if you do not select to scale them.
Please consider using the c:geo scaling function to scale down the resolution before submitting the log.
We are using a crowd sourced translation platform to improve the translation and even include new languages. If you see untranslated (i.e. English) or wrong strings or your language is not even supported, you are invited to contribute on this platform!
Especially on geocaching.com it may happen that log texts are interpreted as HTML code although they are not written in HTML.
If you e.g. include a “<” or “>” sign in your log, it may appear truncated or bad formatted later. This does not only affect c:geo but also if you write this kind of log directly on the website. Reason for this is a bad implementation for HTML detection on the website, but no fault in c:geo.
You need either to avoid such special characters in your log or use HTML-formatted logs to work around this problem.
c:geo scans the whole SD card if it cannot find gpx files in the predefined folder. If you have a lot of files and folders on your SD card this scanning might take some time.
It is useful to put all of your PQs into a specific folder and set this as the default import directory for gpx imports. This folder will be scanned first which will speed up the process.
You can specify the GPX import and export folders in the settings of c:geo:
Menu → Settings → System → “GPX Export Directory” / “GPX Import Directory”
If the app is not working as it should you can send a log to the developers.
When c:geo crashes or does not work properly it writes debug messages to an Android log if this option is set in c:geo settings. This log contains data of all apps for a short period of time (from several seconds to several minutes). Collecting a log as fast as possible after the crash is essential for us.
Please note that your device needs to have an Android version below 4.1 to get a proper system log. On higher Android versions Google disabled the logging ability for security reasons except your device is rooted.
Please find a detailed description of how to get a log in our GitHub Wiki.
Publishing a new cache with c:geo is not possible and there are no plans to implement this function. However you can still use c:geo to record waypoints to help you planning your cache hide. To do so simply use the ‘All destination’ function which offers a history of the coordinates you entered.
In order to e.g. beta-test an unpublished cache you will not be able to access the cache online (because it is unpublished) but you can import the cache via GPX or add the cache waypoints manually to another cache already stored on your device. Furthermore you can view your own unpublished caches with c:geo by searching for its geocode online.
If you select the menu icon to send your log and you get a message saying “Loading Log-Page” the log page on the server was not yet loaded. Check if you have an internet connection and wait a moment until the required data has been loaded and then try again to send your log.
In case you cannot establish an internet connection or the geocaching server is down you can also select to just save the log on your device and send it later by reaccessing the log page. To do this just press back on your device, the log will automatically be saved.
You can also batch submit offline stored logs as fieldnotes to the geocaching website at a later point of time.
On geocaching.com some caches are accessible for Premium Members only. If you are a Basic Member you will still see them in your search results and on the live map but can’t open them. Sadly it is not possible to hide them by default due to server limitations.
The only possibility is to hide them in your lists and search results by applying a local filter in c:geo:
Menu → Filter → Status → “All member access”
If you look at a list of caches (a search result or caches saved on your device) the right side contains some symbols, colors and numbers. Here is a brief explanation of their meaning:
Color in the lower half:
The color represents the average GCVote rating for this cache, where green means good (>3,5 stars),brown means average (between 2,5 and 3,5) and red means a rather bad rating (<2,5 stars). If there is no color shown the cache does not have any votes yet or is not supported in GCVote (GCVote does curerntly only support geocaching.com caches).
Number in the lower half:
The number in this field represents the amount of favorite points of geocaching.com or referrals for opencaching.x given to that cache by users.
Symbol with number in the upper half:
The symbol is a marker which is only shown if the cache contains trackables. The number right next to it is the amount of trackables listed in this cache.
There can be several reasons that c:geo is not working as it should. You should do the following steps:
First of all please check if you are using the latest version (check on Google Play for updates or load the latest version directly from here). If a new version is available you should also see an update notification on the c:geo main screen. If you are using an outdated version please update, because there might be changes on the geocaching website which need a new version of c:geo to work.
Please check if your device is connected to the internet and also try other connections (e.g. Wifi instead of mobile network or vice versa). If c:geo works on another connection there seems to be a problem with your network.
Go to c:geo settings (Menu → Settings → Services) and check your login. If it fails please make sure you are using the correct login credentials. Those are the same you use for the geocaching website.
Check if there are any notifications about problems shown on the c:geo main screen and check our Facebook page to see if others also have a problem and/or we reported a known problem there.
If your problem is still not solved, please contact us and provide a detailed description of your problem and what you tried already to solve it. We will answer as soon as possible.
Besides geocaching.com c:geo is also supporting opencaching platforms for several countries. If you activate the opencaching service in the c:geo settings the nearby search will also provide you the nearest opencaching caches.
if you however accidentally activate an opencaching platform of a foreign country (e.g. you are living in Germany and have activated “opencaching.org.uk”) you will see caches some hundred kilometers away in the nearby list as those are the nearest caches on this platform.
In this case please deactivate the unneeded opencaching platforms in:
Menu → Settings → Services → “Opencaching.xx”.
If you are Basic Member of geocaching.com and try to navigate to a cache directly from a search result, you might see this error message.
If you are no Premium member the geocaching server does not provide coordinates in searches but only an estimation of the distance to the caches and “directional images”. c:geo uses and shows this distance estimation and the “directional images” in the search results. The caches are still sorted by distance, but be aware that the distance shown is the one based on your location when you performed that search. It will not change if your position changes.
Additionally you will not be able to show a map of those results or directly navigate to a cache as c:geo does not have the coordinates for these caches.
To get exact coordinates as a basic member you have to do one of the following:
Open the details or save the geocache to your device. This will request the exact coordinates.
Enable the CAPTCHA in the c:geo settings if desired (Menu → Settings → Services → geocaching.com → Basic member options). After entering the CAPTCHA c:geo will have the coordinates and proper sorting by distance, showing on map and navigating is possible.
If you are premium member and c:geo does not know the location of a cache, please check your login and relogin to make sure c:geo knows you are a premium member.
If you are running the legacy version of c:geo (only for Android version below 2.3) we have some limitations regarding the supported date formats of geocaching.com. In all other versions of c:geo all possible date formats are supported.
If you are on an Android version above 2.2 and notice incorrect dates please update to the newest version of c:geo and refresh the affected caches.
The following explanation is only applicable to the legacy version of c:geo:
With the legacy version the following formats are supported:
dd MMM yy
(dd = day, MM = month, yyyy/yy = year)
The format can be changed on the geocaching websites user preferences page.
Maybe you notice that one format is missing: dd/MM/yyyy
The reason for this is quite simple:
Is 04/10/2011 the 4th of October or 10th of April? So we would have to guess which would lead to inconsistency. Since MM/dd/yyyy is the default at the geocaching website we are supporting this. No problems have ever been reported with MM/dd/yyyy. If you have problems please change the date format to this on the website and refresh the caches showing wrong dates.
There are some reasons why installing c:geo from Google Play might not be possible.
c:geo is shown as “Not supported” for your device:
This means that either your device is running on an Android version below 2.1 or it does not support GPS.
Android versions below 2.1 are no longer supported by c:geo.
If you are on a Android version above 2.1 but your device has no GPS and you still want to install c:geo on it, you have to install c:geo manually by downloading the APK file here. But be aware, that you cannot navigate to caches without GPS!
You cannot find c:geo on Google Play:
That is probably a wrong setting in your Google Play settings. It has a content filtering with a rating that has four different levels, where “All” is the level which can be shown to all users. c:geo however is not on that level, because Google requires apps with position tracking to be level “Low”.
To be able to install the app, you must either choose “Low” (pre teen) or set the option “Install all apps” (which looks exactly like the “All” level, but has a completely different meaning).
We decided to drop the support of Android versions below 2.3. Only a very minor percentage of our users are affected.
The reason for this is, that we want to include more features and further improve usability and stability. Newer Android versions offer a lot more possibilities which we simply can not use if we have to be compatible to e.g. Android 1.6.
Please check if the manufacturer of your device offers an update for your device. If there is no official update it may also be possible to use a Custom-ROM (like Cyanogenmod) if it is available for your device. If nothing can be done to update your device you should consider using a new(er) device running on Android version 2.3 or above.
Additionally we offer a legacy version of c:geo, which is compatible for devices with Android versions 2.1 and 2.2 for the time being. This version will not be updated with new features anymore, critical bugfixes might be done if considered necessary. We might discontinue this version in the near future without any further notice. The PlayStore will automatically offer the matching version for you to download and install.
c:geo needs the following permissions to do its job and will only use them for that purpose:
Of course c:geo needs access to the GPS on your device to locate your position and calculate distance and direction to geocaches.
c:geo will write data onto your phone storage or SD card as soon as you save geocaches for offline use. Furthermore c:geo will use your phone storage for import and export of files and reading of offline maps.
Generally we do not recommend to install an outdated version of c:geo, because it might no longer work as expected as newer versions often include adaptions to changed functions of the geocaching platforms. So we strongly recommend not to go back but to apply all updates as soon as they are available.
We cannot guarantee that older versions will still work!
If you however still want to install an old version (e.g. for testing purposes) you can find a version history with download option in our GitHub Release History. Please be aware that you need to uninstall a newer version of c:geo on your device before installing an older version as downgrading is not possible.
Some users complain that on clicking the notification for a new version on the c:geo main screen Google Play opens but shows no available updates.
Google Play may need several hours to roll out the update in all countries. Trying again some hours later should solve the problem. If the update is still not shown it will help to restart your device to force the Google Play app to synchronize with the server and detect the new version.
If you you still have problems to load the update from Google Play we suggest to download the update as described here: I don’t use the Google Play but still want to use c:geo!
You can download the newest version of c:geo directly to your device from here.
No, c:geo is written for Android and has more than 50 000 lines of code. We will not port it to iOS or other non Android systems because it is too much work. Furthermore the iOS AppStore / Apple is very restrictive and most of us don’t like it.
But c:geo is open source! That means that everyone can get the code from GitHub and rewrite it for other operating systems. Feel free to port (and maintain) it, but be aware of the open source license terms.
Although there is no native c:geo app for Blackberry OS you can still run c:geo on it. The current version of Blackberry OS supports sideloading of Android applications.
Just download the Android APK file here and install it to your Blackberry phone. Instructions about sideloading Android applications can be found in the internet. But please be aware, that we cannot give a guarantee that all features are working and can’t provide support in case of problems.
Sometimes users are asking us how to clone the content in their c:geo installation from one device to another (e.g. in case they got a new device).
Here is a basic instruction for you:
What you need to do this:
On the old device:
On the new device:
If you did everything right, now the content of c:geo on the new device should look like on the old device. This includes all caches on your lists with all its contained information (like waypoints, notes, offline logs, etc.) and - if you did the optional step - also all images on the image tab and static maps.
Android has different mechanisms to provide location information to apps:
You should make sure to enable both of these sources to get the best possible location information in c:geo in every situation. This can usually be done in your device settings (not in c:geo itself) in a menu called “Locations” or similar. Please select all possible sources in that menu or (in newer Android versions) select the “High accuracy mode”.
Furthermore you should check if your device supports “Google Play Services” and eventually enable the usage of that in c:geo:
Menu → Settings → System → “Use Google Play Services”
While you are using c:geo GPS should always be active except if you are in the settings menu. Only if you put your device to standby (switch off the screen) or switch to another app GPS will be deactivated to save battery.
We have no plans to change this behaviour or introduce another setting for this. If you whish to keep GPS always on, we recommend to use a dedicated app for this (e.g. GPS Lock).
Some users complained that their device needs a long time to reobtain a GPS fix after it was switched off. So we decided to keep GPS active while c:geo is being used (except in the settings menu).
To save more battery you can you select Menu → Settings → System → “Activate low-power mode”. c:geo will then use high precise location (GPS) only if needed. This means, that e.g. on cache lists, cache descriptions, trackable screens GPS might be switched off or only used periodically.
In 99% of these cases the problem is your device. c:geo only uses the position and compass information provided by the Android system.
Please first of all try to calibrate the compass sensors of your device. On most devices this can be done by turning the devices around all of its axis three times or moving it horizontally in shape of the number 8 until the compass shows the right magnetic direction. Please be aware that electric field (such as high voltage lines near to you) might influence the device sensors.
If the problem is still not solved you should try another app with compass functionality (e.g. GPS Status & Toolbox) to verify your device capabilities. If another app has the same problems you can be sure, that the problem is on your device.
If nothing helps and the problem persists, please contact us and provide detailed information about your device and the compass misbehaviour.
The “Radar” function works together with the third party app called “GPS Status & Toolbox” available on Google Play.
Once you installed the app c:geo will additionally offer “Radar” as a navigation option.
Paris/France is the default location if c:geo is unable to get any location information on your device, no home coordinates are set on geocaching.com and c:geo never before had any information about your position since start of your phone.
Please make sure all location sources are activated in your device settings. Please check this FAQ entry for more information.
If you had a GPS fix at least once while c:geo is running it should remember this as your last position and open the live map at this position. Additionally you can set your home coordinates on this page on geocaching.com. c:geo will then use these coordinates if no other location information is available.
Please first of all check if you enabled all relevant positioning methods on your system as described in this FAQ entry.
We received reports, that on some devices the “Google Play Services” might be faulty. If all location methods are enabled but you still have problems, please try to switch off the usage of “Google Play Services” in Menu → Settings → System → “Use Google Play Services”.
In order to provide more info about the status of a cache c:geo provides several markers which are shown together with the cache icon on the live map.
Below you will find a short description of them:
Pen icon: Personal note available for this cache
Flagpost icon: Cache is shown at modified coordinates
Disk icon: Cache is saved on device
Yellow Smiley: You already found this cache
Red Smiley: An offline log is stored in c:geo for this cache
Yellow star: This is your own cache
It is normal that you sometimes see some ??-caches on the map.
The ?? means that c:geo was not able to identify the type of this cache. This mostly happens if too many caches are displayed at once (i.e. your zoom level is very low or the cache density is very high). If you reduce the amount of caches shown (by zooming in) or if you click on a specific cache you will get the info about the cache type.
If all caches are shown as ?? you probably changed the live map loading strategy to “Fastest”. With this setting the cache types are not requested to speed up live map loading.
You have to change it back to another mode to see the cache types. This can be done in
Live Map → Menu → Strategy
Caches with orange circles mean that c:geo does only have a graphical approximation of the cache coordinates. The accuracy of the cache position on the map depends on the zoom level and maybe some meters/feet off. The closer you zoom in the more precise the cache position will get.
To retrieve precise coordinates for the map you can also open the cache details once or store the cache for offline. In these cases the orange circle will disappear indicating that the coordinates are precise.
You can influence the accuracy of the live map by selecting an appropriate live map loading strategy in
Live Map → Menu → Strategy
Depending on your requirements the live map offers four different strategies. Some are focused on fast loading, some on accuracy of cache positions and information.
You can select the strategy in
Live Map → Menu → Strategy
This is the meaning of the different options:
Load approximated cache coordinates only and don’t identify the cache type
Same as fastest but try to identify the cache type
Same as fast but load details for 20 caches around your position
Automatic switch from “Detailed” to “Fast” at 30km/h (This is the default setting)
For getting most accurate information you should select “Detailed”, for a fast loading and less priority on detailed information you should select “Fastest” or “Fast”.
The “fast” strategy will only identify “Traditional”, “Multi”, “Mystery” and “Event” caches. Other cache types will be shown as ??-caches.
On some devices there seems to be a problem for c:geo to initially detect whether Google Maps is installed on them. This leads to the problem, that only OSM maps are offered on the live map at the first start of c:geo after installing it.
If this happens to you, please force stop c:geo or reboot your phone and start c:geo again. Then open the live map, click the layer icon and select Google Maps. After doing this once, usually Google Maps will stay available.
Although you activated the option to hide your owned/found caches in c:geo there are some situations where some of them might still be shown on the live map. This is the same as in the live map on the geocaching website: If you zoom out to a huge area own/found caches will no longer be hidden.
Please zoom in to allow c:geo to detect own/found and hide them.
In rare cases starting the (live) map freezes or crashes c:geo permanently. This is a rare problem we were not yet able to debug.
If this happens to you please send us a log (as described in this FAQ).
To get around this problem start c:geo, go to
Menu → Settings → Map → “Select Map Source”
and change the map to OSM:Mapnik.
Now start the live map, it should work. After the live map is started you can switch back to Google Maps if desired.
Yes, there is an easy way to do this without the need to zoom/scroll around:
Perform a search for the desired address/region. Once the results are displayed, click on the map icon in the upper right. You will get the map for the location already containing the caches from your search.
You can now use Menu → “Enable live” to activate the live map function.
Please make sure that live mode is enabled. You might have accidentally disabled it:
Live Map → Menu → Enable live
You can see whether live is enabled or not by looking at the headline:
“Map” means live mode is disabled, “Live Map” means live mode is enabled
If still no caches are loaded please make sure you are logged in correctly.
Send to c:geo is a quicker way to transfer a cache opened in your browser to your c:geo. You will find all relevant information for installation and usage here: send2cgeo
If the registration fails the reason can be one of the following:
You should try again in a couple of minutes/hours and if the problem persists please contact our support.
Yes, multiple devices can be on multiple browsers.
You need to “Register the device” for every browser. The PIN can only be used once. Afterwards you can send caches to c:geo from each of the registered browsers and they will be retrieved on all registered devices on which the import is currently active.
If this appears to you while using Google Chrome please check your cookie settings. It might be required to allow third party cookies for send2cgeo.
Look into your geocaching.com browser tab. If there is a cookie symbol with a red X at the end of the URL dialog, click on it, and in the popup click “Maintain cookie blocking” (or similar) and permit [*.]send2.cgeo.org.
OSM:Offline maps offer you the possibility to use all the map functionality of c:geo even when your device is not connected to the internet. This can be useful e.g. in case of roaming to avoid expensive data transfer or when you are in regions without or with slow network connection. We have implemented a support of mapsforge maps, which uses vector maps based on open street maps data.
In combination with caches already stored in c:geo (manually or via GPX import) and the possibility for offline logging (e.g. for later fieldnote export) you will get a full offline solution for caching.
Once you downloaded or created a map, store it into a folder (e.g. /mfmaps) on your device or SD card. You can also store multiple maps (e.g. for several countries) into this folder to have easy access later directly from c:geo. If you are additionally using Locus it is useful to store the maps in /Locus/mapsVector to have them accessible for Locus as well as for c:geo.
Afterwards go to c:geo Menu → Settings → Map and select the section “Directory with offline maps”. It will automatically scan for maps on your phone memory and offer you the results.
If either no results are returned or your map file is not listed you can select “Choose directory” on the top to use a dir chooser to select the correct path manually.
In order for c:geo to use the selected map you have to choose one of the offline maps (it will list all the map files found in the given directory) in the dropdown menu “Select Map Source” located above the directory settings. You can change this setting also directly from live map. If you now access any map functionality (live map, cache map,etc.) the offline file will be used.
You can quickly switch between different offline maps or switch back to online maps by clicking the layer icon in the titlebar while on a map.
Yes, the mapsforge library we are currently using has some problems which we know of:
c:geo supports offline maps from mapsforge in version 0.3.0.
Many OSM:Offline maps are already pre made on the mapsforge download site. Almost all countries are available for download and will be updated frequently.
Additionally openandromaps.org also offers free, compatible offline maps for many countries and regions. These maps are even including some custom map themes suitable for hiking or cycling (including the display of height lines/isohypses).
If you would like to create your own map please read these instructions.
c:geo is supporting custom rendering themes for OSM:Offline maps. These can be used to change the color style of the map (e.g. to have a night-view map) or to highlight certain objects within the map (e.g. cycle paths or height lines).
Up to now we do not have build-in themes but you need to create them by yourself or download some user made themes from the internet. Try e.g. searching the net for “RGB Night Theme for Vectormaps” to find appropriate nightview themes.
If you have created a personal version of a theme which you are willing to share with us, feel free to contact us.
After having downloaded a theme-package (usually a ZIP-file containing a lot of xml files and graphics) extract it including all its sub-directories into a folder in your device or SD card.
Afterwards select this folder as base-folder for map themes in c:geo settings.
If you have done it right and the theme is valid it should now be selectable from live map via
Live map menu → Map modes → Select map theme
The main purpose of c:geo is to have an online access to your geocaching platform. However c:geo also provides offline functionality to use it without any network connection (e.g. while caching abroad).
In order to use c:geo completely offline you will have to prepare some things depending on your needs:
In case you want to avoid any data transfer you should generally disable the internet connection on your device anyhow, because c:geo will always try to login once you started it. On most devices the internet connection is disconnected automatically in roaming conditions or if the mobile part is switched off.
To allow offline logging of caches please go to
c:geo Menu → Settings → Logging
and enable “Offline Logging”.
Afterwards c:geo will not post logs online but only store the found status offline. You can then at a later point either upload the logs via field note export or reaccess the log page and submit them online while having an internet connection.
Fieldnotes are supported by geocaching.com and allow an offline logging of cache finds and batch uploading them to the website. c:geo is supporting fieldnote export and also an automatic upload to the website.
If you save your cache logs offline in c:geo (e.g. when caching abroad) you have the possibility to export these logs as fieldnote instead of logging them online.
The offline logged caches are marked by an orange line in your lists. To export the logs you have to open the relevant list of saved caches or the history and select
Menu → Manage → Export → Fieldnotes.
From there you can either only export the fieldnote file to your device or additionally upload them to the geocaching website. The option ‘Since last export’ will check the last upload date on geocaching.com and only export those which are composed after this date.
After you exported your fieldnotes to the geocaching website, the website will show that you have pending fieldnotes on this page and you can compose your logs in your browser. Please be aware that it might take a minute after the upload until the website shows the pending fieldnotes.
c:geo optionally downloads Google Maps snapshots of the area around the cache and its waypoints for offline usage while storing a cache. It will download satellite views as well as map views on different zoom levels. So you will have a map function also in case you don’t have an internet connection and you don’t use an OSM:Offline map.
You have to enable this function in
c:geo Menu → Settings → Offline data
for the cache position itself and (if needed) also for the additional waypoints of a cache.
To access the static maps of a cache later on please select Menu → Navigate → Static Maps from the cache details.
Google limits the download of static maps to 1000 requests per day for a single user. So if you batch download or refresh a lot of caches this limit can be reached easily (because for each cache at least five maps are loaded and optionally even more if you enabled the download also for waypoints of a cache).
If the limit is reached you will have to wait for the next day to get more static maps. c:geo will automatically refresh those caches without a static map first. You can also consider to switch off static map loading for additional waypoints to limit the amount of maps which are downloaded.
This is not (yet) possible.
While we are against mass logging of caches still batch sending offline stored logs might be meaningful as this is another usecase. Therefore we are thinking about implementing this but we encourage you to use the existing field note submission for the time being.
Yes, c:geo supports Opencaching platforms in several countries already and we are also planning to add more platforms once they provide an OKAPI interface.
c:geo Menu → Settings → Services
to see which platforms are already supported. Whithin the seperate platform settings you also have the possibility to see which features are supported for the specific platform.
To use these you need to have an account on the opencaching website. With this account data you can activate the platform in c:geo and authorize yourself to the opencaching website with your login credentials.
Afterwards opencaching caches will be shown on the live map,in nearby searches and you can post logs online.
If this is happening to you, please check that your device has the correct date, time and timezone information. For security reasons the Opencaching API will reject requests which are not matching the server time (+- 5 minutes).
On some devices the internet browser does not correctly redirect back to c:geo after you logged in on the opencaching website but tries to open a website like “callback://www.cgeo.org[…]”. This is a faulty behavior of the internet browser you are using, please try another internet browser application to perform the authorization.
Trackable inventory of a geocache:
If you open the details of a cache its trackable inventory will be listed on the tab “Inventory”. This inventory contains a maximum of 20 trackable items listed to be located in this cache. If this tab is not shown the cache either does currently not contain any trackables or you may need to refresh the cache to view the current inventory. Selecting an item will show more details and offer the possibility to compose a log for this trackable (i.e. to retrieve it from the cache or discover it).
Managing the trackables in your personal inventory:
When composing an online log for a cache the trackable items which are currently in your personal inventory are listed underneath the log text window. You have the possibility to select the desired action (visit, drop or no action) for each item individually or select a common action for all of them. As soon as you post the log online the corresponding trackable action will be triggered in parallel.
Searching for a trackable to log it:
Additional to the functions explained above, you can also just search for the public code or the secret tracking code (secret code is currently only working for GC trackables) of an item by entering it either into the search bar on top of the main menu (magnifier icon) or into the trackable search field within the search menu. The details of this trackable will then be shown and you can write a log for it.
Although GeoKrets are mainly used on opencaching platforms GeoKrety.org also supports to place GeoKrets into geocaching.com caches.
This also means you can retrieve and drop them from there as well. The only difference is, that you are encouraged to add the cache coordinates to the log if you drop a GeoKret to a GC cache (as GeoKrety.org might not know the coordinates of all GC caches). In case you log a GeoKret from the log window of a GC cache c:geo will even prefill the coordinate field with the listing coordinates of this cache to assist you.
While for reading GeoKrety information no login is required, you need a dedicated account on GeoKrety.org to log these trackables with c:geo.
If you do not yet have an account you can create it on the Geokrety.org registration page. Afterwards go to Settings → Services → GeoKrety.org in c:geo, enter your login data and authorize to the webpage.
Once you are authorized you can log GeoKrets with c:geo as described here.
Some functionalities which are available on the GeoKrety.org webpage are not (yet) supported with c:geo as either the current version of the interface does not support it or we did not yet have time to implement it:
While logging in to the geocaching.com website c:geo will automatically detect whether you are basic or premium member, but c:geo will only perform a login if it is necessary. So after you became a premium member it can happen, that c:geo does not know this yet.
In this case you can force c:geo to login by either selecting Menu → Settings → Services → geocaching.com → Check Login or simply rebooting your phone and starting c:geo again.
If the distance to a cache on a list of caches or on the compass is jumping between some meters to some kilometers and you are using Cyanogenmod ROM, this might be caused by a known bug in Cyanogenmod 10.
Pleasae udpate to a newer version of Cyanogenmod or change to another ROM.
We are using a hardware acceleration modes to speed up c:geo. It seems some devices on some Android versions have problems with that. They may show blurred fonts or no fonts at all.
For some of these known problematic devices we switched this feature off automatically, but you can also do this manually in
Menu → Settings → System → Hardware acceleration
For devices with Android versions <4.2 we deactivate hardware acceleration by default on a new installation. Nevertheless check the setting if you encounter problems.
Our current version has a problem to show the menu bar in map screens (like the live map) on tablet devices running Android 3.x. We are trying to find a solution for this, but it is not that easy to solve.
As Android 3 is quite old and since some years Android 4 is available for tablet devices we also recommend, that you check if an update for your devices is available either from the vendor or by using a Custom ROM.
We are now using Google Play location services if they are installed on your device. This location services is not compatible with external GPS receivers.
You have to disable the usage of those location services in
c:geo Menu → Settings → System
in order to be able to use your external GPS receiver.
After disabling Google Play location services the interworking with Bluetooth GPS receivers should work as it used to in older versions of c:geo.
Several users reported the problem, that the OSM maps (offline and online) are not displayed properly but only incomplete parts of it. Additionally the cache icons are only displayed as a vertical row over the map but not on their real position.
This affects devices using a MediaTek CPU. There is a mathematical error in the compiler for this CPU type causing the problem. You can find more information here: Wrong division on MediaTek CPU
As this is a bug outside of c:geo we cannot fix it. However we created a special version of our nightly builds which works around this problem. You can download it here: c:geo Nightly Build - NOJIT
Please frequently check if your device vendor offers a firmware update which solves this processor problem.
We recently got complaints that users of Xperia device experience regular crashes of c:geo and problems using the compass (compass not rotating). Not only c:geo is affected by this, but also other navgiation specific apps on these devices.
Our investigation has shown, that these problems are caused by the device firmware after upgrade to Android 5.x and not by c:geo itself. Thus we can not fix these problems, but can give you some workarounds based on user feedback we received:
Crashes while using c:geo
Users gave feedback that this issue was fixed after resetting their device to factory defaults and reinstalling c:geo.
Go to c:geo Menu → Settings → System and disable “Google Play Services”. Afterwards reboot your device.
These workarounds should help to avoid the mentioned problems, however a proper fix for this has to come from Sony in another firmware update.
We are now following the Android design guidelines and thus have the same appearance like other modern apps.
This will also solve the problems with devices with physical buttons and no menu button as the menu is now usable without the need for a HW button. Furthermore the new title bar allows a more consistent menu usage throughout the whole app, which will make it easier for you to find all functionalities and will also help us when implementing new features.
Although the new implementation looks a lot different compared to the old menu, there is actually not much difference once you understood the mechanism. The main difference is the title bar which is shown on the top in each screen of c:geo. You might already know similar title bars from other apps, and this one works alike:
All menu functions are now located on that title bar either as an icon or behind the overflow menu (three-dot button) if they do not fit into the window title. If a menu entry appears as an icon or behind the overflow menu is mainly depending on the screen size of your device. So e.g. turning your phone into landscape mode or using a device with higher resolution (tablet) will also change the appearance of the actionbar items.
If you are unsure about the functionality behind an icon you can always long press it to get the description of it.
Clicking the menu button on your device is now the same as clicking the overflow button.
If you use the most current version and still see the old menu your device is probably running on an Android version <2.3. New features and functions will no longer be implemented for these old versions.
Please refer to this FAQ entry for more information.
If your device is running on Android 2.3 the overflow button (three dot button) is not used. You have to use the menu key of your device instead, which will give you the same options like in the overflow menu.
No, we did not remove any feature/functionality and also preserved the existing menu structure as much as possible.
Due to the actionbar style the menu entries are now divided into icons shown on the title bar itself and a list of entries behind the overflow (three dot) menu. So if you miss an entry in the overflow section it will be located as an icon on the title bar instead. If you are unsure about the function of an icon just long click on it to get its description.
In some parts of the app we used the opportunity to rearrange or regroup some menu items to make the sorting more consistent.
We decided to remove this option while implementing the new menus as it may lead to problems changing the destination directly inside the compass.
You should instead use the various other functions c:geo offers for setting new target coordinates:
It allows adding event caches to your personal calendar. As it is a plugin it will only work if also c:geo itself is installed on your device.
When you open an event cache in c:geo select
Menu → Add to Calendar.
A new appointment for the event will be created in your calendar.
Event cache listings on the geocaching website do only contain the date but not the time of an event.
Nevertheless c:geo will scan the event description and try to extract a time from it. In some cases it might be wrong or we are unable to do so. In these cases you have to manually correct the entry.
First of all you should make sure that your device has a calendar app installed and it is working properly. Also if you are asked which calendar app to use when trying to add an event, please make sure you select the correct one.
On some Samsung devices adding events to the calendar will always fail due to an incorrect implementation of this function by Samsung. Please check for a software update of your device in this case.
The c:geo calendar plugin needs the permission to access the calendar on your device to add event geocaches to your personal calendar in case you use the relevant option in c:geo. As long as you don’t use that menu option the plugin will never read or write any data from/to your calendar.
It allows you direct access to your phonebook when clicking on a username in c:geo. As it is a plugin it will only work if also c:geo itself is installed on your device.
When you click on a username in c:geo (e.g. in the cache logbook) the menu will contain an item to open the corresponding contact card in your phone contacts. This will allow you to directly call or message the user.
The username of the person needs to be stored in the ‘name’ or ‘alias’ field of your contacts in order for the plugin to match the geocaching username to the contact.
Please make sure you stored the geocaching name of the person like it is shown in c:geo in the ‘alias’ field of the contact in your phonebook.
Alternatively the plugin will also match if the geocaching name equals the full name stored in your phonebook.
The c:geo contacts plugin needs the permission to access the contacts on your device to look up other geocachers in case you use the relevant option in c:geo. As long as you don’t use that menu option the plugin will never read any data from your contacts.