**** BEGIN LOGGING AT Fri Feb 02 03:00:06 2018 Feb 02 10:46:43 @UniversalSuperBox there is any progress in ut-halium-compat ? Feb 02 11:56:32 @Walid, No. And there won't be. Feb 02 11:56:54 Unless it's in a different direction. Halium-boot is its replacement. Feb 02 11:57:12 Along with some other fixes that must come later Feb 02 12:10:12 aslampr07 was added by: aslampr07 Feb 02 14:28:30 can somebody have a look at these errors while building ubports-boot Feb 02 14:28:34 https://paste.ubuntu.com/26505937/ Feb 02 14:48:01 (Photo, 480x800) https://irc.ubports.com/wCPvRHBB/file_4005.jpg Feb 02 14:48:12 @NSA_AMERICA Feb 02 14:48:35 @maharudra108, Kernel version? Feb 02 14:48:46 3.10.108 Feb 02 14:49:06 i hate kuid_t error Feb 02 14:49:12 [any curse word] Feb 02 14:49:17 I hate 3.10 Feb 02 14:49:28 @Walid, How to fix? Feb 02 14:49:34 @maharudra108, do you have USER_NS enabled? Feb 02 14:49:38 @NSA_AMERICA, 3.10 is lub Feb 02 14:49:49 @NotKit, Don't know? Feb 02 14:50:02 well, check your kernel config then? Feb 02 14:50:16 https://github.com/usb-bullhead-ubuntu-touch/kernel_msm/commits/android-msm-bullhead-3.10-marshmallow-dr1.6-ut check out Dalton's commits Feb 02 14:50:17 @NotKit, Defconfig? Feb 02 14:50:39 out/device_name/obj/KERNEL_OBJ/.config Feb 02 14:50:41 @NSA_AMERICA, @maharudra108 Feb 02 14:51:07 @NSA_AMERICA, Okay bro Feb 02 14:51:16 @NotKit, Lemme check Feb 02 14:52:10 @maharudra108, I think the following function will help you: … static inline uid_t __kuid_val(kuid_t uid) … { … return uid.val; … } … You can find it in include/linux/uidgid.h Feb 02 14:52:34 but this not good solution Feb 02 14:53:38 Okay Walid Feb 02 14:53:48 @maharudra108, Disable USER_NS Feb 02 14:53:58 That's the right solution Feb 02 14:54:38 @NotKit, Well there is user_qs not NS nd not set to anything Feb 02 14:55:06 @maharudra108, Sorry Feb 02 14:55:14 @maharudra108, Pretty sure you have it enabled Feb 02 14:55:53 Got it it is assigned with y Feb 02 14:56:05 It's called "enabled" Feb 02 14:56:17 You're to unset it Feb 02 14:56:26 Okay done Feb 02 14:56:35 @ilyaishere, lol Feb 02 14:57:17 @NotKit, I changed here @NotKit Feb 02 14:57:56 you need to disable it in defconfig then Feb 02 14:57:57 or it will be overwritten Feb 02 14:58:29 @maharudra108, have you read the docs Feb 02 14:58:38 @vanyasem, Yes Feb 02 14:58:53 @NotKit, But why this cause the issue? Feb 02 14:59:08 what exactly? Feb 02 15:00:29 the source of most of issues during kernel compilation is that kernel vendors don't test if their kernel builds with all the options possible Feb 02 15:00:52 Ohh Feb 02 15:01:31 what is the work of USER_NS enable i mean what it does? Feb 02 15:02:20 user namespaces support for LXC if enabled Feb 02 15:02:31 not needed for Halium as LXC runs with root permissions Feb 02 15:03:22 Okay so that's why we also don't need supersu flag on device tree Feb 02 15:04:28 SuperSu is completely unrelated to Halium Feb 02 15:04:53 @NotKit, Ok i meant root permission Feb 02 15:13:49 https://paste.ubuntu.com/26506132/ Feb 02 15:14:14 @maharudra108, @NotKit Feb 02 16:53:01 hi :) Feb 02 16:53:16 helo Feb 02 16:53:30 :) Feb 02 16:53:35 :) Feb 02 16:53:58 i have one question about GPS, what is your location provider? this? https://code.launchpad.net/ubuntu/+source/location-service Feb 02 16:54:33 krnlyng: umm I think UBports people are using agps Feb 02 16:55:49 @UniversalSuperBox @mariogrip: any comments? ^^^ Feb 02 16:55:50 bshah, ok :) do you have a link to the sources somewhere? Feb 02 16:56:09 let me see if I can dig something out Feb 02 16:56:19 thanks :) Feb 02 16:56:41 okay I was worng Feb 02 16:56:48 they are using geoclue Feb 02 16:57:00 https://github.com/ubports/location-service and https://github.com/ubports/ubuntu-location-provider-geoclue2 is what I could find Feb 02 16:58:53 bshah, ok thanks :) Feb 02 16:58:58 bshah, one more question :) Feb 02 16:59:05 sure Feb 02 16:59:11 bshah, ubuntu/hardware/gps.h <- where can i find this? Feb 02 16:59:58 good question Feb 02 17:00:22 or basically, i would like to see the implementation of: u_hardware_gps_inject_location Feb 02 17:01:13 https://github.com/ubports/platform-api/blob/f6d97d11943e44195b70a508f548b09a016be56d/src/ubuntu/application/touch/hybris/ubuntu_platform_hardware_api.cpp I found this Feb 02 17:01:21 so it must be somewhere around here Feb 02 17:02:18 but really idk Feb 02 17:04:52 ok :) Feb 02 17:05:18 the reason i am asking all this is because i fear you're affected by the same gps bug as we were :) Feb 02 17:05:43 and from the looks of platform-api repository it seems that you are :) Feb 02 17:05:51 link to bug? Feb 02 17:06:23 yep 1 sec Feb 02 17:06:56 bshah, https://bugs.merproject.org/show_bug.cgi?id=1871 Feb 02 17:07:19 bshah, in our case the solution was to add a header patch Feb 02 17:07:49 bshah, in your case (if i understand these repos correctly) it would be to use IMPLEMENT_VOID_SF_FUNCTION2 instead of IMPLEMENT_VOID_FUNCTION2 for inject_location :) Feb 02 17:08:08 @mariogrip: ^^^^ Feb 02 17:11:56 on the other hand. i've found places where it's correct and places where it's incorrect. just a suggestion: double check :) Feb 02 17:12:14 just wanted to let you know about that since it helps us and might help you :) Feb 02 17:12:45 Okay, thanks Feb 02 17:15:45 no i think it's incorrect in all cases :), hard to tell. but in case someone who does gps arrives ping me and lets go through the problematic lines of code :) Feb 02 17:16:47 hard to tell because i am looking at different repositories which seem to be unrelated or i am looking at the wrong branches :) Feb 02 17:17:03 even though they depend on each other :) Feb 02 17:29:23 @NSA_AMERICA, . Feb 02 17:56:23 Guys, i've got a problem... https://paste.ubuntu.com/26506861/ Feb 02 18:10:44 bshah, found the place Feb 02 18:10:46 bshah, https://github.com/ubports/android-headers/blob/xenial-7.1-caf/hardware/gps.h#L817 Feb 02 18:10:59 bshah, this needs to be patched Feb 02 18:12:13 (not the only function that suffers from this issue as well) Feb 02 18:12:54 but the second function that suffers from this is not as problematic since it's most likely not used Feb 02 18:13:06 bshah, what i am more concerned about is https://github.com/ubports/android-headers/blob/xenial-7.1-caf/hardware/audio.h#L304 Feb 02 18:13:16 bshah, are you using hardware/audio.h anywhere? Feb 02 18:13:38 bshah, if that is used then it also needs to be patched (there are more functions like this as well) Feb 02 19:31:05 @NotKit by running … breakfast [codename] … what to type inplace 'codename'? Feb 02 19:32:33 @Progromizd, Your device Feb 02 19:33:35 my device is dooge_x5pro, gues just type x5pro there? Feb 02 19:34:54 ahh, found. Feb 02 19:43:51 (Photo, 1280x733) https://irc.ubports.com/gEc8Q6JS/file_4008.jpg How to fix it? Feb 02 19:44:44 `breakfast android_device_dogee_x5pro` is wrong. Use only `breakfast_x5pro` Feb 02 19:50:55 (Document) https://irc.ubports.com/cL9EOCSm/file_4010.png Feb 02 19:52:07 is this a cm-14.1 device tree? Feb 02 19:52:28 I think this repo has only been used in < 13.0 Feb 02 19:54:55 @JBBgameich , my .repo/manifest contains: … Feb 02 19:57:47 @JBBgameich , do I need to change cm-14.1 to cm-13.0 and repeat ./setup my device again? Feb 02 19:58:52 No. But I wonder why you even have 4 remotes Feb 02 19:59:28 you need @JBBgameich and this is my ./devices/manifests/dooge_x5pro.xml: … Feb 02 20:02:45 i'm not sure about correction of linking these 2 files Feb 02 20:02:46 you only need one remote ... just use the hal remote and add "revision="cm-14.1" or "revision="ANdroid7.1.1" to the tags Feb 02 20:04:17 @JBBgameich ,do i need to run ./setup after this change again? Feb 02 20:04:31 Yes. This command copes your manifest to .repo Feb 02 20:13:50 @JBBgameich looks like this config is wrong too, since produced tha same resut: … Feb 02 20:15:01 https://bpaste.net/show/69f7a5e495cb - any obvious mistakes with how layer_config is handled? Feb 02 20:15:44 seems like wrong revision in my case Feb 02 20:19:29 @Progromizd, 😂🤦‍♂ Feb 02 20:21:13 … - single combination, which not produce any errors during ./setup Feb 02 20:24:23 looks better Feb 02 20:30:34 @JBBgameich … Repository for x5pro not found in the LineageOS Github repository list. Feb 02 20:31:02 That's ok. It's not an "official" LineagOS device Feb 02 20:31:03 as an output from breakfast x5pro Feb 02 20:31:19 it's still the gps file missing, try adding the android_device_common repo Feb 02 20:33:00 @JBBgameich inside project tags? Feb 02 20:33:11 as new line Feb 02 20:33:18 add a new projet to your manifest, yes Feb 02 20:36:04 @JBBgameich I have no idea what ot type in Path and Remote Feb 02 20:36:23 path="device/common" remote="los" Feb 02 20:36:55 @JBBgameich Name = doesn't make, may be any, yes? Feb 02 20:37:15 name is "android_device_common" Feb 02 20:38:32 @JBBgameich, ok. without revision? Feb 02 20:39:01 the latest available, I guess it's "staging/cm-14.0" Feb 02 20:42:30 (Photo, 665x563) https://irc.ubports.com/JctKRGbW/file_4012.jpg is it normal output? Feb 02 20:42:37 @JBBgameich Feb 02 20:42:59 @Progromizd, Yes **** ENDING LOGGING AT Sat Feb 03 03:00:01 2018