| T4 | <adampigg> Rokk3rz, take a look | 08:42 |
|---|---|---|
| piggz | mal: how does this sound... | 09:35 |
| piggz | macro/auto/continuous = focusmodepoiint + searchAndLock | 09:36 |
| piggz | else focuspoint = center + searchandlock | 09:36 |
| piggz | macro/autp/continuous allows focus point to be changed | 09:37 |
| piggz | the only wierdness i have is that if im sitting in the house, pointing outside at trees, selecting infinity, i expect the trees to comr into focus but they dont | 09:37 |
| piggz | if i use auto and click they do | 09:37 |
| piggz | abranson: ^^ | 09:38 |
| abranson | piggz: interesting. i think according to the definition, they should | 09:39 |
| piggz | abranson: yes id have thought so.. | 09:39 |
| piggz | abranson: infact, i made it so that clicking the screen does a search and lock, and in infinity mode, it doesnt appear to do anything | 09:42 |
| abranson | piggz: no, there are certain focus modes that qtmm classifies as fixed. it'll ignore focus commands then. | 09:43 |
| abranson | hyperfocal and infinity off the top of my head | 09:43 |
| piggz | abranson: so, why are my trees not in focus! | 09:44 |
| abranson | piggz: dirty lens? :P | 09:44 |
| piggz | anyway, i think the rest of the code is ok then from what you say... | 09:44 |
| masha11 | Hi! Result of mer_verify_kernel_config: https://pastebin.com/dLxM0rnN. My defconfig: https://pastebin.com/Fc0DAF77. What warnings must be removed? | 09:48 |
| piggz | mal: abranson: https://github.com/piggz/harbour-advanced-camera/compare/focus-changes?expand=1 | 09:48 |
| mal | piggz: is focuspointcenter the correct, why not auto? | 09:51 |
| piggz | mal: my thinking was that it doesnt matter, because they are fixed points ... and the crcel goes to center ... another option is to remove the circle | 10:13 |
| mal | piggz: also should we call unlock if we change the mode? | 10:23 |
| piggz | mal: lets try | 10:24 |
| piggz | mal: ah, i dont check for supported focus modes..... | 10:34 |
| piggz | mido supports | 10:34 |
| piggz | focus-mode-values = auto,infinity,fixed,macro,continuous-video,continuous-picture,manual | 10:34 |
| piggz | mal: actually, i do check, but.... | 10:36 |
| piggz | https://git.merproject.org/mer-core/qtmultimedia/blob/95ffdbaf9d82e8742ee38f9282a11e75e00c69fb/qtmultimedia/src/plugins/gstreamer/camerabin/camerabinfocus.cpp#L113 | 10:36 |
| piggz | abranson: ^^ | 10:36 |
| piggz | camerbin doesnt check focus-mode-values!! | 10:36 |
| mal | piggz: wrong branch | 10:37 |
| mal | https://git.merproject.org/mer-core/qtmultimedia/blob/mer-5.6/src/plugins/gstreamer/camerabin/camerabinfocus.cpp#L129 | 10:37 |
| mal | piggz: come on, you implemented that yourself :D | 10:37 |
| piggz | mal: phew! | 10:38 |
| piggz | i was wondering if id missed something then! | 10:38 |
| piggz | ok, then its not working properly | 10:38 |
| piggz | lets see | 10:40 |
| mal | piggz: which one is missing? | 10:40 |
| piggz | mal: camera ui says hyperfocal is supported, but tis not on mido | 10:41 |
| piggz | mal: good point, qtmm code is ok...... | 11:45 |
| masha11 | mal: Could you help me? I still can’t start SailfishOS and I don’t see messages about mer. Result of mer_verify_kernel_config: https://pastebin.com/dLxM0rnN. My defconfig: https://pastebin.com/Fc0DAF77. What warnings must be corrected? | 11:57 |
| piggz | mal: abranson: phew, there is no bug | 12:01 |
| piggz | hyperfocal == fixed in GST terms | 12:01 |
| Thaodan | lbt: can you look in my changes to mer_verify_config? | 12:14 |
| mal | masha11: manually check your .config in out/ folder against these https://github.com/mer-hybris/hybris-boot/blob/master/init-script#L319 | 12:14 |
| mal | piggz: we should think a bit more about how each mode should go, maybe later today after work | 12:16 |
| piggz | mal: re unlocking..... | 12:17 |
| piggz | qt docs say | 12:17 |
| piggz | It's also acceptable to relock already locked settings, depending on the lock parameter this initiates new focusing, exposure or white balance calculation. | 12:17 |
| piggz | so, i think its ok to not unlock, as we always search for a new lock anyway | 12:17 |
| piggz | what fo you think | 12:17 |
| mal | piggz: what happens if we change to a mode where we do not lock, the old lock would still remain? | 12:20 |
| masha11 | mal: ok | 12:21 |
| piggz | mal: unlock added | 12:58 |
| lbt | Thaodan: where are they? | 13:14 |
| mal | lbt: probably this https://github.com/mer-hybris/mer-kernel-check/pull/15 | 13:21 |
| lbt | OK - that's old - I hadn't seen it | 13:32 |
| piggz | also, there is my d-h-v pull for native builds if anyone is interested ;) | 13:32 |
| mal | piggz: I'll have a look this weekend, maybe need to discuss with others | 13:32 |
| piggz | @eugenio_g7 so we are good to post a release then .... sensors can be updated with OTA config udpate? | 13:34 |
| T4 | <eugenio_g7> piggz: not yet, seems the systemd unit doesn't work reliably, I'll check tonight if I'm not too tired otherwise tomorrow :P | 14:03 |
| T4 | <eugenio_g7> Also the new battery has been delivered \o/ | 14:04 |
| T4 | <m_aurel> Hello, This week I have got the information, that the successor model of our potential ODM uses the Qualcomm Snapdragon 425 (MSM8917). I could find the chipset reference in the Code Aurora project, but with the suffix _64. Has someone experiences with porting Sailfish OS for this chipset. I will ask our ODM, if he could confirm one of the | 16:18 |
| T4 | build tags, that are listed for this chipset: https://wiki.codeaurora.org/xwiki/bin/QAEP/release | 16:18 |
| mal | @m_aurel I couldn't see 8917 in that list | 16:21 |
| T4 | <m_aurel> Sorry, copy and paste error. The new one is Qualcomm Snapdragon 430 (MSM8937) | 16:23 |
| mal | I don't see any reason why that chipset would be any different from others, if you have device repo and kernel it should not be too difficult (in theory) | 16:25 |
| piggz | @eugenio_g7 perhaps add all the paths to the systemd unit? | 16:25 |
| T4 | <m_aurel> Porting Nemo Mobile would be similar? Hopefully we find an agreement with Jolla to be allowed to port and ship Sailfish, but we need a fall back | 16:30 |
| piggz | @m_aurel afaik, you dont need permission to port and ship sailfish....we all do it! | 16:31 |
| mal | piggz: not really sure if that is the case if the devices are sold | 16:32 |
| T4 | <m_aurel> Jolla's CEO confirmed, the we are not allowed to sell devices with Jolla without a license agreement. This is ok. We just have to find an agreement, that matches our business model. | 16:33 |
| T4 | <m_aurel> I mean, with Sailfish | 16:33 |
| T4 | <m_aurel> So we may need a fall back. | 16:34 |
| piggz | mal: ah ok | 16:40 |
| T4 | <m_aurel> another community member found out, that the current model seems to based on an AOSP build instead of a Code Aurora build: OPM1.171019.011repsectively android-8.1.0_r1. It's referenced at https://source.android.com/setup/start/build-numbers | 16:50 |
| piggz | mal: evening | 20:28 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!