Tuesday, 2019-05-14

*** OhYash1 is now known as ohyash05:29
Nebrassy[m]how's the progress on 9.0 compatibility?10:05
r0kk3rztheres progress?10:16
malwell it does build10:21
masha11Hello. Devise - griffin (motorola moto z), cm-14.1. I can not start GUI. Help me, please.10:38
masha11I get the error “droid-hal-init: Failed to initialize property area”. I lowered libhybris to release and get the same error.  dmesg: https://pastebin.com/zv1HN2uv journalctl: https://pastebin.com/9qD8m0YJ systemctl: https://pastebin.com/bDXawc9C10:38
masha11I created a directory /property_contexts and now i get the error “property set(...)failed”.10:38
masha11dmesg: https://pastebin.com/cELz2i6m journalctl: https://pastebin.com/CCdUeQmQ systemctl: https://pastebin.com/uqataaBa systemctl status droid-hal-init: https://pastebin.com/cvnSFQDN10:38
T4<Harsh18262> i am getting bad exit status error while running buildpackages.sh https://paste.ubuntu.com/p/VSVY9B67P9/10:49
T4<DSstill01> 7.1 is the best10:54
mal@Harsh18262 it says what you need to do, you need to add "%define droid_target_aarch64 1" to droid-hal spec file (somewhere before the line with %include, do not add anything after that)11:35
T4<Harsh18262> https://paste.ubuntu.com/p/RxvGzcZwr3/11:42
malcheck the build log, maybe something in the kernel config11:44
malit says where the build log is located11:44
T4<Harsh18262> yes it has some errors thanks11:49
Nebrassy[m]On my a/b device, I'm not getting anything, not even anything in console ramoops (it's still the log from the recovery), and I can't boot to the recovery that's supposed to be included12:02
Nebrassy[m]Is there anything special that I need to do for a/b devices other than change mounts?12:02
maldepends on the device, some skip ramdisk init and need a kernel commit reverted to be able to boot to sailfsih12:03
Nebrassy[m]And the ramdisk in the image is 1.4 mb so the boot image format is probably wrong12:07
Nebrassy[m]You mean sailfish needs to boot the ramdisk?12:08
malyes, it does some things there12:08
Nebrassy[m]Ah, I know just the thing12:08
malthat is how it was done in xa212:10
masha11mal: Is there any other solution to my problem?12:54
Nebrassy[m]can this cause any issue?12:57
Nebrassy[m]./hybris/hybris-boot/Android.mk:71: warning: ********************* /boot appears to live on /dev/block/bootdevice/by-name/boot12:57
Nebrassy[m]it's boot_a12:57
T4<elros34> TheKit: are planning to upgrade droid 4 to 3.0.3?13:05
malmasha11: there probably is some solution, I can help right now13:06
mal*I can't help right now13:06
malbusy with work13:06
masha11mal: ok13:06
T4<elros34> TheKit: 3.0.3 use glibc 2.25 with —enable-kernel=3.2. I compiled glibc with 3.0 kernel option so I can boot system but invoker fails to load applications compiled against 3.2 kernel. Maybe you have some ideas how to overcome it?13:08
TheKitelros34, no, I didn't update it. It would be ideal to use mainline kernel on it, since it has good support, but is missing one critical for Sailfish part - GPU acceleration17:15
T4<meierrom> @piggz [just re-capped the power board in our tv, and …], Sounds interesting but I don't get it :) I know what recapping tyres means tho :)20:47
piggz@meierrom replace capacitors, as its common for them to wear/dry out20:48
T4<meierrom> @piggz [@meierrom replace capacitors, as its common fo …], Oh, thanks :)20:49
piggzps, the first rule about #sailfishos-porters is .... dont use reply feature20:49
T4<meierrom> Ok, sorry...20:51
T4<adampigg> np ;)20:56

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!