07:00:41 <flypig> #startmeeting Sailfish OS, open source, collaboration -- 28th April 2022
07:00:41 <sailbot> Meeting started Thu Apr 28 07:00:41 2022 UTC. The chair is flypig. Information about MeetBot at http://wiki.debian.org/MeetBot.
07:00:41 <sailbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
07:00:48 <flypig> #info Meeting information and agenda can be found here:
07:00:53 <flypig> #link https://forum.sailfishos.org/t/community-meeting-on-irc-28th-april-2022/11173
07:01:03 <flypig> I am the meeting's chairperson today, and will be doing my best to keep time and order. Please respect the timings and collect your grades at the end (the Sailors all got high-Cs).
07:01:09 <flypig> (that's supposed to be a joke)
07:01:15 <flypig> #topic Brief introduction (5 min). Please prefix your name/handle with #info
07:01:23 <ExTechOp> #info Otto Mäkelä, community
07:01:30 <pherjung> #info pherjung, community
07:02:26 <flypig> #info David Llewellyn-Jones, sailor @ jolla
07:03:04 <sebix[m]> #Info Sebix, community
07:03:05 <sledges> #info Simonas Leleiva, privateer
07:05:07 <abr> #info Andrew Branson, slightly in hospital
07:05:34 <flypig> Oh, hope you're okay Andrew?
07:06:36 <flypig> A score draw, 3:3
07:06:40 <abr> Yeah lovely and bored thanks
07:06:47 <krnlyng> #info Frajo Haider, developer at jolla
07:07:13 <flypig> Okay, glad you're okay Andrew. Hopefully we can help your boredom for an hour or so.
07:07:24 <flypig> Late goal leaves us 4:3 to the sailors.
07:07:25 <thilo[m]> #info thigg, comunity dev, lurking
07:07:40 <thilo[m]> No ;) 4:4
07:07:46 <flypig> Good shot :)
07:07:53 <flypig> Alright, let's head to our first question.
07:07:57 <flypig> #topic Poll users for Sailfish OS upgrade experience (10min -- asked by direc85)
07:08:06 <flypig> #info <direc85> As users tend to write more about issues than successes about a Sailfish OS release in its release notes thread (Vanha Rauma is the prime example), the majority about posts tend to be negative.
07:08:16 <flypig> #info <direc85> This can be off-putting to cautious users, as the thread seems to be mostly about issues.
07:08:23 <flypig> #info <direc85> To combat this, and to help everyone get more realistic picture about a software update, I suggest that a standard poll is added to release notes to see how the update went.
07:08:32 <flypig> #info <direc85> It should probably separate the early access phase and the final release, so two polls could possibly be held side by side.
07:08:39 <flypig> #info <direc85> As an example, Manjaro Linux, which I use, has this practice.
07:08:45 <flypig> #info <direc85> I like to pop in and leave a vote after an update, and from my own experience, it works well for both the community and the devs.
07:08:52 <flypig> #link https://forum.manjaro.org/t/stable-update-2022-04-15-kernels-mesa-nvidia-budgie-pipewire-libreoffice-kde-frameworks-wine/108422
07:09:23 <flypig> Unfortunately direc85 couldn't make it to the meeting, but we have an answer at least.
07:09:31 <flypig> #info <Jolla> Thank you for this suggestion. There's plenty to agree with in what you write, and since we didn't want to delay until the meeting today, we went ahead and implemented your great idea.
07:09:37 <flypig> #link https://forum.sailfishos.org/t/release-notes-vanha-rauma-4-4-0/10656#how-did-the-upgrade-go-61
07:09:43 <flypig> #info <Jolla> The current poll shows the following results: 79% no issues; 16% small issues; 5% serious issues. It's not a direct comparison, since the wording is different, but these results aren't dissimilar to those in the Manjaro poll (88%, 5%, 7%).
07:09:55 <flypig> #info <Jolla> We'll continue to post a similar poll for future releases. We'd be interested to hear about your thoughts on the poll results.
07:10:02 <flypig> #info <Jolla> It raises also the question about whether there are other great ideas like this that would be worth considering.
07:10:22 <flypig> That's the answer. Did everyone here vote already?
07:10:29 <pherjung> Yes :)
07:10:47 <sebix[m]> btw, openSUSE Tumbleweed (Rolling Release Distro) has something very similar: https://review.tumbleweed.boombatower.com/
07:11:10 <pherjung> Just curious, some here have various phone. Is there any possibility to vote various time?
07:11:24 <flypig> #info <sebix[m]> openSUSE Tumbleweed (Rolling Release Distro) has something very similar
07:11:29 <flypig> #link https://review.tumbleweed.boombatower.com/
07:12:13 <sebix[m]> flypig: No, didn't upgrade because of existing issues.
07:12:14 <flypig> That's a lot of info behind that link.
07:12:41 <flypig> pherjung, I'm pretty certain the forum only allows one vote per account I'm afraid.
07:13:06 <flypig> sebix[m], which issues, if you don't mind me asking?
07:13:24 <sebix[m]> flypig: They have a faster release cycle and heavier testing of course. But it's a similar objective though.
07:13:26 <ExTechOp> (I voted, adding to "no issues")
07:14:05 <Thaodan> #info Björn Bidar - Sailor @ Jolla
07:14:08 <Nico> #info Nico, late community member
07:14:12 <Thaodan> Sorry guys I'm late
07:14:12 <sebix[m]> flypig: Unfortunately I need to leave the meeting in one minute, sorry :(
07:14:22 <flypig> Nice to see you both.
07:14:36 <flypig> sebix[m], no worries, glad you could make it briefly!
07:14:52 <dcaliste> #info Damien Caliste, community
07:14:58 <dcaliste> (sorry to be late)
07:15:07 <flypig> Glad you're here dcaliste.
07:16:37 <flypig> Okay, well, I think we answered direc85's question, so I suggest we move on and have more time for later questions.
07:16:55 <Nico> Hm, how many moderators are there on the forum? Could some community members help out there, since Jolla said they need to cut down community interaction, maybe some trusted community members could help with tagging bug reports and organizing threads? (re other suggestions)
07:17:40 <flypig> I think that's something for pherjung to comment on.
07:17:44 <Nico> (Also I expect more people to vote next time, none who had a good upgrade is probably going back to that thread)
07:18:15 <pherjung> Nico: In that case, we are 3 (nephros, thilo[m] and me). We collect all data and provide them to flypig.
07:18:17 <Thaodan> I think we talked about something like this last time? It clearly sounds like an dejavu for me.
07:18:22 <flypig> Nico, I agree. I was impressed that so many votes came in so quickly to be honest, given it was added later.
07:18:25 <Nico> Well, if you think you don't need any help, that's good too, but I'll let you thin about it :D
07:18:44 <pherjung> Well, if you want to join us you're welcome.
07:19:12 <pherjung> but, let's go further. We can discuss about it later
07:19:13 <Thaodan> What we need IMHO is more hightlighting of different types of user rolles in the forum, e.g. Jolla staff vs. trusted users.
07:19:16 <flypig> We have a bug roundup topic on the agenda today. Perhaps we could discuss this further there.
07:19:24 <Nico> Hm, sure, why not. I wasn't as active recently as I am finishing up a thesis but I could do some things here and there
07:19:28 <flypig> Thaodan, I agree with that too.
07:19:32 <Nico> Thaodan, true
07:19:43 <flypig> Nico, we'd love to have your input.
07:20:25 <flypig> Let's move on to the next question.
07:20:28 <flypig> #topic Toggle-able option to add digits row in keyboards (5 min -- asked by remote)
07:20:35 <flypig> #info <remote> Last 3 phones are 21:9, so having digits row is convenient.
07:20:38 <Nico> Maybe if there is no easy way to add mod/jolla status to profiles, we could at least put it in a thread or so, where people can look it up
07:20:47 <flypig> #info <remote> 3d party solutions (not for every language) exist, manual patching (tedious, resets every update) exists.
07:20:56 <flypig> #info <remote> But I don't see why this can't be implemented in stock.
07:21:33 <flypig> Here's the answer from Jolla.
07:21:35 <flypig> #info <Jolla> Thanks for this suggestion. We've created a task on our Bugzilla related to this so we can discuss it further internally. We're considering ways to improve the keyboard right now and will add this to the mix.
07:21:46 <flypig> #info <Jolla> However, we don't have any immediate plans to implement it for an upcoming release.
07:21:52 <flypig> #info <Jolla> Would you be able to share links to the 3rd party solutions that you mention? We'd be interested generally in opinions from the community about how best to improve the keyboard.
07:22:12 <flypig> I don't think remote was able to make it today.
07:22:48 <Thaodan> I think having a concrete solution and a quick path is a different thing.
07:22:59 <Nico> Possibly https://openrepos.net/content/adel/multi-keyboard-layouts ?
07:23:17 <pherjung> Related to the the keyboard, there is a patch from leszek increasing the bar space. Very useful.
07:23:19 <flypig> #link https://openrepos.net/content/adel/multi-keyboard-layouts
07:23:20 <ExTechOp> A keyboard improvement would also be creating a fix for what seems to bug a fair amount of people (including me): the narrow space bar https://forum.sailfishos.org/t/space-bar-narrow-width-is-making-me-want-to-switch-to-android/6470
07:23:22 <flypig> Thanks for that Nico
07:23:28 <Thaodan> I would think it is possible to apply smaller fixes like increasing the spacebar side but larger works could take time.
07:23:34 <flypig> pherjung, do you have a link for that?
07:24:09 <Thaodan> flypig:it is included in the openrepos link
07:24:20 <flypig> Thaodan, agreed, the spacebar fix could be a small, quite quick change. Unfortunately anything with the keyboard requires some work, because there are many of them.
07:24:29 <flypig> Thaodan, perfect, thanks (regarding the link)
07:24:55 <Thaodan> flypig: They spacebar is the same in all keyboards (I tried to do similar stuff years ago)
07:25:06 <Nico> I am actually somewhat happy with the keyboard. Not to say that it can't be improved, more that I would wish the finger term keyboard was as good :D
07:25:16 <pherjung> flypig: looking for it. Name is Wide Spacebar or SailfishOS 4
07:25:22 <flypig> So, is the general view here that the spacebar should be wider, and the comma/fullstop keys thinner?
07:25:32 <Thaodan> I think so
07:25:40 <dcaliste> There is also the repo from ichthyosaurus : https://github.com/ichthyosaurus/sailfish-public-patch-sources
07:25:51 <flypig> Nico, would you like Fingerterm to use the standard keyboard?
07:26:02 <flypig> #link https://github.com/ichthyosaurus/sailfish-public-patch-sources
07:26:04 <pherjung> flypig: here is it https://coderus.openrepos.net/pm2/project/widespacebar-llelectronics
07:26:12 <flypig> #link https://coderus.openrepos.net/pm2/project/widespacebar-llelectronics
07:26:21 <dcaliste> It has a lot a various keyboard patches that could be worth give a look to.
07:26:29 <Nico> flypig: Not quite, having some of the command keys is useful, but the fingerterm keyboard is so different and the keys are so small, that they are hard to hit :3
07:26:39 <Nico> Made sense on small screens, now it is a bit of a bother
07:27:03 <Thaodan> the fingerterm keyboard could scale but that is another issue.
07:27:12 <flypig> Nico, the nice thing about Fingerterm is that it's full open, so if you have ideas, they can be fixed with a PR.
07:27:35 <Nico> Yep... once I have free time again I can look at that :D
07:27:47 <Nico> (I'm not good with UI stuff though)
07:28:28 <flypig> No worries Nico (although I'm sure you are), and of course, just because you don't create a PR, doesn't mean you can't ask for an improvement.
07:28:59 <flypig> Alright, remote only asked for 5 mins on this topic, so we should move on. Many thanks for the useful links everyone.
07:29:11 <flypig> #topic Bug roundup (15 mins -- asked by pherjung)
07:29:30 <flypig> #info <Jolla> The Community Bug Coordination team have been herding bugs beautifully this week.
07:29:33 <Nico> I was partially also asking if anyone else wanted to see improvements to the fingerterm keyboard too :3
07:29:50 <flypig> #info <Jolla> The idea here is for us to go through the bugs they've highlighted to try to get movement on them.
07:30:08 <flypig> Nico, I would be one :)
07:30:09 <flypig> Many thanks for all of your work in shepherding bugs this week. I've been through the list you provided. Let me summarise where things are at, and I'd appreciate your opinions on some of them.
07:30:26 <flypig> #info 1. The following have been tagged as tracked or fixed:
07:30:31 <flypig> #link https://forum.sailfishos.org/t/10916
07:30:34 <flypig> #link https://forum.sailfishos.org/t/1181
07:30:40 <flypig> #link https://forum.sailfishos.org/t/10741
07:30:43 <flypig> #link https://forum.sailfishos.org/t/10894
07:30:45 <flypig> #link https://forum.sailfishos.org/t/8944
07:30:52 <flypig> #info 2. I've asked internally about the following in case they're already fixed. Depending on the result, I'll either mark them as tracked or fixed.
07:30:58 <flypig> #link https://forum.sailfishos.org/t/8294
07:31:01 <flypig> #ink https://forum.sailfishos.org/t/2032
07:31:04 <flypig> #info 3. I've posted a reply on this topic to try to get more info, and tagged the related bug report as tracked.
07:31:11 <flypig> #link https://forum.sailfishos.org/t/10848
07:31:15 <flypig> #info 4. Asked internally and Thaodan, who worked on the change, has replied to this bug:
07:31:20 <flypig> #link https://forum.sailfishos.org/t/10930
07:31:25 <flypig> #info 5. It looks like this issue here is due to lack of VoLTE. I've posted a reply, but I think there's no appropriate way to flag the bug.
07:31:31 <flypig> #link https://forum.sailfishos.org/t/1593
07:31:35 <flypig> #info 6. I've requested the OP to mark this bug as "solved". I'm not sure it makes sense to flag it as either tracked, or fixed though. What do you think?
07:31:42 <flypig> #link https://forum.sailfishos.org/t/9149
07:31:47 <flypig> #info 7. I'm not sure what the right approach is for this bug. It seems to be related to failed updates, which are notoriously hard to debug.
07:31:51 <flypig> #link https://forum.sailfishos.org/t/10792
07:31:57 <flypig> That's all of 'em. I'd appreciate your thoughts on how to tackle the more complex ones here.
07:32:18 <flypig> And sorry for the text dump. I'm not sure how this process should best work; we should refine it!
07:32:42 <Nico> I have to say, seeing such a dump of bug triaging feels weirdly encouraging :D
07:33:32 <flypig> Okay, that's a good sign then :) pherjung thilo[m] and nephros put in a lot of work.
07:33:55 <Nico> Thanks, guys!
07:34:49 <flypig> Any thoughts on 5, 6 or 7 especially?
07:35:01 <dcaliste> Many thanks to the bug shepherds.
07:35:46 <pherjung> In any case, as long as there is a comment with the latest information it's fine for me
07:36:14 <flypig> Will they cause you problems if they're not tagged pherjung?
07:37:26 <thilo[m]> Tagged as tracked you mean?
07:38:23 <flypig> Well, at the moment the best outcome is to get things tagged as "tracked" or "fixed" I think. But not all of these could be.
07:38:23 <pherjung> I think not. As long as it is noted somewhere, it's okay
07:38:44 <flypig> Okay, that's good to hear.
07:39:03 <pherjung> And currently it's noted in a framalist. So I know this bug report has already been seen
07:39:10 <thilo[m]> Can we tag them as seen?
07:39:34 <flypig> Would that be useful? I'm happy to do that if it would be useful.
07:39:39 <pherjung> A tag is in any case better
07:39:46 <thilo[m]> Yes
07:39:56 <thilo[m]> Because then we can filter them
07:40:02 <Nico> About 7 it might be nice to have an accepted solution of "run this to complete the upgrade" on that thread for others to find and a general bug to improve upate reliability to prevent such things from happening in the future?
07:40:32 <dcaliste> Maybe add a new 'pending' tag for them ?
07:40:33 <pherjung> What about: tracked-by-community? Or something similar
07:40:42 <pherjung> oh, pending is much better
07:40:58 <thilo[m]> Yes
07:41:06 <flypig> 7. is thilo[m]'s bug I think?
07:41:19 <thilo[m]> And either they are no bug reports or they will be tracked or declined
07:41:30 <flypig> Okay, so we add a "pending" tag? That works for me.
07:41:52 <Thaodan> flypig: pending sounds good
07:41:58 <pherjung> Great :)
07:42:06 <flypig> #action flypig to request a "pending" tag be added.
07:42:24 <flypig> #info Bugs which have been considered, but are neither tracked nor fixed, will get a pending tag.
07:42:40 <Thaodan> Pending would help us look into bugs.
07:43:00 <thilo[m]> Sorry my phone doesnt like more than one app open right now apperantly. Cant look
07:43:06 <flypig> Excellent. Good progress :)
07:43:16 <Nico> How are you triaging incoming reports btw? Would broadly categorizing them into "calls", "apps", "upgrade process" or similar help you to get the right people look at it or is it the same person creating bug reports anyway?
07:43:38 <pherjung> flypig: could you than update your thread https://forum.sailfishos.org/t/notes-on-tagging-bug-reports/11252 ?
07:44:12 <thilo[m]> Bug #7 was resolved for me after a while just left it open for others
07:44:21 <flypig> pherjung, thanks for suggesting that, I would have missed it. Once the tag exists I'll update the post.
07:44:28 <pherjung> :)
07:44:47 <flypig> thilo[m], could you do as Nico suggests and create an accepted solution? Would that work there?
07:45:05 <thilo[m]> Ill take a look
07:45:10 <flypig> Great, thank you.
07:45:40 <flypig> Nico, concerning categorising reports, could you elaborate?
07:45:45 <Nico> Funny that the "how to tag bug reports" is not stickied to the top of the bug reports :D
07:46:48 <Nico> flypig: I usually use tags to broadly categorize areas something falls in when triaging my bugs, so that I can quickly look at everything not fixed with a voip label to check, if I fixed anything else too by accident.
07:47:16 <Nico> Not sure if that is useful on the forum, but it could maybe make it easier for Jolla peeps to pick out bugs related to the area they are working on
07:47:24 <Nico> Or it would just be useless overhead :D
07:47:52 <flypig> We do add tags when they get transferred to our internal bugzilla.
07:48:17 <Nico> Yeah, it is probably just unneeded duplication then?
07:48:54 <flypig> I think it's possible it's easiest for us to categorise them, since many of the categories are quite technical (e.g. related to the relevant component). That may not always be obvious to bug reporters.
07:49:05 <pherjung> As long the bug report has a good description and can be reproduced, it's not necessary. I think.
07:49:30 <pherjung> Some user (I'm the first) wouldn't categorize correctly
07:49:56 <Nico> Mhm, makes sense :3
07:50:08 <flypig> It's a nice idea Nico. I'd suggest we revisit it in the future, see how things go in the meantime.
07:50:12 <flypig> We're hitting time on this topic. Should we do the same again at the next meeting?
07:50:20 <Thaodan> Usually the more tags the better as long as it is not the wrong tags, however in Jolla together it also worked so I think we will make it work.
07:50:33 <pherjung> flypig: yes :)
07:50:51 <pherjung> Oh, just asking. Is it okay for you 10 bug reports + all fixed one?
07:51:04 <pherjung> Like I did for this community meeting?
07:51:05 <flypig> #info Nico suggested to consider adding tags to categorise bugs to the forum.
07:51:22 <flypig> pherjung, I think it worked well, so fine by me, yes.
07:51:29 <Nico> I think the bug reporting section was really usefull and should definitely be something somewhat regular :3
07:51:45 <flypig> Okay, that's a great vote of confidence. Thanks Nico.
07:51:53 <thilo[m]> <3
07:52:02 <flypig> Let's move on.
07:52:04 <flypig> #topic Status of VoLTE (10-15min -- asked by Solrac)
07:52:11 <flypig> #info <Solrac> There have been some concerns with the implementation of VoLTE, specially now that it is starting to become mandatory in some countries (most notably in the US).
07:52:19 <flypig> #info <Solrac> Unfortunately, it has already been stated that older devices will not recieve VoLTE support, which brings up another concern that I'd like to ask about as well.
07:52:29 <flypig> #info <Solrac> What might be the state of VoLTE at the moment? Might there be a roadmap?
07:52:36 <flypig> #info <Solrac> Is it planned to arrive with 4.5, or would it be an update for 4.4, or would it be a simple package update?
07:52:43 <flypig> #info <Solrac> And would be only implemented for officially supported devices, or will it be possible to implement it in community builds (for porting to other devices)
07:52:55 <flypig> Here's our reply.
07:53:02 <flypig> #info <Jolla> Thank you for the question. This topic was last discussed in the community meeting on 9th December, so this is a good opportunity to revisit it.
07:53:11 <flypig> #info <Jolla> As we stated there "The initial target is to enable VoLTE for Sony Xperia 10 II and III".
07:53:17 <flypig> #link https://forum.sailfishos.org/t/community-meeting-on-irc-9th-december-2021/9310/5
07:53:23 <flypig> #info <Jolla> On the Vanha Rauma blog post we detailed that development of the new telephony adaptation needed for VoLTE is progressing.
07:53:30 <flypig> #info <Jolla> There we also posted a video of the VoLTE prototype demonstrating simultaneous data and calls, which is definitely worth a look if you've not seen it already.
07:53:37 <flypig> #link https://blog.jolla.com/vanharauma/
07:53:39 <flypig> #link https://youtu.be/c2E69IAAvzc
07:53:43 <flypig> #info <Jolla> However, beyond the fact that we still plan to bring VoLTE support this year, we don't have a public roadmap for it.
07:53:50 <flypig> #info <Jolla> Concerning community builds, this will very much depend on the specifics of the devices in question. Rest assured, as soon as we have more to say publicly, we will make it known loudly.
07:54:32 <flypig> Solrac wasn't sure if they'd be able to make it today.
07:54:58 <flypig> But if anyone else would like to comment, please do feel free.
07:55:35 <Nico> Will all the VoLTE stuff be open-source for people to take a stab at it to port it elsewhere? Probably was mentioned somewhere already at some point, but...
07:56:05 <Thaodan> Sony devices usually have an easier time adopting those things however VoLTE has to work on the device in AOSP first  usually.
07:56:45 <flypig> Thaodan, that's in relation to VoLTE on community adaptations?
07:56:59 <Thaodan> flypig: yes
07:58:14 <flypig> Nico, I think that's an unknown at this point (maybe some other sailor with better info can say?)
07:58:55 <ExTechOp> Ceterum censeo, talking about Sony Xperia 10 III, is there yet a timeline on when SFOS would be available?
07:59:14 <Nico> Oki, I think it would be encouraging to some if that was known, because then they could easily say they can port it to their own devices without needing to play with a black box :3
07:59:57 <flypig> It's a bit early for Latin for me :)
08:00:25 <flypig> Nico, understood. Would you like the comment added to the minutes?
08:01:09 <Nico> Well, I would appreciate a statement from Jolla about that probably, if adding it to the minutes helps with that, then I would like that too :3
08:01:24 <flypig> ExTechOp, nothing public yet, I don't think. Maybe someone else can correct me.
08:02:15 <flypig> #info <Nico> Will all the VoLTE stuff be open-source for people to take a stab at it to port it elsewhere?  I think it would be encouraging to some if that was known, because then they could easily say they can port it to their own devices without needing to play with a black box.
08:02:26 <Nico> ty <3
08:05:18 <flypig> We reached time on this topic, so let's go to General Discussion.
08:05:23 <flypig> #topic General discussion (20 min)
08:05:23 <thilo[m]> Would also be interesting to know if it is possible to make a community port for older sony devices. Its a bit sad i cant get this on my xa2
08:06:13 <pherjung> Nico: would you like to join the Bug Coordination Group?
08:07:00 <Nico> Hm, sure, why not, but I will probably not be active for the next 2 weeks, but after that I could probably contribute properly :3
08:07:18 <sleepnicely[m]> <ExTechOp> "Ceterum censeo, talking about..." <- I am also curious when it is going to be ready since I only have the Xperia 10 III 🥺
08:07:40 <thilo[m]> We're having lots of fun there ;)
08:07:46 <Nico> Forum account: https://forum.sailfishos.org/u/kuroneko/summary
08:07:47 <thilo[m]> And all the bugs
08:07:59 <pherjung> Nico: what's your telegram's Nickname?
08:08:09 <Nico> Oh boy
08:08:25 <thilo[m]> Note that this is public here
08:08:27 <Nico> That is a good question, I only every use my telegram bridge nowadays
08:09:17 <flypig> sleepnicely[m], we're working to get it to you as soon as we can, rest assured. We want you to be able to fully use your 10 III.
08:09:37 <Nico> pherjung, I'll dm you?
08:09:55 <pherjung> Nico: ok
08:10:00 <thilo[m]> Anyone knows if someone tried a ccommunity port of a newer android version to the XA2? (although it would be quite pointless regarding android apps)
08:10:54 <thilo[m]> I heard the 10III is buggy on android, are you struggeling with that as well?
08:12:08 <Nico> Anyway, I need to go now, I need to catch a train, thanks everyone!
08:12:53 <flypig> Thanks Nico, safe travels!
08:13:03 <flypig> And best of luck with your thesis.
08:13:39 <Nico> Thank you <3
08:19:33 <flypig> thilo[m], XA2 is nile, which Sony provides firmware blobs for up to Android 11 it seems, so I suppose it's possible, but I don't know that's it's been done.
08:23:05 <flypig> thilo[m], from internal discussions, it seems different bases have different issues, and the XA2 based on 8 is in good shape, so it's unlikely a newer base would inherently make it better.
08:23:47 <Thaodan> Newer kernel and vendor could bring improvements
08:24:34 <Thaodan> Newer kernels have better cgroup support etc.
08:25:11 <flypig> Maybe it's something to try then (not by me though: I don't have the skills).
08:25:44 <flypig> Alright, we heading to wrapping up time. Does anyone want anything added to the minutes from the discussion?
08:26:09 <flypig> Or any final remarks?
08:26:23 <ExTechOp> I'd really like to run SFOS on 10 III :-D
08:26:40 <sleepnicely[m]> thilo: I only got the 10 III 4 days ago, but haven't experienced any bugs yet, just the camera is little bit too slow while launching but I don't really care about camera in a phone that much
08:27:18 <flypig> #info Much interest for the Xperia 10 III release of Sailfish OS.
08:27:20 <ExTechOp> Oh, and I'd like to thank piggz for the "Advanced Camera"
08:27:42 <flypig> You want that in the minutes?
08:27:46 <abr> Xa2 wouldn't be good on 64bit
08:28:06 <ExTechOp> flypig No, I just noted he is here and wanted to ping him
08:28:32 <flypig> ExTechOp, good that you did! Thanks.
08:29:24 <flypig> abr, do you want to elaborate?
08:31:17 <flypig> Okay, we should wrap up. It's a shame the people who submitted questions weren't here today to discuss them, but I'm glad we had some nice discussions anyway.
08:31:24 <flypig> #topic Next meeting time and date (5 min)
08:31:30 <flypig> Proposing Thursday 12th May at 07:00am UTC
08:32:02 <Thaodan> ExTechOp: Go build it :p
08:32:07 <ExTechOp> WorksForMe
08:32:30 <flypig> Alright, and no objections, so let's call that a decision :)
08:32:36 <flypig> #info Next meeting will be held on Thursday 12th May 2022 at 07:00am UTC:  2022-05-12T0700Z
08:32:46 <abr> Just that it's a bit low on RAM. Would most likely get more oom problems than the newer xperias
08:33:16 <flypig> Okay, a nice remark to wrap up on. Thank you abr, and thanks to everyone today for some nice discussion and good progress.
08:33:22 <flypig> #endmeeting