MrGPS – Mister GPS the ultimate GPS tracking and real time statistics tool for sport professionals

 

 

Current software version: 1.2.1

 

Date: July 31, 2013

 

Author: Amacri

 

Download: http://store.ovi.com/content/359009

 

O.S.: Symbian phones

 

Note: if your installed version is different from the one here reported, you need to perform an upgrade through Nokia Ovi.

 

MrGPS is an high-performance, compact, robust, comprehensive application which logs GPS tracks and provides real time statistics to sport professionals with voice aid.

 

The speech capabilities of MrGPS allow hands-free assistance while you are fully focused in cycling, driving, climbing, sailing, hiking, racing or in any other sport activity requiring physical and mental concentration in optimal performance.

 

To meet the widest customization requirements and address differentiated usage needs, MrGPS provides 240+ configuration settings through menus and property files.

 

MrGPS is written by the same author of Event_Logger for TomTom with a decade of experience in GPS logging and real time travel statistics.

 

MrGPS also works in case the mobile phone is dedicated to tracking, even without a SIM. The support of Symbian phones allows sport professionals to select lightweight mobile devices also starting from the cheapest or old ones and dedicate them to long running tracking and real time support, without the risk to damage new and very expensive smartphones or tablets while making sport.

 

The technical implementation of MrGPS allows consistency even if the mobile phone is accidentally switched off and on, or in case of need to change the phone battery. Allowing the user to bring additional batteries provides longer continuity for days of uninterrupted service, useful for instance when hiking or sailing. As MrGPS is a native and compact Symbian application designed for low memory and limited resource consumption, it easily supports concurrent navigation applications providing complementary assistance on mapping, directions and business POIs. MrGPS will not stop in case phone calls are placed or received, or in case other applications (like mapping tools) are concurrently executed.

 

MrGPS has specialized functionalities to monitor and report altitudes via visible and voice based alerts. It can manage uphill and downhill directions and provides real-time information of achieved quotes, limiting prompting to effective data. Considering that generally a GPS device might not be as accurate with elevation data as for horizontal coordinates, MrGPS is able to automatically discard unreliable values and, through an advanced proprietary algorithm, it can report percentages of slope with reliable figures, for instance useful while cycling.

 

MrGPS has many corollary functions, like automatic time GPS sync, also supported through advanced settings, and a configurable voice clock, where you can define different volume settings for different time periods. It also provides an Astronomic Calendar, with ephemerides of sun and moon, as well as a system information tool providing detailed information of the mobile device.

 

MrGPS has been accurately tested and tuned with many Symbian devices and supports Nokia Belle Feature Pack 2, Nokia Belle Feature Pack 1, Nokia Belle Refresh, Nokia Belle, Symbian Anna, Symbian^3, S60 5th Edition, S60 3rd Edition FP2, S60 3rd Edition FP1 and even S60 3rd Edition.

 

If you are taking all care to plan days of cycling, climbing, sailing or any other activity where you will not accept a failure to record your unforgettable moments, MrGPS is the appropriate application for you.

 

 

Purchasing MrGPS

 

MrGPS can be purchased via Ovi Store.

 

Alternatively, if you wish to purchase MrGPS via PayPal, please enter here your phone IMEI and email address, then press "Buy Now" to complete your transaction. To view the IMEI number of your phone (15 digits), dial the following digits:

*#06#

Please, select the option you consider most appropriate:

MrGPS: €8,00 EUR MrGPS with small donation: €10,00 EUR MrGPS with additional donation: €15,00 EUR

Enter your phone IMEI here:

Enter your email here:

 

Version history

 

●    MrGPS 1.2.1, July 30, 2013:

●    Support for all Symbian Phones starting from S60v3.

●    Improved volume control.

 

●    MrGPS 1.1.1, June 30, 2013:

●    improved data publishing process,

●    tested integration with Funambol OneMediaHub,

●    bug fixing,

●    updated documentation.

 

●    MrGPS 1.0.1, April 30, 2013:

●    initial version

 

GPX Tracking System

 

Through appropriate internal drivers, MrGPS creates tracks in one of the following three different output formats:

●    NMEA - National Marine Electronics Association (MrGPS supports NMEA 0183)

●    KML - Keyhole Markup Language (used by Google Maps and Google Earth; MrGPS supports KML 2.2)

●    GPX - GPS eXchange Format (MrGPS supports GPX 1.0)

 

Of these three MrGPS drivers, the one creating GPX files has the most complete set of functionalities, including structured tracking and management of waypoints based on user events and real-time analysis.

 

GPX (the GPS Exchange Format) is a light-weight XML data format for the interchange of GPS data (waypoints, routes, and unstructured or structured tracks) between applications and Web services on the Internet. Find more information at http://www.topografix.com/gpx.asp.

 

The majority of tracking analysis programs can manage GPX data. Among them, TopoFusion, OpenStreetMap/JOSM, Google Earth and GPSBabel are notable for their capabilities.

 

TopoFusion is an appropriate tool to perform basic graphical representation and analysis of GPX files produced by MrGPS (with 2D and 3D rendering); it can download and cache maps and digital elevation data from Internet as well as access them locally. It allows normalizing tracks (e.g., see spline/interpolate functionality), calculates speed (average, instantaneous, etc.), path length (also interpolated) and allows adding elevation data to a track; it can then perform lap and climbing statistics as well as other types of analysis.

 

OpenStreetMap is a CC-BY-SA project creating and distributing free geographic data for the world and allowing any user to cooperate by updating maps, POIs or any other georeferenced information via portal or stand-alone applications. OpenStreetMap allows uploading GPS tracks in GPX format, so that, through it on-line editor, performed tracks can be overlapped to maps and to already existing vector cartography, obtaining a reference to edit and update OpenStreetMap data. JOSM (“Java OpenStreetMap Editor”) is an excellent and extensible editor for OpenStreetMap data, definitively comprehensive. It does not require an Internet connection while editing, and is suited for the needs of advanced users. A majority of edits to the OpenStreetMap database are contributed using JOSM. A well implemented feature in JOSM is the integration with OpenStreetMap GPX data, as well as the ability to load GPX tracks (which can be simply dragged over JOSM to be rendered). Besides, JOSM has plugins to manage and analyze GPX tracks.

 

Google Earth is the well known 3G soft globe and graphical information application; it can directly import the GPX files produced by MrGPS.

 

GPSBabel is one of the most interesting utility to convert the GPX files produced by MrGPS in many other formats. It has free license and can manage about four dozen file formats, including TomTom POI, NMEA, HTML, KML, Magellan, Garmin and many others. GPSBabel runs on almost any computer and provides both a command-line interface and a GUI.

 

MrGPS installation

 

The easiest way to install and run MrGPS is to download it from Ovi Store and perform a standard setup. The description in this paragraph guides you to perform the most appropriate installation process.

 

After finishing the download operation from Ovi Store, the following panels are shown in sequence.

 

 

 

To start the installation process, press OK in the first panel; in the subsequent memory drive selection panel, choose Memory Card or Mass memory and avoiding configuring the output directory of MrGPS with the internal phone memory.

 

Planning the most appropriate target memory device for MrGPS tracks is important; by default, tracks are stored in the installation drive, but this configuration can be changed. In case Mass Memory or Memory Card are chosen, these memories need to be active to run MrGPS (for instance, the SD card must be inserted into the phone). Installing MrGPS on your Phone Memory will avoid this requirement; nevertheless, if the output directory is not changed to a different drive, it reduces the available free space of this small memory. While MrGPS takes less than 150 KB for its executable file (fairly irrelevant size for the phone memory), logged data might significantly reduce the available rooms. In general, it is not advisable to install new applications to the phone’s internal memory as it is small and can fill up quickly. Anyway, MrGPS allows installation in any memory and then, through the configuration menu, you can select the output memory to store logged data (Start MrGPS, check Options > Configuration > Edit settings > Output tab, “Memory in use”; notice that logging shall be stopped to enable this parameter to be shown and changed).

 

The default Root Folder within the selected target memory is Others/MrGPS; this directory can be shown translated by your device UI; anyway, you can change the directory path through the configuration menu of MrGPS (check Options > Configuration > Edit settings > Output tab > “Root folder”; notice that logging shall be stopped to enable this parameter to be shown and changed).

 

To go on with the installation, read the Notes panes in the third picture and then complete installation as shown in the following pictures. Notice that Nokia Belle Feature Pack 2, Nokia Belle Feature Pack 1, Nokia Belle Refresh, Nokia Belle, Symbian Anna, Symbian^3, S60 5th Edition, S60 3rd Edition FP2 install a full featured application, while S60 3rd Edition FP1 and S60 3rd Edition still support MrGPS but with some limitations.

 

  

 

The application is ready to run and already configured with the most appropriate default settings.

 

After starting MrGPS, if Bluetooth GPS is selected, the following panel might appear, asking to connect and pair one of the GPS devices in range (a password shall be inserted while connecting the device for the first time).

 

 

You can cancel operation if not interested in connecting external Bluetooth GPS units. If you are not planning to connect such devices, to disable this feature follow the description in Location based services configuration, removing Bluetooth GPS.

 

Conversely, if you plan to connect an external Bluetooth GPS device, verify that it is available in the “Last devices used” list, otherwise select “More devices” to start a search operation. When your device is found, select it; accept the pairing request, enter password and perform the Authorize operation to trust the paired device, so that you can allow it to connect automatically to your phone: go to Phone Settings (through the Home key of your phone) > Connectivity > Bluetooth (shall be activated if not active); right tab related to Associated Devices, Options, select “Authorized”; follow this Nokia guide or further information; check also your phone manual. Features using Bluetooth technology increase the demand on battery power and reduce the battery life.

 

To start tracking, press the “Start” soft button (or select “Start Now” from Options).

 

 

 

Then select GPX.

 

 

Tracking starts and information from the main panel is shown on the screen as in the following example (obtained with default values, that can customized one by one).

 

 

To verify that track recording is active, check that the sat lock is reached by browsing the “Sat. Num” parameter. Another way to check that recording is active is to verify the Notification lights if enabled (check related configuration), or monitor the Point counter in the main panel, which shall increase upon each acquired fix.

 

When pressing “Pause”, the tracking is temporarily stopped until the Resume key is pressed.

 

 

 

Notice that the status bar in the top side of the screen always shows MrGPS state: protocol and operation. “Idle” means that recording is not activated. “GPX – Recording” means that logging is currently active. “GPX – Pausing” means that, while recording GPX tracks, the pause key has been pressed.

 

To stop recording, press “Stop”. The following panel shows:

 

 

In the status bar, “Processing, please wait…” is reported until the GPX track completes the consolidation process, where the following operations are executed (with reference to the related configuration settings):

●    the GPX log collects waypoints and tracks into one single file; then this GPX file is correctly closed;

●    the statistic file is saved;

●    all files are published.

 

In case the Auto-start option is activated in MrGPS, when starting the application the logging automatically begins. When closing the application, MrGPS automatically accomplishes the consolidation and publishing processes before exiting. This method allows avoiding any configuration matter for normal operation: simply start MrGPS to log tracks and close it to publish them.

 

MrGPS also provides a Schedule Start functionality (Options > Schedule start), which allows planning the track logging at a specific Start Date and Start Time.

 

 

Text-to-speech installation

 

In order to exploit the speech functionalities, TTS has to be correctly installed and configured on the mobile device with the language that you plan to use.

 

  

 

Select Settings, Phone, TTS and verify that the appropriate language and voice are selected. If TTS is not available in your device configuration or if it is not correctly set, access page http://www.nokia.com/global/support/text-to-speech/ and install the desired national language package with the related available voice packages. Verify whether your phone is a S60 3.0/3.1 version or a S60 3.2 or higher (MrGPS provides this information at Options > Tools > System info, by checking the line named “O.S.”). Select the downloads related to your phone version and than two SIS files: one for the language and the other for the voice (notice that many voices might be available depending on the selected language); install all SIS files on your mobile device with Nokia Suite.

 

Go to Settings, Language and verify that your language is selected; select the appropriate voice, set volume to the maximum level (this is important to effectively manage mixed TTS and pre-recorded prompts), select also speed to an average level.

 

Location based services configuration

  

In order to select the most appropriate method to access GPS data, it is important to correctly configure the related GPS parameters. To understand the positioning methods provided by your Nokia phone, go to http://www.developer.nokia.com/Community/Wiki/Location_methods_in_S60

 

The configuration of the positioning methods is accessible through Phone Menu (home button) > Settings > Applications settings > Positioning > Positioning methods.

 

●    Assisted GPS (A-GPS)

If your SIM is configured with GSM/UMTS data link, Assisted GPS speeds up the first GPS lock through by querying the network. As this implies data costs charged by your mobile operator, the A-GPS option is suggested in case of already active data traffic subscription.

 

●    Integrated GPS

It is the internal GPS of the device and this should be ON for the device to use it's own GPS chipset.

 

●    Bluetooth GPS

This should allow you to use external GPS accessories interconnected with the mobile device via Bluetooth. This option is suggested in alternative to Integrated GPS. The external GPS device has to be paired with your phone and the appropriate password should be inserted.

 

●    Wi-Fi/Network

This option allows you to access the A-GPS function on demand via Wi-Fi when possible, instead of using the mobile data network. Unselect this option in case the Wifi connection is not used or not active.

 

●    Network Based

This setting allows the device to extrapolate approximate position from cellar data. As the returned value is useful for mapping programs but not accurate enough for a tracking tool like MrGPS, this option is not useful and can be switched off.

 

MrGPS configuration guide

 

An effective method to complete configuration and appropriately customize MrGPS is to load one by one the preconfigured settings detailed in the following list; this can be done via Options > Configuration > “Import settings”.

 

Steps to perform a quick customization of MrGPS:

●    download this archive

●    unzip it to a local directory of your PC

●    via Nokia Suite, create a directory on the mobile phone and copy relevant files to that directory (saving these files to the target MrGPS folder is better; it should be under Others\MrGPS on the selected MrGPS installation drive); if you also need voice prompts, copy them to E:\Sounds\Digital on your mobile phone.

●    Open MrGPS. Options > Configuration > “Import settings”.

●    Perform the following import operations (use the right key of the mouse to save the below mentioned links to local files instead of visualizing them):

●    Import “Suggested settings.ini”

●    Import “English messages.ini” (or “Italian messages without prompts.ini”, or “Italian messages with prompts.ini” provided that you also copied voice prompts to E:\Sounds\Digital).

●    Verify that the GPS source is correctly defined and that TTS (Text to Speech) is enabled with your language.

●    Basing on the following list, import the configuration file that most fits your needs (they are all alternative configurations, so load only one of them):

●    “Driving.ini”

●    “Sailing.ini”

●    “Cycling.ini”

●    “Walking.ini”

●    “Climbing.ini”

●    “Hiking.ini”

●    “Racing.ini”

 

This finishes the basic configuration steps and provides a ready-to-run MrGPS, already customized for most use cases.

 

Main configuration parameters

 

The following steps guide you to take advantage of additional functionalities of MrGPS.

 

Main configuration settings:

Options > Configuration > Edit settings > General tab:

●    Auto-unlock Keypad: With rec. started (or always)

●    Double click: Play Message

 

Options > Configuration > Edit settings > Input device tab:

●    Positioning method: select “Assisted GPS” if mobile network will be used to speed up satellite lock. If you plan to use MrGPS without a SIM, select Integrated GPS. Use GPS Bluetooth in case of external GPS antenna interconnected via BlueTooth.

●    Auto sync time after: set 10 seconds to be sure that the system time will always be synced with the GPS time

 

Options > Configuration > Edit settings > Display tab:

●    Measurement system: set the appropriate system used to display distances and speeds.

●    Metric: distance in metres/kilometres, speed in kilometres per hour, altitude in metres

●    Imperial: distance in feet/yards/imperial miles, speed in miles per hour, altitude in feet (1 imperial mile is 1,609 metres)

●    Nautical Metric: distance in metres/kilometres, speed in knots, altitude in metres

●    Nautical Imperial: distance in nautical miles, speed in knots, altitude in feet (1 nautical mile is 1,852 metres)

●    Items: select the items you wish to show during your travel

●    Speed decimal digits: select 1 digit

●    Course decimal digits: select 0

●    Min. secs for new popup: select 15

●    Set fonts: description font size = 100, Value font size = 210, Text color white, Backgroung color black.

 

Options > Configuration > Edit settings > Alerts tab:

●    Volume controls: set “Night volume start time” and “Night volume end time” if you plan to keep MrGPS active overnight. Night period begins at start time and ends one minute before end time. To avoid using night volume, set both start time and end time to 00:00 (more generally, setting start time and end time to the same value disables the time dependent volume feature). Notice that, according to the current time, volume can be directly set through the volume keys of the mobile phone, without need of navigating the configuration menu: the changed volume automatically reflects the related period (day time or night time).

 

●    General alert settings: in order to be compliant with Nokia directives, by default MrGPS is set to play sound and voice alerts only when the application is visible on the screen; if you conveniently need to also receive alerts when the application is in background, set “Activate alerts” to always (this setting is suggested). Set “Allow alerts after [secs.]” to e.g. 5 seconds or more to avoid too frequent alerts. If you want to receive an alert when position is lost or reacquired, set “Alert Sat quality” to “When sat state changes”.

●    Settings for altitude: in case you plan to go uphill or downhill, it is suggested to receive alerts when altitude changes; the related option is “Alert on delta altitude”, to be set to 50 or 100 metres (if you plan to use feets, you need to convert them in metres to set this variable, even if the measurement system in the display tab is set to Imperial/Nautical).

●    Settings for distance: set “Alert on delta distance”, to the most appropriate value fitting your needs; e.g., 5000 metres (if you plan to use miles, you need to convert them in metres to set this variable, even if the measurement system in the display tab is set to Imperial/Nautical).

●    Settings for time: set “Alert on local time” to 15 mins or 30 mins or 60 mins. Check also the Time Signal Voice Assistant chapter. Set also “Delta moving time” to 15 mins or 30 mins or 60 mins.

●    Settings for battery level: set “Low Battery Level” to 50% or less. Notice that the system might not intercept in time values lower than 20.

 

A very effective feature is provided through the double click of the screen area (for phones provided with a soft-keyboard) or by pressing the centre hard key of the phone (for phones with a hard keyboard), which allows to listen to trip data via text-to-speech (e.g., altitude, travelled distance, current time, etc.). See “Double Click” and “Alert double click” options for related configuration.

 

Options > Configuration > Edit settings > Notification lights: set Notification lights to the last value (Green/White+Err.notif.keys)

 

Options > Configuration > Edit settings > Output: set Autostart GPX.

 

The following bullets suggest appropriate tuning for specific usages of MrGPS.

 

●    Driving:

●    GPS update [millisecs.]: 1000

●    Intervals: none

●    Min. horizontal distance: 50 meters

●    Auto-pause(H. Speed): < 5 km/h

●    Auto-pause(H. + V. Speed): none

●    Auto-pause(H. Accuracy): none

●    Auto-pause(HDOP): none

●    Auto-pause(PDOP): none

 

●    Sailing:

●    GPS update [millisecs.]: 1000

●    Intervals: none

●    Min. horizontal distance: 20 meters

●    Auto-pause(H. Speed): < 2 km/h

●    Auto-pause(H. + V. Speed):

●    Auto-pause(H. Accuracy): none

●    Auto-pause(HDOP): none

●    Auto-pause(PDOP): none

 

●    Cycling:

●    GPS update [millisecs.]: 1000

●    Intervals: none

●    Min. horizontal distance: 20 meters

