27 messages in com.googlegroups.android-developersRe: Incorrect timezone in m3-rc37a?
FromSent OnAttachments
Dan U.03 Jan 2008 19:30 
Peter Stevenson04 Jan 2008 09:54 
Digit04 Jan 2008 10:14 
Dan U.04 Jan 2008 11:19 
Digit04 Jan 2008 11:58 
Dan U.04 Jan 2008 12:13 
Digit04 Jan 2008 12:41 
Dan U.04 Jan 2008 14:55 
Dan U.07 Jan 2008 12:40 
Digit07 Jan 2008 14:36 
Dan U.08 Feb 2008 02:37 
Digit08 Feb 2008 02:44 
Dan U.08 Feb 2008 02:48 
Diego Torres Milano08 Feb 2008 14:22 
Dan U.08 Feb 2008 14:56 
cirion10 Feb 2008 13:14 
j16 Feb 2008 12:48 
Digit16 Feb 2008 15:15 
Ted Hopp17 Feb 2008 13:29 
Dan U.17 Feb 2008 13:51 
Ted Hopp17 Feb 2008 17:29 
Dan U.17 Feb 2008 17:36 
Ted Hopp17 Feb 2008 17:54 
Dan U.17 Feb 2008 18:27 
Ted Hopp17 Feb 2008 18:34 
Dan U.17 Feb 2008 19:55 
Kosmaj17 Feb 2008 21:47 
Subject:Re: Incorrect timezone in m3-rc37a?
From:Diego Torres Milano (dtmi@gmail.com)
Date:02/08/2008 02:22:28 PM
List:com.googlegroups.android-developers

You can try this using adb shell

# /system/bin/date Fri Feb 8 23:19:42 CET 2008 # /system/bin/date -u Fri Feb 8 22:19:51 GMT 2008

which shows that 37a is working fine, at least in Linux.

On Feb 8, 11:48 am, "Dan U." <dan.@gmail.com> wrote:

Seems rather odd. It was working correctly in the previous sdk versions for me.

On Feb 8, 2:45 am, Digit <digi@gmail.com> wrote:

This is right, the problem is verified, and a solution is under way. unfortunately, it requires painful platform-specific handling of timezone files/settings to work appropriately. I can't give you an date estimate for its resolution though, due to higher priority items...

note that it depends on your OS/timezone (which means that it already works in some timezones, not all of them).

On Feb 8, 2008 11:37 AM, Dan U. <dan.@gmail.com> wrote:

As I understand it, this problem has been verified. Digit, is there any information you can post about the problem and/or solution?

On Jan 7, 2:36 pm, Digit <digi@gmail.com> wrote:

yes, but it would help if you could send me the adb log fixe

On Jan 7, 2008 9:40 PM, Dan U. <dan.@gmail.com> wrote:

Is this still being worked on? Do you need me to do anything more?

On Jan 4, 2:56 pm, "Dan U." <dan.@gmail.com> wrote:

Something doesn't appear to be working correctly. I have the output for 37a, but both 20a and 22a give me:

* daemon not running. starting it now * * daemon still not running * error: no device

when I run the adb command. It would seem to me this is because it can't detect that the emulator is running, but it is and I'm using the adb version that comes with each emulator. Should I instead be using the adb that came with 37a when I test 20a and 22a emulators?

And I verified that both the 20a and 22a emulators show the correct time, but 37a is off by 8 hours.

On Jan 4, 12:42 pm, Digit <digi@gmail.com> wrote:

thanks, can I ask you to do the following and report the results

here,

with

both emulator versions:

- start the emulator, and wait until the "Home" screen appears - in a terminal, run "adb shell logcat -b radio > radio.log.txt",

this

will

dump the radio logs, which include the GSM AT commands

answer to this e-mail with the radio.log.txt files corresponding

to

each

emulator version you can test (indicating which file belongs to which emulator version). this should help us understand what's happening

here...

thanks in advance !

On Jan 4, 2008 9:14 PM, Dan U. <dan.@gmail.com> wrote:

Pacific Time

On Jan 4, 11:58 am, Digit <digi@gmail.com> wrote:

hmmmm, can you tell us in which time zone you're working ?

On Jan 4, 2008 8:19 PM, Dan U. <dan.@gmail.com> wrote:

Actually, it's the other way around for me. Earlier versions

did

know

about the localtimezoneand did show the time correctly,

whereas

this

version does not know the localtimezone(defaults to GMT). I

have

not

manually changed thetimezoneand wipe-data doesn't help.

On Jan 4, 10:14 am, Digit <digi@gmail.com> wrote:

this is not supported to happen like this.

previous versions of the emulator didn't know anything

about

the

local

machine'stimezone, and thus always assumed GMT on the other hand, the version in 37a does send the

localtimezone

to

the

emulated system, which should be able to use it directly.

the only exception to this last rule is if you have

manually

changed

the

timezone. in this case, your setting is saved in the /data

partition

and

used on the next boot. I don't remember if the settings is

simply a

timezone

offset or something more specific, but it could explain

that

the

timezoneis

incorrect when upgrading to a new version of the emulator.

in all cases, does starting with a fresh install (emulator

-wipe-data,

or

even emulator -data foo) solves the problem ?

if not, can you tell me more about yourtimezone?

On Jan 4, 2008 4:31 AM, Dan U. <dan.@gmail.com>

wrote:

I'm using m3-rc37a and the emulator is showing a

GMTtimezoneas

the

default. As I recall, previous versions used

thetimezoneof

the

local

machine (PST in my case). Is anyone else seeing this? Is

it