Ok, how about this - Anybody know a way I can add code or set env to enable rotation, (portrait/landscape, or...). As it is, the qt apps don't respond to phone sensors, but are fixes...

I have found a solution! I did multiple things:

Used newer template files for Android from Qt/6.2.3/android_arm64_v8a/src/android/templates/ (res/values/libs.xml - overwritten, build.gradle - overwritten, AndroidManifest.xml - copy and paste and then edited the content and added the missing things from my old one) Used newer gradle files from /Qt/6.2.3/android_arm64_v8a/src/3rdparty/gradle/gradle/wrapper/ - overwritten Upgrade of Qt Creator, Qt 6.2.2 -> 6.2.3, Android SDK, Android NDK

My current Manifest:

<?xml version="1.0"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android" package="org.dontpanic" android:installLocation="auto" android:versionCode="20000" android:versionName="2.0"> <uses-sdk android:minSdkVersion="23" android:targetSdkVersion="31"/> <!-- The comment below will be replaced with dependencies permissions upon deployment. Remove the comment if you do not require these default permissions. --> <!-- %%INSERT_PERMISSIONS --> <!-- The comment below will be replaced with dependencies permissions upon deployment. Remove the comment if you do not require these default features. --> <!-- %%INSERT_FEATURES --> <supports-screens android:anyDensity="true" android:largeScreens="true" android:normalScreens="true" android:smallScreens="true" /> <application android:name="org.qtproject.qt.android.bindings.QtApplication" android:extractNativeLibs="true" android:hardwareAccelerated="true" android:label="@string/app_name" android:icon="@drawable/icon" android:requestLegacyExternalStorage="true"> <activity android:name="org.qtproject.qt.android.bindings.QtActivity" android:configChanges="orientation|uiMode|screenLayout|screenSize|smallestScreenSize|layoutDirection|locale|fontScale|keyboard|keyboardHidden|navigation|mcc|mnc|density" android:label="@string/app_name" android:launchMode="singleTop" android:screenOrientation="portrait"> <intent-filter> <action android:name="android.intent.action.MAIN"/> <category android:name="android.intent.category.LAUNCHER"/> </intent-filter> <!-- Application arguments --> <meta-data android:name="android.app.arguments" android:value="-- %%INSERT_APP_ARGUMENTS%% --" /> <!-- Application arguments --> <meta-data android:name="android.app.lib_name" android:value="-- %%INSERT_APP_LIB_NAME%% --" /> <!-- Background running --> <!-- Warning: changing this value to true may cause unexpected crashes if the application still try to draw after "applicationStateChanged(Qt::ApplicationSuspended)" signal is sent! --> <meta-data android:name="android.app.background_running" android:value="false" /> <!-- Background running --> <!-- extract android style --> <!-- available android:values : * default - In most cases this will be the same as "full", but it can also be * something else if needed, e.g., for compatibility reasons * full - useful QWidget & Quick Controls 1 apps * minimal - useful for Quick Controls 2 apps, it is much faster than "full" * none - useful for apps that don't use any of the above Qt modules --> <meta-data android:name="android.app.extract_android_style" android:value="minimal" /> <!-- extract android style --> </activity> <service android:name="org.dontpanic.NotificationService"> <meta-data android:name="android.app.lib_name" android:value="-- %%INSERT_APP_LIB_NAME%% --"/> </service> <receiver android:name="org.dontpanic.NotificationReceiver" android:enabled="true" android:exported="true"/> <receiver android:name="org.dontpanic.RebootReceiver" android:enabled="true" android:exported="true"> <intent-filter> <action android:name="android.intent.action.BOOT"/> <action android:name="android.intent.action.LOCKED_BOOT_COMPLETED"/> <action android:name="android.intent.action.BOOT_COMPLETED"/> <action android:name="android.intent.action.QUICKBOOT_POWERON"/> <action android:name="android.intent.action.REBOOT"/> <action android:name="com.htc.intent.action.QUICKBOOT_POWERON"/> <action android:name="android.intent.action.USER_PRESENT"/> <category android:name="android.intent.category.DEFAULT"/> </intent-filter> </receiver> </application> <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/> <uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED"/> </manifest>

@ekkescorner Assam Boudjelthia has done a great work on this and now prepared cherry-picks for 5.15 🙂
see QTBUG-98974
can someone help and test ?

@Phips04 Your welcome

@JonB yes I tried but its giving message that the file is not found.

@SGaist Hey so the reference problem is solved. Seems like the file can be opened, the player works but there is no sound :-/. I'll probably open another thread for this issue. Thanks for the help again!
EDIT: Or maybe it's working :D. On other devices I got a report that the sound is OK. Will investigate that further!

you can use CrossQFile. CrossQFile is a QFile that supports android uri.
https://github.com/mahdize/CrossQFile

@Mehmet-Yilmaz said in UI/UX Mockup tool:

Can I use Qt design as a UI/UX tool or I need to buy an external tool

Well, nobody beside yourself can answer THAT question.

Regards

Hi,

Since you are using V-Play, you might want to bring that question to their forum.

AFAIK, no. But you can check that yourself.

@ekkescorner Hi,
Well, when we develop a mobile app with Qt for Android and iOS (we'll use Start-Up Plan), if we sell the app a customer, Can this customer publish the app on Google Play and AppStore?

Hi,

At V-Play, we have an example on how to achieve this in our Twitter sample app. Check out the screenshots: (Sorry, didn't have time to record an animation ;) )

0_1499349566897_vplay-collapse1.png

1_1499349566898_vplay-collapse2.png

2_1499349566898_vplay-collapse3.png

This sample needs the V-Play SDK to run, which might be useful if you are into app development.
If you don't want to install a third-party SDK, you still might be able to get some inspiration from the sample app.

Cheers,
Lorenz

@piJar
stupid question (just to make sure): you did connect with the debugger right?

@lukas_kosinski would also be great to have more codes - esp Code39 and EAN-Barcodes are essential for my apps

@vladstelmahovsky Thanks. This solves the issue! Shame on me for not reading the documentation more thoroughly.

@Exotic_Devel, acredito que não seja culpa do open source, por que:

Qt usa duas licenças, a Comercial e a LGPL. A licença LGPL diz que:

o. Em caso de ligação dinâmica, então o teu desenvolvimento (o código que você desenvolver) é "trabalho que usa a biblioteca". Sendo assim, o código que você desenvolver apenas usa as bibliotecas Qt, então seu código pode ser proprietário.

o. Em caso de vinculação estática da biblioteca, o próprio aplicativo é "trabalho que faz parte da biblioteca". Qualquer ligação estática com uma biblioteca LGPL, obriga a fornecer o código-fonte do aplicativo para o usuário sob a LGPL.

Então do meu ponto de vista, se existe um culpado, é a Apple! por não permitir vinculação dinâmica! Hora, bastava permitir que resolveria a questão: Quem estivesse sobre licença comercial, faria o vinculo estático; Quem estivesse utilizando alguma biblioteca open, então faria o vinculo dinâmico.

Não é novidade, isso só reafirma que a Apple não é muito edepta do opensource. :-)