Sixthhokage2 / remuco

Automatically exported from code.google.com/p/remuco
1 stars 1 forks source link

Connecting fails on Siemens SP65 #72

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What is your environment?
* OS: openSUSE 11.2
* Remuco version: 0.9.2
* Client device: Siemens SP65, bluetooth connection
* Player: songbird

What steps will reproduce the problem?
1. $ remuco-songbird
2. start songbird
3. start remuco on client
4. Connection: channel set manual (channel 1), authenticate off, encrypt
off (also tried authenticate on and auth on+encrypt on)
5. already ensured hciconfig ok (pscan, iscan) and songbird appears in
sdptool message (channel 1), modified dbus-config-file as described in #5

What is the expected behavior? What happens instead?
expected behavior: songbird-player is found and connection established;
instead: while searching for player, error msg on client: "There was an IO
error while setting up the connection (BT Error Code 4)."

I just don't know what else I could try.  

Additional information:
File bt-transfer ok; i cannot change the devices to be trusted on either
side (pc, mobile phone)
extract of log on client: starts with main loop alive (60)
[CN] open url failed (BT Error Code 4)
[CN] url: btspp://001060B38610:1;master=false;encrypt=false;authenticate=true;
[EN] started
[BF] bluetooth: yes
[TH] loaded theme Vico
[CF] load: success
[CF] close: ok
[CF] load: __devs__='001060B38610|2|1|false|false|Linux'
[CF] oopen: ok, using 1/6190KB
[CF] UTF-8: yes

With WinXP, an application called Bluetooth RC worked.

Original issue reported on code.google.com by va.kl...@gmail.com on 6 Dec 2009 at 1:48

GoogleCodeExporter commented 9 years ago
sorry, I think this should be a support request :)

Original comment by va.kl...@gmail.com on 6 Dec 2009 at 2:41

GoogleCodeExporter commented 9 years ago
I've searched for "BT error code 4" and this seems to be a known problem for 
some
Siemens devices using Bluetooth. Nevertheless I've not found any useful answers 
to
solve this problem.

The only idea I have is to randomly try other channels (in the range 1-30) - 
maybe on
Siemens devices some channel numbers are reserved for specific services (as 
seen on
some BlackBerry devices where a channel > 6 hast to be used).

On the server side the channel can be set in a player adapter's configuration 
file
(see page PlayerAdapterConfiguration in the wiki). On the client you already 
managed
it set it manually.

Original comment by obensonne@googlemail.com on 6 Dec 2009 at 4:01

GoogleCodeExporter commented 9 years ago
Thanks, I will try it and report

Original comment by va.kl...@gmail.com on 8 Dec 2009 at 10:54

GoogleCodeExporter commented 9 years ago
Any news here?

Original comment by obensonne@googlemail.com on 11 Feb 2010 at 10:08

GoogleCodeExporter commented 9 years ago
Closing due to missing feedback.

Original comment by obensonne@googlemail.com on 14 Mar 2010 at 2:06