Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17
  1. #11
    SUPER MODERATOR iGO 64-bit for Trucks [discussion]
    iGO 64-bit for Trucks [discussion]iGO 64-bit for Trucks [discussion]iGO 64-bit for Trucks [discussion]iGO 64-bit for Trucks [discussion]iGO 64-bit for Trucks [discussion]iGO 64-bit for Trucks [discussion]
    Andrey Form's Avatar
    Join Date
    Oct 2019
    Location
    Belarus
    Posts
    3,924
    Rep Power
    2815

    Default

    This thread has been active for almost a year now, and it is time to summarize our findings and provide definitive technical conclusions regarding the use of 64-bit iGO Nextgen applications for heavy commercial truck (TIR) navigation.
    Based on deep-dive community testing, source code analysis, and real-world European logistical feedback, all key results have just been structured and added directly into the first post (OP) of this thread.
    Here is the definitive technical breakdown of the 64-bit distributions we investigated, with a vital focus on the ongoing confusion surrounding the AVICSYNC branch:

    🛑 The AVICSYNC (v9.35.2.227616) Situation: A Dangerous Illusion

    Lately, many users have been trying to force the 64-bit AVICSYNC engine to calculate routes for 40-tonne trucks, resulting in endless confusion. Let's make it clear once and for all: AVICSYNC is architecturally broken for heavy trucks.
    • The HERE Maps Trap: The AVICSYNC routing engine was originally designed by NNG under an OEM contract specifically for Pioneer AVIC passenger multimedia systems and campers. It lacks deep-level truck toll matrix licensing. When you enable "Toll Road Avoidance" with HERE maps, the engine cannot process mandatory electronic truck tolls (like Germany's Toll Collect or Poland's e-TOLL). It treats these entire mandatory networks as physical "road blocks," producing absurd 2,000+ km detours. There is no magic sys.txt tweak, no missing license, and no automatic map converter that can fix this closed engine logic.
    • The TomTom Maps Danger: Some drivers mistakenly celebrate because switching to TomTom maps eliminates the 2,000 km loops, creating a "nice, short route." Beware: this is a lethal trap. The easily cracked AVICSYNC binary simply blinds itself to TomTom's heavy truck physical restrictions layer (weights, dimensions, ADR). It routes a 40-tonne truck exactly like a small passenger car. Driving with this setup in the EU will inevitably lead you under a low bridge, onto restricted weight-limited roads, or into massive BAG fines.

    🛒 The Basar (v9.35.2.262743) Status: Restricted easy routing

    Similar to AVIC, the Basarsoft branch is a regionally locked, passenger-car-oriented core. As experienced members have correctly pointed out, even if .ftr files show up as active (green/white) in the content menu, the engine executive code is prone to silent failures. It regularly messes up heavy truck restriction tables and toll logic, making it highly unreliable for serious commercial international driving.

    🟢 The World (v9.35.2.252374) Verdict: The Only Stable 64-bit Choice

    If you are running a modern 64-bit Android device and need 100% reliable heavy fleet logistics, iGO Nextgen World 64-bit remains the only viable and verified solution. Its global, unrestricted core native algorithm perfectly processes multi-layered HERE .ftr data and calculates optimized, safe, toll-free routes while strictly respecting every physical boundary of a 40-tonne vehicle.
    gps5

    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]


    ©AF_2020-26

  2.    Advertissements


  3. #12
    Member +
    Join Date
    Apr 2015
    Location
    Serbia
    Age
    56
    Posts
    37
    Rep Power
    217

    Default

    There is, but someone deleted it.
    I have no intention of uploading again!


    Spoiler: +
    [Only registered and activated users can see links. ]

    [Only registered and activated users can see links. ]

    [Only registered and activated users can see links. ]
    Last edited by Andrey Form; Yesterday at 07:40 PM.

  4. #13
    SUPER MODERATOR iGO 64-bit for Trucks [discussion]
    iGO 64-bit for Trucks [discussion]iGO 64-bit for Trucks [discussion]iGO 64-bit for Trucks [discussion]iGO 64-bit for Trucks [discussion]iGO 64-bit for Trucks [discussion]iGO 64-bit for Trucks [discussion]
    Andrey Form's Avatar
    Join Date
    Oct 2019
    Location
    Belarus
    Posts
    3,924
    Rep Power
    2815

    Default

    @Petar
    What exactly are we supposed to discuss here? Your statement about a deleted file that you have no intention of uploading, or these silent screenshots?
    Since you attached these images as a technical argument, let's look at what they actually prove:
    1. The 1415 km Illusion (Passenger Car Calculation)
    Your map screen shows a route of 1415 km with a travel time of 14:01. Let's do the simple math: 1415 km divided by 14 hours equals an average speed of ~101 km/h. No heavy commercial truck (TIR) profile in any iGO executive core can calculate a route with an average speed of 101 km/h across European highways due to hardcoded truck speed limiters (80-85 km/h). This is a standard passenger car calculation, which is further confirmed by the active routing icons at the top.
    2. The 2577 km Reality (Toll Matrix Failure)
    The moment you switch to the active guidance screen from Podgorica, the underlying AVICSYNC 9.35.2.227616 executive code tries to apply TIR restriction layers (.ftr) and toll structures. Because this branch lacks proper truck toll matrix licensing, it treats mandatory electronic toll networks as solid roadblocks. The result is right there at the bottom of your screen: an absurd 2577 km detour to reach Poland.
    Your own images perfectly demonstrate exactly what I summarized in the first post: the AVICSYNC engine creates a dangerous illusion of truck navigation on the menu screen, but completely breaks down in real-world application.
    gps5

    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]


    ©AF_2020-26

  5. #14
    Junior Member
    Join Date
    Jun 2022
    Location
    Poznan
    Posts
    5
    Rep Power
    0

    Default

    iGO World 9.35.2.252374 vs AVICSYNC 9.35.2.227616 – My Real-World Test Results

    I would like to share the results of my tests performed today, as they do not support the claim that iGO World 64-bit is significantly better for heavy truck navigation than AVICSYNC.

    Today, I built a fresh installation of iGO World 9.35.2.252374, using only the essential files, without unnecessary add-ons or modifications.

    I then compared it directly with iGO AVICSYNC 9.35.2.227616.

    I placed two smartphones side by side, calculated identical routes and ran navigation simulations simultaneously.

    Test results:

    Both versions calculate practically identical routes.

    Both display the same road signs and speed limits.

    Lane guidance and road markings appear identical.

    POI and KML handling is the same.

    Navigation simulation behaves practically identically.

    Both versions exhibit exactly the same TRUCK routing problem with HERE maps.

    When selecting the TRUCK profile and disabling toll roads, both AVICSYNC and World incorrectly avoid major roads covered by electronic truck toll systems, such as e-TOLL in Poland and Toll Collect in Germany, resulting in extremely long and unnecessary detours.

    The same problem does not occur with TomTom maps.

    My conclusions:

    Based on these tests, I found no evidence that World 9.35.2.252374 has a better truck routing algorithm than AVICSYNC 9.35.2.227616.

    On the contrary, both engines behave almost identically, including the HERE toll-road avoidance problem.

    I am not claiming that their internal code is identical, but I suspect they share the same or a very similar routing mechanism.

    Therefore, I cannot agree with the statement that iGO World 64-bit is the only fully reliable solution for heavy truck navigation.

    At least regarding HERE/TRUCK routing in my tests, World offers no advantage over AVICSYNC.

    It is possible that this issue is related to a shared routing mechanism within the NNG 9.35.2 engine family rather than to a specific distribution.

    I would be interested in hearing from other users who have performed similar comparisons, especially if anyone can demonstrate a genuine difference in heavy truck routing between World and AVICSYNC.

  6. #15
    iGO Enthusiast iGO 64-bit for Trucks [discussion]
    Boki's Avatar
    Join Date
    Jun 2014
    Location
    Niš
    Age
    54
    Posts
    7,283
    Rep Power
    4907

    Default

    The thing is, contrary to what some might think, none of the 64-bit apps are designed for heavy-duty/truck use. Previous versions were much more generous in that regard.
    No skin, add-on, UX, or anything else can compensate modules that do not exist within the APK itself.
    Additionally – a major problem with licenses
    Before asking a question, know it's already discussed here and at 99.9% is not unique. Use search.
    NO ONE IS A SEER, READ (click on): [Only registered and activated users can see links. ] <- Click!
    [Only registered and activated users can see links. ] <- Click!

    Spoiler: obs
    Many questions become very arduous, a lot of time chewed deja vu...Since we have lost all the year of work and effort, many people have no will to answer the same questions again. Me neither. Use a search, please.

  7. #16
    SUPER MODERATOR iGO 64-bit for Trucks [discussion]
    iGO 64-bit for Trucks [discussion]iGO 64-bit for Trucks [discussion]iGO 64-bit for Trucks [discussion]iGO 64-bit for Trucks [discussion]iGO 64-bit for Trucks [discussion]iGO 64-bit for Trucks [discussion]
    Andrey Form's Avatar
    Join Date
    Oct 2019
    Location
    Belarus
    Posts
    3,924
    Rep Power
    2815

    Default

    🚚 Practical Logistics in the 64-bit Era: How to Successfully Run iGO World on a 40-Tonne Truck

    For those running modern 64-bit Android devices without backwards compatibility for 32-bit applications, the landscape of iGO truck navigation has drastically changed. As established by core analysis and senior member feedback, the native, deep-level Truck Toll Matrix module found in the classic 32-bit Nextgen (Israel/PAL) does not exist inside the executive binary code of the 64-bit Nextgen family (World, Avicsync, Basar).
    This architectural limitation means that forcing any 64-bit iGO app to automatically calculate a long-distance (1000+ km) cross-border route while checking "Avoid Toll Roads" will inevitably fail. The engine simply views national electronic toll networks (like Germany's Toll Collect or Poland's e-TOLL) as solid physical road blocks, spitting out absurd 2,500 km loops in a desperate bid to find non-existent toll-free commercial corridors.
    However, this does not mean iGO World 64-bit (v9.35.2.252374) is useless. While it cannot act as an automated logistical financial planner, it remains an excellent, rock-solid physical gatekeeper for your vehicle's dimensions. Its global, unrestricted core is the only 64-bit distribution that reliably holds and processes multi-layered HERE .ftr data in operational memory without silent data drops. It will never route a 40-tonne fleet under a low bridge, onto weight-restricted roads, or into tight residential traps.
    To bypass the toll-routing bug and utilize iGO World 64-bit as a dependable commercial tool, drivers must shift from "automated routing" to "manual tactical logistics."

    🛠 Operational Routing Strategy for iGO World 64-bit

    Stop relying on the 64-bit core to think for you over long haul distances. Instead, apply one of these two professional dispatching techniques:

    Method 1: The Multi-Stage Intermediate Approach (Via Points)

    Instead of letting the application dictate the general corridor, pre-plan your legal toll-free or national road skeleton.
    • Manually plot sequential Via Points along the national or regional highways you intend to use.
    • The Role of iGO World: Between these specific coordinates, the World 64-bit executive core takes full control of physical safety. It cross-references your configured truck profile (4.0m height, 40t weight, axle limits, ADR) against the HERE road attributes, ensuring you safely hop from one waypoint to the next without catching massive police fines or clipping trailers.

    Method 2: Short-Leg Sectional Mission Planning (Border-to-Border)

    Break down an international transit route into short, manageable regional segments.
    • Program your destination strictly to the upcoming national border or regional hub (200–400 km legs).
    • On these heavily compressed distances, the limited routing algorithm processes data cleanly, respects the toll avoidance checkbox properly within local parameters, and prevents systemic loops. Once the section is complete, load the next border leg.

    🗺 External Strategy & Route Mapping Architecture

    Because the 64-bit iGO engine functions strictly as an on-road safety executor rather than a high-level logistical planner, strategic routing layouts should be engineered outside the app before typing coordinates into the head unit.

    1. Professional Web-Based Toll Calculators (Primary Mapping)

    • Official Toll Operators (e.g., Toll Collect Route Planner): Use official European truck network calculators to identify exactly where commercial charging zones begin and end. This lets you map out safe, legal alternative state routes.
    • Google Maps (Satellite + Street View): An indispensable tactical reconnaissance asset. Before committing to a national detour or bypass via points, drop down to Street View at major roundabouts or country road turnoffs to visually confirm that local municipalities haven't erected fresh weight limits or truck bans.

    2. Secondary Mobile Truck Ecosystems (Tactical Co-Drivers)

    Cross-examine your planned route structure using mobile platforms that maintain separate routing algorithms:
    • Sygic Truck Navigation: Useful for initial macro-routing analysis due to its separate handling of modern European toll tariffs and local transit updates.
    • TomTom GO Navigation (Truck Profile): Excellent for analyzing live commercial traffic, lane blocks, and holiday restrictions on secondary state routes before applying those paths to iGO.

    📋 The Professional Driver's Workflow:

    1. Reconnaissance: Open a dedicated web truck route planner to draft the legally sound, cost-effective transport corridor.
    2. Verification: Inspect complex highway junctions or regional bypasses via Google Street View to spot unauthorized local restriction signs.
    3. Execution: Input this verified corridor into iGO World 64-bit utilizing tight Via Points or segmented Short-Leg targets.
    4. Transit: Drive with absolute peace of mind. You control the logistics and corporate expenses, while iGO World 64-bit safely guards your structural overheads, axle pressures, and trailer dimensions.
    gps5

    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]


    ©AF_2020-26

  8. #17
    iGO Enthusiast iGO 64-bit for Trucks [discussion]
    Boki's Avatar
    Join Date
    Jun 2014
    Location
    Niš
    Age
    54
    Posts
    7,283
    Rep Power
    4907

    Default

    AI?

    In my region, we have an extremely strong community that deals with this issue. It's amazing how much the language and Pongo skin have adapted to these (truck) needs.I can claim that more than half of the truck drivers in Europe use this work. Others - many, but really many are stealing that material from us
    After much wasted time - in short - if you need, buy a device of high enough quality with a large screen and with an older system, insert the classic NextGen and use it for these purposes
    (at least until someone manages to steal, modifies and adapt 9.35 from fleet devices)
    Before asking a question, know it's already discussed here and at 99.9% is not unique. Use search.
    NO ONE IS A SEER, READ (click on): [Only registered and activated users can see links. ] <- Click!
    [Only registered and activated users can see links. ] <- Click!

    Spoiler: obs
    Many questions become very arduous, a lot of time chewed deja vu...Since we have lost all the year of work and effort, many people have no will to answer the same questions again. Me neither. Use a search, please.

 

 

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •