clean up tmp files

screenshot and xml dumps are pulled from device and stored into
tmp directories, this leaves a lot of traces behind until the
system reboots. we now keep track of temp directories created
and delete them when the app exits.

Change-Id: I3190dd93c3b413afc0a513eaedf11409f3e5efa8
fixing some UI issues on Linux

* the app was showing some strange layout on Linux, removing the
  fill layout for base panel resolves it, not clear why though
* resizing behavior was incorrect on Linux, removing "no redraw
  on resize" style fixed this problem.

also verified on Mac that things still works correctly with
these changes

Change-Id: I423ed83d9909391d07be95c3b948eb308c25f00e
Force the input area to hide

Currently DummyIME is just an empty implementation, which is not
good enough: sometimes this causes a full screen input area to
be shown. This change forces the DummyIME to hide input area
explicitly.

Change-Id: I1282df8c74e5b37bf31acdc6f188b6859c5379bc
merge in jb-mr0-release history after reset to jb-dev
Clean up of code comments and fixed UiSelector clone

- Removed UiDevice.isPhone()
Change-Id: Id0157d5c425cd14fd738f4850a4623a36e5e4ab1
merge in jb-mr0-release history after reset to jb-dev
Generate api stubs for uiautomator library.

Run "make android_uiautomator" to generate the stub library.

Bug: 6814443
Change-Id: I6a242575a2ac93095999a84b58d9c9c56d6df4a1
add API to get screen size in dp, and a skeleton test

As a replacement for UiDevice#isPhone, a better way to determine
the layout in use is to look at screen size, as most apps are
doing to adjust layout, more specifically, the width in dp

The skeleton test is meant to be used as a prototype for
spawning new UI tests. It has basic setup to be built in the
source tree, and has one single test case.

Change-Id: I1c4738eba4aca24fcb960dfd873c51107777789e
Merge "Generate api stubs for uiautomator library." into jb-dev
merge in jb-mr0-release history after reset to jb-dev
Noticed some clicks are fired but going ignored during tests

Unsure what this is but it looks as if the clicks (touch down then up)
are fired too fast and maybe ignored in some cases causing tests
to fail.

Also documentation error for the swipe methods

Change-Id: I2a9bcb32c66a0f771d66d3133522646bb7a25fda
merge in jb-mr0-release history after reset to jb-dev
resolved conflicts for merge of 9858df8b to jb-dev-plus-aosp

cherry-picked from AOSP
"""
    removing uiautomatorviewer from frameworks/testing
    It is to be moved into sdk
"""

Change-Id: I8b2fc6bcdceda0705d7e2f337a7dc71c3451c26c
merge in jb-mr0-release history after reset to jb-dev
Allow "click" logging to appear in logcat

We see clicks disappearing and actions not performed. To help in
diagnosing this, we will need to be sure a click is being fired
by the uiautomator. This was only enabled in DEBUG. Now it should
always be allowed. Clicks are rare and should not cause any log
spam.

Change-Id: I5914cc4b3ce5104ab60939bc64c09b33b07cabad
UI Automator public API cleanup

@hide some public methods and classes that we do not intend to
export in the SDK. Also adjust visibility on variables, methods
used inside the library classes.

Change-Id: I3492bb30a4b0040b298b7d96f255f137599ee8aa
more tweaks to visibility of methods, variables

Change-Id: Ia51395f89a5d3aa3994b550ab142519774dbe0f1
merge in jb-mr0-release history after reset to jb-dev
Merge android-4.1.2_r1