Try <blue>FullScreen</blue> in your remote.xml file
Just so you know in order to cross reference a keyboard button to an action aka press button A does so so... so you can edit the remote button to do the same. You have to look at the keyboard.xml file which by default is located in /usr/share/xbmc/system/keymaps. There is an xml file for each input, keyboard, remote, xbox controller, joystick even.
Read up on how default vs the version in home dir works
http://wiki.xbmc.org/?title=Keymap.xml#U...al_Remotes
Essentially the version in /home/USER/.xbmc/userdata/keymaps folder is for customization and only the specific changes you want should be in there (remove all other sections from the xml file, aka if you still have to keep the general structure of the code but remove the COMMANDS).
This way when you update xbmc you remote customizations are still in effect with out having to re-edit them, while at the same time anything new will take effect as well.
Example... This is just an example not the whole file...
Here is the original text in the xml
<global>
<keyboard>
<p>Play</p>
<q>Queue</q>
<f>FastForward</f>
</keyboard>
</global>
Lets say you want to only edit the Play button (leaving fast forward etc default). You would copy the xml from the usr/share... dir to /home/USER/... dir then delete everything you want to stay default and edit like...
<global>
<keyboard>
<p>EDITED PLAY ACTION COMMAND</p>
</keyboard>
</global>
Notice I had to keep the structure of the file... think of it like folders... Global is the parent folder, which has a folder called Keyboard. The commands are in the keyboard folder... I have to keep the folders the way they are (but could delete another folders/sections if I have no commands to change in them) but the files/commands are removed/edited.
XBMC always looks for commands in the xml file in the /home/USER... location FIRST. If it doesn't find a command, it then checks the default location of /usr/share... etc