Does M5 map lag behind?

[JMckie]

Glowing review at:

http://www.davespda.com/reviews/pda/iquem5.htm

However,

"Sometimes the software would get a little delayed...I do not know if this was the main processor lagging, the screen not repainting fast enough, or the GPS itself. This sometimes caused the QueMap software to not quickly notice I was driving off course (sometimes taking up to two blocks) and then it also had to take time to replot the map. The system was only slightly slower than others I have used, and I blame the rerouting on the processor speed of the device."

How often does this happen?

[AKlopper]

I haven't noticed any problems with it, apart from the apparently normal PPC tendency to require soft resets fairly frequently, particularly when I have been playing with the wireless stuff.

When I first got the unit I noticed that loading of QueMap and drawing of maps seemed noticeably slower than on the iQue 3600, but this was due to apps hogging memory in the background and was remedied by installing MagicButton.

It is definitely slower than the iQue 3600 at switching between QueMap, QueFind, QueRoutes, etc. (if they aren't already running in the background), but I can live with that. Route calculation is definitely faster.

[NCTRNL]

I think a lot of the performance issues can happen because of how many other programs are running in the background. If you reset the unit, there are no other applications running and the map should never lag or have any issues. If you have messaging, contacts, settings, solitaire, and a bunch of other things open it will slow down the Que program.

[cabazon]

I have a brand new M5 ,and it has give me fits. All the map city detail which is really minimal anyway for Vancouver Island occasionally disappears altogether. The only way I can get it back is to use the reset button. Sometimes it will freeze up solid and I can't even sut it off. I land up resetting the button again.
Another question is, How do you choose a comm port setting for GPS using oxiexplorerCE. I tried a few different settings within the OZI program and it can't find the signal.
Another aggravation is when you shut the unit off and by mistake hold your finger on the button for more than a fraction of a second the backlite slider setting returns to 0 and you have you fumble to reset it in the dark. What a pain that is! any suggestions?

[AKlopper]

Originally posted by cabazon
I have a brand new M5 ,and it has give me fits. All the map city detail which is really minimal anyway for Vancouver Island occasionally disappears altogether. The only way I can get it back is to use the reset button. Sometimes it will freeze up solid and I can't even sut it off. I land up resetting the button again.

This happened to me a few times, but it hasn't happened since I started using MagicButton to ensure that applications actually close when you click on the close button, rather than just minimising to the background. It may simply be QueMap competing with other applications for memory. You might also try ejecting and re-inserting the SD card with the maps to force QueMap to rediscover the maps.

Originally posted by cabazon
Another question is, How do you choose a comm port setting for GPS using oxiexplorerCE. I tried a few different settings within the OZI program and it can't find the signal.

COM2 has NMEA output from the GPS. The NMEA standard specifies 4800 baud as the speed, but it seems to work with every baud rate that I have tried.

Originally posted by cabazon
Another aggravation is when you shut the unit off and by mistake hold your finger on the button for more than a fraction of a second the backlite slider setting returns to 0 and you have you fumble to reset it in the dark. What a pain that is! any suggestions?

Hold the power button down again for a second and the backlight will come back on.

[AKlopper]

On a slightly different note, another reason for slow off-route detection might be driving on a parallel road very close to the original route (even in the opposite direction to the route). QueRoutes seems to calculate the distance from you to the closest point on the route and only recalculate if that distance exceeds a certain amount.