| *** ChanServ sets mode: +v T4 | 02:04 | |
| *** ChanServ sets mode: +v T4 | 08:07 | |
| *** phdeswer_ is now known as phdeswer | 11:19 | |
| *** ChanServ sets mode: +v T4 | 14:22 | |
| vknecht | so I have a hall/lid sensor on /dev/input/event8 : https://pastebin.com/kB7rM56w ... howto instruct MCE to use it ? | 16:20 |
|---|---|---|
| vknecht | SW_LID mapping doesn't seem appropriate, since there are two different keys | 16:20 |
| vknecht | (and doesn't seem to work, using KEY_00fb) | 16:20 |
| vknecht | I see lidsensoradaptor-evdev in https://git.merproject.org/mer-core/sensorfw/blob/master/config/sensord-ubuntu.conf but not sure it's right or how to configure it | 16:21 |
| * vknecht tentatively pings spiiroin :) | 16:25 | |
| spiiroin | vknecht: so, you get "KEY_00fb" press + release on lid close, and KEY_WEIBO press + release on lid open? which would be yet another novel approach probably requiring some code changes ... | 17:38 |
| vknecht | spiiroin, yes it seems so ; I was reading https://github.com/vknecht/android_kernel_alcatel_msm8916/blob/hybris-14.1/drivers/input/keyboard/gpio_keys.c wondering if I could inject SW_LID in there | 17:42 |
| vknecht | but maybe better to manage that in MCE ? | 17:42 |
| spiiroin | vknecht: unless the driver is doing something odd, it probably would be easier to tweak it to use SW_LID than trying to make mce understand a bit odd convention | 17:54 |
| spiiroin | I can take a peek at it a bit later | 17:55 |
| spiiroin | vknecht: not as simple as I hoped, but.. the keycodes used in kernel are KEY_UNLOCK_COVER & KEY_LOCK_LED_COVER | 18:10 |
| spiiroin | added to input device capabilities around line 720, and the key-press + release is around line 409 | 18:11 |
| spiiroin | minimal but a bit dirty solution might be to replace the two input_set_capability(input, EV_KEY, ...) calls with single input_set_capability(input, EV_SW, SW_LID) | 18:16 |
| spiiroin | and the input_event + input_sync + input_event triplet with input_event(input, EV_SW, SW_LID, (hall_key == KEY_LOCK_LED_COVER)) | 18:17 |
| spiiroin | pulled out of hat and untested etc ;-) | 18:19 |
| taixzo | mal: any news on matissewifi? | 18:29 |
| mal | taixzo: nope, I have been trying to rest a bit | 18:42 |
| mal | taixzo: maybe I should just give you some image because otherwise it might take forever before I'm satisfied it's good enough | 18:48 |
| r0kk3rz | just send it already :P | 18:49 |
| *** Fred_ is now known as Guest31616 | 18:52 | |
| taixzo | mal: I would be fine with that - I don't need perfection, just good enough for me to test my app on it | 19:20 |
| mal | taixzo: well the problem I have is the UI scaling, I find everything a bit too large so it might affect app testing | 19:29 |
| mal | one of the reasons for problems is the quite low resolution compared to the display size | 19:33 |
| *** ChanServ sets mode: +v T4 | 20:11 | |
| piggz | mal: Nokius_: Amazfish is now abstracted away from the Bip....feel free to contribute new devices! https://github.com/piggz/harbour-amazfish/commit/7546f9ad1c4e0a383c65b2d5545087205ea9f526 | 22:44 |
| mal | piggz: nice work | 22:45 |
| mal | hopefully I'll have some time to investigate my watch again | 22:46 |
| piggz | mal: more to to, as always, but there are interfaces to implement, and the gui shouldnt depend on the device | 22:46 |
| piggz | new devices in here ps :) https://github.com/piggz/harbour-amazfish/tree/master/src/devices | 22:47 |
| mal | ok | 22:47 |
| piggz | mal: does sfos3 hel your pairing? | 22:49 |
| piggz | newer kernel on X? | 22:50 |
| mal | I doubt the issue is kernel, I think it's just some stupid security feature of the watch | 22:52 |
| T4 | Emac1999 was removed by: Emac1999 | 23:53 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!