mmalmeida / bdremote-ng Goto Github PK

[ 46%] Building C object
CMakeFiles/bdremoteng_generic.dir/root/bdremote/src/lirc_thr.c.o
/usr/bin/gcc  -DENABLE_REPEAT=1 -g -Wall -Wextra -pedantic 
-I/root/bdremote/build/../src   -o
CMakeFiles/bdremoteng_generic.dir/root/bdremote/src/lirc_thr.c.o   -c
/root/bdremote/src/lirc_thr.c
/root/bdremote/src/lirc_thr.c: In function 'lircThread':
/root/bdremote/src/lirc_thr.c:188:23: error: 'name' undeclared (first use
in this function)
/root/bdremote/src/lirc_thr.c:188:23: error: (Each undeclared identifier is
reported only once
/root/bdremote/src/lirc_thr.c:188:23: error: for each function it appears in.)
make[2]: ***
[CMakeFiles/bdremoteng_generic.dir/root/bdremote/src/lirc_thr.c.o] Error 1
make[2]: Leaving directory `/root/bdremote/build/linux'
make[1]: *** [CMakeFiles/bdremoteng_generic.dir/all] Error 2
make[1]: Leaving directory `/root/bdremote/build/linux'
make: *** [all] Error 2

i downloaded svn today (12th october 2009) and the file src/lirc_thr.c
which is referenced in the build is not there

What steps will reproduce the problem?
0. A Logitech diNovo MX5000 keyboard/mouse securely (with authentication
and encryption) connected to a computer is required, though other
models/keyboards may be affected as well.

hci0 my default BT interface

1. Connect your keyboard/mouse to PC (usually, by typing/moving mouse)
2. Start bdremote-ng daemon
3. Disable security (i.e., with 'sudo hciconfig hci0 noauth noencrypt')
4. Connect Sony BD Remote by pressing 'PS' button
5. Enable encryption back ('sudo hciconfig hci0 auth encrypt')
5. Ensure remote is connected (e.g., with LIRC utilities)
6. Wait for mouse/keyboard timeout. Alternatively, kill connection with
'sudo hcitool dc 00:07:XX:XX:XX:XX', where the argument is your
keyboard/mouse BT address.

What is the expected output? What do you see instead?
Expected: after moving mouse/typing a mouse/keyboard should reconnect
automatically, and begin typing/mousing.
Actual: it doesn't happen, there's no cursor movement or characters
appearing on screen.

What version of the product are you using? On what operating system?
bdremote-ng-0.5, Debian 5 Lenny on amd64. Other systems may be affected as
well.

Please provide any additional information below.
1. Mouse/keyboard in scenario above gets connected (I can see their packets
in 'hcidump'), but it looks like they don't reach X server. So maybe the
problem is in 'hidd' daemon or with accessing BT socket.
2. Everything starts working after I kill off bdremote-ng daemon (which can
be done with a usb / ps/2 keyboard).

P.S. Can bdremote-ng functionality be integrated into hidd?

remove text

"second, where key is pressed."

from the README. you already did it in the code.

Atso Peter mentioned this issue:

> Thanks for the correction about the unpairing thing you are right it
> will remain "paired" until I pair the device with something else. I
> agree that the device needs to switch off to save batteries. I'm still
> curious how long does it take on your setup to go from "sleep" to
> action if you press something when the device is not connected ? On my
> setup it sometimes takes really long like 10-15s so I think maybe
> there is something wrong with my settings or maybe it wakes up only
> from some buttons but not all.

I think this should be looked at.
I am using 60 sec timeout, where this seem to happen often.

Reading from the remote should timeout after say 60 seconds, if no new key
presses are received. I don't think that this works any more after all the
changes I made to the source.

I have two devices I need to connect via Bluetooth: A Logitech diNovo Edge 
keyboard and the PS3 remote -- it currently appears impossible with 
bdremoteng, it seems.

I'm on a Mythbuntu 9.04 install (AMD64) on an Asrock ION 330 box.

If I stop bluetooth (sudo /etc/init.d/bluetooth stop) and run bdremoteng, I 
can get it to attach to my remote (sudo ./bdremoteng -a 00:23:06:E6:B9:54 -
n -d  0) and send the keys correctly to lirc on port 8888.

But when I start bluetooth again, it fails to connect to the HID control 
channel or some such, and consequently cannot connect to my keyboard...

In the logfile (daemon.log) it says this:

