Thread: iGO sys editor

iGO Sys Editor — Feature Overview

Core database

514 parameters across 24 categories, covering all three engine variants: nextgen_32, luna_64, luna_32
Every parameter carries: name, section, default value, list of valid options (where applicable), per-version compatibility flags, and descriptions in 5 languages (Slovak, English, Russian, Slovenian, Turkish)

Editing

Each parameter row shows one always-editable value field — type directly, or click it to get a dropdown of known-valid options (custom-built list, not relying on the browser's native datalist, since that proved unreliable)
Clicking the parameter name shows its full explanation in the status bar; clicking the value is reserved purely for editing
Built-in range/format validation for specific fields (e.g. dpi 96–640, TMC download radius ≤200 km)

File handling

Load an existing sys.txt, parse it, and edit it directly
Auto-detects which engine version a loaded file is for — but never silently overrides a version you've picked yourself; if the file looks like a different version, it tells you and asks rather than switching underneath you
Export a clean sys.txt back out
Save/restore full session profiles (JSON), undo/redo history

Smart export logic

"Skip values matching iGO's built-in default" — with a review list showing exactly which parameters match, each individually checkable to keep or omit
Two-tier confidence: values verified directly against real device config files are marked (✓), versus values inferred from the general default field (·) — never presented as equally certain
A fixed set of parameters (TMC, memory, driver-alert distances, engine_1.1 voice config, focus/resume behaviour, etc.) are always written regardless of the skip setting, because omitting them breaks functionality — and this list itself respects per-version compatibility, so it never forces a Nextgen-only key into a Luna export or vice versa
Detects parameters that are flatly incompatible with the currently selected version and offers to remove them

Everything behind it is evidence-based, not guessed

Defaults, valid option lists, and compatibility flags have been cross-checked against real APKs (native library strings, decompiled Lua, and actual shipped config files from real devices) rather than assumed — and corrected multiple times over this project when better evidence turned up

New big update: 1. post

iGO sys.txt Editor – Features

Supported versions

iGO Nextgen 9.18, 32-bit (9.18.27.955559)
iGO Luna 9.35, 32-bit (9.35.2.153810)
iGO Luna 9.35, 64-bit (9.35.2.227616)

The editor’s data for each version was taken from that version’s own APK: the native engine library and the Java layer. This covers which keys exist, which section each key is read from, the value type and the built-in default.

Opening and creating files

Open a sys.txt with the button or by drag and drop. The text encoding (UTF-8, UTF-16 or Windows-1250) is detected automatically.
Detects which iGO version the file belongs to. It uses the file header, data_folder_name, the log path and how well the keys match each version. You can also pick the version yourself.
Create a new, empty sys.txt.
Load the factory sys.txt that ships inside each APK, as a starting point.
Duplicate keys are reported, and the last value wins, just as in iGO.

Browsing and editing

Parameters are sorted into categories: GPS, route, map and icons, 3D, POI, sound, TTS, voice guidance, traffic/TMC, Android and folders, and more.
Each parameter card shows:
its section, a plain-language description, type and unit
the built-in default
meanings of the allowed values
a support table for all three versions
whether it is important
web sources, where available
Values are set with on/off toggles, drop-down lists of suggested values or free text. Each value is checked against the key’s type.
Search by key, section or words in the description.
Filters: all, in the file, changed, important.
An expert list contains every key the engine reads for the selected version, including keys without a description.
An “Unknown keys” view lists keys from your file that the selected version does not read.
Add any key manually. Section names are suggested as you type.
Pin a key (⭐) so it is always written, even when it equals the default.
Reset a key, or undo changes (up to 60 steps, Ctrl+Z).

File check (runs automatically)
The check starts when you load a file, switch versions or restore earlier work. Results are grouped, and each group has “Tick all / Clear” buttons:

Remove keys the version does not have. Keys that are merely unknown are not ticked by default, because a skin or voice pack may read them.
Fix sections, typos and wrong values.
Moves a key to the section the engine actually reads.
Renames typos, for example acuracy_workaround becomes accuracy_workaround.
Renames wrongly named keys, for example [interface] poi_w becomes [map] poi_w.
Offers to replace a value of the wrong type with the APK default.
Insert or adjust important parameters. These are the settings for comfortable navigation, inserted with values verified in the APK.
Redundant values: keys that only repeat the built-in default.
Other: suggestions to switch version, duplicate keys, and similar notes.

It also flags specific problems, such as:

TMC turned on but no network or profile set
a fixed DPI value
logging switched on
missing voice-guidance paths
poi_distant_distance used on Luna 64, where the engine reads poi_distant_zoomlevel instead

Recommended presets (one click)

Online traffic (TMC over the internet)
Tunnel mode: no “GPS lost” announcements
AutoRad: speed cameras always visible
Redraw the map at once when returning to iGO
POI icons: larger when near, smaller when far. The version-specific variant, with icons larger and shrinking beyond 1000 m, is available on Luna 64 only.

Saving (export)

A pre-save check lists comments, default values, unsupported keys, unknown keys, wrong sections, invalid values and missing important parameters. Missing important parameters can be inserted straight from this dialog.
Export options:
add a description comment above each key
also write values that equal the APK default
also write keys the selected version does not support
also write unknown keys
Shows how many keys will be written and which are skipped. Skipped default-value keys can be ticked individually to keep them.
Keys stay in the file’s original section order. A header with the version and build is added.
Download as sys.txt with Windows line endings (CRLF), or copy to the clipboard.

Comparing files

Compare the current file with another sys.txt to see changed keys and keys present in only one file.
Adopt missing keys or changed values from the other file in one step.

Interface and convenience

Languages: Slovak, English, Russian, Slovenian, Turkish.
Light and dark theme. The layout works on phones (side drawer).
Work in progress is saved automatically in the browser and can be restored on the next visit.
Keyboard shortcuts: Ctrl+S (export), Ctrl+O (open), Ctrl+F (search), Ctrl+Z (undo), Esc (close).
A single self-contained HTML file that runs offline in any browser.

Limitation: keys read only by a skin or voice pack (data.zip) cannot be checked against the engine, because data.zip is not part of the APKs. They are labelled as skin/voice keys.

Hi

Thanks

Tested it but I'm not really convinced by advices about sys.txt.............

Setting in sys.txt change speed of iGO rapidly.
Final version uploaded in first post.

Rapidly? The original sys file has a couple of lines

What slows down the software are plugins, add-ons and redundant content

Yes, rapidly. For 32 bit version Nextgen with TTS engine 1_1, TMC, WEATHER, buildings and long route it is a must. Now for me, is iGO navigation flawlessly.
There is a lot of bugs in datas.zip files, in pongo skin too, branddings, weather plugin, crossroads plugins, voices.
With claude all is gone and navigation is perfect fluently.

Hi all

There is a lot of bugs in datas.zip files, in pongo skin too, branddings, weather plugin, crossroads plugins, voices.

They will be very happy to read this !!!

Yes, nothing new, it is well known

Originally Posted by Saiph

Yes, rapidly...
With claude all is gone and navigation is perfect fluently.

You are looking at the situation the wrong way
Sys files that are distributed (with certain packages) are adapted to all situations - both standard voice and tts, and these plugins and those, certain mechanisms, a bunch of warnings, for all possible devices, for all possible software releases, etc ... etc.
Over the decades they have been supplemented and supplemented ... to cover every possible scenario
If the user would adjust his setup and throw out what he doesn't need, all the functions would definitely work better and faster

And I'm pretty sure that your editor has bugs, actually omissions also
Certainly, congratulations for the effort