From: Stefan Jonasson <sjond00@student.vxu.se>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] SonyEricsson K700i and HID
Date: Fri, 15 Apr 2005 14:07:34 +0200 [thread overview]
Message-ID: <4ca6094ca1c0.4ca1c04ca609@vxu.se> (raw)
How exactly did you get it to work .. just by starting hidd with --nosdp, and then it worked out if the box?
How did you connect the mouse decive to X? I don't think that there are any appropriate mouse protocols / keyboard layouts for the k700 phone !?
----- Original Message -----
From: Marcel Holtmann <marcel@holtmann.org>
Date: Friday, April 15, 2005 1:41 pm
Subject: Re: [Bluez-devel] SonyEricsson K700i and HID
> Hi Stefan,
>
> > I just bought an SonyEricsson K700i and it have support for
> bluetooth HID.
> > After researching a bit I realized that there probably isent any
> way to make it work in linux atm..
> >
> > I tyred to use it as a keyboard/ mouse with hidd. The phone and
> computer can connect to each other the phone shows the input map (
> just as it does in windows when you use this function). And hidd
> dosent report any failures...
> >
> > Now I want hidd to do something useful like creating a mouse
> device and a keyboard!
> >
> > A list of questions:
> >
> > Which implementations do I need to chage?
> > How to I make hidd k700i aware?
> > Shoud I create an new application that uses the hidp module
> directly?> How do I inspect the traffic?
> > It there anyway to make hidd print debug info?
> > Is this possible to do?
> > Wich specifications do I need, where can I get them?
> > I found a nice document on ericssons dev site
> http://developer.sonyericsson.com/getDocument.do?docId=66147 will
> it help?
>
> the problem with the K700i is that it only supports two L2CAP
> connections at the same, but for our implementation we will need
> actually three of them. Otherwise we can't get the HID descriptor and
> thus we can only do boot. However I successfully used a K700i with the
> --nosdp option.
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real
> users.Discover which products truly live up to the hype. Start
> reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-04-15 12:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 12:07 Stefan Jonasson [this message]
2005-04-15 12:21 ` [Bluez-devel] SonyEricsson K700i and HID Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2005-04-15 11:26 Stefan Jonasson
2005-04-15 11:41 ` Marcel Holtmann
2005-04-18 9:12 ` Marcel Hilzinger
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=4ca6094ca1c0.4ca1c04ca609@vxu.se \
--to=sjond00@student.vxu.se \
--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