Thursday, 2021-02-04

mighty17<mal "when does that happen"> When I run make -j4 command to make the images04:02
mighty17<deathmist "mighty17: I mean it probably hel"> It just says error6 and then unable to install zip :(04:03
mighty17Also hi deathmist! I didn't know u were here :D04:03
mighty17> <> when does that happen04:25
mighty17 * When I run make -j$(nproc --all) hybris-hal droidmedia command to make the images04:25
mighty17<deathmist "mighty17: I mean it probably hel"> command? lol i flashed from twrp :/04:37
mighty17<mighty17 "command? lol i flashed from twrp"> even adb sideload gives error6 :/05:42
mighty17idk what i did wrong it used to work before i got as far to able to telnet05:43
mighty17 we also have working sfos although old but i dont know what im doing wrong 😭05:46
malmighty17: can you show more output when that failure happens09:40
mighty17<mighty17 "now any idea for this https://pa"> mal:09:48
mighty17see the pastbin has the log09:49
malmighty17: run "sudo zypper in grep -busybox-symlinks-grep"10:02
mighty17mal: i fixed it by putting that script manually (edited to remove line 36)10:04
mighty17is that not correct?10:04
mighty17<mighty17 ""> another question can i update sfos from here? (it is ancient and has many issues though)10:06
malprobably easier to use the repos used in that only as an example and start for the beginning10:07
mighty17I did everything from scratch like 2 times, firstly I got error of Mount so I redid everything with changed fstab and fixup-mount points now I get error 6 🙁10:12
mighty17okay guys... i have a new problem10:45
mighty17it seems to have booted and tapping on screen shows backlight on but there is no ui or anything10:45
mighty17but i cant get into ssh or telnet or anything
T42<edp_17> mighty17: Try to pull up the network manually. Use this:
mighty17okay any idea what can be wrong?11:03
mighty17i used old fstab (of cm12.1)11:03
T42<edp_17> Probably there is a problem with the mount points, I guess /system is not mounted. But without seeing the device, this is just a guess.11:05
T42<edp_17> That's why I suggested to bring up the network manually and then you can check what's on the device.11:05
mighty17okay im just doing that11:06
mighty17i rebooted to twrp which seems to have removed los/sailfishos11:06
T42<edp_17> Have you tried telnet?11:06
mighty17nope i dont know what ip to put11:06
T42<edp_17> telnet 232311:07
mighty172323? or just 23?11:07
T42<edp_17> 232311:07
mighty17gimme sometime as installing sfos takes some minutes11:09
T42<edp_17> mighty17: a little extract from that site I gave you:
mighty17thanks a lot!! i will try telnet first11:11
T42<edp_17> (This is how I brought up the network manually when the device wasn't reachable via ssh.)11:11
mighty17edp_17 telnet worked11:19
T42<edp_17> What does the mount command say?11:23
T42<edp_17> and what does this? cat /lib/systemd/system/system.mount11:24
mighty17<T42 "<edp_17> What does the mount com"> nothing11:25
T42<edp_17> and thsese:11:25
T42<edp_17> cat /lib/systemd/system/efs.mount11:25
T42<edp_17> cat /lib/systemd/system/preload.mount11:25
mighty17okay let me try11:25
mighty17> <> <edp_17> What does the mount command say?11:29
mighty17 * see this
T42<edp_17> Okay, so you have /system mounted. What's in here: cat /var/lib/environment/compositor/droid-hal-device.conf11:33
* mighty17 sent a long message: < >11:33
T42<edp_17> Change this: EGL_PLATFORM=hwcomposer to EGL_PLATFORM=fbdev11:35
mighty17how do i change that?11:35
mighty17i have to remake sfos then?11:35
T42<edp_17> vi /var/lib/environment/compositor/droid-hal-device.conf11:36
T42<edp_17> then press SHIFT+I11:36
T42<edp_17> Then with cursors navigate to that line and change, then press ESC, then press these thre characters :wq11:37
T42<edp_17> *three11:37
T42<edp_17> But I think the problem is somewher else as the device doesn't get to the stage where it gets an IP address.11:37
mighty17yes it changed and saved11:38
T42<edp_17> Reboot.11:38
mighty17power button right or is there some command11:38
T42<edp_17> you can use the command reboot or the power button. :)11:38
T42<edp_17> How did you install the kernel? Did you used the hybris-boot.img or something else?11:40
mighty17i followed the manual11:42
mighty17<T42 "<edp_17> you can use the command"> still same thing11:43
T42<edp_17> Did you applied the selinux=0 in BOARD_KERNEL_CMDLINE?11:43
mighty17let me see11:43
mighty17 this is my kernel11:43
T42<edp_17> Plus you can check the following:11:43
T42<edp_17> zcat /proc/config.gz | grep CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE11:43
T42<edp_17> zcat /proc/config.gz | grep CONFIG_SECURITY_SELINUX_BOOTPARAM11:43
mighty17<T42 "<edp_17> zcat /proc/config.gz | "> it is set to 011:43
mighty17<T42 "<edp_17> zcat /proc/config.gz | "> it is =y11:44
T42<edp_17> The BOARD_KERNEL_CMDLINE is in the device tree not in the kernel.11:44
mighty17in boardconfig?11:44
T42<edp_17> Okay, then those two flags are fine in the kernel.11:44
mighty17<T42 "<edp_17> The BOARD_KERNEL_CMDLIN"> BOARD_KERNEL_CMDLINE := androidboot.hardware=espresso11:45
mighty17<T42 "<edp_17> Did you applied the sel"> nothing like that is said in the manual11:46
T42<edp_17> Double check that: Section 9.3.1 Bootloops11:49
T42<edp_17> But that is not the case for you because your device is not bootlooping.11:49
T42<edp_17> Okay what these do say:11:50
T42<edp_17>     cat /lib/systemd/system/efs.mount11:50
T42<edp_17>     cat /lib/systemd/system/preload.mount11:50
T42<edp_17>     cat /lib/systemd/system/system.mount11:50
mighty17`cat: can't open '/lib/systemd/system/preload.mount': No such file or directory`11:53
T42<edp_17> These also look fine. (I am not sure that preload.mount still exists.)11:54
mighty17my guess would be that i used cm12.1 fstab but los14.1 as the base rom11:55
mighty17as when i used los14.1's fstab the /system location was wrong11:55
mighty17or the fixup-mount points was wrong11:56
T42<edp_17> I see. Probably that's the problem. You need to fix /system location in the 14.1 base.11:57
mighty17<T42 "<elros34> what? no you seems to "> should i try this11:57
mighty17<T42 "<edp_17> I see. Probably that's "> or fix fixup-mountpoints?11:58
T42<edp_17> Yes/ What is in the fuxup-mountpoints?11:58
* mighty17 sent a long message: < >11:59
mighty17 this is the fstab12:01
mighty17so i followed what elros34 said and used los14.1 fstab with the changes fixup-mountpoints12:08
mighty17hybris/hybris-boot/ ********************* /boot appears to live on /dev/block/mmcblk0p5 /dev/block/platform/omap_hsmmc.1/by-name/KERNEL12:08
mighty17hybris/hybris-boot/ ********************* /data appears to live on /dev/block/platform/omap_hsmmc.1/by-name/DATAFS12:08
mighty17is this correct?12:08
T42<edp_17> This is what I used for my i9100 (galaxy S2):
T42<elros34> first one looks wrong and and is probably reason for sed failure later12:12
T42<edp_17> Have you checked the mount points on android before you started the porting? (HADK Section 5.3 Configure Mountpoint Information)12:12
T42<elros34> you need to remove extra /boot entry from fstan line 26 then it should be fine12:15
T42<elros34> I guess that will also fix issue you opened in mer-hybris/hybris-boot12:15
T42<elros34> Probable there should same safety check for boot as for data partition: ifneq ($(words $(HYBRIS_DATA_PART)),1)12:19
mighty17<T42 "<elros34> first one looks wrong "> To me?12:21
T42<elros34> yes12:22
mighty17<T42 "<elros34> you need to remove ext"> Yes I did it and am making sfos again if it works I'll upstream it12:22
mighty17<T42 "<elros34> yes"> I didn't understand, it just shows it when I run make12:22
mighty17<T42 "<elros34> first one looks wrong "> Sed failure happens no matter what is there12:23
mighty17<T42 "<elros34> you need to remove ext"> I removed from all of them 😲12:24
mighty17<T42 "<edp_17> Have you checked the mo"> Yes :)12:24
T42<elros34> all? 1 line in 1 fstab. Can you show make hybris-hal output now, especially  ********************* /boot appears to live on" part12:25
mighty17It's same output and by all I mean I removed /omap from all the fixup mount points in espresso thing12:27
T42<elros34> I am talking about this line:
mighty17<T42 "<elros34> I am talking about thi"> But u said to remove /omap from fixup-mount points12:30
T42<elros34> that was yesterday, next issue is that entry:
mighty17<T42 "<elros34> that was yesterday, ne"> The sed issue? It can be fixed by putting hybris-updater-script without line 3612:35
T42<elros34> I don't know how it can be fixed that way but anyway you need to remove that line so make hybris-hal will finish without errors12:38
mighty17I removed the line 36 😄12:43
mighty17And make runs successfully12:46
mighty17should i try with sfos3.2.x as sfos3.4 dosent support kernel version 3.0 @elros3412:50
T42<elros34> no, now you should check journalctl and dmesg with your current build12:51
mighty17ok i will check with build having lineageos 14.1 fstab and /omap removed from fixup-mount12:53
T42<elros34> no, use that one you have on device already.12:54
mighty17on device?12:56
mighty17as in the cm12.1 fstab?12:56
T42<elros34> there is no point wasting time and creating new image now because based on your answers to edp17 your mount units are correct12:57
mighty17ohh thats dope12:58
mighty17now what should i do12:58
T42<elros34> just get journal13:00
mighty17 * ?? whats that13:00
T42<elros34> type journalctl --no-page13:00
mighty17in telnet right13:01
T42<elros34> in telnet max 1 min after reboot13:01
mighty17 elros3413:04
T42<elros34> that is all? let it boot for a while to get all logs or use journalctl --no-tail -f so you will see live logs. What about dmesg?13:07
mighty17<T42 "<elros34> that is all? let it bo">
mighty17<T42 "<elros34> in telnet max 1 min af"> oh sorry didnt read this13:09
mighty17<T42 "<elros34> that is all? let it bo"> now?13:10
T42<elros34> ah so droid-hal-init is in dmesg. I wonder why is that for some samsung devices13:10
mighty17any fixes?13:12
T42<elros34> Have you added symlinks mentioned in hybris-14.1 chapter of hadk-faq? What about old cm12 based droid-configs? Check sparse/etc/mod* whether it loads some kernel modules13:15
mighty17<T42 "<elros34> Have you added symlink"> there is no hadk-faq chapter atleast in the latest manual, and i didnt quite understand the 2nd part, check where?13:17
mighty17/home/mighty/hadk/hybris/droid-configs/sparse dosent have a etc folder (this is on my pc)13:17
T42<elros34> about sparse/etc check it in old cm12 droid-configs repo13:18
mighty17okay lemme see13:18
mighty17<T42 "<elros34> about sparse/etc check">
mighty17<T42 "<elros34>">  no i havent run `Run this script in $ANDROID_ROOT`13:19
T42<elros34> you can create those symlinks on device now so you don't have to create new image yet13:20
mighty17oh thats great how do i do it?13:21
T42<elros34> removing "hybris/droid-configs/sparse" in script should be fine I think. Also etc/modules.d13:24
T42<elros34> modules-load.d and modprobe.d from old repo might be useful13:24
mighty17<T42 "<elros34> removing "hybris/droid"> which script? as in how is it possible to do in on the device itself?13:25
T42<elros34> script mentioned in faq13:26
mighty17<T42 "<elros34> modules-load.d and mod"> modprobe.d/droid-hal-espresso3g.conf seems to be about wifi13:26
mighty17<T42 "<elros34> script mentioned in fa"> ??? but i never ran it in the first place13:27
mighty17sorry i cant seem to understand13:27
T42<elros34> so run it now on device just without that part in paths I mentioned13:28
mighty17<T42 "<elros34> so run it now on devic"> i think this is correct13:31
mighty17@elros34 i ran it13:36
mighty17now what?13:37
T42<edp_17> reboot?13:39
T42<elros34> so you already had the symlinks there or you run it twice? Check wheter they are correct13:40
mighty17<T42 "<elros34> so you already had the"> i ran it twice my bad13:41
mighty17<T42 "<edp_17> reboot?"> okay13:41
T42<edp_17> @elros34 : Hi, I have a question for you. I've just seen that 4.0 EA is out. Do you know when can I start building 4.0?13:41
mighty17<T42 "<edp_17> reboot?"> nope still the same13:43
T42<elros34> oh good to know 4 is out!13:43
mighty17<mighty17 "nope still the same"> tapping the display shows backlight but nothing on the screen13:46
mighty17any logs i should send?13:46
T42<elros34> @edp_17 For local build you can probably upgrade target,tooling and try to build it now but for obs you will have to wait after official release and obs targets are ready13:46
T42<elros34> 3.10 minimum kernel bump:(13:49
T42<edp_17> Yeah, that device is not on OBS atm.13:50
T42<edp_17> 3.10? So, doesn this mean that 4.0 cannot be built for my S2 (i9100)? (That's kernel is 3.0.)13:51
mighty17edp_17 s2 has partial mainline support
mighty17and what should i do now?13:53
T42<elros34> @edp17 I don't know yet I need changelog to find reason for this min kernel change13:53
T42<elros34> read*13:54
T42<edp_17> @elros34 : Okay, thanks for looking into it anyway!13:54
T42<elros34> Yeah I also use 3.0 kernel device..13:54
T42<edp_17> mighty17: I know there is partial mainline support for the S2 but not much is working on that unfortunately, so I stay with its original kernel.13:55
mighty17you can mainline xD13:55
mighty17even im trying to mainline my device (it has 3.0 kernel)13:55
mighty17<mighty17 "and what should i do now? "> ??? rebuild sfos or what? this is confusing13:58
T42<edp_17> No, at the moment you don't need to re-build neither the kernel nor the sfos image. Now you are fixing everything on the device. Once it works, then you can go back to PC and apply all the stuff in there you amended on the device and then re-build the image. This way, you'll get a working image with the less re-builditeration.14:01
mighty17that is great but what should i do xD14:05
mighty17it still dosent work on device14:05
mighty17i cant understand what the problem is, is it fstab? is it sfos 3.4 dosent support kernel 3.0? what is it14:07
T42<edp_17> SFOS 3.4 does support that kernel as I am using that on my galaxy s2 which also has kernel version 3.014:20
mighty17thanks to patches from elros :)14:20
mighty17also if u have any idea for my problem ping me i am shutting down the device for now14:20
mighty17btw it does say charging ??/100 though14:21
T42<edp_17> I just checked the targets and tooling url and both of them are available for Great! I'll skip building 3.4 and will move on to 4.0. 😊14:29
mighty17<T42 "<edp_17> I just checked the targ"> But kernel patches? Aren't u on 3.014:41
T42<edp_17> That device (Note 4 treltexx) I was referring to has 3.10.9 so looks like can get 4.0. 😊14:43
mighty17Ooh that's great!!15:04
mighty17Btw @edp_17 should I try with 3.2.x version as it officially supports 3.0 kernel? I'm so tired of making this work15:04
T42<elros34> how about you answer this: Building older sfos release will on create more issues15:11
T42<edp_17> mighty17: I don't think SFOS 3.2.x does officially support kernel version 3.0. If it did support, I wouldn't needed Elros' glibc patch.15:29
T42<edp_17> Although, with Elros' glibc patch you cna try building 3.4 because that works for sure. (At least it works on my S2, so potentially that could be built for other devices too.)15:29
mighty17<T42 "<edp_17> mighty17: I don't think"> In his pr he.says sfos 3.3.0.x needs kernel ≥ 3.2 so 3.2 would support kernel 3.015:30
T42<edp_17> @elros34 : So, are you suggesting to not sweat on and accept that on those old devices the latest SFOS version is 3.4?15:31
mighty17<T42 "<edp_17> Although, with Elros' g"> Yup it does work I can see it show charging ??/100 but other than that we might need to fix some stuff15:31
mighty17* In his pr he.says `sfos 3.3.0.x needs kernel ≥ 3.`2 so 3.2 would support kernel 3.015:31
mighty17But I don't know how to fix it15:32
T42<elros34> @edp_17 hm? I will try everything to get it working on 4.0.1. So far I did not find anything except big systemd upgrade which might be the culprit15:36
T42<adampigg> warning, systemd breaks ports15:38
T42<adampigg> see ^^ for fix15:39
T42<adampigg> basically, no user session starts15:39
T42<edp_17> @elros34 : Don't missread me, I wasn't complaining. At all. 😊 I just stated that might be 3.4 is the last available version for that device. Don't waste time on that if something not obvious or very difficult. Thanks for you glibc work, what we already achieved with that device is incredible!15:41
T42<elros34> I will spend time anyway because I want to have it on my ancient device15:43
T42<edp_17> Then, your work for your own device will be the added bonus for all of us. 😃15:45
mighty17ya thanks 😃17:14
mighty17<mighty17 "Yup it does work I can see it sh"> anyone?17:16
T42<godogabor> How can I do this? "However, if the user first directs the voice to the HF speaker and then back to the headset, the voice can be heard at the headset."17:40
rinigus@adampigg: why is that systemd fix needed? Wondering if it's needed for ports that follow official version closer...18:37
T42<adampigg> rinigus: afaik its related to kernel version ... not needed on new kernels18:37
rinigusGood, which kernel do you have?18:41
rinigus@adampigg ^18:42
T42<adampigg> rinigus: 4.4.15318:43
rinigus@adampigg: ok, we are on 4.9. but 4.4 is not the oldest one...18:53
T42<adampigg> rinigus: cgroups v2 came in kernel 4.5, so i expect it will impact <= 4.418:58
mighty17can u guys help me? see the chat above i just get backlight when i touch the screen (device - espresso3g base - LineageOS 14.1 SFOS Kernel - 3.0.101)19:01
rinigus@adampigg: but in that case older official devices would have to use the same trick with systemd19:34
T42<adampigg> rinigus: i think they do, im sure mal used it in an official repo somewhere19:35
rinigus@adampigg: ok, good to know it's about kernel version. Thanks!19:36
T42<W %lastname%> sdk platform for sfos where can I download it?19:46
malrinigus: about that systemd fix piggz did
maland yes, it's about kernel version19:52
mal@adampigg interestingly old enough kernel are fine without that fix19:53
piggzmal: its a shame systemd doesnt detect the required features19:54
malpiggz: for example 3.10 kernel of xperia x didn't need it based on git log19:54
T42<Heng %lastname%> In ssu what does "Waiting" mean?21:05
T42<Heng %lastname%> trying to update to 4 but seems hung21:06
T42<elros34> @edp_17 false alarm so far everything works good on and 3.0 kernel22:01
T42<adampigg> cool .... hopefully be ok on latte then22:16

Generated by 2.17.1 by Marius Gedminas - find it at!