[HARD ERROR] Issue about UI of android 6.0
-
Hi @raven-worx !
this problem , i found here , is i cant load UI , Layout of Qt to my device .
But when i deploy to another device it work well (my device Q896s , android 6.0 )@TranVinhPhuc
i think you rather need to ask this question to the manufacturer of the device.
Since it's very likely that this is a highly customized Android ROM (incl. Linux kernel) -
@TranVinhPhuc
when you say: when i deploy to another device it work well
what other device are you talking about another android 6.0 device?Android 6.0 was released in 2015 and Qt 5.10 in 2018. Maybe there are some issues with drivers or something similar.
Can you run and deploy a simple bare-bone Ui-Porgramm. Maybe just a textfield saying "Ui is loaded"
Something along that line
@J.Hilk , i create a simple button have text "THIS IS " , but it just like this
-
@TranVinhPhuc
i think you rather need to ask this question to the manufacturer of the device.
Since it's very likely that this is a highly customized Android ROM (incl. Linux kernel)@raven-worx , i search many things , and they said it have relate to RPATH , RUNPATH ,..
-
@raven-worx , i search many things , and they said it have relate to RPATH , RUNPATH ,..
@TranVinhPhuc said in [HARD ERROR] Issue about UI of android 6.0:
they said it have relate to RPATH , RUNPATH ,..
what in detail?
-
Maybe it 's there !
https://stackoverflow.com/questions/33206409/unused-dt-entry-type-0x1d-arg/41900551#41900551i try to do following that but
it not work . maybe im fogort something :D -
Maybe it 's there !
https://stackoverflow.com/questions/33206409/unused-dt-entry-type-0x1d-arg/41900551#41900551i try to do following that but
it not work . maybe im fogort something :D@TranVinhPhuc
you can safely ignore these warnings regarding DT_FLAGS
This is already known and shouldnt have an impact on your appMaybe logcat logs may help here too:
// First clear the existing logcat messages adb logcat -c //Then reproduce the issue and save the logcat messages to a file adb logcat -d > logcat.txt
-
@TranVinhPhuc
you can safely ignore these warnings regarding DT_FLAGS
This is already known and shouldnt have an impact on your appMaybe logcat logs may help here too:
// First clear the existing logcat messages adb logcat -c //Then reproduce the issue and save the logcat messages to a file adb logcat -d > logcat.txt
@raven-worx !
I think this log just show about infomation of network state , it does not show about info of this error :D ... -
i try to create a simple example with button and text. i deploy to my device and ...
my code qml:
import QtQuick 2.10
import QtQuick.Window 2.10
import QtQuick.Controls 2.0
Window {
visible: true
width: 640
height: 480
title: qsTr("Hello World")
Button{
width: 500
height: 200
anchors.centerIn: parent
text: "THIS"}
}
-
@TranVinhPhuc
you can safely ignore these warnings regarding DT_FLAGS
This is already known and shouldnt have an impact on your appMaybe logcat logs may help here too:
// First clear the existing logcat messages adb logcat -c //Then reproduce the issue and save the logcat messages to a file adb logcat -d > logcat.txt
@raven-worx Do you have any ideas about my problem ? :D
-
@raven-worx Do you have any ideas about my problem ? :D
@TranVinhPhuc
yes, and i already said that.
you didnt answer my question in an earlier post -
@TranVinhPhuc
yes, and i already said that.
you didnt answer my question in an earlier post@raven-worx, i try using that logcat , and it just show information about network , wifi state ...
-
Hi All ! , i think i have same problem with this topic in Qt Forum
https://forum.qt.io/topic/72681/qt-quick-проект-не-запускается-на-эмуляторе-android -
@raven-worx, i try using that logcat , and it just show information about network , wifi state ...
@TranVinhPhuc
the one before that one.
(regarding what they said in detail)
Note: again the DT_FLAGS warnings can be ignored and do not relate to this problem.Do you have root access to the device?
-
@TranVinhPhuc
the one before that one.
(regarding what they said in detail)
Note: again the DT_FLAGS warnings can be ignored and do not relate to this problem.Do you have root access to the device?
@raven-worx said in [HARD ERROR] Issue about UI of android 6.0:
garding what they said in detai
my device was rooted
i using root to access to my device -
@raven-worx said in [HARD ERROR] Issue about UI of android 6.0:
garding what they said in detai
my device was rooted
i using root to access to my device@TranVinhPhuc
can you check how your partitions are mounted thenadb shell mount // or adb shell cat /proc/mounts
-
@TranVinhPhuc
can you check how your partitions are mounted thenadb shell mount // or adb shell cat /proc/mounts
@raven-worx !
after run command !
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,relatime,mode=750,gid=1000 0 0
tmpfs /mnt tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
tmpfs /sensors_cache tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/by-name/system /system ext4 ro,relatime,data=ordered 0 0
/dev/block/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/by-name/alog /logger ext4 rw,nosuid,nodev,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic,data=ordered 0 0
tmpfs /storage tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/by-name/bootloader /bootloader vfat rw,relatime,uid=1000,gid=1000,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=ascii,shortname=lower,errors=remount-ro 0 0
/dev/block/dm-0 /data ext4 rw,nosuid,nodev,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0 -
@raven-worx !
after run command !
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,relatime,mode=750,gid=1000 0 0
tmpfs /mnt tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
tmpfs /sensors_cache tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/by-name/system /system ext4 ro,relatime,data=ordered 0 0
/dev/block/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/by-name/alog /logger ext4 rw,nosuid,nodev,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic,data=ordered 0 0
tmpfs /storage tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/by-name/bootloader /bootloader vfat rw,relatime,uid=1000,gid=1000,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=ascii,shortname=lower,errors=remount-ro 0 0
/dev/block/dm-0 /data ext4 rw,nosuid,nodev,noatime,nomblk_io_submit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0@TranVinhPhuc said in [HARD ERROR] Issue about UI of android 6.0:
rootfs / rootfs ro,relatime 0 0
rootfs is mounted read-only (which is ok AFAIK) .. but this is what the error complains about.
Try the following commands:
- adb shell
- su
- mount -o remount,rw /
then run your app again and check if the error/issue is gone.
To mount it read-only again:
mount -o remount,ro /
-
i try following as u show me , but it not work , the UI can not load . it just have the blank background and rectangle like my button example at above
i downloaded some app of QT on CH Play and i can not load the UI of that app , same as my app :D ... what wrong now @@
this app of qt on chplay
https://play.google.com/store/apps/details?id=org.example.qt.quick.controls&hl=vi -
@TranVinhPhuc
i think you rather need to ask this question to the manufacturer of the device.
Since it's very likely that this is a highly customized Android ROM (incl. Linux kernel)@raven-worx !
the manufacturer of the device confirm with me that this device using standard android 6.0 version with root right . not customized.
I was checked about device , it is using arm 32bit processor. it have related with problem ? -
i try to reinstall the os of my deive to android 4.4 and it work well.. but i dont know how in the android 6.0 , the qt application cant work :D
May be it have problem with android 6.0 ?