| T42_ | <Pachof> Hello, a question, I am repairing the camera in a Port for Redmi Note 8, the native Sailfish OS camera does not work but in Waydroid the camera does work, what could be done? | 00:46 |
|---|---|---|
| rainemak | #startmeeting Sailfish OS, open source, collaboration -- 4th July 2024 | 07:00 |
| sailbot | Meeting started Thu Jul 4 07:00:02 2024 UTC. The chair is rainemak. Information about MeetBot at http://wiki.debian.org/MeetBot. | 07:00 |
| sailbot | Useful Commands: #action #agreed #help #info #idea #link #topic. | 07:00 |
| rainemak | #info Meeting information and agenda can be found here: | 07:00 |
| rainemak | #link https://forum.sailfishos.org/t/community-meeting-on-4th-july-2024/19089 | 07:00 |
| rainemak | I am the meeting's chairperson today, and will be doing my best to keep time and order. Please respect the timings and bee-hive. | 07:00 |
| rainemak | #topic Brief introduction (5 min). Please prefix your name/handle with #info | 07:00 |
| Crabster | morning rainemak , wrong channel :) | 07:01 |
| rainemak | #endmeeting | 07:01 |
| sailbot | Meeting ended Thu Jul 4 07:01:43 2024 UTC. | 07:01 |
| sailbot | Minutes: https://irclogs.sailfishos.org/meetings/sailfishos-porters/2024/sailfishos-porters.2024-07-04-07.00.html | 07:01 |
| sailbot | Minutes (text): https://irclogs.sailfishos.org/meetings/sailfishos-porters/2024/sailfishos-porters.2024-07-04-07.00.txt | 07:01 |
| sailbot | Log: https://irclogs.sailfishos.org/meetings/sailfishos-porters/2024/sailfishos-porters.2024-07-04-07.00.log.html | 07:01 |
| rainemak | Crabster, oops | 07:01 |
| T42_ | <b100dian> Yeah, something is happening with the telegram bridge, it bridges the #sailfishos meeting now too:) | 07:02 |
| rainemak | Nope, it was my fault | 07:02 |
| T42_ | <b100dian> Oh, it was indeed wrong channel:) | 07:02 |
| T42_ | <vilez0> @mal i executed repo sync again but the test folder (and other folders) didnt appear | 14:01 |
| T42_ | <vilez0> ` | 14:02 |
| T42_ | <vilez0> Fetching: 100% (1200/1200), done in 12m5.527s | 14:02 |
| T42_ | <vilez0> Checking out: 100% (1200/1200), done in 2m31.220s | 14:02 |
| T42_ | <vilez0> repo sync has finished successfully.` | 14:02 |
| mal | remove that one folder and sync again | 14:07 |
| T42_ | <vilez0> okay, solved now | 14:15 |
| T42_ | <vilez0> `[ 88% 516/585] including hybris/hybris-boot/Android.mk ... | 15:03 |
| T42_ | <vilez0> FAILED: | 15:03 |
| T42_ | <vilez0> hybris/hybris-boot/Android.mk:71: warning: ********************* /boot appears to live on /dev/block/bootdevice/by-name/boot | 15:03 |
| T42_ | <vilez0> hybris/hybris-boot/Android.mk:72: warning: ********************* /data appears to live on /dev/block/bootdevice/by-name/userdata | 15:03 |
| T42_ | <vilez0> In file included from hardware/synaptics/wlan/synadhd/Android.mk:1: | 15:03 |
| T42_ | <vilez0> hybris/hybris-boot/Android.mk:357: error: Multiple power_profile.xml files. | 15:03 |
| T42_ | <vilez0> 14:58:59 ckati failed with: exit status 1 | 15:03 |
| T42_ | <vilez0> | 15:03 |
| T42_ | <vilez0> #### failed to build some targets (14:37 (mm:ss)) ####` | 15:03 |
| T42_ | <vilez0> `$ find . -name "power_profile.xml" | 15:04 |
| T42_ | <vilez0> ./device/google/cuttlefish/shared/overlays/core/res/xml/power_profile.xml | 15:04 |
| T42_ | <vilez0> ./device/xiaomi/sweet_k6a/overlay/Frameworks/res/xml/power_profile.xml | 15:04 |
| T42_ | <vilez0> ./frameworks/base/core/res/res/xml/power_profile.xml | 15:04 |
| T42_ | <vilez0> ./frameworks/base/tools/powermodel/test-resource/power_profile.xml` | 15:04 |
| T42_ | <vilez0> so, which file should i delete? or what should i do? | 15:04 |
| mal | you can also manually hack the hybris/hybris-boot/Android.mk to disable that stuff | 15:15 |
| T42_ | <vilez0> okay | 15:16 |
| T42_ | <vilez0> `FAILED: build/make/core/main.mk:1312: warning: device/xiaomi/sweet_k6a/lineage_sweet_k6a.mk includes non-existent modules in PRODUCT_PACKAGES | 15:41 |
| T42_ | <vilez0> Offending entries: | 15:41 |
| T42_ | <vilez0> SimpleSettingsConfig | 15:41 |
| T42_ | <vilez0> libprotobuf-cpp-full-3.9.1-vendorcompat | 15:41 |
| T42_ | <vilez0> libprotobuf-cpp-lite-3.9.1-vendorcompat | 15:41 |
| T42_ | <vilez0> build/make/core/main.mk:1312: error: Build failed. | 15:41 |
| T42_ | <vilez0> 15:33:55 ckati failed with: exit status 1` | 15:41 |
| mal | and you have added all needed repos to local manifests? | 16:12 |
| T42_ | <vilez0> yes but for some reason repo didnt sync them properly | 17:05 |
| T42_ | <vilez0> `FAILED: ninja: 'libui_compat_layer', needed by 'hybris-hal', missing and no known rule to make it | 18:38 |
| T42_ | <vilez0> 18:24:27 ninja failed with: exit status 1 | 18:38 |
| T42_ | <vilez0> | 18:38 |
| T42_ | <vilez0> ` | 18:38 |
| T42_ | <vilez0> `#### failed to build some targets (15:56 (mm:ss)) ####` | 18:38 |
| mal | btw, did you apply patches correctly? | 18:47 |
| mal | and check other things in faq? | 18:47 |
| mal | https://github.com/mer-hybris/hadk-faq/blob/master/README.rst#hybris-16-0 that says how to clone the missing libhybris, and how to apply patches, also check the stuff in 17.1 part for selinux stuff and how to add the version to droid-configs spec | 18:50 |
| T42_ | <vilez0> @mal i didnt apply any patch, just following HADK from the website | 18:55 |
| mal | well then no wonder you have problems | 18:57 |
| mal | those patches change quite many things | 18:57 |
| T42_ | <vilez0> i applied them now | 18:57 |
| mal | also clone the libhybris | 18:57 |
| T42_ | <vilez0> i did it also | 18:58 |
| T42_ | <vilez0> `FAILED: //system/sepolicy:recovery_sepolicy.cil Building cil for recovery_sepolicy.cil [common] | 20:21 |
| T42_ | <vilez0> Outputs: out/soong/.intermediates/system/sepolicy/recovery_sepolicy.cil/android_common/recovery_sepolicy.cil | 20:21 |
| T42_ | <vilez0> Error: exited with code: 1 | 20:21 |
| T42_ | <vilez0> Command: out/host/linux-x86/bin/checkpolicy -C -M -c 30 -o out/soong/.intermediates/system/sepolicy/recovery_sepolicy.cil/android_common/recove` | 20:21 |
| T42_ | <vilez0> `ry_sepolicy.cil out/soong/.intermediates/system/sepolicy/recovery_sepolicy.conf/android_common/recovery_sepolicy.conf # hash of input list: a316674d1dc0868a105f79e687a4b6449e6a8801cfa3253b9c426787c1c40d09 | 20:21 |
| T42_ | <vilez0> Output: | 20:21 |
| T42_ | <vilez0> device/xiaomi/sweet_k6a/sepolicy/vendor/vendor_hal_citsensorservice_xiaomi_default.te:21:ERROR 'unknown type vendor_sensors_dbg_prop' at token ` | 20:21 |
| T42_ | <vilez0> `';' on line 94701: | 20:21 |
| T42_ | <vilez0> #line 21 | 20:21 |
| T42_ | <vilez0> allow vendor_hal_citsensorservice_xiaomi_default vendor_sensors_dbg_prop:file { getattr open read map }; | 20:21 |
| T42_ | <vilez0> checkpolicy: error(s) encountered while parsing configuration | 20:21 |
| T42_ | <vilez0> | 20:21 |
| T42_ | <vilez0> `should i delete it from sepolicy? | 20:21 |
| mal | probably | 20:21 |
| T42_ | <b100dian> Is libui_compat_layer now built by default? :D | 21:02 |
| T42_ | <vilez0> @b100dian (re @vilez0: FAILED: ninja: 'libu...) | 21:02 |
| T42_ | <b100dian> Yeah, just noticed that. The question was for mal. I had to manually include that before. You were havimg the error because of the missing hadk-faq manual, with patches to apply I guess. | 21:04 |
| T42_ | <b100dian> *having | 21:05 |
| mal | @b100dian yeah, we enabled libui_compat_layet build by default because newer android bases need it for gralloc | 21:13 |
| T42_ | <b100dian> great. One thing I seem to remember was that some previous ports were needing nulling out some default gralloc so (by mount binding /dev/null over). That still needs to be manually "detected" and "fixed" on a case by case basis I guess? | 21:18 |
| mal | we changed the order of things, no need for nulling that anymore | 21:20 |
| mal | it tries libui first, then gralloc hw module | 21:20 |
| T42_ | <b100dian> That sounds very good, thank you! | 21:21 |
| mal | https://github.com/sailfishos-mirror/libhybris/blob/master/hybris/gralloc/gralloc.c#L109 | 21:21 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!