Commentary

Elena Malykhina
 

Three Easy Ways To Make Sure Your Smartphone Survives The Daylight-Saving Transition

Everyone is aware that in the U.S. daylight-saving time is coming three weeks earlier this year, on March 11. But did you know your smartphone applications and operating system could be affected by the daylight-saving time bug, just as easily as desktop software programs? Here are some suggestions to keep things running smoothly.

Everyone is aware that in the U.S. daylight-saving time is coming three weeks earlier this year, on March 11. But did you know your smartphone applications and operating system could be affected by the daylight-saving time bug, just as easily as desktop software programs? Here are some suggestions to keep things running smoothly.1. Check with your mobile operating system provider or smartphone vendor for any updates or patches related to daylight-saving time. Microsoft, Research In Motion, and Palm all have posted updates and patches on their Web sites to prevent smartphone calendars and clocks from displaying the wrong times and dates once the switchover happens.

2. Make sure you have the right time zone selected on your smartphone. Some tools won't properly update the daylight-saving time settings, unless you manually change the time zone. Smartphone users in the U.S., Canada, and Mexico will be affected by the switchover.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

3. Pay special attention to calendar appointments scheduled on your smartphone from March 11 to April 1, 2007, and Oct. 28 to Nov. 4, 2007. Daylight-saving time will now start three weeks earlier (2:00 a.m. on the second Sunday in March) and will end one week later (2:00 a.m. on the first Sunday in November).

If your smartphone was issued to you by your employer, ask your IT support about the steps you should take. It's possible the update will be sent to you automatically. Better safe than sorry!

Got any other useful tips? Please share.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links