| *** birdzhang_pc is now known as birdzhang | 05:17 | |
| T4 | <Harsh18262> getting the following error | 07:27 |
|---|---|---|
| T4 | <Harsh18262> ninja: error: 'libsf_compat_layer', needed by 'hybris-hal', missing and no known rule to make it | 07:27 |
| abracadabra18262 | i am getting a following error https://paste.ubuntu.com/p/FnsksgnX2D/ | 07:48 |
| rinigus | kimmoli: ping regarding testing of the release | 08:02 |
| kimmoli_ | rinigus: i have had it with me now, but no really used | 08:12 |
| *** kimmoli_ is now known as kimmoli | 08:13 | |
| kimmoli | i forgot to disable build on testing: obs. now it is disabled | 08:13 |
| kimmoli | i think we can release it | 08:14 |
| rinigus | kimmoli: 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 soon | 08:18 |
| kimmoli | rinigus: just triggered CI build https://gitlab.com/sailfishos-porters-ci/onyx-ci/-/jobs/210785944 | 08:19 |
| kimmoli | i will upload those to images this evening | 08:19 |
| rinigus | kimmoli: excellent! xda post? | 08:20 |
| kimmoli | evening when all is ready | 08:30 |
| Mister_Magister | obs machine broke | 08:32 |
| Mister_Magister | trying 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 |
| Mister_Magister | weird | 08:33 |
| r0kk3rz | repo only gets updated once everythibg has finished building | 08: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-only | 08:54 |
| T4 | mode, 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_Magister | r0kk3rz: but everything did finnish | 09:25 |
| Mister_Magister | i mean finish* | 09:26 |
| Mister_Magister | i get confused too much | 09: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: http://volla.online/blog/files/community-days.html | 10:50 |
| 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.0 | 10: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 what | 11: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 |
| r0kk3rz | we dont have a lot of experience with mtk ports | 11:20 |
| T4 | <m_aurel> Is there some port for Mediatek? | 11:23 |
| r0kk3rz | not sure, maybe a couple | 11:25 |
| mal | geminipda is mediatek | 11: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 |
| mal | hmm, I don't think I said anything about effort, it's not easy to estimate the amount of work | 11: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 |
| mal | might be, I have never really calculated how much time it takes to port | 11: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 OS | 12: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 libc.so.6 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 |
| mal | manually define older revision | 12:04 |
| mal | in _service file on OBS | 12:04 |
| mal | give a link to the OBS project | 12:05 |
| T4 | <DSstill01> ahh, ok ,thanks | 12:05 |
| mal | which android base? | 12:06 |
| T4 | <DSstill01> 7.1 | 12:06 |
| mal | new libhybris should work with that | 12:06 |
| T4 | <DSstill01> hmm no, it says im missing libc.so.6 GLIBC-2.22 | 12:07 |
| T4 | <DSstill01> even when i run libhybris test it says that | 12:07 |
| mal | hmm, I really need to see what you are building | 12:08 |
| T4 | <DSstill01> libhybris | 12:09 |
| T4 | <DSstill01> lol | 12:09 |
| mal | DETAILS!!!!!!!!!!!!!!!!!!! | 12:09 |
| T4 | <DSstill01> http://repo.merproject.org/obs/nemo:/devel:/hw:/samsung:/a5ultexx/ | 12:09 |
| T4 | <DSstill01> i built libhybris, upgraded by ignoring that warning and rip | 12:09 |
| mal | why would you give the download link | 12:09 |
| T4 | <DSstill01> ah https://build.merproject.org/project/show/nemo:devel:hw:samsung:a5ultexx | 12:09 |
| mal | did you update your device to 3.0.3? | 12:10 |
| T4 | <DSstill01> nno | 12:10 |
| mal | OBS latest is 3.0.3 now | 12:10 |
| T4 | <DSstill01> really? | 12:10 |
| mal | 3.0.3.9 to be exact | 12:10 |
| T4 | <DSstill01> aww | 12:10 |
| T4 | <DSstill01> didnt know that | 12:10 |
| mal | glibc was updated in 3.0.3 so now wonder it breaks if you didn't update all of sfos | 12:11 |
| T4 | <DSstill01> aand how to upgrade to next release? | 12:11 |
| mal | so run: "ssu re 3.0.3.9" then "version --dup" | 12:12 |
| T4 | <DSstill01> ok | 12:12 |
| mal | maybe show output of "ssu lr" before running that latter command | 12:12 |
| T4 | <DSstill01> @mal [maybe show output of "ssu lr" before running t …], repos are fine | 12:14 |
| mal | ok | 12:14 |
| mal | just wanted to be sure | 12: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 sayin | 12:16 |
| T4 | <DSstill01> i will just interrupt the update and flash a bootimg with a logo | 12:16 |
| mal | ok | 12:17 |
| T4 | <elros34> monich: I built few ofono versions and I think this commit: https://git.merproject.org/mer-core/ofono/commit/549fe2355f6a63059a4ecae904388856185a50ad might cause sms issue and long (1 minute) connection to provider. | 12:20 |
| T4 | <elros34> Issue is reported here: https://together.jolla.com/question/202278/sms-does-not-work-after-installing-3028/?answer=205366#post-id-205366 | 12:20 |
| wdehoog | hi trying to build 3.0.3.9 on bacon (cm12.1). droid-hal-init fails see http://susepaste.org/53187956 | 12:28 |
| wdehoog | using libhybris 0.0.5.30 | 12:29 |
| wdehoog | running droid-hal-init from cmdline results in segfault | 12:29 |
| wdehoog | logcat is empty (logcat read failure: Connection refused) | 12:30 |
| mal | wdehoog: try using 0.0.5.25 (20bcd5be11fcd82aa9e2e995c4bb37af9c94cbad) | 12:32 |
| wdehoog | mal: will do. thanks. | 12:33 |
| mal | wdehoog: it seems there is something wrong in libhybris on some older bases | 12:33 |
| mal | which needs to debugged properly | 12:33 |
| mal | @Harsh18262 did you already figure out the libsf_compat_layer error? | 13:49 |
| mal | wdehoog: 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 error | 13:50 |
| T4 | <Harsh18262> https://paste.ubuntu.com/p/f9hbwjqfKm/ | 13:52 |
| mal | your fixup-mountpoints file is wrong, show the changes you made | 13:55 |
| wdehoog | mal: just tried. it did not help, see http://susepaste.org/19024479 | 13:56 |
| wdehoog | for 3.0.2.8 using libhybris 0.0.5.25 helped but there droid-hal-init was always working. now it is not | 13:57 |
| wdehoog | just in case here is dmesg: http://susepaste.org/70267083 | 13:58 |
| T4 | <Harsh18262> (Document) Could not save file. | 13:58 |
| T4 | <Harsh18262> fixup-mountpoint on paste bin https://paste.ubuntu.com/p/CzswTKDKyH/ | 13:59 |
| mal | what is the device codename for your device? | 14:00 |
| T4 | <Harsh18262> X00TD | 14: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 same | 14:06 |
| T4 | <austenite> there is space before XOOTD line | 14:06 |
| mal | yes, there is a mixture of tabs and spaces which probably might break it | 14:07 |
| mal | make sure the indentations are the same as in the previous entries | 14:07 |
| Thaodan_ | any reason why the latest sdk image is not 3.0.3.9? | 14:12 |
| mal | probably just hasn't been updated yet | 14: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 af | 16:18 |
| Thaodan_ | any reason why libhybris is installed into the device target? | 16:19 |
| Thaodan_ | I get issues removing mesa-llvmpipe for it | 16:19 |
| mal | @elros34 what requires 3.2 kernel? | 16:31 |
| mal | Thaodan_: because you build packages that depend on libhybris | 16:32 |
| mal | Thaodan_: what issues? | 16:32 |
| T4 | <elros34> mal: everything. I cant boot to system, glibc is compiled with against 3.2 kernel, busybox-static also | 16:33 |
| Thaodan_ | mal: breaking dependencies when removing mesa-llvmpipe | 16:36 |
| mal | Thaodan_: show some details | 16:36 |
| mal | Thaodan_: maybe try sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper in libhybris | 16:37 |
| mal | Thaodan_: that should handle the dependencies better than just removing mesa | 16:37 |
| Thaodan_ | mal: https://invent.kde.org/snippets/196 | 16:38 |
| Thaodan_ | thats what the offical build script does too | 16:39 |
| mal | that doesn't look normal | 16:40 |
| Thaodan_ | I do sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -R -msdk-install zypper -n rm mesa-llvmpip | 16:41 |
| Thaodan_ | I do sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -R -msdk-install zypper -n rm mesa-llvmpipe | 16:41 |
| Thaodan_ | as the deploy function does when deploying libhybris | 16:42 |
| mal | hmm | 16:44 |
| Thaodan_ | I simply used --do-not-install and it works fine | 16:45 |
| Thaodan_ | the image has libhybris installed as expected | 16:45 |
| mal | ok | 16:46 |
| 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 ridicolus | 17:49 |
| mal | anyone 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 slow | 18:05 |
| T4 | <DSstill01> [Edit] Yes, but currently im on a crappy place where the signal is always low | 18:05 |
| kimmoli | rinigus: https://forum.xda-developers.com/showpost.php?p=79508087&postcount=1022 | 18:06 |
| T4 | <DSstill01> My professional ofono fork will always work | 18:10 |
| T4 | <abhishek_0> Heyy @meierrom just moved on from the techie stuff, still trying to figure out was it a passion or a phase | 18: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 atm | 18:31 |
| kimmoli | is it just me or is upload to devaamo sosloooow? | 18:36 |
| kimmoli | 133kB/s | 18:36 |
| wdehoog | any idea how I can find out what makes droid-hal-init segfault? | 18:49 |
| rinigus | kimmoli: thanks! | 18:49 |
| mal | wdehoog: strace? | 18:52 |
| mal | or gdb | 18:52 |
| mal | btw, latest libhybris has support for debugging also android side libs | 18:52 |
| wdehoog | strace gives nada, after reading /init/props it segfaults | 18:52 |
| wdehoog | gdb gives a stacktrace with only numbers | 18:53 |
| wdehoog | mal: can I find some doc on how to debug libhybris and/or android side? | 18:53 |
| mal | maybe you need to set HYBRIS_ENABLE_LINKER_DEBUG_MAP=1 | 18:54 |
| mal | assuming you are using latest libhybris | 18:54 |
| wdehoog | btw it was /default.prop | 18: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 afaik | 18:58 |
| wdehoog | mal: maybe it is not a libhybris issue. I tried both 0.30 as well as .31 but same result and no debug output | 19:21 |
| wdehoog | I tried: HYBRIS_ENABLE_LINKER_DEBUG_MAP=1;LD_LIBRARY_PATH=/usr/libexec/droid-hybris/system/lib/:/vendor/lib:/system/lib /sbin/droid-hal-init | 19:21 |
| mal | did you with gdb and that env var | 19:23 |
| wdehoog | mal: like this? http://susepaste.org/view//37338634 | 19:25 |
| mal | ok, that's not very useful | 19:28 |
| wdehoog | mal: /lib/ld-linux-armhf.so.3 --list /sbin/droid-hal-init says it is statically linked | 19:28 |
| mal | ok | 19:28 |
| T4 | <adampigg> mal, u have data issues? i think mido is ok | 19:35 |
| mal | @adampigg yep, no luck getting mobile data working in 3.0.3 | 19: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 upstream | 20:04 |
| mal | what fork | 20:05 |
| mal | and we were using the same ofono version in previous release afaik so probably something else | 20:06 |
| T4 | <DSstill01> Ah | 20:08 |
| mal | I think I know what errors cause that but not sure why those happen | 20:10 |
| mal | compared to 3.0.2 build and it didn't have those shell script segfaults | 20:11 |
| T4 | <DSstill01> If i were you id try my pro fork | 20:32 |
| mal | you still didn't say where it is or anything else | 20:33 |
| T4 | <DSstill01> On my github account | 20:35 |
| T4 | <DSstill01> Https://github.com/deadsquirrel01/ofono | 20:36 |
| T4 | <DSstill01> Tested by me and it works | 20:36 |
| mal | so why do you need that? | 20:41 |
| T4 | <DSstill01> To make calls working on samsung devices | 20:42 |
| T4 | <DSstill01> Like mine, obv | 20:43 |
| Nebrassy[m] | is sailfish os compatible with a/b devices? | 21:47 |
| T4 | Nebrassy was added by: Nebrassy | 22:08 |
| mal | yes, for example xa2 has a/b partitioning | 22:21 |
| nk2IsHere | hi, any way to fix this? (mmcblk0p21 is userdata) "couldn't mount as ext3 due to feature incompatibilities" latest kmesg from device: https://pastebin.com/ijeDN9VR | 22:50 |
| mal | nk2IsHere: I doubt that is the real issue, you can see some watchdog message near the end | 22:58 |
| nk2IsHere | searching "watchdog: S3C2410 Watchdog: watchdog did not stop!" revealed me that it's something connected with shutting down the system | 23:06 |
| nk2IsHere | mal: 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 ext3 | 23:07 |
| nk2IsHere | S3C2410 is samsung's nand controller | 23:08 |
| mal | nk2IsHere: do you see in host dmesg how far the boot goes | 23:10 |
| nk2IsHere | mal: it lives for approx 10 secs then just dies https://pastebin.com/ijeDN9VR <- dmesg | 23:19 |
| T4 | <meierrom> @adampigg [<reply to media>], Wow, true dev board. Guess we'll be having another quality port very soon :) | 23:22 |
| nk2IsHere | mal: this dmesg cutout is from recovery bootup process https://pastebin.com/TVJasjYS, same mounting goes normally 2637 EXT4-fs (mmcblk0p21): mounted filesystem with ordered data mode. Opts: noauto_da_alloc,journal_async_commit,errors=panic | 23:23 |
| mal | nk2IsHere: I said host dmesg, if the boot goes far enough host dmesg will have debug info in usb messages | 23:24 |
| mal | assuming usb cable is connected during boot | 23:25 |
| nk2IsHere | mal: well, there is nothing in dmesg of host concerning usb messages: sudo dmesg | grep -i usb +- IOAudioEngine[<ptr>]::resetStatusBuffer(), full: https://pastebin.com/dVsFCJj4 | 23:37 |
| nk2IsHere | i should go and install linux on my machine | 23:38 |
| mal | where you run that if you don't have linux? | 23:40 |
| nk2IsHere | os x for local testing and vps for building and stuff | 23:40 |
| mal | ah, that dmesg of yours has systemd message in the end so it must reach quite far | 23:42 |
| mal | which means userdata is mounted | 23:42 |
| mal | are you sure you correctly disabled selinux? | 23:43 |
| mal | the 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 |
| nk2IsHere | hmm, 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 |
| nk2IsHere | second one helped me to pass throung it and get this error (i've set CONFIG_SECURITY_SELINUX=n in addition) | 23:48 |
| nk2IsHere | but even though i've set CONFIG_SECURITY_SELINUX_BOOTPARAM=y, config checker still argues about it | 23:49 |
| mal | AUDIT should be =y usually on reasonably modern devices | 23:55 |
| mal | what did the checker complain? | 23:56 |
| mal | usually CONFIG_SECURITY_SELINUX_BOOTPARAM=y and in kernel commandline selinux=0 should be enough | 23:57 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!