Sunday, 2022-10-02

budrzdoing a Google Pixel 3a XL build and got stuck (again) in section 7.2.113:17
budrzoutput of rpm/dhd/helpers/ --droid-hal :
budrzkernel build log:
budrzsome of my other files and patches:
malbudrz: you need to apply this patch in rpm/dhd folder
malthen try again13:21
budrzmal: that worked but I got some errors related to 7.2.2 on "Installed (but unpackaged) file(s) found" but I'll try and fix it13:31
budrzthanks for the patch13:31
malread the straggler_files part of hadk pdf13:33
budrzI will13:36
budrzI have a  ".inc" file  instead of ".yaml"13:50
budrzwould I just add "Requires: droid-hal-bonito-detritus"13:50
budrzmal: trying to follow 7.2.2, I made these changes:
budrzbut it ended with this error:
budrzHere is the full log file:
budrzperhaps has something to do with test suites that need to run but can't?16:50
voidanix[m]@budrz check hadk-hot, it has this specifically:
budrz@voidanix[m], I'll check it out17:16
poetasterpiggz, damn those stop releases!17:41
piggzpoetaster: what other devices were you referring to which had video issues?17:42
poetasterI think both the 10ii and the 10iii. sec, I'll check.17:42
T42<elros34> is 4.4.0.x -> upgrade really needed before upgrading to 4.5.0 in future or it' is not necessary?17:45
malprobably any 4.4.0.x is ok17:46
budrz @voidanix[m] that worked. thanks!17:46
malpoetaster: does x10 II also have camera issues?17:46
T42<elros34> ok that sounds reasonable17:46
poetastermal, searching. I thought so, but ....17:47
malafaik x10 III has some known issues but x10 II should work17:47
poetasterI've only seen the error on the Volla/GS290 and the 10ii has no issues with the camera (other than being crappy for sony standards).17:48
malnot sure if x10 III and volla issues are related or not17:48
malwhich kernel does that gs290 have?17:49
poetasterLinux VollaPhone 4.9.248+ #37 SMP PREEMPT17:49
malok, different kernel version so it's not that17:50
malI was just thinking if it could be some kernel issue17:51
poetasterfor sony, 10iii, someone mentioned:
T42<elros34> @voidanix[m] did you figure out your image building issue?17:54
poetasterthe volla and sony have this in common: Unable to generate thumbnail image from: /home/defaultuser/Videos/Camera/20221002_195402.mp4[W] unknown:0 - QImage::scaled: Image is a null image17:58
poetasterJun 28 09:44:21 Xperia10III [9359]: [W] unknown:0 - QImage::scaled: Image is a null image17:58
malis that for video that was recorded on the device? is the video playing?17:59
poetasterthat video never completes recording on the volla. sounds same vrom the 10iii. They wrote:17:59
poetaster"When I try to record a video with the native camera app, the frame freezes and the app crashes. I can open the app again, but the image stays black as if no camera were detected."17:59
T42<elros34> I wouldn't worry about that QImage::scaled too much, I saw something similar on totally different device/port18:01
T42<elros34> I can be error from thumbnail/gallery18:01
poetasteryeah, I don't think it's material either. The forum link above, he has: CameraBin error: “Could not initialize supporting library.”18:02
T42<Verevka86> + Xiaomi mi6 (hybris17.1) and Poco X3 Pro (hybris18.1.)18:04
T42<Verevka86> while camera recording works in 32 bit version on xiaomi mi618:04
mal@Verevka86 does video recording fail on those?18:04
T42<Verevka86> Yes (re @SailfishFreenodeIRCBridgeBot: <mal>@Verevka86 does...)18:05
malhybris-18.1 is missing the 32-bit codec fixes, I will push those18:05
malnot sure why 17.1 would fail though18:05
poetasterpiggz, vollas on 17 or?18:07
piggzpoetaster: yeah18:08
malhmm, why would that fail18:08
piggzwe've been through this before ..... one moment18:08
piggzi think my debugging found it stuck here
piggzit was nt getting any frames18:09
T42<Verevka86> It seems to me that the problem is not in the version, but in bitness (re @SailfishFreenodeIRCBridgeBot: <mal>not sure why 17...)18:09
malbut 17.1 has a fix for bitness compatibility, unless those libs are not loaded?18:10
malsomeone needs to strace18:11
malprobably jolla-camera for example18:11
maland check from where stagefright libs are loaded18:12
poetasterthis is fun.18:16
poetasterit's not the kind of m movie I had in mind (hee, hee)18:17
poetastermal, where would you like that strace.18:23
poetastermal, and what bits18:23
poetastermal, library loads stagefright there are four from :/usr/libexec/droid-hybris/system/lib64/18:25", O_RDONLY|O_18:25",18:25", O18:25", O18:25
poetasterpiggz, a lot of: recvmsg(3, {msg_namelen=0}, MSG_DONTWAIT|MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable)18:26
poetasterpiggz, not from strace but beyond strace -o .... moov atom not found?18:30
budrzNow on section 8.4 but there seems to be file conflicts even though I made the following changes:
budrzand ran sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper --plus-repo $ANDROID_ROOT/droid-local-repo/$DEVICE in droid-config-$DEVICE'18:57
budrzhere is the log file:
T42<elros34> did you build package after making changes to it?18:59
malbudrz: why do you use patches for those droid* repos?19:00
budrzmal: just in case I make a mistake I can just apply the patch when I start over19:01
budrzplus to see the differences19:02
budrzT42: after I ran sb2 ... command I ran --mic19:04
T42<elros34> but you made changes to droid-config, did you build droid-config rpm after?19:05
budrzno I didn't19:05
T42<elros34> everything is packaged and installed during mic image creation. If you change something then you must build related package19:06
T42<Verevka86> Its work perfect 👍 (re @SailfishFreenodeIRCBridgeBot: <mal>https://github....)19:13
budrzT42: I re-ran rpm/dhd/helpers/ --configs but ended up with:
budrzI am trying to follow:
T42<elros34> add these before '%include droid-configs-device/'19:22
mal@Verevka86 so 17.1 still has issues though?19:28
voidanix[m]@elros34 didn't fix yesterday's issue but will try again tomorrow on another host distro19:29
T42<Verevka86> can't check now (re @SailfishFreenodeIRCBridgeBot: <mal>@Verevka86 so 1...)19:29
malbut good that 18.1 now works19:32
T42<elros34> @voidanix[m] I have read changelog and I think this can be related to changes in mic19:32
budrzT42: placing it before and re-running --configs worked. thanks!19:34
malbudrz: btw, don't highlight T42, use the nick after that, for example @elros3419:36
T42<elros34> @voidanix[m] one change is that --verbose added to mic should print what you would expect from set -x but erroronfail handling could can cause your issue now19:36
budrzmal: ok, I didn't know19:37
malyeah, that telegram tunnel bot is a bit unusual19:38
budrzit is19:40
budrzalso, I will clean up and remove any unneccesary "patch" files that I have when all is seid and done... I know it's kind of odd but it just helps me remember what I did19:40
malbudrz: just using normal git commits might be easier19:41
maland pushing the repo to github or gitlab19:41
budrzok, I will try that19:42
budrzI kind of new to all of this, as you can tell19:46
voidanix[m]@elros34 afaiu if `--erroronfail` is not specified then it should not error out like that19:58
voidanix[m]idk python but there is a bit of a sussy line in that commit19:59
T42<elros34> but it is so it fails as expected, add --verbose to mic then you will now why or || true to some commands in this script20:00
voidanix[m]will do tomorrow, thanks for looking into this :)20:01
T42<elros34> @NotKit thanks to your hidl_compat audio works on samsung zerofltexx20:05
malwhat hidl_compat?20:43
T42<elros34> this one: for devices without 64bit audio lib20:44

Generated by 2.17.1 by Marius Gedminas - find it at!