Mobile and Embedded

Great and thanks for sharing the solution ! Since you have it working now, please update the thread title prepending [solved] so other forum users may know a solutions has been found :)

Neither are supported because of the current restriction imposed by their respective platform. For iOS, it's a rule of the AppStore to use Apple's webkit. For Android I don't currently remember. Anyway for basic web usage you have now the new "QtWebView":https://qt.gitorious.org/qt/qtwebview/ module that provides an interface to the native web views for both

I found the solution !! https://www.calligra.org/blogs/sharing-with-qt-on-android/ Have a nice code!

You'r welcome ! Since you have your libraries now, please update the head title prepending [solved] so other forum users may know a solution has been found :)

Hi, gstreamer is a backend in QtMultimedia. On the other hand QtGStreamer is a wrapper library were you use gstreamer. With it you e.g. build the pipeline that you want to use. It provides various sync to paint on widget/QML/OpenGL widget. Note that the QtGstreamer library is not part of the Qt distribution it's an independent project

Hmm.. It is strange that QtSerialPort works on WinCE, because its sources was broken (may broken, as I know). It is just magic.. :)

Yes, both 4.2 and 4.4 are supported. As for installing it on an unlocked consumer device, it depends. The Nexus 7 is guaranteed to work. Others may not. See http://blog.qt.digia.com/blog/2014/07/04/making-an-android-device-boot-to-qt/

But my calqlatr on windows phone 8.1 don't have this bug. Is there any solution?

Thanks for quick reply and your suggestions. Unfortunately I was unable to resolve my problems. I have managed to work around the genymotion crash however, I downgraded the virtual-device image I was using to 4.3 ABI 18.

Unfortunately I cannot help you with this. I am however also interested in how this would be accomplished as it would be a cool thing to do.

[quote author="metRo_" date="1420753935"]It says that the enterprise edition comes with pre-built software stack for linux and android, there is anyway to built it from the Community edition? Or it is a Enterprise only feature?[/quote]The software stack is Enterprise only. Essentially, the folks at Digia put together a custom Linux distro that is optimized for deploying, running and debugging Qt applications in embedded systems. That distro is the software stack. (I don't know what exactly is in the stack -- it could be open-source software plus commercial Qt, or it could contain custom-written software too) The Community version of that is to build a distro (Ubuntu, or Angstrom, or something else) that contains Qt libraries. The "Yocto Project":https://www.yoctoproject.org/ is a good place to start. Further reading: "HTG Explains: What’s a Linux Distro and How Are They Different?":http://www.howtogeek.com/132624/htg-explains-whats-a-linux-distro-and-how-are-they-different/

I ended up changing the QAndroidPlatformFontDatabase to load only one font: the NotoSans CJK Japanese otf font. Apparently the other languages fall back to the system's loaded fonts because all of the other language glyphs (Russian, Portuguese, Spanish, Chinese, Korean, etc.) are displayed properly. I'm not sure exactly why this works, but it works. I'm closing this topic.

Youc an also specify the capabilities to be used inside the pro file, so that you do not need to manually update the Manifest each time. Check http://doc.qt.io/qt-5/qmake-variable-reference.html#winrt-manifest for more documentation. In that specific case add the following to your .pro file: WINRT_MANIFEST.capabilities_device = location

Actually as also indicated in the bug report, you can create a package including a recources.pri and that is via Visual Studio. Visual Studio usually takes also other steps when you are uploading a package to the store and you need to use it in any case. So my proposal is to let VS create the final package for you to have all requirements set.

Hi and welcome to devnet, You should rather check with the PTXdist guys, they are more likely to be able to help you with that error

Hi, That's a bit vague. You should add what option you used to cross-compile Qt , which version you are running etc.

Hi, That could be something you could suggest as a feature request on the "bug tracker":https://bugreports.qt.io/

It was definately my mistake. The screen did properly rotate after I fixed that. I'm surprised that I didn't have to rotate the resistive touch sense 180 as well (which I know can be done with an environment variable) - it just worked! The mouse not being rotate is a bit odd, but this is a non-issue in our application. Laszlo, thank you!