xiaomi-lavender: adapt Halium 9.0 support
This should be merged after !1144 (closed).
Image is available for testing here: https://github.com/ubports-lavender/ubports-ci/releases/tag/lavender-20200527
Merge request reports
Activity
mentioned in merge request !1144 (closed)
By Danct12 on 2020-04-21T01:27:30
- Resolved by Administrator
What does this screenshot tell me? I have the same FPS on X with framebuffer backend, even more:
(except android and hybris EGL_* things)
P.S. I can't switch my head to downstream kernel right now, but I'll try to test this (together with 1144 some time this week)
By Alexey Min on 2020-04-23T03:36:37
Edited by Administrator
added category::device + 1 deleted label
added 31 commits
-
8f26991a...f45890b6 - 28 commits from branch
postmarketOS:master
- 101b39fb - device-xiaomi-lavender: adapt Halium to the port
- 0258fb9a - linux-xiaomi-lavender: Halium-friendly defconfig
- f2f88a76 - device-xiaomi-lavender: hybris-ized xorg server config
By Danct12 on 2020-05-01T18:47:16
Toggle commit list-
8f26991a...f45890b6 - 28 commits from branch
added 15 commits
-
f2f88a76...38de3498 - 12 commits from branch
postmarketOS:master
- eb5dbe6a - device-xiaomi-lavender: adapt Halium to the port
- 5d9bfd13 - linux-xiaomi-lavender: Halium-friendly defconfig
- 949ab6db - device-xiaomi-lavender: hybris-ized xorg server config
By Danct12 on 2020-05-03T21:31:22
Toggle commit list-
f2f88a76...38de3498 - 12 commits from branch
81 ACTION=="add", KERNEL=="ion", OWNER="aid_system", GROUP="aid_system", MODE="0664" 82 ACTION=="add", KERNEL=="rtc0", OWNER="aid_system", GROUP="aid_system", MODE="0660" 83 ACTION=="add", KERNEL=="smd0", OWNER="aid_system", GROUP="aid_system", MODE="0660" 84 ACTION=="add", KERNEL=="smd4", OWNER="aid_system", GROUP="aid_system", MODE="0660" 85 ACTION=="add", KERNEL=="smd_cxm_qmi", OWNER="aid_radio", GROUP="aid_radio", MODE="0640" 86 ACTION=="add", KERNEL=="smd5", OWNER="aid_system", GROUP="aid_system", MODE="0660" 87 ACTION=="add", KERNEL=="smd6", OWNER="aid_system", GROUP="aid_system", MODE="0660" 88 ACTION=="add", KERNEL=="smd7", OWNER="aid_bluetooth", GROUP="aid_bluetooth", MODE="0660" 89 ACTION=="add", KERNEL=="ccid_bridge", OWNER="aid_system", GROUP="aid_system", MODE="0660" 90 ACTION=="add", KERNEL=="ipa", OWNER="aid_radio", GROUP="aid_radio", MODE="0660" 91 ACTION=="add", KERNEL=="wwan_ioctl", OWNER="aid_radio", GROUP="aid_radio", MODE="0660" 92 ACTION=="add", KERNEL=="ipaNatTable", OWNER="aid_radio", GROUP="aid_radio", MODE="0660" 93 ACTION=="add", KERNEL=="rmnet_ctrl", OWNER="aid_usb", GROUP="aid_usb", MODE="0660" 94 ACTION=="add", KERNEL=="dpl_ctrl", OWNER="aid_usb", GROUP="aid_usb", MODE="0660" 95 ACTION=="add", KERNEL=="ipa_odl_ctl", OWNER="aid_radio", GROUP="aid_radio", MODE="0660" 96 ACTION=="add", KERNEL=="ipa_adpl", OWNER="aid_system", GROUP="oem_2905", MODE="0660" It should, udev rules are generated by:
DEVICE=lavender # replace with your device codename cat /var/lib/lxc/android/rootfs/ueventd*.rc /vendor/ueventd*.rc | grep ^/dev | sed -e 's/^\/dev\///' | awk '{printf "ACTION==\"add\", KERNEL==\"%s\", OWNER=\"%s\", GROUP=\"%s\", MODE=\"%s\"\n",$1,$3,$4,$2}' | sed -e 's/\r//' >/etc/udev/rules.d/70-$DEVICE.rules
By Danct12 on 2020-05-04T00:03:38
that doesn't add the aids:
cat /var/lib/lxc/android/rootfs/ueventd*.rc /vendor/ueventd*.rc | grep ^/dev | sed -e 's/^\/dev\///' | awk 'function cvt(u) {return (u == "root" || u ~ /^oem/) ? u : "aid_" u } {printf "ACTION==\"add\", KERNEL==\"%s\", OWNER=\"%s\", GROUP=\"%s\", MODE=\"%s\"\n",$1,cvt($3),cvt($4),$2}'
By Eli Riggs on 2020-05-08T12:28:23
Edited by Administrator
- Resolved by Administrator
172 ACTION=="add", KERNEL=="sec_nvm_*", OWNER="aid_system", GROUP="aid_system", MODE="0660" 173 ACTION=="add", KERNEL=="cryptoapp", OWNER="aid_system", GROUP="aid_system", MODE="0660" 174 ACTION=="add", KERNEL=="spdaemon_ssr", OWNER="aid_system", GROUP="aid_system", MODE="0660" 175 ACTION=="add", KERNEL=="cam-hyp-intf*", OWNER="aid_system", GROUP="aid_camera", MODE="0660" 176 ACTION=="add", KERNEL=="gemini0", OWNER="aid_system", GROUP="aid_camera", MODE="0660" 177 ACTION=="add", KERNEL=="jpeg0", OWNER="aid_system", GROUP="aid_camera", MODE="0660" 178 ACTION=="add", KERNEL=="jpeg1", OWNER="aid_system", GROUP="aid_camera", MODE="0660" 179 ACTION=="add", KERNEL=="jpeg2", OWNER="aid_system", GROUP="aid_camera", MODE="0660" 180 ACTION=="add", KERNEL=="jpeg3", OWNER="aid_system", GROUP="aid_camera", MODE="0660" 181 ACTION=="add", KERNEL=="adsprpc-smd", OWNER="aid_system", GROUP="aid_system", MODE="0664" 182 ACTION=="add", KERNEL=="adsprpc-smd-secure", OWNER="aid_system", GROUP="aid_system", MODE="0644" 183 ACTION=="add", KERNEL=="system_health_monitor", OWNER="aid_radio", GROUP="aid_system", MODE="0644" 184 ACTION=="add", KERNEL=="mdss_rotator", OWNER="aid_system", GROUP="aid_system", MODE="0664" 185 ACTION=="add", KERNEL=="cpu_dma_latency", OWNER="root", GROUP="aid_system", MODE="0660" 186 ACTION=="add", KERNEL=="byte-cntr", OWNER="aid_system", GROUP="oem_2902", MODE="0660" 187 ACTION=="add", KERNEL=="mhi_qdss", OWNER="aid_system", GROUP="oem_2902", MODE="0660" added 4 commits
-
ffcc6acd - 1 commit from branch
postmarketOS:master
- 4d8851aa - device-xiaomi-lavender: adapt Halium to the port
- 9d08fed4 - linux-xiaomi-lavender: Halium-friendly defconfig
- db20eb1a - device-xiaomi-lavender: hybris-ized xorg server config
By Danct12 on 2020-05-06T12:49:58
Toggle commit list-
ffcc6acd - 1 commit from branch
- Resolved by Administrator
somehow no add_android_groups was executed on post-install (had to execute it manually)
then after a reboot I could start lxc container (that was spitting tons of errors in dmesg), but no test_hwcomposer for me
cannot locate symbol "_ZN7android8hardware23getOrCreateCachedBinderEPNS_4hidl4base4V1_05IBaseE" referenced by "/vendor/lib64/vendor.display.config@1.0.so"... Assertion failed: err == 0 (test_common.cpp: create_hwcomposer_window: 370) Aborted
using prebuilt image in OP post of !1144 (closed)
unstoppable spam od errors in logcat
06-10 19:50:56.801 2131 2131 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/android.hardware.health@2.0-service": cannot locate symbol "_ZN7android8hardware15interfacesEqualERKNS_2spINS_4hidl4base4V1_05IBaseEEES8_" referenced by "/vendor/bin/hw/android.hardware.health@2.0-service"... 06-10 19:50:56.801 2132 2132 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/android.hardware.ir@1.0-service": library "android.hardware.ir@1.0.so" not found 06-10 19:50:56.801 2133 2133 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/android.hardware.usb@1.0-service": library "android.hardware.usb@1.0.so" not found 06-10 19:50:56.805 2136 2136 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.google.wifi_ext@1.0-service-vendor": library "libwifi-system-iface.so" not found 06-10 19:50:56.806 2137 2137 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/qseecomd": library "libxml2.so" not found 06-10 19:50:56.809 2138 2138 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/vndservicemanager": cannot locate symbol "selinux_vendor_log_callback" referenced by "/vendor/bin/vndservicemanager"... 06-10 19:50:56.810 2141 2141 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.qti.hardware.perf@2.0-service": library "libxml2.so" not found 06-10 19:50:56.814 2130 2130 E cutils-trace: Error opening trace file: No such file or directory (2) 06-10 19:50:56.815 2130 2130 D vndksupport: Loading /vendor/lib64/hw/android.hardware.graphics.composer@2.1-impl.so from current namespace instead of sphal namespace. 06-10 19:50:56.815 2135 2135 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.display.color@1.0-service": cannot locate symbol "_ZN7android8hardware23getOrCreateCachedBinderEPNS_4hidl4base4V1_05IBaseE" referenced by "/vendor/lib64/vendor.display.color@1.0.so"... 06-10 19:50:56.815 2130 2130 E ServiceManagement: Failed to dlopen android.hardware.graphics.composer@2.1-impl.so: dlopen failed: library "android.hardware.graphics.mapper@3.0.so" not found 06-10 19:50:56.815 2130 2130 E android.hardware.graphics.composer@2.1-service: Could not get passthrough implementation for android.hardware.graphics.composer@2.1::IComposer/default. 06-10 19:50:56.817 2139 2139 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.qti.esepowermanager@1.0-service": cannot locate symbol "_ZN7android8hardware23getOrCreateCachedBinderEPNS_4hidl4base4V1_05IBaseE" referenced by "/vendor/lib64/vendor.qti.esepowermanager@1.0.so"... 06-10 19:50:56.819 2140 2140 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.qti.hardware.alarm@1.0-service": cannot locate symbol "_ZN7android8hardware23getOrCreateCachedBinderEPNS_4hidl4base4V1_05IBaseE" referenced by "/vendor/lib64/vendor.qti.hardware.alarm@1.0.so"... 06-10 19:50:56.823 2145 2145 F linker : CANNOT LINK EXECUTABLE "/system/vendor/bin/dpmQmiMgr": cannot locate symbol "_ZN7android8hardware23getOrCreateCachedBinderEPNS_4hidl4base4V1_05IBaseE" referenced by "/vendor/lib64/com.qualcomm.qti.dpm.api@1.0.so"... 06-10 19:50:56.824 2148 2148 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/android.hardware.media.omx@1.0-service": library "libstagefright_omx.so" not found 06-10 19:50:56.828 2149 2149 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/wifidisplayhalservice": cannot locate symbol "_ZN7android8hardware23getOrCreateCachedBinderEPNS_4hidl4base4V1_05IBaseE" referenced by "/vendor/lib/com.qualcomm.qti.wifidisplayhal@1.0.so"... 06-10 19:50:56.829 2143 2143 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.qti.hardware.tui_comm@1.0-service-qti": cannot locate symbol "_ZN7android8hardware22readEmbeddedFromParcelERKNS0_11hidl_handleERKNS0_6ParcelEmm" referenced by "/vendor/lib64/vendor.qti.hardware.tui_comm@1.0.so"... 06-10 19:50:56.844 2150 2150 F linker : CANNOT LINK EXECUTABLE "/system/vendor/bin/cnd": library "libnetutils.so" not found 06-10 19:50:56.857 2151 2151 F linker : CANNOT LINK EXECUTABLE "/system/vendor/bin/ipacm": library "libxml2.so" not found 06-10 19:50:56.958 2152 2152 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/qcrild": library "android.hardware.radio@1.0.so" not found 06-10 19:50:56.985 2153 2153 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/qcrild": library "android.hardware.radio@1.0.so" not found 06-10 19:50:56.997 2154 2154 F linker : CANNOT LINK EXECUTABLE "/system/vendor/bin/qti": library "libnetutils.so" not found 06-10 19:50:57.012 453 594 W ServiceManagement: Waited one second for android.hardware.health@2.0::IHealth/default. Waiting another... 06-10 19:50:57.013 2155 2155 F linker : CANNOT LINK EXECUTABLE "/system/vendor/bin/adpl": library "libnetutils.so" not found 06-10 19:50:57.023 2156 2156 F linker : CANNOT LINK EXECUTABLE "/system/vendor/bin/netmgrd": library "libnetutils.so" not found
dmesg looks like
[ 608.930633] init: Sending signal 9 to service 'dpmQmiMgr' (pid 3006) process group... HYBRIS: killing PID instead of process group. [ 608.930945] init: Service 'vendor.ipacm' (pid 3015) exited with status 1 [ 608.930954] init: Sending signal 9 to service 'vendor.ipacm' (pid 3015) process group... HYBRIS: killing PID instead of process group. [ 608.952474] binder: 3514:3514 transaction failed 29189/-22, size 0-0 line 3014 [ 608.972565] binder: 3528:3528 transaction failed 29189/-22, size 0-0 line 3014 [ 608.985520] binder: 3479:3479 transaction failed 29189/-22, size 0-0 line 3014 [ 609.024310] init: starting service 'vendor.qcrild'... [ 609.029711] init: Service 'vendor.qcrild' (pid 3016) exited with status 1 [ 609.029722] init: Sending signal 9 to service 'vendor.qcrild' (pid 3016) process group... HYBRIS: killing PID instead of process group. [ 609.057097] init: starting service 'vendor.qcrild2'... [ 609.062414] init: Service 'vendor.qcrild2' (pid 3017) exited with status 1 [ 609.062426] init: Sending signal 9 to service 'vendor.qcrild2' (pid 3017) process group... HYBRIS: killing PID instead of process group. [ 609.073820] init: starting service 'vendor.dataqti'... [ 609.077048] init: Service 'vendor.dataqti' (pid 3018) exited with status 1 [ 609.077069] init: Sending signal 9 to service 'vendor.dataqti' (pid 3018) process group... HYBRIS: killing PID instead of process group. [ 609.086633] init: starting service 'vendor.dataadpl'... [ 609.089826] init: Service 'vendor.dataadpl' (pid 3019) exited with status 1 [ 609.089847] init: Sending signal 9 to service 'vendor.dataadpl' (pid 3019) process group... HYBRIS: killing PID instead of process group. [ 609.099399] init: starting service 'vendor.netmgrd'... [ 609.102585] init: Service 'vendor.netmgrd' (pid 3020) exited with status 1 [ 609.102607] init: Sending signal 9 to service 'vendor.netmgrd' (pid 3020) process group... HYBRIS: killing PID instead of process group. [ 609.550617] init: starting service 'vendor.camera-provider-2-4'... [ 609.551397] init: couldn't write 3021 to /dev/cpuset/camera-daemon/tasks: No such file or directory [ 609.554061] init: Service 'vendor.camera-provider-2-4' (pid 3021) exited with status 1 [ 609.554082] init: Sending signal 9 to service 'vendor.camera-provider-2-4' (pid 3021) process group... HYBRIS: killing PID instead of process group. [ 609.952646] binder: 3514:3514 transaction failed 29189/-22, size 0-0 line 3014 [ 609.972714] binder: 3528:3528 transaction failed 29189/-22, size 0-0 line 3014 [ 609.985667] binder: 3479:3479 transaction failed 29189/-22, size 0-0 line 3014
By Alexey Min on 2020-05-27T07:42:01
Edited by Administrator
added 113 commits
-
f05dd3cd...daa2ea29 - 110 commits from branch
postmarketOS:master
- 2942741c - device-xiaomi-lavender: adapt Halium to the port
- de1b2dd6 - linux-xiaomi-lavender: Halium-friendly defconfig
- 6c14cdba - device-xiaomi-lavender: hybris-ized xorg server config
By Danct12 on 2020-06-05T17:48:07
Toggle commit list-
f05dd3cd...daa2ea29 - 110 commits from branch
- Resolved by Administrator
@danct12 I have an idea, how about we split commit
linux-xiaomi-lavender: Halium-friendly defconfig
into a separate MR? I think that commit is fine on its own. The other 2 commits from this MR can be squashed in this MR to a single one or left as is for later review.What do you think?
By Alexey Min on 2020-07-08T15:42:02
Edited by Ghost User
mentioned in merge request !1411 (merged)
By Alexey Min on 2020-07-13T13:19:48