Re: Help with FSO calls timeouts (was: (om2009) OpenBmap client keeps crashing)
I reflashed om2009 (latest unstable) only to see that paroli can't always login to network (well actually now that I mention it, I was able to see it also on the previous isntallatin - paroli often gave me the about 10 error messages..) here are last lines from /var/log/paroli.log http://pastebin.com/m18850984 otoh frameork log doesn't know anything about this: http://pastebin.com/m37b98cf3 (lines printed with tail) Is it paroli or fso that's failing? I might be able to provide more logs if needed r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Help with FSO calls timeouts (was: (om2009) OpenBmap client keeps crashing)
restarting a couple of times lets me use paroli, gps and everything with no problems! I actually was able to run 4 apps at the same time using gps, not bad! And Paroli connects to gsm networks nicely. Thanks! r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Help with FSO calls timeouts (was: (om2009) OpenBmap client keeps crashing)
comments inline On Thu, Aug 6, 2009 at 10:19 PM, Onenonen...@free.fr wrote: I changed the subject, in order to try bringing attention to your timeouts issues... good If paroli doesn't run, it wont start at all. This might be because my application does not request the GSM ressource. Thus, if GSM is not up and running, requested by another application, I am not sure of how nice it handles it. Thats what I thought. Requesting the GSM resource might be a good idea, if FSO can handle more than one app doing it: this way I shouldnt have to run other apps if I just want to log stuff. I have some problems with GPS, I feel that Tangogps or openbmap alone can't actually ever see any satelites, but if I first start omgps (using ublox), I get a nice fix and then when I start openbmap or tango, it changes to fso and things sometimes work. Well I request GPS ressource and uses it through FSO API here. So at the moment I can't see my application being guilty here. Understand Sometimes (like every 20th restart - I really mean it, i've wasted hours in the bus trying to run this and it's actually very frustrating...) it starts with no problems but then I can't turn it on (to make it actually store cell info) but it freezes and suddenly shows no UI. Difficult to help without logs... A very quick response would be a timeout about the GPS response (as you explain you meet difficulties with it) which my app does not handle correctly (but this never happened to me so far...). What logs you want? fso? does openbmap strore it's own logs in .openbmap.. will check.. In this case I request a ressource (GPS and CPU, the latter for preventing the phone to suspend, but allow the screen to dim light) through FSO D-Bus API. This calls times out. For some reason I had this bad feeling that actually it's FSO that fails, not openbmap.. Too bad I'm missing many cells, can't get higher in the openbmap stats :) That is very much annoying yes! You should have a backup distribution installed on SD card in case of ;-) Well yes, true.. I just didn't believe it that suddenly sometghint would break so that things stop working if I don't install anything.. I've heard they call Linux stable so I trusted.. :) The only changing thing here is the country and the GSM cells, other than that I really can't come up with anything that has changed. r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Help with FSO calls timeouts (was: (om2009) OpenBmap client keeps crashing)
On 8/7/09, Risto H. Kurppa ri...@kurppa.fi wrote: This might be because my application does not request the GSM ressource. Thus, if GSM is not up and running, requested by another application, I am not sure of how nice it handles it. Thats what I thought. Requesting the GSM resource might be a good idea, if FSO can handle more than one app doing it: this way I shouldnt have to run other apps if I just want to log stuff. FSO can handle more than one app requesting resource (that's what resources are supposed to do by design), but then openBmap will have to implement PIN handling and few other things. And you'll miss calls when you'll use only GSM-aware openBmap without any other phone app. So I can't see much sense with openBmap requesting GSM resource... -- Sebastian Krzyszkowiak dos ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
(om2009) OpenBmap client keeps crashing
Hi!
I'm travelling with om2009 unstable from about 2 weeks ago. I'm having
hard time running openbmap and recording cells, most of the times it
crashes when I try to start it.
If paroli doesn't run, it wont start at all.
I have some problems with GPS, I feel that Tangogps or openbmap alone
can't actually ever see any satelites, but if I first start omgps
(using ublox), I get a nice fix and then when I start openbmap or
tango, it changes to fso and thigs sometimes work.
Sometimes (like every 20th restart - I really mean it, i've wasted
hours in the bus trying to run this and it's actually very
frustrating...) it starts with no problems but then I can't turn it on
(to make it actually store cell info) but it freezes and suddenly
shows no UI.
It's now been about a week travelling when I haven't been able to
record any cells, because can't start openbmap. It tries to do its
magic for some minutes (I have paroli running, sometimes also omgps
with gps fix)
Traceback (most recent call last):
File /usr/bin/openBmapGTK, line 356, in module
hwg = openBmapGTK()
File /usr/bin/openBmapGTK, line 130, in __init__
self._obmlogger = openbmap.logger.ObmLogger()
File /usr/lib/python2.6/site-packages/openbmap/logger.py, line
832, in __init__
self._gsm = Gsm(self._bus)
File /usr/lib/python2.6/site-packages/openbmap/logger.py, line 64,
in __init__
self.get_device_info()
File /usr/lib/python2.6/site-packages/openbmap/logger.py, line
223, in get_device_info
data = dbus.Interface(obj, 'org.freesmartphone.GSM.Device').GetInfo()
File /usr/lib/python2.6/site-packages/dbus/proxies.py, line 68, in __call__
return self._proxy_method(*args, **keywords)
File /usr/lib/python2.6/site-packages/dbus/proxies.py, line 140, in __call__
**keywords)
File /usr/lib/python2.6/site-packages/dbus/connection.py, line
622, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did
not receive a reply. Possible causes include: the remote application
did not send a reply, the message bus security policy blocked the
reply, the reply timeout expired, or the network connection was
broken.
or this:
Traceback (most recent call last):
File /usr/bin/openBmapGTK, line 356, in module
hwg = openBmapGTK()
File /usr/bin/openBmapGTK, line 132, in __init__
self._obmlogger.init_openBmap()
File /usr/lib/python2.6/site-packages/openbmap/logger.py, line
1118, in init_openBmap
self.request_ressource('CPU')
File /usr/lib/python2.6/site-packages/openbmap/logger.py, line
859, in request_ressource
request = dbus.Interface(obj,
'org.freesmartphone.Usage').RequestResource(resource)
File /usr/lib/python2.6/site-packages/dbus/proxies.py, line 68, in __call__
return self._proxy_method(*args, **keywords)
File /usr/lib/python2.6/site-packages/dbus/proxies.py, line 140, in __call__
**keywords)
File /usr/lib/python2.6/site-packages/dbus/connection.py, line
622, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply:
Message did not receive a reply (timeout by message bus)
I have no idea it it's because of openbmap or fso but I'd really
appreciate it if someone could gice me a tip if there's something I
can do to fix this. It just stopped working some days ago without any
upgrade or program installation (I haven't had the phone connected to
internet for a week or so).
Too bad I'm missing many cells, can't get higher in the openbmap stats :)
r
--
| risto h. kurppa
| risto at kurppa dot fi
| http://risto.kurppa.fi
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Help with FSO calls timeouts (was: (om2009) OpenBmap client keeps crashing)
I changed the subject, in order to try bringing attention to your
timeouts issues...
Hi Risto,
let's see how I can help you!
Risto H. Kurppa wrote:
If paroli doesn't run, it wont start at all.
This might be because my application does not request the GSM ressource.
Thus, if GSM is not up and running, requested by another application, I
am not sure of how nice it handles it.
I have some problems with GPS, I feel that Tangogps or openbmap alone
can't actually ever see any satelites, but if I first start omgps
(using ublox), I get a nice fix and then when I start openbmap or
tango, it changes to fso and things sometimes work.
Well I request GPS ressource and uses it through FSO API here. So at the
moment I can't see my application being guilty here.
Sometimes (like every 20th restart - I really mean it, i've wasted
hours in the bus trying to run this and it's actually very
frustrating...) it starts with no problems but then I can't turn it on
(to make it actually store cell info) but it freezes and suddenly
shows no UI.
Difficult to help without logs... A very quick response would be a
timeout about the GPS response (as you explain you meet difficulties
with it) which my app does not handle correctly (but this never happened
to me so far...).
It's now been about a week travelling when I haven't been able to
record any cells, because can't start openbmap. It tries to do its
magic for some minutes (I have paroli running, sometimes also omgps
with gps fix)
Traceback (most recent call last):
File /usr/bin/openBmapGTK, line 356, in module
hwg = openBmapGTK()
File /usr/bin/openBmapGTK, line 130, in __init__
self._obmlogger = openbmap.logger.ObmLogger()
File /usr/lib/python2.6/site-packages/openbmap/logger.py, line
832, in __init__
self._gsm = Gsm(self._bus)
File /usr/lib/python2.6/site-packages/openbmap/logger.py, line 64,
in __init__
self.get_device_info()
File /usr/lib/python2.6/site-packages/openbmap/logger.py, line
223, in get_device_info
data = dbus.Interface(obj, 'org.freesmartphone.GSM.Device').GetInfo()
File /usr/lib/python2.6/site-packages/dbus/proxies.py, line 68,
in __call__
return self._proxy_method(*args, **keywords)
File /usr/lib/python2.6/site-packages/dbus/proxies.py, line 140,
in __call__
**keywords)
File /usr/lib/python2.6/site-packages/dbus/connection.py, line
622, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did
not receive a reply. Possible causes include: the remote application
did not send a reply, the message bus security policy blocked the
reply, the reply timeout expired, or the network connection was
broken.
In this case, the application calls a D-Bus FSO API in order to get
hardware details. It seems the framework times out :-(
or this:
Traceback (most recent call last):
File /usr/bin/openBmapGTK, line 356, in module
hwg = openBmapGTK()
File /usr/bin/openBmapGTK, line 132, in __init__
self._obmlogger.init_openBmap()
File /usr/lib/python2.6/site-packages/openbmap/logger.py, line
1118, in init_openBmap
self.request_ressource('CPU')
File /usr/lib/python2.6/site-packages/openbmap/logger.py, line
859, in request_ressource
request = dbus.Interface(obj,
'org.freesmartphone.Usage').RequestResource(resource)
File /usr/lib/python2.6/site-packages/dbus/proxies.py, line 68,
in __call__
return self._proxy_method(*args, **keywords)
File /usr/lib/python2.6/site-packages/dbus/proxies.py, line 140,
in __call__
**keywords)
File /usr/lib/python2.6/site-packages/dbus/connection.py, line
622, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply:
Message did not receive a reply (timeout by message bus)
In this case I request a ressource (GPS and CPU, the latter for
preventing the phone to suspend, but allow the screen to dim light)
through FSO D-Bus API. This calls times out.
So my application should handle this much more nicely. But, this is
normal that it refuses to start if one of these calls does not succeed.
The only hint I can give you so far, is that I ran under such issues
under Debian when calling the monitoring interface. When this would
happen, then exiting obm, and trying to relaunch it, would bring
timeouts as you meet.
I could not find much info about this so far though :-( I am not sure
what is happening.
I have no idea it it's because of openbmap or fso but I'd really
appreciate it if someone could gice me a tip if there's something I
can do to fix this. It just stopped working some days ago without any
upgrade or program installation (I haven't had the phone connected to
internet for a week or so).
Too bad I'm missing many cells, can't get higher in the openbmap stats :)
That is very much annoying yes! You should have a
