[FSO] GPS-problems / tangogps in testing-feed broken
Hi,
(I'm mailing to this list because I don't know where to post bug reports
targetting the package-management in the fso-{testing,unstable}-feeds.
Is trac.freesmartphone.org the right place?)
My problem: I'm experiencing problems with GPS since an upgrade with the
fso-testing-feed.
After the upgrade neither tangogps (tangogps-fso_0.9.2-r1) nor zhone
(0.0.0+gitr69e029bd85a1caaad4e5d61087836a8e1ea20dcc-r8) are getting a
fix which hadn't been such a problem before (same outdoors place as
before, rather grey weather conditions but not entirely clouded, 30 mins
waiting).
One problem definitely is that tangogps throwing two TypeErrors which
show that it's having trouble with the dbus-interface[1].
Has there been a change in the dbus-interface which hasn't been followed
in the packages? Is this part of the yesterday on this list mentioned
major frameworkd changes[3]? If yes: How comes they're in the
testing-feed (would expect them in unstable, if at all)?
zhone only tells gps ok[2], so I don't know if it's suffering from the
same problem or just having a bad time with the available gps data.
As the weather is quite bad ATM, I cannot debug further. It might also
be that zhone and agpsui (didn't know there's a fso-compatible version
until a few minutes ago) would show a fix once the sky is clear again
(probably next april... :/), but the tangogps-error probably should be
taken care of.
Anybody else having problems?
Thanks and Greetings,
/Ben
[1]
** (tangogps:1439): WARNING **: Cannot get position: Traceback
(most recent call last):
File /usr/lib/python2.5/site-packages/dbus/service.py, line 745, in
_message_cb
_method_reply_return(connection, message, method_name, signature, *retval)
File /usr/lib/python2.5/site-packages/dbus/service.py, line 252, in
_method_reply_return
reply.append(signature=signature, *retval)
TypeError: More items found in D-Bus signature than in Python arguments
** (tangogps:1439): WARNING **: Cannot get accuracy: Traceback (most recent
call last):
File /usr/lib/python2.5/site-packages/dbus/service.py, line 745, in
_message_cb
_method_reply_return(connection, message, method_name, signature, *retval)
File /usr/lib/python2.5/site-packages/dbus/service.py, line 252, in
_method_reply_return
reply.append(signature=signature, *retval)
TypeError: More items found in D-Bus signature than in Python arguments
[2]
DEBUG gps ok: Interface ProxyObject wrapping dbus._dbus.SystemBus (system)
at 0x12cf90 :1.3 /org/freedesktop/Gypsy at 0x12f930 implementing
'org.freedesktop.Gypsy.Accuracy' at 0x12fb30, Interface ProxyObject wrapping
dbus._dbus.SystemBus (system) at 0x12cf90 :1.3 /org/freedesktop/Gypsy at
0x12f930 implementing 'org.freedesktop.Gypsy.Position' at 0x12fc30,
Interface ProxyObject wrapping dbus._dbus.SystemBus (system) at 0x12cf90
:1.3 /org/freedesktop/Gypsy at 0x12f930 implementing
'org.freedesktop.Gypsy.Satellite' at 0x12fd30
[3]
Message-ID: [EMAIL PROTECTED]
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [FSO] GPS-problems / tangogps in testing-feed broken
Hello,
On Fri, Aug 22, 2008 at 8:51 PM, Benito Torres [EMAIL PROTECTED] wrote:
Hi,
(I'm mailing to this list because I don't know where to post bug reports
targetting the package-management in the fso-{testing,unstable}-feeds.
Is trac.freesmartphone.org the right place?)
My problem: I'm experiencing problems with GPS since an upgrade with the
fso-testing-feed.
FWIW, I am running FSO-testing on my Neo 1973 (not the FreeRunner). I
am using an external antenna, and have verified that it is workng on
my FreeRunner (which doesn't run FSO).
Since this is a 1973, I have installed gllin[1], and dbus-monitor
shows that gps events are sent:
[EMAIL PROTECTED]:~# dbus-monitor --system
signal sender=org.freedesktop.DBus - dest=:1.9
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus;
member=NameAcquired
string :1.9
signal sender=:1.3 - dest=(null destination) path=/org/gpsd;
interface=org.gpsd; member=fix
double nan
int32 1
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
signal sender=:1.3 - dest=(null destination) path=/org/gpsd;
interface=org.gpsd; member=fix
double nan
int32 1
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
double nan
And the output from gpsd shows that it gets a fix:
[EMAIL PROTECTED]:~# cat /tmp/nmeaNP | grep GPRMC
$GPRMC,212405.00,A,5955.147356,N,01045.531408,E,000.0,000.0,220808,,,A*5B
$GPRMC,212406.00,A,5955.147356,N,01045.531408,E,000.0,000.0,220808,,,A*58
$GPRMC,212407.00,A,5955.147356,N,01045.531408,E,000.0,000.0,220808,,,A*59
$GPRMC,212408.00,A,5955.147356,N,01045.531408,E,000.0,000.0,220808,,,A*56
$GPRMC,212410.00,A,5955.147356,N,01045.531408,E,000.0,000.0,220808,,,A*5F
$GPRMC,212412.00,A,5955.147356,N,01045.531408,E,000.0,000.0,220808,,,A*5D
$GPRMC,212413.00,A,5955.148148,N,01045.532991,E,000.0,000.0,220808,,,A*50
$GPRMC,212414.00,A,5955.148405,N,01045.532836,E,000.0,000.0,220808,,,A*57
$GPRMC,212415.00,A,5955.148596,N,01045.532664,E,000.0,000.0,220808,,,A*54
$GPRMC,212416.00,A,5955.148760,N,01045.532491,E,000.0,000.0,220808,,,A*54
$GPRMC,212417.00,A,5955.148760,N,01045.532491,E,000.0,000.0,220808,,,A*55
$GPRMC,212419.00,A,5955.148760,N,01045.532491,E,000.0,000.0,220808,,,A*5B
$GPRMC,212421.00,A,5955.149661,N,01045.531970,E,000.0,000.0,220808,,,A*50
$GPRMC,212422.00,A,5955.149853,N,01045.531870,E,000.0,000.0,220808,,,A*5D
$GPRMC,212423.00,A,5955.150058,N,01045.531689,E,000.0,000.0,220808,,,A*5F
$GPRMC,212424.00,A,5955.150058,N,01045.531689,E,000.0,000.0,220808,,,A*58
$GPRMC,212425.00,A,5955.150058,N,01045.531689,E,000.0,000.0,220808,,,A*59
$GPRMC,212426.00,A,5955.150058,N,01045.531689,E,000.0,000.0,220808,,,A*5A
$GPRMC,212427.00,A,5955.150883,N,01045.531326,E,000.0,000.0,220808,,,A*55
Nut neither zhone nor tangoGPS gets anything, not even time from the gps.
References:
1) http://wiki.openmoko.org/wiki/Gllin
--
Regards,
Torfinn Ingolfsen
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [FSO] GPS-problems / tangogps in testing-feed broken
Hi, On Fri, Aug 22, 2008 at 23:27 (+0200), Torfinn Ingolfsen wrote: signal sender=:1.3 - dest=(null destination) path=/org/gpsd; interface=org.gpsd; member=fix I don't see this kind of message. Maybe that's due to different daemon-implementations on different hardware? Also all dbus-paths start with /org/freesmartphone/ here. Anyway I'm sure this is an application/dbus-problem as in the meantime I ran agpsui successfully: 90 seconds for the first fix. But even after agpsui having a fix, zhone is still clueless -- which can be explained by agpsui parsing ttySAC1 directly. (Interesstingly I can start and stop gpsd to my pleasure without any changes for agpsui or zhone. What's gpsd for, anyway?) Manually asking Gypsy via dbus reveals, that the dbus-interface is broken as it prints the same message that tangogps reported: dbus-send --system --print-reply --dest=org.freesmartphone.ogpsd /org/freedesktop/Gypsy org.freedesktop.Gypsy.Position.GetPosition Error org.freedesktop.DBus.Python.TypeError: Traceback (most recent call last): File /usr/lib/python2.5/site-packages/dbus/service.py, line 745, in _message_cb _method_reply_return(connection, message, method_name, signature, *retval) File /usr/lib/python2.5/site-packages/dbus/service.py, line 252, in _method_reply_return reply.append(signature=signature, *retval) TypeError: More items found in D-Bus signature than in Python arguments Other methods like GetAccuracy fail, too, while GetSatellites successfully returns an empty array and GetConnectionStatus returns 1. Could anybody with more insights to the frameworkd/dbus-development shed some light on this? Is this a known problem? Should we simply wait for the next package? Thanks, /Ben ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
