| T42 | <nc1x72> Something must have gone wrong. | 11:46 |
|---|---|---|
| T42 | <nc1x72> I made the changes you suggested. It compiled fine but now the phone display turns off few seconds after SailfishOS splash screen. | 11:46 |
| T42 | <nc1x72> | 11:46 |
| T42 | <nc1x72> I have also removed everything, repo sync everything and compiled a fresh rootfs = same problem | 11:46 |
| mal | hmm | 11:48 |
| mal | go to folder rpm/dhd and there run "git reflog" | 11:50 |
| T42 | <nc1x72> Ok but wouldn’t that be the same as removing the whole hadk folder and repo syncing from scratch? Because I already deleted hadk folder and did everything from the beginning | 11:53 |
| T42 | <nc1x72> Oh sorry reflog | 11:54 |
| T42 | <nc1x72> You want log | 11:54 |
| mal | there is pretty much never need to start from beginning, it's just waste of time | 11:55 |
| mal | oh, you removed that dhd/rpm folder from earlier build? | 11:56 |
| T42 | <nc1x72> yep | 11:57 |
| mal | I just want to see what difference there is between the earlier build and latest build | 11:57 |
| T42 | <nc1x72> removed everything | 11:57 |
| T42 | <nc1x72> nonta72@localhost:~/hadk/rpm/dhd$ git reflog | 11:57 |
| T42 | <nc1x72> 732c329 (HEAD, m/hybris-21.0) HEAD@{0}: | 11:57 |
| T42 | <nc1x72> nonta72@localhost:~/hadk/rpm/dhd$ | 11:57 |
| mal | you should not do that, it's just huge waste of time | 11:58 |
| mal | a moment, I did some test build and found some issues, check what is causing those | 12:05 |
| T42 | <nc1x72> You did test build on fp5 repos? Or spacewar? | 12:07 |
| mal | fp5, it seems the latest rpm/dhd submodule has a bug, making a test now with a possible fix | 12:09 |
| mal | @nc1x72 go to rpm/dhd and there run "git fetch origin" and then "git reset --hard origin/linkerconfig" | 12:16 |
| mal | then back to ANDROID_ROOT and repackage droid-hal rpms with "rpm/dhd/helpers/build_packages.sh -d" and then build a new image with "rpm/dhd/helpers/build_packages.sh -i" | 12:17 |
| mal | @nc1x72 and just for future, instead of removing all hadk folder it's enough to just remove the out/ folder from there, that is where the whole output of android side build goes | 12:32 |
| mal | and the need to remove out/ is very rare | 12:32 |
| T42 | <nc1x72> Ok noted | 12:48 |
| T42 | <nc1x72> Ok that worked. Now boots and audio is working. | 14:53 |
| T42 | <nc1x72> | 14:53 |
| T42 | <nc1x72> However, it has broken camera which now gets stuck on a black screen and not responding | 14:53 |
| T42 | <nc1x72> Some logs : https://paste.opensuse.org/pastes/a5b9a151e91e | 15:08 |
| T42 | <nc1x72> | 15:08 |
| T42 | <nc1x72> But I doubt it's due to SELinux denials | 15:08 |
| mal | those can be ignored | 15:12 |
| mal | show logcat when you try to use camera | 15:12 |
| mal | you could try removing /home/defaultuser/.cache/gstreamer* on device and try again | 15:16 |
| T42 | <nc1x72> logcat : https://paste.opensuse.org/pastes/9116895abeb4 | 15:20 |
| T42 | <nc1x72> Removing gstreamer cache didn’t work | 15:20 |
| T42 | <nc1x72> android.hardware.camera.provider@2.4.so is in /vendor/lib (and lib64) | 15:23 |
| mal | wait, are minisfservice and minimediaservice process running? | 16:00 |
| T42 | <nc1x72> minimediaservice yes, but not minisfservice | 16:06 |
| T42 | <nc1x72> [root@phone1 defaultuser]# pgrep minisfservice | 16:07 |
| T42 | <nc1x72> [root@phone1 defaultuser]# pgrep minimediaservice | 16:07 |
| T42 | <nc1x72> 2288 | 16:07 |
| T42 | <nc1x72> Wait, is it on the android side? | 16:09 |
| mal | @nc1x72 for testing you could add symlink for the /vendor/lib64/android.hardware.camera.provider@2.4.so in /usr/libexec/droid-hybris/system/lib64/ | 17:01 |
| T42 | <nc1x72> android.hardware.camera.provider@2.4.so is also in /usr/libexec/droid-hybris/system/lib64/ already | 18:59 |
| T42 | <nc1x72> I didn’t put it there | 19:00 |
| mal | ok | 19:01 |
| mal | it seems that one change in linkerconfig is not good for android 14 | 19:03 |
| T42 | <nc1x72> Ok | 19:13 |
| mal | you could try to symlink it to /system/lib64/ | 19:21 |
| T42 | <nc1x72> Yes that actually worked! | 19:41 |
| T42 | <nc1x72> video recorder is broken (that bug was already there before the new linkerconfig patches tho). | 19:42 |
| T42 | <nc1x72> Should I make changes on my repos regarding this symlink or wait for a fix on linkerconfig? | 19:42 |
| mal | I'll try to fix it, I just used the patch from newer android bases and it seems there are issue with it in android 14 base, I didn't have time to test it on fp5 yet | 19:43 |
| mal | hmm, how does video recording fail? | 19:44 |
| mal | show logcat when that happens | 19:45 |
| mal | @nc1x72 did camera work before the linkerconfig changes? | 19:52 |
| T42 | <nc1x72> Camera worked before yes but not for recording videos. In other terms, it's back to the state it was before linkerconfig changes: I can open it and take pictures. I can even switch to video recorder mode. When I click on video recorder button, it starts recording. When I click to stop, camera app hangs. | 19:57 |
| T42 | <nc1x72> | 19:57 |
| T42 | <nc1x72> Here's the logs : https://paste.opensuse.org/pastes/9c3d3efbf7e6 | 19:57 |
| T42 | <nc1x72> | 19:57 |
| T42 | <nc1x72> The line CANNOT LINK EXECUTABLE "/usr/libexec/droid-hybris/system/bin/minisfservice" was before the symlink and it was spamming a lot, I removed all the lines from the logs to keep just 3. Same for thes lines : "Codec2Buffer: GraphicMetadataBuffer does not work in 32+64 ..." and "QC2Comp : [avcE_15] Returning work with no/empty ..." | 19:57 |
| mal | what does "getprop debug.stagefright.c2inputsurface" show on your device | 20:06 |
| T42 | <nc1x72> Empty | 20:07 |
| mal | try "setprop debug.stagefright.c2inputsurface -1" and then try recording | 20:08 |
| T42 | <nc1x72> Still hangs | 20:11 |
| mal | same messages in logcat? | 20:11 |
| T42 | <nc1x72> Yep : https://paste.opensuse.org/pastes/e4f967fc2ba1 | 20:14 |
| mal | I don't see those GraphicMetadataBuffer errors anymore | 20:14 |
| T42 | <nc1x72> I missed those ... | 20:19 |
| T42 | <nc1x72> Video recording works with front camera | 20:20 |
| mal | ok, just a moment | 20:21 |
| mal | I think you need to figure out what it the largest supported video resolution that works, I suspect maybe 4k resolution, so try the first two lines https://github.com/mer-hybris/droid-config-f5121/blob/master/sparse/etc/dconf/db/vendor.d/jolla-camera-hw.txt#L1 but resolution value of 4160x3120 if it fails the try lower values | 20:29 |
| mal | or maybe 3840x2160 | 20:30 |
| T42 | <nc1x72> I'm assuming just this line ? https://github.com/mer-hybris/droid-config-f5121/blob/508c0c9b5cf69649cabb43a425184e92a8f72651/sparse/etc/dconf/db/vendor.d/jolla-camera-hw.txt#L2 | 20:31 |
| mal | yes, you have the file already | 20:31 |
| mal | after editing the dconf file on device run dconf update and restart camera app | 20:31 |
| mal | "dconf update" | 20:31 |
| T42 | <nc1x72> Yes, but the file doesn't have the other settings like https://github.com/mer-hybris/droid-config-f5121/blob/master/sparse/etc/dconf/db/vendor.d/jolla-camera-hw.txt#L4-L54 that's why I asked. | 20:38 |
| T42 | <nc1x72> | 20:38 |
| T42 | <nc1x72> Anyway, running dconf update returns "(dconf:36174): GLib-GIO-CRITICAL **: 21:33:28.526: g_dbus_connection_emit_signal: assertion 'object_path != NULL && g_variant_is_object_path (object_path)' failed" | 20:38 |
| T42 | <nc1x72> | 20:38 |
| T42 | <nc1x72> I restarted the phone, still hangs | 20:38 |
| T42 | <nc1x72> I chose 1920x1080 | 20:38 |
| mal | the setprop doesn't remain across reboots at moment | 20:38 |
| mal | so remember to set that again | 20:39 |
| T42 | <nc1x72> Oh yes, I forgot, I should have set it in droid-hal-early-init script | 20:39 |
| mal | or patched in to build.prop in /system/ | 20:39 |
| mal | either way is fine | 20:40 |
| T42 | <nc1x72> Ok fixed after setting setorio | 20:41 |
| T42 | <nc1x72> setprop* | 20:42 |
| T42 | <nc1x72> I'm gonna go with droid-hal-early-init script | 20:42 |
| mal | you should find what is the best value to use for recording, some standard resolution | 20:42 |
| T42 | <nc1x72> Indeed | 20:42 |
| T42 | <nc1x72> I'll try that now and then move to vibrator fixing maybe tomorrow | 20:43 |
| mal | 3840x2160 is a good guess for first tests, that seems to be the usual 4k resolution, I think fp5 can do 4k | 20:43 |
| T42 | <nc1x72> Thank you mal! | 20:43 |
| T42 | <nc1x72> Spacewar can do 4k too (at least on Android) | 20:44 |
| mal | I wonder if you need the same way to handle vibrator that I use on fp5, depends on the kernel driver | 20:44 |
| T42 | <nc1x72> I knew vibrator was going to be an issue, that's why I left it alone as the final boss | 20:44 |
| mal | well if it's the same as fp5, it's just tiny change to one spec file and patterns and build one package | 20:46 |
| T42 | <nc1x72> On the first attempts, I used the same package you use on fp5. It resulted in constant, strong vibration. After switching to native vibrator as you suggested earlier, it simply stopped working (no vibration at all), which is fine by me for now because the constant vibration almost broke the motor. Anyway, I'll dig deeper later. | 20:49 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!