| T42 | <edp_17> @elros: Does it matter which bluez I use 4 or 5? What's the difference and the benefit using one of them over the other. Which one is suggested? Thank you. | 00:24 |
|---|---|---|
| T42 | <elros34> @edp_17 I think you should use what everybody else use so bluez 5 unless you have old kernel (I think <=3.4). Also bluetooth-rfkill-event instead these udev hacks I see in your repo. I told you that you should not run time consuming scripts in udev rules. | 01:21 |
| T42 | <elros34> <=3.4) | 01:22 |
| T42 | <elros34> Oh and remove these udev rulles and use bluetooth-rfkill-event | 01:23 |
| T42 | <edp_17> Well, currently I am using bluez4 because I thought with that I could make the bluetooth work. I was wrong, so I go back and try with bluez5. In the meantime I got totally lost in rild, ofono, ril_subscription and related stuff but couldn't work out why rild is crashing. 😔 Without help I don't have the knowledge to solve this. | 01:26 |
| T42 | <edp_17> Using bluez5 will make any difference regarding rild and ofono? | 01:26 |
| T42 | <edp_17> Thank you for your response by the way! | 01:27 |
| T42 | <elros34> no, I cant see conection between bluetooth and radio | 01:28 |
| T42 | <edp_17> That is good news. Thanks. | 01:28 |
| T42 | <elros34> btw don't add tmp, installroot, documentation.list. They are dynamic and created when you build package | 01:31 |
| T42 | <edp_17> Somehow I was able to get an output from '/usr/lib/ofono/test/list-modems' but I can't remember what I changed in ril_subscription and since the command doesn't give me anything. | 01:32 |
| T42 | <edp_17> Okay. Now it is too late for me, I barely can see. So, thank you and good night. | 01:34 |
| T42 | <elros34> see ya | 01:34 |
| *** kimmoli_ is now known as kimmoli | 04:32 | |
| rinigus | piggz: morning! Can you please tag also test app? | 05:37 |
| rinigus | Maybe later we can have some more user oriented app name and polish bit ui. As it will probably be used as main fp entry point on my port. | 05:40 |
| rinigus | piggz: do you have fp test app icon as svg? So we could use it for cover of the app | 05:41 |
| T42 | <Verevka86> (Photo, 720x1280) https://irc.thaodan.de/.imgstore/BjkF1BL2Jw.png | 06:02 |
| T42 | <Verevka86> @adampigg @rinigus Big thanks 🤝 | 06:02 |
| rinigus | @Verevka86: enjoy! | 06:20 |
| rinigus | piggz: I will make few smaller changes in test app | 06:23 |
| T42 | <adampigg> Rinigus, will add svg to repo | 06:48 |
| rinigus | @adampigg: I'll probably submit PR soon, no need to release before that | 06:48 |
| T42 | <adampigg> Sure... No need to release before waking up either | 06:49 |
| piggz | rinigus: test app looks good | 08:13 |
| piggz | rinigus: you still need the svg? | 08:14 |
| rinigus | piggz: not necessary, but maybe good to have in the sources. if you have it | 08:15 |
| piggz | i do.... | 08:15 |
| rinigus | piggz: thanks! | 08:16 |
| piggz | rinigus: here you go sailfish-fpd-community-test.svg | 08:19 |
| piggz | perhaps we should p.s.a? | 08:19 |
| rinigus | piggz: yes, now all tagged, should be ready for p.s.a | 08:20 |
| rinigus | please do | 08:21 |
| piggz | PSA: To all community porters. If you want to bring fingerprint support to your device, please try https://github.com/piggz/sailfish-fpd-community. See myself or rinigus for help/advice. Requires android 8+ base. PRs welcome, this a community project. | 08:24 |
| deathmist | for OBS I assume you just drop droid-biometry-fp RPM in your droid-hal packaging and call it a day? :p | 09:32 |
| deathmist | also the init rc file (https://github.com/piggz/sailfish-fpd-community/pull/12#issuecomment-636517230) from yesterday shouldn't be needed anymore, right? | 09:36 |
| piggz | deathmist: correct, the file is not needed now | 09:41 |
| piggz | deathmist: and yes for the rpm, just like the other local build ones | 09:42 |
| piggz | jusa: hi, i have an mtk device, running audiosystem-passthrough, audiosystem-passthrough-dummy-af, pulseaudio-modules-droid-hidl .... on calls, i can hear other side, but other side cant hear me, any suggestions? | 10:10 |
| deathmist | piggz: everything seems to work perfectly so far :) I'll make a new CI image and test that as well before making an announcement on the port XDA page, thanks for your work on this! | 11:32 |
| T42 | <edp_17> Hi all, I have a question and a problem. | 11:34 |
| T42 | <edp_17> I have switched to bluez5 as I was advised. | 11:35 |
| T42 | <edp_17> But when I tried to install the earlier generated broadcom-bluetooth rpm, I got a message "requires bluez-libs" which is not installed indeed. | 11:36 |
| T42 | <edp_17> Then I thought I needed to rebuild broadcom-bluetooth and bluetooth-rfkill-event packages so I tried in Platform. | 11:36 |
| T42 | <edp_17> But when I ran "rpm/dhd/helpers/build_packages.sh --mw=https://github.com/mer-hybris/broadcom-bluetooth -s rpm/broadcom-bluetooth.spec", I got "bluez-libs-devel is needed by broadcom-bluetooth-1.0.4-1.armv7hl" | 11:37 |
| T42 | <玉宸 %lastname%> Fwd from Gavin %lastname%: saw this one is quite interesting, just watch and can get free bitcoin, anyone interested,can you use my referral code, hhh;https://www.okex.com/academy/en/earn-free-bitcoin-while-staying-home?channelFlag=ACECK2501477 | 11:38 |
| T42 | <edp_17> Then I tried to install the "bluez-libs-devel" but got "Problem: bluez-libs-devel-4.101+git77-1.4.1.jolla.armv7hl requires bluez-libs = 4.101+git77, but this requirement cannot be provided not installable providers: bluez-libs-4.101+git77-1.4.1.jolla.armv7hl[jolla]" and a 3 option to remove some packages or break the current installati | 11:40 |
| T42 | on or do not install at all. | 11:40 |
| T42 | <edp_17> What am I missing? I thought for bluez5, I still need the broadcom-bluetooth and bluetooth-rfkill-event packages. | 11:41 |
| deathmist | anyone else experienced the call UI getting stuck? I just made a call and couldn't close it until the other end ended the call. I was nowhere near the proximity sensor and pressing the power button just kept revealing the UI and it blanked very quickly every time. this is SFOS 3.3 | 12:04 |
| ggabriel | deathmist: very rarely, and often while running some sort of heavy process like tracker | 12:28 |
| deathmist | oh that could actually be it, I just rebooted the phone before making the call and I also just reflashed it before that to test other things | 12:31 |
| rinigus | Deathmist: you also need to have sailfish-fpd-community among your packages at OBS. -test could be also of interest | 12:36 |
| rinigus | ... in addition to droid-biometry-fp | 12:36 |
| deathmist | rinigus: done that, they're all packaged and I'm about to test the new CI image :) | 12:37 |
| deathmist | existing users can upgrade with zypper ref && zypper dup and choosing option 1 to deinstall the conflicting encsfa packages | 12:37 |
| deathmist | https://github.com/sailfishos-oneplus5/droid-config-cheeseburger/commit/96ddb890bbbf86438d801b4da18c0ef7ad562d9a and obviously I added everything to meta-package / patterns | 12:38 |
| rinigus | I am testing now if we can get this uninstall automatically. let's see if it's possible | 12:39 |
| deathmist | https://i.imgur.com/ju6tpsx.png it came up with the FP dialog on initial setup and everything worked just fine ^^ | 12:43 |
| spiiroin | deathmist: " power button just kept revealing the UI and it blanked very quickly" = what p-sensor stuck to "covered" would cause - try triple-power-key-press | 12:43 |
| deathmist | ah, I'll have to remember that in the future if this happens again | 12:44 |
| T42 | <Verevka86> @deathmist [anyone else experienced the call UI getting st …], Work good Xiaomi Mi6 | 12:55 |
| T42 | <elros34> @edp_17 use bluez5 spec files (check PR) for both packages | 13:00 |
| piggz | deathmist: yeah, works on initial boot on volla too | 13:29 |
| T42 | <ankaos> my device is camera not found | 13:35 |
| T42 | <ankaos> how fix this problem? | 13:36 |
| piggz | spiiroin: could I map KEY_F11 to turn on screen? | 13:59 |
| piggz | rinigus: my FP also gives out key events when tap/swipt | 14:00 |
| piggz | s/swipe | 14:00 |
| piggz | thers that syntax to map keys, lemme see | 14:00 |
| piggz | spiiroin: reading what was suggested to rinigus, my FP gives a bunch of KEY_FXX events, not gesture events... what is the best course of action for wakeup when touching the FP sensor? | 14:21 |
| Kabouik | Do we have an equivalent of libdbus-1-dev under another name? | 14:26 |
| Kabouik | Not sure if libdbusaccess or libdbus-qeventloop-qt5 are the same thing | 14:26 |
| spiiroin | piggz: mapping to power key should work, but due to gemini pda ... KEY_ESC is sort of semi-power key too - you could try if one is better than other | 15:23 |
| spiiroin | piggz: the "semi" part = always wakes up screen, but does not blank unless mce is pretty sure UI is not using it for some other purposes | 15:25 |
| rinigus | piggz: it seems like double tap could be useful. not always detected though for me, but I am usually triggering pickup gesture when I pickup the phone (not related to fp) | 15:28 |
| piggz | rinigus: spiiroin: if i keep the finger on the sensor for a second, i fet key_f12 | 15:29 |
| piggz | s/key | 15:29 |
| piggz | spiiroin: so, i have this file but it doesnt work | 15:29 |
| piggz | sh-3.2# cat 99-fp-power.ini | 15:29 |
| piggz | [EVDEV] | 15:29 |
| piggz | KEY_F12=KEY_POWER | 15:29 |
| rinigus | that's probably hold | 15:29 |
| piggz | spiiroin: evdev says this about the device https://paste.mozilla.org/oxMUqrqe | 15:31 |
| piggz | rinigus: its easier to trigger that, than the others | 15:31 |
| piggz | a tap gives F11, but sometimes you get a swip, whcih is f1-4 | 15:32 |
| spiiroin | piggz: and you restarted mce after installing the ini-file? | 15:33 |
| piggz | spiiroin: yes | 15:33 |
| spiiroin | have you checked that you get down and up events? | 15:33 |
| piggz | spiiroin: https://paste.mozilla.org/J9Y60wc2 | 15:34 |
| spiiroin | piggz: looks ok | 15:36 |
| spiiroin | you could try something like: mce -Tq -levent-input.c:evin_iomon_keypress_cb -lpowerkey.c:* | 15:36 |
| piggz | did i get the syntax right | 15:36 |
| spiiroin | to see if something sane happens | 15:36 |
| piggz | nope, nothing there when i hold finger | 15:37 |
| piggz | how can i check if mce reads and process the config file? | 15:39 |
| piggz | and if mce even ready from event3? | 15:39 |
| spiiroin | evdev_trace -I -> shows what processes have files open | 15:40 |
| spiiroin | mce -Tq -levent-input.c:evin_iomon_device_add --auto-exit=0 | 15:40 |
| spiiroin | shows how mce classifies the input device | 15:40 |
| piggz | spiiroin: mce: T+0.000 N: event-input.c: evin_iomon_device_add(): /dev/input/event3: name='ff_key' type=USER ACTIVITY ONLY | 15:40 |
| spiiroin | doh | 15:41 |
| piggz | thatll do it :) | 15:41 |
| spiiroin | ... and obvious stuff. the ini is in /etc/mce dir? | 15:42 |
| piggz | sh-3.2# cat /etc/mce/99-fp-power.ini | 15:42 |
| piggz | [EVDEV] | 15:42 |
| piggz | KEY_F12=KEY_POWER | 15:42 |
| spiiroin | looks ok, and mapping should be used in probing already | 15:42 |
| spiiroin | I guess it slips through gaps | 15:46 |
| spiiroin | odd... need to stare code a bit | 15:47 |
| piggz | spiiroin: thanks v much | 15:47 |
| *** redj_ is now known as redj | 17:33 | |
| piggz | spiiroin: am I to assume that the device type is determined before the mappings are loaded which convert key_f12 to key_power | 18:48 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
