**** BEGIN LOGGING AT Tue May 01 03:00:06 2018
May 01 04:05:29 <b010000100100001> It was said on here a day or two ago that if I have a device with a too-old kernel, I will most likely not get a newer one. I found that the unlegacy android project maintains a kernel for omap4 devices, including mine. The GitHub repo I found appears to have a 3.4 branch. It is at https://github.com/Unlegacy-Android/android_kernel_ti_omap4/tree/3.4/espresso. Note that I still have not been able to find 3.4 kernels as binari
May 01 07:05:10 <ubptgbot> <Loader009> fastboot wipe userdata should decrypt and wipe it. Sometimes (dunno why) an encrypted data partition without password set can get mounted without password prompt in twrp. In that case a data wipe did not disable encryption because /dev/block/dm-0 was wiped instead of the raw partition.
May 01 07:30:13 <ubptgbot> <JBBgameich> @b010000100100001, 3.4 would be new enough. You don't need a prebuilt binary for Halium, so that would be fine.
May 01 08:10:16 <ubptgbot> <NotKit> to avoid some confustion, usually stock firmware from vendor nowadays comes with "forceencrypt" option in fstab, which causes it to encrypt data on boot
May 01 08:10:39 <ubptgbot> <NotKit> LOS usually changes this to encryptable in their build (optional encryption)
May 01 08:23:32 <ubptgbot> <DemonSingur> That's false
May 01 08:23:49 <ubptgbot> <DemonSingur> Every forceencrypt device MUST be force encrypted on Lineage
May 01 08:27:09 <ubptgbot> <jonny> Is it possible to backup lineageOS completely so that I can completely restore it after flashing halium?
May 01 08:28:06 <ubptgbot> <DemonSingur> If you have FBE, no
May 01 08:28:13 <ubptgbot> <DemonSingur> Everything else can be backed up fine
May 01 08:28:18 <ubptgbot> <DemonSingur> Use TWRP
May 01 08:28:47 <ubptgbot> <jonny> What is FBE?
May 01 08:28:55 <ubptgbot> <jonny> Twrp is on recovery
May 01 08:29:52 <ubptgbot> <trueleo> @jonny, You can make full backup using TWRP.
May 01 08:30:24 <ubptgbot> <DemonSingur> FBE is file based encryption … basically only 4.4 kernel devices use FBE
May 01 08:30:28 <ubptgbot> <jonny> Oh great. So I do not need to know which partitions I need?
May 01 08:30:38 <ubptgbot> <DemonSingur> Nop
May 01 08:30:43 <ubptgbot> <DemonSingur> Just backup system, boot, userdata
May 01 08:31:08 <ubptgbot> <jonny> Great, thanks!
May 01 10:43:38 <ubptgbot> <jonny> If I do a repo sync does it redownload things that are already there?
May 01 10:45:36 <ubptgbot> <Flohack> Guys we have a ticket on Ubuntu Touch about issues with the compass sensor. Turns out some devices dont even have one. But there is no libhybris test for that. It would be nice though to have a test, since we cant distinguish properly between "not built in" and "failing to access"
May 01 10:52:39 <ubptgbot> <abhishek_0> @jonny, Yes. But it also clears your local work.
May 01 10:53:12 <ubptgbot> <jonny> Oh, not what I would except from a "sync". But good to know.
May 01 11:09:21 <ubptgbot> <jonny> When running `./halium/devices/setup taoshan` I get … ```fatal: duplicate path device/qcom/common in /home/jonatan/.Programmieren/UbuntuTouch/Halium/Sony_Xperia_L/halium/.repo/manifest.xml … fatal: duplicate path device/qcom/common in /home/jonatan/.Programmieren/UbuntuTouch/Halium/Sony_Xperia_L/halium/.repo/manifest.xml``` … But I ha
May 01 11:09:21 <ubptgbot> ve looked into that and there is no duplicate path.
May 01 11:09:32 <ubptgbot> <jonny> (Document) https://irc.ubports.com/xl5k1QeD.xml
May 01 11:12:04 <ubptgbot> <jonny> Mh, I guess I do not even need that command, as I have ran it already in the past...
May 01 11:14:23 <ubptgbot> <jonny> @vanyasem, here I am with hands on the device. Are you still bored?
May 01 11:14:41 <ubptgbot> <ilyaishere> 😆
May 01 11:17:13 <ubptgbot> <bhushanshah> @jonny, Perhaps I could help
May 01 11:17:41 <ubptgbot> <jonny> Great! Is the error message above something I should worry about?
May 01 11:18:17 <ubptgbot> <jonny> I have setup the device in the past already. I don't know if there was the same error message back then which I might have overseen.
May 01 11:18:42 <ubptgbot> <bhushanshah> Looks like so
May 01 11:19:35 <ubptgbot> <bhushanshah> Basically remove devices/qcom/common from your device manifest
May 01 11:19:44 <ubptgbot> <bhushanshah> it was added in halium manifest while ago
May 01 11:21:57 <ubptgbot> <jonny> Ok. Do I need a sync repo again or is it enough to do the `./halium/devices/setup taoshan`?
May 01 11:22:29 <ubptgbot> <bhushanshah> I think you would need sync
May 01 11:23:03 <ubptgbot> <jonny> Ok, thanks
May 01 11:23:22 <ubptgbot> <jonny> There are other duplicates as well. I keep removing them now and then I sync again...
May 01 11:24:46 <ubptgbot> <JBBgameich> I think the taoshan manifest in halium-devices has already been updated and the duplicates where removed.
May 01 11:25:03 <ubptgbot> <JBBgameich> [Edit] I think the taoshan manifest in halium-devices has already been updated and the duplicates were removed.
May 01 11:25:12 <ubptgbot> <jonny> So I should simply download that and startover?
May 01 11:26:02 <ubptgbot> <JBBgameich> I'm not sure if the porting workflow changed since you started the port, but nowadays you should just use `halium/devices/setup taoshan`, which should use the manifest from halium-devices.
May 01 11:26:44 <ubptgbot> <JBBgameich> Maybe you need to run `git fetch hal; git pull hal halium-7.1` in the halium/devices folder first, if you didn't sync it for a long time
May 01 11:27:19 <ubptgbot> <jonny> So no need for repo sync then?
May 01 11:27:35 <ubptgbot> <JBBgameich> the setup script does that for you already.
May 01 11:27:44 <ubptgbot> <jonny> Oh, I see.
May 01 11:27:52 <ubptgbot> <JBBgameich> Just make sure the halium-devices subrepository is up to date
May 01 11:28:54 <ubptgbot> <jonny> So the documentation is outdated then?
May 01 11:29:12 <ubptgbot> <jonny> Because it still tells you to use `repo sync -c` first.
May 01 11:29:35 <ubptgbot> <JBBgameich> You need to run repo sync on the initial setup, because you won't have halium-devices without it.
May 01 11:29:44 <ubptgbot> <jonny> Oh, I see.
May 01 11:29:46 <ubptgbot> <JBBgameich> [Edit] You need to run repo sync on the initial setup, because you wouldn't have halium-devices without it.
May 01 11:30:22 <ubptgbot> <jonny> But with the workflow now I will need to download almost everything twice, once when running repo sync and again when running the device setup?
May 01 11:30:34 <ubptgbot> <jonny> Initially
May 01 11:40:02 <ubptgbot> <jonny> It is at `Fetching projects:  99% (213/215) ` vor 10 min already. In the system monitor I can see that it is not downloading anything. Is that normal?
May 01 11:40:15 <ubptgbot> <jonny> [Edit] It is at `Fetching projects:  99% (213/215) ` for 10 min already. In the system monitor I can see that it is not downloading anything. Is that normal?
May 01 11:40:41 <ubptgbot> <JBBgameich> The last two repositories are probably device specific ones that were not downloaded on the initial repo sync -c
May 01 11:40:57 <ubptgbot> <JBBgameich> I tested downloading the repositories for your device yesterday, it should work.
May 01 11:42:03 <ubptgbot> <jonny> The system monitor shows an overall download rate of arround 50kB/s. That is not what I would except from my internect connection...
May 01 11:42:50 <ubptgbot> <JBBgameich> that's `repo` 😆 Nobody knows what it does ... … Do you see any git processes running in htop?
May 01 11:43:56 <ubptgbot> <Flohack> @jonny, Thats normal. Where is @UniversalSuperBox and his screenshot of how to abort repo?
May 01 11:45:01 <ubptgbot> <jonny> @Flohack, Normal in a sense of "be patient. It will come to an end." Or normal like "kill it and restart it"?
May 01 11:45:18 <ubptgbot> <jonny> @JBBgameich, there are three inactive git processes.
May 01 11:45:19 <ubptgbot> <Flohack> If you are patient, you wait. If not, you try to kill it ;) - It wont harm anything
May 01 11:46:16 <ubptgbot> <jonny> Ctrl+C makes it continue :D
May 01 11:46:58 <ubptgbot> <jonny> But there is an error message … ```error: Cannot fetch Halium/android_libcore … aborted by user … Deleting obsolete path /home/jonatan/.Programmieren/UbuntuTouch/Halium/Sony_Xperia_L/halium/device/qcom/common … Deleting obsolete path /home/jonatan/.Programmieren/UbuntuTouch/Halium/Sony_Xperia_L/halium/device/qcom/sepolicy … Deleting o
May 01 11:46:58 <ubptgbot> bsolete path /home/jonatan/.Programmieren/UbuntuTouch/Halium/Sony_Xperia_L/halium/external/stlport … error: Ihre lokalen Änderungen in den folgenden Dateien würden beim Auschecken … überschrieben werden: …   core/main.mk … Bitte committen oder stashen Sie Ihre Änderungen, bevor Sie Branches … wechseln. … Abbruch``` … (sorry, partly German).
May 01 11:47:12 <ubptgbot> <Flohack> You got changes in your tree
May 01 11:47:16 <ubptgbot> <Flohack> and want to update over them
May 01 11:47:20 <ubptgbot> <Flohack> type repo diff
May 01 11:47:26 <ubptgbot> <Flohack> to see what you need to stash or commit
May 01 11:48:53 <ubptgbot> <jonny> Oh, I see. That is what repo wanted to tell me with keeping silent.
May 01 11:49:02 <ubptgbot> <jonny> 😁
May 01 11:49:08 <ubptgbot> <Flohack> normally not, it will abort, but repo is fragile
May 01 11:52:17 <ubptgbot> <JBBgameich> The multithreading is so badly implemented that it will sometimes wait for git processes to finish downloading, even when a critical error appeared
May 01 11:53:22 <ubptgbot> <Flohack> yes
May 01 12:03:00 <ubptgbot> <jonny> I stashed all changes. But still it gets stuck at the same point. After using Ctrl+C there is a `error: Cannot fetch Halium/android_libcore` and then it continues normally.
May 01 12:10:51 <ubptgbot> <JBBgameich> Is there any other error message?
May 01 12:11:33 <ubptgbot> <JBBgameich> I already managed to break the local git repository by using Ctrl + C once, so I just want to make sure that's not the problem.
May 01 12:11:35 <ubptgbot> <jonny> Yes, later I get an `Syncing work tree:  84% (181/215)  error: in `sync --local-only -c -j12 -q`: revision refs/heads/halium-7.1 in Halium/android_libcore not found`
May 01 12:11:54 <ubptgbot> <jonny> [Edit] Yes, later I get an … ```Syncing work tree:  84% (181/215)  error: in `sync --local-only -c -j12 -q`: revision refs/heads/halium-7.1 in Halium/android_libcore not found```
May 01 12:12:45 <ubptgbot> <jonny> So it may be a good idea to just keep the device folder and start over?
May 01 12:13:27 <ubptgbot> <jonny> Oh, I found another line: `./setup-makefiles.sh: line 68: [: ==: unary operator expected`
May 01 12:13:27 <ubptgbot> <bhushanshah> just force sync in libcore
May 01 12:13:43 <ubptgbot> <bhushanshah> repo sync --force-sync libcore
May 01 12:13:46 <ubptgbot> <JBBgameich> @jonny, That's from your device tree ...
May 01 12:13:55 <ubptgbot> <JBBgameich> But should be fine probably ...
May 01 12:31:02 <ubptgbot> <aribk> Does anyone know of a good guide where I can read up on the exact mechanics of the boot process in halium and UT? I also need to figure out what kmesg is telling me.
May 01 13:16:54 <ubptgbot> <jonny> @bhushanshah, That made it. Thanks!
May 01 13:18:56 <ubptgbot> <jonny> Now  `breakfast taoshan` doesn't work anymore: https://pastebin.com/B4UMe0kT
May 01 13:20:27 <ubptgbot> <bhushanshah> `repo sync device/qcom/sepolicy`
May 01 13:21:38 <ubptgbot> <jonny> `error: project device/qcom/sepolicy not found`
May 01 13:21:49 <ubptgbot> <jonny> Didnt I remove that one just today?
May 01 13:22:05 <ubptgbot> <JBBgameich> Wasn't that qcom_common??
May 01 13:22:06 <ubptgbot> <JBBgameich> [Edit] Wasn't that qcom_common?
May 01 13:22:49 <ubptgbot> <jonny> No, there have been some more duplicates that it complained about after removing common. I removed them too.
May 01 13:22:56 <ubptgbot> <jonny> sepolicy was one of them
May 01 13:23:03 <ubptgbot> <jonny> I can add it again
May 01 13:23:12 <ubptgbot> <bhushanshah> Did you remove it from your manifest or from halium-device manifest?
May 01 13:24:02 <ubptgbot> <JBBgameich> qcom_sepolicy is already included in the base manifest btw: https://github.com/Halium/android/blob/halium-7.1/default.xml#L40
May 01 13:24:05 <ubptgbot> <bhushanshah> because halium manifest should have it
May 01 13:24:06 <ubptgbot> <bhushanshah> https://github.com/Halium/android/blob/halium-7.1/default.xml#L40
May 01 13:24:09 <ubptgbot> <jonny> I removed it from .repo/manifest.xml which points at .repo/manifests/default.xml
May 01 13:24:13 <ubptgbot> <bhushanshah> ^5 @JBBgameich
May 01 13:24:18 <ubptgbot> <bhushanshah> xD
May 01 13:24:31 <ubptgbot> <bhushanshah> @jonny alright, please revert that change and remove it from your device manifest
May 01 13:24:32 <ubptgbot> <jonny> That was what the error message was complaining...
May 01 13:24:38 <ubptgbot> <jonny> I see
May 01 13:46:51 <ubptgbot> <jonny> Halium is building now
May 01 13:47:12 <ubptgbot> <jonny> I only need to build systemimage and halium-boot, correct?
May 01 13:47:18 <ubptgbot> <jonny> Besides the rootfs
May 01 13:47:30 <ubptgbot> <JBBgameich> Yes, that's correct
May 01 13:47:39 <ubptgbot> <jonny> 👍🏿
May 01 14:29:34 <ubptgbot> <jimexp> (Photo, 1280x960) https://irc.ubports.com/cBHEJ0sF.png
May 01 14:35:13 <ubptgbot> <jonny> yey, i reach the device via telnet again!
May 01 14:35:35 <ubptgbot> <JBBgameich> Cool! You are using halium-boot now?
May 01 14:36:00 <ubptgbot> <JBBgameich> Then the dmesg would be interesting
May 01 14:39:09 <ubptgbot> <jonny> yes
May 01 14:39:47 <ubptgbot> <Flohack> @Flohack, No one so far for my compass question?
May 01 14:40:08 <ubptgbot> <jonny> https://pastebin.com/8TtVHWCs
May 01 14:40:55 <ubptgbot> <JBBgameich> @jonny, the dmesg from the phone will probbaly help more
May 01 14:41:49 <ubptgbot> <jonny> Can I pull a file via telnet?
May 01 14:43:03 <ubptgbot> <JBBgameich> `telnet 192.168.2.15 dmesg > dmesg` Could work (I haven't tested it)
May 01 14:43:08 <ubptgbot> <JBBgameich> At least this works for ssh
May 01 14:44:42 <ubptgbot> <jonny> `telnet 192.168.2.15 | dmesg > dmesg.log` seems to do the job
May 01 14:45:20 <ubptgbot> <jonny> (Document) https://irc.ubports.com/XYNlg4Zl.null
May 01 14:45:30 <ubptgbot> <JBBgameich> @jonny, No, that can't really work, since you would pipe the output from telnet through your hosts demsg and then in a file
May 01 14:45:48 <ubptgbot> <jonny> mh, you are right. It is my local dmesg
May 01 14:47:41 <ubptgbot> <jonny> Is there a way to shutdown the phone without pulling out the battery?
May 01 14:48:27 <ubptgbot> <JBBgameich> If you can login using `telnet 192.168.2.15`, the shutdown -f command will probably work
May 01 14:48:56 <ubptgbot> <jonny> shutdown not found
May 01 14:49:34 <ubptgbot> <JBBgameich> maybe poweroff exists?
May 01 14:50:28 <ubptgbot> <jonny> 👍🏿
May 01 14:51:28 <ubptgbot> <JBBgameich> But just logging in, running dmesg and copy-pasting that should work, shouldn't it?
May 01 14:51:43 <ubptgbot> <jonny> The file is large
May 01 14:52:02 <ubptgbot> <JBBgameich> The end is probably the most important part anyway
May 01 14:52:23 <ubptgbot> <JBBgameich> If it's still to large, `dmesg | grep initrd` would maybe also do it
May 01 14:53:52 <ubptgbot> <jonny> https://pastebin.com/v4P2dmzW
May 01 14:54:07 <ubptgbot> <jonny> it could not mount system.img
May 01 14:54:18 <ubptgbot> <jonny> Maybe there is not enough space?
May 01 14:55:38 <ubptgbot> <JBBgameich> Mounting doesn't take space normally
May 01 14:56:04 <ubptgbot> <jonny> Makes sense
May 01 14:56:47 <ubptgbot> <JBBgameich> `[    4.988097] initrd: Halium rootfs is` also doesn't look correct
May 01 14:56:57 <ubptgbot> <JBBgameich> I think it should say /data/rootfs.img there
May 01 14:57:13 <ubptgbot> <JBBgameich> Any chance you can get a more complete dmesg?
May 01 14:57:17 <ubptgbot> <jonny> Btw, I have used you halium-install-scripts
May 01 14:57:30 <ubptgbot> <jonny> yes
May 01 14:57:48 <ubptgbot> <JBBgameich> Maybe `echo dmesg | telnet 192.168.2.15> dmesg` works (just guessing again)
May 01 14:58:48 <ubptgbot> <jonny> There is no way to get into recovery to use adb, is there?
May 01 14:58:57 <ubptgbot> <jonny> I can get into fastboot (bootloader)
May 01 15:00:10 <ubptgbot> <JBBgameich> Since the data partition is mounted as (/tmpmnt I think?), you could run dmesg > /tmpmnt/dmesg, reboot into recovery and pull /data/dmesg using adb.
May 01 15:01:20 <ubptgbot> <jonny> But on Sony devices you can't reach recovery without a working boot image afaik
May 01 15:01:28 <ubptgbot> <jonny> I would need to flash twrp on boot first...
May 01 15:01:33 <ubptgbot> <jonny> should work
May 01 15:02:39 <ubptgbot> <jonny> So I will find my actual halium root somewhere in twrp?
May 01 15:03:36 <ubptgbot> <JBBgameich> The ininitrd runs fully inside the ram, so you can't access it's data from TWRP. the only possibility is writing it to the data partition, which is mounted under a different name in the initrd.
May 01 15:04:00 <ubptgbot> <JBBgameich> Another thing: is busybox httpd available in the initrd?
May 01 15:04:13 <ubptgbot> <jonny> https://pastebin.com/XaqkMcPF
May 01 15:04:25 <ubptgbot> <JBBgameich> @JBBgameich, You could start a webserver and download it from the running phone using wget or even a browser
May 01 15:04:36 <ubptgbot> <jonny> The dmesg output is not too long for the terminal output...
May 01 15:04:50 <ubptgbot> <jonny> Sorry
May 01 15:05:59 <ubptgbot> <jonny> `mount: can't find /halium-system in /etc/fstab`
May 01 15:06:13 <ubptgbot> <JBBgameich> Did you follow the instructions from the github issue about using halium-boot?
May 01 15:06:14 <ubptgbot> <jonny> This sounds suspicous. Doesn't it?
May 01 15:06:25 <ubptgbot> <JBBgameich> You need to create some extra files on /data iirc
May 01 15:07:03 <ubptgbot> <jonny> I think once I did. This time no. I just found this one without that instructions anymore: https://github.com/Halium/halium-boot
May 01 15:07:47 <ubptgbot> <JBBgameich> https://github.com/Halium/projectmanagement/issues/40
May 01 20:17:47 <AA-ron[m]> does the samsung galaxy tab 4 have a port?
May 01 20:31:16 <AA-ron[m]> hmm my device workswith libhybris
May 01 20:52:18 <AA-ron[m]> nvm
**** ENDING LOGGING AT Wed May 02 03:00:03 2018