| whodat | bitchx-1.3-git + ipx/1.b5 | 00:14 |
|---|---|---|
| T42 | <F1a5H> can sailfish keep wifi active when sleeping? | 00:42 |
| *** Herrie|2 is now known as Herrie | 01:39 | |
| rinigus | morning! on arm32/aosp9/tama port, 4.0.1.48, I have seen that phone display is not always turned on when receiving a call. while it is fine with proximity closed, it is not expected when just on a table. | 07:00 |
| rinigus | frequency is not very high, but when it gets into that "mood", it can happen several times in a row | 07:01 |
| rinigus | logs at https://github.com/sailfishos-sony-tama/main/issues/129 | 07:01 |
| rinigus | looks like mce is failing by not triggering tklock_uiexception_rethink | 07:02 |
| spiiroin | rinigus: "classic" symptoms of stuck p-sensor... have you tried activating on-demand p-sensor use? | 07:10 |
| spiiroin | e.g. https://github.com/mer-hybris/droid-config-sony-nile/blob/master/sparse/etc/mce/60-proximity-sensor-nile.conf | 07:11 |
| spiiroin | ^ makes default be the same as using: mcetool --set-ps-on-demand=enabled | 07:12 |
| rinigus | spiiroin: let me see | 07:16 |
| rinigus | spiiroin: it is not enabled in the port by default. what are the drawbacks of using it? | 07:18 |
| rinigus | spiiroin: OK, looks like this is an issue in some variants of tama and we had discussion regarding it before. will insert the link in the issue | 07:29 |
| spiiroin | rinigus: when p-sensor state needs to be known -> the sensor needs to be ramped up -> introduces delays to certain ops | 07:30 |
| spiiroin | most visible is probably: reacting to power key presses is slower | 07:30 |
| rinigus | spiiroin: just noticed it while switching on display :) | 07:31 |
| spiiroin | it would not need to be like that always - there is a bz ticket for fixing it, but ... it is not exactly a top priority thing. | 07:33 |
| rinigus | spiiroin: well, it makes sense that it is slower. otherwise we have pocket dialing which is even more annoying. fortunately, it seems to be not too frequent even on xz2c, at least according to my testing | 07:36 |
| techgeekster | Hi again. I still have a problem where the Ninja tool not finding the kernel in order to make the boot.img (FAILED: ninja: 'out/target/product/raphael/kernel', needed by 'out/target/product/raphael/boot.img', missing and no known rule to make it). My device manifest: https://pastebin.com/pSkdYhuW and the console log (https://pastebin.com/JDYEW5yt). Does anyone know what could be wrong in my config? | 08:24 |
| *** techgeekster_ is now known as techgeekster | 08:39 | |
| rinigus | techgeekster: from the quick look into console log, looks like you miss kernel sources | 09:06 |
| techgeekster | I have added them in the device manifest. Should I put the sources somewhere else? | 09:08 |
| rinigus | techgeekster: no idea. log asks to put "source repository to kernel/xiaomi/sm8150" | 09:10 |
| rinigus | it may help to build plain lineageos and/or check its instructions. that way you would know where to put kernel sources and can check that your build works | 09:11 |
| rinigus | techgeekster: ^ | 09:11 |
| techgeekster | Oh ok. I'll try that | 09:12 |
| techgeekster | Maybe xiaomi is a bit sneaky with the whole kernel thing. Thanks @rinigus | 09:12 |
| rinigus | yes, it will take a bit of time, but you will be able to see how well your device works on your build. | 09:12 |
| rinigus | you're welcome | 09:13 |
| T42 | <edp_17> mal: The camera on the n7000 drives me crazy! I've managed to make all functions work on the first build that was heavily amended on the device. I also applied the same changes in the sdk and in the second built and the camera is only partial working. The front camera works for pictures and videos but the main camera shows black screen | 10:00 |
| T42 | in picture mode while it works fine in video mode. Plus the video cannot be played in Gallery app. | 10:00 |
| T42 | <edp_17> First I thought this was because of I removed the theaudiosystem-passthrough-dummy-af from the build, so I added it back but it didn't help. | 10:01 |
| T42 | <edp_17> I also use the same jolla-camera-hw.txt file what I am using in the first build. So, I am puzzled wha's wrong. | 10:03 |
| T42 | Chrisme69 was added by: Chrisme69 | 10:06 |
| T42 | <edp_17> mal: This is the jolla-camera-hw.txt: https://paste.ubuntu.com/p/GXk763HjSB/ | 10:10 |
| T42 | <edp_17> and this is the logcat when starting the camera in picture mode: https://paste.ubuntu.com/p/3vbPY8FbrZ/ | 10:10 |
| T42 | <Chrisme69> I have a question; sure that this isn't the right Channel. I'm looking for an unofficial port of sailfish forma nexus 5. I found the link to a file hosting site that doesn't exist anymore (devaamo.fi). Someone knows if this ported roms are available somewhere on the web? | 10:12 |
| T42 | <Chrisme69> Thanks in advance | 10:12 |
| T42 | <edp_17> mal: and the medi_codecs*: https://paste.ubuntu.com/p/QY6gvCdw6W/ | 10:12 |
| T42 | <elros34> @edp_17 I can't find single line related to video decoder/encoder in that logcat | 10:13 |
| T42 | <edp_17> @Chrisme69 : Try this: https://talk.maemo.org/showpost.php?p=1562106&postcount=785 | 10:13 |
| T42 | <edp_17> @elros34 : I think because the camera was in picture mode not in video. | 10:14 |
| T42 | <elros34> I think you should still have plenty of omx or something related in logcat | 10:14 |
| T42 | <edp_17> @Chrisme69 : I also recommend you to read this thread: https://talk.maemo.org/showthread.php?t=96932 | 10:15 |
| T42 | <Chrisme69> @edp_17 [@Chrisme69 : Try this: https://talk.maemo.org/ …], Thanks but I don't manage to connect to talk.maemo anymore | 10:15 |
| T42 | <Chrisme69> I think the server is down | 10:15 |
| T42 | <Chrisme69> Or my browser can't connect | 10:15 |
| T42 | <edp_17> @Chrisme69 [I think the server is down], Don't thinks so, I am on that site and copied the URLs from there. | 10:15 |
| T42 | <Chrisme69> I tried from the PC and from handy bit nothing | 10:16 |
| T42 | <Chrisme69> Maybe there's something with the firewall | 10:17 |
| T42 | <Chrisme69> Not capable to connect | 10:17 |
| T42 | <edp_17> @elros34 [I think you should still have plenty of omx or …], I copied all the logcat output. What I spotted now is if I start the camera in picture mode and get that blank screen, the device gets rebooted after a while. Even if I close the camera app. (I'll try it without starting the camera.) | 10:18 |
| T42 | <edp_17> @Chrisme69 : The site surely is up and running, so there is something on sour system that prevents you connect to it. | 10:19 |
| T42 | <Chrisme69> Thank's Miklos | 10:19 |
| T42 | <Chrisme69> I tried with mobile data and works | 10:19 |
| T42 | <Chrisme69> Thanks a lot | 10:19 |
| T42 | <elros34> @edp_17 you should check whether gst-droid is used at all (output from jolla-camer or GST_DEBUG might be useful) | 10:21 |
| T42 | <edp_17> @Chrisme69 : No problem. 😃 | 10:21 |
| T42 | <Chrisme69> Yess. I'm taking a look on that site. | 10:21 |
| T42 | <Chrisme69> 😃👍 | 10:21 |
| T42 | <edp_17> @elros34 : This logcat is when I started the camera in picture mode, switched to video mode, closed it, restarted in video mode, switched to front camera (video mode) then switched to picture mode (still front camera) and closed it: https://paste.ubuntu.com/p/zpyCNn3zp5/ | 10:23 |
| T42 | <edp_17> I'll get the other outputs too. | 10:23 |
| T42 | <elros34> you can clearly see that there is only audio and hwcomposer logs there | 10:24 |
| T42 | <edp_17> @elros34 : jolla-camera output: https://paste.ubuntu.com/p/4zPwby2vfx/ | 10:26 |
| T42 | <edp_17> Something weird is happening on the device. It became unresponsieve, then lipstick restarted and when I unlock the lock screen I got a screen where the background is blurred and the app drawer is not available. | 10:29 |
| T42 | <edp_17> The 'GST_DEBUG=6 mk-cam-conf 0 /dev/null 2>&1 | grep params_parse | sed -e 's/.*param\s//' | sort -u' command gives me nothing. (Although, this can be because of that weird thing I explained.) I reboot and retry. | 10:30 |
| T42 | <edp_17> @elros34 : GST_DEBUG: https://paste.ubuntu.com/p/K5Kc4nxTYx/ | 10:38 |
| T42 | <elros34> Have you checked all logs for failing services and that you use correct gst-droid version and up to date droidmedia? | 10:41 |
| T42 | <edp_17> My gst-droid in this commit: commit f6a1b484cbbbd77a636cc860f38b5d77241e0a41 (HEAD, tag: 0.20201104.0) | 10:44 |
| T42 | <edp_17> I've added MINIMEDIA_AUDIOPOLICYSERVICE_ENABLE := 1 and AUDIOPOLICYSERVICE_ENABLE := 1 into mer/android/droid/external/droidmedia/env.mk | 10:45 |
| T42 | <edp_17> then rebuilt the kernel (make -j$(nproc --all) hybris-hal droidmedia) and the configs (rpm/dhd/helpers/build_packages.sh -c) and the droidmedia stuff (rpm/dhd/helpers/build_packages.sh -gg -D -o) then built an image (rpm/dhd/helpers/build_packages.sh -i) | 10:45 |
| T42 | <edp_17> I've rebuilt the configs because I added theaudiosystem-passthrough-dummy-af package into patterns-sailfish-device-adaptation-n7000.inc | 10:46 |
| T42 | <elros34> I would suggest to not use -D (do-not-install) switch for droidmedia and gst-droid | 10:50 |
| T42 | <elros34> I guess you probably did not change anything but if you build hybris-hal then you should also package it -d switch | 10:52 |
| T42 | <Chrisme69> @Miklos | 11:02 |
| T42 | <Chrisme69> I surfed that site but it redirects always to that "devaamo.fi" site that exists anymore. | 11:02 |
| T42 | <Chrisme69> Simeone knows where these roms could be hosted? | 11:02 |
| T42 | <edp_17> @Chrisme69 : have you checked the other one I gave you? https://talk.maemo.org/showpost.php?p=1562106&postcount=785 | 11:03 |
| T42 | <Chrisme69> Thank's a lot. Some linked deposits work. | 11:05 |
| T42 | <Chrisme69> Hope I fine something there | 11:05 |
| T42 | <Chrisme69> In love with this OS.... | 11:05 |
| T42 | <Chrisme69> 😀 | 11:05 |
| T42 | <edp_17> @elros34 [I guess you probably did not change anything b …], How do you mean I did not change anything? And what's the command to package hybris-hal? | 11:05 |
| T42 | <edp_17> @Chrisme69 [Thank's a lot. Some linked deposits work.], I know becauce this is my build and hosted by me. 😉 | 11:06 |
| T42 | <edp_17> @elros34 : I thought when I do the mic, that will include all freshly built packages into the zip file. | 11:08 |
| T42 | <elros34> @edp_17 yes mic instlal all packages and nothing more, it doesn't build any package. I don't know what you changed in android part but if you are building that then package it: build_packages --help will tell you how to package android part (droid-hal) | 11:09 |
| T42 | <edp_17> @elros34 : The -d switch is for droid-hal. is this that I need? https://paste.ubuntu.com/p/KspTqh5PyB/ | 11:12 |
| T42 | <edp_17> That can explain why the camera doesn't work on my new build. | 11:13 |
| mal | techgeekster: in case you didn't find the correct kernel path, it's here https://github.com/TingyiChen/device_xiaomi_raphael/blob/lineage-16.0/BoardConfig.mk#L48 | 11:13 |
| T42 | <Chrisme69> @miklos | 11:14 |
| T42 | <Chrisme69> I want to try sfdroid on mybold nexus and see if it works | 11:14 |
| techgeekster | @mal Thank you, will try it asap | 11:14 |
| T42 | <elros34> @edp_17 yes -d switch but as I said if you didn't change anything in android side this is irrelevant. I suggest you to package droid-hal only because you were building hybris-hal | 11:15 |
| mal | @edp_17 do you still have issues with camera, could you try to remove the gst cache from .cache/gstreamer-1.0 I think it contains one file and if it misdetected things first time it might have disabled gst-droid | 11:16 |
| T42 | <edp_17> I see, so any time I build hybris-hal, I need to build droid-hal too? | 11:16 |
| T42 | <elros34> obviouosly, what is the point to build android part and then not package it so it can be included in image? | 11:17 |
| T42 | <edp_17> I though, that will build the kernel and I only need to install that on device. | 11:18 |
| T42 | <elros34> if you only change something small in kernel then sure make hybris-hal or just hybris-boot and flashing kernel is enough. Check droid-hal*rpm packages so you will know what is really packaged there | 11:21 |
| T42 | <edp_17> Okay, thanks! This explains some issues that I had when I changed something in kernel and didn't make effect. Because I didn't rebuild droid-hal. 😃 At least, now I know this. (I think this can be the issue why camera doesn't work on the hammerhead either.) | 11:23 |
| T42 | <edp_17> I'll rebuild droid-hal and create a new image for the n7000 to try. | 11:23 |
| T42 | <edp_17> @elros34 : I have a question. I have double checked what I installed on my first build where the camera does properly work. I rebuilt what I wrote above and only installed droid-config*, droidmedia, gstreamer1.0*, patterns*, pulseaudio-modules-droid-glue*, audioflingerglue* and audiosystem-passthrough-dummy-af*. Plus I flashed the kern | 11:35 |
| T42 | el that I rebuilt with 'make -j$(nproc --all) hybris-hal droidmedia'. I did NOT rebuild and install droid-hal, so in theory I should get the same issues there. Right? | 11:35 |
| T42 | <elros34> the important part for camera is droidmedia and gst-droid so don't focus that much on hybris-hal packaging in that case. Make sure you do not use -D with -g switch and follow mal's advise about cache | 11:39 |
| T42 | <edp_17> I've tried that, removed tha cahce but did help. (I'll remember to not use the -D with -g) | 11:41 |
| deathmist_ | any idea what would cause systemd errors such as "Failed to connect to system bus: No such file or directory" on SFOS 4.0? I ended up updating my hybris-16.0/arm32 base after all and I've got "systemd.legacy_systemd_cgroup_controller=yes" on my cmdline; journal https://pastebin.com/raw/3ubVDpUz | 13:02 |
| deathmist_ | all relevant repos should be under https://github.com/sailfishos-oneplus5 | 13:08 |
| calebccff | deathmist_ apparently that cmdline hack is fixed with: https://github.com/mer-hybris/hybris-patches/commit/54008fe9fc67c13eff6d3d48f78bb268af7883be | 13:18 |
| deathmist_ | I had the same errors spammed even without it appended to cmdline, I added it just in case | 13:23 |
| T42 | <elros34> @deathmist_ your paste don't work | 13:23 |
| deathmist_ | @elros34 how about https://dpaste.org/9oXa/slim ? the previous link still works fine for me | 13:26 |
| T42 | <elros34> that one works | 13:26 |
| rinigus | deathmist_: cmd line fix is needed if you have kernel <4.5 or /dev/cg2_bpf is mounted by android | 13:26 |
| *** Herrie|2 is now known as Herrie | 19:42 | |
| *** Mister_Magister_ is now known as Mister_Magister | 19:42 | |
| *** lynxis_ is now known as lynxis | 21:24 | |
| T42 | <edp_17> @elros34 : I've re-built qt5-qpa-hwcomposer-plugin from your A31 branch. It has removed the 'isValidDimension: layer handle is NULL' flood from the log. | 23:47 |
| T42 | <edp_17> However, the video recording still doesn't work. The camera app hangs. I don't know what the issue is. Some logs. logcat: https://paste.ubuntu.com/p/W8JB57Vj9D/ | 23:48 |
| T42 | <edp_17> and journalctl: https://paste.ubuntu.com/p/qcN9ZyXPth/ | 23:48 |
| T42 | <edp_17> Do you have any suggestions? | 23:48 |
| T42 | <edp_17> "CameraBase( 2109): mediaserver's remote binder Camera object died" | 23:49 |
| T42 | <edp_17> What's this mediaserver's remote binder or OMX/mediaserver? | 23:50 |
| T42 | <edp_17> oh, and GST_DEBUG: https://paste.ubuntu.com/p/JxSmhHspjf/ | 23:52 |
| T42 | <elros34> did you try connecting external display? This errors looks different then errors in your previous logs. Does video playback with gst-droid works? From logs it's not clear so do you have mini* services running? | 23:59 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!