**** BEGIN LOGGING AT Wed Aug 07 03:02:32 2019
Aug 07 03:15:46 <ubptgbot> BCD 👻👻 was added by: BCD 👻👻
Aug 07 03:18:43 <ubptgbot> <Tygerpro> (Sticker, 512x512) https://irc.ubports.com/bSNsb5Jj.webp
Aug 07 03:31:30 <ubptgbot> <BCD 👻👻> (Sticker, 512x512) https://irc.ubports.com/7WlchiYV.webp
Aug 07 05:40:55 <ubptgbot> <Jalvathi> @mp107 [What device?], Samsung S7. Code name SM-G930F
Aug 07 08:22:23 <ubptgbot> <Nightwal> how should i start writing the mainfest?  i got this error: E486: Pattern not found: xml version="1.0" encoding="UTF-8"
Aug 07 08:23:50 <ubptgbot> <Nightwal> i got an error while creating the manifest. this is the error: E486: Pattern not found: xml version="1.0" encoding="UTF-8"
Aug 07 08:24:38 <ubptgbot> <Nightwal> i got this error when i typed : <?xml version="1.0" encoding="UTF-8"?>    after creating and opening the xml file
Aug 07 08:25:12 <ubptgbot> <Nightwal> what should i do?
Aug 07 08:28:50 <ubptgbot> <fredldotme> please paste the manifest to a pastebin-like service and send the link
Aug 07 09:45:21 <ubptgbot> <Nightwal> Pastebin isnt allowing me for some reason so I'm posting it here. … <?xml version="1.0" encoding="UTF-8"?> … <manifest> … <project path="device/wingtech/wt88047" name="[repository name]" remote="[remote]" revision="[revision]" /> … </manifest> … what should i fill here in the square brackets? please be specific or tell me what where will
Aug 07 09:45:21 <ubptgbot>  i find my repo name, remote and revision.
Aug 07 09:47:38 <ubptgbot> <fredldotme> what's supposed to be in there depends on your device and how the source tree is supposed to look like. Do it akin to what I did here: https://github.com/Halium/halium-devices/blob/halium-7.1/manifests/sony_suzu.xml
Aug 07 09:48:43 <ubptgbot> <fredldotme> also, maybe take a look at an existing manifest (LOS or AOSP) and compare those to your manifest
Aug 07 09:48:59 <ubptgbot> <fredldotme> [Edit] also, maybe take a look at an existing manifest for your device (LOS or AOSP) and compare those to your manifest
Aug 07 09:57:49 <ubptgbot> <fredldotme> in a nutshell: the repository path is composed by the remote + repository name in most cases. revision tells repo to pull from a branch, like "halium-7.1" or "cm-14.1"
Aug 07 10:57:51 <techfreak[m]> https://paste.ubuntu.com/p/vPdmYsSBxG/ Can somebody tell me who got halium working why my mountpoint fails in the SailfishOS Boat loader ?
Aug 07 10:59:23 <techfreak[m]> I can mount the partition manually by writing  mount /dev/sda18 /data/ that works but the platform entry point is gone in the halium image.
Aug 07 10:59:41 <techfreak[m]>  * I can mount the partition manually by writing  "mount /dev/sda18 /data/ " that works but the platform entry point is gone in the halium image.
Aug 07 12:49:23 <ubptgbot> <Tygerpro> I think theres a S7 port started or in progress, dont know who the last person to work on it was, but I know someone got the UT GUI at least on an Galaxy S7 in the past
Aug 07 12:49:50 <ubptgbot> <Tygerpro> Theres even a video of it on YouTube
Aug 07 16:58:48 <ubptgbot> <Jalvathi> @Tygerpro [I think theres a S7 port started or in progress, dont know who the last person t …], Oh thanks Tygerpro . I will search for it on the internet.
Aug 07 17:00:03 <ubptgbot> <Jalvathi> Is it like, only if we have the linux kernel for our device in the LineageOS website, we will be able to flash Ubuntu Touch in our phone??
Aug 07 17:50:57 <ubptgbot> <Tygerpro> The kernel is LineageOS based, but configured differently for what we need
Aug 07 18:35:58 <techfreak[m]> Damn it drives me mad why my mountpoints not work. With mounting manually I even get bash running.
Aug 07 18:45:34 <ubptgbot> <fredldotme> techfreak[m] what's dmesg saying?
Aug 07 18:52:16 <techfreak[m]> @fredldotme dmesg: https://paste.ubuntu.com/p/MxmMWbrZ8m/
Aug 07 19:00:38 <techfreak[m]> @fredldotme Anything that you might see that I could fix ?
Aug 07 19:01:45 <ubptgbot> <fredldotme> this looks kind of weird: `<6>[    4.647050]  [5:           init:    1]  lun0: unable to open backing file: /dev/mmcblk0`
Aug 07 19:05:12 <techfreak[m]> Isn't mmcblk0 the mountpoint for some devices ? I know from my fstab file that my samsung s6 does not have it.
Aug 07 19:06:43 <ubptgbot> <fredldotme> I'm not sure if you have access to parted or fdisk but mmcblk0 should contain the partition table
Aug 07 19:06:55 <ubptgbot> <fredldotme> have you tried booting with halium-boot instead?
Aug 07 19:08:04 <techfreak[m]> Well you are correct that the output is from the hybris-recovery with normal boot (after flashing hybris-boot) I just run in to a boot loop.
Aug 07 19:11:00 <techfreak[m]> @fredldotme I am gonna test that out now
Aug 07 19:33:48 <ubptgbot> <Tygerpro> The mount points if your going raw device is /dev/mmcblk0p<whatever> if its not mounting, double check its in the fixup_mountpoints script if your using reference rootfs and hybris-boot
Aug 07 19:36:41 <ubptgbot> <Tygerpro> So for example /dev/mmcblk0p492 would be the builtin storage, on the 492 partition of it
Aug 07 19:37:54 <techfreak[m]> Okay but when I looked in to the los fstab file they did not link to  /dev/mmcblk0p492 they linked to /dev/block/sda18
Aug 07 19:38:51 <techfreak[m]> So how I find out the corresponding partition numbers ?
Aug 07 19:42:39 <ubptgbot> <Tygerpro> Sda18? Hmm, i think if you go into the /dev/block/by-name/ directory (assuming you have one) I think its something like "ls -lf" I might be wrong but either way ls --help and use whatever one follows symlinks
Aug 07 19:43:15 <ubptgbot> <Tygerpro> It should output something similar to what I said
Aug 07 19:44:43 <techfreak[m]> @Tygerpro https://paste.ubuntu.com/p/Ysjgpk37v5/ maybe that helps you to understand my confusion
Aug 07 19:45:06 <techfreak[m]> that is my fstab file and the way I followed the symlink
Aug 07 19:46:00 <ubptgbot> <Tygerpro> I see no mention of sda in your fstab, the section before VOID is what you need to pay attention to
Aug 07 19:47:16 <techfreak[m]> yeah if you look down when I executed the readlink command the result is /dev/block/sda
Aug 07 19:47:19 <ubptgbot> <Tygerpro> Nvm, I thought that was one file, but yeah, thats weird, unless the phones storage is setup to be that way
Aug 07 19:48:12 <techfreak[m]> in the whole fixup-mointpoints file there are other devices which seems to be also using sda
Aug 07 19:48:17 <ubptgbot> <Tygerpro> Could try removing the /block part so it would read /dev/sda instead in your fixup mount points, I believe the block is added as a result of the android boot
Aug 07 20:00:00 * techfreak[m] sent a long message:  < https://matrix.org/_matrix/media/v1/download/matrix.org/mxjFcqfXvCrwcghZlRPwldYr >
Aug 07 20:00:32 <techfreak[m]> why does it not try to mount /dev/sda... that would work
Aug 07 20:24:27 <ubptgbot> <Tygerpro> The first fail caused the rest of them, the first one might work if you just remove the /block portion
Aug 07 20:27:46 <techfreak[m]> Would it be smart to  run "make clean" before I rebuild all the img files ?
Aug 07 20:35:21 <ubptgbot> <Tygerpro> You can if you want, but it shouldnt matter, it will just recompile whatever changes were made and build it, where as make clean is basically starting over at "mka mkbootimg"
Aug 07 21:17:21 <techfreak[m]> changed it but that did not fix it
Aug 07 23:50:27 <techfreak[m]> Okay the  /dev/mmcblk0 error I will be never able to fix because the s6 has no sdcard and that is apparently the mountpoint for sdcards.
Aug 07 23:56:47 <ubptgbot> <Tygerpro> Well if your device is showing sda instead of mmcblk0 then its just how the storage is configured, are you using hybris-boot with reference rootfs?
Aug 07 23:58:17 <techfreak[m]> yes
Aug 08 00:02:49 <techfreak[m]> I think the current issue that hybris-boot wants to work with the old mountpoints /dev/block/platform/157..../.../USERDATA but they don't exists in that way only as /dev/block/sda18
Aug 08 00:03:02 <techfreak[m]>  * I think the current issue is that hybris-boot wants to work with the old mountpoints /dev/block/platform/157..../.../USERDATA but they don't exists in that way only as /dev/block/sda18
Aug 08 00:06:22 <techfreak[m]> It seems to be hardcoded in to the init script. And I am not sure how to fix it.
Aug 08 00:10:09 <ubptgbot> <Tygerpro> If you can telnet in, do an "ls /dev/platform" and see if you can figure out what the actual layout is
Aug 08 00:11:32 <techfreak[m]> "ls /dev/platform"  "No such file or directory"
Aug 08 00:12:30 <techfreak[m]> it has the sdas under dev but the whole platform path is gone
Aug 08 00:17:01 <techfreak[m]> Any idea on what I could do ? @Tygerpro
Aug 08 00:26:49 * techfreak[m] uploaded an image: image.png (35KB) < https://matrix.org/_matrix/media/v1/download/matrix.org/uzCfNUybTmNfHJmbYvaMhfAp >
Aug 08 00:29:29 <techfreak[m]> Okay seems I have to give up at this point because the fix-mountpoint script requires the /dev/mmcblkMpm which I can't have because I have no sdcard.
Aug 08 00:30:34 <techfreak[m]>  * Okay seems I have to give up at this point because the fix-mountpoint script requires the /dev/mmcblkMpm which I can't have because the s6 has no sdcard.
Aug 08 00:32:21 <techfreak[m]> What a bummer I would have liked to continue porting it for my device.
Aug 08 00:54:14 <ubptgbot> <Tygerpro> Sorry I have stuff going on here, could just try /dev/sda for your mountpoints then?
Aug 08 01:08:45 <ubptgbot> tr45h was added by: tr45h
Aug 08 01:12:58 <ubptgbot> <Tygerpro> @techfreak[m] [Any idea on what I could do ? @Tygerpro], Porting a device is like problem solving, the first attempt rarely goes perfect, and you have to troubleshoot and investigate to figure out possible solutions and try them one by one till something works
**** ENDING LOGGING AT Thu Aug 08 02:59:57 2019