I have a problem with the maemo mapper and the bluetooth gps.
the problem i encounter are after say 30 sec. is that it looks like the connection is stil running but it is not. the strange thing is when i close the cover and op it agian then the bt reconnects again for about a min or 2 and then agian it freezes.
I installed the latest versions of:
Maemo Mapper v1.1
Maemo Bluetooth Plugin version 0.5.0,
and use a Oasis Media Bluetooth GPS Receiver its the same as the ADAPT AD-300 Bluetooth GPS.
any one got an idea ? how to solve this problem...
Try using rfcomm. It seems to be a suitable workaround for GPS receivers with this problem. Search the forums for how.
I did notice that in the bluetooth settings and set it to /dev/rfcomm0 with no change in behavior. Sorry I forgot to mention it.
I just took my laptop for a spin using gpsdrive and it held the connection for the entire time, so it appears the gps unit itself is fine.
While on vacation and once today, I was unable to re-establish my bluetooth connection. The 1st time it happened, I deleted the pairing and recreated it and then was able to use it again via MM. Today, I tried this again while the bluetooth MAC setting was set to /dev/rfcomm0 and I couldn't reconnect even after deleting the pairing. Once I scanned from MM and selected the detected MAC, I was able to reconnect.
It just died again. When it dies, the GPS receiver still shows an active bluetooth connection. At first glance, all seems well in MM as well; the GPS Info window is populated with lat and long, speed, altitude. It also claims to be using 7 of 10 satellites and have a 3D fix. However, this data is all frozen in time. When I reset it jumps back to life, with continual minute adjustments to all until it dies again.
I did notice that in the bluetooth settings and set it to /dev/rfcomm0 with no change in behavior. Sorry I forgot to mention it.
Am I only supposed to have /dev/rfcomm0 while MM is running? If I use rfcomm0 instead of scanning for bluetooth devices, will MM create the device node itself?
I've just run 'cat /dev/rfcomm0'. I could see output scrolling for a bit then it simply freezes. It looks like MM believes the bluetooth connection is still there, but it simply isn't receiving output from /dev/rfcomm0.
BTW, I googled 'maemo mapper rfcomm0' when I noticed /dev/rfcomm0 didn't exist. The 3rd result was a post to maemo-users titled "GPS receiver problem after N800 flash". The OP solved his issue by adding swap, but I'd already done that long ago. They went on to discuss a media crawler, metalayer-crawl, which was consuming far too much memory and theorized that since his memory cards had many, many files, this crawler was impacting MM.
Anyway, I've removed my memory cards (although I don't have anywhere near the number of files he did) and will try again during lunch. Grasping at straws, I know.
If anyone has any suggestions, I'd love to hear them.
EDIT: arrrgh! scratch that, it took only 3 secs or so for it to freeze again. This is incredibly frustrating. I bought that GPS specifically for use with MM and it's the only thing I can't use the GPS with. crap.
In a move of pure desperation, I flashed the n800 today and did not restore my backup this time. No change.
When my wife and I were in PR recently, she commented that the freeze-ups seemed to coincide with our stops. I though she was nuts. But, today, on the way home, my car came to a complete stop 3 times. MM froze up at two of the three. Am I just going nuts? Coincidence?
I'm getting awfully close to chucking this thing in the junk drawer for good.
