Monday, 2021-04-12

T42<dgmarie2> anybody know what's preventing the boot?01:03
rinigusThaodan thanks for keeping me in the loop.05:36
T42<b100dian> Hi all, for starting the porting from a lineage-17.1 ROM, do I need to be able to customize the vendor.img? I'm starting from a port that doesn't build one, but works with the one from the device09:08
malwe usually don't modify system.img and vendor.img09:38
T42<adampigg> except for bind-mounting as required ;)09:45
T42<b100dian> thanks - given my luck so far, one month later I'll come back asking what was that bind mounting Adam was talking about:)10:16
T42<b100dian> what about sdclang, can it be used for compiling the kernel?10:17
T42<elros34> @dgmarie2 check whether you have typo in droid-hal-device.conf. I wonder why didn't you use all birdzhang sources: kernel, droid-config/hal, probably that would boot at first time. BTW either enable persistent logging (hadk-faq) in journal or try to get logs (journal, dmesg, logcat) closely after reboot to be sure everything is includ10:52
T42<birdzhang> @dgmarie2 davinci?11:41
T42<birdzhang> if you use LOS base rom, you need replace /system/lib/, it’s broken.11:44
*** wiktorek141 is now known as wiktorek14012:27
refaHi all, I'm porting Sailfish OS to Moto G 2013 (falcon) and got no display. I can connect to the device via telnet. The dmesg in and I've following the FAQ to test hwc and minimer, but I got this error
refaAlso I can't find TARGET_QCOM_DISPLAY_VARIANT in,, and other files that included by those files16:18
refaAny clue?16:19
T42<karlin5233> Hi! anyone know if this error prevents system startup? i have a nexus 516:25
T42<karlin5233> (Photo, 720x1280)
T42<elros34> most probably data is already mounted that is why you see that warning. You can ignore it16:29
T42<karlin5233> @elros34 [most probably data is already mounted that is …], Thanks, I can't install it, I did all the procedures and it remains on the Google logo, you don't know any certain method?16:31
T42<elros34> no, you would have to ask porter. What instruction did you follow? Have you installed correct cm/lineage version first and that was working?16:34
T42<ankaos> @karlin5233 [<reply to media>], not problem16:34
T42<karlin5233> @elros34 [no, you would have to ask porter. What instruc …], Yes, the instructions given by the developer of the port, but I can't start it in any way and if it works in other users.16:40
*** muhammadrefa is now known as refa17:06
malrefa: looks like droid-hal-init fails for you, it can't setup selinux things, which android base? did you disable selinux the correct way?17:08
refamal: I'm using hybris-14.1. I'll check it later17:09
malrefa: how did you disable selinux?17:13
T42Gen_Goddy2shoes was added by: Gen_Goddy2shoes17:42
rinigusmanaged to get flatpak running on aarch64/aosp10 port. so, in principle, access to qt5.1519:54
T42<gibcheesepuffs> @rinigus [managed to get flatpak running on aarch64/aosp …], Which device is that?20:09
rinigus@gibcheesepuffs: sony xz2c (tama platform device)20:10
rinigusbut not sure if it all works yet to the same extent as on arm32 bit port variant... early days20:11
refamal: I'm not disabling selinux yet. So I need to follow HADK section 9.3.1?20:40
malrefa: yes20:44
*** refa is now known as muhammadrefa21:59
refamal: Ok I've disabled selinux, and I got this error when following the FAQ to fix display
refaAnd I can't find TARGET_QCOM_DISPLAY_VARIANT in and in other files that included22:02
refaIn I see caf/msm8974 in Display column. What does it means?22:04
malI don't see any relevant error22:04
refamal: The display still not working. It shows "Unlocked bootloader" screen (that always appear every startup)22:05
refaBut the screen can turned off and the notification light turned on22:05
maldoes droid-hal-init start successfully now?22:06
refamal: yes it's active22:16
*** muhammadrefa is now known as refa22:21
T42<zinstack625> Perhaps there is something in logcat. Display can be accessed, but lipstick is dead, as it seems22:36

Generated by 2.17.1 by Marius Gedminas - find it at!