**** BEGIN LOGGING AT Thu Apr 11 02:59:58 2019 Apr 11 07:23:36 xander_m was added by: xander_m Apr 11 08:58:21 Hello. Have anybody met a problem when rootfs is mounted as readonly system while Plasma Mobile is booting? … By unknown reasons it is mounts as readonly system on my device and due to this it is impossible to start lxc container. Apr 11 09:06:56 JordiBA was added by: JordiBA Apr 11 09:28:20 Hi there! Apr 11 09:28:56 I'm wondering, if I would be able to build Halium for my Samsung Galaxy A3 (2017) device... Apr 11 09:29:25 I do know some little programming (PHP) Apr 11 09:29:40 I have a little experience building projects Apr 11 09:30:10 @chris_blues [I do know some little programming (PHP)], Have you already built and run Lineage OS? Apr 11 09:30:11 But I'm quite sure, I would not know, how to fix problems in such a complex project... Apr 11 09:30:26 Nope, no LineageOS build yet Apr 11 09:31:42 Is that needed for Halium? Apr 11 09:32:25 @chris_blues [Nope, no LineageOS build yet], It is a good point to start. You shall find a suitable kernel and device configs for your device. … Lineage OS build makes you sure that they are working. … It will much more easily to build Halium and makes you familiar with a build system. Apr 11 09:32:47 OK... Apr 11 09:33:32 I was just looking over the Halium documentation (first steps) and landed here. Apr 11 09:33:52 I'm not even sure, what the general architecture is! Apr 11 09:34:19 @chris_blues [OK...], Looks like there is no official Lineage OS build for your device https://wiki.lineageos.org/devices/#samsung so you have to find unofficial one and its sources Apr 11 09:34:38 Actually, I'm interested in having PlasmaMobile on my device. Which, I found, is sitting on top of Halium (which I assume is the OS) Apr 11 09:35:56 @ubptgbot Yes, there is one, but it's somewhat old - and it's unofficial, so I'm not sure, if I really want to have that on my device... Apr 11 09:36:09 @chris_blues [Actually, I'm interested in having PlasmaMobile on my device. Which, I found, is …], Halium is just a way to access hardware using LXC container for running android system image and libhybris to access its libraries. Apr 11 09:36:56 So, Halium is the running on Android? Apr 11 09:37:07 @chris_blues [@ubptgbot Yes, there is one, but it's somewhat old - and it's unofficial, so I'm …], For building Halium basic you need to have device configs, kernel and proprietary blobs. If you find unofficial build sources you can start with them Apr 11 09:37:34 it uses Android base to access the hardware basically Apr 11 09:38:19 [it uses Android base to access the hardware basically] I see. So we know, whats working and what is not? Apr 11 09:43:30 Ok, thanks a lot for giving me some directions! I guess, it'll be a while till i'm back here! :o) I'll go try to build LineageOS, and once that's fine I'm sure I'll have more questions on Halium... Apr 11 09:45:12 Actually at the beginning of the porting process mostly nothing works Apr 11 09:48:36 @nanu_c [Actually at the beginning of the porting process mostly nothing works], Yeah it would frighten me if the GUI comes up on first boot lol Apr 11 09:51:43 @upbtgbot Please, can you take a look, so that I'm not going into the wrong jungle? Here's a LineageOS-ROM for my device: https://forum.xda-developers.com/samsung-a-series-2017/development/rom-lineageos14-1-t3735022 Apr 11 09:52:02 And here are the sources, I think: https://github.com/a3y17lte Apr 11 09:52:04 @nanu_c [Actually at the beginning of the porting process mostly nothing works], So much true! Apr 11 09:53:04 So, I'll try to build this according to the LineageOS wiki/documentation? Apr 11 09:54:01 @chris_blues [And here are the sources, I think: https://github.com/a3y17lte], Looks good. Have you done some preparations like unlocking bootloader and flashing custom recovery like TWRP? Apr 11 09:54:58 Not yet. But I'll need that after the build is done, or am I missing sth here? Apr 11 09:55:51 @aa_sokolov [Looks good. Have you done some preparations like unlocking bootloader and flashi …], it is 15.1 Apr 11 09:56:04 @chris_blues [Not yet. But I'll need that after the build is done, or am I missing sth here?], It is up to you. You won't be able to flash your image until bootloader is locked. Recovery will help to install your image. Apr 11 09:56:16 you currently need either 12 or 14 Apr 11 09:57:03 [you currently need either 12 or 14] ??? wHAT DO YOU MEAN? Apr 11 09:57:10 Sorry for CpasLock... Apr 11 09:57:18 @NotKit [it is 15.1], There are also brunches for cm-14.1 in repositories. Apr 11 09:59:58 @chris_blues [[you currently need either 12 or 14] ??? wHAT DO YOU MEAN?], You have to use sources for Lineage OS 14 or 12 version. They are usually can be found on branches like "cm-14.1" Apr 11 10:01:07 What's wrong with 15? Apr 11 10:01:28 This repo seems to be started at 15... Apr 11 10:03:05 libhybris doesnt support android 8 Apr 11 10:03:27 and 15 uses android 8 Apr 11 10:04:18 libhybris is used that the linux can talk with the hardware Apr 11 10:04:18 Ok, that's a bummer! Apr 11 10:05:34 People are working on support for 8 and 9 but this will take still a long time. There is a reason why mostly older phones are used for porting ;) Apr 11 10:06:16 Well, if Samsung had it's way, I would be using a 2018 phony by now... :o) Apr 11 10:06:59 Ok, so I would have to find something suitable... Apr 11 10:07:11 This question comes quite often, we should put it in the firststeps doc of halium ;) Apr 11 10:12:56 One more thing: About the overall layout. PlasmaMobile runs on top of Halium. And Halium runs on top of lineageOS? Or what's the idea? Apr 11 10:16:29 @chris_blues [One more thing: About the overall layout. PlasmaMobile runs on top of Halium. An …], Not actually. Halium doesn't need running Lineage OS on device. It just uses same sources with Lineage OS. Apr 11 10:17:43 So Halium is an OS of its own? Apr 11 10:18:21 @chris_blues [So Halium is an OS of its own?], Basically it's a wrapper around android drivers Apr 11 10:19:06 So it needs either Android or LineageOS to run? Apr 11 10:24:35 @chris_blues [So it needs either Android or LineageOS to run?], Not a complete Android or Lineage OS. It needs hardware access libraries and I guess some native services from its - parts that are "below" Java virtual machine. Apr 11 10:24:49 @chris_blues [So it needs either Android or LineageOS to run?], [Edit] Not a complete Android or Lineage OS. It needs hardware access libraries and I guess some native services from it - parts that are "below" Java virtual machine. Apr 11 10:27:01 Ok thanks! So I'll try reading further for now, on how to accomplish something... Apr 11 10:29:22 @chris_blues [Ok thanks! So I'll try reading further for now, on how to accomplish something.. …], May be it would be usefull for you to walk through Sailfish OS Hardware Adaptation Guide https://sailfishos.org/content/uploads/2019/03/SailfishOS-HardwareAdaptationDevelopmentKit-3.0.1.0.pdf … First steps are quite similar for Sailfish a Apr 11 10:29:22 nd Halium. … It also was very useful for me to read an old CyanogenMod porting document https://fat-tire.github.io/porting-intro.html … Just to be welcome with building system. Apr 11 10:33:32 Thanks a lot! Apr 11 13:51:17 @aa_sokolov [Hello. Have anybody met a problem when rootfs is mounted as readonly system whil …], Hi again. I'm a little bit stuck into halium-boot debuging. I have a problem with "mountroot()" function in "scripts/halium" file. When it executes lines for "Normal boot" it tries to create "/root/android" and "/root/userdata" directories Apr 11 13:51:17 , but "/root" is already mounted as read-only partition. … I can't trace why it happens this way. I'm thinking that it is because "readonly" variable set to "y", but I'm not sure about this. Has anybody met similar problems? Apr 11 13:54:04 in dmesg look for fatal filesystem errors. in twrp run e2fsck -fy /data/rootfs.img Apr 11 13:54:12 [Edit] in dmesg look for fatal filesystem errors. in twrp run `e2fsck -fy /data/rootfs.img` Apr 11 13:57:24 @minlexx [in dmesg look for fatal filesystem errors. in twrp run e2fsck -fy /data/rootfs.i …], I receive these output lines: … ```~ # e2fsck -fy /data/rootfs.img … e2fsck 1.42.9 (28-Dec-2013) … Pass 1: Checking inodes, blocks, and sizes … Pass 2: Checking directory structure … Pass 3: Checking directory connectivity … Pass 4: Checking Apr 11 13:57:24 reference counts … Pass 5: Checking group summary information … /data/rootfs.img: ***** FILE SYSTEM WAS MODIFIED ***** … /data/rootfs.img: 19732/128000 files (4.0% non-contiguous), 152726/512000 blocks``` … Looks like like something was wrong. I will try to boot again Apr 11 13:57:44 @minlexx [in dmesg look for fatal filesystem errors. in twrp run e2fsck -fy /data/rootfs.i …], [Edit] I've received these output lines: … ```~ # e2fsck -fy /data/rootfs.img … e2fsck 1.42.9 (28-Dec-2013) … Pass 1: Checking inodes, blocks, and sizes … Pass 2: Checking directory structure … Pass 3: Checking directory connectivity … Pass Apr 11 13:57:45 4: Checking reference counts … Pass 5: Checking group summary information … /data/rootfs.img: ***** FILE SYSTEM WAS MODIFIED ***** … /data/rootfs.img: 19732/128000 files (4.0% non-contiguous), 152726/512000 blocks``` … Looks like like something was wrong. I will try to boot again Apr 11 13:59:25 @minlexx [in dmesg look for fatal filesystem errors. in twrp run e2fsck -fy /data/rootfs.i …], No effect :( Apr 11 14:04:15 can you force to run telnet? e.g. create init_enter_debug file in target rootfs? login into telnet and try: … - check that /target/.halium-ro does not exist … - try remount /target with rw (umount /target; mount /data/rootfs.img /target) and see dmesg for fatal fiesystem errors Apr 11 14:05:04 [Edit] can you force to run telnet? e.g. create init_enter_debug file in target rootfs? login into telnet and try: … - check that `/target/.halium-ro` does not exist … - try remount /target with rw (`umount /target`; `mount /data/rootfs.img /target`) and see dmesg for fatal fiesystem errors Apr 11 14:11:57 @minlexx [can you force to run telnet? e.g. create init_enter_debug file in target rootfs? …], Thank you for an advice. But I'm not sure I understand you right. … I login into telnet after I use … ```fastboot boot halium-boot.img -c ``` … I don't remember … ```/target``` … mounts this way. I remember … ```/target``` … direc Apr 11 14:11:57 tory when I boot … ```hybris-boot.img``` … instead of … ```halium-boot.img``` … . … Do you mean this? Apr 11 14:12:35 yeah maybe I meant hybris-boot Apr 11 14:12:55 Ok, I will try, thank you Apr 11 14:13:17 @minlexx [can you force to run telnet? e.g. create init_enter_debug file in target rootfs? …], [Edit] Thank you for an advice. But I'm not sure I understand you right. … I login into telnet after I use … ```fastboot boot halium-boot.img -c ``` … I don't remember … `/target` … mounts this way. I remember … `/target` … direct Apr 11 14:13:17 ory when I boot … `hybris-boot.img` … instead of … `halium-boot.img` … . … Do you mean this? Apr 11 14:14:59 halium-boot is supposed to mount rootfs as read-only i think Apr 11 14:20:52 @minlexx [halium-boot is supposed to mount rootfs as read-only i think], I guess it mounts android-rootfs as a read-only filesystem, because there is no need to write something there. But `/root` is mounted for another purposes I guess. … Moreover we attempt to create two subdirectories `android/` and `userdata/` here. … Everything al Apr 11 14:20:52 right if I boot `hybris-boot.img` Apr 11 14:22:24 @aa_sokolov [Hi again. I'm a little bit stuck into halium-boot debuging. I have a problem wit …], How did you transfer the image to the device? Apr 11 14:23:00 You need to use halium-install with -p ut parameter, that will create a ton of directories and softlinks, without them it cant work properly Apr 11 14:23:14 THe rootfs of UT is not ready to run out of box ^^ Apr 11 14:24:33 I have used `/halium-scripts/halium-install` scripts and reference rootfs Apr 11 14:30:55 Oki then you need -p reference or so Apr 11 14:31:08 See docs ^^ Apr 11 14:32:12 @Flohack [Oki then you need -p reference or so], Guess I understand, I will try. Thanks a lot. Apr 11 14:45:48 @Flohack [Oki then you need -p reference or so], I have tried to install reference rootfs with this command … ```halium-install-standalone.sh -p reference halium-rootfs-20170630-151006.tar.gz system.img``` … and boot with `halium-boot.img` and I still have same problems :( Apr 11 14:46:20 there should be one without standalone Apr 11 14:46:30 did it ask for root pw Apr 11 14:46:33 ssh pw Apr 11 14:46:54 @Flohack [did it ask for root pw], yes it is Apr 11 14:48:00 I took it here https://gitlab.com/JBBgameich/halium-install … There is also a link to "standalone" version. I think it just all files in one. Apr 11 15:00:27 @aa_sokolov [I took it here https://gitlab.com/JBBgameich/halium-install … There is also a link …], Thats good but just call halium-install Apr 11 15:07:58 @Flohack [Thats good but just call halium-install], Ok. I got no choise anyway :) `halium-boot.img` debuging can wait a little bit Apr 11 15:24:32 @Flohack [Thats good but just call halium-install], Same problem. Looks like it doesn't depend on rootfs installing method. Apr 11 15:28:23 Interesting Apr 11 15:28:59 @Flohack [Interesting], May `halium-boot.img` for arm64 be different from arm 32-bit ? Apr 11 15:30:01 Sure. I also have issues with arm64 ubuntu touch edge rootfs. Cant find init Apr 11 15:30:26 I will try 32 bits tonight. Wont work much but init should run Apr 11 15:34:47 @Flohack [I will try 32 bits tonight. Wont work much but init should run], It would be great if share results. I will try to run 32-bit `halium-boot.img` too. Apr 11 21:07:19 kutlay1653 was added by: kutlay1653 Apr 11 21:09:13 I think halium should support oreo or pie in todays. Because new phones, example xiaomi mi a2, a2 lite..., don't support Los14.1. Apr 11 21:09:38 Is there any development for hal-9 or something like this? Apr 11 21:11:33 ATM no, but you can go ahead and start working on it if you so desire Apr 11 21:13:45 aslında bazı dosyaların revisionları değiştirilebilir Apr 11 21:13:56 @ankaos [aslında bazı dosyaların revisionları değiştirilebilir], Wrong Apr 11 21:15:41 @archi_dagac [Is there any development for hal-9 or something like this?], I have proof-of-concept with test_hwc2 running on few devices, but it makes sense only if you're a dev Apr 11 21:17:28 it general, it is not about "Halium should support", but actually putting Android 8/9 system in LXC container and writing newer middleware code due to changed APIs for respective projects (UBPorts, Plasma, etc) **** ENDING LOGGING AT Fri Apr 12 02:59:57 2019