Saturday, 2022-01-15

T42<elros34> @Verevka86 maybe overlayfs?01:44
ThaodanThe halium patch seems easier01:44
T42<elros34> doesn't it require building  system.img or something else?01:46
ThaodanIt requires rebuilding hal01:47
Thaodansystem.img is without hybris patches.01:47
T42<elros34> if this part is hybris-hal then sure it's better idea than overlayfs01:48
Thaodanyes it is.01:48
T42<Verevka86> it requires system.img (re @elros34: doesn't it require b...)06:07
T42<AntonlX> I've fixed adsprpcd spam with firmware mounting and I am getting this hal error now10:35
T42<AntonlX> droid-hal-init: Control message: Could not find 'android.hardware.sensors@1.0::ISensors/default' for ctl.interface_start from pid: 3573 (/system/bin/hwservicemanager)10:35
T42<AntonlX> but locate in system/lib10:36
T42<Verevka86> I tried via LD_LYBRARY_PATH but something went wrong 😁 (re @SailfishFreenodeIRCBridgeBot: <mal>I haven't looke...)11:08
T42<AntonlX> And how to disable libperfmgr service?11:26
Thaodancreate an rc file and overwride the service with one that has a file that doesn't exist12:05
T42<Verevka86> /apex/
T42<Verevka86> I don't have this library 😳14:24
T42<Verevka86> logcat-14:24
T42<Verevka86> linker  : CANNOT LINK EXECUTABLE "/usr/libexec/droid-hybris/system/bin/minimediaservice": library "" not found: needed by /system/lib/ in namespace (default)14:24
T42<Verevka86> I added in init.rc >16:38
T42<Verevka86> on fs export LD_LIBRARY_PATH /oem/lib:/oem/lib6416:38
T42<Verevka86> Its work πŸ‘ (re @SailfishFreenodeIRCBridgeBot: <mal>I haven't looke...)16:38
Thaodan@Verevka86: Don't patch init.rc but add it to an rc file in sparse16:38
Thaodancreate something ld_lib_path_hack.rc and put the contents into sparse/usr/libexec/droid-hybris/system/etc/16:40
T42<Verevka86> Thanks I will check 🀝 (re @SailfishFreenodeIRCBridgeBot: <Thaodan>create some...)16:40
T42<Verevka86> Its work thank you16:47
piggzmal: this is strange ...on PP,  in csd, prox sensor works fine ... but in a call, it doesnt dim the screen16:56
piggzmal: logs show mce sees it...17:05
piggzJan 15 17:03:26 PinePhone mce[2088]: modules/proximity.c: mp_datapipe_set_proximity_sensor_actual(): state: OPEN -> CLOSED17:05
piggzJan 15 17:03:31 PinePhone mce[2088]: modules/proximity.c: mp_datapipe_set_proximity_sensor_actual(): state: CLOSED -> OPEN17:05
piggzJan 15 17:03:31 PinePhone ofonod[2143]: drivers/qmimodem/voicecall.c:hangup_active()17:05
T42<Verevka86> + hybris18.1 (re @SailfishFreenodeIRCBridgeBot: <piggz>mal: this is ...)17:44
T42<Verevka86> Hybris18.1 sound work only bluetooth headphones 😳17:45
T42<XAP2P> lmao (re @Verevka86: Hybris18.1 sound wor...)17:46
T42<XAP2P> vital (rus: ΠΆΠΈΠ·Π°)17:47
T42<AntonlX> How to deal with these errors?18:21
T42<AntonlX> KONA Media1: ASoC: no backend DAIs enabled for KONA Media118:21
T42<AntonlX> q6asm_audio_client_buf_alloc_contiguous: buffer already allocated18:21
malnot all of those are critical issues19:27
malyou should show full journal log and logcat19:27
T42<AntonlX> @mal journalctl log:
T42<AntonlX> logcat log:
T42<AntonlX> my droid configs
T42<elros34> @AntonlX at least you are missing /vendor/firmware_mnt not sure about others because your journal is generated way too late20:32
T42<AntonlX> I've mounted firmware_mnt (re @elros34: @AntonlX at least yo...)20:45
T42<elros34> then update your droid-config repo, still in logcat there was /vendor/firmware_mnt/* "no such file" error21:01
T42<elros34> I wonder why do you need this: Do not you have binder mount unit generated in droid-ha-device.log? Probably I have already asked about it but not sure whom and never get answer21:05
ThaodanI wouldn't do anything in the android init that isn't necessary21:08
T42<AntonlX> Yes, I dont need this. I just update my github (re @elros34: I wonder why do you ...)21:10
T42<Verevka86> Fix 😊 (re @Verevka86: Hybris18.1 sound wor...)21:15
malwhat was the problem?21:33
malI mean di you edit that file or just copy it?21:33
ThaodanAntolX: If you need to adjust that file your should patch the android sources and rebuild21:35
Thaodanthe copied and edited it I guess.21:36
Thaodaneh Verevka86 not AntolX21:36
malmore intesting part is what the modification was if it was modified21:36
maland can it be avoided somehow21:36
Thaodan""Delete <mixPort name="usb_surround_sound"21:36
ThaodanHowever I'm not sure either since audio for Android 11 isn't ready.21:37
malah, true, there are still some issues with it21:37
T42<elros34> I think I saw similar modifications on older bases too when pulseaudio wasn't happy about some entries in xml file21:38
ThaodanThat's not pa but hybris plugins21:38
malanother option is to fix pulse droid modules to handle those21:38
ThaodanThat's wip21:39
malwould be nice to see the real error21:39
malif it's in pulse output21:39
Thaodanthose plugins are currently refactored21:39
malbut if the fix is some simple thing it could still be handled21:39
ThaodanOn Xperia 1 II audio isn't working at all right now while Xperia 10 III at least has speakers.21:41
ThaodanBut I don't want to waste my time fixing things before refactoring is done.21:42
ThaodanMy point is more complex cases could require more work right now to even get working where as if the routing is working with the new format it can work normally.21:46
T42<Verevka86> Edit (re @SailfishFreenodeIRCBridgeBot: <mal>I mean di you e...)21:46
malwas there some error from pulseaudio?21:48
T42<Verevka86> Delete this section (re @SailfishFreenodeIRCBridgeBot: <mal>more intesting ...)21:49
T42<Verevka86> I applied the same solution in halium-1121:53
T42<b100dian> Removing some usb related tags in audio xmls sounds familiar for me too:-S22:13
T42<Verevka86> there is no sound during a telephone conversation (also in halium11) πŸ˜”22:26
T42<Verevka86> The camera and vibration also do not work, otherwise hybris 18.1 looks very good22:27
malvibra should usually work22:29
malunless there is some permission issue22:29
malhow did you test vibra?22:29
T42<Verevka86> when entering text, it was on my sagit with hybris18.1, now it is nowhere to be found 😊 (re @SailfishFreenodeIRCBridgeBot: <mal>how did you tes...)22:42
Thaodanmal: vibra usn't working because ngfd doesn't support ffmemless custom without PR22:55
ThaodanHe is on sm8150 which uses ffmemless for vibra22:59
T42<b100dian> It is possible, this being a xiaomi, that it has the same vibra custom stuff. I was surprised there's some from sony23:00
ThaodanIts not sony but qcom related23:07
malThaodan: oh, again some device needing custom things23:10
ThaodanIts not really custom but just some pattern defined in dts instead of a vibration curve23:11
T42<b100dian> I thought they get to choose peripherals, thats why I mentioned the vendor. Is vibra on the SoC too?:-/23:16
ThaodanI guess so, which soc do you have?23:19
T42<b100dian> sm6150 I guess23:25
T42<b100dian> I dont have the patterns in dts as you23:26
T42<b100dian> Far more likely IMO, the source the hardware and then each one does its own thing. I think the custom vibra is more like a dumb hardware thing (with good feedback, I might add)23:27
T42<b100dian> *they23:27
T42<b100dian> Nowhere near an 808 vibra if you ask me, but nor were the AOD and doubletap available on these *ndroids for some time:-S so getting there.. :)?23:32

Generated by 2.17.1 by Marius Gedminas - find it at!