**** BEGIN LOGGING AT Sat Jan 13 03:00:01 2018
Jan 13 07:52:10 <Herrie|2> Morning
Jan 13 07:52:18 <Herrie|2> Tofe: I'm a bit lost on the lvm side...
Jan 13 07:53:02 <Herrie|2> Tried the following in the init script: https://bpaste.net/show/4510cbe90109
Jan 13 07:53:08 <Herrie|2> Nothing seems to output anything :S
Jan 13 07:53:31 <Herrie|2> Only dmstats seems to output "No devices found" that's it
Jan 13 07:57:21 <Herrie|2> Tried redirecting output to /dev/kmsg as well same result
Jan 13 07:57:39 <Herrie|2> Tried it in a for loop too just to make sure it's not a single line issue
Jan 13 08:22:32 <Herrie|2> Tofe: Ah maybe i need to add something like: https://github.com/shr-distribution/meta-smartphone/blob/pyro/meta-hp/recipes-core/initrdscripts/initramfs-boot-android/init-tenderloin.sh#L66
Jan 13 08:26:11 <Tofe> Morning
Jan 13 08:26:18 <Tofe> Herrie|2: could you send me your initrd ?
Jan 13 09:16:35 <Herrie|2> https://bpaste.net/show/082207d4f5a5
Jan 13 09:37:10 <Tofe> Herrie|2: you should try to append directly "  > /dev/kmsg" to your /usr/sbin/... lines 65-88, just in case
Jan 13 09:37:21 <Tofe> also I was interested in the whole initramfs image
Jan 13 09:50:14 <Herrie|2> Tofe: on 65->80 did that before same result
Jan 13 09:50:27 <Tofe> ok
Jan 13 09:50:49 <Herrie|2> Tofe: you want .fastboot or .gz?
Jan 13 09:51:18 <Tofe> .gz of ramdisk
Jan 13 09:51:30 <Tofe> the cpio stuff
Jan 13 09:52:34 <Tofe> I'm wondering if the executables are starting at all or something like that
Jan 13 09:52:51 <Tofe> maybe it only output on stderr and the ">" doesn't catch it
Jan 13 09:53:07 <Herrie|2> Tofe: http://vve-goudenleeuw.nl/initramfs-android-image-mido.cpio.gz
Jan 13 09:53:12 <Tofe> thx
Jan 13 09:53:16 <Herrie|2> They are all in the image
Jan 13 09:55:49 <Tofe> yes,  all looks good
Jan 13 09:56:59 <Tofe> do you think you could change /etc/lvm/lvm/conf ?
Jan 13 09:57:10 <Tofe> there are some verbosity setup there
Jan 13 09:58:08 <Tofe> also maybe it could be useful to compare it with a tenderloin's lvm.conf
Jan 13 09:58:32 <Herrie|2> Tofe: OK will give that a go a bit later
Jan 13 09:59:28 <Tofe> debugging initramfs has never been easy...
Jan 13 10:00:30 <Tofe> maybe one thing though: did you try starting adb in the initramfs ? for example by removing lines 41 and 46
Jan 13 10:11:52 <Herrie|2> Tofe: Yeah didn't work
Jan 13 10:15:19 <Herrie|2> I might have a look at how AsteroidOS or Halium do it
Jan 13 10:15:31 <Herrie|2> They seem to do some more commands in order to get ADB working
Jan 13 10:16:09 <Herrie|2> https://github.com/AsteroidOS/meta-asteroid/blob/master/recipes-core/initrdscripts/initramfs-boot-android/init.sh#L42 -> 56
Jan 13 10:17:10 <Tofe> right maybe there's something useful there
Jan 13 10:35:12 <Herrie|2> Tofe: Now doesn't bootloop but also cannot adb in
Jan 13 10:35:17 <Herrie|2> Logs might provide something
Jan 13 10:35:27 <Tofe> :/ I hope
Jan 13 10:35:39 <Herrie|2> l1045-1046
Jan 13 10:42:56 <Herrie|2> https://bpaste.net/show/9a8330ba27f3
Jan 13 10:43:01 <Herrie|2> Useful if I paste log :P
Jan 13 10:52:36 <Tofe> mmh not sure what to do with that
Jan 13 11:04:03 <Tofe> We didn't have bluez5 on TP so far ?
Jan 13 11:04:32 <Tofe> my new kernel boots up, but it doesn't look like the good ol' bluetoothd is working
Jan 13 11:05:52 <Herrie|2> Tofe: No not yet I think
Jan 13 11:05:58 <Herrie|2> That's why we needed BT backports
Jan 13 11:38:22 <Herrie|2> Tofe: https://bpaste.net/show/370f1051bf57
Jan 13 11:38:41 <Herrie|2> Gives me: https://bpaste.net/show/97a89edbd40b
Jan 13 11:38:56 <Herrie|2> L1056 at least shows something
Jan 13 11:45:33 <nizovn> Herrie|2: i'm not sure you can pipe echo two times (in adb setup)
Jan 13 11:57:12 <nizovn> Herrie|2: i would try something like: echo 0 | tee /sys/class/android_usb/android0/enable > /dev/kmsg ,etc..
Jan 13 12:00:57 <Herrie|2> nizovn thnx
Jan 13 12:24:32 <Herrie|2> nizovn: I get adb device listed now, just connection gets closed
Jan 13 12:31:42 <nizovn> Herrie|2: maybe lvm executable should be static in initramfs
Jan 13 12:31:51 <nizovn> if i'm right it's dynamic now
Jan 13 12:56:47 <Herrie|2> nizovn: lvm.static doesn't seem to do anything
Jan 13 12:56:52 <Herrie|2> How do I get it static?
Jan 13 12:58:44 <nizovn> Herrie|2: seems there is no /usr/sbin/lvm.static in initramfs
Jan 13 12:59:46 <nizovn> Herrie|2: i'm not sure now if it's relevant, dynamic binaries should work as well it seems
Jan 13 13:51:01 <Herrie|Laptop> Tofe: I guess I know why ADB (android-tools) doesn't work.. We use 5.1 based on 7.1 build at least for mido
Jan 13 13:51:06 <Herrie|Laptop> I guess that could explain something?
Jan 13 13:52:05 <Herrie|Laptop> Tofe: I mean https://github.com/openembedded/meta-openembedded/blob/pyro/meta-oe/recipes-devtools/android-tools/android-tools_5.1.1.r37.bb
Jan 13 13:54:31 <Herrie|Laptop> Ah wait we might be using even older from 4.4
Jan 13 13:54:59 <Herrie|Laptop> 4.2.2 even https://github.com/shr-distribution/meta-smartphone/blob/pyro/meta-android/recipes-android/android-tools/android-tools_4.2.2.bb
Jan 13 13:56:04 <Herrie|Laptop> Yup 4.2.2
Jan 13 13:56:16 <Herrie|Laptop> I guess that might explain why you couldn't get it to work earlier on 5.1 targets
Jan 13 13:57:17 <Herrie|Laptop> Tofe: Let me retry with the 5.1.1 one
Jan 13 13:57:22 <Herrie|Laptop> And it that doesn't work try 7.1.2
Jan 13 14:35:12 <nizovn> Herrie|Laptop: which partition is LuneOS installed on? seems init doesn't try to mount system_partition
Jan 13 14:36:48 <nizovn> maybe lvm is not needed at all..
Jan 13 15:00:28 <Herrie|Laptop> nizovn: Seems we need sdcard partition and that's my issue on mido as per https://github.com/webOS-ports/meta-webos-ports/blob/pyro/meta-luneos/recipes-core/initrdscripts/initramfs-boot-android/init.sh
Jan 13 16:06:29 <nizovn> Herrie|Laptop: you can also try to mount sdcard_partition specifying ext4 fs type instead of auto, seems it's not being recognized
Jan 13 16:27:02 <Herrie|2> nizovn treied that long time ago already
Jan 13 16:29:26 <Herrie|2> Get the magic mismatch
Jan 13 16:30:09 <nizovn> ok..
Jan 13 16:57:24 <Tofe> nizovn: on android, iirc, it's /dev/mapper/dm0 which is mounted; which would mean it uses lvm
Jan 13 17:15:34 <nizovn> is this of any help? https://github.com/LineageOS/android_device_xiaomi_mido/blob/cm-14.1/rootdir/fstab.qcom
Jan 13 18:42:18 <Herrie> nizovn: Yeah I'm aware of that one
Jan 13 18:42:36 <Herrie> Tofe: But I'm correct in assuming that android-tools should match our Android version?
Jan 13 18:43:04 <Herrie> Seeing it takes stuff from Google's Android system Core for a specific android version
Jan 13 18:43:45 <Tofe> Herrie: not sure it's very important... after all, we use the very same adb in the real rootfs and it works (on our current 5.1 devices), doesn't it
Jan 13 18:43:51 <Herrie> I would assume it should match? https://github.com/openembedded/meta-openembedded/blob/master/meta-oe/recipes-devtools/android-tools/android-tools_5.1.1.r37.bb
Jan 13 18:44:11 <Herrie> Tofe: Yeah it does, but I can imagine that using a 4.2.2 version on 7.1 gives headaches :P
Jan 13 18:44:22 <Herrie> And I told you before ADB is flaky at times for me
Jan 13 18:44:24 <Tofe> It can't hurt to have matching version, for sure
Jan 13 18:44:29 <Herrie> Anyway our recipe is wrong
Jan 13 18:44:49 <Herrie> We have a 5.1.1 bbappend in meta-wopp but are actually using 4.2.2 from meta-smartphone
Jan 13 18:44:57 <Herrie> Which I guess we should just drop
Jan 13 18:45:15 <Herrie> Since it's in upstream: https://github.com/openembedded/meta-openembedded/blob/pyro/meta-oe/recipes-devtools/android-tools/android-tools_5.1.1.r37.bb
Jan 13 21:31:16 <Tofe> yes, must be an old mistake
Jan 13 21:38:38 <Herrie> The 7.1.2 seems it needs some work
Jan 13 21:38:42 <Herrie> Will try to get that working
**** ENDING LOGGING AT Sun Jan 14 03:00:03 2018