Initial checking

This project should allow me to have a system service that connects to BlueZ
over DBUS on Android.

So far I'm able to start it through:
CLASSPATH="btle-framework.jar" \
                     /system/bin/app_process \
                     /system/bin \
                     --system-name=btle-framework \
                     android.server.le.BluetoothLEService
Adding dbus-java

Adding dbus-java-2.7 as is.
Removing viewer folder as Android doesn't support Swing
non needed
fixed to build point, stashing before formatting and debug schema changing
formated with AOSP rules for Eclipse
Connection works now, cosmetic changes

Connection works now, it was missing SASL authentication, as part of my migration.

Replaced Debug references with Android Log, so debug can be enabled/disabled per file
Replacing Debug interface with Android Log.

Using Android Log by default on every file by default now.
Adding DBus connection handling

Code now can connect to DBus and do things with it.
Adding interfaces for BlueZ DBus API

Started working on interfaces for connecting to BlueZ DBus API
Adding Hexdump

I'm adding cx.ath.matthew.utils.Hexdump to the class base so
java-dbus works correctly
Removing useless methods

This methods I'm taking out are for dbus-session and tcp connections which we
don't have in Android and makes no sense to make the framework bigger.
Adding dbus-java to Android.mk

Adding dbus-java to the build script so it gets built accordly.
Adding README and .gitignore

I'm adding this necessary files for a well formed project

Readme has references to DBus API that will be used.
Moving files to match what DBus-java expects.

The documentation says that java namespace needs to match the one from
dbus, so if we want to use org.bluez.Manager from DBus we need to have
org/bluez/Manager.java
Manager Interface completed

Added a full org.bluez.Manager interface
Adding BlueZ LE API inteface

Adding interfaces to all the Objects with Signals and Errors for
the BlueZ LE API provided with ics.

It may be missing some more interfaces but I need to stage the
code before testing further
Making signal parameters public
Adding an inquiry testing process

This commits creates a testing framework that allows to do inquiries
and test the adapter, as a POC that the DBus API works well enough
Fixed typo

It's Characteristics not Characeteristics