Mobile and Embedded

we can change the rgb values of each point in a cloud

Hi, NDK-r18b is supported since Qt 5.12. You can either use an older version of the NDK like suggested in the Android getting started document or update Qt.

Yah i got solution for this. i.e arranging roles in order how database tables are. Thank you.

after hours of searching and testing various suggestions, we found that androiddeployqt doesn't search in libraries for qml imports, seems it just searches the directory of app's standalone.pro file. so a some hackish suggest was to make a symlink to "../editorlib/qml" and the other one was to make a qml file in app's standalone.pro directory and import all qml modules in that file. someting like: @ import QtQuick 2.5 import QtQuick.Window 2.2 import QtQuick.Layouts 1.2 import QtQuick.Controls 1.4 import QtQuick.Controls.Styles 1.4 Page{} @ we chose the first one and made the symlink. for having necessary libs in android apk adding next line to standalone.pro solved missing dependant libs in android. @ QT += qml quick widgets 3dcore 3drender 3dextras 3dinput 3dlogic 3dquick 3drender-private core @ and the app ran on android like a charm. also bonus point is that there is no need to create android template in project, no manifest editing or etc..

@GuYan QtCreator requires a GDB debugger with Python support enabled. As you are cross- and remote debugging, you need: gdbserver running on your ARM target A cross gdb for ARM target archicture with Python support running on your PC Usually, these gdb's are called arm-angstrom-linux-gnueabi-gdb or similar. Note that you can also debug from within this gdb, or use the DDD debugger GUI if you can't get it working in QtCreator.

Yes, of course. But I'm just don't tried nothing yet. :)

I had the same problem. I solved it by going to Projects->Build Environment and changing ANDROID_NDK_PLATFORM from android-16 to android-28 and then "Build->Run qmake" and Build.

@koahnig sorry I missed the issue regarding QT_QPA_EGLFS_PHYSICAL_* message. You may want to take a look at this post

Found it: https://github.com/qt/qtbase/blob/5.12/src/corelib/global/qlogging.cpp Specifically, I needed to set application name in QCoreApplication.

No. How I can "install the driver from <ANDROID_SDK_ROOT>/extras/google/usb_driver"? There is no .exe file in the "/extras/google/usb_drive" .

@dheerendra That is the content found in an archive dowload from November 2017. I have just checked the qmake.conf is from 2. October 2017 [image: 8945bd90-f559-459a-929e-56db98441c65.png] Therefore no changes from my side.

@MrYang Hi and welcome to devnet forum When find or file a bug report, please make sure to post a link here. This allows others to vote through the link increasing the chances that the bugs are treated and solved.

Sorry for necro-posting on an old thread but it might be useful for others. To the best of my knowledge and from past experience, VNC requires the X windows system and Raspbian Lite does not have this installed. Raspbian PIXEL = yes, you can VNC into it Raspbian LITE = no VNC since there's no X windows (It's possible that one of the Qt installs completely scaffolds X11 if it's not there; I wouldn't know.)

@bigjake I haven't worked with Qt yet (waiting for my license to start) but I have worked with the Raspberry Pi 3B + 2.8" capacitive/resistive touchscreens as sold by Adafruit. Properly adjusting orientation for both display/touch at the same time for both console-based and X windows—based apps is rather difficult. Here is a conversation I just had with Ada herself on the subject, which might be useful.

@Aleksey_K-0 you may want to take a look at QAndroidJniObject class, and also check this question in stackoverflow

@Aleksey_K-0 yep. store at app data location

@metaDom converted Your result to UUID: QCryptographicHash hash(QCryptographicHash::Sha1); hash.addData(getAndroidID().toLocal8Bit()); auto id = QUuid::fromRfc4122(hash.result().left(16));

To whoever else comes across this thread, here's the official bug-report regarding this issue: https://bugreports.qt.io/browse/QTCREATORBUG-20379