**** BEGIN LOGGING AT Wed Jan 20 02:59:57 2021 Jan 20 03:04:48 @NotKit [next problem is usually having Java dependencies as PRODUCT_PACKAGES in device t …], That's probably the problem. The Java dependencies would be files that end in .jar, .java, or .class in mydevice-vendor.mk, correct? Jan 20 03:15:59 @dopamine404 [had that in my vendor tree for the msm8916 chip], Hi you successfully built for msm8916? Jan 20 03:23:12 @NotKit [next problem is usually having Java dependencies as PRODUCT_PACKAGES in device t …], It does appear that was the solution. Thank you very much for your help! :) Jan 20 04:08:42 @Daniel K [Hi you successfully built for msm8916?], yup Jan 20 04:10:12 @dopamine404 [yup], That's great. What phone was it? Jan 20 04:25:26 Samsung J5 2016 Jan 20 04:27:57 Quick question: when flashing halium-boot.img via TWRP it asks which partition to put flash it too (boot, system image, vendor image, install recovery ramdisk). I assume I select the boot option, but I don't want to break anything so I'm just checking Jan 20 04:28:57 did you make a nandroid backup? Jan 20 04:29:34 I have not Jan 20 04:29:41 do so Jan 20 04:29:51 you'll need it :D Jan 20 04:33:01 Cool Jan 20 04:33:25 @Daniel K [Cool], Why were you asking :p Jan 20 04:33:56 Moto G3 2015 msm8916 osprey Jan 20 04:34:03 ah Jan 20 04:34:07 good luck mate Jan 20 04:34:10 It has given me grief Jan 20 04:34:34 LMFAO Jan 20 04:34:39 welcome to the club pal Jan 20 04:34:48 Yes yes haha Jan 20 04:35:18 Anything worth sharing that you had to change? Jan 20 04:35:18 Which part are you stuck at? Jan 20 04:35:29 DTC scripts Jan 20 04:35:35 Some kernel configuration Jan 20 04:35:36 [Edit] Some kernel configurations Jan 20 04:35:51 And some vendor tree adjustments Jan 20 04:35:52 No graphics. Jan 20 04:35:57 yikes. Jan 20 04:36:05 jesus. Jan 20 04:36:11 does it boot? Jan 20 04:36:30 Let me jump on my computer so I can type Jan 20 04:36:35 alright Jan 20 04:40:30 Ok, so I did a build 6 months ago, it booted. Was able to ssh in, was able to activate wifi. Jan 20 04:40:45 alright Jan 20 04:40:56 which rootfs were you using? Jan 20 04:41:06 I did another build last week, with a fresh mind... now wifi is missing. everything else was the same. Jan 20 04:41:33 Good question, I used an older rootfs that I found on site Jan 20 04:41:42 halium rootfs? Jan 20 04:41:46 or something else? Jan 20 04:42:03 let me show you the link just a sec. Jan 20 04:42:14 alright Jan 20 04:43:50 Let me just not the build I did last week used the current : ubports-touch.rootfs-xenial-armhf.tar.gz Jan 20 04:44:02 ah you use the ubports one Jan 20 04:44:11 you are using halium-boot? Jan 20 04:44:17 i need to see where the older one is Jan 20 04:44:19 or are you using hybris-boot Jan 20 04:44:24 Halium boot Jan 20 04:44:32 @Daniel K [i need to see where the older one is], ah it shouldn't be much of an issue Jan 20 04:44:38 @Daniel K [Halium boot], hmm Jan 20 04:44:41 never used hybris Jan 20 04:44:49 @Daniel K [never used hybris], alrigh Jan 20 04:45:15 did you setup udev rules? Jan 20 04:46:54 I did not Jan 20 04:47:03 you should. Jan 20 04:47:15 what was the devices codename? Jan 20 04:47:42 osprey Jan 20 04:48:15 sudo mount -o remount,rw / Jan 20 04:48:22 sudo -i Jan 20 04:49:05 cat /var/lib/lxc/android/rootfs/ueventd*.rc|grep ^/dev|sed -e 's/^\/dev\///'|awk '{printf "ACTION==\"add\", KERNEL==\"%s\", OWNER=\"%s\", GROUP=\"%s\", MODE=\"%s\"\n",$1,$3,$4,$2}' | sed -e 's/\r//' >/usr/lib/lxc-android-config/70-[codename].rules Jan 20 04:49:16 and change [codename] to osprey Jan 20 04:49:29 Sorry, yes I did. Each time Jan 20 04:49:33 ah Jan 20 04:49:56 sudo lxc-info -n android Jan 20 04:50:03 What was your linage base? Jan 20 04:50:06 is the android container running? Jan 20 04:50:09 @Daniel K [What was your linage base?], 14.1 Jan 20 04:50:13 yes it is running Jan 20 04:50:20 ok, same Jan 20 04:50:30 can you gist the output Jan 20 04:52:59 yes just a sec Jan 20 04:53:04 alright Jan 20 05:02:41 is the output instant? Jan 20 05:02:47 yeah Jan 20 05:03:05 I think your lxc container might not be functioning correctly Jan 20 05:03:07 opps sudo Jan 20 05:03:10 because mine wasn't either Jan 20 05:03:27 @Daniel K [opps sudo], don't think that's necessary but go ahead Jan 20 05:04:20 yep output is a loop of text about audiodaemon Jan 20 05:04:35 thats weird Jan 20 05:04:43 This: Jan 20 05:04:46 01-20 03:32:03.871 61 195 V AudioDaemon: bool android::AudioDaemon::getStateFDs(std::vector > &): 0 sound cards detected … 01-20 03:32:03.871 61 195 E AudioDaemon: Sleeping for 100 ms Jan 20 05:04:51 Never ending... Jan 20 05:04:57 lmfao. Jan 20 05:05:17 not really sure how you could fix that Jan 20 05:05:35 the android container is definitely stuck tho Jan 20 05:08:03 I might have to start from scratch again. Jan 20 05:08:19 I honestly feel it is the only way and I learn more each time. Jan 20 05:08:20 you'll probably get the same results sadly Jan 20 05:08:32 @Daniel K [I honestly feel it is the only way and I learn more each time.], oh yeah thats definitely true Jan 20 05:08:54 but you were able to boot it which is a pretty good sign in itself Jan 20 05:09:05 Quick question, how did you go getting the proprietary files? no problems? Jan 20 05:09:22 you mean vendors? Jan 20 05:09:39 most of them were present in my vendor trees Jan 20 05:09:39 Yes Jan 20 05:10:16 and the ones missing were due to my device being slightly different from j5xlte (mine is j5xnlte) Jan 20 05:10:31 so I just removed the references to missing files Jan 20 05:10:33 Some files were missing from my vendors tree for 14.1, someone one here helped me and found that they were deleted for what ever reason Jan 20 05:10:47 huh that's interesting Jan 20 05:11:09 they were in the git history fotunately Jan 20 05:11:16 fortunately* Jan 20 05:11:21 thats lucky :D Jan 20 05:11:39 you might wanna search google for this error btw Jan 20 05:11:46 so you had touch working? Jan 20 05:11:51 yup Jan 20 05:12:05 yes, I'll have to look it up if it happens again. Jan 20 05:12:15 GSM/LTE? Jan 20 05:12:16 except camera lights vibrator sim and bluetooth Jan 20 05:12:27 @Daniel K [GSM/LTE?], the interface showed up Jan 20 05:12:29 Wow, good job. Jan 20 05:12:42 thank you :p Jan 20 05:12:50 @dopamine404 [the interface showed up], but didn't really work Jan 20 05:13:27 Still that is something Jan 20 05:13:42 @dopamine404 [you might wanna search google for this error btw], pretty sure some android devs encountered it too Jan 20 05:13:52 @Daniel K [Still that is something], yeah Jan 20 05:14:01 I mean you getting ssh is something too Jan 20 05:16:13 https://forum.xda-developers.com/t/miui-v7-port-sound-card-not-detected.3379736/ Jan 20 05:16:18 check this out Jan 20 05:16:37 Do you know if there is a disadvantage if I use Halium 5.1? Jan 20 05:16:48 I am actually not sure :D Jan 20 05:16:57 I never used it Jan 20 05:17:36 it is another option for me to try. at some point. I dod this tonight I am going to be a zombie tomorrow Jan 20 05:17:41 Yvette was added by: Yvette Jan 20 05:17:41 do* Jan 20 05:17:56 lmfao Jan 20 05:18:01 good luck again Jan 20 05:18:20 @dopamine404 [https://forum.xda-developers.com/t/miui-v7-port-sound-card-not-detected.3379736/], this seems promising btw Jan 20 05:19:02 I would say first try to figure this out before trying to change halium versions Jan 20 05:21:45 ok good advice. Jan 20 05:22:26 Thank you for your help. Appreciate your time. Jan 20 05:22:27 you can ask for help here if you get stuck Jan 20 05:22:35 Ah no problem man :D Jan 20 05:22:37 Good luck Jan 20 05:22:45 I'll let you know. Jan 20 05:22:52 Alright Jan 20 05:36:22 奥智惠 was added by: 奥智惠 Jan 20 09:30:50 [In the Halium documentation 'Ge](https://github.com/lineageos)In the Halium documentation 'Get Halium Source' found [here](https://docs.halium.org/en/latest/porting/get-sources.html). … In the section "Adding your device-specific source" it says I should find the repositories for my device on LineageOS's GitHub organization … Jan 20 09:30:50 What can I do if my device is not listed there? Jan 20 09:31:42 you might search for your device on github Jan 20 09:32:00 and find the necessary sources for the build and write your own manifest Jan 20 09:33:37 @dopamine404 [you might search for your device on github], OK I'll give that a try. Thanks. Jan 20 09:33:55 No problem Jan 20 09:43:34 @dopamine404 [No problem], The device in question is a 'Samsung Galaxy Tab2 10.1' I have cyanogenmod installed on it. Can I use this to get the files I need? Jan 20 09:44:06 Use what exactly :D Jan 20 09:44:38 If you have cyanogenmod installed that means the sources you need for the device probably is on github Jan 20 09:44:42 search things like Jan 20 09:45:06 android_device_ followed by your devices codename Jan 20 09:50:05 @dopamine404 [Use what exactly :D], It says in the documentation that I need to find device-specific files. I have no idea what they are! Thanks for your help and time though. … It says this "Okay, so now you have the default manifest for Halium. This will enable you to download the basic Android sources used to build Halium, bu Jan 20 09:50:05 t you’ll need to find device-specific files. These enable the build system to make Android for your device." Jan 20 09:50:50 @SovereignFreeman [It says in the documentation that I need to find device-specific files. I have n …], Ahhh sorry :D Jan 20 09:51:28 device spesific would consist of the device tree vendor tree and the kernel Jan 20 09:51:56 they ,are as written, device spesific files used for the device hardware and etc. Jan 20 09:52:31 first of all you might wanna find a lineage os or cyanogenmod manifest file Jan 20 09:52:45 and modify it to suit your needs Jan 20 09:54:12 wait is your device's codename p5110? Jan 20 09:55:20 @dopamine404 [wait is your device's codename p5110?], I think it might be. It's the WIFI variant Jan 20 09:57:14 wait a sec Jan 20 09:58:41 https://github.com/Halium/projectmanagement/issues/238 Jan 20 09:58:47 there Jan 20 09:59:18 @mighty17[m] [fix*], helllo there Jan 20 09:59:50 @dopamine404 [there], Thank you very much 😁 Jan 20 09:59:57 no problem :D Jan 20 10:00:33 I believe that you guys are porting for the same device Jan 20 10:00:46 so I should note that he was having problems Jan 20 12:15:49 Khant_Nyar_Zaw was added by: Khant_Nyar_Zaw Jan 20 20:54:41 [Afte](https://docs.halium.org/en/latest/porting/get-sources.html#sync)After downloading the source tree as described in the [get Halium source](https://docs.halium.org/en/latest/porting/get-sources.html#initialize-and-download-source-tree) documentation. … There are several steps to do before the final task on that page which is Jan 20 20:54:41 to Sync the repositories by using the command … ./halium/devices/setup DEVICE … I see that in my downloaded '~/halium' directory that there is no 'devices' folder and no trace of a 'setup' file which I'm assuming is some script that performs the sync action. Is there another way to download the halium source tree other than using the commands?: … Jan 20 20:54:41 repo init -u https://github.com/Halium/android -b halium-5.1 --depth=1 … and … repo sync -c -j 16 Jan 20 21:39:24 @SovereignFreeman [After downloading the source tree as described in the get Halium source document …], Figured it out, the halium directory tree had not downloaded properly. After a couple of re-attempts it finally worked **** ENDING LOGGING AT Thu Jan 21 02:59:57 2021