●    Auto-pause(H. Speed): < 4 km/h

●    Auto-pause(H. + V. Speed): none

●    Auto-pause(H. Accuracy): >=100m

●    Auto-pause(HDOP): none

●    Auto-pause(PDOP): >= 10.0

 

●    Walking:

●    GPS update [millisecs.]: 1000

●    Intervals: none

●    Min. horizontal distance: none

●    Auto-pause(H. Speed): < 1 km/h

●    Auto-pause(H. + V. Speed): none

●    Auto-pause(H. Accuracy): >=100m

●    Auto-pause(HDOP): none

●    Auto-pause(PDOP): >= 10.0

 

●    Climbing:

●    GPS update [millisecs.]: 1000

●    Intervals: 5 sec.

●    Min. horizontal distance: none

●    Auto-pause(H. Speed): none

●    Auto-pause(H. + V. Speed): none

●    Auto-pause(H. Accuracy): >=100m

●    Auto-pause(HDOP): none

●    Auto-pause(PDOP): >= 10.0

 

●    Hiking:

●    GPS update [millisecs.]: 1000

●    Intervals: 1 sec.

●    Min. horizontal distance: 10 meters

●    Auto-pause(H. Speed): < 2 km/h

●    Auto-pause(H. + V. Speed): none

●    Auto-pause(H. Accuracy): >=100m

●    Auto-pause(HDOP): none

●    Auto-pause(PDOP): >= 10.0

 

●    Racing:

 

Main functionalities

●    Enhanced GPX tracking, also supporting basic NMEA and KML logging

●    Real-time statistics, provided through screen items in the main panel and through statistic panels.

●    Geotagging

●    Accurate management of altitudes and slopes

●    Shortcut facility

●    Notification lights

●    Auto-segmentation of GPX tracks

●    Fully customizable voice assistant and alert manager (pop-ups, sounds and voices)

●    Time signal voice assistant, configurable for night and day

●    Automatic time sync of the phone clock with the GPS reference

●    Astronomic calendar

●    Data publishing

●    Resilience feature and function to change the battery within the same trip

●    Configuration management with 240+ settings and with the possibility to load, save and edit specific configuration presets

●    Customizable font sizes

●    System information panel

 

Geotagging

 

When recording is active, a manual operation is allowed, so that a named or unnamed waypoint (PoI = point of interest) can be stored within the GPX track.

 

Select “Tag current position”, give a PoI name (or press Cancel to avoid naming the PoI), then confirm to store the geotag.

 

   

 

Monitoring altitude

 

MrGPS is leading application to manage altitude values via visible and voice based alerts. The uphill direction is shown by an Up arrow symbol and downhill direction by a Down arrow symbol, while flat slopes are shown as a right oriented horizontal arrow. An asterisk close to slopes indicates imprecise slope values. Notice that only accurate values are compared and stored.

 

MrGPS shows the following real time figures related to altitude:

●    Altitude of the WGS84 ellipsoid

●    Altitude above the sea (SLM), referred to the geoid

●    Geoidal separation (difference between Ellipsoid Altitude and Sea Altitude)

●    Vertical speed

●    Vertical Accuracy

●    VDOP (Vertical Dilution of Precision)

●    PDOP (Positional (3D) Dilution of Precision)

●    Current slope

●    Maximum sea level altitude

●    Minimum sea level altitude

●    Total vertical rise (total sum of increasing altitude differences)

●    Total vertical drop (total sum of decreasing altitude differences)

●    Max slope when raising

●    Max slope when sloping

 

The following alerts are allowed in relation to altitude:

●    Alert on delta altitude

●    Alert small delta altitude

●    Alert uphill delta altitude

●    Alert downhill delta altitude

●    Alert min altitude

●    Alert max altitude

●    Alert uphill

●    Alert downhill

 

MrGPS allows to include the following altitude parameters within other alert messages:

●    {Altitude2}

●    {Altitude}

●    {MaxAltitude}

●    {MinAltitude}

 

How to monitor satellite lock

 

There are two methods to monitor satellites with MrGPS.

 

One is through Options > Tools > Satellite Status (in this case the standard Symbian GPS graphics appears).

 

  

 

The other is through the “Sat. Num” display item (Options > Configuration > Edit settings > Display tab > Items > Sat. Num).

 

 

 

“Sat. Num” shows two numbers separated by a slash: number of satellites in use and number of satellites in view. "satellites in view" are those ones which are tracked, meaning that they are identified in the firmament and there is some reception of signal data. The GPS unit will attempt to download ephemeris data from the satellites in view and this operation takes time. Note that satellites can be tracked at a lower signal level than the needed quality to download ephemeris so it is possible to track a satellite for a long time and not be able to use it. "satellites in use" are those ones which are receivable in praxis. If satellites in use are greater than 0 (and typically equal or greater than 3), the GPS lock is acquired. More specifically, useful data shown by “Sat. Num” are the following:

●    no value (or <None>): no satellites are available in view; this is the worst reception case (no position, no time reference).

●    0/1 to 0/v: limited reception, without lock; v can be 1 to the max number of satellites in view; in general, the higher this number, the shorter the time needed to get the lock. Even with one satellite in view, time reference is received; consider anyway that a fix is needed for affordable values.

●    3/v (with v >= 3): three satellites are needed to get a valid fix, but generally with imprecise altitude.

●    u/v (with u > 3 and v >= u): m represents the locked satellites. The higher this number, the more precise the 2D and 3D coordinates. The potential number of satellites that can be locked is reported by v.

 

Modifying color and font size

 

  Main screen

Description

 

Four configuration settings included in the display submenu allow to modify color and font size of the main screen panel:

●    Description font size: size of the font used for the description fields, which are on the left side of the main screen panel.

●    Value font size: size of the font used for the value fields, which are on the right side of the main screen panel. 

●    Text color: this is the color used for the text (avoid using the same color of the text).

●    Background color: this is the color used for background (avoid using the same color of the text).

 

   

 

The size of single cells can be emphasized by pressing for some seconds the related “Value" area through the touchscreen (i.e., the right part of the screen).

The size of emphasized cells can be reset by pressing for some seconds the related “Description” area.

 

For instance, in the below picture, to emphasize the Ellipsoid Altitude field, press the related value (i.e., over “195 m”) and keep the finger pressed until its value gets emphasized.

 

 

The picture below shows updated positions with emphasized ellipsoid altitude obtained with the previously described procedure. To reset the size of this field to normal dimension, press its description part (i.e., over “Ellips.Alt.”) and keep the finger pressed until the field size gets reset.

 

 

Multiple cells can be emphasized and reset, independently. Any change of panel (e.g., switch from the main panel to the statistical panel and return back to the main panel) will reset all values to standard dimension.

 

MrGPS Keyboard map: hard keys and softkeys

 

This paragraph details all softkeys and keys provided by MrGPS.

Softkeys available in the menu bar (lower bar):

●    Options: this soft key, positioned in the lowest left corner of the display of Symbian phones and shown as the Option symbol in the lowest right corner of Nokia Belle phones, allows accessing all MrGPS Options, described in next paragraph named “Menu Items”.

●    Hide: this soft key, positioned in the lowest right corner of the display of Symbian phones and shown as the Hide symbol in the lowest left corner of Nokia Belle phones, puts MrGPS in background with no signal sent to the application. Depending on the audio configuration, when MrGPS is in background the audio alerts might or might not be played. Logging and notification lights are not affected by background/foreground states of MrGPS.

To reduce unwanted menu bar pressures, a MrGPS option allows toggling the menu bar through the double click function of the touch screen (or through the main phone button of the keyboard for phones provided with an hard keyboard). Check Options > Configuration > General setting > Double click.

 

Other than the menu bar in the lower part of the screen (or defined as the left and right keys of Belle phones), MrGPS also allows a toolbar (defined as the three middle symbols on the toolbar of belle phones), which can be disabled through the configuration setting Options > Configuration > General setting > Toolbar.

●    Context softkeys in the toolbar (upper bar):

●    Stats (Sigma symbol, Σ): open the statistic panel; see paragraph Statistic Panel for a description of all available statistical features.

●    Start (play symbol, ►): stat recording

●    Pause (double vertical symbol, ║): pause recording

●    Resume (black circle symbol, ●): resume recording exiting a pause state

●    Stop (black square symbol, ■): stop recording, consolidating all log files; notice that the stopping operation can take some seconds depending on the log file size.

●    Quit (diagonal cross symbol, ╳): exit MrGPS, finalizing and closing logging and statistics

 

●    Statistics softkeys in the toolbar (upper bar):

●    Stat st. (Sigma symbol, Σ):open the statistic panel

●    GPS st. (G symbol, G). open the GPS data dump

●    NMEA (N symbol): open the NMEA dump

●    Copy (Interception symbol, ∩): allow selecting all statistics and copying them to the clipboard

●    Save (OK or square root symbol, √): allow selecting all statistics and saving them to a file

 

●    Statistics softkeys in the toolbar (lower bar):

●    Reload (round clockwise arrow symbol, ↻): this key is a toggle, which alternates the statistics autorefresh functionality, to provide always updated data, or freezes the screen, to allow scrolling and visual analysis on the shown data

●    back (left arrow symbol, ←): this key allows returning back to the main screen from the function panels (statistics, calendar, system information, NMEA, GPS).

 

Other than soft keys, MrGPS allows control through the hard keyboard, when available. Check Options > Configuration > General setting > Shortcut (or Options > Help > Shortcuts) for the configuration of this feature. This is the list of available keyboard shortcuts:

1                      Start Now Current

2                      Schedule Current

3                      Pause/Resume/Stop menu

-                       Stop

.                       Exit

,                       Hibernate

0, Space          Geotag position

p, P                 Pause/Resume

r, R                  Resume

 

n, 9                  Start Now NMEA

N                     Schedule Start NMEA

g, 5                  Start Now GPX

G                     Schedule Start GPX

K                     Start Now KML

K                     Schedule Start KML

 

Enter                toggle display filter

*, u, U              Lock keypad

#, j, J               Tools menu

L                      Start Now/Stop

L                      Schedule Start/Stop

v, V, 7              O.S. Version

c, C, %             Configuration

z, Z                  Statistic Viewer

o, O                 Toggle Sat. Off/On

a, A                  Astronomic Calendar

^                      Save sys info to file

>, )                   Save settings to file

