Re: qtMoko getting bad Network Time

2015-01-07 Thread Jorge
Wait... If I apply to the calue 136 the code from https://github.com/freesmartphone/cornucopia/blob/master/fsogsmd/src/lib/consts.vala#L975 I get -120 minutes, which is Ok: --- public int ctzvToTimeZone( int ctzv ) // ctzv = 136 { var bcd1 = ( ctzv / 0x10 );

Re: qtMoko getting bad Network Time

2015-01-07 Thread Jorge
Thanks. I've found this wording for the time zone info [1][2]: "(indicates the difference, expressed in quarters of an hour, between the local time and GMT; range -96...+96)" So, a value of 136 would not be valid. I'll try to track this one. Jorge [1] http://www.etsi.org/deliver/etsi_ts/

QtMoko & Firefox OS

2015-01-07 Thread Peter Viskup
Hi all, anybody took over QtMoko maintanence? Seems that Radek will not release any new version. If not, is anybody working on Firefox OS port to GTA02/4? -- Peter Viskup ___ Openmoko community mailing list community@lists.openmoko.org http://lists.open

Re: qtMoko getting bad Network Time

2015-01-07 Thread Christ van Willegen
Hi, On Wed, Jan 7, 2015 at 4:08 AM, Paul Wise wrote: > The log confirms that QtMoko is definitely looking for the GMT-34 timezone. > > Looking at the QtMoko source code, +CTZV is an "Unsolicited result > code for time zone change events". > > Your operator's CTZV value is 136. I also noticed thi