Re: [FSO] M4.1 issues (GPS, Suspend)

2008-12-15 Thread Olivier Migeot
On Sat, Dec 13, 2008 at 11:44 AM, Michael 'Mickey' Lauer
mic...@openmoko.org wrote:

 Yes, integration with illume -- or X and a window manager in general is not
 perfect yet.

Well, at least it works :)

 Yes, I have seen this, but not been able to reproduce with meaningful logs. I
 would appreciate creating an FSO ticket w/ debug logs.

I'll try to get you those. It's not that hard to reproduce, but
setting a debug environment seemed a little daunting to me. But it's
just a matter of time, I guess :)

BTW, one of the previous posters suggested restarting Zhone when the
problem occurs, and I can confirm that it works for me so far. Not a
perfect solution, but at least I can keep on using FSO (already had a
few calls in and out, and no echo noticed by me nor by my
callers/callees).

 You have run 'mdbus -s -l' in another shell? cli-framework is not able to show
 you the async. signals.

Tried this. I see some signals occuring in the mdbus shell, but
nothing related to GPS, no matter how long I keep it on or how often I
query it from cli-framework. Odd, I would at least expect some kind of
I'm not working signals, but there nothing.

-- 
Olivier

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [FSO] M4.1 issues (GPS, Suspend)

2008-12-13 Thread Andy Green
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Somebody in the thread at some point said:
| Hi,
|
| Andy Green a...@openmoko.com writes:
| | while, it gets unable to go to sleep. I can press the power button ten
| | times, it still stays on. Only way I found for now is to reboot. Not
| | pretty :/
|
| This is a kernel issue I think, it should be gone in andy-tracking based
| kernels with Balaji's new regulator based PMU driver in.
|
| It seems to me it's not. I used stable for some time and seen the
| same issue. Now i switched to andy-tracking and it's just the same
| (though suspends now seems to be faster). The FSO issues several
| commands to the GSM modem prior to suspending, if they fail, it

Yes if userspace is getting the button presses and eating them, it will
give same end result.  There was a bug flying around where we lose an
interrupt from the PMU and after that we don't get notified about button
presses: that should be gone anyway.

| But you are right, it's time to try the new kernel, as FSO works ok
| with it (minor modifications necessary, reported on fso trac).

Great.

- -Andy


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAklDjVIACgkQOjLpvpq7dMpJSwCghmdBzV5MlALdJ77fzUB2TrJH
edoAn2mpGR9fySWZF46WcZEKXjcAW/sV
=P8L7
-END PGP SIGNATURE-

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [FSO] M4.1 issues (GPS, Suspend)

2008-12-13 Thread Michael 'Mickey' Lauer
Hi Olivier,

  - It looks like the only way to go into suspend is to press the power
 button shortly. That's ok for me, but Illume's config is still stating
 suspend happens just after blanking, which itself occurs after 30s of
 idling. But since I prefer to chose when I suspend, I won't complain
 (it's just a little odd).

Yes, integration with illume -- or X and a window manager in general is not 
perfect yet.

 What's worse is that sometimes, after a
 while, it gets unable to go to sleep. I can press the power button ten
 times, it still stays on.

Yes, I have seen this, but not been able to reproduce with meaningful logs. I 
would appreciate creating an FSO ticket w/ debug logs.

 I'm completely in love with the cli-framework
 command. I mean, this is exactly the reason why I hopped on the
 OpenMoko wagon.  I can tweak, explore, experiment, and I like that.

Glad to hear that, this is why we did that way.

 problem is, GPS subsystem doesn't seem to work at all (either through
 Zhone, Tango or cli-framework). I launch cli, Request GPS resource
 (which took less than 10 secondes). And then, I can wait forever, I
 can't see a single satellite (through GetSatellites()).

You have run 'mdbus -s -l' in another shell? cli-framework is not able to show 
you the async. signals.

-- 
:M:

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


[FSO] M4.1 issues (GPS, Suspend)

2008-12-12 Thread Olivier Migeot
Hello ev'rybody.

For a few days, I've been testing FSO M4.1, mostly because of my
latest (and noisy) problems with QTE. Just to be safe, I kept QTE on
the internal storage, and put FSO on the SD card. First of all, kudos
to FSO Team : it's really starting to look and feel good. For now,
only two things are preventing me to move for real :

 - It looks like the only way to go into suspend is to press the power
