AndroidManifest.xml: move <uses-permission> entries before <application> to avoid warnings
Add support for Google-TV devices
TerminalKeyListener: Add comment about printing characters and how C0 sequences are handled
TerminalManager: re-insert log message in onCreate(). Got lost in a cherry-pick
get rid of BugSense
fix eclipse project setup
use SDK constants to decide whether to use the action bar.

This gets rid of the ugly try/catch

Refactor the SDK constants in PreferenceConstants to reduce number of
Integer.parsInt() calls
PubkeyUtils: code style and small optimizations
Irssi Channel Switcher: use AlertDialog instead of Dialog to fix keyboard hiding/showing issues
Terminal long press: remove useless additional dialog creation
ConsoleActivity: only show SYM/CTRL/ESC/... on action bar if it is enabled
ConsoleActivity: fix transparent background of Ctrl button image
ConsoleActivity: add Tab button to on-screen keyboard group, and the action bar / menu

Slightly reduced the padding between the buttons.
ConsoleActivity: fix on-screen button-group auto hiding interfering with clicks

As soon as the on-screen group is made visible, its hiding is scheduled.

In case of a click on one of the buttons the group is instantly hidden.

The problem was, that the scheduled task was not removed in this case.
This could lead to unexpected behaviour if the group was opened again,
while the scheduled task was not yet performed -> the group would disappear
too early.

Solve it by removing the the Runnable from the Handler when group is hidden.
ConsoleActivity: don't force open the soft keyboard on rotation

Before, every time the screen was rotated the soft keyboard popped in,
even if it was hidden before the rotation.

This commit makes the soft keyboard stay in the state it was before
the rotation occured.
HostListActivity: hide soft keyboard when entering the host list

Only show the soft keyboard when the user actually wants to add
a new host and deliberately touches the 'user@host' editbox.
ConsoleActivity: properly handle orientation change for API 13+

added 'screenSize' to 'android:configChanges', because it gets
triggerd additionally to 'orientation' on API 13+.

From the docs:
> Note: If your application targets API level 13 or higher
> (as declared by the minSdkVersion and targetSdkVersion attributes),
> then you should also declare the "screenSize" configuration,
> because it also changes when a device switches between
> portrait and landscape orientations.

This restores the intended behaviour before the bump to API 15,
which speeds up the orientation change a lot, because the whole
activity destory/create part is skipped.

This also fixes a bug where all menu entries were disabled after
an orientation change.
terminal session: replace ugly 'setVolumeControlStream()' hack with proper way to disable volume key beeps

Volume key beeps are fired on key up events. Consuming them will disable the beep.

This is a much cleaner way than fiddling with the audio streams.
ConsoleActivity: Menu optimizations and bugfix

- refactor redundant code in onCreateOptionsMenu and onPrepareOptionsMenu:
  onCreateOptionsMenu did the same enabling/disabling of the buttons
  that onPreareOptionsMenu is doing all the time, anyways.
  It is not needed, and was removed.

- Disable the sym/ctrl/key/... buttons, too, in case we are disconnected.

- Work around a bug in android that does not properly call onPrepareOptionsMenu
  in case the device has a hard menu button and the menu button is pressed
  for the first time.
  This could lead to in invalid menu, like buttons being enabled, when they
  actually shouldn't be, because we got disconnected in the meantime.
  This is related to the ActionBar and thus happens only on API13+
  Compare
  * http://code.google.com/p/android/issues/detail?id=24231
  * http://stackoverflow.com/questions/12405825/how-can-i-force-the-onprepareoptionsmenu-method-to-fire
  * http://stackoverflow.com/questions/12886751/jelly-bean-not-calling-onprepareoptionsmenu-when-opening-the-menu-for-the-firs
  The invalidateOptionsMenu() solution is pretty bad, because it causes the whole menu to be rebuilt.
  Instead, just cover this one special case ourselves.