**** BEGIN LOGGING AT Fri Oct 04 03:02:52 2019 Oct 04 06:27:45 @NotKit https://bpaste.net/show/JsYf Oct 04 06:28:38 hangs at sudo start lxc-android-config Oct 04 06:31:51 https://bpaste.net/show/8Z5c Oct 04 06:35:03 yay Oct 04 06:35:04 root@ubuntu-phablet:~# sudo lxc-info -n android … Name: android … State: RUNNING … PID: 910 … IP: 10.15.19.82 … root@ubuntu-phablet:~# Oct 04 06:37:48 test hwcomposer faileds wit same problem Oct 04 07:05:50 can i copy system img to data? Oct 04 07:06:03 or halium-install dose something spechial Oct 04 07:06:31 becouse full install with rootfs tooks time Oct 04 07:12:36 seems to use convert_androidimage 2>&1 | $out Oct 04 07:15:05 @Luka [test hwcomposer faileds wit same problem], Have you tried `EGL_PLATFORM=hwcomposer test_hwcomposer` instead? Oct 04 07:19:42 yep i used it Oct 04 07:29:01 Hervé was added by: Hervé Oct 04 08:07:28 @Luka [becouse full install with rootfs tooks time], You could comment out the rootfs part, that should speed it up. Oct 04 08:08:09 @JBBgameich [You could comment out the rootfs part, that should speed it up.], yep thanks, next time i will do that Oct 04 08:09:54 @Luka [test hwcomposer faileds wit same problem], strace it and check /system/bin/logcat as well Oct 04 08:10:11 it is possible that your chip is too old and has HWComposer 1.0 Oct 04 08:19:09 @NotKit [it is possible that your chip is too old and has HWComposer 1.0], any way to check? Oct 04 08:19:59 can you run mir_demo_server with verbose? Oct 04 08:20:21 it is in mir-demos package Oct 04 08:20:24 later, reinstaling Oct 04 08:20:41 @NotKit [it is in mir-demos package], is it pre-instaled? Oct 04 08:20:53 no Oct 04 08:21:14 hmm then i must test wifi Oct 04 08:21:21 but i know how Oct 04 08:21:50 echo 1 > /sys/devices/platform/sd8x-rfkill/pwr_ctrl … cd /lib/modules … insmod mlan.ko … insmod sd8xxx.ko drv_mode=5 cfg80211_wext=12 sta_name=wlan wfd_name=p2p max_vir_bss=1 Oct 04 08:22:04 worked on pmos Oct 04 08:29:57 [c0] mlan: Unknown symbol __aeabi_unwind_cpp_pr0 (err 0) … [ 113.971313] [c0] mlan: Unknown symbol __aeabi_unwind_cpp_pr1 (err 0) Oct 04 08:30:12 with last defconfig i cant insmod anything Oct 04 08:30:58 phablet@ubuntu-phablet:~$ dmesg … dmesg: read kernel buffer failed: Operation not permitted … phablet@ubuntu-phablet:~$ Oct 04 08:31:28 i think apparmor problem Oct 04 08:36:47 try sudo? Oct 04 08:37:04 works Oct 04 08:37:07 with sudo Oct 04 08:37:20 @Luka [with last defconfig i cant insmod anything], you changed config but didn't rebuild modules Oct 04 08:37:43 hmmm i did Oct 04 08:37:48 or it can be broken kernel sources Oct 04 08:39:58 phablet@ubuntu-phablet:~$ /system/bin/logcat … logcat read failure: No such file or directory Oct 04 08:46:03 i cant compile with CONFIG_USER_NS Oct 04 08:46:15 @Luka [i cant compile with CONFIG_USER_NS], that's not needed Oct 04 08:46:27 ok Oct 04 08:46:49 @NotKit [or it can be broken kernel sources], not much options Oct 04 08:52:41 so what can i do? Oct 04 09:08:19 fbo is ok Oct 04 09:08:21 lol Oct 04 09:12:50 (Photo, 1386x1154) https://irc.ubports.com/GsutMnEL.png cutt.ly/meuowdY … 👌👍😳 Oct 04 09:15:30 @Luka [so what can i do?], debug and fix whatever is wrong with it :) Oct 04 09:18:24 but how? Oct 04 11:36:43 @JBBgameich What is the reason the debian rootfs is i386? Could I try on a 64 bit system (e.g. KDE Neon) when building libhybris myself and maybe patch Qt for kernel 3.10 or is there more to take into account? … Thanks in advance Oct 04 11:40:34 @Daniel [@JBBgameich What is the reason the debian rootfs is i386? Could I try on a 64 bi …], It was originally built for a device that only supports I386. Building a 64 bit one should be easy in theory, the packages are already there, but depending on your hardware you might run into gles problems. Oct 04 11:41:33 Neon might actually already have amd64 Libhybris builds in the plamo repository. Oct 04 11:44:59 For debian it's only a question of adding a new architecture to the build matrix of the rootfs-builder. Oct 04 11:45:52 Ok, I see... thanks! who can I tell if Ill run into GLES issues? Oct 04 11:47:34 If your graphics chip supports desktop GL it will work. If it only supports gles, it will require more work to rebuild Qt. Oct 04 11:49:17 Ok, i got a PowerVR. So I guess no Desktop GL... Oct 04 11:49:18 Currently Qt is only built with GLES support on arm and i386, but actually we could probably do that on all architectures given that debian-pm only targets embedded systems anyway. Oct 04 11:57:00 Hm... didnt know there were arch specific parts in Qt. I guess it will require some work then...? Oct 04 11:57:03 I was just asking because there is a growing number of software not (properly) supporting i386 (like Spotify 😑) Oct 04 11:58:59 So currently the work might exceed the benefits... Oct 04 12:32:17 Adetunji Strange was added by: Adetunji Strange Oct 04 12:32:21 https://tgraph.io/TON-launch-is-confirmed-10-04 Oct 04 12:40:42 Daniel do you have 64-libs on device? Oct 04 12:40:49 [Edit] Daniel do you have 64-bit libs on device? Oct 04 12:47:56 @Daniel [Hm... didnt know there were arch specific parts in Qt. I guess it will require s …], That's mostly in the packaging. The gl type is chosen based on the architecture since Qt can't support gles and desktop gl in one build. **** BEGIN LOGGING AT Fri Oct 04 13:16:54 2019 Oct 04 13:43:59 @NotKit [Daniel do you have 64-bit libs on device?], I assume you mean the Android libs, right? Those are i386... Oct 04 13:46:47 yes, then having 64-bit libhybris won't help Oct 04 13:56:10 @JBBgameich [That's mostly in the packaging. The gl type is chosen based on the architecture …], Ah, ok. But can I sill run a 64 bit system with hybris support? Oct 04 13:59:27 Generally yes, but probably that also depends on which android libs are available as NotKit said. Oct 04 14:01:35 @Daniel [@JBBgameich What is the reason the debian rootfs is i386? Could I try on a 64 bi …], i386 =/= arm(32) … Unless you're talking about an intel powered zenfone or so.. Oct 04 14:02:00 Yes, this is an intel device Oct 04 14:02:07 Then I take that back Oct 04 14:04:09 @JBBgameich [Generally yes, but probably that also depends on which android libs are availabl …], Ok. I guess I will focus then on getty kwin work properly first. Thanks for the clarification Oct 04 14:04:10 Also, I know there is a 4 GB RAM version of the Zenfone 2, so there should exist a 64 bit version, right? Oct 04 14:05:55 you can have more than 3GB RAM on 32-bit Oct 04 14:06:59 i'm pretty sure the chip in the zenfone supports PAE Oct 04 14:09:30 You are right, cpuinfo says so... Oct 04 14:09:34 but yes, android platform 21 and newer supports both x86 and x86_64 Oct 04 14:13:37 so looks like it could be either 32-bit or 64-bit android since it came with lollipop which was api level 21 Oct 04 14:15:51 so i guess see what `uname -m` says on factory image? Oct 04 14:21:42 Well uname gives x86_64 (kerne is 64 bit) but file on a library yields that those are 32 bit... Oct 04 14:23:15 if only 32-bit userspace is available, then yeah, you need i386 hybris anyway. but i suppose you could also possibly build 64-bit userspace with halium if you wanted instead Oct 04 14:34:14 @Daniel [Well uname gives x86_64 (kerne is 64 bit) but file on a library yields that tho …], Have you checked if `/system/lib64/` is also available? **** BEGIN LOGGING AT Fri Oct 04 14:39:44 2019 Oct 04 14:46:04 @peat_psuwit [Have you checked if /system/lib64/ is also available?], Unfortunately not. Also proprietery libs are only available in 32 bit. Oct 04 14:52:30 Ok. Oct 04 14:55:22 Thanks for the input anyways. Oct 04 14:56:50 hmmm can i havw link to wipp halium 8? Oct 04 15:06:45 @Luka: https://github.com/Herrie82/android/tree/halium-8.1 Oct 04 15:06:53 It builds, but that's about it ;) Oct 04 15:11:39 thanks Oct 04 15:11:52 @Herrie [It builds, but that's about it ;)], it builds, cool Oct 04 15:12:17 what is not right with it? Oct 04 15:19:32 cloning Oct 04 15:19:51 what is better to use armv7 or aarch64 Oct 04 15:19:55 i have bothe Oct 04 15:39:32 I would go for aarch64 to be honest but depends on what you want to boot after Halium as well Oct 04 15:39:45 Well it doesn't boot, which can be a lot of things Oct 04 15:39:58 I just quickly tried with Hammerhead, didn't have much chance to debug anything yet Oct 04 15:41:14 ok Oct 04 15:41:25 will use armv7 for now Oct 04 15:41:33 synced device Oct 04 15:41:43 will try to debug Oct 04 15:41:52 what is best rootfs ? Oct 04 15:41:54 ut? Oct 04 15:42:09 @Herrie [I just quickly tried with Hammerhead, didn't have much chance to debug anything …], serial is friend Oct 04 15:44:24 do i need mer-kernel-checkonfig? Oct 04 15:45:10 or ./halium/halium-boot/check-kernel-config Oct 04 15:45:14 will do that Oct 04 15:46:02 That's a good one, not too familiar with UT Oct 04 15:46:15 Mer & LuneOS work with mer-kernel-checkconfig Oct 04 15:46:21 But UT needs apparmor and other bits Oct 04 15:48:01 ok will use ut checker and arn64 Oct 04 15:48:08 will build now Oct 04 15:49:17 but firstly fix fstab Oct 04 15:51:13 Ehm the setup script should normally do that Oct 04 15:51:40 I.e.: https://github.com/Herrie82/halium-devices/blob/halium-8.1/setup Oct 04 15:51:44 If not a PR would be good ;) Oct 04 15:52:51 I tried to automate a lot of the device repo patching in the setup script. Because we were mainly forking the device/vendor repos for disabling Java/APK/JAR stuff and fixing fstab ;) Oct 04 15:53:07 build/core/base_rules.mk:238: error: vendor/motorola/cedric: MODULE.TARGET.SHARED_LIBRARIES.libril already defined by hardware/ril/libril. Oct 04 15:53:45 How does your device manifest look like? Oct 04 15:53:45 @Herrie [I tried to automate a lot of the device repo patching in the setup script. Becau …], yes, but i didnt changed f2fs to ext4 Oct 04 15:54:24 Ah ok. Yeah that might be a good addition ;) Oct 04 15:54:31 @Herrie [How does your device manifest look like?], https://bpaste.net/show/15zd Oct 04 15:54:35 Anyway for that error: In your device manifest you might want to remove: https://github.com/Herrie82/android/blob/halium-8.1/default.xml#L551 Oct 04 15:55:06 thanks i will Oct 04 15:55:28 Similar to: https://github.com/Halium/halium-devices/blob/halium-5.1/manifests/hp_tenderloin.xml#L9 Oct 04 15:59:24 ok rebuilding Oct 04 16:00:42 passed that error Oct 04 16:04:46 hanging at [ 97% 248/254] Install: /home/hello/halium8/out/host/linux-x86/bin/depmod Oct 04 16:05:30 damn Oct 04 17:17:10 let me change source Oct 04 17:29:13 building Oct 04 17:32:59 @Luka [yes, but i didnt changed f2fs to ext4], if it is for data, it doesn't matter Oct 04 17:33:30 Android fstab is not read to mount it Oct 04 17:33:31 hmmm on ut f2fs is bad idea Oct 04 17:33:55 hmm If the type of the ‘data’ or ‘userdata’ partition is f2fs, it is required to change it to ext4. Oct 04 17:34:04 http://docs.ubports.com/en/latest/porting/building-halium-boot.html Oct 04 17:34:34 that doc part is wrong then Oct 04 17:34:47 hmm may be Oct 04 17:34:50 [ 53% 7/13] Building Kernel Oct 04 17:34:57 waiting Oct 04 17:35:36 I advice to try to get container working on pmOS first Oct 04 17:35:50 with UBPorts you will have issues getting to SSH Oct 04 17:36:06 you are about halium 8? Oct 04 17:36:10 yes Oct 04 17:36:16 may be Oct 04 17:36:38 what is the arm64 device? Oct 04 17:36:59 device with aarch64 cpu i think Oct 04 17:37:10 msm8937 in my case Oct 04 17:37:37 @NotKit [what is the arm64 device?], but what do you mean? Oct 04 17:37:52 device tree/ kernel/vendor Oct 04 17:38:08 that is what i am using Oct 04 17:40:08 @Luka [ok will use ut checker and arn64], if you are about that Oct 04 17:41:48 device name Oct 04 17:41:55 cedric Oct 04 17:41:58 moto g5 Oct 04 17:42:16 https://github.com/Sohamlad7/android_device_motorola_cedric/tree/lineage-15.1-64 Oct 04 17:42:19 weird target for dealing with 8, but ok Oct 04 17:42:25 without rootf all is ok Oct 04 17:42:48 @NotKit [weird target for dealing with 8, but ok], why? Oct 04 17:43:05 because stock is much older Oct 04 17:44:02 yes 7.1 Oct 04 17:44:09 but there is 8.1 Oct 04 17:44:13 stock Oct 04 17:44:32 cm14 tree is 32 and unstable Oct 04 17:46:51 ninja: error: 'vendor/motorola/cedric/proprietary/vendor/etc/permissions/ConnectivityExt.xml', needed by '/home/hello/halium8/out/target/product/cedric/obj/ETC/ConnectivityExt_intermediates/ConnectivityExt.xml', missing and no known rule to make it Oct 04 17:52:47 Can anyone tell me which folders should i have under /android Oct 04 17:53:35 i have one which is called /android/none which gives me impression thats not nice Oct 04 18:06:26 @Luka [ninja: error: 'vendor/motorola/cedric/proprietary/vendor/etc/permissions/Connect …], tree problem? Oct 04 18:16:12 ok passed Oct 04 18:39:37 32% Oct 04 18:41:13 compiling is relatively easy part, making modifications to allow rootfs to boot and start LXC is going to be more tricky Oct 04 18:54:11 Yep Oct 04 18:54:21 If ssh wount work Oct 04 18:54:50 It will be tricky Oct 04 18:57:51 Is serial working in halium? Oct 04 19:01:05 depends completely on kernel and rootfs, that part doesn't utilize Android blobs in any way Oct 04 19:05:00 ok will try to do that without shh, dont whant to disasemble phone Oct 04 19:05:11 still building Oct 04 19:05:30 hmm damn it tg x is broken on android q Oct 04 19:33:32 how can i check if init was successfull? Oct 04 19:34:02 like see logs without need to timeout to ssh in 1s Oct 04 22:58:41 litanyzhae was added by: litanyzhae Oct 04 23:31:24 @litanyzhae [litanyzhae was added by: dohbee], @UniversalSuperBox @Flohack @fredldotme spammer Oct 04 23:35:32 fakoboja was added by: fakoboja Oct 05 00:40:29 Dominic Donnelly was added by: Dominic Donnelly **** ENDING LOGGING AT Sat Oct 05 03:01:28 2019