MER: eglfs: Allow scaling down the window surface

Adapted from commit 0061edc2 from mer-stable branch.

See merge request !17

Online

One particular scenario fixed with this patch:

1. Session state changes from Connected to Connecting (that could be another bug but why not?)
2. _q_networkSessionStateChanged switches online to false
3. Session state changes to Disconnected, online is already false
4. online state stays false even though another configuration gets connected.

With this change, when one session becomes Disconnected, a new session is created and online state becomes true when it should.

See merge request !18

A few fixes to evdev touch filtering

- Clamp the position to the bounding rect of the device
- Send TouchRelease only once

Change-Id: I8776079dbc886612e6adfb1fef5ec7cf14a8af3b
Reviewed-by: Laszlo Agocs <laszlo.agocs@qt.io>

See merge request !20

- Clamp the position to the bounding rect of the device
- Send TouchRelease only once

Change-Id: I8776079dbc886612e6adfb1fef5ec7cf14a8af3b
Reviewed-by: Laszlo Agocs <laszlo.agocs@qt.io>

Remove redundant declaration

See merge request !19

Improvements to touch filtering

- Add support for devices where touch coordsystem is different
   from screen's.
 - Expose correct normalPosition
 - Avoid race condition in filtered. reportPoints() can change m_touchPoints
   so it needs to be covered by the mutex.

See merge request !16

- Add support for devices where touch coordsystem is different
  from screen's.
- Expose correct normalPosition
- Avoid race condition in filtered. reportPoints() can change m_touchPoints
   so it needs to be covered by the mutex.

Particularly, it handles the following scenario:

1. Session state changes from Connected to Connecting
   (that could be another bug but why not?)
2. _q_networkSessionStateChanged switches online to false
3. Session state changes to Disconnected, online is already false
4. online state stays false even though another configuration
   gets connected.

With this change, when one session becomes Disconnected, a new
session is created and online state becomes true as it should.

This reverts commit 3112a8bd.

This patch introduces the QT_QPA_EGLFS_SCALE environment variable.
When set to an integer number > 1 it will scale the draws window
content down by that scale factor.

This is only needed for the Sailfish SDK emulator, for now and i'm
not sure this belongs upstream.

(cherry picked from commit 0061edc2)

Update project URL

See merge request !15

[qtbase] QLocale data regenerated with initial Tatar locale support. Fixes MER#1707

The Tatar locale data is taken from the recent CLDR tag (v30.0.2), but all other
locales kept in the same version (v27). The language data is inserted in between,
so it moves a lot of other locale data, which increases the diff.

Before the commit I verified, that generation without Tatar locale files results in
no other changes, than generation timestamp in a comment.

Steps to update the data with Tatar locale support:
1. Find out the used CLRD version. The current version is v27.
(grep "Common Locale Data Repository" src/corelib/tools/qlocale_data_p.h)
2. Download the same version at http://cldr.unicode.org/index/downloads (file core.zip)
3. Extract the data to a directory, e.g. ~/cldr-27
4. Generate XML data. Probably it would be more convenient to it in the "qtbase" directory:
util/local_database/cldr2qlocalexml.py ~/cldr-27/common/main > locales.xml
5. At the same directory:
util/local_database/qlocalexml2cpp.py locales.xml `pwd`
6. Ensure that there is no changes in code (changes in comments are OK).
7. Choose the needed version for Tatar locale. "trunk" seems to be reasonable version at this moment.
http://cldr.unicode.org/index/downloads/
8. Download the locale files from seed/main (currently) or common/main (once the locale
   will be finished) to the main CLDR directory (~/cldr-27/common/main). E.g.:
wget http://www.unicode.org/repos/cldr/trunk/seed/main/{tt,tt_RU}.xml;
mv tt*xml ~/cldr-27/common/main;
9. Repeat steps 4 and 5.
10. Check that the changes are applied (git diff shows difference in src/corelib/tools/qlocale_data_p.h)
11. Done. Optionally: make a commit.

See merge request !14

The Tatar locale data is taken from the recent CLDR tag (v30.0.2), but all other
locales kept in the same version (v27). The language data is inserted in between,
so it moves a lot of other locale data, which increases the diff.

