| *** ChanServ sets mode: +v T4 | 05:38 | |
| T4 | <m_aurel> We need some help again for our negotiation with the potential ODM. They say, that we need an authorisation of Qualcomm for a port of Sailfish OS, if the vendor of the ODM would provide modified source code of Qualcomm. It doesn't make sense to me, because the source code of Qualcomm is open source. We have asked the OEM for the Android B | 09:18 |
|---|---|---|
| T4 | oard Support Package for aport. I'm afraid their manager doesn't know, what we are talking about. Do we really need the source code or a build, that we can link the libraries? | 09:18 |
| r0kk3rz | yeah you do | 09:29 |
| T4 | <m_aurel> What do we need of the both alternatives? | 09:29 |
| r0kk3rz | theres no such thing as an android 'board support package' really, the ODM will give you a full aosp tree with driver blobs | 09:30 |
| r0kk3rz | you need that | 09:30 |
| T4 | <m_aurel> As a source code or build? | 09:30 |
| r0kk3rz | well.. normally they will give you a compiled android image, and you hope the aosp source they give you works | 09:30 |
| r0kk3rz | you need the source | 09:30 |
| r0kk3rz | but if you want to go down this road i urge you to pay jolla to do it, device adaptation is a tough subject | 09:31 |
| T4 | <m_aurel> I'm confused. You say: normally they will give you a compiled android image. | 09:31 |
| r0kk3rz | what we do here isnt normal, i hope you understand that | 09:32 |
| T4 | <m_aurel> Indeed we would involve Jolla. But we have to clarify, what we can get from the ODM under which conditions. | 09:34 |
| T4 | <m_aurel> Jolla is very optimistic: "Porting Sailfish OS for Qualcomm based device is quite straight forward process. The main reason is that Qualcomm is providing the source codes of their Android deliveries at https://www.codeaurora.org/, with the exception of the parts that ODM has modified, thus ODM needs to provide some of source code. We have | 09:34 |
| T4 | done many hardware porting projects since the beginning with Qualcomm chipsets and the same working model has been used." | 09:34 |
| r0kk3rz | jolla have more experience with ODMs than anyone here | 09:34 |
| r0kk3rz | we are merely community porters | 09:34 |
| T4 | <m_aurel> Ok, the best thing will be to bring Jolla and the ODM together. | 09:35 |
| r0kk3rz | definitely | 09:36 |
| T4 | <m_aurel> It just makes no sense to me, that we need am athorisation of Qualcomm, becasue the modified source code comes form the OEM or his vendor. | 09:37 |
| T4 | <m_aurel> [Edit] It just makes no sense to me, that we need an authorisation of Qualcomm, becasue the modified source code comes form the OEM or his vendor. | 09:38 |
| r0kk3rz | stupid legal contracts no doubt | 09:38 |
| r0kk3rz | jolla will know what they need and what qcom has agreed to before | 09:39 |
| T4 | <meierrom> @m_aurel: A nice video on “how the sausage is getting made” published by Jolla: https://www.youtube.com/watch?v=BSLaliD8Mq4 | 10:31 |
| abranson | piggz: i already implemented chroma-flash as a quirk, but it's not merged yet because i'm not sure about it | 13:24 |
| abranson | it might help with poor white balance on flash photos though | 13:24 |
| abranson | https://github.com/sailfishos/gst-droid/commits/extras | 13:25 |
| abranson | also experimented with temporal noise reduction for videos, and a 'scene-detect' property | 13:25 |
| mal | abranson: what's the logic of auto being manual in the scene modes? | 13:49 |
| abranson | mal: I read somewhere that 'auto' just meant no scene mode was being used, which is really manual. using the manual value for that means I could use auto for asd | 14:29 |
| abranson | but that was before piggz did his scene stuff | 14:29 |
| mal | abranson: ok, interesting anyway, we should check that somehow | 14:30 |
| mal | abranson: looks like you are right https://android.googlesource.com/platform/hardware/qcom/camera/+/jb-mr2.0-release/QCamera2/HAL/QCameraParameters.cpp#415 | 14:31 |
| abranson | mal: ah the HDR is interesting there too. OFF, because something else gets activated instead. | 14:34 |
| mal | abranson: probably it sets the separate HDR setting | 14:34 |
| mal | abranson: the one we have as quirk | 14:35 |
| abranson | yeah that bracket thing | 14:35 |
| mal | abranson: some hdr stuff also https://android.googlesource.com/platform/hardware/qcom/camera/+/jb-mr2.0-release/QCamera2/HAL/QCameraParameters.cpp#2188 | 14:36 |
| mal | although the links are for quite old release but anyway | 14:36 |
| mal | that seems similar even in newer base https://github.com/LineageOS/android_hardware_qcom_camera/blob/cm-14.1/QCamera2/HAL/QCameraParameters.cpp#L8825 | 14:39 |
| mal | abranson: wondering if the HDR quirk is even needed, maybe the camera just directly uses it internally in the android hal | 14:42 |
| abranson | it wouldn't be a parameter if it didn't need setting | 14:42 |
| abranson | i think it's a scene mode for UI purposes | 14:42 |
| mal | abranson: hmm, so you think setting HDR scene mode is not enough? | 14:43 |
| abranson | mal: the other magic could happen in the camera service. best way to check is to see if that param changes when it's on | 14:45 |
| abranson | it seems to be on in piggz's screenshots though | 14:45 |
| abranson | and i don't think he's setting the quirk | 14:46 |
| mal | abranson: ok, so some testing is needed to see how it works | 14:47 |
| *** ChanServ sets mode: +v T4 | 17:52 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!