Use "&" (bitwise and) operator to determine if characteristic is Read or Notify

Previously used "|" bitwise or) operator, always evaluated to true.
Merge pull request #40 from avantol/master

BluetoothLeGatt: Use "&" (bitwise and) operator on GattProperty
Workaround for bug #14104 - there is no way to generate java interface, so do it manually and invoke it by reflection.
[ApiDemo] Start to cover additions from Googles latest 'ApiDemos' iteration

Update and begin porting newly offered APIs and examples from Googles ApiDemos sample
Adjusting the padding on a textview.
Asyncify the reverse geo coding example.
[ApiDemo] Fix fade / zoom animation activity launch on API 10 and lower devices
[ApiDemo] Disable a few activities when running below API 14 or 11
[ApiDemo] Fix InvalidCastException in VoiceRecognition
Initial commit Image effects demo
Merge pull request #42 from prashantvc/master

Image effects demo
Set TargetFrameworkVersion to 2.3.3.

These projects had $(TargetFrameworkVersion) set to "v2.3", which is
API level 9, which we no longer support (and Google no longer
supports, and we haven't shipped API-9 in ages, and...).

Bump these projects to target "v2.3.3" (API-10), which IS supported.
Revert "Set TargetFrameworkVersion to 2.3.3."

This reverts commit d2bb4d3b540cdfd1737560f62cde9600da3ff163.

On Windows, $(TargetFrameworkVersion)=v2.3 IS API-10; a v2.3.3 framework is
NOT installed, and not selectable, and selecting API-10 within e.g.
Visual Studio results in $(TargetFrameworkVersion)=v2.3, not v2.3.3.

Which is just a level of confusion I was not expecting...
Merge pull request #2 from xamarin/master

pull latest