
- Y2K10-Bug-with-Geko-201
- 01-24-2010
![]() Re: Y2K+10 Bug with Geko 201
| Craig Wallace | 01-25-2010 |
![]() ![]() Re: Y2K+10 Bug with Geko 201
| Bernhard Fische... | 01-27-2010 |
![]() Re: Y2K+10 Bug with Geko 201
| Andreas Weller | 01-27-2010 |
![]() Re: Y2K+10 Bug with Geko 201
| Andreas Weller | 01-27-2010 |
![]() ![]() Re: Y2K+10 Bug with Geko 201
| Gene E. Bloch | 01-28-2010 |
![]() ![]() ![]() Re: Y2K+10 Bug with Geko 201
| Bob Martin | 01-28-2010 |
![]() ![]() ![]() ![]() Re: Y2K+10 Bug with Geko 201
| Gene E. Bloch | 01-28-2010 |
![]() ![]() ![]() ![]() ![]() Re: Y2K+10 Bug with Geko 201
| Stephen Turner | 01-31-2010 |
![]() ![]() ![]() ![]() ![]() ![]() Re: Y2K+10 Bug with Geko 201
| Gene E. Bloch | 02-01-2010 |
![]() ![]() Re: Y2K+10 Bug with Geko 201
| Heinrich Pfeife... | 02-01-2010 |
![]() Re: Y2K+10 Bug with Geko 201
| jairichard | 02-01-2010 |
![]() ![]() Re: Y2K+10 Bug with Geko 201
| jairichard | 02-02-2010 |
![]() ![]() ![]() ![]() ![]() ![]() ![]() Re: Y2K+10 Bug with Geko 201
| Rick Richardson | 02-09-2010 |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Re: Y2K+10 Bug with Geko 201
| Bernhard Fische... | 02-09-2010 |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Re: Y2K+10 Bug with Geko 201
| Bernhard Fische... | 02-13-2010 |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Re: Y2K+10 Bug with Geko 201
| Rick Richardson | 02-13-2010 |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Re: Y2K+10 Bug with Geko 201
| Rick Richardson | 02-17-2010 |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Re: Y2K+10 Bug with Geko 201
| Chuck Crannell | 02-21-2010 |
![]() ![]() Re: Y2K+10 Bug with Geko 201
| Chuck Crannell | 02-23-2010 |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Re: Y2K+10 Bug with Geko 201
| Andreas Weller | 02-09-2010 |
![]() ![]() ![]() ![]() ![]() ![]() ![]() Re: Y2K+10 Bug with Geko 201
| Andreas Weller | 02-09-2010 |
![]() ![]() Re: Y2K+10 Bug with Geko 201
| Rick Richardson | 03-17-2010 |
![]() ![]() ![]() ![]() Re: Y2K+10 Bug with Geko 201
| Christian Zietz | 03-29-2010 |
![]() ![]() ![]() ![]() ![]() Re: Y2K+10 Bug with Geko 201
| Andreas Weller | 03-29-2010 |
![]() ![]() ![]() ![]() ![]() ![]() Re: Y2K+10 Bug with Geko 201
| jairichard | 03-31-2010 |
If you were Registered and logged in, you could reply and use other advanced thread options
>> I sent an e-mail to Garmin (US and EU) but sadly no reply yet :-(
> Today I received a reply from Garmin germany:
> the bug is non reproducible for them. They admit this error may only
> affect few devices. Therefore there's no bug-fix available.
> Unfortunately Garmin doesn't recognize responsibility for their
> products. They simply shift issues onto customers.
> The lesson is clear: if I will buy a new Garmin device I can also
> pick an US or far east import as Garmin's german support not nearly
> justifies the 40% surcharge.
> the bug is non reproducible for them. They admit this error may only
> affect few devices. Therefore there's no bug-fix available.
> Unfortunately Garmin doesn't recognize responsibility for their
> products. They simply shift issues onto customers.
> The lesson is clear: if I will buy a new Garmin device I can also
> pick an US or far east import as Garmin's german support not nearly
> justifies the 40% surcharge.
I cannot repair your Geko but there is a workaround:
Gartrip comes with a new version 210c. When detecting a jump beyond
one year in the time stamps of a track, it asks the user for the
correct date and it repairs the track accordingly. This should help
until Garmin fixes it. See www.gartrip.de
--
Heinrich
http://www.gartrip.de
mail: new<at>gartrip.de
news.t-online.com...
> >> I sent an e-mail to Garmin (US and EU) but sadly no reply yet :-(
> > Today I received a reply from Garmin germany:
> > the bug is non reproducible for them. They admit this error may only
> > affect few devices. Therefore there's no bug-fix available.
> > Unfortunately Garmin doesn't recognize responsibility for their
> > products. They simply shift issues onto customers.
> > The lesson is clear: if I will buy a new Garmin device I can also
> > pick an US or far east import as Garmin's german support not nearly
> > justifies the 40% surcharge.
> > the bug is non reproducible for them. They admit this error may only
> > affect few devices. Therefore there's no bug-fix available.
> > Unfortunately Garmin doesn't recognize responsibility for their
> > products. They simply shift issues onto customers.
> > The lesson is clear: if I will buy a new Garmin device I can also
> > pick an US or far east import as Garmin's german support not nearly
> > justifies the 40% surcharge.
> I cannot repair your Geko but there is a workaround:
> Gartrip comes with a new version 210c. When detecting a jump beyond
> one year in the time stamps of a track, it asks the user for the
> correct date and it repairs the track accordingly. This should help
> until Garmin fixes it. Seewww.gartrip.de
> --
> Heinrichhttp://www.gartrip.de
> mail: new<at>gartrip.de
> Gartrip comes with a new version 210c. When detecting a jump beyond
> one year in the time stamps of a track, it asks the user for the
> correct date and it repairs the track accordingly. This should help
> until Garmin fixes it. Seewww.gartrip.de
> --
> Heinrichhttp://www.gartrip.de
> mail: new<at>gartrip.de
My Geko 201 has the same problem. The pan track feature is
essentially non-functional, and if I try to download tracks with
Mapsource I get an error message saying the track is invalid, using
g7toWin I can get the track and it shows some good 2010 dates and then
some 1991 and 1952 dates.The trip odometer worked fine for a while and
then suddenly went bonkers after I had the gps off changed location by
a few miles and re-started the gps. It also is acting like it is
having a problem remembering the almanac.
> Hi.
> There seems to be a year 2010 bug with my Garmin Geko 201.
> When switching it on date and time are calculated wrong. But making it
> even worse almanac data is also lost. So it needs to search for all
> satellites whenever it is turned on. Indeed the whole celestial
> mechanics is wrong: trying to display sunset results in a hung up geko -
> I needed to remove the batteries to switch it off.
> First I thought this problems might be caused by a broken buffer
> battery. But I tried it using two Geko 201 with different firmware
> versions. The problem is repeatable with both devices.
> On the Garmin web-page there's nothing about this - no FAQ entry, no
> Firmware update...
> Would you please check whether your Garmin is also affected? May be only
> the german firmware is affected. Or it's a fundamental problem with the
> phasetrac12 chipset used in this series of GPS devices.
> I sent an e-mail to Garmin (US and EU) but sadly no reply yet :-(
> Regards,
> =A0 Andreas Weller
> There seems to be a year 2010 bug with my Garmin Geko 201.
> When switching it on date and time are calculated wrong. But making it
> even worse almanac data is also lost. So it needs to search for all
> satellites whenever it is turned on. Indeed the whole celestial
> mechanics is wrong: trying to display sunset results in a hung up geko -
> I needed to remove the batteries to switch it off.
> First I thought this problems might be caused by a broken buffer
> battery. But I tried it using two Geko 201 with different firmware
> versions. The problem is repeatable with both devices.
> On the Garmin web-page there's nothing about this - no FAQ entry, no
> Firmware update...
> Would you please check whether your Garmin is also affected? May be only
> the german firmware is affected. Or it's a fundamental problem with the
> phasetrac12 chipset used in this series of GPS devices.
> I sent an e-mail to Garmin (US and EU) but sadly no reply yet :-(
> Regards,
> =A0 Andreas Weller
I use my 201 to record hillwalks so its track dates and times are
central to that. This Sundays (yesterday) track had a date in
September 2029 and the GPS has its time in August 1988. My 201 also
produced a very corrupt track for part of the day with errors like
exagerated SA of 1 or 2 Km which is assume is another symptom of the
problem. I have mailed Garmin on their website. I hope this leads to
a new firmware version and a fix.
> > Hi.
> > There seems to be a year 2010 bug with my Garmin Geko 201.
> > When switching it on date and time are calculated wrong. But making it
> > even worse almanac data is also lost. So it needs to search for all
> > satellites whenever it is turned on. Indeed the whole celestial
> > mechanics is wrong: trying to display sunset results in a hung up geko =
-
> > There seems to be a year 2010 bug with my Garmin Geko 201.
> > When switching it on date and time are calculated wrong. But making it
> > even worse almanac data is also lost. So it needs to search for all
> > satellites whenever it is turned on. Indeed the whole celestial
> > mechanics is wrong: trying to display sunset results in a hung up geko =
> > I needed to remove the batteries to switch it off.
> > First I thought this problems might be caused by a broken buffer
> > battery. But I tried it using two Geko 201 with different firmware
> > versions. The problem is repeatable with both devices.
> > On the Garmin web-page there's nothing about this - no FAQ entry, no
> > Firmware update...
> > Would you please check whether your Garmin is also affected? May be onl=
y
> > First I thought this problems might be caused by a broken buffer
> > battery. But I tried it using two Geko 201 with different firmware
> > versions. The problem is repeatable with both devices.
> > On the Garmin web-page there's nothing about this - no FAQ entry, no
> > Firmware update...
> > Would you please check whether your Garmin is also affected? May be onl=
> > the german firmware is affected. Or it's a fundamental problem with the
> > phasetrac12 chipset used in this series of GPS devices.
> > I sent an e-mail to Garmin (US and EU) but sadly no reply yet :-(
> > Regards,
> > =A0 Andreas Weller
> > phasetrac12 chipset used in this series of GPS devices.
> > I sent an e-mail to Garmin (US and EU) but sadly no reply yet :-(
> > Regards,
> > =A0 Andreas Weller
> I use my 201 to record hillwalks so its track dates and times are
> central to that. This Sundays (yesterday) track had a date in
> September 2029 and the GPS has its time in August 1988. My 201 also
> produced a very corrupt track for part of the day with errors like
> exagerated SA of 1 or 2 Km which is assume is another symptom of the
> problem. =A0I have mailed Garmin on their website. I hope this leads to
> a new firmware version and a fix.- Hide quoted text -
> - Show quoted text -
> central to that. This Sundays (yesterday) track had a date in
> September 2029 and the GPS has its time in August 1988. My 201 also
> produced a very corrupt track for part of the day with errors like
> exagerated SA of 1 or 2 Km which is assume is another symptom of the
> problem. =A0I have mailed Garmin on their website. I hope this leads to
> a new firmware version and a fix.- Hide quoted text -
> - Show quoted text -
I have spoken to Garmin this morning on their UK support number and
they are aware of this problem now and it is in the hands of their US
people. They took my phone and email with a promise to keep me
updated. Watch this space.....
> > > Hi.
> > > There seems to be a year 2010 bug with my Garmin Geko 201.
> > > When switching it on date and time are calculated wrong. But making i=
t
> > > There seems to be a year 2010 bug with my Garmin Geko 201.
> > > When switching it on date and time are calculated wrong. But making i=
> > > even worse almanac data is also lost. So it needs to search for all
> > > satellites whenever it is turned on. Indeed the whole celestial
> > > mechanics is wrong: trying to display sunset results in a hung up gek=
o -
> > > satellites whenever it is turned on. Indeed the whole celestial
> > > mechanics is wrong: trying to display sunset results in a hung up gek=
> > > I needed to remove the batteries to switch it off.
> > > First I thought this problems might be caused by a broken buffer
> > > battery. But I tried it using two Geko 201 with different firmware
> > > versions. The problem is repeatable with both devices.
> > > On the Garmin web-page there's nothing about this - no FAQ entry, no
> > > Firmware update...
> > > Would you please check whether your Garmin is also affected? May be o=
nly
> > > First I thought this problems might be caused by a broken buffer
> > > battery. But I tried it using two Geko 201 with different firmware
> > > versions. The problem is repeatable with both devices.
> > > On the Garmin web-page there's nothing about this - no FAQ entry, no
> > > Firmware update...
> > > Would you please check whether your Garmin is also affected? May be o=
> > > the german firmware is affected. Or it's a fundamental problem with t=
he
> > > phasetrac12 chipset used in this series of GPS devices.
> > > I sent an e-mail to Garmin (US and EU) but sadly no reply yet :-(
> > > Regards,
> > > =A0 Andreas Weller
> > > I sent an e-mail to Garmin (US and EU) but sadly no reply yet :-(
> > > Regards,
> > > =A0 Andreas Weller
> > I use my 201 to record hillwalks so its track dates and times are
> > central to that. This Sundays (yesterday) track had a date in
> > September 2029 and the GPS has its time in August 1988. My 201 also
> > produced a very corrupt track for part of the day with errors like
> > exagerated SA of 1 or 2 Km which is assume is another symptom of the
> > problem. =A0I have mailed Garmin on their website. I hope this leads to
> > a new firmware version and a fix.- Hide quoted text -
> > - Show quoted text -
> > central to that. This Sundays (yesterday) track had a date in
> > September 2029 and the GPS has its time in August 1988. My 201 also
> > produced a very corrupt track for part of the day with errors like
> > exagerated SA of 1 or 2 Km which is assume is another symptom of the
> > problem. =A0I have mailed Garmin on their website. I hope this leads to
> > a new firmware version and a fix.- Hide quoted text -
> > - Show quoted text -
> I have spoken to Garmin this morning on their UK support number and
> they are aware of this problem now and it is in the hands of their US
> people. They took my phone and email with a promise to keep me
> updated. Watch this space.....
> they are aware of this problem now and it is in the hands of their US
> people. They took my phone and email with a promise to keep me
> updated. Watch this space.....
I sent email to Garmin and got this reply:
"Please download, install and run the WebUpdater application to
install the most current software version onto your unit:
http://www8.garmin.com/products/webupdater/howtoinstall.jsp
You will also need to do a master reset on your unit. Doing a master
reset will delete all user data, but it will also delete any corrupt
system data which may be causing the issue. Be sure to back up all
user data, if possible, before continuing. To do the master reset,
with the unit off, press and hold 'up' + 'ok' + 'page' + 'power' at
the same time for about five seconds.
The above two steps should take care of this issue. If it doesn't, the
unit will need to come in for repair/replacement. The flat rate to
repair/replace a Geko 201 is $59 plus any applicable tax. "
I already had the latest firmware, but the master reset did the job
for me.
PLEASE NOTE:
1) The master reset only occurs if the device is OFF before pushing
the buttons !!!
2) Immediately after the reset, the track log dates were still screwy,
but after turning the unit off and then back on I am getting a normal
tracklog with the correct dates and times.
Tom
- Car charger with 1490LMT
- Garmin GPS
- 2012-03-19
- Fwd: [1203.3433] Measurement of the neutrino velocity with the ICARUS detector at the CNGS beam
- Satellite Navigation
- 2012-03-18
- How can I save my Garmin nüvi 670 NA with European maps (see photos)
- Global Positioning System
- 2012-03-26
- MapSource V6.5 with nRoute
- Garmin GPS
- 2012-04-05
- Any cameras with integrated gps
- Garmin GPS
- 2012-03-22