Oct 17 19:37:22 asrock bluetoothd[11981]: Failed to listen on control 
channel
Oct 17 19:37:22 asrock bluetoothd[11981]: input-server: Operation not 
permitted (1)

If I start bdremoteng while bluetooth is already running (I know, not 
supposed to...) it says this:

Using BT address: 00:0A:3A:7B:B5:AE.
bind: Address already in use
Can't listen on HID control channel: Address already in use
bdremoteng.c:166 -> 19:51:46:
InitcaptureLoop failed.

So apparently bdremoteng monopolize the HID "control channel" somehow and 
cannot coexist with other HID devices?

I'm using the latest 0.4 RC.

Pls advice -- appears like a nasty bug to me?


-- Per ([email protected])

What steps will reproduce the problem?

bdremoteng -a 00:19:C1:52:EF:F6 -n -d 1

What is the expected output? What do you see instead?

Configuration:
 - listen port: 8888.
 - timeout    : 60.
 - repeat rate: 10 per secound.
 - debug      : 1.
 - remote addr: 00:19:C1:52:EF:F6.
 - detach     : 0.
 - user       : not set.
 - group      : not set.
bdremoteng: /usr/src/bdremote-ng-read-only/src/captureif.c:46:
InitCaptureData: Assertion `_cd->config == ((void *)0)' failed.
Aborted

What version of the product are you using? On what operating system?

path: .
URL: http://bdremote-ng.googlecode.com/svn/trunk
Repository Root: http://bdremote-ng.googlecode.com/svn
Repository UUID: 1989ecb2-9d63-11de-b975-97273e741547
Revision: 29
Node Kind: directory
Schedule: normal
Last Changed Author: [email protected]
Last Changed Rev: 27
Last Changed Date: 2009-09-14 08:55:23 +0100 (Mon, 14 Sep 2009)


Please provide any additional information below.

just followed the instructions in the readme and this is what happens

See the mailing list for patch and discussion.

http://sourceforge.net/mailarchive/forum.php?thread_name=4B05D595.5080301%40san.
rr.com&forum_name=bdremote-ng-devel

A release should be created after the basic bugs are fixed.

The current Makefile is poorly written and does not take all deps into account.

As agreed, I am trying to test this on Ubuntu Karmic Beta

What steps will reproduce the problem?
1. Cmake in Karmic Koala beta (10-10-2009)
2. Compile in a jaunty machine and copy the file to Karmic
3. Run hcitool scan
4. run bdremoteng -a 00:21:4F:A5:51:15 -n -d 1


On step 1, I get:

CMake Error at CMakeLists.txt:22 (message):
  Required bluetooth headers not found.

Note that the bluez-utils package has (disregarding the docs):
/usr
/usr/share
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/bluez-utils

And there isn't a bluez-libs package in Karmic.

I compiled the program in Jaunty and proceeded.

3- I got: hcitool scan
Scanning ...
    00:21:4F:A5:51:15   n/a
4- I got: dremoteng -a 00:21:4F:A5:51:15 -n -d 1
/home/miguel/Desktop/bdremoteng: error while loading shared libraries:
libbluetooth.so.2: cannot open shared object file: No such file or directory

So, I'd appreciate some help trying to make this script work on Karmic. Has
any of you tested it on this distro or are able to help me test it?

What steps will reproduce the problem?
1.Install on Ubuntu 10.04
2.Create the boot script as per wiki
3. Reboot

What is the expected output? What do you see instead?
We expect the remote to work.
If we run irxevent we expect irw to display the buttons pressed in the remote.
In the general wiki, the comments from "Comment by beejay41,  May 21, 2010"
onwards refer to this issue.
Something has changed in the boot sequence that has made these scripts stop
working. I have tried some different boot priorities, but none worked.

I would like to help fix this issue and update the corresponding wiki page,
but I am failing to diagnose the problem correctly...

Hi,

I am using Debian Squeeze and trying to get to run bdremoteng. I have used the 
scripts as provided under section ubuntu 10.04. When starting script 
bdremote.sh my messages log has the following:

Jan 23 14:32:26 ogmedia logger: Checking if BT device is ready (0).
Jan 23 14:32:26 ogmedia logger: Found device hci0.
Jan 23 14:32:26 ogmedia oliver: stopping bluetooth
Jan 23 14:32:26 ogmedia oliver: starting bdremote
Jan 23 14:32:27 ogmedia oliver: Attempting to start bdremoteng .. start
Jan 23 14:32:27 ogmedia oliver: Attempting to start bdremoteng .. end
Jan 23 14:32:27 ogmedia oliver: started bdremote ..
Jan 23 14:32:27 ogmedia logger: /usr/local/bin/bdremoteng: error while loading 
shared libraries: libbluetooth.so.3: cannot open shared object file: No such 
file or directory
Jan 23 14:32:28 ogmedia oliver: started bluetooth again .. 

Any idea how I can get this to run properly?

Kind regards
Oliver

do i need to do something special in my /etc/lircrc to get repeating keys
to work?

root@MyXBMC:/home/xbmc/Bureau/XBMC_PS3Remote# bdremoteng -a
00:1E:3D:0D:47:50 -n -d 1
Configuration:
- listen port: 8888.
- timeout : 60.
- repeat rate: 10 per secound.
- debug : 1.
- remote addr: 00:1E:3D:0D:47:50.
- detach : 0.
- user : not set.
- group : not set.
bind: Address already in use
Can't listen on HID control channel: Address already in use
InitcaptureLoop failed.

Any idea ? Thanks

What steps will reproduce the problem?
n/a
What is the expected output? What do you see instead?

battery charge status need to documented in Wiki.(I see it is pooped into
the log is that only when it changes?)
this thing sucks batteries so if I knew it was low I could have a script
pop up and tell me to swap the batteries.  What might be neat is if you
made 6 new buttons on the remote named something like Battery100,Battery80,
etc.. instead of just pooping it in to the log.

What version of the product are you using? On what operating system?
bdremote-ng 0.5RC2 Ubuntu 9.04 64-bit(up to date)

Please provide any additional information below.
I like pie.

Use valgrind.

Patch sent to mailing list.

This daemon does not need higher privileges (AFAIK), as soon as it opens
the BT device. LIRC uses a port > 1024 too.

i switched from bdremoted 0.2 to bdremote-ng svn rev 58 and the cpu usage
is near 10% ( atom 330 gentoo linux x64 )

It is possible to get battery information from the remote. Someone wrote a
post on the mailing list about it with a LIRC patch from which this
information could be extracted.

All interfaces must be documented. Lets use Doxygen comments - unless
something better comes along.

I don't think that this ever worked. 

The thread used to send events to lirc was converted into a simple
function, so this definitely will not work any more.

when using -d 9 it says that the delay is in ms and the repeat rate is
repeats per second

there does not seem to me to be any change no matter what values i use
and the repeat is not consistent (and sometimes none at all)

What steps will reproduce the problem?
Using bdremote-ng with lirc. 

What is the expected output? What do you see instead?
Keys should have been repeated according repat setting, but only 1 keypress
per second was received

What version of the product are you using? On what operating system?
0.5, ubuntu 9.10

Please provide any additional information below.
Fixed the issue by modifying lirc_thr.c line 197 as follows:
-broadcastToLirc(ld, name, 0 /*ks.repeat_sent*/,
ps3remote_keys[ks.lastKey].code);
+broadcastToLirc(ld, name, ks.repeat_count, ps3remote_keys[ks.lastKey].code);

This has been done in SVN, the bug is just a reminder.

Some files still lack doxygen comments.

hello
i've upgraded the kernel from 2.6.36 to 2.6.39 and bdremoteng does not work any 
more
the bluez version is still the same (4.82)

the bluetooth subsystem seems to work properly, here the output from hcidump

enter
> ACL data: handle 42 flags 0x02 dlen 17
    L2CAP(d): cid 0x0041 len 13 [psm 0]
      0000: a1 01 00 00 08 0b ff ff  ff ff ff 01 05           .............
> ACL data: handle 42 flags 0x02 dlen 17
    L2CAP(d): cid 0x0041 len 13 [psm 0]
      0000: a1 01 00 00 00 ff ff ff  ff ff ff 00 05           .............

pause 
> ACL data: handle 42 flags 0x02 dlen 17
    L2CAP(d): cid 0x0041 len 13 [psm 0]
      0000: a1 01 00 00 00 39 ff ff  ff ff ff 01 05           .....9.......
> ACL data: handle 42 flags 0x02 dlen 17
    L2CAP(d): cid 0x0041 len 13 [psm 0]
      0000: a1 01 00 00 00 ff ff ff  ff ff ff 00 05           .............


bdremote-ng just does not capture anything, i've tried recompiling

/usr/local/src/bdremote-ng-read-only/build/linux/bdremoteng -t 900 -n -d -p 
8888 -a 00:21:4F:B0:32:76


capture_bluez.c:503 -> 22:35:48:
Using BT address: 00:10:DC:EA:39:B8.
lirc_thr.c:129 -> 22:35:48:
Started LIRC thread:
 - using repeat rate : 10.
 - waiting ms between repeated keys: 100.
 - using repeat delay: 200.
bdremoteng.c:286 -> 22:35:48:
Started listener thread.
capture_bluez.c:374 -> 22:35:48:
Using destination address: 00:21:4F:B0:32:76.
.
.
capture_bluez.c:399 -> 22:34:31:
No data captured ..
capture_bluez.c:399 -> 22:34:32:
No data captured ..



i'd really appreciate a fix, i hate to use the vdr-remote app on the android  ;)
let me know if you need any more information
thanks :)

I tried running btremoteng on arch linux i686. It compiles cleanly, however
when run as 
./bdremoteng -a .....
it dies as follows:
*** glibc detected *** /tmp/bdremote-ng-0.2/build/linux/bdremoteng: free():
invalid pointer: 0xb8072890 ***
======= Backtrace: =========
/lib/libc.so.6[0xb7f6a9b1]
/lib/libc.so.6[0xb7f6c0b2]
/lib/libc.so.6(cfree+0x6d)[0xb7f6f17d]
/tmp/bdremote-ng-0.2/build/linux/bdremoteng(InitCaptureData+0x15a)[0x804af4a]
/tmp/bdremote-ng-0.2/build/linux/bdremoteng(main+0x1fd)[0x8049951]
/lib/libc.so.6(__libc_start_main+0xe6)[0xb7f15a36]
/tmp/bdremote-ng-0.2/build/linux/bdremoteng[0x80496c1]
======= Memory map: ========
08048000-0804d000 r-xp 00000000 08:01 1128541   
/tmp/bdremote-ng-0.2/build/linux/bdremoteng
0804d000-0804e000 rw-p 00005000 08:01 1128541   
/tmp/bdremote-ng-0.2/build/linux/bdremoteng
09eef000-09f10000 rw-p 00000000 00:00 0          [heap]

debugging with gdb shows:
(gdb) bt
#0  0xb8091424 in __kernel_vsyscall ()
#1  0xb7f29461 in raise () from /lib/libc.so.6
#2  0xb7f2ac62 in abort () from /lib/libc.so.6
#3  0xb7f64add in __libc_message () from /lib/libc.so.6
#4  0xb7f6a9b1 in malloc_printerr () from /lib/libc.so.6
#5  0xb7f6c0b2 in _int_free () from /lib/libc.so.6
#6  0xb7f6f17d in free () from /lib/libc.so.6
#7  0x0804af4a in InitCaptureData (_cd=0xbfb19438, _config=0xbfb194b8,
_p=0xbfb19458, 
    _dest_address=0x9eef008 "00:1e:3d:11:eb:51", _timeout=60) at
/tmp/bdremote-ng-0.2/src/captureif.c:54
#8  0x08049951 in main (argc=3, argv=0xbfb19624) at
/tmp/bdremote-ng-0.2/src/bdremoteng.c:121

(gdb) frame 7
#7  0x0804af4a in InitCaptureData (_cd=0xbfb19438, _config=0xbfb194b8,
_p=0xbfb19458, 
    _dest_address=0x9eef008 "00:1e:3d:11:eb:51", _timeout=60) at
/tmp/bdremote-ng-0.2/src/captureif.c:54
54    FREEVAL(_cd->dest_address);
(gdb) p _cd
$1 = (captureData *) 0xbfb19438
(gdb) p *_cd
$2 = {config = 0xbfb194b8, p = 0xbfb19458, bt_dev_address = 0x0,
dest_address = 0xb8072890 "b\220\004\b\020ii\r", 
  timeout = -1207369726, sockets = {-1207301616, 134516010, -1207491276}}

if i run the latest source in the foreground (-n), it does send data to lirc
if i run it in the background then there is no output.

release 0.3 works fine on the machine - so i know that the remote/receiver
and bluetooth software is working correctly

See the mailing list for patch and discussion.

http://sourceforge.net/mailarchive/forum.php?thread_name=4B05D604.9040207%40san.
rr.com&forum_name=bdremote-ng-devel