**** BEGIN LOGGING AT Sat Jul 06 02:59:56 2019 Jul 06 04:31:29 Wow ... At logo first boot... 😱 Jul 06 04:31:40 [Edit] Wow ... logo at first boot... 😱 Jul 06 04:58:55 @ankaos [I have installed ubports. I made the kernel file according to both halium and ub …], That means UT is either crashing or unity is failing Jul 06 09:27:19 @Tygerpro [That means UT is either crashing or unity is failing], Solution? Jul 06 09:56:37 @Tygerpro [That means UT is either crashing or unity is failing], https://paste.ubuntu.com/p/wcKcK6WdJR/ Jul 06 11:34:12 UT is crashing cause you have mount tasks failing which could be why your container isnt working Jul 06 11:34:54 You could try editing your fstab file to see if that works Jul 06 11:40:03 fixup-mountpoint edit ? Jul 06 11:43:52 and what parts will I edit? Jul 06 11:45:42 (Document) https://irc.ubports.com/WZH6E5T6.txt Jul 06 11:57:56 @Tygerpro [You could try editing your fstab file to see if that works], how make ı? ı dont know Jul 06 11:59:27 JBB-xmpp: just for you: https://gitlab.com/JBBgameich/halium-install/merge_requests/28 :-) Jul 06 12:02:19 Are you sure that would not break mkfs.ext4? Jul 06 12:02:43 In your /etc/rootdir/etc/fstab.qcom (file name might differ) you could try manually editing that to the device names rather than trying to have halium-boot figure it out, this isnt the ideal way to get things mounted, but it should help give some insight Jul 06 12:06:18 > JBB-xmpp: just for you: https://gitlab.com/JBBgameich/halium-install/merge_requests/28 :-) Jul 06 12:06:18 There is usually a package containing simg2img in most distributions. That's what I used so far. Using halium-install in the halium tree is kind of a new usecase... maybe we should check for the executables in the root PATH || or the user path? Jul 06 12:18:16 JBB-xmpp: also halium-install won't work if e2fsck returns a warning about the FS being modified Jul 06 12:18:25 system: ***** FILE SYSTEM WAS MODIFIED ***** Jul 06 12:18:26 system: 2438/196608 files (0.0% non-contiguous), 139177/786432 blocks Jul 06 12:19:25 probably my image was a chance out of thousands because i recall this doesn't show up on other images i created Jul 06 12:29:02 How to connect to device via telnet if this connects to localhost instead of device Jul 06 12:48:47 JBB-xmpp: it doesn't break it, I tried it Jul 06 12:50:26 JBB-xmpp: but I'm a bit confused on what the script does. I see that it pushes the images with adb, but what happens next? I flashed the hybris-boot.img via TWRP, and then TWRP warns me that there is no OS installed Jul 06 12:51:04 don't we need to move the uploaded images to the respective partitions? Jul 06 12:53:08 @mardy [JBB-xmpp: but I'm a bit confused on what the script does. I see that it pushes t …], Thats normal if you cleared your device before flashing, hybris-boot goes to your boot partition then the rest go to /data, TWRP is looking for more stuff and since it doesnt see it, it says theres no OS installed Jul 06 12:54:14 TWRP can flash hybris-boot but the rest just yet put in /data after you process them so they can be mounted Jul 06 12:54:35 @Tygerpro: so, the code in hybris-boot will be loading the two images from /data itself? Jul 06 12:56:03 If it successfully boots yes, otherwise you shoukd get a telnet connection which will have a diagnosis ile that will tell you what failed Jul 06 13:08:48 I don't get it (not even with the lsusb trick -- my device does not appear in dmesg at all) Jul 06 13:12:32 If its hybris-boot it may take a bit, on my galaxy note 4 it took 20 minutes to boot when it was successfully booting, but 3 seconds if something failed Jul 06 13:54:20 @Tygerpro: ouch! Well, I didn't wait that long. :-) But shouldn't I see it in dmesg almost immediately? Jul 06 14:06:46 In theory yeah, but in practice doubt it, I figured it out by accident actually Jul 06 19:40:27 (Photo, 1280x719) https://irc.ubports.com/6uzZhwil.png Jul 06 19:40:51 Tygerpro not open. Android container stopped. Jul 06 19:55:55 @ankaos [Tygerpro not open. Android container stopped.], http://docs.halium.org/en/latest/porting/debug-build/debug-android-userspace.html Jul 06 19:56:07 have you tried logcat? Jul 06 19:57:10 (Photo, 1280x719) https://irc.ubports.com/xGAXd7p0.png Jul 06 19:58:30 root@ubuntu-phablet:~# /system/bin/logcat … logcat read failure Jul 06 19:59:14 dmesg? Jul 06 20:03:09 @fredldotme [dmesg?], https://paste.ubuntu.com/p/KxrRmF3pZB/ Jul 06 20:05:46 @ankaos [https://paste.ubuntu.com/p/KxrRmF3pZB/], try running whatever is in /etc/init/lxc-android-config.conf manually Jul 06 20:08:13 how? Jul 06 20:08:38 via your shell/ssh of course Jul 06 20:56:35 I wrote a few notes about my port, if they can be of any help: http://www.mardy.it/blog/2019/07/notes-on-porting-the-samsung-j3-to-halium-%2B-ubports.html Jul 07 01:40:29 @mardy [I wrote a few notes about my port, if they can be of any help: http://www.mardy. …], I just skimmed through your link, I did spot a few of the same problems I had, did you end with a booting port? **** ENDING LOGGING AT Sun Jul 07 03:00:53 2019