Notices


Reply
Thread Tools
gnuite's Avatar
Posts: 1,245 | Thanked: 421 times | Joined on Dec 2005
#131
Originally Posted by bradb
Actually, I think the real problem is that sometimes the "apps" directory itself is missing (if, for example, you never used the built-in e-mail client). So if you have "/home/user/apps", you'll be fine.
Yes; Maemo Mapper creates the maemo-mapper directory if it doesn't exist, but not the apps dir. The real problem is that there is no mkdir-recursive function in GnomeVFS, which really bothers me. For that reason (and because the GdkPixbuf libraries don't work with URI's anyway), I'll probably forget about using GnomeVFS for the Map Cache.

Originally Posted by bradb
Also it appears that you need to be careful about what other bluetooth devices are near when you run it the first time after the install - the program tried to connect to my desktop (w/ a motorola bluetooth adapter) and it just wouldn't connect to my garmin gps. Even though I had it installed and working fine before (I just did a reflash).

The solution was to run "hcitool scan", note the gps' MAC address, then manually typing it into the settings menu.
Right; in my instructions, I recommended running Maemo Mapper for the first time in the presence of only one bluetooth device: your GPS device. This is because the "auto-detection" only searches for the first bluetooth device that responds. I did this to minimize binary size, since this funtion is only ever used once in the entire use of the program.

In v0.2, I will move the entire "Initial GPS Setup" code into a separate binary that will get run the first time Maemo Mapper is started. This will allow me to make the wizard as arbitrarily large as needed to ease initial setup.
 
Posts: 23 | Thanked: 0 times | Joined on May 2006
#132
Does anybody else have a problem with maemo-wrapper 0.1 ceasing to function after a few minutes of proper operation? It ignores the GPS. Telling it to disable and enable the GPS causes it to start looking for a GPS receiver, but it never finds one. If I reboot and re-run maemo-mapper, it works again. Implication is that there is nothing in the state of the GPS receiver which causes the failure. Problem only seems present when a fix is available.
 
Posts: 7 | Thanked: 0 times | Joined on Dec 2005
#133
Maybe I missed this. Is there a way to enter/store/whatever points of interest? For instance, I want to enter in my house, all my friends' houses, free wifi hotspots, etc. Minimally a dot and a text tag. Nice to have, different color dot or symbol depending on type of POI.
 
