Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 1 day, 23 hrs ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 2 days ago -
Maemo repository (3)
to Community by torsen - 2 days, 16 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 3 days, 14 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 4 days, 20 hrs ago - more...
 |
|
2007-11-27
, 15:01
|
|
Posts: 531 |
Thanked: 79 times |
Joined on Oct 2006
@ This side of insane, that side of genius
|
#352
|
i have noticed that my POI's have been affected by one of the recent updates. i have the newest (2.1) version and the POI's are placed correctly on the map, but when i view/edit the POI, the longitude and latitude are all 0's.
to the command prompt, boy wonder...
a select * from poi; shows all of the POIs and their relevant data and attributes. i do notice that the long and lat fields are very long numbers.
example: a hostel that i stayed at a few years back
lat - 48.1609191894531
long - 11.5581817626953
might there be too many significant figures? just a thought...
now i thought that since i had the display in Heading-Deg-Mins-Secs format, there was a conversion issue and by default it zeroed the entry. that doesnt seem to be the case as i switched to dd.ddddd format and the POI's still have all zeros in the long/lat fields.
is there any way to clear this up?
to the command prompt, boy wonder...
a select * from poi; shows all of the POIs and their relevant data and attributes. i do notice that the long and lat fields are very long numbers.
example: a hostel that i stayed at a few years back
lat - 48.1609191894531
long - 11.5581817626953
might there be too many significant figures? just a thought...
now i thought that since i had the display in Heading-Deg-Mins-Secs format, there was a conversion issue and by default it zeroed the entry. that doesnt seem to be the case as i switched to dd.ddddd format and the POI's still have all zeros in the long/lat fields.
is there any way to clear this up?
__________________
Nokia n800
OS 2008
Pharos iGPS 360-BT
ElmScan 5 BlueTooth
BlackBerry Bold (9000)
AT&T Wireless
Nokia n800
OS 2008
Pharos iGPS 360-BT
ElmScan 5 BlueTooth
BlackBerry Bold (9000)
AT&T Wireless
|
|
2007-11-27
, 16:37
|
|
Posts: 98 |
Thanked: 3 times |
Joined on Nov 2007
@ Knightdale, NC
|
#353
|
I upgraded to 2.1 and I cant seem to get mapper to connect to the gps now. I use a BT?? gps receiver with N700 os2007he. Yes it has been working. I usually shut it off and turn it back on, but this time not matter what I tried I cannot get the two to talk. The bluetooth receiver is visible on the device so that's not the problem. Any suggestions?
BTW - this is a great software and I'm really devistated right now not be able to use it.
BTW - this is a great software and I'm really devistated right now not be able to use it.
 |
