Friday, 2022-08-19

T42<kreatowastaken> is having a 0.96 MB ramdisk size normal?00:22
T42<kreatowastaken> I usually seen 3 or 4 MB ramdisk on android so00:22
T42<kreatowastaken> maybe thats why it doesnt work00:22
KabouikIs OBS having issues somehow? I don't see how this could build for 3.4 i486 but not other architectures here:01:39
KabouikIt complains about "nothing provides qt5-qtgui >= 5.6.2 needed by qt5-qtwayland-wayland_egl", but qt5-qtgui is available in 3.401:40
KabouikSFOS 3.4 has qt5-qtgui-devel-5.6.3+git25.1-1.14.2.jolla.armv7hl, specifically01:52
T42<kreatowastaken> i think the ramdisk is built incorrectly @elros3404:37
T42<kreatowastaken> i took a look at the contents of it and theres only a compiled init program and fstab04:37
T42<kreatowastaken> theres not any programs, shell scripts or whatever04:37
T42<kreatowastaken> which seems wrong04:37
T42<kreatowastaken> where can i get a prebuilt ramdisk image?04:46
T42<kreatowastaken> if that is possible of course04:46
T42<kreatowastaken> I forwarded the logs from /data/.stowaways/sailfish/init.log to /proc/kmsg06:01
T42<kreatowastaken> so i can get logs now06:01
T42<elros34> so di06:04
T42<elros34> sorry, so do you have init.log? Have you tried modification for usb setup which I suggested06:05
T42<kreatowastaken> uh06:06
T42<kreatowastaken> i extracted the ramdisk06:06
T42<kreatowastaken> then changed this line: `exec > /init.log 2>&1` on init to `exec > /dev/kmsg 2>&1` to get logs06:06
T42<kreatowastaken> so it would forward stuff to kmsg and i can see them06:06
T42<elros34> what about that one line change to get telnet working?06:07
T42<kreatowastaken> i didnt change that line, since you didnt tell me to change it06:07
T42<kreatowastaken> theres a lot of permission denied errors06:12
T42<kreatowastaken> like this06:12
T42<kreatowastaken> `<12>[    6.413607]  [6:           init:    1] can't create /sys/class/android_usb/android0/iSerial: Permission denied`06:12
T42<kreatowastaken> i cut out some parts of the last_kmsg that is relevant (re @kreatowastaken:
T42<kreatowastaken> i can send the full last_kmsg if you want aswell06:14
T42<kreatowastaken> i think those permission denied errors are the culprit but dont know what causes it06:15
T42<kreatowastaken> btw i tested the rndis by trying to boot another ramdisk, it does work06:16
T42<kreatowastaken> just doesnt on hybris ramdisk for some reason06:16
T42<kreatowastaken> i cut out some parts of the last_kmsg that is irrelevant (edited) (re @kreatowastaken:
T42<elros34> You shouldn't have android0 permission errors unless detection failed, change order of 'if' which selects whether to use android0 or configfs06:29
T42<kreatowastaken> detection of what06:30
T42<kreatowastaken> ```06:30
T42<kreatowastaken>     if [ -d $ANDROID_USB ]; then06:30
T42<kreatowastaken>         usb_setup_android_usb $106:30
T42<kreatowastaken>     elif [ -d $GADGET_DIR ]; then06:30
T42<kreatowastaken>         usb_setup_configfs $106:31
T42<kreatowastaken>     fi```06:31
T42<kreatowastaken> do you mean this by changing order?06:31
T42<elros34> yes06:31
T42<kreatowastaken> putting gadget_dir first then06:31
T42<kreatowastaken> anddd06:33
T42<kreatowastaken> it works!06:33
T42<kreatowastaken> im on telnet06:34
T42<kreatowastaken> whats next06:34
T42<elros34> make a PR, there was somebody with similar issue and didn't bother to fix it upstream06:34
T42<kreatowastaken> i will06:34
T42<kreatowastaken> so (re @kreatowastaken: whats next)06:35
T42<kreatowastaken> i guess ill check dmesg first06:35
T42<elros34> ah and you have wrong fixup06:35
T42<kreatowastaken> of what (re @elros34: ah and you have wron...)06:36
T42<kreatowastaken> theres a file called "diagnosis.log"06:36
T42<kreatowastaken> it says `CONFIG_AUTOFS4_FS=y not found in /proc/config.gz`06:36
T42<kreatowastaken> so06:36
T42<kreatowastaken> do i need to enable that option?06:36
T42<kreatowastaken> okay i added that option06:38
T42<elros34> of mountpoints06:41
T42<kreatowastaken> ah (re @elros34: of mountpoints)06:41
T42<kreatowastaken> had that fixup for a while06:42
T42<kreatowastaken> no suprise it didnt work lol06:42
T42<kreatowastaken> guess i made a mistake06:42
T42<kreatowastaken> hope i can get these info from recovery06:45
T42<kreatowastaken> these seem correct though06:49
T42<kreatowastaken> do i have to specify full path like /dev/block/sda1 for example or just sda106:50
T42<kreatowastaken> ls -la /dev/block/bootdevice/by-name output06:54
T42<kreatowastaken> beyond1lte part of fixup-mountpoints06:54
T42<kreatowastaken> checked it, seems to be correct06:55
T42<elros34> so do you still have failed data partition mount in init.log?07:03
T42<kreatowastaken> yes (re @elros34: so do you still have...)07:05
T42<kreatowastaken> no idea why07:06
T42<kreatowastaken> but it seems fixup-mountpoints related07:06
T42<kreatowastaken> i couldnt found any issues tho07:06
T42<elros34> so how did you check fixup-mountpoints? Did you check how partitions are defined in fstab according to hadk-hot?07:07
T42<kreatowastaken> uh07:07
T42<kreatowastaken> i compared these outputs one by one to see if they match up (re @kreatowastaken:
T42<kreatowastaken> i didnt know hadk-hot had something about this ill check that07:07
T42<kreatowastaken> its says to find it in $ANDROID_ROOT/device/$VENDOR/*/rootdir/ but  it isnt there07:11
T42<kreatowastaken> `ls: cannot access '/home/kreato/hadk/device/samsung/*/rootdir/': No such file or directory`07:11
T42<kreatowastaken> @elros34 /dev/block on telnet seems like a link to /dev/07:22
T42<kreatowastaken> `lrwxrwxrwx    1 0        0                1 Aug 19 07:21 block -> .`07:22
T42<elros34> don't bother about it, just open fstab and compare with your fixup changes, clearly there is a typo07:23
T42<kreatowastaken> fstab on what?07:24
T42<kreatowastaken> recovery?07:24
T42<elros34> in device repository07:26
T42<elros34> or in device itself, doesn't matter07:26
T42<kreatowastaken> you mean this?
T42<elros34> yeah this is critical to create fixup-mountpoints. How can you create it without reading fstab07:28
T42<kreatowastaken> well07:28
T42<kreatowastaken> the truth is07:28
T42<kreatowastaken> i didnt07:28
T42<kreatowastaken> i got it from someone else that was working for this device aswell07:28
T42<kreatowastaken> guess he made a mistake07:28
T42<elros34> I guess from Umeaman but he never really finished this07:30
T42<kreatowastaken> it seems correct except there isnt by-name07:30
T42<kreatowastaken> so07:30
T42<kreatowastaken> its `block/platform/13d60000.ufs/userdata` instead of `block/platform/13d60000.ufs/by-name/userdata` on fixup-mountpoints07:30
T42<kreatowastaken> idk if that makes a difference or not07:30
T42<kreatowastaken> got it from dani07:31
T42<kreatowastaken> didnt know there was someone else than him and me that was working on this (re @elros34: I guess from Umeaman...)07:31
T42<elros34> obviously it makes a difference, sed wil not replace path if it doesn't match07:31
T42<kreatowastaken> oh right07:32
T42<kreatowastaken> ill add by-name to all of em then07:32
T42<kreatowastaken> what do i have to do to apply changes after that?07:32
T42<kreatowastaken> do i just
T42<elros34> at least build hybris-hal and flash hybris-boot.img to get telnet at 2323, then you can think about not found fstab in droid hal build log and fix it07:34
T42<kreatowastaken> alright07:34
T42<kreatowastaken> im curious07:35
T42<kreatowastaken> what file does this sed replace stuff on?07:35
T42<kreatowastaken> the fstab.exynos9820 i sent before?07:35
T42<kreatowastaken> okay07:36
T42<kreatowastaken> hopefully itll work this time07:36
T42<kreatowastaken> it seems that it does work!07:40
T42<kreatowastaken> now telnet works07:40
T42<kreatowastaken> without modifications07:40
T42<kreatowastaken> rn the phone has black screen07:41
T42<kreatowastaken> y07:46
T42<elros34> it use fstab and ini*.rc as source and replace by-name paths with direct path to block device. hybris-boot use that info and systemd mount units too07:51
T42<kreatowastaken> ah i see07:53
T42<kreatowastaken> welp07:54
T42<kreatowastaken> i am flashing the one i built rn07:54
T42<kreatowastaken> hope it works07:54
T42<kreatowastaken> black screen07:57
T42<kreatowastaken> and no telnet07:57
T42<kreatowastaken> ok i do have telnet now08:03
T42<kreatowastaken> ```08:04
T42<kreatowastaken> [    5.766540] systemd[1]: system_root.mount: Mount process exited, code=exited status=3208:04
T42<kreatowastaken> [    5.766548] systemd[1]: system_root.mount: Failed with result 'exit-code'.```08:04
T42<kreatowastaken> ```08:11
T42<kreatowastaken> [    6.672745] systemd[1]: dev-mtp.mount: Mount process exited, code=exited status=3208:11
T42<kreatowastaken> [    6.672751] systemd[1]: dev-mtp.mount: Failed with result 'exit-code'.08:11
T42<kreatowastaken> [    6.673268] systemd[1]: Failed to mount FFS mount.08:11
T42<kreatowastaken> [    6.673750] systemd[1]: dev-binderfs.mount: Mount process exited, code=exited status=3208:11
T42<kreatowastaken> [    6.673755] systemd[1]: dev-binderfs.mount: Failed with result 'exit-code'.08:11
T42<kreatowastaken> ```08:11
T42<kreatowastaken> 08:11
T42<kreatowastaken> also these08:11
T42<kreatowastaken> `/bin/mount rootfs /system_root -t rootfs -o remount,bind,ro,nodev` this command fails by`mount: /system_root: mount point not mounted or bad option.`08:20
T42<kreatowastaken> @elros34 /system is empty08:54
T42<kreatowastaken> is that normal?08:54
T42<TheVancedGamer> did you change /system_root mountpoint to /?11:09
T42<kreatowastaken> uh no (re @TheVancedGamer: did you change /syst...)11:09
T42<TheVancedGamer> also replies on telegram side look awful on IRC side11:10
T42<kreatowastaken> yeah forgot, sorry11:10
T42<TheVancedGamer> for now, try changing /system_root in fstab to /11:11
T42<kreatowastaken> which fstab?11:11
T42<kreatowastaken> i am confused11:11
T42<TheVancedGamer> your device fstab11:12
T42<kreatowastaken> @TheVancedGamer that error seems to be gone but its still at telnet11:37
T42<kreatowastaken> hm11:39
T42<kreatowastaken> i rebooted now my dmesg says `[362876.663272] usb 1-2: Product: init-debug in real rootfs`11:39
T42<kreatowastaken> i guess thats a good thing?11:39
T42<kreatowastaken> /system is just empty11:45
T42<kreatowastaken> so is /system_root11:45
T42<kreatowastaken> i think thats the problem11:45
T42<kreatowastaken> shouldnt it have files?11:45
T42<TheVancedGamer> / should have system's contents now11:49
T42<kreatowastaken> system doesnt have anything tho11:50
T42<kreatowastaken> thats the thing11:50
T42<kreatowastaken> i checked system on the recovery, it has nothing in it11:50
T42<TheVancedGamer> ah11:50
T42<TheVancedGamer> wait11:50
T42<kreatowastaken> i think thats the main issue11:50
T42<TheVancedGamer> you need to flash lineage11:50
T42<kreatowastaken> wait11:50
T42<kreatowastaken> is sailfish supposed to install on top of lineage?11:50
T42<kreatowastaken> i didnt now that lol11:51
T42<TheVancedGamer> I think so11:51
T42<edp_17> @kreatowastaken : ALWAYS flash the android base first, THEN the sfos zip on top of it. Otherwise it won't work.12:33
T42<kreatowastaken> yeah i didnt know that until now12:33
T42<kreatowastaken> im doing that now12:33
T42<edp_17> lols, have your read the docs? :)12:36
T42<kreatowastaken> i did but i guess i missed that part12:36
T42<edp_17> :D12:39
T42<kreatowastaken> @TheVancedGamer i flashed lineage, did fstab to / but it is still at telnet for some reason12:43
T42<kreatowastaken> and i have no iea as what is keeping it in telnet12:43
T42<kreatowastaken> system and system_root seems to be mounted12:46
T42<kreatowastaken> ```12:50
T42<kreatowastaken> [    9.000593] systemd[1]: Mounting Droid mount for /dev/binderfs...12:50
T42<kreatowastaken> [    9.010299] systemd[1]: Failed to mount Droid mount for /dev/binderfs.```12:50
T42<kreatowastaken> 12:50
T42<kreatowastaken> only error i saw is this12:50
T42<kreatowastaken> which isnt essential afaik12:50
T42<11> I don't understand what to do with it
T42<kreatowastaken> droid-hal-init.service doesnt work13:05
T42<kreatowastaken> ```13:06
T42<kreatowastaken>   Process: 4850 ExecStart=/bin/sh /usr/bin/droid/ (code=exited, status=6)13:06
T42<kreatowastaken>   Process: 4849 ExecStartPre=/bin/sh /usr/bin/droid/ (code=exited, status=2)```13:06
T42<kreatowastaken> the script that is on the ExecStartPre doesnt exist...13:07
T42<kreatowastaken> no idea why but theres that13:07
T42<KernelPanix> Warning[08/19 13:03:28] : file /etc/ofono/binder.conf conflicts between attempted installs of droid-config-sweet-1-202208191239.aarch64 and ofono-configs-binder-1.1.3-1.3.1.jolla.aarch6413:08
T42<KernelPanix> i get this error (re @KernelPanix: Warning[08/19 13:03:...)13:08
T42<KernelPanix> my repo: (re @KernelPanix: Warning[08/19 13:03:...)13:08
T42<KernelPanix> my device bootloop logo xiaomi 10s and auto reboot15:42
ThaodanYou port your phone not the qualcomm soc15:52
Thaodansm8150 already runs on sfos and sm6150 isn't nile15:52
T42<KernelPanix> yes (re @SailfishFreenodeIRCBridgeBot: <Thaodan>You port yo...)15:54
ThaodanAlso if you want to install repo to /usr , grab it from your package manager, if not use /usr/local15:54
T42<KernelPanix> I want to invite more devs to this channel15:54
T42<KernelPanix> ah okay (re @SailfishFreenodeIRCBridgeBot: <Thaodan>Also if you...)15:55
T42<Verevka86> sm6150 work too (re @SailfishFreenodeIRCBridgeBot: <Thaodan>sm8150 alre...)15:56
voidanix[m]huh? How is msmnile even related to the note 10 pro19:20
Thaodanvoidanix[m]: that's the codename of sm815019:28
voidanix[m]ikr but the SoC is different there, phone codename is sweet19:29
Thaodanvoidanix[m]: which soc is it?19:29
voidanix[m]no wait SM7150 is 732G but the boardconfigs here point to sm6150 (?)19:31
Thaodancodename for that is
T42<kreatowastaken> droid-hal-init has errors
malwhich android base?20:39
T42<kreatowastaken> hybris-18.120:39
T42<elros34> Did you apply all hybris patches like: system/core/0002-hybris-Don-t-create-mount-dev-proc-sys.-when-booting.patch20:56
T42<kreatowastaken> i think no?20:57
T42<kreatowastaken> how do i do that20:57
T42<elros34> looks like, hadk-faq: hybris-17 section about patches20:57
T42<kreatowastaken> i did so but it still gives the same error21:52
Thaodanthis is driving me nuts.. pci-msm-rc 0002:00:00.0: Refused to change power state, currently in D323:20
Thaodansomething makes my modem not suspend23:21
Thaodan(SM8250, Edo, PDX203, Xperia 1 II)23:21
T42<kreatowastaken> when i try to install the zip it says Updater process ended with signal:723:22
T42<kreatowastaken> ```23:22
T42<kreatowastaken> Unmounting System...23:22
T42<kreatowastaken> Updater process ended with signal:7```23:22
T42<kreatowastaken> heres the /tmp/recovery.log23:25

Generated by 2.17.1 by Marius Gedminas - find it at!