From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Output power
Date: Fri, 27 May 2005 20:44:12 +0200 [thread overview]
Message-ID: <1117219452.12036.130.camel@pegasus> (raw)
In-Reply-To: <000501c562ea$b4c89240$8200a8c0@priveiqvfluhp9>
Hi Pieter,
> I measured the transmit power level of a Bluetooth-dongle, but it stays 0 in
> a range of 10m.
> I'm sure that the link quality raises (from 212 tot 255 on a distance of
> 2m), so I thought it was because the transmit power level is stronger.
>
> Do you have experience with the transmit power level indication?
send in "hciconfig -a", because some dongles don't really support the
transmit power level. They always return 0.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-05-27 18:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 14:41 Small fix for L2CAP MTU Stephen Crane
2005-05-25 14:46 ` [Bluez-devel] " Marcel Holtmann
2005-05-25 15:02 ` Stephen Crane
2005-05-25 15:59 ` Marcel Holtmann
2005-05-26 10:13 ` Stephen Crane
2005-05-26 10:31 ` Marcel Holtmann
2005-05-26 10:45 ` [Bluez-devel] Output power Pieter De Mil
2005-05-26 10:48 ` Marcel Holtmann
2005-05-27 18:34 ` Pieter De Mil
2005-05-27 18:44 ` Marcel Holtmann [this message]
2005-05-26 13:55 ` [Bluez-devel] Re: Small fix for L2CAP MTU Stephen Crane
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=1117219452.12036.130.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox