Thursday, 2024-02-22

T42_<elros34> I see big clean up is comming soon. Are you going to keep armv7hl alive?09:42
T42_<WrrrIamAnAngryCat> what kind of cleanup?09:44
T42_<elros34> If I get it right dropping support for kernel < 4.0 devices means  there were be only aarch64 devices supported. That is why I ask about arm09:47
genericv2hey, i am back14:58
genericv2had some work to do, now i'll work on audio14:58
genericv2with quirks arg removed:
genericv2ah, my bad15:09
genericv2need to run it as user, not root15:09
genericv2as defaultuser:
genericv2same with no args too
genericv2mal: anything>15:35
malsome issue still with linker config probably, or something like that15:36
genericv2E: [pulseaudio] droid-util.c: Failed to load audio hw module audio.primary : Invalid argument (22)16:02
T42_<elros34> some silly idea just to test (make sure you backup your current /odm/): ln -s /usr/libexec/droid-hybris/system/lib64/*.so /odm/lib64/16:19
malgenericv2: which device was that again? is it some qcom device or something else?16:24
genericv2xiaomi mi 6, qcom msm899816:24
genericv2with kernel 4.416:24
genericv2sound also magically started to work now16:25
genericv2i don't have a single idea what i did, but it's working16:25
genericv2First of all i added and to /odm, lots of library errors dissapeared. Then i removed the config i added.16:27
genericv2i'll try to restart.16:27
maloh, libaudioroute16:28
malwait a minute16:28
malmight be that you needs some similar symlink16:29
genericv2also i realized my screen cracked even more now xD16:29
genericv2i'll try, a min16:29
genericv2restarting brokes pulseaudio btw, starting it via terminal is okay16:30
malyou need to find where that lib is on the device16:30
genericv2i have it on /apex
genericv2can i symlink this one>16:31
T42_<elros34> it is found normally in strace16:31
T42_<elros34> can you show few seconds of working strace for comparision?16:32
genericv2here you go:
genericv2i terminated it at end16:34
genericv2it's not crashing16:34
genericv2mal: symlink gives this ( but copying the file to there and removing it from /odm is okay16:37
T42_<elros34> how could change anything? Doesn't it work same if you remove symlinks/copies?16:40
mal@elros34 I suspect linker config issue, it doesn't find it from apex16:40
malbecause sfos side doesn't have any linker config it uses so it falls back to some default paths16:41
T42_<elros34> that is the point  I can see it found it16:41
maleven without anything?16:41
T42_<elros34> yeah
genericv2yup, everything messes up when i remove, look:
maldoes symlink work in odm?16:43
genericv2a minute16:43
malstrace will tell what it tries to do16:46
malwhat happens if you remove that HYBRIS_USE_VENDOR_NAMESPACE=yes ?16:46
genericv2i'll try16:47
genericv2so different:
malok so that didn't work17:01
T42_<Endrju176> do anyyone have a ril/imei fix for sailfishos-a5y17lte-release- ?17:09
genericv2mal: besides from this, can you give me a doc on building sources with .spec files?17:42
genericv2nevermind find it, i'll it now17:44
genericv2found it*17:44
genericv2what did i just write17:48
T42_<elros34> interesting diff about these straces you uploaded are: not found in /odm, loaded form /system and then whole bunch of libraries from /system are loaded including libc and so on instead libexec17:50
Mister_Magistermal: so the new sfos will require 4.4 kernel? do you think is it still doable to carry on with 3.4 on backports?17:55
malwell not sure if it will require it yet17:59
T42_<elros34> Are you going to update systemd in next sfos release?17:59
malnot sure yet, it's possible18:01
malgcc 10 update is currently blocked by some systemd issues, not sure if it's possible to fix those without updating18:01
Mister_Magistermal: o7 gotcha18:11
Mister_Magisteri'm really worried as i love this deviec18:11
maleven systemd update is not certain to require newer kernel18:12
Mister_MagisterI wonder how many of my apps will jolla break in next update18:14
T42_<elros34> our current systemd requirements are >=3.13 according to README but it still works on older kernels18:15
mal@elros34 yes, v251 brings hard dependency to 3.1518:16
Mister_Magisterthen probably at most jsut couple patches and voila18:18
malone afaik18:18
malunless other ones have been added later18:18
T42_<elros34> so there is a hope:)18:18
Mister_Magisterthen thats fine18:19
T42_<Endrju176> is here like a generic imei fix for sailfish??18:52
T42_<elros34> you need to explain your issue. What is imei fix18:53
T42_<Endrju176> ive very succesfully installed the newes sailfish updae of 4.5 but i have no imei, its just blank18:55
T42_<Endrju176> my device is samsung a5y7lte18:56
Mister_Magisterdo you have no imei or is it simply not displayed19:02
Mister_Magisterdoes the sim card work fine?19:02
T42_<elros34> did you update via OTA?19:08
T42_<Endrju176> i have no imei, no i sideloaded it through twrp,  -23:11
T42_<Endrju176> yes sim works23:12
T42_<Endrju176> as it was my first time installling sfos on this phone, i simply installed twrp, and through that i first sideloaded lineage 18 which had no problem with the imei. i then proceded to install sfos. all boots phine, put the place where imei should be is completly blank23:16
T42_<elros34> 'ssu status' also doesn't show imei in DEVICE UID field?23:21
T42_<Endrju176> nope23:28
T42_<elros34> I guess this is read from ofono but no idea where excatly search for it. Did you check for any ofono errors?23:35

Generated by 2.17.1 by Marius Gedminas - find it at!