[Gpephone-devel] GSM time updates and UTC/locale/TZ
Joshua Layne
joshua at willowisp.net
Tue Apr 24 03:27:45 CEST 2007
Hi Yu Yijun,
Thank you for the reply. Your description of how the GPEPE architecture would achieve this is excellent and I believe it meets all the requirements implied by my user scenario.
I very much appreciate the prompt reply and the consideration.
Regards,
Joshua
On Mon, 23 Apr 2007 04:59:04 +0200, "YU Yijun RD-ILAB-PEK" <yijun.yu at orange-ftgroup.com> wrote:
> Hi, Joshua,
>
> Definitely it is a good feature. We may consider to implement it like
> this:
> 1. a global setting parameter CURRENT_TIME_ZONE is defined, which can be
> r/w by phone server, calendar, etc.
> 2. Once local time zone changed, GSM tower will notify the phone server in
> the device, and phone server will update the parameter of CURRENT_TIME_ZONE
> 3. the change of CURRENT_TIME_ZONE will notify all interested applications
> that local time zone has changed, and these applications shall update
> themselves accordingly.
>
> Does it meet your requirements?
>
> Regards
> Yu Yijun
>
>
>
>>-----Original Message-----
>>From: gpephone-devel-bounces at linuxtogo.org
>>[mailto:gpephone-devel-bounces at linuxtogo.org] On Behalf Of Joshua Layne
>>Sent: 2007Äê4ÔÂ22ÈÕ 2:11
>>To: gpephone-devel at linuxtogo.org
>>Subject: [Gpephone-devel] GSM time updates and UTC/locale/TZ
>>
>>Attention, votre correspondant continue de vous ¨¦crire ¨¤ votre ancienne
> adresse
>>en @orange-ft.com, qui va ¨ºtre d¨¦sactiv¨¦e d¨¦but avril. Veuillez lui
> demander
>>de mettre ¨¤ jour son carnet d¡¯adresses avec votre nouvelle adresse en
>>@orange-ftgroup.com.
>>
>>Caution : your correspondent is still writing to your orange-ft.com
> address,
>>which will be disabled beginning of April. Please ask him/her to update
> his/her
>>address book to orange-ftgroup.com
>>..................................................
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>Hi all,
>>I have been thinking about this for a bit (mostly in frustration towards
> my
>>current WM2005 phone because it doesn't do this), but basically, any GSM
> phone
>>I have ever had except my current POS (Ericsson and Nokias, mostly) has
> been
>>able to pull time from the cell towers on a GSM network and automatically
> update
>>the time on the phone (usually with a user prompt: "The local time is
> xxxxxx,
>>update?"). Windows Mobile does not do this (surprise!) and so on a
> battery
>>failure, requires you to reset time and date, screws up the call log
> (which has
>>a time/date stamp), etc...
>>
>>My thinking is that this is a fairly easy problem to fix.
>>
>>I added a few comments to this page:
>>http://www.linuxtogo.org/gowiki/GpepeTodo?action=show
>>
>>but I wanted to provide more detail and a brief use case of _desired_
>>functionality here:
>>
>>---
>>I live in the Bay Area, CA, USA (Pacific TZ). We are currently in DST
> (thanks
>>to mister bush) and so our local time is currently GMT -7 (? have to say
> I always
>>get confused on this.... normally GMT -8, but with DST, we are +1 hour, I
>>think...).
>>
>>I have a calendar entry for a meeting that starts monday at 8AM PDT. It
> is stored
>>internally in my phone calendar as Monday at 3PM (15:00) UTC and when I
> view
>>my calendar in San Francisco, shows as starting at 8AM on monday (PDT).
>>
>>I get on a plane and fly to New York on Sunday night. When I get off the
> plane
>>and turn my phone back on, I am prompted that the local time is 6AM EDT
> (it is
>>3AM in SF) - Do I want to update my local time?
>>
>>I click 'yes' and my _locale/TZ_ is updated to Eastern Daylight Time.
> The
>>internal UTC time (provided there is no gross difference, say a few
> milliseconds
>>- standard NTP-like functionality) is not updated.
>>
>>When I view my calendar, I now see that my meeting is at 11AM EDT (note
> that
>>the internal calendar storage time did not change at all) and am able to
> call
>>into my meeting a little sleep deprived, but at the correct time.
>>
>>If I now receive an invite for another meeting, the calendar translates
> to UTC
>>(probably from senders TZ settings) before inserting the meeting into my
>>schedule.
>>---
>>
>>Sorry if this is too much "user land", but I figure if I wait until GPEPE
> is
>>fully built, it'll be too late :), Also - this may be a trivial problem
> and already
>>how everything works but when I reviewed the architecture, I did not see
> any
>>interface specified between the RTC and GSM, unless this functionality is
>>mediated by 'atd'. With most modern phones and towers, this could be
>>accomplished with standard NTP functionality for the UTC internal clock,
> but
>>servers are not location-aware. That is the benefit that the cell towers
> have
>>with GSM.
>>
>>Comments, thoughts, flames?
>>
>>Thanks in advance,
>>Joshua Layne
>>
>>
>>_______________________________________________
>>Gpephone-devel mailing list
>>Gpephone-devel at linuxtogo.org
>>http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/gpephone-devel
>>
More information about the Gpephone-devel
mailing list