|
2007-11-27
, 21:52
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#354
|
Originally Posted by brendan
This bug should have been fixed in 2.1.1. Please upgrade to 2.1.1 and confirm that you still experience the bug.
i have noticed that my POI's have been affected by one of the recent updates. i have the newest (2.1) version and the POI's are placed correctly on the map, but when i view/edit the POI, the longitude and latitude are all 0's.
to the command prompt, boy wonder...
a select * from poi; shows all of the POIs and their relevant data and attributes. i do notice that the long and lat fields are very long numbers.
example: a hostel that i stayed at a few years back
lat - 48.1609191894531
long - 11.5581817626953
might there be too many significant figures? just a thought...
now i thought that since i had the display in Heading-Deg-Mins-Secs format, there was a conversion issue and by default it zeroed the entry. that doesnt seem to be the case as i switched to dd.ddddd format and the POI's still have all zeros in the long/lat fields.
is there any way to clear this up?
|
|
2007-11-27
, 22:03
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#355
|
Originally Posted by dburr10085
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....
I upgraded to 2.1 and I cant seem to get mapper to connect to the gps now. I use a BT?? gps receiver with N700 os2007he. Yes it has been working. I usually shut it off and turn it back on, but this time not matter what I tried I cannot get the two to talk. The bluetooth receiver is visible on the device so that's not the problem. Any 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:
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-27
, 23:22
|
|
Posts: 85 |
Thanked: 79 times |
Joined on Nov 2007
@ Erfurt, Germany
|
#356
|
I found some time to update the preliminary OS2008 port to version 2.1.1 today, the package and the patches are available under http://people.debian.org/~tschmidt/m.../maemo-mapper/ as usual.
My suggestion to OS2008-users is to stick with version 2.0.5chinook5 from my page, because of the GPS-related problems described in the last posts.
(The only way i can use GPS with maemo-mapper 2.1.1 on my N800 in an easy way is to activate gpsd with the wayfinder app or with the gps control panel applet and setting up maemo-mapper to use the gpsd on localhost, port 2947.
@Gnuite: Regarding the patches: I had to revert the check for libgdbm to the way it was done in mm 2.0.5 because otherwise libgdbm was not found.
Another other issue was that MSGFMT and GMSGFMT variables were empty, so it was not possible to build the locales (i did specify them with AC_PATH_PROG as a workaround).
The most noticable difference to the previous port is that i disabled displaying of the stopwatch because i was not able to fix the problem with it not being showed correctly.
My suggestion to OS2008-users is to stick with version 2.0.5chinook5 from my page, because of the GPS-related problems described in the last posts.
(The only way i can use GPS with maemo-mapper 2.1.1 on my N800 in an easy way is to activate gpsd with the wayfinder app or with the gps control panel applet and setting up maemo-mapper to use the gpsd on localhost, port 2947.
@Gnuite: Regarding the patches: I had to revert the check for libgdbm to the way it was done in mm 2.0.5 because otherwise libgdbm was not found.
Another other issue was that MSGFMT and GMSGFMT variables were empty, so it was not possible to build the locales (i did specify them with AC_PATH_PROG as a workaround).
The most noticable difference to the previous port is that i disabled displaying of the stopwatch because i was not able to fix the problem with it not being showed correctly.
|
|
2007-11-27
, 23:33
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#357
|
Originally Posted by Chelli
I have a version running on OS2008 now, and I noticed that problem, too. But I figured out the cause: Nokia changed the icon itself from the hourglass to the diagonal lines. So, it's actually working as expected, although I don't agree with their change.
The most noticable difference to the previous port is that i disabled displaying of the stopwatch because i was not able to fix the problem with it not being showed correctly.
I've solved the problem by distributing the hourglass directly with Maemo Mapper, so Nokia can't just change it beneath me without notice.
|
|
2007-11-27
, 23:35
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#358
|
Originally Posted by Chelli
I've fixed these problems in my own OS2008-compatible build, by the way. It will probably be released today or tomorrow.
My suggestion to OS2008-users is to stick with version 2.0.5chinook5 from my page, because of the GPS-related problems described in the last posts.
(The only way i can use GPS with maemo-mapper 2.1.1 on my N800 in an easy way is to activate gpsd with the wayfinder app or with the gps control panel applet and setting up maemo-mapper to use the gpsd on localhost, port 2947.
|
|
2007-11-28
, 00:21
|
|
Posts: 531 |
Thanked: 79 times |
Joined on Oct 2006
@ This side of insane, that side of genius
|
#359
|
Originally Posted by brendan
forgot to mention... with the above issue, i cannot click and hold on a POI, select POI and then Download Route to...
i have noticed that my POI's have been affected by one of the recent updates. i have the newest (2.1) version and the POI's are placed correctly on the map, but when i view/edit the POI, the longitude and latitude are all 0's.
to the command prompt, boy wonder...
a select * from poi; shows all of the POIs and their relevant data and attributes. i do notice that the long and lat fields are very long numbers.
example: a hostel that i stayed at a few years back
lat - 48.1609191894531
long - 11.5581817626953
might there be too many significant figures? just a thought...
now i thought that since i had the display in Heading-Deg-Mins-Secs format, there was a conversion issue and by default it zeroed the entry. that doesnt seem to be the case as i switched to dd.ddddd format and the POI's still have all zeros in the long/lat fields.
is there any way to clear this up?
each time i try this, i get destination that is clearly not the right one. the longitude is always -0.000008.
__________________
Nokia n800
OS 2008
Pharos iGPS 360-BT
ElmScan 5 BlueTooth
BlackBerry Bold (9000)
AT&T Wireless
Nokia n800
OS 2008
Pharos iGPS 360-BT
ElmScan 5 BlueTooth
BlackBerry Bold (9000)
AT&T Wireless
|
|
2007-11-28
, 11:35
|
|
Posts: 85 |
Thanked: 79 times |
Joined on Nov 2007
@ Erfurt, Germany
|
#360
|
Originally Posted by gnuite
Ok, stupid me, just checked that the file still exists, did not check the actual content of the file.
I have a version running on OS2008 now, and I noticed that problem, too. But I figured out the cause: Nokia changed the icon itself from the hourglass to the diagonal lines. So, it's actually working as expected, although I don't agree with their change.
-Rip