Monday, 2026-06-29

*** n2klb_ is now known as n2klb01:59
sharksWoohoo! With a bit more screwing around I have telnet! And more importantly, logcat! And I can debug on a live system now!06:30
sharksUnfortunately @mal was dead right, it seems this `tad` service is the killer, logcat is spammed constantly with `tadif   : Failed to connect to tad.`06:30
T42<securebootoff> tad is ta daemon07:59
T42<securebootoff> you'll get broken modem, mac addresses, etc without it07:59
sharkshmm, that's what I thought, it wouldn't hold up boot. That said, still want to fix it.08:09
sharksI am also still fighting android.hardware.graphics.composer - is there a best practice to edit / override `/vendor/etc/vintf/manifest.xml`? It is missing any section about android.hardware.graphics.composer which I suspect is the issue? Unless I am barking up the wrong tree?08:11
T42<adampigg> you can bind mount over the top of it with a modified version (re @SailfishFreenodeIRCBridgeBot: <sharks>I am also st...)08:12
sharksThanks piggz, I did not spot your reply until now - I am trying that but do not know where to put the command to bind mount! If I put it in droid-hal-early-init.sh is that sufficient?08:30
sharksRight, here's some hopefully relevant lines from logcat, journal, and the vintf manifest that I have bind-mounted to a modified file from droid-hal-early-init.sh --> https://paste.opensuse.org/pastes/3c904aeca69a08:50
sharksI freely admit I have no idea what I am doing, but if anyone can help I would be grateful08:51
sharksI don't know if this offers any insight either --> https://paste.opensuse.org/pastes/c520fb1990c708:53
T42<elros34> droid-hal-early-init is executed before droid-hal-init (android init) so yes. If you have no idea then would be better to not filter out logs but shows everything right?09:29
sharksThe logcat file is too big to upload to opensuse, mainly its full of megabytes of `tadif   : Failed to connect to tad.` but even with all that cut out it's still over the limit, I'll do my best09:43
T42<elros34> no, that is not how do you generate logs. You get them as soon as possible/include all early logs. Several MB of repeated logs 2 minutes after boot are useless09:45
sharksI understand that, elros. These logs are collected as soon as I can telnet in and dump to file. They are only a few seconds old.09:45
T42<elros34> why would you dump to file? just print it. Also for sure you can get them even faster with init_enter_debug2 and then excuting logcat as soon as droid-hal-init starts09:48
sharksHow is it easier to print 70,000 lines of logcat to my terminal window and try to copy it out of there? simpler just to run logcat > somefile.txt. Anyway, it is done now. logcat -> https://paste.opensuse.org/pastes/6e241e7fe837 and journal -> https://paste.opensuse.org/pastes/440f4a200dd709:52
sharksYou are right I probably could get faster / shorter logs with init_enter_debug2, I guess I will do that next time. Thanks09:54
T42<elros34> this journal is only 30s10:00
T42<elros34> so have you tried to start/strace this tad service?10:00
sharksYes, the journal is only 30s. I got it as soon as I telnet'd in like I said10:03
sharksNo, I have not tried to strace tad. I have been more focused on the composer as that seemed like the fish that I might be able to fry a bit easier10:04
sharksBut I will try to strace tad now10:05
T42<elros34> as soon as fast doesn;t mean only 30s. 30s is usual timeout. Try to reenable vold service and see if that will help with hwcomposer10:06
sharksresult of strace --> https://paste.opensuse.org/pastes/feddd2bf08e710:10
sharksjournal longer than 30s --> https://paste.opensuse.org/pastes/c2f8e48351eb10:12
sharksI apologise, I am unsure how to 'reenable vold service'. I never disabled it, but I can see in journal logs it is failing?10:13
T42<elros34> based on logs it's probably in 'Parsing file /usr/libexec/droid-hybris/system/etc/init/disabled_services.rc'. Btw do you have some services masked?10:15
T42<elros34> sailfish services*10:15
sharksI only have usb-moded masked per your suggestion a few days ago to allow telnet to work10:16
T42<elros34> ok10:17
sharksYes, looks like vold is in disabled_services.rc -> `service vold vold_HYBRIS_DISABLED`. I will remove it and reboot, see what happens?10:17
sharksshort answer, enabling vold was a bad idea10:25
sharkssee journal, vold kills the system after a few minutes --> https://paste.opensuse.org/pastes/543d4f9e80dc10:25
sharksPhone ends up rebooting10:25
T42<elros34> ah because it has reboot_on_failure property and it fails10:27
sharksappears that way, yes10:28
sharksWhy is vold trying to open system_a directly? It is already mounted...?10:30
T42<elros34> no idea how it works internally. About that tad. From where did you get whole command to run it?10:35
sharksAh, good question, give me a minute to reboot and I will find it again10:35
T42<elros34> ah so from /odm/etc/init/init.sony.rc?10:37
sharksYes10:37
T42<elros34> can yo ushow it?10:37
sharksThe whole file? hold on will upload10:38
T42<elros34> you have also also some service with miscta in name, check whether it works and do not restart10:39
sharkshttps://paste.opensuse.org/pastes/b0c18fa1561410:39
T42<elros34> I guess it woul dbe good idae to strace it directly in rc file, it starts with some custom user/group10:41
sharksI'm sorry, I am still learning how to do all this stuff. Would you mind elaborating? What is the best way to go about doing that?10:42
T42<elros34> I need to remember/find exact command10:43
sharksthanks10:43
T42<elros34> mkdir -m777 /data/strace/ and then change that line which starts tad  to "service tad /usr/bin/strace -ff -s256 -o /data/strace/tad.strace /vendor/bin/tad /dev/block/bootdevice/by-name/TA 0,16". I guess you can override it in disabled_services.rc ir that partition is not writiable10:48
T42<elros34> I wonder where is failing lipstick in your logs10:51
sharksI was googling while you worked that out and found a similar solution, same command but I did another bind-mount in early-init.sh to be able to edit the file. Output here --> https://paste.opensuse.org/pastes/6286d37be51010:51
sharksI assumed lipstick failed because the composer is failing? Seemed to make sense to me as a novice that the graphical environment would fail if the graphics hardware wasn't able to work10:53
sharksBut I don't see where in the logs there is really any mention of lipstick10:53
T42<elros34> openat(AT_FDCWD, "/dev/block/bootdevice/by-name/TA", O_RDWR|O_SYNC) = -1 EACCES (Permission denied)10:57
sharksYou reckon that's the killer? I don't know how to fix it but I'll start researching if you don't have any ideas10:59
T42<elros34> I'm wondering why there is no 'Trim Area using TA version 3' in logcat, clearly binary prints it somwhere. Can you start including commands you are executing10:59
T42<elros34> not just output11:00
T42<elros34> most obvious would be ls -al /dev/block/bootdevice/by-name/TA11:00
sharksOkay device has been up for 15 mins or so therefore not uploading full logcat but "TA version 3" is in logcat. `/usr/libexec/droid-hybris/system/bin/logcat | grep TA` outputs "Trim Area using TA version 3.", "Failed to open /dev/block/bootdevice/by-name/TA (Permission denied)", and "Failed to configure TA library." spammed repeatedly every few ms11:02
T42<nikita_kraev> Any way to support `parse-android-dynparts` for system_b / system_ext_b / any kind of _b slots? I am only getting _a from the mapper (link: https://gist.github.com/nikita-kraev/800409d366bfb7863911ec1bb2871cf5), i can surely reflash hybris-boot in partition a, but i am wondering if there is a way11:02
sharks`ls -al /dev/block/bootdevice/by-name/TA` --> "lrwxrwxrwx    1 root     root            15 Jun  5 18:39 /dev/block/bootdevice/by-name/TA -> /dev/block/sda1"11:02
sharks@nikita_kraev I found the same thing and just reflashed to _a, but I am not the smartest fellow here so I am sure there is a way11:03
T42<nikita_kraev> yeah, i'll probably do that as well, just need to update my systemd mappings since i hardcoded them to have _b slots11:04
sharksLol I did that too!11:05
T42<elros34> @sharks so how this is not included in logcat you uploaded. this strace was simply waste of time if all info are in logs11:05
sharksProbably because the logcat I uploaded was of early boot as requested. As I said the device has been up for a long time now so by now the logcat is mostly spam about tad failing.11:07
T42<elros34> ok so always provide logs which include: all early messages + 2 minutes after boot. I guess this is because this strange idea to pipe everything to file. What about ls -al dev/block/sda1? does it have also rwx for everybody?11:10
sharksexample of current `/usr/libexec/droid-hybris/system/bin/logcat` output spam --> https://paste.opensuse.org/pastes/3bc5ece48c1311:11
sharks`ls -al dev/block/sda1` --> "lrwxrwxrwx    1 root     root             7 Jun  5 18:39 dev/block/sda1 -> ../sda1"11:12
T42<elros34> keep digging untill its no longer symlink11:14
sharks`ls -al dev/sda1` --> "brw-rw----    1 root     disk        8,   1 Jun  5 18:39 dev/sda1"11:15
sharksSorry, I should have realised that needed doing.11:15
sharksSo are the permissions of /dev/sda1 the problem?11:16
T42<elros34> pff no need to. I was also just guessing.11:16
sharksHaha okay11:16
T42<elros34> change to oem_2997 root or add rwx to 'other' group too and see what will happend11:17
sharksYes, I think that fixed tad! --> logcat output: https://paste.opensuse.org/pastes/296def3b03c7, strace: https://paste.opensuse.org/pastes/26fd4b67d1db11:26
sharksNow logcat spam about tad has gone away, we have cleared up room for all the other logcat spam to come to life: https://paste.opensuse.org/pastes/c1693edce2e511:26
sharksAnyway I appreciate your help elros and thanks for putting up with me as I'm learning. Unfortunately it is getting quite late and I have work at 6am tomorrow, so I need to put this aside for the night. If you have any further suggestions I will action them tomorrow after work. Thankyou again11:28
T42<elros34> one less spamming service for the win11:39

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