**** BEGIN LOGGING AT Fri Mar 01 02:59:57 2019 Mar 01 05:10:11 Bensuperpc was added by: Bensuperpc Mar 01 07:59:23 For completeness, have you tried running with: `EGL_PLATFORM=hwcomposer test_hwcomposer` Mar 01 08:00:00 [Edit] For completeness, have you tried running: `EGL_PLATFORM=hwcomposer test_hwcomposer` Mar 01 11:10:04 Has anyone of you had experience with using heimdall to flash the boot.img it always says something about a failed packet. I'm not on my pc right now so I can't provide the full message Mar 01 12:08:19 @Flohack, In fact, I have already changed the fixup-mountpoint from the one already provided. But I will try to change the fstab Mar 01 12:08:50 @NotKit, I need to check that Mar 01 12:09:04 @NotKit, I will check that Mar 01 12:41:44 OK fuck 3.4 kernels I give up, waiting for oreo/pie compatibility or a gsi Mar 01 12:42:14 @Nebrassy how would that help with 3.4 kernels? Mar 01 12:42:38 and were you booting UBPorts or what? Mar 01 12:43:23 @NotKit, I'd be working on my new phone rather than my ancient one Mar 01 12:43:27 @NotKit, Yeah Mar 01 12:47:15 what were the issues with 3.4? I doubt it would be easier at first Mar 01 12:48:23 @thatannoyingguy4, I just flash the boot image using TWRP, makes life a bit easier that way Mar 01 12:49:22 @NotKit, Kernel panics for seemingly no reason and unity8 never starting after solving all other problems, possibly incompatible drivers Mar 01 12:49:40 @Nebrassy, . Mar 01 12:55:53 is it 7.1-caf? Mar 01 12:56:09 Yup Mar 01 12:56:25 wrong platform is selected by Mir then Mar 01 12:56:33 try with latest rootfs Mar 01 12:57:15 I should be using this right? … https://ci.ubports.com/job/xenial-hybris-edge-rootfs-armhf/ Mar 01 12:57:22 not edge Mar 01 12:57:41 This then … https://ci.ubports.com/job/xenial-rootfs-armhf/ Mar 01 12:57:48 y Mar 01 12:58:45 Been having the same problem for months, I'll try with the latest rootfs, the problem is I'm not finding what the problem is Mar 01 12:59:39 Do you think using 5.1 instead of 7.1 could help? Mar 01 13:05:59 not really, better debug it Mar 01 13:43:50 @thatannoyingguy4, I "> Ok @Tygerpro, I'll try that, thanks Mar 01 13:49:15 Oh wow, Matrix replies through IRC through Telegram are really screwed up **** BEGIN LOGGING AT Fri Mar 01 17:27:35 2019 Mar 01 20:07:04 @Daniel, Did you already have time to test whether it works? Mar 01 21:28:40 @Nebrassy, ping me on UBPorts porting channel when you try so I notice Mar 01 21:29:16 Alright Mar 01 21:36:09 DickThomas was added by: DickThomas Mar 01 21:51:11 @Flohack, What do you mean by wrong ? … I check both file and I can't find what can do an error … I'm not sure but can I use the modemnvm3, modemlog, modemnvm2 and splash2 partition ? Mar 01 21:51:31 @aurnytoraink, For the fstab file Mar 01 21:57:47 @aurnytoraink, Can you provide boot log with halium messages from initd Mar 01 21:57:54 or systemd more or less Mar 01 21:58:35 That can seem a stupid question but where do I find that ? Mar 01 21:58:55 make a wrong boot. boot into recovery again and cat /proc/last_kmsg Mar 01 21:59:10 ah okay Mar 01 22:01:32 (Photo, 720x1280) https://irc.ubports.com/c6XEUdpd.png Hmmm Mar 01 22:03:55 then smth is really wrong with your kernel Mar 01 22:04:34 Ah! Mar 01 22:05:09 @aurnytoraink which is your kernel version? Mar 01 22:05:16 it is pstore starting from 3.18 on Qcoms Mar 01 22:06:23 Hmmm first it's a huawei device, so it's a Kirin socket and I think the linux kernel is 3.10.xxx Mar 01 22:06:29 Let me check Mar 01 22:07:27 3.10.108 Mar 01 22:08:21 oops 3.10.105 Mar 01 22:08:47 do you have /proc/last_kmsg normally? Mar 01 22:08:54 e. g. when rebooting Android Mar 01 22:10:38 I don't know, I need to restore my Android backup to test that Mar 01 22:11:04 you can just reboot from recovery into recovery Mar 01 22:11:11 I mean I haven't try this before Mar 01 22:11:41 @NotKit, Hmm okay Mar 01 22:15:59 Well, I reboot my phone in recovery mode … And try the command directly on the phone … But it still doesn't work Mar 01 22:31:04 @aurnytoraink ls /sys/fs/pstore Mar 01 22:31:49 actually there is 3 "ramops" file Mar 01 22:32:01 then it is pstore on your device Mar 01 22:32:14 ah okay thanks Mar 01 22:32:38 dmesg-ramoops and console-ramoops are generally the interesting ones Mar 01 22:33:10 actually I have one console and 2 dmesg Mar 01 22:42:09 okay there is a lot of fail Mar 01 22:42:16 like this: … [ 9.484586s]BT chip type is not match, skip driver init … [ 9.484617s]BT-sleep chip type is not match, skip driver init … [ 9.484647s]gps chip type is not match, skip driver init Mar 01 22:42:48 [Edit] like this: … [ 9.484586s]BT chip type is not match, skip driver init … [ 9.484617s]BT-sleep chip type is not match, skip driver init … [ 9.484647s]gps chip type is not match, skip driver init … [ 9.484678s][pid:1,cpu1,swapper/0]wifi chip type is not match, skip driver init Mar 01 22:43:22 [ 0.000000s][pid:1,cpu0,swapper/0]/cpus/cpu@4: Unknown CPU type … Is it good ? Mar 01 22:51:28 those kind of errors are normal for Android kernels Mar 01 22:51:35 real problem is usually at the end Mar 01 23:10:41 hello, has anyone here had any joy with building for a note3 (sm-N9005) I can build it all without any errors and transfer it but then it just sits at the device spash screen. I do get a Android device attempt to mount on my PC but nothing else Mar 01 23:26:02 I also built an image for a samsung device but it bootloops on the splash screen and it doesn't even attempt to establish an usb connection. I compiled with the 4 PTRACE options but twrp doesn't show the ptrace directory in /sys/fs . Last_kmesg only shows something about the S-BOOT bootloader and the last nessage is always something with (3) Mar 01 23:28:27 oh joy. I've not this note3 on my desk and I thought I'd do something useful with it :D Mar 01 23:30:20 there is one video on youtube of it working but nothing to help lol reminds me of that xkcd comic Mar 02 01:20:32 I did a port for the note 4, does your device show up in dmesg? **** ENDING LOGGING AT Sat Mar 02 02:59:57 2019