Application does not work

That is the most common question but we don't know nothing what are you trying to ask.
You should do the following:
- please check if you are using the latest version (check Market or our page). If not please UPDATE!
- Go to settings and check your login. If it fails re-enter your username and password.
- check our Facebook page if others have the same problem
- check issues list on git (opened and closed) to see if we are already avare of problem.
If your problem does not go away, contact us on Facebook or over email. We will answer as soon as possible.

Cache listing is incomplete / logs are missing

C:geo downloads cache only once. Then it stores it in memmory to save 3G traffic. To get most recent data you need to refresh a cache (on cache detail page).

Dates in log are missing

GC.com removed dates from log in Aug 2011. A couple of days after it they put it back. In order to get dates back you need to:

- update c:geo to version 22.08.2011 or newer
- refresh already stored caches.

Nearby is not sorted by distance

When downloading nearby caches and you are not PM (or not logged in) GC.com does not provide coordinates in searches. If c:geo has some coordinates in it's database from previously opened caches those are displayed first and later on caches with no coordinates.
If you are PM, check your login and if you are not PM you can enable chapta in settings.

Caches are off for about 50 feet

You don't have user username and password entered into c:geo. Go to settings and check login.

Wrong dates / No Dates Shown

Currently we support the following formats:

yyyy-MM-dd
yyyy/MM/dd
MM/dd/yyyy
dd/MMM/yyyy
MMM/dd/yyyy
dd MMM yy

(dd = day, MM = month, yyyy/yy = year)
Format can be changed in GC.com 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 4 October or 10 April? So we would have to guess which would lead to inconsistency. Because MM/dd/yyyy is the default at gc.com we're supporting this.

No problems have ever been reported with MM/dd/yyyy. If you have problems in GC.com user preferences set this and refresh caches with wrong dates.

How do I send log to developers

If application if not working as it should you can send us a log. When c:geo crashes or does not work properly c:geo writes to an android log. This log contains data of all app 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.
Here is a description how to do it.

Cannot install c:geo from Market

That's probably a wrong setting in your market. It has a content filtering with a rating that has 4 different levels, where "all" is the level which can be shown to all users. c:geo 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).

Searching for gpx files takes ages

c:geo searches whole SD card if it cannot find folder named "gpx". If you have a lot of files and folders on your SD card create folder gpx and copy all PQs in that folder. Searching will be faster.

Cannot publish log online

If the button for posting a log to geocaching.com is labeled with "Logging not possible", this means that c:geo has not enough data to send the log. Check if you have an internet-connection and wait a moment.

Is c:geo available for the iPhone?

No. c:geo is written for Android and has more than 50 000 lines of code. We won't port it to iOS because it's too much work and the AppStore / Apple is very restrictive and most of us don't like it.

But: c:geo is open source! That means that you can get the code from GitHub and rewrite it for iOS. Feel free to port (and maintain) it, but please keep the open source license in mind.

Why c:geo is not using Groundspeak's public API

Let us answer this once and for all in one place. But let's start with basics.
There is very simple reason why us and GC.com can't sync. We are FREE, opensource application, they are corporation. We give our software for no money, they would like to make a big profit with a service. They don't like what we do, we don't like what they do. It's like fire & water, cat & dog, hell & heaven....
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?

- c:geo only for premium members
- no support for OpenCaching or other platforms than gc.com
- Groundspeak-ads

Also there are problems with development:
- development would take 2-4 months to implement the API
- during this time there would be only access to a testing-server, no nightly-builds
- devs are using the development-build for caching
- the API requires a private key for the app. But c:geo is open-source. There are a lot of independent developers, but only one would get the key - all other developers wouldn't be able to test what they do
- c:geo no longer open-source
- only few core-developers
- much slower development

The Groundspeak's "public" API would fix most of our current problems, however c:geo would then force users to pay money to a corporation. This is not the opensource spirit.
If the Groundspeak says OK to our idea then c:geo might have API some day...

Live map strategies

Live map has 4 strategies

- Fastest: Load approximated cache coords only
- Fast: Same as fastest but try to identify the cache type
- Detailed: Same as fast but load details for 20 caches around your position
- Speed dependent: Automatic switch from detailed to fast at 30kmh

Markers around caches in Live map

There are several markers around caches in Live map

- Personal Note available (Pen icon)
- Modified coordinates available (Flagpost icon)
- Caches is saved on device (Disk icon)
- Offline log is stored (Red smiley)
- Cache coords are approximated (Encircled in Orange)
- Cache type is unknown (?? as cache type)
- Own cache (Star)
- Cache found (Smiley)

