Bluetooth connection with sx1

Forums › Legacy mobile platforms (Windows Mobile, Palm OS, Web OS, Symbian, Meego, Blackberry) › Bluetooth connection with sx1

Bull_uk

7 posts

Wannabe Geek
Inactive user

#1328 5-Apr-2004 08:25

I've been trying to get my SX1 working properly with bluetooth. The computer is able to communicate with the phone, I've been able to pair them and do an OBEX file push from the PC to the phone but thats my limit.
When I try to connect via the virtual serial port I always get the

[img]https://cdn.geekzone.co.nz/images/articles/3650/bt4.jpg[/img]

error, sometimes a few seconds later the [img]https://cdn.geekzone.co.nz/images/articles/3650/mroutericon1.jpg[/img] goes green somes times not. When I try to connect to the PC from the phone it always says "unable to create bluetooth connection".

I'm wondering if my network set up is the cause. I've read lost of points about firewalls so I'm starting to look at my router as the culprit. My set up is 1 pc that plugs into a router with a built in ADSL modem and into the phone line.

[img]http://www.bradfordmbrl.com/route.jpg[/img]

That doesn't look right to me but I don't know how it should look. My router sits on 10.0.0.2 and the bluetooth LAN sectiion has set up as 192.168.0.1 (for ICS.)

As you've probably guessed I'm starting to confiuse myself so can anyone help.

TIA

freitasm

BDFL - Memuneh
79253 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#4594 5-Apr-2004 08:29

