| Mister_Magister | mal: mAAAAAAAAAAAAAAaaaaaaaaaaaaaaal, did you have issues with bluetooth reconnecting on android 10? like you can pair the device, turn bt (or device) off/on and you cannot connect to paired device? | 17:01 |
|---|---|---|
| mal | no that I remember | 17:03 |
| Mister_Magister | aaaaaaaaaaaaaaaaaaaaaaaaany idea how to fix it? xd | 17:03 |
| mal | stop writing like that, looks annoying | 17:04 |
| mal | check debug logs | 17:04 |
| Mister_Magister | sorry | 17:04 |
| Mister_Magister | no fun allowed :P which log precisely, the usual 3? | 17:04 |
| mal | I mean bluez debug output | 17:05 |
| mal | looks for anything pairing related in there | 17:06 |
| Mister_Magister | oki | 17:08 |
| T42 | <edp_17> If light sensor doesn't work, where should I investigate? | 17:19 |
| mal | do other sensors work? | 17:22 |
| T42 | <edp_17> Yes. | 17:23 |
| mal | anything in sensorfwd logs? | 17:23 |
| T42 | <edp_17> evdev_trace says: light senor is /dev/input/event8 | 17:23 |
| mal | usually sensors go through and side | 17:24 |
| mal | *android side | 17:24 |
| T42 | <edp_17> Should I just run that sensorfwd? Like: https://paste.ubuntu.com/p/QF93MQ4mHS/ | 17:24 |
| mal | you have it running already probably, and it probably takes some parameters, check the systemd service file of it | 17:26 |
| mal | and we use devel-su in sailfish, not sudo | 17:26 |
| T42 | <edp_17> Should I have something for light sensor in /etc/sensorfw/primaryuse.conf? https://paste.ubuntu.com/p/xgqJnw5C63/ | 17:29 |
| mal | it's als | 17:34 |
| mal | ambient light sensor = als | 17:35 |
| T42 | <edp_17> Thanks | 17:37 |
| Mister_Magister | mal: @elros34 So @notkit said to run the test app directly not via lipstick and it is aware of events so… somewhere there's a break | 23:15 |
| Mister_Magister | but ig we figured out its not plugin nor application | 23:20 |
| Mister_Magister | so either lipstick or wayland | 23:20 |
| Mister_Magister | it would seem that lipstick absolutely ignores tablet events https://github.com/sailfishos/lipstick/blob/master/src/compositor/lipstickcompositorwindow.cpp#L256 | 23:24 |
| Mister_Magister | so I don't know what the guy telling me that they'reusing evdevtablet was smoking, but he's high as… | 23:24 |
| T42 | <NotKit> it might be it produces normal touch events on touchscreens somehow? | 23:24 |
| mal | piggz is using evdevtablet https://github.com/sailfish-on-dontbeevil/droid-config-pinephone/blob/master/sparse/var/lib/environment/compositor/droid-hal-device.conf | 23:25 |
| Mister_Magister | yeah | 23:25 |
| Mister_Magister | and it has no way of working | 23:25 |
| Mister_Magister | https://invent.kde.org/thesamesam/qtbase/-/blob/v5.15.5-lts-lgpl/src/platformsupport/input/evdevtablet/qevdevtablethandler.cpp#L153 it has hardcoded tablet event | 23:26 |
| Mister_Magister | and nothing in lipstick handles tablet event | 23:26 |
| Mister_Magister | what kind of magic is that | 23:26 |
| mal | so implement it, should not be too difficult | 23:26 |
| Mister_Magister | i'm incredibly confused | 23:26 |
| Mister_Magister | I will | 23:26 |
| Mister_Magister | I just want to keep you updated and also complain | 23:26 |
| mal | see if it work after adding support in that function you linked | 23:27 |
| Mister_Magister | i don't understand what magic are they doing that it works for piggz but i doubt it works | 23:27 |
| Mister_Magister | mal: i will I will | 23:27 |
| mal | I wonder how mouse events are handled | 23:27 |
| mal | since those work afaik | 23:27 |
| Mister_Magister | oh right… wait… wtf | 23:27 |
| mal | that has things like mouseMoveEvent not sure where those are called | 23:28 |
| Mister_Magister | mal: but normally evdevmouse is not enabled | 23:28 |
| Mister_Magister | I think | 23:28 |
| Mister_Magister | ye by default you're getting evdevtouch and evdev keyboard | 23:29 |
| Mister_Magister | so mouse has to be handled via wayland or something | 23:29 |
| Mister_Magister | mind that i have 0 clue what I'm talking about | 23:29 |
| Mister_Magister | mal: oh, there's like mouse event method below so they must be called somehow, maybe thanks to installEventFilter | 23:30 |
| Mister_Magister | but we're getting somewhere and i got idea of what i need to do thanks mal @notkit | 23:32 |
| mal | https://github.com/sailfishos/qtwayland/blob/mer-5.6/src/compositor/compositor_api/qwaylandsurfaceitem.h#L93 | 23:32 |
| Mister_Magister | so i was right saying they're handled by wayland? | 23:33 |
| Mister_Magister | my madman mumbling was true for once | 23:34 |
| mal | what kind of events did you see in the test app? | 23:37 |
| Mister_Magister | mal: well the display wasn't working but I have seen in output the app reacting, most notably D] unknown:0 - near QTabletEvent::PointerType(Pen) | 23:39 |
| Mister_Magister | what's interesting, pressing buttons doesn't change the type | 23:40 |
| Mister_Magister | oh wait | 23:41 |
| Mister_Magister | https://invent.kde.org/thesamesam/qtbase/-/blob/v5.15.5-lts-lgpl/src/platformsupport/input/evdevtablet/qevdevtablethandler.cpp#L113 | 23:41 |
| Mister_Magister | if it sends touch, that should work no issue | 23:41 |
| Mister_Magister | but mine sends BTN_TOOL_PEN | 23:42 |
| Mister_Magister | maybe thats why it doesn't work for me | 23:42 |
| Mister_Magister | i'm purely speculating again | 23:42 |
| Mister_Magister | let me do cheeky evdevtrace | 23:42 |
| Mister_Magister | https://paste.opensuse.org/pastes/e13f6aa83b4f | 23:43 |
| mal | you have BTN_DIGI in there | 23:45 |
| mal | and BTN_TOUCH | 23:45 |
| mal | what is that BTN_DIGI even, no idea | 23:46 |
| Mister_Magister | oh ye touch is there too | 23:46 |
| Mister_Magister | mal: so clicking buttons doesn't seem to send any events, and BTN_DIGI i think is "BTN_TOOL_* value 1 -> proximity enter" as per comment | 23:48 |
| Mister_Magister | because it first appear (pen getting near) and then touch switches between 0/1 depending if im touching or not | 23:48 |
| mal | ok | 23:49 |
| Mister_Magister | from linux docs For example, a pen tablet may set BTN_TOOL_PEN to 1 and BTN_TOUCH to 0 while the pen is hovering over but not touching the tablet surface | 23:50 |
| Mister_Magister | aaand if piggz's touchpanel is sending tablet events, he won't ever get hovering cause… you can't detect hovering finger yet | 23:50 |
| Mister_Magister | I cound for example, modify kernel driver to stop sending the tool events | 23:51 |
| Mister_Magister | but thats not really the solution as i'm not sure if pressure would be taken into account | 23:51 |
| Mister_Magister | I'll modify lipstick and see how it goes | 23:52 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!