**** BEGIN LOGGING AT Thu Mar 28 02:59:57 2019 Mar 28 07:52:03 RiderExMachina was added by: RiderExMachina Mar 28 07:53:40 Can someone please point me in a direction to get the proprietary blobs for the Xiaomi Tissot? Mar 28 07:54:31 Besides TheMuppets GitHub, as there doesn't seem to be what I need there Mar 28 08:08:43 @RiderExMachina, Install stock rom with android 7.1 and twrp recovery and then use the `extract-files.sh` in your device tree Mar 28 08:09:45 Maybe that's what I'm doing wrong. I have the Stock Android One ROM installed and that's what I extracted Mar 28 08:25:54 It extracts only the files listed in propietary-files if you need more you can add them there Mar 28 08:33:43 Well, the error I'm getting is "[file] needed by [output] missing with no rule to make it" Mar 28 08:34:20 I just installed Android 7 and ran the extract-files.sh script, it still happens. Mar 28 08:35:24 what device tree are you using, i see lineageos does not have a tree for nougat Mar 28 08:36:19 Los, should I change over to cm? Mar 28 08:37:24 In the build information it says that it's LineageOS 14.1 Unofficial Mar 28 08:37:27 What SoC does it have Mar 28 08:37:36 @RiderExMachina, so you won't find it on lineageos github Mar 28 08:38:20 RiderExMachina https://github.com/TheMuppets/proprietary_vendor_xiaomi/tree/lineage-15.1 Mar 28 08:38:54 @K31j0, They don't have the files I'm missing Mar 28 08:39:33 Good luck then Mar 28 08:39:45 You didn't paste the exact error Mar 28 08:40:54 I'm wondering if changing device tree would fix it Mar 28 08:46:24 It seems to be everything in the `bin` folder Mar 28 08:47:06 you need ro find nougat tree and blobs Mar 28 08:47:14 [Edit] you need to find nougat tree and blobs Mar 28 08:48:00 and kernel ofc Mar 28 08:48:40 Is there a way to extract them from the stock images? Mar 28 08:50:08 blobs, yes. but you need a nougat proprietary-files.txt in a nougat device tree Mar 28 08:50:40 That might be impossible Mar 28 14:45:53 Em0lution was added by: Em0lution Mar 28 14:48:09 I'm stuck... in build phase of the port of google taimen when i get to breakfast combo it ends with "do you have the right product manifest?" HELP! Mar 28 15:10:31 That means so etching is missing from your manifest Mar 28 15:11:12 Double check the dependency file and check to see if there's any -common dependecies Mar 28 16:23:23 Guys, sooo, im trying to port halium for the motog5s (montana). But when i try running "./halium/devices/setup motorola_montana" it gives "The given device is not supported". I tried to sync my manifest in 'local_manifests' but it still gives ou this error Mar 28 16:23:42 My manifest is https://pastebin.com/QnxjXMxw Mar 28 16:24:25 any one have ported it for j7 nxt/core/neo #SM-J701X Mar 28 16:24:44 [Edit] any one have ported it for j7 nxt/core/neo #J701X Mar 28 16:28:03 I have issues with booting on the Galaxy S6 (zerofltexx). My kernel was booting to the point where I was able telnet into it. The diagnosis file there told me to enable CONFIG_IKCONFIG. Now I have bootloops. Here are a log I was able to extract and my current kernel configuration: https://filebin.net/p6qcix7st4hcy9x4 Mar 28 16:28:31 Has anyone an idea what is going on? Or can hint me where I may be able to find the issue? Mar 28 16:35:58 @paktosan ,try setting defconfig according to warnings? may work Mar 28 16:37:12 @austenite ,what warnings exactly do you mean? Mar 28 16:38:17 @paktosan when mer-verify-kernel-config is used Mar 28 16:40:47 https://filebin.net/p6qcix7st4hcy9x4/kernel-check-warnings.txt?t=x4f9nsik These are all hints, I am getting. I would only consider the first one, but I was unable to find out, if my device even uses the watchdog Mar 28 16:41:44 I have ignored the other 3 warnings, since the kernel version I am building is 3.10.xx Mar 28 16:46:01 @austenite: Should I enable them anyway? Mar 28 16:46:44 @paktosan i dont know about it, for my device, display didnt work untill i had an optional config enabled.. Mar 28 16:48:38 @paktosan use pastebin or some other text service Mar 28 16:49:39 Oh? I liked Filebin for being able to have a collection of files. Mar 28 16:51:57 https://hastebin.com/haqewatoba.txt Is this better for you, @austenite? Mar 28 16:58:20 @SomeRandom_Person, Why do you have two sources for the same repo? And the other dependencies section shouldn't be needed, if you get errors with syncing without them then leave them in there Mar 28 16:58:45 ok Mar 28 16:58:56 im gonna try again then Mar 28 16:59:39 Ok, should be able to remove one of those kernel repos as well Mar 28 16:59:51 ok then Mar 28 17:25:31 just out of curiosity Mar 28 17:26:05 for example if i run './halium/devices/setup DEVICE' what should i put in device Mar 28 17:27:43 I believe if you do what the documentation says it should work fine, the error you were getting is usually due to a manifest issue Mar 28 17:27:51 strange Mar 28 17:28:37 Well the manifest is where most people (myself included) usually have the most issues when getting started Mar 28 17:28:44 Yeah Mar 28 17:28:52 I noticed Mar 28 17:28:52 Still Mar 28 17:29:15 Even doing your modifications it still pops ou this error Mar 28 17:29:26 First time I tried doing my device I figured out I had to add the common dependencies as well Mar 28 17:29:48 oh Mar 28 17:29:58 that might be the case? Mar 28 17:30:32 https://pastebin.com/DcU8KABn Mar 28 17:31:42 If that's thema ifest you just tired then uncomment the kernel otherwise it won't work Mar 28 17:34:37 Might need the qcom_common, but the device settings should be ok to remove Mar 28 17:34:46 ok them Mar 28 17:38:25 Might have to use android_device_motorola_qcom-common but I doubt that is needed based on the dependencies file Mar 28 17:38:49 really Mar 28 17:45:27 Yeah, based on the dependencies file you shouldn't need to specify the motorola_qcom-common over just qcom_common Mar 28 18:07:14 Tygerpro im new to this not sure i understand what you mean by etching in my manifest... Mar 28 18:08:34 I prob meant something, my phone doesn't like my thumbs Mar 28 18:09:26 Yeah I meant to say "something in your manifest" Mar 28 18:10:21 oh haha lol Mar 28 18:21:36 wrong channel.. redirecting here Mar 28 18:21:36 Fwd from fredldotme: I'm again taking a look at audio on the Xperia X now. so loading pa-modules-android-24 (with the proper touch config) works, but the indicator is a lie. paplay doesn't output any sound. looks like the android-side hw module is loaded properly. Mar 28 18:21:36 Fwd from fredldotme: I also have miniafservice running in the android container. time to remove it? Mar 28 18:43:48 ummmm Mar 28 18:44:04 Does any device manifest work by default Mar 28 18:44:58 because i cant use any use setup.sh in any manifest. Otherwise it just gives de error 'This device is not supported' Mar 28 18:45:13 Its that normal? Mar 28 18:45:43 `setup.sh` only works for files that are already inside `halium/halium-devices` Mar 28 18:45:51 ohhhh Mar 28 18:46:21 thanks Mar 28 19:20:01 ExploShot was added by: ExploShot Mar 28 19:20:28 Hi :) Mar 28 19:29:04 (Sticker, 512x512) https://irc.ubports.com/gCf6bpov.webp **** ENDING LOGGING AT Fri Mar 29 02:59:57 2019