Bluetooth HID Profile

[tazzix]

Can the e680i connect to Bluetooth HID devices?

Anyone having more knowledge with BT can tell if a modified kernel should solve this issue or the hardware needs to have some thing special?

I am selling out a PalmWireless IR keyboard to replace it with a BT keyboard but there would be no driver with any brand so HID could work if it is supported Thoughts?

[maxx_730]

afaik no, but i'm pretty sure this is software. Its not like ist limited by the bandwidth of the bluetooth chip or something like a2dp, since hid doesnt use that much bandwidth.

[tazzix]

There are some BT keyboards operating on the serial profiles, but in my opinion, they'll be much harder to get to work.

[bluenectar]

is there any difference between bluetooth inside E680i and other phones, i mean like SE phones ? since SE was the first who developed bluetooth i thought the technology will not be the same.
hope there's no difference cause when me and my two friends bonded to each other, my friend using SE phone and the other one using O2 XDA2, the SE phone always get faster than mine

[al750n]

Intel Xscale Bulverde (PXA 270) 312MHz CPU OMA DRM Phase 1 (Forward Lock. Combined Delivery. Separate Delivery ... May be DRM make bluetooth speed little bit slower .. how abt ur diskspace ? try to remove some files and then compary again the sending speed ..

[bluenectar]

my diskspace is enough i guess since i haven't installed anything but linloader and qonsole, it's weird when you know that E680i' bluetooth can't be comparable with other brands such as SE

[tallemd]

how to get a frogpad to work with e680i
this type of method should be fairly standard
be warned that mouse kb combo's look to have
wiggy configs that are hard to get right
here are my links
http://frogpad.zeroforum.com/zerothread?id=245 for basic info
http://www.gentoo.org/doc/en/bluetooth-guide.xml for host config
http://www.bluez.org/hardware.html take a look at the holtmann pages
umm and a lot of other pages that basically say use
hidd --search method and fail to give the method

bluez # ./btstop.sh
./ezx-hciattach: no process killed
rm: cannot remove `/tmp/bd_addr': No such file or directory
rmmod: module hci_uart is not loaded
rmmod: module hidp is not loaded
rmmod: module bnep is not loaded
rmmod: module rfcomm is not loaded
rmmod: module l2cap is not loaded
rmmod: module sco is not loaded
rmmod: module bluez is not loaded

bluez # ./btinit.sh
Connected. Starting read/write
Writing 08 bytes: 02 81 0c 00 00 00 00 00
Writing 12 bytes: 38 01 00 00 00 00 ff ff 00 00 00 00
Reading 08 bytes:
Read : 02 81 04 00 00 00 00 00
Expecting : 02 81 04 00 00 00 00 00
(correct)
Reading 04 bytes:
Read : 00 00 00 00
Expecting : 00 00 00 00
(correct)
Writing 08 bytes: 0c 86 00 00 00 00 00 00
Reading 08 bytes:
Read : 0c 86 04 00 00 00 00 00
Expecting : 0c 86 04 00 00 00 00 00
(correct)
Reading 04 bytes:
Read : 00 00 00 00
Expecting : 00 00 00 00
(correct)
Writing 08 bytes: 0b 86 00 00 00 00 00 00
Reading 08 bytes:
Read : 0b 86 04 00 00 00 00 00
Expecting : 0b 86 04 00 00 00 00 00
(correct)
Reading 04 bytes:
Read : 00 00 00 00
Expecting : 00 00 00 00
(correct)
Writing 08 bytes: 0d 86 00 00 00 00 00 00
Reading 08 bytes:
Read : 0d 86 0a 00 00 00 00 00
Expecting : 0d 86 0a 00 00 00 00 00
(correct)
Read BDADDR : 00 00 00 00 00 14 9a 45 db 7e

bluez # cd etc/init.d/
init.d # ./bluetooth
Usage: /etc/init.d/bluetooth {start|stop}
init.d # ./bluetooth start
Starting Bluetooth subsystem: hcid sdpd rfcomm pand.

init.d # hciconfig -a
hci0: Type: UART
BD Address: 00:14:9A:45B:7E ACL MTU: 377:10 SCO MTU: 64:0
UP RUNNING PSCAN ISCAN
RX bytes:116 acl:0 sco:0 events:13 errors:0
TX bytes:319 acl:0 sco:0 commands:13 errors:0
Features: 0xff 0xff 0x0d 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: '((none))'
Class: 0x100100
Service Classes:
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x3 LMP Ver: 1.1 (0x1) LMP Subver: 0x700
Manufacturer: Broadcom Corporation (15)

init.d # hcitool inq
Inquiring ...
00:0AF:00:04:2B clock offset: 0x247d class: 0x002540

init.d # rfcomm connect 0 00:0AF:00:04:2B 1
Can't connect RFCOMM socket: Connection refused

bluez # hcitool info 00:0AF:00:04:2B
Requesting information ...
BD Address: 00:0AF:00:04:2B
Device Name: FrogPad
LMP Version: 1.1 (0x1) LMP Subversion: 0x300
Manufacturer: Cambridge Silicon Radio (10)
Features: 0xfc 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
<encryption> <slot offset> <timing accuracy> <role switch>
<hold mode> <sniff mode> <park state> <RSSI> <channel quality>
<SCO link> <HV2 packets> <HV3 packets> <u-law log> <A-law log>
<CVSD> <paging scheme> <power control> <transparent SCO>

bluez # hidd --search
Searching ...
Connecting to device 00:0AF:00:04:2B

then i flip back to good ole opie bt manager
and sure enough i have a good connection
2 problems 1 pin seems to be flubbing things up
i need to enter it in the keyboard and the phone
both at about the same time i assume

also no text at all in any of the programs
may be due to the pin being wrong
but may also have to due with
there only being half of a dev dir

odds on bet its the pin though because
the kb lights acts like that's what's happening
the descriptions don't tell how to enter the pin

kbing is possible. i know cause the sites say
thou must have at least kernel version 2.6.8
and we do on at least my phone
and also the frogpad has been tested as working on desktops

looks like this guide is incomplete at least so far
my phone decided to lock up
then stop responding to telnet and samba
prolly nonstd ip ... its 3ap here ... sweet dreams ...

[tallemd]

my usb card flaked and started giving bad power
thereby causeing half of anything connected to not work
well the ph still works i guess
so i have to go buy a usb card in the next town over or something
before i can continue work

although i did find a nice tidbit on the /dev/ filesystem here
http://ubuntuforums.org/archive/index.php/t-7432.html
looks like we need to have a /input/ dir with stuff in it i guess
at least in order to have keyboards and mice that is

also this link has some hints on auth and encryption
http://forums.gentoo.org/viewtopic-p-2006436.html

well toodles i'm going to arrange for transportation

export PATH=$PATH:/diska/bluez/bin:/diska/bluez/sbin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/diska/bluez/lib
if ! test -e /dev/rfcomm0;then cp -a /dev /tmp/dev ; mount --bind /tmp/dev /dev; for i in 0 1 2 3 4 5 6 7; do mknod /dev/rfcomm$i c 216 $i; done;fi
cd /diska/bluez
./btinit.sh
cd etc/init.d/
./bluetooth start
hidd --search

that's the script i use ...
you can try pasteing it into the command window
the last command is hidd
it might not work the first time because
you have to hit return at the right time
still no output in the phones notepad
another fun command is hidd --show

hidd --show
00:0AF:00:04:2B HID Boot Device [0000:0000] connected [boot-protocol]

Here's the trick with my keyboard
i toggle number shift until it toggles the toggle led
this shows that its ready for a pin
then don't enter pin just press enter
on other keypads you might try numlock

when i'm bound properly with the null pin entered
i get the right leds turning on and off
which means from the keyboard side its ok


here's the syslog paraphrased
<4>get_halted_bit: UHCBHED is NULL!!,return!
<4>nonzero read bulk status recieved: -104
<4>get_halted_bit: UHCBHED is NULL!!,return!
<4>nonzero read bulk status recieved: -104

[tallemd]

that was me hehe
note to self must be logged in to post as self

export PATH=$PATH:/diska/bluez/bin:/diska/bluez/sbin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/diska/bluez/lib
if ! test -e /dev/rfcomm0;then cp -a /dev /tmp/dev ; mount --bind /tmp/dev /dev; for i in 0 1 2 3 4 5 6 7; do mknod /dev/rfcomm$i c 216 $i; done;fi
cd /diska/bluez
./btinit.sh
cd etc/init.d/
./bluetooth start
hidd --search

that's the script i use ...
you can try pasteing it into the command window
the last command is hidd
it might not work the first time because
you have to hit return at the right time
still no output in the phones notepad
another fun command is hidd --show

hidd --show
00:0AF:00:04:2B HID Boot Device [0000:0000] connected [boot-protocol]

Here's the trick with my keyboard
i toggle number shift until it toggles the toggle led
this shows that its ready for a pin
then don't enter pin just press enter
on other keypads you might try numlock

when i'm bound properly with the null pin entered
i get the right leds turning on and off
which means from the keyboard side its ok

here's the syslog paraphrased
<4>get_halted_bit: UHCBHED is NULL!!,return!
<4>nonzero read bulk status recieved: -104
<4>get_halted_bit: UHCBHED is NULL!!,return!
<4>nonzero read bulk status recieved: -104