**** BEGIN LOGGING AT Fri Mar 16 03:00:02 2018 Mar 16 04:05:02 @Qiangong2 interesting about sensors.. what happens without that Doze ? Mar 16 04:05:20 you mean test_sensors fails otherwise? Mar 16 04:32:20 bshah: Indeed interesting about sensors. I don't know what happens on other devices to be honest Mar 16 04:32:58 I was just looking into way to have the setup script automate some of the common actions, so we don't need to always fork everything and to make porting new devices easier :) Mar 16 04:37:39 Seems there are different variants of Doze out there, SamsungDoze, XiaomiDoze, ZteDoze, LenovoDoze, YuDoze, OneplusDoze, HammerheadDoze, KiwiDoze, ZenfoneDoze, LgDoze and regular Doze..... Mar 16 04:38:46 If the Doze package would be needed an alternative might be to comment out or delete the reference to the SettingsLib mk file. I've seen that done in one of the device repos in Halium as well Mar 16 04:39:17 And that could be automated with a regexp in the script ;) Mar 16 05:19:46 @bhushanshah when you do not build doze, for some reason the proximity sensor is no longer detected, which isn't a huge deal now, but later on when we get PM to a fully usable state, we will want it Mar 16 05:20:33 It may be the same issue with all the different versions of doze, or just with SamsungDoze Mar 16 05:21:21 And why exactly do we need SettingsLib removed? Mar 16 05:31:38 @Qiangong2, Because it is not used.. we're not including any Java library in the Android container.. Mar 16 05:32:57 I think now i understand why you think doze is needed.. that is when doze is not included proximity sensor to turn screen on-off doesn't work in Android, but that is different thing.. Mar 16 05:33:05 There are two bits Mar 16 05:33:32 Sensor library and doze controller (settings library) Mar 16 05:34:20 Sensors provides data and doze settings library reads that data and adjusts brightness or controls screen Mar 16 05:34:52 But in case of PM/UT/LuneOS there would be totally different thing controlling this stuff Mar 16 05:35:19 E.g powerdevil/powerd/mce Mar 16 05:35:26 So no, you don't need doze Mar 16 05:37:19 Again... Full speculation.. I don't own device which have doze Mar 16 05:41:48 bhushanshah: Which devices do you have yourself? Just curious :) Mar 16 05:45:30 @Herrie|Laptop, I've Nexus 5, 5X, and OnePlus 5 (which I don't use for development) Mar 16 05:59:19 bhushanshah: Ah OK Mar 16 06:07:23 bhushanshah: Seems that there's a Doze for Hammerhead in LOS CAF repo: https://github.com/LineageOS/android_device_lge_hammerheadcaf/tree/cm-14.1/doze Mar 16 06:40:36 @mariogrip Why this is still not merged :) https://github.com/ubports/android_hardware_qcom_audio/pull/1 Mar 16 07:04:53 @bhushanshah, Hammerhead *_* Mar 16 15:09:26 libmedia_compat_layer.so ? is it part of libhybris ? Mar 16 15:11:21 audio don't work, so i copied libmedia_compat_layer.so form FP2 system image , now audio work, Mar 16 18:41:13 libmedia_compat_layer its builded in ubport-5.1 in system/lib, so for xenial Ubuntu Touch the good way is to use ubport-5.1 to build system.img and use normal boot.img, Mar 16 19:01:45 Walid it's in libhybris/compat folder, just in case Mar 16 19:21:26 yes , i tried to build libhybris, but there is no libmedia_compat_layer.so file, i will see how it dose in ubports-5.1 Mar 16 19:29:28 @Walid, you tried to build it in Android build system? Mar 16 19:29:38 compat folder is for Android Mar 16 19:30:53 yes that what i have found it, compat folder must build in android source tree Mar 16 20:13:35 apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/telepathy-ofono" ???? Mar 16 23:04:11 garshol was added by: garshol Mar 16 23:26:36 Peppe was added by: Peppe Mar 16 23:27:28 Does it use 8 img system for the halium installation project sources? Mar 16 23:27:58 Because 7 old enough for mine standards Mar 16 23:29:14 @bhushanshah, I can help you with doze Mar 17 00:14:42 Hey, I have a question about my fstab file: why does it have /cache and /data twice?? Mar 17 00:24:11 What's different between the two Mar 17 00:25:58 one is f2fs and one is ext4 Mar 17 00:26:12 That's why, then Mar 17 00:26:38 delete the f2fs entry Mar 17 00:30:38 is the f2fs left over from an old setup? Mar 17 01:10:40 No, it means it'll moumounted either Mar 17 01:47:21 do I need to set CONFIG_AUDIT to y in my kernel config? Mar 17 02:02:02 @Igor Dikiy, If your device needs CONFIG_AUDIT support in kernel, set SELINUX_BOOTPARAM=y. Then disable them via kernel cmdline: audit=0 selinux=0. You can also leave audit enabled, if you don't plan to use systemd's containers. ***This is straight from the kernel config checker Mar 17 02:05:13 thanks, if I do need to disable them via kernel cmdline, where do I do that? after my device boots? Mar 17 02:06:56 i disabled it in my boardconfig.mk file Mar 17 02:07:02 before building Mar 17 02:07:15 "kernel cmdline:" **** ENDING LOGGING AT Sat Mar 17 03:00:00 2018