**** BEGIN LOGGING AT Wed Nov 14 03:00:00 2018
Nov 14 11:22:52 <ubptgbot> srmane4444 was added by: srmane4444
Nov 14 11:35:45 <ubptgbot> <srmane4444> Hi all, I'm new to porting, confused what to specify in the device manifest? Looked here https://github.com/LineageOS/android_device_xiaomi_whyred … https://github.com/Halium/halium-devices/tree/halium-7.1/manifests … and the manifestos are different, the consoles are not everywhere. … Just signed up for Github, and I don't have
Nov 14 11:35:45 <ubptgbot> a single repo. How not to download repo, not to place repo on your page, but just to indicate in the manifest? Stuck on remotes: Lineage or AOSP, hal or them. I do not know what to choose. I port on Xiaomi Redmi Note 5 (whyred). … Here is what I was able to fill: …   <? xml version = "1.0" encoding = "UTF-8"?> … <manifest> …       <project path = "
Nov 14 11:35:45 <ubptgbot> device / xiaomi / whyred" name = "android_kernel_xiaomi_sdm660" remote = "?" /> … </ manifest>
Nov 14 11:36:36 <ubptgbot> <srmane4444> *Consoles > Remotes
Nov 14 11:40:26 <ubptgbot> <minlexx> @srmane4444, First thing to see is that https://github.com/LineageOS/android_device_xiaomi_whyred does not contain android 7.1 (lineage-14.1) branch so that probably means it cannot be used for halium
Nov 14 11:40:55 <ubptgbot> <minlexx> @srmane4444, [Edit] First thing to see is that https://github.com/LineageOS/android_device_xiaomi_whyred does not contain android 7.1 (lineage-14.1) branch so that probably means it cannot be used for halium (yet)
Nov 14 16:41:13 <ubptgbot> <dohniks> Is anybody else annoyed by the five different ways how to check and fix the kernel config?
Nov 14 16:41:45 <ubptgbot> <dohniks> We clearly need a sixth way to do it: https://github.com/doniks/halium_kernel_config_fragments
Nov 14 16:42:18 <ubptgbot> <NotKit> the "proper" one is to use menuconfig/xconfig and then regenerate defconfig
Nov 14 16:42:31 <ubptgbot> <UniversalSuperBox> @dohniks, (☞ﾟヮﾟ)☞
Nov 14 16:43:22 <ubptgbot> <bhushanshah> @dohniks, Hero we deserve.
Nov 14 16:58:05 <ubptgbot> <dohniks> @NotKit, I think many android kernel configs are past the point where they survive a menuconfig pass
Nov 14 16:59:04 <ubptgbot> <NotKit> hm, generally they do if you edit config generated from defconfig
Nov 14 17:01:19 <ubptgbot> <dohniks> Ok, I admit my sample size is one: I used menuconfig once and it came out a mess, so I started over and never looked back
Nov 14 17:01:42 <ubptgbot> <dohniks> [Edit] Ok, I admit my sample size is: one. I used menuconfig once and it came out a mess, so I started over and never looked back
Nov 14 19:02:58 <ubptgbot> <Flohack> Anyone online with an idea about NV items and why they are not loaded on boot?
Nov 14 19:03:20 <ubptgbot> <UniversalSuperBox> What?
Nov 14 19:03:45 <ubptgbot> <Flohack> In MSM chipsets there are certain entries from NVRAM which need to be loaded into hardware, like WiFi MAC addy
Nov 14 19:04:00 <ubptgbot> <Flohack> On the OPO this is not happening. All OPOs out there have the same invalid MAC addy
Nov 14 19:04:04 <ubptgbot> <Flohack> I finally want to fix that
**** ENDING LOGGING AT Thu Nov 15 03:00:00 2018