Thursday, 2023-03-23

T42<b100dian> mal: I think that if you build hybris-hal without droidmedia, the latter target isn't evaluated anymore, when you actually make droidmedia. I even touched the hybris-boot and it didn't build anything (nothing to do).00:42
T42<b100dian> Getting the targets and listing them in the make command works. Just saying that reports of people not being able to run —gg _may_ be because of something like this.00:42
malnot quite sure what you mean00:43
T42<b100dian> Well for the last week I've been just making `hybris-hal` or `hybris-recovery` specifically. Now I started to create the repos for hal, config, and version and went through -d -c -m -g -v build and —gg failed. I went to make droidmedia but "nothing to do" says ninja00:47
T42<b100dian> the droidmedia target is in hybris boot right? droidmedia: $(shell external/droidmedia/ $(PORT_ARCH) $(TARGET_ARCH))00:48
T42<b100dian> Maybe that is not evaluated.. all the time00:49
malmaybe I need to test that, you are sure the environment was properly setup i.e. PORT_ARCH for example00:49
T42<b100dian> Yes, I needn't change that. Not sure about TARGET_ARCH, that looks like coming from the Android mk files00:51
malit's from android build00:51
malbut just in case check in the build env "echo $PORT_ARCH"00:51
T42<b100dian> Yes, it is aarch6400:52
T42<k1gen> I have the same situation with -g that b100dian described06:03
T42<elros34> but why do you even build droidmedia again? You build it once and forget for the next release07:47
T42<k1gen> I don't even know what droidmedia is ¯\_(ツ)_/¯07:51
T42<elros34> so why do you keeps building it then07:52
T42<elros34> what excatly error you have when running -g?07:54
T42<k1gen> I'm not home, I'll send exact error when I come back08:01
*** Danct12 is now known as Guest863510:11
*** amccarthy is now known as Guest863610:27
*** amccarthy_ is now known as amccarthy10:27
T42<k1gen> @elros34
T42<k1gen> mal: I tried to build, I have an error:
T42<k1gen> mal: also, should I define in makefstab_skip_entries only partitions from BoardConfig's AB_OTA_PARTITIONS or BOARD_GOOGLE_DYNAMIC_PARTITIONS_PARTITION_LIST?16:53
maldynamic ones, probably the list I mentioned yesterday17:29
malnot sure about that build error17:30
T42<k1gen> @elros34 any clues why parse-android-dynparts doesn't build?17:49
T42<k1gen> here's more log:
T42<k1gen> sorry, forgot to recurse submodules. it built fine with -b hybris/mw/parse-android-dynparts with manual cloning instead of --mw=
T42<k1gen> mal: is it safe to copy contents of your systemd mount units for dynparts my device has?18:26
T42<k1gen> stuff like What=/dev/mapper/dynpart-system_ext_a, shouldn't it be unique? if yes - where do I get it?18:29
T42<k1gen> also, do I have to add in _a in systemd mount units?18:35
piggzmal: do you know where repomd-pattern-builder is?
T42<k1gen> mal: what does sda10 represent in your
piggzmal: found issue19:38
T42<b100dian> mal: yesterday droidmedia build was PBKAC, I am building Android bits on host shell and didn't have PORT_ARCH there, and of course I tested in PlatformSDK$ when you asked.20:00
T42<k1gen> damn, I guess mal is really needed in this chat when he's offline :D20:02
T42<parmjotsinghrobot> 5 in 7 of the last messages have mal in them20:03
T42<b100dian> he'll pick it up later. I had a 'follow-up' :)20:04
T42<b100dian> @k1gen still have problems with droidmedia?20:04
T42<k1gen> @b100dian yeah, here's log of rpm/dhd/helpers/ -g:
T42<b100dian> Unfortunately is not the problem I "had". The 'More than one file on a line' seem to reference droid config files :scratches-head:20:11
T42<elros34> its issue related to wrong droid-hal-device submodule20:13
T42<k1gen> I think in there should be dmsetup create --concise "$(/usr/bin/parse-android-dynparts /dev/<my android super partition block device, defined in fixup-mountpoints>)". am I right?20:13
T42<k1gen> @elros34 there's no *hal* in this log, that's why I asked. how do I fix it then?20:15
T42<elros34> revert what you did before rebuilding droidmedia.. but seriously just search in channel logs its, really there or follow recommended revisions from hadk-hot. I assume you already had correct version previously20:16
T42<k1gen> "revert what you did before rebuilding droidmedia" that was literally a week ago20:18
T42<k1gen> also, I already use droidmedia-0.20220929.0, recommended in hadk-hot20:19
T42<k1gen> oh, you mean dhd. how do I revert repo, already populated with my device configs to 960d6af?20:21
T42<elros34> git checkout20:23
T42<k1gen> and no local changes will be deleted?20:25
T42<elros34> you do not make local changes in submodules20:26
T42<elros34> at least you shouldnt20:26
T42<k1gen> well I deleted kf5bluezqt-bluez4 from helpers/build_packages.sh20:28
T42<elros34> minor change, you can always git stash and git stash pop20:33
T42<k1gen> I reverted dhd & dhc to versions recommended in hadk-hot, same error:
T42<elros34> yeah some droidmedia leftovers, make sure you remove anything droidmedia related from mw/ or maybe some other places too20:35
T42<elros34> anyway there is still no point building droidmedia again your previousl rpms were removed20:37
T42<k1gen> droidmedia built successfully after rm -rf hybris/mw/droidmedia-localbuild20:37
T42<k1gen> I know I shouldn't reply because of irc, but I want to come back to dynparts. also, thanks for helping with droidmedia (re @k1gen: I think in dmsetup.s...)20:38
T42<elros34> whole instruction is for dynamic partitions so yes its about that block device20:40
T42<k1gen> ok, and what should I rebuild to get these changes to my device?20:41
T42<k1gen> -d -g?20:41
T42<elros34> think what do you change?20:41
T42<k1gen> *-i instead of -g20:41
T42<elros34> which package do you modify? then rebuild that one20:42
T42<k1gen> -c to rebuild droid-configs, then -i to pack rootfs, right?20:43
mal@k1gen that sda10 is the super partition20:44
T42<k1gen> got this already, thanks :)20:45
malok, good20:45
T42<k1gen> glad you're back online20:45
maldo you have some open questions?20:46
T42<k1gen> do I have to add in _a in systemd mount units?20:51
malwhat do you mean? to name of service or somewhere inside?20:52
T42<k1gen> for example What=/dev/mapper/dynpart-system_ext_a in system_ext.mount20:52
T42<k1gen> also, why is system.mount differents than others? Type=none and Options=bind instead of fstab mount args20:53
malyou can see what you need if you run the command from manually i.e. dmsetup create --concise "$(/usr/bin/parse-android-dynparts /dev/sda10)" and then check what appears in /dev/mapper/20:53
malthose mount services should be the same in most cases unless you need to remove the _a, run the command (with correct device node of course) and then check what appears in /dev/mapper/20:54
malthose Type=none Options=bind will be the same always20:55
T42<k1gen> ok, got it. what's the best way to use new rootfs?20:57
T42<k1gen> delete /data/.stowaways/sailfisos, then create it, unpack tar.gz?20:57
malthat is one way, but for testing you can just copy the file manually without rebuilding rootfs20:58
malof course remember to add any working changes to droid-configs regularly so you won't forget things20:58
T42<k1gen> alright20:59
T42<k1gen> is there any way to turn off the display over ssh?21:02
maldepends on how far the boot is21:07
T42<k1gen> well you have my latest journalctl :)21:08
malI think you should now figure out those mounts and then we can look into other issues21:16
T42<k1gen> yeah, I agree21:17
T42<k1gen> mal: new journal:
T42<k1gen> also, there's no parse-android-dynparts on device somehow21:52
T42<k1gen> can I copy the binary to device over ssh? where is it on the host?21:56
kcrootHello All21:59
kcrootcan someone have sfos image for Nexus 5X ?22:00
mal@k1gen you can copy the rpm from $ANDROID_ROOT/droid-local-repo/$DEVICE and then install it on device using rpm -i filename.rpm22:05
T42<k1gen> thanks, I'll write back22:06
T42<k1gen> did you read the journalctl output?22:06
T42<k1gen> here's output after dmsetup create --concise "$(/usr/bin/parse-android-dynparts /dev/sda14)":
malok, so you don't have odm there so either it doesn't exist at all or it's normal partition, in any case from my example skip the odm from mount services and from the droid-hal spec skip line22:12
T42<k1gen> already. odm didn't exist even in lineage-18.122:12
T42<k1gen> so, are we done with dynparts?22:13
T42<k1gen> mal: ?22:26
T42<k1gen> there's only control in /dev/mapper until I manually run dmsetup create --concise "$(/usr/bin/parse-android-dynparts /dev/sda14)", weird22:35
T42<k1gen> goodnight, I'll come back in the morning :)22:42
T42<b100dian> @DennisSwe I think you can harvest info from Seems old and probably unmaintained.22:43
mal@k1gen some devices don't have odm, it's fine, the dmsetup is run by the script I linked yesterday22:49
mal@k1gen are you sure you enabled the dmsetup.service and have also the in correct place (with executable bit set just in case)22:51
T42<k1gen> mal: will you be online in ~8-9 hours? I can't check it now, but thanks for suggesting22:52

Generated by 2.17.1 by Marius Gedminas - find it at!