Garmin iQue M5 slow: Duplicates in DB_notify_events

Garmin iQue M5 slow: Hundreds of duplicates in DB_notify_events

Symptom: when the acquisition of the satellites seems to be complete,
the iQue M5 gets stuck for a short period. After that, it performs
satisfactory (except for the irregular NMEA sentences).
This 'stuck' period gets longer and longer, and after a few weeks it
becomes noticeable: the clock on the satellite view page stops for a few
seconds (just after it has been synchronized with the satellites).
After a longer period of time (4-6 weeks in my case) the pocketPC
doesn't come out of this 'stuck' situation any more and becomes totally
unusable, with response times of 2-3 minutes.
Unless I flip the antenna closed. Then I have a fully functional
pocketPC. But without GPS.
I already had to hard reset the unit three times in the past to make it
work again.

Anybody else experiences this problem?

Today I discovered hundreds of duplicate entries in DB_notify_events,
with a free program called CheckNotifications from
www.scarybearsoftware.com
With this program I deleted all the duplicate entries, and the
acquisition-delay (that had already increased to 6 seconds since the
last necessary hard reset 3 weeks ago) was gone!
Deleting the duplicates reduced the number of entries from 402 to 15.
I've already found out that every soft reset increases this number by 2,
but I don't believe I have performed as much as 200 soft resets in the
last 3 weeks.

Maybe this contribution contains valuable information for other
(frustrated) iQue M5 users too?

I know I should report this to Garmin, but my experiences with iQue M5
support in the past were very unsatisfactory. I don't want to go into
another e-mail battle that lasts for months, just to get this piece of
information at the proper place. (and it looks like I have a makeshift
solution now anyway)
So maybe some responsible Garmin employee could pick this up from this
newsgroup? :-)

Unfortunately, removing all the duplicate entries did not solve the
problem of the irregular NMEA sentences coming way too late. I kinda
hoped both problems were caused by the same bug, because they start at
exactly the same moment.

These are the two records that have all the duplicates:

Application: MyTimeChangedEvent
Notify Type: 1
Event Status: 0
Event Type: 1
Arguments: AppRunAfterTimeChange
Start time: 0-0-0, 00:00
End time: 0-0-0, 00:00


Application: QUE_TIME_NTFYEVNT
Notify Type: 1
Event Status: 0
Event Type: 1
Arguments: (none)
Start time: 0-0-0, 00:00
End time: 0-0-0, 00:00