Mobile and Embedded

@UPSNAIL did you succeed in this? if yes kindly help me also i am also having the same problem when trying to display a widget application in raspberry pi

I write because my thread with same topic... https://forum.qt.io/topic/80451/nfc-android

@ekkescorner I cannot use Bluetooth Le due to hardware restrictions

with a little help from @Jake-Petroules: here's HowTo avoid all these warnings. Add into .pro iOS { ... disable_warning.name = GCC_WARN_64_TO_32_BIT_CONVERSION disable_warning.value = No QMAKE_MAC_XCODE_SETTINGS += disable_warning

Ok, I've since taken a step back and had a cup of tea. I had a search for additional packages which may have sounded useful and I came up with the following: libx11-xcb-dev and libxext-dev. Downloaded them both and copied the header files/directories to /usr/include. I then ran a make clean on the qtbase directory before re-attempting to reconfigure. When I did eventually do a ./configure, I noticed that the EGL for X11 suddenly had a bit, fat YES next to it, along with a number of other XCB options which were previously NO. Having run make and make install and then deployed the qt5 target folder to the TK1, I can now say that everything just works! Thank you @jsulm for your help with this.

@sandycoolxyz Maybe you can also use std::bitset.

I don't have such a watch so I can't comment on how/what to do however I've seen some demos from the watchOS platform maintainer so there's likely things to be done :)

@Andy-Matos Does this USB camera work on your device?

@Mena I see ;-) Looks like you are not the only one who has this problem: https://bugreports.qt.io/browse/QTBUG-56648

@jsulm Our application is launched as part of a system service on startup. I redirected the output and it all looks normal. I think we're resolved the issue though. It appears some qml environment variables were being set before launch when we had recently changed to qwidgets. Upon changing to EGLFS these vestigial variables prevented EGLFS from rendering text correctly for some reason.

@jsulm Thx for a reply in this desperating thing... I checked that page already (a bit hidden by the way). It is registered and the application get launched on tag detection, but i don't receive the data because the QNearFieldTarget::Error(TargetOutOfRangeError) probability related to the null pointer exception in java. i wonder if it could be related to https://bugreports.qt.io/browse/QTBUG-59343

@no_ideaw Can you show your pro file? Also did you run qmake and rebuild your project after changing Kit to "Android for armeabi-v7a"?

@SGaist you're right: would be better to use a symbolic link haven't thought about this (that's the drawback doing as most stuff as possible from IDE's instead of cmd line ;-)

@jsulm Sr if my information is not correct. However, I have asked the same question before and the answer I got that "decode using GPU not use Hardware IP so performance is not good on Qt in that time". So I chose the way that I use Qt to control Gstreamer directly, not using QMediaplayer of Qt for playback. It worked Ok but there is some problem with UI. By the way, I heard that Qt4.7 support Phonon support good for media playback but it's not available on Qt5.

@ekkescorner thanks so much, i have some tasks, will do it before trying that maybe blog will be ready

Hi, What about old video game style ? Create a keyboard widget and move your letter cursor around using your available keys.

[image: giphy.gif]

Back from the dead. I had some free time, so I applied my patches to a fork of the latest Qt 4 repo on Github: https://github.com/leeson-consulting/qt I've applied some other patches gleaned off the internet to allow the code to work with VS 2017 and added a helper build script. Hope it's of use to someone :-)