I have a couple of questions.
I have this BT app in taskbar, when I can connect serial port, so that PC suite can find the phone (using mrouter).
When I turn on pc, I have no problem connecting at all. the problem arises, once I am connected and go away (past the 10 meter range) and the connection is dropped.
Once I return and try to reconnect, I can't 😞
The BTTray app seems like it is frozen. I can't get the "connect" menu from it again and when I try to connect using the "my bluetooth" app on desktop, it cannot connect.
The message I get is. "the (phonename) connection failed: The remote device closed the connection".
Anyone experienced this and is there any solution, apart from having to reboot my pc?
Looking forward to hear if anyone knows of this problem.
Another issue. I thought bluetooth was a "find and connect" technology.
Can it not autoconnect ? or is it a mrouter problem? or is it my BTTray.exe app, that causes the problem?
I have another problem
i have BT Conceptronic
when i start my windows XP and my BT is connected on the USB i can't make it work......
if I disconnect it and then connect it again, it works......
don't know why.....
but when it is working it is fantastic and very quick
Hmm.. Not quite the same problem i have, but I tried unplugging the BT adapter and putting it in again and that helped..
A flaw in the way Bluetooth is managed maybe?
I know I wrote this before, but as it seems noone really has an answer, there is one thing I would like to hear if others have the same problem I have..
The BBTray app I can use the first time to create a serial port connection.
After that, I cannot get in contact with it anymore. Not until I have done a reboot. That sucks :-?
Anyone have the same problem? (Using the sandberg BT (zeevo chip))
I've got a D-Link USB Bluetooth device, and have the same problem. I've gotten mRouter to connect only when I freshly set-up the connection.
Otherwise, clicking on the device through my Bluetooth places just gives me a message that says the remote device closed the connection. mRouter doesn't respond, and the bluetooth tray icon is unresponsive to right-clicking. Interestingly, the phone's little bluetooth icon thinks there's an active connection.
Anyone have a solution yet?
thanks,
-- Frank
Yes, I have the exact same problem, once I have connected to my phone, BTTray freezes. And it happens immediately after connecting, even though the connection was succesful. However, killing BTTray from Task Manager and restarting it does the trick for me, with this I can control the bluetooth again. However, mRouter seems not to support this kind of connect/reconnect behaviour, you have force it to lookup the connection again (by opening the mRouter connection properties where you have to uncheck and then check the COM port again).
After a bit of browsing on the problem, I downloaded the bluetooth software from MSI (google search). It's about 16M, but it seems to work with D-link. It still gives an error, but at least mRouter connects.
-- Frank
Go to "My Bluetooth Places", "Entire Bluetooth Neighboorhood", "nokia 3650", right-click, "discover available services", right-click "connect bluetooth serial port". That should do it.
or
Find which is your local services BT serial com port number (com 5 on mine), and your client applications serial com port number (com 4 on mine).
Open mRouter, disconnect all ports.
connect your client applications serial com port first
after about 3 seconds connect your local services serial com port.
you can find your BT settings by right-clicking your bt icon on the bottom right corner of your monitor, near the clock and going to "advanced configuration"
complicated, but it works for me (a lot of trial and error on this one...)
[quote="Tatuagem"]Go to "My Bluetooth Places", "Entire Bluetooth Neighboorhood", "nokia 3650", right-click, "discover available services", right-click "connect bluetooth serial port". That should do it.[/quote]
Yup. This is also the way I do it Tatuagem. I placed a shortcut of My Bluetooth Places in my task bar. I right click it and choose explore. When open I do as you stated and... It may not always connect the first time. And sometimes it says The Bluetooth Serial Port connection failed: The remote device closed the connection
But I just keep doing it and suddenly it connects even though it claims to have failed. Wierd. But I get the connection :-P
It may not always connect the first time. And sometimes it says The Bluetooth Serial Port connection failed: The remote device closed the connection
IT's always like this. It still connects though even if it says the connection failed. Just ignore the warning.
It seems that the BT software is the root of the problem here. Has anyone switched off the "Look for BT devices every..." thing? It should be the one that refreshes everything, even with the ports. Besides, when the port is still connecting, and the Software is checking the Thread of the checking, and it detects its not yet connected, it already says an error message. This means that it doesn't wait for the connection process to be finished before it says the message.