[Bluez-devel] Again: Problems with Dongle, Headset or btsco

[Bluez-devel] Again: Problems with Dongle, Headset or btsco

[Ben Pezzei]

Hi

I still try to use my Anycom 240 USB Dongle with the Plantronics 2500
Headset.  As Marcel stated in a previous Thread, this dongle looks
like to have an RSSI inquiry bug.

to make it short: shall I buy another dongle? And which one is known
to work without problems?

Here is the List what I did:

compile 2.6.10 Kernel (without patch-2.6.10-mh1.gz). In
previous trys I used the bluez libs and tools (compiled
them outside the kernel).

compile the latest btsco csv

btsco <addr> connects to the headset and i can change
the volume via the headset-button.

So i guess the rfcomm Communication is ok

But aplay -D plughw:Headset soundfile doesnt work.
either arecord ...
(btw: Should aplay ... be executed while btsco is connected
to the HS?)

weird thing: when using the hstest prog in bluez-utils i am
able to record _something_ but it's more or less static
(although the noises appear to be the spoken text - with
wrong frequency/speed).

Any Hints?

friendly regards
ben





-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Again: Problems with Dongle, Headset or btsco

[Lars Grunewaldt]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

maybe this is redundant information, but the correct use of btsco is this:

1. start btsco <addr>

when it is ready connection to the headset (no more output), press the
headset "connect" button - some output like "open hwdep, connected sco
channel" should show up

keep btsco running! do not quit it!

2. use any audio app including aplay to play/record audio while the
headset is connected

3. disconnect the headset by pressing the "connect" button of the
headset again. Audio stops working until you "connect" again with the
button.

******

If you did everything like this, it should work like described. If it
does not, you might need another dongle :)

I'm using a epox bt-dg03 and it works fine for me, that is, for my
logitech mx900 bt mouse and my sony ericsson hbh-35 headset. I don't
know if this is the "best" dongle.

I was also able to use the headset with the "dongle" that came with the
MX900, but I never made much tests there (the headset is only used with
the epox dongle because I keep my IM programs running on that PC)

best regards,
~  Lars


Ben Pezzei wrote:
| Hi
|
| I still try to use my Anycom 240 USB Dongle with the Plantronics 2500
| Headset.  As Marcel stated in a previous Thread, this dongle looks
| like to have an RSSI inquiry bug.
|
| to make it short: shall I buy another dongle? And which one is known
| to work without problems?
|
| Here is the List what I did:
|
| compile 2.6.10 Kernel (without patch-2.6.10-mh1.gz). In
| previous trys I used the bluez libs and tools (compiled
| them outside the kernel).
|
| compile the latest btsco csv
|
| btsco <addr> connects to the headset and i can change
| the volume via the headset-button.
|
| So i guess the rfcomm Communication is ok
|
| But aplay -D plughw:Headset soundfile doesnt work.
| either arecord ...
| (btw: Should aplay ... be executed while btsco is connected
| to the HS?)
|
| weird thing: when using the hstest prog in bluez-utils i am
| able to record _something_ but it's more or less static
| (although the noises appear to be the spoken text - with
| wrong frequency/speed).
|
| Any Hints?
|
| friendly regards
| ben
|
|
|
|
|
| -------------------------------------------------------
| This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
| Tool for open source databases. Create drag-&-drop reports. Save time
| by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
| Download a FREE copy at http://www.intelliview.com/go/osdn_nl
| _______________________________________________
| Bluez-devel mailing list
| Bluez-devel@lists.sourceforge.net
| https://lists.sourceforge.net/lists/listinfo/bluez-devel
|


- --
Lars Grunewaldt
* software development
* multimedia design
skills: C/C++/Java/PHP/(X)HTML/Flash/audio/video
web: http://www.dark-reality.de
mail: lgw@dark-reality.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB8P6DQWC6DTWkDAoRAgmVAJ958WwHgmm39/qLwikw/+fxjfcRfQCdFYxW
5cxxgzhyPe3uyV92DZ9nc8k=
=WGAL
-----END PGP SIGNATURE-----


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Again: Problems with Dongle, Headset or btsco

[Ben Pezzei]

Hi Lars,

Tnx for your reply

Lars Grunewaldt schrieb:

...

> 3. disconnect the headset by pressing the "connect" button of the
> headset again. Audio stops working until you "connect" again with the
> button.

like i said, the rfcomm connection is fine: (output from btsco <addr>):

   Device is 1:0
   Voice setting: 0x0060
   RFCOMM channel 1 connected
   recieved AT+CKPD=200
   opened hwdep
   connected SCO channel
   Setting sco fd
   Done setting sco fd
   recieved AT+VGS=04
...

after reconnecting via headset:
   disconnected SCO channel
   recieved AT+CKPD=200
   opened hwdep
   Can't connect SCO audio channel
   : Connection timed out

I always have to replug the dongle and restart btsco.

The question remains: Do I need the patch-2.6.10-mh1.gz patch?

I guess the Problem has to do with the SCO or ALSA Stuff

> If you did everything like this, it should work like described. If it
> does not, you might need another dongle :)

well, looks like the anycom 240 is fubar

greetings
ben



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Again: Problems with Dongle, Headset or btsco

[Lars Grunewaldt]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ben Pezzei wrote:
| Hi Lars,
|
| Tnx for your reply
|
| Lars Grunewaldt schrieb:
|
| ...
|
|> 3. disconnect the headset by pressing the "connect" button of the
|> headset again. Audio stops working until you "connect" again with the
|> button.
|
|
| like i said, the rfcomm connection is fine: (output from btsco <addr>):

btsco handles rfcomm and sco connections, so...

|   Device is 1:0
|   Voice setting: 0x0060
|   RFCOMM channel 1 connected
|   recieved AT+CKPD=200
|   opened hwdep
|   connected SCO channel
|   Setting sco fd
|   Done setting sco fd

this looks good.

| after reconnecting via headset:
|   disconnected SCO channel
|   recieved AT+CKPD=200
|   opened hwdep
|   Can't connect SCO audio channel
|   : Connection timed out

this does not. It should re-connect without problems, but I can't tell
whether this would be solved with mh1-patches or what might causing that
you can't reconnect to the headset.

You can try the patches out, I use them and it works well.

| I guess the Problem has to do with the SCO or ALSA Stuff

sco, not alsa I think. The alsa stuff is only needed to transmit the sco
data to the alsa functions and vice versa, so it's unlikly that the
impossibility of reconnecting on a new sco channel is the problem. More
likely the sco channel is not terminated correctly in the first place.

best regards,
~  Lars


- --
Lars Grunewaldt
* software development
* multimedia design
skills: C/C++/Java/PHP/(X)HTML/Flash/audio/video
web: http://www.dark-reality.de
mail: lgw@dark-reality.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB8TY3QWC6DTWkDAoRAlCCAJ9CyuecdSlBzOw+WP2AOqK5G0BOoACfWSNH
P0eRv2FWV2wQNyVtdZ3+m9I=
=NCy7
-----END PGP SIGNATURE-----


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Again: Problems with Dongle, Headset or btsco

[mirko_3]

> 
> You can try the patches out, I use them and it works well.
> 
Hi,
allow me to say: I have the exact same problem, can't get my dongle to work. Anyway, what I meant to say was that the patches change absolutely nothing: still have to replug the dongle to reconnect, and still get no audio (although volume buttons work).
If you need any information to cross-check and try to isolate the problem, just ask.

-mirko_3




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Again: Problems with Dongle, Headset or btsco

[Ben Pezzei]

Hi Lars,

Lars Grunewaldt schrieb:
> | I guess the Problem has to do with the SCO or ALSA Stuff
> 
> sco, not alsa I think. The alsa stuff is only needed to transmit the sco
> data to the alsa functions and vice versa, so it's unlikly that the
> impossibility of reconnecting on a new sco channel is the problem. More
> likely the sco channel is not terminated correctly in the first place.

ok. Is it possible that the SCO Part of this dongle is somehow broken?
Obviously the RFCOMM Part is working fine.

Since the hwdep module is part of the alsa-libs it looks like
the dongle can't be re-initialized (as a soundcard) after a
disconnect.

Question: when connected via btsco and trying to play
some sound with:
aplay -D plughw:Headset soundfile
Does soundfile need to have the correct samplerate,frequency,etc
as the Headset?
I am also able to set speaker and capture volume of the Headset
with alsamixer -c 1

unfortunately
arecord -D plughw:Headset z1.out
Recording WAVE 'z1.out' : Unsigned 8 bit, Rate 8000 Hz, Mono

only creates a 44 Byte big file z1.out with the header but
no content

Last Question: Which are other methods to send/receive
data from/to the headset beside aplay / arecord?

eg cat /dev/snd/pcmC1D0c > z1.out ? :)

greetings
b





-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Again: Problems with Dongle, Headset or btsco

[mirko_3]

On Sat, 22 Jan 2005 14:59:39 +0100
Ben Pezzei <ben@webstuhl.net> wrote:

> ok. Is it possible that the SCO Part of this dongle is somehow broken?
> Obviously the RFCOMM Part is working fine.
> 
> Since the hwdep module is part of the alsa-libs it looks like
> the dongle can't be re-initialized (as a soundcard) after a
> disconnect.
> 
> Question: when connected via btsco and trying to play
> some sound with:
> aplay -D plughw:Headset soundfile
> Does soundfile need to have the correct samplerate,frequency,etc
> as the Headset?
> I am also able to set speaker and capture volume of the Headset
> with alsamixer -c 1
> 
> unfortunately
> arecord -D plughw:Headset z1.out
> Recording WAVE 'z1.out' : Unsigned 8 bit, Rate 8000 Hz, Mono
> 
> only creates a 44 Byte big file z1.out with the header but
> no content
> 
> Last Question: Which are other methods to send/receive
> data from/to the headset beside aplay / arecord?
> 
> eg cat /dev/snd/pcmC1D0c > z1.out ? :)


Can't help you with the rest, but in xmms you can select the headset...


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Again: Problems with Dongle, Headset or btsco

[ligi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


|>
|>
|> Last Question: Which are other methods to send/receive data
|> from/to the headset beside aplay / arecord?
|>
|> eg cat /dev/snd/pcmC1D0c > z1.out ? :)
|
you have to use snd_pcm_oss  for that.
from kernel doc:
To enable OSS digital audio (PCM) emulation (/dev/dsp*), say Y    
here and read <file:Documentation/sound/alsa/OSS-Emulation.txt>.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB8mXj3NorRo/jFWIRAnJ0AJ4w5XM6K4gIDpV6I97uAJXIy9J9UACfREgR
tNjcjdUFWajYEr/e4NJh758=
=TER7
-----END PGP SIGNATURE-----



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

[Bluez-devel] Re: Again: Problems with Dongle, Headset or btsco

[Paul Ionescu]

Hi,

On Sat, 22 Jan 2005 14:59:39 +0100, Ben Pezzei wrote:

> Since the hwdep module is part of the alsa-libs it looks like the dongle
> can't be re-initialized (as a soundcard) after a disconnect.

How do you know the dongle can't be re-initialized ?
What does it say when you launch again btsco ?

> Last Question: Which are other methods to send/receive data from/to the
> headset beside aplay / arecord?
> 
> eg cat /dev/snd/pcmC1D0c > z1.out ? :)

I was able to use gnomemeeting, mplayer and other programs that use alsa
or oss.
For mplayer I used -ao alsa:device=hw=Headset -srate 8000 -channels 1





-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Re: Again: Problems with Dongle, Headset or btsco

[Ben Pezzei]

Hi ,

Paul Ionescu schrieb:

> How do you know the dongle can't be re-initialized ?
> What does it say when you launch again btsco ?

After disconnecting via Headset (press Button) and connecting again
the btsco looks like:
   disconnected SCO channel
   recieved AT+CKPD=200
   opened hwdep
   Can't connect SCO audio channel
   : Connection timed out

Same when exiting ctrl+c btsco and start it again

> I was able to use gnomemeeting, mplayer and other programs that use alsa
> or oss.
> For mplayer I used -ao alsa:device=hw=Headset -srate 8000 -channels 1

no X installed ;(

greetings
ben



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

[Bluez-devel] Re: Re: Again: Problems with Dongle, Headset or btsco

[Paul Ionescu]

On Sat, 22 Jan 2005 18:43:39 +0100, Ben Pezzei wrote:

> Hi ,
> 
> Paul Ionescu schrieb:
> 
>> How do you know the dongle can't be re-initialized ? What does it say
>> when you launch again btsco ?
> 
> After disconnecting via Headset (press Button) and connecting again the
> btsco looks like:
>    disconnected SCO channel
>    recieved AT+CKPD=200
>    opened hwdep
>    Can't connect SCO audio channel
>    : Connection timed out

you can try to disconnect btsco (with ^C)
verify with
hcitool con
that you don't have any connections still active after you disconnect
btsco, (if they are, delete them with hictool dc MAC_OF_HEADSET)
and then try again to connect with btsco.

I had this problem and I solved this way.

> Same when exiting ctrl+c btsco and start it again
> 
>> I was able to use gnomemeeting, mplayer and other programs that use alsa
>> or oss.
>> For mplayer I used -ao alsa:device=hw=Headset -srate 8000 -channels 1
> 
> no X installed ;(

You don't need X for mplayer




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

[Bluez-devel] Re: Again: Problems with Dongle, Headset or btsco

[Sebastian Roth]

Hi Ben,

> ok. Is it possible that the SCO Part of this dongle is somehow broken?
> Obviously the RFCOMM Part is working fine.
I've had problems with a Anycom 220 dongle (also Silicon Wave chip) too. 
RFCOMM seemed to work but no sound. hcidump showed a flow of sco packets 
with handle 0. Can't get it working till now so I decided to use another 
one.

> Question: when connected via btsco and trying to play
> some sound with:
> aplay -D plughw:Headset soundfile
> Does soundfile need to have the correct samplerate,frequency,etc
> as the Headset?
IMHO, no.

> unfortunately
> arecord -D plughw:Headset z1.out
> Recording WAVE 'z1.out' : Unsigned 8 bit, Rate 8000 Hz, Mono
> 
> only creates a 44 Byte big file z1.out with the header but
> no content
For older versions of arecord this is the usual behaviour. Update 
alsa-tools or try the commandline switch '-d' (man arecord).

Best regards,

Sebastian



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Re: Again: Problems with Dongle, Headset or btsco

[Ben Pezzei]

Hi Sebastian,

Sebastian Roth schrieb:

>> unfortunately
>> arecord -D plughw:Headset z1.out
>> Recording WAVE 'z1.out' : Unsigned 8 bit, Rate 8000 Hz, Mono
>>
>> only creates a 44 Byte big file z1.out with the header but
>> no content
> 
> For older versions of arecord this is the usual behaviour. Update 
> alsa-tools or try the commandline switch '-d' (man arecord).

Well, I'll give it a last try: I'll patch the kernel
with the mh1 patch from bluez and the latest alsa libs.
(currently installed arecord version is 1.0.7 - latest is 1.0.8),
although i doubt this will finally work :)

One very last Question (BT specific):

I upgraded the Dongle on a win xp box to BT 1.2. After reading
the docs, 1.2 has some changes in it regarding Audio which imho
affects the SCO part, right? Does it make sense to downgrade the
dongle to 1.1 (if possible)?

finally, tnx all for your replies & tips

greetings
ben



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Re: Again: Problems with Dongle, Headset or btsco

[Lars Grunewaldt]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ben Pezzei wrote:
| Hi Sebastian,
|
| Sebastian Roth schrieb:
|
|>> unfortunately
|>> arecord -D plughw:Headset z1.out
|>> Recording WAVE 'z1.out' : Unsigned 8 bit, Rate 8000 Hz, Mono

uhm, this is wrong. If you are using the "actual" btsco package from CVS
- - and you should be - it must record as signed 16 bit if I'm not
mistaken (possibly unsigned 16B, but in no case 8 bit)

best regards,
~  Lars

- --
Lars Grunewaldt
* software development
* multimedia design
skills: C/C++/Java/PHP/(X)HTML/Flash/audio/video
web: http://www.dark-reality.de
mail: lgw@dark-reality.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB8+RoQWC6DTWkDAoRAo4rAJ4r9GbBnH1eUtDQ08ngF6UyXeX0lgCgpdlx
Hn7p+uz6pWQTIRA3jPF0e28=
=Wgk/
-----END PGP SIGNATURE-----


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Re: Again: Problems with Dongle, Headset or btsco

[Ben Pezzei]

Hi

Lars Grunewaldt schrieb:

> 
> uhm, this is wrong. If you are using the "actual" btsco package from CVS
> - - and you should be - it must record as signed 16 bit if I'm not
> mistaken (possibly unsigned 16B, but in no case 8 bit)

This worked neither

Anyways, I just want to let you know that I kicked the Anycom
Dongle and bought an D-Link DBT 120 Rev 4, et voila: Everything
is working fine.

Headset: Plantronics 2500

tnx again for your help and congrats @ Developers

greetings
ben




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Re: Again: Problems with Dongle, Headset or btsco

[Lars Grunewaldt]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marcel,

as it seems that those dongles seem not to work with the currect sco
implementation, what would you propose to debug this misfunction?

Maybe the hci_usb driver can be fixed or a workaround added for this
chipsets (I think they are buggy, not our implementation, but if there's
a simple workaround...)

best regards,
~  Lars

Ben Pezzei wrote:
| Hi
|
| Lars Grunewaldt schrieb:
|
|>
|> uhm, this is wrong. If you are using the "actual" btsco package from CVS
|> - - and you should be - it must record as signed 16 bit if I'm not
|> mistaken (possibly unsigned 16B, but in no case 8 bit)
|
|
| This worked neither
|
| Anyways, I just want to let you know that I kicked the Anycom
| Dongle and bought an D-Link DBT 120 Rev 4, et voila: Everything
| is working fine.
|
| Headset: Plantronics 2500
|
| tnx again for your help and congrats @ Developers
|
| greetings
| ben
|
|
|
|
| -------------------------------------------------------
| This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
| Tool for open source databases. Create drag-&-drop reports. Save time
| by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
| Download a FREE copy at http://www.intelliview.com/go/osdn_nl
| _______________________________________________
| Bluez-devel mailing list
| Bluez-devel@lists.sourceforge.net
| https://lists.sourceforge.net/lists/listinfo/bluez-devel
|


- --
Lars Grunewaldt
* software development
* multimedia design
skills: C/C++/Java/PHP/(X)HTML/Flash/audio/video
web: http://www.dark-reality.de
mail: lgw@dark-reality.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB9NpEQWC6DTWkDAoRApYwAJ0V/f3tlellTspUzas4S250FqlRJgCfZuRy
IuFYlvDUJWm5dCvrf8qLrjk=
=F9NV
-----END PGP SIGNATURE-----


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] Re: Again: Problems with Dongle, Headset or btsco

[Marcel Holtmann]

Hi Lars,

> as it seems that those dongles seem not to work with the currect sco
> implementation, what would you propose to debug this misfunction?
> 
> Maybe the hci_usb driver can be fixed or a workaround added for this
> chipsets (I think they are buggy, not our implementation, but if there's
> a simple workaround...)

the Silicon Wave chips are not the best ones. They have problems and it
seems that they are not going to fix them. Mostly because they sell ROM
chips are these ones can't be updated by a newer firmware. However if
this is the problem with SCO packets and handle 0 then the hci_usb
driver should simply drop these frames, because they are not valid SCO
payload.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

[Bluez-devel] Re: Re: Again: Problems with Dongle, Headset or btsco

[Jesse Guardiani]

Marcel Holtmann wrote:

> Hi Lars,
> 
>> as it seems that those dongles seem not to work with the currect sco
>> implementation, what would you propose to debug this misfunction?
>> 
>> Maybe the hci_usb driver can be fixed or a workaround added for this
>> chipsets (I think they are buggy, not our implementation, but if there's
>> a simple workaround...)
> 
> the Silicon Wave chips are not the best ones. They have problems and it
> seems that they are not going to fix them. Mostly because they sell ROM
> chips are these ones can't be updated by a newer firmware. However if
> this is the problem with SCO packets and handle 0 then the hci_usb
> driver should simply drop these frames, because they are not valid SCO
> payload.

I'm confused by this response. I have a USB-240 dongle too. Does this mean
that a simple workaround is possible, or no?

-- 
Jesse Guardiani, Systems Administrator
WingNET Internet Services,
P.O. Box 2605 // Cleveland, TN 37320-2605
423-559-LINK (v)  423-559-5145 (f)
http://www.wingnet.net




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel