You may find some predefined configuration files in cfg-data/Server-mode and cfg-data/Bemused-emulation directories. I hope after investigation of these configuration files You'll become more familiar with its format.
AutoRepeat=false
Auto repeat feature (as on PC keyboard - about 10 events per second). Usefull for mouse emulation, for example. Default value is false.
Baudrate=19200
Baudrate to use; default value is 19200
Device=bluetooth:10
Device to connect; default value is /dev/rfcomm0.
If anyRemote works as server correct value for Device could be: Device=socket:"port" or Device=bluetooth:"channel"or just Device=bluetooth (to choose first available channel).
Log=true
Print or not to print logging info to the file $HOME/.anyRemote/anyremote.log, default value is false.
Debug=true
Print or not to print verbose logging info to the file $HOME/.anyRemote/anyremote.log, default value is true.Works only if Log=true.
Screen=true
Send or don't send any commands (SetStatus(), SetTitle(), etc.) to phone. Default value is false.
MaxTextSize=18
Set the maximal size of text which can be sent to phone by Set(text...) command. MaxTextSize measured in chunks of 240 byte size. So, 18 chunks is about 4Kbyte. Set MaxTextSize to -1 to unset the limit. Default value is 18.
GuiAppName="application name"
GuiAppBinary="name of executable"
GuiAppRun="command do determine is application running or not; must returns OK or NOK"
GuiAppIcon="icon name"
GuiAppType=Application|Custom|Example
These parameters are used by GUI tools only.
GuiAppName=Amarok GuiAppBinary=amarok GuiAppRun=echo 'A=`dcop | grep amarok`; if [ "x$A" == "x" ]; then echo NOK; else echo OK; fi' | bash -f -s GuiAppIcon=amarok.png GuiAppType=Application
[Aliases] section
Format:
Key_Code=New_alias
1=One 49=Oneand then use "One" in [Keys] section instead of "1" or "49"
[Keys] section
A short example:
[Keys] (Init)=Exec(kdialog --msgbox "Initialized"); (Connect)=Exec(kdialog --msgbox "Connected on $(Time)") (Disconnect)=Exec(kdialog --msgbox Disconnected) 1=Exec(kdialog --msgbox 1) 2=Exec(kdialog --msgbox 2) 3=Exec(kdialog --msgbox 3) 4=Exec(kdialog --msgbox 4) 5=Exec(kdialog --msgbox 5) [End]
Format:
Key_Codes=Command1;Command2;Command3;....
Where CommandX could be:
Exec() command
1=Exec(kdialog --msgbox 1) 2=Exec(kdialog --msgbox 2)
It is possible to define multi-key commands
3 1=Exec(kdialog --msgbox 3_1) 3 2=Exec(kdialog --msgbox 3_2) 3 3 1=Exec(kdialog --msgbox 3_3_1)
It is not good idea to define:
3 3=Exec(kdialog --msgbox 3_3) 3 3 1=Exec(kdialog --msgbox 3_3_1)
simultaneously, since only one command will works (which one - depends on search order).
It is possible to group keymappings in so-called "mode" to set more than one command to the key:
1=Exec(kdialog --msgbox 1) 2=Exec(kdialog --msgbox 2) [Mode]=1 1=Exec(kdialog --msgbox 1_in_Mode_1) 2=Exec(kdialog --msgbox 2_in_Mode_1) [ModeEnd] [Mode]=2 1=Exec(kdialog --msgbox 1_in_Mode_2) 2=Exec(kdialog --msgbox 2_in_Mode_2) [ModeEnd]
If current mode is not default mode (see SetMode() command), then firstly key will be searched in current mode and if not found then it will be searched in default mode. As a result it needs to use (EnterMode) and (ExitMode) "events" very carefully in default mode.
It is possible to write rather complex commands inside Exec(), for example:
1=Exec(echo 'D=`dcop | grep digikam`; if [ "x$D" == "x" ]; then digikam& else dcop $D MainApplication-Interface quit;' | bash -f -s)
Command could be parametrized (see here for details):
List($$)=Exec(kdialog --msgbox $(Param))
Macro() command
This command used to group several commands:
1=Macro(Macro1) Macro1=Exec(kdialog --msgbox 1);Exec(kdialog --msgbox 2)
Set()
These commands used to control and customize GUI of Java client. See detailed description here.
It is possible to change: |
![]() |
![]() |
Format: ExecAndSet(tag,command)
This command similar to the Set(), but uses the output of command specified as a string to set GUI elements of Java client specified in tag field. See detailed description here.
5=ExecAndSet(title,dcop amarok player nowPlaying); 6=ExecAndSet(status,date)Timer()
Format: Timer(timerId, timeout, maxTimes, tag, command)
This command similar to the ExecAndSet(), but it will be executed periodically by timer. See detailed description here.
For example, the following command run 'dcop amarok player nowPlaying' command 2 times with timeout equal to 5 sec and set result to the title field of Java client:
7=Timer(id1, 5, 2, title, dcop amarok player nowPlaying)
The following command run 'date' command every 10 sec and set result to the status field of Java client:
8=Timer(id2, 10, 0, status, date)
It is impossible to have two active timer commands with the same timerId. If results of the executed command is the same as previous one, then results will not be sent to Java client.
CancelTimer()Format: CancelTimer(timerId)
This command deletes timer previously created by Timer() command by specified timerId.
9=CancelTimer(id1)
Load() command
This command used to load commands from file and execute them:
1=Load(file_name.cmds)
Include() command
This command used to include definitions from [Keys] section from external cfg.file:
1=Include(xmms.cfg))
Only [Keys] section will be loaded (no [Aliases] and [Alarms]). Definitions from included file will not rewrite
existing definitions if any.
Send()
Format: Send(string, string_value)
or Send(byte, byte_value1, byte_value2,...)
Send to the Java client specified string or sequence of bytes. This command is used mainly in Bemused server emulation.
1=Send(string, simple_string)
byte_valueX is string representation of 1 - 255 values. Send(byte, ...) command sends to the Java client specified bytes of data, one by one. Mainly this command is used to Bemused server emulation.
2=Send(bytes,35,42,0)
ExecAndSend()
Format: ExecAndSend(tag,command)
This command similar to the Send(tag, ...), but uses the output of command specified as a string to send. So, it is possible to execute dynamically created command. This command also is used in Bemused server emulation.
3=ExecAndSend(string,date) 4=Exec(echo "Set(title,dynamic title)">/tmp/command.txt);ExecAndSend(string,cat /tmp/command.txt)Get()
Format: Get(screeen_size|model) or
Get(is_exists,16|32,_icon_name_)
This command used to retrieve from phone some information.
3=Get(screeen_size) 4=Get(model) 5=Get(is_exists,16,next)Get(screeen_size) used to get screen size of cell phone. As a response to this command two replies will be send: SizeX(width,) and SizeY(height,). SizeX(width,) reply will be the first one.
Get(model) used to get "microedition.platform" property of Java client. For many phones this property contains manufacturer and model number (like "SonyEricssonK750i/R1CA021" for SE-K750). As a response to this command Model(,_string_) reply will be send. Get(is_exists,...) used to determine was icon with given name and size uploaded to phone or not. As a response to this command IconExists(_icon_name_,) or IconNotExists(_icon_name_,) reply will be send.
There are several "internal" commands:
TempDisconnect used to temporary (1 minute) disconnecting from phone:
1=TempDisconnect;
Exit command used to exit from application:
2=Exit;
Switch off "remote control" functionality without disconnecting:
3=RemoteOff;
Switch on "remote control" functionality:
4=RemoteOn;
Change mode:
5=SetMode(xmms)
There are several "events" could be triggered:
(Init) event will be fired when anyRemote is initialized:
(Init)=Exec(kdialog --msgbox "Initialized")
(Connect) event will be fired when connection established:
(Connect)=Exec(kdialog --msgbox "Connected on $(Time)")
(Disconnect) event will be fired when connection is lost:
(Disconnect)=Exec(kdialog --msgbox Disconnected)
Auto-lock example:
(Connect)=Exec(killall kdesktop_lock) (Disconnect)=Exec(kdesktop_lock --forcelock)
Incoming call handling. Not sure it will works for all JSR-82 capabled phones. But it works at least for SE-K750.
(InCall)=Exec(kdialog --msgbox "Incoming call")
End of call handling. Not sure it will works for all JSR-82 capabled phones. But it works at least for SE-K750.
(EndCall)=Exec(kdialog --msgbox "Call ends")
Auto-mute example (amixer utility should be installed, example is for soundcard #0):
(InCall)=Exec(amixer -c 0 sset Master,0 mute);RemoteOff (EndCall)=RemoteOn;Exec(amixer -c 0 sset Master,0 unmute)
Take a look to the order of commands above. RemoteOff command is the last one. If You change order to
(InCall)=RemoteOff;Exec(amixer -c 0 sset Master,0 mute)
then Exec(amixer -c 0 sset Master,0 mute) will not be executed.
If mode is changed by SetMode() then (ExitMode) event for current mode and (EnterMode) event for the new mode will be fired:
*=SetMode(XMMS) (ExitMode)=Exec(kdialog --msgbox "Exiting from current mode") [Mode]=XMMS % Do some initialization steps (EnterMode)=Exec(kdialog --msgbox "Enter to XMMS mode");Exec(xmms) % Do some cleanup steps (ExitMode)=Exec(kdialog --msgbox "Exiting from XMMS mode");Exec(killall xmms)
Variable substitution:
In Exec(), ExecAndSet(), Timer(), SetMode(), Load(), Include() commands is it possible to use several predefined internal "variables".
Current time will be substituted instead of $(Time):
2=Exec(kdialog --msgbox $(Time))
Current mode be substituted instead of $(Mode):
3=SetMode(xmms);Exec(kdialog --msgbox "New mode is $(Mode)")
Directory in which resides used cfg.file will be substituted instead of $(CfgDir):
3=ExecAndSet(list,replace,Cfg Files,ls -1 $(CfgDir))
There are $(Param) and $(Index) variables defined in handling command issues from Java Client menus. See here for details. Use $$ inside braces to specify parametrized commands.
Choose($$)=Exec(xmmsctrl track $(Index));Exec(kdialog --msgbox "Selected track is $(Param)")
[Alarms] section
Format:
Alarm_file=command1;command2;...
When file Alarm_file will be created, then command1, command2 ... will be executed.
/tmp/alarm1=SetStatus("xmms was stopped")