Thread: Low resource Igo

Depends on the processor.
I have Mio MOOV 500 with Samsung proc, 400 MHz, 64 MB RAM, WINCE 5 (whose RAM consumption is lower than WinCE6)
I use full primo (NASA dem, poi, speedcam, building, TTS).
Also, it depends a lot on the used unlock, to stop all unnecessary process.
It is advisable to quit or reduce files : speedcam, dem.
Regarding on skin, a good skin can help the device.
On Mio P 360 Dimka help a lot, it moves better than the default skin.

The issue is from "The units have dual core".
I have found the same issues to other devices with dual core(WinCE 6 800x480) and the only working SW at this moment is Sygic.
Primo doesn't work at this moment.

No error messages . At times the turn now command is 20m after the corner but mostly it is the back ground function like steering wheel controls taking a long time to take effect. The copysI have used are a cut down basic version with memory restriction in the sys text through to a full TTS version with all the trimmings ( Megris).
Cheers G

That is not problem with high or low resources.
For example, new Prestigio navigator 5800 runs or WinCE6, have ARM11 DualCore CPU, and uses iGO.
Btw, I remember, 3 years ago, I was at one event, first time have unit with dual core in my hands (can't remember the exact model, sorry, it was preproduction), and I didn't notice any problems that 3 days I've use it.
Costas and D.I.I. are probably right. It is metter of processor. And implemented instructions...and version of Primo that support it. So meny android versions, nobody says why are so meny, what are true deferences or improvements. Because of hardware support, no software.
Just my opinion, maybe I am wrong...