Tuesday, 2026-05-12

Mister_Magisterman, i can turn on otg and have the device working but there's absolutely no signal when otg device is connected so i cannot do it automatically ;-00:18
nightishamanim halfway through fixing the quirks to make it build: https://github.com/maltesermailo/android_kernel_google_gs-6.1_google-modules02:40
T42<edp_17> What is the xulrunner-qt5 package for?09:29
T42<abranson> it's the gecko web browser engine09:34
T42<abranson> from mozilla. heavily modified.09:34
T42<edp_17> Thanks.09:49
T42<edp_17> mal, Do you remember my issue with the stock browser segfaulting on my treltexx (Galaxy Note4) port ?11:34
T42<edp_17> I've managed to fix it. The issue was in mm/shmem.c.11:35
T42<edp_17> The fix was adding a condition at this line: https://github.com/edp17/android_kernel_samsung_exynos5433/blob/lineage-17.1-treltexx/mm/shmem.c#L295411:50
T42<edp_17> Just in case anyone else has got similar issues.11:50
mal@edp_17 so you patched kernel? or what?11:53
T42<edp_17> Yes I did that.12:08
T42<edp_17> However, now the browser starts from command line but doesn't start with its icon. :)12:09
T42<edp_17> The desktop icon uses: /usr/bin/invoker --type=browser,silica-qt5 -A -- /usr/bin/sailfish-browser %U12:09
T42<edp_17> when I run this at command line I get: "invoker: warning: Launch failed, application specific booster is not available."12:10
Mister_Magistermal: any luck with camera2?14:11
malno time14:12
Mister_Magistergotcha14:12
Mister_Magisterbut if it's just that user id thingy that needs fixing, couldn't you just show me what you have in progress so that i can fix it myself?14:12
Mister_Magisterunless there's more fixes that are needed14:12
T42<edp_17> Once i fixed the issue in kernel, the browser started fine from command line but didn't start with its desktop icon. I have figured out that the root cause was using a too old firejail. Once I installed the one from official repo, the browser started to behave. :)14:44
maxmight5328Hello, after running 'rpm/dhd/helpers/build_packages.sh --mic' i got this list of artifacts, is it as expected? https://paste.opensuse.org/pastes/dd1012d5ab9416:10
T42<elros34> looks sane16:47
maxmight5328Does hybris look for the OS at /data/.stowaways/sailfishos by default or this is something that has to be explicitly configured for my port?16:54
T42<Mister_Magister> no it does so by default16:54
T42<Mister_Magister> https://github.com/mer-hybris/hybris-boot/blob/master/init-script#L16816:55
maxmight5328Ok, thats good. I flashed boot.img and extracted the files top the stowaways directory. Unfortunately it boot-loops :(16:58
maxmight5328It displays the sonly logo and after about a minute it reboots.16:58
maxmight5328No USB logs in the host dmesg log16:59
T42<elros34> boot.img is lineage boot image, you want hybris-boot.img17:04
T42<elros34> you have init.log in stowaways?17:05
T42<elros34> /data/.stowaways/sailfishos/init.log17:05
maxmight5328Ah yes, it was hybris-boot.img indeed. How can how do i get the contents of this log file from fastboot? Do I need to flash the los recovery boot img and use adb?17:18
T42<elros34> in recovery you can access /data right?17:19
maxmight5328Yes, I think so17:19
maxmight5328I flashed back LOS boot and vendor_boot but when i booted into recovery it did return an error and wanted me to erase data :(17:29
T42<elros34> why did you flash los boot? does it have recovery inside?17:29
maxmight5328I thought this is how I get back to recovery, is this not the way?17:33
T42<elros34> I don't know. Its device/android version specific17:35
maxmight5328I got this idea from the nagara port https://github.com/sailfishos-sony-nagara/main/wiki/Flashing-Sailfish-OS#accessing-lineageos-recovery-after-flashing-sailfish-os17:37
maxmight5328now it is showing the three spinnig circles boot animation for some minutes but has not booted up into android yet...17:38
T42<elros34> don't even try to boot android, you will encrypt /data so sfos will not boot17:39
maxmight5328Ohh, good to know. I managed to get it back into recovery... now lets see what do we have in /data17:43
nightishamanIs it becoming harder once I got the kernel to build or is it easier?19:30
T42<FakeShell> @fredldotme i gave up on icd, getting surfaces with libhardware was too much work and i can't figure out why icd didn't work so i just ended up making hybris install vulkan as libvulkan.1.99.999, so ldconfig picks it up without having to mess with dpkg diversions20:15
T42<FakeShell> if you want a way to ship in ubuntu then this may be an acceptable (temporary) solution20:15
Mister_Magistermal: quick question, motorola has phone gestures like chop chop to turn flashlight on, and from android guy who helps me i've learned they're exposed via sensormanager, and sensorfw is already talking to sensormanager via binder, and mce to sensorfw. and i'm wondering if i could implement them? i mean reading data should be straightforward i'm more pondering how to control them as in on/off from let's say settings20:50
Mister_Magister>quick question >literally one of the more convoluted issues20:50
malcheck if sensorfw lists those, maybe debug output helps21:00
Mister_Magisteryeah i will i'm just wondering if when i get past that, how can we turn them on/off via sensorfw from settings21:00
Mister_Magisteris that doable?21:00
malmight be, but might be quite a lot of work21:01
Mister_Magisterthats what i feared21:02
Mister_Magistermal: they're indeed there! https://paste.opensuse.org/pastes/612977a1233221:30
Mister_Magisterand all of them are setActive false HYBRIS CTL setActive(65748=SENSOR_TYPE_PRIVATE_65557, false) -> success21:34
Mister_Magisterbut I've learned 2 things: 1. they're there 2. sensorfw can turn them on/off21:41
nightishaman11 more kernel modules to fix and the kernel compiles21:41
malMister_Magister: question is what kind of event those would send21:41
Mister_Magistermal: i can tell you!21:41
Mister_Magisterhttps://github.com/LineageOS/android_hardware_motorola/blob/lineage-23.2/packages/MotoActions/src/org/lineageos/settings/device/actions/ChopForTorch.kt21:42
Mister_Magistersorry that's settings21:42
Mister_Magisterhttps://github.com/LineageOS/android_hardware_motorola/blob/lineage-23.2/packages/MotoActions/src/org/lineageos/settings/device/SensorHelper.kt21:42
malok it just ignored the event21:43
Mister_Magisteryeap21:43
Mister_Magisternow if i could add handler for those and then send key event to mce somehow and then make mce react to that, it would be cool21:43
Mister_Magisterahhhh oneplus is using separate program to execute the gestures https://github.com/sailfishos-oneplus5/gesture-daemon21:45
Mister_MagisterSo I don't even need mce, i can just talk with sensorfw and do the settings via daemon21:45
Mister_Magisteri might be wrong but that looks straightforward to implement, add handler in sensorfw, create daemon, connect to sensorfw, fetch motorola events, execute actions, write settings page, talk to daemon to turn them on/off, anything i'm missing mal?21:46
Mister_Magisterhttps://github.com/LineageOS/android_hardware_motorola/blob/lineage-23.2/packages/MotoActions/src/org/lineageos/settings/device/actions/ChopForTorch.kt#L86 the chopchop gesture you don't even need the data since it's a toggle21:51
Mister_Magisterwe already have flip over to silence gesture in sfos done via software, motorola does that via firmware21:52
Mister_Magisteri'll try to simply handle the chopchop21:53
Mister_MagisterI think I got this :321:58
Mister_MagisterI'll do it all on my own21:58
malthinking if we should see if we could add some customizable simple event sensor, like something that could be used for any such gesture events, not sure how easy that would be21:59
Mister_Magisterwell… neither sensorfw nor mce has any possibility to act upon gesture21:59
Mister_Magisterlike say turn on camera or flashlight22:00
malso configuration could define the event code to use and so on, but needs some thinking how22:00
malyeah, that is the part that needs thinking22:00
Mister_Magisterseparate gesture package that runs as user is necessityi think22:00
Mister_Magisterbut I don't think you need to think about that :P I'm just gonna add my handlers and create my daemon and be done with it :P22:01
Mister_Magisteri'd say its such a minor stuff, if someone wants they can fork it, and you got better things to think about honestly22:03
Mister_Magisterjust the fact that in all my years of porting i'm probably first one to bring that up means it's turbo low priority22:03
malusefulness of gestures is a bit of a matter of opinion22:06
Mister_Magisteralso not every phone has them in sensormanager22:07
malyeah22:07
Mister_Magisteronepluses don't, they have touchscreen gestures that are sent via evdev22:07
Mister_Magistermy g2 port from 2015 nobody even once complained about missing chop chop (or i forgot)22:07
Mister_Magisternow i want to check sensormanager on there too xd22:08
malI haven't even checked if fairphones support some gestures like that22:08
Mister_Magisterfor motorola it's one of the things the phones are famous for22:08
Mister_Magisterbut mal could you comment if my plan/general idea sounds valid? just wanna make sure22:11
malprobably reasonable for a start22:12
Mister_Magisterthanks22:13
Mister_Magisterohhh maybe I'll make sensorfw test app while i'm at it, not one that talks via qt but directly, and lists all the sensors and their values22:26

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!