iGO Primo Android black screen during voice guidance

**RaGlaSi** · 23rd August 2017, 01:52 PM

iGO Primo 9.2.29.483387

During the voice guidance the screen goes black.
When the "voice leader" stop talking the iGO is normally visible.

If I delete the .ftr files inside the maps iGo works normally.

Please help.

**osiris4isis** · 23rd August 2017, 05:23 PM

Your .ftr files might be corrupted. Check it under Help->About->Content->Truck Restrictions

**janch** · 23rd August 2017, 09:06 PM

Nope, this is a "known" issue on some Android tablets running Primo with all recent Here maps (2016-->2017). No known solution so far..However, no such problems on Nextgen, but some truckers still prefers iGO Primo. It's really frustrating to be forced to use Nextgen instead of Primo just because of this tiny bug..

**osiris4isis** · 23rd August 2017, 11:55 PM

I go with info given by the user

Originally Posted by RaGlaSi

iGO Primo 9.2.29.483387

During the voice guidance the screen goes black.
When the "voice leader" stop talking the iGO is normally visible.

If I delete the .ftr files inside the maps iGo works normally.

Please help.

and note the careful working

Originally Posted by osiris4isis

Your .ftr files might be corrupted. Check it under Help->About->Content->Truck Restrictions

**janch** · 24th August 2017, 06:52 AM

Yes, you had a good point no doubt, but I remembered that this issue was already discussed with no other solution than to delete .ftr file(s). But doing so, truck navigation functions are compromised.

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

It's really hard to understand how can .ftr files affect voice commands and screen flickering as these files are just additional map attributes which has nothing to do with the graphic or with the voice commands. And on the other side Nextgen handles them without a problem.

**osiris4isis** · 24th August 2017, 07:33 AM

It happened because part of .ftr is corrupted. Case in point, I'm having a streaking graphic (crazy lines drawing from center) for one POI in 2017 HERE USA map. The problem is only for that single POI and it depends on zooming. And this is with NextGen9.18.27.687519-Gift(26Jan2017) So if part of that .poi is corrupted. Data corruption lead to memory corruption (when loaded) and causes impact on other subsystems.
The reason why NextGen doesn't have issues with it might be because it has different API for loading the data. This is my best guess.

**janch** · 24th August 2017, 07:48 AM

That is well explained but I doubt that all ftr files from any recent HERE maps are corrupted or at least it's a bad definition. As you say I also believe that NNG must have slightly changed something in ftr files which affects Primo having troubles handling them. But it's still confusing that in most Android tablets/phones there is no such problems in relation Primo + ftr.

**osiris4isis** · 24th August 2017, 08:06 AM

Ok, if problem exists for all .ftr then it has to be an API problem, not corruption. Does this problem has to do with ONLY .ftr or other content causes problem as well?

**janch** · 24th August 2017, 08:22 AM

ftr only in all cases that I can recall.

**Midnight Blues** · 24th August 2017, 05:48 PM

I have same problem with Primo in other situations, like when having listed traffic events and then try to open one of them iGO always crashes or screen goes black.
Also sometimes when starting iGO, display stuck on loading screen or goes black, but program goes on in background
Pressing home button and Primo icon againg, display comes back like nothing happened.

But it is only on some devices with Android 4.x.x
I never had this problem on Android 5.x or 6.x with exactly same data files

So my conclusion was that it is problem with graphic driver compatibility, and I tried every possible variant in sys.txt, but with no solution

And then I stepped forward to NextGen