public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Claudio Takahasi" <cktakahasi@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] help with Logitech Travel Mouse
Date: Tue, 25 Sep 2007 09:24:33 -0300	[thread overview]
Message-ID: <e1effdeb0709250524n16217623p194a891fa858810c@mail.gmail.com> (raw)
In-Reply-To: <2759cf860709250450yc36a945m846bd529d006b289@mail.gmail.com>

Hi,

Once the input device is created(using CreateDevice) the device will
reconnect automatically to the host when the user presses any key or
moves the mouse. Currently, there isn't a wizard applet to setup input
device, bluez-gnome and KDEBluetooth will support this functionality
soon. Bear in mind that an authorization agent(bluez-gnome implements
it) is required to authorize the incomming connection, alternatively
you can add this device in the trusted list to skip authorizations.

dbus-send examples are a workaround for testing purpose.

We have reconnect problems with some buggy keyboards, otherwise the
service is working fine.

BR,
Claudio.

On 9/25/07, Jared Greenwald <greenwaldjared@gmail.com> wrote:
> Someone else in #bluez-users pointed me to a page on this wiki with a
> bunch of little python scripts that would do the connection from
> bluetooth to device and vice-versa (HOWTO/InputDevices).
>
> I find it interesting that someone on this list would explicitly say
> to not use the hidd commands, but people readily offer these python
> scripts as fixes.  If these are so ubiquitous, why aren't they already
> part of the bluez-utils package?
>
> In any case, I tried running the dbus-send commands that are listed
> next to the python scripts and got nowhere.
>
> $dbus-send --system --type=method_call --print-reply --dest=org.bluez \
> /org/bluez org.bluez.Manager.ActivateService string:input
>    string ":1.8"
>
> $ dbus-send --system --type=method_call --print-reply --dest=":1.8"
> /org/bluez/input org.bluez.input.Manager.CreateDevice
> string:00:07:61:48:FC:DB
> Error org.bluez.input.Error.AlreadyExists: Input Already exists
>
> This can't be good.  Maybe this is around from me trying to run hidd --search?
>
> $ dbus-send --system --type=method_call --print-reply --dest=":1.8"
> /org/bluez/input/mouse0 org.bluez.input.Device.Connect
> Error org.freedesktop.DBus.Error.UnknownMethod: Method "Connect" with
> signature "" on interface "org.bluez.input.Device" doesn't exist
>
> I'm not sure I understand what this error is telling me, but I assume
> that it's not going to be good.
>
> Thoughts?
>
> -Jared
>
> On 9/24/07, Martin Stolle <mstoll@sus.mcgill.ca> wrote:
> > On Tue, Sep 25, 2007 at 01:12:34AM +0200, Marcel Holtmann wrote:
> > > Hi Martin,
> > >
> > > > > > Yea, I would think that would fix things, but I tried that (the hidd
> > > > > > --connect) and it doesn't seem to work to get connected...
> > > > >
> > > > > use the new input service and don't use hidd. The input service will
> > > > > convert your configured devices automatically. There is no need to use
> > > > > hidd --search or hidd --connect more than once. Whoever tells you
> > > > > differently is wrong. Period.
> > > >
> > > > Thanks, I didn't know that. how do you solve the problem at hand then?
> > > > What are the commands to use for the new input service?  Which man pages
> > > > should I look at?
> > >
> > > checkout wiki.bluez.org. It has all the examples.
> > >
> >
> > Sorry, but I can't find any end-user examples on the wiki.  They are all
> > programming examples in C and python.  Are you saying that the simple
> > "hidd --search" tool call has been replaced by having to write a whole
> > python program?  That's seems like quite a regression.  Or maybe I am
> > not able to find the appropriate page?
> >
> > Martin

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-09-25 12:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-24 19:13 [Bluez-users] help with Logitech Travel Mouse Jared Greenwald
2007-09-24 19:22 ` Martin Stolle
2007-09-24 19:33   ` Jared Greenwald
2007-09-24 22:14     ` Marcel Holtmann
2007-09-24 22:21       ` Martin Stolle
2007-09-24 23:12         ` Marcel Holtmann
2007-09-24 23:21           ` Martin Stolle
2007-09-25 11:50             ` Jared Greenwald
2007-09-25 12:24               ` Claudio Takahasi [this message]
2007-09-25 12:34                 ` Martin Stolle
2007-09-26 11:30                   ` Stefan Seyfried
2007-09-26 14:05                     ` Martin Stolle
2007-09-26 22:06                       ` Marcel Holtmann
2007-09-26 22:18                         ` Martin Stolle
2007-09-27  7:39                           ` Marcel Holtmann
2007-09-27 13:42                             ` Martin Stolle
2007-09-27 23:08                               ` Marcel Holtmann
2007-09-25 12:41                 ` Jared Greenwald

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=e1effdeb0709250524n16217623p194a891fa858810c@mail.gmail.com \
    --to=cktakahasi@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox