Saturday, 2019-05-11

*** birdzhang_pc is now known as birdzhang05:17
T4<Harsh18262> getting the following error07:27
T4<Harsh18262> ninja: error: 'libsf_compat_layer', needed by 'hybris-hal', missing and no known rule to make it07:27
abracadabra18262i am getting a following error
riniguskimmoli: ping regarding testing of the release08:02
kimmoli_rinigus: i have had it with me now, but no really used08:12
*** kimmoli_ is now known as kimmoli08:13
kimmolii forgot to disable build on testing: obs. now it is disabled08:13
kimmolii think we can release it08:14
riniguskimmoli: np - let's release as it is. I have used it for some time now and haven't seen anything which would affect my usage so far. although its not 100% covering functionality :) . then we can start with 3.0.3 as well soon08:18
kimmolirinigus: just triggered CI build
kimmolii will upload those to images this evening08:19
riniguskimmoli: excellent! xda post?08:20
kimmolievening when all is ready08:30
Mister_Magisterobs machine broke08:32
Mister_Magistertrying to build update of package but only older versions of package exist in repos (you can't download built packages cause they doesn't exist)08:32
r0kk3rz repo only gets updated once everythibg has finished building08:34
T4<DSstill01> Guys i cant select usb mode, it always use the charging one, and if i choose to always ask, the popup doesnt appear and it stays on charging mode. When i try to choose a mode like mtp or mass storage (which i installed) it says that it would be enabled after usb reconnection, but if i do it, it says that it's currently on charging-only08:54
T4mode, and i have to reconnect usb to use the mode ive chosen. … i tried to steal the usb-moded args file from sibon but that didnt work. What the hacker do i have to do?08:54
Mister_Magisterr0kk3rz:  but everything did finnish09:25
Mister_Magisteri mean finish*09:26
Mister_Magisteri get confused too much09:26
T4<m_aurel> Hello just a quick reminder for our community event next week. I'll try to organize a live stream for people who aren't able to travel to our location:
T4<m_aurel> Are there any experiences with Porting Sailfish OS to a device with a Mediatek MTK Hello P23 (MT6763) Octa-Core 2.0 GHz Chipset?10:51
T4<m_aurel> The device comes by default with Android Pie 9.010:52
T4<m_aurel> I think the effort is less than for a Spreadtrum Chipset. An engineer of Jolla told me, that we should calculate with 24 man month. So I'm looking for alternatives.10:53
T4<m_aurel> I learned from this community, that Android Pie is a challange. But all devices you can order and that are vailable until the next year, come with Android Pie.10:53
T4<m_aurel> We are also in negotiation with a vendor, that offers devices with Qualcomm chips. This would be the best choice, I learned from this community. The customisation process is not clear, yet.10:55
T4<m_aurel> So, would do you think would be the effort for Hardware Adaption for the mentioned Mediatek chipset? Jolla told me, that we should calculate 10 man month for Qualcomm. What's your experience with Mediatek?10:56
T4<DSstill01> Lol what11:01
T4<m_aurel> [Edit] So, what do you think would be the effort for Hardware Adaption for the mentioned Mediatek chipset? Jolla told me, that we should calculate 10 man month for Qualcomm. What's your experience with Mediatek?11:05
T4<m_aurel> Sorry, there was a typo in my question.11:05
r0kk3rzwe dont have a lot of experience with mtk ports11:20
T4<m_aurel> Is there some port for Mediatek?11:23
r0kk3rznot sure, maybe a couple11:25
malgeminipda is mediatek11:26
T4<m_aurel> Thanks, I you was the one, who suggested to calculate something between the effort for Qualcomm (10 MM) and Spreadtrum (24 MM), right? It's a wide range. I think I should ask Jolla either.11:26
T4<m_aurel> [Edit] Thanks, I think you was the one, who suggested to calculate something between the effort for Qualcomm (10 MM) and Spreadtrum (24 MM), right? It's a wide range. I think I should ask Jolla either.11:27
malhmm, I don't think I said anything about effort, it's not easy to estimate the amount of work11:27
T4<m_aurel> I'm afraid, you are right. I think we need to invest one MM as a PoC to make the estimation. Do you think that is a reasonable approach?11:29
malmight be, I have never really calculated how much time it takes to port11:39
T4<NotKit> @m_aurel [Are there any experiences with Porting Sailfis …], beware that it is what Cosmo will come with and it will probably have Sailfish OS12:01
T4<NotKit> (MediaTek SoC with Pie BSP, not exactly MT6763 though)12:02
T4<DSstill01> i installed the newest libhybris from my obs repo, ignoring missing error because that was present in /lib/ and now libhybris is broken and display and many stuff dont work. how can i downgrade it?12:04
malmanually define older revision12:04
malin _service file on OBS12:04
malgive a link to the OBS project12:05
T4<DSstill01> ahh, ok ,thanks12:05
malwhich android base?12:06
T4<DSstill01> 7.112:06
malnew libhybris should work with that12:06
T4<DSstill01> hmm no, it says im missing GLIBC-2.2212:07
T4<DSstill01> even when i run libhybris test it says that12:07
malhmm, I really need to see what you are building12:08
T4<DSstill01> libhybris12:09
T4<DSstill01> lol12:09
T4<DSstill01> i built libhybris, upgraded by ignoring that warning and rip12:09
malwhy would you give the download link12:09
T4<DSstill01> ah
maldid you update your device to 3.0.3?12:10
T4<DSstill01> nno12:10
malOBS latest is 3.0.3 now12:10
T4<DSstill01> really?12:10
mal3.0.3.9 to be exact12:10
T4<DSstill01> aww12:10
T4<DSstill01> didnt know that12:10
malglibc was updated in 3.0.3 so now wonder it breaks if you didn't update all of sfos12:11
T4<DSstill01> aand how to upgrade to next release?12:11
malso run: "ssu re" then "version --dup"12:12
T4<DSstill01> ok12:12
malmaybe show output of "ssu lr" before running that latter command12:12
T4<DSstill01> @mal [maybe show output of "ssu lr" before running t …], repos are fine12:14
maljust wanted to be sure12:14
T4<DSstill01> is there a way to print a black screen on device?12:15
T4<DSstill01> since my display is already burned i dont want to burn it more, you know what im sayin12:16
T4<DSstill01> i will just interrupt the update and flash a bootimg with a logo12:16
T4<elros34> monich: I built few ofono versions and I think this commit: might cause sms issue and long (1 minute) connection to provider.12:20
T4<elros34> Issue is reported here:
wdehooghi trying to build on bacon (cm12.1). droid-hal-init fails see
wdehoogusing libhybris
wdehoogrunning droid-hal-init from cmdline results in segfault12:29
wdehooglogcat is empty (logcat read failure: Connection refused)12:30
malwdehoog: try using (20bcd5be11fcd82aa9e2e995c4bb37af9c94cbad)12:32
wdehoogmal: will do. thanks.12:33
malwdehoog: it seems there is something wrong in libhybris on some older bases12:33
malwhich needs to debugged properly12:33
mal@Harsh18262 did you already figure out the libsf_compat_layer error?13:49
malwdehoog: did the older version work?13:49
T4<Harsh18262> @mal [@Harsh18262 did you already figure out the lib …], yes but now there is a new error13:50
malyour fixup-mountpoints file is wrong, show the changes you made13:55
wdehoogmal: just tried. it did not help, see
wdehoogfor using libhybris helped but there droid-hal-init was always working. now it is not13:57
wdehoogjust in case here is dmesg:
T4<Harsh18262> (Document) Could not save file.13:58
T4<Harsh18262> fixup-mountpoint on paste bin
malwhat is the device codename for your device?14:00
T4<Harsh18262> X00TD14:00
mal@Harsh18262 the enrty you added is not formatted the same way as the previous ones, not sure how sensitive that is for formatting, better make sure it's the same14:06
T4<austenite> there is space before XOOTD line14:06
malyes, there is a mixture of tabs and spaces which probably might break it14:07
malmake sure the indentations are the same as in the previous entries14:07
Thaodan_any reason why the latest sdk image is not
malprobably just hasn't been updated yet14:13
T4<elros34> oh looks like sailfish is now compiled against 3.2 kernel. Not good for my 3.0 kernel ...15:49
T4<DSstill01> 3.0 is old af16:18
Thaodan_any reason why libhybris is installed into the device target?16:19
Thaodan_I get issues removing mesa-llvmpipe for it16:19
mal@elros34 what requires 3.2 kernel?16:31
malThaodan_: because you build packages that depend on libhybris16:32
malThaodan_: what issues?16:32
T4<elros34> mal: everything. I cant boot to system, glibc is compiled with against 3.2 kernel, busybox-static also16:33
Thaodan_mal: breaking dependencies when removing mesa-llvmpipe16:36
malThaodan_: show some details16:36
malThaodan_: maybe try sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper in libhybris16:37
malThaodan_: that should handle the dependencies better than just removing mesa16:37
Thaodan_thats what the offical build script does too16:39
malthat doesn't look normal16:40
Thaodan_I do sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -R -msdk-install zypper -n rm mesa-llvmpip16:41
Thaodan_I do sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -R -msdk-install zypper -n rm mesa-llvmpipe16:41
Thaodan_as the deploy function does when deploying libhybris16:42
Thaodan_I simply used --do-not-install and it works fine16:45
Thaodan_the image has libhybris installed as expected16:45
T4<meierrom> @abhishek_0 [Any signs of volte yet?], Am I the only one who missed you. Where have you been. :)17:23
T4<meierrom> @NotKit [beware that it is what Cosmo will come with an …], Your point being? :)17:26
T4<meierrom> @m_aurel [I think the effort is less than for a Spreadtr …], I'm sure you are talking to Jolla's sales department. :)17:29
T4<meierrom> @m_aurel: you develop software, you know Linux, you can find time? That's all you need to get started with porting yourself. You have the right people here to assist you. :)17:42
T4<DSstill01> "calculating" porting time is ridicolus17:49
malanyone else having issues with mobile data on 3.0.3?17:57
T4<DSstill01> Yes, but currently im on a crappy place where the signal is always slow18:05
T4<DSstill01> [Edit] Yes, but currently im on a crappy place where the signal is always low18:05
T4<DSstill01> My professional ofono fork will always work18:10
T4<abhishek_0> Heyy @meierrom just moved on from the techie stuff, still trying to figure out was it a passion or a phase18:10
T4<meierrom> @abhishek_0 [Heyy @meierrom just moved on from the techie s …], It was both. And now you are moving to the next phase with us. :)18:15
T4<DSstill01> Me too but i still do some stuff. Basically only sailfishos atm18:31
kimmoliis it just me or is upload to devaamo sosloooow?18:36
wdehoogany idea how I can find out what makes droid-hal-init segfault?18:49
riniguskimmoli: thanks!18:49
malwdehoog: strace?18:52
malor gdb18:52
malbtw, latest libhybris has support for debugging also android side libs18:52
wdehoogstrace gives nada, after reading /init/props it segfaults18:52
wdehooggdb gives a stacktrace with only numbers18:53
wdehoogmal: can I find some doc on how to debug libhybris and/or android side?18:53
malmaybe you need to set HYBRIS_ENABLE_LINKER_DEBUG_MAP=118:54
malassuming you are using latest libhybris18:54
wdehoogbtw it was /default.prop18:54
wdehoog.30 or .31?18:54
mal.30 should be enouhg, it doesn't have the env var yet but has debug enabled always afaik18:58
wdehoogmal: maybe it is not a libhybris issue. I tried both 0.30 as well as .31 but same result and no debug output19:21
wdehoogI tried: HYBRIS_ENABLE_LINKER_DEBUG_MAP=1;LD_LIBRARY_PATH=/usr/libexec/droid-hybris/system/lib/:/vendor/lib:/system/lib /sbin/droid-hal-init19:21
maldid you with gdb and that env var19:23
wdehoogmal: like this?
malok, that's not very useful19:28
wdehoogmal: /lib/ --list /sbin/droid-hal-init says it is statically linked19:28
T4<adampigg> mal, u have data issues? i think mido is ok19:35
mal@adampigg yep, no luck getting mobile data working in 3.0.319:38
mal@adampigg I seem to get a lot of type=1701 audit(1557601316.462:792): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=24047 comm="sh" reason="memory violation" sig=11 and also [rmnet0] error: rmnet_ioct called for unsupported cmd[35325]19:40
T4<DSstill01> Try my professional ofono fork, maybe they added something nasty in upstream20:04
malwhat fork20:05
maland we were using the same ofono version in previous release afaik so probably something else20:06
T4<DSstill01> Ah20:08
malI think I know what errors cause that but not sure why those happen20:10
malcompared to 3.0.2 build and it didn't have those shell script segfaults20:11
T4<DSstill01> If i were you id try my pro fork20:32
malyou still didn't say where it is or anything else20:33
T4<DSstill01> On my github account20:35
T4<DSstill01> Https://
T4<DSstill01> Tested by me and it works20:36
malso why do you need that?20:41
T4<DSstill01> To make calls working on samsung devices20:42
T4<DSstill01> Like mine, obv20:43
Nebrassy[m]is sailfish os compatible with a/b devices?21:47
T4Nebrassy was added by: Nebrassy22:08
malyes, for example xa2 has a/b partitioning22:21
nk2IsHerehi, any way to fix this? (mmcblk0p21 is userdata) "couldn't mount as ext3 due to feature incompatibilities" latest kmesg from device:
malnk2IsHere: I doubt that is the real issue, you can see some watchdog message near the end22:58
nk2IsHeresearching "watchdog: S3C2410 Watchdog: watchdog did not stop!" revealed me that it's something connected with shutting down the system23:06
nk2IsHeremal: i'm trying to fix "259 EXT4-fs (mmcblk0p21): couldn't mount as ext3 due to feature incompatibilities", it basically tries to mount ext4 as ext323:07
nk2IsHereS3C2410 is samsung's nand controller23:08
malnk2IsHere: do you see in host dmesg how far the boot goes23:10
nk2IsHeremal: it lives for approx 10 secs then just dies <- dmesg23:19
T4<meierrom> @adampigg [<reply to media>], Wow, true dev board. Guess we'll be having another quality port very soon :)23:22
nk2IsHeremal: this dmesg cutout is from recovery bootup process, same mounting goes normally 2637 EXT4-fs (mmcblk0p21): mounted filesystem with ordered data mode. Opts: noauto_da_alloc,journal_async_commit,errors=panic23:23
malnk2IsHere: I said host dmesg, if the boot goes far enough host dmesg will have debug info in usb messages23:24
malassuming usb cable is connected during boot23:25
nk2IsHeremal: well, there is nothing in dmesg of host concerning usb messages: sudo dmesg | grep -i usb  +- IOAudioEngine[<ptr>]::resetStatusBuffer(), full:
nk2IsHerei should go and install linux on my machine23:38
malwhere you run that if you don't have linux?23:40
nk2IsHereos x for local testing and vps for building and stuff23:40
malah, that dmesg of yours has systemd message in the end so it must reach quite far23:42
malwhich means userdata is mounted23:42
malare you sure you correctly disabled selinux?23:43
malthe mer kernel checker suggests one watchdog related kernel config, maybe enable that in case selinux is really correctly disabled, how did you disable it?23:44
nk2IsHerehmm, first time i've built kernel, it was stopping even earlier because of selinux (i've already set CONFIG_SECURITY_SELINUX_BOOTPARAM=y, CONFIG_AUDIT=n, others left untouched)23:47
nk2IsHeresecond one helped me to pass throung it and get this error (i've set CONFIG_SECURITY_SELINUX=n in addition)23:48
nk2IsHerebut even though i've set CONFIG_SECURITY_SELINUX_BOOTPARAM=y, config checker still argues about it23:49
malAUDIT should be =y usually on reasonably modern devices23:55
malwhat did the checker complain?23:56
malusually CONFIG_SECURITY_SELINUX_BOOTPARAM=y and in kernel commandline selinux=0 should be enough23:57

Generated by 2.17.1 by Marius Gedminas - find it at!