linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Steffen Becker <steffen.becker@tu-ilmenau.de>
Cc: Kal Torak <chronognosis@aim.com>,
	linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: main.conf issues
Date: Sun, 29 Apr 2012 14:44:50 +0300	[thread overview]
Message-ID: <CABBYNZJ2ygZ42r==cDbBFmtzmOFTA-HnDCWk_XM669pHYtfs5Q@mail.gmail.com> (raw)
In-Reply-To: <4F9B0108.2000007@tu-ilmenau.de>

Hi,

On Fri, Apr 27, 2012 at 11:26 PM, Steffen Becker
<steffen.becker@tu-ilmenau.de> wrote:
> Hello Torak,
>
> I'm not very familiar with BlueZ (also just asking questions on this mailing
> list), but what I can tell is that:
> You have to setup this file:
> /var/lib/bluetooth/<local-bdaddr>/config
> At the moment I can't look up the right syntax for all the configuration,
> but if i remember right, for enabling discoverable mode you have to enter
> something like this in the config-file:
>
> onmode discoverable
> mode discoverable
>
> For changing the name of your device, you have to edit this line in the
> config-file:
>
> name <your-name>

Please no top-posting here, those files are not supposed to be
manually edited, use D-Bus API otherwise you may cause
inconsistencies.

>> Hello, When I setup the main.conf with the values for Name, Class,
>> PairableTimeout and DiscoverableTimeout, and restart the bluetoothd,
>> hciconfig shows that nothing change name still the same, I cant "see"
>> the device from the outside(iscan is disabled), and the class still
>> 0x000100, and I must re-do hciconfig hci name #### class #### and
>> hciconfig hci0 piscan by hand to make the device visible and try
>> streaming support, OTOH I just can't see and/or connect to the device.
>> a ConWise 6622 Bluetooth dongle.
>> I'm using bluez-4.99 and linux 3.2.15.Any information will be usefull...

You don't have to do that in main.conf, except for class, those values
are only used when there is nothing already configured, so to change
this you really should be using D-Bus. You can find under
tests/test-adapter how to set this permanently in the configuration of
the adapter.

Btw, for the class it actually gets updated automatically when you
register the services.

-- 
Luiz Augusto von Dentz

  reply	other threads:[~2012-04-29 11:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 15:40 main.conf issues Kal Torak
2012-04-27 20:26 ` Steffen Becker
2012-04-29 11:44   ` Luiz Augusto von Dentz [this message]
2012-05-01 18:20     ` Kal Torak
2012-05-02  8:08       ` Luiz Augusto von Dentz
2012-05-04 17:32         ` Kal Torak

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='CABBYNZJ2ygZ42r==cDbBFmtzmOFTA-HnDCWk_XM669pHYtfs5Q@mail.gmail.com' \
    --to=luiz.dentz@gmail.com \
    --cc=chronognosis@aim.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=steffen.becker@tu-ilmenau.de \
    /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;
as well as URLs for NNTP newsgroup(s).