| T42 | <maffeen> https://del.dog/emecymejib.txt What should I do? | 06:05 |
|---|---|---|
| T42 | <edp_17> @Parallellhistory : If you are interested in harbour-containers, you can find some info here: http://talk.maemo.org/showthread.php?t=101080 | 08:30 |
| *** monich_ is now known as monich | 10:33 | |
| sambiak | Hello, is porting sailfish OS to a device that only supports android 10 is impossible ? | 13:07 |
| mal | at the moment android 10 support is not yet ready | 13:07 |
| T42 | <Anton %lastname%> Is it possible to port native vibrator to 4.9 kernel? I'm not sure how to debug ngfd | 13:12 |
| T42 | <Anton %lastname%> Or, perhaps, droid one's fine? | 13:12 |
| mal | vibrator should work fine on 4.9 kernel | 13:17 |
| mal | it has worked on several devices already | 13:17 |
| mal | droid-vibrator really shouldn't be used | 13:17 |
| T42 | <Anton %lastname%> qt5-feedback-haptics isn't used across the default system, am I right? | 13:20 |
| T42 | <Anton %lastname%> There's no ffmemless across /dev/input/event*, as evdev_trace reports, and it says something about every one of events, perhaps my kernel config is incorrect? | 13:28 |
| mal | most devices don't support ffmemless | 13:28 |
| mal | so do you have native vibrator packages installed? | 13:28 |
| T42 | <Anton %lastname%> At the moment, no. Working on it. | 13:29 |
| mal | I mean ngfd-plugin-native-vibrator and qt5-feedback-haptics-native-vibrator | 13:30 |
| T42 | <Anton %lastname%> I have them both | 13:33 |
| mal | so anything in logs? | 13:46 |
| mal | I assume you are using hybris-16.0? when did you update hybris-patches the last time? | 13:46 |
| T42 | <Anton %lastname%> This wednesday, I believe, I checked out the whole hadk folder | 13:48 |
| T42 | <Anton %lastname%> logcat screams that: https://pastebin.com/MhRiGN85 | 13:49 |
| mal | native vibrator has nothing to do with android side | 13:50 |
| T42 | <Anton %lastname%> dmesg has references to vendor.vibrator-1.0 constantly dying | 13:50 |
| mal | it uses directly the sysfs interface | 13:50 |
| mal | journalctl is more relevant | 13:50 |
| mal | or dmesg | 13:51 |
| T42 | <Anton %lastname%> there's "ngfd[4742]: libprofile: session bus connection requested while blocked" right before hwcomposer | 13:52 |
| mal | try what happens if you do "systemctl restart ngfd" | 14:00 |
| T42 | <Anton %lastname%> That's fun, there's no such service | 14:00 |
| T42 | <Anton %lastname%> Systemctl status, however, reports starting it as a part of user@100000.service | 14:01 |
| T42 | <elros34> use systemctl-user | 14:02 |
| mal | yes, forgot it was a user service | 14:02 |
| T42 | <Anton %lastname%> restarts and runs fine | 14:03 |
| T42 | <Anton %lastname%> How should I test it though? | 14:03 |
| T42 | <Anton %lastname%> Perhaps it is working?? | 14:03 |
| mal | there is the components app which has feedback testing possibility | 14:04 |
| T42 | <Anton %lastname%> That means there's no vibration then. At least my sanity is still in place | 14:06 |
| mal | can you manually control vibrator in sysfs | 14:07 |
| mal | either in /sys/class/timed_output/vibrator/enable or under /sys/class/leds/vibrator/ | 14:08 |
| mal | in latter case you first need to write a value to duration and then 1 to activate | 14:10 |
| mal | you should also check the permissions of those | 14:10 |
| T42 | <Anton %lastname%> There are none of those | 14:10 |
| T42 | <Anton %lastname%> My kernel is not configured properly then? | 14:11 |
| mal | what device is that? | 14:12 |
| T42 | <Anton %lastname%> motorola moto g7, river | 14:13 |
| mal | I assume vibrator worked in android? | 14:14 |
| T42 | <Anton %lastname%> Yep, one of the best phones for lineage os | 14:15 |
| mal | do you see any firmware loading issues in dmesg or journalctl? | 14:15 |
| T42 | <Anton %lastname%> Other than logcat spamming, because I turned android support for vibrator, no | 14:16 |
| mal | that seems to have aw869x vibrator based on device repo, check that it has that driver enabled in kernel | 14:16 |
| T42 | <Anton %lastname%> It just so happens, that I turned it off right before getting here | 14:19 |
| T42 | <Anton %lastname%> Building it now | 14:19 |
| mal | CONFIG_AW869X_HAPTIC=y that is in lineage defconfig at least | 14:20 |
| T42 | <Anton %lastname%> Exactly | 14:20 |
| T42 | <Anton %lastname%> I've had a bad read from hadk and hadk-faq | 14:20 |
| mal | hmm, where did you see anything like that in those? | 14:21 |
| T42 | <Anton %lastname%> All this ffmemless and driver adapting stuff just somehow flipped a switch somewhere | 14:21 |
| mal | ok | 14:22 |
| mal | ffmemless is very rare now | 14:22 |
| T42 | <elros34> it has 16kB memory so no memless bridge:) | 14:22 |
| T42 | <Anton %lastname%> It's the only way, according to hadk and hadk-faq | 14:23 |
| mal | but pattern templates have the native vibrator which makes it the default | 14:26 |
| mal | the ffmemless is mentioned as an optional thing if supported | 14:26 |
| mal | faq even says " you need a kernel haptics driver that supports a memless interface " | 14:27 |
| T42 | <Anton %lastname%> I read it as "If you don't want to use droid-vibrator, you better prepare for writing memless haptics driver yourself", especially considering point 1 | 14:28 |
| mal | hopefully it will work now | 14:30 |
| mal | did the dummy_netd help with mobile data? | 14:30 |
| T42 | <Anton %lastname%> dummy_netd made everything perfect | 14:33 |
| mal | good | 14:33 |
| mal | do you have any broken features left? | 14:33 |
| T42 | <Anton %lastname%> Just vibrator | 14:33 |
| T42 | <Anton %lastname%> Booted with the new kernel, there is /sys/class/leds/vibrator now, and it works, ngfd, still not so much | 14:34 |
| T42 | <Anton %lastname%> Okay, I figured out how to make vibration work, it involved setting permissions to /sys/class/led/vibrator/ contents. I'll add that to udev sparse file tomorrow, as well as play with some configs. After that, the system looks like it will be ready for release | 19:14 |
| T42 | <elros34> are you sure you have this patch applied? https://github.com/mer-hybris/hybris-patches/blob/hybris-sony-aosp-pie/system/core/0040-hybris-Allow-input-group-to-use-vibrator.patch | 19:18 |
| mal | I did ask about that earlier | 19:20 |
| T42 | <Anton %lastname%> the init.rc file in out/target/product/*/init.rc has it | 19:21 |
| mal | does the init.rc on device have it? | 19:21 |
| xmn | got to say sailfish looks to be running very nicely on the pinephone. So thanks to whoever has been working on that. | 19:23 |
| T42 | <Anton %lastname%> init.rc on device has it too | 19:24 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!