To run anyRemote frontend execute command:
ganyremote
for Gnome or
kanyremote
for KDE
After startup anyRemote icon will appear in the tray. To open main window choose "Restore" tray menu item. It is possible to specify -o option to open main window at startup. Upon startup frontend will scan all found configuration files and show list which will looks like picture below. | ![]() |
![]() |
Status column shows does particular application runs on PC or not. Frontend will rescan application activity each minute (can be changed in preference window).
To run anyRemote it needs just to double-click application name. Alternatively it is possible to use tray menu items Execute/Stop, or
File->Execute/Stop menu items in main window.
In preferences window (see below) it is possible to specify locations of configuration files, filters and tune various parameters.
![]() |
To use anyRemote GUI it needs to have at least one element in "Directory" list. In normal situation frontend will find
location of configurational files automatically.
By default frontend will scan for BT devices each minute. Found devices will be marked as "Available" in list. To be detected an BT device must be in discoverable mode. If new BT device will be detected, then Device Detail window (see below) will be shown automatically. | ![]() |
In Device Detail window it is possible to
|
![]() |
... be double sure that all software prerequisites are installed.
By default anyRemote will search the following configuration files:
You can specify another configuration file with -f option, for example:
anyremote -f /...path_to.../xmms.cfg
You may find some predefined configuration files in:
It is possible to use anyremote2http package to organize web interface for anyRemote. With help of this interface any device which contains web browser and which can connect to PC with anyRemote by IP (GPRS, Wi-Fi, ...) could be used as remote control. Read for details.
By default anyRemote does not prints any logging information.
It is possible to set Log=false|true|debug in configuration file or use "-log" command line option to allow logging. By default all logging information will be stored in $HOME/.anyRemote/anyremote.log file. This could be altered by setting AR_TMPDIR environment variable. If AR_TMPDIR environment variable is set then logging information will be printed to ${AR_TMPDIR}/anyremote.log.${USER}
If configuration file uses amixer utility to control sound volume and it needs to control non-default soundcard it is possible to create file $HOME/.anyRemote/amixer.card with content like "-c X", where X is number of sound card to control.