Friday, 2022-03-18

T42<edp_17> @elros34 : I need your help. Yesterday I built an image with los 17.1 base. It boots but stucks on the logo. There was no telnet, so I manually brought up the network and telnet-ed in. I've seen there was no /system mounted. (Actually there were only a few partitions mounted.) I've also seen in dmesg that selinux=enforcing.10:52
T42<edp_17> mounts and init.log:
T42<edp_17> dmesg:
T42<edp_17> I've added BOARD_KERNEL_CMDLINE := selinux=0 into and CONFIG_SECURITY_SELINUX_PERMISSIVE=y into defconfig but none of them helped.10:52
T42<edp_17> Oh, and I don't have logcat because there is no libexec in /usr.10:54
T42<edp_17> And I had to use port 23 when telnet-ed in. (2323 didn't work)10:55
T42<elros34> line 14 in your init.log10:58
T42<elros34> selinux looks good at least at kernel level10:59
T42<edp_17> BOOTLOGO= ?10:59
T42<edp_17> Oh, 14 not 4. Sorry.10:59
T42<edp_17> This? DATA_PARTITION=/dev/platform/15540000.dwmmc0/by-name/USERDATA11:00
T42<edp_17> What this should be?11:00
T42<edp_17> I see, this is in section 5.3 Configure Mountpoint Information in HADK.11:04
T42<edp_17> I'll flash the los17.1 to see what it is using, then will need to update fixup-mountpoints. Right?11:05
T42<elros34> no, you just check your fstab11:05
T42<elros34> and fill fixup-mountpoints accordingly11:05
T42<Spidey24Z> You need to specify mmc block number in fixup-muntpoints (re @edp_17: This? DATA_PARTITION...)11:06
T42<elros34> one entry for data you already know from init.log, rest will be probable the same but still worth to check11:06
T42<Spidey24Z> Hey @elros34 how are you doing?11:08
T42<elros34> hi, whats up?11:09
T42<Spidey24Z> Good, what about you ?11:10
T42<edp_17> @elros34 : I've used the same in fixup-mountpoints that worked for los14.1. This:
T42<elros34> but your fstab is different now, it's all about entries in fstab and rc files11:11
T42<Spidey24Z> I build hybris 16 tomorrow and it booted but stuck on iniramfs11:12
T42<edp_17> @elros34 : I see. Where should I check fstab, on device or somewhere on local repo?11:12
T42<elros34> in device repo11:13
T42<edp_17> There are a few fstab in different locations and all are the same:
T42<elros34> device repo -> your device specific repository -> $ANDROID_ROOT/device/$VENDOR/*/11:20
T42<edp_17> In there I have a recovery.fstab and fstab.universal5433 :
T42<edp_17> How should I know what mmcblk0p* is BOOT or SYSTEM or USERDATA?11:38
T42<elros34> you do not know after porting all these devices? According to hadk you run ls command in android/recovery11:40
T42<edp_17> Yeah, I am in recovery currently and checking the mounts there.11:40
T42<elros34> ls -l /dev/block/platform/15540000.dwmmc0/by-name/11:41
T42<edp_17> This is what I wanted to do but you said just check fstab. :)11:44
T42<elros34> sorry I assumed you already done this trivial part long time ago and you just wondering why mounting /data in initramfs doesn't work11:46
T42<edp_17> No worries. :) I am flashing Los17.1 to do that check.11:47
T42<edp_17> I don't know either why that didn't work.11:47
T42<elros34> what for, recovery is more than enough, you could even check this gpt labels in telnet now11:48
T42<edp_17> In fixup-mountpoints, I've created a section for treltexx:
T42<edp_17> Do I need all of those partitions?12:06
T42<elros34> usually not all but it will not harm and save you time later in case you did not add some required partition12:08
T42<edp_17> Thanks.12:10
T42<edp_17> Now the device shows the Sailfish os logo. Although, for too long by now. :)12:10
T42<elros34> Anybody familiar with mb2 knows how to build glibc easily? I do not remember exactly but I think previously "mb2 -s glibc.spec  build --doprep" worked but now looks like "build --prepare" do not unpack required archive before applying patches12:42
T42<elros34> I can see in obs there is: "/xz -dc /home/abuild/rpmbuild/SOURCES/glibc-2.30.tar.xz" step which is missing in mb2 prepare12:53
ThaodanWhy do you want to rebuild glibc?13:11
T42<elros34> ok so not really solution to make it automatically but I think it worked in some older release. I build it because of old kernel required changes.13:15
T42<Kai> i have a vollaphone ... :)13:29
T42<Kai> Forwarded from Kai: So i have some  question i do not find answers easily.13:29
T42<Kai> 1. Screenshot taking works exactly one time - after that phone crashes or restarts ... can not figure out what of both13:29
T42<Kai> 2. Camera video taking does not work, that is - if you stop the record the app hangs and asks if i want close or wait (happens with both the preinstalled and your adnvaced camera app from chum)13:29
T42<Kai> so - may be i do something wrong or this are bugs ?13:29
T42<Kai> hi all - i got logcat error grep working :
T42<Kai> Forwarded from Kai: Just forwarded13:29
T42<Kai> Forwarded from Kai: Its a cam problem13:29
T42<Kai> Forwarded from Kai: I can not record videos :(13:29
T42<Kai> hi all , i have some  question i do not find answers easily.1. Screenshot taking works exactly one time - after that phone crashes or restarts ... can not figure out what of both 2. Camera video taking does not work, that is - if you stop the record the app hangs and asks if i want close or wait (happens with both the preinstalled and your adnvaced camera app from chum) :
T42<Kai> i have a vollaphone13:31
T42<Kai> and can not record video ...13:31
T42<Kai> image capture works fine ... also recording i think up to the point where i stop recording ...13:32
T42<Kai> thx for any help :)13:32
T42<elros34> would be good if you provide exactly sfos version you use. I think no screenshots is known issue for volla13:34
T42<Kai> sfos ... yes screenshot is not a big issue for me but video recording would be nice ...13:36
T42<Kai> may be it works with older version of sfos ?13:36
T42<edp_17> @elros34 : Do you apparently know how to fix the following? When I want to flash it fails with "This package is for device: trelte, treltexx,tre3gxx; this device is ." It looks like the device "identifier" is blank. As a quick workaround I've commented out that check in the updater-script but would like to fix it properly. (Never seen this before on older sfos.)13:47
T42<edp_17> I got the same message when tried to flash the los17.1 zip file so is it possible that somehow it came through from there to sfos and it has built into the
T42<elros34> check what getprop returns in recovery, it should have ro.product.device but maybe your codename is in different property13:49
T42<elros34> could be just broken recovery13:50
T42<edp_17> The same recovery is used for flashing other zips. Plus, the same sfos version with cm14.1 base works fine. That's why I thought it could be the new android base somehow.13:57
T42<edp_17> Do you know the default password for defaultuser?13:57
T42<elros34> there is no default password13:57
T42<edp_17> Thanks.13:58
T42<edp_17> After fixing the mount points, the device booted but stucks on the sailfish logo (yamui). Although ssh started, I cannot ssh in as couldn't set password for either defaultuser nor root. Telnet works though.14:00
T42<elros34> I think 'passwd defaultuser' should do the job but it's not really needed, you can always "su -l defaultuser" from telnet if you need it.14:19
T42<edp_17> Thanks. I've used only 'su defaultuser'14:50
T42<edp_17> All these these services are failed: droid-bootctl.service, droid-hal-init.service, droid-late-start.service, systemd-tmpfiles-setup.service and wait_for_keymaster.service. I guess one of them is responsible why the device stucks on the sfos logo, right?15:13
T42<edp_17> Oh and some user services as well: jolla-startupwizard-pre-user-session.service, lipstick.service and pulseaudio.service.15:14
T42<edp_17> journal:
piggzjusa: hi, did you get my logs?15:20
T42<edp_17> It looks like the issue is "library "" not found". However, it's there:
T42<edp_17> This was the file ( which was missing and therefore, the droid-hal didn't build and I needed to manually copy it. And I commenetd out the relevant part in
T42<edp_17> That's why I got this error. I have to rebuild droid hal again.15:28
T42<elros34> you need to change /system entry in fstab to / and rebuild droid-hal16:05
ThaodanNot really SFOS is /, you need to mount bind /system_root/system to /system or package it.16:11
T42<elros34> and this is automatically handled if your fstab use / for system instead /system16:11
T42<edp_17> In fstab where? I don't have any fstab in $ANDROID_ROOT/device/$VENDOR/*/16:37
T42<elros34> sure you have, you showed it few hours ago but make sure changes are also in fstab in  out/16:39
T42<edp_17> Ah yes, I mixed up and looked for fstab in vendor/* rather than device/*. Found and amended them both, fstab.universal5433 and recovery.fstab.16:43
T42<edp_17> Don't need to rebuild hybris-hal?16:44
T42<elros34> yes you need16:45
T42<edp_17> Okay.16:49
T42<Kai> someone use vollaphone ?21:52

Generated by 2.17.1 by Marius Gedminas - find it at!