| *** ChanServ sets mode: +v T4 | 02:25 | |
| T4 | Prashantpp was added by: Prashantpp | 03:27 |
|---|---|---|
| jusa | piggz: what's with BT? :) | 08:00 |
| T4 | <adampigg> Jusa, bt keyboard presses are doiubled | 08:05 |
| T4 | <adampigg> Ive got fw lpading fixed, and can pair | 08:06 |
| T4 | <adampigg> But struggling with pairing my headphones...but, keyboard first | 08:06 |
| *** ChanServ sets mode: +v T4 | 08:46 | |
| jusa | ok | 08:55 |
| T4 | <adampigg> Jusa, i guess no ideas? :( | 08:59 |
| jusa | what happens when trying to pair, logs from bluetoothd, pulseaudio? | 09:00 |
| jusa | for keyboard no ideas (other than are there any logs :)) | 09:01 |
| T4 | <adampigg> I had a btmon log, but i posted it in #bluez! | 09:51 |
| T4 | <adampigg> (Document) http://149.202.119.142:9090/LuziJbr6w5.txt | 09:54 |
| T4 | <adampigg> Jusa, can you see that? It shows keyboard connecting, and pressing qwerty | 09:55 |
| r0kk3rz | @adampigg so it doubles each keypress? | 09:58 |
| T4 | <adampigg> Yes | 09:58 |
| r0kk3rz | i'll have to take a btmon log of mine for you | 09:58 |
| T4 | <adampigg> Which makes typing a pain :D | 09:58 |
| r0kk3rz | i'm wondering whether these messages should be there `a1 01 00 00 00 00 00 00 00 00` | 09:59 |
| r0kk3rz | but i guess maybe thats keyrelease | 09:59 |
| T4 | <adampigg> Trying evdev trace... | 10:00 |
| T4 | <adampigg> I dont think evdev trace shows 2 presses | 10:01 |
| T4 | <adampigg> Hang on | 10:01 |
| T4 | <adampigg> (Document) http://149.202.119.142:9090/r5fGXKJn4q.txt | 10:02 |
| T4 | <adampigg> What u make of that? | 10:02 |
| r0kk3rz | yeah its definitely a kernel driver issue | 10:05 |
| r0kk3rz | i think the bt side is fine | 10:05 |
| T4 | <adampigg> If i had my usb otg,, id try a real keyboard | 10:07 |
| r0kk3rz | the issue seems to be whatever piece of code translates the bt HID protocol into keyboard signals | 10:09 |
| T4 | <adampigg> What did evdev look like to you? | 10:09 |
| T4 | <adampigg> Did you see doubles? | 10:10 |
| r0kk3rz | yes | 10:10 |
| r0kk3rz | but there isnt doubles in the btmon log | 10:10 |
| r0kk3rz | hmm maybe they arent doubles actually | 10:10 |
| r0kk3rz | 0x010/KEY_Q - 1 = press, 0x010/KEY_Q - 0 = release? | 10:11 |
| T4 | <adampigg> Yes, thats what i thought | 10:15 |
| T4 | <adampigg> No doubles.in evdev, so, wft!!!! | 10:16 |
| r0kk3rz | must be higher up then | 10:33 |
| T4 | <adampigg> That would be where...qt? Wayland? | 10:34 |
| r0kk3rz | libinput im guessing | 10:34 |
| r0kk3rz | maybe spiiroin knows | 10:39 |
| spiiroin | r0kk3rz: 1st though ... both scancode (or stte?) and key id are sent - could it be possible that both of those get mapped into separate key presses? | 10:48 |
| spiiroin | I do not recall ever seeing MSC_SCAN events, so no idea how those might get handled ... | 10:49 |
| T4 | <adampigg> I cant seen any libinput packages ... There iz a trace tool.for that apparntly | 10:50 |
| r0kk3rz | yeah i'll grab some logs from my keyboard later to compare against | 10:51 |
| T4 | <adampigg> Ill.do the same later with a real kb | 10:52 |
| T4 | <adampigg> Doing some reading, msc events should maybe only be generated for unknown keys | 11:30 |
| r0kk3rz | what i was just reading says they're the raw scan codes | 11:32 |
| r0kk3rz | so idk, see what my keyboard does i guess | 11:32 |
| T4 | <adampigg> This worked on tbj | 11:32 |
| T4 | <adampigg> But on mido, i cant get it to connect! | 11:33 |
| T4 | <adampigg> What kernel did tbj have? | 11:33 |
| *** OhYash1 is now known as ohyash | 11:33 | |
| T4 | <Prashantpp> Hi. | 11:34 |
| r0kk3rz | @adampigg which kernel are you using? | 11:41 |
| r0kk3rz | an idea is to steal the hid driver from the sony kernel - https://github.com/r0kk3rz/android_kernel_sony_msm/blob/hybris-sony-aosp-6.0.1_r80-20170902/drivers/hid/hid-input.c | 11:42 |
| T4 | <adampigg> 3.14.79 | 11:53 |
| T4 | <adampigg> Good plan | 11:53 |
| Umeaboy | Hi! | 13:42 |
| Umeaboy | Merry Christmas to everyone. | 13:42 |
| Umeaboy | If I take this guide made for the Xperia X model and adapt it to my XZ Premium, https://sailfishos.org/wiki/Sailfish_X_Build_and_Flash I need a hybris-sony-aosp-7.1.2_r36-20181220 branch on https://github.com/mer-hybris/android | 13:45 |
| Umeaboy | Who can add it? | 13:45 |
| r0kk3rz | you cant use aosp8? | 13:46 |
| Umeaboy | Nope. Memory to low. | 13:47 |
| Umeaboy | 8 GB. | 13:47 |
| Umeaboy | Need 16 GB. | 13:47 |
| r0kk3rz | huh? | 13:47 |
| Umeaboy | Yeah, the build fails due to lack of memory if I use AOSP 8.1.. | 13:48 |
| r0kk3rz | geez, thats a bit rough | 13:48 |
| Umeaboy | Plus there is no Oreo branch for my device. | 13:48 |
| T4 | <adampigg> R0kk3rz, there is a subtle difference between the 2 versions of hidinput.c regarding creating the ev_msc event | 13:55 |
| T4 | <adampigg> Def worth trying | 13:55 |
| T4 | <adampigg> Actually, im looking at a newer kernel | 13:55 |
| T4 | <adampigg> I might just comment out those events! | 13:55 |
| T4 | <adampigg> Yours is the same | 13:55 |
| mal | Umeaboy: what? I assume that XZ premium is codenamed maple which has android 8 branch in sony repos | 13:56 |
| r0kk3rz | @adampigg: yeah maybe grab from torvalds is a cleaner idea | 13:56 |
| Umeaboy | mal: It is, but the problem is that android.googlesource.com refuses to initialize even with the --no-clone-bundle flag. | 14:03 |
| Umeaboy | So, unless you have an alternative location to initialize the repo from I can't use the 8.1.0 branch for mer-hybris. | 14:04 |
| mal | which branch? | 14:05 |
| *** ChanServ sets mode: +v T4 | 14:05 | |
| Umeaboy | repo init -u https://android.googlesource.com/platform/manifest -b android-7.1.2_r36 --no-clone-bundle and many more. | 14:06 |
| mal | Umeaboy: you did the usual repo init and then normal repo sync or some extra for repo sync? | 14:06 |
| mal | Umeaboy: I still think it would much easier to use 8.1 since you would have the repo ready and things like bluetooth would be easier | 14:06 |
| Umeaboy | It's the repo init that fails. I wanted to try to build Oreo for maple, but no luck. Initializing the Lineage cm-14.1 branch works fine though. | 14:07 |
| mal | Umeaboy: does the hybris build fail with memory issue or the aosp build? | 14:07 |
| Umeaboy | Haven't tried the hybris build yet, but I'll do that later tonight. | 14:07 |
| mal | I have aosp sources for 8.1 so I can build an image for any sony aosp 8.1 device | 14:08 |
| Umeaboy | If I do the guide to initialize android-7.1.2_r36 and above it halts before it's finished. | 14:10 |
| mal | I still think doing 7.1 is a bad idea | 14:10 |
| Umeaboy | https://pastebin.com/pTKCeGUA | 14:10 |
| mal | how about you try the hybris build for 8.1 for your device and I'll build you the aosp images needed? | 14:11 |
| Umeaboy | I even used the --no-clone-bundle command and it seemed to work at the start, but it doesn't finish. | 14:11 |
| Umeaboy | Sure. | 14:12 |
| Umeaboy | I'll do that when I get home later tonight though. | 14:12 |
| Umeaboy | Take care. | 14:12 |
| piggz | r0kk3rz: that confirms it ... pluggin in my usb-otg hub + keyboard ..... each press is doubled! | 18:11 |
| piggz | which begs the question .... WTF?? | 18:12 |
| r0kk3rz | piggz: what did you use to trace input event for the log? | 18:14 |
| piggz | evdev_trace | 18:14 |
| r0kk3rz | ok, i get lots of msc_scan messages as well | 18:16 |
| r0kk3rz | the output seems identical to yours | 18:16 |
| r0kk3rz | but im pretty sure a usb keyboard would go through the same hid-input driver | 18:16 |
| piggz | r0kk3rz: so, i say again, wtf! :D | 18:38 |
| piggz | @eugenio_g7 can you try a usb keyboard on your tab? | 18:38 |
| piggz | how do we have similar evdev traces, but I get double keypresses | 18:39 |
| r0kk3rz | ummm | 18:41 |
| r0kk3rz | good question | 18:41 |
| piggz | r0kk3rz: afaict we dont use libinput | 18:41 |
| piggz | atleast i couldnt see any packages | 18:42 |
| r0kk3rz | i always though that was ike *the* wayland thing | 18:44 |
| r0kk3rz | but perhaps not | 18:44 |
| piggz | r0kk3rz: i have a module loaded called ....hid.....ko | 18:45 |
| piggz | infact lots of hid....ko modules | 18:55 |
| r0kk3rz | lots? | 18:55 |
| piggz | r0kk3rz: for various sensors | 18:56 |
| piggz | and a sensor hub | 18:56 |
| piggz | potentially, a lot going through the hd system | 18:56 |
| piggz | r0kk3rz: https://bpaste.net/show/6c2ad3ae29f4 | 18:57 |
| piggz | r0kk3rz: not modules .... i renamed the module dir, rebooted, no modules loaded, and its the same | 19:09 |
| piggz | r0kk3rz: an idea ... i only traced one event device ... i wonder if i trace them all, i will get inputs from more than one.... | 19:13 |
| r0kk3rz | worth a shot at least | 19:13 |
| r0kk3rz | i just did evdev_tract -t | 19:13 |
| piggz | i did the bt device specifically | 19:14 |
| piggz | nope, not that | 19:15 |
| piggz | /dev/input/event7: 1545333332.830 - 0x04/EV_MSC - 0x004/MSC_SCAN - 458772 | 19:15 |
| piggz | /dev/input/event7: 1545333332.830 - 0x01/EV_KEY - 0x010/KEY_Q - 1 | 19:15 |
| piggz | /dev/input/event7: 1545333332.830 - 0x00/EV_SYN - 0x000/SYN_REPORT - 0 | 19:16 |
| piggz | /dev/input/event7: 1545333332.933 - 0x04/EV_MSC - 0x004/MSC_SCAN - 458772 | 19:16 |
| piggz | /dev/input/event7: 1545333332.933 - 0x01/EV_KEY - 0x010/KEY_Q - 0 | 19:16 |
| piggz | /dev/input/event7: 1545333332.933 - 0x00/EV_SYN - 0x000/SYN_REPORT - 0 | 19:16 |
| piggz | one keypress of Q | 19:16 |
| r0kk3rz | seems reasonable | 19:16 |
| piggz | but still the same 2 presses in apps! | 19:17 |
| piggz | hmmm | 19:18 |
| r0kk3rz | i think we need to know what the higher parts of the stack are | 19:26 |
| piggz | r0kk3rz: im thinking the lipstick options evdev* plugins ? | 19:27 |
| piggz | r0kk3rz: yup, ive fixed it | 19:27 |
| piggz | but, i need to figure out how/why! | 19:28 |
| r0kk3rz | \o/ | 19:28 |
| piggz | yay, ive got my BT keyboard setup again | 19:28 |
| piggz | r0kk3rz: so, i commentoued out the lipstick options a-la | 19:29 |
| piggz | #LIPSTICK_OPTIONS="-plugin evdev:/dev/input/event3 -plugin evdevkeyboard:keymap=/usr/share/qt5/keymaps/droid.qmap" | 19:29 |
| piggz | and it works.... | 19:29 |
| piggz | strangely, the touchscreen still works | 19:30 |
| piggz | i did try the evdevtouch plugin again, and that gave the same result with double-keys and bad TS | 19:30 |
| piggz | i guess I should try it with the evdev plugin, and without the evdevkeyboard plugin | 19:31 |
| piggz | and videversa | 19:31 |
| r0kk3rz | huh | 19:32 |
| r0kk3rz | well its a lead anyway | 19:32 |
| r0kk3rz | it must be listening on the event twice, which sounds weird | 19:33 |
| r0kk3rz | i wonder why its not doing that for me | 19:33 |
| piggz | r0kk3rz: what re your options? | 19:33 |
| piggz | r0kk3rz: ok, so it also works without the evdevkeyboard plugin loaded | 19:34 |
| r0kk3rz | hang on | 19:34 |
| r0kk3rz | mine says evdevtouch, yours says evdev | 19:34 |
| piggz | yes, that is becuase of my screen | 19:35 |
| r0kk3rz | oh ok | 19:35 |
| piggz | do you have the keyboard one? | 19:35 |
| r0kk3rz | https://github.com/r0kk3rz/droid-config-scorpion_windy/blob/hybris-aosp6/sparse/var/lib/environment/compositor/droid-hal-device.conf#L6 | 19:35 |
| piggz | r0kk3rz: right, its the evdevkeyboard plugin | 19:37 |
| piggz | with just that plugin loaded, it fails | 19:38 |
| piggz | so, i guess for the time being, i'll go with no options set as it all seems to work | 19:38 |
| piggz | who would have a view on whats going on there? | 19:39 |
| piggz | jusa: BT audio problem https://bpaste.net/show/25b3dc355502 | 19:46 |
| piggz | this shows my scanning, trying to pair with "Plattan ADV Wireless" ... the first 2 times fail, the third pairs, but then it fails to connect | 19:47 |
| piggz | r0kk3rz: and harbour-taskswitcher is working | 20:15 |
| r0kk3rz | thats good! | 20:18 |
| *** ChanServ sets mode: +v T4 | 20:54 | |
| T4 | <adampigg> Jusa, mybe headphone connection problem is cos we dont have PA running yet | 20:56 |
| r0kk3rz | yeah you need pulse | 21:13 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!