matf-kabouik

The good news is we now have more time to convince them about improved layouts. :> I must admit I was secretly hoping the March production batches would be delayed, so that we could at least get some feedback on the layouts suggestions that were sent, and a chance for Nordic and Azerty backers to see what they purchased before delivery.

I could wait even longer. The Pro1x is a device I plan on using for years, it's an investment for the long term and being niche, I know it won't get iterations and updates every year. I'd rather wait years and have it finally delivered with no compromises. An older SOC is not an issue for me, I plan on using mainline eventually, which also answers the question on whether I care about certification (however, I believe having Android as an option really increased the backer base and was therefore likely a sound decision). My plan is to use the device to run Mobile Linux, meaning it's best if the

I like the shifted keyboard! Especially on Sailfish since there is no toolbar on the right of the screen (in landscape), so having hands properly centred on the keyboard is great. I'll make an opinion on unshifted when I get my Pro1x, but I really hope they take the community feedback/suggestions into account when placing / and ? keys. :/

You're implying I suggested it. I did not, I think I even wrote the opposite, and I didn't detail how to do it either. What I did say is there is no technical/hardware limitation to running Alien Dalvik and other paid Sailfish X software on a Pro1, as was also posted by others on Twitter, including a former Jolla employee. However I made it clear that there are commercial and legal limitations (i.e., the licence cannot be purchased and flashed to anything else than an official device, which in turns creates technical barriers), this is not a secret in any way. I encouraged buying a licenc

Thanks for the details. I can confirm I have write permissions on my host's $HOME with no issue, and I think I could also mount the host's / and write there. It is very convenient for me, even though I also kept a separate guest's $HOME for things I want to keep separated.

Just wanted to add that there are also some native us-intl xkb variants (with or without dead keys) coming pre-configured on SailfishOS.

Thanks for sharing your setup too, it looks very interesting and, being running in Android, it undoubtedly can be used by many more people than any Sailfish solution! I'm very happy to hear about users using their device as a desktop UMPC. 1. You two know much more than I do about hardware acceleration and how it works under the hood, to me this is just like trying to understand those green symbols falling down in the matrix, so I won't try to reply accurately to that question. All I can say is the developer of sailfish-containers told me that, theoretically, HW acceleration in LXC could

I'm not sure I understood what you meant about qwertz. Can you please elaborate @EskeRahn? Is that related to not all keys having a secondary layer for a second colour? I guess if keys are redone to change the layout, it's not changing much to the production to change which keys get a secondary layer in the first place. Their plans for Scandic already shows new keys with secondary colour compared to what we currently have on Pro1 or in other Pro1x layouts (N and K for instance). The issue would most likely be to use the previously produced keypads, to avoid wasting parts.

I have completed the draft on the gist with an additional layout with only two colours, and larger labels to make it more realistic considering what we currently have on the Pro1. I also added that our previous us-intl layouts were partly incorrect, because some keys had labels that should not exist, there were a couple duplicates, and also those layouts were showing a mix of third-level and fourth-level characters. This is an issue because our colour hint suggests that AltGr produces these characters, not Shift + AltGr. Mixing them makes it non standard and hard to follow, even if it is

I hope you get some news soon, posting to keep this thread up in the list.

The Discord channel would probably be the best way to ask more info, since I believe this is where most people are. There are also multiple Telegram channels, of which t.me/sfos_user_pro1 is probably the most relevant in your case.

I can confirm Aurora and Whatsapp would work on a Pro1 running SFOS but you would need rpms from a XA2 (meaning license + device) and it wouldn't be legal. However if you purchase a XA2 license alone and ask the community it would at least be close to morally acceptable (in my opinion, but who am I to tell something illegal is morally acceptable? D:).

LXC is such a good combination with the Pro¹ that it might be worth a video on the official forum, even though I'm not very active here: - LBRY for good connections (big file): https://open.lbry.com/@Kab:7/LXC_sailfishos_Pro1:b?r=BZ8k2XPpJvbZhRttC15UQs34pYd2SS97 - Youtube for slower connections: https://youtu.be/-dgD5jci8Dk DESCRIPTION Sorry for the annoying accent. This is an overview of full desktop Linux distributions running as LXC containers in SailfishOS, on a F(x)tec Pro1 qwerty slider phone. If not interested in Sailfish itself, jump to 06'23" f

