Mobile and Embedded

@debian logs?

Hi and welcome to devnet, You should add which version of Qt you are using as well as board name.

Hello Markus, Awesome! Thanks for pointing out these valuable resources... They indeed look like what I need in order to get the MX28 working with Yocto. I'll give them a try and report if I get them to work! Thanks again! :) JP

Yes, definitely it was work with Qt 5.4.2. In fact, I solved it on Java side. https://forum.qt.io/topic/57625/solved-keep-android-5-screen-on/2 But it does not work with QAndroidJniObject.

@Leonardo : thanks. @Kambiz : thanks

The virtualization is not the problem. If you can, change the cross-compiler version, for e.g. a 4.8

Hi, thank you for your response! I was able to install Qt on my PI2 using their apt-get process. It works great now! How can you find out which version of Raspbien is installed (jessie, etc)?

Hi! There is no general answer to such a question. It depends on your application: what did you use to implement it (Qt?)?

Thanks for the reply ,will certainly try the QtSpalshScreen thing when I get on the machine with the proper environment.I have noticed that when you start a new android project with Qt creator the project just runs fine. It is only when I import an external project in my instance of Qt Creator that the problem occurs.I decided to just learn a few basics on android native development ,deal with problems in the native environment ,and hopefuly it will be easier to deal with these on the Qt side of things.

Hi everyone! I created two wiki pages Qt Device Info and Qt Application Info. @marco_piccolino said: @shav if you want to contribute with more useful pieces of information, there is currently a trello board to plan out the portal's structure. Just post your Trello handle here and I will add you. https://trello.com/b/kCCQ7B9V/qtwiki-mobile-portal Thanks! You can add me with this handle @andrewshapovalov

Maybe this works. Button { id: button1 x: 40 y: 103 width: 120 height: 70 text: qsTr("1") activeFocusOnPress :true }

Thanks once again. Eskil Abrahamsen Blomfeldt ’s blog is good. I used one of his articles last week as a base for my first Qt Android Proof-of-Concept app - to send SMSes. The whole Qt multi-platform thing (on Android at least) is to some extent hamstrung by the fact that things that can be done on other mobile platforms via QML / C++ can (at the moment) only be done via java calls to Android’s java APIs. (e.g. send SMS, list contacts). On the other hand the GPS functionality was pretty much cut and paste from SailfishOS to Android, as Qt Positioning / Location is supported on both platforms. The existing SailfishOS app is mainly QML, a group of pagestack pages. For things that could not be done directly / easily with QML, I import C++ helper classes (e.g. SMSHelper, TorchHelper) which call the Qt / SailfishOS C++ APIs. I had assumed that in the ported Qt Android version of the app, each of the equivalent C++ helper classes would call its own dedicated java activity class. However if a Qt Android App can only have one activity class, then it looks like the C++ helper classes will have to share one central fatish java activity class. This java class would be the central “gateway” for all Android API calls from the various parts of my app.

any answer ?

@SGaist ok thanks i will try..