Oh, that's true, i didn't paid attention to that ...
It's a relief ^^
--
Gand'
On Sun, Oct 3, 2010 at 2:46 PM, Ole Carlsen o...@carlsen-web.dk wrote:
Den 03-10-2010 14:08, Gand' skrev:
Since i moved to the v27, my touchscreen is kind of weird ... I can't
draw a straight line, and when i
Since i moved to the v27, my touchscreen is kind of weird ... I can't draw a
straight line, and when i keep the stylus on the screen, it draws a tiny
star (more or less 9mm²) It makes the docked keyboard pretty unusable as
when press a key, one of the surrounding key often responds ...
--
Gand'
Den 03-10-2010 14:08, Gand' skrev:
Since i moved to the v27, my touchscreen is kind of weird ... I can't
draw a straight line, and when i keep the stylus on the screen, it draws
a tiny star (more or less 9mm²) It makes the docked keyboard pretty
unusable as when press a key, one of the
Le 27/09/2010 19:08, Alfa21 a écrit :
2010-09...@17:32 Thomas HOCEDEZ
and go to the dial interface
I can confirm this.
ooh! great, you remembered to me an annoying usability issue about the answer
screen:
when I'm in a hurry or I'm walking sometimes I push the answer button twice
[cut]
Also it can compare only system clock with RTC, so we always assume that
system time is correct. Calypso time - do we need it at all?
Maybe to correct drifting RTC?
--
Patryk LeadMan Benderz
Linux Registered User #377521
() ascii ribbon campaign - against html e-mail
/\
Le 25/09/2010 10:53, Radek Polak a écrit :
Hi,
new experimintal qtmoko-v27 with 2.6.34 kernel is out now. You can download
it
from our sourceforge page [1]
Qtmoko is distribution based on debian+qtopia, for more info see [2][3][4].
Changes from latest v26 stable release:
* New 2.6.34
2010-09...@17:32 Thomas HOCEDEZ
and go to the dial interface
I can confirm this.
ooh! great, you remembered to me an annoying usability issue about the answer
screen:
when I'm in a hurry or I'm walking sometimes I push the answer button twice due
to the latency of the gui just because
On 09/25/2010 10:45 PM, Timo Juhani Lindfors wrote:
Alex Samorukovm...@os2.kiev.ua writes:
Thank you for update. How did you measure this drift? Anyway, i don`t
With http://lindi.iki.fi/lindi/openmoko/compare-clock-sources.pl
Thanks.
Also it can compare only system clock with
Alex Samorukov m...@os2.kiev.ua writes:
With http://lindi.iki.fi/lindi/openmoko/compare-clock-sources.pl
Also it can compare only system clock with RTC, so we always assume
compare-clock-sources.pl compares
1) GPS to system time
2) GPS to pcf time
3) GPS to calypso time.
It does not compare
Hi,
new experimintal qtmoko-v27 with 2.6.34 kernel is out now. You can download it
from our sourceforge page [1]
Qtmoko is distribution based on debian+qtopia, for more info see [2][3][4].
Changes from latest v26 stable release:
* New 2.6.34 kernel [5]
* GPRS fixes (Alex Samorukov and Pierre
Hi, Radek.
I have been testing 2.6.34 kernel for one week now and to me it looks ok.
There can be issues with SD card [6],
[6] http://www.shr-project.org/trac/ticket/1143
About this issue: here, recompiling shr-2.6.32 kernel, i can reproduce
problems with sd-card. For example i have to
. with broken LCD screen or case)
then i`ll be glad to buy it - its hard to do too much experiments on
every-day phone :)
On 09/25/2010 10:53 AM, Radek Polak wrote:
Hi,
new experimintal qtmoko-v27 with 2.6.34 kernel is out now. You can download it
from our sourceforge page [1]
Qtmoko
В Сбт, 25/09/2010 в 21:38 +0200, Alex Samorukov пишет:
2) Syslogd replacement with debian`s busybox. Its already works for me,
i will try to send patches tomorrow.
Why?
Gennady
___
Openmoko community mailing list
community@lists.openmoko.org
On 09/25/2010 08:41 PM, Gennady Kupava wrote:
В Сбт, 25/09/2010 в 21:38 +0200, Alex Samorukov пишет:
2) Syslogd replacement with debian`s busybox. Its already works for me,
i will try to send patches tomorrow.
Why?
I`m using memory buffer for logging and it makes my flash
Alex Samorukov m...@os2.kiev.ua writes:
could you please add RTC sync on every suspend to the sources? It is
*very important* to make it synced before suspend, because if they are
not in sync - phone will wake up in the wrong time. I will send you the
patch.
At least here the RTC drifts so
On 09/25/2010 09:53 PM, Timo Juhani Lindfors wrote:
At least here the RTC drifts so fast (6 seconds per hour) that I don't
even try to keep it in sync. Instead I predict what the RTC will read
at a given time using a simple linear model. I sent a patch to add
--predict option to hwclock and
Alex Samorukov m...@os2.kiev.ua writes:
Thank you for update. How did you measure this drift? Anyway, i don`t
With http://lindi.iki.fi/lindi/openmoko/compare-clock-sources.pl
see that its a big issue. E.g. i have a daily alarm set, so in a worst
case (phone was in a standby mode, no
17 matches
Mail list logo