After the first start, you have to setup how often and to which server your position data should be sent. Click the settings tab to switch to the setup screen.

Enter the IP address of the server running GPSLog@HomeServer into the fields host or host/path. Private internet connections usually change their IP address each time the connection is initiated. To find out your IP address, visit the page from the computer running GPSLog@HomeServer.

You can get a hostname for your computer by registering for a DYNDNS service. Many DSL routers offer DYNDNS support so your IP is updated automatically each time you connect to the internet. Visit the wikipedia-article about DYNDNS for more information and a list of DYNDNS service providers. Enter you DYNDNS hostname instead of your IP address into the field host or host/path.

If you use a http-server for receiving position data, enter the URL without the prefix http:// into the field host or host/path, e.g.

You have to enter the same port-number into the field port, that you entered in GPSLog@HomeServer. Use the default value 10536 unless this port is already used by another service on your computer. If you use a http-server, enter the port of the http-server which is typically 80.

Multiple users can be configured in GPSLog@HomeServer. Each user is identified by a username and a password. Enter the username and the password of one of these users into the corresponding fields in GPSLog@Home.

The following three fields are used to configure how often and to which server your position data should be sent. If you enter the values 60, 250 and 10 as shown in the screenshot on the left, your position will be sent every 60 seconds. If you move more than 250 meters away from the last sent position before the 60 seconds are over, your position will be sent immediately. But this only happens, if at least 10 seconds have passed since the last position has been sent. If no GPS signal is available, the same position will be sent multiple times.

The last field poll GPS every X seconds kann normally left empty. If your GPS turns off between data transmissions and you get inaccurate or no position data, you can enter a value here. Try out, how small this value has to be to keep your GPS alive. If you enter 0, GPS will be polled permanently. Shorter intervals will lead to higher power consumption.

Now click the tab GPSLog@Home to return to the start screen and click start log. You can switch to other applications now. GPSLog@Home will continue running in the background which is indicated by an icon in the notification bar at the top of the screen. You can get GPSLog@Home back to the foreground by clicking on this icon or by clicking on the application icon. Click stop log to stop the service.



GPSLog@HomeServer has to be configured, too. Open the settings-dialog by clicking the gear-icon in the left tool bar.

Enter the port-number on the tab Network. Use the default port 10536 unless this port is already used by another service. Always enter the same port number in GPSLog@Home and GPSLog@HomeServer.

Switch to the tab Users and enter at least one username with a password of your choice. Enter exactly the same values into the corresponding fields of your android app. If you want to monitor the positions of multiple android devices, e.g. of some friends, enter a username and a password for each device by clicking +.

The third tab Log allows to configure a directory where the position data should be saved.

DSL-routers and firewalls

If you have a DSL connection, your computer is connected to the internet via a router. Your computer is not reachable from the internet directly. You have to configure port forwarding in your router for receiving data with GPSLog@HomeServer. Look for something like port fowarding in the configuration tool of your router and enter a forwarding rule for the port number you entered in GPSLog@HomeServer. Choose the protocol TCP. The target is the computer running GPSLog@HomeServer.

If you use a firewall, you have to configure port forwarding there, too. By default, the Windows firewall will ask you, if you want to allow GPSLog@HomeServer to run as a server. Click do not block.

Using your own HTTP-server

GPSLog@Home sends its data via HTTP-GET. You will receive the following utf-8 encoded arguments:

useruser name
latlatitude as a decimal number
lonlongitude as a decimal number
altaltitude in meters
timetimestamp (seconds sinve 1970/01/01)
dirdirection in degrees
speedspeed in m/s