I don't mean to self promote, the following guide it is not necessarily better than the guide on the forum, but it should be more comprehensive and provides a link to the Sailfish CI images: https://gist.github.com/Kabouik/f77539b3eb6a77b032d2fa827271b81d

Works for me. At this point I think what would determine whether we use the most minimal symbols or those more visually complex with corners or bars is whether we enclose them between brackets or not. Note that we could also just write "Fn" on the top right corner of the modifier key, and then show those symbols on their respective top right corner too, I may be equally clear that Fn is needed to use those functions. While AltGr would be in a distinct colour similar to us-intl symbols. Of course for layouts with no us-intl symbol labels, the issue vanishes because only two label colours a

Yeah I would discard those ⇤ and ⇥ from the potential candidates too.

Note that the home and end symbols you selected don't have the same bar length (I couldn't find any long bottom bar), so if we go with the bar, we'd better use the short ones for both keys.

If we suggest symbols to keep the labels short, I think those are more or less common (maybe not conventional, but at least straightforward): Page Up: ⇞ Page Down: ⇟ Home: ↖, ↸, ⭶, ⤒, ⇤, ⌜, ⇱ End: ↘, ⭸, ⤓, ⇥, ⌟, ⇲ Del: ␡, ⌦ Ins: ⎀ Source. Some are my own invention and may not make sense, some others are actually borrowed from Tab, but there wouldn't be any ambiguity in our case. We could propose a keyboard layout with that and only two label colours, with or without brackets. Note that ⎇ is also standard for Alt, albeit rarely used. This could be an

After @EskeRahn's comment, I heard from someone I can't name that, indeed, distinct label colours in addition to white are unlikely (but we never know). Blue might be possible, but I mentioned that this would mean changing the Fx label so there's no firm answer on that either. In any case, I believe we could send our message almost as is and keep the images we have, but add a couple sentences to acknowledge that layouts with multiple label colours are difficult to produce. However, this could be dealt with by printing only us-intl labels and not Fn keys (I think it's fine if they're hidde

Hey @Slion, how about swapping the left AltGr with Fn? This would make it closer to the current layout and hence maybe increase chances of having it approved. That's one of the reasons which contributed to making this choice for the qwerty proposal and it would be consistent. Both AltGr are still independent so one could configure Alt_L on the left AltGr if they don't need two Alt_R, and that would make easy Ctrl+Alt combinations on both sides. Also, Fn+Alt would be easier by default, which could be useful for Alt+F1-12. Ctrl+F1-12 would become a tad more difficult, however. Is it necessa

That's true but given those labels are just for third-level symbol, that would probably be acceptable anyway in my opinion. People who need them just need to be able to find them until they get used to the layout (which they might already be since it's standard). At worst, F(x)tec could always change the hue for something slightly lighter, or go for a layout with just intl labels on the alpha keys. Also, here we used the online editor because it is convenient and looks good, but in practice the labels seem to be printed in bigger and bolder font on the Pro1.

Absolutely, and maybe F(x)tec won't deem our proposal relevant anyway. :> In any case, I guess if they accept a layout change, it will be featured in an IGG update and those who got the Christmas perk should get the opportunity to get their device as announced and for Christmas, or wait more for a unit with the upgraded layout, so it'd still be better to send the suggestion early enough. My personal favourite is now the 2nd one (with full us-intl labels). Initially I was not a big fan of printing all labels, yellow international labels used to make the keyboard very busy and I thought

I just updated the gist with the missing pictures, and fixed a couple aesthetic issues in the others (no layout change, just fixing some alignment inconsistency when having or not having us-intl labels, and removing us-intl labels that were actually visible in dark grey in the first layout). Looks OK to me now. If you guys agree, maybe we shouldn't wait too much before sending it to porters and to Liangchen. It would maximise our chances to get it reviewed before they start production (the Xmas perk should already be under production actually).

Thanks! Yep I didn't have them and don't have the permalinks of other ones to avoid starting from scratch. I added the placeholder text so that we don't forget to add them.

I tried to add arguments to strengthen our proposal, and also emphasized that all this was a discussion where everyone was welcome, not just one isolated community member's suggestion (but I'm very grateful to Craig for starting the initiative and taking leadership here). I wanted you guys to see the revision history but didn't want to force anyone (myself included) into using a word processor and eventually get cancer, so I put my changes in a Gist that you can all review, comment and maybe edit directly (not sure). You can view the revisions from the "Revisions" tab at the top. Tho