Monday, 2021-03-08

T42<PizzaG> Hey Barry00:11
T42<F1a5H> hi01:39
rinigusmal: I didn't check minimedia, but looked on strace of audiopolicy. Also kept 32 bit links, as in seine. So, cannot tell much regarding it05:16
T42<lackingcheesepuffs> Can lineage 17.1 trees be used with sailfishos now?07:20
T42<Verevka86> @lackingcheesepuffs [Can lineage 17.1 trees be used with sailfishos …], Yes09:09
T42<edp_17> @elros34 [the values in hw-settings.ini seems to be qt k …], Thanks @elros34 . I've defined these and therefore I can test all of them with csd. Although, pressing the home button do nothing ib csd. Otherwise the home button does work (it wakes the screen up and goes back to the home page). What is funny, csd/Key doesn't react on p10:41
T42ressing the home button, but if I go back to the Hardware tests page, pressing the home button it minimizing the csd app and taking me to the Home page.10:41
T42<edp_17> The same code 0x01000090 does work on Note 4 (treltexx) and S2 (i9100).10:41
malwhat are you trying to do?10:46
T42<edp_17> @birdzhang [@edp_17 check MINIMEDIA_AUDIOPOLICYSERVICE_ENA …], I've don this and the result:10:51
T42<edp_17> When I turn on the camera and picture mode is selected, the image appears in the view finder for a second, then it goes black.10:51
T42<edp_17> When I turn on the camera and video mode is selected, I always see the image correctly in the view finder. When I start recording a video the counter counts at the top but when I hit the stop button the app gots frozen and not responding. The recorded video is not stored anywhere only an empty file created in ~/Videos/Camera.10:51
T42<edp_17> mal: I was trying to test the Home button in csd.10:52
malnot sure if there is support for that10:53
T42<edp_17> mal: thats not important at all, as the home button dos work, only cannot be tested in csd. I just wanted to highlight this. Don't worry about it as I have more important issues to solve.10:53
malprobably not worth the effort to look into that right now10:54
T42<edp_17> mal: Exactly. I agree.10:54
T42<edp_17> mal: The HADK still says to build and install gstreamer1.0-droid and gstreamer1.0-droid-tools and droid-camres. (Section 14.3 Camera) Is it still required to make the camera work?11:19
malgstreamer1.0-droid is needed for camera, those others help creating needed configuration files (those can be made manually also)11:29
T42<elros34> @edp_17 Have you checked logcat? That hang after recording might generate some error11:43
T42<edp_17> The HADK said to add audiosystem-passthrough-dummy-af into pattern and rebuild droid-configs. I also rebuilt droidmedia and then installed all packages onto device. Now, both, picture and video mode, shows black screen. The viewfinder in video mode is gone.12:06
T42<edp_17> Okay, I manually created /etc/gst-droid, then run the command mk-cam-conf 0 /etc/gst-droid/gstdroidcamsrc-0.conf and mk-cam-conf 0 /etc/gst-droid/gstdroidcamsrc-1.conf12:10
T42<edp_17> Now, the viewfinder in video mode is back.12:10
T42<edp_17> When I stop video recording and the caera hangs, I get this in journal: CameraBin error: "Couldn't create encoder for format video/x-h264"12:12
T42<edp_17> When I start camera in picture mode, I get this in journal: CameraBin error: "failed to negotiate caps"12:14
T42<edp_17> Full journal log:
mal@edp_17 no need to have gstdroidcamsrc-0.conf files12:37
mal@edp_17 only the jolla-camera-hw.txt12:37
malwhich is created by droid-camres12:37
T42<edp_17> Okay, so the only thing I need to build is droid-camres, then generate that jolla-camera-hw.txt. Thanks. (Atm, this file doesn't exist on the device.)12:39
malyes, that is the important part12:40
malthose other ones are obsolete files12:40
T42<edp_17> Thanks. I'll try now.12:40
maldroid-camres is in common repo12:41
malso you should be able to just install it12:41
T42<edp_17> So, I don't need to build. Great!12:41
T42<edp_17> mal: Interestingly  got this:
malyou need to downgrade gst-droid12:45
malto tag 0.20201104.012:46
T42<edp_17> mal: thanks.12:46
malPSA: do not update gst-droid to latest version12:46
T42<edp_17> mal: do I need these in external/droidmedia/env.mk12:59
T42<edp_17> plus, do I need audiosystem-passthrough-dummy-af in patterns?12:59
maldepends on your device13:06
mallogcat should tell what you need13:06
T42<edp_17> mal: I've managed to create the jolla-camera-hw.txt but it didn't make any difference. The camera app still works the same way (picture viewfinder is blank and only video viewfinder shows image).13:58
maldo the resolutions in the jolla-camera-hw.txt look ok?14:01
T42<edp_17> mal:
malyou can see some issues there14:04
T42<edp_17> mal: What are they? Are these like @PRIIMAGE169RES@ ?14:05
maltry to check the output of this: GST_DEBUG=6 mk-cam-conf 0 /dev/null 2>&1 | grep params_parse | sed -e 's/.*param\s//' | sort -u14:06
malalso same for camera 1 (the number after mk-cam-conf in that line)14:06
T42<edp_17> cam 0:
piggzmal: for gst-droid is it the tag before multi-camera that should be used?14:07
T42<edp_17> mal: cam 1:
malpiggz: yes14:10
mal@edp_17 interesting your secondary camera only support 4:3 aspect ratio, make sure you select that aspect ration from camera app settings14:12
T42<edp_17> mal: Done. And I am trying to modify the jolla-camera-hw.txt based on the output of those commands.14:13
swanuxSo I rebuilt the rootfs (now proper, but I still can't get GUI (same segfault with lipstick on 16.0 base). Any news / ideas on this topic?14:16
swanux(saw some display related discussion above, I'm not sure if it's applicable /relevant for other devices)14:17
malswanux: did older version work?14:20
T42<edp_17> mal: A little problem here. When I change the Photo resolution of the camera app in Settings/Apps, it doesn't save it. I set it to 4:3 but when I go out and come back, it is reverted to 16:9.14:21
swanuxmal: No, it was worse (complete freeze before telnet or any usb connection - the 15.1 lineage itself seemed to be quite buggy too)14:22
malswanux: you probably need to show logs14:23
mal@edp_17 anything in logs when that happens14:23
malin journal14:23
T42<edp_17> mal: nothing in journal when I change those values14:24
T42<edp_17> mal: neither in logcat14:25
swanuxmal: lipstick (logcat -, strace -, test_hwcomposer (logcat - last part looping here, strace - here too)14:34
swanuxHmm. May it be relevant? ( I mean the CONFIG_QCOM_BSP seems to work with more than one device. Or is this irrelevant?15:01
swanuxAlso here's the logcat for test_edl ( which also segfaults15:05
swanuxtest_glesv2 & 3 works15:07
swanuxHeck, even test_opencl & test_gps do work.15:17
malwait, only hwcomposer fails?15:19
T42<edp_17> mal: Thanks for your help! Camera for making pictures does work now. Only recording a video is the problem as the app hangs.15:21
malquite sure you will something being waited in logcat15:21
mal*will see15:21
piggzlike audiopolicy service?15:22
malyes, or audioflinger15:24
piggzmal: is there a reason not to enable fake audio policy for everyone?]15:24
T42<edp_17> mal: everytime the camera hangs, I need to rebbot the device because when I restart camera it only displays black screen. In the log it says: CameraService: CameraService::connect (PID -1) rejected (too many other clients connecting).15:28
T42<edp_17> CameraBase: An error occurred while connecting to camera 0: Service not available15:28
T42<edp_17> DroidMediaCamera: Failed to connect to camera service15:28
T42<edp_17> So, it looks like the app doesn't quit properly.15:29
T42<edp_17> mal: I rebooted to be able to replicate the issue and get the logcat:
swanuxmal I put together a short summary ( I'm pretty sure there's the problem, I just lack the experience to see it.15:41
T42<edp_17> mal: Might I need this?:
mal@edp_17 not sure, could you check what media_codecs* files you have in /system/etc and /vendor/etc15:57
T42<edp_17> mal: You mean this?
T42<edp_17> Mal: Sorry, I understand now.16:12
T42<edp_17> mal: I have these:
mal@edp_17 please create a symlink /etc/media_codecs_google_video_le.xml which points to /system/etc/media_codecs_google_video_le.xml16:17
malalso symlink the other similar files if some symlinks are missing16:19
T42<edp_17> mal: Only this was missing.16:20
mal@edp_17 did that symlink help at all?17:35
T42<elros34> mal: do you have some ideas where to search that issue with recommends packages not being installed? I checked fresh sdk and it is same. BTW during search I figure out why adaptation0 doesn't work on fresh sdk. It requires changing domain from sales to sailfish: sudo ssu domain sailfish17:46
malhmm, interesting17:50
mal@hacker12455 hi, are you around?17:55
T42<elros34> mal: I used wrong repo so maybe there is change after fresh sdk installation, need to test18:10
malwhat wrong repo?18:11
T42<elros34> I used obs instead local repository for testing18:11
T42<elros34> Is there a chance that obs is the culprit? There is Provides and Requires in patterns-sailfish-device-configuration-$DEVICE.rpm at details page of obs but ther eis Recommends18:28
T42<elros34> there is not*18:28
T42<hacker12455> mal: yeah, why?18:39
T42<elros34> seems to also missing Recommended csd package18:43
T42<elros34> lbt: any ideas about that Recommended packages are not pulled when using obs repository?18:47
lbtRecommended are not pulled in as build time dependencies18:48
lbtso if a package you BuildRequire has a Reccomends that you want then you must also BuildRequire that if you need it18:49
T42<elros34> I am not talking about build requirements. I meant that when I used obs repo when creating image via mic then Recommended packages are not pulled18:51
mal@hacker12455 I can tell you the selinux changes needed if you have time19:15
T42<hacker12455> sure19:15
T42<hacker12455> even if I don19:15
T42<hacker12455> *don't test it today it will be useful for later19:16
mal grab that folder but replace file minimum/policy/policy.30 with /vendor/etc/selinux/precompiled_sepolicy from your android repos (or similar location in /system if that doesn't exist) and also replace minimum/contexts/files/file_contexts with /vendor/etc/selinux/vendor_file_contexts from your device (same applies there, it19:18
malshould be in /vendor but if not then find it in /system)19:18
malalso make sure you don't disable selinux from kernel commandline (remove the selinux=0 from kernel commandline in case you added it there before), not sure if making selinux in android side permissive is needed but I have it, so add androidboot.selinux=permissive to kernel commandline19:20
malalso make sure you have latest droid-configs-device submodule and add this line to your droid-config spec file
T42<hacker12455> anything else?19:36
malnone that I can think of now19:38
T42<hacker12455> I assume I have to rebuild the rootfs?19:38
malwell those could be done on device also (except for kernel commandline changes if needed) but maybe better build new image19:40
T42<hacker12455> do I rename the files from the device?19:56
T42<hacker12455> for example if I grabbed vendor_file_contexts do I rename it to file_contexts19:57
T42<hacker12455> goddamnit20:16
T42<hacker12455> Error <creator>[03/08 20:16:10] : Unable to find package: patterns-sailfish-device-configuration-cedric20:16
T42<hacker12455> ah right my adaptation-community repo was gone from the kickstart file again20:18
malyes, rename the file to what I mentioned20:19
T42<hacker12455> for now I have to fix this20:21
T42<hacker12455> Error <creator>[03/08 20:20:00] : URLGrabber error: can't find file ///home/kacper/hadk/droid/droid-local-repo/cedric/repodata/repomd.xml20:21
malhmm, is the path correct, show the whole line20:22
T42<hacker12455> yea fixed that20:23
T42<hacker12455> had a droid folder in there accidentally20:23
rinigusevening. back with arm32/aosp9/tama port update to 4.0.1. looking through kernel options, cgroup specifically, there are no diffs between ganges and tama.20:29
rinigusCGROUPS and CGROUP_SCHED are not specified in tama configs, but they seem to be enabled by default (/proc/config.gz on device and .config in kernel obj)20:29
rinigusI have not updated hybris patches in my hadk/android and I can see that /dev/cg2_bpf cgroup device was removed recently. but I am not sure it is relevant20:31
rinigusseems to be mounted in my builds.20:32
rinigusalthough, /sys/fs/bpf has some issues mounting it. which was fine in 3.4.20:37
rinigusprobably bpf has nothing to do with my cgroups trouble - it is still mounted.20:47
rinigusactually, maybe I am wrong. should test with this applied:
malyeah, seems there was a reason doing that21:19
T42<elros34> I think issue is that obs repodata/*-primary.xml.gz is missing recommended packages. Maybe it's not using createrepo_c to generate repodata23:00

Generated by 2.17.1 by Marius Gedminas - find it at!