First of all the error message and subsequently the phone trying to connect is normal. At this time the phone will try to initiate a connection to your computer, and the Bluetooth software will accept the connection on the Incoming COM port (that's why it goes green). If the router software is listening to this port then the phone will connect to your computer and you can then synchronise, explore, etc.

Sometimes the phone will not call back. It's normal and it's something on the Symbian software. It happens with Nokia 3650, Sony Ericsson P800 and P900.

Trying to connect from the phone will not work, as you found out.

The network configuration has no impact on this. But firewalls may cause problems.

Make sure you check the mRouter software to listen the correct COM port. Have a second read in the guides.

Bull_uk

7 posts

Wannabe Geek
Inactive user

#4595 5-Apr-2004 08:34

thanks for the VERY quick reply.

The bluetooth icon goes green briefly as if it connects but quickly drops it. mRouter never shows connected and Ive tried it with all com ports checked and just com 3 (the one listed in local client)

So you say I can basically ignore the router from the equation? I started looking there because of this guide
http://www.geekzone.co.nz/content.asp?contentid=1922

freitasm

BDFL - Memuneh
79253 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#4597 5-Apr-2004 09:38

(the one listed in local client): This should be the local service, not client.

Yep, don't worry about your router, it'll not impact on how the Nokia PC Suite connects to your phone. You do have to worry about Zone Alarm, NIS or other personal firewall software.

Bull_uk

7 posts

Wannabe Geek
Inactive user

#4613 6-Apr-2004 04:29

"This should be the local service, not client."

sorry that was a typo on my part. Under local service it is listed as com 3 and client apps as com 4. I think thats basically in and out so them not being the same is fine, am I right?

So in my current set up the bluetooth icon goes green for about 10 secs when I do quick connect---> serial but even while its green mRouter shows all com ports and "not connected" and in siemens data suite (which I'm guessing is basically the same as the Nokia equivalent) it shows as "no phone connected"

freitasm

BDFL - Memuneh
79253 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#4618 6-Apr-2004 07:35

Yep, the ports are supposed to be different. In your case the mRouter should be listening on COM3.

You should launch the Data Suite after establishing the connection. Again, mRouter using TCP/IP for communication with other programs, so any firewall will impact on this if not properly configured.

Also, have you installed the Data Suite after the Bluetooth software or before? To work properly and correctly identify all ports it should be installed after the Bluetooth. Perhaps you should remove it and install again?

Bull_uk

7 posts

Wannabe Geek
Inactive user

#4620 6-Apr-2004 10:08

I'm having a very similar conversation to this on club-siemens. I was pointed to this thread

http://www.club-siemens.net/forum/viewthread.php?tid=33063

Having gone through the ideas there and reinstalling Widcomm then mrouter and SDS I posted the following. Just wondering if you had any thoughts:

"anyway I'm still none the wiser. I've tried the things suggested in that thread. I don't have a dial up modem installed, I installed the dongle 1st then mrouter and SDS, I've tried it paired and unpaired (it just pairs then continues,) I have no firewall etc.

The only lead I got out of that thread was I have the serial connection on com 3 on local services and com 4 on client apps. In mrouter I can select and unselect com 3 regardless of anything else I'm doing but when I use quick connect to make a serial connection and the icon goes green it says another app is using com 4 and it cant access it. Am I right in thinking that means the PC is communicating with the phone but the phone isn't talking back? That would make sense as I'm able to send files to the phone but haven't been able to send them back"

freitasm

BDFL - Memuneh
79253 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#4621 6-Apr-2004 10:14

As I said, it happens on other Symbian phones. You connect the phone, it disconnects, but sometimes it fails to initiate the connection back. Really annoying...

Have you tried removing the battery and leave out for a couple of minutes before trying again? Weird, but sometimes work as a reset.

Equinox IT

Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.

Bull_uk

7 posts

Wannabe Geek
Inactive user

#4622 6-Apr-2004 10:27

I hadn't but have now.

I have come accross a strange thing though. I had the computer listed as a trusted device but hadn't got round to setting that up again after I'd unpaired and repaired it. In mrouter I was testing when I can and cant switch on monitoring of com 4 and I found that with no active connection via quick connect checking com 4 caused the phone to prompt me to authorise a connection from the computer. I authorised it but the status in mrouter and the bluetooth icon didnt change. I then tried unchecking and rechecking com 4 in mrouter and got the "another app is currently using this com" error. I tried turning BT off in the phone to disconnect it and it said that there was an active connection and then crashed.

Its almost as if the computer connected without the BT software knowing it

freitasm

BDFL - Memuneh
79253 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#4623 6-Apr-2004 10:40

You shouldn't need to check mRouter to look on COM4 at all. COM4 is an outgoing port, and connections from the phone will come on the incoming port, COM3.

Checking COM4 will confuse the phone.

Bull_uk

7 posts

Wannabe Geek
Inactive user

#4636 7-Apr-2004 05:51

I think Ive fallen over a solutiion without fully understanding the problem.

In mRouter I checked each com port from the highest (in my case com 6) down to the 2nd to lowest. I have local service in com 3 and client on com 4. After checking com4 a few seconds later I was prompted on the PC to authorise a connection from the phone. I did then checked com 3 and all of a sudden the phone is shown connected. I then loads data suite and theres the phone.

It looks like simply checking com 4 activate the connection to the phone which triggers the handshake sequence.. Ive not yet tested setting the phone to auto scann com 4 every few mins but I think that will probably seal the set up.

Thanks loads for the pointers freitasm. The last few days have been very frustrating

freitasm

BDFL - Memuneh
79253 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#4640 7-Apr-2004 07:55

checking com 4 activate the connection to the phone which triggers the handshake sequence

Yep, that's the idea of doing the manual connection. This or you'll have to check COM4 every time on mRouter.

Perhaps it was the lack of authorisation to allow the phone to connect back?

Bull_uk

7 posts

Wannabe Geek
Inactive user

#4641 7-Apr-2004 09:06

I dont think so as a pop up appeared saying the phone was trying to connect and did I want to allow iit. There was a check box saying "always authorise." I get the impression the phone had never got the initial connection from the PC before and so of course wasn't replying.

Anyway I'm up and running and I've been able to route my GPRS viia my DSL which was nice although Ive not got it working with Opera yet (I had to use something called Dorris.)

It's character building as my old man would say