On Thursday 27 May 2010 11:50:23 Yann SLADEK wrote:
Hi Radek,
after a test on Gand's FR with v22, I decided to reflash from v21 to v22
But, every times the FR goes into sleep, I got a WSOD
This is strange, i havent seen wsod for long time except when working with
xrandr or with qvga.
I
Hi Radek,
after a test on Gand's FR with v22, I decided to reflash from v21 to v22
But, every times the FR goes into sleep, I got a WSOD
I tried to see if I didn't mess with files when flashing but everything was ok
Then, I realized that, at start, QI says the kernel is qtmoko-v21 (creation
I have the same 'problem' here with the v21 instead of v22 ...
but mine is rock stable ^^
--
Gand'
On Thu, May 27, 2010 at 11:50 AM, Yann SLADEK yann.sla...@free.fr wrote:
Hi Radek,
after a test on Gand's FR with v22, I decided to reflash from v21 to v22
But, every times the FR goes
Hi,
On Sat, May 22, 2010 at 6:57 PM, Al Johnson
openm...@mazikeen.demon.co.ukwrote:
On Saturday 22 May 2010, Linus Gasser wrote:
Le 14.05.10 23:28, Torfinn Ingolfsen a écrit :
Hi,
The new version appears to work fine here (just a quick test so far).
BTW, my Ubuntu laptop (Xubuntu
Hi,
On Sat, May 22, 2010 at 9:24 PM, Dr. H. Nikolaus Schaller h...@goldelico.com
wrote:
It is a probolem of the OM kernel that provides a random Mac address
Now, why would the OM kernel do a stupid thing like that?
More to the point: why would it change MAC address every time I connect my
if it happens with both an ubuntu box and macos x, it's most likely caused
by the fr.
nevertheless, on ubuntu you may try to set
udevadm control --log-priority=debug
and watch the log for more information.
another idea that occurs to me: is the interface always correctly shut
down?
what
i forgot:
what does
/etc/udev/rules.d/70-persistent-net.rules
look like?
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Hi,
On Sun, May 23, 2010 at 6:51 PM, arne anka openm...@ginguppin.de wrote:
if it happens with both an ubuntu box and macos x, it's most likely caused
by the fr.
nevertheless, on ubuntu you may try to set
udevadm control --log-priority=debug
and watch the log for more information.
I
Hi,
On Sun, May 23, 2010 at 6:53 PM, arne anka openm...@ginguppin.de wrote:
i forgot:
what does
/etc/udev/rules.d/70-persistent-net.rules
look like?
Now, this is an interesting file. Here are a few lines:
# This file maintains persistent names for network interfaces.
# See udev(7) for
Torfinn Ingolfsen tin...@gmail.com writes:
On Sun, May 23, 2010 at 6:53 PM, arne anka openm...@ginguppin.de wrote:
what does
/etc/udev/rules.d/70-persistent-net.rules
look like?
Now, this is an interesting file. Here are a few lines:
...
# USB device 0x1457:0x5122 (usb)
On Tue, Apr 27, 2010 at 7:33 PM, Radek Polak pson...@seznam.cz wrote:
Hi,
i have uploaded new stable QtMoko debian images [1].
..
- workaround for the GSM (restart not needed now)
..
As for the fixes: first two are quite clear. The problem with GSM not
registering can be partially
Le 14.05.10 23:28, Torfinn Ingolfsen a écrit :
Hi,
The new version appears to work fine here (just a quick test so far).
BTW, my Ubuntu laptop (Xubuntu 9.10) exhibits a strange symptom: each
time I connect my FR, the network interface name increases:
eg. it started out with 'eth9' (what
On Saturday 22 May 2010, Linus Gasser wrote:
Le 14.05.10 23:28, Torfinn Ingolfsen a écrit :
Hi,
The new version appears to work fine here (just a quick test so far).
BTW, my Ubuntu laptop (Xubuntu 9.10) exhibits a strange symptom: each
time I connect my FR, the network interface name
Linus Gasser l...@markas-al-nour.org writes:
The new version appears to work fine here (just a quick test so far).
BTW, my Ubuntu laptop (Xubuntu 9.10) exhibits a strange symptom: each
time I connect my FR, the network interface name increases:
eg. it started out with 'eth9' (what happened
Am 22.05.2010 um 18:29 schrieb Linus Gasser:
Le 14.05.10 23:28, Torfinn Ingolfsen a écrit :
Hi,
The new version appears to work fine here (just a quick test so far).
BTW, my Ubuntu laptop (Xubuntu 9.10) exhibits a strange symptom: each
time I connect my FR, the network interface name
no - andy-tracking does not have kms stuff. All 2.6.32 kernels were until now
also without kms - they are built from om-gta02-2.6.32. At that time KMS
branch had some problem, which were fixed. Last time i tried KMS branch it
worked fine. So maybe next 2.6.32 based release will be with kms.
On Saturday 15 May 2010 17:47:47 mobi phil wrote:
but still do not know if it is based on andy tracking.
All 2.6.29 kernels in QtMoko are based on andy-tracking. They are built with
nodebug config and wifi patch from here:
whatever kernel it is.. does it have the Thomas Whites Kms stuff
On Saturday 15 May 2010 17:47:47 mobi phil wrote:
but still do not know if it is based on andy tracking.
All 2.6.29 kernels in QtMoko are based on andy-tracking. They are built with
nodebug config and wifi patch from here:
http://github.com/radekp/qtmoko/tree/master/devices/neo/linux_kernel/
la. den 15. 05. 2010 klokka 00.28 (+0200) skreiv Torfinn Ingolfsen:
Hi,
The new version appears to work fine here (just a quick test so far).
BTW, my Ubuntu laptop (Xubuntu 9.10) exhibits a strange symptom: each
time I connect my FR, the network interface name increases:
eg. it started out
the uImage-v22.bin is 2.6.29 isn't it?
was not following for a while the list... could anybody tell me where
I could find a 2.6.32.bin?
On wiki it is stated that andy tracking would be used for 2.6.32, but
not sure if that is from the 2.6.29 times..
rgrds,
mobi phil
being mobile, but
On Sat, May 15, 2010 at 1:31 PM, mobi phil m...@mobiphil.com wrote:
the uImage-v22.bin is 2.6.29 isn't it?
Yes, QtMoko V22 has this kernel:
neo:~# uname -a
Linux neo 2.6.29-rc3-v21 #10 Tue Apr 6 22:54:31 CEST 2010 armv4tl GNU/Linux
was not following for a while the list... could anybody tell
thanks
but still do not know if it is based on andy tracking.
whatever kernel it is.. does it have the Thomas Whites Kms stuff merged?
On Sat, May 15, 2010 at 1:54 PM, Torfinn Ingolfsen tin...@gmail.com wrote:
On Sat, May 15, 2010 at 1:31 PM, mobi phil m...@mobiphil.com wrote:
the
On Friday 14 May 2010 00:33:48 Gand' wrote:
Do you mean it's significantly more unstable than the v20 ?
'Cause i've been using it for a while, and there was nothing critical in it
...
It should be better then v20, but both have the problem that it eats battery
in suspend - much more then
Oh ok, so i'll give it a try :)
Improved reactivity worth the shorter battery :D
--
Gand'
On Fri, May 14, 2010 at 10:24 AM, Radek Polak pson...@seznam.cz wrote:
On Friday 14 May 2010 00:33:48 Gand' wrote:
Do you mean it's significantly more unstable than the v20 ?
'Cause i've been using
On Friday 14 May 2010 11:52:09 Gand' wrote:
Oh ok, so i'll give it a try :)
Improved reactivity worth the shorter battery :D
I think v22 is most reactive - after debug stuff was removed i subjectively
think it's the fastest what we had.
Regards
Radek
Hi,
The new version appears to work fine here (just a quick test so far).
BTW, my Ubuntu laptop (Xubuntu 9.10) exhibits a strange symptom: each time I
connect my FR, the network interface name increases:
eg. it started out with 'eth9' (what happened with usb0?), the next time I
connected the FR
Is this possible to update from v20 to v23 without flashing ?
--
Gand'
On Wed, May 12, 2010 at 7:43 AM, Radek Polak pson...@seznam.cz wrote:
On Wednesday 12 May 2010 02:13:13 Denis Johnson wrote:
I re-flashed with latest v23 files
Just a warning note: v23 is still not good enough for
Gand' wrote:
Is this possible to update from v20 to v23 without flashing ?
You can always update manually if you replace /opt and check the differences in
rootfs.
But v23 is experimental based on 2.6.32. I'd recommend it only for testing not
for serious using now.
Regards
Radek
Do you mean it's significantly more unstable than the v20 ?
'Cause i've been using it for a while, and there was nothing critical in it
...
--
Gand'
On Thu, May 13, 2010 at 10:01 PM, Radek Polak pson...@seznam.cz wrote:
Gand' wrote:
Is this possible to update from v20 to v23 without
Hi all,
I started using v22 as my default phone a couple days ago, and for the most
part it has been very stable and worked great.
However, I've noticed that the contact name resolution (for incoming calls)
doesn't work.
If I initiate the call it works fine, but whenever I have something
Thanks for all your hard work and efforts.
I re-flashed with latest v23 files and my first call, although I could
hear the other party pretty well (although I would like to increase
the volume), the other party complained of bad distortion so I guess
it is time to find the correct mix of state
On Wednesday 12 May 2010 02:13:13 Denis Johnson wrote:
I re-flashed with latest v23 files
Just a warning note: v23 is still not good enough for daily use. It's based on
2.6.32 and it has problems with power management. For daily use i'd recommend
v22.
Regards
Radek
Feedback for sms.
There are no problems in receving messages (short sms or long sms). The
problem in sending long sms still remains. If the sms is 3 pages long then
an error appears and the recipient receives only 2 parts of 3 of the sms. If
the sms is 2 pages long there is no error and the
Hi
Please take a piggy bank:
- googlecontactsync still misses phones, but now found only if they are the
same type (2 mobile, 2 workers, etc.)
Mail in this case does not pass.
-
Thank you for your attention.
--
View this message in context:
My bad..
I follow instructions on french wiki, it tells to modify DeepSleep in
Active=always (as shr in fact)
I modified it in the right way (Active=yes) and I got
Apr 28 09:10:37 neo Qtopia: AtChat : T : AT%SLEEP=4
So it sounds good, let's wait for an experiment in the real life now
On Wednesday 28 April 2010 09:16:09 Yann SLADEK wrote:
My bad..
I follow instructions on french wiki, it tells to modify DeepSleep in
Active=always (as shr in fact)
I modified it in the right way (Active=yes) and I got
Apr 28 09:10:37 neo Qtopia: AtChat : T : AT%SLEEP=4
So it
Hi Radek,
Thanks a lot for this version
Have you planned testing release with 2.6.32 kernel ?
Regards,
Yann
- Mail Original -
De: Radek Polak pson...@seznam.cz
À: List for Openmoko community discussion community@lists.openmoko.org
Envoyé: Mardi 27 Avril 2010 11:33:37 GMT +01:00
On Tuesday 27 April 2010 16:19:20 Yann SLADEK wrote:
Thanks a lot for this version
Have you planned testing release with 2.6.32 kernel ?
I have not worked on 2.6.32 since last release. I want some stable version
which has no annoying bugs (hopefully it's v22?). But then i would like to
: List for Openmoko community discussion community@lists.openmoko.org
Envoyé: Mardi 27 Avril 2010 16:44:39 GMT +01:00 Amsterdam / Berlin / Berne /
Rome / Stockholm / Vienne
Objet: Re: QtMoko v22
On Tuesday 27 April 2010 16:19:20 Yann SLADEK wrote:
Thanks a lot for this version
Have you planned
On Tuesday 27 April 2010 17:00:52 Yann SLADEK wrote:
What are the annoying bugs you're talking about ?
I'm on v21 (or v20 I don't remember but 2.6.32 kernel) for a month now and
I didn't see any regressions (touchscreen is smoother, speed has been
improved, etc..)
Oki, nice to hear it.
The
I'm also using kernel 2.6.32, and there is no problem with it (if you except
the poor battery life ...)
--
Gand'
On Tue, Apr 27, 2010 at 6:15 PM, Radek Polak pson...@seznam.cz wrote:
On Tuesday 27 April 2010 17:00:52 Yann SLADEK wrote:
What are the annoying bugs you're talking about ?
I have also implemented power management for locked/unlocked screen. If
you
set intervals to 0 in When locked mode - it will not be used and Qtmoko
will
use suspend intervals based on power source. This feature is still quite
experiment and i think sometimes it does now properly.
I
Looks like need to upgrade to v22 - i'm on shr now because of no rcv smses on
QtMoko ;/
Thx Radek!
Dnia 27 kwietnia 2010 19:52 Gand' lt;gand...@viroenforce.comgt; napisał(a):
I'm also using kernel 2.6.32, and there is no problem with it (if you except
the poor battery life ...)
--
Gand'
On
Ok one bug - have Message Icon on Home screen with info SMS Full - looks like
smses are not deleted from sim.
System Info shows 25 smses used/ 0 free. How to easy delete all of them just
from sim? When locked kicks ass. Best regards.Bartlomiej Zimon.ps. i have
still problems with qt/qtmoko
On Tuesday 27 April 2010 17:00:52 Yann SLADEK wrote:
The only weird thing I got is a poor battery life (24h
max) althought I have a buzzfixed GTA02 (the battery goes up to 80h with
SHR for example). I did the modification of the right file but I have the
same behaviour than with Android who
45 matches
Mail list logo
