**** BEGIN LOGGING AT Sun Dec 22 02:59:58 2019 Dec 22 04:21:19 Hi I have 6GB ram with android 9. How can I port it. Just guide. I will do. Dec 22 04:53:30 @Guru Sharma [Hi I have 6GB ram with android 9. How can I port it. Just guide. I will do.], Only works if you have a build of android 5.1 or android 7.1 Dec 22 04:56:19 @Guru Sharma [Hi I have 6GB ram with android 9. How can I port it. Just guide. I will do.], That is your device should have lineage os 14.1 or 12.1 build Dec 22 04:56:57 If I'm not wrong, I had linked you the docs, it was clearly mentioned there Dec 22 04:57:17 @Guru Sharma [Hi I have 6GB ram with android 9. How can I port it. Just guide. I will do.], http://docs.halium.org/en/latest/porting/first-steps.html Dec 22 04:59:02 @itexpert120 [Hi, I have a device with 8 GB storage? Is it possible to port UBTouch to it?], ? Dec 22 05:01:05 @itexpert120 [Hi, I have a device with 8 GB storage? Is it possible to port UBTouch to it?], What android version is it Dec 22 05:01:27 Does it have lineage os 12.1 or 14.1 build? Dec 22 05:01:43 @Win32_downdadup [Does it have lineage os 12.1 or 14.1 build?], Official or unofficial anything is ok as long as it works Dec 22 05:06:54 @Win32_downdadup [If I'm not wrong, I had linked you the docs, it was clearly mentioned there], There is no support for android 9. I read the docs. Dec 22 05:07:02 @Win32_downdadup [Does it have lineage os 12.1 or 14.1 build?], It has 14.1 Dec 22 05:07:10 Its stable Dec 22 05:07:12 @itexpert120 [It has 14.1], Then it's possible Dec 22 05:07:16 @Win32_downdadup [Then it's possible], Yey Dec 22 05:07:25 @Guru Sharma [There is no support for android 9. I read the docs.], Oh then it's not possible Dec 22 05:07:31 Its ROM is 8 gigs, is that okey tho? Dec 22 05:07:52 8gigs ROM? Dec 22 05:07:57 @Win32_downdadup [8gigs ROM?], Yes Dec 22 05:08:00 You mean internal? Dec 22 05:08:03 @Win32_downdadup [You mean internal?], Yeah Dec 22 05:08:08 Oh yeah that's fine Dec 22 05:08:14 @Win32_downdadup [Oh yeah that's fine], Great Dec 22 05:08:50 So get started😊 Dec 22 05:08:57 @Win32_downdadup [So get started😊], Yes 😊 Dec 22 05:08:59 @Win32_downdadup [Oh then it's not possible], Can't we do it using another way? Dec 22 05:09:25 @Guru Sharma [Can't we do it using another way?], I heard they are trying it out on Android 8 but I don't know the others Dec 22 05:09:32 *the progress Dec 22 05:09:48 I guess you'll have to wait Dec 22 05:09:59 @Win32_downdadup [I heard they are trying it out on Android 8 but I don't know the others], Who is trying for it? I want to talk with him for support. Dec 22 05:10:02 @Guru Sharma [Can't we do it using another way?], Another old device would be great Dec 22 05:10:49 @Guru Sharma [Who is trying for it? I want to talk with him for support.], I just read that here in the community when I was searching for messages, you can search here for messages related to it Dec 22 05:11:06 You'll find it probably Dec 22 05:12:03 @Win32_downdadup [You'll find it probably], Sadly, I am not being able to do anything myself. Dec 22 05:24:57 So what is halium? I'm lost. It runs Android container on top of halium core. Is halium linux? Or something else? Dec 22 05:52:40 @itexpert120 [So what is halium? I'm lost. It runs Android container on top of halium core. Is …], Think of Halium as a layer that acts as a bootloader, translation, and VM, the way it works varies by the rootfs you wish to use Dec 22 05:52:54 @Shakendo [Think of Halium as a layer that acts as a bootloader, translation, and VM, the w …], Nice Dec 22 05:53:26 Im dumbing it way down, but thats the gist of it Dec 22 07:39:06 Fwd from Win32_downdadup: guys how to add "insmod /system/lib/modules/wlan.ko" to init Dec 22 08:17:52 蒋明 was added by: 蒋明 Dec 22 08:29:17 徐倩奠 was added by: 徐倩奠 Dec 22 12:07:07 Hello everyone!~ Finally back on Halium development! Dec 22 12:07:42 I have a really interesting and maybe impossible question. Is it possible to somehow emulate the device so you don't have to flash the hybris-boot and all? Dec 22 12:07:54 Since for now I do not have the device- Dec 22 12:13:37 After research it may be possible with QEMU, am I right? Dec 22 12:41:00 so i have an issue with yet another device Dec 22 12:41:09 when i boot into mer debug mode on the phone Dec 22 12:41:16 i get this: … `__bionic_open_tzdata_path: ANDROID_DATA not set! … __bionic_open_tzdata_path: ANDROID_ROOT not set!` Dec 22 12:41:27 i check diagnosis and add the needed kernel config Dec 22 12:41:31 and then it doesnt boot at all Dec 22 12:41:37 i dont get anything showing on pc Dec 22 12:43:06 Give it some time, it may be booting very slowly, keep an eye on dmesg, my note 4 takes 20 minutes to boot reference rootfs Dec 22 12:51:05 @Shakendo [Give it some time, it may be booting very slowly, keep an eye on dmesg, my note …], damm Dec 22 12:51:13 ill give it 30 minutes then Dec 22 12:57:55 ok so back to austin Dec 22 12:57:59 im gonna document the device port Dec 22 13:22:32 SuperSandro2000 was added by: SuperSandro2000 Dec 22 13:44:41 @bengris32 [good night everyone], oh crap Dec 22 13:44:49 would be a good idea if i got the lxc container working first Dec 22 14:09:10 @bengris32 [would be a good idea if i got the lxc container working first], That would definately help with moving forward Dec 22 15:29:49 @bengris32 [i get this: … __bionic_open_tzdata_path: ANDROID_DATA not set! … __bionic_open_tzdat …], Thats only for timezone data, you can ignore that messages normally Dec 22 15:32:05 Cgroup memory controller: missing Dec 22 15:32:09 what config do i need to enable for this Dec 22 16:07:57 what the hell is this Dec 22 16:08:04 i added kernel configs for lxc container Dec 22 16:08:06 and now its not booting Dec 22 16:08:15 hurr durr Dec 22 16:08:30 nevermind im inpaitent Dec 22 16:55:20 @bengris32 [what config do i need to enable for this], anyone? Dec 22 16:55:25 everything says enabled apart from this Dec 22 17:08:58 another issue: https://paste.ubuntu.com/p/93mZ7dQM6g/ Dec 22 17:10:31 At line 56, did you try to create the directory? Dec 22 17:21:11 @SomeIrrelevantPerson0000 [At line 56, did you try to create the directory?], that error doesnt seem important Dec 22 17:21:18 its just trying to delete adbd Dec 22 17:38:37 is it that the rootfs is mounted r? Dec 22 17:52:49 @rixchy [I have a really interesting and maybe impossible question. Is it possible to som …], +1 Dec 22 17:57:34 wait should system be rw? Dec 22 17:57:36 wait a minute Dec 22 18:11:18 Specific paths are rw and lead to data partition Dec 22 18:11:40 But Systeme ought to be ro Dec 22 18:14:00 @bengris32 [another issue: https://paste.ubuntu.com/p/93mZ7dQM6g/], Its just when lxc container tries to start it complains about read only filesystem Dec 22 18:27:04 richie_flicker was added by: richie_flicker Dec 22 18:51:08 I've got Debian GNU/Linux 10 running on Redmi 4X using halium ramdisk Dec 22 18:51:28 How do I make it mount /android/system filesystems? Dec 22 18:52:49 [Edit] How do I make it mount /android/system and etc. filesystems? Dec 22 18:53:23 I have system.img which was excellently working with Ubuntu Touch Dec 22 18:57:47 @bengris32 more logs? Dec 22 18:58:07 prior to the first failure Dec 22 19:02:20 nope Dec 22 19:04:05 exact same error with system mounted rw Dec 22 19:04:51 sure Dec 22 19:05:02 please show more logs Dec 22 19:05:19 systemctl only shows a bunch of lines Dec 22 19:06:02 things like dmesg? Dec 22 19:06:13 also is the root filesystem meant to be ro? Dec 22 19:08:02 could it be because selinux cant load the policy? Dec 22 19:09:12 dmesg: https://paste.ubuntu.com/p/xKg2szknPD/ Dec 22 19:48:55 aeh write errors? Dec 22 19:49:00 [ 11.330373] .(3)[249:loop0]loop: Write e Dec 22 19:49:46 no sorry no idea.. I would have liked to see the full lxc container start up log.. then we might see if there is an issue with the system.img Dec 22 20:04:06 @anpok [no sorry no idea.. I would have liked to see the full lxc container start up log …], How do I get that? Dec 22 20:07:14 aehm journalctl -u lxc-android.service or so.. Dec 22 20:09:45 (Voice, 142s) https://irc.ubports.com/ywls95W4.oga Dec 22 20:11:55 @anpok [aehm journalctl -u lxc-android.service or so..], `-- No entries --` Dec 22 20:15:48 everything is bloody readonly Dec 22 20:15:51 wtf Dec 22 20:19:15 I mistyped maybe - you should get at least the same that you pasted.. Dec 22 20:20:12 oh that explains it Dec 22 20:20:18 probably 1k+ lines of read only file system Dec 22 20:20:39 (Photo, 1280x507) https://irc.ubports.com/Cvk0zQhN.png Dec 22 20:24:08 why does it try to remove it? Dec 22 20:24:21 do you have different lxc start script? Dec 22 20:24:26 idk Dec 22 20:24:30 or used a different halium-install script Dec 22 20:24:30 im using the reference rootfs Dec 22 20:24:35 @anpok [or used a different halium-install script], yep Dec 22 20:24:38 ah Dec 22 20:24:59 sorry I havent played with the halium reference roots for hmm years.. Dec 22 20:25:05 https://gitlab.com/JBBgameich/halium-install/ Dec 22 20:25:18 but it sounds as if you have the system image baked into your rootfs Dec 22 20:25:48 so i should use the one from halium scripts? Dec 22 20:26:21 hmm no maybe someelse has more clue Dec 22 20:27:02 ( at lest I believe that halium reference root fs assumes the android container to be its own image ) Dec 22 20:27:20 [Edit] hmm no maybe someone else has more clue Dec 22 20:28:20 @bengris32 [so i should use the one from halium scripts?], transfering rootfs tarball ... … adb: error: failed to copy '../halium-install/halium-rootfs-20170630-151006.tar.gz' to '/recovery/': remote Is a directory Dec 22 20:28:23 thats why i didnt use it Dec 22 20:28:31 thx for buggy scripts halium❤️ Dec 22 20:29:48 nvm mkdir /recovery fixes it Dec 22 20:38:40 nope Dec 22 20:38:45 using official install script didnt work Dec 22 20:38:47 still fucking ro Dec 22 20:38:51 wtaf Dec 22 20:39:31 rEaD-oNlY fIlE sYsTem Dec 22 20:40:56 `[ 101.000616] .(3)[930:init]init: SELinux: Failed to load policy; rebooting into recovery mode` Dec 22 20:41:07 im putting all my money that its bloody stupid selinux Dec 22 20:41:13 this thing was always a problem for developers since day 1 Dec 22 20:48:27 some of the above - .. yes .. you disable selinux in your kernel Dec 22 20:48:39 and you should verify that the rootfs is proper before rebooting - Dec 22 20:50:42 what if my emmc is bad Dec 22 20:50:50 im getting a bunch of i/o erros from loop devices Dec 22 20:55:53 yes I saw those Dec 22 20:55:56 thats possible too Dec 22 20:57:55 then your effort ends here - or you could try to replace the faulty chip... or replace the whole mainboard - or pick up a better porting target? Dec 22 20:58:17 @anpok [then your effort ends here - or you could try to replace the faulty chip... or r …], i have a j2lte that wont boot halium Dec 22 20:58:20 exynos3475 Dec 22 20:58:32 its wierd tho Dec 22 20:58:36 it was running android fine Dec 22 21:08:05 ok it looks like disabling selinux changed something! Dec 22 21:08:08 but now i cant ssh to the device Dec 22 21:08:09 [34399.607456] usb 2-1.4: Product: Fire … [34399.607458] usb 2-1.4: Manufacturer: amazon Dec 22 21:13:10 shit there is probably a prop in dt that makes it adb insecure Dec 22 21:13:25 so when the android container starts it kinda Dec 22 21:13:28 messes up Dec 22 21:39:43 ● lxc@android.service - LXC Container: android … Loaded: loaded (/lib/systemd/system/lxc@.service; enabled; vendor preset: enabled) … Active: active (running) since Sun 2019-12-22 21:38:14 UTC; 1min 20s ago Dec 22 21:39:44 YES Dec 22 21:39:46 IT WAS SELINUX Dec 22 21:42:46 @NotKit [you need either to apply libhybris patch to support shim libs and rebuild libhyb …], oh btw Dec 22 21:42:53 that symbol is found in hwcomposer.mt8127.so Dec 22 21:43:06 maybe its not getting copied? Dec 22 21:45:13 if you check symbol imports/exports table, it probably requires that symbol, not provides it Dec 22 21:45:45 hwcomposer.mt8127.so is driver lib, so normally no other libs can be linked against it Dec 22 21:46:00 hmm ok Dec 22 21:46:13 well im gonna leave today as "hey lxc container finally fucking started" Dec 22 21:46:48 things dont look so good in the logcats tho Dec 22 21:46:51 except maybe camera Dec 22 21:47:20 E/HAL ( 16): dlopen failed: library "libnativehelper.so" not found Dec 22 21:47:20 nvm Dec 22 21:49:34 ```Binary file ./amazon/austin/proprietary/lib/libasp.so matches … Binary file ./amazon/mt8127-common/proprietary/lib/libvcodecdrv.so matches … Binary file ./amazon/mt8127-common/proprietary/lib/hw/hwcomposer.mt8127.so matches … Binary file ./amazon/mt8127-common/proprietary/lib/libcam.camshot.so matches … Binary file ./amazon/mt8127-co Dec 22 21:49:34 mmon/proprietary/lib/libgralloc_extra.so matches … Binary file ./amazon/mt8127-common/proprietary/lib/libcam.device1.so matches … Binary file ./amazon/mt8127-common/proprietary/lib/libMtkOmxAIVPlayer.so matches … Binary file ./amazon/mt8127-common/proprietary/lib/libcam.camadapter.so matches … Binary file ./amazon/mt8127-common/proprietary/lib/libg Dec 22 21:49:34 ui_ext.so matches``` Dec 22 21:49:47 guess ill die Dec 22 21:59:30 If there's a unofficial build of Lineage, just curious where would you get your sources? Dec 22 22:04:38 @SomeIrrelevantPerson0000 [If there's a unofficial build of Lineage, just curious where would you get your …], Look at XDA thread of build Dec 22 22:04:44 Go to where it says sources Dec 22 22:04:45 Ez Dec 22 22:26:47 There is no xda thread Dec 22 22:39:28 then try to track down the author and ask him Dec 22 22:39:36 no other way, unfortunately Dec 22 22:39:55 His is on github, I will try. :) Dec 22 22:40:13 @NotKit Thank you very much ❤ Dec 22 22:40:24 no corresponding repos on his GitHub account though? Dec 22 22:40:54 I don't see the gt58wifi device repo. But I found everything else. Dec 22 22:41:20 My previous builds were kinda frankenstein builds, from different repos. Dec 22 22:41:39 I want a pure build. Haha Dec 23 00:34:35 When writing .xml files. Must all sources be of a cm-14.1 branch? Dec 23 00:39:43 Gredfix was added by: Gredfix **** BEGIN LOGGING AT Mon Dec 23 01:23:44 2019 Dec 23 01:36:17 someone@SomeIrrelevantPerson:~/halium$ ./halium/devices/setup samsung_gt58wifi … The given device is not supported. :( Dec 23 01:36:50 (Document) https://irc.ubports.com/iaM4pPyO.xml **** ENDING LOGGING AT Mon Dec 23 03:00:01 2019