![]() |
Quote:
Quote:
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. |
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.
|
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.
|
Quote:
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 Hope it works for you. |
Quote:
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. |
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. |
Quote:
|
Quote:
Quote:
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. Quote:
|
Quote:
Quote:
<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 |
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. |
All times are GMT. The time now is 12:06. |
vBulletin® Version 3.8.8