Before the commit I verified, that generation without Tatar locale files results in
no other changes, than generation timestamp in a comment.

Steps to update the data with Tatar locale support:
1. Find out the used CLRD version. The current version is v27.
(grep "Common Locale Data Repository" src/corelib/tools/qlocale_data_p.h)
2. Download the same version at http://cldr.unicode.org/index/downloads (file core.zip)
3. Extract the data to a directory, e.g. ~/cldr-27
4. Generate XML data. Probably it would be more convenient to it in the "qtbase" directory:
util/local_database/cldr2qlocalexml.py ~/cldr-27/common/main > locales.xml
5. At the same directory:
util/local_database/qlocalexml2cpp.py locales.xml `pwd`
6. Ensure that there is no changes in code (changes in comments are OK).
7. Choose the needed version for Tatar locale. "trunk" seems to be reasonable version at this moment.
http://cldr.unicode.org/index/downloads/
8. Download the locale files from seed/main (currently) or common/main (once the locale
   will be finished) to the main CLDR directory (~/cldr-27/common/main). E.g.:
wget http://www.unicode.org/repos/cldr/trunk/seed/main/{tt,tt_RU}.xml;
mv tt*xml ~/cldr-27/common/main;
9. Repeat steps 4 and 5.
10. Check that the changes are applied (git diff shows difference in src/corelib/tools/qlocale_data_p.h)
11. Done. Optionally: make a commit.

[Qt] Aarch64 build fixes. Contributes JB#36790

Add -no-pch to configure for aarch64 builds
EGL X seems to be built if it can be, which seems to be under aarch64.

See merge request !12

Add -no-pch to configure for aarch64 builds
Include the eglfs-x11 intergration if X11 is present

Improve touch filtering. Contributes to JB#36352.

Rather than using separate 1D filters for each of x,y,vx,vy, use a 2x2
matrix to represent position and velocity in a more proper kalman filter.

See merge request !11

Rather than using separate 1D filters for each of x,y,vx,vy, use a 2x2
matrix to represent position and velocity in a more proper kalman filter.

Jb36619



See merge request !10

So that if QtCore is updated then all pre-5.6.2 modules will also be
updated.

We must ensure that QDBusServer's newConnection() signal has been
processed by the application, before starting processing messages on it.

Task-number: QTBUG-55087
Change-Id: I595329b2f98788dbf9f40558b8c230c0c0817ef8
Reviewed-by: Timo Jyrinki <timo.jyrinki@iki.fi>
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>

[packaging] Configure with -no-opengles3 to avoid inclusion of problematic gl3.h header. Contributes to JB#35409.

The next stateChanged() may already be queued by the time we have received
closed() signal and cleared the session reference. Sometimes that was
resulting in QNetworkAccessManager getting stuck in NotAccessible state.

Conflicts:
	src/network/access/qnetworkaccessmanager.cpp

Configuration via QtProject/QPlatformTheme.conf (system settings only)

Change-Id: I7f0d3bcc86d319eb242bd9cb30b2eb54f0696aa4

Originally introduced to mer-packages/qtbase with
62ba0852

[MER]: This patch is not upstreamed as libsystrace is not widely in use, the
impact of additional function calls into QtBase was undesired, and the general
approach is not really generic to other types of tracing at this time.

libsystrace is a very small initialized-on-load wrapper for Android systrace
functionality, used so that data is written in order, regardless of how many
different libraries are writing data to it at a given time.

systrace is very useful for tracking system behavior, and for performance
analysis and improvement.

See also:
https://developer.android.com/tools/debugging/systrace.html

Some example uses of QSystraceEvent are also included in this patch. More are
undoubtedly possible. Additional tracing (e.g. counting the number of ongoing
HTTP requests and various other bits and pieces) are also easily accomplished.

Change-Id: I70012f6ddaa084f5b08685ee40795d7fafcd9c96

Conflicts:
	configure
	src/corelib/global/global.pri
	src/dbus/qdbusintegrator.cpp

Change-Id: I39f5c4918107d894b8335b11c3b9c26b2b728421
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>