Android App via debugger cashes updateNativeActivity() not found
-
Hello, I an on the way to my first Android app with Qt.
Buildings and Deploying seems to work. I get the following message in the output page:
E/ample.TestQMake: No implementation found for boolean org.qtproject.qt.android.QtNative.updateNativeActivity() (tried Java_org_qtproject_qt_android_QtNative_updateNativeActivity and Java_org_qtproject_qt_android_QtNative_updateNativeActivity__) - is the library loaded, e.g. System.loadLibrary? E/ashmem : Pinning is deprecated since Android Q. Please use trim or other methods.
I use windows Qt 9.6.0 Clang x86_64.
It is the simple QWidget App created from the New Project Wizzard of the creator.
Only a MDI window. Can I run such apps as test on Andriod or must I make something with Activitys ?Here is the full output:
I/ample.TestQMake: Late-enabling -Xcheck:jni I/ample.TestQMake: Using CollectorTypeCMC GC. W/ample.TestQMake: Unexpected CPU variant for x86: x86_64. W/ample.TestQMake: Known variants: atom, sandybridge, silvermont, goldmont, goldmont-plus, goldmont-without-sha-xsaves, tremont, kabylake, alderlake, default D/nativeloader: Load libframework-connectivity-tiramisu-jni.so using APEX ns com_android_tethering for caller /apex/com.android.tethering/javalib/framework-connectivity-t.jar: ok D/nativeloader: Configuring clns-9 for other apk /data/app/~~hP84UzBmRXWCWEUhmprqNQ==/org.qtproject.example.TestQMake-6ifFkwJbpUsenwhhUVe83Q==/base.apk. target_sdk_version=35, uses_libraries=, library_path=/data/app/~~hP84UzBmRXWCWEUhmprqNQ==/org.qtproject.example.TestQMake-6ifFkwJbpUsenwhhUVe83Q==/lib/x86_64:/data/app/~~hP84UzBmRXWCWEUhmprqNQ==/org.qtproject.example.TestQMake-6ifFkwJbpUsenwhhUVe83Q==/base.apk!/lib/x86_64, permitted_path=/data:/mnt/expand:/data/user/0/org.qtproject.example.TestQMake D/CompatChangeReporter: Compat change id reported: 202956589; UID 10217; state: ENABLED I/ample.TestQMake: AssetManager2(0x73a87ae6e638) locale list changing from [] to [en-US] V/GraphicsEnvironment: Currently set values for: V/GraphicsEnvironment: angle_gl_driver_selection_pkgs=[] V/GraphicsEnvironment: angle_gl_driver_selection_values=[] V/GraphicsEnvironment: org.qtproject.example.TestQMake is not listed in per-application setting V/GraphicsEnvironment: ANGLE allowlist from config: V/GraphicsEnvironment: org.qtproject.example.TestQMake is not listed in ANGLE allowlist or settings, returning default V/GraphicsEnvironment: Neither updatable production driver nor prerelease driver is supported. I/DisplayManager: Choreographer implicitly registered for the refresh rate. I/ample.TestQMake: AssetManager2(0x73a87ae675b8) locale list changing from [] to [en-US] E/ample.TestQMake: No implementation found for boolean org.qtproject.qt.android.QtNative.updateNativeActivity() (tried Java_org_qtproject_qt_android_QtNative_updateNativeActivity and Java_org_qtproject_qt_android_QtNative_updateNativeActivity__) - is the library loaded, e.g. System.loadLibrary? E/ashmem : Pinning is deprecated since Android Q. Please use trim or other methods. I/EGL_emulation: Opening libGLESv1_CM_emulation.so I/EGL_emulation: Opening libGLESv2_emulation.so W/HWUI : Failed to choose config with EGL_SWAP_BEHAVIOR_PRESERVED, retrying without... W/HWUI : Failed to initialize 101010-2 format, error = EGL_SUCCESS Art: App Profiles gelöscht. D/nativeloader: Load /data/app/~~hP84UzBmRXWCWEUhmprqNQ==/org.qtproject.example.TestQMake-6ifFkwJbpUsenwhhUVe83Q==/base.apk!/lib/x86_64/libc++_shared.so using class loader ns clns-9 (caller=/data/app/~~hP84UzBmRXWCWEUhmprqNQ==/org.qtproject.example.TestQMake-6ifFkwJbpUsenwhhUVe83Q==/base.apk): ok D/nativeloader: Load /data/app/~~hP84UzBmRXWCWEUhmprqNQ==/org.qtproject.example.TestQMake-6ifFkwJbpUsenwhhUVe83Q==/base.apk!/lib/x86_64/libQt6Core_x86_64.so using class loader ns clns-9 (caller=/data/app/~~hP84UzBmRXWCWEUhmprqNQ==/org.qtproject.example.TestQMake-6ifFkwJbpUsenwhhUVe83Q==/base.apk): ok I/QtCore : Start D/nativeloader: Load /data/app/~~hP84UzBmRXWCWEUhmprqNQ==/org.qtproject.example.TestQMake-6ifFkwJbpUsenwhhUVe83Q==/base.apk!/lib/x86_64/libQt6Gui_x86_64.so using class loader ns clns-9 (caller=/data/app/~~hP84UzBmRXWCWEUhmprqNQ==/org.qtproject.example.TestQMake-6ifFkwJbpUsenwhhUVe83Q==/base.apk): ok D/nativeloader: Load /data/app/~~hP84UzBmRXWCWEUhmprqNQ==/org.qtproject.example.TestQMake-6ifFkwJbpUsenwhhUVe83Q==/base.apk!/lib/x86_64/libQt6Widgets_x86_64.so using class loader ns clns-9 (caller=/data/app/~~hP84UzBmRXWCWEUhmprqNQ==/org.qtproject.example.TestQMake-6ifFkwJbpUsenwhhUVe83Q==/base.apk): ok D/nativeloader: Load /data/app/~~hP84UzBmRXWCWEUhmprqNQ==/org.qtproject.example.TestQMake-6ifFkwJbpUsenwhhUVe83Q==/base.apk!/lib/x86_64/libQt6Svg_x86_64.so using class loader ns clns-9 (caller=/data/app/~~hP84UzBmRXWCWEUhmprqNQ==/org.qtproject.example.TestQMake-6ifFkwJbpUsenwhhUVe83Q==/base.apk): ok D/nativeloader: Load /data/app/~~hP84UzBmRXWCWEUhmprqNQ==/org.qtproject.example.TestQMake-6ifFkwJbpUsenwhhUVe83Q==/base.apk!/lib/x86_64/libplugins_platforms_qtforandroid_x86_64.so using class loader ns clns-9 (caller=/data/app/~~hP84UzBmRXWCWEUhmprqNQ==/org.qtproject.example.TestQMake-6ifFkwJbpUsenwhhUVe83Q==/base.apk): ok I/Qt : qt started D/nativeloader: Load /data/app/~~hP84UzBmRXWCWEUhmprqNQ==/org.qtproject.example.TestQMake-6ifFkwJbpUsenwhhUVe83Q==/base.apk!/lib/x86_64/libTestQMake_x86_64.so using class loader ns clns-9 (caller=/data/app/~~hP84UzBmRXWCWEUhmprqNQ==/org.qtproject.example.TestQMake-6ifFkwJbpUsenwhhUVe83Q==/base.apk): ok D/CompatChangeReporter: Compat change id reported: 352594277; UID 10217; state: ENABLED D/CompatChangeReporter: Compat change id reported: 279646685; UID 10217; state: ENABLED D/CompatChangeReporter: Compat change id reported: 309578419; UID 10217; state: ENABLED D/DesktopModeFlags: Toggle override initialized to: OVERRIDE_UNSET W/HWUI : Image decoding logging dropped! W/HWUI : Image decoding logging dropped! W/HWUI : Image decoding logging dropped! D/CompatChangeReporter: Compat change id reported: 63938206; UID 10217; state: ENABLED D/CompatChangeReporter: Compat change id reported: 349153669; UID 10217; state: ENABLED W/HWUI : Unknown dataspace 0 I/ample.TestQMake: AssetManager2(0x73a87ae73db8) locale list changing from [] to [en-US] I/ample.TestQMake: AssetManager2(0x73a87ae6d9b8) locale list changing from [] to [en-US] I/ample.TestQMake: AssetManager2(0x73a87ae72198) locale list changing from [] to [en-US] D/InsetsController: hide(ime(), fromIme=false) I/ImeTracker: org.qtproject.example.TestQMake:51deb493: onCancelled at PHASE_CLIENT_ALREADY_HIDDEN W/Qt A11Y : Unable to initialize the accessibility delegate with a null layout W/HWUI : Image decoding logging dropped! I/ImeTracker: org.qtproject.example.TestQMake:e540658a: onRequestHide at ORIGIN_CLIENT reason HIDE_SOFT_INPUT fromUser false D/InsetsController: hide(ime(), fromIme=false) I/ImeTracker: org.qtproject.example.TestQMake:e540658a: onCancelled at PHASE_CLIENT_ALREADY_HIDDEN Art: App Profiles kompiliert. I/ample.TestQMake: Compiler allocated 5042KB to compile void android.view.ViewRootImpl.performTraversals() D/ProfileInstaller: Installing profile for org.qtproject.example.TestQMake
-
Hi
first, QtQuick is recommended for Android and iOS over QtWidget which isn't optimal for those platforms.
I have serious doubt about MDI window on Android platform (iOS also). Android is not intended to open multiple windows at once and I just wonder whether windows inside window could be the actual cause of your issue.
I haven't made much mobile development with Qt but as far as I remember, android simulator has to be configured in 32 bits instead of 64 on older android versions, which might explain the "unexpected cpu variant for x86" message ?@Andy314 said in Android App via debugger cashes updateNativeActivity() not found:
Can I run such apps as test on Andriod or must I make something with Activitys ?
No, you do NOT need to write any Activity related code to create an app for Android.
-
Hi
first, QtQuick is recommended for Android and iOS over QtWidget which isn't optimal for those platforms.
I have serious doubt about MDI window on Android platform (iOS also). Android is not intended to open multiple windows at once and I just wonder whether windows inside window could be the actual cause of your issue.
I haven't made much mobile development with Qt but as far as I remember, android simulator has to be configured in 32 bits instead of 64 on older android versions, which might explain the "unexpected cpu variant for x86" message ?@Andy314 said in Android App via debugger cashes updateNativeActivity() not found:
Can I run such apps as test on Andriod or must I make something with Activitys ?
No, you do NOT need to write any Activity related code to create an app for Android.
@CassD said in Android App via debugger cashes updateNativeActivity() not found:
Hi
first, QtQuick is recommended for Android and iOS over QtWidget which isn't optimal for those platforms.
I have serious doubt about MDI window on Android platform (iOS also). Android is not intended to open multiple windows at once and I just wonder whether windows inside window could be the actual cause of your issue.
I haven't made much mobile development with Qt but as far as I remember, android simulator has to be configured in 32 bits instead of 64 on older android versions, which might explain the "unexpected cpu variant for x86" message ?Yes you are right, MDI makes no sense here. I have a tablet app (with widgets!) that runs on a windows tablet very well. Now, I want to transform it to an Andriod app.
The current app ist only for testing, as the simplest gui app the creator creates automatically.The hint about the 32 is interesting, I will I will investigate it further, before I answer.
-
@CassD said in Android App via debugger cashes updateNativeActivity() not found:
Hi
first, QtQuick is recommended for Android and iOS over QtWidget which isn't optimal for those platforms.
I have serious doubt about MDI window on Android platform (iOS also). Android is not intended to open multiple windows at once and I just wonder whether windows inside window could be the actual cause of your issue.
I haven't made much mobile development with Qt but as far as I remember, android simulator has to be configured in 32 bits instead of 64 on older android versions, which might explain the "unexpected cpu variant for x86" message ?Yes you are right, MDI makes no sense here. I have a tablet app (with widgets!) that runs on a windows tablet very well. Now, I want to transform it to an Andriod app.
The current app ist only for testing, as the simplest gui app the creator creates automatically.The hint about the 32 is interesting, I will I will investigate it further, before I answer.
@Andy314 said in Android App via debugger cashes updateNativeActivity() not found:
@CassD said in Android App via debugger cashes updateNativeActivity() not found:
I haven't made much mobile development with Qt but as far as I remember, android simulator has to be configured in 32 bits instead of 64 on older android versions, which might explain the "unexpected cpu variant for x86" message ?
The hint about the 32 is interesting, I will I will investigate it further, before I answer.
The CPU hint seem to be no the problem. Its only a warning I found in the net. Because I take a newer Android is all 64 bit.
-
@CassD said in Android App via debugger cashes updateNativeActivity() not found:
Hi
first, QtQuick is recommended for Android and iOS over QtWidget which isn't optimal for those platforms.
I have serious doubt about MDI window on Android platform (iOS also). Android is not intended to open multiple windows at once and I just wonder whether windows inside window could be the actual cause of your issue.
I haven't made much mobile development with Qt but as far as I remember, android simulator has to be configured in 32 bits instead of 64 on older android versions, which might explain the "unexpected cpu variant for x86" message ?Yes you are right, MDI makes no sense here. I have a tablet app (with widgets!) that runs on a windows tablet very well. Now, I want to transform it to an Andriod app.
The current app ist only for testing, as the simplest gui app the creator creates automatically.The hint about the 32 is interesting, I will I will investigate it further, before I answer.
@Andy314 said in Android App via debugger cashes updateNativeActivity() not found:
@CassD said in Android App via debugger cashes updateNativeActivity() not found:
I have serious doubt about MDI window on Android platform (iOS also). Android is not intended to open multiple windows at once and I just wonder whether windows inside window could be the actual cause of your issue.
It is not really correct, what I wrote, that it is my first Android app - its my first I really will use.
When I began with QT - nearly 7-8 years ago - I had a large Windows Desktop Programm and made and try only for testing to let in run in Android. After about 3 day it worked and I was very impressed of it, how easy it was and how similar the gui looks (and in my favourite language C++).
Indeed I had a MDI Main Windows with menü etc. All was very small, so could not work by touch with but with the mouse all works like a normal windows desktop app. MDI Chield creates Qt in its onw way, that must not be OS-Windows, it think.