maemo.org - Talk - View Single Post - Maemo Mapper v1.0 for the 2006 OS

	gnuite	2006-08-08 , 02:38
	Posts: 1,245 \| Thanked: 421 times \| Joined on Dec 2005	#202

Originally Posted by avdigital

I had the same issue and also did the 'sudoers' trick but didn't work for me.

After my vacation with the Nokia MeamoMapper System I tried the '/dev/rfcomm' trick and this works perfectly; no loss of BlueTooth GPS connection at all.

I modified my Nokia so it will automaticly connect to the GPS unit when I startup Meamo-mapper. Modify the /etc/bluetooth/rfcomm.conf file. (first gain root access to do this)
Replace the sample values with your own values (MAC address) and set BIND to yes. Then the connection will be established at each reboot.

Now even when I switch off the GPS or get away from my Nokia with it it reconnects immediately when switched on or get nearby again.

Question: Is it so that the BlueTooth hardware is now always active (and searching) and is draining the battery more if I don't use Maemo-mapper?

By adding the device to BIND, it doesn't actually keep the connection open all the time (and it doesn't try looking for the device, either).

What really happens is that, whenever an application opens the /dev/rfcomm device for reading (or writing, I imagine), the bluetooth driver only then looks for and connect to the device. If the device is not present, I think it returns EOF or a failure condition or something. When the application closes the "file", the connection is dropped.

So, it won't drain your battery unless you leave Maemo Mapper on (without the cover on the display).

Using rfcomm this way may, in fact, be the (unfortunately) ideal solution to the dropout situation, until Nokia (or whoever) fixes the bug that causes the dropouts.

GPSD may also be a potential solution, since I think it uses rfcomm.

Quote & Reply |