What and where is send2c:geo

Send to c:geo is a quicker was to transfer a cache open in browser to c:geo. All you need to do is follow this link http://send2.cgeo.org

How does it work

To use send2c:geo you need to:
a) register your browser to our servers
b) register your device to our servers
c) connect your device to your server.

Registering your browser is easy. Open send2c:geo page and click Register your browser. After registration you can add "a friendly name".

Registering your device is done in c:geo settings. You set a name and click "Register". After registration you get PIN number. Pin is valid only once and only for about an hour. You can always request new pin.

After you have both things registered open a send2c:geo page in browser, click "Add device", enter your PIN given by android phone and click add. You are done

I would register my device, but it shows 'registation failed'. Why?

Registering a device is only needed for send2cgeo. If it fails it can be one of the:
a) your device does not have internet connection
b) our servers are down or busy
c) a communication error or timeout occured
You can try again in couple of minutes (or hours) and if it persists contact us.

Can i use multiple browsers and/or devices?

Multiple devices can be on multiple browsers. You need to "register device" for every browser. PIN can only be used once.

There is no option "import from web" only "from GPX"

Your device got unregistered from send2cgeo website due to inactivity. Please re-register your device and it will work again.

Transfering caches with send2c:geo

On your app open stored caches, press menu, import, Import from web. After that c:geo waits for new caches.
In browser Open a cache and if script is installed and activated you should have button "send to c:geo".

How to make OSM Offline map

c:geo supports maps VERSION 0.2.4. Do not download or make 0.3.0 until we upgrade library!

Some offline OSM maps are pre-made on mapsforge website. Almost all countries are there to download. If you would like different map here is short and almost developer-like how to. How-to is written for Windows operating system with Java installed.

- Make a directory on your local harddrive (For our example we will use D:\OSM\). Try to avoid having space in a folder - like Document and Settings.
- Download Osmosis into D:\OSM\
- Unpack a zip in D:\OSM\ Please keep the directory structure. (you get D:\OSM\osmosis-0.39\)
- Download Trove (Click on latest version)
- Open trove zip file and inside zip under lib directory you will find trove-x.x.x.jar. Copy that jar to D:\OSM\osmosis-0.xx\lib\default (x can be any number)
- Create directory D:\OSM\plugins\
- Download mapsforge plugin to D:\OSM\plugins\
- Before downloading read Bandwidth and Connection Rate Limits. This is not our webpage and we are not responsible if you get banned.
- Find a map you wish to have offline on http://download.geofabrik.de/osm/ and download it to D:\OSM\ File must end with .osm.pbf
- Open a CMD and move to D:\OSM\ (Windows command line)
- Run the following command (replace -mapName- with exact map name you downloaded
osmosis-0.39\bin\osmosis --rb file=-mapName-.osm.pbf --mw file=-mapName-.map

Possible issues:
- You get an error saying "OutOfMemmory"
Java has some memory limitations by default. To give a map converter more memory run the following command before conversion. You can replace 2000m with something bigger if your computer has more memory. It's not recommended to set memory limit to high. Max value is 2000m (aprox. 2GB) for 32bit systems. Try to set this limit to 1GB less of your PCs physical memory.
set JAVACMD_OPTIONS="-Xmx2000m"
If you do not have enough memory you can set a program to use harddisk to convert map. Conversion will take longer but will not run out of memory. Just add type=hd at the end of command
osmosis-0.39\bin\osmosis --rb file=-mapName-.osm.pbf --mw file=-mapName-.map type=hd

Offline maps for c:geo

When c:geo is not connected to internet you can still have maps. Offline maps. See other FAQ how to download or build own maps. Here is an explanation how to use them:
Download or build will produce .map file. Copy that file somewhere in SD card.
Start c:geo and go to settings (Main screen, press menu, select Settings)
Go down to Map sources and in list select "OSM: Offline"
then press "..." just below a pulldown menu. c:geo searches your SD card for .map files.
Now select correct file you just uploaded (.map files from Navigon does not work)
Press back to leave settings. Every map (live map, navigate by map) will now use offline maps.

Mapsforge library has 2 bugs:
- 2 maps cannot be started simultaneously (Live map, select cache, full details, navigate, map) if you do that c:geo crashes with outof memmory
- large map files causes realy slow rendering and usually out of memmory crash. Try smaller files.
- only map files version 0.2.4 are supported!