| T42 | <edp_17> @elros34 : I wasn't sure, so I tried both (KERNEL and KERNELS). The result is the same, after reboot permission still system:system | 06:54 |
|---|---|---|
| T42 | <elros34> If we assume rule works (you could try to write some tmp file in that rule to be sure) then something overwrites this behavior. Have you checked init*rc files in /system or /vendor? | 06:56 |
| T42 | <edp_17> Yes, I've checked /system and /vendor, there is no init*rc file in there. I'll try that you suggested (tmp file). | 07:01 |
| T42 | <elros34> here is service file I used to debug race on my device together with systemd-analyse plot > boot.svg , there is probably better way to do this..: https://pastebin.com/33FgGtK5. | 07:03 |
| T42 | <edp_17> Thank you! | 07:04 |
| T42 | <edp_17> tmp file wasn't created, so that udev rule didn't make effect. | 07:07 |
| T42 | <elros34> so use that service file, it will generate flood of messages but at least you will be sure what events you got | 07:07 |
| T42 | <edp_17> Does it matter how I name the rule? Is that number at the end of name is an order to run it? | 07:08 |
| T42 | <edp_17> I'll use the service now. | 07:08 |
| T42 | <elros34> I think name shouldn't matter for your case, you are not overriding any other rule | 07:10 |
| T42 | <edp_17> I see, thanks. | 07:15 |
| T42 | <edp_17> udev_monitor.log : https://paste.ubuntu.com/p/N2NWGBxgBF/ | 07:15 |
| T42 | <edp_17> I also used systemd-analyze plot > /boot.svg | 07:18 |
| T42 | <elros34> see timed_output appears somewhere at 24s, maybe try only: SUBSYSTEM=="timed_output", TAG+="systemd" and then RUN commands. After that generate plot | 07:20 |
| T42 | <edp_17> There is another one around 22s | 07:22 |
| T42 | <elros34> ah I see you use 102- in file name, IFAIK this will not work like you expect, please use 99 for example | 07:30 |
| T42 | <edp_17> Do you know why doesn't work with file name 102-? | 07:39 |
| T42 | <edp_17> I also have other rules with name 100-* and 100-* and they do work. | 07:39 |
| T42 | <elros34> I meant that AFAIK they are not parsed after 99-rules but before, this can cause issues but most likely not in your case | 07:40 |
| T42 | <edp_17> Ah, ok, I see. Good to know when I add a new rule. :) | 07:41 |
| T42 | <elros34> so did you generate plot after adding systemd tag? | 07:42 |
| T42 | <edp_17> No, it was before. Since then I am renaming the rules for getting the tmp file generated. No luck so far. | 07:46 |
| T42 | <edp_17> Yeah, it doesn't matter if I named the rules 99*, they do not generate files. | 07:47 |
| T42 | <edp_17> These are the rules: https://paste.ubuntu.com/p/Md4D3NWQ6Q/ | 07:49 |
| T42 | <elros34> so even with simple rule like: 'SUBSYSTEM=="timed_output", TAG+="systemd"' you do not have anything in : systemctl | grep timed? THis is not shell I am not sure redirection will work > | 07:50 |
| T42 | <elros34> echo also might not work, must be /bin/echo. That is why I told you to add systemd tag then it would be obvious in plot or systemct output | 07:51 |
| T42 | <edp_17> Oh, I see. this is systemctl | grep timed : https://paste.ubuntu.com/p/RdXV99gm5M/ | 07:52 |
| T42 | <edp_17> So, files cannot be created this way. how about using touch? Would that work better? | 07:53 |
| T42 | <elros34> touch is always the best way for debugging. So if there was no sys-devices-virtual-timed_output-vibrator.device previously then rule works, please show now plit | 07:54 |
| T42 | <elros34> plot* | 07:54 |
| T42 | <edp_17> It is 190kb, don't think I can upload it to paste.ubuntu. How can I share it with you? | 07:56 |
| T42 | <edp_17> I'll load them up to github. Give me a second. | 07:58 |
| T42 | <elros34> ok I need to go so please compare plot with ngfd start time. You should see when devices-virtual-timed_output-vibrator.device appears and with some systemctl-user magic you need to find out when ngfd starts | 07:59 |
| T42 | <edp_17> No worries. Thanks for your help. | 08:01 |
| T42 | <edp_17> I've uploaded the plots, boot.svg before TAG+ was added and boot2.svg after. https://github.com/edp17/systemd-analyze-plot | 08:02 |
| T42 | <edp_17> sys-devices-virtual-timed_output-vibrator.device appears a bit before 25s | 08:07 |
| T42 | <edp_17> Once you back please tell me about the systemctl-user magic you were referring to. :) | 08:07 |
| T42 | <elros34> so looks like it's way before user session (and ngfd) starts so make sure rules works and change permissions | 08:38 |
| T42 | <edp_17> Interestingly, rules does work as when added touch, it generated the tmp file. However, it doesn't change the permission to system:input or something else changes that back to system:system later. | 09:43 |
| T42 | <edp_17> I have this rule but permission remains system:system after reboot: | 09:43 |
| T42 | <edp_17> SUBSYSTEM=="timed_output", TAG+="systemd", RUN+="/bin/chown system:input /sys/class/timed_output/vibrator/enable" | 09:43 |
| T42 | <nephros> You could try to replace the RUN+= with a script in which you do more stuff like test for existence, ls -l etc, and log it to a file. | 10:09 |
| T42 | <edp_17> @nephros : Thanks for the idea. | 11:07 |
| T42 | <edp_17> It seems something changes permission to system:system later in the start process. | 11:07 |
| T42 | <edp_17> I've created a script that logs the permission, changes it to system:input, then logs it again. In that 99* rule, instead of the chmod I run this script. After boot I've found two permissions in the log file. | 11:10 |
| T42 | <edp_17> 1. root:root | 11:10 |
| T42 | <edp_17> 2. system:input | 11:10 |
| T42 | <edp_17> So, the rule (and script worked). However, if I check the permission now, it is system:system. | 11:10 |
| T42 | <edp_17> So, there is something else that runs after that rule and changes the permission. | 11:11 |
| T42 | <Spidey24Z> Could you please send a package? (re @nephros: I have built qpa-sur...) | 11:17 |
| T42 | <Spidey24Z> @elros34 I patch MCE but didn't help | 11:17 |
| T42 | <nephros> Can't build at the moment, there might be one on OBS though. Let me check. (re @Spidey24Z: Could you please sen...) | 11:39 |
| T42 | <nephros> https://build.sailfishos.org/package/show/home:nephros:hw:sony:tuba/qt5-qpa-surfaceflinger-plugin no idea if it is useful though | 11:41 |
| T42 | <edp_17> Okay, I've found the way to restart all those services. :) I know it's a hack but will come back to it later. | 13:25 |
| T42 | <edp_17> Can I get a little help with routing audio to the headset? | 13:25 |
| T42 | <edp_17> I have /dev/input/event18 which is "apq8064-tabla-snd-card Headset Jack" and also have /sys/class/switch/h2w/state that reacts on headset plugged in. | 13:26 |
| T42 | <edp_17> However, any of them defined in /etc/ohm/plugins.d/accessories.ini, audio is not routed to headset. :( | 13:26 |
| T42 | <Spidey24Z> thank i install it but it didn't work (re @nephros: https://build.sailfi...) | 13:28 |
| T42 | <Spidey24Z> thanks i install it but it didn't work (edited) (re @nephros: https://build.sailfi...) | 13:28 |
| T42 | <Spidey24Z> when i run minimer it segfault | 13:29 |
| T42 | <Spidey24Z> EGL_PLATFORM=hwcomposer /usr/lib64/qt5/bin/qmlscene -platform surfaceflinger /minimer/main.qml | 13:29 |
| T42 | <Spidey24Z> cannot locate symbol "_ZN7android21SurfaceComposerClient17getBuiltInDisplayEi" referenced by "/usr/libexec/droid-hybris/system/lib64/libsf_compat_layer.so"... | 13:30 |
| T42 | <Spidey24Z> Segmentation fault (core dumped) | 13:30 |
| Thaodan | I think we mean init/*.rc | 13:36 |
| Thaodan | e.g. find /vendor /system -name \*.rc -exec grep -H <term> {} \; | 13:36 |
| dcaliste | Hello porters, if I would like to add a new HAL interface to a manifest, so it can be picked up by hwservicemanager in aliendalvik, which file should I touch ? | 14:28 |
| dcaliste | I tried to add it under /host_vendor/etc/vintf/manifest/foo.xml but after aliendalvik restart, it seems to not be picked up by hwservicemanager that complains that foo cannot be find in manifest or framework… | 14:29 |
| Thaodan | dcaliste: why do you want to do that? | 16:14 |
| T42 | <elros34> @Spidey24Z you must build it yourself in platform sdk | 16:56 |
| T42 | <elros34> @edp_17 you could mask droid-hal-init/user@10000 then start only droid-hal-init. If that change permission to system:system then it must be *rc file (or script executed by *rc) somewhere on device | 16:58 |
| Thaodan | why are you using the qpa-surfaceflinger? | 17:11 |
| T42 | <Spidey24Z> do i need a full source for building it ? (re @elros34: @edp_17 you could ma...) | 17:13 |
| T42 | <elros34> at least droid-hal/lihybris/... rpms | 17:14 |
| T42 | <elros34> @edp_17 ah don't you use some waydroid or something like that which starts and change permissions? | 17:22 |
| T42 | <edp_17> @elros34 : Not yet. On this install I haven't installed waydroid. I've tested that on an older image. Altghough, lxc container and a desktop debian in it is installed. | 20:28 |
| T42 | <edp_17> But I start that guest os manually, so there is no service like in waydroid. | 20:29 |
| T42 | <edp_17> I'd like to use waydroid but first want to fix some stuff like audio, bluetooth, camera and video playing/recording. | 20:31 |
| T42 | <Umeaman> Building hybris-hal and droid-media fails with this error: https://pst.klgrth.io/paste/7hxvx | 22:35 |
| T42 | <Umeaman> As you can see I'm fully up-to-date otherwise. | 22:35 |
| T42 | <Umeaman> Any workaround? | 22:36 |
| T42 | <Umeaman> I know I can remove projects from my manifest, but it's not my manifest the problem lies in. | 22:38 |
| Thaodan | You can remove projects in device.xml since it is sourced as local manifet | 23:01 |
| Thaodan | Sony does the same | 23:01 |
| Thaodan | E.g. see here: | 23:02 |
| Thaodan | https://github.com/sonyxperiadev/local_manifests/blob/master/untracked.xml | 23:02 |
| T42 | <Umeaman> Thaodan: Shouldn't that be in the HADK then? | 23:05 |
| T42 | <Umeaman> In case someone gets the same error. | 23:05 |
| Thaodan | It's more of an edge case | 23:09 |
| Thaodan | Also it's more an Android issue than a SailfishOS issue. | 23:10 |
| T42 | <Umeaman> Right. | 23:14 |
| T42 | <Umeaman> What about the patch step? It's removed from the HADK...... isn't it mandatory to do the patches regardless of make and model? | 23:15 |
| Thaodan | what patch step, do you mean hybris patches? | 23:31 |
| T42 | <Umeaman> Thaodan: Yes. | 23:46 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!