**** BEGIN LOGGING AT Tue Feb 26 02:59:57 2019 Feb 26 08:16:30 @JaMa so should i be building thud branch? Feb 26 08:16:47 Also i hope my 180GB disk space is enough for this... Feb 26 08:27:49 Morning! Feb 26 08:28:04 saidinesh5: For your tablet, do you use Android based build or direct linux with binary blobs? Feb 26 08:28:16 Because if direct linux with binary blobs, you don't need libhybris Feb 26 08:28:27 libhybris is used for talking to Android drivers Feb 26 08:29:00 @Herrie|Laptop o/ i am trying to use the meta-intel layer directly... and i was hoping to find out where/what is pulling in that libhybris dependency (currently it says qtwebengine.. but not sure how) Feb 26 08:29:47 saidinesh5: Let me have a look Feb 26 08:46:28 i did a grep for hybris in the raspberry pi layer and found nothing.. so wasn't sure if it was pulling it from shr or something Feb 26 08:50:03 saidinesh: I suspect it has to do with luneos-dev-package somehow Feb 26 08:50:10 Just I haven't found yet how exactly Feb 26 08:57:40 I think you might want to use luneos-dev-image Feb 26 08:57:56 That's what we do for the RPi devices: $ MACHINE=raspberrypi3 bb luneos-dev-image Feb 26 08:59:50 Tofe: I think we might need to add this back? https://github.com/webOS-ports/meta-webos-ports/blob/pyro/meta-luneos/recipes-core/packagegroups/packagegroup-luneos-extended.bb#L133 Feb 26 09:21:10 Herrie|Laptop: wll try it out Feb 26 09:30:00 WARNING: /src/LuneOS/webos-ports-env/webos-ports/meta-webos-ports/meta-luneos/recipes-webos/nyx-modules/nyx-modules.bb: Unable to get checksum for nyx-modules SRC_URI entry intel-corei7-64.cmake: file could not be found | ETA: 0:00:35 Feb 26 09:30:00 WARNING: /src/LuneOS/webos-ports-env/webos-ports/meta-webos-ports/meta-luneos/recipes-webos/luna-sysmgr-conf/luna-sysmgr-conf.bb: Unable to get checksum for luna-sysmgr-conf SRC_URI entry luna-platform.conf: file could not be found (need to fix these too..i think) Feb 26 09:30:22 Herrie|Laptop: ERROR: Required build target 'luneos-dev-image' has no buildable providers. Missing or unbuildable dependency chain was: ['luneos-dev-image', 'packagegroup-luneos-extended', 'qtwayland-plugins', 'libhybris'] Feb 26 09:30:50 i think i have to manually add some "provides" to my meta-intel-luneos i think Feb 26 09:30:59 maybe an xserver or wayland (preferably the latter) Feb 26 09:31:47 so once i am off work, will add stuff to that meta-intel-luneos i am making , that includes some file from meta-intel and adds more provides/removes Feb 26 09:42:52 Herrie|Laptop: oh, right, of course Feb 26 09:44:53 saidinesh5: could it be your intel tablet has an IGP directly supported by Mesa ? Feb 26 09:45:49 Tofe: I think so.. that's why i added teh meta-intel layer Feb 26 09:46:02 so need to figure out what's pulling in the libhybris and remove it Feb 26 09:49:24 libhybris should only be pulled if you specify that virtual/EGL is provided by libhybris in the machine conf file Feb 26 09:49:47 Ahhh Feb 26 09:51:00 There are other possibilities (like a mistake in luneos-dev-package definition), but this one is the main one Feb 26 09:51:11 https://git.yoctoproject.org/cgit.cgi/meta-intel/tree/conf/machine/intel-corei7-64.conf Feb 26 09:51:15 this is my machine conf Feb 26 09:57:32 Seems ok; you'll probably also need to add some things similar to qemu: https://github.com/webOS-ports/meta-webos-ports/blob/pyro/meta-luneos/recipes-core/packagegroups/packagegroup-luneos-extended.bb#L154 Feb 26 09:58:49 Just to be sure, did you already modify packagegroup-luneos-extended.bb ? In which case, what did you add/change ? Feb 26 10:03:30 saidinesh5: for stable and testing builds we use pyro Feb 26 10:03:35 i haven't modified anything except the BBLayers so far though Feb 26 10:03:41 just added the meta-intel to the bblayers Feb 26 10:03:49 rocko,sumo,thud,master aren't ready for end-users Feb 26 10:03:58 Ahh I see Feb 26 10:04:16 so it depends if you want to help with migration to newer Yocto or just get your intel support working in current pyro Feb 26 10:06:33 well once I have a working build, I can help with migration I think Feb 26 10:06:42 otherwise there will be too many unknowns right? Feb 26 10:10:49 right Feb 26 11:13:09 Tofe: Should I PR the change? Feb 26 12:17:12 Herrie|Laptop: it would be good to verify the build first, as it would basically mean revert that revert: https://github.com/webOS-ports/meta-webos-ports/commit/2e37a061d1ebb5772bcfbf28e9e1b2f329c31fe2 Feb 26 12:18:45 and to me it kind of indicates we might be forgetting something here :p Feb 26 13:00:05 Tofe: Well you said you fixed the modules, right? Feb 26 13:00:17 Or maybe they need some more fixing Feb 26 13:00:29 JaMa's reversal seems to be sumo/thud related? Feb 26 13:23:53 Looks somebody @ home was playing with the power button of the PC :P Feb 26 13:24:01 Need to disconnect it I guess ;) Feb 26 14:04:44 Herrie|Laptop: reversal? Feb 26 14:05:21 JaMa: s/reversal/revert/ Feb 26 14:06:06 Herrie|Laptop: yes, it should work, I just want to double check before doing one more ping-pong revert Feb 26 14:07:13 Tofe: Will try a build once builder is back online and let you know Feb 26 14:07:16 I've forgot all about this commit to be honest Feb 26 14:23:59 JaMa: Stuff might or might not have been fixed with https://github.com/webOS-ports/nyx-modules-hybris/commits/master Feb 26 18:16:15 anyone here? Feb 26 18:16:59 so meta-luneui > recipies-qt > qt5 > qtwayland_git.bbappend has a line like this: Feb 26 18:17:00 EXTRA_PACKAGECONFIG ?= "libhybris-egl-server" Feb 26 18:17:00 EXTRA_PACKAGECONFIG_qemuall = "drm-egl-server" Feb 26 18:17:00 EXTRA_PACKAGECONFIG_rpi = "" Feb 26 18:17:27 can i change add another EXTRA_intel-corei7-64="drm-egl-server" ? Feb 26 18:19:28 ookay that seems to work Feb 26 18:19:58 yes, you can :) Feb 26 18:20:50 actually it's not great that it's located in meta-webos-ports Feb 26 18:21:17 yeah.. but it is okay Feb 26 18:21:26 that'll do for now Feb 26 18:21:37 so i will have to make sure i am not building too much additional stuff Feb 26 18:21:54 Tofe: is there a way to quickly get an overview of the changes i made? Feb 26 18:21:59 like repo status or some such thing? Feb 26 18:22:38 not repo, but git status in meta-webos-ports and meta-smartphone should be quite all you've done Feb 26 18:22:52 i also edited conf/bblayers etc.. too Feb 26 18:23:14 https://bpaste.net/show/0906646f9942 Feb 26 18:23:22 unfortunately it's not really centralized Feb 26 18:23:47 Ahhh Feb 26 18:24:06 git diff might also give details. But not for the files that were not added in git Feb 26 18:24:23 would be nice if all these meta-* are added as git submodules or something and that way everything gets updated with git pull Feb 26 18:24:27 but i digress Feb 26 18:24:28 1 sec Feb 26 18:24:44 So do i need to have a meta-intel-luneos? Feb 26 18:24:53 right now i don't think i have any stuff in there.. yet Feb 26 18:25:25 I don't know if you need it, I just read earlier that you used intel's layer -- maybe I misunderstood Feb 26 18:25:30 added: to bblayers.conf ${TOPDIR}/meta-intel \ Feb 26 18:25:43 yeah i used the meta-intel , like there is a meta-raspberrypi Feb 26 18:25:51 ok yes Feb 26 18:26:03 but there is also a meta-rpi-luneos, seems to have luneos related overrides Feb 26 18:26:21 so blindly created meta-intel-luneos .. but there is nothing in there yet Feb 26 18:26:54 my machine=intel-corei7-64 directly is defined in meta-intel itself.. Feb 26 18:27:04 It could also fit in meta-smartphones, I guess. I'm never quite sure in which order our layers are used Feb 26 18:27:12 JaMa: ^ Feb 26 18:27:47 You'll very probably need to refine your machine.conf for luneos Feb 26 18:28:07 Ahh so there has to be a meta-intel-luneos then anyway right? Feb 26 18:28:31 I never had to make one myself, but I guess it would make sense Feb 26 18:29:35 you'll probably end up with similar things as in meta-rpi-luneos repo Feb 26 18:29:57 I see Feb 26 18:30:14 btw. how come you guys updated only qt5 to thud, and everything else is pyro? in layers.txt Feb 26 18:31:34 Though most of what's in there is to fix build issues, due to the weird locations of the egl headers Feb 26 18:32:08 the meta-rpi-luneos right? Feb 26 18:32:11 yep seems like it Feb 26 18:32:15 yes Feb 26 18:32:48 saidinesh5: meta-qt5 lives quite its own life; for pyro we went up to 5.11.3, as pyro is - so far - our daily working codebase Feb 26 18:33:47 rocko/sumo/thud are more WIP, and therefore we try to couple them with the latest meta-qt5, even if there will be fixes to be done Feb 26 18:33:57 ahh .. but this layers.txt has everything else on pyro and just Qt on thud Feb 26 18:34:04 testing one Feb 26 18:34:52 relying on pyro or thud doesn't necessarily change our luneos-related recipes: in a perfect world, it would work as-is on both. Feb 26 18:35:33 Ahh but the rest of the packages from pyro - like say network manager qt/what webos uses there may depend on a specific qt right? Feb 26 18:35:50 same for meta-qt5: ideally we could use any recent version of it (Qt 5.9, 5.10, 5.11, 5.12...) without any change on our side. Of course, it's not so simple, but we try to minimize the work Feb 26 18:36:00 Ahh.. Feb 26 18:36:19 So this layers.txt is okay? https://bpaste.net/show/f3723aeb4958 Feb 26 18:36:54 LGTM Feb 26 18:38:22 (Y) Feb 26 18:39:28 started bitbake: https://bpaste.net/show/0411ca416147 Feb 26 18:40:51 :) Feb 26 18:41:30 i think i will have to buy more ram for this ryzen 7.. just 16gigs right now.. so added a swapfile of another 16 Feb 26 18:45:06 I also have 16Gb... but in my case the CPU is the bottleneck (i5 6600) Feb 26 18:45:48 Ah.. for me with 16GB ram.. a chrome + firefox open.. building something like qtwebengine is *verrrry* risky Feb 26 18:48:00 basically my old 2013 nexus 7is slowly dying.. so i need a decent touch optimized OS, which fits nicely in 2GB ram for this intel atom tablet.. I could go back to android... buuut an OS with gestures seems nicer Feb 26 18:50:47 plus it would be ****verrrry*** nice to have something like this enabled in the browser: https://01.org/blogs/joone/2018/using-chrome-os-graphics-stack-intel-based-linux-desktops Feb 26 18:51:16 on windows 10 that came with tablet, Edge performed quite nicer than firefox/chromium.. Feb 26 18:51:42 so with some patches like this, it would be quite nice to have this on linux too Feb 26 18:53:55 not exactly sure how to make QtWebEngine take advantage of this though Feb 26 18:55:01 well if the EGL drivers are optimized, it should benefit QtWebEngine Feb 26 18:55:54 we don't have X, that's for sure ! :) Feb 26 18:56:37 oh this machine pulls in X no? Feb 26 18:56:40 *MACHINE Feb 26 18:57:03 qemu image too uses X right? Feb 26 18:57:42 https://git.yoctoproject.org/cgit.cgi/meta-intel/tree/conf/machine/intel-corei7-64.conf Feb 26 19:00:39 So i have to add this stuff to my meta-intel-luneos ? https://bpaste.net/show/d1b6c2b90ee2 Feb 26 19:11:24 nope, our compositor is wayland-only, we don't need X Feb 26 19:12:05 defining XSERVER won't necessarily make it used/installed; though I quite don't know the details... Feb 26 19:12:32 We just need EGL drivers, basically. Feb 26 19:15:06 ( ... with the "EGL_WL_bind_wayland_display" extension ) Feb 26 19:17:43 Ahh I see Feb 26 19:34:51 Tofe: I should limit which MACHINEs I'm building for unstable (rocko, sumo, thud) to make the sstate a bit smaller, should I do just tissot and qemux86 for now? or are other devices interesting for you as well right now (will enable more once we get some first ones working a bit) Feb 26 19:35:30 the builder is still doing thud for last 2-3 days Feb 26 19:36:08 for now that's fine; I'd be interested in hammerhead too, but I understand it doesn't share much with the rest, and I can very well built it myself too Feb 26 19:37:13 JaMa: but anyway I rarely use your sstate, most of the time I'm better off rebuilding it locally than downloading it ;) Feb 26 19:38:25 I can use your sstate? O_O Feb 26 19:38:49 or wait.. i dont think that would be possilbe when machines are different right? Feb 26 19:40:17 saidinesh5: well, you're using x86-64, so maybe there's a possibility of reusing qemux86-64's sstate Feb 26 19:41:36 JaMa: with https://bpaste.net/show/0411ca416147 , saidinesh5 shares some common sstate with qemux86-64, right ? Feb 26 19:42:19 though you just said you'll first only build qemux86 :p Feb 26 19:45:35 Bah... Ran out of ram Feb 26 19:45:40 System froze up Feb 26 19:47:28 oh. I never get that, maybe you can change the build configuration ? Feb 26 19:47:44 Yeah.. Waiting for the system to unfreeze Feb 26 19:47:54 Trying to ssh from phone and kill Firefox Feb 26 19:48:02 I have 4 thread + make j4 Feb 26 19:49:05 conf/local.conf: I have PARALLEL_MAKE = "-j 4" and BB_NUMBER_THREADS = "4" Feb 26 19:49:14 Ah Feb 26 19:50:01 My CPU is mostly 100% the whole time, so I think it's a pretty good config for me Feb 26 19:50:37 Yeah.. will definitely have to get more ram for this machine.. otherwise it'll be very underutilized Feb 26 19:53:28 Btw. I think sharing sstate with qemu x86_64 may not be possible... Because of the TUNE_FEATURES Feb 26 19:53:42 oh... right... Feb 26 19:53:42 Maybe noarch packages... Feb 26 19:53:57 well that's not the most interesting part :p Feb 26 19:54:02 Yup Feb 26 19:55:39 Which Rizen do you have ? Feb 26 19:55:49 1700.. Feb 26 19:56:10 Ryzen 7 1700. got it in a clearence sale this december lol. so nice 8 cores 16 threads Feb 26 19:56:38 oh, 16 threads, I see... You use -j 16 ? Feb 26 19:56:53 bit bake used 16 jobs.. plus each job seems to be parallellized lol Feb 26 19:57:40 I'd say try with 4 and -j8, it should already take most of it without topping the memory too much Feb 26 19:57:56 yeah.. fortunately the swapfile i added saved the day! Feb 26 19:57:58 system unfroze Feb 26 19:58:24 4908 tasks done out of 7185 Feb 26 19:58:48 i will let it finish.. it is not as if i sit around recompiling the same packages until we update from pyro right? Feb 26 20:00:45 oh it's a 65W TDP ? Same as mine; I mainly selected it to consume not too much while being decent enough, and at the time AMD was doing quite poorly on that former side Feb 26 20:01:43 my main powerhog is that RX580 Feb 26 20:01:59 that one gobbles up like 400W when fully running i think Feb 26 20:02:19 I have a Nvidia 1050Ti, 75W, for the same reason :) Feb 26 20:02:29 but for the first time ever .. 0 issues with graphics on linux with foss drivers lol Feb 26 20:03:11 wow .. 75W sounds pretty sweet for a GPU Feb 26 20:03:24 * Tofe doublechecks... Feb 26 20:03:59 yup, that's the right number. Feb 26 20:04:26 Oh wait ... Mine is 225W Feb 26 20:04:35 *only* :) Feb 26 20:04:38 I confused this with the Vega 56 Feb 26 20:04:41 Lol Feb 26 20:05:25 My choices then were buy an rx580 here.. or make a friend from the US bring me one of those vega 56 for the same price I'd have paid here Feb 26 20:05:35 For my rx580 Feb 26 20:06:03 But then at 400W the price of electricity enters the equation ;) Feb 26 20:06:12 Yep Feb 26 20:06:26 That's why decided against it Feb 26 20:07:28 I mean the games i played with... I was literally playing 10 year old games on this Intel atom tablet .. And some games on 720p on that laptop gpu lol.. it's not as if I'll care about the graphics when i was used to it Feb 26 20:09:49 so far this 580 played Hitman 2 very nicely .. so i am very happy... and it's opensource amd drivers => 0 headaches meddling with bumblebee etc.. breath of fresh air Feb 26 20:09:53 :) I understand, until recently I just needed my Intel HD 530 on the i5, and it was mostly alright Feb 26 20:10:11 HD 530 ? which game did you play? Feb 26 20:11:26 or rrather which game made you upgrade to the 1050ti? Feb 26 20:11:31 Civilization V, Fallout 3, Morrowind, Shank Feb 26 20:11:34 Ahh Feb 26 20:12:07 Now I can play Tomb Raider, Batman Arkham, things like that Feb 26 20:12:18 yup.. Tomb Raider was surprisingly nice on linux Feb 26 20:12:31 waiting for feral to release the linux version of the latest.. so i can buy it Feb 26 20:12:39 :) Feb 26 20:12:50 bought arkham during the last steam sale.. yet to play that .. spending a lot of time on this simulator Feb 26 20:13:18 gotta admit.. really thankful to valve for literally changing the linux graphics/gaming scene Feb 26 20:13:28 it plays very nice with wine -- I also bought it with that sale Feb 26 20:13:38 Shadow? Feb 26 20:13:47 I just played Origin so far Feb 26 20:13:53 Ahh.. Feb 26 20:14:07 but I guess (hope?) that Shadow will play as nicely Feb 26 20:14:18 with DXVK it's surprisingly fast Feb 26 20:14:25 Shadow of the tomb raider.. i am waiting for feral to release so my money directly goes to them.. the last two games.. i bought in sale and then feral released linux versions .. so i got them for free Feb 26 20:14:37 yup. i have heard that too Feb 26 20:15:17 hitman 2.. i played on windows.. totally loved hitman 1.. so didn't wait for feral this time.. i hear even that runs very well on wine/Steamplay on linux Feb 26 20:15:19 Let's just wait for a Vulkan version of Chromium, eh :) Feb 26 20:15:29 haha... is that even in their roadmap? Feb 26 20:15:34 dunno Feb 26 20:16:12 I don't even know if the latest Qualcomm CPUs provide Vulkan drivers Feb 26 20:16:21 they do right? Feb 26 20:16:41 I don't have a clue -- but I do hope so Feb 26 20:16:42 i mean vulkan has been part of android since android 7 i think.. so any qualcomm chipset released since then has vulkan suppor Feb 26 20:17:03 oh ? ok, I learned something tonight, good :) Feb 26 20:17:35 But libhybris... I didn't see anything on that front Feb 26 20:17:45 Ahh. true.. Feb 26 20:18:23 well, I guess it's not our top-priority either :D Feb 26 20:18:39 but what userspace program on hybris side of OSes even use vulkan? Feb 26 20:20:00 plus if it is an SDL program .. we can directly link it wiht bionic and it should work right? Feb 26 20:21:08 is our QtWebEngine actually hardware accelerated? Feb 26 20:24:25 on libhybris Feb 26 20:25:02 saidinesh5: Tofe: with default config it should share a bit (mostly just native stuff and some low level deps, but if there is bbappend for qtbase, then not the rests (like qtwebengine and all big stuff) Feb 26 20:25:53 the TUNE_FEATURES are the same "m64 corei7" Feb 26 20:25:55 Ah .. I see.. how can it share though.. like TUNE_FEATURES are different right? Feb 26 20:25:56 oh Feb 26 20:25:59 i see Feb 26 20:26:05 saidinesh5: QtWebEngine uses our GLESv2 drivers yes Feb 26 20:26:13 ah no, I cannot read, sorry qemux86-64 is "m64 core2" Feb 26 20:26:18 oh that's very nice.. Feb 26 20:26:20 As does QML also Feb 26 20:26:26 yeah QML has to Feb 26 20:26:32 just not sure about webengine though Feb 26 20:26:57 so that's kind of why i totally ruled out sailfish os/nemomobile for this tablet Feb 26 20:27:28 the browser.. the one core piece of software is totally unoptimized for it.. and when i tried to compile chromium/qtwebengine.. it wasjust a nightmare Feb 26 20:27:41 old gcc.. half the packages qtwebengine needs aren't available in mer repos Feb 26 20:28:08 SFOS's browser is currently a shame, I hope they find the time to upgrade it and/or to provide a recent QtWebEngine Feb 26 20:28:11 so thought.. no point in redoing the packaging work.. someone else has done so many times before me.. might as well pick a distro that lets me skip that Feb 26 20:28:52 yep.. wrote a little browser-let.. to mimic android's browser on sailfish os.. but even that's broken as of now Feb 26 20:29:15 need to update my patch to lipstick for that Feb 26 20:29:54 Tofe: btw. how's anbox looking on luneos? Feb 26 20:32:31 i think with the MiA1 you guys should have pretty recent kernel.. so shouldn't be too hard to get it up and running Feb 26 20:33:53 saidinesh5: status unknown so far, I'm more trying to fix the vkb issue than anbox right now Feb 26 20:34:00 woot: 10: gnu-efi-3.0.5-r0 do_package - 20s (pid 3282) Feb 26 20:34:00 11: diffutils-3.5-r0 do_package_write_ipk - 5s (pid 4998) Feb 26 20:34:00 12: grub-efi-2.00-r3 do_configure - 5s (pid 6013) Feb 26 20:34:00 13: syslinux-6.03-r0 do_configure - 3s (pid 6571) Feb 26 20:34:05 oh .. what vkb issue? Feb 26 20:35:14 it looks like a touchscreen issue, either on kernel side or on userland side: somehow, we register two touches, so the text field gets focus and immediately after loses it, so the vkb just pops up and disappear Feb 26 20:36:00 oh interesting... Feb 26 20:36:04 at each boot, it either works well or not at all. It seems to be related to the way we initialize it -- maybe also related to the way we initialize hwcomposer Feb 26 20:36:46 does hwcomposer come into picture for input? Feb 26 20:36:58 i thought input happens via. /dev/input/* Feb 26 20:37:07 only when we disable it after a timeout: it also deactivates the touchscreen Feb 26 20:37:21 oh.. interesting Feb 26 20:38:16 it = hwcomposer? Feb 26 20:38:23 I've spent quite some hours so far, and with no precise leads to chew; it's a bit frustrating Feb 26 20:38:24 yes Feb 26 20:39:42 I've also tried to debug it on rosy (Mi 5), where it happens almost all the time, but without much success Feb 26 20:40:04 interesting.. Mi 5 has a very well working sailfish port Feb 26 20:40:13 so shouldn't be kernel right? Feb 26 20:40:34 shouldn't be; also recovery is working very well, using the same kernel Feb 26 20:40:42 yep Feb 26 20:40:45 could it be just Qt? Feb 26 20:41:00 like can you disable the compositor and run an SDL program or osmethign and check? Feb 26 20:41:46 I would suspect our hwcomposer timeout -- something I didn't try so far was to deactivate that timeout completely Feb 26 20:42:25 i see.. Feb 26 20:43:09 and that kind of logic is specific to LuneOS, so a bug there wouldn't necessarily be also in Sailfish Feb 26 20:43:31 yeah Feb 26 20:43:46 iirc sailfish uses something called mce to handle enabling/disabling the touchscreen Feb 26 20:44:15 yes, it's provided by Mer, we don't use that one Feb 26 20:44:22 Ah Feb 26 20:45:05 we have mecanisms with powerd, sleepd, registered on LS2 bus, things like that Feb 26 20:45:21 and the timing mecanism is in LunaSysMgr Feb 26 20:45:32 Oh.. I see Feb 26 20:45:56 Which has a nice State Machine to handle the different switches Feb 26 20:46:22 Ahh.. interesting Feb 26 20:46:51 this bug could just be a Qt level bug though right? the two touchscreen events one.. Feb 26 20:47:05 but I'll digg this deactivation of hwcomposer lead tomorrow, it's too late to begin that tonight :) Feb 26 20:47:12 Aye Feb 26 20:47:54 It could be; I would have to see exactly what event is sent by the kernel Feb 26 20:48:36 yep.. like a simple Qt program inplace of the compositor.. should give you the idea Feb 26 20:48:39 we have activated the evbug module, so it outputs the events it sees, which is a good thing here Feb 26 20:48:53 Ahh Feb 26 20:48:59 is it a kernel module? Feb 26 20:49:34 more like a functionality Feb 26 20:49:40 I see Feb 26 20:50:05 the only time i had to deal with touchscreen issues was adding double tap support to my Mi 3 on sailfish os Feb 26 20:50:07 it's really just a simple file in the kernel which adds hooks and printf code Feb 26 20:50:13 Ahh Feb 26 20:50:15 in sysfs? Feb 26 20:50:20 dmesg Feb 26 20:50:23 Ahh Feb 26 20:51:35 Still, I'll have a look at sailfish's port for Mi 5, in case they added a commit of two Feb 26 20:51:44 yeah Feb 26 20:54:56 how's the integration/unification/not sure what to call it.. with webosse coming along? Feb 26 20:55:10 lol, look at that last commit: https://github.com/zhxt/android_kernel_xiaomi_msm8996/commit/d4d941b1791e152f825f96589c8b9b3ac87020dc Feb 26 20:56:01 Ah interesting Feb 26 20:56:09 This could be something right? Feb 26 20:56:34 could be; it's still a long shot, but who knows, it's in the right area Feb 26 20:57:52 Yep Feb 26 20:58:06 Didn't know the A1 had synaptics touchscreen Feb 26 21:00:56 mmh it's already applied on my Mi 5 kernel -- my source code seems to be much more recent. But for me it's "rosy", whereas for sailfish it is "gemini", so a little bit different devices it seems Feb 26 21:02:11 Anyway, time to go -- see you ! Feb 26 21:02:22 Good night? Feb 26 21:02:36 I'm at 6890 packages Feb 26 21:02:43 No question mark there btw. Lol **** ENDING LOGGING AT Wed Feb 27 02:59:56 2019