#sailfishos-meeting: Sailfish OS, open source, collaboration -- 30th March 2023

Meeting started by ViGe at 08:00:10 UTC (full logs).

Meeting summary

    1. Meeting information and agenda can be found here: (ViGe, 08:00:15)
    2. https://forum.sailfishos.org/t/community-meeting-on-irc-30th-march-2023/15013 (ViGe, 08:00:19)

  2. Brief introduction (5 min). Please prefix your name/handle with #info (ViGe, 08:00:35)
    1. Ville Nummela, sailor @ Jolla, chairperson today (ViGe, 08:01:00)
    2. Otto Mäkelä, community (ExTechOp, 08:01:47)
    3. pherjung, community (pherjung[m], 08:02:27)
    4. crun, community (crun, 08:03:08)
    5. Damien Caliste, community (dcaliste, 08:03:21)
    6. David Llewellyn-Jones, community (flypig, 08:03:40)
    7. nas nas, community (nas, 08:04:24)
    8. Andrew Branson, sailor! (abr, 08:05:26)

  3. Will there be an official port for Xperia 10 iv? (5 min -- asked by martinbook85) (ViGe, 08:05:56)
    1. <martinbook85> Jolla / Sailfish has had an official port for all the middle range Xperia phones since Xperia X, continuing with Xperia XA2, Xperia 10, Xperia 10 ii and Xperia 10 iii. (ViGe, 08:06:04)
    2. <martinbook85> The 10 iii is somewhat difficult to get at a reasonable price and therefore several (5-10 that I have encountered, maybe more) people have gone out to get an Xperia 10 iv. (ViGe, 08:06:08)
    3. <martinbook85> There has been no promise about a port for Xperia 10 iv but it is still available for purchase at quite an OK price. (ViGe, 08:06:12)
    4. <martinbook85> It would therefore be good to know if there will be an official port. (ViGe, 08:06:15)
    5. <Jolla> Sony Xperia 10 IV is plausible candidate for the officially supported Sailfish X device. (ViGe, 08:06:32)

  4. Add the ability to change haptics in keyboard / improve reactivity (5 min -- asked by Valorsoguerriero97) (ViGe, 08:10:32)
    1. <Valorsoguerriero97> The default sailfish keyboard is frustating because of its weak haptics, I ask for having the GUI to change vibration intensity and to improve its reactivity on SFOS forum. (ViGe, 08:10:38)
    2. <Valorsoguerriero97> Try posting with it on default browser and you'll experience heavy lags. (ViGe, 08:10:42)
    3. <Valorsoguerriero97> However the biggest thing I would love to see is the option to have low/medium/strong haptic feedback. (ViGe, 08:10:45)
    4. <Valorsoguerriero97> Thx! (ViGe, 08:10:50)
    5. <Jolla> The haptic feedback details depend quite much on the hardware. (ViGe, 08:11:18)
    6. <Jolla> On some it’s nicely fast and precise while on cheaper haptic modules it takes some time to start. (ViGe, 08:11:22)
    7. <Jolla> The device isn’t mentioned here, but perhaps the device configuration on the amount could be checked. (ViGe, 08:11:25)
    8. <Jolla> However, increasing the force might mean delaying the lag on feedback start and stop. (ViGe, 08:11:28)
    9. Adam Pigg, community (piggz[m], 08:12:29)
    10. Lukáš Karas, community developer (karry, 08:15:12)

  5. Right-To-Left Optimization(RTL) (5 min -- asked by mad_dev) (ViGe, 08:15:49)
    1. <mad_dev> RTL is not yet optimized in SFOS, where input fields and headers are automatically text aligned to the right if the script is right to left. (ViGe, 08:15:54)
    2. <mad_dev> I have also sent an email on March 13 with the same topic. (ViGe, 08:15:57)
    3. <mad_dev> My question is, what is Jolla's stance on RTL, and is the patched solution(appending a mirroring declaration) the best way forward? (ViGe, 08:16:01)
    4. <Jolla> Proper RTL support is definitely a thing we’d like to have, but as we haven’t gotten big enough need for any RTL language yet, the polishing hasn’t been done. (ViGe, 08:16:09)
    5. <Jolla> On the details we’d likely keep the UI layout otherwise the same but just make sure the text fields work nicely right aligned. (ViGe, 08:16:13)
    6. <Jolla> Not sure what the mentioned patched solution is specifically. (ViGe, 08:16:17)
    7. https://forum.sailfishos.org/t/unofficial-rtl-support/671 (flypig, 08:18:38)
    8. https://github.com/Logic-gate/unofficial-jolla-language-pack-ar/blob/master/tests/rtls.sh (flypig, 08:19:21)

  6. - (5 min -- asked by crun) (ViGe, 08:20:48)
    1. <crun> Sailfish itself is now pretty usable. (ViGe, 08:20:53)
    2. <crun> However the X10iii has hardware related issues that are showstoppers for me - I cannot use it beyond a secondary phone. (ViGe, 08:20:55)
    3. <crun> These may all relate to Sony and the Sony AOSP. (ViGe, 08:20:58)
    4. <crun> Can any of them be fixed at all by Jolla, or are these just AOSP bugs in a now obsolete phone that Sony will never fix? (ViGe, 08:21:00)
    5. <crun> Standby Battery Drain. (ViGe, 08:21:04)
    6. <crun> GPS Lock is slow/unable when signal is weak - Side-by-side is different to Android. (ViGe, 08:21:06)
    7. <crun> Seems to be all Sonys, not just 10iii. (ViGe, 08:21:09)
    8. <crun> Internet/cell disabled - this is nothing to do with AGPS. (ViGe, 08:21:11)
    9. <crun> VoLTE does not configure/register on any of the 3 carriers in NZ Android or SFOS - registration appears disabled here, and my carrier blames Sony. (ViGe, 08:21:14)
    10. <crun> I can probably get the required configuration data from the carrier, but need a way to put it in the phone. (ViGe, 08:21:17)
    11. <crun> Does Sony block whole countries? (ViGe, 08:21:20)
    12. <crun> Is the X10iii whitelisted (i.e. (ViGe, 08:21:23)
    13. <crun> only Sony contracted carriers/regions will every work)? (ViGe, 08:21:25)
    14. <crun> Is this happening in blobs or is it something SFOS can access? (ViGe, 08:21:28)
    15. <crun> Do you know how VoLTE configures and registers (i.e. (ViGe, 08:21:31)
    16. <crun> what is going on here), or is this a block box to you as well? (ViGe, 08:21:33)
    17. <crun> Does Sony help in any meaningful way e.g answering questions now the X10iii is obsolete? (ViGe, 08:21:36)
    18. <crun> Can we get a might fix / can't fix acknowledgement? (ViGe, 08:21:39)
    19. <crun> To date there have not been any requests for tests/info on any of these topics. (ViGe, 08:21:42)
    20. <crun> I have both Android and SF X10iii's and can side by side compare them. (ViGe, 08:21:45)
    21. <Jolla> Sony does still fix issues in AOSP for Xperia 10 III. (ViGe, 08:22:22)
    22. <Jolla> We can’t comment on agreements between Sony and carriers. (ViGe, 08:22:25)
    23. https://forum.sailfishos.org/t/standby-battery-high-drain-on-xperia-10-iii/15208 (crun, 08:24:29)
    24. https://forum.sailfishos.org/t/gps-signal-very-bad/13026/35 (crun_, 08:37:06)

  7. Untracked bug reports (5 min -- asked by Community Bug Coordination Team) (ViGe, 08:38:27)
    1. <Community Bug Coordination Team> Our regular Community Bug Coordination Team update - see the forum for the links to actual bug reports (ViGe, 08:38:41)
    2. <Jolla> The Community Bug Coordination Team have done a superb job once again. (ViGe, 08:38:47)
    3. <Jolla> As a result of their work, we now have: (ViGe, 08:38:51)
    4. <Jolla> 7 high quality bug reports now recorded internally and tagged as "tracked". (ViGe, 08:38:55)
    5. <Jolla> 2 bug reports marked as "pending" more info. (ViGe, 08:38:59)

  8. Open PR discussion (5 mins -- asked by jolla) (ViGe, 08:42:53)
    1. <jolla> Any open PRs to discuss? (ViGe, 08:43:05)

  9. General discussion (20 min) (ViGe, 08:47:15)
    1. <abr> For the VoLTE, the device firmware contains modem configs for each operator, that come from the carriers themselves. (ViGe, 08:49:01)
    2. <abr> you can see hem all in /vendor/firmware_mnt/image/modem_pr/mcfg/configs on the device (ViGe, 08:49:18)
    3. https://github.com/sailfishos/mce/pull/14 could use some review and discussion (ViGe, 09:05:47)

  10. Next meeting time and date (5 min) (ViGe, 09:07:23)
    1. Next meeting will be held on Thursday 13th April 2023 at 07:00am UTC: 2023-04-13T0700Z (ViGe, 09:11:26)


Meeting ended at 09:11:51 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. ViGe (101)
  2. crun_ (17)
  3. flypig (16)
  4. pherjung[m] (7)
  5. dcaliste (6)
  6. crun (5)
  7. abr (5)
  8. ExTechOp (4)
  9. karry (4)
  10. sailbot (2)
  11. nas (1)
  12. piggz[m] (1)


Generated by MeetBot 0.1.4.