Mobile and Embedded

That seems to be the solution, I found a map at http://doc-snapshot.qt-project.org/qt5-stable/qtsensors/compatmap.html that shows the available interfaces. I hope this will be part of 5.2!

Thanku @slerdzlo.. Thanku very much

Duplicate of this thread: http://qt-project.org/forums/viewthread/29763/

Edit: thanks portoist for pointing the right link, was too slow ;) When developping for an embedded device, you need a Qt version dedicated (or at least compiled) for this plateform. So when cross compiling, you have your "host" Qt version, here your MSVC2010 version, and the "device" Qt version, including all the binaries compiled for that precise platform (different compiler and/or build options). The "host" version is optional as it is only needed to be able to run your application on your windows for testing purposes. So basically you have two Qt directories/version. You usually have to build the "device" one yourself, which means: Extracting your sources to the new device Qt version directory (Optionnally modifying/creating the plateform specific mkspec file, containing compiler/linker path, etc.) In a terminal, running "configure" to well... configure your Qt version. Here you would use "-platform win32-msvc2010" and "-xplaform linux-qnx-something" as options. The "platform" option represents the host machine architecture, and the "xplatform" option represents the target machine architecture. The string used after each option is the name of a mkspecs directory (see QtBase/mkspecs directory in your Qt sources) Run qmake and make, which should end up with a valid Qt version built specifically for your target. Here is a link for further information to cross compile for linux embedded, from Linux (Qt 4.8, not 5). http://qt-project.org/doc/qt-4.8/qt-embedded-crosscompiling.html Note that to cross compile for a Linux embedded target, it is way easier to have a linux host. If this is something you can do, Ubuntu is really accessible and has a bunch of tools to do that kind of development.

[quote author="Moster" date="1373370824"]Have you only tried to use it on the emulator yet? Since its running fine on my real device Btw, opengl on the android emulator has never been of any use.[/quote] OK, problem solved. Not sure what changed, maybe the very action of writing this post made me to be more careful about what to do, but now after having it working in my device, it also works in the emulator. What I did change was using "Deploy" instead of "Run" in Qt Creator. Also, by running the emulator in the console, I found out this error message: @ emulator: ERROR: Could not load OpenGLES emulation library: libOpenglRender.so: cannot open shared object file: No such file or directory emulator: WARNING: Could not initialize OpenglES emulation, using software renderer. @ which happens because the path to libOpenglRender.so must be added to the LD_LIBRARY_PATH variable. I don't know it this makes any difference at all; if so, maybe it should be noted in the instructions given in the web.

There are pre-built Qt for iOS SDKs for Qt 4.8.5/5.0.2/5.10 available from http://www.mediator-software.com (as well as source code). These SDKs contain additional functionality and bug fixes (for iOS) that are not present in the official releases (yet).

Here is the source code. Can you let me know if there is a fix for this problem? main.cpp @ #include "widget.h" #include <QApplication> int main(int argc, char *argv[]) { QApplication a(argc, argv); Widget w; w.show(); return a.exec&#40;&#41;; } @ widget.h @ #ifndef WIDGET_H #define WIDGET_H #include <QLabel> class Widget : public QLabel { Q_OBJECT public: Widget(QWidget *parent = 0); ~Widget(); }; #endif // WIDGET_H @ widget.cpp @ #include "widget.h" Widget::Widget(QWidget *parent) : QLabel(parent) { setText(QString::fromUtf8("\u0627\u0644\u062C\u0632\u064A 700-1414")); } Widget::~Widget() { } @

Adding my Experience. I was having the similar problem, where QT Creator was always starting the simulator. The problem in my case was, Android Device – Settings – About Device – Android version - 4.1.2 But the settings for Project i.e. QTCreator - Projects – Android Run configuration – package configuration – mainfest – Android target SDK - API 17. I changed it to API 16. It started the debugging on Device. ( I had already set the device for "Developer options" and I had also installed the USB driver for windows for the device. )

Please don't post the same thread multiple times in different subforums "Duplicate":http://qt-project.org/forums/viewthread/29606/

Note that Google has a page where you can download all the default android artwork for free. (buttons, etc) http://developer.android.com/design/downloads/index.html

Thank you very much for all your help and useful information. I thank you for taking time out to answer my question Portoist.

I cannot provide you code, but you can start looking at the documentation: "QTcpServer":http://qt-project.org/doc/qt-4.8/qtcpserver.html and "QTcpSocket":http://qt-project.org/doc/qt-4.8/qtcpsocket.html

In such case you might also consider using Phonon: "Streaming Audio with Qt":http://www.developer.nokia.com/Community/Wiki/Streaming_Audio_with_Qt. In general streaming should be also possible with "QMediaPlayer from Qt Mobility but I have no idea does it work fine on Symbian":http://www.developer.nokia.com/Community/Discussion/showthread.php/209751-S-3-Stream-audio-via-WLAN-with-QMediaPlayer.