Failure: Unable to Deploy and run package on device

ahsan737

I am using Qt 5.12.3. Trying to build a simple Bluetooth communication app for Android.
The build is completed successfully. but I am facing error when Qt tries to deploy the app on the device.

I Zygote  : ForkAndSpecializeCommon: fork is finished, pid=0
W Zygote  : mz_is_rooted false
W main    : type=1400 audit(0.0:1514415): avc: denied { create } for name="cgroup.procs" scontext=u:r:zygote:s0 tcontext=u:object_r:cgroup:s0 tclass=file permissive=0
I Zygote  : ForkAndSpecializeCommon: Beginning of SetGids
I Zygote  : ForkAndSpecializeCommon: End of SetGids
I zygote  : Late-enabling -Xcheck:jni
W zygote  : Using default instruction set features for ARM CPU variant (cortex-a9) using conservative defaults
W System  : ClassLoader referenced unknown path:
I FlymeFontsHelper: UserId == 0
I QtCore  : Start
W linker  : "/data/app/org.qtproject.example.BTHC05-hwskKYzDPYkGkbiwNaGieA==/lib/arm/libQt5AndroidExtras.so" has unsupported flags DT_FLAGS_1=0x80
W linker  : "/data/app/org.qtproject.example.BTHC05-hwskKYzDPYkGkbiwNaGieA==/lib/arm/libQt5Bluetooth.so" has unsupported flags DT_FLAGS_1=0x80
W linker  : "/data/app/org.qtproject.example.BTHC05-hwskKYzDPYkGkbiwNaGieA==/lib/arm/libQt5Gui.so" has unsupported flags DT_FLAGS_1=0x80
W linker  : "/data/app/org.qtproject.example.BTHC05-hwskKYzDPYkGkbiwNaGieA==/lib/arm/libQt5Widgets.so" has unsupported flags DT_FLAGS_1=0x80
W linker  : "/data/data/org.qtproject.example.BTHC05/qt-reserved-files/plugins/platforms/android/libqtforandroid.so" has unsupported flags DT_FLAGS_1=0x80
I Qt      : qt started
I zygote  : Do partial code cache collection, code=29KB, data=29KB
I zygote  : After code cache collection, code=29KB, data=29KB
I zygote  : Increasing code cache capacity to 128KB
I zygote  : Do partial code cache collection, code=52KB, data=56KB
I zygote  : After code cache collection, code=52KB, data=56KB
I zygote  : Increasing code cache capacity to 256KB
E linker  : normalize_path - invalid input: "C", the input path should be absolute
W linker  : Warning: unable to normalize "C"
E linker  : normalize_path - invalid input: "C", the input path should be absolute
W linker  : Warning: unable to normalize "C"
I Adreno  : QUALCOMM build                   : 85a6576, Ie95bd5cb08
I Adreno  : Build Date                       : 07/17/18
I Adreno  : OpenGL ES Shader Compiler Version: EV031.23.02.01
I Adreno  : Local Branch                     : mybranch34750041
I Adreno  : Remote Branch                    : quic/gfx-adreno.lnx.1.0.r32-rel
I Adreno  : Remote Branch                    : NONE
I Adreno  : Reconstruct Branch               : NOTHING
I Adreno  : PFP: 0x016ee164, ME: 0x00000000
I zygote  : android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasWideColorDisplay retrieved: 0
I OpenGLRenderer: Initialized EGL, version 1.4
W ResourceType: Failure getting entry for 0x010400df (t=3 e=223) (error -75)
E SpannableStringBuilder: SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
W libBTHC05.so: qt.bluetooth.android: ACCESS_COARSE|FINE_LOCATION permission available
I BluetoothAdapter: startDiscovery
F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x730085 in tid 8953 (qtMainLoopThrea), pid 8930 (.example.BTHC05)


"org.qtproject.example.BTHC05" died.

J.Hilk

@ahsan737

From the log I can see you added Bluetooth permissions to your manifest, did you also add
android:name="android.permission.ACCESS_COARSE_LOCATION"/> ?

ahsan737

@J.Hilk yes it has included "android.permission.ACCESS_COARSE_LOCATION". But I haven't made changes in the android manifest, it is default version being generated by Qt.

J.Hilk

@ahsan737 alight

Well the app actually deploys correctly and starts and your bluetooth instance is scanning for devices.

So a good point in time to enable remote debugging on your device and do just that.

Start a debug build (with the debugger attached of course), let it crash and inspect the backtrace

ahsan737

@J.Hilk thank you, that sounds so technical. Actually, I am a beginner so I do not have a deep understanding of it. And yesterday it was all working fine.