Hello, after my "install from scratch" (reported here: http://lists.linuxtogo.org/pipermail/smartphones-userland/2009-August/001861.html) I can't get anything useful from GPS. This used to work without a problem, so I exclude a possible hardware problem at the moment).
I did install the firmware update some time ago: +CGMR: "GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko11" There is a thread on this list possibly describing the same problem but no answer ([Debian] tangogps not work after update): http://lists.linuxtogo.org/pipermail/smartphones-userland/2009-March/001286.html Searching around for a bit, I came across this: http://totalueberwachung.de/blog/2008/10/14/fso-tutorial-part-1-gps Assuming that the description in there is still valid, trying to talk to gps (while zhones gps thingie is running and thus GPS should be active) goes like this: neo:~# cli-framework ERROR:dbus.proxies:Introspect error on org.freesmartphone.DBus:/org/freesmartphone/DBus: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freesmartphone.DBus was not provided by any .service files DBus Exception. dbus-hlid not installed DBus Exception. dbus-hlid not installed DBus Exception. dbus-hlid not installed ERROR:dbus.proxies:Introspect error on org.bluez:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided by any .service files failed to connect to bluez freesmartphone.org interactive command line >>> I assume at this point, that dbus is working in principle (I can make calls). So I request GPS and a position: >>> usageiface.RequestResource("GPS") >>> gpsposition.GetPosition() (0, 0, 0.0, 0.0, 0.0) It takes a few seconds but does complete without error messages. So it seems I can talk to the GPS hardware. Going outside and starting the gps part of zhone I used to see the lines "searching" change to "signal unusable" and "signal aquired" within a minute or so. Now the lines do not change within say 10 minutes. FWIW: booting into OM2009, running tangogps there will get a fix in less than 10 minutes. I decided to enable logging of frameworkd ... Lots of lines like these: 2009.08.23 13:08:30 ogpsd DEBUG Discarded data not UBX '\n$GPGSA,' 2009.08.23 13:08:30 ogpsd DEBUG Discarded data not UBX 'A,1,,,,,,,,,,,,,' 2009.08.23 13:08:30 ogpsd DEBUG Discarded data not UBX '99.99,99' 2009.08.23 13:08:30 ogpsd DEBUG Discarded data not UBX '.99,99.9' 2009.08.23 13:08:30 ogpsd DEBUG Discarded data not UBX '9*30\r\n$G' So it seems that ogpsd is expecting UBX data but is instead getting NMEA data. So I changed /etc/frameworkd.conf [ogpsd] # set 1 to disable a module disable = 0 # possible options are NMEADevice, UBXDevice, GTA02Device, EtenDevice -device = GTA02Device +device = NMEADevice # possible options are SerialChannel, GllinChannel, UDPChannel, FileChannel channel = SerialChannel # For UDPChannel the path defines the port to listen to path = /dev/ttySAC1 And presto: there comes the fix again. So questions remain: 1. is the update to Moko11 firmware changing the behaviour? 2. is ogpsd not requesting UBX data correctly? 3. is this the way its supposed to be? 4. what exactly is introducing the change? 5. where should it be fixed? Cheers, Erich _______________________________________________ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
