![]() |
2007-11-30
, 20:49
|
|
Posts: 32 |
Thanked: 7 times |
Joined on Oct 2007
|
#362
|
![]() |
2007-11-30
, 21:00
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#363
|
Google terrain maps work great now... just need the v=w2p.62 argument on the regular street map URL.
The Following User Says Thank You to gnuite For This Useful Post: | ||
![]() |
2007-11-30
, 21:08
|
|
Posts: 32 |
Thanked: 7 times |
Joined on Oct 2007
|
#364
|
![]() |
2007-11-30
, 23:55
|
Posts: 19 |
Thanked: 5 times |
Joined on Nov 2007
|
#365
|
A few, to be tried independently in no particular order, but before I mention them, I should admit that I accidentally introduced a bug in v2.1 (or v2.1.1) that eliminates the "Establishing GPS Fix" window completely. So, Maemo Mapper will show "Connecting to GPS Receiver" while it is connecting to the GPS receiver and also after it has connected to the GPS receiver, while the receiver is establishing a fix, up until the point where the receiver has a fix. So, make sure you're not being bitten by this bug. As for my suggestions....
First, try playing with the new BT pairing features that OS2007 offers. I don't know how well they work on the 770, but try pairing and/or unpairing your BT receiver to see if that helps Maemo Mapper to see your receiver. Sometimes it works better when paired, sometimes it works better when unpaired....
Second, try the "Bluetooth" option in Maemo Mapper's Settings, both with and without filling in a MAC address. When the MAC address field is empty, Maemo Mapper tries to find a GPS receiver on its own - it may have better success than if you specify the MAC address manually. Or, it may not.
Third, try using rfcomm to connect your GPS receiver outside of Maemo Mapper, then use the rfcomm device path (something like "/dev/rfcomm0") in the "File Path" option in Maemo Mapper's Settings. If the "File Path" option doesn't work, try starting GPSD outside of Maemo Mapper and connecting to it directly. If you are using Maemo Mapper v2.1, then gpsd is installed with Maemo Mapper, so in an xterm, run the following command:
(Replace "/dev/rfcomm0" with whichever rfcomm device you created using rfcomm.) Once you've started GPSD, use the "GPSD Host" option in Maemo Mapper's Settings, and specify the host "127.0.0.1" or "localhost". This will force Maemo Mapper to use the GPSD server that you started separately.Code:/usr/sbin/gpsd -n -N -F /tmp/.my_ctrl_sock /dev/rfcomm0
Good luck, and please share your findings in the thread.
![]() |
2007-11-30
, 23:59
|
Posts: 19 |
Thanked: 5 times |
Joined on Nov 2007
|
#366
|
![]() |
2007-12-01
, 05:09
|
Posts: 28 |
Thanked: 1 time |
Joined on Aug 2007
|
#367
|
![]() |
2007-12-02
, 01:49
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#368
|
Hope this help solving the issue that appeared with v2.1. In the meantime, is it possible to find an older v2 version, such as 2.0.5 which is, IIRC, the last version I had, working with the BT GPS, before switching to v2.1.
![]() |
2007-12-03
, 13:59
|
Posts: 98 |
Thanked: 3 times |
Joined on Nov 2007
@ Knightdale, NC
|
#369
|
Hi Gnuite,
First, thanks for mapper, my prefered app with FBReader.
I have basically the same setup than Dburr, N770 with 2007HE and a BT GPS. Since Mapper v2.1, it doesn't connect to the GPS. I have tried your first two suggestions since I still have to learn how rfcomm work. The trials was made on your last version, v2.2, installed a few minutes ago. The results are:
- Pairing the BT GPS doesn't make any difference. Same 3 attempts to connect to the GPS based on the waiting icon beside the message "Searching for GPS receiver", BT icon appearing each time, same message at the end "Error connecting to GPSD server. Retry?" (Yes, BT GPS was selected, not GPSD)
- Having the MC address defined do change the way Mapper react. With the MAC address, it reacts as described above with the GPSD error message. Without a MAC address, the message "Searching for GPS receiver" will appear 3 times also, but with a much faster cycle and no BT icon so it apparently do not make any attempt to connect through BT. Beside, the error message is now correct, saying "Error connecting to GPS receiver. Retry?" instead of GPSD as above.
Hope this help solving the issue that appeared with v2.1. In the meantime, is it possible to find an older v2 version, such as 2.0.5 which is, IIRC, the last version I had, working with the BT GPS, before switching to v2.1.
And thanks again for this great app.
Vincent
![]() |
2007-12-03
, 23:10
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#370
|
Yes - I'm actually still having the problem after trying everything also. I've even re-installed a couple of times to no avail. Hopefully, we can have a fix for this soon.
This may be useful for countries that google maps does not cover like Romania (mine).
So if anyone needs this kind of gpx data let me know. It's not public yet since the scripts run on my little nslu2 :|
@gnuite maybe you can use these scripts. They need a little maintenance work since the lovely MSN site keeps changing the damn polyline format.