Linux Bluetooth Remote Control 0.6.4 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Linux Bluetooth Remote Control 0.6.4 (Default branch)
# 1  
Old 12-28-2008
Linux Bluetooth Remote Control 0.6.4 (Default branch)

ImageLinux Bluetooth Remote Control (LBRC) is a remotecontrol program that allows a Linux computer to becontrolled by a J2ME device via Bluetooth. It isdivided into a server part that runs on thecomputer and reacts to input events and a clientpart that runs on the J2ME device. The J2ME clientsends the device's keycodes, which are translatedto keystrokes, mouse movements, mouse clicks, orother input events on the controlled computer.License: GNU General Public License (GPL)Changes:
LBRC now works with the new bluez DBUS API.Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. Solaris

T3-2 Remote control Problem

Hi Peeps, Wondering if anyone can help me, trying to launch the remote console on a T3-2. When I select use serial redirection it comes up with a dialogue box that says. "The remote console application requires java 5.0. Please Download java from http://www.java.com" "Do you wish to... (1 Reply)
Discussion started by: callmebob
1 Replies

2. Hardware

Bluetooth Dongle Pairing but Not Connecting (Linux)

I have been trying to get bluetooth working correctly on Linux for a while now. I am using two systems that are having identical issues: Linux Mint 15 64-bit & Ubuntu 13.04 32-bit. Both are using the Cinnamon desktop. I have the following bluetooth dongle: ... (6 Replies)
Discussion started by: Deluge
6 Replies

3. Linux

SSH remote control question

I am pretty new to linux so forgive me for asking a basic question :P I am using SSH to control 40 machines. What i am trying to do is remotely bash a shell script on each machine. I am using a for loop to bash every script, code as follows. code in host machine runallworkers.sh: ... ... (2 Replies)
Discussion started by: mgsolid
2 Replies
Login or Register to Ask a Question
RFCOMM(1)																 RFCOMM(1)

NAME
rfcomm - RFCOMM configuration utility SYNOPSIS
rfcomm [ options ] < command > < dev > DESCRIPTION
rfcomm is used to set up, maintain, and inspect the RFCOMM configuration of the Bluetooth subsystem in the Linux kernel. If no command is given, or if the option -a is used, rfcomm prints information about the configured RFCOMM devices. OPTIONS
-h Gives a list of possible commands. -a Prints information about all configured RFCOMM devices. -r Switch TTY into raw mode (doesn't work with "bind"). -f <file> Specify alternate config file. -i <hciX> | <bdaddr> The command is applied to device -A Enable authentication. -E Enable encryption. -S Secure connection. -M Become the master of a piconet. hciX , which must be the name or the address of an installed Bluetooth device. If not specified, the command will be use the first available Bluetooth device. -A Enable authentification -E Enable encryption -S Secure connection -M Become the master of a piconet -L <seconds> Set linger timeout COMMANDS
show <dev> Display the information about the specified device. connect <dev> [bdaddr] [channel] Connect the RFCOMM device to the remote Bluetooth device on the specified channel. If no channel is specified, it will use the chan- nel number 1. If also the Bluetooth address is left out, it tries to read the data from the config file. This command can be termi- nated with the key sequence CTRL-C. listen <dev> [channel] [cmd] Listen on a specified RFCOMM channel for incoming connections. If no channel is specified, it will use the channel number 1, but a channel must be specified before cmd. If cmd is given, it will be executed as soon as a client connects. When the child process ter- minates or the client disconnect, the command will terminate. Occurrences of {} in cmd will be replaced by the name of the device used by the connection. This command can be terminated with the key sequence CTRL-C. watch <dev> [channel] [cmd] Watch is identical to listen except that when the child process terminates or the client disconnect, the command will restart lis- tening with the same parameters. bind <dev> [bdaddr] [channel] This binds the RFCOMM device to a remote Bluetooth device. The command did not establish a connection to the remote device, it only creates the binding. The connection will be established right after an application tries to open the RFCOMM device. If no channel number is specified, it uses the channel number 1. If the Bluetooth address is also left out, it tries to read the data from the config file. If all is specified for the RFCOMM device, then all devices that have bind yes set in the config will be bound. release <dev> This command releases a defined RFCOMM binding. If all is specified for the RFCOMM device, then all bindings will be removed. This command didn't care about the settings in the config file. AUTHOR
Written by Marcel Holtmann <marcel@holtmann.org>. APRIL 28, 2002 RFCOMM(1)