Tuesday, 2022-02-15

T42<edp_17> mal, @elros34 : Thanks for your help. The image I built yesterday booted and more or less works as expected on the device. 👍07:14
T42<edp_17> None of the sensors work but drops errors to the log: https://paste.ubuntu.com/p/PtJ5rkXV3x/08:13
T42<edp_17> Therefore, I've updated sensorfw to the latest and built the rpm.08:13
T42<edp_17> When trying to install it on device I get: "Fatal error: the to be installed hybris-libsensorfw-qt5-hal-0.12.6-0.armv7hl conflicts with 'hybris-libsensorfw-qt5-binder' provided by the installed hybris-libsensorfw-qt5-binder-0.12.4-1.3.1.jolla.armv7hl"08:14
T42<edp_17> Do I need to re-build hybris-libsensorfw-qt5-binder somehow, or there is another workaround?08:15
T42<edp_17> If install it with rpm -i --nodeps, will it break the system?08:16
T42<elros34> Did you follow "Everyone using old hal versions of sensorfw..." point for 4.2.0 in collabedit.com/kr9xx?08:36
T42<edp_17> Ops, no, I haven't. I'll try that. Thanks.08:42
T42<edp_17> Once I rebuilt configs, do I need to rebuild sensorfw too?08:43
T42<elros34> if it's not in your repo then probably yes, you will see if it's missing in local repo or some common, I do not remember08:46
T42<edp_17> Thanks.08:49
T42<edp_17> I've rebuilt configs, version, geoclue-providers-hybris and sensorfw. Copied all rpm files to the device but cannot install them in one go, either one by one. Is building a new image the only way to try the new packages?09:09
T42<elros34> what error do you have?09:38
T42<elros34> Why don't you use obs?09:41
T42<edp_17> When tried to install droid-hal*.rpm, I got: nothing provides 'patterns-sailfish-device-configuration-i9100'.09:48
T42<edp_17> When tried to install patterns*.rpm, I got: nothing provides 'droid-hal-version-i9100'09:48
T42<edp_17> When tried to install packages manually I realized: patterns-sailfish-device-adaptation-i9100 depends on droid-hal-version-i9100, but droid-hal-version-i9100 depends on  patterns-sailfish-device-adaptation-i9100.09:48
T42<edp_17> The install-local *.rpm didn't help either.09:48
T42<edp_17> So, I gave up and built a new image. I am about installing it on device.09:49
T42<edp_17> Why not use OBS? TBH, I don't know. I still need to build packages locally and build the image as well. I never had enough time to swich to that, probably that's why.09:50
T42<elros34> you only need to build locally droidmedia and droid-hal then everything else can be build on obs, that way you would just zypper dup without worring about which package you need to install first (you should all at once)09:52
T42<edp_17> Well, it sounds good. I'll try that. I guess there is a guide about it somehwere.09:56
T42<elros34> what guide? You already have repo setup, there is nothing new, just upload changes to github then push trigger rebuild button09:59
T42<elros34> then if you need image you run mic manually  with proper repo pointing to obs instead local repo10:03
T42<edp_17> That's how I meant. Does this "proper pointing to obs" mean that I need to amend the local 'Jolla-@RELEASE@-$DEVICE-@ARCH@.ks' file?10:19
T42<edp_17> On the new image all sensors do work fine now. The only issue so far is the camera. When I start the jolla camera app, the device gets rebooted. Will try to get some logs.10:57
T42<edp_17> This is the full journal from a fresh boot until when the device reboots because of the camera: https://paste.ubuntu.com/p/2g72YVMJST/11:26
T42<edp_17> and dmesg: https://paste.ubuntu.com/p/9KZ3gQRHjf/11:30
malhow did solve the sensor and geoclue package issue? did you note that if you need the hal versions then you need to force the package name in patterns12:43
mallike this https://github.com/mer-hybris/droid-config-f5121/commit/ac3b0a0625d773d4ddd848cdcf4ab386ac8525f712:44
T42<edp_17> mal: Yes I noted that. My solution for sensors was: I have applied those *-hal changes into 'patterns-sailfish-device-adaptation-i9100.inc'. Then rebuilt config, version, geoclue-providers-hybris and sensorfw packages and created a new image that I installed on device.12:59
T42<edp_17> Another question. I think broke something in the kernel as MTP stopped working.13:11
T42<edp_17> I've set USB to 'Always ask' but the selection window doesn't pop up neither when I plug the cable in nor when I restart the usb-moded service. In the log there isn't much: https://paste.ubuntu.com/p/G6RvmJdqX7/13:11
T42<elros34> about *.ks: this is covered in OBS section13:28
T42<edp_17> @elros34 : Thanks.13:30
T42<edp_17> I'd need a little help with the wifi on my i9100.14:21
T42<edp_17> Wifi doesn't work when I build a kernel with the latest commit: https://github.com/edp17/android_kernel_samsung_smdk4412/commit/667d052ca5e2846c469a8eeda4f7f98ac9b1626f14:21
T42<edp_17> In the journal this is the error: https://paste.ubuntu.com/p/4wNR4RpWQ6/14:22
T42<edp_17> However, wifi works, when I go back to the previous commit: https://github.com/edp17/android_kernel_samsung_smdk4412/commit/0e148b7e6564a5042757bdfcab6a30c1d021558814:22
T42<edp_17> I probably didn't backport some changes but I don't know what's missing. Can you please help me to find out?14:23
T42<edp_17> (Unfortunately, really hard to get logs from device with that kernel because no wifi and no usb connection either. Therefore, I need to flash wrong/okay kernel back and forth to create/copy logs to PC.)14:26
T42<elros34> is wlan built as modules?14:28
T42<edp_17> Ops, yes. Perhaps I need to copy over the relevant drivers then. :) Right?14:31
T42<elros34> yes14:32
T42<edp_17> Is it only the hdh.ko from out/target/product/i9100/system/lib/modules/? There are some other *.ko files too. (e.g. cifs.ko, nfs.ko, Si4709_driver.ko, etc. Nine files alltogether.)14:37
T42<elros34> best would be package droid-hal and install droid-hal-$DEVICE-kernel-modules14:39
T42<edp_17> Okay. Thanks.14:39
T42<edp_17> @elros34 : It worked. Thanks.14:49
poetasterhej, piggz! what's up!?19:42
piggzjust got back from skiing, now going swimming!!!19:43
piggzback just after 9 UTC19:44
poetastercool! we were skiing two weeks ago!19:49
poetasterhave fun (he's already having fun).19:50
T42<HengYeDev> @elros34 I have reset the init script so its not so hacky. i get to the point where it is mounted and waits 60 seconds. init.log is present but completely empty, what does this mean20:57
T42<elros34> what is mounted? init.log is created very early, next line is echo so it should contains something20:59
T42<HengYeDev> init.log is in userdata, i removed it and tried again and its there so it definitely is being written (re @elros34: what is mounted? ini...)21:01
T42<elros34> anything you changed in init-debug?21:03
T42<HengYeDev> Not at all (re @elros34: anything you changed...)21:03
T42<elros34> hmm do you have sfos unpacked?21:03
T42<HengYeDev> @elros34 I think so21:04
T42<HengYeDev> /data/.stowaways/sailifhsos is filled up21:05
T42<HengYeDev> in init-debug-stderrout i have one line: "+ exec"21:05
T42<elros34> are you sure you have correct /bin/sh and /bin/busybox-static symlinks with valid targets?21:08
T42<elros34> did you make any changes to initramfs script?21:09
piggzpoetaster: im ready for a sleep :D21:29
T42<HengYeDev> @elros34 all the inits are exactly the same, in rootfs /bin/sh points to ../usr/bin/busybox and bysybox-static  are not symlinks21:57
T42<HengYeDev> i will try re unpacking the rootfs21:57
T42<elros34> so I have no idea what breaks, init-debug-stderrout is created just when it switch to second stage21:59
T42<HengYeDev> seems like i messed up the unpacking process somewhere, i retried it and i get the log now22:08
T42<HengYeDev> when modifying the init with the usb.rc, should i apply changes to the init in initramfs or rootfs? @elros3422:10
T42<elros34> obviously to rootfs so you see the results in init.log, initramfs is read only22:11
T42<elros34> maybe not read only but you lose the log after reboot22:12
T42<HengYeDev> @elros34 can you clarify about c.1 and c.2? I saw this which fixes the same error on linux with the same processor https://forum.xda-developers.com/t/linux-porting-native-linux-to-galaxy-note9.3936077/post-7972885622:13
T42<elros34> as far as I can see he doesn't use second configuration c.2 (it's commented out)22:16
T42<elros34> maybe you can show init.logs from just previous ideas we had "Conf 1", you can add MaxPower  and android0/enable22:18
T42<elros34> otherwise try acm,rndis in configuration if that is what supposed to fix the issue22:19
*** ggabriel is now known as Guest49622:30
jules[m]Hi all22:54
jules[m]I try to rebuild oneplus5 image for 4.3.0.1522:55
jules[m]I use https://github.com/JamiKettunen/sfbootstrap22:55
jules[m]last step failed with error about python package22:55
jules[m]Retrieving package python-2.7.17+git6-1.4.2.jolla.aarch64 (1/5),  20.4 KiB ( 20.4 KiB unpacked)22:56
jules[m]Retrieving: python-2.7.17+git6-1.4.2.jolla.aarch64.rpm [done]22:56
jules[m]Failed to provide Package python-2.7.17+git6-1.4.2.jolla.aarch64 (jolla). Do you want to retry retrieval?22:56
jules[m]do you have an explain about that ?22:57
jules[m]thanks22:57
T42<elros34> somebody had the same issue but he didn't provide any more feedback about it: https://irclogs.sailfishos.org/logs/%23sailfishos-porters/%23sailfishos-porters.2022-02-11.log.html#t2022-02-11T16:57:5423:00

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