Posts: 6 | Thanked: 0 times | Joined on May 2006
#134
Originally Posted by RussNelson
Does anybody else have a problem with maemo-wrapper 0.1 ceasing to function after a few minutes of proper operation? It ignores the GPS. Telling it to disable and enable the GPS causes it to start looking for a GPS receiver, but it never finds one. If I reboot and re-run maemo-mapper, it works again. Implication is that there is nothing in the state of the GPS receiver which causes the failure. Problem only seems present when a fix is available.
I have this problem. Not sure what the reason is, but I suspect it has something to do with power saving on the nokia, or somethink like that (even I read it could be defective units, but everything else works fine for me, so I don't think so). The problem arises also with gpsdrive.

So finally I created a workaround for testing (a better scripting would be great, or another solution). I run this script as root while I'm running maemo-mapper and whenever the connection gets lost, it restart it and maemo-mapper does well refinding the gps.

Code:
#!/bin/sh

LOG_FILE=/tmp/bt_restom.log

> $LOG_FILE

while true ;
do
        result_str="$( hcitool lq $( cat /home/user/gps.id ) 2>&1 )"
        result_value=$?
        echo "$(date): $result_str" >> $LOG_FILE
        if [ $result_value -ne 0 ] ;
        then
                ## Do restom
                echo "$(date): Restarting BT" >> $LOG_FILE
                hciconfig hci0 down
                sleep 1
                hciconfig hci0 up
                echo "$(date): BT restarted" >> $LOG_FILE
        fi

        sleep 15
done
You will need your bt gps address stored at /home/user/gps.id. Also, you can delete logging code if it doesn't matter for you. I was interested in the times the Bluetooth was restarted.

Hope it works for you.
 
Posts: 23 | Thanked: 0 times | Joined on May 2006
#135
Originally Posted by pstorralba
Code:
                hciconfig hci0 down
                hciconfig hci0 up
Running those two commands got it back again. I was going to run strace on it to see what was happening on the system level, but I can't see strace in the Application Catalog. Sounds like it might be somethiing outside maemo-mapper's control.

I've also seen maemo-mapper lock up on restoring from screen blanked. I have debug turned on now, so if that problem recurs, I'll at least know what subr it happened in.
 
gnuite's Avatar
Posts: 1,245 | Thanked: 421 times | Joined on Dec 2005
#136
pstorralba or RussNelson:

Are either of you doing anything special (like also being connected to a cell phone or to a WAP) when this happens?

I thought I saw this happen to me once before, but it went away when I put the cover on and took the cover back off. I did this before I added the "Enable GPS" checkbox to the code, but disabling/enabling that causes the same course of events that is caused by replacing/removing the cover, so my debugging was similar to RussNelson's. Since my actions made the problem go away, but RussNelson's didn't, I can't be sure that I experienced the same thing, but I'd still like to figure out what's going on.

pstorralba: You said you saw the problem with GPS Drive. Was that using GPSD or by having GPS Drive directly connect to the GPS receiver? If the anomaly doesn't manifest itself when using GPSD, it might be a suitable workaround. (GPSD support is coming in Maemo Mapper v0.2.)

Thanks for your help, guys.
 
Posts: 23 | Thanked: 0 times | Joined on May 2006
#137
Originally Posted by gnuite
Are either of you doing anything special (like also being connected to a cell phone or to a WAP) when this happens?
Nope. Not using any other BT devices. Enabling / disabling the GPS doesn't solve the problem for me. With verbose debugging turned on, I can see that it's calling g_iol_cb_error (or something like that; message already scrolled off) with GIOCondition==24 (8 == ERR + 16 == HUP). Then it tries closing and reopening the bluetooth socket.
 
Posts: 6 | Thanked: 0 times | Joined on May 2006
#138
Originally Posted by gnuite
pstorralba or RussNelson:

Are either of you doing anything special (like also being connected to a cell phone or to a WAP) when this happens?
Nothings special. No wireless, nor other BT conection.

Originally Posted by gnuite
pstorralba: You said you saw the problem with GPS Drive. Was that using GPSD or by having GPS Drive directly connect to the GPS receiver? If the anomaly doesn't manifest itself when using GPSD, it might be a suitable workaround. (GPSD support is coming in Maemo Mapper v0.2.)
Both. At first I used GPS Drive with GPSD. I tried connecting directly to the GPS receiver, but it didn't worked.

hciconfig hci0 down/up is the only solution I found. It works also for GPS Drive and GPSD.

Do you know how can I enable more debugging info on the kernel side? I think the problem is down there.

Originally Posted by gnuite
Thanks for your help, guys.
Thanks for your program :-) I can wait to see that 0.2 version.
 
Posts: 481 | Thanked: 190 times | Joined on Feb 2006 @ Salem, OR
#139
Originally Posted by gnuite
If the anomaly doesn't manifest itself when using GPSD, it might be a suitable workaround. (GPSD support is coming in Maemo Mapper v0.2.)
I have the same problem with maemo-mapper and I had same problem with gpsdrive and gpsd.

Originally Posted by pstorralba
I have this problem. Not sure what the reason is, but I suspect it has something to do with power saving on the nokia, or somethink like that (even I read it could be defective units, but everything else works fine for me, so I don't think so). The problem arises also with gpsdrive.
I don't think the problem is from power saving on nokia. I did this with mine to test:
<maemo.org instructions>
1. Using xterm, scan for remote BT devices:
# hcitool scan
2. Copy the adress of the newly found BT GPS receiver. (looks like xx:xx:xx:xx:xx:xx)
3. Start the serial protocol over BT :
# rfcomm bind /dev/rfcomm0 xx:xx:xx:xx:xx:xx
4. After that, your BT GPS should get connected to everytime /dev/rfcomm0 is opened. You can check this by doing:
# cat /dev/rfcomm0
This should give NMEA GPS output.
</maemo.org instructions>


and I left it like that, running, overnight (about 10 hours) and I got the nmea gps output all this time with no intreruption.

-ioan
 
Posts: 2 | Thanked: 0 times | Joined on Mar 2006
#140
first of all, i want to thank gnuite and the others for maemo-mapper and the effort you are putting into this.

but unfortunately i experience problems with the gpx-webservice. i get the error "Error: An error occurred while attempting to retrieve the driving directions - are the source and destination valid?" with sources/destinations that work in google-maps.
 
Reply


 
Forum Jump


All times are GMT. The time now is 05:02.