Wednesday, 2021-07-21

T42<max_simon7> :
rinigusb100dian great that you got it running. Completely forgot that we have different types of images :). elros34, good catch05:31
*** amccarthy_ is now known as amccarthy07:11
T42<amyosx> hey, is the hadk accurate for hybris-17.1?07:14
T42<amyosx> im getting an error07:15
T42<amyosx> FAILED: ninja: 'libhwc2_compat_layer', needed by 'hybris-hal', missing and no known rule to make it07:15
T42<edp_17> @elros34 : I've rebuilt droid-hal and re-ran the 'rpm/dhd/helpers/ -o' command but it failed again with the same message.07:50
T42<edp_17> Then I realised that I needed to update pulseaudio-modules-droid.07:50
T42<edp_17> After that I was able to build pulseaudio-modules-droid. 😊07:51
mal@amyosx you need to clone libhybris to correct place, that part is mentioned in the hybris-16.0 section of that page09:38
malalso that mentions patches you need to apply before building09:38
T42<elros34> @edp_17 ah offline builds that e10:34
T42<elros34> xplain why pulseaudio wasn't updated automatically10:34
T42<edp_17> As didn't want some modules get updated I used the switch -o. Now, I have went through all modules in hybris/mw and updated the ones I didn't want to keep and built all of them individually.10:36
T42<edp_17> Interestingly when I built dummy_netd individually, it successfully built, but when I ran the 'rpm/dhd/helpers/ -o' command, it failed with "Could not get version for dummy_netd: make sure it is cloned without --depth=1 or clone-depth="1""10:38
T42<edp_17> I didn't expect this as that package has built without any error.10:38
T42<edp_17> Into which pattern should I add gmp-droid (adaptation or configuration)?11:08
T42<edp_17> When tried to build gpm-droid with command 'rpm/dhd/helpers/ --mw=', I got this error:
T42<edp_17> I've seen issues reported about building gmp-droid. Is this one of them? How can I solve it?11:11
T42<Bedjo> Hi, any info for porting project sailfish in oneplus X ? Thanks11:24
T42<Bedjo> The last porting is version 311:24
T42<amyosx> Did (re @SailfishFreenodeIRCBridgeBot: <mal>also that menti...)11:35
rinigus@Bedjo: I stopped working on onyx a while ago, same for kimmoli . so, it waits for someone wishing to spend time and make it work12:16
kimmoliyep. still using onyx, but really old version13:05
T42<elros34> not sure why about dummy_netd but for some reason git describe --tags had to failed. I am wondering whether do you even need it on hybris-14?13:36
T42<elros34> @edp_17 ^13:36
T42<Bedjo> Any info for the last project to continue ? Git link or anything else ? (re @SailfishFreenodeIRCBridgeBot: <rinigus>@Bedjo: I s...)13:39
rinigus@Bedjo: take a look at . Each of the packages has a _service file with the link to github repo13:50
T42<edp_17> Thanks @elros34 . My workaround was completely delete the dummy_netd from mw then clone it again. After that all packages were built and the image has also created.14:08
T42<edp_17> I've installed it on the device. It is booting, sfos is loading up. Now I am testing the functions.14:09
T42<amyosx> this process could probably be extremely simplified imo :P14:12
T42<amyosx> anyway i got an error and the thingy in hadk didnt help14:12
T42<amyosx> RPM build errors:14:12
T42<amyosx>     Empty %files file /home/amy/hadk/dtbo.files14:12
T42<amyosx>     Installed (but unpackaged) file(s) found:14:12
T42<amyosx>    /product_services14:12
T42<elros34> there is whole point about your second error (Installed (but unpackaged) file(s) found) in hadk pdf, use search function14:14
T42<amyosx> i said ive tried that14:14
T42<elros34> then show your changes, it must help14:15
T42<amyosx> can someone send me the output of tree in there environment14:15
T42<amyosx> i might have paths wrong14:15
T42<Bedjo> Thanks mate, i will look on it (re @SailfishFreenodeIRCBridgeBot: <rinigus>@Bedjo: tak...)14:42
deathmistmal: is there any chance you could look at I feel like it's a rather usefuful addition to build_packages as we have to downgrade certain packages to get them building without new additional deps etc.15:11
maldeathmist: ok, need to check15:28
T42<elros34> @deathmist shouldn't --recurse-submodules be added to git reset?15:30
deathmist@elros34 perhaps, I guess at least libhybris uses submodules and is a part of the packages built15:37
malyeah, we have had issues with submodules getting out of sync16:09
*** ggabriel is now known as Guest163717:21
*** ggabriel_ is now known as ggabriel17:21
T42<b100dian> Yay, I booted 4.1.0 built on obs exclusively* \o/18:58
T42<adampigg> \o/ (re @b100dian: Yay, I booted 4.1.0 ...)18:58
T42<b100dian> (now I need to check what pavkages I got wrong:D)18:58
T42<b100dian> mal: do you have time for a quest? only package-jiggling involved, no logs to read20:35
T42<b100dian> I noticed that I have no sound in calls just by upgrading from gst-droid 20201104 to 2021030420:40
T42<b100dian> but there's more, let me know when/if I got your attention..:)20:45
T42<b100dian> anyway, to a more mundane problem, yesterday when thinking about adding tooling/target for 4.1.0 on my local machine, I've created a snapshot with sdk-manage target snapshot xiaomi-tucana-aarch64 xiaomi-tucana-aarch64-4.0.1 and now the yells at me: The 'xiaomi-tucana-aarch64' target has snapshots - refusing to use it directly :D20:54
T42<b100dian> This seems to have solved it: sdk-manage target remove xiaomi-tucana-aarch64-4.0.120:56
mal@b100dian gst-droid should not affect call audio, unless some process is failing, logcat might tell something, or journal22:53
T42<b100dian> ready for the quest then? I have and audioserver enabled to make my ultrasound proximity sensor work22:54
T42<b100dian> That worked alright in 4.0.1 with gst-droid 2020110422:55
malso it worked before?22:55
T42<b100dian> When I upgraded to 20210304, audi calls (microphone) stopped working22:55
malare you sure it's not because you updated to 4.1.022:55
T42<b100dian> _then_22:55
malor are you still in 4.0.1?22:55
T42<b100dian> (no, I did the same upgrade with 4.0.1 but now I want the full 4.1.0 advanced camera functionality:)22:56
T42<b100dian> _then_ if I remove mapplauncherd-booster-silica-qt5-media audio microphone works again22:56
T42<b100dian> so I tested that gst-droid upgrade with 4.0.1 too, but was not 'worried' about it, I downgraded it back22:57
T42<b100dian> now with 4.1.0 I _could_ have used the old version, but found this _other_ workaround.22:57
T42<b100dian> The thing is, there is no audio related code between the two revisions. The media booster explains why would gst-droid be started at boot in a way, but.. what do you make of it?22:58
mallogs are needed22:59
T42<b100dian> darn, I was hoping there's a hunch without them - so you believe logs are useful in which combo?23:00
T42<b100dian> with media booster on and off or with gst-droid downgraded and upgraded?23:00
malof course the broken way23:01
malreboot device, do something where you get broken audio and then get output of "journal -b --no-pager" and /usr/libexec/droid-hybris/system/bin/logcat23:02
malone thing to check is to see if the mini* services are running as they should23:04
T42<b100dian> I should also mention that disabling the audio-hal-2 and audioserver services also works, but no proximity sensor..23:04
malok, so then it could be a race condition23:05
malthat is quite odd proximity sensor if it needs those23:05
T42<b100dian> Breaking it again and getting fresh logs in 1m23:05
malso depending on which services start first at boot it can result in working call audio or not23:06
malI remember seeing something like that on some device23:06
mallogs are probably not needed if disabling those services helps, then it's clear what is causing the issue23:07
T42<b100dian> ok, so it's like a race at startup - one question though23:12
T42<b100dian> is there anything I can do to make pulseaudio droid enable the 'ultrasound' proximity sensor.. sound card?23:12
T42<b100dian> so I can get away without the android services23:13
maldo you have any information about that sensor, sources or config or anything23:13
T42<b100dian> let me look up the config files, I think I saw it on in one of the audio xmls. I also have the whole driver, but it's with all the other sound drivers..23:16
malok, I can have a look tomorrow, it's quite late here already23:17
T42<b100dian> sure, thanks for your input!23:17
*** amccarthy_ is now known as amccarthy23:26
T42<b100dian> here's one reference to ultrasound
T42<b100dian> and another one, both from /vendor/etc/23:28
T42<b100dian> the driver is more or less the elliptic here, but I think this is an android services issue - not driver - just attaching it as a reference23:29

Generated by 2.17.1 by Marius Gedminas - find it at!