xreactx[m]__ | mal: "FAILED: /home/vincent/hadk/out/target/product/guacamole/vendor.img " was this the vendor issue you mentioned? | 00:24 |
---|---|---|
xreactx[m]__ | https://pastebin.com/StdqdmYP | 00:52 |
T42 | <adampigg> Vknecht, just read about the bug, unfortunate | 06:05 |
masha11 | Some sensors do not work on my device griffin: accelerometer, gyroscope,light, proximity. Can I turn them on somehow? test_sensors shows 29 sensors: https://pastebin.com/hNAuA5d1 | 08:35 |
T42 | <birdzhang> For example: https://github.com/mer-hybris/droid-config-f5121/blob/master/sparse/usr/share/csd/settings.d/hw-settings.ini | 08:38 |
T42 | <srLuxint> Does anyone know how to take advantage of Bluetooth vendor-specific HCI commands with BlueZ? Is there any generic mechanism for it? Seems like bluedroid does. | 09:36 |
mal | MSameer: which android base? | 09:47 |
mal | oops | 09:47 |
mal | masha11: ^ | 09:47 |
masha11 | mal: 14.1 | 09:53 |
masha11 | 7.1 (cm 14.1) | 09:56 |
T42 | <birdzhang> mal: "/bin/bash: line 0: test: too many arguments" when build hybris-16.0, it's from https://github.com/libhybris/libhybris/blob/master/compat/input/Android.mk#L26 | 10:06 |
T42 | <birdzhang> and we need this pr https://github.com/mer-hybris/hybris-boot/pull/169/files | 10:06 |
mal | how was that not merged yet | 10:12 |
mal | @birdzhang I assume both are cause by same kind of issue, in first case here https://github.com/libhybris/libhybris/blob/master/compat/Android.common.mk | 10:16 |
mal | @elros34 the droid-hal-device udev PR you made has some issue, I tested it and one of the cpu paths didn't get correct permissions and group | 10:19 |
mal | @birdzhang is that libhybris issue critical i.e. does build fail? | 10:27 |
T42 | <birdzhang> mal: not critical, build pass | 10:28 |
masha11 | @birdzhang thank, I'll try | 10:28 |
T42 | <adampigg> mal: there is never a great rush to merge changes in hybris repos! | 10:30 |
mal | @birdzhang ok, I can then fix that in my upcoming libhybris cleanup PR | 10:33 |
mal | @adampigg merged :) | 10:44 |
T42 | <adampigg> mal, any plans to make hybris-boot device independant, so there is no need to modify fixup-mountpoints? it seems to be like that function should move out to some device repo | 10:46 |
mal | @adampigg I think there was talk about that earlier, need to check if the code still exists | 10:47 |
mal | @adampigg often those PRs are just forgotten if they are not critical | 10:47 |
masha11 | birdzhang: thanks. I added it more: https://github.com/wdehoog/droid-config-bacon/commit/a32611102157c1a60d4dfe7de867fb2e3021f948. Sensors have earned. Only proximity sensor in Messwerk is crossed out. | 11:05 |
mal | masha11: are you missing the hw-settings.ini, you shouldn't need that override if hw-settings.ini is correct | 11:28 |
mal | masha11: something like this https://github.com/mer-hybris/droid-config-sony-ganges-pie/blob/master/sparse/usr/share/csd/settings.d/10-hw-settings.ini | 11:29 |
mal | adapt values to match your device | 11:29 |
mal | ah, missed that you already got a similar link | 11:30 |
mal | @srLuxint what are you trying to do with those? | 11:30 |
masha11 | mal: yes i added hw-settings.ini. all sensors work! | 11:36 |
mal | masha11: good, can you remove the other file and do those still work? | 11:38 |
masha11 | mal: in my case, the sensors only work when both files (hw-settings.ini and 60-sensor-selection-oeverrides.conf) are present. | 12:05 |
mal | masha11: that is very odd, the latter really shouldn't be needed | 12:05 |
mal | what do you see in logs in both cases, any difference? | 12:06 |
mal | journalctl is the relevant one | 12:06 |
masha11 | then maybe my sensors are unstable ...I’ll check now. | 12:07 |
mal | or some timing issue? | 12:10 |
masha11 | mal: I don’t understand yet. https://pastebin.com/ujnXXzp3 (with 60-sensor-...conf), https://pastebin.com/DBNnhzP0 (without). | 12:17 |
mal | @adampigg did you have v4l codecs working on latte or pinephone dev kit? | 12:32 |
masha11 | mal: However, with this file sometimes there are no working sensors. But after 1-3 reboots they work again. Then the problem may be in something else. | 12:38 |
mal | masha11: logs :) maybe try https://github.com/mlehtima/droid-config-fp2-sibon/commit/4825b6f5a8d52eb61b4bdff97bf7e01bbaa6c5be | 12:39 |
T42 | <srLuxint> mal: Nevermind. I've already found the solution. Basically my question was about bt hw address. And it can be dealed with hci_stp.c under drivers/bluetooth in inoi t8 (?) kernel. | 12:56 |
masha11 | mal: I added sensors-delay-hack.service. After the first reboot, the sensors did not work https://pastebin.com/x8CQ16Nd .After the second - they worked https://pastebin.com/C0u5uLfx. After 3,4,5,6 reboots do not work again :(https://pastebin.com/fUDVDA1M | 13:01 |
mal | masha11: not full logs, use "journalctl -b" | 13:03 |
mal | masha11: or better "journalctl -alb --no-pager" | 13:03 |
T42 | <adampigg> mal: v4l camera capture is somewhat working on the pinephone | 13:04 |
T42 | <adampigg> @dylanvanassche is the expert there | 13:04 |
T42 | <DylanVanAssche> @adampigg mal: v4l works until the level of GStreamer. Nothing further, the Jolla Camera app and QtMultimedia isn't being nice to the v4l camera :( | 13:05 |
mal | @DylanVanAssche ok, needs some invetigation then | 13:06 |
mal | @DylanVanAssche do you have v4l enabled in qtmultimedia? | 13:07 |
T42 | <DylanVanAssche> mal: This where I got stuck: https://wiki.merproject.org/wiki/Adaptations/PinePhone64#Cameras | 13:07 |
T42 | <DylanVanAssche> I didn't modified QtMultimedia though | 13:07 |
T42 | <DylanVanAssche> The selfie.jpg is the last thing I did. | 13:08 |
mal | @DylanVanAssche we have v4l disabled in qtmultimedia so no wonder it doesn't work | 13:10 |
abranson | i think it made the jolla1 crash? | 13:10 |
T42 | <DylanVanAssche> mal: Well :P that's definitely an issue :O | 13:10 |
mal | abranson: we could enable it but package it separately? | 13:10 |
T42 | <DylanVanAssche> mal: We can package it for the native repo? | 13:11 |
mal | @DylanVanAssche yes, for now, but in theory it could be in mer-core if packaged properly | 13:11 |
abranson | probably easiest to fork it for now, get it working, then see about a merge | 13:12 |
mal | yes, that was my idea | 13:12 |
abranson | think there might be more to do in there... | 13:12 |
T42 | <DylanVanAssche> Yes that would be the goal ofcourse, but for now native repo seems sufficient. | 13:12 |
mal | @DylanVanAssche so if you try to enable it then package it separately to a new package in the same spec | 13:12 |
abranson | there's quite a lot of reliance on droidcamsrc in there i think | 13:13 |
mal | abranson: yes, but those backends are separate afaik | 13:13 |
T42 | <DylanVanAssche> abranson: True | 13:13 |
mal | abranson: which place do you mean? | 13:13 |
T42 | <DylanVanAssche> mal: That's an option, something like qtmultimedia-v4l or whatever. No idea when I will have time for it, but will do | 13:14 |
abranson | mal: thinking about all of those element properties | 13:14 |
mal | @DylanVanAssche https://git.merproject.org/mer-core/qtmultimedia/blob/mer-5.6/rpm/qtmultimedia.spec#L92 something like that maybe | 13:15 |
mal | @DylanVanAssche hmm, there is v4l mediacapture stuff here https://git.merproject.org/mer-core/qtmultimedia/blob/mer-5.6/rpm/qtmultimedia.spec#L101 | 13:16 |
mal | but still needs to be enabled probably | 13:16 |
T42 | <DylanVanAssche> mal: okay :) hmmm maybe that's what need, just enabling it :D | 13:16 |
T42 | <DylanVanAssche> Now that the sensors are working on the PineTab, only the back camera is left. Sound is broken (missing Kernel stuff, nothing about SFOS) | 13:17 |
masha11 | mal: log with working sensors: https://paste.ubuntu.com/p/4hgvdB8q37/ , not working: https://pastebin.com/2F7QYeVj | 13:17 |
mal | @DylanVanAssche https://git.merproject.org/mer-core/qtmultimedia/blob/mer-5.6/rpm/qtmultimedia.spec#L159 | 13:26 |
T42 | <DylanVanAssche> mal: Noted :) | 13:27 |
T42 | <DylanVanAssche> Thanks! | 13:27 |
vknecht | @adampigg: unfortunate, indeed ; maybe it's worth trying with QVideoProbe instead... | 14:17 |
T42 | <adampigg> hoping for a release tonight if mal gives the green light to the rotation pr, and that version will go to harbour | 14:58 |
T42 | <adampigg> then onto the pinetab | 14:58 |
T42 | <adampigg> will assist in the v4l packagng | 14:58 |
mal | @adampigg did you check the latest comments in the PR? | 14:58 |
T42 | <adampigg> mal, i resolved some this morning on the bus, any since then? | 14:59 |
vknecht | if you release tonight, wouldn't the actual snapshot PR be good enough ? | 14:59 |
vknecht | (for now) | 15:00 |
T42 | <adampigg> i havnt tried it myself yet, id like to store it up, doesnt mean another release cant happen soon | 15:00 |
mal | @adampigg ok, I missed the email it seems | 15:00 |
vknecht | ok :-) | 15:00 |
vknecht | slider is better | 15:09 |
T42 | <adampigg> yeah, fixed that | 15:14 |
jellypony | Hello everyone! Flashed hybris-boot, got no gui, only telnet. (nearly anything else not working too :C) | 15:45 |
jellypony | init.log: https://pastebin.com/GcG9XvHr | 15:45 |
jellypony | journalctl: https://pastebin.com/eE2zWYcN | 15:45 |
jellypony | Am I right it is mounting issue? | 15:45 |
vknecht | jellypony, droid-hal-init failing, and lipstick crashing... hmm, guess you should check straggler files, and try test_hwcomposer after touching /init_enter_debug2 | 16:40 |
vknecht | for better journal, also set persistent logging | 16:40 |
piggz | hmm, is there anything to raise at the community meeting ..... | 18:00 |
piggz | mal: fingerprint sensor support for community devices? | 18:00 |
mal | piggz: that would be nice | 18:00 |
piggz | ive raised it before, and the answer has always been, we'll work on it or such, and nothing coes | 18:01 |
mal | but still some poking might help | 18:02 |
rinigus | piggz: maybe late to raise anything now. topics are supposed to be there 1 day in advance. although, maybe they can reply regarding fingerprint support... | 18:05 |
vknecht | and... « <Jaymzz> as we don't usually announce things on the IRC meeting :P » | 18:10 |
vknecht | (quoted from http://merproject.org/meetings/mer-meeting/2019/mer-meeting.2019-09-19-08.00.log.html ) | 18:11 |
vknecht | so wait for blog post ? :-) | 18:12 |
piggz | its gotta be said, the way meeting topics are organised is shit ... what are you supposed to do, add another comment to the topic on tjc ? | 18:16 |
piggz | there has to be a better way | 18:16 |
vknecht | maybe porter' community could self-organize better, and have a collective voice of its own, its own blog and communication channel ? | 18:18 |
vknecht | *channels, not depreciating this channel, which is vital :-) | 18:19 |
rinigus | piggz: you have to change main post, its wiki | 18:21 |
vknecht | eg. thinking about maybe newsletter & website about all community ported devices, etc. | 18:21 |
piggz | rinigus: oh, so people edit the wiki, and then the edits are deleted? | 18:23 |
piggz | i cant see any proposals there | 18:23 |
piggz | its just odd! | 18:23 |
rinigus | vknecht: not sure we even manage to keep mer wiki up to date. That would be a start... | 18:24 |
piggz | mal: that shortest direction change was worth it | 18:25 |
rinigus | piggz: there is a template that you copy below current questions and fill in. After meeting they will cancel old questions | 18:25 |
vknecht | not untrue, but this is individual effort (ie. each porter manages its device wikipage/xda thread); I'm talking about collective communication | 18:26 |
mal | piggz: I know :) | 18:27 |
rinigus | vknecht: would be good to have it. But I guess its mainly waiting for someone to make it | 18:29 |
vknecht | rinigus, probably users would like/support such an effort and help, so it may not even be such a chore, after all, for us ; most important is to give initial impulse :-) | 18:29 |
vknecht | and have a will to do so | 18:30 |
rinigus | Maybe. Have to go now... :) | 18:30 |
vknecht | :-) | 18:30 |
vknecht | have sweet dreams of pies :-D | 18:30 |
piggz | have we ever discussed the white browser rendering on native ports? | 18:31 |
piggz | that could be a topic... | 18:31 |
piggz | @eugenio_g7, @dylanvanassche | 18:31 |
piggz | mal: camera pr good and tested? | 18:36 |
mal | piggz: need to make quick test of the latest version, those are the same changes I had but still need to do a test | 18:37 |
T42 | <eugenio_g7> piggz: I think we did, but nothing was made out of it IIRC | 18:39 |
vknecht | made a build of the rotation PR branch, might be interesting to get feedback of f5121 users : http://repo.merproject.org/obs//nemo:/devel:/hw:/TCL:/idol3/sailfish_latest_armv7hl/armv7hl/harbour-advanced-camera-0.5.1+rotation.20191016064352.11.g2da90ce-1.35.1.jolla.armv7hl.rpm | 18:40 |
piggz | Done ... 0.6.0 is tagged on github, rpms uplaoded to openrepos, and submitted to harbour qa! | 19:11 |
piggz | i forgot we added the share featre too this reelase! | 19:11 |
vknecht | guess people will notice :-) | 19:23 |
vknecht | rebased, will have to test and check tho... also had a few comments, guess will have to handle multiple /media/sdcard/ subdirs, and allow choice with a combobox or something ; or just allow to pick a chosen dir | 19:44 |
vknecht | not sure we really want to depend on jolla camera settings ? | 19:45 |
piggz | is there a command line way to connect to an access point? | 19:59 |
mal | piggz: maybe using iw? | 20:01 |
mal | or connmanctl if that is installed? | 20:02 |
piggz | yay, got the pinetab online | 20:23 |
T42 | Akatsu %lastname% was added by: Akatsu %lastname% | 20:33 |
xreactx[m]__ | Any work arounds for getting the vendor.img to build? | 23:19 |
jellypony | vknecht: test_hwcomposer: test_hwcomposer.cpp:174: int main(int, char**): Assertion `err == 0' failed. | 23:21 |
jellypony | Aborted | 23:21 |
jellypony | the error is "droid-hal-init.service: Main process exited, code=exited, status=6/NOTCONFIGURED" | 23:21 |
jellypony | But I don't know what that means >:c | 23:22 |
jellypony | systemctl status output: https://pastebin.com/Af8iin9d | 23:50 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!