Originally posted by asa572
View Post
Been playing around with the GPS some more.
According to resinfo, the DNS810 WinCE partition can see about ~200mb of memory, and has about ~100mb free. CPU usage spikes to 100% when you skip tracks (SD&FLAC).
Have given Primo 9.8 a try, completely stripped back to bare essentials (ie no TTS/building/3d/DEM files etc etc, just the primo.exe, maps and license files), seems to be a bit faster when changing volumes/skipping tracks, but as soon as you start a route (ie i'm simulating a 1000km route, it bogs down and you get lag. Stop the simulation and it goes back to responsive again.
It seems like for whatever reason that when Primo is running a route/simulation, its using the entire CPU, so when you try and change a track its battling for resources and won't let the units WinCE partition use the CPU, so it just freezes until you either pause navigation or minimize it.
Whether or not this is an issue with Primo being a resource hog, or the DNS's CPU (it should be a dual core 1.2ghz ARM processor, should have bucketloads of processing power), i'm not sure.
It may still be an issue with the DNS not fully utilising the second core? I know that was an issue, but was under the impression that it was supposed to be fixed?
I'm wondering whether there is a way to limit how much CPU Primo uses, say, make it only use a max of 80%, might make it a bit less responsive, but might give the unit some breathing room?
Comment