button shortly. That's ok for me, but Illume's config is still stating
suspend happens just after blanking, which itself occurs after 30s of
idling. But since I prefer to chose when I suspend, I won't complain
(it's just a little odd). What's worse is that sometimes, after a
while, it gets unable to go to sleep. I can press the power button ten
times, it still stays on. Only way I found for now is to reboot. Not
pretty :/
 - I'm not sure whether this one is a problem or not, and I'd like to
be (sure, that is). I'm completely in love with the cli-framework
command. I mean, this is exactly the reason why I hopped on the
OpenMoko wagon. I can tweak, explore, experiment, and I like that. The
problem is, GPS subsystem doesn't seem to work at all (either through
Zhone, Tango or cli-framework). I launch cli, Request GPS resource
(which took less than 10 secondes). And then, I can wait forever, I
can't see a single satellite (through GetSatellites()). Not even a
little one with a weak signal or anything. gpstime.GetTime() is still
returning 0. Maybe it's just my lack of luck (I'd rather). Some time
ago, I managed to get a fix both with QTE4.4 demo and another (Gtk
based) GPS test app. Is this the normal behaviour of a GwaF (GPS
without a Fix), or not?

Thanks by advance :)

-- 
Olivier

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [FSO] M4.1 issues (GPS, Suspend)

2008-12-12 Thread Andy Green
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Somebody in the thread at some point said:

| while, it gets unable to go to sleep. I can press the power button ten
| times, it still stays on. Only way I found for now is to reboot. Not
| pretty :/

This is a kernel issue I think, it should be gone in andy-tracking based
kernels with Balaji's new regulator based PMU driver in.

- -Andy


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAklCguwACgkQOjLpvpq7dMo0FwCcDDds9tMfQCGvY/flb8ks4OTL
me4An2qEkLRMKeF0dSi8kl5zj6HbfjOV
=2VK8
-END PGP SIGNATURE-

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [FSO] M4.1 issues (GPS, Suspend)

2008-12-12 Thread Antony King
This is the behavour I noticed; it seems that the GPS resets itself for some 
reason and then ogpsd/frameworkd can't talk to it any more because it is 
expecting UBX but is getting NMEA. There's a bug #265 against it but not been 
a lot of activity on that recently. Search the mailing list for GPS - it came 
up originally in a debian distro but with the same symptoms so it's most 
likely a frameworkd problem rather than FSO specific.

On FSO M4 , on the GPS app in Zhone, you can get status info for each 
satellite by pressing the unlabled buttons on screen; even without a fix you 
should normally get a few with 'signal unusable' or 'downloading' or 
something other than 'searching' even if you are indoors (for certain values 
of indoors of course).


On Friday 12 December 2008 14:53:53 Olivier Migeot wrote:

 For a few days, I've been testing FSO M4.1, mostly because of my
snip
 problem is, GPS subsystem doesn't seem to work at all (either through
 Zhone, Tango or cli-framework). I launch cli, Request GPS resource
 (which took less than 10 secondes). And then, I can wait forever, I
 can't see a single satellite (through GetSatellites()). Not even a
 little one with a weak signal or anything. gpstime.GetTime() is still
 returning 0. Maybe it's just my lack of luck (I'd rather). Some time
 ago, I managed to get a fix both with QTE4.4 demo and another (Gtk
 based) GPS test app. Is this the normal behaviour of a GwaF (GPS
 without a Fix), or not?

 Thanks by advance :)



-- 

Antony King - 01908 268 901
Systems Consultant
SolutionTrax Technologies - http://www.solutiontrax.com

___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community


Re: [FSO] M4.1 issues (GPS, Suspend)

2008-12-12 Thread Paul Fertser
Hi,

Andy Green a...@openmoko.com writes:
 | while, it gets unable to go to sleep. I can press the power button ten
 | times, it still stays on. Only way I found for now is to reboot. Not
 | pretty :/

 This is a kernel issue I think, it should be gone in andy-tracking based
 kernels with Balaji's new regulator based PMU driver in.

It seems to me it's not. I used stable for some time and seen the
same issue. Now i switched to andy-tracking and it's just the same
(though suspends now seems to be faster). The FSO issues several
commands to the GSM modem prior to suspending, if they fail, it
doesn't try to enter suspend. The suspend should work, it can be
checked by echo mem  /sys/power/state (though it will resume
shortly and consume more energy than needed, because of the GSM). Also
i'm always able to suspend again after restarting gsm0710muxd (by
exiting Zhone, in example) or killing the whole frameworkd along with
gsm0710muxd.

But you are right, it's time to try the new kernel, as FSO works ok
with it (minor modifications necessary, reported on fso trac).

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com


___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community