Friday, 2023-08-25

T42<parmjotsinghrobot> I think it would be nice that considering SFOS makes all of these scripts and modifications to a user's .bashrc and whatnot, that instead of all this, a new user just for building SFOS is created, so that it is all kept separate and clean00:05
T42<parmjotsinghrobot> Just an idea00:05
T42<Walid> I got black screen for device Samsung note5 N920C, hybris-14.1, sdk,09:00
T42<Walid> rpm/dhd : HEAD detached at 960d6af09:00
T42<Walid> droid-configs/droid-configs-device : HEAD detached at 414d96c09:00
T42<Walid> droidmedia : HEAD, tag: 0.20230605.109:00
T42<Walid> dmesg :
T42<Walid> logcat :
T42<Walid> journal :
T42<elros34> first of all you are building for old but using droid-config/droidmedia recommended for
T42<Walid> so what correct branch (re @elros34: first of all you are...)09:06
T42<Walid> oh i see 0.20211101.009:07
T42<elros34> do not build outdated sailfish there is no point especially while porting09:07
T42<Walid> ok , i will reinstall last sdk and tools09:08
T42<elros34> no need to just next time use correct RELEASE09:09
T42<elros34> this is minor update09:09
T42<elros34> also disable audit via bootparams. You seems to have quite a lot kernel errors. Is sda13 important?09:12
T42<Walid> sda13 is for PERSDATA09:14
T42<elros34> what was you repo?09:19
T42<elros34> have you tried surfaceflinger/minimer/test_hwcomposer?09:25
T42<Walid> no will do it, i just rebuild rootfs with droidmedia branch  0.20211101.009:26
T42<elros34> why? you were supposed to build latest sfos release instead09:28
T42<elros34> this is not even correct version for droidmedia on
T42<Walid> so what correct version for it ?09:30
T42<elros34> correct is
T42<elros34> did you rebuild droid-ha/lubhybris after adding mali quirks?09:34
T42<Walid> yes, i will fix sdk version and rebuild all (re @elros34: did you rebuild droi...)09:35
T42<elros34> cmon I told you that you do not have to. just set RELEASE in .hadk.env09:36
T42<elros34> from where did you get that kernel sources?09:37
T42<elros34> ah android_samsung_noblelte_stock  is probably not correct09:39
T42<elros34> what device repository did you use? I do not see any for lineage-14.109:42
T42<Walid> i use (re @elros34: what device reposito...)09:56
T42<elros34> so which kernel then? android_kernel_samsung_noblelte?10:06
T42<elros34> if yes then did you disable selinux somehow? because in you defconfig it's still enabled10:12
def@elros34: good day, could I have your mind on this? thank you :)12:18
T42<elros34> read errors, its pretty clear: "repo: command not found"12:23
T42<Walid> yes, and the deconfig not yet updated , but /system/bin/getenforce return disabled (re @elros34: so which kernel then...)12:26
T42<Walid> how can i install target/tools ?12:27
T42<Walid> in server there is only
T42<elros34> so ping me when you will upload all your changes12:29
def@elros34, mean it's pretty clear : I have to reinstall it at each reboot of the computer (thats what i understand)12:54
T42<TheVancedGamer> def: did you add `PATH=~/.local/bin:$PATH` to your .bashrc?12:55
T42<TheVancedGamer> it's in repo setup guide12:55
def@elros34: I have to do this each time12:56
defmkdir -p ~/.bin12:56
defcurl > ~/.bin/repo12:56
defchmod a+rx ~/.bin/repo12:56
def@thevancedgamer : im looking12:57
T42<TheVancedGamer> def: there you go, there's your problem12:57
T42<TheVancedGamer> you aren't adding the path export to your bashrc12:57
T42<TheVancedGamer> that's the only thing you're missing, repo is installed fine12:58
def@thevancedgamer : this is within the .bashrc12:59
defalias sfossdk=$PLATFORM_SDK_ROOT/sdks/sfossdk/sdk-chroot12:59
defexport PLATFORM_SDK_ROOT=/home/hd/sf/12:59
T42<TheVancedGamer> def: did you read what I said12:59
T42<TheVancedGamer> you need to add PATH="${HOME}/.bin:${PATH}" to your .bashrc12:59
T42<Umeaman> What online guide is the right one to keep a device tree updated? I mean with older devices that used to be supported by Lineage. I know that there are omnirom repos for AOSP, but to my knowledge a lot of devices that runs AOSP don't have omnirom repos. I guess I can just use a fairly updated unofficial repo that someone used to build a certain version of Lineage with and fork it.13:01
T42<TheVancedGamer> def: are you out of space?13:03
T42<Walid> (re @elros34: so ping me when you ...)13:08
def@thevancedgamer : looks like yes ; but how much space does it takes? pdf says about 15/20GB, looks like it took over 50GB..13:15
T42<elros34> def: Probably you have already filled whole /home/hd from previous attempts. Also again you initialize repo in home. It must be in$ANDROID_ROOT according to instruction, your .hadk.env is incorrect.13:17
def@elros34 : i moved it because / is highly less than 15GB free disk space, instead /home had 50GB for it13:17
T42<elros34> open your home directory and see, I bet it's full of android sources13:18
T42<elros34> @walid this commit is very wrong: It hides issue and can cause time outs and hard to debug issues13:20
def@elros34: hadk folder takes 40GB13:21
defdo I have to resize the partition ?13:22
T42<elros34> I am talking about /home/hd/* including hidden /home/hd/.repo13:22
T42<elros34> just open file manager13:23
T42<elros34> @walid you overwrite CONFIG_CMDLINE, it's not empty by default13:24
T42<Walid> ok i will revert it, but how can i install /update to target ? the latest is (re @elros34: @walid this commit i...)13:24
T42<elros34> I told you several times, you don't do this. You only change RELEASE in .hadk.env. WHat is unclear in that13:25
T42<elros34> btw it's really not necessary to enable all these OPTIONAL file systems from mer-kernel-check13:32
T42<Walid> yes but i found for systemd and SFOS 4.5, there are configs required to make systemd run , like CONFIG_SQUASHFS=y13:34
T42<Walid> CONFIG_XFS_FS=y13:34
T42<Walid> CONFIG_XFS_QUOTA=y13:34
T42<Walid> for example (re @elros34: btw it's really not ...)13:34
T42<elros34> I am talking about  CONFIG_BTRFS_FS CONFIG_NFS_FS and so on13:37
T42<Walid> yes u are right i will clean it, first i want get GUI work13:40
T42<elros34> stop booting in initramfs after reverting that power_supply commit because it might be hard to even telnet13:43
poetasterpiggz, I've this issue on the rephone (GS5) where videos get made, but only at 192x108 pixels. I think it's because the camera is a different one than the GS5. How do I go about debugging?14:41
piggzpoetaster: erm, well probably the vendor partition on that device could be different, with different libs for the camera?14:44
piggzprobably would be wise to get the rephone android-11 vendor paritition, and replacing the one used on the install14:45
piggzyou want to get an image of the vendor partition, and place it here /var/lib/lxc/android/vendor.img14:46
poetasterpiggz, ah thought it'd be a libs issue. But was surprized that the camera took photos normally otherwise.14:49
piggzyeah, that is a bit weird14:49
piggzwhats the difference with the camera?14:49
poetasterI believe it's a 64 vs 48 mp camera.14:51
poetasterpiggz, advanced camera issues a "unknown:0 - CameraBin error: "error initializing video recorder"" and doesn't record.15:06
poetasterpiggz, jolla camera records and shows viewfinder while recording but as mentioned with the wrong res. When booting up advanced camera, it seems to obtain at least reasonable resolutions, when not the higher ones I'd expect.15:07
poetasterunknown:0 - "2560x1440" highest under supported.15:08
poetasterpiggz, logcat
poetasterpiggz, camera around 681 I think.15:57
def@elros34: i started to follow the pdf on another computer with ~500GB disk just for it, it's a huge download still about 32GB of data..18:22
T42<elros34> I hope you do not download it to home now18:29
def@elros34: not especially, but i still have hundreds of GB free ; howeveer, hope it doesnt takes huge tons of space disk...18:50
def@elros34 : on the previous installation, i ran everything especially on /home due to lack of space disk on /, and /home was about 50GB free/avvailable ; i wouldnt thought it was going to take more, as the pdf says about 13GB..18:52
T42<elros34> you don't get the point. I am  not talking about /home (which is root partition)  but /home/$user.18:55
T42<elros34> so to avoid another huge download:  did you follow pdf with every steps in there especially cd $ANDROID_ROOT before running repo init? Where is your .repo directory now?18:57
T42<elros34> maybe that is unclear so: either / /home or /home/<user> are not correct place for repo initialization19:04
def@elros34: it's because on the previous nistallation, / and /home were on different partitions, and / was 20GB total space disk, with less of 5GB free (triboot computer)19:07
T42<elros34> can you answer the question: "Where is your .repo directory now?"19:13
T42<elros34> ok so "~/hadk/" was enough19:30
def@elros34: i have added the m7.xml, do I have to do20:40
defsource build/envsetup.sh20:40
defexport USE_CCACHE=120:40
T42<elros34> like in instruction, yes you need prepare evironment before building android part20:47
def@elros34: okay, but I mean, if i guess well the first repo command was to add like an android source, regadin the device with m7.xml?20:55
defso I can do those both commands without problem?20:55
defrepo init -u -b hybris-11.020:55
deffor me it's obviously related to android, to get some parts to make sailfish working well?20:55
def(but i still discover the system, i might be wrong on few things..)20:56
T42<elros34> how about you read same basic instruction of repo command especially what repo init/sync do. Then follow hadk instruction which is simple: repo init, add local manifest, repo sync, that is really all21:00
T42<b100dian> def: are you using the search on previous errors others have encountered like we all do? would be one. I was a beginner too, but I learned from that as much as I learned from asking21:04
def@elros34: breakfast $DEVICE ; mean I have to do breakfast m7 ?21:17
defbreakfast $DEVICE21:18
defincluding vendor/cm/vendorsetup.sh21:18
defls: cannot access 'device/*/hammerhead/': No such file or directory21:18
defbuild/core/ *** Can not locate config makefile for product "cm_hammerhead".  Stop.21:18
defDevice hammerhead not found. Attempting to retrieve device repository from CyanogenMod Github (
defIm wondering why it's looking for hammerhead instead of htc m721:21
defI have well the  hadk/.repo/local_manifests/m7.xml21:22
def@elros34: do i have to add the htc m7 with repo init plus repo sync? i mean with that one
T42<elros34> you could just read what I say but ok I will repeat 3th you have wrong .hadk.env21:36
defyuo mean this ?  repo init, add local manifest, repo sync, that is really all21:37
T42<elros34> what are you talking about? Open pdf, ctrl+f and search for ".hadk.env"21:38
T42<Walid> so i revert the comment of error message and fix it like this,21:42
T42<Walid> is it safe ?21:42
defelros34: this is the wrong .hadk.env?21:59
defexport ANDROID_ROOT="$HOME/hadk"22:00
defexport VENDOR="htc"22:00
defexport DEVICE="m7"22:00
def# "armv7hl" is still supported, but we encourage to have full 64bit ports22:00
defexport PORT_ARCH="aarch64"22:00
def# Uncomment the next line to conveniently build all RPMs in local repo:22:00
def#alias mb2='mb2 --output-dir "${ANDROID_ROOT?}/droid-local-repo/${DEVICE?}"22:00
defmy thught is, do i have to add the both hybdis-11 plus htc_m7 tree... firstly with init, then sync22:09

Generated by 2.17.1 by Marius Gedminas - find it at!