**** BEGIN LOGGING AT Thu Feb 01 03:00:04 2018 Feb 01 03:01:37 @UniversalSuperBox, the new image is officially broken Feb 01 03:01:40 and my port is ok Feb 01 03:01:45 and I am officially stupid Feb 01 03:02:15 Exaplain Feb 01 03:02:36 i am stupid as i forgot to replace [codename] with my actual codename Feb 01 03:02:41 my port is ok as it booted and it works Feb 01 03:03:03 Well it sounds like you messed up then Feb 01 03:03:04 the image is broken as it doesn't boot (even no splash screen), but the old one is cool Feb 01 03:03:22 Might be something in the caf/no-caf change Feb 01 03:03:42 @UniversalSuperBox, should probably try the caf one later then Feb 01 03:03:44 But I wouldn't call it 'broken' that it doesn't show the splash when udev rules aren't set up Feb 01 03:03:49 @vanyasem, Nah. Feb 01 03:03:54 i will anyways Feb 01 03:03:56 That's going away Feb 01 03:06:34 Now, check out /etc/ubuntu-session... I think Feb 01 03:07:01 It should have a bunch of files for different devices. Feb 01 03:07:23 Create one for yours with a GRID_UNITS_PX setting in it. Feb 01 03:07:43 That sets how many pixels constitute a UITK 'grid unit' Feb 01 03:07:55 Or, in simpler terms, display scaling Feb 01 03:09:04 Also, feel free to dance, run around the house, and do other things that very happy people do. Feb 01 03:10:27 @UniversalSuperBox, i woke my mother up and showed her my stuff Feb 01 03:10:42 I'm sure she was very confused Feb 01 03:10:45 she's afaid that i am going to die because of my all-nighers Feb 01 03:10:59 @UniversalSuperBox, Linux Mint users are like that, yeah Feb 01 03:11:02 Sometimes I wish my roommate gave half of a shit but he's basically allergic to Linux anyway. Feb 01 03:11:04 Pfffft Feb 01 03:11:22 @UniversalSuperBox, nope, wrong path Feb 01 03:11:29 Bah Feb 01 03:11:30 there is `ubuntu-touch-session.d` Feb 01 03:11:31 is that it Feb 01 03:11:34 Yes Feb 01 03:11:53 GRID_UNIT_PX=23 … QTWEBKIT_DPR=2.5 Feb 01 03:11:57 I'm gonna guess... How large is the screen? Feb 01 03:11:59 this is for hammerheafd Feb 01 03:12:06 5.5 inches, 2k res Feb 01 03:12:24 ... 37 pixels per grid unit Feb 01 03:12:33 do i just make pme.conf? Feb 01 03:12:35 there Feb 01 03:12:36 I don't actually know the calculation. Feb 01 03:12:37 Yes Feb 01 03:13:06 And then reboop. Or maybe restart lightdm. Feb 01 03:13:53 writes note to make document for that Feb 01 03:15:16 omg it's huge Feb 01 03:15:30 Pic? Feb 01 03:15:32 my grandma would love that Feb 01 03:15:47 (Photo, 960x1280) https://irc.ubports.com/eJxfyZ0i/file_3973.jpg Feb 01 03:15:58 Okay yeah that's too much Feb 01 03:16:44 trying 28 Feb 01 03:17:22 hello @bhushanshah Feb 01 03:17:28 Unity 8 with UITK apps has to-die-for scaling. Feb 01 03:17:32 Sometimes I feel we should have halium ubports and halium pm rooms 😛 Feb 01 03:17:33 please congratulate me and take a look at my plasma issues Feb 01 03:17:51 @vanyasem, 28 is just right Feb 01 03:17:55 Yawn.. I am off till almost afternoon Feb 01 03:18:03 @bhushanshah, Well no one else was using it. :P Feb 01 03:18:16 @bhushanshah, not now, just informing you that i discovered them Feb 01 03:18:20 probably related to kwin Feb 01 03:18:22 And I'm trying to bring the two together now! Feb 01 03:18:55 Have fun with whatever else you're doing Feb 01 03:19:03 I'm going to sleep now Feb 01 03:19:21 @UniversalSuperBox, good night dalton Feb 01 03:19:24 thank you a LOT Feb 01 03:19:42 Anytime. Except when I'm asleep or busy Feb 01 03:19:52 :P Feb 01 03:32:09 @UniversalSuperBox, never give up your dreams. Feb 01 07:49:26 matcher84 was added by: matcher84 Feb 01 08:00:52 @JBBgameich Feb 01 08:01:12 (Photo, 480x800) https://irc.ubports.com/myTtfbKf/file_3985.jpg Feb 01 08:02:16 Btw krillin nd my device is same Feb 01 08:05:19 same SoC? Feb 01 08:06:12 Yup Feb 01 08:06:20 Twin brothers Feb 01 08:06:43 oh well, this surely isn't going to be an easy trip Feb 01 08:06:59 Difference in only battery capacity with 100mah difference Feb 01 08:07:02 since they based device tree on MediaTek AOSP and not on LineageOS or anything Feb 01 08:07:17 @NotKit, Mine is los based Feb 01 08:07:25 Custom one Feb 01 08:08:09 is krillin supported by UBPorts? Feb 01 08:09:28 @NotKit, Don't know but it is shipped with ubuntu touch Feb 01 08:20:08 Also see the last one Feb 01 08:20:45 (Photo, 480x800) https://irc.ubports.com/knYtVqH6/file_3987.jpg Feb 01 08:21:38 do you have prebuilt kernel? Feb 01 09:05:57 Nope Feb 01 09:06:06 Should i compile one? Feb 01 09:07:41 STUP1D_PR0GR4MM3R was added by: STUP1D_PR0GR4MM3R Feb 01 09:19:19 @maharudra108, your device tree needs to compile one instead of using pre-built blob, if it does Feb 01 09:19:59 @NotKit, How pls guide me Feb 01 09:20:36 I didn't see your current device tree and if your device has kernel source code Feb 01 09:21:14 I have device tree on device/micromax/a106 Feb 01 09:21:34 Kernel on kernel/micromax/a106 Feb 01 09:21:56 ok, then check if device tree actually builds the kernel Feb 01 09:22:07 How? Feb 01 09:22:33 in BoardConfig.mk Feb 01 09:23:00 I made changes on kernel as on documention described and compiled it Feb 01 09:23:12 @NotKit, What to do with BoardConfig Feb 01 09:23:37 how did you compile the kernel? Feb 01 09:24:36 cd kernel dir then ./dd(mine kernel is based on daredevil) Feb 01 09:24:58 Adapted from pablito krillin kernel Feb 01 09:27:30 it's just that Halium expects the kernel to be compiled as part of build process, not separately Feb 01 09:29:37 So how to compile along device tree Feb 01 09:29:55 I never did anything like this Feb 01 09:32:57 I'm not good at LineageOS porting, try to Google for CyanogenMod/LOS information Feb 01 09:33:02 this is not Halium-specific Feb 01 09:33:28 https://github.com/danielhk/android_device_lenovo_aio_otfp/blob/cm-14.1/BoardConfig.mk#L78 Feb 01 09:33:41 this is example device tree which builds the kernel, but it's for way newer SoC Feb 01 09:33:53 I compile lots of roms based on los Feb 01 09:33:54 maybe you can find some example for MT6582 which builds the kernel Feb 01 09:34:16 Also based on aosp bt never faced such a issue like this Feb 01 09:34:59 @maharudra108, Compiled* Feb 01 09:38:35 you can also try to check Halium-modified Makefiles to understand why it can't make android-boot.img Feb 01 09:38:48 Can someone give me any hints about how to debug if the lxc@android reboots the device. I don't see anything at all in the system journal Feb 01 09:38:55 Ok Feb 01 09:39:49 https://github.com/Halium/android_build/blob/halium-7.1/core/Makefile#L607 Feb 01 09:40:12 Thnxx bro Feb 01 09:40:17 ZeroPointEnergy: show me last_kmsg or let's say journalctl with lxc@android rebooting device Feb 01 09:40:25 @ZeroPointEnergy, ubports rootfs? Feb 01 09:40:34 I will check it currently i m going class Feb 01 09:40:39 Also I suppose you are not manually starting the lxc@android twice? Feb 01 09:41:27 I do Feb 01 09:41:37 That's bad Feb 01 09:41:50 well I do over systemctl Feb 01 09:41:55 you are not supposed to be starting lxc@android twice never ever Feb 01 09:43:09 say if lxc@android container faiiled to start, don't restart it.. but just reboot Feb 01 09:43:49 At the moment I have to rename systems.img so I don't even make it to ssh, which is probably another problem. So it does not get started because of the dependency. Once I have an ssh session I rename the system.img and try to start the container Feb 01 09:44:18 hm Feb 01 09:44:20 so for start Feb 01 09:44:30 Don't rename system.img Feb 01 09:44:46 systemctl disable lxc@android, and reboot Feb 01 09:45:02 then systemd hangs somewhere and dropbear never starts Feb 01 09:45:14 maybe I should try to fix that one first :-) Feb 01 09:46:10 yep :) Feb 01 09:50:33 At least I have a way to get into ssh and debug it with a running systemd. I only discovered that because I accidentally corrupted the system.img :-) Feb 01 10:30:16 @bhushanshah /lib/udev/rules.d/50-firmware.rules causes race condition with ueventd if it's used as userspace firmware helper Feb 01 10:31:35 (sometimes the loading works, sometimes it fails and in case of MTK the kernel panics) Feb 01 10:31:49 See the issue about that on projectmanagement Feb 01 10:32:01 Issue number umm.. Feb 01 10:33:07 https://github.com/Halium/projectmanagement/issues/9 Feb 01 10:33:29 is it masked in PM builds though? Feb 01 10:33:42 https://github.com/Halium/projectmanagement/issues/33 Feb 01 11:00:19 jimexp was added by: jimexp Feb 01 12:02:58 Hunter616 was added by: Hunter616 Feb 01 12:03:42 Luxxer was added by: Luxxer Feb 01 12:16:26 RenanPrastaJenie was added by: RenanPrastaJenie Feb 01 12:47:09 Did anyone try to port moto x (2014) victara for Halium? I have a spare one, and could give it a try. Feb 01 12:48:04 @jimexp, take a look at github projectmanagement repo Feb 01 12:48:11 look for your device there Feb 01 12:48:18 if its not there, port it Feb 01 12:49:45 if it is, don't forget to say thanks Feb 01 12:56:17 Oke, thanks! Feb 01 15:18:39 How to find what target_device is set Feb 01 16:56:20 @maharudra108, Do you mean TARGET_PRODUCT ? Feb 01 16:57:07 In my tree, it's `TARGET_PRODUCT`, `target`, and `target_device` Feb 01 16:57:18 And you can do `echo $any--of-those` to find them Feb 01 17:16:07 algorrapti was added by: algorrapti Feb 01 17:25:55 Not working nd i don't know how it has been assign to generic instead of my device code name Feb 01 17:29:12 Have you done `breakfast` or `lunch` Feb 01 17:29:31 Breakfast Feb 01 17:34:10 Okay, I've got a file called full_potter.mk which specifies `PRODUCT_DEVICE := potter` Feb 01 17:34:22 It's also in `lineage.mk` Feb 01 17:35:58 Okay Feb 01 17:36:08 Thnxx Feb 01 17:48:00 Actually that time i forgot to do breakfast😝😝 Feb 01 19:52:32 (Photo, 720x1280) https://irc.ubports.com/XLUSZbOP/file_3993.jpg Feb 01 19:52:36 I think I broke it Feb 01 19:52:50 wow Feb 01 19:52:55 on-screen kernel panic :) Feb 01 19:53:08 Oh! So that's what `msm_poweroff.download_mode=01` does Feb 01 19:53:53 That's actually really handy. Feb 01 19:54:40 So @bhushanshah, this is what I was talking about and you were really confused about the other day ^ Feb 01 19:57:31 Aha. That panic means "There is no initramfs" Feb 01 19:57:35 And it is 100% correct Feb 01 20:03:26 @UniversalSuperBox, 'demigod' Feb 01 20:13:54 @UniversalSuperBox, The cable is laughing at you Feb 01 20:14:09 I was hoping someone would notice that! :D Feb 01 20:20:32 @UniversalSuperBox, I find it beautiful Feb 01 20:21:42 It is, actually. I wonder if any other devices have this feature Feb 01 20:21:49 Because it'd be incredibly useful Feb 01 20:39:48 I imagine it's a standard qcom thing judging by the QPST thing it references Feb 01 20:40:10 I have a bad feeling that it's deactivated by a qfuse Feb 01 20:40:55 You can test by adding `msm_poweroff.download_mode=1` and then causing a kernel panic Feb 01 20:41:11 adding it to your cmdline, specifically Feb 01 20:41:28 If I had an unlocked device with me at work I'd try it Feb 01 21:27:42 How to define do I need to configure dependencies for my DOOGEE_X5PRO in xml? Feb 01 21:41:05 @UniversalSuperBox, It is possibile to have a "commandline"(like your kernel panic) in halium instead default phone logo? Feb 01 21:41:26 Yes, there is a framebuffer console on MSM devices Feb 01 21:41:29 But it normally doesn't work Feb 01 21:47:53 @Progromizd, by trial and error Feb 01 21:48:31 there are no dependencies listed in device tree though Feb 01 21:58:48 @UniversalSuperBox, There is a way to enable It? (Specially in halium) Feb 01 21:59:01 No clue. Feb 01 21:59:24 @UniversalSuperBox, Ah ok, thank you! Feb 01 22:21:01 Well, I figured out why ssh doesn't work on the Nexus 5X with Ubuntu Touch Feb 01 22:21:05 bash never starts Feb 01 22:21:33 Why? I can't find out. Bash won't run. :P Feb 01 23:10:49 Update: There appear to be some syscalls that cause everything to stop. For example, running `sudo -i` makes everything stop responding Feb 01 23:11:59 The only hint is `[ 42.849965] msm_rng:Data not available!` appears when it stops responding Feb 01 23:53:17 @UniversalSuperBox, That almost sounds like a kernel issue Feb 01 23:55:12 @UniversalSuperBox, That triggers here at line 147: … https://github.com/LineageOS/android_kernel_lge_bullhead/blob/2a0cfff1e9e2ae1540e21c3713d281d14dcd7219/drivers/char/hw_random/msm_rng.c Feb 01 23:59:45 Right, this is what I get with telnet after the thing happens: https://paste.ubuntu.com/26503042/ Feb 01 23:59:49 And it just sits Feb 02 00:00:08 (I had to shove telnetd onto the rootfs since sshd locks up) Feb 02 00:13:50 It's a red herring! I can `cat /dev/random` and it gives that message a lot, but doesn't actually crash Feb 02 00:14:31 Oh... yes it did. Feb 02 00:15:12 what code path did we break Feb 02 00:30:44 This is two strace's: the first is where the bug is not triggered. The second is. See any differences? https://paste.ubuntu.com/26503159/ Feb 02 00:48:58 Wait Feb 02 00:49:07 I didn't edit the kernel config Feb 02 00:49:42 But... Feb 02 00:49:44 :-P Feb 02 00:49:58 Why do I do this to myself Feb 02 00:54:57 Well I'm stuck in town for now... @bhushanshah you checked out halium-boot yet? :P Feb 02 00:55:27 I did read on issue yes Feb 02 00:55:48