summaryrefslogtreecommitdiffstats
path: root/dist/changes-5.3.2
blob: e700e85e27f5de52126646b7a362026cc74bda22 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
Qt 5.3.2 is a bug-fix release. It maintains both forward and backward
compatibility (source and binary) with Qt 5.3.0 and Qt 5.3.1.

For more details, refer to the online documentation included in this
distribution. The documentation is also available online:

  http://qt-project.org/doc/qt-5.3

The Qt version 5.3 series is binary compatible with the 5.2.x series.
Applications compiled for 5.2 will continue to run with 5.3.

Some of the changes listed in this file include issue tracking numbers
corresponding to tasks in the Qt Bug Tracker:

  http://bugreports.qt-project.org/

Each of these identifiers can be entered in the bug tracker to obtain more
information about a particular change.

****************************************************************************
*                           General                                        *
****************************************************************************

QtBluetooth
-----------

 - Removed dead code from the library.

****************************************************************************
*                      Platform Specific Changes                           *
****************************************************************************

Android
-------

 - [QTBUG-39815] Removed calls to Android's BluetoothSocket.isConnected().
   It does not work reliably on all devices and prevented those devices from
   successfully establishing an RFCOMM socket connection.

 - [QTBUG-40172] Increased robustness of QBluetoothSocket::connectToService()
   by providing a fallback implementation using private Android APIs which
   increase the chance of successful connects on some devices.

Linux
-----

 - Removed undesirable system header includes from the Bluez code base.
 - Fixed incomplete SDP entries when using L2CP sockets and avoided
   crash on client side when incomplete SDP entry is encountered.