Friday, 2026-05-29

nightishamanhttps://pastebin.com/ShMQCUMg00:04
nightishamani changed into defaultuser using su and ran lipstick with the correct options manually00:04
nightishamanthis is what happens00:04
malprobably the android side process are not ok because linkerconfig was failing earlier00:11
nightishamanyeah but why does it fail00:34
nightishamanfor some reason it also waits 2 minutes before continuing with booting here: https://pastebin.com/vDv96nk501:08
malI wonder if all modules in system side have been loaded? I don't mean vendor_boot but the modules in /lib/modules in roofs01:16
mal*rootfs01:16
nightishamanaccording to a previous log it detected the modules and loaded them in droid-hal-init01:17
nightishamanbecause stock os has an init.rc for that01:17
malcould you run "getprop vendor.all.modules.ready"01:18
nightishamanthe reason it waits 2 mins is because it runs udev-settle and that timeouts in 2 minutes01:19
nightishamani just found that out01:19
malone thing is that loading modules in sfos side might affect that01:20
nightishamanits not set01:21
malthat could affect how android side works01:21
malif android side i.e. droid-hal-init thinks module loading was not fully done then it will not continue startup properly01:22
malon fp6 which is also android 16, I copied the module lists from the other locations, vendor_dkml and system_dlkm and where ever you might have those (excluding vendor_boot) and added those to sparse/etc/modules.load.d/modules.conf which just contain module names as list (with path or .ko file extension)01:24
malnow with modules loaded in sfos side I added /usr/libexec/droid-hybris/system/etc/init/modules_load.rc with content01:25
malon early-init setprop vendor.all.modules.ready 101:25
malsorry01:25
malthis content https://pastebin.com/Tffu2RT101:25
nightishamanvendor.all.modules.ready seems to be set nowhere tho01:26
malhmm01:26
nightishamani cant find an rc file that does it01:27
nightishamanonly vendor.common.modules.ready is set01:27
malok, then you have different name for it01:27
maland is that set now?01:27
nightishamanyes vendor.common.modules.ready was set01:27
malok01:27
nightishamansetting vendor.all.modules.ready also didnt do anything01:27
nightishamani tried setprop and let it settle01:27
nightishamanthe only mention of vendor.all.modules.ready is that the haptics processor wont enable before it is set01:30
nightishamanso i might add that actually to make sure01:30
nightishamanit seems to be stuck restarting vendor.citadeld and vendor.keymint-trusty, the droid-hal-init01:33
malwhat do you see in logcat?01:33
malone option is to try to strace droid-hal-init01:34
malnightishaman: wait, I see in that journal it's waiting for some device nodes to appear, are you sure none of the .mount services in /usr/lib/systemd/system/ contain some path which contain "by-name" or something01:36
nightishamanmal: some do, mnt-vendor-modem_img.mount for example01:38
malfix those01:38
nightishamanand how01:40
nightishamanshould i use the direct sda id?01:40
malyes, the actual device node like is used in those that were correctly handled by fixup-mountpoints01:41
nightishamanit was only that one01:44
malsome other fails also, maybe different reason01:46
malmnt-vendor-efs_backup.mount01:46
malalso mnt-vendor-persist.mount fails01:46
nightishamanmnt-vendor-persist already uses /dev/sda101:48
malmount: /mnt/vendor/persist: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.01:49
malcheck that the partition is correct01:49
nightishamanit is not mentioned in by-name, idk whether sda1 is the partition01:52
nightishamannvm, im just blind, the partition is correct01:53
nightishamanit seems to be mounted as f2fs by the mount point but its either f2fs or ext4 according to fstab01:54
nightishamanit is an ext4 filesystem01:58
nightishamanso the mountpoint is wrong01:58
nightishamanhttps://pastebin.com/UECQgZpz02:03
nightishamanfixed the mountpoints02:03
nightishamanno progress02:03
nightishamanhttps://pastebin.com/MjtsdGgL02:10
nightishamanlogcat shows this02:10
nightishamanfor keystore2 libandroidicu.so is missing02:11
nightishamani can only find it in apexes02:11
nightishamanalso libtrusty: tipc_connect: cannot open tipc device "/dev/trusty-ipc-dev0": No such file or directory02:12
malyou fixed modem_img mount incorrectly, there should be no block/ in the path, just /dev/sda2902:13
nightishamani fixed it now just /dev/sda2902:20
nightishamanudevadm settle still waits for 2 minutes02:20
nightishamanim really confused02:24
nightishamanhttps://pastebin.com/NnvYmURt02:24
nightishamankeystore2 starts fine earlier but later it doesnt work anymore02:25
nightishamanbut it also has the problem that the keymint trusty doesnt start02:25
nightishamanits waiting for it02:25
malyou should try to strace the droid-hal-init process using strace -p pid_of_droid-hal-init, check the pid to use from ps aux02:27
nightishamanhttps://pastebin.com/i2U5NcZP02:36
nightishamanhttps://pastebin.com/fh7DCsp803:01
nightishamanmy trusty doesnt seem to start properly03:01
nightishamanokay, problem, trusty-virtio is loaded before trusty-ipc03:35
nightishamanquestion is why does android recovery load it in the correct order, but my load_kernel_modules doesnt03:36
T42<Mister_Magister> modules.dep idk07:31
malnightishaman: what does you module loading use?12:03
mal*your12:03
malinsmod or modprobe?12:03
Mister_Magisterbro ims.apk is goldmine, it decompiles co clearly13:54
Mister_Magistermal: yop, callstatechanged is 26 not 24 as in the plugin, i was correct with my assumption, 25 is call  state changed in 1.1, 24 is onSsacStatusChangedIndication on 1.013:57
Mister_Magisterwait now if i correct the indication id's and request id's and response id's, i should be able to use 1.2 interface13:58
Mister_Magisterbasically it has onVopsStatusChangedIndication and onSsacStatusChangedIndication on 1.0 additionally14:19
Mister_MagisterI think i'll bump it to 1.5 regardless14:19
Mister_Magisterand yeah request of 1.1 hangup is id 45 not 4114:24
Mister_Magistereven cancelModifyResponse is wrong on 1.014:27
Mister_Magistermaybe that'll fix rejecting a call14:27
Mister_Magistercool beans there's no 1.1 hangup response14:28
T42<Mister_Magister> theres literally no 1.1 or 1.2 responses14:31
Mister_MagisterI think sending sms on 1.2 works now but i neex other end to confirm15:10
Mister_Magisterat least messages app said it's sent which is new15:11
Mister_Magisteryo i just fixed sms send and receive on volte hell yeah15:23
Mister_Magisterstill cannot reject a call15:23
T42<nightishaman> mal: I modified the first stage Android init to do the kernel module loading and then exit immediately after that, since the order of loading the way Android init does it is important.15:34
malloading of which modules?15:35
malall?15:35
T42<nightishaman> Everything from vendor kernel boot15:35
T42<nightishaman> It’s run in the init ramdisk15:35
malthat is different from what I was talking about15:36
malI meant the other modules which are loaded later in the boot from rootfs15:36
T42<nightishaman> Id have to check that, but the thing currently is, trusty-virtio loads before trusty-ipc even tho trusty-virtio has a soft dependency on trusty-ipc. In Android recovery it loads correctly, but in mine it doesn’t which causes the keymint to fail15:39
Mister_Magistermal: i enabled the not implemented hangup but switched it from 1.2 interface to 1.2 and it liked that15:47
Mister_Magistereverything works now15:47
mal@nightishaman you didn't say what you use for module loading, modprobe or insmod?15:55
T42<the_hiktor> good day, i was building mw packages but it fails15:59
T42<the_hiktor> https://paste.opensuse.org/pastes/2e4bddbf736315:59
T42<the_hiktor> here's the logs15:59
T42<the_hiktor> https://paste.opensuse.org/pastes/08424efff4d615:59
malare you building against 5.0?16:04
T42<the_hiktor> wdym ?16:05
T42<the_hiktor> still dumb to understand that 🥲16:06
T42<the_hiktor> if you could explain in more noob friendly lamguage 🥲16:07
Mister_MagisterI'm not a noob and i'm also confused, but I think he means if you're buliding on 5.0 target16:08
Mister_Magisteras in if your target is 5.0 sfos16:08
T42<the_hiktor> yeah latest16:09
Mister_Magisterlatest is not necessarily 5.0 so verify it16:09
T42<the_hiktor> i just updated to 5.0.0.77 yesterday so yeah16:10
malmaybe go to folder hybris/mw/libhybris16:10
maland check with git diff if it's latest revision16:10
maland that the submodule has been updated also16:10
T42<the_hiktor> that folder doesnt exist16:13

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