| Mister_Magister | man, 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 |
|---|---|---|
| nightishaman | im halfway through fixing the quirks to make it build: https://github.com/maltesermailo/android_kernel_google_gs-6.1_google-modules | 02:40 |
| T42 | <edp_17> What is the xulrunner-qt5 package for? | 09:29 |
| T42 | <abranson> it's the gecko web browser engine | 09: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#L2954 | 11: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 %U | 12: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_Magister | mal: any luck with camera2? | 14:11 |
| mal | no time | 14:12 |
| Mister_Magister | gotcha | 14:12 |
| Mister_Magister | but 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_Magister | unless there's more fixes that are needed | 14: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 |
| maxmight5328 | Hello, after running 'rpm/dhd/helpers/build_packages.sh --mic' i got this list of artifacts, is it as expected? https://paste.opensuse.org/pastes/dd1012d5ab94 | 16:10 |
| T42 | <elros34> looks sane | 16:47 |
| maxmight5328 | Does 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 default | 16:54 |
| T42 | <Mister_Magister> https://github.com/mer-hybris/hybris-boot/blob/master/init-script#L168 | 16:55 |
| maxmight5328 | Ok, thats good. I flashed boot.img and extracted the files top the stowaways directory. Unfortunately it boot-loops :( | 16:58 |
| maxmight5328 | It displays the sonly logo and after about a minute it reboots. | 16:58 |
| maxmight5328 | No USB logs in the host dmesg log | 16:59 |
| T42 | <elros34> boot.img is lineage boot image, you want hybris-boot.img | 17:04 |
| T42 | <elros34> you have init.log in stowaways? | 17:05 |
| T42 | <elros34> /data/.stowaways/sailfishos/init.log | 17:05 |
| maxmight5328 | Ah 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 |
| maxmight5328 | Yes, I think so | 17:19 |
| maxmight5328 | I 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 |
| maxmight5328 | I 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 specific | 17:35 |
| maxmight5328 | I got this idea from the nagara port https://github.com/sailfishos-sony-nagara/main/wiki/Flashing-Sailfish-OS#accessing-lineageos-recovery-after-flashing-sailfish-os | 17:37 |
| maxmight5328 | now 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 boot | 17:39 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!