**** BEGIN LOGGING AT Sun Mar 03 02:59:56 2019
Mar 03 07:28:39 <ubptgbot> DibyaXP was added by: DibyaXP
Mar 03 07:28:46 <ubptgbot> <DibyaXP> Hi everyone
Mar 03 07:33:48 <ubptgbot> <DibyaXP> Is it possible to have a sound cloud app for Ubuntu phone?
Mar 03 09:53:25 <thatannoyingguy4> can't run halium-install-standalone: update-binfmts: warning: qemu-arm not in database of installed binary formats.
Mar 03 09:53:25 <thatannoyingguy4> update-binfmts: exiting due to previous errors
Mar 03 09:53:26 <thatannoyingguy4> I installed binfmt- support but I also have systemd-binfmt somewhere on the system
Mar 03 11:01:30 <thatannoyingguy4> Binfmt stuff seems to have been resolved but I still end up on the error /bin/bash: dpkg-reconfigure: command not found. It seems as if it doesn't want to enter the chroot
Mar 03 11:11:06 <ubptgbot> <Walid> is this rootfs work ubports-touch.rootfs-xenial-arm64.tar.gz?
Mar 03 11:26:46 <ubptgbot> <JBBgameich> Can you modify the script to run echo  $PATH instead? Maybe the path variable is not correctly setup inside the chroot.
Mar 03 11:58:26 <thatannoyingguy4> I tries to build the ubuntu touch rootfs which can now be mounted in the hybris recovery. Now the line in my pastebin with mmcblk0p21 on /target/data is now /dev/block/loop0 on /target. Up inspecting /target, I see many directories with the name of android directories like persist,firmware,vendor etc which I can't check the content of (ls: /target/cache: No such file or directory). The fstab of my device
Mar 03 11:58:26 <thatannoyingguy4> doesn'include these partitions but I've got the feeling that I haven't qdded those partitions to the fixup-mountpoints. I'll try to rebuild and retry
Mar 03 12:48:20 <ubptgbot> <dohniks> I  see many directories with the name of android directories like persist,firmware,vendor etc -> I think thats good
Mar 03 12:49:06 <ubptgbot> <dohniks> which I can't check the content of (ls: /target/cache -> taht's a bit strage, are you doing ls /target/cache or ls /data/target/cache
Mar 03 12:49:27 <ubptgbot> <dohniks> either way, I think you're good to try booting halium reference rootfs
Mar 03 12:49:44 <ubptgbot> <NotKit> @Walid, kinda, it boots on Gemini from time to time, but more problems than with armhf yet
Mar 03 12:50:24 <ubptgbot> <dohniks> [Edit] which I can't check the content of (ls: /target/cache -> taht's a bit strage, are you doing ls /target/cache or ls /target/data/cache
Mar 03 13:10:15 <thatannoyingguy4> I'm doing /target/cache. Upon checking init.log of the recovery I see the line mount --bind /data/ /target/data
Mar 03 13:10:16 <thatannoyingguy4> mount: mounting /data/ on /target/data failed: No such file or directory. ls /target shows as if something called data exists in the /target directory but ls /target/data says no such file or directory
Mar 03 13:23:47 <ubptgbot> <dohniks> https://github.com/Halium/hybris-boot/blob/master/init-script#L148
Mar 03 13:34:33 <thatannoyingguy4> The /data partition exists and hast the same contents as /data on android. the rootfs.img is mounted on /target, that isn't the problem.
Mar 03 13:35:37 <ubptgbot> <dohniks> well, then I think there is no problem, right? can you boot halium rootfs?
Mar 03 13:36:40 <thatannoyingguy4> there is a problem: /data can't be mounted on /target/data
Mar 03 13:37:17 <ubptgbot> <dohniks> how do you know that this is a problem?
Mar 03 13:37:29 <ubptgbot> <dohniks> honest question. it might be! I just don't see it right now
Mar 03 13:39:18 <thatannoyingguy4> It just worries me because the init.log tells me it failed to mount /data on /target/data. Why would it try to mount it when it isn't important?
Mar 03 13:39:55 <ubptgbot> <dohniks> who knows :)
Mar 03 13:40:05 <ubptgbot> <dohniks> do you know what exactly it is trying to mount?
Mar 03 13:40:07 <ubptgbot> <dohniks> https://github.com/Halium/hybris-boot/blob/master/init-script#L151
Mar 03 13:40:18 <ubptgbot> <dohniks> what is ${data_subdir}
Mar 03 13:41:12 <ubptgbot> <dohniks> is there a data_subdir in your kernel commandline?
Mar 03 13:43:36 <thatannoyingguy4> no
Mar 03 13:44:05 <ubptgbot> <dohniks> so I guess it tries
Mar 03 13:44:19 <ubptgbot> <dohniks> mount —bind /data/ /target/data
Mar 03 13:44:35 <ubptgbot> <dohniks> what exactly is the error you get?
Mar 03 13:45:27 <thatannoyingguy4> quick question: what's the difference between hybris-boot and halium-boot? mount: mounting /data/ on /target/data failed: No such file or directory
Mar 03 13:47:05 <ubptgbot> <dohniks> different initrds
Mar 03 13:47:18 <ubptgbot> <dohniks> hybris-boot supports reference rootfs and plasma
Mar 03 13:47:25 <ubptgbot> <dohniks> halium-boot supports ubports
Mar 03 13:49:02 <thatannoyingguy4> oh okay. I'm using the ubports rootfs so halium-boot is still the right img. I thought I had to change the boot.img
Mar 03 13:49:52 <ubptgbot> <dohniks> wawawawait
Mar 03 13:50:06 <ubptgbot> <dohniks> aren't we telnet debugging in hybris-recovery.img ?
Mar 03 13:50:17 <thatannoyingguy4> yes
Mar 03 13:50:23 <thatannoyingguy4> yes we are
Mar 03 13:50:30 <ubptgbot> <dohniks> ok, then use hybris-boot.img
Mar 03 13:50:39 <ubptgbot> <dohniks> and try to boot the halium reference rootfs
Mar 03 13:50:44 <ubptgbot> <dohniks> once that works ok
Mar 03 13:50:51 <ubptgbot> <dohniks> you swtich to halium-boot and ubports
Mar 03 13:50:58 <ubptgbot> <dohniks> you can't mix and match
Mar 03 13:51:30 <thatannoyingguy4> but there is the problem: I'm unable to create the halium rootfs because of the chroot issue with dpkg
Mar 03 13:51:35 <ubptgbot> <dohniks> hybris-recovery.img is basically the same as hybris-boot.img, it just always does telnet
Mar 03 13:52:11 <ubptgbot> <dohniks> mhm
Mar 03 13:52:36 <ubptgbot> <dohniks> well, you could switch to halium-boot and ubports, but you still need to halium-install it, so same problem :-P
Mar 03 13:52:49 <ubptgbot> <dohniks> what was the chroot problem again?
Mar 03 13:53:42 <ubptgbot> <dohniks> @thatannoyingguy4 what did this yield?
Mar 03 13:53:43 <ubptgbot> <dohniks> Fwd from JBBgameich: Can you modify the script to run echo  $PATH instead? Maybe the path variable is not correctly setup inside the chroot.
Mar 03 13:59:42 <thatannoyingguy4> but the ut postinstall directive doesn't involve dpkging. I added chroot_run "echo $PATH" but it returns my PATH of my host machine
Mar 03 14:00:01 <thatannoyingguy4> and the update-binfmts-things starts again...
Mar 03 14:01:19 <ubptgbot> <dohniks> maybe single quotes
Mar 03 14:01:28 <ubptgbot> <dohniks> chroot_run 'echo $PATH'
Mar 03 14:01:32 <ubptgbot> <dohniks> of
Mar 03 14:01:42 <ubptgbot> <dohniks> chroot_run 'echo \$PATH'
Mar 03 14:01:59 <ubptgbot> <dohniks> [Edit] or
Mar 03 14:04:49 <ubptgbot> <dohniks> or you could comment out the chroot_run stuff, just halium-install it, then boot into twrp and manually do in chroot
Mar 03 14:05:16 <ubptgbot> <dohniks> ooor, if ut is easier use halium-boot and ut
Mar 03 14:05:22 <ubptgbot> <dohniks> so many ways to skin the cat :)
Mar 03 14:05:38 <ubptgbot> <bhushanshah> 🤔
Mar 03 14:06:02 <thatannoyingguy4> halium-boot and ut are the things currently installed
Mar 03 14:06:23 <ubptgbot> <dohniks> good. do they boot?
Mar 03 14:06:51 <thatannoyingguy4> no the halium-boot.img bootloops
Mar 03 14:07:03 <ubptgbot> <dohniks> last_kmsg?
Mar 03 14:10:52 <thatannoyingguy4> still the same: https://pastebin.com/RGa2VDiP I copied out the relevant boot
Mar 03 14:13:31 <ubptgbot> <dohniks> I think when you add break=bottom to the kernel commandline the halium-boot init should give you a telnet interface
Mar 03 14:14:59 <thatannoyingguy4> is there a faster method to edit the cmdline than rebuilding the halium-boot.img?
Mar 03 14:15:47 <ubptgbot> <dohniks> smt like this
Mar 03 14:15:48 <ubptgbot> <dohniks> fastboot -c "$(abootimg -i hybris-boot.img | sed -ne '/cmdline/s/. cmdline . //p' ) bootmode=debug" boot hybris-boot.img
Mar 03 14:15:55 <ubptgbot> <dohniks> oh fastboot hehe
Mar 03 14:16:05 <thatannoyingguy4> yeah heimdall :D
Mar 03 14:16:38 <ubptgbot> <dohniks> well you can abootimg -x it, modify it and piece it back together, but I think there were some gotchas ... how long does it take to build
Mar 03 14:17:20 <thatannoyingguy4> less than a minute normally but I first have to find the config entry
Mar 03 14:19:50 <thatannoyingguy4> ok I got a config enty in the kernel config and ne in the boardconfig but hey only vontain the console entry. Are there any other "common plaxes" where such things could be stored?
Mar 03 14:21:36 <ubptgbot> <dohniks> BOOTIMG_COMMANDLINE in halium/halium-boot/Android.mk
Mar 03 14:27:08 <thatannoyingguy4> what about this message when compiling the kernel: Warning: you may need to install module-init-tools? is it harmless?
Mar 03 14:27:32 <ubptgbot> <dohniks> dunno
Mar 03 14:40:23 <thatannoyingguy4> the break=bottom is ignored. the kernel cmd line doesn`t apply the change and neither does the boarcommonconfig. I'll try again with the halium/halium-boot/Android.mk
Mar 03 14:59:58 <thatannoyingguy4> nope. I added the directive to 3 places but it won't boot with the new option. Android kitchen showed me that the directive is in the cmdline but it doesn't boot with it
Mar 03 15:02:53 <ubptgbot> <dohniks> what does "doesn't boot" mean
Mar 03 15:03:27 <ubptgbot> <dohniks> screen is expected to stay black/logo and you're supposed to get a telnet interface via usb
Mar 03 15:04:22 <thatannoyingguy4> turns on, see the splash for 5-10 seconds then turns black and reboots
Mar 03 15:04:46 <ubptgbot> <dohniks> is taht different than before you added the option?
Mar 03 15:05:00 <thatannoyingguy4> no
Mar 03 15:07:31 <ubptgbot> <dohniks> break=top ?
Mar 03 15:13:34 <thatannoyingguy4> nothing changed
Mar 03 15:16:04 <ubptgbot> <dohniks> you see the ot
Mar 03 15:16:21 <ubptgbot> <dohniks> you see the option in the last_kmsg ?
Mar 03 15:18:57 <thatannoyingguy4> yes
Mar 03 15:19:58 <thatannoyingguy4> TARGET_NO_BOOTLOADER := true
Mar 03 15:19:58 <thatannoyingguy4> TARGET_PROVIDES_INIT := true
Mar 03 15:19:59 <thatannoyingguy4> TARGET_PROVIDES_INIT_TARGET_RC := true
Mar 03 15:20:02 <thatannoyingguy4> I found those in the boardconfig. Are those generic config entries?
Mar 03 15:21:00 <ubptgbot> <dohniks> running out of ideas. I think if I were you I'd try to get hybris-boot and halium going first, not sure how to solve the distribution problems you had there though
Mar 03 15:21:09 <ubptgbot> <dohniks> don't know these variables
Mar 03 15:30:11 <ubptgbot> <DickThomas> hi again. okay we gathered that $ heimdall flash --BOOT hybris-boot.img doesn't work as the image is larger than the boot partition but how do i compress it.. turns out my google fu isn't strong as I hope … so how do i compress the boot img?
Mar 03 15:31:53 <ubptgbot> <dohniks> you can try changing the kernel compression algorithm. smt like this:
Mar 03 15:31:54 <ubptgbot> <dohniks> https://github.com/doniks/android_kernel_google_msm/commit/7c4b9bc382756d2dcc3160260c0af182cc984959
Mar 03 15:32:21 <ubptgbot> <dohniks> but I don't know which ones are expected to be better that what
Mar 03 15:37:28 <ubptgbot> <DickThomas> Thanks  … hmm that's what I was doing. I hoped it was some extra step I was missing
Mar 03 15:38:02 <ubptgbot> <dohniks> did it change the size at all?
Mar 03 15:38:08 <ubptgbot> <dohniks> how much too big is it?
Mar 03 15:44:00 <ubptgbot> <DickThomas> current file is 8.1mb according to heimdall  the partition expecting boot.img is 22528blocks or 11mb according to a unit converter
Mar 03 15:44:26 <ubptgbot> <DickThomas> http://paste.debian.net/1071225/
Mar 03 15:46:09 <thatannoyingguy4> I just transferred the rootfs and system.img files and mounted the rootfs file on a directory. when I chroot into it I get FATAL: kernel too old
Mar 03 17:37:02 <thatannoyingguy4> how can I tell the halium build system what format a certain partition is formatted has so it doesn't have to probe?
Mar 03 17:52:26 <thatannoyingguy4> and is it normal that the fs under /target doesn't have an init file?
Mar 03 19:32:02 <ubptgbot> <Walid> Walid, [03.03.19 20:30] … i have this error … /android/system/lib/liblog.so" is 32-bit instead of 64-bit … should i use 64 bit rootfs ?
Mar 03 19:35:24 <ubptgbot> <dohniks> please don't crosspost
Mar 03 20:09:40 <ubptgbot> <Walid> ok no more question
**** ENDING LOGGING AT Mon Mar 04 02:59:57 2019