[Qt 5.1] Can't run apps on Android emulator/device



  • Hi!

    p. I've tried to run some simple apps (desktop and Qt Quick) with no success. It always happens the same. Black screen until the "Force closing" dialog pops up.

    p. I've tried all the options in "Deploy configurations" I've checked that the qt libraries deployed are the ARM version. Everything seems to compile and deploy fine (there's no error message).

    p. Everything I've read in this forum or in the Google Group didn't work for me.

    p. This is what I get from adb logcat: http://pastebin.com/6EpdML5M

    p. I am using what I think are the most recent versions of Qt Creator (2.7.2), Qt (5.1.0), Android NDK (android-ndk-r8e) and Android SDK (22.0.1).

    p. Any idea about what am I doing wrong?

    p. Thanks in advance.

    Regards,



  • What is your OS, ant and java version?

    Try this little test app
    http://www.mediafire.com/download/x2kydyzzlh6aymn/test.zip



  • p. Oh, I forgot that... I'm using Linux (Kubuntu 13.04). And Java...

    p. java version "1.7.0_21"
    OpenJDK Runtime Environment (IcedTea 2.3.9) (7u21-2.3.9-1ubuntu1)
    OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)

    p. I tried the test app from that link and the only difference I got it took longer to show the pop up dialog to force the closing of the app.



  • What is the device you are running it on?

    Btw, the log didnt really show any error. Are you sure its from the moment that the app crashes?



  • I'm using a HTC Tattoo. But using the emulator makes no difference. And the Android target is correct (I tried with both 9 and 10 API levels)... I mean, the targets I chose are less or equal than de the phone/emulator API level.

    Abou the logs, I ran the test app and just before the "Force closing" pops up this is what I get:

    I/Process ( 179): Sending signal. PID: 5570 SIG: 3
    I/dalvikvm( 5570): threadid=4: reacting to signal 3
    I/dalvikvm( 5570): Wrote stack traces to '/data/anr/traces.txt'
    I/Process ( 179): Sending signal. PID: 179 SIG: 3
    I/dalvikvm( 179): threadid=4: reacting to signal 3
    I/dalvikvm( 179): Wrote stack traces to '/data/anr/traces.txt'
    I/Process ( 179): Sending signal. PID: 282 SIG: 3
    I/dalvikvm( 282): threadid=4: reacting to signal 3
    I/dalvikvm( 282): Wrote stack traces to '/data/anr/traces.txt'
    I/Process ( 179): Sending signal. PID: 248 SIG: 3
    I/dalvikvm( 248): threadid=4: reacting to signal 3
    I/dalvikvm( 248): Wrote stack traces to '/data/anr/traces.txt'
    D/dalvikvm( 179): GC_EXPLICIT freed 757K, 46% free 6512K/11847K, external 1109K/1621K, paused 187ms
    E/ActivityManager( 179): ANR in org.qtproject.example.test (org.qtproject.example.test/org.qtproject.qt5.android.bindings.QtActivity)
    E/ActivityManager( 179): Reason: keyDispatchingTimedOut
    E/ActivityManager( 179): Load: 3.89 / 3.39 / 3.2
    E/ActivityManager( 179): CPU usage from 8931ms to 0ms ago:
    E/ActivityManager( 179): 64% 3/ksoftirqd/0: 0% user + 64% kernel
    E/ActivityManager( 179): 2.3% 314/com.google.process.gapps: 2.1% user + 0.2% kernel / faults: 209 minor 1 major
    E/ActivityManager( 179): 2% 179/system_server: 1.2% user + 0.7% kernel / faults: 11 minor 1 major
    E/ActivityManager( 179): 1% 129/akmd: 0.1% user + 0.8% kernel
    E/ActivityManager( 179): 0.6% 282/com.android.phone: 0.3% user + 0.3% kernel / faults: 10 minor
    E/ActivityManager( 179): 0.4% 4958/com.google.android.apps.maps:GoogleLocationService: 0.3% user + 0.1% kernel / faults: 55 minor
    E/ActivityManager( 179): 0% 123/rild: 0% user + 0% kernel / faults: 3 minor
    E/ActivityManager( 179): 0.3% 248/com.android.systemui: 0.2% user + 0.1% kernel / faults: 37 minor
    E/ActivityManager( 179): 0.2% 6/events/0: 0% user + 0.2% kernel
    E/ActivityManager( 179): 0.2% 5276/zygote: 0.2% user + 0% kernel / faults: 2 minor
    E/ActivityManager( 179): 0.2% 5607/com.google.android.apps.maps:LocationFriendService: 0.2% user + 0% kernel
    E/ActivityManager( 179): 0.1% 5467/com.google.android.gms: 0.1% user + 0% kernel / faults: 4 minor
    E/ActivityManager( 179): 0% 5578/com.google.android.gsf.login: 0% user + 0% kernel
    E/ActivityManager( 179): 0% 13337/tiwlan_wifi_wq: 0% user + 0% kernel
    E/ActivityManager( 179): 7.5% TOTAL: 4.9% user + 2.5% kernel
    E/ActivityManager( 179): CPU usage from 1202ms to 1763ms later:
    E/ActivityManager( 179): 20% 3/ksoftirqd/0: 0% user + 20% kernel
    E/ActivityManager( 179): 10% 179/system_server: 5.3% user + 5.3% kernel / faults: 1 minor
    E/ActivityManager( 179): 8.9% 210/InputDispatcher: 3.5% user + 5.3% kernel
    E/ActivityManager( 179): 1.7% 180/HeapWorker: 1.7% user + 0% kernel
    E/ActivityManager( 179): 1.7% 317/er$SensorThread: 1.7% user + 0% kernel
    E/ActivityManager( 179): 1.7% 624/GpsLocationProv: 0% user + 1.7% kernel
    E/ActivityManager( 179): 12% TOTAL: 5.3% user + 7.1% kernel



  • You cannot really rely on the android emulator. It sucks to be honest.
    Which android version is your HTC tattoo actually running on?

    Here is some precompiled version of my test app http://www.mediafire.com/download/68w3r7hq76f57y3/Test-debug.apk (target api level is 10, minimum for qt)

    I just want to know if the issue comes from your setup or your device



  • The HTC Tattoo is running Android 2.3.7 provided by Cyanogenmod 7.2.

    I tried that apk and there is no dialog popping up. The screen stays black, though.



  • Could it be because both processors (I tried a Samsung Galxy Mini with the same result) are ARMv6? I think I read somewhere that Qt needs an ARMv7 but I'm not sure.



  • Yes, it needs an armv7 cpu when you use the Qt installer. There was another thread yesterday where someone had a armv6 device.
    You can build Qt5 for older devices on your own, but I dont exactly know if it eventually works.

    https://groups.google.com/forum/#!topic/android-qt/wliNaQnOPyI
    Check the 2nd last post.


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.