T42_ | <elros34> makes sense now, I see this new repo now | 00:03 |
---|---|---|
mal | after next release we can build fewer packages in our common repo on community OBS | 00:04 |
T42_ | <elros34> I see qtwayland was updated to 5.6, which breaks my nested compositor but this is nice improvement. 5.6 includes support for QWaylandOutput | 00:11 |
mal | yes, it was updated | 00:36 |
rinigus | piggz: did you realize that slava submitted to chum directly, without going through testing. so we have testing and chum out of sync. | 07:16 |
piggz | rinigus: oh | 07:16 |
rinigus | wrote a longish response to him, but SR got accepted meanwhile :) | 07:16 |
piggz | neeed to keep an eye on that | 07:16 |
rinigus | I guess we will have to sync now between testing and chum | 07:16 |
rinigus | as for actdead - I have POC working. now will have to make it properly | 07:17 |
piggz | rinigus: whats the actdead concept ... i fixed actdead mode on volla last night, except for the ask-password .... had to inhibit the volla charging program service | 07:52 |
T42_ | <oMinimalist> http://fars.ee/PuAO | 07:57 |
T42_ | <oMinimalist> conflicts problem | 07:57 |
rinigus | piggz: as there are many services that are wishing to get /home mount, I am mounting some tmp dir to /home in actdead mode | 08:13 |
piggz | rinigus: what does stock do ... surely doesnt mount /home? | 08:14 |
rinigus | it doesn't. but I am not fully sure why it works there. | 08:14 |
rinigus | we have a bit different set of requirements and it seems to me that such fake mount is more generic way of approaching it | 08:15 |
rinigus | piggz: what was your solution? ask-passwd hints that decryption was still triggered | 08:16 |
piggz | rinigus: not a solution for this, just getting actual actdead to work | 08:16 |
piggz | (except for the password prompt) | 08:17 |
rinigus | piggz: yeah, was there as well. ok, will continue with changes and it should be ready today | 08:17 |
rinigus | I think you can assume that this part will work :) . question is whether we want to make some kind of oneshot service for people doing OTA? | 08:19 |
rinigus | something renaming home->home_open and adding config with non-encrypted /home | 08:19 |
rinigus | piggz: ^ | 08:19 |
piggz | what can go wrong with ota? | 08:21 |
piggz | btw, i'll be quiet today, 5hrs driving son to university :( | 08:21 |
rinigus | piggz: 5hrs is rather long distance... or is it in Paris? | 08:26 |
T42_ | <TheVancedGamer> 5h is nothing compared to my university's distance | 08:26 |
T42_ | <TheVancedGamer> I have to go to the next city | 08:26 |
piggz | rinigus: 2.5 each way | 08:27 |
rinigus | re OTA: users should actually flash new image. but few will make OTA and start asking why it doesn't work. some kind of wizard showing up, failing to format non-existent home_open and asking them to contact me (tama) or you (volla) | 08:27 |
rinigus | piggz: 2.5 is better :) | 08:28 |
rinigus | didn't realize that you want to get back... | 08:28 |
flypig | What's the best way for someone unfamiliar with SFOS to find the most up-to-date ports? Is there a set of good web pages to read, for example? | 08:51 |
rinigus | flypig: good question - I don't think we have good up to date resource for it | 08:53 |
rinigus | maybe we should have a topic at FSO as a wiki with the list of ports in "good standing"? | 08:54 |
flypig | It would rely on people being aware of it, and keeping it up-to-date, but it would be a really useful resource. | 08:55 |
rinigus | so far we have https://wiki.merproject.org/wiki/Adaptations/libhybris . but there are dead ports over there | 08:55 |
rinigus | and indeed, it does require people updating the list | 08:56 |
rinigus | flypig: maybe something pinned at https://forum.sailfishos.org/c/hw-adaptation/10 ? | 08:57 |
flypig | Thanks, that table is really nice; does it include up-to-date info on new ports (including dead ports is unfortunate, but not the end of the world). | 08:57 |
flypig | There's no Volla, Pine, f(x)tec on there, so I guess not fully up-to-date. | 08:58 |
T42_ | <elros34> https://gitlab.com/sailfishos-porters-ci is also good source for some up-to-date ports. Other one is searching for droid-config-<device codename> in github | 08:58 |
T42_ | <elros34> droid-config-<device codename> | 08:59 |
flypig | Thanks T42_, how complete is that gitlab list? That's one came up for me most prominently in searches. | 08:59 |
flypig | rinigus, "maybe something pinned..." > this sounds like a great idea to me. But there's a danger it fragments things further. | 09:00 |
T42_ | <elros34> it's up to porter to decide whether he wants to build sfos images online | 09:00 |
T42_ | <elros34> @oMinimalist what command did you use to build libhybris? Your prompt is missing in log | 09:01 |
flypig | T42_, okay, but at least if they do it's likely to offer the latest build. Unfortunately the gitlab page isn't very inviting for someone unfamiliar to SFOS. | 09:01 |
flypig | T42_, but it's certainly a nice resource. Thanks. | 09:02 |
rinigus | flypig: in the case of Tama port, I dropped CI. not sure anyone else did. | 09:02 |
flypig | rinigus, can I ask why? | 09:02 |
rinigus | flypig: I have to make images for 6 devices (xz2 xz2c xz3; single- plus dual). at some point there was something broken and I found that it was easier to write a script building image from OBS based build on PC that fight with CI | 09:03 |
T42_ | <elros34> last source would be searching for device codename her https://build.sailfishos.org/project and checking which releases are added to testing repo | 09:03 |
rinigus | flypig: but details are fuzzy. in the end, as local script worked very well I had no reason to invest into fixing CI builds | 09:04 |
piggz | i dont think id manage without CI :D | 09:05 |
piggz | pro1, volla, pinephone, pinetab, latte | 09:05 |
flypig | rinigus, thanks, it sounds like it was really just about extra burden. Understandable. | 09:05 |
rinigus | sounds like we have data fragmented already a lot. adding one more list wouldn't hurt much :) | 09:05 |
flypig | rinigus, true. I'm just wondering if effort would be better spent keeping https://wiki.merproject.org/wiki/Adaptations/libhybris up-to-date though. It's already a nice table. | 09:06 |
T42_ | <elros34> @oMinimalist also do you have up-to-date droid-hal submodule? | 09:07 |
rinigus | flypig: maybe. it is just in somewhat obscure place and we forget about updating it (cc piggz ) | 09:07 |
T42_ | <oMinimalist> https://forum.sailfishos.org/t/rebuild-image-for-oneplus6-some-problem/8223 (re @elros34: @oMinimalist what co...) | 09:07 |
T42_ | <elros34> I am asking about excat command, did you use just build_packages.sh without arguments? | 09:08 |
T42_ | <elros34> exact* | 09:08 |
rinigus | flypig: one advantage in having it as wiki on FSO would be that users can update it. but I am not really pushing for this idea strongly, just hoping to offload documentation to users :) | 09:09 |
T42_ | <oMinimalist> yes , no arguments (re @elros34: I am asking about ex...) | 09:10 |
rinigus | ideally, we need to have some kind of quick overview which would list well-maintained ports, ports behind few releases, and abandoned ones. right now such overview is missing | 09:10 |
T42_ | <elros34> @oMinimalist why do you build such an old release 3.3.0? This will for sure cause some issues. Latest is 4.2.0.21 | 09:10 |
flypig | rinigus, I agree, the mer wiki is probably no longer the first place people immediately think of. Right now an FSO wiki page seems like a better solution. | 09:10 |
piggz | flypig: i propose you start a new wiki page ;) | 09:11 |
T42_ | <oMinimalist> My reference is https://github.com/sailfish-oneplus6/sf-enchilada/blob/master/building.md (re @elros34: @oMinimalist why do ...) | 09:12 |
T42_ | <elros34> yeah yet another outdated list:) there were second list in mer wiki also, create 3th in forum... | 09:12 |
rinigus | flypig: I also don't this we need such detailed table for an overview | 09:12 |
flypig | piggz, haha, you're good at this motivation thing :) | 09:12 |
rinigus | piggz: I do wonder whether it is you driving ... | 09:13 |
flypig | I'll talk to Ville on Monday, see if he'd be willing for it to be pinned. If not, I think it's a non-starter. | 09:13 |
flypig | If we can have it pinned, then I think it's worth trying. Just my opinion. Perhaps it's also worth discussing in the community meeting. | 09:15 |
flypig | Is anyone here planning to attend the meeting on 30th and would be willing to substitute for me if I can't make it? | 09:16 |
T42_ | <elros34> @oMinimalist as you can see it's from 2020, sfos gets several updates since that. Hadk pdf is more up-to-date. Anyway no idea what this bp -cvi commands do internally. You can of course try to fix your error with following cmd but probably you will have more issues with such an outdated build: "sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper in libhybris-libEGL" then remove mesa when it ask | 09:18 |
flypig | ... silence ..... ;) | 09:19 |
rinigus | flypig: no commitment to attend that one, sorry | 09:20 |
rinigus | as for pinning - agree . it should be there. but I don't see why it wouldn't be pinned | 09:21 |
flypig | rinigus, no worries re the meeting. I'm likely to be there anyway. If I'm not, and you happen to be there, feel free to pick it up! | 09:21 |
rinigus | flypig: sure | 09:21 |
flypig | rinigus, I'm not sure what the rules are for pinning, if there are any. I should check though. | 09:22 |
T42_ | <adampigg> About to set off! (re @SailfishFreenodeIRCBridgeBot: <rinigus>piggz: I do...) | 09:24 |
rinigus | @adampigg: enjoy! | 09:24 |
T42_ | <oMinimalist> Thank you , I will try again. (re @elros34: @oMinimalist as you ...) | 09:24 |
T42_ | <oMinimalist> well , The problem remains. (re @elros34: @oMinimalist as you ...) | 09:30 |
T42_ | <oMinimalist> well , The problem remains. (re @elros34: @oMinimalist as you ...) | 09:31 |
flypig | Community meeting topic, for info: https://forum.sailfishos.org/t/community-meeting-on-irc-30th-september-2021/8043/11 | 09:36 |
T42_ | <elros34> @oMinimalist without more details/full log from your try I can not help | 09:49 |
T42_ | <oMinimalist> http://fars.ee/HA_e (re @elros34: @oMinimalist without...) | 09:51 |
T42_ | <elros34> read last few lines, see now package name is different but like I said better build 4.2.0.21 and fillow hadk pdf | 09:52 |
T42_ | <oMinimalist> https://github.com/sailfish-oneplus6 Has not been maintained for a long time | 09:54 |
T42_ | <oMinimalist> I am a newer for sfos. I have try new sdk version this week, that's more problems. So I follow the website , use old version do it. | 09:56 |
T42_ | <elros34> even with old version, build_packages.sh will still build latest packages so you will have issues. You need to read https://sailfishos.org/develop/hadk/ and http://collabedit.com/kr9xx then update this port to latest release | 09:59 |
T42_ | <oMinimalist> Got it. Thank you very much. (re @elros34: even with old versio...) | 10:02 |
rinigus | piggz: actdead is fixed and fix available at github | 13:24 |
rinigus | PSA: After about 1.5 month development, community edition of device encryption has hit it's first tagged release - 1.0.0 was used for all packages in the project. To my knowledge, all critical bugs have been fixed and you are welcome to test on your ports. Should work for LVM-based as well as regular LineageOS based ports | 13:28 |
rinigus | available at https://github.com/sailfishos-open/sailfish-device-encryption-community | 13:28 |
poetaster | rinigus: u rock. | 13:32 |
locusf | wow thats nice! | 13:56 |
T42_ | <eugenio_g7> 🎉 congrats, great work | 13:57 |
locusf | btw is this done in initrd? | 13:58 |
T42_ | <i54pxqix> Capsule Toy ,the latest Hot NFT after Loot1199 Capsule Toys will be on the initial sale, flash sale with limited quantity, first come, first servedCapsule Toy aims to build an NFT crypto empire ,which consists of collection, social communication, game, DEFI, financial derivatives and other related NFTs around Capsule Toy. Holders of Capsule Toy will have the opportunity to win the super prize of ETH and mysterious NFT.Join Capsule Toy commu | 14:11 |
rinigus | locusf: no, it is later in the boot, after basic.target. on hybris devices, it needs android bits to start to be able to use android hw keystore anyway. so I could use qt for GUI as well | 14:24 |
rinigus | thanks! | 14:24 |
locusf | ah so no full-disk encryption tomfoolery | 14:29 |
locusf | good to know though | 14:29 |
rinigus | locusf: no, home only. could probably use for other bits as well (it is possible to define several mountpoints/devices), not sure which though | 14:31 |
locusf | rinigus: yeah and it doesn't make much sense for hybris devices anyway (full disk encryption) | 14:31 |
locusf | would be really sweet to see something like this used as initrd gui https://github.com/Immediate-Mode-UI/Nuklear | 14:34 |
rinigus | locusf: I don't know (and don't want to know) what is the usual length of the password that you use, but having android hw backed key generation is a "key" over here. essentially, it is impractical to pull out LUKS header from the device and crack of fast PCs. | 14:42 |
rinigus | with the "plain text" passwords, such cracking could be successfult | 14:42 |
poetaster | rinigus: when I've updated a build in chum:testing and am happy with it, do I do a submit request to get it into chum proper? | 14:49 |
rinigus | poetaster: yes, please do so! that makes our lives with piggz easier | 14:50 |
poetaster | do I need to specify target package sailfishos:chum/harbour-tidings ? | 14:50 |
poetaster | (I finally, thanks to piggz, also have a 4.1 device with aarch64). | 14:51 |
rinigus | poetaster: usually, sailfishos:chum is sufficient. packages should have the same name | 14:52 |
poetaster | ok, I'll give it a kick. | 14:57 |
poetaster | rinigus: I think I did it incorrectly. | 14:59 |
rinigus | poetaster: no, all is fine. accepted | 15:00 |
rinigus | in http://releases.sailfishos.org/sdk/targets/ , 4.2.0.21 is missing (or hidden under latest) | 15:04 |
poetaster | rinigus: okidoke. I'm stalling a bit on other apps till the meeting on the 30th. | 15:05 |
poetaster | piggz: I'm not sure if it isn't jolla, but TLS connections fail (IMAP) on 4.1 with the jolla mail app. | 15:12 |
poetaster | piggz: I'm wondering if I should stick to 3.4 for daily driver or try to debug | 15:13 |
poetaster | piggz: Fixed the mail app. It seems repeat config, reboot, rinse repeat works. | 15:24 |
xmn | Does anyone kown why the latest sailfish sfos_upgrade should be install emmc only? piggz? | 15:37 |
xmn | know? | 15:37 |
xmn | know* ... lol | 15:38 |
poetaster | xmn: I'm just looking at it, but don't see what you mean by emmc only? | 15:42 |
xmn | https://nitter.net/adampigg/status/1438797370687381512#m | 15:42 |
xmn | "The latest build of #SailfishOS for the @thepine64 #pinephone is def our best ever. Latest 4.2, encryption, browser and smooth setup. Note, flash to emmc only!" | 15:43 |
xmn | I should have mention I was talking about pinephone | 15:43 |
piggz | xmn: because the flash=-it script will create a 3rd partition for home ...which will happen on SD. .... but the scripts for mounting it assume it is on the emmc | 16:50 |
xmn | ah, that make sense. probably also for encryption too no? | 16:50 |
xmn | thanks for the info | 16:51 |
poetaster | xmn: ah, got ya. | 16:51 |
piggz | xmn: yes, if you have another OS on emmc, that also happened to create a 3rd partition, it will happily encrypt that fr you, so be aware :D | 16:51 |
xmn | heh, cool | 16:57 |
xmn | wil need to see how I can override that, since I've been using sailfish as a sdcard install only OS. But perhaps down the road, no time yet | 16:59 |
poetaster | piggz: just noted after switching sim and memory card back to the 3.4 volla (and back again) that the 4.1 build only ever shows 2G network. | 17:08 |
piggz | xmn: its easy, edit the file in /etc/sailfish-community-device-encrytion/*.ini | 17:09 |
xmn | ooh! Thx piggz. This will be very useful. | 17:15 |
piggz | rinigus: updated volla to 1.0.0 ... when boot should be actdead, which was working somewhat, its now USER | 17:51 |
piggz | no time to debug tonight | 17:51 |
rinigus | piggz: update would miss changes. you would have to reset config.ini. new config.ini made by the wizard includes few changes and additional service | 17:53 |
piggz | ok, lets try | 17:53 |
rinigus | but having USER boot instead is odd - ACT_DEAD is expected. unless it rebooted for some reason? | 17:53 |
rinigus | (started working on tama bump to 4.2) | 17:53 |
piggz | rinigus: its weird ... phone HW def thought it was in charging mode, becuase when i unplugged USB, it turned off instantly .... yet it booted to liptick | 17:55 |
piggz | i checked the bootreason, and it was USB as expected | 17:56 |
rinigus | obviously after removing config.ini you would have to boot into regular OS. that should start wizard and all the next steps... | 17:56 |
rinigus | as for UBS/USER - no clue :( | 17:56 |
piggz | ok, gone through wizrd... | 17:57 |
piggz | ok, this boot, no lipstick, and no ask-pass-gui ... but also no charge animation | 18:03 |
rinigus | piggz I wonder if some older config remains stayed behind... Maybe tgz of etc/systemd/system? | 18:21 |
rinigus | But we can do it tomorrow as well | 18:21 |
rinigus | mal: looks like libgbinder-radio is not updated in https://build.sailfishos.org/package/show/nemo:devel:hw:common/libgbinder-radio to 4.2.0.21 version | 18:30 |
rinigus | as a result, ofono-ril-binder-plugin cannot be updated | 18:31 |
rinigus | testing looks to be fine | 18:33 |
T42_ | <elros34> I guess updated version can be in adaptation-common repo now | 18:34 |
rinigus | @elros34: which adaptation-common? I must have missed it... do you have url? | 18:36 |
T42_ | <elros34> it's easy to miss it in all these adaptation repos: adaptation-common ... https://releases.jolla.com/releases/4.2.0.19/jolla-hw/adaptation-common | 18:37 |
rinigus | @elros34: if we build at OBS, we need it to have there the package as well. just seems most are building in :testing and not working in :devel first | 18:38 |
rinigus | I better wait for mal reply ... he may have not had time to update devel version | 18:39 |
T42_ | <elros34> yeah but ofono-ril-binder-plugin is also in adaptation-common so only if you need bleeding edge version | 18:39 |
rinigus | @elros34: I see. maybe then I do need to drop it... | 18:42 |
rinigus | ... from my build | 18:42 |
rinigus | thanks! | 18:42 |
rinigus | but anyway, devel:common should be probably updated | 18:42 |
T42_ | <elros34> I am not sure: https://irclogs.sailfishos.org/logs/%23sailfishos-porters/%23sailfishos-porters.2021-09-18.log.html#t2021-09-18T00:04:56 | 18:45 |
T42_ | <TechTino> hiya guys. ive been trying to port sailfish to my galaxy s9. im getting: https://pastebin.com/zpDRbD6B. I have read that this is about lineage os and soong but doesnt seem to be making much sense | 18:46 |
T42_ | <XAP2P> Wow : https://irc.thaodan.de/.imgstore/25216795/file_2696.jpg | 18:46 |
mal | rinigus: hmm | 18:57 |
mal | rinigus: looks like I forgot to update it in devel common, I did update it in testing common | 18:59 |
mal | rinigus: fixed now | 19:00 |
mal | @elros34 that new adaptation-common only helps after we have updated to 4.2.0 not during update | 19:02 |
T42_ | <elros34> ah obviously that is right point | 19:03 |
mal | @TechTino have you applied the hybris patches is mentioned in faq https://github.com/mer-hybris/hadk-faq#hybris-17-1 not sure which android base you are using | 19:08 |
T42_ | <TechTino> yeah. i just realised though that ive been trying to build 17.1 with hybris 16 synced so lol. | 19:09 |
T42_ | <TechTino> ill try it the correct way and then we'll see | 19:10 |
mal | 16.1 is fine also just follow instructions for it | 19:11 |
mal | depends on which version you really want to use | 19:11 |
T42_ | <TechTino> yeah. see i had 17.1 branches of stuff specified in my manifest but had the hadk for 16 | 19:11 |
mal | not sure if I understand, what did you use for repo init | 19:17 |
T42_ | <TechTino> repo init -u git://github.com/mer-hybris/android.git -b hybris-16.0, i did this, when i should have done repo init -u git://github.com/mer-hybris/android.git -b hybris-17.1 as i have pointed to lineage 17.1 branches in manifest. all good tho im syncing now on 17.1 | 19:25 |
mal | ok | 19:27 |
T42_ | <TechTino> error: in sync --fetch-submodules: revision refs/heads/lineage-17.1 in LineageOS/android_art not found, this keeps happening, i even went in and changed the revision to lineage-17.1 and it didnt work either | 20:06 |
rinigus | mal: thank you very much! | 21:15 |
T42_ | <TechTino> rpm/dhd/helpers/build_packages.sh --droid-hal is taking forever, and isnt using any cpu whatsoever. | 22:29 |
T42_ | <TechTino> any way to see verbose? | 22:30 |
T42_ | <b100dian> mal: since the build passed and am no calculated person, I made the tar —numeric-owner backup and upgraded. Nothing bad happened - other than jolla-camera breaking - so I don't know if this kind of backup is good. I am now upgrading the gst-droid. All through the browser click-click thanks lbt :) | 22:30 |
T42_ | <b100dian> camera works with upgrade-4.2.0 branch, I don't see five cameras (only one) though. piggz-o-vision works though. Happy evening:) | 22:34 |
mal | @b100dian do you mean in advanced-camera you see the extra cameras? | 23:23 |
mal | @TechTino which package is it building? | 23:23 |
T42_ | <TechTino> droid-hal | 23:23 |
mal | ah, droid-hal it should not take very long | 23:23 |
T42_ | <TechTino> i think its hanging | 23:24 |
mal | just kill it and try again | 23:24 |
T42_ | <TechTino> https://pastebin.com/mcVrV6Z9 | 23:26 |
T42_ | <TechTino> this is what i get. seems fine right? b4 i was getting some weird gpg errors from sb2 though but that was b4 i ran breakfast and built stuff again | 23:27 |
T42_ | <b100dian> mal: were there in 4.1, though not correctly mapped in advanced-camera. For jolla camera anything other than gst-droid I shoild upgrade? | 23:27 |
T42_ | <TechTino> or should i go fix the warnings | 23:28 |
mal | @TechTino I think the issue is that it can't find any ueventd*.rc files in the folder it is trying to look at in out/ https://github.com/mer-hybris/droid-hal-device/blob/master/droid-hal-device.inc#L479 | 23:30 |
T42_ | <TechTino> i dont have a vendor folder hmm | 23:30 |
mal | @TechTino maybe try running "make modules" and look for anything uevent and fstab related in the output | 23:31 |
T42_ | <TechTino> nope, neither of those in the output | 23:32 |
mal | @b100dian jolla-camera needs configs for extra cameras in 4.2.0 https://github.com/mer-hybris/droid-config-sony-seine/blob/master/sparse/etc/dconf/db/vendor.d/jolla-camera-hw.txt | 23:32 |
T42_ | <TechTino> i think my issue is that i dont have a vendor folder built, but idk why | 23:34 |
mal | @TechTino hmm, maybe then look for such files in device repos under device/ and copy those manually to correct places, check the Android.bp or Android.mk files in device in folder where you find the files or in higher level folders | 23:34 |
T42_ | <TechTino> could it be bcs its common vendor files and not for the specific codename | 23:34 |
mal | @TechTino vendor folder in not always needed, did you look at those files in all of out/target/product/* ? maybe try "find out/target -name '*uevent*'" | 23:35 |
T42_ | <TechTino> https://pastebin.com/fYPNJfqv | 23:36 |
T42_ | <TechTino> for fstab: out/target/product/starlte/obj/ROOT/hybris-boot_intermediates/initramfs/etc/fstab | 23:37 |
T42_ | <TechTino> out/target/product/starlte/obj/ROOT/hybris-recovery_intermediates/initramfs/etc/fstab | 23:37 |
mal | how about "find device -name '*uevent*'" | 23:40 |
T42_ | <TechTino> device/qcom/sepolicy-legacy-um/vendor/common/ueventd.te | 23:41 |
T42_ | <TechTino> device/qcom/sepolicy-legacy/common/ueventd.te | 23:41 |
T42_ | <TechTino> device/qcom/sepolicy/generic/vendor/common/ueventd.te | 23:41 |
T42_ | <TechTino> device/qcom/sepolicy/legacy/vendor/common/ueventd.te | 23:41 |
T42_ | <TechTino> oh interesting none for my device appear | 23:41 |
mal | try to grep for that in your device repo | 23:43 |
T42_ | <TechTino> i dont seem to see it hm | 23:50 |
T42_ | <b100dian> mal: that's a short jolla-camera-hw.txt :) the order is from droid-camres? I'll experiment but that tool outputs > 10 cameras here:) | 23:51 |
T42_ | <TechTino> https://pastebin.com/YQ7vXFEY only files relating to sepolicy and .te files, no ueventd hm | 23:52 |
mal | @b100dian droid-camres is obsolete since 4.2.0 | 23:53 |
mal | @TechTino go to device/samsung/universal9810-common and try running "git revert 2a210ce7fb59ed39c3d7424ab6112c5849b8eade" | 23:53 |
T42_ | <b100dian> I've added labels a,b,c,d,e and i only see c, d, e and another dozen of unlabeled cameras (not seeing a,b,c because of lacking scroll) - just as I remembered from droid-camres. I will look into this tomorrow - I did have access through 'e' to the 5x tele camera so .. :) | 23:55 |
T42_ | <b100dian> not seeing a, b I mean | 23:55 |
mal | how can it report that many cameras? | 23:55 |
T42_ | <b100dian> definitely not expected, but wasn't a problem before | 23:55 |
T42_ | <b100dian> i'll get back to this, but surely is interesting, there should be max. 5 | 23:56 |
mal | something is then wrong in configuration, does logcat show anything about listing available cameras | 23:56 |
mal | getting debug output from gst-droid would also help | 23:57 |
mal | @b100dian wondering if that is the first multi-camera community port? or has there been any other device | 23:57 |
T42_ | <b100dian> will grep tomorrow - my camera logcat is pushing thousands of lines per second. | 23:57 |
T42_ | <b100dian> I don't know, was hoping to see 5 of them of course. | 23:58 |
mal | yeah, logcat needs some grep magic to get the needed information | 23:58 |
T42_ | <b100dian> no way to screenshot in the camera app:) | 23:59 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!