| T42 | <Umeaman> I see that the lineage-18.1 WIP shortened links are no longer working. Can someone please fix them? | 03:19 |
|---|---|---|
| T42 | <Umeaman> On the unofficial hadk-faq. | 03:19 |
| *** Daanct12 is now known as Danct12 | 05:08 | |
| *** Daaanct12 is now known as Daanct12 | 05:08 | |
| Thaodan | Create a PR | 07:24 |
| T42 | <Spidey24Z> might boringssl_selftest* fail because of missing library files due to apexd-bootstrap get killed or this normal "Sending signal 9 to service 'apexd-bootstrap' (pid 2894) process group... HYBRIS: killing PID instead of process group." (re @elros34: looks like boringssl...) | 08:29 |
| T42 | <elros34> not sure but I guess could be normal if apexd finished or have nothing to do on your device. Have you tried to run that test manually? | 08:33 |
| T42 | <elros34> or search in channel logs about it? | 08:33 |
| T42 | <Spidey24Z> phone reboot before telent start (re @elros34: not sure but I guess...) | 08:43 |
| T42 | <Spidey24Z> okay (re @elros34: or search in channel...) | 08:43 |
| T42 | <Spidey24Z> phone reboot before telnet start (edited) (re @elros34: not sure but I guess...) | 08:44 |
| T42 | <elros34> after, telnet starts way before droid-hal-init and you can stop this process too if it reboots too fast but not sure how debug this ssltest | 08:45 |
| T42 | <elros34> can you show your device repo, maybe there is something there? | 08:46 |
| T42 | <Spidey24Z> how can i stop it if telnet not started? (re @elros34: after, telnet starts...) | 08:49 |
| T42 | <Spidey24Z> https://github.com/LineageOS/android_device_samsung_universal7880-common (re @elros34: can you show your de...) | 08:49 |
| T42 | <Spidey24Z> i found this journal mce[2854]: library "libdl_android.so" not found | 08:50 |
| T42 | <Spidey24Z> mce[2854]: *** UNRECOVERABLE FAILURE *** | 08:50 |
| T42 | <elros34> about telnet: read hadk-hot, section generating logs | 08:51 |
| T42 | <Spidey24Z> it's not telnet but phone reboot quickly in a few seconds and keep rebooting | 08:52 |
| T42 | <Spidey24Z> it's a bootlooop | 08:52 |
| T42 | <elros34> did your that fast this whole section I wast talking about?:O | 08:53 |
| T42 | <Spidey24Z> sorry i'm lost | 09:04 |
| T42 | <Spidey24Z> i'll mask droid-hal-init and run boringssl_tsets manually | 09:06 |
| T42 | <elros34> if you are lost then I again suggest to read channel logs, it has possible workaround for reboot on that test failure. That way droid-hal-init may works and maybe you could start/strace test. hadk-hot has info how to prevent bootloop but your idea to mask droid-hal-init will also do the job | 09:21 |
| *** Daaanct12 is now known as Daanct12 | 10:09 | |
| mal | @Spidey24Z is that hybris-18.1 based? | 11:37 |
| T42 | <Spidey24Z> yes (re @SailfishFreenodeIRCBridgeBot: <mal>@Spidey24Z is t...) | 14:16 |
| T42 | <Spidey24Z> i masked droid-hal-init and run boringssl test it return not found | 14:18 |
| T42 | <Spidey24Z> / # /system/bin/boringssl_self_test32 | 14:18 |
| T42 | <Spidey24Z> /bin/sh: /system/bin/boringssl_self_test32: not found (re @elros34: if you are lost then...) | 14:18 |
| T42 | <Spidey24Z> can i share a full log maybe i miss something? | 14:20 |
| mal | that seems like issue I have had | 15:19 |
| mal | it's an issue with apexd | 15:19 |
| T42 | <Spidey24Z> Any fix ? | 15:19 |
| T42 | <elros34> you probably can't test it like that without started droid-hal-init, so better try workaround to avoid reboots, and if that helps then you could debug it further | 19:15 |
| T42 | <Spidey24Z> Which workaround? | 19:27 |
| mal | @Spidey24Z I never found a proper fix, I had a way to make the device boot to UI with manual hack at every boot | 19:27 |
| T42 | <Spidey24Z> How ? (re @SailfishFreenodeIRCBridgeBot: <mal>@Spidey24Z I ne...) | 19:28 |
| T42 | <elros34> @Spidey24Z that one in logs, how many times do I have to tell it? Did you even bother to search for "boringssl_self_test32" in channel logs? | 19:30 |
| mal | I need to remember how, it has been quite a long time since I booted the device last time | 19:30 |
| T42 | <Spidey24Z> Yes I search I didn't found any fix or workaround (re @elros34: @Spidey24Z that one ...) | 19:31 |
| T42 | <Spidey24Z> Okay thanks (re @SailfishFreenodeIRCBridgeBot: <mal>I need to remem...) | 19:32 |
| T42 | <elros34> so why didn't you just tell that you couldn't find it? https://irclogs.sailfishos.org/logs/%23sailfishos-porters/%23sailfishos-porters.2022-04-13.log.html#t2022-04-13T13:48:50 | 19:34 |
| T42 | <Spidey24Z> I don't want to bother you, thanks I'll try this (re @elros34: so why didn't you ju...) | 19:41 |
| T42 | <elros34> if that doesn't fully help then search for in all rc files for reboot_on_failure and get rid of this. If this will slow down reboot then check whether you have something in /apex/com.android.runtime/bin/ (after apex starts) | 19:52 |
| T42 | <Spidey24Z> I did that now it's not reboot but apex not mounted (re @elros34: if that doesn't full...) | 20:09 |
| T42 | <elros34> not hing in /apex or just no com.android.runtime? What about errors in logs? | 20:11 |
| T42 | <Spidey24Z> Nothing in /apex (re @elros34: not hing in /apex or...) | 20:12 |
| T42 | <Spidey24Z> All services crashing 'cannot execv' | 20:13 |
| T42 | <elros34> yeah but what about apex related logs | 20:32 |
| T42 | <Spidey24Z> full log https://pastebin.ubuntu.com/p/cY9BPhHFRk/ and this what mounted https://pastebin.ubuntu.com/p/CcYSwDWNKX/ (re @elros34: yeah but what about ...) | 20:52 |
| T42 | <elros34> what do you have in /system/apex? | 21:35 |
| T42 | <elros34> what if you would mount /system/apex to /apex before droid-hal-init starts? | 21:41 |
| mal | if that issue is what I think it is, then it's because something to do with updatable vs non-updatable apex, one of the code paths fails at the moment because of the hybris patches, some part of the needed init is not done | 23:17 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!