| T42 | <edp_17> mal : Good morning. Yes, dsme is still crashing. logcat: https://paste.ubuntu.com/p/5wZgHfhvSR/ | 05:39 |
|---|---|---|
| T42 | <edp_17> journal: https://paste.ubuntu.com/p/qgz7b874SZ/ | 05:40 |
| T42 | <edp_17> I've tried to start dsme without and with debug as @elros34 suggested. Here is the log from console: https://paste.ubuntu.com/p/yZbhScSC7q/ | 05:40 |
| T42 | <edp_17> @elros34 : Good morning. | 05:41 |
| T42 | <my90ds> Please tell me how to fix this (https://pastebin.com/QZ5RJE5W)? | 05:49 |
| T42 | <edp_17> @my90ds : The same command is working for me so the issue will be your connection. | 05:53 |
| T42 | <edp_17> @my90ds : Try again. | 05:53 |
| T42 | <my90ds> Tried repeatedly. There are no problems with the Internet. The problem is only with the execution of this command. (re @edp_17: @my90ds : Try again.) | 05:54 |
| T42 | <edp_17> @my90ds : Use this: repo init -u https://github.com/mer-hybris/android.git -b hybris-16.0 | 05:56 |
| T42 | <my90ds> Thank you. It worked. (re @edp_17: @my90ds : Use this: ...) | 05:58 |
| T42 | <elros34> @edp_17 hi, "-- -p /usr/lib/dsme/startup.so" is not part of gdb but dsme command so include it if you start dsme manually. I assume nothing really crash right? | 06:30 |
| T42 | <edp_17> @elros34 : No, if I include those to the dsme call, there is no crash: https://paste.ubuntu.com/p/Dj6STSyHTp/ | 07:22 |
| T42 | <edp_17> But the device keeps rebooting. :( | 07:22 |
| T42 | <edp_17> When I mask dsme.service, it reboots much quicker (I cannot even telnet in) | 07:22 |
| T42 | <elros34> so mask something else like droid-hal-init/user@100000 to ease debugging. Get rid of StartLimitAction=reboot, PrivateNetwork=true and other sandboxing options too see if that will help | 07:32 |
| T42 | <elros34> from dsme.service | 07:32 |
| *** Daaanct12 is now known as Daanct12 | 07:35 | |
| T42 | <Asgard_f0rk> Can someone guide me how can I situp my PC for porting sailfishos | 07:36 |
| T42 | <edp_17> @Asgard_f0rk : Follow the HADK: https://sailfishos.org/content/uploads/2022/02/SailfishOS-HardwareAdaptationDevelopmentKit-4.3.0.15.pdf | 07:37 |
| T42 | <edp_17> @elros34 : I've masked user@100000 and droid-hal-init. Didn't help, the device keeps rebooting. Now, I amend dsme.service as you requested. | 07:47 |
| T42 | <edp_17> dsme service before: https://paste.ubuntu.com/p/HMxDygRfD2/ | 07:47 |
| T42 | <edp_17> and after: https://paste.ubuntu.com/p/kX4tftbWZM/ | 07:47 |
| T42 | <edp_17> Result: blue led is blinking, I have telnet and seemingly the reboot stopped. | 07:50 |
| T42 | <edp_17> I guess because I removed this: StartLimitAction=reboot | 07:51 |
| T42 | <edp_17> Now, should I start droid-hal-init and user@100000 services? | 07:51 |
| T42 | <elros34> check whether it still crash | 07:58 |
| T42 | <edp_17> Here is the journal since the last reboot: https://paste.ubuntu.com/p/nb6pDyQ3PW/ | 08:15 |
| T42 | <edp_17> It looks like not crashing, doesn't it? | 08:16 |
| T42 | <edp_17> I've unmasked droid-hal-init and user@100000 services and got this in journal: https://paste.ubuntu.com/p/239xS9ZNsx/ | 08:43 |
| T42 | <edp_17> Wait, both services are still masked. | 08:48 |
| T42 | <edp_17> Yeah, when I unmasked them the device keeps rebooting before I can get in. | 08:53 |
| T42 | <edp_17> When user@100000 was masked and droid-hal-init was unmasked, the device kept rebooting. | 09:43 |
| T42 | <edp_17> When user@100000 was unmasked and droid-hal-init was masked, the reboot stopped. | 09:43 |
| T42 | <edp_17> @elros34 ^ | 09:43 |
| T42 | <edp_17> I thought trying to start droid-hal-init manually. | 09:48 |
| T42 | <edp_17> Seen that it first starts droid-hal-early-init.sh that bind mounts ld.config.29.txt. (I don't need this as don't have ld.config.29.txt) | 09:49 |
| T42 | <edp_17> Then it starts droid-hal-startup.sh. When tried to execute the commands manually, I got this : https://paste.ubuntu.com/p/qzy7hs6RQW/ | 09:49 |
| T42 | <edp_17> Okay, if I manually start all steps from /usr/bin/droid/droid-hal-startup.sh, lipstick starts and the device doesn't reboot. | 10:00 |
| T42 | <edp_17> What about if I increase these in droid-hal-init.service? : TimeoutSec=15 | 10:07 |
| T42 | <edp_17> StartLimitInterval=60 | 10:07 |
| T42 | <edp_17> StartLimitBurst=2 | 10:07 |
| T42 | <edp_17> Might it be the device need more time for something but dorid-hal-init doesn't wait long enough? | 10:07 |
| T42 | <edp_17> full journal: https://paste.ubuntu.com/p/DjpFf8g9Vn/ | 10:08 |
| *** attah_ is now known as attah | 10:13 | |
| *** attah_ is now known as attah | 10:41 | |
| T42 | <edp_17> How can I know whether I need bluez4 or bluez5? | 13:26 |
| T42 | <edp_17> Should have searched logs first: "kernel version. 3.4 can't use bluez5", so it will be bluez4. :) | 13:28 |
| mal | yes, it is dependent on kernel version, 3.4 can also use bluez5 if you use backported kernel bluetooth drivers | 13:28 |
| T42 | <edp_17> mal : I have not backported anything but the kernel might have that driver. How can I check? | 13:30 |
| T42 | <edp_17> I've checked this in my kernel and all are there. https://github.com/bluez-android/misc/blob/master/patches-kernel/0001-hid-Backport-hid-generic-driver.patch | 13:36 |
| T42 | <edp_17> So, it means I already have backported bluez5 driver that I can use, doesn't it? | 13:36 |
| T42 | <edp_17> mal ^ | 13:36 |
| mal | can you give a link to the kernel sources | 13:44 |
| T42 | <edp_17> mal : Sure. https://github.com/edp17/android_kernel_samsung_jf | 13:46 |
| T42 | <edp_17> lineage-17.1 branch: https://github.com/edp17/android_kernel_samsung_jf/tree/lineage-17.1 | 13:46 |
| T42 | <edp_17> For building broadcom-bluetooth (bluez5), I need to install bluez5-libs-devel. When trying to install, I get: https://paste.ubuntu.com/p/ztsDt9q6Js/ | 13:51 |
| T42 | <edp_17> Can I simply chose solution 1? | 13:51 |
| mal | so you have broadcom bluetooth? | 13:53 |
| mal | yes, you can select 1 | 13:54 |
| T42 | <edp_17> Yep. Thanks for confirming. | 13:56 |
| T42 | <edp_17> mal : Do you have idea why droid-hal-init crashes when it starts as service but it runs happily when started manually (I mean command by command from the script)? | 13:57 |
| mal | how does it crash? | 14:04 |
| mal | one thing I could think of is systemd sandboxing, if it's because of that it would suggest some issue in kernel | 14:07 |
| mal | you can try if it work without sandboxing by commenting out line 15-17 in /usr/lib/systemd/system/droid-hal-init.service i.e. https://github.com/mer-hybris/droid-hal-configs/blob/master/sparse/usr/lib/systemd/system/droid-hal-init.service#L15-L17 | 14:08 |
| mal | I will be away for an hour or so | 14:09 |
| T42 | <edp_17> mal : No worries. I'll catch you up later. I'll try what you recommended. | 14:10 |
| T42 | <edp_17> mal : I do not have those "Protect*" lines in my /usr/lib/systemd/system/droid-hal-init.service. | 14:12 |
| T42 | <edp_17> my current droid-hal-init.service file is: https://paste.ubuntu.com/p/XCtmR5THsw/ | 14:13 |
| T42 | <edp_17> But the device kept rebooting with this one too. | 14:13 |
| T42 | <edp_17> Oh, and dsme.service looks like this : https://paste.ubuntu.com/p/kX4tftbWZM/ | 14:15 |
| T42 | <edp_17> @pketo, please add Galaxy S4 access to the store. Thanks. Device model: Galaxy S4 (jfltexx / jfltexx) | 14:18 |
| mal | @edp_17 does dsme fail if you have those sandboxing lines enabled? | 16:03 |
| T42 | <edp_17> mal : Yes it does. Moreover all apps that use sandboxing do crash and not start. (e.g. :sailfish-browser) | 16:39 |
| T42 | <edp_17> Well, almost all because gallery and calendar do start. | 16:49 |
| T42 | <elros34> @edp_17 try to set this to -1: https://github.com/edp17/android_kernel_samsung_jf/blob/lineage-17.1/kernel/audit.c#L72 then get dmesg from dsme failure, droid-hal-init or anything else which fails. | 18:50 |
| T42 | <elros34> Would be good if you can find any other device with 3.4 kernel which works fine on sfos 4.4.0. That way you could compare missing/breaking commits | 18:52 |
| T42 | <elros34> I can see lipstick complains about missing: libandroidicu.so | 18:58 |
| mal | ah, that libandroidicu.so needs the usual symlink probably | 19:22 |
| mal | fp2 has 3.4 kernel and works fine, I had to patch the kernel a bit though | 19:23 |
| T42 | <edp_17> It was complainig when dsme was masked but then this error gone when I enabled dsme and masked droid-hal-init and manually started its commands one by one. (re @elros34: I can see lipstick c...) | 19:26 |
| T42 | <edp_17> I'll try to set that in kernel and get some logs. | 19:27 |
| T42 | <edp_17> mal : what did you patch in your kernel? | 19:27 |
| T42 | <edp_17> @elros34 : what does that audit_initialized do and how could it help? | 19:31 |
| T42 | <elros34> it should make our dmesg readable, currently it's flooded with useless messeages so there is no way to see even boot messages, not to mention errors when dsme/droid-hal-init fails | 19:32 |
| T42 | <edp_17> I see, thanks. | 19:35 |
| T42 | <edp_17> @elros34 : I've changed that line like this. Is it okay? https://github.com/edp17/android_kernel_samsung_jf/commit/7527ac99b8eb85a3edce4883cb77019d262b6126 | 21:20 |
| T42 | <elros34> I hope so | 22:56 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!