Notices

I'm not sure, but may be there is still some gconf daemon running - with cached data. Try to find out and kill it, or simply reboot.

I don't have internet access from my cell phone, so I wish I had this:
an option where you send the coordinates of two points from the map using sms (gnokii lib) and receive the route (driving directions) in a sms.

my prepaid t-mobile phone can send a sms to an email address. a small application will sit on the home desktop reading the emails (sms), then will query gnuite's gpx cgi and then send back the xml file as an attachment to a sms.

I will build the "server" which will sit on the home computer if somebody makes the modifications for the maemo-mapper.
-ioan

Except that SMS text only has a limit of 140 bytes which I think will get used up rather quickly in even the smallest route directions.

I just received my Holux GPSlim236 bt gps receiver.

Meamo Mapper detects it fine, but when I opt 'Enable GPS' it doesn't work, it pops up the message "Searching for GPS receiver" and stays there.

Note: the MAC address is correct, I checked with hcitool scan and tried to pair with btpair; no popup for any key though, should be 0000 ....
I don't see the device in /var/lib/bluetooth/[MAC]/linkkeys, it does show up in /var/lib/bluetooth/[MAC]/names and I have no clue whether that's ok or not....


Any hints?

try this:
http://www.internettablettalk.com/fo...2895#post22895

-i

Same result: popup saying: Searching for GPS receiver



any other hints?


[edit]
tried also to do
rfcomm connect /dev/ttyS3 [BT-MAC] 1
as I read here:
http://www.internettablettalk.com/fo...0&page=4&pp=10
but I get:
Can't connect RFCOMM socket: Host is down

and upon trying again:
Can't connect RFCOMM socket: Resource temporarily unavailable

Oh yeah, I tried to cat /dev/rfcomm0 but that too told me 'Host is down'...

try this, see if you can connect to the gps receiver:

http://maemo.org/maemowiki/Bluetooth...ight=%28gps%29

Thanks again, ioan!

Couldn't bind to rfcomm0 - address already in use; binding to rfcomm1 works ok.
Then,
cat /dev/rfcomm1
results in the 'host is down' reply.

hcitool scan
shows the device fine, including name....!



Took out the /etc/bluetooth/rfcomm.conf bind yes instruction, rebooted, tried with rfcomm0 - same result: host is down.

BTW somewhere along the line I also changed the /etc/bluetooth/pin to have 0000 as default pin - which is what the Holux GPSlim 236 should have as well...

I have the same receiver and it works perfectly. The only problems I ever had were related to it losing connection occasionally. That, and goofing with the SIRF utility completely hosed it, requiring the internal backup battery to be shorted out to reset it to factory defaults. I would suggest trying it with a PC to make sure it works.

Larry

lbattraw, thanks for your response. I knew from another topic here that people used the Holux 236 with the 770, which is why I got that one. Well, that and the strong recommendation that it's a fine product.

I was thinking it could be set to sirf protocol (as I read on the net that some people had trouble getting it going), but then it should at least have given some response to the cat /dev/rfcomm0 command, or shouldn't it have?
And I was thinking it might be using a different channel...

In any case, I needed to check that Sirf vs NMEA setting, so I tried with a windows machine at work today - for lack of one at home, I have only Linux machines, including the N770 - and both with gpstool (I think that's the name) and sirfdemo from holux uk website, no data ever came out. I couldn't even connect to it, it seems.

That was whilst connected via usb.

Is it easy/straightforward to open it to short the internal battery, and would that void the warranty?

I passed the holux 236 to a colleague who has a bluetooth numerix device, and asked him if he could have a look if it would work for him; he might not be in tomorrow, so maybe I only get it back after the weekend, not sure.
In any case, I'm strongly thinking of sending it back.....