**** BEGIN LOGGING AT Wed Feb 28 03:00:02 2018 Feb 28 07:57:10 kuailexs was added by: kuailexs Feb 28 08:05:44 Hey, I'm looking into porting ubports to my device Feb 28 08:07:00 However I'm using the mainline kernel so I'm not sure halium would work Feb 28 08:09:19 Would I be able to just skip out gallium? Feb 28 08:09:21 Halium Feb 28 08:19:47 you just need to boot a chroot then. you might need to build the boot image though Feb 28 08:41:57 @opendata, What you mean with mainline kernel? Feb 28 08:43:17 Non android kernel Feb 28 08:43:55 No android binary drivers are compatible with it, we use Linux drivers Feb 28 08:44:27 Which device is it? =) Feb 28 08:44:40 Xperia Z2 tablet Feb 28 08:45:33 opendata: Well when you use mainline kernel and no binary blobs are needed, you can skip libhybris ;) Feb 28 08:45:34 Hmm as Ivan says, its not that complicated at all, if you can see how the Halium initrd is crafted, you can use this ramdisk and the stuff to attach it to your kernel probably Feb 28 08:45:37 And Android in general ;) Feb 28 08:45:57 Yes but we are talking now about booting, and for a Halium-compatible bott he needs to use our initrd system Feb 28 08:46:07 And probably also configure the kernel options Feb 28 08:46:28 Its just you cannot use halium-boot Android target, but you can probably rewrite it into a packaing script Feb 28 08:47:40 Right Feb 28 08:47:57 Do I need a halium compatible boot for ubports? Feb 28 08:52:20 @Flohack Feb 28 08:52:40 I *think* you can get around with standard ubuntu rootfs Feb 28 08:53:38 Is ubports even a good fit for a tablet Feb 28 08:53:47 it is yes Feb 28 08:58:30 How can I build a rootfs Feb 28 08:58:49 As I need to add in WiFi config files and freedreno firmware Feb 28 08:59:32 possibly question for @mariogrip / @UniversalSuperBox or maybe #ubports on freenode Feb 28 09:11:22 @UniversalSuperBox , @JBBgameich: I've opened a discussion here https://github.com/Halium/projectmanagement/issues/61 as a result of my analysis for integration halium-boot in LuneOS Feb 28 09:11:35 integrating* Feb 28 09:15:36 I'm experimenting a bit with ostree and wonder if this could be used as a means to multiboot and or atomic updates, at least among halium based systems. Feb 28 09:20:57 Ha anyone else done some work in this area? Feb 28 09:42:29 last i checked ostree wants uboot Feb 28 09:42:39 which isnt what android devices use Feb 28 11:12:10 @Tofe, The question when android images should be mounted was always a little bit complicated. Maybe @UniversalSuperBox can explain why he mounts them in the initrd. Feb 28 11:13:09 I know answer for it , but bit busy to write it up right now, will follow up in ticket if @UniversalSuperBox doesn't beat me to it Feb 28 11:16:10 Also, many of the things you want are currently the case with hybris-boot (like the udev rules thing) and it's not yet decided if they should be in the rootfs or device tree. From a packager perspective, I'd also like to have them in the rootfs, and as less modifications to the rootfs by the initrd as possible. There are still ma Feb 28 11:16:10 ny reasons to replace hybris-boot (like we need udev running before the rootfs) Feb 28 11:16:37 [Edit] Also, many of the things you want are currently the case with hybris-boot (like the udev rules thing) and it's not yet decided if they should be in the rootfs or device tree. From a packager perspective, I'd also like to have them in the rootfs, and as little modifications to the rootfs by the initrd as possible. There are Feb 28 11:16:37 still many reasons to replace hybris-boot (like we need udev running before the rootfs) Feb 28 11:47:23 @JBBgameich yes, the more you modify the rootfs, the less generic you are; and there is also an init system in the distribution, which can do things too. Having a "Halium" systemd service that finishes the job would be no problem to me, for instance. But I also understand there are things that need to be done as early as possible. Feb 28 12:34:10 @r0kk3tz No, ostree is independent of the bootloader. It is basically like git but for read-only root images. Feb 28 12:35:19 ZeroPointEnergy: but to do the useful things, like rolling back atomic updates, it needs features that uboot provides but fastboot doesnt Feb 28 12:38:13 What I'm thinking about is to implement this directly in the initrd. Feb 28 12:38:31 if you can make it work id love to hear about it Feb 28 12:41:32 make: *** No rule to make target '/home/kunal_bhat/halium/out/target/product/z3c/obj/SHARED_LIBRARIES/libta_intermediates/export_includes', needed by '/home/kunal_bhat/halium/out/target/product/z3c/obj/EXECUTABLES/macaddrsetup_intermediates/import_includes'. Stop. Feb 28 12:41:46 :/ Feb 28 12:41:51 Any ideas? Feb 28 12:53:11 do you have removed any .jar or .apk in /vendor/your/device/Android.mk Feb 28 12:54:39 No... Feb 28 12:55:27 I did remove Qualcomm location in device/vendor/device/device-vendor.mk Feb 28 12:55:41 Thats because it was giving errors Feb 28 12:56:18 it seems you need to add libta in the build/core/main.mk and/or local manifest Feb 28 12:56:28 in /vendor/youDevice/Android.mk remove all block of code where you see any .jar or .apk Feb 28 12:56:49 this is not error about the apk though Feb 28 12:57:53 Alright I will try both those things once I'm home :) Feb 28 12:57:57 Thank you Feb 28 13:47:14 Tofe, replied. 😁 Feb 28 13:55:55 UniversalSuperBox: yes, I saw that, thanks ! I'll take some time to read that :) Feb 28 14:01:23 UniversalSuperBox: I just learned UBPorts has a one-for-all-devices rootfs, I wasn't aware of that... It explains quite some stuff... Feb 28 14:02:17 doesn't ubports only support arm? Feb 28 14:02:25 or was it sailfish... ? Feb 28 14:04:59 Tofe: well not quite one, but more like two (one for CAF and other generic) Feb 28 14:05:00 but yes Feb 28 14:05:18 Tofe: same goes for the Plasma Mobile Feb 28 14:05:18 We only make ARM builds and a lot of the stack depends on Android being around Feb 28 14:05:35 (That was @KunalBhat) Feb 28 14:05:45 Tofe: and at some point I would love if LuneOS goes at same path btw ;) Feb 28 14:06:05 ahh Feb 28 14:06:33 @bshah... i can't find libta in any repo Feb 28 14:06:40 Tofe: Yes, one image to rule them all (and each device may provide its overlay to bind them) Feb 28 14:06:58 i think it's supposed to be using libtar Feb 28 14:07:00 @KunalBhat, Did you fix it? Feb 28 14:07:09 nope Feb 28 14:07:11 still working on it Feb 28 14:07:20 Can i help? Feb 28 14:07:29 sure Feb 28 14:07:30 *may Feb 28 14:07:36 😆 Feb 28 14:09:28 @KunalBhat, ```touch /home/kunal_bhat/halium/out/target/product/z3c/obj/SHARED_LIBRARIES/libta_intermediates/export_includes``` … try this :) Feb 28 14:09:41 That's a hack, but it will essentially work Feb 28 14:09:56 Check for what Makefile calls `libta`, try changing it to `libtar` Feb 28 14:10:14 @UniversalSuperBox, I was going to try that . Im looking for the makefile Feb 28 14:10:27 I have literally suggested this to many.. On sailfish and haliumm... Works everytime Feb 28 14:10:45 @abhishek_0, Sure, it builds... but at what cost Feb 28 14:10:46 Lol Feb 28 14:10:48 I have 3 different device trees that it calls from Feb 28 14:10:55 @abhishek_0, Can't touch 😆 Feb 28 14:11:00 most probably a spelling derp Feb 28 14:11:53 Tofe, you can find an example of the overlay that we use at UBports (of course it's in the wrong namespace) for the FP2: https://github.com/ubports/android_device_fairphone_fp2/blob/ae523d3c14e03a9d8a061c59889ae41869861116/FP2.mk#L157 Feb 28 14:12:23 ummm Feb 28 14:12:27 it's not libtar! Feb 28 14:12:31 libta is a thing Feb 28 14:12:35 oh sorry Feb 28 14:12:50 wow ok Feb 28 14:12:56 😆 Feb 28 14:12:58 oops Feb 28 14:13:16 I can't find it on halium or lineage repos :/ Feb 28 14:13:34 https://github.com/sonyxperiadev/macaddrsetup/blob/f8e1ced21df32887397f5e382262ea0781138ceb/macaddrsetup.c#L16 it is supposed to be binary blob it seems? Feb 28 14:14:33 https://github.com/sonyxperiadev/macaddrsetup/commit/dceef471f223dbea9d87fdbec98c5e05d961758d Feb 28 14:14:43 That's aosp Feb 28 14:14:51 here is the lineage mkfile Feb 28 14:15:51 nevermind Feb 28 14:15:52 yup Feb 28 14:15:54 same file Feb 28 14:16:05 :P Feb 28 14:16:38 I believe you need to backport the commit I showed you in your macaddrsetup repo I thinkk Feb 28 14:16:40 XD Feb 28 14:21:26 Alright Feb 28 14:21:29 I'll try Feb 28 14:24:28 Okay done Feb 28 14:24:39 Left it to buil Feb 28 14:34:31 bshah, UniversalSuperBox: ok, I see. On LuneOS we have a different way of doing things, mainly inherited from using OpenEmbedded: our recipes are splitted depending on the architecture dependency. So we have "all", "armv7", "hammerhead", "mako", "aarch64"... Feb 28 14:35:19 It can be seen clearly on the packages folders: http://build.webos-ports.org/luneos-testing/ipk/ Feb 28 14:37:22 Also we have machine-dependent recipes, for instance all that uses android-headers -- I wonder how you address that Feb 28 14:42:02 Then again on LuneOS you can also run without Android dependency. Feb 28 14:42:49 sure, for non-halium you can have totally seperate rootfs Feb 28 15:26:59 arg, I close the issue by mistake Feb 28 15:27:10 ok reopened, sorry for that. Feb 28 15:44:13 hi, I'm still having issues with libbtnv (https://dpaste.de/iJih) and additionaly with msm8998/mm-video-v4l2 where VQZip.h is missing. could someone please help? Feb 28 15:53:16 sorry, had issues with my network Feb 28 16:07:14 joonnnyyyy was added by: joonnnyyyy **** BEGIN LOGGING AT Wed Feb 28 16:16:28 2018 Feb 28 17:10:45 I got Halium to boot and give me ssh, however it doesn't seem to be starting the container, if I start it manually, the phone boots me out and won't let me back in, and the screen on the phone stays at the power on screen, any ideas on what to check from there? Feb 28 17:11:07 Remove *usb*.rc from init.rc in your device tree Feb 28 17:11:59 That will help halium start the nandroid container? Feb 28 17:13:03 Never (re)start android container manually.. unless you've manually disabled it Feb 28 17:13:46 @bhushanshah, OK, I'm new to Ubuntu touch, at least this side of it, what would you reccomend? Feb 28 17:14:18 Halium I'm very new to Feb 28 17:16:58 @Tygerpro Tygerpro, Just let it start automatically, instead of manually starting it with e.g lxc-start or upstart or systemd :) Feb 28 17:18:16 @bhushanshah, OK, do you have any tips on getting to that point cause so far its not doing it, left it alone for 2 hours and did nothing and there isn't really much of a guide with halium-boot atm Feb 28 17:21:17 ahm, how do you verify if container is not started? Feb 28 17:21:45 because the `systemctl status lxc@android` won't work on the ubports Feb 28 17:21:59 Lxc-info -nandroid iirc I have it written down on my desk at home Feb 28 17:22:14 Okay Feb 28 17:22:51 It says Android stopped when I enter that Feb 28 17:23:22 @UniversalSuperBox ^ something for ya to debug (since it is utouch) :P Feb 28 17:23:51 And a new device, he's the one that told me to do lxc-info Feb 28 17:24:28 Right.. can you paste dmesg somewherE? Feb 28 17:24:52 If I were in front of my PC I could, I'm on meal break at work ATM though Feb 28 17:25:31 When I checked it it was spammi g what looked like battery charging status messages Feb 28 17:25:32 okay no problem, take your time Feb 28 17:26:39 It had "time till full" and "time remaining" with rather large numbers (presumably hours in second or minute form) Feb 28 17:27:08 I wonder if your device is booting in charger mode somehow Feb 28 17:27:32 please check `/proc/cmdline` for `bootmode` option Feb 28 17:28:15 Its a galaxy note 4 if that helps, I obviously have it connected to computer and it seems to be charging whenever I connect to any USB cable, I will defibately check that Feb 28 17:28:46 Is there a way to change it if it is booting in charge mode? Feb 28 17:38:58 Boot with the power button rather than by plugging in the USB cable Feb 28 19:49:13 does anybody knows where VQZip.h should come from? my msm8998 supports it and the `Android.mk` for qcom_media enables it for msm8998 Feb 28 20:05:06 for my understanding #include "" means header is shipped in project while #include <> means system. VQZip.h should be shipped in qcom_media but it's not there. that sucks Feb 28 23:49:19 am I right that java_library.mk is missing in halium-7.1 build/core directory? Mar 01 00:29:33 @UniversalSuperBox, I usually boot with "adb reboot" or "/sbin/reboot" Mar 01 01:14:36 How would I exclude an apk from getting built from my device tree? I have removed it from proprietary-files.txt, but since my tree calls the vendor file, it keeps trying to make compile it Mar 01 01:55:56 Seems like the only solution is to comment it out in the local tree :( Mar 01 01:56:02 [Edit] Seems like the only solution is to comment it out in the local tree Mar 01 01:57:18 It will be in your vendor folder, be sure to comment out the whole section with #'s Mar 01 01:59:51 Actually, all you need to comment out is the package in the vendor makefile Mar 01 02:00:08 builds fine after that Mar 01 02:00:25 Well I had to do the whole section that mentions the apk otherwise it still errored out Mar 01 02:01:07 hmm, Maybe it's because I also deleted it from proprietary-files.txt Mar 01 02:01:24 Maybe *shrugs* Mar 01 02:03:19 I'm still trying to get halium-boot to start the nandroid container lol Mar 01 02:06:07 lol Mar 01 02:06:18 Good luck Mar 01 02:06:25 I'm still using hybris-boot Mar 01 02:07:06 I was using that, thinking I might switch back, never got it to successfully mount partitions though **** ENDING LOGGING AT Thu Mar 01 02:59:59 2018