Wednesday, January 19, 2011

Fix for Wrong Timezone in Dev Build

In addition to the static audio bug in the recent releases, the dev build has a bug where the timezone resets to Pacific Standard Time (PST) and can't be changed to any other timezone. Once again, Google's on it and already has a fix that just needs pushing out. In the meantime though, the workaround for this is quite easy, we'll just set the timezone manually via the command line:
  1. Your Cr-48 needs the developer switch on (towards battery contacts). Press CTRL+ALT+T to get the crosh shell and type "shell" to get a bash shell. You don't however need to be root, the chronos user has rights to do what we need to do.
  2. Run the command:
    cd /var/lib/timezone
    This puts in the directory where timezones are set.
  3. Run the command:
    ls -l
    That's l, s, space, dash, lowercase letter L. This shows us the current localtime file which is just a symlink to the selected timezone. Because of the bug, this will always be /usr/share/zoneinfo/US/Pacific.
  4. Run the command:
    rm localtime
    Here we get rid of the incorrect timezone setting.
  5. Run the command:
    ln -s /usr/share/zoneinfo/US/Eastern localtime
    which will recreate our symlink pointing the symlink file localtime at the correct timezone. You may of course need to change Eastern to be one of Alaska, Aleutian, Arizona, Central, East-Indiana, Hawaii, Indiana-Starke, Michigan, Mountain, Pacific-New or Samoa depending on your local timezone. If you managed to sneak your Cr-48 out of the U.S., there are other timezones one directory up.
  6. reboot. Your time should now be correct for your localtimezone!
As always, please be sure to share your experience with the fix in the comments, good or bad.


    1. Or you can do it with one command -
      'sudo ln -sf /usr/share/zoneinfo/US/Eastern /var/lib/timezone/localtime'
      as I mentioned in the cr-48 Test Ppilots group -!searchin/cr-48-test-pilots/timezone/cr-48-test-pilots/JXA60jS5m3Y/FAqD5SuGjqgJ

    2. Yeah, I did the same fix as DennisL... and it worked great :)

      Did this before I saw anything about it and figured it would at least get the system timezone fixed, didn't know if Chrome used the timezone... luckily it does :)

    3. The latest dev build changed the terminal font. It's larger, and any bash color changes look plain awful. How can I change this?

    4. does this ruin any chance of getting auto updates

    5. @Vinic I agree with you, a change is needed.

    6. Awesome, @DennisL's way worked. I can't be sure of the other, I restarted after I did DennisL's