| T4 | <adampigg> @eugenio_g7/mal is it better to add symlink for /system/etc/firmware -> /etc/firmware, or to change path to BT FW to /system/etc/firmware/bt/...... ? | 08:41 |
|---|---|---|
| T4 | <eugenio_g7> I think it's better to package the firmwares and ship them in /etc/firmware, as we're going to get rid of /system anyways | 08:43 |
| T4 | <adampigg> ok, i'll add the firmware to sparse/etc then? | 08:43 |
| T4 | <adampigg> while you are discussing the 'big plan' (tm) ... will /system be our / ? where will we stick data/ ? | 08:45 |
| T4 | <eugenio_g7> Do we need data/? | 09:04 |
| T4 | <adampigg> @eugenio_g7 probably not, just wondering how we would structure the filesystem | 09:13 |
| T4 | <adampigg> it would be kinda nice if sfos apps installed to a seperte partition, then you could seperate the OS and apps/data like android | 09:14 |
| T4 | <m_aurel> Hello. From our ODM we have received the kernel source code, binaries and a build ID for the Android Source Tree for the hardware adaption of Qualcomm based device. For the build ID we got OPM1.171019.011. This is the build ID of a factory image but not of an Android Source Tree at Code Aurora: https://wiki.codeaurora.org/xwiki/bin/QAEP/r | 10:04 |
| T4 | elease. I' afraid, there is a misunderstanding. The build ID of the factory image is not sufficient for the hardware adaption, right? | 10:04 |
| T4 | <m_aurel> I it possible, that the ODM uses a pure AOSP? | 10:04 |
| T4 | <m_aurel> Can some help to clarify the required information? | 10:05 |
| r0kk3rz | youd need to patch the tree they gave you | 10:07 |
| r0kk3rz | and you should be asking them for clarification, not us :p | 10:08 |
| T4 | <m_aurel> That's the point. Isit correct, that the mentioned build ID is not sufficient to get the tree? It would be possible to get the tree, if we would have the build ID of Code Aurora, right? | 10:10 |
| r0kk3rz | why are you asking us? | 10:10 |
| r0kk3rz | ask them | 10:10 |
| T4 | <m_aurel> I have no experiences with hardware adaption. I just want to make sure, that we get all information and sources, that are required for hardware adaption. I assumed that the focus of this chat room is porting Sailfish OS to hardware devices. | 10:14 |
| T4 | <m_aurel> Unfortunately the ODM is not experienced in hardware adaption. Like the most ODMs, they are focussed on Android. So I have sent them a list of thinks we need from them. | 10:15 |
| T4 | <m_aurel> [Edit] Unfortunately the ODM is not experienced in hardware adaption. Like the most ODMs, they are focussed on Android. So I have sent them a list of things we need from them. | 10:16 |
| T4 | <m_aurel> [Edit] That's the point. Is it correct, that the mentioned build ID is not sufficient to get the tree? It would be possible to get the tree, if we would have the build ID of Code Aurora, right? | 10:16 |
| r0kk3rz | they will know how to build android from source | 10:16 |
| r0kk3rz | do that | 10:16 |
| r0kk3rz | check it works with the code they provide | 10:17 |
| T4 | <m_aurel> Unfortunately not. This is done by the PCBA board designer, their vendor. So they have to forward my request. | 10:18 |
| T4 | <m_aurel> Currently we have just the kernel source code and the binaries. I'm told, that we need the Android Source Tree in addition. | 10:19 |
| r0kk3rz | so you have no idea, build and test a working android first | 10:20 |
| T4 | <m_aurel> If the community ports Sailfish OS. Where do you usually get the Android Source Tree for the hardware adaption? Have you worked with Code Aurora oder the pure AOSP of Google? | 10:20 |
| T4 | <m_aurel> First I want to check, whether the ODM can deliver all required information for HA. As soon this is clarified I can start the commercial negotiation with the ODM. As soon we have an agreement, we will hire one or more developer for the HA. | 10:45 |
| T4 | <m_aurel> So you recommend trial and error with own Android Image? | 10:46 |
| T4 | <m_aurel> [Edit] So you recommend trial and error with an own Android Image? | 10:46 |
| T4 | <m_aurel> [Edit] First I want to check, whether the ODM can deliver all required information for HA. Afterwards I can start the commercial negotiation with the ODM. As soon we have an agreement, we will hire one or more developer for the HA. | 10:47 |
| r0kk3rz | you need to verify the code they give you | 10:49 |
| r0kk3rz | because it probably wont work | 10:49 |
| r0kk3rz | if you can build a working android, you have what you need for a hybris adaptation | 10:50 |
| T4 | <m_aurel> I have no code, yet. Just the kernel source code and the binaries. The android source tree is missing. I asked for the build ID of the Code Aurora project, because I was told, that we can get the android source code from there for Qualcomm chipsets. Last week I got the quoted build ID, but this is the build ID of the Android factor image. | 10:58 |
| T4 | So my questions are: … 1. Is it true, that the build ID of the factory image doesn't help to get the Android Source Tree? … 2. Or can I conlcude from the build ID for the factory image the Android Source Tree we could download, maybe from the AOSP? … If both anseres are NO, i have to ask the ODM again for the build ID of the Code Aurora Project. | 10:58 |
| T4 | The pattern of the build ID should be something like LA.UM.7.6.2.r1-06900-89xx.0, correct? | 10:58 |
| T4 | <m_aurel> [Edit] I have no code, yet. Just the kernel source code and the binaries. The android source tree is missing. I asked for the build ID of the Code Aurora project, because I was told, that we can get the android source code from there for Qualcomm chipsets. Last week I got the quoted build ID, but this is the build ID of the Android factor | 10:59 |
| T4 | y image. So my questions are: … 1. Is it true, that the build ID of the factory image doesn't help to get the Android Source Tree? … 2. Or can I conlcude from the build ID for the factory image the Android Source Tree we could download, maybe from the AOSP? … If both anseres are NO, i have to ask the ODM again for the build ID of the Code Aurora P | 10:59 |
| T4 | roject. The pattern of the build ID should be something like LA.UM.7.6.2.r1-06900-89xx.0, correct? | 10:59 |
| T4 | <m_aurel> [Edit] I have no code, yet. Just the kernel source code and the binaries. The android source tree is missing. I asked for the build ID of the Code Aurora project, because I was told, that we can get the android source tree code from there for Qualcomm chipsets. Last week I got the quoted build ID, but this is the build ID of the Android f | 11:00 |
| T4 | actory image. So my questions are: … 1. Is it true, that the build ID of the factory image doesn't help to get the Android Source Tree? … 2. Or can I conlcude from the build ID for the factory image the Android Source Tree we could download, maybe from the AOSP? … If both anseres are NO, i have to ask the ODM again for the build ID of the Code Aur | 11:00 |
| T4 | ora Project. The pattern of the build ID should be something like LA.UM.7.6.2.r1-06900-89xx.0, correct? | 11:00 |
| T4 | <m_aurel> [Edit] I have no code, yet. Just the kernel source code and the binaries. The android source tree is missing. I asked for the build ID of the Code Aurora project, because I was told, that we can get the android source tree code from there for Qualcomm chipsets. Last week I got the quoted build ID, but this is the build ID of the Android f | 11:01 |
| T4 | actory image. So my questions are: … 1. Is it true, that the build ID of the factory image doesn't help to get the Android Source Tree? … 2. Or can I conlcude from the build ID for the factory image the Android Source Tree we could download, maybe from the AOSP? … If both answers are NO, i have to ask the ODM again for the build ID of the Code Aur | 11:01 |
| T4 | ora Project. The pattern of the build ID should be something like LA.UM.7.6.2.r1-06900-89xx.0, correct? | 11:01 |
| r0kk3rz | oh wow, stop spamming the edits | 11:01 |
| T4 | <m_aurel> Oh, do you see the edits as repeating post? I don't see this in my Telegram client. Sorry. | 11:02 |
| T4 | <adampigg> The first rule of #sailfishos-porters ... dont use telegram features that dont mix well with IRC ;) | 11:03 |
| r0kk3rz | talk to the odm about building android | 11:05 |
| piggz | mal: this is what i was talking about the other day, now fixed https://github.com/piggz/harbour-advanced-camera/commit/0c7d739c49803a124f07fb9706985881014e8ea8 | 11:12 |
| T4 | <m_aurel> The ODM candidate is focussed on assembling. While the Android image is delivered by their PCBA board vendor, the ODM just adds some additional apps in their manufactoring process. So they don't know, how to build Android. I can ask the ODM to forward my request for Android build intructions, but it's unlikely, that the PCBA board vendor | 11:19 |
| T4 | respond. It's more likely to get an answer for a simple and clear question like aany reference to the Android Source Tree. | 11:19 |
| T4 | <m_aurel> There are some cumminity ports available. For example for the Nexus 5x. Where did the porter get the necessary sources for the HA in this case? | 11:21 |
| T4 | <m_aurel> If someone is interested to support the sourcing process for a another device with a preinstalled Sailfish OS oder Nemo Mobile, he or she can send me a private message to continue without annoying the community. We are anyway looking for developers, we can hire as freelancers or later this year as an employees. | 11:30 |
| T4 | <m_aurel> Any further suggestion and recommendation is welcome. | 11:30 |
| masha11 | Hi! Where should i build LineageOS in $HOST or $HABUILD_SDK? | 11:48 |
| mal | piggz: btw, I think you shouldn't have harbour-advanced-camera.pro.user in git repo | 11:53 |
| mal | masha11: doesn't your device have a existing LineageOS build somewhere online? | 11:54 |
| T4 | <m_aurel> Is it true, that the Sailfish community ports except for the Planet Computer device are based on LineageOS or has someone prted another device "from the scratch"? | 11:56 |
| mal | @m_aurel Fairphone 2 port is based on the AOSP sources (Faiphone Open OS) released by Fairphone | 11:58 |
| masha11 | mal: yes, but Sailfish.zip firmware I assembled did not work (black screen on the device). Do I need to build my own LineageOS.zip? | 11:58 |
| mal | masha11: it's rare that first build works, now you need to try to telnet to the device, depending on what state it is, check host dmesg for usb related messages when connecting the phone and see if it says anything | 12:00 |
| mal | masha11: which device? | 12:00 |
| masha11 | mal: my device is Motorola Moto Z (griffin) | 12:01 |
| T4 | <m_aurel> Ah, interesting. Are porters for the Fairphone member of this community? It would be helpfull to ask them for their experiences. | 12:02 |
| T4 | <adampigg> Mal, true | 12:03 |
| mal | @m_aurel I'm the porter of Sailfish OS to Fairphone 2 | 12:04 |
| T4 | <m_aurel> Great. Which sources have you used for the port beyond the AOSP? I assume binaries for some drivers and the kernel source code? If this is true, we might already have everything in place, because we can download AOSP sources from Google. | 12:06 |
| mal | I just synced the whole manifest provided by Fairphone and then patched it with the hybris patches and then build it | 12:07 |
| mal | I think Fairphone sources are mostly just AOSP but with some additional security patches probably | 12:08 |
| masha11 | mal: I could not log into telnet 192.168.2.15 2323. Error: "Unable to connect to remote host. Connection refused." "lsusb -v | grep iSerial" Error: "Couldn't open device, some information will be missing iSerial 3 ZY223LT4KZ". | 12:08 |
| mal | masha11: pastebin the relevant parts of dmesg, look for any usb message related to Mer | 12:09 |
| T4 | <m_aurel> I see, our ODM candidate confirmed, that they use a pure stock Android with just two additional apps. We have likely the same situation here. | 12:10 |
| mal | then it should be possible, I assume you have device repo and kernel repo for the device? | 12:11 |
| mal | so you'll first need to build a clean AOSP image for it and then have another source tree which you patch with the hybris patches and use for hybris-hal build | 12:12 |
| mal | @m_aurel which android version is the device using? | 12:14 |
| T4 | <m_aurel> The ODM did provide us a download link for the zipped firmware image with all binaries and the kernel source code. | 12:15 |
| T4 | <m_aurel> Oreo | 12:15 |
| T4 | <m_aurel> OPM1.171019.011 | 12:15 |
| mal | @m_aurel but do you have also device repo in addition to the kernel sources? | 12:18 |
| T4 | <m_aurel> No, we have no access to a device repository. We have just the binaries from the zipped firmware image. Jolla told us, that it would be sufficient, if we would have the Android Source Tree in addition. Because our ODM is using a Qualcomm shipset (no surprise), we should use an Android Source Tree from Code Aurora. But with the last inform | 12:26 |
| T4 | ation, the build ID OPM1.171019.01 I conclude, that the manager at the ODM is confused or the device is realy compatible to Google's device. Maybe we could use the LineageOS port for the Sailfish OS port in this case. | 12:26 |
| T4 | <m_aurel> The kernel source code contains a folder msm-3.18 | 12:27 |
| mal | @m_aurel I mean if you can build AOSP image for the device then you can build also sailfish, but to be able to build AOSP image you need at least two repos, kernel and a device repo, the latter of which defines what features the device has etc | 12:30 |
| T4 | <m_aurel> What does a device repository contain? Jolla hasn't mentioned this as a prerequisit for hardware adaption. | 12:35 |
| mal | here is a random example of a aosp device repo https://android.googlesource.com/device/google/wahoo/+/master | 12:38 |
| mal | @m_aurel what device are you planning on porting? | 12:38 |
| masha11 | mal: no usb message related to Mer in the dmesg: https://pastebin.com/y0h5HdUP | 12:45 |
| mal | masha11: does the device reboot or stay on? | 12:46 |
| masha11 | mal: this dmesg is in mode fastboot. The device after flashing rebooted but did not turn on. | 12:53 |
| mal | masha11: what device and how did you build the image? | 12:56 |
| masha11 | mal: Motorola Moto Z (griffin). Build the image using HADK. | 13:00 |
| masha11 | mal: version SailfishOS - 3.0.0.8, version LineageOS - 15.1. | 13:08 |
| mal | masha11: so if you now reboot the device while it's connected to USB how does host dmesg look like | 13:08 |
| mal | masha11: did you do the additional things needed for 15.1 base as instructed in faq (linked in channel topic) | 13:08 |
| masha11 | mal: only one new message has appeared: usb 1-1: USB disconnect, device number 7. | 13:14 |
| masha11 | mal: yes, but i used brunch android8-initial-update instead of android8-initial in "git clone --recurse-submodules https://github.com/mer-hybris/libhybris.git" due to error | 13:20 |
| mal | masha11: what error | 13:24 |
| mal | also don't just randomly select messages from logs | 13:24 |
| T4 | <NotKit> @m_aurel if you don't have Android tree, it might be easier to start on LineageOS tree for similar device with same SoC | 13:39 |
| masha11 | mal: libhybris android8-initial error: https://pastebin.com/7Z1STevY | 13:48 |
| mal | ok, anyway using that -update branch is fine | 14:00 |
| masha11 | mal: ok, I will try to build the image first with using faq-had. What version of Lineage is better to build: 14.1 or 15.1?Own LineageOS is not necessary to build if there is ready? | 14:06 |
| mal | both 14.1 and 15.1 are fine, depends on which one you have available, faq-hadk only has some additional instructions for the 15.1 base (also for 14.1 base but since you use 15.1 those are irrelevant) | 14:12 |
| masha11 | mal: Thank you. When i tried to build my LineageOS, an error occurred: https://pastebin.com/c07WjdPn | 14:17 |
| mal | if you have a prebuild lineage there is no need to build it yourself | 14:19 |
| masha11 | mal: ok, thank you. | 14:19 |
| mal | that error looks like a mismatch in versions of some repos | 14:19 |
| mal | maybe | 14:20 |
| masha11 | mal: ok, maybe | 14:21 |
| mal | but anyway if you build hybris-hal successfully then it's fine | 14:21 |
| masha11 | mal: yes, hybris-hal build was completed successfully | 14:27 |
| mal | masha11: also are you sure you have correctly modified fixup-mountpoints file? | 14:27 |
| masha11 | mal: yes, i checked the fixup-mountpoints. | 14:28 |
| mal | and check that there is some fstab file in out/, use this command to check (in $ANDROID_ROOT) find out/ -name fstab* | 14:28 |
| mal | masha11: could you show the modifications to that file? | 14:29 |
| mal | use pastebin or something like that for it | 14:29 |
| masha11 | mal: I will show later. Thank you. | 14:31 |
| mal | it's one of the most common mistakes people make while porting | 14:31 |
| T4 | <m_aurel> @mal [here is a random example of a aosp device repo …], Thanks for the link. I assume, that the device repositories of Google are related to their Pixel devices, aren't they? Neither Jolla nor the UBports Foundation has told us, that we need a device repository for hardware adaption. This is new for me. … We would finally port a device, | 14:44 |
| T4 | that is not on the market, yet. I currently check whether the ODM is able to provide the prerequisits for a hardware adaption of an available model. | 14:44 |
| mal | @m_aurel hmm, so in the sources you got you don't have anything like that? | 14:46 |
| T4 | <m_aurel> The zipped firmware has a size 3,37 GB and contains the boot.img, many further *.img files ... unfortunately no source code ... . The source code we got is just for the kernel. | 14:55 |
| *** qtwyeuritoiy is now known as ambernite | 15:02 | |
| T4 | <adampigg> Not so much porting done this afternoon. ... | 15:51 |
| T4 | <adampigg> (Document) http://149.202.119.142:9090/JahY1xXmKO.jpeg | 15:53 |
| T4 | <m_aurel> By the way. I think my colleage has already asked this question in this or another forum: Woud the hardware adaption of Nemo Mobile almost the same as the one for Sailfish OS? We think about Nemo Mobile as a fall back. | 15:53 |
| T4 | <adampigg> (Document) http://149.202.119.142:9090/hthfeQrfnQ.jpeg | 15:55 |
| mal | @m_aurel quite often people test nemo mobile by installing the packages to a sailfish device, it just a few packages | 15:56 |
| T4 | <m_aurel> I would be interesting to test a pure Nemo Mobile, because Sailfish seem to have much more system features beyond the obvious differences of different standard apps and system UI. | 15:59 |
| T4 | <m_aurel> We have ordered a Necunos device for the evaluation. the hardware adaption would almost be the same? | 15:59 |
| mal | it's quite the same | 16:03 |
| T4 | <m_aurel> Sounds good. | 16:04 |
| T4 | <m_aurel> @mal Do have another channel to send you the device link. Maybe you have an idea. | 16:11 |
| *** heroic_1_ is now known as heroic_1 | 16:41 | |
| T4 | <m_aurel> I will send another email to our ODM and ask the manger to forward another request for the build ID of the Code Aurora Project with an explenation, that we need to be able to build Android on our own to flash the device. Is that correct? | 16:45 |
| T4 | <m_aurel> Jolla just confirmed some minutes ago, that the build ID of the factory image doesn't help us. | 16:45 |
| mal | I don't really know much about those build IDs | 16:46 |
| T4 | <m_aurel> I also realized, that the build ID for the factory image is not unique. Google offeres a different download for each support4ed devices with the same build ID | 16:47 |
| T4 | <NotKit> I suppose your ODM does not use CodeAurora but has customized tree | 16:47 |
| T4 | <NotKit> what is the device SoC? does it have Project Treble support? | 16:48 |
| heroic_1 | m_aurel: ask them to send you the complete manifest. "some codeaurora branch" doesn't help you much | 16:48 |
| heroic_1 | fwiw, codeaurora is very similar to source.android.com, see https://source.codeaurora.org/quic/la/ | 16:48 |
| heroic_1 | you will get a specialized branch with your Board Support Package, e.g. https://source.codeaurora.org/quic/la/device/qcom/sepolicy/tree/common?h=LA.UM.6.3.r4-05900-sdm845.0 | 16:49 |
| heroic_1 | that one corresponds to google's crosshatch(=Pixel 3) device | 16:49 |
| T4 | <m_aurel> I was told that, Qualcomm provides modified Android Source Tree for their chipsets in the Code Aurora Project: https://wiki.codeaurora.org/xwiki/bin/QAEP/release. PCBA Board designer can use and modify it. | 16:50 |
| heroic_1 | yes, that is true. often times what qualcomm provides is not immediately useful, you need to adapt it a bit | 16:51 |
| heroic_1 | I don't know if you yourself are a technical person, but I would recommend that you build an AOSP image for some device to get familiar with the build process | 16:52 |
| heroic_1 | Or better, try to build a custom ROM like LineageOS or OmniROM. That way, you will get intimately familiar with what is required for porting | 16:53 |
| heroic_1 | Only if you have a working android image does it make sense to start porting sailfish | 16:53 |
| heroic_1 | Don't want to beat the drum too much, but you can get a used sony xperia x for ~100€, and building AOSP for it is completely seamless | 16:55 |
| heroic_1 | Then you can judge yourself whether you think you are able to port to a new device, and what to tell the person you're thinking of hiring | 16:56 |
| T4 | <m_aurel> Indeed, I'm not familar with HA. My education and focus is software requirements and development. I will try to hire a developer for the HA or outsource this to a company. My current task is to check, wether the ODM can provide, what this developer would need. Then I would go ahead with the commercial negotiation. However, it is not wron | 17:02 |
| T4 | g to deal with HA, and if it only serves to better specify requirements and control implementation as a product manager. | 17:02 |
| T4 | <m_aurel> @heroic_1 [you will get a specialized branch with your Bo …], Indeed, this kind of reference is what I requested.. | 17:03 |
| T4 | <m_aurel> What do you mean with manifest? The build tag of Code Aurora like LA.UM.7.6.2.r1-06900-89xx.0 is not sufficient? I know minifest files from Java projects. Is that the kind of manifest, you mean? | 17:06 |
| T4 | <m_aurel> By the way: the chipset of the current model is Qualcomm Quad-Core Snapdragon425 | 17:06 |
| heroic_1 | a manifest looks like this: https://android.googlesource.com/platform/manifest/+/android-9.0.0_r31 (it's the default AOSP one for Pie) | 17:32 |
| heroic_1 | it's pretty much an xml representation of the needed git repositories, their revision/branch name and into which folder they get cloned | 17:33 |
| heroic_1 | this would be an example of a project using codeaurora directly https://github.com/halogenOS/android_manifest/blob/XOS-8.1/snippets/caf.xml | 17:36 |
| heroic_1 | codeauroa is often shortened to "caf" btw | 17:36 |
| heroic_1 | same with qualcomm -> qcom | 17:36 |
| heroic_1 | snapdragon 425 is msm8917 so no caf branch I can see for it. most likely you're gonna get an ancient kernel like 3.10 or sth, which will make porting an Oreo-based sailfish image very unlikely | 17:40 |
| heroic_1 | I guess you want to keep the budget down, maybe for emerging markets, but your devs are going to hate you since your bsp will be based on marshmallow or sth | 17:42 |
| heroic_1 | and qcom almost never updates the bsp to recent android versions once they've sold it, they only maintain security patches | 17:43 |
| T4 | <NotKit> 425 is newer than 3.10 | 17:45 |
| T4 | <NotKit> probably 3.18 | 17:45 |
| T4 | <m_aurel> Yes, I can confirm, that the kerne source code, we got is named msm-3.18 | 20:29 |
| T4 | <m_aurel> @heroic_1 [snapdragon 425 is msm8917 so no caf branch I c …], Not a good news. I will ask the ODM on which chispset the successor model will be based. | 20:31 |
| T4 | <NotKit> I think your best reference devices in case of going LineageOS way are Xiaomi Redmi 4A/5A, maybe Moto E5 | 20:31 |
| T4 | <NotKit> that way basing on Oreo is possible (but SailfishOS does not care much about Android base in terms of core functionality, except for Alien Dalvik) | 20:33 |
| T4 | <m_aurel> So you suggest to work on a LineageOS image first and afterwards on a Sailfish adaption? | 20:36 |
| T4 | <NotKit> that's one way, another is AOSP/CAF build, depends on what is easier to get running for particular device | 20:38 |
| T4 | <m_aurel> I'll add a request for the manifest file in my response to the ODM with a follow up call next week, | 20:42 |
| T4 | <m_aurel> Xaomi Redmi 4A is based in the same chipset. So we might start to play around with this LineageOS port. Is that your suggestion? https://github.com/sayan-tan/device_xiaomi_rolex | 20:52 |
| T4 | <NotKit> that's too new probably. Which version is your stock Android? | 20:56 |
| T4 | <m_aurel> Oero 8.1 | 20:57 |
| T4 | <NotKit> then it has Treble, maybe better https://github.com/LineageOS/android_device_xiaomi_santoni/tree/lineage-15.1 | 20:58 |
| T4 | <m_aurel> This is Snapdragon 435 like the Accione P | 21:01 |
| T4 | <NotKit> yes, I know, but rolex tree you linked says it was based on santoni | 21:02 |
| T4 | <m_aurel> Surprising becuase of so different chipsets. | 21:03 |
| T4 | <m_aurel> Accione P is by the way very fast. Even the old Sailfish browser. We have two devices of the model here. | 21:04 |
| T4 | <NotKit> surprised you managed to get it, newer saw it in real life | 21:04 |
| T4 | <m_aurel> We are in direct contact with Jala and got some devices for our focus group. | 21:06 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
