| Oksana | Help, please! I am trying to use https://build.sailfishos.org/ , and I see button "Add file", but I do not see button "Add folder/aka/directory". What should I do? | 03:14 |
|---|---|---|
| r0kk3rz | what do you want a folder for? | 03:14 |
| Oksana | r0kk3rz: I am trying to build pyhoca-cli for Sailfish OS. As a first step for getting a working X2Go client. Looking at source code, it has hierarchical structure, with some python code put into a pyhoca directory. | 03:22 |
| r0kk3rz | two options, upload a tarball or use the git | 03:22 |
| r0kk3rz | preferrably use the git | 03:22 |
| Oksana | But looking at spec file, it uses a tar.gz archive. So, I might try that route. But I don't like how a tar.gz file has everything put into a directory, internally, and not just in root of the tarball. | 03:23 |
| Oksana | https://code.x2go.org/releases/source/pyhoca-cli/pyhoca-cli-0.6.1.2.tar.gz ^ | 03:23 |
| r0kk3rz | why is that a problem? | 03:24 |
| * Oksana would have expected a tarball to contain the source code directly inside the tarball, and not inside a pyhoca-cli-0.6.1.2 directory | 03:25 | |
| r0kk3rz | preferably you create the packaging in a git like this https://git.sailfishos.org/mer-core/python3-attrs | 03:26 |
| r0kk3rz | your account will work there also | 03:27 |
| Oksana | Hmm, thank you! Didn't know this git existed - will use that, instead of github. | 03:28 |
| Oksana | Build breaks at line '%{py2_build}'/var/tmp/rpm-tmp.1HbsK7: line 36: fg: no job control error: Bad exit status from /var/tmp/rpm-tmp.1HbsK7 (%build) | 03:29 |
| r0kk3rz | this is an example of how you can export to OBS from the gitlab https://build.sailfishos.org/package/view_file/mer:core/python3-gobject/_service?expand=1 | 03:31 |
| r0kk3rz | you just create a _service file with that contents | 03:31 |
| Oksana | Complicated conditional spec... | 03:34 |
| r0kk3rz | where did you get the spec from? | 03:44 |
| rinigus | @adampigg: great! I'm ready to join (tonight). If you have some docs to read up, please post. In particular, what are the libs/parts involved | 06:21 |
| rinigus | mal: ping regarding sensorfw and qtsensors MR reviews | 06:22 |
| T42 | <hacker12455> anyone knows why this happens? | 08:08 |
| T42 | <hacker12455> Error building the cache: | 08:08 |
| T42 | <hacker12455> [adaptation0|plugin:/ssu?repo=adaptation0] Valid metadata not found at specified URL | 08:08 |
| r0kk3rz | remove adaptation0 repo | 08:08 |
| T42 | <hacker12455> where are the repos stored? | 08:09 |
| r0kk3rz | ssu | 08:10 |
| T42 | <hacker12455> weird I can't seem to remove the repo | 08:17 |
| T42 | <hacker12455> https://bpa.st/FWRA | 08:18 |
| T42 | <hacker12455> is there something going on with the releases.sailfishos.org server? | 08:33 |
| T42 | <hacker12455> since downloading the ubuntu tarball fails | 08:34 |
| T42 | <hacker12455> with wget it works | 08:49 |
| T42 | Yourshobhit was added by: Yourshobhit | 11:18 |
| T42 | <ankaos> https://github.com/enesutku07/android_kernel_samsung_msm8916/tree/sailfishos https://github.com/enesutku07/android_kernel_samsung_msm8916/tree/sailfishos @elros34 where is problem? | 12:38 |
| T42 | <elros34> problem with what? Did you make wlan working? Did you modprobe wifi module you found in /lib/modules/`uname -r`/? | 13:00 |
| T42 | <elros34> I am talking about xiaomi | 13:01 |
| T42 | <ankaos> @elros34 [problem with what? Did you make wlan working? …], I found the wlan. I change it. however, the problem persists. | 13:19 |
| T42 | <ankaos> @elros34 [problem with what? Did you make wlan working? …], los-14.1 not open. | 13:20 |
| T42 | <ankaos> I prepared the files. I am now waiting for the people who will improve it. | 13:21 |
| T42 | <elros34> please be more verbose, what happend when you type: modprobe 'you wlan module name'? | 13:32 |
| T42 | <ankaos> kernel say me wil6210 | 13:36 |
| T42 | <elros34> so, type: modprobe wil6210 | 13:36 |
| T42 | <ankaos> @elros34 [so, type: modprobe wil6210], okey. test this code. | 13:37 |
| T42 | <ankaos> I want to compile on my brother's device. he is using j5lte. I wonder if you can. | 13:38 |
| T42 | <ankaos> @ankaos [https://github.com/enesutku07/android_kernel_s …], @elros34 these are the files. | 13:52 |
| T42 | <ankaos> ı look los-16 kernel config. ı edit wifi line. | 18:15 |
| T42 | <ankaos> `Warning[05/26 18:50:33] : repo problem: nothing provides libbinder.so needed by` droid-config how fix? | 18:51 |
| rinigus | piggz: any pointers regarding fp? or you'd prefer to focus on it yourself as it starts to work out? | 19:06 |
| piggz | rinigus: open to help.... | 19:23 |
| piggz | rinigus: start by buiding https://github.com/piggz/biometryd/tree/sailfish | 19:24 |
| T42 | <ankaos> piggz: say problem. | 19:24 |
| piggz | i know the spec needs work, and needs split into a -devel package.... | 19:24 |
| rinigus | piggz: we don't have it at OBS? | 19:24 |
| piggz | so, atm when you install on device, you have some odd deps | 19:24 |
| piggz | not yet | 19:25 |
| piggz | maybe i can add it, one minute | 19:25 |
| rinigus | piggz: exactly, let's add at obs. | 19:25 |
| rinigus | (separate repo?) | 19:26 |
| piggz | rinigus: it needs the dbus-cpp from my home project | 19:29 |
| rinigus | looks from obs that it has to be in the ported device repo | 19:29 |
| rinigus | piggz ^ | 19:29 |
| piggz | yes, needs hybris-devel | 19:29 |
| piggz | rinigus: you also need to build a part in your android sdk | 19:30 |
| rinigus | piggz: which part of android-sdk? | 19:31 |
| piggz | the part to build your DHD | 19:31 |
| piggz | ie ubu chroot | 19:32 |
| rinigus | ok, what should be built there? | 19:32 |
| rinigus | https://github.com/erfanoabdi/biometryd/blob/xenial/android/hybris/biometry_fp_hidl_for_hybris.cpp ? | 19:32 |
| piggz | yes | 19:32 |
| piggz | rinigus: modue is called libbiometry_fp_api_32 | 19:33 |
| rinigus | piggz: `make libbiometry_fp_api_32` I presume. and then we need to somehow package/move it to device, right? | 19:34 |
| piggz | yup | 19:34 |
| piggz | its all manual atm | 19:34 |
| piggz | that should get you running biometryd on device | 19:34 |
| piggz | copy it to usual /usr/libexec/droid-hybris/system/lib/ | 19:35 |
| rinigus | piggz: `it` is biometryd and its produced by that module? | 19:36 |
| piggz | it is libbiometry_fp_api.so | 19:37 |
| rinigus | OK, I'll start then | 19:37 |
| piggz | biometryd is a normal linux application | 19:37 |
| rinigus | silly question: now, when we will get it up, then what? any idea how to hook it to sfos? | 19:38 |
| piggz | that is a bigger question | 19:38 |
| piggz | :D | 19:38 |
| piggz | so, running biomteryd will atleast let you test the FP | 19:39 |
| piggz | after that, my idea is to write a systemd service that implements the sailfish-fpd dbus protocol | 19:39 |
| piggz | as a backend, we could use biometryd, or, as erfan suggests, take the code from the android biometryd plugin and write our own | 19:40 |
| rinigus | piggz: ideally, we should make it so that others (nemo, for example) could use it. what's this sailfish-fpd protocol? | 19:40 |
| piggz | atm, for speed, im gonna try and use the biometryd qt interface | 19:40 |
| rinigus | piggz: what does that qt interface look like? how can it be hooked to unlocking of device? | 19:41 |
| rinigus | sorry for dragging with questions | 19:41 |
| piggz | sfos fp lockscreen talks to sailfish-fpd using dbus ... sailfish-fpd talks to sailfish-fpd-slave using a custom ipc (so its difficult to implement the slave) .... and the salve talks to android | 19:41 |
| piggz | so, easiest is to create a package the provides: sailfish-fpd, but uing our own daemon | 19:42 |
| piggz | i got a dbus-monitor of the protocol, and there isnt much to it | 19:42 |
| rinigus | OK, sounds good. if needed we can also open up lockscreen and add some new protocol. I'll start compiling | 19:43 |
| piggz | rinigus: i think its basically https://bpa.st/4Q2A | 19:43 |
| piggz | and #define SERVICE_NAME "org.sailfishos.fingerprint1" | 19:44 |
| piggz | so, if you have an XA2 device handy, and dbus montoring output may be useful :) | 19:44 |
| rinigus | nope, no XA2 - only my own ported XZ2 (just a letter difference). | 19:45 |
| rinigus | btw, completely unrelated - my car managed to get phonebook out from my phone while I was using it today. looks like SFOS 3.3.0.x had some improvements in BT stack. earlier it wasn't able to do so... | 19:47 |
| piggz | i thought it was 3.3 that broke it! | 19:47 |
| piggz | i always could get the phonebook, and it stopped working in 3.3 ... there is some timing issue betwen bluez and ofono, not sure if its resolved yet | 19:48 |
| rinigus | it didn't connect immediately, had to reconnect the device. after that, very nice surprise | 19:49 |
| rinigus | piggz: https://build.merproject.org/package/live_build_log/home:rinigus:fp/biometryd/sailfish_latest_armv7hl/armv8el | 20:14 |
| rinigus | did not look happy regarding qt config | 20:14 |
| rinigus | piggz: I'll look into missing deps | 20:16 |
| piggz | rinigus: ta, it was just building locally so could have had things installed | 20:27 |
| rinigus | piggz: building now. if it builds, will send pr | 20:27 |
| piggz | rinigus: thanks, it needs a PR for the -devel seperation too ;) | 20:28 |
| rinigus | piggz: ooh, that can wait. unless its many GBs in storage | 20:29 |
| piggz | no, its tiny | 20:30 |
| rinigus | piggz: from api at https://bpa.st/4Q2A - how do you remove fingerprint? | 20:34 |
| rinigus | it did compile, but crossed some badness levels. will fix and make -devel as well | 20:36 |
| rinigus | piggz ^ | 20:36 |
| piggz | rinigus: there may be methods missing ... that dbus-monitor was taken while enrolling/unlocking | 20:52 |
| piggz | so, i am definitiely missing a lot of the strings used also | 20:53 |
| piggz | but, we have to reverse engineer it | 20:53 |
| rinigus | piggz: or make up our own. I have to finish for tonight, its late over here. will continue tomorrow. as it is, android bits are ready; obs is at https://build.merproject.org/project/show/home:rinigus:fp | 20:57 |
| rinigus | it required also process-cpp from mal's repo. decided to add it into the same obs build repo for simplicity in installation | 20:58 |
| rinigus | gn | 20:58 |
| piggz | rinigus: yeah, makes sense to have everything together | 21:08 |
| T42 | <edp_17> Hi guys. I am trying to create configs for cameras but getting errors: https://paste.ubuntu.com/p/Qjw6PFDWBY/ | 22:05 |
| T42 | <edp_17> Is this changed in hadk? | 22:06 |
| T42 | <edp_17> Or I did something wrong in kernel/sailfish? | 22:08 |
| T42 | <elros34> mk-cam-conf is not needed anymore | 22:16 |
| T42 | <edp_17> How can I get the conf files then? | 22:20 |
| T42 | <elros34> they are not needed | 22:24 |
| T42 | <edp_17> Okay. In settings/apps/camera the photo resolution is 16:9(?Mpix) and 4:3(8Mpix) for the back and 16:9(?Mpix) and 4:3(2Mpix) for the front. I guess the ?Mpix is wrong. How can I fix it? | 22:35 |
| T42 | <edp_17> In the past it was the conf file what fixed this. | 22:35 |
| T42 | <ankaos> @elros34 [they are not needed], https://paste.ubuntu.com/p/428fvVPzqm/ full log | 22:42 |
| T42 | <elros34> ? We seems can not communicate properly. I ask you to run modprobe but you provide me some logs without any context. This is going nowhere. I can not help you | 22:53 |
| T42 | <ankaos> sh-3.2# modprobe wil6210 | 22:57 |
| T42 | <ankaos> modprobe: FATAL: Module wil6210 not found in directory /lib/modules/3.18.113+ | 22:57 |
| T42 | <ankaos> sh-3.2# modprobe wlan | 22:57 |
| T42 | <ankaos> modprobe: FATAL: Module wlan not found in directory /lib/modules/3.18.113+ | 22:57 |
| T42 | <elros34> you said you have moule builtin, what uname -r and ls -alR /lib/modules/ shows? | 23:00 |
| T42 | <ankaos> sh-3.2# uname -r | 23:03 |
| T42 | <ankaos> 3.18.113+ | 23:03 |
| T42 | <ankaos> https://paste.ubuntu.com/p/FYS5926fmy/ | 23:04 |
| T42 | <elros34> hmm, does depmod -av help? Anything in dmesg after trying to modprobe? | 23:08 |
| T42 | <ankaos> sh-3.2# depmod -av | 23:17 |
| T42 | <ankaos> /lib/modules/3.18.113+/ufs_test.ko needs "test_iosched_unregister": /lib/modules/3.18.113+/test-iosched.ko | 23:17 |
| T42 | <ankaos> /lib/modules/3.18.113+/mmc_block_test.ko needs "test_iosched_unregister": /lib/modules/3.18.113+/test-iosched.ko | 23:17 |
| T42 | <ankaos> /lib/modules/3.18.113+/generic_bl.ko needs "devm_backlight_device_register": /lib/modules/3.18.113+/backlight.ko | 23:17 |
| T42 | <ankaos> sh-3.2# ls lib/modules/3.18.113+/ | 23:19 |
| T42 | <ankaos> ansi_cprng.ko diagchar.ko lcd.ko modules.alias.bin modules.dep modules.order modules.symbols.bin ufs_test.ko | 23:19 |
| T42 | <ankaos> backlight.ko evbug.ko mmc_block_test.ko modules.builtin modules.dep.bin modules.softdep sdcardfs.ko wil6210.ko | 23:19 |
| T42 | <ankaos> br_netfilter.ko generic_bl.ko modules.alias modules.builtin.bin modules.devname modules.symbols test-iosched.ko wlan.ko | 23:19 |
| T42 | <edp_17> @elros34 : Last time you recommended to stop pulseaudio service and start it in more verbose mode: pulseaudio -vvvv (+ params form /etc/sysconfig/pulseaudio". Here is what I got: https://paste.ubuntu.com/p/Fcsk3YHjKG/ | 23:20 |
| T42 | <edp_17> I think this is the issue: "Failed to load module "module-droid-card" (argument: "rate=48000"): initialization failed." | 23:21 |
| T42 | <edp_17> How should I found out the correct rate? | 23:21 |
| T42 | <elros34> read first line from pulseaudio | 23:22 |
| T42 | <edp_17> Sorry, I wasn't realized that I was root. Here the new one as nemo: https://paste.ubuntu.com/p/mcPz92R9KG/ | 23:23 |
| T42 | <edp_17> I stopped the service but it seems running. How can I gracefully stop it? | 23:25 |
| T42 | <elros34> service is in /usr/lib/systemd so use systemctl-user to stop it | 23:27 |
| T42 | <edp_17> Thank you. Here is the more verbose log: https://paste.ubuntu.com/p/j2FtgBzFrd/ | 23:29 |
| T42 | <elros34> maybe this: Failed to parse configuration from /system/etc/audio_policy.conf | 23:31 |
| T42 | <edp_17> At line 48 it says: "Failed to parse configuration from /system/etc/audio_policy_configuration.xml" | 23:34 |
| T42 | <edp_17> I don't have such an xml file. | 23:34 |
| T42 | <edp_17> I see, line 46 above. | 23:34 |
| T42 | <elros34> but for sure you have audio_policy.conf | 23:35 |
| T42 | <edp_17> Yes, I have that in /system/etc/ | 23:36 |
| T42 | <edp_17> And what about this: Failed to open module "module-droid-glue" | 23:36 |
| T42 | <elros34> I guess you did not build it? | 23:37 |
| T42 | <edp_17> Is it audioflingerglue? | 23:38 |
| T42 | <edp_17> I did built Gstreamer, Camera and BT stuff. I followed the hadk. | 23:39 |
| T42 | <edp_17> (broadcom-bluetooth and bluetooth-rfkill-event) | 23:39 |
| T42 | <edp_17> The pulseaudio-modules-droid-glue was part of the camera section and I did build it. | 23:41 |
| T42 | <elros34> it is loaded after droid module so maybe that is the reason it fials | 23:41 |
| T42 | <elros34> fails | 23:41 |
| T42 | <edp_17> The zypper says on device that pulseaudio-modules-droid-glue is installed. | 23:43 |
| T42 | <elros34> like I said focus on droid module first | 23:43 |
| T42 | <edp_17> All three are installed: pulseaudio-modules-droid, pulseaudio-modules-droid-common and pulseaudio-modules-droid-glue | 23:45 |
| T42 | <elros34> try to remove that AUDIO_OUTPUT_FLAG_MULTI_CH to see if that helps | 23:52 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!