if trying to click on a webelement in a frame, use synthetic events as it is not easy to calculate the location of the element if there are nested frames

Fixes #231
adding test for clicking element in frame

currently fails due to element.getText not throwing a stale element reference exception
fixing so the click itself doesn't throw a stale reference exception
Use a wait until the server on the device is started in the e-2-e tests.
Correct spelling in error message. No logical change.
Correctly capitalize "stackTrace" so that responses now print them out.
Make the returned SelendroidResponse exception match the requirements of the RemoteWebDriver.

This means constructing a frame object per element in the stack trace, rather than simply
spamming everything into a String. Note: this change does not contain the full trace, just
the exception that is passed in.
correcting my name / username in pom - authors
Added facilities to inject base-level UI operations with more advanced synchronization
than android Instrumentation class does. This allows us to fetch and propagate unhandled
exceptions, occurring in application under test and causing a crash, to the local end.

Signed-off-by: Simon Stewart <simons@fb.com>
an illegal state can happen due to line AndroidNativeElement.getView()

should just return a stale element exception instead
Adding comstructor just for app testing if users have no preference with regards to device type.
Reduce length of output result logs.
Using a different property to identify that the emulator boot is done which seems to work more reliable.
Update README.md