Mobile and Embedded

@cerr change elf.My1AlertSignal().emit(req.level) to self.My1AlertSignal.emit(req.level). Don't add unnecessary parentheses

i installed SDK via android studio. should i install sdk and ndk manually please provide version

The Problem solved itself after closing and opening again. It looks like I have not applied the change from java 11 to java 8 directory.

@dxvx said in Init new Android project: when qtcreator tries to create the gradle and android template, it fails because there is no template in the android SDK Possibly Google changed the layout again. Sorry, I don't know how to fix this, last time I tried creating templates it worked fine. Make sure you're using the newest Qt Creator and if it persists, please report a bug on Qt bug tracker.

Hi, You may have to use the Qt 4 phonon module.

After some analysis it turned out that assets are updated correctly. The fault was in QML cache - it was preserving old data between application runs and even versions. Our current solution is to clear application cache in every startup.

@Cleiton-Bueno Thanks

@cano said in Not able to compile "qgroundcontrol" on windows 64 bit: Project ERROR: Cannot run target compiler ‘C:\Users\Neha\AppData\Local\Android\Sdk\ndk\21.0.6113669/toolchains/arm-linux-androideabi-4.9/prebuilt/windows-x86_64/bin/arm-linux-androideabi-g++’. Output: Two things here, clearly the compiler cannot run and you didn't paste the whole error message qt 5.14.2 From the link you posted, instructions call for using Qt 5.7.1 "Make sure to install Qt version 5.7.1 NOT 5.4.x, 5.6.x, 5.8.x, etc." I'm not sure if that will make a difference...

I believe that the QPA closest to qws would be linuxfb or EGLFS.

Hi and welcome to devnet, That's something you should bring the authors of that module. They are going to be more likely able to help you in your situation.

@pixbyte I have to build my C++ with Android Studio with the needed ABI Right then import this *.so LIB into QT Yes, copy them to the proper location (depending on the ABI platform) in your Qt project folder structure, so Qt Creator finds it and deploys to the Android device without any issue, i.e.: my-qt-project/android/libs/armeabi-v7a/ no need to create any JNI interface, this is all done by QT I don't think so. I guess you still need to go like you're currently doing.

I don't know if there's another way but yours surely worked for me. Thanks a lot!

Ok, the main sector is definitely the jre delivered with Android Studio. Thanks you for your help guys. It works now like a charme.

Hi @KroMignon Thank you for you help! It really sorted out my issue completely. I install tools + plus i had to move JDK 8 (from 11) [image: 6dc703a2-98c2-4cb3-9ca0-6fca98b9cf3d.png] The single one issue i notices during building is Found corrupted package.xml at C:\Users\user\AppData\Local\Android\sdk\lldb\3.1\package.xml However building project finished successfully: BUILD SUCCESSFUL in 3m 29s 25 actionable tasks: 25 executed Package.xml looks like <?xml version="1.0" encoding="UTF-8" standalone="yes"?><ns2:repository xmlns:ns2="http://schemas.android.com/repository/android/common/01" xmlns:ns3="http://schemas.android.com/repository/android/generic/01" xmlns:ns4="http://schemas.android.com/sdk/android/repo/addon2/01" xmlns:ns5="http://schemas.android.com/sdk/android/repo/repository2/01" xmlns:ns6="http://schemas.android.com/sdk/android/repo/sys-img2/01"><license id="android-sdk-license" type="text"> ---------Stacktrace------ org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 460; XML document structures must start and end within the same entity. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203) at That looks strange since xml looks correct.

Hi @Nikten The same thing here:( Did you find a way?

Hi @SGaist , if load it directly the video plays on mute.