Thread: iGO Nextgen Avicsync 64bit, Pongo skin [mod FotiL]

Sorry, but that’s comparing apples and oranges; the two iGO versions are worlds apart 😏
We should be grateful for what the skinners have achieved so far for 64-bit and what they’ve made possible for us — though, unfortunately, Arimi is no longer involved...

@Facan
sys.txt:
[rawdisplay]
driver="gles_2_0_android"
screen_xy="auto"
dpi=640

Cheldron

Thanks, this setting worked for me.

Golom

Hello. I tried the "UX" components from AVIC on iGO World, but the result was no different from iGO Basar.

@Cheldron

9.35.2.262743 is a modern, native 64-bit version of iGO Nextgen, designed for newer Android systems and OpenGL ES 2.0/3.0 engines.

Since this version is based on a modern architecture, the driver line can be deleted and iGO will automatically select the appropriate rendering. In many modern sys.txt builds, this line is left completely empty or not included at all under [rawdisplay], because the 64-bit iGO engine automatically handles Android graphics acceleration.
The [rawdisplay] section is completely empty because the 64-bit engine of iGO Basarsoft Nextgen (9.35.2.262743) and the Xiaomi 14T Pro (HyperOS / Android) communicate directly with each other without any software restrictions.
This means that you have turned off manual forcing and handed over control to the native automation of the software.
The Xiaomi 14T Pro display is physically very dense (446 ppi), but HyperOS scales the surface to a comfortable, optimal size in software. When you remove the limiting commands from iGO, the navigation fits into this system-wide scaling. iGO does not start counting microscopic physical pixels one by one, but draws on a virtually enlarged, optimized graphics layer provided by the phone's operating system.
The screen_xy="auto" line is also deleted, the default (factory) value of the iGO Nextgen engine is "auto". If the software does not find a fixed pixel value, it automatically occupies the entire available display area (Fullscreen). It does not limit itself, so the map fills the Xiaomi's 20:9 elongated screen.
errors are caused by conflicting commands in sys.txt.!
By removing everything from under [rawdisplay], all internal code conflicts are eliminated. The iGO engine simply does its job: it starts, asks the phone for the dimensions, the phone gives it the perfectly prepared values, and the navigation is drawn pin-sharp, with the correct icon size.

Remove the entire section from

"sys.txt"!

̶[̶r̶a̶w̶d̶i̶s̶p̶l̶a̶y̶]̶
̶d̶r̶i̶v̶e̶r̶=̶"̶g̶l̶e̶s̶_̶2̶_̶0̶_̶a̶n̶d̶r̶o̶i̶d̶"̶
̶s̶c̶r̶e̶e̶n̶_̶x̶y̶=̶"̶a̶u̶t̶o̶"̶
̶d̶p̶i̶=̶6̶4̶0̶

Or, if you don't want to delete it, comment it out like this:

;[rawdisplay]
;driver="gles_2_0_android"
;screen_xy="auto"
;dpi=640
I always delete all the "junk" to keep the file clean, so the iGO engine doesn't have to skip over it.

The DPI section (dpi & base_dpi) has influence. Leave it
Otherwise, native UX files from the 9.35 series cannot be mixed with those from 9.18. Modified ones can work but this is generally not the rule