Doc: Improved example documentation

-include a section about running the example (from qtbase/doc/global)
-added links to Qt Bluetooth or Qt NFC
-updated copyright year
-added markup to a string and other small corrections
-added \brief

Task-number: QTBUG-33597
Change-Id: Ia65821549a0e2e3fbf164188982114b4741be233
Reviewed-by: Alex Blasche <alexander.blasche@digia.com>
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>
Do not always filter Serial Port profiles out anymore on Android

1.) If we find a custom and SPP uuid we create only on service
using custom uuid as service uuid and SPP as service class uuid.
THis is the recommended way. Any remote service should really
advertise a custom uuid. Unfortunately this is not always the
case on some embedded devices. Hence we need to cover the cases
below.

2.) If we find a custom uuid only we create a service which uses
the custom uuid as service uuid but we do not set a service class.

3.) If we find a SPP uuid only, we create a service which uses SPP
as service uuid and as service class uuid. This is no problem as
Android's connectToRfcommService() call explicitly permits an SPP
uuid as connection parameter.

4.) We find none of the above the problem doesn't exist in the
first place and no service was found.

Task-number: QTBUG-38140
Change-Id: I2e9080f65b98db23782264ef9e62a410ab9f91f1
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@digia.com>
Add Qt 5.3.0 change log for QtNfc and QtBluetooth

Change-Id: Id489adfe1cfb4c652907e67950b8a12bf1c18c8c
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Fix discovery hanging in unrecoverable state due to incorrect error handling

The discovery of services happens in a sequentiali per-device order.
Once the first device's services were found, the results are processed
and the discovery is started on the next device. Unfortunately
if the search didn't create any results due to the remote device
refusing the SDP discovery or because the given remote Bluetooth
address was not valid, the discovery agent didn't continue with
the next device.

Now the error handling ensures that the discovery process is continued
with the next device (if there is any).

Task-number: QTBUG-38362
Change-Id: Ie27bbc5327eadc4bcc31b589227c51dc4fa2c7c1
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Merge remote-tracking branch 'origin/release' into stable

Change-Id: Ic86710cdf2550f5cf70c81af3f351d6712cd1b0e