Monday, 2021-10-18

T42<adampigg> Rinigus: should submissions to chum always.come from testing?07:07
T42<adampigg> ignore that ... we shouldnt get submissions directly to chum anyway07:55
piggzmal: ping slave pls and ask him to re-submid harbour-valuelogger2 to testing: :)07:55
piggzoops, grep-the-logs is doewn as i didnt pay my vps!07:57
riniguspiggz: slava has been submitting directly to chum for some time now. and then I manually submit to testing. either he got confused with me asking to submit from testing->chum or there is some other reason.09:27
rinigusbut would be good if someone can talk to him face2face. I just couldn't find proper way to communicate it again and again09:28
piggzyeah, everyone shoould only submit to testing, and then admins submit to main right09:28
rinigusin sum: all my fault :)09:28
riniguspiggz: or they can change in testing and then submit from testing to chum main that we accept. this is for already submitted and accepted packages to reduce our load09:29
rinigusactually, few were doing that already and all worked just fine. (few could be n=1)09:30
kquote03[m]Hello, I've tried changing my fixup-mountpoints, and for the love of god I cannot figure out what's wrong. I am pretty sure that this is the issue tho as the log has the same mounting errors. Here's my current fixup-mountpoints ,  here's how the structure is on LOS
T42<elros34> looks sane (except 1 typo) but without seeing fstab I can't be sure. Also did you run make hybris-hal after fixup-mount points adjustments?13:00
malare you sure it finds the fstab file?13:21
piggzrinigus: ^^notice anything odd?15:16
piggzi wonder if i got the wrong icon pack installed15:18
riniguspiggz: where are the icons???15:18
piggzrinigus: yeah, thats what i mean :) i think ive got the wrong pack installed though as i changed the pixel ratio15:18
kquote03[m]<T42> "<elros34> looks sane (except 1..." <- fstab? Android has an fstab? I thought it didn't ..?17:07
kquote03[m]As for hybris hal, no i didnt, ill try that now17:07
T42<elros34> so how did you know what by-name path you should use without fstab? You will find it in $ANDROID_ROOT/device/*/*/17:09
kquote03[m]T42: I did it by using the ls -l command found in the pdf...17:09
kquote03[m]Alright, found the fstab in  the ramdisk folder17:14
kquote03[m]fstab has 10 entries but using ls has 25 entries. does sfos need the other 15?17:17
T42<elros34> fstab is not only place from which mount units are created so it's easier to add all17:18
T42<elros34> .rc files are also used17:19
kquote03[m]so like18:48
kquote03[m]TWRP just crashes when I'm extracting the rootfs18:49
kquote03[m]Thaodan is right, TWRP sucks18:49
kquote03[m]like no joke, when im flashing the zip, twrp restarts mid install, and when i extract the rootfs via adb shell, it goes to a black screen and basically dies18:50
kquote03[m]i will extract the rootfs from android18:50
piggzmal: i have a library in .../lib64/vnd-29/.... but according to strace, that path is never searched, just .../lib64/...18:57
malpiggz: you mean this lib
piggzno, in this case its android.hardware.biometrics.fingerprint@2.1.so19:00
piggzfor fingerprint support19:00
malsame method should work19:00
piggzok, wondered if there was somethng more elegant ... but i guess a symlink will do the job :D19:01
malso a suitable symlink19:01
malyeah, not sure why we have issues with linker19:01
kquote03[m]is there a way i can mount everything manually in debug init shell and continue booting manually?19:14
malwhy is the fixup not working for you, it should be simple to fix19:19
kquote03[m]mal: i know .-.19:20
kquote03[m]it's really weird19:20
kquote03[m]is my phone the one off that bends all the rules???????19:20
kquote03[m]can i try something stupid?19:21
kquote03[m]what if i put /dec/mmcblk0p* in my fixup-mountpoints?19:21
malwhat does the build log tell, it should tell what it sees19:23
Thaodancheck the generated systemd mount units19:48
Thaodane.g. the mount point of system_a is /system not /systemd_a19:49
T42<elros34> are you sure that init.log fails in same place?19:58
kquote03[m]<T42> "<elros34> are you sure that init..." <- Yes,
kquote03[m]<Thaodan> "check the generated systemd..." <- systemd commands dont seem to be available20:13
kquote03[m]<mal> "what does the build log tell, it..." <- Can you clarify?20:13
T42<elros34> search for  "/data appears to live on" on make hybris-hal output and make sure it's correct20:14
kquote03[m]T42: Alright20:14
T42<b100dian> We are all T42 now:)20:20
T42<b100dian> where did I read how to trigger an alarm from commandline? I can't find it..20:23
T42<b100dian> nvm, duck duck went for it
kquote03[m]<T42> "<elros34> search for  "/data..." <- `hybris/hybris-boot/ warning: ********************* /boot appears to live on /dev/block/platform/13540000.dwmmc0/by-name/BOOT`20:46
kquote03[m]Appears to be fine20:46
malkquote03[m]: another question, do you see any fstab* file in out/?20:50
maluse "find out/ -name '*fstab*'"20:50
kquote03[m]mal: this will take time to answer, i did make clean20:50
kquote03[m]yea, fixup-mountpoints wouldnt print anything wtihout that20:52
T42<elros34> hybris -boot do not search for fstab in out/ but in device/. Read Android.mk20:52
malyeah, so it behaves differently from dhd20:52
malwhich is why I asked if fstab is in out20:52
T42<elros34> so asuming HYBRIS_DATA_PART is correct then $(HYBRIS_FIXUP_MOUNTS) "$(TARGET_DEVICE)" "$@" must fail. If your un it manually on hybris-boot_intermediates/initramfs/init you will see whether it replace DATA_PART correctly20:56
mal@elros34 or the fstab file is not copied which leads to no systemd mount services21:03
T42<elros34> he stuck at initramfs21:06
malhmm, then the issue sounds like something else21:08
malare we sure it's mount issue?21:08
malalso are we sure userdata for example is not encrypted?21:08
T42<elros34> yeah init.log shows that DATA_PART points to by-name/DATA path21:10
T42<elros34> there is also something wrong (CONFIG_AUTOFS4_FS) in defconfig but that is next issue21:12
T42<Conrad> I got SFOS 4.0.x build for the Z3 Tablet, but as like the previous version (3.4), the boot stuck, only showing the device logo. Is there a way to debug the boot process and access the log files?21:31
T42<Conrad> Using the adb-shell does not give me any clue.21:31
maladb shell? is it booting to recovery?21:35
T42<Conrad> no, I went into adb. I thought, I might access the filesystem this way21:38
T42<Conrad> ssh needs the password, which I can not set without UI21:41
T42<adampigg> Use adb to set persistent logs, reboot, back in adb, pull the journal to pc amd read21:41
T42<Conrad> ok21:41
T42<adampigg> Or, telnet on 2323?21:41
T42<Conrad> for telnet, I have to go to recovery (?), which is broken to a defect Vol + button21:44
T42<Conrad> I will try with persistent log once I found the option21:44
mint[m]Good evening! I'm trying to build Sailfish for laurel_sprout (Xiaomi Mi A3) using LineageOS 17.1 as a base. I'm reading the FAQ and under chapter 3.4 there's a fix saying `Add to sparse: You may need to replace symlinks with the actual files from your device.`. How do I know if the fixes work as-is with my device?21:51
mint[m]And how would I apply them?21:51
T42<elros34> Conrad  no you do not need recovery for telnet, read hadk pdf, it has instruction how to use telnet21:58
T42<Conrad> wow, indeed there is22:01
T42<Conrad> thanks, I will dig deeper22:01
T42<Conrad> Yup, I got it, as expected there is lipstick troubling around. Thanks so far but I might come back for more.22:11
kquote03[m]<mal> "kquote03: another question, do..." <- There is no file with fstab in its name in $ANDROID_ROOT/out/22:13
kquote03[m]I tried changing the fixup-mountpoints to only include what was in the fstab, it keeps bootlooping22:29
kquote03[m]the screen decreased in brightness22:29
kquote03[m]when i touch the screen it increases in brightness22:29
kquote03[m]it is still on the boot logo tho22:29
kquote03[m]there is no serial device22:30
kquote03[m]i think it actually booted fine now, but the screen is not working22:30
kquote03[m]is there a way i can SSH into it in this state? The phone gave me an IP.22:32
maltelnet is the way in early boot, unless something is wrong22:37
kquote03[m]mal: I can use telnet now? I am assuming that the system is totally booted now22:38
malyou can try "telnet 2323"22:54
kquote03[m]worked. It seems systemctl commands are available and root is properly mounted23:05
kquote03[m]tho just a long term concern, if i am ever able to get this to work, is there a way to disable telnet for security?23:06
kquote03[m]YOSSS YALL BUNDLE VIM23:07
kquote03[m]It seems that framebuffer does not work23:20
kquote03[m]cat /dev/urandom > /dev/fb0 does nothing23:20
kquote03[m]catting /dev/input/event(1-6), every input works, touch screen, buttons, etc23:27
kquote03[m]Alright, how can one begin to debug why the screen won't work? Also as for the mounting issue, I have no idea what I did differently, but seems to not be an issue now23:38
T42<elros34> start by reading hadk-faq and other notes then search for errors in journalctl, dmesg and logcat23:40
kquote03[m]T42: Alright, thanks23:43

Generated by 2.17.1 by Marius Gedminas - find it at!