Friday, 2022-02-18

T42<HengYeDev> @elros34 ok i did that, now the parts are mounted00:11
T42<HengYeDev> droid hal init is still failing00:11
T42<elros34> partial logs are useless00:11
T42<HengYeDev> i lose the log with knox, i will patch kernel so i can get whole log then00:12
T42<edp_17> I've done that and now I do have a folder in /var/log/journal that has few files in it. Although, their content looks like compressed or something, cat doesn't display them properly: (re @elros34: enable persistent lo...)08:01
jusaPSA: I'm going to fork pulseaudio-modules-droid shortly to make Android 11+ based adaptations easier to maintain. The original modules are going to be renamed to pulseaudio-modules-droid-q ( and will continue to be usable as is in current adaptations, just need to replace used repository08:16
jusa( Any thoughts or concerns about this change?08:16
T42<edp_17> @elros34 : Interestingly now the journalctl command shows log entries pre-reboots:
T42<eugenio_g7> jusa: when you have some time, could you have a look at and ? Thanks!08:23
jusayes, just approved the PR 111 :) since you are here, do you want to still do those small things I mentioned?08:36
jusasuccess = pa_conversion_parse_output_channels(filename, n, value, true, &output->channel_masks) > 0;08:37
T42<eugenio_g7> jusa: thanks for the super fast review :) Will amend that shortly08:39
T42<edp_17> Is it possible to build sfos 4.2 with tooling and target 4.3? Or must be used target and tooling 4.2?08:54
T42<TheVancedGamer> Deleted (re @SailfishFreenodeIRCBridgeBot: <Thaodan>yeeted?)09:03
T42<TheVancedGamer> Because the bots delete the messages immediately, but they get forwarded to irc09:04
piggz_mal: lbt: builds are still failing because of space
T42<eugenio_g7> jusa: PR updated09:07
piggz_jusa: i dont suppose you have a Pinehone to hand? :) .... got a weird issue routing.  cant route call audio to speaker09:08
piggz_probably down to names of things?09:08
piggz_speaker does work for media playback09:08
T42<edp_17> More on this one. It looks like lipstick is crashing and tracker-miner-fs-3.service is failing.09:25
T42<edp_17> logcat:
T42<edp_17> journal:
T42<edp_17> Why they are fine after a fresh install? (re @elros34: enable persistent lo...)09:25
piggz_lbt: for 4.4, can you make sure the new adaptation-common repo pacakges are on OBS to allow eg d-h-v to build properly?09:50
T42<elros34> @edp_17 any reason why do you have audit enabled? There is no reboot reason in journal, try /sys/fs/pstore/. BTW you did not copy some bluetooth file, see errors in your journal10:01
T42<elros34> you have some lib akm error in logcat, Didn't you use some fix for it in previous release? Do you use same libhybris version as previously when gui worked?10:06
jusaeugenio_g7: noticed one issue when double checking your PR10:18
T42<edp_17> Yes, it was commented out but since I updated libhybris in mw. I only have two line numbers 4218 and 4219 but I am not sure the same lines should be commented out in the latest libhybris/hybris/common/n/linker.cpp. (re @elros34: you have some lib ak...)11:05
T42<edp_17> No, there is no reason. I waan't aware of it was disabled. How do you mean try /sys/fs/pstore/?11:12
T42<edp_17> Regarding BT, are you referring to errors about /etc/bluetooth/main.conf , jolla.conf, input.conf and audio.conf?11:12
T42<edp_17> I don't know where from I should copy them over. (re @elros34: @edp_17 any reason w...)11:12
T42<elros34> looks like only fails so not sure it will fix your crash part, maybe try using older version of libhybris. About pstore: this or /proc/last_kmsg should have logs if your kernel crashed. Bluetooth files seems to be related to bluez4 drop and files you did not copy11:15
T42<edp_17> I'll try an older libhybris. Unfortunately, I have no idea what version I had before updated to the current one.11:25
T42<edp_17> Regarding bluetooth, I am still using an old bluetooth-rfkill-event (I am at this commit fb19a4117399c2832afafecce91057260615b4e1). So bluez4 drop shouldn't impact it, should it?11:25
jusapiggz: nope don't have Pinephone :/11:28
piggzjusa: ok, ny thoughts? could you go from config, or cold i get relevant logs?11:29
piggzalsa ucm config is and pulse config is
piggzcurrent on-device pa config is
piggzi did quite a bit of debugging with mal around ohm etc ... those logs have expired though so id have to get more11:33
T42<elros34> @edp_17 don't you backup sailfish image with *.packages file per release after all this upgrade issues you had? About bluetooth I am talking about droid-config submodule and files which were removed not rfkill-event11:43
T42<edp_17> @elros34 : the last working sfos version (4.0) has libhybris-*.67fb336+libhybris.b19ff09-1 in the *.packages. So, the last good libhybris version was with this commit 67fb336. Right?11:48
T42<edp_17> I thought always had to update libhybris to the latest.11:48
T42<edp_17> Regarding bt, I have updated dcd sub-module. Should I go back to pre-"drop-bluez4" version?11:49
T42<elros34> sure you should use latest libhybris but if you have some issues without any apparent reason then obviously reverting kernel or downgrading packages is good idea11:52
T42<edp_17> I see. Thanks.11:53
jusapiggz: verbose pulseaudio logs would probably rule out ohm etc quite easily11:54
T42<elros34> @edp_17 I don't get you about bluetooth, you have in logs "/etc/bluetooth/main.conf failed: No such file or directory" and this file was removed in so obviously you either did not copy all files or you did not downgrade submodule11:57
T42<elros34> whatever you prefer is up to you11:58
T42<edp_17> @elros34 : Yes, I did miss these files. I'll rectify the i9100 port as well. Thanks.12:03
T42<elros34> n7000 is 3.0.101 right? I do not daily use but from short test on same kernel I did not had such crash issues like you12:06
T42<edp_17> Yes, n7000 is 3.0 kernel. The i9100 is on the same 3.0 kernel and works fine with sfos4.3 (just built 2 days ago).12:09
T42<edp_17> No crash on the i9100 although, those bluetooth files are also missing as I didn't downgrade the dcd only reinstated the removed bluez4 stuff into  droid-configs.inc12:10
T42<edp_17> What is weird about the crash/reboot on n7000. It happens when the device is off charger.12:11
T42<edp_17> If it is on charger, the system keeps running but lipstick crashes/restarts.12:12
T42<edp_17> Plus, this is only happening once the device went through the initial setup. Weird.12:12
T42<elros34> check whether your have /proc/last_kmsg directly after such a device crash12:12
T42<edp_17> Will it stay after the reboot?12:13
T42<edp_17> I'll check that.12:13
piggzjusa: enjoy! ... the gaps in the logs are where i hit enter and pressed the speaker button12:13
T42<elros34> @edp_17 after crash and first boot not simple reboot that is the point of it12:14
piggzjusa: around line 700 maybe relevant?12:15
jusapiggz: can you add pactl list to that paste?12:17
piggzjusa: sure12:19
piggzjusa: pactl list
T42<edp_17> I'll try this. Thanks. (re @elros34: @edp_17 after crash ...)12:24
jusapiggz: if you could get verbose pulseaudio logs as well that would be helpful? have you tried changing the routing from command line during call? pactl set-card-profile alsa_card.0 "Voice Call" and pactl set-sink-port alsa_output.0.HiFi__hw_PinePhone_0__sink "[Out] Speaker" ?12:25
piggzjusa: i havnt....12:25
piggzjusa: no such entity12:29
piggzjusa: this is the log with PA added  to the mix
piggz[defaultuser@PinePhone ~]$ pactl set-sink-port alsa_output.0.HiFi__hw_PinePhone_0__sink "[Out] Speaker"12:30
piggzFailure: No such entity12:30
piggz[defaultuser@PinePhone ~]$ pactl set-sink-port alsa_output.0.HiFi__hw_PinePhone_0__sink "Speaker"12:30
piggzFailure: No such entity12:30
jusaodd.. do you have journal ratelimiter on btw, it at least looks like log lines have been dropped12:45
piggzjusa: ok, one moment13:00
T42<eugenio_g7> jusa: thanks, fixed13:01
jusapiggz: ok I have and idea what to try, modify xpolicy.conf like this:
maljusa: there was also something we were thinking before, do we hardcode the input/output names anywhere in policy side or ohm, I mean we have those with different naming now13:26
jusaand above commands failed because the sink/source was wrong during the call, they have card profile embedded in the name so correct one would be alsa_output.0.Voice_Call__hw_PinePhone_0__sink13:26
jusamal: names are in xpolicy.conf, xpolicy.conf.d etc, currently xpolicy.conf is pretty android-adaptation centric, it wouldn't hurt to modify it more generic so that only variables need to be modified for adaptations, but I haven't done that since I haven't done native adaptation with it13:31
piggzjusa: mal:will try13:46
piggzjusa: worked with pactl command, not automatcially13:49
jusapiggz: so speaker worked when calling from cmdline?13:49
piggzjusa: yes13:49
jusapiggz: ok, so then it's just xpolicy.conf changes13:49
piggzpactl set-sink-port alsa_output.0.Voice_Call__hw_PinePhone_0__sink "[Out] Speaker"13:49
jusaah make the call more strict, so sink = startswith:"alsa_output.0.Voice_Call"13:53
jusaand same for source13:53
piggzjusa: nope :(13:57
jusahrmh.. it has something to do how policy-enforcement does the port switching and there may or may not be a bug, anyways I guess the call starts with Earpiece enabled, toggling back and forth doesn't help either?13:58
piggzjusa: .... gap in the logs near the end is where i pressed the speaker button .. oddly, nothing logged by PA at that point13:58
piggzyeah, toggleing doesnt help13:59
jusait's not a big thing I'm sure but I suspect it is that the module doesn't take into account sinks that are registered during routing change, so need to take a look but that's probably gonna happen next Monday14:02
jusaah no, one thing more...14:05
jusathat's not the optimal way to do that but should work and I need to head home :D14:11
piggzjusa: that makes it go to the speaker only :)(14:13
piggzthx for help!14:13
jusayeah, you need to do similar for all *forcall14:13
piggzok, will do, after a small run!14:13
T42<LSolrac> Hello. Ive a question. Can I override a reference in repo? Im trying to sync and fetch the submodules for lineage18.1; however I got this14:35
T42<LSolrac> error: in `sync --fetch-submodules: revision refs/tags/android-11.0.0_r46 in platform/prebuilts/clang-tools not found`14:35
T42<edp_17> @elros34 : Is it enough to rebuild configs if I downgraded droid-configs-device sub-module?15:25
T42<edp_17> Thanks!15:25
piggzjusa: mal: struggline to get call audio to the headset still :D15:31
deathmistjusa: is there a reason Android 8+ support won't be maintained in pulseaudio-modules-droid? I'd assume the HIDL stuff also makes audio stuff nicer to work with compared to 7 or below16:08
deathmist(as in why will the new repo be limited to just 11+ and not 8+)16:09
piggzlbt:mal: phost4 still suffering from disk space16:22
T42<LSolrac> anyone? (re @LSolrac: Hello. Ive a questio...)17:49
T42<elros34> do you sync lineage or hybris-18?17:51
T42<LSolrac> yes17:51
T42<LSolrac> hybris-18 sorry17:51
T42<elros34> try once without fetch-submodules to see if it will pass then add it back17:51
T42<LSolrac> Followed the readme.17:52
T42<LSolrac> Should I replace it with appropriate URL?17:52
T42<elros34> not sure but yes maybe you should use hybris-18.1-update instead. Hybris-18 is WIP anyway17:54
T42<LSolrac> I can try with hybris-17 but I think I mightve made the same mistaken, but I had a lot of issues with the sources18:24
piggz_PSA log searching is offline while i change VPS provider18:44
T42<HengYeDev> @elros34 Here is the full journalctl
T42<HengYeDev> Here is init.log
T42<HengYeDev> device doesn't have have system_ext, dsp, and other partitions that can't be found ini int.log (re @elros34: partial logs are use...)20:05
T42<HengYeDev> @elros34 Here is the full journalctl
T42<HengYeDev> Here is init.log
T42<HengYeDev> device doesn't have have system_ext, dsp, and other partitions that can't be found in init.log (edited) (re @elros34: partial logs are use...)20:05
T42<HengYeDev> here is findmnt
T42<HengYeDev> It says it can't find /sbin/droid-hal-init but the file is there20:10
T42<elros34> so you didn't use provided script? I do not see mounted /system20:10
T42<elros34> journal is still not full20:11
T42<elros34> dmesg could be also useful20:11
T42<HengYeDev> I did, i put it in /usr/bin/ and executed it in init-debug (re @elros34: so you didn't use pr...)20:12
T42<elros34> so what is the content of /system_root/?20:12
T42<HengYeDev> @elros34 its filled up20:13
T42<HengYeDev> with the stuff in dynpart-system20:13
ThaodanHaving system_ext doesn't mean you need it20:13
T42<elros34> :) sure but what it contains. Is your device system-as-root or with regular /system20:13
Thaodane.g. /product is present on Xperia 10 III but unused for hybris-hal20:14
T42<HengYeDev> I believe its system as root20:14
T42<HengYeDev> It has directories such as20:14
T42<HengYeDev> acct                  debug_ramdisk         init.usb.configfs.rc  omr                   storage20:14
T42<HengYeDev> apex                  default.prop          init.usb.rc           optics                sys20:14
T42<HengYeDev> bin                   dev                   init.zygote32.rc      prism                 system20:14
T42<HengYeDev> bugreports            dqmdbg                init.zygote64_32.rc   proc                  ueventd.rc20:14
T42<HengYeDev> cache                 efs                   lost+found            product               vendor20:14
T42<HengYeDev> charger               etc                   metadata              product_services20:14
T42<HengYeDev> config                init                  mnt                   res20:14
T42<HengYeDev> d                     init.environ.rc       odm                   sbin20:14
T42<HengYeDev> data                  init.rc               oem                   sdcard20:14
Thaodandoes the system partition contain /system or not?20:14
Thaodanstop the spam20:14
T42<elros34> so do you have /system  mounted?20:15
T42<HengYeDev> yes /system_root/system seems to be20:15
T42<elros34> so why it's missing your findmnt output?20:17
T42<HengYeDev> not sure, theres definetly stuff in there tho20:18
T42<elros34> so "findmnt /system returns" something20:19
T42<elros34> ?20:22
T42<HengYeDev> no20:23
ThaodanHis system is in /system_root/system so I think  no.20:23
T42<HengYeDev> but /system_root yees20:23
ThaodanWell /system_root is supposed to be /20:23
T42<elros34> so how do check when you said that /system is mounted?20:23
Thaodanto that's why it doesn't work, you either symlink it or idk.20:23
T42<elros34> but he said it is mounted, script also bind mounts it so I want to understand what is wrong20:24
ThaodanOK bind mount should work20:24
Thaodanso yeah weird20:25
T42<elros34> I guess you didn't really use provided script but some modified then20:26
T42<HengYeDev> @elros34 I think i typoed, /system is empty, the system (as root) partition is mounted at /system_root @elros3420:44
T42<HengYeDev> @elros34 I think i typoed, /system is empty, the system (as root) partition is mounted at /system_root (edited)20:44
T42<HengYeDev> should i symlink /system_rooot/system to /system?20:44
T42<elros34> or bind mount it should be alread done in script20:44
T42<HengYeDev> i wonder why its not bind mounted20:46
T42<HengYeDev> the script is the same as pastebin20:46
T42<HengYeDev> maybe its the mount error in the init.log20:46
T42<elros34> script prints all relevant info to dmesg20:47
T42<HengYeDev> ok i will get that, is the output in init.log20:50
T42<Verevka86> (re @HengYeDev: @elros34 I think i t...)21:52
T42<HengYeDev> @Verevka86 @elros3422:42
T42<HengYeDev> seems like mount --bind /system_root/system /system22:42
T42<HengYeDev> is causing:22:42
T42<HengYeDev> mount: bad usage22:42
T42<HengYeDev> in journalctl - i can tell because the commands for mounting system_root is immediately before in log and system_ext is immeidately after22:42
T42<HengYeDev> it works perfectly in telnet though22:42
T42<HengYeDev> @Verevka86 @elros3422:43
T42<HengYeDev> seems like mount --bind /system_root/system /system22:43
T42<HengYeDev> is causing:22:43
T42<HengYeDev> mount: bad usage22:43
T42<HengYeDev> in journalctl - i can tell because the commands for mounting system_root is immediately before in log and system_ext is immeidately after22:43
T42<HengYeDev> it works perfectly in telnet though (edited)22:43
T42<HengYeDev> seems like the wrong command was used for that line, i used the one from the pastebin, the one from vayu works22:44
T42<elros34> indeed, funny that nobody who used this script  reported mistake..22:46
T42<HengYeDev> ok, now it boots, shows an black screen for 2 seconds, then bootloops22:58
T42<HengYeDev> I was able to telnet in quickly and get dmesg22:58
T42<HengYeDev> reboot is after 42 s in total23:01
T42<elros34> don't you have exactly same issue as dcmmc yesterday?
T42<HengYeDev> so its ofono, device does not have wifi, should i try
T42<elros34> why do you think it's ofono? I am talking about file encryption23:06
T42<HengYeDev> ahh i got confused, previous section had sim cards23:17

Generated by 2.17.1 by Marius Gedminas - find it at!