Wednesday, 2021-08-25

T42<duhjokersinhell> i would like to port sailfish os to pixel 3a am i in the right place00:17
T42<duhjokersinhell> how do i start the repo00:24
malwhich android base does it have?01:04
T42<duhjokersinhell> android 9 pie02:03
T42<XAP2P> who knows about xiaomeme ginkgo/willow port?03:02
T42<birdzhang> @XAP2P i'm doing that, something not working yet, like sound and camera03:04
T42<duhjokersinhell> where can i download the HADK? im reading the pdf but cannot find the link just instructions on setting it up03:43
rinigus@duhjokersinhell: you are probably looking for
riniguspiggz: encryption repos moved to sailfishos-open.05:48
riniguspiggz: looks like we are missing
T42<duhjokersinhell> ok ty. is there an updated build guide05:49
rinigusfor aosp9 based? checkout FAQ as well (see this room header for links)05:59
T42<duhjokersinhell> ok i have been reading the pdf and i am lost.06:04
T42<duhjokersinhell> does the platform sdk replace the hadk?06:04
rinigus@duhjokersinhell: no, it doesn't. read hadk and work according to it. when getting lost, ask. but check faq just in case before06:05
rinigusas written last night - /home decrypt scripts have now hwcrypt support as well.
rinigusearly days still, have to adjust decrypt script to be able to respond to hw-backed and recovery passwords in parallel06:08
rinigusthat way user can choose which password to enter...06:08
rinigusalso scrypt bits are missing for password processing. but most critical part - interaction with android hw key handling - has been checked and worked during a boot as well.06:09
T42<duhjokersinhell> oh i think i am starting to understand the hadk is the pdf?06:09
T42<pherjung> yes06:11
T42<duhjokersinhell> ok ty. lol i was confused thinking it was software06:12
T42<elros34> @duhjokersinhell to save you from issues at the beginning from outdated docs read also this:
T42<adampigg> rinigus: i need -test on volla as its not working :/07:04
T42<adampigg> Ironic that it was the fist phone to supporrt ot07:05
rinigus@adampigg: I preinstall sailfish-fpd-community-test as GUI for FP setup. it works better than the official one on tama07:06
T42<adampigg> heh07:06
rinigusbut maybe we should move that repo also to -open07:06
T42<adampigg> something crashes android side on new aarch64 port07:07
T42<adampigg> sure, will move when i get to laptop....also needs fixing, systemd unit is still in /lib07:08
rinigus@adampigg: ouch. for tama it works well...07:08
rinigusbut sony have their own oss fpd implementation on aosp.07:08
rinigusre unit in /lib - we don't have any in fpd-test, right?07:09
T42<adampigg> no, i mean the main pkg07:10
rinigusand the one in fpd proper should be in /usr/lib/systemd/system - as it is expected to be for aarch64 as well07:10
T42<adampigg> unless i installed an old version last night...could have07:11
riniguson tama it is in correct spot. must be old version07:12
piggzrinigus: mal: seen this before?07:40
piggz[D] unknown:0 - bool makePath(const char*, const char*, const char*, QFileDevice::Permissions) /var/lib/sailfish-fpd-community/100000   QFlags(0x1000|0x2000|0x4000)07:40
piggz[D] unknown:0 - void AndroidFP::setGroup(uint32_t, const QString&) 0 "/data/vendor_de/100000/fpdata"07:40
piggzAborted (core dumped)07:40
riniguspiggz: no, unfortunately08:10
riniguspiggz: but I have it under `/data/system/users/100000/fpdata`08:18
piggzrinigus: have you altered fpd-community for that path?08:22
riniguspiggz: not that I remember. let me check08:23
piggzrinigus: pretty sure the one i mentioned is hard coded08:23
riniguspiggz: nope, it pulls sources from old repo (piggz)08:24
rinigusso, it should be grabbing path from android side08:25
riniguspiggz: it is hard coded but has one if statement08:26
riniguspiggz: ^08:27
piggzrinigus: yeah, same issue as before, looking at old source!08:27
riniguspiggz: but I presume it was working for you before with vendor_de path. and for tama I had to use the other one08:28
piggzrinigus: yeah, it worked previously, but that was android 9/armv708:31
piggzive now rebased on los17 aarch6408:31
rinigusfor me it stayed put, but maybe it did change for you.08:32
rinigusflashing los17 and checking where it stores fingerprints?08:33
riniguspiggz: ^08:33
piggzrinigus: looks like it dies in setActiveGroup
riniguspiggz: some null pointer in there. no idea what is it doing. is fingerprint vendor blob or some oss implementation?08:42
piggzi presume vendor blob08:43
piggzjust debugging why its choosing that path08:43
rinigusfor sony we have sources.08:43
riniguspiggz: but maybe it would make sense to check where fp are stored in los. just in case it is a simple fix08:44
rinigusalthough I have no idea how frequently android moves it all around08:44
piggzrinigus: plan b ... ask erfan and notkit if fp works for them on UT :D08:47
riniguspiggz: great plan! assuming that they moved to android 1008:47
riniguspiggz: actually, why did you move to android 10? is there something better on volla with it?08:48
piggzrinigus: i know they are on halium 10 base08:48
piggzrinigus: yeah, its loads more stable, plus, if i was rebasing  to aarch64 anyway, made sense08:48
piggzfor some unknown reason, kernel was leaking on 9, causing OOM every few days08:49
riniguspiggz: I see - good reasons.08:50
T42<wkming> hello  everyone ,  how to get root permission on salifish os ?09:08
rinigus@wkming: in settings/development set password and in terminal use it when asked by `devel-su`09:17
T42<XAP2P> oh :D (re @birdzhang: @XAP2P i'm doing tha...)09:49
T42<wkming> thank you (re @SailfishFreenodeIRCBridgeBot: <rinigus>@wkming: in...)09:59
piggzrinigus: well, learned something new10:34
piggzi didnt know logcat now filtered messages based on user ... i was running logcat wondering why i wasnt seeing messages, runs as root and there they are!10:34
mighty17[m]`/home/mighty/hadk/hybris/mw/libhybris/libhybris/hybris/tests/test_common.cpp:142: undefined reference to `hwc2_compat_device_on_hotplug'` any ideas why it breaks?10:52
mighty17[m]i think im supposed to build libhybris with the `rpm/dhd/helpers/` as external/libhybris was missing when i cloned it with repo10:55
mighty17[m]oh nvm found it in hadk-faq10:58
mighty17[m]`error: Failed build dependencies: pkgconfig(droidmedia) is needed by gstreamer1.0-droid-0.20210820.0-1.armv7hl`12:53
mighty17[m]how do i fix this?12:54
mighty17[m]same thing happens for gmp droid13:10
piggzmighty17[m]: build/package droidmedia13:14
T42<edp_17> mighty17: I was told to use these commits: droidmedia: 9450a66a133ffa4df4af5f1d2af5b09ff794606d13:18
T42<edp_17> gst-droid: 364c13e3f6b3d99a87b58beb526bd13f377ce6f413:18
T42<edp_17> gmp-droid: b61b740987a9880fccf5401220644c7dcf184be213:18
T42<edp_17> For me all worked fine.13:18
mighty17[m]building droidmedia failed, I'll give that commit a go13:18
mighty17[m] piggz13:20
piggzmighty17[m]: you are not following the hadk13:21
mighty17[m]im still on hadk 3.4 due to testing out new kernel and stuff before updating to 4.x13:21
piggzdroidmedia is built in the ubuntu sdk (for android)13:22
piggzthen, you package all with -gg13:22
mighty17[m]3.4's hadk doesnt tell me to build droidmedia*13:22
mighty17[m]oh derp13:23
mighty17[m]`make -j$(nproc --all) hybris-hal droidmedia` was already done before13:23
mighty17[m]wtf its rebuilding now?? im sorry something must be rly broken on my machine13:29
mighty17[m]`Problem: geoclue-provider-hybris-hal-0.2.31-1.armv7hl conflicts with geoclue-provider-hybris-binder provided by geoclue-provider-hybris-binder-0.2.31-1.armv7hl` ??14:48
mighty17[m] * piggz: yup built droidmedia acc to hadk still the same issue15:51
mighty17[m] i had to follow steps from here for gst-droid15:51
mighty17[m]but no clues about gmp-droid15:51
T42<elros34> if you are building for old sfos release then usually you can't just use latest versions for everything (gmp-droid, gst-droid, droidmedia, droid-hal/config submodules and maybe others)15:59
mighty17[m]welp can i go back to the commit?16:00
mighty17[m]as the older base i had was cm13 so i cannot copy over the working folders from there to los15.116:00
T42<elros34> you can either manually checkout to older version then build package with offline option or apply this and then you can specify commit or tag you want to build16:02
mighty17[m]oh thats pretty neat!16:05
mighty17[m]is there a way i can know commit is of what sfos version? like with branches or do i need to check all commits16:06
T42<elros34> I do not think you can use branches, maybe only for some packages so better either use your cm13 base droid-local-repo as reference of 3.4.0 changelog from sfos forum.16:09
mighty17[m] seems to have worked :D16:15
T42<elros34> 3.4.0 changelog version is few commits older, that is why I do not recommended branches but it's up to you16:19
mighty17[m]`Unable to find pattern: Jolla Configuration espresso3g`uh oh16:27
mighty17[m]well why does it complain about patterns on .416:30
T42<edp_17> @elros34 : Hi. I have a question for you. I've found a newer kernel (3.12) for the i9100 but that kernel only works with Android 4.3 (Jelly Bean - CM10.2). My current port uses the original kernel (3.0) with CM12.1 base. Does it worth to try using the newer kernel? If yes, will it work with that cm12.1 base or I should use cm10.2?16:32
mighty17[m]s2 has 3.12 kernel wow16:33
T42<elros34> no idea whether is worth or whether it will work out of the box. If you have any issues with current kernel then sure it's worth to try. How can cm10 have newer kernel than cm12?16:35
mighty17[m]seems like 3.12 is heavily modified for cm1016:37
T42<elros34> nice version, IIRC I have 3.3 for one device:)16:37
T42<elros34> remember that nobody use hybris-10 and probably only one insane hybris-1116:39
mighty17[m]@elros34 Unable to find pattern: Jolla Configuration espresso3g , i feel like to give up on this xD16:40
T42<edp_17> Yeah, the guy who ported kernel 3.12 has modified cm10.2 to make it work with that kernel.16:40
T42<edp_17> I've installed that kernel for los14.1 but didn't start. It booted but stuck at the screen after the boot logo. However, when I installed a cm10.2 rom, it works well with that kernel.16:42
T42<elros34> @mighty17[m] really? then maybe you should build 4.1.0 and avoid such a issues. Obviously its fixable, just a matter of providing logs and uploading sources16:42
mighty17[m]i mean i know for a fact that 3.4 with its patterns works, but well new android new kernel then lets just use new hadk16:42
T42<edp_17> That's why I asked. Perhaps first I would need to make cm12.1 work with that kernel, then it could be used for sfos as well.16:43
mighty17[m]"need to make cm12.1 work with that kernel" have fun with android16:44
mighty17[m]im still waiting for sailfish + mainline kenrel16:44
T42<edp_17> Haha. That was a rethorical sentence. :-)16:45
T42<b100dian> But isnt hardware lacking proper drivers preventing that? The vebdor blobs with binder apis are like a new api surface for crippled drivers. I know i fought to drive a vibrator and its not fun. The drivers in question wouldnt pass my review at work, even less so linux reviews. So we get the hardware but cannot use it without provided crutches17:45
T42<b100dian> *vendor17:45
mighty17[m]"hardware lacking proper drivers preventing that" wdym sfos on mainline?18:22
T42<skvorl> You can run SFOS on PinePhone. Is it what you are waiting for?) (re @SailfishFreenodeIRCBridgeBot: <mighty17[m]>im stil...)18:39
malmighty17[m]: sfos can run even on qcom devices using mainline kernel, not really good enough for releases but UI works18:41
rinigusfrom experimenting with the systemd-ask-password - looks like Lipstick has some support for it. although, it doesn't really send anything back and just states that the password is incorrect18:56
rinigusI guess, half-baked feature in 4.1 SFOS18:56
T42<edp_17> I am still puzzled how the drivers of a newer kernel can work with a device hardware that designed for older kernel. I expect if this was pissible for an android version, it should be possible for another version too.19:52
T42<XAP2P> do you have test builds? well sooooo interesting to see (re @birdzhang: @XAP2P i'm doing tha...)20:00

Generated by 2.17.1 by Marius Gedminas - find it at!