Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 1 of 3 123 LastLast
Results 1 to 10 of 24
  1. #1
    Member + SanFrancisco's Avatar
    Join Date
    Aug 2017
    Location
    CA, USA
    Posts
    36
    Rep Power
    37

    Default Incorrect time on nüvi 255W

    Recently I bought a few old Garmin devices from a "second hand items" shop. One nüvi 255W and two nüvi's 250W. I have updated all through WebUpdater (first) and then GarminExpress. After that, no further updates available for these units. Peculiar thing however, is that the nüvi 255W shows the local time 1 hour behind the actual time. See screenshot below. Both nüvi's 250W show the correct time.

    Spoiler: pic
    iMXOk2b


    - I checked the units for presence of the gmaptz.img file. All have the latest version (v22.00) stored in the X:\Garmin folder.
    - I reinstalled the latest FW again. No luck.
    - I took the unit for a drive around (thinking I must use it above a certain speed first). No luck.
    - Time setting is set to "Automatic".
    - The unit has 5 green bars of satellite reception, so it knows where it is. In terms of navigating the roads, the unit works fine.

    Further details below:
    nüvi 255W, FW 7.80, HWID 1091
    nüvi 250W, FW 4.10, HWID 0737
    nüvi 250W, FW 4.10, HWID 0835

    Anyone have any ideas as to what I may have overlooked? Thanks in advance!


    PS: Forgot to mention:
    - Restored unit to factory settings few times. No luck.
    Last edited by Magnetron; 17th October 2019 at 02:37 AM.

  2.    Advertissements


  3. #2
    iGO Enthusiast

    Boki's Avatar
    Join Date
    Jun 2014
    Location
    Niš
    Age
    51
    Posts
    6,334
    Rep Power
    4230

    Default

    Did you set the time zone?
    Before asking a question, know it's already discussed here and at 99.9% is not unique. Use search.
    NO ONE IS A SEER, READ (click on): [Only registered and activated users can see links. ] <- Click!
    [Only registered and activated users can see links. ] <- Click!

    Spoiler: obs
    Many questions become very arduous, a lot of time chewed deja vu...Since we have lost all the year of work and effort, many people have no will to answer the same questions again. Me neither. Use a search, please.

  4. #3
    Important User

    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,449
    Rep Power
    1033

    Default

    Quote Originally Posted by SanFrancisco View Post
    .........
    Anyone have any ideas ........
    A long shot. Try unchecking 'Automatic', set the time manually and let it get a good sat. fix, then reset it to automatic time to see how it behaves.

  5. #4
    Member + SanFrancisco's Avatar
    Join Date
    Aug 2017
    Location
    CA, USA
    Posts
    36
    Rep Power
    37

    Default

    Quote Originally Posted by Boki_Srb View Post
    Did you set the time zone?
    The nüvi 255W does not have such option. I have seen it on other model nüvi's, like the nüvi 250W.

    Quote Originally Posted by Butters View Post
    A long shot. Try unchecking 'Automatic', set the time manually and let it get a good sat. fix, then reset it to automatic time to see how it behaves.
    Unfortunately, that did not fix it either.

    I have two more nüvi's 255W, but with HWID 0827. They both show the correct local time. The problem is limited to the HWID 1091 unit only...

  6. #5
    Member + SanFrancisco's Avatar
    Join Date
    Aug 2017
    Location
    CA, USA
    Posts
    36
    Rep Power
    37

    Default

    Done some additional troubleshooting:

    The UTC time on this HWID 1091 device shows correct. It's just the local time that is 1 hour behind. One possible cause is the device does not consider Day Light Saving correctly. We'll know that first weekend of November when the clock moves 1 hour back. If the nüvi then still lags by one hour, we know the time database is correct *), but for some reason it has an offset of -1 hour.

    *) Actually we already know that the time database is correct. Otherwise all my other devices would demonstrate the same issue.

    So the other option is that the FW or internal settings somehow got damaged. I know I already reloaded the same FW several times now, but a very wise teacher at this forum once upon a time taught me that rolling back FW and then reinstalling the new FW again does more "deep cleaning" than reverting back to factory settings.

    I therefore flashed FW version nuvi2x5W_GCDFile-MTK__760.gcd into the device via WebUpdater. After reboot however the same 1 hour lag still shows.
    I then let WebUpdater load the latest FW version nuvi2x5W_GCDFile-MTK__780.gcd into the device again. Still no luck.

    Not sure if there is anything else I have not tried yet. Running out of ideas here.

  7. #6
    Administrator
    Magnetron's Avatar
    Join Date
    Nov 2011
    Location
    Western Australia
    Age
    71
    Posts
    9,813
    Rep Power
    1572

    Default

    Just correct the UTC by 1 hr to get your local time right.
    Can't see a link/attachment? Don't post asking why. Just 'Like' the post & hit F5:
    THE LIKE BUTTON IS NOW IN THE BOTTOM LEFT HAND CORNER
    Posts serving no purpose like thanks or to ask about links go to [Only registered and activated users can see links. ] or are deleted, it's GPS Power policy.

  8. #7
    Important User

    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,449
    Rep Power
    1033

    Default

    Quote Originally Posted by SanFrancisco View Post
    ........ rolling back FW and then reinstalling the new FW again does more "deep cleaning" than reverting back to factory settings.

    I therefore flashed FW version nuvi2x5W_GCDFile-MTK__760.gcd into the device via WebUpdater. After reboot however the same 1 hour lag still shows.
    I then let WebUpdater load the latest FW version nuvi2x5W_GCDFile-MTK__780.gcd
    As you'd know the first nuvi to have the ability to clear nonvol via the hidden menu behind the speedo was the 1xxx series. In earlier devices like the 2x5 series it is possible to perform a similar function by downgrading fw but it usually needs to be done by several versions. There can be a risk of white screen bricking if the device has a late series of PCB that wasn't issued at the time of issue of the old fw and a white screen may result in a genuine brick, as in paper weight. The safest option might be to simply open it up and disconnect the battery for some time then hard reset it again on subsequent start up. Might work but if not go with your idea about daylight saving. Good luck!

  9. #8
    Member + SanFrancisco's Avatar
    Join Date
    Aug 2017
    Location
    CA, USA
    Posts
    36
    Rep Power
    37

    Default

    Quote Originally Posted by Magnetron View Post
    Just correct the UTC by 1 hr to get your local time right.
    ....so if the speedometer in your car shows an incorrect speed, you simply turn the dial plate to correct it, rather than fix the cause?

    Apart from the fact UTC is showing correct on this device, UTC is an official world-wide atomic clock time standard. National laboratories around the world have atomic clocks synchronised to this atomic time standard. It has an accuracy of less than a micro second, and you suggest I change it by no less than an hour??? How on earth would I ever pull off such a trick?

    Quote Originally Posted by Butters View Post
    ...In earlier devices like the 2x5 series it is possible to perform a similar function by downgrading fw but it usually needs to be done by several versions. There can be a risk of white screen bricking...
    I'm most willing to accept confrontation with a WSOD (white screen of death). The educational aspect of the exercise outweighs the risk of bricking the device. However, version 7.60 and 7.80 are the only FW flavours I have for this particular HWID. The only additional version available at "Perry" is 7.70, but that is even more recent than the 7.60 version which I already tried.

    Will try to backup rgn.41, then erase it and see if that brings back the correct local time. If not, I will see if formatting the internal memory using RMPrepUSB helps and then start with a clean slate. I can always restore the backed up rgn.41.

    To be continued...

  10. #9
    Important User

    Butters's Avatar
    Join Date
    Jul 2017
    Location
    CA
    Posts
    1,449
    Rep Power
    1033

    Default

    @SF
    I've got older versions on an unused HDD somewhere, just need to locate it. Probably i'll have very old 0827 versions for sure, but not so certain about 1091 MTK. I'll have a look and let you know. It's unlikely properly reformating the visible file system in region 48 will help as the problem is indeed likely residing in region 41 as you suspect. Certainly your plan to erase rgn41 and see if the time changes to the correct local time has merit. If it does then a restore of nonvol followed by a radical fw downgrade will either fix it or kill it if you wish to take that risk.

  11. #10
    Administrator
    Magnetron's Avatar
    Join Date
    Nov 2011
    Location
    Western Australia
    Age
    71
    Posts
    9,813
    Rep Power
    1572

    Default

    UTC is a time reference not a must. If your device doesn't except day light saving then you correct the error by offset it will still be time accurate.
    You may not except my reference but I have to do this many time over the years with software and forums to Be time local.
    Software is not perfect, I hate having to update every 6-12 mth so I don't use crap devices and be lead into updating all the time.
    So I use a non map GPS and a mapping system that doesn't rely on updating maps.
    Can't see a link/attachment? Don't post asking why. Just 'Like' the post & hit F5:
    THE LIKE BUTTON IS NOW IN THE BOTTOM LEFT HAND CORNER
    Posts serving no purpose like thanks or to ask about links go to [Only registered and activated users can see links. ] or are deleted, it's GPS Power policy.

 

 

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •