All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Pieczynski <pieczy@web.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Protocol error in btsco
Date: Sat, 4 Jun 2005 15:49:11 +0200	[thread overview]
Message-ID: <200506041549.11210.pieczy@web.de> (raw)
In-Reply-To: <200506041519.15949.pieczy@web.de>

On Saturday 04 June 2005 15:19, Frank Pieczynski wrote:
> I try to play a short wav file, it works. But after on of the next tries
> the connection dies somehow with "Protocol error"
some addtitional info (I discovered the -V of hcidump):

< HCI Command: Add SCO Connection (0x01|0x0007) plen 4
    handle 47 ptype 0x00e0
    Packet type: HV1 HV2 HV3
> HCI Event: Command Status (0x0f) plen 4
    Add SCO Connection (0x01|0x0007) status 0x00 ncmd 1
> HCI Event: Max Slots Change (0x1b) plen 3
    handle 47 slots 1
> HCI Event: Connect Complete (0x03) plen 11
    status 0x24 handle 47 bdaddr 00:0E:DA:XX:XX:XX type SCO encrypt 0x00
    Error: LMP PDU Not Allowed
> HCI Event: Max Slots Change (0x1b) plen 3
    handle 47 slots 5

What is wrong here?
Frank


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2005-06-04 13:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-04 13:19 [Bluez-users] Protocol error in btsco Frank Pieczynski
2005-06-04 13:49 ` Frank Pieczynski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200506041549.11210.pieczy@web.de \
    --to=pieczy@web.de \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.