Saturday, 2021-05-08

UmeaboyCan someone please tell me why this happens?01:52
UmeaboyI DID change the values and still it says that it's unset. That should NOT happen.01:53
UmeaboyI'm off to bed while waiting for a reply. I'll be back in 8 hrs or so.02:01
T42<A_T_R> Hi, Anyone who successfully compiled hybris-17.1 with  4 GB of RAM (host)??06:33
Thaodanwhy would you take so much pain?07:37
Thaodanyou could try make -j1 but even then it could be hard07:38
*** Daaanct12 is now known as Danct1207:49
rinigustook sailfish-fpd-community as the next for aarch64/aosp10 on sony tama. in this case, fpd is 64 bit and all compiled fine.08:15
rinigusit fails to load which is at /system/lib64/vndk-29/android.hardware.biometrics.fingerprint@2.1.so08:15
rinigusafter adding the link from /usr/libexec/droid-hybris/system/lib64 all seems to work08:16
rinigushere "all" is the -test program08:16
riniguspiggz mal ^08:17
riniguswhat would be correct way to enable search in /system/lib64/vndk-29/ by hybris linker?08:18
Thaodanmount bind might help on this too we use symlinks atm08:18
Thaodansee droid-config-sony-seine08:18
rinigusThaodan: let me check08:18
Thaodanmagisk achieves similar things by using bound mount bind08:20
rinigusThaodan: cannot find it in nor in the common sparse-1008:20
ThaodanI meant
Thaodanwe link system for some libs so e.g. camera works08:21
ThaodanSo that could work here to08:22
rinigusThaodan: I see. but fingerprint works for you without it?08:22
riniguswe have those ICU bits as well08:22
riniguspiggz and mal : with the symlink suggested by Thaodan , fpd works on aarch64/aosp10 based port.09:32
T42<adampigg> Woop09:32
malrinigus: what symlink?10:37
maloh, that vndk thing, so similar that audio needs10:37
rinigusmal: yes, in vndk. I wonder whether seine needs the same one or you have some different solution for it11:24
rinigusas droid-config-sony-seine does not have this symlink11:25
malrinigus: I should test that on fp3, it has non-working fpd, it used to work on hybris-16.012:18
T42<ankaos> PlatformSDK [enes@enes hadk]$ sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper dup12:48
T42<ankaos> which ı use?
T42<ankaos> 1/2/3/c which?12:56
T42<b100dian> Context:13:10
T42<b100dian>  I noticed that if I LD_PRELOAD the for vndservicemanager my device crashes some 60-80 seconds after booting with adsp failure bringing down the kernel.13:10
T42<b100dian> If I _dont_ then it is not rebooted, and logcat works and it spams me with `E /vendor/bin/adsprpcd: vendor/qcom/proprietary/commonsys-intf/adsprpc/src/adsprpcd.c:48:adsp daemon will restart after 25ms.`13:10
T42<b100dian> New change that gpt me 'past' this:13:10
T42<b100dian> Copying device's /vendor/ueventd.rc to out/target/product/${device}/root/ueventd.${device}.rc made it not reboot anymore.13:10
T42<b100dian> So the first simpler question would be: how can I make this change permanent (between builds)?13:10
rinigusmal  for me, 64 bit version worked. Let's see what it would be for fp313:11
T42<b100dian> 2/2 Also, even though the device does not reboot now, it kicks me out of telnet after 42 seconds since booting: Here's the console-oops from /sys/fs/pstore
T42<b100dian> Can someone tell me when does the usb0 disconnect and more importantly why can't I not get telnet to it anymore :( ?13:14
T42<b100dian> s/when/why13:14
malrinigus: what kind of error did you see in logs?13:15
mal@b100dian which android base?13:22
T42<b100dian> mal: lineage 17.113:22
malthat should not be using libselinux_stubs13:22
mal17.1 is done so that it assumes selinux is enabled13:23
T42<b100dian> However the vndservicemanager would crash otherwise.13:24
T42<b100dian> That doesn't mean I should actually enable selinux in kernel, right?13:24
malhow did you disable it?13:25
T42<b100dian> boot cmdline + param enabled in kernel config13:26
T42<b100dian> selinux=0 in cmdline, that is13:26
maland yes, it should be enabled and not disabled at kernel commandline, then some configuration is needed in droid-configs repo13:26
T42<b100dian> you mean like sparse/etc/selinux?13:27
malrinigus: it seems my system is not seeing "android.hardware.biometrics.fingerprint@2.1::IBiometricsFingerprint/default" in manifest13:27
mal@b100dian yes13:28
malsomething like this
T42<b100dian> thanks mal. let me try that13:29
malnote that the files are copied from other places13:29
mal if you check here you can see where13:30
malthose are the symlinks but we have to copy the actual files13:30
rinigusmal: sorry, stepped away from kbd13:31
rinigusmal: error was that the sailfish-fpd-community.service crashed with the core dump13:31
rinigusthen when I ran it in terminal, it just stated that it cannot find the library13:32
malrinigus: I have the service in /vendor/odm/etc/vintf/manifest.xml but still I get the manifest error in logcat and then "Unable to get FP service"13:32
rinigusmal: I haven't checked logact, but have andoid daemon running (biometry one), as shown by binder13:33
rinigusso, I guess it should be in the manifest13:34
malrinigus: no idea why it's not seeing it in the manifest13:36
rinigusmal: no idea, no such errors over here...13:38
rinigusbut does it work in aosp?13:38
malthis is lineage based build13:38
maland I assume it should be working there13:38
malit did work in 16.0 based sailfish also13:39
rinigusyeah, for me it was rather straightforward when based on your PR for 64bit support.13:40
mallooks like my issue is something in android side maybe13:42
malnot sure what should be loading that /vendor/odm/etc/vintf/manifest.xml13:42
rinigusmal: yes, sounds like it. maybe test in lineage?13:42
malI hate to reflash it13:43
rinigusmal: can you use some backup/restore? twrp?13:44
rinigusI presume it is not using lvm13:44
malI have no backup of lineage13:44
rinigusyes, but that can be flashed after making backup of sfos. then it is easy to get back. but I can understand the reluctance to do so.13:46
rinigusalthough, if FP is not working, probably someone has complained about it13:46
riniguson xda13:46
malrinigus: it seems this one is not lvm based build for some reason, I did use it for 16.0 base13:47
malprobably because hybris-17.1 is hacky and won't fully work without manual hacks13:47
malI mean unless using packaged /system13:48
malI need to figure out how to patch libhybris to make it work13:48
rinigusmal: early days :) . for aosp10 it is not too bad, although there are issues here as well. but not with flashing and building13:49
malrinigus: main issue is camera13:49
riniguson lineage?13:50
malon any device not using packaged /system13:50
riniguspackaged - as provided by us via RPM and used to build full image, right? since sony tama camera is just fine :)13:51
malyes, without patching libhybris camera won't really work if /system is mounted from lineage or aosp13:52
riniguspity. and probably non-trivial to fix13:53
malrinigus: it might not be too difficult, needs to be able to load ld.config*.txt from /usr/libexec also13:56
maland then some custom ld.config*.txt with suitable search paths13:56
malrinigus: hmm, managed to fix fpd, needed ln -s /vendor/odm /odm13:58
malno idea why13:58
rinigusI guess /vendor/odm was not searched...14:00
malrinigus: wondering why the file was there14:01
rinigusso, you don't have /odm otherwise?14:01
rinigusI have /vendor/odm, but it has only one file: etc/build.prop14:02
malrinigus: I still have another issue with fingerprint on fp3, it doesn't obey the fingerprint data path set in fpd14:03
malso it tried to write those to wrong path in /data/ and doesn't have permission to do so14:03
rinigusohh, we were warned with piggz that for some devices the path was not supported well.14:04
rinigusat least it rings some bells. but don't remember exactly what were the limitations14:04
malrinigus: it writes it to /data/vendor_de/0/fpdata/ not to /data/vendor_de/100000/fpdata/14:05
riniguslet me try to find where it is for me14:06
rinigusmal: I have it under /data/system/users/100000/fpdata/user.db14:09
rinigusro.product.first_api_level is 26 for tama14:10
malyeah, so it follows what fpd sets14:10
rinigusbut why it tries to write under 0 and not 100000 for you?14:10
malrinigus: no idea14:12
rinigusmal: looking at the code, we have 100000 hard coded in FPDCommunity::FPDCommunity()14:13
malso that is not really multi-user friendly :)14:13
malrinigus: I see in journal "setActiveGroup to /data/vendor_de/100000/fpdata"14:14
rinigusmal: no, not really. there is a limit regarding number of fingers that can be stored and nemo/defaultuser is expected to have more than that already.14:14
rinigusbut we just postponed multiuser implementation, to make it future us problem14:15
rinigusmal: that journal record is correct. do you have such file then?14:16
malyes, but it's empty14:16
malthe files still go to /data/vendor_de/0/fpdata/14:16
rinigusshould have user.db or something like it for fingerprints.14:17
malrinigus: wondering something somehow check the pid of the process using fingerprint and sets the pid from it14:17
malit has : fids     fp2.bin  uid14:17
rinigusmal: so, fpd daemon works but crashes while you try to add fp?14:18
rinigusjust trying to figure out what's an issue14:18
rinigusmal: re pid - don't know14:18
malrinigus: no, adding fingerprints works fine if I give /data/vendor_de enough permissions so anyone can write to it and then the /data/vendor_de/0/fpdata/ appears with the fingerprints14:19
malfor now the only way could be to make fpd systemd service run some chmod in pre start to give that correct permissions14:20
malthat would be a quite ugly workaround14:20
rinigusmal: here are the permissions that I have over here -
malyes, I need to make sure system pid/group can create  /data/vendor_de/014:23
rinigusmal: I wonder how is it in lineage ... but it is strange that it pushes it to 0 path. which means that it ignores setActiveGroup call and still sets it to zero14:25
rinigusprobably setting permissions would be good enough14:26
malrinigus: checking strings of the vendor blob it has "/data/vendor_de/@/fpdata" and I assume that @ is replaced with something14:28
rinigusmal: seems so. question is whether it takes that something from env and setActiveGroup is in this respect ignored14:30
malvery difficult to say what it does14:31
malrinigus: maybe I should do a new build with those hacks in place, still need to figure out the camera hack14:32
malof course it would be easier to just patch /system14:33
malalthough doing it in libhybris would remove the need for having the ugly hack in /system14:33
rinigusmal: but then we have ugly hack in hybris.14:39
rinigus... which is a big hack anyway :)14:40
malrinigus: is it really ugly hack in libhybris, we have done search path changes in there already14:41
rinigusspeaking of hybris, I have an odd problem with flatpak support for aarch64/aosp10. when using similar approach as for earlier aosp versions, I cannot enforce hybris linker loading14:42
rinigusas a bg: flatpak support is similar to porting itself, it is just that hybris bits have to be injected into flatpak runtime via extension path. in this case, mounted under /usr/lib/aarch64-linux-gnu/GL/host14:42
rinigusso, some hybris bits are copied under there (linker, lib64) and I have set some env vars to point there (HYBRIS_EGLPLATFORM_DIR, HYBRIS_LINKER_DIR, HYBRIS_LD_LIBRARY_PATH)14:43
riniguswhen checking strace, it does load libhardware, but not proceeding to /dev/socket/property_service14:43
rinigusstrace bits available at
rinigusquestion is: how can I check why linker is not loaded?14:43
rinigus(sorry for wall of text, had to describe bg)14:44
malhmm, need to check that a bit later, I need to get some food14:45
rinigusmal: would be great to get ideas. thanks a lot and enjoy the food14:46
rinigusmal: but no rush, could be pushed further into the future14:49
rinigus... as you are in the middle of FP fixes14:49
Mister_Magistermal: got some time? i got g2 with 3.4 update and broken camera15:09
mallogs as usual, have you updated anything?15:12
Mister_Magisteri updated to 3.4 :D every package is updated i think… dcd and dvd submodules too15:13
Mister_Magisterwhat logs do you require?15:13
Mister_MagisterGST_DEBUG the camera?15:14
rinigusmal: my issue could be that qt 5.15 loads plugins bit differently. will investigate and come back on flatpak15:20
Mister_Magisterminimedia is running just fine15:23
rinigusno, read it wrong. plugins are probably ok -  just hybris linker is not kicking in . but I'll try to dig in15:30
malMister_Magister: that and maybe logcat, also how exactly does it fail?15:32
T42<A_T_R> make hybris-hal16:11
T42<A_T_R> log
T42<ankaos> @A_T_R [make hybris-hal16:12
T42<ankaos> log- …], line:13916:12
T42<A_T_R> @A_T_R [ …], @ankaos16:51
Mister_Magistermal: i start camera, viewfidner works fine, i snap photo, viewfinder stars spazzing out but if u just move hand in front of camera it will be bacc to okay and recording freezes app on stop17:15
mallogcat might be useful in that case17:27
Mister_Magistermal: logcat18:07
Mister_Magisterthere was like nothing when stopping18:07
Mister_Magistergstdebug is better18:10
Mister_Magisteruseful info18:10
mal"FAILED to allocate omx component ''"18:25
malthat suggests something wrong in adaptation side, maybe some firmware loading failed or some symlink is missing18:28
malMister_Magister: ^18:33
Mister_Magisternot sure what that could be mal18:34
malcheck dmesg and journal for any signs of firmware loading18:34
malI assume that older device so maybe also the xml symlink in /etc/18:35
Mister_Magisterit is older yeah18:36
Mister_Magistermal: well /etc didn't change in 3years18:37
malso it worked before 3.4.0?18:38
malwhere is the adaptation repo for that?18:38
Mister_Magistergot (semi) same device on 3.3 and its fine18:38
T42<b100dian> Ok, set selinux=1, backed out LD_PRELOAD-ing selinux_stubs, copied vendor_file_contexts to file_contexts and precompiled_sepolicy to policy.30, now it's radiosilence about *servicemanager crashes, but I assume they just don't start (not in ps -ef) and droid-hal-init fails running atrace etc:
Mister_Magistermal: can't find anything in dmesg
malMister_Magister: how about journal18:47
Mister_Magisterwaaait [    1.791679]    1.791679,1]   No soundcards found.18:48
mal@b100dian do you have the ld.config things (assuming your device needs those) and this line in spec
Mister_Magistershould it be like that18:48
malMister_Magister: I think that can be normal18:49
Mister_Magisterye audio work18:49
T42<b100dian> I have /usr/libexec/droid-hybris/system/etc/ld.config.29.txt  with added `dir.system = /usr/libexec/droid-hybris/system/bin/` and that line in spec yes18:50
Mister_Magistermal: lemme correct myself prevous dmesg wasn't from root
mal@b100dian just to be sure, do you have /system/etc/ld.config.29.txt ?18:53
T42<b100dian> mal: just checked, yes18:53
mal@b100dian is the ld.config.29.txt mounted over that i.e. do you have the systemd mount service18:53
T42<b100dian> you mean `/dev/sda32 on /system/etc/ld.config.29.txt type f2fs` (line from mount | grep ldconfig)18:55
Mister_Magistermal: and here's journal also couldn't find anything
Mister_Magistermal: any idea?19:33
malMister_Magister: try removing the gst cache from $HOME/.cache/gstreamer-1.0/ and then try to check GST_DEBUG and logcat19:36
Mister_Magistermal: gst_debug is same thing same is logcat i tihnk19:39
Mister_Magisteroh i did'nt send logcat19:43
malcan you check the permissions for /dev/video*19:45
maland do you have some symlinks in /dev/video/19:45
malMister_Magister: just wondering what would happen if you change also those audio groups to camera, although there must have been a reason for the audio change19:49
Mister_Magistermy 5z has camera not audio but it doesn't have 3.4…19:49
malMister_Magister: those rules are in
Mister_Magisterits like 5yo or older file it could be a typo19:51
malmaybe change on device the group and then reboot and see if anything changes19:51
Mister_Magisteron it19:52
Mister_Magistermal: nailed it19:54
Mister_Magisterthat was the issue19:54
malmake sure also playback works in gallery19:54
Mister_Magisterit does19:54
Mister_Magisterwell camera still spazzes out after taking photo19:54
malbut at least it should be better now19:55
malalso check logcat when playing in gallery to be sure it uses hw codecs19:55
Mister_Magistermal: i mean it goes away pretty easy yeah19:57
Mister_Magister heresthe logcat as i'm too dumb to know if it uses hw or not19:59
Mister_Magisteri think it uses19:59
malthat seems to be showing video recording now playback, maybe20:04
mal*not playbakc20:05
Mister_Magisteroh… there could be both but i was focusing on recording yeah20:05
Mister_Magisteromxcodec so i think hw…?20:06
Mister_Magistergotta ask abranson later about how to get capabalities from gstdroid20:07
malI don't see anything about h264 decoding in that20:07
maljust in case remove the gst cache like I mentioned earlier and try playback again20:08
Mister_Magisterthere is this20:09
malyes, that seems correct now20:09
Mister_Magisterare we doing something about pictures spazzing out (of which i had nothing in GST_DEBUG) or…20:10
malmaybe not now, that is not so critical issue, let's see some other time20:11
maldid that happen also before 3.4?20:11
Mister_Magistermal: okay i'm fine with that pics are semi working, not perfect but working :) i'll build 3.4 image and release to users, and hop on to fixing another phone or porting hybris1720:12
Mister_Magisterthanks a ton though!20:12
malhmm, I remember there being some option somewhere for older devices with some issues20:13
malMister_Magister: add a new file to /var/lib/environment/nemo/ (similar way of naming as the existing files) and add just this in that file: QTMULTIMEDIA_VIDEO_TEXTURE_BACKEND_NO_RETAIN_TEXTURES=120:18
Mister_Magisteri was almost about to say it doesn't work but i automatically added it to compositor not nemo xd20:20
malnot sure if there is difference or not20:21
Mister_Magisterwelp that didn't help20:22
Mister_Magisteri would say made it worse but no big difference really20:22
malok, then revert the change if it didn't help20:23
Mister_Magisterafter couple photos now its just flashing wrong frame once20:23
Mister_Magisterit doesn't matter much20:23
Mister_Magisterits like your viewfinder just doesn't work for second20:23
Mister_Magisterit doesn't matter much to me as you can still make photos just fine20:24
Mister_Magisterlets see if advanced camera has same issue20:24
Mister_Magistermal: it doesn't :O20:25
Mister_Magisteri take it back20:25
piggzcos....its more advanced ;)20:25
Mister_Magisterit does20:25
piggzoh :(20:25
Mister_Magisteryeah the issue is more advanced indeed it doesn't recover20:25
Mister_Magistermal: i'll add that variable back, camera was recovering easier20:26
piggzadv-cam will get some nice additions with the gst-droid in 4.220:26
Mister_Magisteryeah advanced camera doesn't recover, camera sometimes has difficulty too20:28
Mister_Magistermal: to describe issue, after you make photo, it keeps flashing one frame and then viewfinder20:29
malok, quite strange, not sure what could be causing that, is that one frame the one it normally shows for a moment after taking a picture i.e. the preview of the photo20:32
malat least jolla-camera does that20:32
Mister_Magistermal: no its like if you moved phone sideways super fast, advanced camera jsut stays on that20:33
Mister_Magistersince i'm at udev i'm gonna remove those annoying udev rules20:34
Mister_Magisteroh i cant nvm20:35
piggzmal: latte needed the systemdcmdline fix21:00
malpiggz: what fix?21:07
piggzfor the old cgroups21:09
piggzmal: may aswell move all servicers to /usr while im updating!21:13
T42<Алексей %lastname%> Hello, I am porting SFOS (Hybris 17.1) I am getting a black screen. droid-hal-init.service won't start. "can't execute '/ sbin / droid-hal-init': Too many levels of symbolic links"21:22
T42<Алексей %lastname%> I added /usr/libexec/droid-hybris/system/etc/ld.config.29.txt but that didn't solve the problem. Could you help me?21:22
T42<Алексей %lastname%> My journal log
T42<Алексей %lastname%> My ld.config.29.txt
T42<Алексей %lastname%> And why i have error "Too many levels of symbolic links" other servise too?21:22
piggzmal: after running migrate_patterns script ... is it ok to remove the left over pattern?21:26
T42<b100dian> hmm I used to have something like system/vendor linked to /vendor and /vendor linked back to system/vendor, check your rootfs for circular links Алексей21:27
T42<elros34> "system-etc-ld.config.29.txt.mount: What= setting is missing. Refusing". Also looks like you disable audit or am I wrong?21:29
T42<Алексей %lastname%> @elros34 ["system-etc-ld.config.29.txt.mount: What= sett …], yes, i have "# CONFIG_AUDIT is not set" My cofig
T42<elros34> so revert any selinux/audit changes you did in defconfig21:35
T42<b100dian> speaking of audit, I just enabled back selinux after he pointed out that lineage-17.1 would need it and got radio silence from servicemanager(s) - discussion above. Now I am seeing denied messages for droid-hal-init.. :hmm:
T42<b100dian> I enabled audit too, that's why it's so spammy21:39
T42<elros34> I guess audit=0 can be used , I was talking about CONFIG_AUDIT=n which is part of selinux dependency thus disable CONFIG_SELINUX* also21:41
T42<b100dian> Oh, I get it. But in my case I want audit to actually know what's wrong.21:43
T42<b100dian> Other than the fact that audit logs look like an unwanted strace, their ending in permissive=1 means they dont.. apply I guess?21:48
T42<b100dian> *looking21:48
malthose audit messages are probably not critical, you can see at least some android side services starting in there, does logcat work? (/usr/libexec/droid-hybris/system/bin/logcat)21:51
T42<b100dian> no, it doesn't, read error21:53
T42<b100dian> I'm assuming for logcat to work, logd must be running. If I try stracing logd, I get `setuid(1036)                            = -1 EPERM (Operation not permitted)` and "failed to set AID_LOGD"21:54
T42<b100dian> Алексей you could also try strace, maybe you find what circular links you have21:55
T42<b100dian> mal, you're right the messages show droid-hal-init spawning android services, but shouldn't thy also show in process list if they were?21:55
T42<elros34> @b100dian that is only ~35s of log so if droid-hal-init crash later then logcat might not work21:57
T42<Алексей %lastname%> @b100dian [I'm assuming for logcat to work, logd must be …], Ok , I check now21:58
T42<b100dian> @elros34 agreed, and it does crash. here's the before-audit log, sligthly longer (1 minute), which stops right before "droid-hal-init.service: Main process exited, code=exited, status=6/NOTCONFIGURED", and in which you see several services started by droid-hal-init not being able to run.22:01
T42<elros34> try to run logcat before droid-hal-init crash then22:05
mal@b100dian also verify what files you have in /usr/libexec/droid-hybris/system/etc/init/22:08
T42<b100dian> I have "disabled_services.rc, disabled_services_device.rc, ecclist.rc, hybris_extras.rc,            overrides.rc, servicemanager.rc", where 2 of them are from (which are from sagit, 17.1 too)22:15
T42<b100dian> @elros34 I couldn't come up with this idea in 1 month, but that actually worked22:15
T42<b100dian> I have 10k+ lines of 10 seconds of logcat before its gone
T42<b100dian> I should have dumped to a file, that was my terminal limit because I output to screen..22:17
T42<elros34> set limit to inifinity22:19
malthe journal log linked earlier didn't show the crash of droid-hal-init, would be good to see it22:21
T42<b100dian> I don't think it was more than " Main process exited, code=exited, status=6" but let me post a longer boot without audit22:24
malmaybe some messages a bit earlier than that could show something22:26
T42<b100dian> let's see.. beginning of logcat
mal@elros34 this looks interesting in that log "VendorServiceManager: add_service('display.qservice',1) uid=1000 - PERMISSION DENIED"22:34
T42<b100dian> 5 mins of journalctl
T42<b100dian> sorry, I was selecting and scrolling all this time, should have cleared the backbuffer first, only now I am looking into logcat too:)22:35
T42<b100dian> there's an actual audit denied above that line, with permissive=0, and .. audit disabled in cmdline22:36
mal@b100dian can you check "ls -l /dev/mdss_rotator" assuming there is such device22:37
T42<b100dian> there isn't22:37
T42<elros34> yeah a lot of permission denied22:37
T42<b100dian> should I try enforcing=0 in cmdline ..?22:38
maldo you have androidboot.selinux=permissive in kernel commandline, check "cat /proc/cmdline"22:40
T42<b100dian> yes I have it..22:41
malhmm, strange, the log says "permissive=0"22:44
malI mean in logcat in some selinux messages22:44
T42<elros34> can you change mode to 644 here: no idea whether this is relevant but you have 8 failures because of that in journal22:46
T42<b100dian> Sure, next reboot is 644. The entire /proc/cmdline is btw22:47
T42<b100dian> That message was bugging me, you found the cause so fast :+1:22:49
T42<elros34> not so fast, it took me few minutes to figure out it but looks like it's only warning so it shouldnt cause anyy issue22:50
mal@b100dian do you have this file /etc/selinux/minimum/contexts/dbus_contexts22:51
T42<b100dian> Not trying to minimize it, it's just that I had hours and din't find the minutes:)22:51
T42<b100dian> yes mal, it's basically a DTD + "<busconfig>22:52
T42<b100dian> <selinux>22:52
T42<b100dian> </selinux>22:52
T42<b100dian> </busconfig>22:52
T42<b100dian> "22:52
T42<elros34> @b100dian move your /lib/systemd/ dir to /usr/lib/systemd/22:58
T42<elros34> your mnt-vendor-persist.mount have incorrect symlink22:59
T42<b100dian> oh23:00
T42<b100dian> I had the link fixed locally but I think at one point I moved them to etc because they didn't started.. let me do this proper then, thanks for this23:02
T42<elros34> be aware that your sparse/system directory is most likely ignored because /system_root/system is bind mounted to /system23:09
bakulinmhey everyone. I have a (probably) strange question. I need to run sailfish on an arm board, I can run debian for arm64 on it, have source for kernel including drivers, etc. do I still need to port Android on it first and then use HADK guide to run sailfish?23:13
malbakulinm: it is also possible to run sailfish on linux kernel assuming mesa has support for the graphics23:15
bakulinmare there any howtos? where do I start?23:16
malbakulinm: you might want to talk to piggz on this channel for example, he has done a native linux port, you might even be able to use the image he made with some changes23:16
bakulinmthank you, will try23:17
malbakulinm: just as an example of running sailfish on linux kernel that used the image piggz had made for another native linux port23:18
T42<b100dian> new journal (I'd say not much changed) and logcat (if mal or @elros34 you're still around)23:33
T42<b100dian> overlay-service is active now, I tried adding back enforcing=0 to cmdline..23:34
T42<b100dian> mnt-vendor-persist is active now too..23:34
mal@b100dian about the selinux configuration files, did you copy the files from your device or my repo?23:38
T42<b100dian> from a mounted vendor.img - let me check they're the same on the device though23:39
mal@elros34 one bad looking thing in the journal "dbus.service: Main process exited, code=exited, status=1/FAILURE"23:40
T42<b100dian> (they are the same)23:41
T42<b100dian> hmm systemctl status says dbus - active23:41
T42<b100dian> I think it restarts..23:42
T42<ankaos> rpm/dhd/helpers/ —gg output
mal@b100dian I see many dbus related messages in the log, those are probably quite serious issue, but it's quite late here already so more debugging some other time23:45
T42<b100dian> yes, thanks mal, I straced that and I have food for thought
T42<elros34> mal that journal is incomplete23:46
mal@elros34 still dbus failure doesn't look good, there were several of those23:47
T42<ankaos> mal: ı use `since --gg didn't compile gst-droid, do it manually with -b hybris/mw/gst-droid`23:48
T42<ankaos> mal: but I get the same error.23:48
mal@ankaos did you downgrade gst-droid23:49
malas mentioned in the link23:49
T42<ankaos> mal: downgrade `gstreamer1.0-plugins-bad gstreamer1.0-plugins-bad-devel gstreamer1.0-plugins-base gstreamer1.0-plugins-base-devel gstreamer1.0-plugins-good`23:50
T42<elros34> mal: sure you are right but who knows when it start to crash in partial log23:50
mal@ankaos did you even read the link I gave23:50
T42<b100dian> this would be the link to the telegram mesage @ankaos to downgrade gst-droid23:50
mal@ankaos go to hybris/mw/gst-droid and run "git clean -x -f -d" and then "git reset --hard 0.20201104.0" and then check that the common/ folder in there has content, then back to $ANDROID_ROOT and run rpm/dhd/helpers/ -b hybris/mw/gst-droid23:50
T42<ankaos> @mal [go to hybris/mw/gst-droid and run "git clean - …], yea rebuild gst-droid23:52
T42<b100dian> @elros34 I think my journal is not persistent since I've re-built the image, that's why I don't get the first lines. I'll probably post them here tomorrow. Thank you both for the help!23:53
T42<ankaos> mal:
T42<b100dian> Hmm does git work from PlatformSDK for you @ankaos ?23:55
T42<b100dian> >  git: command not found23:55
T42<ankaos> zypper in git23:55
T42<ankaos> @b100dian [>  git: command not found], "git submodule init" this is problem23:57
T42<b100dian> maybe issue that yourself from outside platformsdk, but it is worrying that you'd have no git in here23:57

Generated by 2.17.1 by Marius Gedminas - find it at!