<, (                   Load settings from file

m, M                System Information

 

For the settings tabs:

e, E                  Edit item

b, B                 Back to the main screen

 

All the above listed keys and soft keys are also accessible via menu options.

 

The red and green phone keys (End and Answer keys) have no influence with MrGPS (in case the Application type settings in Options > Configuration > Edit Settings > General is set to Standard Application, MrGPS is killed when pressing the End key).

 

The lateral volume buttons of the phone (when MrGPS is in foreground) control MrGPS volume. Keeping the Volume Up pressed, the volume is automatically set to 8 (and a beep is heard); keeping the Volume Down pressed, the volume is automatically set to 0 (disabled). To move MrGPS volume to the max value (10), keep the Volume Up pressed (set value to 8) and then click it for additional two times.

 

The pressure of the centre hard key of the phone, or the double click of the touch screen for phones provided with this feature, runs the “Alert double click” message (see Options > Configuration > Edit Settings > Alerts).

 

MrGPS Menu items

 

This paragraph details all menu options provided by MrGPS, accessible through the Options soft key.

 

 

●    Start Now (crash recording); this feature starts GPS logging, using one of the available formats:

●    NMEA (linear NMEA recording through all configurable sentences, without possibility of geotagging and with no track segmentation; NMEA can also be used to record a track for further playback through the mobile device)

●    GPX (suggested option, including all advanced features provided by MrGPS, like geotagging, track segmentation, and high availability)

●    KML (basic features; will be possibly enhanced in future releases).

      “Start Now” is the same as pressing the Start soft key.

 

 

●    Schedule Start (schedule recording); this feature schedules a future auto-start of the GPS logging basing on the comparison of the configured start time/date with the GPS timestamp (not the phone one). All available formats can be used for schedule start:

●    NMEA

●    GPX

●    KML

 

●    Reset counters; counters used to control border values and real time statistics can be manually reset during the trip.

●    Duration: reset total duration of the trip

●    Speed: reset the recorded maximum speed

●    Partial Speed: reset the recorded maximum partial speed

●    Altitude: reset the recorded maximum and minimum altitude

●    Slope: reset the recorded maximum uphill and downhill slopes

●    All counters: reset all above listed counters

 

 

●    Tools

●    Satellite Status: visual report of the GPS Satellite Information through standard Symbian User Interface panels, including:

●     Firmament view, which displays all the satellites in view with the satellite's number on a firmament.

●     Signal strength view, which displays all the satellite with their correspoinding signal strength represented by bars.

●     Compass view (optional, only for Symbian Anna and Belle phones), which displays latitude, longitude, speed and direction along with 2D/3D type of Fix.

●    GPS Status: dump of information provided by the GPS device (when satellites are locked)

●    NMEA Viewer: NMEA dump of information coming from the GPS device

●    Statistic Viewer: list of all MrGPS statistics

●    Astronomic Calendar: ephemerides of sun and moon.

●    Save Calendar: save to file the statistic information provided by the Astronomic Calendar

●    Stats Snapshot: save to file the statistic information provided by the Statistic panel

●    Satellites off/on: turn off or on the GPS device; notice that no recording can happen when the GPS device is off (even if this benefits the battery consumption); sometimes the GPS connection gets stuck and switching off and on satellites allows restoring the GPS lock; this feature is also automatically performed when the GPS lock is lost for long period

●    Sync time: sync the phone time with the GPS reference; this feature provides automatic adjustment of the phone time according to the GPS data

●    Hibernate: quit MrGPS without finalizing and closing the GPX file and without accounting statistics, so that a new MrGPS restart will go on with the current trip logging instead of creating a new log. This feature is useful to change the phone battery during a trip; hibernating MrGPS before switching off the phone shall be the correct operation to change the battery; when rebooting the phone and restarting MrGPS, the current logging continues. As MrGPS periodically saves temporary data for resilience, it is also able to recuperate the current logging after a phone crash or after a phone automatic switch off due to exhausted battery (check Options > Tuning > Snapshot Period to adjust the periodical save operation). To perform a standard quit of MrGPS, also finalizing log data, check Exit option (or exit soft key).

●    Reset config: remove all customized settings restoring MrGPS settings to default values.

●    System Info: panel providing detailed information on phone operating system, storage, CPU and MrGPS process counters.

●    Save system Info: this feature saves to file the information shown in the “System info” panel.

 

  

●    Configuration

●    Edit Settings: MrGPS setting menus; all configuration and tuning of MrGPS can be performed through this function.

●    LBS Settings: this is a shortcut to the phone LBS (location based services) settings (outside MrGPS), also accessible through the standard phone configuration panels.

●    TTS Settings: this is a shortcut to the phone TTS (text-to-speech) settings (outside MrGPS), also accessible through the standard phone configuration panels.

●    Load settings: MrGPS settings can be loaded, saved, imported or exported. Saving settings creates a binary file which fully duplicates MrGPS current configuration, so that a saved configuration can be restored through the Load settings. This allows for instance to create different configuration for specific trip patterns, like cycling, driving, footing, hiking, etc. To enable loading a configuration, logging shall be stopped.

●    Save settings; save to file the current configuration.

●    Export settings: other than loading and saving configuration, MrGPS supports exporting and importing data through standard text files. Export settings dumps the whole MrGPS configuration to a text file which can be manually edited through a standard text editor or also manually cut into separate pieces only including relevant data. This feature enables to easily exchange configuration patterns through MrGPS users, like for instance TTS configuration settings for a specific language.

●    Import settings: this feature allows importing a text file reporting partial or total configuration settings of MrGPS parameters.

●    Switch off filter: this toggle allows disabling the filtering of shown statistical parameters provided by “Options > Configuration > Display settings > Display > Items” setting, either showing all parameters or only the ones configured through this configuration setting.

 

●    Help

●    About: show MrGPS version and copyrights

●    Shortcuts: list of keyboard shortcuts allowed by MrGPS

 

●    Exit: quit MrGPS, involving finalization of logs (check Hibernate to quit MrGPS keeping the current configuration active). Notice that the closing operation can take some seconds depending on the log file size. This option is also available via soft key, after stopping a log.

 

File types and formats

 

This chapter lists all file types and format managed by MrGPS.

 

Output GPX tracks:

●    Formats: GPX, KML, NMEA

●    Direction: generated by MrGPS

●    Base name format: yyyymmddhhMMss.<extension>; y=year, m=month, d=day, h=hour, M=minutes, s=seconds; <extension> is configurable through related settings and defaults to gpx, kml, nmea.

●    Sample file names: 20130224140711.gpx, 20130224140711.kml, 20130224140711.nmea

●    Notes: extension is configurable through the related setting menus when the logging is stopped

 

Output GPX waypoints:

●    Formats: GPX

●    Direction: generated by MrGPS

●    Base name format: yyyymmddhhMMss-Wpt.<extension>; y=year, m=month, d=day, h=hour, M=minutes, s=seconds; <extension> is configurable through related settings and defaults to gpx.

●    Sample file name: 20130224140711-Wpt.gpx

●    Notes: extension is configurable through the related setting menus when the logging is stopped

 

Output GPX tracks with embedded waypoints:

●    Formats: GPX

●    Direction: generated by MrGPS

●    Base name format: yyyymmddhhMMss-Wpt.<extension>; y=year, m=month, d=day, h=hour, M=minutes, s=seconds; <extension> is configurable through related settings and defaults to gpx.

●    Sample file name: 20130224140711-Wpt.gpx

●    Notes: this file is similar to the two ones listed above (GPX tracks and GPX waypoints), but embeds waypoints and tracks in the same file. It has the same name of the “GPX waypoints” file.

 

Output statistics:

●    Formats: TXT file

●    Direction: generated by MrGPS

●    Base name format: same as the related output track with “-Stats.txt” extension (e.g., 20130224140711-Stats.txt)

●    Notes: save operation accessible through Options > Tools > Stat Snapshot

 

Astronomic calendar output:

●    Formats: TXT file; save operation accessible through Options > Tools > Save Calendar

●    Direction: generated by MrGPS

●    Base name format: Calendar<number>.txt (file name can be changed through the related pop-up panel while saving configuration file)

 

System information output:

●    Formats: TXT file

●    Direction: generated by MrGPS; save operation accessible through Options > Tools > Save System Info

●    Base name format: SysInfo<number>.txt (file name can be changed through the related pop-up panel while saving configuration file)

 

Configuration:

●    Formats: DAT file

●    Direction: input and output

●    Base name format: Configuration<number>.dat (file name can be changed through the related pop-up panel while saving configuration file)

 

Configuration dumps (setting export and import):

●    Formats: INI file

●    Direction: input and output

●    Base name format: ConfigDump<number>.ini (file name can be changed through the related pop-up panel while saving configuration file)

 

Auto-segmentation of trips

 

MrGPS is able to automatically include segmentation tags inside the GPX tracking, basing on stop periods.

 

Segmentation adds information to your logged trips, improving real-time statistics, allowing you to understand where you stopped and reducing logging size.

 

Even if default trip segmentation parameters are appropriate for most usage cases, MrGPS allows configuring ad tuning auto-segmentation and this paragraph describes in detail the related process.

 

A trip is segmented through different counters, allowing to compute the following listed timeframes and to automatically partition the related GPX tracking accordingly.

●    Pause: this is a manual operation of pressing the pause key; total pause duration is the sum of the timeframes between pause commands and resume commands. Excluding pauses from the trip duration means that only the recording time is computed.

Long delay segmentation logs the following GPX tags: </trkseg> </trk> <trk> <cmt>Manual pause</cmt> <trkseg>. Besides, the subsequent logged fix repeats the last fix before the segmentation and includes the GPX tag <name>PAUSE</name>.

●    Long delay: period between two fixes exceeding a configurable parameter (longer than “short delay”) which defaults to 10 minutes (to change it, check Options > Configuration > Edit settings > Segmentation > Long delay [secs]); even if the period between fixes is generally governed through the logging granularity parameters, it might happen that for some reasons the time between two consecutive fixes becomes much longer than expected (e.g., missing satellites in view for a sustained period). For example, in case during a mountain excursion part of the time is spent inside a shelter where satellites are not received, this period is logged and, if excluded from the total trip time, allows automatic computation of related statistical parameters like speed when walking to reach the shelter excluding time inside the shelter.

Long delay segmentation logs the following GPX tags: </trkseg> </trk> <trk> <cmt>Long delay</cmt> <trkseg>. Besides, the subsequent logged fix repeats the last fix before the segmentation and includes the GPX tag <name>DELAY</name>.

●    Short delay which defaults to 30 seconds (to change it, check Options > Configuration > Edit settings > Segmentation > Short delay [secs]): period between two fixes exceeding a configurable parameter (shorter than “long delay”). Periods between two fixes exceeding a configurable parameter are divided into two groups: short and long delays, the latter delay is greater than the former. In general, a short delay might be caused by temporary missing satellite coverage, possibly due to occasional incorrect GPS receptions (e.g., when walking in a canyon, like a narrow street within high buildings); long delays typically happen when remaining into a building for quite a long time. Notice that when the recording is paused, long and short delays are not computed.

Short delay segmentation logs the following GPX tags: </trkseg> <trkseg>.

●    Automatic stop detection. Segmentation based on pause detection is ruled by the “auto pause” process and by a configuration parameter named “Number of Autopaused fixes to Segment”.

"Auto pause" is a function that automatically pauses and resumes logging according to the following GPS parameters:

●    H.Speed (Horizontal Speed)

●    Speed (speed vector calculated using horizontal and vertical speed)

●    H.Acc (Horizontal Accuracy)

●    HDOP (Horizontal Dilution Of Precision)

●    PDOP (Positional (3D) Dilution Of Precision)

When the auto-pause condition persists for a number of consecutive fixes exceeding a configuration parameter named “Number of Autopaused fixes to Segment”, segmentation occurs.

Auto-pause time is also accounted by two real time statistical parameters: stop and pull-up.

●    Pull up: total auto-pause time of a trip (without reference to “Number of Autopaused fixes to Segment”).

●    Stop: total auto-pause time exceeding “Number of Autopaused fixes to Segment”.

The Pull up period is generally wider than the Stop one, but might account improper timeframes like sporadic auto-pauses related to temporary satellite coverage reduction, or speed slower than the configured auto pause Speed parameter, or other incorrect stop conditions; the configuration parameter named “Number of Autopaused fixes to Segment” can be tuned and should mitigate the possibility to introduce improper auto-pause times in statistics. In general, “Stop” shall be the reference statistical value accounting auto-pauses, while “Pull up” helps the user to correctly tune “Number of Autopaused fixes to Segment”.

Automatic stop detection logs the following GPX tags: </trkseg> <trkseg>. Besides, the subsequent logged fix repeats the last fix before the segmentation and includes the GPX tag <name>(Repeated fix)</name> (or other possible messages describing the segmentation reason).

 

The following pictures obtained with the mentioned Topofusion application show how waypoints and segmentation can improve track quality. A fix is repeated upon each auto-pause, in order to provide continuity to the track.

 

 

 

You might request that MrGPS embeds a visual mapping panel, maybe a tool to provide directions and possibly a feature compute distance and expected time to a predefined destination: indeed MrGPS has a different target. MrGPS is a tracking application which shall be kept running for the whole track duration, without sensibly affecting the mobile phone performance and without jeopardizing the handset overall functionalities; this is the design basis for this project. Notice that MrGPS can run in background and will not be killed by the operating system in case of reducing resources. Besides, you can associate it to any mapping application, considering that you might open your favourite mapping product when you need to consult it and close it whenever you want. Generally, mapping and graphical trackers take significant resources and have different goals than MrGPS. Notice also that the GPX logs generated by MrGPS can be loaded by Nokia Ovi Maps to analyze the included waypoints. To accomplish this, open Nokia File Manager, browse the MrGPS output folder, select a GPX file, click on it; a list of all included waypoint shall appear; through the Options button you can send a group of waypoints via SMS, e-mail, Bluetooth or show a waypoint on map; this last feature invokes Nokia Ovi Maps to graphically represent the selected element.

 

A mapping product suggested for its wide set of functionalities is MapNav. The latest MapNav version is here http://mapnav.spb.ru/site/files/mapnav_4_8_16.zip. As MapNav is a J2ME application, you need to appropriately setup the Java Virtual Machine options so that MapNav opens in full screen without asking confirmation questions and with no security restrictions; this operation is a bit tricky on Nokia phones. MapNav can load waypoints from MrGPS and runs concurrently as an excellent mapping front-end.

 

Associating photos to GPX tracks can be done through external tools. MrGPS allows to very easily geotag a position by applying a name or default data. Besides, with the Nokia camera tool, you can automatically add GPS coordinates to your picture, so that location is directly embedded in the related EXIF image metadata. You can for instance load GPX tracks and geotagged images with JOSM into a single graphical representation. MrGPS does not embed images in GPX files in order to avoid creating extremely large logs, that could result unusable by geo analysis programs. In case EXIF data are missing in your photos (e.g., taken with a standard camera), you can exploit tools to geotag them through the GPX track produced by MrGPS; these tools compare the time when the pictures were taken with the related GPX position an that time. Try googling “geotag photos gpx”.

 

Alerts

 

MrGPS allows configuring three kinds of real-time notifications, named alerts: pop-ups, beeps and voice messages.

●    Pop-ups: the following alert messages can generate a visual pop-up: "Alert min altitude", "Alert max altitude", "Alert uphill", "Alert downhill", "Alert max speed", "A. max partial speed", "Alert no sat", "Alert locked sat ok". See also “Activate alerts” and “Allow alerts after [secs.]” configuration variables to activate pop-ups and control related delays.

●    Beeps: depending on the configuration of each alert message, an alert can generate a fixed predefined beep, where configuration variables "Beep pitch [Hertz]" and "Beep duration [millisecs.]" control the pitch and duration reference parameters for all alerts; each alert message has a specific pitch and duration that is set as a multiple or a fraction of these reference values. See also “Activate alerts” configuration variable. The internal representation of this option is number 1.

●    Voice messages, with different options: no sound, internal and external sounds/melodies/audio clips, spoken texts, MrGPS tokens or any combination of them.

●    No sound: if an alert is set to “<Disabled>”, no sound event is generated apart from the pop-up. The internal representation of this option is number 0.

●    Internal sounds, melodies or audio clips: MrGPS can configure any predefined ring tone available within the firmware of the mobile device through the “Internal fixed sound” option; a submenu allows navigating through all existing clips; when selecting one, it is played in preview and if confirmed, the related pathname is saved within the configuration setting.

●    User defined sounds, melodies or audio clips: three options are available to browse and select a clip included in:

●    Phone memory (the internal phone storage)

●    Memory card (an SD card, if active)

●    Mass memory (The built in internal memory available with some phones where files should be stored instead of the Phone memory)

The audio playback component included in MrGPS supports the following audio formats: Wave, AMR, MIDI, MP3, AAC, RNG and Real Audio.

●    Spoken tests: if the configured setting is not a number or a pathname, it is considered spoken text and it is sent to the Text-to-speech component, also able to process punctuation, MrGPS tokens and to replace $ (or #) with the alert value and related unit.

●    MrGPS tokens: a number of reserved words are substituted with the appropriate value when playing TTS text; see “MrGPS tokens” for further details.

●    Combination of sounds: through character ‘|’ used to separate sounds, MrGPS allows defining a combination of different sounds, text and tokens within each alert.

 

MrGPS sets the audio output to the phone loudspeaker. Volume can be controlled through the lateral volume buttons of the phone (when MrGPS is in foreground) and through the configuration options; while the volume buttons allow setting volatile levels, the configuration options set permanent values, valid each time MrGPS is started; volume control can also be organized in day time and night time to set different volume levels for day and night (ref. Options > Configuration > Edit settings > Alerts tab > Alert > Volume Controls). MrGPS has sound priority versus the most common applications concurring to use the same audio output device and generally other playing applications (like FM radio, music or streaming player) are interrupted when MrGPS takes the control of the audio device to play sounds or to speak (after the sound completion of MrGPS, the other applications concurrently accessing the headphones or loudspeakers can automatically or manually restart, depending on the way these are developed). Volume=10 is the highest volume level. Volume=0 disables the sounds and is useful to avoid interrupting other applications. Notice that by keeping the up volume button pressed, the volume directly goes to 8, while when keeping the down volume button pressed, the volume switches to 0.

 

Each alert message allows the following edit options:

●    <Disabled>
No sound associated to the alert.

Internal label: 0

●    Predefined beep
When the alert is triggered, beeps are played out.

Internal label: 1

●    Internal fixed sounds
Ring tones.

Example: Z:\Data\Sounds\digital\ringtone.rng

●    Phone memory
Clip included in the phone memory.

Example: C:\Data\Audio\clip.mp3

●    Memory card
Clip included in the memory card.

Example: E:\Sounds\Digital\Sun fun.aac

●    Mass memory
Clip included in the mass memory.

●    (Drive info)

Description of all available drives including path, total memory and free memory.

●    Manually edit pathname

Text and combination of texts and sounds.

                  Example: Current altitude|$|{Distance2}|C:\Data\Audio\clip.mp3

●    (Help on reserved words)

List of predefined tokens that can be used inside the combination of texts and sounds

 

Sample of manually edited pathnames.

 

C:\Data\Audio\clip.mp3|Current altitude|$|{MaxSpeed}

 

In the above example, the following speech is played:

●    C:\Data\Audio\clip.mp3: melody

●    Current altitude: the word “Current altitude” is recited by the text-to-speech phone function

●    $: 145 m (text-to-speech)

●    {MaxSpeed}: 115 km/h (text-to-speech)

 

MrGPS tokens:

●    General tokens and messages:

●    Pathname: the content is considered an audio clip and it is executed by the internal player

●    free string: the content is considered a test to be recited through TTS (internal Text-To-Speech function)

●    |: separator character; it allows consecutive pathnames, free strings, tokens or patterns

●    $: alert value pattern, substituted with the default parameter related with the specific alert (including unit). Ref. each alert description for the actual value of this pattern.

●    #: same as $

 

●    Full messages including the play out of the complete configuration setting related to the specified alert (beep or combination of voice messages):

●    {Altitude}: execute the most appropriate Altitude alert (uphill, downhill or flat). Ref. {Altitude2} for a simplified message. Related value is the current MSL Altitude.

●    {ResetSpeed}: reset the maximum speed to 0.

●    {ResetPartialSpeed}: reset the maximum partial speed to 0.

●    {MaxSpeed}: execute the Maximum Speed alert (playing the max speed of a trip). Related value can be reset with {ResetSpeed}.

●    {MaxPartialSpeed}: execute the maximum partial speed alert. Ref. {MaxPartialSpeed2} for a simplified message. Related value can be reset with {ResetPartialSpeed}.

●    {MaxAltitude}: execute the Maximum Altitude alert.

●    {MinAltitude}: execute the Minimum Altitude alert.

●    {Distance}: execute the Distance alert (total trip distance). Ref. {Distance2} for a simplified message.

●    {LocTime}: execute the Local Time alert (playing the current time).

●    {RecTime}: execute the Total Moving Time alert, but passing the total trip time argument (playing the total recording time) instead of the total moving time.

●    {MovTime}: execute the Total Moving Time alert (playing the total time when in movement).

 

●    Simplified messages only including value and unit:

●    {Altitude2}: simple alert message including value and unit of the current MSL altitude (same as if all three “Altitude” alerts were set with a simple “$” pattern). Ref. {Altitude} for a full message.

●    {Distance2}: simple alert message including value and unit of the total trip distance (same as if the “Distance” alert was set with a simple “$” pattern). Ref. {Distance} for a full message.

●    {MaxPartialSpeed2}: simple alert message including value and unit of the maximum partial speed (same as if the “MaxPartialSpeed” alert was set with a simple “$” pattern). Ref. {MaxPartialSpeed} for a full message. Related value can be reset with {ResetPartialSpeed}.

●    {RecTime2}: simple alert message including value and unit of the total recording time for the whole trip (same as if the “RecTime” alert was set with a simple “$” pattern). Ref. {RecTime} for a full message.

●    {MovTime2}: simple alert message including value and unit of the total moving time (same as if the “MovTime” alert was set with a simple “$” pattern). Ref. {MovTime} for a full message.

 

●    Automation of recording controls:

●    {StartGpx}: start recording using GPX format for logging.

●    {StartKml}: start recording using KML format for logging.

●    {StartNmea}: start recording using NMEA format for logging.

●    {Stop}: stop recording.

●    {Suspend}: stop recording keeping the statistics active, so that a restart goes on with the current real time statistics instead of resetting them.

●    {StopExit}: stop recording and terminate MrGPS.

●    {SuspendExit}: same as Hibernate option; stop recording and quit MrGPS keeping the statistics active, so that running MrGPS again and restarting logging will keep real time statistics instead of resetting them.

●    {Stats}: activate the statistic panel

 

●    Jump controls:

●    {Skip}: skip the subsequent elements of the message; it is possible to add {skip}|{skip}|{skip} to skip the subsequent three elements; this token is useful to comment out message elements.

●    {Break}: skip all subsequent elements of the message; this token is useful to temporarily reduce the number of played out message elements without deleting settings.

 

Sample of message including tokens.

 

Stopped|{break}|{altitude}

 

In the above example, the following speech is played:

●    Stopped: the word “Stopped” is recited by the text-to-speech phone function

●    {break}: all subsequent messages are skipped

●    {altitude}: skipped message

 

Other sample of message including tokens (e.g., referred to the double click alert).

 

{altitude2}|{distance2}|{MaxPartialSpeed2}|{ResetPartialSpeed}|{MovTime2}

 

In the above example, the following speech is played:

●    {altitude2}: value and unit of the current MSL altitude

●    {distance2}: value and unit of the total trip distance

●    {MaxPartialSpeed2}: value and unit of the maximum partial speed

●    {ResetPartialSpeed}: reset the maximum partial speed to 0

●    {MovTime2}: value and unit of the total moving time

 

Other sample of message referred to the local time:

 

Z:\Data\Sounds\Digital\Topic.aac|It’s $

 

The following speech is played:

●    Z:\Data\Sounds\Digital\Topic.aac: this clip is played out (e.g., time signal)

●    It’s $: in case this pattern is referred to “Alert local time”, the dollar symbol is substituted with the local time (e.g., 11:35) and the whole message becomes “It’s 11:35”, which is in turn recited by the text-to-speech phone function

 

 

Astronomic Calendar

The Astronomical Calendar panel of MrGPS provides a textual report of the ephemerides of Sun and Moon.

 

Example of report:

Astronomic Calendar - Ephemerides of Sun and Moon

Day length (HH:MM): 15:37

  with civil twilight: 16:52

  with nautical twilight: 18:33

  with astronomical twilight: 20:49

Length of civil twilight: 00:38

Length of nautical twilight: 01:28

Length of astronomical twilight: 02:36

Sun at south at 13:19

  rises at 05:30, sets at 21:08

Civil twilight starts at 04:52, ends at 21:45

Nautical twilight starts at 04:02, ends at 22:36

Astronomical twilight starts at 02:54, ends at 23:44

Local Civil Time: Fri, 07 Jun 2013 07:52:31 UTC+2

Terrestrial Dynamical Time: 07:53:51

Local Mean Time: 08:32:32 - Julian Day 2456,450.745

The Moon is waning crescent: 5 days and 17.0 hours past Last Qtr.

Moon is above the horizon.

  Az=93[E], Elev.=30 dgr.

Greenw.Mean Sidereal Time: 00:55:42

Local Sidereal Time: 01:35:43

Sun Local Hour Angle (LHA): 08:33:41

Sun: Declination 22.768 Degrees,

Sun is above the horizon.

  Azimuth 79.222 Deg. [E],

  Elevation 21.795 degr.

Moonrise 04:46   Tomorrow: 05:29

Moonset  20:02   Tomorrow: 20:53

 

Many internet sites can help to understand the meaning of the shown data. Check in particular http://www.stjarnhimlen.se/comp/tutorial.html and http://www.stjarnhimlen.se/comp/riset.html for further information.

 

For the definition of sunrise and sunset, moonrise and moonset, civil, nautical and astronomical twilight, visit page http://aa.usno.navy.mil/faq/docs/RST_defs.html. (Civil twilight is when illumination is sufficient, under good weather conditions, for terrestrial objects to be clearly distinguished. During nautical twilight general outlines of ground objects may be distinguishable, but detailed outdoor operations are not possible, and the horizon is indistinct. In astronomical twilight sky illumination is so faint that it is practically imperceptible even if it is not dark enough for accurate star observation.)

 

Notice that all times are represented as local, not UTC.

 

Sun and moon can be immediately identified in the sky above us through their horizontal coordinates:

●    Azimuth (Az): the horizontal angle of the sun (or of the moon) or related direction produced through compass bearing, like that one graphically represented by TomTom. The azimuth is the arc between the true north and the vertical circle passing through the centre of the sun or the moon, clockwise from the north point (0°) through 360 degrees

●    Elevation (Elev.): the angular distance of the sun (or of the moon) above the horizon, represented in degrees between -90° and 90°; 0° represents the horizon; the elevation is the arc of a vertical circle intercepted between the sun (or the moon) and the horizon

 

Elevation and azimuth: 1 horizon, 2 zenith, 3 sun or moon, 4 meridian, 5 vertical circle; the angle from the horizon is the elevation, 6 azimuth (angle from north=0°), 7 observer

 

In order to determine the position of the sun and of the moon:

●    read the azimuth and elevation of the sun through the Astronomical Calendar,

●    ensure that the elevation angle is positive (when negative, the celestial object is not visible,

●    switch back to MrGPS main panel (or to the statistical panel) and read the course parameter (move the phone for some meters in order to read a valid bearing),

●    orientate the phone to the same azimuth angle of the celestial body to find its direction.

●    The elevation measures the vertical angle of the sun or moon in degrees from the horizon. A negative value means sun or moon below the horizon. More specifically: -0.5833 degrees is sunrise/sunset (which will delimit night time from daytime), -6 degrees is the civil twilight, -12 degrees is the nautical twilight and the astronomical twilight is 18 degrees below the horizon (-18°).

The following table maps the elevation of the sun (reported at line “Elevation … degr.”) with the position of the sun in relation to the horizon:

●    any positive value for degrees: daylight time

●    0 degrees: centre of Sun's disk touches a mathematical horizon

●    -0.25 degrees: sun's upper limb touches a mathematical horizon

●    -0.583 degrees: centre of Sun's disk touches the horizon; atmospheric refraction accounted for

●    -0.833 degrees: sun's supper limb touches the horizon; atmospheric refraction accounted for (civil sunrise/sunset)

●    -6 degrees: civil twilight (one can no longer read outside without artificial illumination)

●    -12 degrees: nautical twilight (navigation using a sea horizon no longer possible)

●    -15 degrees: amateur astronomical twilight (the sky is dark enough for most astronomical observations)

●    -18 degrees: astronomical twilight (the sky is completely dark)

 

 Astronomic Calendar

 

Condition of solar eclipse:

●    Both sun and moon are visible, apart from the period when the moon obscures the sun (e.g., each elevation > 0)

●    Azimuth of the sun = azimuth of the moon

●    Elevation of the sun = elevation of the moon

 

Condition of lunar eclipse:

●    Moon is visible, apart from the period when not obscured by the sun (e.g., elevation > 0; possibly the moon should be gibbous or full)

●    Azimuth of the sun = opposite of the azimuth of the moon (e.g., difference of 180 degrees between them)

●    Elevation of the sun = opposite of the elevation of the moon (e.g., same absolute value with opposite sign)

 

Eclipse (umbra and penumbra): E= earth, M =moon, , S =sun

 

Publishing to OneMediaHub

 

Funambol OneMediaHub is a very well developed native Symbian App, effectively functional and stable.

This chapter is a tutorial describing the step-by-step operations to install the appropriate software and configure it to publish tracks to OneMediaHub cloud service through Funambol Symbian client.

●    Access OneMediaHub and create a personal account.

●    Optionally, download and install the Windows App from the OneMediaHub web site, after accessing it with a valid user.

●    Open the Web Browser on your mobile phone and verify that the Internet access is ready (WiFi or Mobile Operator link).

●    Install is Funambol OneMediaHub 10.0.6 Symbian client to the phone device.

●    Update the application to the last version if suggested by a pop-up alert.

●    With the Funambol phone client app, login to the same personal account previously defined.

●    Enter the configuration options of the Funambol phone client app and set, disable or enable Contacts, Calendar, Notes, Images and Video synchronization, according to your preferences.

●    Select Files; set and enable Bidirectional Syncronization; select also the appropriate storage device where MrGPS will publish data (e.g., use the same storage drive adopted by MrGPS).

●    Select General and set Automatic synchronization for the appropriate data links

●    Open the standard Symbian file manager and verify that a directory named “Funambol MediaHub” is created in the drive configured with the Funambol phone client app

●    Open the standard Symbian file manager and verify that a directory named “Funambol MediaHub” is created in the drive configured with the Funambol phone client app

●    With MrGPS, access the “Data publishing” configuration submenu and set:

●    “Publishing feature” to Enabled

●    “Publishing process” to Copy

●    “Publishing folder name” to the full pathname of the folder name previously read with the Symbian file manager, possibly adding an appropriate subdirectory for MrGPS (e.g., “E:\Funambol MediaHub\MrGPS”).

●    “Select data to publish” to relevant files to be published (e.g., at least GPX tracks)

●    “Also copy hibernated data” to Disabled

 

How to record a track for subsequent play-back

 

MrGPS can exploit an external engineering tool developed by Nokia named Simulator_PSY to record a track than can be subsequently played back.

The track must be recorded in NMEA format.

 

Recording:

●    Open MrGPS, go to Options > Configuration > Edit settings > NMEA tab > “Sentences” and set all NMEA sentences active, but “GPZDA” and “Others”.

●    In the Output menu, set one fix per second and disable all auto-pausing settings.

●    GPS update [millisecs.]: 1000

●    Intervals: 1 sec.

●    Min. horizontal distance: none

●    Auto-pause(H. Speed): none

●    Auto-pause(H. + V. Speed): none

●    Auto-pause(H. Accuracy): none

●    Auto-pause(HDOP): none

●    Auto-pause(PDOP): none

●    Start tracking to NMEA and record a path

 

Playback:

●    Download and install Simulator PSY.

●    Download and install Symbian File Browser.

●    Run Symbian File Browser, browse the created NMEA file, rename it with nme extension and move it to c:\system\data

●    Open MrGPS, go to Options > Configuration > LBS Settings. Select “Simulation PSY”. Options, Settings, so that “Sim PSY FileName” is shown. Options, “Select config file”, choose the previously copied file. Return to the main screen.

Now the playback begins.

 

To stop the playback:

●    Open MrGPS, go to Options > Configuration > LBS Settings. Disable “Simulation PSY”.

 

Notes:

●    Simuator PSY does not like day 31 (or maybe only 31/12/2012 is not accepted); related NMEA tokens are $GPRMC,

●    Simuator PSY needs the following verbs: $GPGGA, $GPGSV, $GPRMC.

●    Simuator PSY is only able to send one NMEA line per second to the upstream driver, regardless the GPS time stored in the NMEA sentences; this means that Simuator PSY cannot produce any delay related to pauses or auto-pauses (that shall be avoided when a NMEA feed is recorded for subsequent playback via Simuator PSY).

 

Voice assistant

 

MrGPS includes an advanced and fully configurable voice assistant, which is capable to manage prompts, text-to-speech data and patterns in any sequence.

 

Prompts are pre-recorded clips which can be played out through a media player; MrGPS supports the following formats: Wave, AMR, MIDI, MP3, AAC, RNG and Real Audio. These files can be music clips, ringtones or prerecorded voices. To generate pre-recorded voices (e.g., wav or mp3 clips), you can either record your voice with a media recorder or exploit web sites provided with advanced text-to-speech capabilities, like Oddcast or many others.

 

Text-to-speech data are free text strings that are read by the speech synthesizer embedded into the Symbian phone. You can use punctuation to improve speech emphasis. See a previous paragraph (“Mr GPS installation and configuration guide”) to understand how to install and configure a TTS engine in your Nokia Symbian phone.

 

Patterns are special characters which are automatically expanded by MrGPS with an English string representing numeric value and related unit. Patterns include meta-characters and tokens. Patterns are then played by the TTS engine. See “Alerts” paragraph to understand how to use meta-characters and tokens.

 

MrGPS allows concatenating any sequence of prompts, text-to-speech and patterns into a single message.

 

Time signal voice assistant

 

MrGPS can be used as a time signal assistant, automatically telling the time at predefined intervals. Besides, time signal can be restricted to specific hours through the volume options for day-time and night-time.

 

The time signal feature does not require that the GPS is active, even if through the GPS it can benefit of the automatic phone time synchronization with satellite reference.

 

Activating the time signal.

 

Defining day time and night time.

 

Activating GPS time synchronization.

 

Synching time with sat reference

 

MrGPS supports phone time synchronization with the satellite reference. By default, this operation is executed after the manual confirmation to the related popped up panel.

 

 

Time sync is performed when answering “Yes” to this panel.

 

The automatic periodic synching can be set through Options > Configuration > Edit settings > Input device tab > “Auto sync time after”. For instance, you can set 10 seconds to be sure that the system time will always be synced with the GPS time when the two times differ of more than 10 seconds. A special option allows to always disabling sync.

 

Two additional settings allow to tune the sync process: “Sync shift” and “Time digits to sync”. See related description in the configuration menu panels.

 

Detailed description of each menu option

 

 

    Configuration (main menu)

 

This chapter details all options available in “Options > Configuration > Edit settings”.

 

When entering in one of the Settings submenu, left and right arrows allows moving forward or backward in submenus; up and down arrows select the specific option. Enter chanes the option values.

 

Available submenus: General, Input device, Display, Alerts, TTS Engine, Tuning, Notification lights, Output, Segmentation, Data publishing, NMEA, GPX, KML.

 

Menu – General

 

 

●    Shortcuts: Default is Selected. when enabled, the keyboard can be used to activate specific MrGPS functions; the shortcut help can be found in Options – Help – Shortcuts

Shortcuts can be disabled in order to avoid that unwanted keyboard pressures might produce incorrect commands. This setting requires hard keyboard (e.g., Nokia E6) and is useless in case the mobile device is only provided of soft keyboard (e.g., Nokia 5230).

 

●    Application type: System Application or Standard Application. Default is System Application. Select System Application in order to avoid that Symbian kills MrGPS in case of low phone resources or when pressing the End key (the phone red key). Setting Standard Application, the phone red key (end key) kills MrGPS, while with “System Application” the red key puts MrGPS to background (keeping the application active).

 

●    Task Icon: Show or Hide. Default: Show. This option allows to hide MrGPS from the Task list. In case MrGPS runs in background and is not visible in the Task List, simply select it from the application menu to restore it to foreground.

 

●    Auto-unlock Keypad: Never, With valid record, When updating position, With recording started, Always (default). Option controlling the phone keyboard auto-lock behavior when the application is in foreground. MrGPS can avoid screensaver activation when a valid fix is received, or when the device is in movement or when recording is active. When MrGPS is in background, the key-lock is not influenced.

 

●    Show toolbar: Show (default) or Hide, Depending on Symbian version, the soft toolbar is composed of:

●    The three centre soft buttons of the five keys Symbian Belle toolbar, or

●    a three button bar above the menu bar (Symbian s60v5),

●    or is not available (old Symbian versions).

Toolbar allows to easily select the most common commands through a simple soft-key pressure, without navigating the menus. Disabling the toolbar allows a wider screen area for data and avoids unwanted pressures of related toolbar soft keys.

 

●    Double click: Disabled, Enabled, Tag current position, Blank/restore toolbar, Play message. This option allows controlling the action related to double clicking the screen area (for phones provided with a soft-keyboard) or by pressing the centre hard key of the phone (for phones with a hard keyboard).

●    Setting this option to “Disabled” prevents unwanted actions in case of accidental key pressure or double clicks.

●    When “Enabled”, it acts as the toolbar centre soft key: when recording is not active, starts it; when recording is active, toggles pause/record.

●    “Tag current position”: when recording is not active, starts it; when recording is active, it has the same behavior as Options > “Tag current position”.

●    “Blank/restore toolbar”: on Symbian s60v5 phones, toggles blanking the menu bar (menu bar can be blanked to avoid accidental soft-key pressure)

●    “Play message”: plays the sequence described in Menu, Alerts, “Alert double click”. This is the most commonly used option as it provides an effective short-cut to listen to trip data (ref. configuration of “Alert double click”) via text-to-speech (e.g., altitude, travelled distance, current time, etc.).

 

Tip: in order to switch off the toolbar and disable the menu bar on Symbian s60v5 phones with soft keyboard (e.g., Nokia 5230), set General, “Show toolbar” to Hide and Double Click to “Blank/restore toolbar”. Then double click the screen.

 

Menu – Input device

 

 

 

●    Positioning method: selecting [Info on all modules, a pop-up window appears, listing all available GPS modules. This setting allows to show the default configured module and to configure a different GPS module than the default one. For instance, you can force to use A-GPS or to avoid using assistance.

Example:

1.      Assisted GPS (internal GPS device including wireless assistance via mobile network).

2.      Integrated GPS (internal GPS device without assistance)

3.      Wi-fi/Network (imprecise positioning performed via IP network)

4.      etc.

Select Integrated GPS when you are using MrGPS without a SIM or with your phone set to off-line (this will reduce battery consumption, will not need an active SIM but takes minutes to get the initial satellites lock). Select Assisted GPS if your phone is connected to a mobile network with data traffic active (this will highly speed up the initial satellite lock).

 

●    GPS Update (milliseconds): this is an important setting allowing to tune the internal GPS update period, which is useful to control GPS resolution; use 1 second in normal cases; when using the internal GPS device, you can reduce updates (to save resources) or even increase them to i.e. 500 milliseconds for very precise resolution in case of high speed movements or e.g. for race competitions. Notice that this period shall be lower or equal to “Output” Intervals (check “Output” configuration menu and related parameters). Besides, this period is dependent on the actual GPS hardware characteristics and related communication method; for instance, there is no advantage to apply 500 milliseconds resolution with an external Bluetooth GPS device providing updates every second.

 

●    GPS Timeout (milliseconds): this parameter controls the timeout while waiting for a fix from the selected GPS module. The value shall be significantly higher than “GPS Update” parameter.

 

●    Auto sync time after (seconds): this feature enables the automatic synchronization of phone time with GPS time when the time shift is greater than the indicated seconds. Setting the value to 0, enables a sync time query, so that the user is queried to sync time after the first satellites lock (notice that “Alert, Reminder alert for query” is also played when asking for confirmation to sync time). Setting the value to a negative value or to 100000 is a special option to always force disabling sync.

 

●    Sync shift [+/- tenths seconds]: adds a positive or negative time shift to the GPS time before syncing the phone.

 

●    Time digits to sync: valid options are All (default sat.), Do not use sat., Only sat. seconds, Only seconds and minutes, Secs, mins and hours, Day and time, Month, day and time. This feature allows managing glitches of some external GPS modules, which do not correctly manage the GPS date and time. For instance, Syscell SYBTGPS480 GPS Bluetooth adapter sets time to an incorrect year.

●    “All” means that all time digits acquired by the GPS are used to sync the clock time; this is the default option and is appropriate for the internal GPS module.

●    “Do not use sat.” read time form the phone instead of from the GPS and sync phone with this time (sync shift is applied).

●    “Only sat. seconds” can be used in case minutes, hours and date fetched by an external GPS module are wrong, while seconds are correct.

●    “Only seconds and minutes” can be used in case hours and date fetched by an external GPS module are wrong, while seconds and minutes are correct.

●    “Secs, mins and hours” can be used in case date fetched by an external GPS module is wrong, while time is correct.

●    “Day and time” can be used in case month and year fetched by an external GPS module are wrong, while time and day are correct

●    “Month, day and time” can be used in case year fetched by an external GPS module is wrong, while time, day and month are correct

 

●    NMEA input processing: default or Enhanced: default option relies on the internal NMEA processing provided by Symbian; it should be appropriate for most cases and is the correct option for the internal GPS module (for phones provided with GPS feature). When setting it to Enhanced, the default processing adds an extensible custom parser to the default Symbian internal algorithm, managing the following parameters: Satellite Geoidal Separation  (from $GPGGA), Magnetic Heading (from $GPVTG), True Course and Magnetic Course (from $GPRMC); to verify received GPS parameters, select Options > Tools > GPS Status; to check that GPS parameters are appropriately valued, you can compare them with the NMEA specifications of the external module; switch NMEA input processing to Enhanced in case MrGPS does not process the above listed parameters with default input processing option.

 

●    NMEA altitude: Geoid (default MSL), Ellipsoid; leave this option to Geoid (default) when using the internal GPS module for phones provided with GPS feature; this option allows managing a glitch of some external GPS modules, which incorrectly provide altitude; in case you realize that returned sea level altitude is always shifted of some metres (or better tenths metres), possibly the GPS module returns the ellipsoid altitude instead of the geoid one; in this case, Sea Level Altitude might be fixed by enabling Ellipsoid option.

 

●    Geoid separation: (default) or Calculated by application. Default option relies on the geoid separation parameter provided by the GPS (and shall be the selected one when using the internal GPS module). “Calculated by application” exploits a custom algorithm included in MrGPS that calculates the geoid separation (basing on coordinates and on a high level geoid terrestrial model) in place of the default GPS value; use this option to correct glitches of external GPS modules which wrongly report geoid separation (producing improper sea level altitudes) or do not provide it.

 

●    Altitude correction [+/- m]: this option applies a fixed shift to the sea level altitude returned by the GPS module (it might help correcting glitches of external GPS modules providing altitudes always shifted of a fixed number of metres; leave it to 0 when using the internal GPS module).

 

Menu – Display

 

 

 

●    Measurement system: metric, imperial, nautical metric, nautical imperial

●    Metric: distance in kilometres, speed in km/h, altitude in metres

●    Imperial: distance in yards or miles, speed in miles per hour, altitude in feet

●    Nautical metric: distance in kilometres, speed in knots, altitude in metres

●    Nautical imperial: distance in yards or miles, speed in knots, altitude in feet

 

●    Coordinate format: select disply notation for coordinates: "DDD°MM'SS.SS" (default), "DDD°MM.MMMM" or "DDD.DDDDD°".

 

●    Items: select the items shown in the main menu:

●    File name: name of the file used to log recording

●    Start time: date and time when recording started

●    Point: number of logged fixes (and log file size in parentheses)

●    Distance: total travelled distance

●    Duration: total trip duration

●    Longitude: current coordinate

●    Latitude: current coordinate

●    Ellipsoid Altitude: altitude of the WGS84 ellipsoid

●    Sea Altitude: altitude above the sea (SLM), referred to the geoid

●    Geoidal separation: difference between Ellipsoid Altitude and Sea Altitude

●    H. Speed(V. Speed): horizontal speed (with vertical speed in parentheses)

●    H. Speed: horizontal speed

●    V. Speed: vertical speed

●    Course: degrees

●    Magnetic Course: degrees

●    H.Acc(V.Acc): Horizontal accuracy (with Vertical accuracy in parentheses)

●    H. Accur: Horizontal Accuracy

●    V. Accur: Vertical Accuracy

●    H. DOP(V. DOP): Horizontal Dilution of Precision (with Vertical Dilution of Precision in parentheses)

●    H. DOP: Horizontal Dilution of Precision

●    V. DOP: Vertical Dilution of Precision

●    P. DOP: Positional (3D) Dilution of Precision

●    Sat. Num: number of satellites in use / number of satellites in view

●    Sat. Time: date and time returned by the GPS device

●    Sys. Time: date and time returned by the phone internal realtime clock

●    Trip avg speed: average speed of the trip excluding pauses, calculated as [total distance / (total trip time – total pauses)]

●    Duration w/o pauses: Trip duration excluding the total duration of pauses

●    Speed no Ldelay: Average speed of the trip, excluding timeframe related to pauses and to long delays

●    Duration w/o LDelays: total trip time, excluding timeframe related to pauses and long delays

●    Speed no delay: Average speed of the trip, excluding timeframe related to pauses, long and short delays (average speed, including stops and pull ups)

●    Duration w/o delays: total trip time, excluding timeframe related to pauses, long and short delays (trip period, including stops and pull ups)

●    Speed no stop: Average speed of the trip, excluding timeframe related to pauses, long delays, short delays and stops (this is the actual indication of the average moving speed)

●    Duration w/o stops: total trip time, excluding timeframe related to pauses, long delays, short delays and stops (this is the actual indication of the movement period)

●    Speed no pullup: Average speed of the trip, excluding all pauses, delays, stops and pull-ups (average speed when moving)

●    Duration w/o pullups: total trip time, excluding all pauses, delays, stops and pull-ups (moving time)

●    Total recording time: total duration of the trip, from start (or auto-start) to stop (or exit), including any stops and delays

●    Total pull-up time: sum of pull-up periods

●    Total stop time: sum of stop periods

●    Short delay time: sum of short delays

●    Long delay time: sum of long delays

●    Total pause time: sum of manual pause/resume intervals

●    Waypoints: number of recorded waypoints

●    Current slope: calculated slope (errors introduced by the GPS device when computing altitude might be sensible; these errors reflect slope precision; even if MrGPS includes a dynamic algorithm to normalize values, discarding improper altitude measures and taking into account enough distance to minimize deviations, current slope might sometimes be affected by imprecise figures)

●    Max. speed: maximum horizontal speed of the trip

●    Max. partial speed: maximum horizontal partial speed. Max speed and max partial speed are similar parameters, with separate reset tokens. Both can be manually reset and can also be configured to be automatically reset by specific alerts. You can for instance configure partial speed to be automatically reset at each stop, after playing the partial speed message.

●    Max. altitude msl: maximum sea level altitude

●    Min. altitude msl: minimum sea level altitude

●    Total vertical rise: total sum of increasing altitude differences

●    Total vertical drop: total sum of decreasing altitude differences

●    Max rising slope: max slope when raising

●    Max dropping slope: max slope when sloping

●    Travelled distance: total travelled distance

●    Time of last fix: time when last valid fix was logged (even if not recorded)

●    Previous fix time: time of the valid fix preceding the last one (even if not recorded)

●    Start rec. time: time when recording started

●    Last rec. time: time when the storage of the last fix was performed

●    Last pause time: time when last pause has been issued

●    Last stop time: time of last recorded stop

●    Last stop interval: last stop duration

●    Last interval: time interval between current valid fix and last valid fix

●    Last pause interval: time interval between last pause/resume

●    Last delay interval: duration of the last short or long delay

●    Time between tracks: time interval between last logged track and this track being logged (interval between stop and start)

●    Hibernation period: duration of the Hibernation period

 

●    Speed decimal digits: number of decimal digits shown for speed values.

 

●    Course decimal digits: number of decimal digits shown for course values.

 

●    Description font size: size of the font used for the description fields.

 

●    Value font size: size of the font used for the value fields.

 

●    Text color: color used for the text (avoid using the same color of the text).

 

●    Background color: color used for background (avoid using the same color of the text).

 

●    Min. dist. to calc. slope [m]: minimum logged distance enabling the slope calculation (this parameter minimizes the slope computation error when travelling too short distance; increasing this value reduces the probability of slope errors, but provides less sensibility to rapid slope changes).

 

●    Min. mins to show popups: when the trip starts (start button or auto-start), all popups are disabled until this timeframe (expressed in minutes) expires. Increasing this period avoids unwanted popups (like speed alerts) at the beginning of the trip recording, until cruise stabilizes.

 

●    Min. secs for new popup: after a popup is presented, all subsequent ones are disabled until this timeframe (expressed in seconds) expires. Increasing this period avoids too many pop-ups one after the other.

 

●    Show positioning method: (enabled/disabled). This parameter enables or disables a specific pop-up presented after the first fix, showing the used positioning method (disable this parameter if this popup is unwanted).

 

Menu – Alert

 

      

 

Volume controls:

●    Alert volume (day): day-time volume. This parameter can be also controlled through the volume keys during day time. E.g., set this value to 8/10 or to 10/10. Notice that by keeping the up volume key pressed, the volume directly goes to 8/10, while when keeping the down volume pressed, the volume goes to 0.

 

●    Night alert volume (day): night-time volume. This parameter can be also controlled through the volume keys during night time. E.g., set this value to 0/10 to disable volume during the night or set it to a low value (3/10). Notice that by keeping the up volume key pressed, the volume directly goes to 8/10, while when keeping the down volume pressed, the volume goes to 0.

 

●    Night volume start time: time of the day when night-time starts. E.g., 21:00.

 

●    Night volume end time: time of the day when night-time ends. E.g., 7:30. Night period begins at start time and ends one minute before end time. To avoid using night volume, set both start time and end time to 00:00 (more generally, setting start time and end time to the same value disables the time dependent volume feature).

 

General alert settings:

●    Activate alerts: Never, Only visual popups, Only in foreground, Always.

●    Never: alerts are always disabled

●    Only visual popups: speech alerts are disabled and only visual popups are enabled for the following alert messages: "Alert min altitude", "Alert max altitude", "Alert uphill", "Alert downhill", "Alert max speed", "A. max partial speed", "Alert no sat", "Alert locked sat ok".

●    Only in foreground: speech alerts and visual popups are enabled only when MrGPS is in foreground. In order to be compliant with Nokia directives, by default MrGPS is set to play sound and voice alerts only in this case, when the application is visible on the screen; if you conveniently need to also receive alerts when the application is in background, set “Activate alerts” to always.

●    Always: alerts are always enabled (this setting is suggested)

 

●    Allow alerts after [secs.]: to avoid spikes, alerts are stored for some seconds before being played; this improves information quality by only presenting useful alerts to the user. In order to achieve this, an internal algorithm queues alerts and controls the alert history, removing queued alerts when needed; for instance, in case a sat coverage issue arises an alert which is subsequently followed by a new successful lock within few seconds, both alerts are dropped. Similar example for max speed: if two max speed alerts happen within few seconds, only the last one is kept. “Allow alerts after” parameter controls this queuing period; increasing this value reduces the probability of unwanted alerts, but inserts a delay between the actual occurrence of the event and its notification. You might keep this value to 0 as default and, in case you receive too many consecutive notifications, you can set e.g. 5 (to 10) seconds. Alerts affected by this parameter are the following: "Alert min altitude", "Alert max altitude", "Alert uphill", "Alert downhill", "Alert max speed", "A. max partial speed", "Alert no sat", "Alert locked sat ok".

 

●    Alert Sat quality: available options: Never, With invalid fix, When sat state changes, When delay state ends, When long delay ends. This options control the activation/deactivation of the following alerts: “Alert no sat”, “Alert locked sat ok”, “Alert short delay”, “Alert long delay”.

●    Never: disables the following alerts: “Alert no sat”, “Alert locked sat ok”, “Alert short delay”, “Alert long delay”. Alerts related to missing satellite coverage, restored satellites and delays are all disabled.

●    With invalid fix: enables “Alert no sat”. The only enabled alert is related to missing satellite coverage.

●    When sat state changes: enables “Alert no sat” and “Alert locked sat ok”. The only enabled alerts are related to missing or restored satellite coverage. Use this option if you want to receive an alert when position is lost or reacquired.

●    When delay state ends: enables “Alert no sat”, “Alert locked sat ok”, “Alert short delay” and “Alert long delay”. Other than missing and restored satellite coverage alerts, also the short delay alert is enabled, notified when the short delay period ends.

●    When long delay ends: enables “Alert no sat”, “Alert locked sat ok” and “Alert long delay”. All related alerts are active; long delay is notified when the related period ends.

 

●    Beep pitch [Hertz]: base frequency for beep alerts. Depending on the selected alert, to distinguish one from the other, related beep frequency might be two or three times the base frequency.

 

●    Beep duration [millisecs.]: base duration for beep alerts. Depending on the selected alert, to distinguish one from the other, related duration might be two or three times the base duration.

 

Settings for altitude:

●    Alert on delta altitude [m]: altitude values are grouped in discrete steps with increments indicated by this delta altitude parameter, that allows configuring the number of metres to notify a new altitude; if set to e.g., 100 metres, related discrete levels are 100, 200, 300, …, 1500, 1600, …, 2300, 2400, 250, …; in this case, when passing from e.g. 90 metres to 110 metres, a notification is triggered. Suggested values are steps of 50 metres (when cycling or walking) or 100/200 metres (when driving). Alert messages related to this parameter are the following: “Alert small delta altitude”, Alert uphill delta altitude” and “Alert downhill delta altitude”. When a new altitude level is reached, depending on the actual slope, one of these three alert messages is activated. By differentiating messages according to slope, you can inhibit some of them (if wanted), or differentiate speech or also complement played altitudes (e.g., metres or feet) with elevation information (e.g., "new altitude uphill" or downhill).

 

●    Alert small delta altitude: alert message triggered when the next altitude step is reached (ref. “Alert on delta altitude” parameter) and in case slope is not enough to be considered uphill or downhill (this message might be simplified, just playing metres, or even disabled in normal cases).

Alert tokens are valid for this message.

Dollar (or dash) is substituted with the current altitude and related unit symbol (e.g., 100 m).

Example: “Altitude: $”

 

Alert uphill delta altitude: alert message triggered when the next altitude step is reached (ref. “Alert on delta altitude” parameter) and in case the current slope reports uphill direction. Alert tokens are valid for this message.

Dollar (or dash) is substituted with the current altitude and related unit symbol (e.g., 700 m).

Example: “New altitude uphill: $”

 

●    Alert downhill delta altitude: alert message triggered when the next altitude step is reached (ref. “Alert on delta altitude” parameter) and in case the current slope reports downhill direction.

Alert tokens are valid for this message.

Dollar (or dash) is substituted with the current altitude and related unit symbol (e.g., 900 m).

Example: “New altitude downhill: $”

 

●    Alert min altitude: alert message when the minimum MSL altitude is reached.

Alert tokens are valid for this message.

Dollar (or dash) is substituted with the current MSL altitude and related unit symbol (e.g., 500 m).

This alert is delayed by “Min. secs for new popup”.
Example: “Minimum altitude: $”

 

●    Alert max altitude: alert message when the maximum MSL altitude is reached.

Alert tokens are valid for this message.

Dollar (or dash) is substituted with the current MSL altitude and related unit symbol (e.g., 1200 m).

This alert is delayed by “Min. secs for new popup”.
Example: “Maximum altitude: $”

 

●    Alert uphill: this message is triggered upon every switch of slope from flat (or downhill) to uphill.

Alert tokens are valid for this message.

Dollar (or dash) is substituted with the current altitude and related unit symbol (e.g., 700 m).

This alert is delayed by “Min. secs for new popup”.
Example: “Altitude: $ uphill”

 

●    Alert downhill: this message is triggered upon every switch of slope from flat (or uphill) to downhill

Alert tokens are valid for this message.

Dollar (or dash) is substituted with the current altitude and related unit symbol (e.g., 1100 m).

This alert is delayed by “Min. secs for new popup”.
Example: “Altitude: $ downhill”

 

Settings for distance

●    Alert on delta distance [m]: distance to trigger the "Alert delta distance" message. Even if displayed messages can be kilometres or miles, this value must always be set with metres. If you set e.g. 5000 metres, messages are triggered when travelled distance reaches each multiple of this reference distance: 5 km, 10 km, 15 km, 20 km, 25 km, ...

 

●    Alert delta distance: this message is triggered every time the total distance reaches a multiple of the above reported parameter named "alert on delta distance [m]";

Alert tokens are valid for this message.

Dollar (or dash) is substituted with the current distance and related unit symbol (e.g., 25 km).

Example: “Travelled distance: $”

 

Settings for time

●    Alert on local time [mins]: delta time (referred to the local time expressed in hours and minutes) to notify an alert; when time reaches a multiple of minutes of this value, the alert named "Alert local time" is triggered. For instance, if set to 15, alert are triggered at 10:00, 10:15,10:30, 10:45, 11:00, 11:15, ...

 

●    Alert local time: Local time is triggered when minutes are multiple of “Alert on local time [mins]”.

Alert tokens are valid for this message.

Dollar (or dash) is substituted with the local time  with format based on the selected locale.

You can e.g. Introduce the message with a melody or a trill and then add a prompt like "it's". Example: “Z:\Data\Sounds\Digital\Topic.aac|It’s $”

 

●    Delta moving time: delta trip duration to notify an alert. Moving time excludes delays and stops from the total trip duration (but includes pull-ups). When the total moving duration of the trip expressed in minutes reaches a multiple of this value, the alert named "Alert delta moving time" is triggered. For instance, if set to 30, alerts are triggered at 30 minutes, 1 hour, 1 hour and 30 minutes, 2 hours, 2 hours and 30 minutes, 3 hours, ...

 

●    Alert delta moving time: Moving time excludes delays and stops from the total trip duration (but includes pull-ups). Alerts are triggered basing on “Delta moving time”.

Alert tokens are valid for this message.

Dollar (or dash) is substituted with the total moving time with format based on the selected locale. See {RecTime2} token to get the total trip time instead of the total moving time.

Example: “Trip duration: $”

 

Settings for speed

●    Alert max speed: alert triggered when reaching the maximum horizontal speed.
Alert tokens are valid for this message.

Dollar (or dash) is substituted with the maximum horizontal speed including unit symbol (e.g. 45 km/h, or 22 ml/h, or 15 knots). Use {ResetSpeed} to reset the maximum speed to 0.
This alert is delayed by “Min. secs for new popup”.
The parameter named "Speed decimal digits" is used to display the number of digits.

Example: “Maximum speed: $”

 

●    A. max partial speed: alert triggered when reaching the maximum horizontal partial speed. A very short message (or disabled message) is suggested.

Dollar (or dash) is substituted with the maximum partial speed including unit symbol (e.g. 45 km/h, or 22 ml/h, or 15 knots). Use {ResetPartialSpeed} to reset the maximum partial speed to 0.

Alert tokens are valid for this message.

This alert is delayed by “Min. secs for new popup”.

The parameter named "Speed decimal digits" is used to display the number of digits.

Example: “$”

 

Other alerts

●    Alert beginning a stop: alert triggered at each stop (with reference to the "Stop" parameter). A stop can be exploited to play a set of additional parameters that the user can listen with better attention than when moving. This alert will only be triggered if auto-pause options are configured.

Dollar (or dash) is not substituted with this alert.

Alert tokens are valid for this message.

Alert tokens are valid for this message.

Example: “{altitude2}|{distance2}|{MaxPartialSpeed2}|{ResetPartialSpeed}|{MovTime2}”

 

●    Alert ending a stop: alert triggered at each end of a stop, when moving begins (ref. "stop" parameter). This alert will only be triggered if auto-pause options are configured.

Dollar (or dash) is not substituted with this alert.

Alert tokens are valid for this message.

Example: “Moving now”

 

●    Reminder alert for query: this message is played when a query is prompted.

Dollar (or dash) is not substituted with this alert.

Alert tokens are valid for this message.

Example: “Attention. Answer question”

 

●    Alert no sat: alert triggered when satellite lock is lost.

Dollar (or dash) is not substituted with this alert.

Alert tokens are valid for this message.

This alert is delayed by “Min. secs for new popup”.

Example: “Position lost”

 

●    Alert locked sat ok: alert triggered when satellite lock is established again.

Dollar (or dash) is not substituted with this alert.

Alert tokens are valid for this message.

This alert is delayed by “Min. secs for new popup”.

Example: “Position acquired”

 

●    Alert short delay: alert triggered when a short delay happens.

Dollar (or dash) is not substituted with this alert.

Alert tokens are valid for this message.

Example: “Moving after short stop”

 

●    Alert long delay: alert triggered when a long delay happens.

Dollar (or dash) is not substituted with this alert.

Alert tokens are valid for this message.

Example: “Movement restarted after long stop”

 

●    Alert double click: alert occurring when double clicking the touch screen or when pressing the enter key (appropriate parameter "Double click" must be set to "Play message"). This alert can be exploited to play a set of useful parameters that the user can listen in sequence.

Dollar (or dash) is not substituted with this alert.

Alert tokens are valid for this message.

Example: “{altitude2}|{distance2}|{MaxPartialSpeed2}|{ResetPartialSpeed}|{MovTime2}|{LocTime}”

 

●    Alert charger on: alert occurring each time the charger is connected to the phone. This alert can be used to perform specific actions (like starting the recording).

Dollar (or dash) is not substituted with this alert.

Alert tokens are valid for this message.

Example: “{break}|{startgpx}”

 

●    Alert charger off: alert occurring each time the charger is disconnected from the phone. This alert can be used to perform specific actions (like starting the recording).

Dollar (or dash) is not substituted with this alert.

Alert tokens are valid for this message.

Example: “{break}|{stop}”

 

●    Low battery level [%]: this parameter sets the battery level to enable the alert named “Alert low battery”. All levels above this value inhibit the “Alert low battery” alert.

 

●    Alert low battery: when battery level is below “Low battery level [%]” value, an alert is triggered each time the level changes.

Dollar (or dash) is substituted with the battery level (0 to 100).

Alert tokens are valid for this message.

Example: “Attention. Battery: $%”

 

●    Translation table: in order to allow effective speech quality, this table allows converting symbols into text and also provides a way to correct improper messages. This table is applied to all messages delivered to the Text-To-Speech engine. The format is a multiline list of conversions where each element is represented in the form:

      symbol=converted text.

Symbols used by MrGPS are the following:

●    Time:

●    <no data>

●    days

●    hours

●    minutes

●    seconds

●    Distance:

●    ft

●    yd

●    m

●    mi

●    ml

●    km

●    mi

●    Speed:

●    mph

●    knots

●    km/h

●    Plurals to singular (use translated form):

●    1 days

●    1 hours

●    1 minutes

●    1 seconds

●    1 kilometres

●    1 metres

Example of translation table for English language:

km/h=kilometres per hour

<no data>=missing information

mph=miles per hour

kn=miles per hour

km=kilometres

ml=miles

mi=miles

yd=yards

ft=feet

days=days

hours=hours

minutes=minutes

seconds=seconds

1 days=1 day

1 hours=1 hour

1 minutes=1 minute

1 seconds=1 second

1 miles=1 mile

1 knots=1 knot

1 yards=1 yard

1 feet=1 foot

m=metres

1 kilometres=1 kilometre

1 metres=1 metre

Example of translation table for Italian language:

km/h=chilometri all’ora

<no data>=dato mancante

mph=miglia all’ora

kn=miglia all’ora

km=chilometri

ml=miglia

mi=miglia

yd=iarde

ft=piedi

days=giorni

hours=ore

minutes=minuti

seconds=secondi

1 days=1 giorno

1 hours=1 ora

1 minutes=1 minuto

1 seconds=1 secondo

1 miles=1 miglio

1 knots=1 miglio all’ora

1 yards=1 iarda

1 feet=1 piede

m=metri

1 kilometres=1 chilometro

1 metres=1 metro

 

Menu – TTS Engine

 

 

Restart application after changing these values

 

●    TTS Module: this parameter allows setting the most appropriate TTS engine to play texts.

●    Disabled: TTS engine is not loaded; no text-to-speech message is played

●    Fixed: Usage of the TTS language related to the selected locale; in case the phone setting for the TTS (Menu Settings, Phone, TTS) is configured for a different language, this configuration is ignored.

●    Default: Usage of the language defined in the phone TTS configuration (Menu Settings, Phone, TTS). Notice that the volume level with this setting might be slightly lower than with the “Fixed” setting, so use “Fixed” as the default setting and, in case your phone locale language is different form TTS language (e.g., English phone locale different from French TTS language), use “Default”.

●    Module 1: force usage of TTS module 1 (Nokia engine, in case this is the installed one)

●    Module 2: force usage of TTS module 2 (to be used in case other phone engines are installed e.g. from different produces than the default Nokia engine)

●    Module 3: force usage of TTS module 3 (to be used in case other phone engines are installed e.g. from different produces than the default Nokia engine)

●    Module 4: force usage of TTS module 4 (to be used in case other phone engines are installed e.g. from different produces than the default Nokia engine)

 

●    Decimal point: this parameter controls the usage of the decimal symbol in numeric patterns, required for a correct TTS speech of numbers.

●    Use default: keep the decimal symbol defined in the locale settings of the phone configuration

●    Force point: force usage of point as decimal symbol

●    Force comma: force usage of point as decimal symbol

 

Menu – Tuning

 

 

 

Restart application after changing these values

 

●    Snapshot period [secs.]: MrGPS periodically saves real time statistics by performing a snapshot than can be loaded by a subsequent MrGPS instance in case of battery failure, phone crash or other unexpected events. This process is completely unattended and can be tuned or disabled through this parameter. Setting the number of seconds for each snapshot allows configuring the granularity of this process. Setting the value to zero disables the service. Suggested values are 30 to 240 seconds.

 

●    Max samples to calc. slope: MrGPS includes an internal proprietary slope stabilizer implemented through an algorithm that can be tuned; this parameter sets the max size of the internal history matrix used to calculate slope. The next two parameters tune the actual size of this matrix, balancing slope responsiveness with accuracy.

 

●    History reduction factor: the actual size of the matrix is automatically calculated basing on speed, distance and a tuning reduction factor. This parameter allows defining a factor identifying the minimum number of history elements to calculate a valid slope. The higher this value, the higher the probability slope values are marked as inaccurate.

 

●    History distance factor: this parameter sets influence of speed when calculating history reduction. At lower speed, slope is affected by reduced responsiveness to provide enough accurate values.

 

●    Min. inverse alt. [m]: this parameter allows tuning the minimum inverse altitude to change the vertical direction (regardless slope deviation).

 

●    Min. inverse slope [%]: this parameter allows tuning the minimum inverse slope to change the vertical direction (regardless altitude).

 

●    Delta alt to update border altitude [m]: this parameter sets the minimum difference of altitude to accept an update of max or min altitude values.

 

●    Delta alt to trigger alert [m]: this parameter sets the minimum difference of altitude to trigger alerts.

 

Menu – Notification Lights

 

 

●    Notification Lights: MrGPS allows visual monitoring of active logging through notification lights, which can drive different physical LEDs depending on the phone model. Upon each acquired and recorded fix, one or more LEDs flicker (switching on and off) or “breath” (fading in and out) for visual indication of successful logging and an option also allows signalling missing satellite reception through a different pattern.

In order to define the most appropriate target lighting device (or devices) for the selected phone model, this setting lists available targets and combinations; only a part of them are physically available on specific phones. Notice that the more LEDs are driven, the higher the battery consumption. It is suggested to select single LEDs like the green, white and red hard keys or the LED next to the USB port, if available. If a selected option is not compliant with the phone hardware, the setting is immediately reset to “No notification light”.

●    No notification light: with this option, the notification light feature is disabled.

●    Primary Display: Primary display backlights of the device.

●    Primary Keyboard: Primary keyboard backlights of the device; this is device dependent, for those devices provided with retro-illuminated hard keyboard.

●    Primary Display and Keyboard: Both primary display and the primary keyboard backlights of the device; this is device dependent, for those devices provided with retro-illuminated hard keyboard.

●    Secondary Display: Secondary display backlights of the device; this is device dependent, for those devices provided with a secondary display.

●    Secondary Keyboard: Secondary keyboard backlights of the device; this is device dependent, for those devices provided with a secondary retro-illuminated hard keyboard.

●    Secondary Display and Keyboard: Both secondary display and the secondary keyboard backlights of the device; this is device dependent, for those devices provided with a secondary display and secondary retro-illuminated hard keyboard.

●    Notification Light for some phones: Led indicator on the top left corner for phones provided with this light; existence and position of this led depends on the mobile phone; on N8 it is the white charging battery LED next to the USB port.

●    Breathing Light for some phones: Special effect of a device dependent indicator; in N8 phones, this is the menu button light, appearing as fade in / fade out.

●    Notification Light for other phones: Other special effect of a device dependent indicator; in N8 phones, this is the menu button light, blinking like when you have a missed call / missed SMS.

●    Breathing Light for other phones: Another special effect of a device dependent indicator; in N8 phones, this is the menu button light, just on, without any other light effects on it..

●    Green & White notification keys: this is the sum of the last two effects (“Breathing Light for some phones” and “Notification Light for other phones”); phones with three retro-illuminated keys like 5230 (e.g., green, white and red hard keys under the soft keyboard, left to right) produce the blinking green and white keys.

●    Green, White and Error notification keys (default): this is the same as the previous effect (“Green & White notification keys”), with two kinds of notifications; in case of successful fix, both keys blink (like the previous effect) and, in case of satellite coverage error, only the central white key breathes (e.g., fades in and out repeatedly).

 

●    Notification Duration [millisec.]: duration of each led pulse, expressed in hundredths of second; the wider this period, the higher the battery consumption.

 

●    Notification Light Intensity (0 to 10): LED luminosity control; high values are suggested for a clear and visible status notification.

 

●    Notification Light Fading (disabled or enabled): selection of flickering method (light fading disabled with usage of on/off pulses) or breathing method (light fading enabled through fading in/out pulses).

 

Menu – Output

 

  

 

●    Autostart: This parameter controls the action automatically performed by MrGPS after starting the application, as well as the behaviour of the start soft-key.

●    Disabled: when MrGPS starts, the logging status is set to idle and recording must be manually started through the “Start Now” or “Schedule start” menu options (these options also allow to select the logging format, which can be GPX, NMEA or KML; GPX is strongly suggested); in case the “Start” soft key is pressed, a pop-up menu allows selecting the logging format (GPX is strongly suggested). This option is useful when the A-GPS method (providing fast GPS lock) is not selected or when the mobile phone runs MrGPS without a SIM; in this case, starting MrGPS some minutes in advance to the trip allows the GPS device to lock satellites before the trip starts.

●    NMEA: select autostart option with NMEA logging. When MrGPS starts, NMEA logging is automatically activated; besides, the start soft-button automatically runs NMEA logging.

●    GPX: select autostart option with GPX logging. When MrGPS starts, GPX logging is automatically activated; besides, the start soft-button automatically runs GPX logging.

●    KML: select autostart option with KML logging. When MrGPS starts, KML logging is automatically activated; besides, the start soft-button automatically runs KML logging.

 

●    Memory in use: This parameter is enabled when MrGPS is in idle state (not recording). Select the most appropriate memory device to store logs, statistics and configuration. A “Drive Info” option allows listing all available storage devices showing total and free space sizes. Using Mass Memory or Memory card (when these are available) is strongly suggested than Phone memory.

 

●    Root folder: This parameter is enabled when MrGPS is in idle state (not recording). With reference to the selected memory (ref. previous settings named “Memory in use”), select the most appropriate root folder to store logs, statistics and configuration. Default is using “Others” directory. If some directory within the configured path does not exist, MrGPS automatically creates it.

 

●    Subfolder: This parameter is enabled when MrGPS is in idle state (not recording). With reference to the selected memory (ref. previous settings named “Memory in use”) and root folder (ref. previous settings named “Root folder”), select the most appropriate subfolder to store logs, statistics and configuration. Default is using “MrGPS” directory. For instance, GPX logs are created in {Memory in use}:\{Root folder}\{Subfolder}\{filename}.gpx, e.g., C:\Data\Others\MrGPS\20190128220131-Wpt.gpx. If some directory within the configured path does not exist, MrGPS automatically creates it.

 

●    Intervals (none, 1 sec., 2, 3, 4, 5, 10, 15, 20, 30 secs., 1 min., 90 secs., 2 mins.): default is 1 sec. Regardless the GPS update frequency, that is defined through the “GPS Update” parameter of the “Input device” configuration menu and sets the GPS resolution (also depending on the GPS hardware and related communication method), a fix is logged to the output file basing on rules defined through a number of output filtering parameters, including “Intervals”, “Min. horizontal distance” and all Auto-pauses. “Intervals” is a reference setting defining the maximum timeframe to log fixes and defines the minimum resolution time in case other filtering conditions occur. If set to null, timing is ignored and e.g., no fix is written in case a stop occurs as defined by the auto-pause parameters. If set to 1 min, a fix is always written every minute even if other filtering conditions are valid (like too low speed).

 

●    Min. horizontal distance (none, 10 m., 20, 25, 50, 100, 200, 250, 500, 1000 m.): default is none; this is an output filtering condition defining the minimum horizontal distance to write fixes.

 

●    Auto-pause(H. Speed) (none, < 1024 km/h, < 1 kmh, < 2, 3, 4, 5, 10, 20 km/h): default is none; this parameter defines the minimum horizontal speed to write fixes. This parameter shall be tuned in case of e.g. walking rather than driving. In case of actual speed lower than this definition, auto-pause filtering condition occurs.

 

●    Auto-pause(H. + V. Speed) (none, < 1024 km/h, < 1 kmh, < 2, 3, 4, 5, 10, 20 km/h): default is none: this is similar to “Auto-pause(H. Speed)” but basing on the speed vector composed of horizontal and vertical speed elements; use this configuration with attention, because the vertical speed accuracy is much lower than the horizontal speed precision and the resulting vector might be affected by possible vertical speed errors.

 

●    Auto-pause(H. Accuracy) (none, >= 10m, >= 20m, >= 30m, >= 40m, >= 50m, >= 100m): default is none: this parameter checks the horizontal accuracy parameter returned by the GPS device to define whether to use or discard a GPS fix; if the horizontal accuracy is lower than the defined parameter, the related fix is discarded and auto-pause filtering condition occurs.

 

●    Auto-pause(HDOP) (none, >= 2.0, 3.0, 4.0, 5.0, 6.0, 7.0o, 8.0, 9.0, 10.0, 20.0): default is none: this parameter allows controlling the error computed by the GPS device in relation to a fix and checks the Horizontal Dilution Of Precision (HDOP) parameter to define whether to use or discard a fix; if the accuracy is lower than the defined parameter, the related fix is discarded and auto-pause filtering condition occurs.

 

●    Auto-pause(PDOP) (none, >= 2.0, 3.0, 4.0, 5.0, 6.0, 7.0o, 8.0, 9.0, 10.0, 20.0): default is none: this parameter allows controlling the error computed by the GPS device in relation to a fix and checks the Positional (3D) Dilution Of Precision (PDOP) parameter to define whether to use or discard a fix; if the accuracy is lower than the defined parameter, the related fix is discarded and auto-pause filtering condition occurs.

 

●    Max horiz. speed [km/h] default is 450 km/h: this parameter allows discarding fixes where speed is higher than the defined value, so that improper speeds are not recorded; it helps fixing possible GPS errors reporting too high speeds in some improper cases.

 

●    Min vertical accuracy [m] default is 80 m: this parameter allows discarding fixes where altitude accuracy is lower than the defined value expressed in meters, so that improper altitudes are not discarded; it also helps reducing slope computation errors.

 

●    Statistics output file (disabled or enabled): default is Disabled. If this setting is enabled, when a logging is stopped, the related statistical data are saved to a file named with the same path and base name of the track and “-Stats.txt” extension (e.g., 20130223110602-Stats.txt).

 

●    Use DOS newlines: the newline format of all output files produced by MrGPS are all customizable; selecting DOS newlines is suggested for better file portability to Windows devices.

●    NMEA logs.

●    GPX logs.

●    KML logs.

●    GPX waypoints.

●    Statistics.

●    Settings export.

●    Save calendar.

 

●    UTF8 instead of Unicode: this option defines the file format used to save statistics and settings (UTF8 is the default setting); select the most appropriate format to review accented characters with your editor. Notice that GPX files are always written in UTF8 format.

●    Statistics.

●    Settings export.

●    Save calendar.

 

Menu – Segmentation

 

 

Segmentation is an advanced MrGPS feature which allows organizing GPX tracks into segments for better visual readability and statistical analysis. GPX segments are defined though the <trk> and <trkseg> tags; all GPX files must have at least one <trk> tag and one <trkseg> tag; anyway, multiple segments can be defined according to track conditions. Upon each new segment, the last fix is repeated to provide path continuity. MrGPS adopts the following rules:

●    Short delay: each time a short delay condition occurs, a new segment is added using the form: </trkseg><trkseg>; a waypoint is also added depending on the “waypoints” configuration of the GPX submenu.

●    Long delay: each time a long delay condition occurs, a new track and a new segment is added using the form: </trkseg> </trk> <trk> <cmt>Long delay</cmt> <trkseg>; a waypoint is also added depending on the “waypoints” configuration of the GPX submenu.

●    Manual pause: each time a manual pause and resume are operated, a new track and a new segment is added using the form: </trkseg> </trk> <trk> <cmt>Manual pause</cmt> <trkseg>; a waypoint is also added depending on the “waypoints” configuration of the GPX submenu.

●    Auto-pause: each time an auto-pause condition occurs, a new segment is added using the form: </trkseg><trkseg>; a waypoint is also added depending on the “waypoints” configuration of the GPX submenu.

 

●    Segments: this option controls the segmentation method adopted for GPX files. Default is Single segment.

●    Single segment: no segmentation added.

●    New seg. on resume: each pause/resume manual operation produces a new segment. Autopause conditions do not produce segmentation.

●    On resume and autopause: a new segment is produced for pause/resume manual operations and auto-pause conditions.

 

●    # autopauses to segment: default is 10. Number of consecutive auto-apuse conditions to create a new segment. For instance, if an auto-pause rule is configured for speed less than 3 km/h, in case 10 consecutive fixes match this condition, a new segment is created upon next not matching fix.

 

●    Short delay [secs.]: default is 30. This setting allows defining the short delay condition. If fixes are missing within this timeframe, a short delay condition occurs.

 

●    Long delay [secs.]: default is 600. This setting allows defining the long delay condition, greater than the short delay condition. If fixes are missing within this long timeframe, a long delay condition occurs.

 

●    Max hibernate [mins.]: default is 600 minutes (10 hours). Max period to accept to resume operation when MrGPS is found in hibernated configuration. In normal condition, hibernate operations are quicly followed by a resume; if, for example, the battery needs to be changed, after hibernating the configuration and performing the battery substitution, MrGPS is promptly restarted, continuing the suspended statistics. Anyway, if MrGPS is restarted after “Max hibernate” period (expressed in minutes), e.g., after one day, the recovery operation does not keep the same statistics and performs a “stop” sequence (which consolidates logs) followed by a “start” (which resets statistics and open a new log).

 

Menu – Data publishing

 

 

MrGPS Data Publishing is a feature defining a staging area where relevant data are moved or copied from the output directory of MrGPS (configurable from the “Output” configuration submenu) so that data can subsequently be published from this staging area by auxiliary applications: specifically, MrGPS Data Publishing works in cooperation with external publishing applications accessing the same staging area managed by MrGPS, which is populated through an intelligent algorithm, automatically copying or moving consolidated files; the external application can read files in the staging area to publish them to a cloud storage service. Data publishing is not strictly necessary, because Nokia Suite allows sharing phone folders through the Nokia Phone Browser (e.g., integrated with Windows Explorer). Anyway, Data Publishing enables additional use cases, with no necessity to interconnect the phone with the target device via USB or Bluetooth through Nokia Suite. A typical use case is to configure the internal mass storage as the MrGPS output folder and to also copy relevant data to the SD card, so that through a manual operation the SD card can be periodically removed from the phone and moved to an external device for sharing tracks with external applications or to upload them to internet web sites like OpenStreetMap. Another use case is to exploit a file sharing application such as WebDAV, SyncML or any personal cloud storage or file hosting service. In principle, any application able to perform file sharing via radio network, WiFi or USB can be virtually associated to MrGPS. Anyway, by now the only tested application is Funambol OneMediaHub 10.0.6. Check the related chapter to configure the integration between MrGPS and Funambol OneMediaHub.

 

●    Publishing feature (Disabled or Enabled): default is Disabled. If enabled, files selected with the “Select data to publish” option (subsequently described) are automatically published to the staging area of the mobile phone. If Disabled, the publishing process is not active.

 

●    Publishing process (Copy or Move): default is Copy. This setting defines whether files are copied from the MrGPS output directory to the publishing area, or moved. When files are moved, they are removed from the output directory after succesfull copy to the publishing area; this saves space and improves operation, especially in case the publishing area is bidirectionally synchronized with a remote resource, so that the remote folder or web site can be used to directly control the generated files; anyway, moving files exposes to the risk of improper manipulation of tracks via remote (e.g., remote deletion of relevant data by mistake).

 

●    Publishing folder name: default is “Publish”. This is the name of the publishing folder and accepts relative or absolute paths. Paths are relative to the output folder of MrGPS. Use relative path when the publishing folder can be a subdirectory of the output path, set via related parameters in the Output submenu (check “Memory in use”, “Root folder” and “Subfolder”); e.g., “Publish”, that is the default configuration; in this case logs are published in {Memory in use}:\{Root folder}\{Subfolder}\{Publishing foleder name}\{filename}.gpx, e.g., C:\Data\Others\MrGPS\Publish\20190128220131-Wpt.gpx. The absolute path allows publishing to a different directory and shall be configured starting form the disk letter followed by colon and the full target folder pathname, e.g., E:\Funambol MediaHub\MrGPS (in this example, data are published to E:\Funambol MediaHub\MrGPS, e.g., “E:\Funambol MediaHub\MrGPS\20190128220131-Wpt.gpx”. If some directory within the configured path does not exist, MrGPS automatically creates it. An error message is popped up in case a publishing operation fails (e.g., wrong publishing directory or missing target hard drive). Notice that absolute paths begin with the drive letter, followed by colon and with the directory tree, starting with a backslash and with each directory separated by backslash; spaces are accepted within file and directory names.

 

●    Select data to publish: this setting controls which data types shall be published. In case the synchronization is performed via radio link, filtering only relevant data improves performance and saves traffic.

●    NMEA logs.

●    GPX logs.

●    KML logs.

●    GPX waypoints.

●    Statistics.

●    Settings export.

●    Save calendar.

 

●    Also copy hibernated data (Disabled or Enabled): default is Disabled. In case of hibernation (which is a sort of data freeze to be continued after a resume operation), data cannot be considered consolidated, and so by default they are not published. Anyway, if you also want to publish data after an hibernation, set this option to Enabled; in this case, upon each hibernate operation, generated files are also published and, subsequently to a resume operation, they are automatically depublished. Notice that, as the hibernate operation shall be accomplished as soon as possible (e.g., resource or power supply leakage), adding the file publishing operation to an hibernation is not suggested as it might not be completed in time under some circumstances.

 

Menu – NMEA

 

 

MrGPS can produce track logs using NMEA, GPX or KML formats. Of them, GPX is the suggested output method. NMEA option will generate log files including NMEA 0183 sentences according to the ones acquired from the LBS (Location Based Services) subsystem. Current NMEA limitations versus GPX are detailed in the following bullets.

●    Missing waypoints and geotagging

●    Missing segmentation and related notes

●    Missing header and related notes

NMEA can be used to dump Bluetooth GPS output or to record all parameters generated by the internal GPS device. The related closeup functionalities when a track is ended are trivial and take very limited times. NMEA is robust to faults and does not generally need specific hibernation features.

 

●    File Name(Ext): default is nmea. This is the definition of the file name extension to be used for NMEA tracks. This setting is only shown when logging is stopped and allows to change the extension name used by MrGPS to log NMEA tracks. File names are in the form yyyymmddhhMMss.<extension>; e.g., 20130224140711.nmea (y=year, m=month, d=day, h=hour, M=minutes, s=seconds).

 

●    Sentences: default is all selected, but “Others”. This settings allow filtering the NMEA sentences received from the GPS device. The actual set of available sentences strictly depend on the GPS device (or by the internal driver of the built-in GPS device for phones provided with internal positioning chipset).

●    GPGGA(required). - Global Positioning System Fix Data

●    GPGLL - Geographic Position, Latitude/Longitude

●    GPGSA - GPS DOP and Active Satellites

●    GPGST - GPS pseudorange noise statistics

●    GPGSV - GPS Satellites in View

●    GPRMC - Recommended Minimum Specific GPS/TRANSIT Data

●    GPVTG - Track Made Good and Ground Speed

●    GPZDA - Time & Date

●    Others. Any other sentence generated by the GPS device.

 

Menu – GPX

 

 

 

GPX is the suggested output method and includes hibernation, related resiliency functions, waypoints, geotagging, segmentation, related notes, header and related notes. The related closeup functionalities when a track is ended takes seconds to get accomplished.

Adopted GPX version is 1.0 for feature compliance and for improved portability (MrGPS exploits tags inside <trkpt> (like speed) that are defined for GPX 1.0 but unfortunately not for GPX 1.1.).

GPX format is UTF8.

The GPX header also includes a reference to an external stilesheet named “gpx.xsl”, to be used for data transformation and rendering; a gpx.xsl file compatible with Internet Explorer 7, transforming the tracked itinerary into a browsable map, can be provided on demand; to implement the transformation, rename the GPX extension to XML and drag the file to Internet Explorer; gpx.xsl shall be in the same folder of the XML file.

 

●    File Name(Ext): default is gpx. This is the definition of the file name extension to be used for GPX tracks. This setting is only shown when logging is stopped and allows to change the extension name used by MrGPS to log GPX tracks. File names are in the form yyyymmddhhMMss.<extension>; e.g., 20130224140711.gpx (y=year, m=month, d=day, h=hour, M=minutes, s=seconds).

 

●    tags: through this option, GPX tags of the <trkpt> element can be enabled or disabled. Default is all selected, apart from “Use vertical speed”, which is discouraged as explained below.

●    Satellite time(required). This is the date/time information when the trackpoint was created, in the form “<time>2012-12-02T18:22:36Z</time>”.

●    Ellipsoid Alt(ele). If this checkbox is enabled, if SeaLevel is disabled and if Eliipsoid altitude is generated by the GPS, the elevation of the trackpoint expressed as ellipsoid altitude is written to the GPX file in the form “<ele>740.3</ele>”.

●    SeaLevel Alt(ele). If this checkbox is enabled and if this value is generated by the GPS (or computed by MrGPS according to data received by the GPS device), the elevation of the trackpoint expressed as SLM altitude is written in the GPX file in the form “<ele>706.6</ele>”. In case both Ellipsoid and SeaLevel altitudes are selected, the latter has precedence when both values are available and, if only the SeaLevel altitude is missing, the Ellipsoid one is used. Notice that <geoidheight> is not used.

●    course. If this checkbox is enabled, the heading in degrees is written to the GPX file, in the form “<course>356.80</course>”. Notiche that this value is the one returned by the GPS device and it is not mediated by the phone internal compass, in case the phone is provided of this tool).

●    speed. This is either the speed over ground (suggested) or the 3D vector speed, depending on the “Use vertical speed” checkbox; value is saved to the GPX file in the form “<speed>12.81</speed>”.

●    Use vertical speed. This parameter allows defining the speed vector used to set <speed> tags. If checked, the 3D vector is used; if unchecked, the horizontal speed over ground will be the adopted quantity: disabling vertical speed eliminates errors related to the GPS vertical speed computation (e.g., erroneous speeds or wrong big speed numbers might appear in GPX data if this parameter is checked).

●    fix. Type of GPS fix. If altitude is available, “<fix>3d</fix>” is written, otherwise “<fix>2d</fix>” is written.

●    sat. The number of satellites in use is written to the GPX file in the form “<sat>5</sat>”.

●    hdop. If returned by the GPS, HDOP (Horizontal Dilution Of Precision) is written to the GPX file in the form “<hdop>1.90</hdop>”.

●    vdop. If returned by the GPS, VDOP (Vertical Dilution Of Precision) is written to the GPX file in the form “<vdop>4.00</vdop>”.

●    pdop. If returned by the GPS, PDOP (Positional (3D) Dilution Of Precision) is written to the GPX file in the form “<pdop>4.40</pdop>”.

 

●    Waypoints: These checkboxes control the creation of waypoints within the GPX file. Default is all (but “Resume from autopause”) selected.

●    Start. Each time the GPX recording is started, a waypoint item is written to the GPX file with “<name>START</name>” tag.

●    Stop. Each time the GPX recording is stopped, a waypoint item is written to the GPX file with “<name>STOP</name>” tag.

●    Hibernate. Each time the GPX recording is hibernated, a waypoint item is written to the GPX file with “<name>HIBERNATE</name>” tag. This option is discouraged because the hibernate operation shall be accomplished as soon as possible in order to avoid GPX corruption e.g. when the phone is being switched off due to power outage. Anyway, in case of corrupted GPX, during the subsequent restart phase an automatic process attempts to recover the file before appending the “restart” tag.

●    Restart. Each time the GPX recording is restarted after an hibernate suspension, a waypoint item is written to the GPX file with “<name>RESTART</name>” tag.

●    Pause. Each time the GPX recording is manually paused, a waypoint item is written to the GPX file with “<name>PAUSE</name>” tag.

●    Resume from pausing. Each time the GPX recording is resumed from manual pausing, a waypoint item is written to the GPX file with “<name>RESUME</name>” tag

●    Man.position recording. Each time the geotag option is selected, a waypoint item is written to the GPX file.

●    Resume from autopause. Each time the GPX recording is resumed from autopausing, a waypoint item is written with “<name> (Repeated fix)</name>” tag. This feature might be only useful for debugging.

●    Long delay. Each time a long delay is identified, a waypoint item is written to the GPX file with “<name>DELAY</name>” tag.

 

●    Author: any string, documenting the author’s name and included in the “<author>” tag of the GPX header. For instance, “Amacri”. If the string is null, the related tag will not be included in the GPX file.

 

●    Email: any string, documenting the author’s email and included in the “<email>” tag of the GPX header. For instance, “Amacri@tiscali.it”. If the string is null, the related tag will not be included in the GPX file.

 

●    URL: any string, documenting the author’s URL and included in the “<url>” tag of the GPX header. For instance, “http://web.tiscali.it/macri/mrgps/”. If the string is null, the related tag will not be included in the GPX file.

 

●    URL name: any string, documenting the author’s site description and included in the “<urlname>” tag of the GPX header. For instance, “MrGPS - Official Web page”. If the string is null, the related tag will not be included in the GPX file.

 

●    Max size to embed wpt: default is 150000. MrGPS concurrently generates GPX waypoints and GPX tracks writing data in two different files, both opened in sequential write for maximum performance and minimum resource consumption. The track file is called yyymmddhhmmss.gpx (e.g., 20130224140711.gpx) and its related waypoint file is named yyymmddhhmmss-Wpt.gpx (e.g., 20130601221035-Wpt.gpx). When finishing the recording (e.g., stop key), a consolidation operation is attempted, to merge these two files into a single one; this operation takes time and its duration depends on the track file size. “Max size to embed wpt” defines the maximum file size of the GPX track (.gpx file) in bytes to enable the merge operation with its related waypoint file (-Wpt.gpx). If the operation is successful, a single file with the same name of the waypoint file includes all data (and the GPX track file is deleted); if conversely the merge operation is not performed, both files are completed and closed, so that they will be both made available in the output directory and will be optionally both published.

 

Menu – KML

 

 

Even if KML provides similar functionalities as GPX, MrGPS can produce simple KML logs, limited in functions as detailed in the following bullets.

●    missing waypoints and geotagging,

●    missing segmentation and related notes,

●    basic headers,

●    missing resiliency and hibernation/resume features.

To exploit all these functions, select GPX output format.

 

●    File Name(Ext): default is kml. This is the definition of the file name extension to be used for KML tracks. This setting is only shown when logging is stopped and allows to change the extension name used by MrGPS to log KML tracks. File names are in the form yyyymmddhhMMss.<extension>; e.g., 20130224140711.kml (y=year, m=month, d=day, h=hour, M=minutes, s=seconds).

 

●    Placemark(name): default is Point. Select the definition of the <Name> tag, which is child element of the <Placemark> tag. Possible values:

●    None.

●    Point.

●    TimeStamp(UTC).

●    TimeStamp(local).

 

●    Placemark(description): default is Point, Longitude, Latitude and Satellite Time(local). Select the definition of the <Description> tag, which is child element of the <Placemark> tag. Possible values:

●    Point.

●    Longitude.

●    Latitude.

●    Ellipsoid Altitude.

●    SeaLevel Altitude.

●    Horizontal Speed.

●    Vertical Speed.

●    Course.

●    Horizontal Accuracy.

●    Vertical Accuracy.

●    Horizontal DOP.

●    Horizontal DOP.

●    Position DOP.

●    Satellite Num.

●    Satellite Time(UTC).

●    Satellite Time(local).

 

 

Configuration files

 

MrGPS allows two types of configuration files:

●    Compiled configurations (DAT format, that cannot be edited and include the whole configuration set);

●    Configuration dumps (INI format, which can include a partial configuration set and can be edited with a text editor like notepad).

 

Compiled configuration files are written through the command Options > Configuration > “Save settings” and can be read through the command Options > Configuration > “Load settings”.

Each file includes a whole configuration set of MrGPS options.

 

Configuration dumps are written through the command Options > Configuration > “Export settings” and can be read through the command Options > Configuration > “Import settings”.

Each file includes a whole or partial set of configuration options defined with the INI file format.

 

INI configuration files are organized in sections and parameters; grouping parameters in sections is mandatory; INI files allow comments introduced by ‘#’ or ‘;’ TTSTranslate is a multiline string and each line is named TTSTranslate+n, where n is the line number starting from 0, which is omitted (TTSTranslate+n=TTSTranslate).

 

The default configuration dump of MrGPS is the following one (occurring after first installation or when resetting MrGPS through Options > Tools > “Reset config.”):

 

;Dump Configuration (MrGPS version 1.1)

;------------------

 

[CONFIGURATION_FORMAT]

CURRENT_VERSION = 44

LOADED_VERSION = 0

DATE = 16/06/2013 23:29:31

 

[GENERAL]

EnableShortcuts = 1

SystemApplication = 1

HideTask = 0

Unlock = 0

Toolbar = 0

DoubleClick = 0

 

[INPUT_DEVICE]

PositioningMethod = 0

GpsUpdateInterval = 1000

GpsTimeoutInterval = 30000

AutoSyncTime = 0

SyncTimeShift = 0

DigitsToSync = 0

ImprovedNmeaInput = 0

CorrectNmeaAltitude = 0

AltitudeGeoidCalc = 0

AltitudeShift = 0

 

[DISPLAY]

MeasurementSystem = 0

DisplayCoordinateFormat = 0

DisplayItems:0 = 1 ; File Name

DisplayItems:1 = 1 ; Start time

DisplayItems:2 = 1 ; Point

DisplayItems:3 = 1 ; Distance

DisplayItems:4 = 1 ; Duration

DisplayItems:5 = 1 ; Longitude

DisplayItems:6 = 1 ; Latitude

DisplayItems:7 = 1 ; Ellips.Alt.

DisplayItems:8 = 0 ; Sea. Alt.

DisplayItems:9 = 1 ; Geoidal Separation

DisplayItems:10 = 0 ; H. Speed(V. Speed)

DisplayItems:11 = 0 ; H. Speed

DisplayItems:12 = 0 ; V. Speed

DisplayItems:13 = 1 ; Course

DisplayItems:14 = 0 ; Magnetic Course

DisplayItems:15 = 0 ; H. Acc.(V. Acc.)

DisplayItems:16 = 1 ; H. Accur.

DisplayItems:17 = 0 ; V. Accur.

DisplayItems:18 = 0 ; H. DOP(V. DOP)

DisplayItems:19 = 0 ; H. DOP

DisplayItems:20 = 1 ; V. DOP

DisplayItems:21 = 1 ; P. DOP

DisplayItems:22 = 1 ; Sat. Num

DisplayItems:23 = 0 ; Sat. Time

DisplayItems:24 = 0 ; Sat. Time

DisplayItems:25 = 0 ; Trip avg speed

DisplayItems:26 = 0 ; Duration w/o pauses

DisplayItems:27 = 0 ; Speed no Ldelay

DisplayItems:28 = 0 ; Duration w/o LDelays

DisplayItems:29 = 0 ; Speed no delay

DisplayItems:30 = 0 ; Duration w/o delays

DisplayItems:31 = 0 ; Speed no stop

DisplayItems:32 = 0 ; Duration w/o stops

DisplayItems:33 = 0 ; Speed no pullup

DisplayItems:34 = 0 ; Duration w/o pullups

DisplayItems:35 = 0 ; Total recording time

DisplayItems:36 = 0 ; Total pull up time

DisplayItems:37 = 0 ; Total stop time

DisplayItems:38 = 0 ; Short delay time

DisplayItems:39 = 0 ; Long delay time

DisplayItems:40 = 0 ; Total pause time

DisplayItems:41 = 0 ; Waypoints

DisplayItems:42 = 0 ; Current slope

DisplayItems:43 = 0 ; Max speed

DisplayItems:44 = 0 ; Max partial speed

DisplayItems:45 = 0 ; Max altitude msl

DisplayItems:46 = 0 ; Min altitude msl

DisplayItems:47 = 0 ; Total vertical rise

DisplayItems:48 = 0 ; Total vertical drop

DisplayItems:49 = 0 ; Max rising slope

DisplayItems:50 = 0 ; Max dropping slope

DisplayItems:51 = 0 ; Travelled distance

DisplayItems:52 = 0 ; Time of last fix

DisplayItems:53 = 0 ; Previous fix time

DisplayItems:54 = 0 ; Start rec. time

DisplayItems:55 = 0 ; Last rec. time

DisplayItems:56 = 0 ; Last pause time

DisplayItems:57 = 0 ; Last stop time

DisplayItems:58 = 0 ; Last stop interval

DisplayItems:59 = 0 ; Last interval

DisplayItems:60 = 0 ; Last pause interval

DisplayItems:61 = 0 ; Last delay interval

DisplayItems:62 = 0 ; Time between tracks

DisplayItems:63 = 0 ; Hibernation period

SpeedDigits = 2

CourseDigits = 2

FontDescrSize = 115

FontValSize = 210

TextColor = -1

BackgroundColor = -1

MinDistSlope = 80

MinTimePopup = 1

MinTimeNewPopup = 5

ShowPosMethod = 1

 

[ALERTS]

AlertMode = 2

BeepSat = 0

BeepFreq = 880

BeepDuration = 50

BeepVolume = 6

TimeDependentVolume = 0

VolumeStartTime = 00:00

VolumeEndTime = 00:00

BeepAfter = 5

NotifyAltitude = 0

NotifyDeltaAltitude = 1

NotifyDeltaAltitudeUpHill = 1

NotifyDeltaAltitudeDownHill = 1

NotifyMinAltitude = 0

NotifyMaxAltitude = 0

NotifyUpHill = 0

NotifyDownHill = 0

NotifyDistance = 0

NotifyDeltaDistance = 0

AlertLocalTime = 0

NotifyLocalTime = 0

NotifyMovingTime = 0

NotifyDeltaTime = 0

NotifyMaxSpeed = 0

NotifyMaxPartialSpeed = 0

NotifyEnterStop = 0

NotifyExitStop = 0

NotifyQuery = 1

NotifySatFail = 1

NotifySatOk = 1

NotifyShortDelay = 1

NotifyLongDelay = 1

NotifyDoubleClick = 0

NotifyChargerOn = 0

NotifyChargerOff = 0

LowBatteryLevel = 20

NotifyLowBattery = 0

TTSTranslate = km/h=kilometres per hour

TTSTranslate+1 = <no data>=missing information

TTSTranslate+2 = mph=miles per hour

TTSTranslate+3 = kn=miles per hour

TTSTranslate+4 = km=kilometres

TTSTranslate+5 = ml=miles

TTSTranslate+6 = mi=miles

TTSTranslate+7 = yd=yards

TTSTranslate+8 = ft=feet

TTSTranslate+9 = days=days

TTSTranslate+10 = hours=hours

TTSTranslate+11 = minutes=minutes

TTSTranslate+12 = seconds=seconds

TTSTranslate+13 = 1 days=1 day

TTSTranslate+14 = 1 hours=1 hour

TTSTranslate+15 = 1 minutes=1 minute

TTSTranslate+16 = 1 seconds=1 second

TTSTranslate+17 = 1 miles=1 mile

TTSTranslate+18 = 1 knots=1 knot

TTSTranslate+19 = 1 yards=1 yard

TTSTranslate+20 = 1 feet=1 foot

TTSTranslate+21 = m=metres

TTSTranslate+22 = 1 kilometres=1 kilometre

TTSTranslate+23 = 1 metres=1 metre

 

[TTS_ENGINE]

TtsModule = 0

TtsDecimalPoint = 0

 

[TUNING]

SnapshotPeriod = 20

MaxSamples = 40

ReductFactor = 2.50

DistanceFactor = 1.50

MinInverseQuote = 50

MinInverseSlope = 1.80

MinMinDeltaQuoteUpdMaxAlt = 3

MinDeltaQuotePlayNewVal = 10

 

[NOTIFICATION_LIGHTS]

DisplayLights = 0

DurationLights = 500

IntensityLights = 10

FadingLights = 1

 

[OUTPUT]

Autostart = 0

Memory = 1

Root = Others\

Directory = MrGPS\

Intervals = 1

Distance = 0

AutoPauseHorizontalSpeed = 0

AutoPauseSpeed = 0

AutoPauseHorizontalAccuracy = 0

AutoPauseHDOP = 0

AutoPausePDOP = 0

MinimumHorizontalSpeed = 450

MinimumVerticalAccuracy = 80

StatisticsEnabled = 0

CrNl:0 = 1 ; NMEA Logs

CrNl:1 = 1 ; GPX Logs

CrNl:2 = 1 ; KML Logs

CrNl:3 = 1 ; GPX Waypoints

CrNl:4 = 1 ; Statistics

CrNl:5 = 1 ; Settings export

CrNl:6 = 1 ; Save Calendar

Utf8:0 = 1 ; Statistics

Utf8:1 = 1 ; Settings export

Utf8:2 = 1 ; Save Calendar

 

[SEGMENTATION]

SegmentationOption = 0

NumberAutoPauseToSegment = 10

ShortDelay = 30

LongDelay = 600

MaxHiberbate = 600

 

[DATA_PUBLISHING]

PublishingEnabled = 0

PublishingMove = 0

PublishingFolder = Public

PublishingData:0 = 0 ; NMEA Logs

PublishingData:1 = 0 ; GPX Logs

PublishingData:2 = 0 ; KML Logs

PublishingData:3 = 0 ; GPX Waypoints

PublishingData:4 = 0 ; Statistics

PublishingData:5 = 0 ; Settings export

PublishingData:6 = 0 ; Save Calendar

PublishingHibernate = 0

 

[NMEA]

NMEAExt = nmea

NMEASentences:0 = 1 ; GPGGA(Required)

NMEASentences:1 = 1 ; GPGLL

NMEASentences:2 = 1 ; GPGSA

NMEASentences:3 = 1 ; GPGST

NMEASentences:4 = 1 ; GPGSV

NMEASentences:5 = 1 ; GPRMC

NMEASentences:6 = 1 ; GPVTG

NMEASentences:7 = 1 ; GPZDA

NMEASentences:8 = 0 ; Others

 

[GPX]

GPXExt = gpx

GPXTags:0 = 1 ; satellite time(Required)

GPXTags:1 = 1 ; Ellipsoid Alt.(ele)

GPXTags:2 = 1 ; SeaLevel Alt.(ele)

GPXTags:3 = 1 ; course

GPXTags:4 = 1 ; speed

GPXTags:5 = 0 ; Use vertical speed

GPXTags:6 = 1 ; fix

GPXTags:7 = 1 ; sat

GPXTags:8 = 1 ; hdop

GPXTags:9 = 1 ; vdop

GPXTags:10 = 1 ; pdop

GPXWpt:0 = 1 ; Start

GPXWpt:1 = 1 ; Stop

GPXWpt:2 = 1 ; Hibernate

GPXWpt:3 = 1 ; Restart

GPXWpt:4 = 1 ; Resume from pausing

GPXWpt:5 = 1 ; Man.position recording

GPXWpt:6 = 0 ; Resume from autopause

GPXWpt:7 = 1 ; Long delay

GPXAuthor =

GPXEmail =

GPXUrl =

GPXUrlName =

GPXFSize = 150000

 

[KML]

KMLExt = kml

KMLPmName = 1

KMLPmDescription:0 = 0 ; Point

KMLPmDescription:1 = 1 ; Longitude

KMLPmDescription:2 = 1 ; Latitude

KMLPmDescription:3 = 0 ; Ellipsoid Altitude

KMLPmDescription:4 = 0 ; SeaLevel Altitude

KMLPmDescription:5 = 0 ; Horizontal Speed

KMLPmDescription:6 = 0 ; Vertical Speed

KMLPmDescription:7 = 0 ; Course

KMLPmDescription:8 = 0 ; Horizontal Accuracy

KMLPmDescription:9 = 0 ; Vertical Accuracy

KMLPmDescription:10 = 0 ; Horizontal DOP

KMLPmDescription:11 = 0 ; Vertical DOP

KMLPmDescription:12 = 0 ; Position DOP

KMLPmDescription:13 = 0 ; Satellite Num

KMLPmDescription:14 = 0 ; Satellite Time(UTC)

KMLPmDescription:15 = 1 ; Satellite Time(Local)

 

Suggested configuration settings (filtering only relevant items):

 

[GENERAL]

Unlock = 4

DoubleClick = 4

 

[INPUT_DEVICE]

PositioningMethod = 1

AutoSyncTime = 10

 

[DISPLAY]

DisplayItems:1 = 0 ; Start time

DisplayItems:5 = 0 ; Longitude

DisplayItems:6 = 0 ; Latitude

DisplayItems:8 = 1 ; Sea. Alt.

DisplayItems:9 = 0 ; Geoidal Separation

DisplayItems:11 = 1 ; H. Speed

DisplayItems:16 = 0 ; H. Accur.

DisplayItems:22 = 1 ; Sat. Num

SpeedDigits = 1

CourseDigits = 0

MinDistSlope = 100

MinTimeNewPopup = 10

 

[ALERTS]

AlertMode = 3

BeepSat = 2

BeepFreq = 880

BeepDuration = 50

BeepVolume = 10

TimeDependentVolume = 2

VolumeStartTime = 22:00

VolumeEndTime = 07:30

BeepAfter = 0

NotifyAltitude = 100

NotifyDistance = 5000

AlertLocalTime = 15

NotifyMovingTime = 30

LowBatteryLevel = 50

 

[OUTPUT]

Autostart = 2

Memory = 2

Distance = 1

StatisticsEnabled = 1

 

[SEGMENTATION]

SegmentationOption = 2

NumberAutoPauseToSegment = 18

 

[DATA_PUBLISHING]

PublishingEnabled = 1

PublishingMove = 0

PublishingFolder = E:\Funambol MediaHub\MrGPS

PublishingData:0 = 1 ; NMEA Logs

PublishingData:1 = 1 ; GPX Logs

PublishingData:2 = 1 ; KML Logs

PublishingData:3 = 1 ; GPX Waypoints

PublishingData:4 = 1 ; Statistics

PublishingData:5 = 1 ; Settings export

PublishingData:6 = 1 ; Save Calendar

 

[GPX]

GPXExt = Gpx

GPXAuthor = Amacri

GPXEmail = Amacri@tiscali.it

GPXUrl = http://web.tiscali.it/macri/mrgps/

GPXUrlName = MrGPS – Official Home Page

GPXFSize = 4500000

 

Set fonts:

 

[DISPLAY]

FontDescrSize = 100

FontValSize = 210

TextColor = 16777215

BackgroundColor = -1

 

Automatically starts recording when in charge and stops recording when plugging off power supply:

This piece of configuration allows activating alerts when the phone is put in charge and when the power supply is plugged off; it is an example of configuring an external device able to control the phone charge and used to start and stop tracking.

[ALERTS]

NotifyChargerOn = {startgpx}

NotifyChargerOff = {stop}

 

English alert messages without prompts:

Options > Configuration > TTS Settings > English language

 

[TTS_ENGINE]

TtsModule = 0 ; set this to 1 if the language is not changed

TtsDecimalPoint = 1

 

[ALERTS]

NotifyDeltaAltitude = Altitude: $

NotifyDeltaAltitudeUpHill = New altitude uphill: $

NotifyDeltaAltitudeDownHill = New altitude downhill: $

NotifyMinAltitude = Minimum altitude: $

NotifyMaxAltitude = Maximum altitude: $

NotifyUpHill = Altitude: $ uphill

NotifyDownHill = Altitude: $ downhill

NotifyDeltaDistance = Travelled distance: $

NotifyLocalTime = Z:\Data\Sounds\Digital\Topic.aac|It's $ ; Verify that this file exists in your phone

NotifyDeltaTime = Trip duration: $

NotifyMaxSpeed = Maximum speed: $

NotifyMaxPartialSpeed = $

NotifyEnterStop = {altitude2}|{distance2}|{maxpartialspeed2}|{resetpartialspeed}|{movtime2}

NotifyExitStop = Moving

NotifyQuery = Attention. Answer question

NotifySatFail = Position lost

NotifySatOk = Position acquired

NotifyShortDelay = Moving after short stop

NotifyLongDelay = Movement restarted after long stop

NotifyDoubleClick = {altitude2}|{distance2}|{maxpartialspeed2}|{resetpartialspeed}|{movtime2}|{LocTime}

NotifyLowBattery = Attention. Battery: $%

TTSTranslate = km/h=kilometres per hour

TTSTranslate+1 = mph=miles per hour

TTSTranslate+2 = knots=miles per hour

TTSTranslate+3 = km=kilometres

TTSTranslate+4 = ml=miles

TTSTranslate+5 = mi=miles

TTSTranslate+6 = yd=yards

TTSTranslate+7 = ft=feet

TTSTranslate+8 = days=days

TTSTranslate+9 = <no data>=missing information

TTSTranslate+10 = hours=hours

TTSTranslate+11 = minutes=minutes

TTSTranslate+12 = seconds=seconds

TTSTranslate+13 = 1 days=1 day

TTSTranslate+14 = 1 hours=1 hour

TTSTranslate+15 = 1 minutes=1 minute

TTSTranslate+16 = 1 seconds=1 second

TTSTranslate+17 = 1 miles=1 mile

TTSTranslate+18 = 1 knots=1 knot

TTSTranslate+19 = 1 yards=1 yard

TTSTranslate+20 = 1 feet=1 foot

TTSTranslate+21 = m=metres

TTSTranslate+22 = 1 kilometres=1 kilometre

TTSTranslate+23 = 1 metres=1 metre

 

Italian alert messages without prompts:

Options > Configuration > TTS Settings > Italian language

 

[TTS_ENGINE]

TtsModule = 0 ; set this to 1 if the language is not changed

TtsDecimalPoint = 0

 

[ALERTS]

NotifyDeltaAltitude = Raggiunta nuova quota|$

NotifyDeltaAltitudeUpHill = Raggiunta nuova quota salita|$

NotifyDeltaAltitudeDownHill = Raggiunta nuova quota discesa|$

NotifyMinAltitude = Altezza minima|$

NotifyMaxAltitude = Altezza massima|$

NotifyUpHill = In salita|$

NotifyDownHill = In discesa|$

NotifyDeltaDistance = Raggiunta nuova distanza|$

NotifyLocalTime = Z:\Data\Sounds\digital\Xylophone.aac|Ore $ ; Verify that this file exists in your phone

NotifyDeltaTime = Superato periodo|$

NotifyMaxSpeed = Velocità massima|$

NotifyMaxPartialSpeed = $

NotifyEnterStop = In Sosta|{altitude2}|{distance2}|{maxpartialspeed2}|{resetpartialspeed}|{movtime2}

NotifyExitStop = In Movimento

NotifyQuery = Attenzione! Rispondi alla domanda

NotifySatFail = Posizione persa

NotifySatOk = Posizione agganciata

NotifyShortDelay = Moto ripreso dopo breve sosta

NotifyLongDelay = Moto ripreso dopo lunga sosta

NotifyDoubleClick = {altitude2}|{distance2}|{maxpartialspeed2}|{resetpartialspeed}|{movtime2}|{LocTime}

NotifyLowBattery = Attenzione, batteria al $%

TTSTranslate = km/h=chilometri all'ora

TTSTranslate+1 = km=chilometri

TTSTranslate+2 = days=giorni

TTSTranslate+3 = <no data>=dato mancante

TTSTranslate+4 = hours=ore

TTSTranslate+5 = minutes=minuti

TTSTranslate+6 = seconds=secondi

TTSTranslate+7 = 1 giorni=1 giorno

TTSTranslate+8 = 1 ore=1 ora

TTSTranslate+9 = 1 minuti=1 minuto

TTSTranslate+10 = 1 secondi=1 secondo

TTSTranslate+11 = m=metri

TTSTranslate+12 = 1 chilometri=1 chilometro

TTSTranslate+13 = 1 metri=1 metro

 

Italian alert messages and prompts (Italian prompt messages are required):

Options > Configuration > TTS Settings > Italian language

 

[TTS_ENGINE]

TtsModule = 0 ; set this to 1 if the language is not changed

TtsDecimalPoint = 0

 

[ALERTS]

NotifyDeltaAltitude = E:\Sounds\Digital\Raggiunta nuova quota.wav|$

NotifyDeltaAltitudeUpHill = E:\Sounds\Digital\Nuova quota salita.wav|$

NotifyDeltaAltitudeDownHill = E:\Sounds\Digital\Nuova quota discesa.wav|$

NotifyMinAltitude = E:\Sounds\Digital\Altezza minima.wav|$

NotifyMaxAltitude = E:\Sounds\Digital\Altezza massima.wav|$

NotifyUpHill = In salita|$

NotifyDownHill = In discesa|$

NotifyDeltaDistance = E:\Sounds\Digital\raggiunta nuova distanza.wav|$

NotifyLocalTime = Z:\Data\Sounds\digital\Xylophone.aac|Ore $ ; Verify that this file exists in your phone

NotifyDeltaTime = E:\Sounds\Digital\Superato periodo.wav|$

NotifyMaxSpeed = E:\Sounds\Digital\Velocità massima.wav|$

NotifyMaxPartialSpeed = $

NotifyEnterStop = E:\Sounds\Digital\In Sosta.wav|{altitude2}|{distance2}|{maxpartialspeed2}|{resetpartialspeed}|{movtime2}

NotifyExitStop = E:\Sounds\Digital\In Movimento.wav

NotifyQuery = E:\Sounds\Digital\Answer please.wav

NotifySatFail = E:\Sounds\Digital\Posizione persa.wav

NotifySatOk = E:\Sounds\Digital\Posizione agganciata.wav

NotifyShortDelay = E:\Sounds\Digital\Short delay.wav

NotifyLongDelay = E:\Sounds\Digital\Long delay.wav

NotifyDoubleClick = {altitude2}|{distance2}|{maxpartialspeed2}|{resetpartialspeed}|{movtime2}|{LocTime}

NotifyLowBattery = Attenzione, batteria al $%

TTSTranslate = km/h=chilometri all'ora

TTSTranslate+1 = km=chilometri

TTSTranslate+2 = days=giorni

TTSTranslate+3 = <no data>=dato mancante

TTSTranslate+4 = hours=ore

TTSTranslate+5 = minutes=minuti

TTSTranslate+6 = seconds=secondi

TTSTranslate+7 = 1 giorni=1 giorno

TTSTranslate+8 = 1 ore=1 ora

TTSTranslate+9 = 1 minuti=1 minuto

TTSTranslate+10 = 1 secondi=1 secondo

TTSTranslate+11 = m=metri

TTSTranslate+12 = 1 chilometri=1 chilometro

TTSTranslate+13 = 1 metri=1 metro

 

Specific customizations

 

●    Driving:

 

; Driving

[INPUT_DEVICE]

GpsUpdateInterval = 1000

[OUTPUT]

Intervals = 0; None

Distance = 5; 50 meters

AutoPauseHorizontalSpeed = 6; < 5 km/h

AutoPauseSpeed = 0; None

AutoPauseHorizontalAccuracy = 0; None

AutoPauseHDOP = 0; None

AutoPausePDOP = 0; None

 

●    Sailing:

 

; Sailing

[INPUT_DEVICE]

GpsUpdateInterval = 1000

[OUTPUT]

Intervals = 0; None

Distance = 2; 20 meters

AutoPauseHorizontalSpeed = 3; < 2 km/h

AutoPauseSpeed = 0; None

AutoPauseHorizontalAccuracy = 0; None

AutoPauseHDOP = 0; None

AutoPausePDOP = 0; None

 

●    Cycling:

 

; Cycling

[INPUT_DEVICE]

GpsUpdateInterval = 1000

[OUTPUT]

Intervals = 0; None

Distance = 2; 20 meters

AutoPauseHorizontalSpeed = 5; < 4 km/h

AutoPauseSpeed = 0; None

AutoPauseHorizontalAccuracy = 6; >= 100m

AutoPauseHDOP = 0; None

AutoPausePDOP = 9; >= 10.0

 

●    Walking:

 

; Walking

[INPUT_DEVICE]

GpsUpdateInterval = 1000

[OUTPUT]

Intervals = 0; None

Distance = 0; None

AutoPauseHorizontalSpeed = 2; < 1 km/h

AutoPauseSpeed = 0; None

AutoPauseHorizontalAccuracy = 6; >=100m

AutoPauseHDOP = 0; None

AutoPausePDOP = 9; >=10.0

 

●    Climbing:

 

; Climbing

[INPUT_DEVICE]

GpsUpdateInterval = 1000

[OUTPUT]

Intervals = 5; 5 secs

Distance = 0; None

AutoPauseHorizontalSpeed = 0; None

AutoPauseSpeed = 0; None

AutoPauseHorizontalAccuracy = 6; >=100m

AutoPauseHDOP = 0; None

AutoPausePDOP = 9; >=10m

 

●    Hiking:

 

; Hiking

[INPUT_DEVICE]

GpsUpdateInterval = 1000

[OUTPUT]

Intervals = 1; 1 sec.

Distance = 1; 10 meters

AutoPauseHorizontalSpeed = 3; < 2 km/h

AutoPauseSpeed = 0; None

AutoPauseHorizontalAccuracy = 6; >=100m

AutoPauseHDOP = 0; None

AutoPausePDOP = 9; >=10m

 

●    Racing:

 

; Racing

[INPUT_DEVICE]

GpsUpdateInterval = 500

[OUTPUT]

Intervals = 1; 1 sec.

Distance = 0; None

AutoPauseHorizontalSpeed = 0; None

AutoPauseSpeed = 0; None

AutoPauseHorizontalAccuracy = 0; None

AutoPauseHDOP = 0; None

AutoPausePDOP = 0; None

 

Tested mobile phones

 

To ensure compatibility of MrGPS with all Symbian phones starting from S60 3rd Edition, MrGPS version 1.2.1 has been installed and directly tested on the devices reported in the following test list:

●    Nokia Belle Feature Pack 2: Nokia 808 Pureview

●    Nokia Belle Feature Pack 1: Nokia 808 Pureview

●    Nokia Belle Refresh: Nokia N8-00

●    Other tested Nokia Belle phones: Nokia 808 Pureview, Nokia 603, Nokia Oro Belle, Vertu Constellation T Belle, Nokia E7-00 Belle, Nokia 701, Nokia 500 Belle, Nokia C6-01 Belle, Nokia C7-00 Belle, Nokia N8-00 Belle, Nokia X7-00 Belle, Nokia E6-00 Belle and Nokia 700

●    Symbian Anna/PS1: Nokia 702T, Nokia Oro C7-00s, Vertu Constellation T, Nokia 500, Nokia Oro, Nokia 801T, Nokia N8-00, Nokia E7-00, Nokia C6-01, Nokia C7-00, Nokia X7-00, Nokia C7 Astound, Nokia T7-00 and Nokia E6-00

●    Symbian^3: Vertu Constellation

●    S60 5th Edition: Nokia X6-00m, Nokia 5230, Nokia 5235, Nokia 5250, Nokia C5-04, Nokia N97 mini, Nokia X6, Nokia N97, Nokia 5228, Nokia 5530 XpressMusic, Nokia 5233, Nokia C6-00, Nokia 5800 XpressMusic and Nokia C5-03

●    S60 3rd Edition FP2: Nokia C5-00, Nokia N79, Nokia E52, Nokia N86 8MP, Nokia N96, Nokia E75, Nokia E72, Nokia E5-00 and Nokia 5320 XpressMusic

●    S60 3rd Edition FP1: Nokia E51, Nokia N82, Nokia N95, Nokia N95 8GB, Nokia E63, Nokia N81, Nokia E66, Nokia E71 and Nokia 6120 classic

●    S60 3rd Edition: Nokia N73, Nokia 3250, Nokia N93, Nokia E62, Nokia E61i, Nokia N80, Nokia E70

 

Notes related to Symbian operating system versions:

●    Nokia Belle Feature Pack 2: this version supports MrGPS with full capabilities, touchscreen and with Nokia Belle graphic toolbar; some softkeys in the right part of the toolbar are shown with transparent frame.

●    Nokia Belle Feature Pack 1: this version supports MrGPS with full capabilities, touchscreen and with Nokia Belle graphic toolbar.

●    Nokia Belle Refresh: this version supports MrGPS with full capabilities, touchscreen and with Nokia Belle graphic toolbar.

●    Nokia Belle: this version supports MrGPS with full capabilities, touchscreen and with Nokia graphic Belle toolbar.

●    Symbian Anna: this version supports MrGPS with full capabilities, touchscreen and standard Symbian character based toolbar.

●    Symbian^3: this version supports MrGPS with full capabilities, touchscreen and with standard Symbian character based toolbar.

●    S60 5th Edition: this version supports MrGPS with full capabilities, touchscreen and with standard Symbian character based toolbar.

●    S60 3rd Edition FP2: all capabilities of MrGPS allowed by this O.S. version are supported; no “Satellite Status” support; the s60v3FP2 middle key toolbar is accessible through numeric key “3”.

●    S60 3rd Edition FP1: this version supports MrGPS with some limitations, including no TTS, no Symbian “Satellite Status” shortcut, no Symbian “LBS Settings” shortcut, no toolbar (unsupported by this O.S. version).

●    S60 3rd Edition: this version supports MrGPS with some limitations, including no INI file support, no TTS, no Symbian “Satellite Status” shortcut, no Symbian “LBS Settings” shortcut, no toolbar (unsupported by this O.S. version).

 

Should you have any question on MrGPS support with your phone, do not hesitate to drop me an email.

 

Afterword

 

I started developing MrGPS when I realized that all the functionalities of Event_Logger for TomTom could also be implemented into smaller and cheaper Nokia mobile phones, also exploiting the quality and robustness of those devices.

 

MrGPS has been designed with robustness and reliability in mind, to become a rugged assistant for demanding use cases.

 

No compromise has been be made on MrGPS architecture, adopting the most appropriate techniques to maximize performance and minimize resource consumption. Coding MrGPS took me years of work and hundreds of test cases.

 

Studying feedbacks form testers and analyzing their comments, I translated their requests into dynamic algorithms supported by specific configuration settings, always verified through iterative revisions and tunings, with a constant and determined goal to address, meet and often outperform the most demanding requirements.

 

This version of MrGPS, which has been released to Nokia Store, encompasses all this work. If you are searching for some specific functions, you might succeed to find them within its wide configuration management.

                                                                                                                                                                                          

MrGPS is your reliable and comprehensive GPS assistant and tracker. The ideal target of MrGPS is to become your inseparable tool when tracking and travel assistance become important for your most exciting sport performances.

If you wish to donate, please, select the option you consider most appropriate:

MrGPS: donate €8,00 EUR MrGPS: donate €10,00 EUR MrGPS: donate €15,00 EUR

Enter your phone IMEI here:

Enter your email here: