Navigation slow to resume after hibernate - 1.1.0.0

sinister99 · 09-01-2007, 11:57 AM

What version of StreetDeck is this bug report for?

1.0.9.8-1.1.0.0

Please give a basic description of the issue here.

Usually (with only a few exceptions) Navigation has low signal for 1-5 (or more) minutes.

Is the system that is listed in your CarPC specs under your user name the same system where you encountered this bug?

yes

Reproduceable?

On my computer...

Please provide any relevant information regarding the issue you have encountered.

If I start streetdeck after a system reboot, nav shows my position immediately. After hibernating, it usually takes a while for the nav to get a signal. There is ALWAYS a delay after resuming from hibernate. Occasionally, the GPS starts after 30 seconds. A few times, it has literally taken more than 5 minutes before I lost patience and rebooted. I would say the average time is 1.5 minutes. I know that my GPS receiver is working properly, because I immediately have signal when starting other GPS applications (Including my copy of MapPoint).

RedGTiVR6 · 09-01-2007, 06:58 PM

you state that the informtion under your user name is the information about your CarPC but there is no information under your user name. Please fill it out according to this thread: http://www.mp3car.com/vbulletin/anno...r-profile.html

S4Per · 09-24-2007, 12:49 AM

i get the same result, and IMHO this bug should be a lot higher severity than 3!
Just dug into it over the last couple of days. I've had it take 15 minutes to get signal back (i.e. to get Nav not to show 'low signal from GPS') and if I exit SD and restart SD, it picks up signal right away.

I don't have log, but you have one above.

Navigation is a key piece of this software. If it's not up and running sub 30 seconds of a computer start or resume, it's useless. It worked better in the past.

RedGTiVR6 · 09-24-2007, 09:09 AM

S4Per - one or two users reporitng an issue does not necessitate a higher priority on our developers list. Many times, when only one user is reporting an issue it's a user or a configuration error.

Only once bugs are reproduced by our team or are verified by other users can we re-evaluate and raise the severity level.