**** BEGIN LOGGING AT Fri Apr 27 03:00:04 2018 Apr 27 08:12:36 Help me Apr 27 08:12:37 Fwd from ankaos: @BlinkSD @archi_dagac hybris/hybris-boot/Android.mk:67: ***************** /boot appears to live on ERROR: *fstab* not found … hybris/hybris-boot/Android.mk:68: ***************** /data appears to live on ERROR: *fstab* not found … hybris/hybris-boot/Android.mk:71: *** There should be a one and only one device en Apr 27 08:12:37 try for HYBRIS_BOOT_PART and HYBRIS_DATA_PART. … make: *** [/home/enesutku07/hadk/out/build-lineage_j5lte.ninja] Error 1 Apr 27 11:01:47 @ankaos, device's fstab seems to be missing. Check it in device/[manufacturer]/[device]/rootdir/etc Apr 27 11:02:11 @ankaos, [Edit] device's fstab seems to be missing. Check if it exists in device/[manufacturer]/[device]/rootdir/etc Apr 27 11:11:52 Not fount Apr 27 12:37:22 Did you run 'source build/envsetup.sh'? Apr 27 13:58:49 vanyasem was added by: vanyasem Apr 27 14:15:39 Pm 5.1 caf rootfs is in rootfs or rootfs-caf dir in the server Apr 27 14:20:14 ritardato there is no 5.1 caf rootfs ..for PM .. there is only caf rootfs and rootfs Apr 27 14:21:20 I mean for halium 5.1 Apr 27 14:21:28 Caf Apr 27 14:21:33 Use the regular one Apr 27 14:22:29 Ok, thanks Apr 27 14:32:46 @ankaos, Which device? Apr 27 15:21:08 @mayltonfnds, Yes Apr 27 15:21:37 @iamasim, Samsung Galaxy j5 Apr 27 15:22:08 @ankaos, Codename? Apr 27 15:24:12 Jlte Apr 27 15:24:24 J5lte Apr 27 15:26:18 @ankaos, Which repository? Apr 27 15:28:58 local manifest? Apr 27 16:55:49 (Document) https://irc.ubports.com/uKOqvq1M.xml Apr 27 16:55:53 @iamasim Apr 27 16:59:22 @ankaos, U have to create a fstab file Apr 27 17:00:16 i can not show what is in itself @iamasim Apr 27 18:15:40 Anyone know how to fix "qdoverlay( 0): Bad ov dump: mdp_overlay z=0 fg=0 alpha=255 mask=-1 " when running test_hwcomposer? It makes display crash Apr 27 18:49:38 Anyone have any suggestions for 'Could not create a socket for 91.189.88.150 (f=2 t=1 p=6) - socket (13: Permission denied)' from `apt update`, `apt-get update`? (Note: I added /etc/hosts entries because apt was seemingly incapable of making DNS resolutions). I applied the patches mentioned on the wiki and added root and _apt to gid 3004 Apr 27 18:53:05 (this is the set of patches I applied https://docs.halium.org/en/latest/porting/debug-build/wifi.html#kernel-3-10-ping-socket-permission-denied ) Apr 27 22:13:12 Is Mediatek X20 good for porting? Apr 27 22:13:37 Depends Apr 27 22:13:41 MT6797 Apr 27 22:13:50 How? Apr 27 22:14:11 Whether your phone is unlockable and has sources Apr 27 22:14:14 Mediatek is sketchy Apr 27 22:14:45 I know, but I think all mediatek device is unlockable, more specifically, there isn't a lock. Apr 27 22:15:24 my MediaTek device was unlocked without needing to get any OEM key or anything Apr 27 22:15:31 The factory mode is all Chinese Apr 27 22:15:34 couldn't comment about the availability of sources Apr 27 22:15:48 All devices are unlockable Apr 27 22:15:52 with enough hacking Apr 27 22:16:07 @lambdaperl[m], What mediatek device is yours? Apr 27 22:16:36 didn't you see the trick they pulled off with Nintendo Switch? ARM devices proved to have bizarre ways of getting into them Apr 27 22:16:50 it was an Alcatel Pixi 4, but I never tried to port Halium to it or anything, although I did install Cyanogen Apr 27 22:17:10 My Mediatek device is the Kodak Extra. Apr 27 22:17:13 Ektra Apr 27 22:17:18 And if you had some hardware you could just manually flip some bits with the method of trial and error and get the bootloader to unlock Apr 27 22:17:20 Anyway for my Alcatel Pixi 4, it was just adb/fastboot unlock Apr 27 22:17:46 My device came with pure Android 6.0.1 and never upgraded Apr 27 22:17:56 There isn't a single update Apr 27 22:18:10 I still stuck on a two years old security patch Apr 27 22:22:46 Although I believe that when I did unlock the bootloader in my phone, the stock OS no longer booted (it went in a boot loop) Apr 27 22:35:58 unlocking the bootloader does a factory reset in most cases Apr 27 22:36:08 it could break the stock OS Apr 27 22:36:14 Yes, that seems probable Apr 27 22:36:38 you could probably reinstall it and it would work Apr 27 22:37:17 Or switch to Cyanogen/Lineage in my case which was the idea all along :-) **** ENDING LOGGING AT Sat Apr 28 03:00:03 2018